Google Play Services GPS Crash

I'm running OCT-M 6.0.1. Every time google apps try to access location services, I get play services crashing. This does not happen with non-google apps such as waze or GPS Test.

I've tried reinstalling play services to the latest, reinstalled google maps, and cleared data for services and framework (backed up beforehand of course).

Does anyone know what could be causing this? I'm unsure where to find a crash log.

Internal storage 128 MB only after a crash

The phone(rooted) was working great and I decide to move to CM11 (to pair with my MOTO 360) as there was no official Kitkat upgrade.

CM had some issues but after a while the nav-keys started mis-behaving and random touches. So, I decide to go back to stock ROM. I followed the standard process and finally after using the LGNPST tool (I had used it in past to fix the "Security Error Boot loop" successfully).

Back to stock ROM v4.1.2 - things were stable for a while but the nav-key touch issue persisted. And one day suddenly apps started crashing. I restarted the phone and all was gone! With my internal memory only 128MB!

I can't hard-reset (it does nothing after selecting factory reset) and using the LG tool I get an error (at 85% - "Fail to write partition Primary GPT, 512th Sector.") Everytime I restart the phone, its factory reset (any app installed are gone!)

How can I repair my Primary partition? Or any way to get back my storage using a stock or custom ROM.

Thank you.

Strange Video Crash Problem

I'm having a strange issue on my HTC 10. It's an unlocked phone converted to rooted stock Verizon. When I play videos, it works the first time. Then, when I try to play another video a day or two later, the video program crashes. At first I assumed it was the VLC video app, but I have tried four different video players, and they all do the same thing ... they work at first, and then they crash later. Also, I can uninstall the app, reinstall it and it will work again for that session. Does anyone have any ideas on where to even start troubleshooting this?

How to add soft keys without crash?

So I remember on my Note 4 and S6, I add the qemu.hw.mainkeys=0 on my build prop and it never really worked on lollipop or marshmallow. Everytime I rebooted, my phone would crash and just keeps giving an error over and over...everytime I pressed ok.

I'm sure the devs know how to fix this since the custom roms for my Note 4 got rid of the error awhile back

Fingerprint Settings Menu Crash

Hi guys, New here, Had my G5 a good few months and absolutely love it!

I've not ran into any issues until yesterday evening 22/07/16. I did the software update, which was around 470mb, and since my fingerprints have not work, the phone then went into a Boot Loop, I restored it to factory settings and and then attempted to add some fingerprints, however each time I go into Settings > Fingerprints & Security > Fingerprints > Next, but as soon as I hit next the app immediately freezes and after a short period of time crashes with the usual message "Unfortunately com.android.settings isn't working" with the usual options to wait or exit, both result in exiting. I have tried reverting back to different stock roms but no luck, was hoping someone may have an idea of what is causing it. I have been through all of the app settings resetting data and cache on various things. I also commented on the facebook app crash post as this was also occurring but reverting to a previous version of facebook solved that one.

Current Software Details are as follows:
Android Version 6.0.1
Android Security Patch Level 2016-06-01
Baseband Version MPSS.TH.2.0.c1.4-00032-M8996FAAAANAZM-1
Kernel Version 3.18.20
Build Number MMB29M
Software Version V10d-EUR-XX

Thanks!
DodgyChris

Sudden lags and crash with some low end games...

So... I am using Moto G4 Plus and when i play some low end games for like 10 minutes the game starts to lag so much and then freezes, but just the games... Any ideas? I already removed Xposed and Root but the problem persists... On my old phone I had no problem with the same games and using same Xposed modules and Root apps

LG-G4 (VS986) and very odd camera-related crash

I have an LG-G4 (VS986 - Verizon), rooted (13b). On three occasions over the past week, the phone has hard-crashed (totally powered off immediately and unexpectedly, and would NOT power up, even after a battery pull). In each case, the only way to bring it back to life was to plug it into a charger, which booted it up when the power button was held - but in every case the battery was at least 80% charged at the time of the crash (and I tried two different batteries), so it wasn't a power issue. It only happened when using the camera (actually taking pictures, not browsing through the gallery). It doesn't occur every time (I shot about 15 pictures this morning, and it didn't reproduce the crash).

I also have noticed that the pictures do not flip vertically/horizontally during viewing (usually in QuickPic but also in Gallery) but Advanced Tools says the accelerometer, etc. are working fine. Tis is also recent.

Anyone else seen this?
Thanks in advance...!

Crash loop com.android.phone [logcat included]

Hello together,

after changing some preferences in the network settings, I have com.android.phone constantly crashing.
I have already tried deleting the data folders for com.android.phone , com.android.telephony.providers and wiping cache ... to no avail.

I am running ParanoidAndroid 6.0.1 on a OnePlus 2

Below is the logcat for the problem:

Code:

---

07-04 22:09:28.413 E/AndroidRuntime(7775):        at com.qti.internal.telephony.dataconnection.QtiDcTracker.<init>(QtiDcTracker.java:102)
07-04 22:09:28.413 E/AndroidRuntime(7775):        at com.qti.internal.telephony.QtiTelephonyPlugin.makeDcTracker(QtiTelephonyPlugin.java:94)
07-04 22:09:28.413 E/AndroidRuntime(7775):        at com.android.internal.telephony.TelephonyPluginDelegate.makeDcTracker(TelephonyPluginDelegate.java:108)
07-04 22:09:28.413 E/AndroidRuntime(7775):        at com.android.internal.telephony.cdma.CDMALTEPhone.<init>(CDMALTEPhone.java:94)
07-04 22:09:28.413 E/AndroidRuntime(7775):        at com.android.internal.telephony.cdma.CDMALTEPhone.<init>(CDMALTEPhone.java:85)
07-04 22:09:28.413 E/AndroidRuntime(7775):        at com.qti.internal.telephony.cdma.QtiCDMALTEPhone.<init>(QtiCDMALTEPhone.java:53)
07-04 22:09:28.413 E/AndroidRuntime(7775):        at com.qti.internal.telephony.QtiTelephonyPlugin.makeCDMALTEPhone(QtiTelephonyPlugin.java:79)
07-04 22:09:28.413 E/AndroidRuntime(7775):        at com.android.internal.telephony.TelephonyPluginDelegate.makeCDMALTEPhone(TelephonyPluginDelegate.java:140)
07-04 22:09:28.413 E/AndroidRuntime(7775):        at com.android.internal.telephony.PhoneFactory.makeDefaultPhone(PhoneFactory.java:184)
07-04 22:09:28.413 E/AndroidRuntime(7775):        at com.android.internal.telephony.PhoneFactory.makeDefaultPhones(PhoneFactory.java:86)
07-04 22:09:28.413 E/AndroidRuntime(7775):        at com.android.internal.telephony.TelephonyPluginBase.makeDefaultPhones(TelephonyPluginBase.java:46)
07-04 22:09:28.413 E/AndroidRuntime(7775):        at com.qti.internal.telephony.QtiTelephonyPlugin.makeDefaultPhones(QtiTelephonyPlugin.java:44)
07-04 22:09:28.413 E/AndroidRuntime(7775):        at com.android.internal.telephony.TelephonyPluginDelegate.makeDefaultPhones(TelephonyPluginDelegate.java:112)
07-04 22:09:28.413 E/AndroidRuntime(7775):        at com.android.phone.PhoneGlobals.onCreate(PhoneGlobals.java:353)
07-04 22:09:28.413 E/AndroidRuntime(7775):        at com.android.phone.PhoneApp.onCreate(PhoneApp.java:41)
07-04 22:09:28.413 E/AndroidRuntime(7775):        at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1014)
07-04 22:09:28.413 E/AndroidRuntime(7775):        at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4741)
07-04 22:09:28.413 E/AndroidRuntime(7775):        ... 8 more
07-04 22:09:28.415 W/ActivityManager(1112): Process com.android.phone has crashed too many times: killing!

---

Is there a possibility to get back to working condition without wiping everything?

Thanks for any tips,
hoomel

Layer Manager crash

Hello,
I here made some terrible mistake with my Galaxy note3.
I rooted my device and then installed busybox on rails.
Then I installed layer manager.
Then installed theme from Google Play!
applied the theme and then reboot.

Now as my phone reboot.
I saw that now google play is not working it crashes everytime I install any app. Theme is very ugly.
Now as I open the layer manager to remove the theme I saw that it crashes again and again ..... everytime.

Their seems no hope, how I can remove this f****** theme from my device.

I would appriciate any help.

please suggest an alternative approach than flashing stock rom via odin!!!

Sent from my F1f using Tapatalk

HELP, huawei y560-u32 crash

Need Help, i have a huawei y560-u32 smartphone and try to change the recovery, but the phone crash, the display show logo 1 seg and then turn white, do not access to recovery mode, bootloader mode dont work, adb not detect the device.

Only the PC detect the phone as "qualcomm HS_USB DIagnostics 900E COM(4)".

some help please :'(

Need help:i bricked my zte blade l3 after a firmware crash

i tried all methods posted in all forums and no one worked
1. igot permanently blackscreen no lifesign from my handy
2.recovery or bootloader etc. dont work
if want to connenct the phone on my computer it connect 2 secs later disconnnect ,then connect ,disconnect (it does that all the time i let it connected on the cable.
so thats my problem ,any idea what i can do now,please help me

thank you in advance

HELP, huawei y560-u32 crash

Need Help, i have a huawei y560-u32 smartphone and try to change the recovery, but the phone crash, the display show logo 1 seg and then turn white, do not access to recovery mode, bootloader mode dont work, adb not detect the device.

Only the PC detect the phone as "qualcomm HS_USB DIagnostics 900E COM(4)".

some help please :'(

no function at all after crash - 1d after warranty repair

Yesterday I got my G4 back from the warranty repair for the bootloop error.
Now it crashed the first time and then got stuck at the bootloader... So I removed the battery to reinsert it - and there's no function at all.
Plugging in the power cord doesn't show up a little charging animation and trying to boot/to enter stock recovery doesn't show up the LG logo at all...

... thats my first Android device I had not getting managed to survive power loss, at least the bootloader should be that power-loss proof to survive a reboot and a reset during execution - not making the whole phone unusable...