Hallo, Hello, Salut,
I want to share my short story of my experience and handling of the ghost typing/typing issues and Google Play Services killing my battery.
Trivia: I followed OnePlus a long time but never had the chance to buy it (due to the lack of invites), but in december 2014 my time was there: I got an invite and bought it immediately.
It was the best decision I could have made. I had and still have a lot of fun with the device (64GB); I love it.
I never had any issues (luckily).
So here we go:
A few weeks ago, I got the OTA update for CM12 Lollipop.
In a good mood and expecting magical fairies I installed the update.
The first days everything went fine, until I noticed a weird behavior during typing something.
I ignored it the first time, but it didn't vanished, so I looked into it, did research 'n stuff.
Apparently, I am not alone. More users complained about this issue and news pages published articles.
With the announcement of a possible fix my hope began to rise but fell shortly after the message, that the fix would be removed due to battery draining.
So I decided to flash back to CM11 44S to get rid of the draining.
Easy to say, first I had to find a download link for CM11S - CM itself does not seem to provide any.
I found the rom I needed here:
http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
I have some experience flashing android phones (My old phone is a nexus 4) but I wanted to take a guide, to prevent mistakes.
I found this guide and followed it along:
https://forums.oneplus.net/threads/...oader-install-custom-recovery-and-root.64487/
Thanks to
@Chromium1
The next issue came up with flashing TWRP. EVERY SINGLE TIME I flashed it, CM decided to overwrite it with the stock recovery, even with disabled overwriting.
Later I had enough and flashed CWM without problems.
Next steps: flashing 44S and GApps.
No problems at all.
After making my phone comfortable again, installing apps and stuff I went to sleep. In the middle of the night I woke up and removed the power cable from my phone. Fully charged. Went to sleep again.
The next morning, first look on the phone: The SHOCK! 87% battery remaining. The normal value would be 95 - 97% , so what happened?
Looked into the battery usage: Google Play Services.
Okay, don't worry.
Normal use on this day.
Noticed weird touchscreen behavior again. Please, in the name of Helix, let it not be ghost typing/issues. Helix denied me.
Battery draining AND touchscreen issues I wanted to get rid of. Good job.
Tried to use it as usual. Did a bit of research for preventing the GPServices to drain my battery.
Ah! Update xnph05q available. Provides fix for the touchscreen. Download. Installing..
Aborted.
Great.
Tried again. Aborted.
Downloaded an incremental stock update and tried to flash it using CWM. Aborted. Assert fail.
Doing massive research I found this thread:
https://forums.oneplus.net/threads/fix-assert-failed-errors-when-flashing-cm-11s-05q-in-twrp. and used (if I can remember correctly) the Modified OTA zip file in method 1.
Worked like a charm. But: battery still draining. Touchscreen still drunk.
Research time.
Prevent GPS from using Wake Up and Keep Alive.
Used the inbuilt privacy manager to set this .
Didn't work. Additionally, GPS keeps crashing now because I removed its right to wake the device up.
MOAR RESEARCH!
The solution:
http://forum.xda-developers.com/gen...stemupdateservice-wakelock-t3060548?nocache=1
Bought Autostarts.
Disabled the described receivers.
OBSERVE!
Seems to work.
Next morning, 95% battery remaining. Phew. No crashs so far. Good.
But my touchscreen? Still on drugs.
I will wait with the update back to CM12 (I mean, I like 11S/Android 4.4 more) until there is a fix.
None of the solutions google came up with worked.
This is really bad because it makes a typing flow impossible.
"Lets put there a character.. And here.. Break into his typing and choose this word.. Swipe there.. But a space here.. And a dot on this position"
For my birthday, I only have one wish. Provide us a solution for the touchscreen problem, both for CM12 and CM11S.
TL;DR:
Touchscreen issues after update to CM12
Battery draining AND touchscreen issues after flashing back to CM11S
Solution for battery draining found
Still touchscreen issues.
If you followed my story, praise helix.
Let me know what you think, critics 'n stuff.
Do you have a solution for the touchscreen problem on 4.4? Experiencing it, too?
Best regards
Click to expand...
