Thread: Streetpilot v2.36/v2.37 app release for Android 4.2.2 and later

Originally Posted by belfort

Thanks for info.
I already used NTU map, but it didnt work as it should. Downloaded new and now i can search with that Adress shortcut.

Only 2.35 has a working search.

Originally Posted by osiris4isis

What does USB Charging Fix do?

It is a heavily modified Android Dalvik bytecode inside classes.dex. In simple terms, some JVM usb functions functions were removed/disabled by someone that made that apk which I found on some Chinese site. As for Native library libgarminos.so, both are identical.

Originally Posted by flagmax

It is a heavily modified Android Dalvik bytecode inside classes.dex. In simple terms, some JVM usb functions functions were removed/disabled by someone that made that apk which I found on some Chinese site. As for Native library libgarminos.so, both are identical.

I didn't think StreetPilot 2.37 was having any problem with USB charging status/icon. I keep checking if it did anything difference from the version without the charging fix.

Stability is still lacking with Taiwan map; so instead of crashing within seconds of accessing the map under 2.35, now it crashed around 5min. Longest was around 30min without crashing. When it crashed, is there a log file I can examine to find out why it crashed?

Any plan on trying to fix the graphic alignment problem with JVC under Highway mode for 800x480?

You can try get logcat. Best way is to use: adb > logdump.txt in MS dos prompt window. Then after about 30 seconds you press CTRL C, yes. Then upload the txt file and pm me a link to it.

Or try app called logcat extreme.

Hopefully we can see where it crashes either Dalvik or .so.

Originally Posted by flagmax

You can try get logcat. Best way is to use: adb > logdump.txt in MS dos prompt window. Then after about 30 seconds you press CTRL C, yes. Then upload the txt file and pm me a link to it.

Or try app called logcat extreme.

Hopefully we can see where it crashes either Dalvik or .so.

Dalvik is not existing anymore on Android 5.0 and higher.
In fact, running on Lolipop 5.1.0, I didn't experience any crashes anymore