Develop Bugs

Black screen aka black death

Seems like a lot of people are facing problem waking up the phone resulting in getting black screen and nothing else.
I faced the same problem too that is why I decided to create a new thread specifically on this.
Let's share what caused our phone to go into coma based on our observations so that in time, the root of the problem can be traced.
Based on my observation, when my phone is left idle for some time, say 1-2hrs, it tends to become sluggish and setcpu will stuck at max or min value (Yes! sluggish even when stuck at max value!). Given long enough idle time, it will fail to wake up (e.g. every morning when i wake up after 7-8hrs of idle time).
I was using OpenDesire v4.0.10 and just changed to v4.0.15 to see if it still exist. I have setcpu set on 1075max 245min (ondemand) and 245max 245min (ondemand) when screen off. Also, using task manager.
Please share your observations and phone settings (ROM, versions, setcpu, task manager and others)

have you tried removing setcpu?

cgrec92 said:
have you tried removing setcpu?
Click to expand...
Click to collapse
Nope, but in OpenDesire thread, people without setcpu experienced the same thing. Do you have such problem?

I noticed using setcpu does make the phone sluggish. when uninstalled problem was solved.
Installed undervolt & got better batt life.
Sent from my HTC Desire using XDA App

Perhaps, a more tailored topic title will help all readers understand what you're talking about.
However, HAVS kernels is the only common factor and SetCPU is not the cause.
And, my two cents, I don't think this issue deserves a dedicated thread since is specific to a single kernel flavor.

shai.bosse said:
I noticed using setcpu does make the phone sluggish. when uninstalled problem was solved.
Installed undervolt & got better batt life.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
what is this undervolt you talking about? mind elaborating a little?

@ngel said:
Perhaps, a more tailored topic title will help all readers understand what you're talking about.
However, HAVS kernels is the only common factor and SetCPU is not the cause.
And, my two cents, I don't think this issue deserves a dedicated thread since is specific to a single kernel flavor.
Click to expand...
Click to collapse
I created a specific thread on this topic because there are many people out there experiencing this bug and there is no dedicate thread to discuss it. I assume you are not facing this problem because otherwise you would understand the pain and frustration of encountering this problem repeatedly

webber2109 said:
what is this undervolt you talking about? mind elaborating a little?
Click to expand...
Click to collapse
Undervolt is a kernel mod that you install and it lowers the cpu drain by setting it to use lower volt values on each cpu freq. This cause it to stay cooler too.
Look for it in this forum. [Kernel] undervolt
Sent from my HTC Desire using XDA App

I am suffering from this once per day on Defrost and OD so I suspect its kernal related. I am running the default HAVS kernel at the stock 998 frequency. I uninstalled SetCPU yesterday and had a lock this morning ( Defrost 4.1 ). The notification LED was flashing orange. So SetCPU is not causeing the problem. I have swapped over to SVS so I will report back on how that goes.

webber2109 said:
Nope, but in OpenDesire thread, people without setcpu experienced the same thing. Do you have such problem?
Click to expand...
Click to collapse
I use OpenDesire 4.0.10, then 4.0.15, then 4.0.16, each release for at least 3 days, and not for once have I encountered such "black death"....no setCPU of course.
Care to elaborate what apps you have there ?

webber2109 said:
I created a specific thread on this topic because there are many people out there experiencing this bug and there is no dedicate thread to discuss it. I assume you are not facing this problem because otherwise you would understand the pain and frustration of encountering this problem repeatedly
Click to expand...
Click to collapse
That issue is relative to OpenDesire and DeFroST ROMs only, and when they use a particular kernel version (HAVS) on selected CPUs, so I continue to think that it'll be eventually sorted out by the respective developers and/or Kali- and the kernel team; those guys do monitor the ROMs threads so they're already aware of the issue.
And yes, I suffered the issue twice, as I wrote more times in the DeFroST thread. "Pain" (panic?) and "frustration" sound a bit strange to me, when dealing with overclocked, custom, highly tweaked cooked ROMs. If a reboot scares you, head for a stock HTC ROM and you'll be fine.

I was worried I was the only one who had this. Thread title isn't that helpful for people seeking advice on it though. Get this after every reboot for about a minute until everything is back to normal.
Had the sluggish issue when using YouTube after about 20/30 mins, other than that I've had no lags.
Using 4.0.16
Sent from my HTC Desire

Double post

I got this on a svs kernal, so its not just restricted to havs. I had 1300 svs installed. With setcpu. Done the same with 1267 svs.

I've also had this issue on SVS kernels, was also having a series of hard resets last night - have rolled back to an earlier version of my favourite ROM flavour for now.

Never experienced anything like that...Although there are times that my Desire's performance would remind me of the bad old Diamond days,where patience was a virtue(well,not a virtue,but a money saving method!throwing your phone to the wall with your full strength after it frustrates you with being slow is known to be a costly process! ).Seems to be some apps running in the background...Maybe if your phone recovers after it without a reboot you can check if any apps use a larger than normal amount of ram.Other than that...Well,god is almighty and people experiencing epiphanies are known to work wonders through the ages!
And something completely off-topic(sorry about that).When using an undervolted rom/kernel you are not able to overclock to values as high as when using a normal-volted(is the word right?I dunno...) rom/kernel,right?I mean,what would happen if someone tried to overclock to 1382MHz(I know,I like the limits) using an undervolted kernel?And finally,how does this all apply to the hardware?Does UV affect the CPU's health like overclocking or something like that?
Thanks a lot!

I've had it on OpenDesire 4.0.10 and 4.0.15 a few times. Stopped happening when I stopped using profiles and defaulted back to to 998/ondemand.
Will try running it on 998/interactive for a while and see what happens.

No lockups after SetCPU to ondemand. OD 4.0.15.
Sent from my HTC Desire using XDA App

Separate thread IS useful, otherwise replies get lost in ROM threads where the focus is not specifically on this problem.
I too had this issue three times. DeFroST on all occasions, versions 3.x iirc. Never tried the HAVS kernels, just plain default what is shipped with the ROM (SVS @ 12xx Mhz?). Also SetCPU'd it, have not yet bothered to try and turn that off yet. SetCPU keeps it at 995 Mhz max, interactive governor, while switching to powersave while asleep.
Issue happened twice while browsing (possibly with Flash ads on the page by accident) and the power state switching (i.e. turn the device off quickly while running for train, afterwards reading for 2 minutes again, etc). Third time it happened while tethering my internet connection to my laptop.
Hth

I had this problem few times a day when I upgraded OD to .10 and the new ADW on the same day.
Then I restore back the old OD with old ADW, then no problem.

[Q] Myn's Warm ROM Question

I guess I'm under 10 posts so I could not post in his thread.
But I installed the rom and everything is awesome btw,
Now under his alternative kernels it has the Netarchy's agressive v7 kernel, I installed it, and if I put setcpu at 1.267 ghz my phone shuts off and reboots?
IS there a reason why?

Also it just went to its first reboot and it went into a bootloop?

K now it's not bootlooping but it starts up and after about 15 seconds it reboots.
EDIT: I flashed the stock kernel and its fine now, but I want to OC it just a little why is it doing that?

you cant overclock it above 1.1 as far as i know thats all the cpu is really capable of
r916 said:
K now it's not bootlooping but it starts up and after about 15 seconds it reboots.
EDIT: I flashed the stock kernel and its fine now, but I want to OC it just a little why is it doing that?
Click to expand...
Click to collapse

4g evo said:
you cant overclock it above 1.1 as far as i know thats all the cpu is really capable of
Click to expand...
Click to collapse
On this rom?
When I had the Evio 2 rom and stock kernel it would go to 1.228.
And on this one, 1.267 makes it reboot.

any kernels or Roms that i have had it would always loop above 1.1 your lucky that u got it to go that high how was it at that speed lol.
r916 said:
On this rom?
When I had the Evio 2 rom and stock kernel it would go to 1.228.
And on this one, 1.267 makes it reboot.
Click to expand...
Click to collapse

i was told that if you OC and start having bootloop scale back the OC until it gets stable again.

I got netarchy's 4.3.2 kernel and it's clocked to 1.228, wont go any higher since the incident.

From my understanding, no two phones are exactly alike and one phone will allow you to OC more than another. The most I ever OC to is 1.19 but I usually keep it at 1.15 and it is very stable. I've gone up to 1.267 and it still worked, but I only left it at that number for a few seconds and I never tried to go higher.

It's a crap shoot with overclocking. With different ROMs, Kernels and hardware in play, the results can be very different from one version to the next. This is the nature of overclocking. As mentioned in a previous post, you need to keep notching it back until it gets stable again.
Sent from my PC36100 using XDA App

cloak.n.dagger said:
It's a crap shoot with overclocking. With different ROMs, Kernels and hardware in play, the results can be very different from one version to the next. This is the nature of overclocking. As mentioned in a previous post, you need to keep notching it back until it gets stable again.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well it was hard to notch it back since I had set at boot checked and it was at 1.267, so I had to re flash the stock #15 htc kernel, and set it at 998 and then flash the new kernel and now it's at 1.228 and stable, and not to mention my battery is amazing.

I keep mine at 1.19 as well, I had it higher at one time, but there's not that much
improvement in performance for me to risk my phone boot looping while i'm asleep at
night.
BTW, Myn's ROM is really good but i've always use KK #9 BFS for it overclocker at 1.19
with no issues, no reboots, only secks.

lock ups

In the past week have just rooted my inc2, flashed OMGB rom and Tiamat 1.1.0 kernel. I also loaded SetCPU from the market. I can't go over 1.036ghz without the phone locking up and having to do a battery pull. When the phone is back on I only have a few seconds to open SetCPU and lower the OC rate or the phone will lock again. I wiped cache/davlik cache before flashing kernel. What am I doing wrong? I have seen in the Tiamat thread in the development forum that people are going as high as 1.9ghz with out a problem. I would only like to get 1.2ghz to 1.3ghz because I read that this is a safe range. I do have have the governor set at Smartass. Thank you for your input.

scott7044 said:
In the past week have just rooted my inc2, flashed OMGB rom and Tiamat 1.1.0 kernel. I also loaded SetCPU from the market. I can't go over 1.036ghz without the phone locking up and having to do a battery pull. When the phone is back on I only have a few seconds to open SetCPU and lower the OC rate or the phone will lock again. I wiped cache/davlik cache before flashing kernel. What am I doing wrong? I have seen in the Tiamat thread in the development forum that people are going as high as 1.9ghz with out a problem. I would only like to get 1.2ghz to 1.3ghz because I read that this is a safe range. I do have have the governor set at Smartass. Thank you for your input.
Click to expand...
Click to collapse
Go back to the kernel thread look for the voltage table. The voltage levels are too low at the overclock levels, that what's causing your freeze ups. Use incredicontrol app from the market to adjust the voltage levels. You want to mirror the settings to match those of the previous version of the kernel
Sent from my Incredible 2 using Tapatalk

Thanks tnez, I found chads post about incredicontrol and sounded like it only worked on ver 1.0.4, will it work on ver 1.1.0 also.
How bad is this freezing for the phone? If I ever get really stuck will booting into recovery and reflashing omgb fix it or using the nandroid backup I created before flashing the kernel? Still new to all the rooting and custom roms and kernels, lots of fun but still have the fear of bricking the phone.

I'm fairly new myself but have been using SetCPU for a while. Make sure the "Set on Boot" option is unchecked until you find a setting that will work for your phone. As far as the nandroid, restore is your friend!! lol I've made many mistakes in the past that have totally locked up my phone and the restore option from recovery has saved me every time. There is always a chance that you can damage your phone but as time has gone by the devs have really made that possibility minimal

scott7044 said:
Thanks tnez, I found chads post about incredicontrol and sounded like it only worked on ver 1.0.4, will it work on ver 1.1.0 also.
How bad is this freezing for the phone? If I ever get really stuck will booting into recovery and reflashing omgb fix it or using the nandroid backup I created before flashing the kernel? Still new to all the rooting and custom roms and kernels, lots of fun but still have the fear of bricking the phone.
Click to expand...
Click to collapse
The app works on any kernel that supports adjustable voltages.
Both methods will work to undo things. Either restore or re flash the rom. But like stated above don't select the set on boot option until you find settings that work good on your phone.
Sent from my Incredible 2 using Tapatalk

Thanks again tnez, I installed incredicontrol and made the changes to the voltages so far so good. I have gone to 1.19ghz with no problems after the voltage changes. Is there app that can be used to test for stability or is just using the phone the way to test for stability.

scott7044 said:
Thanks again tnez, I installed incredicontrol and made the changes to the voltages so far so good. I have gone to 1.19ghz with no problems after the voltage changes. Is there app that can be used to test for stability or is just using the phone the way to test for stability.
Click to expand...
Click to collapse
You can do it by use....open up different apps very quick and switch between them...basically trying to over load the phone by making it multi task at a high level. set cpu also has a built in stress test under the info tab, run that for a few mins. I usually do the stress test for 3-5 mins followed by a quadrant test.
Sent from my Incredible 2 using Tapatalk

In regards to Tiamat, there have been a ton of people say that downgrading back to 1.0.4 Tiamat fixed the issue of the phone locking up when overclocked. If all else fails from what you have been recommended, try that!

TheMavic said:
In regards to Tiamat, there have been a ton of people say that downgrading back to 1.0.4 Tiamat fixed the issue of the phone locking up when overclocked. If all else fails from what you have been recommended, try that!
Click to expand...
Click to collapse
voltages just need to be changed and made to match 1.0.4 for the kernel to run like a champ
Sent from my Incredible 2 using Tapatalk

[Q] Does anyone else's A100 slow down

Does any one else's a100 become super laggy after a few minutes of being on.. I am running the latest flex reaper I even overclock it all the way but I get this huge lag after the first few minutes of being on.. anyone else experience this or have a fix for this?

Crimson Ghoul said:
Does any one else's a100 become super laggy after a few minutes of being on.. I am running the latest flex reaper I even overclock it all the way but I get this huge lag after the first few minutes of being on.. anyone else experience this or have a fix for this?
Click to expand...
Click to collapse
I do not experience this issue. When you flashed the rom, did you do a clean install? Have you formatting the device?

Yup.. I format everything.. I use the touch recovery and just use every option that it provides and wipe everything.. It even does it when there is nothing installed. I usually delete almost all the useless system apps that I don't use like the google music app and all of the ones civato provides... I even change the animation settings to .5 in the developer section.. should I turn them off all together?

Crimson Ghoul said:
Yup.. I format everything.. I use the touch recovery and just use every option that it provides and wipe everything.. It even does it when there is nothing installed. I usually delete almost all the useless system apps that I don't use like the google music app and all of the ones civato provides... I even change the animation settings to .5 in the developer section.. should I turn them off all together?
Click to expand...
Click to collapse
The animations should not have anything to do with it. Does this only occur on that rom? Have you tried other roms and experienced that issue?

not many other roms out there.. I have used stock and his.. had the same issue on both.. Also happens on my brother's a500.. it usually happens when unlocking and going into any app.. it sits there for a few seconds and then opens whatever it is i opened

Crimson Ghoul said:
not many other roms out there.. I have used stock and his.. had the same issue on both.. Also happens on my brother's a500.. it usually happens when unlocking and going into any app.. it sits there for a few seconds and then opens whatever it is i opened
Click to expand...
Click to collapse
This is starting to sound like a hardware issue. Before that is concluded, you could:
- Make sure the governor is not set to "conservative"
- Try a clean install of CM9
If the problem still arises, its most likely a hardware issue.

I'm using the OC kernel and have it to 1500.. I also always leave it on performance.. I figure it would kill my battery life but I don't use it much.. and i tried cm9 also.. too many issues as of right now

Crimson Ghoul said:
I'm using the OC kernel and have it to 1500.. I also always leave it on performance.. I figure it would kill my battery life but I don't use it much.. and i tried cm9 also.. too many issues as of right now
Click to expand...
Click to collapse
It doesn't seem it can be anything else but a hardware issue in that case.
NB. Overclocking to a high frequency can cause instability and bring about that issue (but since you experienced it on the stock rom, its quite likely not to be that).

the overclocking helps to speed it up a tad bit.. for the most part it just lags.. i did a clean install just now

Thought I would jump in. Stock ics would slow down and lag on me, jittery transitions poor performance in games or movies, but it took an hour not a few minutes. However testing the T20 kernel before the release kernel had that exact issue, bogging and lagging within minutes.
His release kernel doesnt do it, and flex extreme as well as my cm9 builds don't, even with T20 kernel. Consider flashing that kernel to see what happens.
Side note...what issues did you have with cm9? And what release? My build 1 has been running for 3 days no reboots stable as can be undervolted and OC when needed. Something to maybe think to try to see if it persists. T20 kernel works fine with it too.
Tapatalked from my Galaxy S II.

Crimson Ghoul said:
Does any one else's a100 become super laggy after a few minutes of being on.. I am running the latest flex reaper I even overclock it all the way but I get this huge lag after the first few minutes of being on.. anyone else experience this or have a fix for this?
Click to expand...
Click to collapse
Yup, EVERYTIME I turned on my screen then unlocked it to laggggggg for a lil while. I'm now using CM9 n that issues gone. Try CM9
forum.xda-developers.com/showthread.php?t=1705554
A100 Running CM9 Nightly ROM n ezT20 OC Kernel :-D

To prevent the lagg after unlock, I set the governor to ondemand and the minimum frequency to 312.

eww245 said:
To prevent the lagg after unlock, I set the governor to ondemand and the minimum frequency to 312.
Click to expand...
Click to collapse
That reminds me...setting a screen off profile with the same min/Max speed can cause issues with that, give Max a notch or two higher. And don't have it change the governor leave it the same. So like interactive screen on Myst nit be conservative screen off, doesn't work that way.
Tapatalked from my Galaxy S II.

I had the same issue on stock. I noticed there are 2 weather applications installed (version 1 and version 2) immediately after I disabled the old weather application (version 1) this stopped happening. I used the ICS GUI to do the disable.
This might not be the case in custom rom, but is true for stock. Post reply and let me know if this fixed it for you also.

Crimson Ghoul said:
Does any one else's a100 become super laggy after a few minutes of being on.. I am running the latest flex reaper I even overclock it all the way but I get this huge lag after the first few minutes of being on.. anyone else experience this or have a fix for this?
Click to expand...
Click to collapse
Do you have a micro SD card plugged in? Try reformatting the card with a computer. Worked for me.
Sent from my A100 using XDA

I felt the need to add my two cents in this....this has been happening to me for the longest with the flex reaper rom ONLY. I've used stock and ZN's rom and those did not lag after unlock...only flex reaper. I'm currently using flex reaper and still experience it from time to time but doesn't destroy my day at all...

Give the CM9 nightly ROM's a go. No Bluetooth n no HDMI audio, but everything else is fine n damn smooth. Those issues will be fixed though
A100 Running CM9 Nightly ROM n ezT20 OC Kernel :-D

eww245 said:
To prevent the lagg after unlock, I set the governor to ondemand and the minimum frequency to 312.
Click to expand...
Click to collapse
I installed Flex 100 Reaper with stock and it it seemed to run smooth enough. Then I installed the OC kernal, and started to get lag. I was looking around to find the OC settings, but can't see it anywhere in settings..
Can anyone direct me to where can I adjust the governor/max/min CPU settings?
Sorry for the noob question.

htc_softbank said:
I installed Flex 100 Reaper with the OC kernal, and started to get lag. I was looking around to find the OC settings, but can't see it anywhere in settings..
Can anyone direct me to where can I adjust the governor/max/min CPU settings?
Sorry for the noob question.
Click to expand...
Click to collapse
Setcpu from the play store.
The overclock settings are not integrated like CM.

franco kernel sluggish or phone damaged?

Hi all,
Today I installed CWM and flashed franco's kernel for JB (the newest one). At first it seemed pretty fast so I was happy. I decided to install setcpu and set it to max 1,8 ghz with set on boot enabled (I know it was stupid, but I did not realize it at the time). After rebooting the phone froze and a purple layer appeared on top of my screen. Seconds later my phone rebooted. I set setcpu on 1,2 ghz max and let it stresstest for a couple of minutes. No errors were found. But now my phone lags sometimes, like if project butter just had disappeared and the normal android sluggishness has reappeared. Is this a kernelissue or did I damage my cpu with this stupid overclock? Btw, apart from the sluggishness in the animations I can run everything just fine.

I'm on Franco and have no problems. Why don't you try another kernel and let us know how it goes?

tobitronics said:
Hi all,
Today I installed CWM and flashed franco's kernel for JB (the newest one). At first it seemed pretty fast so I was happy. I decided to install setcpu and set it to max 1,8 ghz with set on boot enabled (I know it was stupid, but I did not realize it at the time). After rebooting the phone froze and a purple layer appeared on top of my screen. Seconds later my phone rebooted. I set setcpu on 1,2 ghz max and let it stresstest for a couple of minutes. No errors were found. But now my phone lags sometimes, like if project butter just had disappeared and the normal android sluggishness has reappeared. Is this a kernelissue or did I damage my cpu with this stupid overclock? Btw, apart from the sluggishness in the animations I can run everything just fine.
Click to expand...
Click to collapse
I understand people want to ask questions first, did you try to wipe and reflash?
At most I can probably assure you, you didn't damage your CPU.. there would probably be more dire issues if it was.
Did you flash a new kernel yet?
Sent from my Galaxy Nexus using Tapatalk 2

Not yet. Should I reflash franco or try another? Can I flash a new kernel over another kernel without wiping my whole device?

tobitronics said:
Not yet. Should I reflash franco or try another? Can I flash a new kernel over another kernel without wiping my whole device?
Click to expand...
Click to collapse
Wipe dalvik cache and install trinity.
Sent from my Galaxy Nexus using Tapatalk 2

tobitronics said:
Not yet. Should I reflash franco or try another? Can I flash a new kernel over another kernel without wiping my whole device?
Click to expand...
Click to collapse
Yes, I've flashed 3-4 kernels on one ROM. You can dirty flash your ROM too or completely wipe and flash.
Either way its fine. I do suggest wiping and flashing though..
Sent from my Galaxy Nexus using Tapatalk 2

And should I uninstall SetCPU in order to get stock CPU speeds? And what issues would I have if I would have fried my SoC?

tobitronics said:
And should I uninstall SetCPU in order to get stock CPU speeds? And what issues would I have if I would have fried my SoC?
Click to expand...
Click to collapse
Setcpu is fine. In order to get stock, either use a new kernel or dirty flash.
Assuming.. if it was I'd guess the phone probably wouldn't be running?
Sent from my Galaxy Nexus using Tapatalk 2

You need to learn about what you're doing before you do it!

I flashed the trinity 1420-537 JB stable kernel, and everything works as smooth as it has to be. The strange thing is that it was a bit sluggish until I changed my wallpaper from a live to a normal one. Now I switched back and everything is still smooth :? . Anyway, does this kernel overclock the cpu itself or are the speeds in the name just the available range?

z06mike said:
You need to learn about what you're doing before you do it!
Click to expand...
Click to collapse
:good: :good:
tobitronics said:
I flashed the trinity 1420-537 JB stable kernel, and everything works as smooth as it has to be. The strange thing is that it was a bit sluggish until I changed my wallpaper from a live to a normal one. Now I switched back and everything is still smooth :? . Anyway, does this kernel overclock the cpu itself or are the speeds in the name just the available range?
Click to expand...
Click to collapse
if I have such issues I will never flash an oc kernel to look if everthing is working. Install stock rom kernel back and try. If everything is fine......you can try an oc one.
On Trinity; first number is MAX CPU clock range you can chose and second number is fix GPU clock.....or just reading FAQ, Changelog etc. will answer your questions really quick
regards,
Lars

from what I've heard, some gnexs are really picky with roms and kernels. I guess your phone is one of them. I personally had problems with Trinity Kernel, since when I reboot, it sometimes bootloops for 5minutes and such. I personally had no problems with Franco though. In fact, I use Franco as my daily driver
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Franco's app let's you easily tweak the settings (overclock, change governors, etc.) which may help the sluggishness. I almost exclusively run Franco and his M5 is amazing!
Sent from my Galaxy Nexus using Tapatalk 2

A reflash might be the best option ... either the ROM or Kernel or Both lol thats my inner crack flasher talkin'

Never had problems with franco. It's trinity's kernel that made problems for me.

I run Franco's kernel myself. Just have to be careful with flashing the nightlies, it can be hit or miss. They are experimental.
Sent from my Galaxy Nexus using Tapatalk 2

CHANGE YOUR GOVERNOR HURR DURR.
Sent from my Galaxy Nexus using xda app-developers app

Today I reflashed franco and I must say that trinity is way better, at least for me. Franco keeps being sluggish, trinity works smooth.

trinity is better than Franco's in every way possible...
especially battery life