XT1032 running nightly CM 12.1 freezes during phone calls - Moto G Q&A, Help & Troubleshooting

Hello guys!
For a long time I've been a happy owner of Moto G 2014(xt1032).
Oh how happy I was when it got Lollipop! Soon flashed it with cyanogenmod, my favourite ROM, and since then running on nightly, upgrading every week or so.
Unfortunately, lately an issue started to occur. During phone calls (and phone calls only) moto g freezes and soft-reboots, that is it does not go through a full reboot process, but just the final part(the one with cyan smile). It does not take long, ~20-30 seconds, however the call is disturbed, which is really annoying not only for me but also for the person I was talking with. After getting back to the usable state, a bug-reporting notification appears. I've tried reporting this for a long time now, but without any luck.
What I've done to try fix the issue is:
- rebooting the phone
- complete wipe
- reflashing all firmware possible
Some info about the phone:
model: xt1032
radio: MSM8626BP_1032.390.81.01P
kernel: stock from cyanogenmod 12.1 nightly
bootloader: 41.18
recovery: TWRP
I'm feeling helpless here, this is really driving me crazy! Is there anything I can do to fix it?
Oh, forgot to mention - I live in EU

Related

Nexus 5 random reboot

My nexus 5 reboots on average every 15 minutes during use.
It runs android 4.4.2 stock not rooted. It freeze for 5 seconds and then it reboot.
I tried do the factory data reset, but it still randomly reboots.
I got some last_kmsg files and there are 3 different "last boot reason":
- kernel_panic View attachment kmsg.txt
- wdog_reset View attachment kmsg2.txt
- wdog_bite View attachment kmsg5.txt
Please help me, what should I do?
Thanks
francesco9696 said:
My nexus 5 reboots on average every 15 minutes during use.
It runs android 4.4.2 stock not rooted. It freeze for 5 seconds and then it reboot.
I tried do the factory data reset, but it still randomly reboots.
I got some last_kmsg files and there are 3 different "last boot reason":
- kernel_panic View attachment 2516007
- wdog_reset View attachment 2516008
- wdog_bite View attachment 2516009
Please help me, what should I do?
Thanks
Click to expand...
Click to collapse
so your device is completely stock and locked with no custom rom or kernel ever or currently applied?
your kmsg's all point to issues i've seen with users on a custom kernel. specifically a user on one version of android and a kernel on a different decimal version (i.e. 4.4.2 firmware and 4.4 kernel, etc).
xBeerdroiDx said:
so your device is completely stock and locked with no custom rom or kernel ever or currently applied?
your kmsg's all point to issues i've seen with users on a custom kernel. specifically a user on one version of android and a kernel on a different decimal version (i.e. 4.4.2 firmware and 4.4 kernel, etc).
Click to expand...
Click to collapse
Yes, I didn't installed any custom rom or anything.
Maybe it's an outdated kernel (Nov 20 1013)? View attachment 2516120
If it is outdated, please tell me how I can update it (I just recived my first Android phone, I'm quite a noob (now))
Thanks
Edit:
I just got a new reboot reason: Last boot reason: hw_reset View attachment kmsg8.txt
Should I root it and install Franco kernel? Will this stop the rebooting?
I have somewhat the same problem although my device doesn't reboot every 15 minutes but rather 2 times every day.
I have the same android and kernel version so I thought I'd bump this post.
I also am experiencing similar behavior. It reboots maybe twice a day. I was on CM11 and was getting frequent reboots suddenly one day. Tried the Franco kernel with no better results. I switched back to stock everything except TWRP, now they are fewer, but still annoying. Could it maybe be an app that we have in common? I did not experience these reboots when I first got the phone, nor for months with CM11, so it stands to reason that it is something that changed recently.
kernel_panic
My phone has never been rooted and it's running stock 4.4.2 with various apps installed.
I've had occasional random reboots and some were before the 4.4.2 update. I've been unable to work out why but if I had to guess, it would be that it's Wifi related. Previously, it's happened when the phone was on the table, apparently doing "nothing". Today it happened when I was clearing a notification.
The last reboot before today was twelve days ago and the "bugreport" contained no "boot_reason". The bugreport I generated after the reboot today, shows "bootreason=kernel_panic". Not really sure what that means so maybe someone can tell me? I'd really like to know whether this is a hardware or software issue.
I did ring Google support after the reboot twelve days ago. The support person suggested I run the phone is "safe mode" or reset it and run it for a few days without installing any apps to confirm that the cause is not an app that I've installed. I haven't done that because the phone isn't very useful without any apps installed. I told the Google support person that I'd generated a bugreport but he didn't know what I was talking about and had no idea where he could forward it to if I was to send it to him.
In contrast, I also have a Samsung Galaxy S3 that has rebooted itself once in 18 months so I'm not impressed with the Nexus. Not sure what to do, next.

[Q&A] [ROM] Official Cyanogenmod 11 4.4.4 for the Moto G 4G (Peregrine)

Q&A for [ROM] Official Cyanogenmod 11 4.4.4 for the Moto G 4G (Peregrine)
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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Notification light not working with cyanogenmod
Hi,
I'm using cyanogenmod (m6 and afterwards the current daily builds) on my moto g and for quite some time I have the problem that my notification light is not working. I tried out installing the motorola led activator widget, but this doesn't help. Even when trying out an LED tester app nothing happens. The LED is not broken though as it lights up when trying to boot my moto g on low battery. Do you have any ideas how to solve this?
Thank you in advance!
Link down
Seems the latest build link is down
not I download the latest build. fallen servers
Does the ROM still have the low ram bug ?
Problem audio speakers CM11 / Stock ROM
How about, first of all, I'm new here and do not speak English, so I excuse my writing.
I have a problem with my Moto G LTE (XT1040) with Stock ROM 4.4.4 KK Brazil, although I am from LatinAmerica.
Well, I have not much to this terminal, but a few days ago I had some problems with the rom Stock, restarting not it caught more, so I decided to flash the latest rom Cyanogenmod (specifically 20,141,012) due to some stability issues decided you go back to the Stock, having the same error when freezing some applications Motorola as usual to, so back to CM and switch to the "20141016" to the few hours I started to fail the camera, remained frozen when taking a photo . After that, it went back to flashing CM rom and had the same errors, updating the "20141018" was the same, but a new bug, and could not hear the music or videos without headphones was added, calls were heard if it was not for speaker, so I decided to go back to the Stock, but apparently the problem was continuing, feel that the speakers are damaged, but the alarms or notification sounds if they worked properly. Now try wipes Cache / Dalvik from CWM but only achieved a temporary solution, put a good song and all, but to change it or put it back the audio is going.
Help me, do not know what else to do, I guess that having unlocked the bootloader and lost my warranty
Thanks in advance if this post is incorrect or I violate any rule, excuse me, I'll delete.
I'm also trying to get GPS to work on my Moto G LTE in cm11:
Based on what I read here, I reflashed stock, and tried it out, had no problems at all. Then restored the cm11 nandroid I had made, and it couldn't see any satellites still. Will restoring the nandroid backup also restore the not-working-gps then? What is being saved by unlocking the gps? Will I have different results from backing up everything with titanium backup, then going back to stock, using gps, reinstalling cm, and restoring the backed up apps? It's much more of a pain to do it that way, but if it works, I'll find the time...
This is a canadian xt1040, btw, in case it makes a difference.
UPDATE: I went ahead and reinstalled stock, played with gps for a while, and it worked without any trouble, then reinstalled CM11 (oct 21 nightly this time) restored my backed up apps with titanium backup (not any system apps). Unfortunately, still no gps at all. It never sees a single satellite. Is there anything else to try?
Hello,
First of all, thank you and all people to contributing and helping developing CM for this device!
I only have one question about GPS bug :
You indicate that it's necessary to have a GPS lock in the stock ROM first to enable GPS in CM.
Does a fix for this bug is intended/possible or the only one solution is to reinstall the stock rom, enable GPS and install CM?
Thanks in advance.
Audio solved
It updated my previous query, I could solve the problem of audio speaker, I began to disassemble the phone and as imagined, I found steel wool at the entrance and were making contact, so the cell believed to have headphones all the time .
Enable GPS in Moto G Nightly
This is in response to jac0708 in the thread this thread who asked:
Mind expanding on these two? What is the low ram bug? And how do you get a lock from stock for the gps fix?
Sorry for noobishness
Click to expand...
Click to collapse
The answer I found for the GPS not working was that when I installed CM11 within hours after taking delivery of my Moto G, the GPS would not get a fix. The solution is explained here by colinw:
Posted 11 October 2014 - 10:42 PM
Okay I just fixed my problem following some other post for a Moto phone.
1) Made a (nandroid) backup using clockwordmod of my current setup (cyanogen 11)
2) Restored old backup of a stock rom (I restored back to the one that came with my phone)
3) Then I had to USE the GPS - hadn't done that yet. Also made sure it was set to Device Only mode in settings->location because someone somewhere suggested it.
4) Restored to cyanogen rom.
5) Working!!
Click to expand...
Click to collapse
Just wanted to add that it doesn't always work. I tried at least three times, restoring stock, using gps, and then restoring my backup before I had gps working in CM. But it does work now! Be patient, and maybe just leave the phone with the stock, sitting on maps for a while. Perhaps I rushed it before?

Install CM11 from stock 5.0.2

I want to ask if there is any problem (flicker screen, red notification on booting up...) when I install CM11 from stock 5.0.2 on Falcon Moto G XT1032? (follow this official guide on CyanogenMod: http://wiki.cyanogenmod.org/w/Install_CM_for_falcon)
Thank you.
I've done this recently and the only issue I've noticed is the screen flickering problem. The solution is to simply press the power button to lock the screen then unlock it and it should be fixed. You only have to do this once but if you reboot your phone you will have to lock/unlock again on first boot.
Thank you for your answer. Just to be sure, did you follow CM guide? Is there anything important which I should be careful about? (I did the same thing with several phones but still noob)
I just booted into custom recovery (I use Philz) and wiped the different partitions along with /cache and /dalvik. You can follow the guide and use the push method or you can use sideload which I did.
I did that and now i have problems with the mac address (i was using 5.1.1) my shows me a different mac and i don't know how fix it, but if i back to LP the problem is solved.
It's a bootloader issue for sure and general happen because you're bootloader is updated to Lolipop 5.0.2 and now you install kitkat as cm 11 over Lolipop.
In simple words your bootloader is new while the software is old
screen flickering issue can be resolved by downgrade bootloader but "BE EXTREMELY CAUTIOUS" failed to upgrade bootloader make your device permanently dead and downgrading is not recommended....
I will recommend try cm12.1 it's rock solid stable as cm11
I finished installed CM 11, firstly the prob is screen flickering. Then after installing all my apps, the android.com.systemui was crashed over and over and cannot use anymore. I reflashed CM and gapps and reinstalled apps but it happened again. Finally, I had to returned to Lollipop.
Anyway, thank you all for your help
Same thing happened to me unfortunately but I've found this one here and it is working beautifully. Try it and see if it works for you without the constant systemui errors.
Thank you. At the moment i am quite happy with GPE version. It seems that this version GPE 5.1.1 is better than Moto stock one.

Moto G will not stay turned off

Hi guys
I have CM11 installed, the problem I have is when is power off the Moto G, it automatically restarts. I want to be able to keep it off to charge quicker.
Any ideas?
bigmaz said:
Hi guys
I have CM11 installed, the problem I have is when is power off the Moto G, it automatically restarts. I want to be able to keep it off to charge quicker.
Any ideas?
Click to expand...
Click to collapse
Which CM11 build are you using? i built one my self with latest sources and i got the same problem, it's probably due to a specific commit we've probably already identified, (i tried to fix it wit the help of Alberto97 and i failed, more or less, is that i tried to use Lollipop kernel on CM11 to avoid the screen flickering, i got a black screen instead of the automatically restart because of the updated kernel), anyway i just dropped it, the only reason i've tried to get a fully working CM11 was a bug with Motorola update 5.X (yes, stock ROM has that bug too and we get RIL binaries/libraries from it) and my provider only (H3G ITA), when making a call, it doesn't show the number that i called in the recent calls, but it shows "private number" instead.
I've recently received a good offer by a different provider, so i don't longer need to back to KitKat.
Here is the build info. Thanks

[Completed] Note 4 unstable for seemingly no reason

Hey folks, first of all, sorry but I couldn't find anything that helped.
I have a Galaxy Note 4 (SM-N910F (international Version); Codename: "trltexx") and had flashed an unofficial version of Cyanogenmod 14.1. Except for a few bugs, it was running fine.
I've then changed to Lineage OS 14.1, obviously unofficial as well. This was running fine too and had less bugs (i.e. camera was working unlike with CM).
Well, then, after about a week or so, the phone became unstable and just won't recover from it since then - at least two weeks.
System and Play Store apps/services began to crash (sometimes several at once), the device restarts/turns off randomly or keeps displaying the boot animation and won't turn on till I take the battery out and put it back in.
The weird thing is, these problems sometimes don't occur at all and everything runs nice and smooth and later, everything starts again and is even worse. It feels like the phone is destroying and recovering itself over and over again.
Right now, I'm running the latest version of Ressurrection Remix OS (V5.8.1./Android 7.1.1).
Well, I'd like to thank you in advance for your answers.
User422 said:
Hey folks, first of all, sorry but I couldn't find anything that helped.
I have a Galaxy Note 4 (SM-N910F (international Version); Codename: "trltexx") and had flashed an unofficial version of Cyanogenmod 14.1. Except for a few bugs, it was running fine.
I've then changed to Lineage OS 14.1, obviously unofficial as well. This was running fine too and had less bugs (i.e. camera was working unlike with CM).
Well, then, after about a week or so, the phone became unstable and just won't recover from it since then - at least two weeks.
System and Play Store apps/services began to crash (sometimes several at once), the device restarts/turns off randomly or keeps displaying the boot animation and won't turn on till I take the battery out and put it back in.
The weird thing is, these problems sometimes don't occur at all and everything runs nice and smooth and later, everything starts again and is even worse. It feels like the phone is destroying and recovering itself over and over again.
Right now, I'm running the latest version of Ressurrection Remix OS (V5.8.1./Android 7.1.1).
Well, I'd like to thank you in advance for your answers.
Click to expand...
Click to collapse
Greetings and welcome to assist. Have you tried asking in the rom threads to see if anyone else is having the same issues ? Unfortunately using cm/lineage based roms can have bugs as they are not based on samsung firmware
Regards
Sawdoctor
Hi, thanks for the answer. I wanted to say that I went down to resurrection remix Rom which is based on Android 6 (Marshmallow).
It's fine now.
Now I'm just looking to find a way to hide my root. Can't use my banking app anymore since I've rooted my device.
Update 2: The phone problems I have described reoccur over and over again. A factory reset via TWRP fixes that and then the phone slowly goes back to the old problems.
I don't know what to do anymore except for doing this over and over again.

Categories

Resources