Turns out this is obviously an issue with my phone, and not the new kernels I have been using. All though it has only happened with Fserve's franco.Kernel.v19.3-gbs.v15 and franco.Kernel |.v19.4| 2.6.32.46. But the problem is the same between both of them, happens less often with v19.4. But rather than bother the kernel developers I will put a general post here. I'm sure that they already have their hands full, and I don't think it's a kernel issue anymore.
The issue:
My lockscreen keeps burning the image into my LCD when I put the screen to sleep. Always is the last image it was at when I shut it off, and it takes around 3-4 hours after flashing a kernel to start with the issue.
It's basically the same type of thing that happens if you leave a computer monitor on at the same screen for day or so, the image stays on the screen for a while because it has burned itself into the monitor.
I cannot take a Logcat as it is disabled in the franco kernel I am currently running. Current specs are in my signature.
Essentially I am trying to track down the cause of this issue, as it seems to happen across different setups, no matter the LCD sleep settings I set, and doesn't go away with lower overclock settings. But when I flash my phone back to OEM specs with KDZ updater it does not produce the problem at all.
It has to be software related because if it was my hardware, It would produce the same result when KDZ updated.
Anyone have this issue at any point? Any suggestions on how to fix it?
I'm not sure how much use it'll be to you, but if it's actually a kernel issue, and not just an android problem, this might be useful:
instead of logcat you can use dmesg.
in a terminal app or adb shell:
Code:
dmesg > /sdcard/dmesg.txt
if the /sdcard path isn't appropriate for your device, replace it with something accurate.
bigsupersquid said:
I'm not sure how much use it'll be to you, but if it's actually a kernel issue, and not just an android problem, this might be useful:
instead of logcat you can use dmesg.
in a terminal app or adb shell:
Code:
dmesg > /sdcard/dmesg.txt
if the /sdcard path isn't appropriate for your device, replace it with something accurate.
Click to expand...
Click to collapse
No luck, not supported in this kernel. I return the message
Code:
dmesg > /sdcard/dmesg.txt
klogctl: Function not implemented
Just returns an empty dmesg.txt file.
gahhh, i'm sorry. thought that'd work for sure.
maybe adb bugreport?
FOUND IT!!
Turns out the screen off animation in CM7 was the cause of my issues. For whatever reason, with the screen off animation disabled my screen no longer burns any images into the LCD. I have been burn free for 2 days now.
Weird. Oh well
EDIT: **** me it's back again, what the hell? This is truly a noggin scratcher of a problem here...
I have the bugreport:
Download the bugreport(report.txt)
Compiled through Terminal Emulator v1.0.29 and taken 5 min after screen burn was noticed.
Currently running franco.Kernel v19.3 CFS to see if the problem goes away, as I ran this kernel for a week with absolutely no issues.
Update: Logcat is working on v19.3 CFS version so I was able to take a look at what the phone was doing. Turns out the screen state is set to 0 when I turn it off, and it runs all the screen state off commands properly. But, with logcat not working on v19.4 CFS I am not able to compare notes. Going to look through the bugreports I have and see if there are any differences.
Aha! I have found something that might be of some help. In the battery history section of the bugreport, v19.3 does a Kernel wake_lock when turning the screen on and off, while v19.4 is doing just a wake_lock. They may be versions of the same thing, but maybe the difference in the process is what's causing my problems? I ran v19.3 for around 6 hours today and I had no issues with screen burning.
Well, after 8 hours of 19.3 CFS I still am facing the same screen burning problem. Nothing seems to be making the problem go away. My next step is going to KDZ flash my phone back to stock and run it like that for a day. If the problem persists I am taking it in to be serviced because it is definetly a hardware problem.
Update:
Day One of running stock V10V firmware, and no screen burning occurring at all. Going to keep it running like this for the rest of the week to see if anything will pop up. Maybe CM7 went on a fritz? I dunno, I'm no closer to finding the source, but it's looking like software right now.
Been running stock V10V software for more than a week, no symptoms of any type of screen burning. Definitely software related, I am going to begin flashing again tomorrow and see if anything turns up. Will report back if I find the issue again, as for whatever reason this could have just been an anomaly I have found in the custom ROM's and kernels.
On another note, It'll be nice to have this phone running fast again
Okay, approximately 4 hours into CM7 with francokernel v19.4 BFS, I am experiencing the same LCD Screen burning issue. Nothing is making it go away in any settings. Going to try void forever and see if anything changes.
Download Bugreport HERE(log1.txt)
Shofire91 said:
Been running stock V10V software for more than a week, no symptoms of any type of screen burning. Definitely software related, I am going to begin flashing again tomorrow and see if anything turns up. Will report back if I find the issue again, as for whatever reason this could have just been an anomaly I have found in the custom ROM's and kernels.
On another note, It'll be nice to have this phone running fast again
Click to expand...
Click to collapse
How does that happen? If the screen is not on, how could an image be burned onto it? Or is it not 'physically' burned on?
dancom96 said:
How does that happen? If the screen is not on, how could an image be burned onto it? Or is it not 'physically' burned on?
Click to expand...
Click to collapse
Not too sure, it's almost like the backlight LED turns off, leaving the lockscreen image there to burn into the LCD. Or maybe just a programming anomoly?
Either way, 2 hours into void forever's rom I am getting the problem once again (argh!!).
It only seems to do this with a custom ROM, the v10v firmware ran without any LCD issues whatsoever. Now why would it do that? I ran V10V rooted and clockworkmod recovery and no LCD issues. Only with a custom ROM.
Download the bugreport here(log2.txt)
MIUI-Gen71 v0.666 Suicidal Edition
This is apparently the answer to my problems. Since it is based off of CM7.1 6.6.1 it is not producing the LCD issue that I have been having with CM7.1 6.5.7.
Been running this ROM for about a day now. No lockscreen burning issues so far. Cross my fingers and hopefully the issue is gone.
Makes sense since the other roms I've tried were based off of 6.5.7. Could have been a CM7 issue in the first place.
Shofire91 said:
MIUI-Gen71 v0.666 Suicidal Edition
This is apparently the answer to my problems. Since it is based off of CM7.1 6.6.1 it is not producing the LCD issue that I have been having with CM7.1 6.5.7.
Been running this ROM for about a day now. No lockscreen burning issues so far. Cross my fingers and hopefully the issue is gone.
Makes sense since the other roms I've tried were based off of 6.5.7. Could have been a CM7 issue in the first place.
Click to expand...
Click to collapse
i dont know it it is cm7 6.5.7 issue cuz i never experienced ur problem with this rom or rom based on 6.5.7
I'm working on the assumption that my problem is just an anomoly that I have come across. Searches returned nothing, and I was able to run 6.5.7 without a single issue for weeks, across different kernels. It just came out of nowhere, maybe it will still turn up in 6.6.1, but at this point only time will tell.
This thread is essentially a record of my findings over time to help anyone who has had this issue(there are a few, but not many) figure out where to turn on fixing the problem.
Took a bugreport in 6.6.1 MIUI just for anyone to look through and see if any differences turn up. I have yet to find something that points to the cause.
Download the bugreport(log3.txt)
UPDATE:
3 days in and nothing so far, seems to have been a problem in CM7 6.5.7. Haven't had a single bug since.
Im also experiencing the lcd burn issue on cm7 6.5.7 with goldleaf kernel... doesnt happen on other kernels tho. Ive had this issue before with stock froyo when i got my phone. Since goldenleaf or whatever is based on stock kernel then i think it must be the kernels fault...
Wierd, I had the same trouble as soon as I tried fserve's kernel as well. Mind you it was 19.3 gbs v15 where it all began for me. But yet it went away when I flashed the phone back to stock with KDZ updater, but still came back after reflashing CM7 6.5.7 with franco's 19.4 kernel, and any other kernel after that, even the stock CM7 one. Even any ROM I used that is 6.5.7 based caused the problem to come back. CM7 6.6.1 seems to be the only answer for me at this point. Not sure what is causing the problem but it seems to be based from fserve's modded kernels, but yet it only manifests itself on a few number of devices. Is your O1 a P500 or a P500h?
Mine is p500. I flashed v18b2 now. Gonna give it a couple of hours and see if the problem still exsists.
Sent from my LG-P500 using xda premium
ert69 said:
Mine is p500. I flashed v18b2 now. Gonna give it a couple of hours and see if the problem still exsists.
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Let me know how it turns out.
Shofire91 said:
Let me know how it turns out.
Click to expand...
Click to collapse
Nope. Still can see my lockscreen. I think it might be the roms fault as some have stated before. Plus, that kernel drained my batt like crazy so I went back to goldenleaf.
Sent from my LG-P500 using xda premium
Were you not having the same trouble with goldleaf as well? It has to be the ROM because I am running the setup in my signature since Sunday. No issues at all. Something about 6.5.7 and fserve's kernel don't seem to mix for certain phones. I wonder what the difference is that causes it? I wish I knew more about Unix and Java so I could figure it out. Any developers out there with a little free time?
Sent from my LG-P500h using XDA App
Related
Hello,
I'm running Gingerbard GBX0A on my Rhod100FR and noticed only two minor issues :
1st one, the less annoying :
takes in average 5-7 seconds to light the screen up when i press the power button
2nd one, a bit more annoying
unexpected reboot, last one occured in the middle of a phone call.
I was wondering it this was bugs from the kernel files, the rootfs or the build itself ?
Knowing about that would allow me to test different kernel or rootfs.
Going back to FRX06 would force me to start over configuring the whole system and resintalling the apps, unless there's to change ext2 file or something to switch from GB to FR ?
Cheers
Edit : my current kernel is 1320 dated 5/14
Long wakeup -> kernel.
Reboot -> probably kernel as well, usually a kernel panic causes reboots. Not always the kernel's fault, but the kernel should be able to handle anything without panicing.
Have you tried an older kernel? Some of the newer kernels aren't as stable. I still bundle 1276 for a reason.
Also, please post in the build thread. No need for another thread...
arrrghhh said:
Long wakeup -> kernel.
Reboot -> probably kernel as well, usually a kernel panic causes reboots. Not always the kernel's fault, but the kernel should be able to handle anything without panicing.
Have you tried an older kernel? Some of the newer kernels aren't as stable. I still bundle 1276 for a reason.
Also, please post in the build thread. No need for another thread...
Click to expand...
Click to collapse
Thanks arrrghhh, i'll go back to 1276, it seemed to far away in the past compared to 131x or 1320 and my idea was to take latest.
I've never tried older than 1295 as far as i remember. I'll give a try with 1276.
I created a new thread b/c i was not sure it was related to GB and i didn't to mispost in the build topic ... Admin can close or move
diegolvobanania said:
Hello,
I'm running Gingerbard GBX0A on my Rhod100FR and noticed only two minor issues :
1st one, the less annoying :
takes in average 5-7 seconds to light the screen up when i press the power button
2nd one, a bit more annoying
unexpected reboot, last one occured in the middle of a phone call.
I was wondering it this was bugs from the kernel files, the rootfs or the build itself ?
Knowing about that would allow me to test different kernel or rootfs.
Going back to FRX06 would force me to start over configuring the whole system and resintalling the apps, unless there's to change ext2 file or something to switch from GB to FR ?
Cheers
Edit : my current kernel is 1320 dated 5/14
Click to expand...
Click to collapse
Same issue, it was running great, fast UI, data was fine, I rebooted then the same issues appeared on my next boot>
I just wanted to let it be known, he's not the only one with these issues
I also have this problem of rebooting. its very annoying. I use the FRX06 and wistilt2 kernel. Wats more annoying is when it reboots i cant even use my winmo cos it still keeps rebooting in winmo. anyone know how to fix this pls?
I decided to go back to FRX06 with stock kernel (1276) and without overclocking because i'd like to use it daily instead of WinMo.
Gingerbread is a bot nicer, ans a couple of extr&a fetures, but is alpha - not stable enough to operate daily.
prexzone said:
I also have this problem of rebooting. its very annoying. I use the FRX06 and wistilt2 kernel. Wats more annoying is when it reboots i cant even use my winmo cos it still keeps rebooting in winmo. anyone know how to fix this pls?
Click to expand...
Click to collapse
That one's weird - I've had spontaneous autoreboots to WinMo, but I've never had WinMo itself bootloop.
You might have failing hardware?
Sounds like that battery issue people were experiencing.
Remove battery for a few hours put it in and charge it, then turn it on only AFTER charging.
There's a chip in the battery that needs resetting, this should do so.
Thanks. ur solution has been working so far but i cant be removing my battery for hours every now n then. is there a way to reset the chip on the battery of i just get a new one?
prexzone said:
Thanks. ur solution has been working so far but i cant be removing my battery for hours every now n then. is there a way to reset the chip on the battery of i just get a new one?
Click to expand...
Click to collapse
Well, hopefully this bug doesn't hit you that often. You can avoid it by shutting down before battery hits 0 (though most of the time battery hitting 0 doesn't trigger this).
You can also avoid this by:
*Getting a second battery. When this bug hits your first battery, just boot Android with the second, and then while plugged in, swap in your first battery. I believe it should start charging normally.
*Getting an external battery charger.
Last time I checked, you could pick up 3 third-party spare batteries with an external charger for like 10 bucks of eBay.
i changed my kernel n it fixed it. well not really but it doesnt bother me as much n im happy wit it now but the problem is this new kernel im using drains my battery. idk if its cos of the constant red led light. anyone know a kernel that fixes this? pls post link
prexzone said:
i changed my kernel n it fixed it. well not really but it doesnt bother me as much n im happy wit it now but the problem is this new kernel im using drains my battery. idk if its cos of the constant red led light. anyone know a kernel that fixes this? pls post link
Click to expand...
Click to collapse
Uhm, the kernel I bundle with my packages (1276) is pretty solid. You can grab a newer kernel, but some of 'em are not as stable.
arrrghhh said:
Uhm, the kernel I bundle with my packages (1276) is pretty solid. You can grab a newer kernel, but some of 'em are not as stable.
Click to expand...
Click to collapse
The only black spot i faced with 1276 is hte screen not lighting up when unlocking the device.
That happened randomly, and of course, this is alayhs when yhou need it the most.
I steped up to wilstilt2's 1300 to get rid of this.
Thanks dvs for your work and support.
It's arela pleasure to use the portage everyday.
guys can anyone pls give me the link to the kernel. whether its 1276 or wistilt 1300
If you go to ryannathans' "Intro to Android - SD card" sticky, the link to the kernels is up near the top of the first post - along with many other useful links.
prexzone said:
guys can anyone pls give me the link to the kernel. whether its 1276 or wistilt 1300
Click to expand...
Click to collapse
Here you can find tons of kernels :
http://glemsom.users.anapnea.net/android2/htc-msm-linux/
Wilstilt2 ones available from there maybe
http://forum.xda-developers.com/showthread.php?t=885550&highlight=Wistilt
but link in 1st post leads ot v1321.
i don't remeber where i founf v1300... sorry
Okay so I'm not 100% sure if this is a sure fix, but it seems to have worked for myself and my wife. We both were getting random reboots like crazy and it was getting very annoying. I remembered back in my windows mobile TP2 days that a lot of stuff gets stored on the SD card after constant flashing and tweaks. So in order to get a proper flash u normally would have to reformat ur SD card, wipe, wipe, wipe, and then flash ur ROM. That is exactly what I did with my phone as well as my wife's phone. I formatted our SD cards after backing everything up of course. I backed it up on an external harddrive, formatted, put everything back, formatted the phone with a super wipe zip I found somewhere in the development forum, installed a custom stock Rom I have been tweaking and then booted up my phone and have not had a single random reboot since. So as the title says, it is a possible fix. If u try it then please post so that other users can know if it is actually stopping the reboots or if It's just a placebo effect. Thanks and I hope I've helped someone who is extremely frustrated as I was with their 500 dollar phone randomly rebooting.
Sent from my Beastly EVO.. And did I mention it has 3D?
I fixed mine with a buisness card as a shim for the battery lol
atistang said:
I fixed mine with a buisness card as a shim for the battery lol
Click to expand...
Click to collapse
Yeah my battery wasn't loose at all. My phone would also sometimes freeze up and when I rebooted it would just be a black screen. I had to pull the battery to get it working again. I tried the auto brightness fix bit my screen would go black sometimes and rebooting did not fix. I actually had to pull the battery out.
Sent from my Beastly EVO.. And did I mention it has 3D?
See, the problem with my phone is not random reboots, but hard freezes--with custom kernels..only custom kernels. My actual ROM software is very stable.
Now, if someone can figure out why that happens, I will give them $100.
freeza said:
See, the problem with my phone is not random reboots, but hard freezes--with custom kernels..only custom kernels. My actual ROM software is very stable.
Now, if someone can figure out why that happens, I will give them $100.
Click to expand...
Click to collapse
Truth. I've never had random reboots and the only reboots I've done were solely manual because of these hardlocks from custom kernels.
If only my phone played nicely with kernels...
freeza said:
See, the problem with my phone is not random reboots, but hard freezes--with custom kernels..only custom kernels. My actual ROM software is very stable.
Now, if someone can figure out why that happens, I will give them $100.
Click to expand...
Click to collapse
Since we never had this issue with the 4G you think it could just be a borked kernel source from HTC and we are missing some valuable info in it? Or the dual core aspect of it being ours r diff than others being asynchronous, is very touchy to code and adjustments we woulda made on single cores?
Any other of the MSM8660 handsets experiencing this with their custom kernels or is it just ours? If just ours be worth looking at their stable kernel modes source to see difference n what they might be doing differently??
Sent from my PG86100 using XDA App
sgt. slaughter said:
Since we never had this issue with the 4G you think it could just be a borked kernel source from HTC and we are missing some valuable info in it? Or the dual core aspect of it being ours r diff than others being asynchronous, is very touchy to code and adjustments we woulda made on single cores?
Any other of the MSM8660 handsets experiencing this with their custom kernels or is it just ours? If just ours be worth looking at their stable kernel modes source to see difference n what they might be doing differently??
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I'm leaning more towards HTC's screwed up source. As this problem wasn't present in their 2.3.3 source, at least with netarchy's kernel. There weren't nearly as many kernels to choose from but still.
I've heard a few people say the source was either incomplete or messed up somehow. We can only hope that HTC releases an updated software version with a new kernel so that they're obligated to release the source as well, and this time hopefully it will be complete.
atistang said:
I fixed mine with a buisness card as a shim for the battery lol
Click to expand...
Click to collapse
I used a gum wrapper for mine
Sent from my PG86100 using xda premium
I'm having strange issues as well. My phone will sometimes lockup while using it and then it displays the bootanimation and gets stuck on it and I have to battery pull. And it's actually done it once so far while I was sleeping. ROM is stock but I just decided to finally update it to 2.3.4 so I flashed dastin1015's "[ROM][Sense 3.0][2.3.4][Nov. 3, 2011] Stock 2.08.651.3 Deodexed w/ Hotspot and Beats" over it and rolled. Before I flashed, I nandroid'd, Titanium'd, and My Backup Pro'd. I then booted into TWRP and flashed and rolled. I didn't clean reset before or after because I was worried about losing texts and whatnot. That seemed to go well so I flashed chad.goodman's mildAnthraX and also updated my PRI. And keep in mind I haven't touched the clock settings or voltage. Any ideas? I was considering flashing stock kernel and seeing if that fixes it. If not, then I imagine I will have to do what I least want to and clean reset my phone. Will the logcat help identity the problem here?
Lucentio said:
I'm having strange issues as well. My phone will sometimes lockup while using it and then it displays the bootanimation and gets stuck on it and I have to battery pull. And it's actually done it once so far while I was sleeping. ROM is stock but I just decided to finally update it to 2.3.4 so I flashed dastin1015's "[ROM][Sense 3.0][2.3.4][Nov. 3, 2011] Stock 2.08.651.3 Deodexed w/ Hotspot and Beats" over it and rolled. Before I flashed, I nandroid'd, Titanium'd, and My Backup Pro'd. I then booted into TWRP and flashed and rolled. I didn't clean reset before or after because I was worried about losing texts and whatnot. That seemed to go well so I flashed chad.goodman's mildAnthraX and also updated my PRI. And keep in mind I haven't touched the clock settings or voltage. Any ideas? I was considering flashing stock kernel and seeing if that fixes it. If not, then I imagine I will have to do what I least want to and clean reset my phone. Will the logcat help identity the problem here?
Click to expand...
Click to collapse
Ur on the exact setup as I am. Kernel and ROM. Stock kernel still did exactly what u mentioned above as well. After formatting my SD card I have yet to have it happen. It's been about 8 days since I formatted. After reading the posts I don't think formatting my SD card is a fix, but I too am leaning towards HTC kernel being messed up. I think sooner or later my phone is going to do it. My phone was doing exactly as u stated. Booting into the splash screen and not going past it. On some occasions my phone would either freeze up or just go black. The hard buttons would light up but not my screen. Hope this gets figured out soon.
Sent from my Beastly EVO.. And did I mention it has 3D?
Mine resets between the hours of 71-80 of being on
I'm having the same problem and I do not know how to solve it! I am so close to selling my Evo 3D and going to the SG II.
I have ran CleanRom and currently running Fresh. I have tried Mwalts kernel, Bcblends kernel, and stock kernel from Fresh stock. No matter what I tried, my phone ALWAYS resets between the hours of 71-80 of being on.
The reset happens only when I try to turn on the phone. It turns on, off really quick, then I hit the power button again, the lock screen comes on, then the phone resets. It is getting really annoying as I love having stability and this phone isn't stable at all.
Any ideas? I have exhausted everything I know. I'm running the exact same programs as I have on the Evo 4G and since it is resetting at the same hours always at the same time on different ROMS/Kernels, I'm pretty sure its not app issue. I also tried changing between the 3 radios and no change there. The only other option now is to do a fresh install of Fresh and use it stock and see what happens.
Rytt
Try setting min cpu freq to something other than 192000, I use 384000 sleep and 482000 wake. I used to have a reboots and freezes but saw that advice somewhere and gave it a shot. Presto no more issues. Battery life is no worse for wear either. Not saying this will work but worth a try.
3VO Sent
ifly4vamerica said:
Try setting min cpu freq to something other than 192000, I use 384000 sleep and 482000 wake. I used to have a reboots and freezes but saw that advice somewhere and gave it a shot. Presto no more issues. Battery life is no worse for wear either. Not saying this will work but worth a try.
3VO Sent
Click to expand...
Click to collapse
already try that
no luck it still keep rebooting while screen off
freeza said:
See, the problem with my phone is not random reboots, but hard freezes--with custom kernels..only custom kernels. My actual ROM software is very stable.
Now, if someone can figure out why that happens, I will give them $100.
Click to expand...
Click to collapse
my cdma-sense kernels having issues????
RLS9 and RLS14 should be 100% stable - and not based off of htc source
(on pre 2.17 based roms)
i think freeza gave rls9 his seal of approval for stability.. if memory serves correctly
...on my phone i use (not my test phone) im @ 242 hours uptime on rls14 and warm 3.5 r116
...no im not trolling, just looking for feedback
chad.goodman said:
my cdma-sense kernels having issues????
RLS9 and RLS14 should be 100% stable - and not based off of htc source
(on pre 2.17 based roms)
i think freeza gave rls9 his seal of approval for stability.. if memory serves correctly
...on my phone i use (not my test phone) im @ 242 hours uptime on rls14 and warm 3.5 r116
...no im not trolling, just looking for feedback
Click to expand...
Click to collapse
He said that before you found the magic fix I'm pretty sure. Notice that was back from November. Lol
Sent from my PG86100 using xda premium
Huge Thanks
thank you so much for sharing your information my evo 3d was rebooting about every 30 min and i have just been dealing with it because i had took my evo4g into the sprint store because it was rebooting aboutevery 5-10min so they looked at it and couldnt figure it out so the gave me the evo3d for free and i put the sdcard that was in my evo 4g into my evo3d without having any idea that it was the sdcard causing all of my problems so the same thing started to happen to my new evo 3d started off about every day and eventually started to reboot every 30min and i just decided that all htc devices were like this so i have been dealing with it but today i said enough is enough and looked online and saw this thread and wiped my sdcard and sure enough no reboots yet its been about 3 hours so i think its fixed
i cant thank you enough i think it got corrupt from all of the flashing i was doing
son of a ***** right as i was about to hit post the mother ****er rebooted so its not my sdcard after all should i take it in to sprint what do you think ahhh i should have never posted anything it was going so well FML!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
ps hboot 1.4 is the **** no more going to the computer to flash a rom stupid hboot 1.5
I've sometimes had trouble running custom kernels (reboots and strange behaviors) that were fixed when running the stock kernel. But, the stock kernel leaves a lot to be desired in overall performance, so I continue to kernel hop. But, from my lurking on the different ROM forums, it seems that stock is the way to go for stability at the sacrifice of performance.
I had problems with evo rebooting and that in a loop. Very annoying. For that i've changed several roms just to find out that it could probably be because of widgetsoid.
At first the rebooting after some time of use, 1-2 days. And if flashing a different kernel than the one with rom. I was going mad, the last reboot or series of constant reboot after the evo has turned itself on, has occured after i set the brightness to lowest value, it was late so i wanted a darker screen. Interesting it when i set lowest value in system or via leedroid tweaks in widgetsoid widget popup - value im at 12 %. Maybe i got the restarts because i went below 12? Since my brightness im above 12 in widgetsoid and minimal in system, my evo didn't reboot a single time.
Currently i'm at shawn3d rom. Later i'll try some other kernel and rom again and see if the reboots occured.
U get random reboots while using any brightness widget with custom roms. I've narrowed my 3d threshold for the reboots to be anything less than 5%.
No reboots if kept at or above 5% for me...
Sent from my PG86100 using Tapatalk 2
i have had success after formatting system/data/cache to ext4 in the ext4 recovery, i had random reboots and lockups while using twrp and not formatting to ext4, (in all honesty i doubt the twrp was too blame)
Hi everybody,
I'm trying to understand how to fix this problem that's affecting me since I have this device.
I've got it in my hands in the end of November, and I've quickly unlocked and rooted it to install CM7. I don't like motoblur, so I didn't use it until I had CM7 on it. After few hours of happiness, I suddenly started experiencing freezes with black screens (I had to remove battery to unlock it) and auto-reboots.
I've wiped, fastboot-wiped, re-flashed, many times but nothing.
Tried different Roms such as redpill hybrid and dark side...same!
Googling around out there I've found hundreds of users with these two bad issues, and after hours of reading, and observing my own Atrix I've figured out what follows:
There are mainly two different issues. Although they are often considered the same, I think they are separate and I have both:
GPU issue: after playing a game or any app that "stresses" the GPU I have my Atrix not waking up after screen-lock. Black screen but if you call it is up and running somewhere in the background. it appears death, and I have to remove the battery to wake it up again. Device heating at rear-bottom.
RADIO issue: when the signal isn't that good and it changes often spot it reboots all alone.
trying to understand if it is hardware related (not an issue, but maybe small differences in the hardware of different phones) yesterday I went back to stock froyo.
Since then everything seems to work properly. Incompatibility of some ROMs with my device?
I want to stay on stock for some days to a deep test, after that, I will search for a good stock gingerbread firmware to flash.
I hope to find a solution, 'cause since I don't have CM on my device I don't feel it really mine .
Sorry for my English, hope to have made myself clear.
Thanks.
What kernel are you using? Some phones can't handle a high overclock. As for a gb rom I suggest darkside.
Sent from my MB860 using XDA App
Standard kernel @ 1Ghz. I've tried Faux's kernel @1.3 and 1.4, but I did it trying to solve the issue.
After good stock froyo and stock gingerbread experiences, I'm now happily running Aura deblurred.
Thank you, now I'll stay with Aura until CM9...
If you are experiencing the same issue look here: http://forum.xda-developers.com/showthread.php?p=21277632#post21277632
Sent from my MB860 using XDA App
when i press in my touchscreen sometimes i get random direction S**k particular when im typing suck sometimes i get wrong letter. . .what is my phone problem?did my touchscreen broke?sorry for bad english
Nope, it's because of the OC kernel. Underclock to ~800MHz or flash a non-OC kernel.
You're under CM7.2, aren't you?
Sent from my GT-S5830
TeachMePlz said:
when i press in my touchscreen sometimes i get random direction S**k particular when im typing suck sometimes i get wrong letter. . .what is my phone problem?did my touchscreen broke?sorry for bad english
Click to expand...
Click to collapse
Yeah, judging from your post in my thread your phone has issues with oc. Maybe you better off to not.
sat in my one piece devil outfit as I type. . . . . no. . . really!
I already spent a lot of time on that issue, spent boirs, and flashed tons of rom, scripts, and kernels...
It was fine with froyo, but every 2.3 roms had this issue, except kpy and further.
So the problemn has been solved on official roms.
But i get this problem on EVERY custom rom.... Every, except gingereal 1.4, don't know why...
I tried all the CM version, including 7.1 (grif and behrad), 7.2 rc0 and rc1, gingercrust, and all Jusada's rom...
And the problem is in every roop...
I deeply believe it's related to kernel: it's even worst with oc kernel, but trust me, the problem happened with every kernels including non oc.
For me at least, thiz iz the biggest issue on the Ace.
Maybe i will open a new detailed topic, including all what i've done.
I would really appreciate that some dev fix this major issue, poisonning my phone with every custom rom.
Sent from my GT-lS5830 using xda premium
Darvadouille said:
I already spent a lot of time on that issue, spent boirs, and flashed tons of rom, scripts, and kernels...
It was fine with froyo, but every 2.3 roms had this issue, except kpy and further.
So the problemn has been solved on official roms.
But i get this problem on EVERY custom rom.... Every, except gingereal 1.4, don't know why...
I tried all the CM version, including 7.1 (grif and behrad), 7.2 rc0 and rc1, gingercrust, and all Jusada's rom...
And the problem is in every roop...
I deeply believe it's related to kernel: it's even worst with oc kernel, but trust me, the problem happened with every kernels including non oc.
For me at least, thiz iz the biggest issue on the Ace.
Maybe i will open a new detailed topic, including all what i've done.
I would really appreciate that some dev fix this major issue, poisonning my phone with every custom rom.
Sent from my GT-lS5830 using xda premium
Click to expand...
Click to collapse
I have exactly the same issue and i made the same experiences as you.
KPY and later fixes that issue to a certain degree but it still happens sometimes.
I came to the point that it cant be software related. Because my friends ace doesn't have that problem, no matter what rom he flashes.
So either our cpus don't run stable at stock voltage or the touchscreen is defective.
I noticed that the problem is also related to how you charge your phone. Depending on if u charge it via usb or use the wall charger. It definately happens less frequently if i use the wall charger.
So could it probably be a defective battery?
I'm really thinking of bringing it to the service point but they will prolly just flash a kpy or later fw and say it's fixed
prodal said:
I have exactly the same issue and i made the same experiences as you.
KPY and later fixes that issue to a certain degree but it still happens sometimes.
I came to the point that it cant be software related. Because my friends ace doesn't have that problem, no matter what rom he flashes.
So either our cpus don't run stable at stock voltage or the touchscreen is defective.
I noticed that the problem is also related to how you charge your phone. Depending on if u charge it via usb or use the wall charger. It definately happens less frequently if i use the wall charger.
So could it probably be a defective battery?
I'm really thinking of bringing it to the service point but they will prolly just flash a kpy or later fw and say it's fixed
Click to expand...
Click to collapse
The manual book states that if the battery is plugged in to charge, there is a chance of the touchscreen malfunctioning. I have this charging-related issue with my friend's charger (which uses a microUSB adaptor, but the phone is an old Samsung phone): the touchscreen "touches" itself (no sexual reference there).
Another bug I got (which I discussed above) is the malfunctioning touchscreen on an OC kernel.
I can almost be certain that it has nothing to do with the battery, but more with the kernel.
Sent from my GT-S5830
can someone explain this in more detail? i didn't really understood what op meant
oFFoy said:
can someone explain this in more detail? i didn't really understood what op meant
Click to expand...
Click to collapse
Basically the OP says that he's having troubles with the touchscreen, and it's really annoyinng when typing.
I (and several other people) believe it's because of the OC kernel present in Axel's CM7.2 and other ROMs based on it.
Sent from my GT-S5830
I wanted to see if I can post something without getting ridiculed. Seriously doubt that now cause I accidentally posted this in the general Q&A first and did not know how to move it or delete it so i am posing again here. Hopefully a moderator can just take care of that stray posting I made in the general area.
I am on my second ATT SGS2. First one had a GPS issue. Tried everything and finally convinced ATT warranty services that the problem was hardware. They said they would advance replace the handset. So I got it back to stock in every way except the flash counter,this was in December so long before I was aware of mobile odin. Flash counter was at about 12 when I was done trying different ROMs,mostly just try to get the GPS to work. It was in perfect shape, bone stock except for the counter. I cannot imagine I will have an issue, but has anyone ever heard of someone getting charged on a return to stock phone that had a flash counter above stock? Ill update once I know for sure the outcome.
My real question, does everyones SGH-I777 crash on occasion? If so how often? I so happy with the current code that is running on the phone with the exception that it sometimes sleeps and wont wake up, and sometimes it just plain crashes hard, locks up and has to be hard rebooted. Usually this happens about twice a day one or the other. I wiped before installing current kernel. The only reason I am not stock is cause I wanted the CKK6, 2.3.6 update to work and to keep root privaledges, but also needed my wifi cause ATT is throttling me down to dial up speeds when I reach 2GB. So wrong!!! Anyway thats another thread.
I loaded shostock with siyah kernel 2.6.35.14. after wiping everything including both caches. The GPS is solid now, phone is fast, battery is egh, I keep a charger with me... but it crashes hard from one to three times a day. Locks up playing tunes, or wont wake up with out being plugged in or hard booted. Do I have another defective handset or should I just go back to 2.3.4 and UKH7 or should I just deal with it and consider the crashes, "excellent opportunities to reboot."?
Thanks for the all the hours of fun, u know who you are.
I honestly don't remember my phone crashing at all. If it's crashing, it aint stable. Did it crash when it was stock?
yeah I mean duh right? The new handset was updated, rooted, downreved and flashed with the custom rom before it was put under any load, so I do not know if it would have crashed before. I have wiped, re downloaded, checked with hashtab and re flashed my current kernel, so it seems like it has to be hardware, again... ugh. Especially since no one else is having issues with shostock and siyah. I wonder how hard it is going to be to get warranty services to replace the second phone in 3weeks!? Lol.
Try going back to stock and run it for a couple hours to see if it still crashes. If it still crashes then more than likely hardware issues.
Sent from my SAMSUNG-SGH-I777 using xda premium
If it's crashing on stock without SetCPU to set a screen-off profile, you have a hardware problem.
I haven't had a crash, freeze, or spontaneous reboot in ages - despite running kernels that a few others have reported stability problems with (and I have effectively halted my kernel until I can get to the bottom of those reports...)
Too often is when it happens regularly, period.
I'm running CyanogenMod 9 and have almost no crashes, despite it being experimental.
Sent from my GT-I9100 using XDA App
I reverted to stock last night shortly after posting this. Ran fine until re loaded SHOstock v1.9.2-UCKK6. It is not "crashing" but it will go to sleep and not want to wake up again. I can sometimes plug in the charger and that will wake it up but other times I have to hard reboot. So no more crashing, but will not wake from sleep about 10% of the time. Not a huge deal, but its a bit weird because I know that the code I am running is ok, and it seems the hw is ok, so... not sure why this is happening. Anyway thanks all for your suggestions etc.
silashj said:
I reverted to stock last night shortly after posting this. Ran fine until re loaded SHOstock v1.9.2-UCKK6. It is not "crashing" but it will go to sleep and not want to wake up again. I can sometimes plug in the charger and that will wake it up but other times I have to hard reboot. So no more crashing, but will not wake from sleep about 10% of the time. Not a huge deal, but its a bit weird because I know that the code I am running is ok, and it seems the hw is ok, so... not sure why this is happening. Anyway thanks all for your suggestions etc.
Click to expand...
Click to collapse
This sounds like SoD (sleep of death) to me. I would recommend reading through Entropy's kernel thread (yes, it is a LOT of reading) but it might give you some insight into possible causes and/or solutions, and you'll get a great feel for where development on this device has come from, from the beginning...
I had the same problem using the latest siyah kernel, but never with entropy's. I would suggest flashing a new kernel.
Sent from my GT-I9100 using Tapatalk
1. To answer the OP question, I have experienced ONCE that was when I tried to run the Andy's TI-83 emulator on my virgin stock ROM. The result is either my fault or the application isn't compatible with the running OS.
2. With bone stock, it shouldn't crash at all. If it does, RMA.
3. If the owner(s) have "some fun" around it such rip it off, hack it up, install different kernels, different ROMs, ...... then please DO NOT complain the device is suck.
I've seen a lot of knuckleheads who tried to mod their devices, screw them up then claim "they're suck".
dandrumheller said:
This sounds like SoD (sleep of death) to me. I would recommend reading through Entropy's kernel thread (yes, it is a LOT of reading) but it might give you some insight into possible causes and/or solutions, and you'll get a great feel for where development on this device has come from, from the beginning...
Click to expand...
Click to collapse
Thanks this sounds like a plan. I have to do something things have gotten worse. About 3 out of ten times I go to put the phone to sleep now, instead of blinking out the phone takes a screen shot. My fingers are no where near any of the other buttons and it takes a screen shot over and over when I press the power button. I have to move around from screen to screen, hit the home button and then hit the power button to put it to sleep. Weird stuff, could be worse though. Did I say that I thought the phone sucks? I thought I read in one of the replies up there something like that. Aside from the GPS issue that was hardware related, and problems I have brought on myself because stock wasnt good enough, this is hands down the most awesome piece of electronics I have ever owned. iPhone smyphone. I just need to find the perfect turbo charged, rooted but as stock as possible configuration that is stable and I will be set. I really like where I am, hopefully the kernel you suggested does not change much but fixes the problems. Thanks again all.
Grab one of Entropy's DD Kernels and flash it with CWM. I'd suggest getting one from Jan or earlier. His latest ones are trying to track down a issue.
dandrumheller said:
This sounds like SoD (sleep of death) to me. I would recommend reading through Entropy's kernel thread (yes, it is a LOT of reading) but it might give you some insight into possible causes and/or solutions, and you'll get a great feel for where development on this device has come from, from the beginning...
Click to expand...
Click to collapse
axis01 said:
Grab one of Entropy's DD Kernels and flash it with CWM. I'd suggest getting one from Jan or earlier. His latest ones are trying to track down a issue.
Click to expand...
Click to collapse
Ok the noob is going to shine through here... but you say to flash with CWM. With my current config, when I enter recovery mode I am taken to the siyah kernel recovery console. Are we talking the same difference here, and when I go to flash as you mentioned can I do so with Siyah recovery or shall I flash with something that will give me back cwm first and then flash the config that you mentioned in your reply?
silashj said:
Ok the noob is going to shine through here... but you say to flash with CWM. With my current config, when I enter recovery mode I am taken to the siyah kernel recovery console. Are we talking the same difference here, and when I go to flash as you mentioned can I do so with Siyah recovery or shall I flash with something that will give me back cwm first and then flash the config that you mentioned in your reply?
Click to expand...
Click to collapse
That recovery will work. After installing the DD kernel, CWM will change.
Sent from my Galaxy SII
I get a crash here and there everyday...
Sent from my SGH-I777 using xda premium
Have only ever crashed while messing with voltages or clock speeds. if it's crashing something is wrong.
A few people's phones just do not play well with Siya kernal. Most of those people flash Entropy's DD and the sleep deaths go away... give it a try, I bet it will help!
Mine crashes a few times a day if I'm cycling through a lot of apps or installing things. (Stock+root) the other day my phone would crash anytime I tried, to watch a video in web browser. (Either mxplayer or phone)
Sent from my SAMSUNG-SGH-I777 using XDA App
T90 said:
A few people's phones just do not play well with Siya kernal. Most of those people flash Entropy's DD and the sleep deaths go away... give it a try, I bet it will help!
Click to expand...
Click to collapse
With Siyah I crashed more often than I do know with DD...
Sent from my SGH-I777 using xda premium
Ok flashed the DD from 01-30-2012
Thanks for all the help. I will post again when I know if things are better.