So I updated to pre3, reinstalled GApps and flashed the recovery back to CWM. As far as I can tell the battery discharges now more smoothly, thanks for this fix! With only one SIM the roaming bug fix works fine, so no R in Germany with O2/E-Plus (National Roaming).
There is just the GPS “bug” left, that GPS works really great in Location Engineer Mode and much worse and slower in every other app like Google Maps or Pokemon GO. I’m really no expert with Android, but maybe it’s because these apps are more CPU intensive which slows the GPS and maybe could be fixed if the GPS priority would be somehow increased?
Update from pre2 (named pre1 in the updater) to pre3 with the updater worked well. Of course got an error from playstore, so installed Gapps, and had to re-enter my google account data. No issues so far.
Update from pre1 to pre3 failed for me.
The updater app offeted pre3, downloaded and installed it.
After reboot there is a warning in recovery mode that signature verification failed. And a question how to proceed (see screenshot).
No matter if I select yes or no, it seens that the update is not installed.
At least the update app still shows me pre1.
The about phone menu shows me Build number ALPS.KK1.MP5.V1 and Custom build version 1467283639.
For me everything is working ok (thanks for you work @jftr), my only issue is that the battery is still erratic. It was discharging very slowing until it started a sharp drop. I noticed that while it is quickly dropping, the power button only works to wake the device, I cannot sleep, shutdown or restart it, so I removed the battery and it booted with 3%.
As @Sujus already says: CWM does not include our public key and thus cannot verify the signature. I am sorry, but I cannot give any support for CWM. Please re-flash our stock recovery (it is inside the OTA package) if flashing continues to fail.
Oh no, I do not like that. Can you please use the phone for a couple of days and see if the behavior normalizes?
Hey, I also experienced this once immediately after updating, but I wanted to wait over the weekend and observe the behaviour further. I’m also planning to do a batter reset (see #batteryguide).
The thing with the button has happened a lot to me (three times a week maybe), but I set a workaround in Gravity Box: Double tap the status bar and turn off the screen this way. Besides I’ve found out that if I press a volume button, I’m able to press the power button again afterwards. I tried to log this and found log entries that indicated a connection between volume and power button. Unfortunately it’s not reproducible so I can’t properly log the issue.
The roaming issue occurred again because I forgot to merge the changes when switching around code bases. I have already fixed this. So, if pre2 did not show the roaming sign for you, the next release won’t show it either.
There is only a need to try to fix this if pre2 did show the same wrong behavior.
AFAIK the AOSP keyboard does not properly support swiping. You have to install alternative keyboards (Swiftkey, Swype, Google Keyboard, etc. come to mind).
These could be many things … for instance your screen on time seems to be much higher. Also, powwer consumption of GSM, wifi, etc. highly depend on signal strength. Just moving to a different room of your house could mean you get significantly less battery time. Combine that with half an hour more with the screen turned on and you get such a picture… I don’t see anything unusual (unless you tell me these numbers stem from a controlled experimental environment )