Is anyone else having an issue with their screen flickering randomly (& constantly) when they flash a CM10 based rom? I've never had the issue once in stock ice cream sandwich based roms. As soon as I flash a CM10 rom, the issue starts. Anyone else having this issue & is there a fix for it? I love the speed of Jelly Bean, but the screen problem is so annoying that I keep going back to TW/ICS. It's happened on all 3 CM10 based roms I've flashed.
What kind of flickering? A dark to light repeated flicker when it's dimming as the screen is still on? or a flicker where the screen flashes off and then back on?
---> Brought to you in part by my T999 / T-Mobile Galaxy SIII
Kinda like flashing off and back on. Almost like a strobe. The screen doesn't actually turn off. It just flickers real quick. I've been playing around with different settings trying to fix it. No luck yet. I noticed that a new kernel was released today. I'm going to install that to see if it fixes the issue. It's worth a shot.
There was no point in making a thread. U obviously use cm10 or aokp and if u read the threads it is a known issue. Its definitely being worked on. Turn off force GPU rendering in developer options for now ....it helps
this happens on stock rom as well. known issue :/
It's a HW overlay issue. Qualcomm is still updating their drivers for vsync (Butter).
mrmako777 said:
this happens on stock rom as well. known issue :/
Click to expand...
Click to collapse
I'm on team sonics freegs3 RC 6 which is based off the stock rom and have yet to experience this... running the adama v3 kernel as well.
The only thing I notice is when the screen is dimming, sometimes it flickers dark to light a few times before staying dim then turns off.
Are you doing anything specific when this occurs or is it random?
---> Brought to you in part by my T999 / T-Mobile Galaxy SIII
OTAw said:
I'm on team sonics freegs3 rom which is based on stock and have yet to experience this... running the adama v3 kernel as well.
The only thing I notice is when the screen is dimming, sometimes it flickers dark to light a few times before staying dim then turns off.
Are you doing anything specific when this occurs or is it random?
---> Brought to you in part by my T999 / T-Mobile Galaxy SIII
Click to expand...
Click to collapse
typically does it when the keyboard is open. somewhere around here theres a thread about it
I just pinpointed the problem. It's SwiftKey. I just went a half hour with no issues. As soon as I installed SwiftKey, the screen started flickering again. My issue had nothing to do with GPU rendering. I hope this helps anyone else who has been having the same issue.
Sent from my SGH-T999 using xda premium
Ok I think I see something similar to what you guys are talking about. I usually have been seeing it in the Google chrome app when I go to open a new tab.. the tab(s) slots will start flickering and go haywire for a moment.
----
And I'm not using swift key as mentioned above.
---> Brought to you in part by my T999 / T-Mobile Galaxy SIII
I used to have the flicker too til I updated to xquizit v16 ...
Sent from my SGH-T999 using xda premium
Did you try turning off "Force GPU rendering" as sarni suggested? Maybe that's where your particular issue lies. I'm just glad it's software related. Shouldn't be long before we see a fix.
Fuse8499 said:
Did you try turning off "Force GPU rendering" as sarni suggested? Maybe that's where your particular issue lies. I'm just glad it's software related. Shouldn't be long before we see a fix.
Click to expand...
Click to collapse
Seems to be automatically turned off, at least on mine :/
---> Brought to you in part by my T999 / T-Mobile Galaxy SIII
yea its definitely software related. you see it big time in aosp/ jb roms mainly such as cm10 or aokp jb. im running aokp jb build that whitehawkx has out and I do see it. If i keep gpu rendering off it flickers a lot less. basically qualcomm is updating vsync almost everyday and the devs are adding it in as it comes i assume. it will get better over time....anyone running jb aokp go to settings/about phone/android version tap that ten times or so to get the easter egg and u will see a lot of flickering
OTAw said:
Seems to be automatically turned off, at least on mine :/
---> Brought to you in part by my T999 / T-Mobile Galaxy SIII
Click to expand...
Click to collapse
You have to manually check it every time you reboot.
Normally I wouldn't harp on someone for posting a thread that could be answered with a simple search but this is just ridiculous. The flickering issue is probably the largest current bug on all CM10 ROMs and has been discussed countless times in all of the CM10 ROM threads as well as the new kernel threads.
You need to read a little before posting in a panic.
I wasn't in the panic, pal. Thank you for your constructive response!
Sent from my SGH-T999 using xda premium
Fuse8499 said:
Did you try turning off "Force GPU rendering" as sarni suggested? Maybe that's where your particular issue lies. I'm just glad it's software related. Shouldn't be long before we see a fix.
Click to expand...
Click to collapse
It's not "Force GPU rendering" that stops the flickering. You have to check "Disable Hardware Overlay" every time you reboot to stop the flickering at the moment.
Also, to the one individual who said Swiftkey is the issue, it's definitely not. The issue occurs some time after you flash the roms - even if you don't install any third party apps. Like someone else already said, it's more likely to be an issue with the constant driver updates Qualcomm is releasing. Eventually, it should go away.
Hayhay said:
It's not "Force GPU rendering" that stops the flickering. You have to check "Disable Hardware Overlay" every time you reboot to stop the flickering at the moment.
Also, to the one individual who said Swiftkey is the issue, it's definitely not. The issue occurs some time after you flash the roms - even if you don't install any third party apps. Like someone else already said, it's more likely to be an issue with the constant driver updates Qualcomm is releasing. Eventually, it should go away.
Click to expand...
Click to collapse
You are correct sir, it is the HW Overlay, disable it, flickering goes away...
has anyone experienced a tiny flicker when pressing the power button to turn the screen off? i seem to be having this issue with CM10
Related
Hi everyone,
I've looked for a solution all over the net, but seems like no one had this problem before (guess i'm a special girl...):
The vibrate feedback when touching the screen just stopped working, in spite of the settings under "settings -> sounds -> vibrate on touch".
It started after an update to AOKP rom - milestone 5 (based on ICS 4.0.4) + Franco kernel nightly r151, but effects all the other roms. Maybe one untouched system file damaged.
I've tried everything: restore from previous nandroid backup, another rom (CM9), another kernel, another launcher, I even wiped everything and flashed new and clean rom-stock from google developers' page. And yet - no vibrate feedback.
The wired thing is that the haptic feedback is working in few specific applications, like the build-in ICS keyboard and the dialer Dialer-One, so it probably not some hardware failure.
All this time there are five softkeys that still have haptic feedback: the buttons of the nav-bar, the button that opens the applications drawer and the google-search widget.
I've tried using "KickBack" instead, but it's too aggressive and very uncomfortable.
PLEASE, PLEASE - Help me!
Same thing happened to me. I had the exact same setup and the haptic feedback went away after I flashed the kernel. Since I've had lots of issues when trying custom kernels, I just restored a nandroid and went back to the kernel included with aokp.
Sent from my Galaxy Nexus using XDA
Restore fixed my issue, so I'm not sure exactly what to tell you.
Sent from my Galaxy Nexus using XDA
taappel said:
Restore fixed my issue, so I'm not sure exactly what to tell you.
Click to expand...
Click to collapse
I've seen some ppl's msgs that even simple reboot fixed their vibrate problem.
Didn't work for me, unfortunately
Some kernels have haptic adjustment, see pic for kernel does.
I'm running Franco 152 and mines fine.
I know trinity kernels lower it
Sent from my Galaxy Nexus using XDA
Sveke said:
Some kernels have haptic adjustment, see pic for kernel does.
I'm running Franco 152 and mines fine.
I know trinity kernels lower it
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I'm also using Franco kernel, but I don't think this is the problem because i've tried some other kernels and none of them fixed my haptic.
Hi TaliKa
I've just had this problem myself but it happens long after I flashed aokp m5 + franco r152 (too) so I'm not exactly sure what caused it. However after I went to clear my cache and dalvik cache, everything seems fine again.
nich0145 said:
Hi TaliKa
I've just had this problem myself but it happens long after I flashed aokp m5 + franco r152 (too) so I'm not exactly sure what caused it. However after I went to clear my cache and dalvik cache, everything seems fine again.
Click to expand...
Click to collapse
Thanks guys, but as I wrote in the first msg, those actions didn't help.
Is there any pro here who can offer a profound solution that I didn't tried before?
Which system file responsible for the haptic feedback?
Guess I'll have to stuck without haptic feedback...
Sveke said:
Some kernels have haptic adjustment, see pic for kernel does.
I'm running Franco 152 and mines fine.
I know trinity kernels lower it
Click to expand...
Click to collapse
How can I adjust the haptic feedback feature in Trinity kernel?
+1
just wanted to say...exactly the same thing happened to me (started with aokp milestone 5 and vibration gone afterwards...)
im trying several things to get it back...i use it alot (at work and most of the time..its on vibrate)
hopefully we'll find a solution
Yeah this just happened to me too. It was working fine for awhile on AOKP and then all of a sudden it stopped. No idea what happened exactly. I tried whiping everything and restoring CM9 but that didn't work either. I thought maybe hardware but the phone vibrated on boot so it isn't that. Hopefully we find a fix...
takomar said:
+1
just wanted to say...exactly the same thing happened to me (started with aokp milestone 5 and vibration gone afterwards...)
im trying several things to get it back...i use it alot (at work and most of the time..its on vibrate)
hopefully we'll find a solution
Click to expand...
Click to collapse
Dacian said:
Yeah this just happened to me too. It was working fine for awhile on AOKP and then all of a sudden it stopped. No idea what happened exactly. I tried whiping everything and restoring CM9 but that didn't work either. I thought maybe hardware but the phone vibrated on boot so it isn't that. Hopefully we find a fix...
Click to expand...
Click to collapse
unfortunately I didn't get any solution yet. Realy depressing.
I promise to update about any progress, and hope you'll both do the same...
Just don't give up! it isn't hardware thing, so there must be solution somewhere.
TaliKa said:
unfortunately I didn't get any solution yet. Realy depressing.
I promise to update about any progress, and hope you'll both do the same...
Just don't give up! it isn't hardware thing, so there must be solution somewhere.
Click to expand...
Click to collapse
im starting to believe its a hardware issue (well at least for me) i mean i dont even get a vibration upon booting or turning off the phone...and i even went back to full stock...same thing
maybe it might have been some software issue that led to the overburning of the motor(doubt that though)
what is weird though is that the same scenario happened to us so im lost...
maybe i should start talking to samsung for my replacement
meanwhile...im very open to suggestions that might help my case
hope we find something soon...u guys, does it vibrate at all?when u turn on ur phone?turn off? unlock ?
takomar said:
hope we find something soon...u guys, does it vibrate at all?when u turn on ur phone?turn off? unlock ?
Click to expand...
Click to collapse
Yes, it vibrates at boot and also when using application with it's own vibrate settings, like "dialer one" for example.
Did you try using KickBack just to check the hardware?
if it's some hardware issue, maybe you can apply to your warranty supplier about that, just flash stock rom and relock your device before.
TaliKa said:
Yes, it vibrates at boot and also when using application with it's own vibrate settings, like "dialer one" for example.
Did you try using KickBack just to check the hardware?
if it's some hardware issue, maybe you can apply to your warranty supplier about that, just flash stock rom and relock your device before.
Click to expand...
Click to collapse
thats what im gonna do i guess...such a sad day...
i couldnt find KickBack, its not available in my accessibility menu nor in my market (i live in France)
i tried googling an apk but nothing for android 4.0
do you have a link for it?
takomar said:
thats what im gonna do i guess...such a sad day...
i couldnt find KickBack, its not available in my accessibility menu nor in my market (i live in France)
i tried googling an apk but nothing for android 4.0
do you have a link for it?
Click to expand...
Click to collapse
I couldn't find it in play store either, but i download it from here:
http://code.google.com/p/eyes-free/downloads/detail?name=kickback-v1.1.1.apk
works fine for me.
TaliKa said:
unfortunately I didn't get any solution yet. Realy depressing.
I promise to update about any progress, and hope you'll both do the same...
Just don't give up! it isn't hardware thing, so there must be solution somewhere.
Click to expand...
Click to collapse
Good to know. I went ahead and flashed the base image and it restored vibration, then I rooted and flashed AOKP again. It worked for about that day and then this morning when I woke up the vibration is gone again. I'm almost positive it's AOKP's software. I'll test another ROM (Android Revolution) for a day and see if it happens again.
Dacian said:
I'm almost positive it's AOKP's software. I'll test another ROM (Android Revolution) for a day and see if it happens again.
Click to expand...
Click to collapse
Which kernel do you use? and did you set the quite hours on?
If you succeed to restore the vibrate, i'd like to hear exact instructions how to do that, including links to download the boot image, if you plesae...
I just got my S II a few days ago and I flashed CM9. I've noticed the soft key back light is messed up and won't turn on after I get a notification, I read a post where someone suggested an app but that didn't work for me. Does anyone else have a suggestion? Is there a similar problem with other AOSP roms? Thanks
ponygon101 said:
I just got my S II a few days ago and I flashed CM9. I've noticed the soft key back light is messed up and won't turn on after I get a notification, I read a post where someone suggested an app but that didn't work for me. Does anyone else have a suggestion? Is there a similar problem with other AOSP roms? Thanks
Click to expand...
Click to collapse
I am running Cm9 stable and I haven't had any issues, make sure its enabled in settings/display and play around a bit with the settings. Otherwise I would recommend a reflash. That is all I can really think of.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Octane70 said:
I am running Cm9 stable and I haven't had any issues, make sure its enabled in settings/display and play around a bit with the settings. Otherwise I would recommend a reflash. That is all I can really think of.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Its actually pretty much a common issue. With both CM10 and CM9, i had only heard of it being perfect on AOKP ICS. I too had this, i ended up disabling BLN due to a wake lock drastically draining the battery. I miss the old static BLN cause that didnt use a wake lock. It just woke it once to allow them to come on then went back to deep sleep.
elesbb said:
Its actually pretty much a common issue. With both CM10 and CM9, i had only heard of it being perfect on AOKP ICS. I too had this, i ended up disabling BLN due to a wake lock drastically draining the battery. I miss the old static BLN cause that didnt use a wake lock. It just woke it once to allow them to come on then went back to deep sleep.
Click to expand...
Click to collapse
Well I installed AOKP ICS, and it works like a charm with the exception that it still doesn't really work with BLN but I didn't realty care much for that.
Thread Closed !!
New Google's Android 4.2.1 Features
-> Photo Sphere
-> Gesture Typing
-> Multi-User Support (Tablets Only)
-> Miracast Wireless Display Support
-> Daydream
-> Notification Power Controls
-> Google Now Improvements
For More Information on Which of the above features available in CyanogenMod, Come to My New Thread T989 Official CM10.1 4.2.1 Discussion (Coming Soon)
Enjoy !!! :good:
This is very useful! I am currently running AOKP JB and I will pay attention to this thread as it geets updated so I can see which ROM has less bugs, AOKP JB by TLS, or CM10.
theandroidrooter88 said:
This is very useful! I am currently running AOKP JB and I will pay attention to this thread as it geets updated so I can see which ROM has less bugs, AOKP JB by TLS, or CM10.
Click to expand...
Click to collapse
This is why i started this Thread, So we can discuss Bugs in the latest versions. :highfive:
I heard AOKP JB is stll having SODs and RRs. Do u find anything like these?
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
First we have to fix our flashing methods and recoveries used. I for one haven't experienced one single RR or SoD since I started flashing official nightlies. People are probably causing these issues themselves to begin with. Expecting a fix for an issue that has no identifiable cause.. I wonder if any other phones outside the t989 forums are experiencing RR and SoDs with Jelly Bean..
Sent from my SAMSUNG-SGH-T989 using xda premium
algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
running 10-10. I experienced one soft reboot after restoring apps and then running all of them (I don't blame my phone). no sod yet. i don't know if they fixed rr or sod completely but i believe they made an impact. I think people are making assumptions since the 4.1.2 update claimed "better performance and stability fixes" and the bbq log shows a lot of framework and system updates
algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
We are not guessing. I said there are no SODs or RRs because I installed each update and i am pushing hard my device to get a RR. Also as i observed that there are no SODs. CM10 09-Oct Nightly is more stable than previous Nightlies. I know there are still some issues like as i stated above. We can find solutions for common problems but not major problems.
garth719 said:
running 10-10. I experienced one soft reboot after restoring apps and then running all of them (I don't blame my phone). no sod yet. i don't know if they fixed rr or sod completely but i believe they made an impact. I think people are making assumptions since the 4.1.2 update claimed "better performance and stability fixes" and the bbq log shows a lot of framework and system updates
Click to expand...
Click to collapse
Great to hear that your running latest 10-Oct Nightly. A Simple advice to you & all other users, is to restore app without data if your are using any backup tools such as TitaniumBackup etc., Restore Apps with data cause Problems.
srikanth.t989 said:
We are not guessing. I said there are no SODs or RRs because I installed each update and i am pushing hard my device to get a RR. Also as i observed that there are no SODs. CM10 09-Oct Nightly is more stable than previous Nightlies. I know there are still some issues like as i stated above. We can find solutions for common problems but not major problems.
Click to expand...
Click to collapse
Sorry, I don't mean to crap on the thread but unless you can confidently say that SODs and RRs have been fixed (changelogs, yourself writing the code, etc.), going by your own experience shouldn't be the end-all-be-all to say whether something is fixed or not. Just like with call echo, some devices are worse than others.
I see that supposedly the issue with audio and docking has been addressed. However, the docking option is still grayed out for me when docked. Just looking for audio pass-through while docked...
Been running CM10 for the past few days and updating nightlies. My issues so far:
1. No sound with Alarms, just vibrating
2. I have been told by caller that I sounded weird using phone mic, but fine with headset
3. Had phone freeze once this morning on 10/9 with touch keys lit, but screen black, had to pull battery
I am now on 10/10 and plan on doing a clean install of it this afternoon, so I'm not sure how many of these issues with persist yet
SOD RR is not fixed for me, ran latest cm10 as well as aokp nightlies
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
eight_heads said:
Been running CM10 for the past few days and updating nightlies. My issues so far:
1. No sound with Alarms, just vibrating
2. I have been told by caller that I sounded weird using phone mic, but fine with headset
3. Had phone freeze once this morning on 10/9 with touch keys lit, but screen black, had to pull battery
I am now on 10/10 and plan on doing a clean install of it this afternoon, so I'm not sure how many of these issues with persist yet
Click to expand...
Click to collapse
1. There are issues with all of the volume settings. To fix your alarm volume open the clock settings, go to volumes and chnge the volume level. It should work. You can fix all volume settings with a simple toggle. 2. Make sure you have noise suppression enabled in call settings. 3. To avoid pulling the battery hold down the power for 10-15 seconds and it will reboot.
running 10-10 with TWRP and clean install (no tdj scripts). No rr/sod for 6 hrs so far. just a soft reboot after loading a ton of apps and running them all to push my phone to the max. No issues except the ones above and a tiny camera app issue thats already been reproduced (switching from camera mode--> video mode-->panorama-->camera will cause fc). I'm starting to think this is dd material. will let you know of any rr/sods.
I'm on recent CM10 Oct10 nightly and the BLN lights stay on, even with the Oct 7 nightly.
Update: fixed my own problems. This post helped: go to menu - systems - advanced settings - sensor and uncheck and check enable keys notifications and then send yourself a text or email. It actually should work out the box mine always has. Make sure you have notifications checked off in the apps like sms and gmail.
Also check display - notification light to make sure it enabled and you can add the apps you want to have the light enabled to work
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app
on CM10: 10-10. Google Now still no voice. ( prompt voice ). also, Google Now Initializing takes forever after press on mic. I am using GAPP 0726.
garth719 said:
1. There are issues with all of the volume settings. To fix your alarm volume open the clock settings, go to volumes and chnge the volume level. It should work. You can fix all volume settings with a simple toggle. 2. Make sure you have noise suppression enabled in call settings. 3. To avoid pulling the battery hold down the power for 10-15 seconds and it will reboot.
running 10-10 with TWRP and clean install (no tdj scripts). No rr/sod for 6 hrs so far. just a soft reboot after loading a ton of apps and running them all to push my phone to the max. No issues except the ones above and a tiny camera app issue thats already been reproduced (switching from camera mode--> video mode-->panorama-->camera will cause fc). I'm starting to think this is dd material. will let you know of any rr/sods.
EDIT:
Just ran the music player for 45min on a run. no skips, nothing.. ran a 90 mb mp3 file too which usually gives my ipod trouble.. good sign
Click to expand...
Click to collapse
So is that how we're saying we don't get random reboots anymore? We just call them something else??
algorhythm said:
So is that how we're saying we don't get random reboots anymore? We just call them something else??
Click to expand...
Click to collapse
well there was a difference in this reboot because my phone didnt actually fully shut off. the "cyanogenmod" boot animation came up and the phone was ready to go in about 20 seconds. there was no usual vibration indicating that the phone has shut off and no "samsung" boot image as a regular reboot would do. call it what you will
Quote:
[email protected]: on CM10: 10-10. Google Now still no voice. ( prompt voice ). also, Google Now Initializing takes forever after press on mic. I am using GAPP 0726.
Try updating it on the market
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Laazyboy said:
SOD RR is not fixed for me, ran latest cm10 as well as aokp nightlies
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Run only One ROM. Do a clean reflash. We are not experiencing any SODs or RRs. Use only one ROM because Flashing different ROMs one after the Other will Make your device weak. The data left by the AOKP causes some errors to CM10. Thats why i said that don't restore the apps with data.
I'm now on CM10.1 official, but tried stock, Cataclysm and a couple of other roms and kernel combinations.
I always end up with BSOD (black screen of death) at some point. The screen just turns off and doesn't comes on again, even if it receives a call (it does ring though).
Last BSOD was on today's CM10.1 already. I had to remove the battery.
It's not a usual thing to happen, but it ends up happening sometime.
Don't know if it's my new Mugen 2000 mAh battery, or some program I restore using TitaniumBackup. Never had a BSOD in 4.1 roms.
joooe said:
I'm now on CM10.1 official, but tried stock, Cataclysm and a couple of other roms and kernel combinations.
I always end up with BSOD (black screen of death) at some point. The screen just turns off and doesn't comes on again, even if it receives a call (it does ring though).
Last BSOD was on today's CM10.1 already. I had to remove the battery.
It's not a usual thing to happen, but it ends up happening sometime.
Don't know if it's my new Mugen 2000 mAh battery, or some program I restore using TitaniumBackup. Never had a BSOD in 4.1 roms.
Click to expand...
Click to collapse
It is a common issue with custom kernels right now. It is due to a bug in the source. We have to wait for Google to fix it. For the meantime use a stock kernel or anything close to stock like 007 kernel
Sent from my Galaxy Nexus using Tapatalk 2
joooe said:
I'm now on CM10.1 official, but tried stock, Cataclysm and a couple of other roms and kernel combinations.
I always end up with BSOD (black screen of death) at some point. The screen just turns off and doesn't comes on again, even if it receives a call (it does ring though).
Last BSOD was on today's CM10.1 already. I had to remove the battery.
It's not a usual thing to happen, but it ends up happening sometime.
Don't know if it's my new Mugen 2000 mAh battery, or some program I restore using TitaniumBackup. Never had a BSOD in 4.1 roms.
Click to expand...
Click to collapse
deeren said:
It is a common issue with custom kernels right now. It is due to a bug in the source. We have to wait for Google to fix it. For the meantime use a stock kernel or anything close to stock like 007 kernel
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
the same issue with stock kernels too(unrooted and rooted).
btw, its not called bsod, its called sod(sleep oif death)
It's probably not kernel related. Did you turn your animations off in developer settings? Try turning them to .5. Helped me and several others. Running mmuzzy with tiny kernel.
klobkelosh said:
It's probably not kernel related. Did you turn your animations off in developer settings? Try turning them to .5. Helped me and several others. Running mmuzzy with tiny kernel.
Click to expand...
Click to collapse
Will try that.
Thanks everyone.
I have the same BSOD/SOD issue... will try the 0.5 animation trick and report back. I would hate to go back to 4.1 roms.
I found new love for my SGN with the 4.2.1 smoothness.
Did it help?
I am experiencing SOD / BSOD on my Nexus 4 + latest CM10.1 nightly from time to time... (stock kernel).
In developer settings there are actually three settings regarding animations - are all to be set to .5?
Best regards,
ww
For me it did, yes.
No more BSOD.
I put them all to x.5
I've been diagnosing this for some time and I feel fairly confident that it is only the animation duration setting that triggers the sod. I have the other two settings set to 0 and duration set to 1 and no sod. But, it will not turn off that pesky crt animation.
who in here looked at logcat/dmesg when that happens?
do you have daydream ON? do you use an adblocker?
i've had one on 4.2.1, WITH AN ADBLOCKER installed. no adblocker, no bsod. full stock (rooted, unrooted, tried them both, doesn't matter), default settings (only enabled usb debugging)
just had another SOD / BSOD: I connected the charger and realized after 15 minutes, that the clock was unchanged (still 15 Min prior) - I tried to open an app and got a timeout. After I switch the screen off and on again I just saw a black screen (a little bit lighter than actually off) - but no homescreen anymore... damned.
So yeah all the 4.2 Roms are making me very angry because I'll turn my screen off and it doesn't want to turn back on. Is anyone else having this issue? Does anyone know how to fix it?
dakota.breeden said:
So yeah all the 4.2 Roms are making me very angry because I'll turn my screen off and it doesn't want to turn back on. Is anyone else having this issue? Does anyone know how to fix it?
Click to expand...
Click to collapse
its called sod, sleep of death. its a common problem with 4.2.1 kernel source. just about everyone has experienced them, some a lot more than others, root and not rooted, custom rom/kernel and stock. google needs to fix it in its source. there are some anecdotal fixes, some claim work, others say dont work.
I'm running a 4.2 ROM (Beta at that) and am amazed at how much better my device is working. Everything is smoother and I haven't had a single issue. I honestly don't see how everyone is having so many problems with it.
063_XOBX said:
I'm running a 4.2 ROM (Beta at that) and am amazed at how much better my device is working. Everything is smoother and I haven't had a single issue. I honestly don't see how everyone is having so many problems with it.
Click to expand...
Click to collapse
im loving 4.2.1, cant say that i have any real issues with it. but, i do get sod occasionally, about once every ten days or so. if you around the forums, just about everyone has experienced them. some get them several times an hour, some several times a day, some several times a week, some just have had sod once or twice total. every device is different, they will have differing experiences.
dakota.breeden said:
So yeah all the 4.2 Roms are making me very angry because I'll turn my screen off and it doesn't want to turn back on. Is anyone else having this issue? Does anyone know how to fix it?
Click to expand...
Click to collapse
just go back to 4.1.2 if you are having issues.. 4.2.1 is a hit or miss IMO, some ppl get issues while for others it works great
Just a thought, how many of you had bt on when sod occurs?
Sent from my i9250
bk201doesntexist said:
Just a thought, how many of you had bt on when sod occurs?
Sent from my i9250
Click to expand...
Click to collapse
Interesting idea. I never use it and have never had any issues.
i never use bluetooth, but have had sod.
Same here.
063_XOBX said:
Interesting idea. I never use it and have never had any issues.
Click to expand...
Click to collapse
I've had issues with BT on 4.2.1 (OTA), turned it off after a) sending first file OK b) second file fail, and it stuck on " turning off".
Read below.
simms22 said:
i never use bluetooth, but have had sod.
Click to expand...
Click to collapse
dakota.breeden said:
Same here.
Click to expand...
Click to collapse
I've experienced a "black screen" on 4.2.1 (OTA), due to what i think was a crash from XDA app, probably from using it with an ad blocker, at least from what i could see. I could adb shell to the device, remount system, no problem. I've removed the ad blocker from the system, while still on 4.2.1 (OTA), and have not experienced the "black screen of death" again.
I have not experienced a "sleep of death" yet on this device. Note: definition of sod from my galaxy s days: device is in a state (after going into deep sleep) in which the only way to get it back is pulling the battery out. System is unresponsive.
I've flashed JOP40D through stock images, and haven't seen black screen/sod scenarios, recreating the same system, more or less.
As i rarely use BT, i haven't tested it again, but we shall see.
Op, what apps do you have installed? Do you use SR/AVS? If not, please raise voltages by 50mv at each step, or at least the lowest and highest step, for mpu, core and iva.
While the device is in this state, no communication is possible? Can you logcat? dmesg? Can you receive calls?
Sent from my i9250
I have not had that issue or any SOD and I am running CM10.1 with LeanKernel, my wife runs the same setup and she also has not had any issues.
I've seen SoD's on Jellybro CM10.1 with ZenSERIES kernel v14.1, but only when using the ZenX governor. If I change to Pegasusq, the SoD's stop. I guess ADA is still working out some of the kinks in ZenX. Ooo, and it looks like v15 was released a few days ago. Something new to flash.