Revision history [back]

Even though other Android apps work fine with Alien Dalvik GPS support, Sygic often just hangs in the "Waiting for GPS signal" state. As it's a wide-spread app, I think, it's not a Sygic bug but that it is maybe a little more picky when evaluating the GPS data. Maybe the reported accuracy of "0" (as reported by GPS status https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2) is not accepted?

Also, GPS status often reports only "1/17" satellites for a fix, rarely it shows more than one, e.g. "3/17". Maybe Sygic interprets that as unreliable input data?

Even though other Android apps work fine with Alien Dalvik GPS support, Sygic often just hangs in the "Waiting for GPS signal" state. As it's a wide-spread app, I think, it's not a Sygic bug but that it is maybe a little more picky when evaluating the GPS data. Maybe the reported accuracy of "0" (as reported by GPS status https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2) is not accepted?

Also, GPS status often reports only "1/17" satellites for a fix, rarely it shows more than one, e.g. "3/17". Maybe Sygic interprets that as unreliable input data?

Even though other Android apps work fine with Alien Dalvik GPS support, Sygic often just hangs in the "Waiting for GPS signal" state. As it's a wide-spread app, I think, it's not a Sygic bug but that it is maybe a little more picky when evaluating the GPS data. Maybe the reported accuracy of "0" (as reported by GPS status https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2) is not accepted?

Also, GPS status often reports only "1/17" satellites for a fix, rarely it shows more than one, e.g. "3/17". Maybe Sygic interprets that as unreliable input data?

Interesting effect: When switching to the task switcher, then back to Sygic, the GPS device is re-initialized. Often, briefly Sygic works, then reverts back to "Waiting for GPS signal". So, this may be a specific problem of the data continuously reported instead of initially.