I got a question guys, i flashed the latest version PA for our device (PA4.5 beta 2) and notice i was having random reboots, i thought it was the rom, so i flashed CM latest nightly (2014815) & still was having reboots, so i figured it had to be an apk not playing nice & thought i was right when i noticed it was happening the most while using chrome, but it happened during the settings and some other apks, its not constant though, it very random, its like when you stay on an apk for a while, it just randomly reboots, anyone else been having this issue? or had this issue?, i both like two great theses for these roms & would feel like a fool if i cant use em lol, so any help would be appreciated, thanks
Are you wiping between flashes or dirty flashing?
If flashing clean, restore your apps (without data backups) one at a time. If you stop having the issue, then restore your app data one at a time.
If that doesn't fix it and you're flashing clean, going back to stock and doing a factory reset will almost certainly solve the issue.
frostedunit said:
Are you wiping between flashes or dirty flashing?
If flashing clean, restore your apps (without data backups) one at a time. If you stop having the issue, then restore your app data one at a time.
If that doesn't fix it and you're flashing clean, going back to stock and doing a factory reset will almost certainly solve the issue.
Click to expand...
Click to collapse
I always clean flash, I decided to flash sacs until a next major builds releases, thanks though
What kernel are you using?
Related
I have a Nexus 4 running PA 3.15, I love PA, but I get random reboots every few hours.
I rooted this phone and the only thing I flashed was PA. So it was a clean install. I tried factory resetting the phone and doing another clean install and the rebooting still exists.
I am not using an custom kernel, maybe flashing one would help my situation. I am at a crossroads, because PA and it's pie feature are amazing, but the rebooting is making me want to leave.
Any ideas on how to fix it?
Download it one more time then gapps. Wipe everything, flash PA, flash gapps wipe cache, wipe dalvik cache. It must work. Other apps install manually.
If it's using superuser, try disabling it and use supersu instead.
i found some apps hate superuser and strange stuff happens.
I will try using supersu and see what happens. Thanks.
trentgillham said:
I will try using supersu and see what happens. Thanks.
Click to expand...
Click to collapse
I am still having this problem despite clean install. did anyone find a definitive answer. thanks
jadsru1 said:
I am still having this problem despite clean install. did anyone find a definitive answer. thanks
Click to expand...
Click to collapse
I was also having the same problem, my phone sometimes get really hot and it keeps on rebooting. I tried flashing the stock ROM, new kernel everything I could but the problem still persisted. So I called up Google Customer care, as soon as I told them overheating and rebooting, they transferred my call to RMA and they replaced my phone. My phone was 5 months old and recently many people are having this problem, so its better to get it replaced. Before sending it, reflash the phone with Stock ROM and lock the bootloader. You should be fine
I've had my S4 for a little over a week now. I've been flashing different ROMS to find which one I like but all of them except for CleanROM are very, very unstable on my phone. I've tried CM, SlimBean, Graviton, and PACMan. Some are TW, some are AOSP but I get the same results for each. Device becomes unresponsive, I get FCs, random reboots. Its crazy because I had no issues at all on my Note 2. I wipe and factory reset every time, its becoming very tedious to restore each time. I do not restore system apps, I follow all instructions and still get these results. I'm wondering if I have a faulty device? Maybe a sensor or something is not liking certain things on certain apps? I've noticed that after I installed Graviton and went back to CleanROM, Titanium has stopped working and I get the Samsung lockscreen instead of the SGS4 one. I may just go back to MDL stock in Odin, re-root and see what happens...I'm currently wiping everything and fixing permissions
Sorry to hear, sometimes starting over cures 90% of all issues, and the os gets better each time.. If it were me, I would quit wasting time and odin.
Thanks, and good luck.
Don't Forget -
jedimyndtryx said:
I've had my S4 for a little over a week now. I've been flashing different ROMS to find which one I like but all of them except for CleanROM are very, very unstable on my phone. I've tried CM, SlimBean, Graviton, and PACMan. Some are TW, some are AOSP but I get the same results for each. Device becomes unresponsive, I get FCs, random reboots. Its crazy because I had no issues at all on my Note 2. I wipe and factory reset every time, its becoming very tedious to restore each time. I do not restore system apps, I follow all instructions and still get these results. I'm wondering if I have a faulty device? Maybe a sensor or something is not liking certain things on certain apps? I've noticed that after I installed Graviton and went back to CleanROM, Titanium has stopped working and I get the Samsung lockscreen instead of the SGS4 one. I may just go back to MDL stock in Odin, re-root and see what happens...I'm currently wiping everything and fixing permissions
Click to expand...
Click to collapse
Don't forget to immediately freeze the ATT update apps... Or you will get the MF3 OTA... which, for now, is NOT-ROOTABLE & Custom Recoveries NOT-Installable.
I always factory reset,wipe both cache and format system.even when I use a back up.
Sent from my SAMSUNG-SGH-I337 using xda premium
Well I ODIN'ed and went back to CleanROM. So simple. I'm dying to try one of the VZW AOSP themed TW ROMs though. Decisions, decisions. Oh man....when I first got the phone it was on MF3. I spent 3 days on craigslist and found someone to trade me their non-updated phone. Still new to this Android business. So far I love it. Don't see why I spent so many years hating. Thank you all for the help.
Hi All,
I'm having an issue with my G2. I've been running the CM11 nightlies for a while now, they've been pretty decent.
I decided to flash the newest Snapshot today when I saw it pop up on my update list. As soon as I booted, I got the error "Unfortunately, the process com.android.phone has stopped".
This happened yesterday, so I booted into recovery, cleared cash, reinstalled the rom, cleared cache again, reinstalled gapps, cleared cache again, and it worked. Now I'm not getting so lucky. Anyone have any ideas on how to fix this? I'm really hoping this isn't going to be an issue with every CM nightly moving forward.
The best solution I could find seems to be specific to HTC phones, which involves reinstalling the boot.img. I don't think that applies to us, but if it does, how can I do that.
Thanks for your help.
EtherBoo said:
Hi All,
I'm having an issue with my G2. I've been running the CM11 nightlies for a while now, they've been pretty decent.
I decided to flash the newest Snapshot today when I saw it pop up on my update list. As soon as I booted, I got the error "Unfortunately, the process com.android.phone has stopped".
This happened yesterday, so I booted into recovery, cleared cash, reinstalled the rom, cleared cache again, reinstalled gapps, cleared cache again, and it worked. Now I'm not getting so lucky. Anyone have any ideas on how to fix this? I'm really hoping this isn't going to be an issue with every CM nightly moving forward.
The best solution I could find seems to be specific to HTC phones, which involves reinstalling the boot.img. I don't think that applies to us, but if it does, how can I do that.
Thanks for your help.
Click to expand...
Click to collapse
You've done a clean flash? Meaning you wiped Dalvik, Cache, System, Factory reset? I usually erase twice and then install CM and then GAPPS then restart the phone (Don't install custom kernel) some custom kernels are having trouble because looks like they updates some things in their kernels.
xxxrichievxxx said:
You've done a clean flash? Meaning you wiped Dalvik, Cache, System, Factory reset? I usually erase twice and then install CM and then GAPPS then restart the phone (Don't install custom kernel) some custom kernels are having trouble because looks like they updates some things in their kernels.
Click to expand...
Click to collapse
Thank you.
After some more digging, I had the idea to check the development thread of the CM ROM here. Apparently, a few other users have had the same issue.
It turns out, the newest version of CM needs to be cleanly installed, a dirty flash won't work. I just did a wipe and it's now downloading all my apps and reinstalling.
*sigh* such a pain, but whatever. Could be worse.
EtherBoo said:
Thank you.
After some more digging, I had the idea to check the development thread of the CM ROM here. Apparently, a few other users have had the same issue.
It turns out, the newest version of CM needs to be cleanly installed, a dirty flash won't work. I just did a wipe and it's now downloading all my apps and reinstalling.
*sigh* such a pain, but whatever. Could be worse.
Click to expand...
Click to collapse
Yeah it can be such a pain, I flashed nightlies when they sounded like they fixed an important issue (it'd be every other day) and I flashed clean all the time. Now im just going to stick to CM11 M4 until the next milestone.
try changin network type to GLOBAL.
Need some expert assistance. The problem is my phone keeps crashing with systemui errors when using custom roms. It always happens after a reboot and usually within 1-3 days, depends on WHEN I reboot the phone. Let me give you a little backstory.
A little over a month ago, I was running AICP on my phone, but decided to try SimpleAOSP and Hells doctor.. So I created a backup in TWRP, then flashed SimpleAOSP and HD. The next day day I started getting the errors. At the time, I thought it was the kernel or a Titanium Backup glitch.
So I wiped and reflashed SimpleAOSP without HD and without restoring from TB. But the next day, systemui failed to start. I thought it might be a rom issue so I restored AICP from my TWRP backup. And I couldn't believe it when the same systemui errors happened. So I restored the backup again. Again it was okay for a few days, then error.
After that I copied everything from my phone to the PC and wiped internal storage. Then installed the same rom version from AICP that I had been using for weeks prior to all this. Same error after a few days.
So next I tried wiping internal storage again and flashing stock 4.4.4. I used that for over a week with no system errors. So I did a TWRP backup of Google stock rom, Then installed AICP again but this time without modifying any systemui type settings, I left the rom as stock as it could come. Didn't even restore apps or anything. I then the rebooted the phone a couple of times to test and the error came back. This was the same day I installed it.
So I restored the stock backup and have been running fine all week. I want to get back on a custom rom though. Any suggestions?
Am I getting no replies because I'm missing something really obvious?
Or can no one think of anything that I haven't already tried?
By the way, right after posting the OP I installed the L preview and it's been working fine so far. I figured if I had to run stock android it may as well be the latest thing.
Sent from my Nexus 4 using Tapatalk
I don't have any answer to your question but I was wondering if this happens without installing a custom kernel on CM11 and AOSP custom ROMs.
Thanks for replying.
When I tried SimpleAOSP, it was with and then without an additional kernel. I saw no difference as far as the error is concerned. I have not tried a CM11 based ROM since this all started.
Maybe I should try a custom rom that doesn't have heavy modifications like AICP has.
Sent from my Nexus 4 using Tapatalk
Are you flashing a Gapps package? A couple weeks ago when I was trying different ROMs I was getting system crashes after flashing PA Gapps and they updated. I never narrowed it down, but after uninstalling a bunch of them (News/Weather, Talkback, Keep, Newsstand, some others) so they wouldn't update, I stopped getting system crashes.
Idk why I have the feeling your theme/icon pack has something to do with it. I run pa and whenever I try to use click ui icon pack it happens to me but if I just run veu I don't have a problem. Try not using themes for a bit to see what happens
Sorry, I missed your responses, I had kinda given up on the whole thing. Android L is running good for an unfinished product.
Getting back to the original issue, no theme or icon pack was installed.
Yes, I was using PA gapps mini from 9-23. Maybe that was it.
But that would be weird because I don't remember my first ROM running PA gapps, not 100% sure... that was a month ago.
I'll try to install without any gapps package and report back. Thanks.
Sent from my Nexus 4 using Tapatalk
from my past history, I'm facing issues when I did 3 things :
1. if I just dirty flash or factory reset only before flashing new rom.
2. Did restore backup from TB (which from your explanation above, you don't have any problem TB)
Nowdays I always use wipe dalvik, system, data, cache. Because someone once told me if you changing roms, if not it's possible that the system setting from old rom will crash with the new ones. and for the wipe system part (some roms included that command in their roms zip file and some didn't).
So I had been running the unnofficial 5.0.2 CM lollipop on my phone for a while when I finally decided I would do a full wipe and flash the latest version of it (1/26). Prior to the full wipe, the phone had been running fine. But since 1/26, it started depleting battery rapidly and it had tons of input lag. So... I wiped again and went back to what I previously had... only, my problems did not go away. So then I decided I would wipe and go back to CM11. Now, it is a little better, but still is having odd lag / behavioral issues.
My question is this.... I did several full wipes. This doesnt seem to be resolving my issues. I am guessing that wipes dont really get rid of strange behavior. Is there another step? I tried the "repair" option in TWRP but that didnt help much. I am using the latest TWRP. Should I odin a factory ROM then re-root everything? If so, does knox become removable, or am I stuck with it?