Database Info

[Q] com.google.process.location crashing GPlay Services

Update: FIXED
Stock Rooted LG 821 32gb with xposed on 4.4.4
On start up Google Play services cashes, followed immediately by
"Unfortunately, the process com.google.process.location has stopped.
GPS still works, but it doesnt look like AGPS or network location is.
Disabling/reenabling Location Services triggers the crash again.
Don't think any recent settings caused it, I suspected a Play services autoupdate.
So, I cleared caches of Play Service, Play store, etc.
Tried removing readding google account.
Tried uninstalling/reinstalling newest Google play services, still crashes on bootup.
Searched around a few days, this particular process doesn't seem to have caused a lot of trouble for other
Any ideas?

Are you using the "Disable Location Consent" module?

got the same problem, location and play services fc at boot.
it happened after a playstore modification I did, so try to restore your playstore and it should go away.
Also even with this fc at boot, everything works fine for me

Lethargy said:
Are you using the "Disable Location Consent" module?
Click to expand...
Click to collapse
Nope, never fooled with that module. If I had would it cause a crash?

franklin01 said:
got the same problem, location and play services fc at boot.
it happened after a playstore modification I did, so try to restore your playstore and it should go away.
Also even with this fc at boot, everything works fine for me
Click to expand...
Click to collapse
Does you network location work? Do you get the recrash if you toggle location services?

network location is not working, only gps.
fc happens every boot or location toggle
I ll try to fix it later and report back>

Lethargy said:
Are you using the "Disable Location Consent" module?
Click to expand...
Click to collapse
FIXED! My apologies Lethargy. I WAS using Disable Location Consent module.
But, I sure didn't download it myself, and certainly didn't enavle it. How did it get there? Is it a default module in a new update?
How do I alert the module creator that it causes this crash?

subvertz said:
FIXED! My apologies Lethargy. I WAS using Disable Location Consent module.
But, I sure didn't download it myself, and certainly didn't enavle it. How did it get there? Is it a default module in a new update?
How do I alert the module creator that it causes this crash?
Click to expand...
Click to collapse
I assume the module creator is aware as this has affected loads of people recently.
It can't auto install. You MUST have installed it at some point. It's not a "default" module.

rootSU said:
I assume the module creator is aware as this has affected loads of people recently.
It can't auto install. You MUST have installed it at some point. It's not a "default" module.
Click to expand...
Click to collapse
I know there are no default modules, but it doesn't make any sense. I use location RELIGIOUSLY for Ingress, and would never download or install anything that sounded like it would affect my location.
In fact, I had not touched anything Xposed related in weeks leading up to the problem.
It doesn't add up.

subvertz said:
I know there are no default modules, but it doesn't make any sense. I use location RELIGIOUSLY for Ingress, and would never download or install anything that sounded like it would affect my location.
In fact, I had not touched anything Xposed related in weeks leading up to the problem.
It doesn't add up.
Click to expand...
Click to collapse
All it normally does is disable the annoying pop up that asks for you to consent to google using location data. This prompt is seen when swapping between different location modes.
Google play services updated in the last week or so. The module worked fine until that happened.
subvertz said:
Is it a default module in a new update?
Click to expand...
Click to collapse
rootSU said:
It's not a "default" module.
Click to expand...
Click to collapse
subvertz said:
I know there are no default modules
Click to expand...
Click to collapse
Im just answering your question
Sent from my Nexus 5 using Tapatalk

Lethargy said:
Are you using the "Disable Location Consent" module?
Click to expand...
Click to collapse
Wow this has been bugging the crap out of me for days. I was getting this error every time i touched my phone. It was seriously more annoying than sam i am. I was just about ready to toss my phone like a football. So glad that this worked. Thanks a lot!

Same issue here, with:
Android 4.4.4
Google Play Services 6.11
Disable Google Network Location consent module 1.2
If I disable the module I have no more problem.
I will report this issue in "Google Network Location consent module" official thread:
http://forum.xda-developers.com/showthread.php?t=2449926
---------- Post added at 04:07 PM ---------- Previous post was at 03:43 PM ----------
dimm0k said:
much thanks to @MohammadAG, but this mod is no longer required if you Google Play Services has been updated to version 6+. When you attempt to turn off location services, you'll get a checkbox that allows you to disable the popup this module used to hide...
Click to expand...
Click to collapse
I read this post just now.
Well this explains the solution of the issue.

Litlle help
subvertz said:
FIXED! My apologies Lethargy. I WAS using Disable Location Consent module.
But, I sure didn't download it myself, and certainly didn't enavle it. How did it get there? Is it a default module in a new update?
How do I alert the module creator that it causes this crash?
Click to expand...
Click to collapse
Hello all, i got the same problem here, can you please tell me which is the "module" mentioned in your post?
Where can i find it ? Is it in XPOSED Framework? I can't find it !
TIA
Val
EDIT : i found what was the module and i didn't have it installed. So I tried to install it and activate and then uninstall. Nothing change I still have this annoying message and problem with GPS...
Anyone have a solution??

[Q&A] Lollipop 5.0 runs on our msm8960s on kkbl

Q&A for Lollipop 5.0 runs on our msm8960s on kkbl
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Lollipop 5.0 runs on our msm8960s on kkbl. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Battery Life
derpyherp said:
I think its odd how there is no deep sleep state i put a screen shot of the cpu times at each cpu speed... Its odd but somehow battery life is amazing
Click to expand...
Click to collapse
I switch back to cm11 because i have 6%/hr of battery drain, (7hr/41min Screen on time, 65% left), that is for me horrible battery life.
I did not look the cpu states, but, if there is no deep sleep, it sould explain mi experience about battery.

I have the same mensage when I was in f2fs. I have to go back to ext4 to work.

Does anyone know if the AOSP Camera will be made available? I don't like the Google one since it doesn't allow me to choose the external SD card as a storage option.

The system itself boots, and runs quite smoothly from what I've tried so far. Very exciting!
But I've found that Lastpass crashes immediately when I try to launch it. I did a clean install with CM12 11/17. Has anyone else seen this behaviour with this app? I'm assuming for the moment it just hasn't yet caught up to Android 5, and I'll have to sit patiently on 4.4 until then.

Cubkyle said:
The system itself boots, and runs quite smoothly from what I've tried so far. Very exciting!
But I've found that Lastpass crashes immediately when I try to launch it. I did a clean install with CM12 11/17. Has anyone else seen this behaviour with this app? I'm assuming for the moment it just hasn't yet caught up to Android 5, and I'll have to sit patiently on 4.4 until then.
Click to expand...
Click to collapse
I don't use that app, but it's probably either one of two things (or both):
This ROM was just release back on 11/14, so it's fairly new (the 11/14 was the first release), so there could be some issues that are causing the app to fail.
The app needs to be updated to run correctly under LP. There were some major changes to the API for LP that could cause other apps to fail that are now using these deprecated API calls. The developer needs to take there app and compile it under the latest LP compiler and libs to see if it compiles.
So, you'll probably have to wait and see. So far, I've been lucky. The apps that I need to work (CoPilot USA, etc) all work. Just waiting for dhacker to figure out the correct set of libs for DRM so that Google Play Movies and Netflix start working again. They work fine under my Nexus 7 running LP, but that was an official release by Google.

iBolski said:
I don't use that app, but it's probably either one of two things (or both):
This ROM was just release back on 11/14, so it's fairly new (the 11/14 was the first release), so there could be some issues that are causing the app to fail.
The app needs to be updated to run correctly under LP. There were some major changes to the API for LP that could cause other apps to fail that are now using these deprecated API calls. The developer needs to take there app and compile it under the latest LP compiler and libs to see if it compiles.
So, you'll probably have to wait and see. So far, I've been lucky. The apps that I need to work (CoPilot USA, etc) all work. Just waiting for dhacker to figure out the correct set of libs for DRM so that Google Play Movies and Netflix start working again. They work fine under my Nexus 7 running LP, but that was an official release by Google.
Click to expand...
Click to collapse
It turns out it was simply a matter of PEBCAK. I uninstalled Android System Webview, because it has the same icon as the stock Browser, while I was removing unwanted processes.

The first time , I flashed 11/15 version, everything seems to work fine ,then I flashed gapps, then I got no signal anymore,but everything else seems to work, so I did a factory reset, the gsm signal came back again, today when I trying to flash 11/18 version, the signal gone again, this time I don't want loose my data , what should I do to get a gsm signal? *#*#4636#*#* seems not working on 11/18, sorry for my poor english

Cubkyle said:
It turns out it was simply a matter of PEBCAK. I uninstalled Android System Webview, because it has the same icon as the stock Browser, while I was removing unwanted processes.
Click to expand...
Click to collapse
Ah, I'm familiar with those errors as well as the ID10T error as well.

Works just fine, very smooth. Had no troubles with the signal at all.
However, I can't receive a call, the dialer just stops. It is possible though to make a call. Anyone had this problem?

yes had that error many times "dialer has stopped", this is work in progress man. I hope that dhacker checks this and the other thread and try to remedy some of the prob.
For that dialer has stopped error, a reboot can cure it. But again i cant rely on a phone that is going to quit when you need to make or receive a call.

So the fix for no service is still reboot and hope?
I'm on Verizon CDMA, XT926, 11/23 build, 11/22 gapps, SuperSU 2.27
Thanks.
Doug B.

I had an odd issue on 11/22 build:
When I connect my car via bluetooth, when a call comes in, pressing the answer button does nothing and the call keeps ringing forever.
Also,
Is Anyone having issues with restoring on TWRP 2.8.1.0? I tried restoring a backup I made and my phone won't boot. It just gets stuck at the cyanogen mod screen.
Edit: I restored a previous backup, installed TWRP 2.8.2.0 and then restored the backup I was trying to. It worked.

dvgb173 said:
So the fix for no service is still reboot and hope?
I'm on Verizon CDMA, XT926, 11/23 build, 11/22 gapps, SuperSU 2.27
Thanks.
Doug B.
Click to expand...
Click to collapse
On my 11/25 build data wasn't working at first, I just turned it on and off from settings and it started working.

11/25 build is working for me as far as being able to receive phone calls. I was previously getting FCs on it when an incoming call was coming, but I was also running f2fs. I've gone back to ext4 and things seem to have stabilized at this point.

This build is the dhacker? I found nothing in his link. Many changes over the previous build?

When open 3g ,call comein can not.
How to fix it?
Thank.

soowijux said:
When open 3g ,call comein can not.
How to fix it?
Thank.
Click to expand...
Click to collapse
Now, I install 30/11 it OK.
Thanks.

SMS issue
Is the sms issue (can't receive sms, although the phone I'm sending from receives the delivery report) still present in this new build (12-02)? I've tried the 11-25 build and BlissPop and none of them allowed me to receive sms... It's the one real issue that's keeping me from jumping into Lollipop
Razr HD (XT925, KK bootloader)

My device does not come out of the boot with this version.

Bluetooth settings crashing on OB12

Any fixes? It keeps crashing and reboot doesn't fix it.

Open "Beta" build. Expect bugs. Also there's a reason this build is pulled back by OnePlus. Downgrade to OB11. Everything seems fine to me on OB11.

No issues here on OB12

silvercat said:
No issues here on OB12
Click to expand...
Click to collapse
Click pair new device. I'm getting crashes on 9.0. 3 official.

Batfink33 said:
Click pair new device. I'm getting crashes on 9.0. 3 official.
Click to expand...
Click to collapse
Same problem for me. It happens every time I update the ROM, beta or not, I have to do a clean install each time ...

Anyone has fix this Bluetooth issue in ob12?

So it's still not fixed in ob14

Has this issue just yesterday in OB14. Sudden freeze and reboot. After that Bluetooth settings crash, no lock screen and theming worked buggy. Took a backup and clean flashed. No problems so far

Hello,
I had the same crash with stable 9.04 approx one week after upgrading from 9.0.3.
Suddenly, entering bluetooth made settings app force close.
I couldn't find any solution and ended up to factory reset the phone...

elmarian756 said:
Has this issue just yesterday in OB14. Sudden freeze and reboot. After that Bluetooth settings crash, no lock screen and theming worked buggy. Took a backup and clean flashed. No problems so far
Click to expand...
Click to collapse
This happens for me every two weeks... I don't know at all why it happens. I'm thinking it could be caused by the navbar gestures, SwiftKey, cf.lumen or maybe kinscreen. Do you use one of these?
I went back to 9.0.4 because of that and it still happens.

sylvn said:
This happens for me every two weeks... I don't know at all why it happens. I'm thinking it could be caused by the navbar gestures, SwiftKey, cf.lumen or maybe kinscreen. Do you use one of these?
I went back to 9.0.4 because of that and it still happens.
Click to expand...
Click to collapse
Sorry but i use none of these. In my case the rom starts to collapse itself after a few updates dirty flashed. Some system apps not showing on ocasional boots, some sudden soft reboots and then lockscreen not showing at all, theming bugs, and Bluetooth crash. I take backup using oneplus switch and titanium and fresh install open beta, restoring all doesnt take more than 20 minutes.

My bluetooth setting crash, i couldn't connect any new devices. so i searched for solution in this forum. im on OOS 9.0.4. just before i take the plunge wipe data clean install rom, i tried the following.
I first cleared Setting App cache and data, didn't work.
then i gone into recovery and cleared Dalvik cache, didn't work.
then i used Clean Master and cleared system cache, 3gb worth, and bluetooth setting worked again!
hope this helps someone in the future.

Hello guys, i just noticed that bluetooth settings crashing ,everything was working fine for me (as long as i remember), but yesterday i was trying to pair a BT controller and it happened. So let me explain, turning on and off bt affects nothing, but when it's on and you try to go to the settings by long tap on quick settings or by the settings it crashes. when it's off you can go to the settings but once you try to pair a new device it crashes, old paired devices pair when you turn on the BT so it happens only when you try to pair a new device.
I tried to go to the 9.0.6 but it was crashing there too, so i rolled back to OB19.
I'm rooted, magisk 19.2 and twrp and with stock or smurf kernel it crashes , so i ended up pairing the controller with a third party app.
I'm sure it was working before because i paired alot of devices. I tried some "fixes" like freezing the bttestmode or clearing the cache and data of the bluetooth but none of those fixed the issue. So did anyone find a solution.
Thank you

For everyone having BT crashes, try looking at your phone Bluetooth name and check if it's blank. Usually happens to me when fsync fails and I lose my ram data.

Dzemper said:
For everyone having BT crashes, try looking at your phone Bluetooth name and check if it's blank. Usually happens to me when fsync fails and I lose my ram data.
Click to expand...
Click to collapse
You just came out of nowhere, thank you it worked when i found that there was no device name in the About Section, changed it and now it works.

Dzemper said:
For everyone having BT crashes, try looking at your phone Bluetooth name and check if it's blank. Usually happens to me when fsync fails and I lose my ram data.
Click to expand...
Click to collapse
True hero right there. Thanks man !

Dzemper said:
For everyone having BT crashes, try looking at your phone Bluetooth name and check if it's blank. Usually happens to me when fsync fails and I lose my ram data.
Click to expand...
Click to collapse
You are freaking Jesus Christ sir, whole day searching around and I was about to give up and clean flash.

Dzemper said:
For everyone having BT crashes, try looking at your phone Bluetooth name and check if it's blank. Usually happens to me when fsync fails and I lose my ram data.
Click to expand...
Click to collapse
Many Thanx

Bad experience after updating to Android 10

Hey all, I have a OP 7 pro and ever since receiving the OTA update to 10.0.3 everything seems to be buggy. Soon after, 10.3.0 came along and is no better.
Some of my issues include:
- battery drain
- GPS not accurate
- Many apps showing no network connection even though I have internet
- apps crashing on their own
- play store and games won't stay logged in
There are other issues but I can't remember at there moment.
Is there a resolution for these? Can I download back to 9?
Thanks for any advice.

You are no lucky or you are a noob

Not sure how to analyze that answer.
I'm not lucky - sems to be quite a few out there who aren't lucky then... They are posts on many sites with users complaining about issues after this upgrade.
I'm a noob - relevant? Maybe I am, I used to have another XDA account which I don't use any more... Been a member since 2008 - installed my first rooted Rom - Valhalla for the Samsung Galaxy s 4g ( not the s4, the s 4g. - that was before the s2 came out).
Again, not sure what the relevance is, just trying to understand what went wrong with the OTA.

UnheardHawk said:
Hey all, I have a OP 7 pro and ever since receiving the OTA update to 10.0.3 everything seems to be buggy. Soon after, 10.3.0 came along and is no better.
Some of my issues include:
- battery drain
- GPS not accurate
- Many apps showing no network connection even though I have internet
- apps crashing on their own
- play store and games won't stay logged in
There are other issues but I can't remember at there moment.
Is there a resolution for these? Can I download back to 9?
Thanks for any advice.
Click to expand...
Click to collapse
Clear Cache in recovery, if that does not fix the issues, do a factory reset. Recommended to factory reset for maximum experience after big update., like from 9 to 10.

Did the clear cache... Still no joy
I was trying to avoid factory resetting. The upgrade on my OnePlus 5T went seamless. Oh well factory reset it is...
Just funny how Google apps seen to have the biggest issues... Lens always shows no network connection, and Google maps just plain won't pick up my location... Waze works fine which is the silly thing.
Have to wait till I get back home to do FR, thanks.

To be fair, there's not a whole lot one could say with the information given. Like are you completely stock? Rooted? What kinds of magisk modules if any? Etc...
All i can tell you is that i don't have any issues with the 10.0.3 update specifically or 10 in general.
But it does seem like your issues are related to gapps and services so I'd start there

Completely stock, I was thinking gapps... Will experiment and update

Get familiar with A/B slot partitions. It's a lot different from single slot systems.
Try a clean install through TWRP.

UnheardHawk said:
Hey all, I have a OP 7 pro and ever since receiving the OTA update to 10.0.3 everything seems to be buggy. Soon after, 10.3.0 came along and is no better.
Some of my issues include:
- battery drain
- GPS not accurate
- Many apps showing no network connection even though I have internet
- apps crashing on their own
- play store and games won't stay logged in
There are other issues but I can't remember at there moment.
Is there a resolution for these? Can I download back to 9?
Thanks for any advice.
Click to expand...
Click to collapse
Not entirely sure if this matters but are you using a carrier variant or unlocked straight from OnePlus? Also, I'm not one for factory reset, but if you were experiencing problems on 10.0.3 and now 10.3, I can only surmise that some bits were probably corrupt and a factory reset would do you some good. That or flash back to 9.5 and completely update back up. Someone mentioned in another thread, that you should install the full it's 2.1gb if you are running a custom kernel.
Sent from my OnePlus7Pro using XDA Labs

Straight from OnePlus.com on May 14...
I am on T-Mobile but didn't get it from them.

Two new changes today on my phone or of nowhere...

So sometime throughout today my gpay started failing cts and I also got a notification to update my phone's firmware. Lol
I'm still on August as I haven't had a chance to update yet. I am also running Canary Magisk and Kirisakura so clearly in not taking the OTA.
I guess Google decided to push out some server side stuff. Anyway just thought I'd throw this out there for anyone else with the same to know they are not alone.

CyberpodS2 said:
So sometime throughout today my gpay started failing cts and I also got a notification to update my phone's firmware. Lol
I'm still on August as I haven't had a chance to update yet. I am also running Canary Magisk and Kirisakura so clearly in not taking the OTA.
I guess Google decided to push out some server side stuff. Anyway just thought I'd throw this out there for anyone else with the same to know they are not alone.
Click to expand...
Click to collapse
Same thing happened to me this morning with google pay.
Notification saying google pay can't be used because of uncertified software out of nowhere. Fact is, it's a cat and mouse game. We find an exploit, google patches it.

Try to check if hardware verification is enabled
If hardware verification is enabled, CTS will fail
There are currently three solutions
1.Replace ROM, some ROM hardware verification will not be enabled
2.use MagiskHide Props config Change fingerprint
3.Use the module I made to change the name of the phone to the code name, which can maintain the original fingerprint

cracky.ice said:
Try to check if hardware verification is enabled
If hardware verification is enabled, CTS will fail
There are currently three solutions
1.Replace ROM, some ROM hardware verification will not be enabled
2.use MagiskHide Props config Change fingerprint
3.Use the module I made to change the name of the phone to the code name, which can maintain the original fingerprint
Click to expand...
Click to collapse
I just use the basic module and I'm good... I just wanted to head off the rush of posts about this. Figured it would at least corral some of them into one thread.

CyberpodS2 said:
I just use the basic module and I'm good... I just wanted to head off the rush of posts about this. Figured it would at least corral some of them into one thread.
Click to expand...
Click to collapse
It is very difficult to merge threads, because everyone has different ways, and even the wrong way makes developers difficult