Author Topic: Location Response Gibberish  (Read 3473 times)

0 Members and 1 Guest are viewing this topic.

Offline djshack

  • Newbie
  • *
  • Posts: 1
Location Response Gibberish
« on: January 08, 2012, 09:57:49 PM »
I've been testing out the Anti-Theft component of Avast! on my Nexus S 4G running ICS.  Everything seems to work, except below is a response I received when sending a LOCATE command:

Quote
avast! Anti-Theft (www.avast.com) OK: A locate command has been successfully issued.

@ :x\u000c B{< Ap ]z 8Q:7i 5 Ws^ mpN;S+znS =O1e O_7 u L 6 Pt V^ ^W +Z mpN;S+zn_vL Ntk m ]U~aZJ{ F @4 Y6n 6 3Xv I^4k2l vQM-k \X ER=N3BqwEF0+ {X#!{' s j:j;Vsp@

@ :x\u000c q\+Qp{NA wEM6{p@gnw2` Zxb, Th R]P:# hzG]2~8`;J-i{mo@nka&8 ;$n p@i} k 6^*O>k{?] Gm C fA$HM\u000c / d Gm E:wiy \u000c - Ge A> AaMw fk`d Gy Mz fZ"+' bX& F4/:f

That was three separate SMS messages.  I am on a CDMA network (Sprint) which does not support SMS messages over 160 characters.  Regardless of the cause of the issue, the LOCATE command is effectively useless to me.  Any suggestions?

Offline reinhardholzner

  • Super Poster
  • ***
  • Posts: 1364
Re: Location Response Gibberish
« Reply #1 on: January 09, 2012, 12:09:32 PM »
hi actually we use system functions to split > 160 char messages correctly. What happens if you send a normal SMS > 160 chars?

Offline reinhardholzner

  • Super Poster
  • ***
  • Posts: 1364
Re: Location Response Gibberish
« Reply #2 on: January 09, 2012, 01:04:09 PM »
we found out that this is a bug in Android system: http://code.google.com/p/android/issues/detail?id=13737

Offline reinhardholzner

  • Super Poster
  • ***
  • Posts: 1364
Re: Location Response Gibberish
« Reply #3 on: January 09, 2012, 01:53:15 PM »
the next update will contain an option to fix this problem (advanced setting).