redfish64 / TinyTravelTracker

Private Android GPS tracker

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

v1.1.33 and newer crash Launcher,App List etc. on some ROMs

hre999 opened this issue · comments

It seems to be a common issue with getPkgName on OEM and custom ROMs:
https://issuetracker.google.com/issues/64434571
https://gitlab.com/fdroid/fdroiddata/issues/979

In short: Starting with the Gradle Android-Plugin 3.0.0 aapt2 will be used for packaging. Some ROMS don't copy a buffer in getPkgName, which with aapt is fine, with aapt2 will produce crashes.

Actually a bug with the ROMs, but its easily fixed with adding android.enableAapt2=false to grade.properties or using build tools >=27 (the latter I did not test though)

attempt works - v1.1.36 doesn't crash.
Thanks for the quick fix

I'm using a standard OEM rom (never changed, just the usual updates from Samsung) with TTT version 1.1.36 and the map never loads for me. I've cleared app data and such, but it instantly crashes when I open it. I've managed to get to the settings page, but the main page has never worked. I'm not sure how I can provide more useful info, but I have debugging turned on when it crashes so hopefully you're getting something useful from me.

I'm sorry for logging this here, I'm not so adept at using Github, and I wasn't confident enough it was a new problem to create an issue of my own.

If I can provide more useful info, please let me know (my phone is not rooted, in case that's relevant).

MrChunks -- I just bought a Samsung myself and having the same issue. Sorry, but I have been very busy lately due to Chinese New Year and other things. If it is the same problem, it's due to the new permissions framework in Marshmallow (Android 6) and later android versions. Can you tell me the Android version you are using?

Android 7.0
Samsung experience 8.1
Kernel 4.4.13

And no sweat, glad to hear its something not too much of a pain to deal with (I hope any way :))

One thing you may want to try is going into settings, then apps, then tiny travel tracker, then permissions, and set the permission for location to on, for a temporary hack.

I'll try and have a fix done in a few days, anyway.

Yup, that did the job. Thanks for the reply/fix/workaround, I appreciate it!