The first tweak/fix is for a GPS update/change.
Starting with Android 5.0, GPS has been flaky for a lot of people. The device picks up satellites, gets a lock, but then loses the lock. Sometimes it then gets a lock again and holds it, sometimes it just drops it again.
This was not fixed with 5.0.1, 6.0, or 6.0.1. It took Google over a year to even acknowledge it was an issue.
A user suggested a fix in the official bug report thread:
https://code.google.com/p/android/issues/detail?id=81140#c695
They suggest telling the device to not attempt a Mobile Station Based update of GPS information.
This can be done by changing the "CAPABILITIES" value in /system/etc/gps.conf.
I've made a file to automate this. It can be flashed from TWRP.
Nexus_5_GPS_Update_0.1.zip changes /system/etc/gps.conf to not use "MSB" updates.
Nexus_5_GPS_Restore_0.1.zip changes /system/etc/gps.conf back to the default of using "MSB" updates.
-----
The second tweak/fix is for CDMA users. I use my Nexus 5 on FreedomPop (a Sprint MVNO), and on almost every boot I'm greeted with this lovely message:
"Unfortunately, Update Device has stopped."
Its crash message mentions this:
java.lang.IllegalArgumentException: You cannot keep your settings in the secure settings.
From what I've read, moving an app from /system/app to /system/priv-app is supposed to fix this. The two problem files (OmaClient.apk and UpdateSetting.apk) are both located in /system/app, not /system/priv-app.
I figured, "why not move them to priv-app?"
So I've made a file to automate this. It can be flashed from TWRP.
Nexus_5_Sprint_Update_0.1.zip moves the apps from /system/app to /system/priv-app
Nexus_5_Sprint_Restore_0.1.zip moves the apps back from /system/priv-app to /system/app
-----
I tested these on CyanogenMod 13 (May 10th nightly build). There is no binary in the zip, each just contains a script to update the system, so you can easily view them in plain-text. Since both of the issues experienced seem to be impossible to purposely reproduce, I cannot say for sure if these fix the issue.
That's why I wanted to see if the files work or help others.
You can boot to TWRP and flash the zip files there. If you use something like CM Downloader, you can add them as additional zips to flash after any ROM update.
Let me know!
Starting with Android 5.0, GPS has been flaky for a lot of people. The device picks up satellites, gets a lock, but then loses the lock. Sometimes it then gets a lock again and holds it, sometimes it just drops it again.
This was not fixed with 5.0.1, 6.0, or 6.0.1. It took Google over a year to even acknowledge it was an issue.
A user suggested a fix in the official bug report thread:
https://code.google.com/p/android/issues/detail?id=81140#c695
They suggest telling the device to not attempt a Mobile Station Based update of GPS information.
This can be done by changing the "CAPABILITIES" value in /system/etc/gps.conf.
I've made a file to automate this. It can be flashed from TWRP.
Nexus_5_GPS_Update_0.1.zip changes /system/etc/gps.conf to not use "MSB" updates.
Nexus_5_GPS_Restore_0.1.zip changes /system/etc/gps.conf back to the default of using "MSB" updates.
-----
The second tweak/fix is for CDMA users. I use my Nexus 5 on FreedomPop (a Sprint MVNO), and on almost every boot I'm greeted with this lovely message:
"Unfortunately, Update Device has stopped."
Its crash message mentions this:
java.lang.IllegalArgumentException: You cannot keep your settings in the secure settings.
From what I've read, moving an app from /system/app to /system/priv-app is supposed to fix this. The two problem files (OmaClient.apk and UpdateSetting.apk) are both located in /system/app, not /system/priv-app.
I figured, "why not move them to priv-app?"
So I've made a file to automate this. It can be flashed from TWRP.
Nexus_5_Sprint_Update_0.1.zip moves the apps from /system/app to /system/priv-app
Nexus_5_Sprint_Restore_0.1.zip moves the apps back from /system/priv-app to /system/app
-----
I tested these on CyanogenMod 13 (May 10th nightly build). There is no binary in the zip, each just contains a script to update the system, so you can easily view them in plain-text. Since both of the issues experienced seem to be impossible to purposely reproduce, I cannot say for sure if these fix the issue.
That's why I wanted to see if the files work or help others.
You can boot to TWRP and flash the zip files there. If you use something like CM Downloader, you can add them as additional zips to flash after any ROM update.
Let me know!
