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.

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

Installed kernel, now buggy sound on video.

Hi guys,
I'm a bit of a noob so please bear with me. I recently rooted my phone (SGH-I747M Telus), I have CWM recovery installed. I was interested in overclocking so I installed this kernel on my stock rooted rom (I installed the "sammy" one). I also cleared the delvik cache, cache, and fixed permissions before rebooting. Now I'm having a weird problem with video playback. I get these bleep like sounds, like you might hear on a spaceship, lol. The normal audio plays in addition to these sounds. Yet, regular audio plays fine (mp3s), same with youtube. So, my question is, why? Is there any way of fixing this? I'd rather not play around the stock ROM. I made a backup before doing anything and recently tried to restore the boot, but I got an invalid md5 check.
-JC

Okay, I was able to fix my problem by flashing the stock at&t kernel... but I would still like to be able to overclock... is there another kernel that I can try or a way to fix the problem with the kernel I already tried? Thanks.

If you still want to try previous kernel your problem might be because of heavy undervolting , kernel creator posted this voltage chart.
You can experiment by increasing voltage and see if that helps.
Or you can just try this faux kernel , its pretty good also, we don't have many kernel choices for Samsung based roms at this early development cycle.

ghost77 said:
If you still want to try previous kernel your problem might be because of heavy undervolting , kernel creator posted this voltage chart.
You can experiment by increasing voltage and see if that helps.
Or you can just try this faux kernel , its pretty good also, we don't have many kernel choices for Samsung based roms at this early development cycle.
Click to expand...
Click to collapse
Thanks for the reply... but I was able to fix the problem. It was something wrong with the settings of SetCPU which I installed earlier. I changed it from on demand to performance and now all is well. Now I have a question about battery life. Will overclocking drain battery a lot faster? I imagine it would only make a difference if I was doing CPU intensive things.

JustChillin1414 said:
Thanks for the reply... but I was able to fix the problem. It was something wrong with the settings of SetCPU which I installed earlier. I changed it from on demand to performance and now all is well. Now I have a question about battery life. Will overclocking drain battery a lot faster? I imagine it would only make a difference if I was doing CPU intensive things.
Click to expand...
Click to collapse
Well.. performance setting makes it so that your CPU runs 100% all the time. I don't think that will be battery friendly . Overclock generally uses more power and battery longevity will depend on your usage.
You can try messing with setcpu settings. Try Conservative, then limit minimum speed to 384 and max to your preference. Try your movie again.
Current kernels and setcpu are a bit quirky.

I had the same issues on ktoonsez Sammy. Ended up back at stock AT&T. I've heard it's an issue with many of the kernels but a fix is on the way. Couldn't find a way to get rid of it, but that's not to say it can't be done. Don't have much time to tinker right now.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Its a known issue on ktoonsez kernel. Flash faux's kernel, it has the same features (as well as GPU OC) and doesn't have the audio issue.

[Q] super heating.... I'm confused

This is the topic at hand .... not that after a period of use the lg nitro hd p930 is heated in an incredible
way and this caused the system is damaged and the wifi did not work because of this I had to unbrick the phone to
install them other rom that doing ics hard reset on stock 4.0.4 att ... but I just realized I still doing the same in other
rom and you do not and I hope that someone knows about this and can give me an answer.
Note: this step after aver played Turbo Racing League now all I installed rom without playing is heated and the wifi is
going to turn off and remove and replace the battery
excuse my bad English use google translator

Try to change frequency. Standart is about 1500mhz and you should decrease it to 1200 or less. Use set cpu or cpu master (free in google play).
Sent from my LG-P930 using xda premium

No Frills CPU is also free and available from the Play store. I use SmartassV2 and Deadline in the cpu settings.

6783 said:
Try to change frequency. Standart is about 1500mhz and you should decrease it to 1200 or less. Use set cpu or cpu master (free in google play).
Sent from my LG-P930 using xda premium
Click to expand...
Click to collapse
audit13 said:
No Frills CPU is also free and available from the Play store. I use SmartassV2 and Deadline in the cpu settings.
Click to expand...
Click to collapse
thanks for the info ... I cofigurado yesterday with the minimum frequency to 460Mhz and 1000Mhz the Maxima using the SetCPU program ... My concern is that if this resolves the wifi is not active due to heating after that I have to wait for the restart and pull the battery to get it working again ..
If you have further information about the settings they are appreciate ... I'm using the Rom Avatar

You could try installing an ICS rom to see if wifi works. If it does, then you know it's the current rom that is causing the problem.
I have tried a few roms and never had the heating or wifi issue.

not that the wifi does not work is that when heated or I'm using and gives the restart issue is not working anymore for some time

Not sure but maybe there is something wrong with your phone or the battery. Does the battery heat up when connected to a charger and sitting ilde? Does it heat up just sitting idle and not connected to a charger?

This is happening with regularities in these devices and as I see on forum ... is when I'm using a heavy application at first but after was more consistent than using normal applications gives Random restart

I think I read one or two posts from people that had hot batteries but that was due to the person using a custom rom.
I started using my P930 after not using it for many months because I was using a different phone. I loaded CM10 because it seems to give me the best battery life so far. I'll know more when I start using the phone more regularly.

audit13 said:
I think I read one or two posts from people that had hot batteries but that was due to the person using a custom rom.
I started using my P930 after not using it for many months because I was using a different phone. I loaded CM10 because it seems to give me the best battery life so far. I'll know more when I start using the phone more regularly.
Click to expand...
Click to collapse
In my reason I have determined that the problem seems to be hardware that is not heating the battery but processors am using Avatar Rom Android version 4.2.2 based on CM10 ...using wind kerner 2.5...And as I have read it is the cpu frequencies...download an app to adjust the frequencies at the same level...commented after what results

Question. Why does my s4 keep overlooking itself?

I have a S4 mini running custom carbon kk unofficial 4.4.3 as it comes with the settings to set CPU's and governors but the phone keeps changing the min to around 1400 but the max stays at 1700.i don't notice until my battery is draining really fast or gets hot. anyone kno a fix to this?

matizkool said:
I have a S4 mini running custom carbon kk unofficial 4.4.3 as it comes with the settings to set CPU's and governors but the phone keeps changing the min to around 1400 but the max stays at 1700.i don't notice until my battery is draining really fast or gets hot. anyone kno a fix to this?
Click to expand...
Click to collapse
Which governor is it using to set a min of 1400? Ever likely it gets hot and eats power! I use f4k's kernel, and the 'Performance Control' app to look at and alter stuff - you don't say what you use or have tried.
There is a Carbon 4.4.4 available with f4ktion 1.5 kernel - might be an idea to flash that and the problem might go away!

xbin said:
Which governor is it using to set a min of 1400? Ever likely it gets hot and eats power! I use f4k's kernel, and the 'Performance Control' app to look at and alter stuff - you don't say what you use or have tried.
There is a Carbon 4.4.4 available with f4ktion 1.5 kernel - might be an idea to flash that and the problem might go away!
Click to expand...
Click to collapse
It's on every governor this happens but I use Wheatley. I would manually set it to around the 300s but in a couple of hours it would auto set at 1400 on its on. This causes my battery to drain my kernel version is 3.4.91 f4ktion 1.4.5 eur lte

matizkool said:
It's on every governor this happens but I use Wheatley. I would manually set it to around the 300s but in a couple of hours it would auto set at 1400 on its on. This causes my battery to drain
Click to expand...
Click to collapse
Strangely enough I've settled with Wheatley too! but it spends most of its time at 162 when not in deep sleep (a bit like me!). This really needs posting in the Carbon thread so I would post a few more things here to help or comment on stuff to get to 10 posts and then ask in there. I can't think what could be causing that behaviour, if it was me it would be bye bye 4.4.3 and hello 4.4.4

xbin said:
Strangely enough I've settled with Wheatley too! but it spends most of its time at 162 when not in deep sleep (a bit like me!). This really needs posting in the Carbon thread so I would post a few more things here to help or comment on stuff to get to 10 posts and then ask in there. I can't think what could be causing that behaviour, if it was me it would be bye bye 4.4.3 and hello 4.4.4
Click to expand...
Click to collapse
Yeah i flashed to 4.4.4 thanks though

Never mind above still happens even though I flashed 4.4.4

matizkool said:
Never mind above still happens even though I flashed 4.4.4
Click to expand...
Click to collapse
Does the actual minimum change rather than it simply running continually at 1400+ and if so which governor does it change to if any!
I read somewhere in the Carbon thread someone was having similar problems so they flashed the kernel twice, one directly after the other; seems something wasn't getting written correctly the first time but was the second, and the problem went away. Worth a go...

xbin said:
Does the actual minimum change rather than it simply running continually at 1400+ and if so which governor does it change to if any!
I read somewhere in the Carbon thread someone was having similar problems so they flashed the kernel twice, one directly after the other; seems something wasn't getting written correctly the first time but was the second, and the problem went away. Worth a go...
Click to expand...
Click to collapse
I found this : Q: CPU/GPU frequency doesn't stick?
A: If your frequency settings don’t stick, it's because on certain Qualcomm or JB and higher devices, there are certain system services (thermald/mpdecision/project butter) or kernel feature that rewrite frequency settings based on current thermal status and/or touch input. Certain custom kernels for your device should include work around for these issues.
Is this a fix?

matizkool said:
I found this : Q: CPU/GPU frequency doesn't stick?
A: If your frequency settings don’t stick, it's because on certain Qualcomm or JB and higher devices, there are certain system services (thermald/mpdecision/project butter) or kernel feature that rewrite frequency settings based on current thermal status and/or touch input. Certain custom kernels for your device should include work around for these issues.
Is this a fix?
Click to expand...
Click to collapse
It could help. Trickster is good. However, this suggests that there is something else causing or forcing the frequency setting to be changed. The question is what? and I've no idea:crying:

Haha I found the problem it was either this battery saver app or I changed to scheduler to anything besides row

matizkool said:
Haha I found the problem it was either this battery saver app or I changed to scheduler to anything besides row
Click to expand...
Click to collapse
Thats good. It was probably the battery saver because they usually do the opposite!