Related
I'm posting this here because I hope some devs might be able to get a handle on the problem. I think it has something to do with the launcher.
Since I upgraded my phone to a 2.3.4 ROM, I've had constant problems with its randomly rebooting, or occasionally just freezing. (I say "rebooting", but it always gets stuck in a boot loop, and so it might as well be frozen.) The first ROM was Synergy, but I've had the same trouble on Warm, and with three or four different kernels (OC'ed and not OC'ed) on each of those ROM's. In some configurations it's better, and in some it's worse, but I've nearly always had the reboots happen at least once a day. Sometimes it happens while charging, sometimes while it's not; sometimes it happens while I'm touching it, and sometimes when I haven't touched it in hours (kind of annoying when it's my alarm clock--I missed a meeting last week). There's not a lot of consistency in when it happens, though I should say, for the record, that I've been using Launcher Pro the whole time.
Obviously, I'm not the only one with this problem: for some, like me, it started with 2.3.4 (including, in many cases, the stock OTA); for others, it started when the phone was first released; while for others, it's never happened at all. The fact that some people haven't experienced it at all may mean hardware has something to do with it, and I even read one account of a guy who took five different phones back to Sprint for replacements before finding one that worked right.
After searching high and low, I found a thread on the Sprint Community forums that suggested editing the data.prop file to keep the launcher in memory constantly (Look here and scroll down to post #9.). I tried this a couple of days ago, and it hasn't fixed the problem, but it did dramatically reduce it: I went from rebooting every two hours to rebooting once or twice a day.
I've noticed one other interesting thing: a couple of months ago, I started playing Godville, and I've been propping the phone up next to me and letting it idle with the screen on (while on USB), so that I can glance over every once in a while to see if anything is happening in the game. I've noticed that, every few minutes, the home screen wallpaper briefly replaces the app I have open; it happens so fast that I can't tell for sure if the whole launcher is coming up, but I suspect it is. I wonder if this constant yanking of the launcher into the foreground might be the source of the instability.
my mind is like..... blowwwwn
---------- Post added at 01:37 AM ---------- Previous post was at 01:28 AM ----------
no but on a serious note man... many people have had problems with reboots since the launch of the 3D, which was 2.3.3 based. I doubt that was the issue (launcher, your update, your games... gnomes...)
i would say flash the RPM PGIMG86423million update whatever that number is for the bootloader update.zip, and see if that rids you from the reboots.
for me, i fixed my reboots by getting a new SD card... i had the same issue when i first got my 3D late in july. Did it both on 2.3.3 base, and 2.3.4... it occurred to me one day that a bad disk would cause system reboots... and not being able to change out the one built into the phone... i opted for the SD card because it was cheap and i wanted a better one anyways. reboots went away immediately.
it also never occurred to me initially that my SD had been bad for a long time... not just when i had my 3D.. on my previous phone (samsung moment with froyo), whenever i would move apps to the SD card, i would always get some kind of error message. trying to move them a couple times would always successfully move the app(s) to the SD card.. i figured this was a problem with the rom i was on (speaking of my samsung moment)...
then when i transferred my card to my 3D, same problem, along with the reboots, and a light clicked on in my brain and said "***k-tard, your SD card is bad. derp."
haven't had a single reboot since then. i even wonder if the paramount number of people having reboot issues on the 3D was due to HTC possibly shipping them with defective SD cards...
just something to mix around in your brain for a bit...
Yeah, I considered the SD card as a problem, but the reboots happen even when the SD card is mounted as a USB drive. Also, a bad SD card wouldn't explain why keeping the launcher in memory dramatically reduces the problem.
I'll be giving it a try.
Just a side note. I've been using the stock kernel lately and havn't had a single reeboot. I'm on synergy rom and since he put back in the stock kernel w/ no OC I've had no issues.
I may try that, but it would be sad to not to able to OC a rooted phone. I'm starting to wonder if it's a bad internal flash drive, though.
You should try a stock ROM to see if that solves your issue if that's doesn't work maybe you have defective phone
Sent from my PG86100 using xda premium
All my problems went away when I used Senseless ROM. I think the kernel in the ROM is stock. It's been over two weeks since my phone has frozen on me and no more random reboots.
Only stable kernels are tiamat and stock. All the others cause bootloops thanks to tryin to remove ciq
Sent from my PG86100 using Tapatalk
I'm having the same reboot issues. I've noticed a few things:
1. Doesn't matter what sd card or how new, my phone reboots unexpectedly
2. Phone ONLY reboots RIGHT when the screen times out. Only on Android 2.3.4 w/ sense! It does not matter what kernel. Whatever I do, all reboots are directly related to sense on 2.3.4.
3. The only solution I have found is to deactivate the screen time out or gut HTC proprietary sense from the ROM.
P.s. I DO NOT have problemswith any ota based off 2.3.3
bloodrain954 said:
Only stable kernels are tiamat and stock. All the others cause bootloops thanks to tryin to remove ciq
Click to expand...
Click to collapse
Tiamat isn't stable for me.
MTKnife said:
Tiamat isn't stable for me.
Click to expand...
Click to collapse
Nor for me. It causes daily hard lockups that require a battery pull on my phone. Tiamat exhibited this on multiple ROMs for me.
I think trying a largely stock rom is a must as a start to tracing your problem. So is incremental additions of apps, tweaks, etc. Basic debugging and defect isolation stuff.
bloodrain954 said:
Only stable kernels are tiamat and stock. All the others cause bootloops thanks to tryin to remove ciq
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
What about bcblend by mwalt? Senseless rom has been using that for quite some time and I haven't had any issues. When it was switched to tiamat for a short time (2.5 & 2.6, i believe) I had problems with lockups and reboots. Reboots would occur when the screen timed out every once in a while.
Just curious OP - have you tried the phone on a newly installed rom without installing any side apps for a day or so and seeing if you have any problems? Back on my old nexus S 4g i had issues with a particular battery app that would give similar problems to what you are experiencing.
Tiamat has not been stable for me either. I tried many different rom and kernel combos and am still having the issue. I noticed it is mostly happeneing when the phone is plugged in. but it also happens sometimes when im on a call. So there has to be more than one issue one being the proximity sensor and i cant figure out the other ive hset charging profiles to 384max and 198 min and other low clock speeds to see if it would help. Also set a temp profile to underclock when its over 38.0 celsius. Right now im running olympus trinity xe titan i ran it for a few days with mild anthrax and it only froze/rebooted a few times a day. I tried the anthrax kernel and it rebooted twice the first half hour so i flashed tiamat last night. Im trying to give it time to settle in but it just rebooted again when i plugged into pc. I bought my phone used and rooted before i even activated it so i dont know if this is something kernel/rom related. I started another thread a few days ago about this and the few responses i got were people running stock romand kernel not rooted. So i guess all we can hope for is the devs to figure it out or sprint to give us an ota that fixes it since im starting to belive its a hardware issue.
If you're on titan freezas is recommended.
Sent from my PG86100
I saw a few people talking about that but I thought they were talking about for when he released Hades. I'm gonna find the dl link now thanks.
Sent from my PG86100 using XDA App
Cabe24i said:
Just curious OP - have you tried the phone on a newly installed rom without installing any side apps for a day or so and seeing if you have any problems? Back on my old nexus S 4g i had issues with a particular battery app that would give similar problems to what you are experiencing.
Click to expand...
Click to collapse
Not for that long a period, no--unfortunately, I haven't been in a position where I could give up most of the use of my phone for that long. Once I have grades submitted next Monday, I can probably do more methodical testing.
I'm still freaked out by the way the launcher pops up every few minutes, though--has anyone else ever seen anything like that?
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to General
One of my favorite rom and kernel combo's is infected eternity with anthrax but random reboots are common for me with any sense based rom. I run MIUI with whatever aosp kernel and everything is flawless. Other than experimenting with kernels to find battery life, MIUI is the most stable rom I have used so far and is my new daily driver!
Sent from my HTC EVO 3D using xda premium
My evo also reboots and i havent rooted my phone at all. I did get a new SD card and that reduced the amounts of reboots i get! . Although, i still get a few every week.
hope sprint/person finds a fix for this soon.
Mine did it stock / rooted stock and viper ROM I an on fresh and so far smooth as butter ... Stock rooted was awful every time it would time out bam reboot
Sent from my PG86100 using XDA App
hey folks,
i have encountered an annoying problem that has made using the s2 quite an unpleasant experience recently.
I bought my s2 about 4 months ago. after 2 weeks or so i switched to miui (galnet) and have stuck to miui ever since. later i switched to langthangs releases as well as siyahs kernels (loving both, major props to them).
around mid of december, my phone suddenly started to crash. up till then i had a couple of freezes here n there, maybe once or twice a months. but since then, even though i did not change anything, my phone has been crashing more often, like 5-10 times a week. updating kernel and rom didnt help.
i experience two types of crashes:
a) freeze: phone just stops working. i have to take out the battery to reboot
b) reboots: phone just reboots out of the blue. sometimes it reboots 3-4 times in a row, like after the first reboot the phone does nothing for 2-3 minutes, then reboots again and so on
i am not sure if that helps, but most of the time the freezes occur while using the internet, the market and playing games. reboots occur randomly, even if the phone is not used at all.
i haven't done any overclocking, just undervolting using voltage control. but i had been using the reduced voltages for weeks, long before the crashes started to occur. and yes, i did try switching back to the stock voltages.
i may have dropped my phone a couple of times, but none of the drops was really bad as it has no scratches or dents.
Anyone else having the same experience?
Is there a way to check if -maybe- the ram/rom is defect? If nothing helps, i think i ll have to flash a stock rom and submit a warranty claim
I would go on a limb saying its MIUI's fault. Wich version of Syiah are you using? Try to reflash different version, I found that 2.6.2 is stable. Also the new one 2.6.6 wich I'm currently testing is stable to, other ones were kinda buggy.
Also are you undervolting or UC'ing ?
If all else fails flash different ROM, after testing many of them I found the latest Criskelo to be stable as a rock.
The only way to really tell is to flash back to a stock rom and see if the freezes/reboots still occur...
Sent from my GT-I9100 using Tapatalk
well, i have tried different roms. and yeah, i am undervolting and underclocking (200-1000).
but isnt it strange? i have been using miui for months without any problems, and baaam ... suddenly the phone starts crashing? i mean at the time the freezes and reboots started to occur, i had been using the same system (kernel,rom,setting,apps) for weeks without any problems.
i ll try going back to stock. if that doesnt help, ill send it in.
btw. i have flash stock via odin, will the exclamation mark during the bootup process vanish?
dabrain23 said:
btw. i have flash stock via odin, will the exclamation mark during the bootup process vanish?
Click to expand...
Click to collapse
Yep, hence you flashed original firmware the dredded(by some) yellow triangle will dissapear.
It will reapear as soon as you root your device.
that last sentence was supposed to be "if i flash stock via odin ..."
ok. ill try that and report back.
BUT
if flashing a stock rom helps, the problems much likely lies with the custom rom. but if so, why did they work perfectly fine until recently?
i may have dropped my phone a couple of times, but none of the drops was really bad as it has no scratches or dents.
Logic says that is the answer .
jje
u think so?
the phone just slipped out of my hand a couple of times, but it never fell on the floor (lets say 30cm or more).
and why would sth like that cause freezes like that? i mean my sisters ace has a totally shattered glass and its still working perfectly fine.
anyway, backing up all my stuff and trying a stock rom tmr
Hello guys ...
I have a problem that I think is well known to you.
Since I changed the stock ROM on my phone, it turns off itself.
This only happens when the screen is off, and it happens even if I listening music.
Sometimes it happens as soon as I lock the screen (delay 2s and it turns off).
In an attempt to discover what it is, I downloaded the app CatLog and started recording the LogCat. But when I to recording the logcat, it doesn't turn off. I already left him one day and a half (this app really sucks the battery) and it does not shut down. And it also doesn't turn off if it on charge.
The ROMS and Kernels I tried are:
MROM CM7 (HV and SV Kernel)
neutrino
Nottatrix 4G (International and both the Tegra version)
Original CM7.2 (Stable and Nightly)
and 2 others that I can't remember the name.
The only ROM that doesn't rebooting (stayed two days without rebooting) was MROM CM9.
And I saw that some people talked about the AT & T SIM, but my phone was bought here in Brazil, and obviously, from another carrier (Claro) and have this SIM (from another carrier: Oi) at 6 month.
What is happening??
Thanks a lot.
MaxPresi said:
Hello guys ...
I have a problem that I think is well known to you.
Since I changed the stock ROM on my phone, it turns off itself.
This only happens when the screen is off, and it happens even if I listening music.
Sometimes it happens as soon as I lock the screen (delay 2s and it turns off).
In an attempt to discover what it is, I downloaded the app CatLog and started recording the LogCat. But when I to recording the logcat, it doesn't turn off. I already left him one day and a half (this app really sucks the battery) and it does not shut down. And it also doesn't turn off if it on charge.
The ROMS and Kernels I tried are:
MROM CM7 (HV and SV Kernel)
neutrino
Nottatrix 4G (International and both the Tegra version)
Original CM7.2 (Stable and Nightly)
and 2 others that I can't remember the name.
The only ROM that doesn't rebooting (stayed two days without rebooting) was MROM CM9.
And I saw that some people talked about the AT & T SIM, but my phone was bought here in Brazil, and obviously, from another carrier (Claro) and have this SIM (from another carrier: Oi) at 6 month.
What is happening??
Thanks a lot.
Click to expand...
Click to collapse
Same problem here,
Try wiping dalvik Cache about 10 times ..it worked for me ...
I also had this problem ...but it got solved becaz I had a backup of good runing rom without SOD
Can you turn the phone on if it shuts down or do you have to remove battery? I had the problem only on Neutrino rom, but I didn't do a clean install so I thought it was that
I had this problem in all ROMs based on Android 2.3.x. .. including all kernels from nottatrix, with some of them the phone not started.
But I do not have this problem with the new kernel (3.1.10) .. or with CM9 nor the CM 10.1 Epinter. The problem with this kernel is when it heats up very much, the screen tearing.
And no, I do not need to remove the battery ... if I hit once as if I turn on the screen, he turn on himself.
I've tried to save the logcat with the application Catlog and put him to save every 1 line, but not the right ... he save the log a few minutes before turning off.
As the 3.1.10 kernel works, I believe that is not a hardware defect.
My memory is: 0x00EF (0xBEEF)
TegraTevision: A03 prime
Tegraparts: mbr: 1100:100:800
thanks ...
Hi may I ask if you resolved this problem as I have it to. Thanks
lisaamybeth said:
Hi may I ask if you resolved this problem as I have it to. Thanks
Click to expand...
Click to collapse
The post just above yours has a solution... read it.
Sadly I am also on 10.1 and am also using kernel 3.1.10 but it does not stop my device from shutting down.
lisaamybeth said:
Sadly I am also on 10.1 and am also using kernel 3.1.10 but it does not stop my device from shutting down.
Click to expand...
Click to collapse
So what you're saying is that an ALPHA STAGE KERNEL AND ALPHA STAGE ROM is giving you random shut downs? What's that old saying about ALPHA STAGE anythings? Major bugs present, not suitable for daily use, use at your own risk rings a bell. Also, some devices will have the random reboot/shut down bug. That goes back to board revision. Personally, I deal with the reboots and I'm on the same ROM.
Sent from my MB860 using xda app-developers app
palmbeach05 said:
So what you're saying is that an ALPHA STAGE KERNEL AND ALPHA STAGE ROM is giving you random shut downs? What's that old saying about ALPHA STAGE anythings? Major bugs present, not suitable for daily use, use at your own risk rings a bell. Also, some devices will have the random reboot/shut down bug. That goes back to board revision. Personally, I deal with the reboots and I'm on the same ROM.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
I too deal with reboots but my experience is the same as MaxiPresi in that I had this problem in all ROMs based on Android 2.3.x. .. including all kernels from nottatrix AND the current CM stable 7.2.0 so the issue I'm experiencing is NOT only because this is an alpha build !
I've also replaced my battery for a new one but still the issue remains..
lisaamybeth said:
I too deal with reboots but my experience is the same as MaxiPresi in that I had this problem in all ROMs based on Android 2.3.x. .. including all kernels from nottatrix AND the current CM stable 7.2.0 so the issue I'm experiencing is NOT only because this is an alpha build !
I've also replaced my battery for a new one but still the issue remains..
Click to expand...
Click to collapse
In the post that I replied to, you only stated that you had issues with CM10.1/3.1.10 kernel, which is why my post was worded the way it was. you didn't specify that it was also with GB based ROMs as well. The only thing that makes sense at this point is a board/hardware related issue. As I briefly said in my last post, we all have different board revisions. We all won't see the same results. Thats why you see people talking about having screen tearing issues when others have no issue. I suspect its the same in regards to this issue.
Currently on Rootbox 6.18b build. I get quite a few SoD but I can't figure out why. Anybody know the best way to monitor for it? It's not undervolting because I'm on stock kernel at stock voltages and all that jazz. The weird thing to me is that it happens while my phone is plugged in. My Atrix would give me SoD but not if it was plugged in. I can't figure out why my OG is SoD me. Any suggestions or tips appreciated.
Thanks.
SoupySauce said:
Currently on Rootbox 6.18b build. I get quite a few SoD but I can't figure out why. Anybody know the best way to monitor for it? It's not undervolting because I'm on stock kernel at stock voltages and all that jazz. The weird thing to me is that it happens while my phone is plugged in. My Atrix would give me SoD but not if it was plugged in. I can't figure out why my OG is SoD me. Any suggestions or tips appreciated.
Thanks.
Click to expand...
Click to collapse
Those of us getting them are still trying to figure out why. I haven't had one on the newer builds...
Sent from my Optimus G using Tapatalk 4 Beta
Thanks, I appreciate the response. Glad to know I'm not the only one lol. I mean I guess it could be that I am dirty flashing each build, but I have my phone set up perfectly to me and I don't know how to back up home screens and too lazy to restore apps and all that junk lol.
After you have one you can pull a log to help.
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
Sent from my LG-E970 using xda premium
SoupySauce said:
Thanks, I appreciate the response. Glad to know I'm not the only one lol. I mean I guess it could be that I am dirty flashing each build, but I have my phone set up perfectly to me and I don't know how to back up home screens and too lazy to restore apps and all that junk lol.
Click to expand...
Click to collapse
Actually, I think I've only had one or 2 actual BSoDs on houstonn's RootBox (I've been running it exclusively for quite a while...since early to mid April or so) and those were pretty early on. My main issue is hot reboots (which are MUCH less of an issue, more like just an annoyance really). I typically was getting hot reboots approximately every 40 hours of uptime or so, but occasionally in shorter timeframes. They were also most frequently happening when the device was idle, but occasionally it would lock up and reboot while in use.
Since roughly a week or so ago, I have not had a single one - since the update houstonn put out that fixed the issue with changing pages on the lockscreen triggering hot reboots. However, due to a couple rogue wakelocks (caused by apps) requiring reboots, plus houstonn's insane release cycle, I don't think I've gone over about 30 hours of uptime at a shot since then. FWIW, I've only clean flashed 3 times since I've been on RootBox - initial install, probably 3rd or 4th revision, and then around 6/16. I've had hot reboots after every clean flash, so I'm not convinced that's a fix. Every other update I've done (almost all of them) have been dirty flashes.
A few people have been able to grab logs of events close to the times they've gotten reboots, but to my knowledge, so far, they haven't included any info that has been useful to houstonn in tracking the issue. If you are going to be chasing the issue and trying to get logs, you should probably stay updated to the latest build...this will eliminate logs showing problems caused by issues that have already been fixed. I believe houstonn, like most other devs, only provides support for whatever the current build is.
I think most of us who are having these issues on this ROM (and it appears we're a fairly small percentage of the userbase) are getting hot reboots, rather than full-on BSoDs.
dandrumheller said:
Actually, I think I've only had one or 2 actual BSoDs on houstonn's RootBox (I've been running it exclusively for quite a while...since early to mid April or so) and those were pretty early on. My main issue is hot reboots (which are MUCH less of an issue, more like just an annoyance really). I typically was getting hot reboots approximately every 40 hours of uptime or so, but occasionally in shorter timeframes. They were also most frequently happening when the device was idle, but occasionally it would lock up and reboot while in use.
Since roughly a week or so ago, I have not had a single one - since the update houstonn put out that fixed the issue with changing pages on the lockscreen triggering hot reboots. However, due to a couple rogue wakelocks (caused by apps) requiring reboots, plus houstonn's insane release cycle, I don't think I've gone over about 30 hours of uptime at a shot since then. FWIW, I've only clean flashed 3 times since I've been on RootBox - initial install, probably 3rd or 4th revision, and then around 6/16. I've had hot reboots after every clean flash, so I'm not convinced that's a fix. Every other update I've done (almost all of them) have been dirty flashes.
A few people have been able to grab logs of events close to the times they've gotten reboots, but to my knowledge, so far, they haven't included any info that has been useful to houstonn in tracking the issue. If you are going to be chasing the issue and trying to get logs, you should probably stay updated to the latest build...this will eliminate logs showing problems caused by issues that have already been fixed. I believe houstonn, like most other devs, only provides support for whatever the current build is.
I think most of us who are having these issues on this ROM (and it appears we're a fairly small percentage of the userbase) are getting hot reboots, rather than full-on BSoDs.
Click to expand...
Click to collapse
I thought hot reboots was when the phone actually rebooted itself and did not get stuck at a black screen. I'd much rather have that than bsod. I'll probably update to the latest rootbox and see if anything changes. I should probably look into whether or not I'm getting these hot reboots.
SoupySauce said:
I thought hot reboots was when the phone actually rebooted itself and did not get stuck at a black screen. I'd much rather have that than bsod. I'll probably update to the latest rootbox and see if anything changes. I should probably look into whether or not I'm getting these hot reboots.
Click to expand...
Click to collapse
You are correct. BSoD will have you stuck at a black screen (sounds like that's your issue). A hot reboot, the phone will freeze up for maybe 5 seconds, then drop to the boot animation and re-boot - more of an annoyance, and something to make a user mildly concerned about stability.
Hi! I've been reading this forum on and off for few years, but never actually posted. Hope someone here can help me sort out my issue, thanks in advance!
Basically, I've flashed a cm13 via custom recovery on my second phone - Xiaomi Mi4, and I'm having all sorts of issues with it. I bought the phone in China, and for a while
used the stock MIUI interface, but I hated all the bloated apps and weird pop-up advertising, so decided to flash. it was the first time i've attempted it, so it took some
time to figure it out
My two main issues with cm13:
1. It crashes and restarts two/three times daily for me. I mean, I've cleared cache, I basically have no apps on the phone (apart from few messaging apps and facebook).
Is it just because it's an early cm13 build, or it's a nature of custom roms? I'm wondering if switching to a snapshot cm12 build would be better? I don't really care for
android 6 features on this phone that much, I just want a stable experience.
2. The charging became uber slow, painfully so. On MIUI it'd charge to 100% in about 3 hours or so. On cm13 it takes 3-4 hours to get to 30-40%! Never seen anything like
this. Also, if the battery depletes to 0%, the phone wouldn't turn on, even plugged in for charging. It'd turn on after an hour or two into the charging process. Seems weird,
as every other android phone I've owned previously would turn on even with 0% battery if I'm plugged in.
Anyone else experience any of the listed issues? Is it just an early build, or I've done something wrong in the flashing process? I really just want a stable simple os, no advanced
features or whatever, just need it to work
Thanks!
I have been using latest nightly.. No issues no reboot.. Charging time is 3hr
mmrx said:
I have been using latest nightly.. No issues no reboot.. Charging time is 3hr
Click to expand...
Click to collapse
Thanks for reply! Would you mind telling me which gaps you've used for your build? I remember I had some sort of an issue with few gaps
I tried, I think only the smallest package worked for me. Maybe that's the issue and something in the gaps i've installed freezing/rebooting my os?
Thanks