[Q] GPS issue after update to 4.2.2
I recently updated from CM 4.0.4 to CM 4.2.2 (10.1.3 to be exact), and I found that my gps is ALWAYS on, no matter what I do.
What I mean by is that, when I first boot the phone, gps is off, everything is good. Then I use an app that uses GPS - most likely Google Maps, which prompts me to turn on the GPS. I do that, GPS connects just fine, Google Maps locates me using GPS, everything is good.
The problem is when I turn OFF the GPS. I turn off the GPS via notification drawer GPS button, and GPS goes off, and I exit maps. The issue is then is shown in the battery history. Even when I turn off the GPS after using it, according to battery history it was never OFF, and from that point on it would keep showing GPS as on in the battery history.
What's funny is that even though it says GPS is on in the battery history, when I go to Locations Access it is clearly shown that Access to my location is OFF, and the gps box is greyed out as well. However, battery drain seems to suggest that GPS is actually eating away my battery, since my battery drain is significantly higher. Just to check if my GPS is actually on despite saying it is off in Location Access, I try using maps, and it is clear that GPS is not working in maps.
The only way to solve this funny situation is to reboot my phone, after which it would be shown that GPS is off in the battery history. However if I turn on GPS even once, the problem happens, all over again.
I have of course checked all my apps - the only apps that access GPS are Maps, Google Now, Facebook, and GO Weather, and I've made sure that location access in these apps are off. Well, with the Location Access in the system setting off in the first place, these shouldn't be working anyway.
I tried re-flashing 10.1.3, re-flashing gapps, and factory reset, to no avail. I suspect that kernel might be an issue, since I was using an old KT kernel before I updated, and it was slightly unstable. But if that is the case, I have no idea how to fix the kernel aside from re-flashing 10.1.3.
Can anyone help me solve this problem?