Database Users

Random lockups

As per the title, I have started experiencing random system lockups since yesterday. I have had to perform two battery pulls and I'm starting to worry that my ext partition won't be so lucky next time...
I have no idea what is causing the lockups, though both have occurred while using Swype. Coincidence?
For now I'm going to set my system clock back to 600Mhz and use the default input method for a while and see if I still get lockups, at which point I will probably flash another ROM unless I can find a solution, which is where you guys (hopefully) come in. Is there anything else I can do to diagnose and/or solve the problem?
- Typed from my rooted HTC Legend -

It's most likely the OC that's causing the problem, Swpye shouldn't affect the stability. Unless it's a cracked version

Try interactive governor or flash latest kernel from the other thread.

TheGrammarFreak said:
It's most likely the OC that's causing the problem, Swpye shouldn't affect the stability. Unless it's a cracked version
Click to expand...
Click to collapse
That's peculiar, as I've had the processor on 768Mhz for a while now and I've had no problems at all before now.
As for Swype... it could be. ;P
BlaY0 said:
Try interactive governor or flash latest kernel from the other thread.
Click to expand...
Click to collapse
I'll try that, but what exactly does each governor do?

segphault said:
I'll try that, but what exactly does each governor do?
Click to expand...
Click to collapse
It manages when the processor speeds up. It doesn;t run at 768MHz all the time, that's just the highest you allow. Ondemand scales the frequency up when it's needed, and lowers it again afterward. It seems to be a little bugged in our kernels though, and causes crashes.
Interactive does a similar thing, but without polling the CPU. It also ramps the frequency up a little more quickly. I use it, it makes the phone more responsive (IMO), and also eliminates the need for profiles in setCPU (to a degree)

Just checked my kernel version - I already have the latest version (2.6.32.17). I've also set the governor to interactive as suggested, but I have pushed the max clock back to 768Mhz and the min clock to 122Mhz.
While we're here, is there any way to push the min clock down even lower, or would that require fiddling with the kernel? In which case, I have two questions:
1. blay0, I've heard people who can push their min clock down to something ridiculous like 19Mhz if I recall correctly, which makes battery life last a crazy amount of time. Could you include that as the minimum clock in the next kernel for b 0.8?
2. If not, how do I go about changing it myself?
I want to learn.

segphault said:
Just checked my kernel version - I already have the latest version (2.6.32.17). I've also set the governor to interactive as suggested, but I have pushed the max clock back to 768Mhz and the min clock to 122Mhz.
While we're here, is there any way to push the min clock down even lower, or would that require fiddling with the kernel? In which case, I have two questions:
1. blay0, I've heard people who can push their min clock down to something ridiculous like 19Mhz if I recall correctly, which makes battery life last a crazy amount of time. Could you include that as the minimum clock in the next kernel for b 0.8?
2. If not, how do I go about changing it myself?
I want to learn.
Click to expand...
Click to collapse
You'd have to mess around with kernel source code. I wouldn't know where to begin, sorry

Wouldn't 19 MHz min also make the phone painfully slow to wake up? Just curious.
Sent from my Legend using XDA App

MaBlo said:
Wouldn't 19 MHz min also make the phone painfully slow to wake up? Just curious.
Sent from my Legend using XDA App
Click to expand...
Click to collapse
That did cross my mind but other users have reported success with it, so I figured I might as well give it some investigation.

I had mine go to 19 min with screen off once, it did my head in. Maybe interactive with a reasonable upper limit with screen off (like 400) would work, who knows

TheGrammarFreak said:
I had mine go to 19 min with screen off once, it did my head in. Maybe interactive with a reasonable upper limit with screen off (like 400) would work, who knows
Click to expand...
Click to collapse
Maybe not quite 19Mhz, then.
Perhaps we should do some testing to see how much processing power is needed to wake the phone quickly? Is there any way to test that?

Back on topic, I just had another lockup while using the interactive governor. This time I froze up while loading Fruit Ninja.
Now I'm at a total loss for what could be causing the lockups.
- Swyped from my rooted HTC Legend -

Seeing as nobody can seem to pin-point the problem, I'm moving to CM7 permanently as soon as it's released as stable.

Under and Over Volting Madness?

Since we are all wondering what is responsible for this rash of bricks I thought I would start a topic about it. I'm hoping some of our electrical engineering crowd will pipe in on this.
First of all I'm not an engineer and all my knowledge of electronics comes from the practical and theory side of being an amateur radio licensee and a tinkerer of electronic devices.
I think that undervolting is just plain crazy. Our phones are devised to perform in a certain manner at a specific range of voltages. Circuits that are under volted tend to destabilize and do strange things. Resistors change the circuit and the wrong input voltage can change eveything downwind so to speak. Capacitors that are undervolted may not even fire at all. With the advent of LSI's a component may get smoked and you won't even get the satisfaction of smelling the magic smoke (acrid burned smell)
Now over volting definitely has much more applicability here because it's just a plain fact that juicing the cpu results in higher clock speed. Problem here is how to dissipate the heat generated. If we were talking about a desktop we could put on a big heatsink and fan and get decent results. If we wanted to go faster we could do liquid cooling and direct freon injection (phase change) on cpu if we really want to have some fun (if anyone is interested in a world record Epic OC attempt on liquid nitrogen send me a PM). However, none of these methods is going to work well on a phone if you want to keep using it to make phone calls.
From my perspective we can easily OC any processor 10-15% without worrying about heat problems and no under/over volting needed for most phones. As mentioned in another thread, to paraprase Duracell, some can take a licking and some will quit ticking. However, outside of this narrow range we are literally asking for odd kinds of trouble. Just like what we have seen of late...
Sent from Bonsai 7.0.3

Well there is nothing wrong with undervolting..we just need to take things a step at a time...instead of undervolting everything doing 1 change at a time would be much more ideal as its easier to root out problems. One thing I notice is lately these things are released in form of 10-20 changes to try to get better then the kernel before it..instead I would rather see isolated test kernels of 1 thing at a time...so lets say UV ram was the culprit(not saying it is)...but maybe LCD UV is ok..and thats probably what most of us wanted
In my case I was running Genocide and was getting really good underclocks(better then most people) and things were stable..when I saw LCD underclocking on the Vision I just couldn't resist...even though I noticed problems from the get go and my intuition was telling me to go back to Genocide as I had better undervolts there anyways the greed of having LCD undervolt was too much to give up.
What ultimately got me was when I saw the thread about the issue in the kernel...I paniced as I have been having issues and proceeded to shut down my phone to get back into clockworkmod...if I didnt do that my phone would probably still be alive...
So ironically what bricked my phone was not only the kernel itself but the warning about the possible brick lol...thats why I quickly put up the warning to others not to panic and shut down their phones following my footsteps...I dont blame anyone but myself..
There will always be sacrifices along the way..thats just how development is...

I agree,I think we are going down the wrong road when it comes to kernels,but everything is trial and error,just wish more time was spent testing; Not just "hey it boots,testers like it" 2 hours later its uploaded...
Sent from my SPH-D700 using XDA Premium App

ecooce said:
I agree,I think we are going down the wrong road when it comes to kernels,but everything is trial and error,just wish more time was spent testing; Not just "hey it boots,testers like it" 2 hours later its uploaded...
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Well as I said it would have been nice if we got the kernel features separated...aka 1 kernel with UV ram, one kernel with UV CPU and one kernel with UV LCD..then 10 days later if there were no issues go to UV CPU + LCD kernel and UV RAM + UV LCD Kernel..and then if everything is ok 10 days later merge them all into one..
My regret is not bricking my phone but the fact that it was bricked without providing much use...at the very least if my phone was bricked during a UV ram only test for example we would know where the issue was and not go that road..instead we are now stuck guessing the possibilities...
I guess our ambition is getting the better of us :/..slow and steady wins the race...

I totally agree with you about all the changes at one time being detrimental to good development. I've brought this up several times with the Bonsai Team. The problem from my perspective is that if you change 20 things and you have a problem you have no clue about what screwed what. Making one change and making observations is the hallmark of scientific testing. Now sometimes doctors use the shotgun approach, but only when they don't know what will work and someones life is on the line.
Sent from Bonsai 7.0.3

Top Nurse said:
I totally agree with you about all the changes at one time being detrimental to good development. I've brought this up several times with the Bonsai Team. The problem from my perspective is that if you change 20 things and you have a problem you have no clue about what screwed what. Making one change and making observations is the hallmark of scientific testing. Now sometimes doctors use the shotgun approach, but only when they don't know what will work and someones life is on the line.
Sent from Bonsai 7.0.3
Click to expand...
Click to collapse
Yeah I agree as well, however these are regular guys and gals that do this in their own free time and if they compile one thing at a time I believe it becomes way more time consuming. It could literally take months or even years to completely shake down a build, going one by one. Bleeding edge is the only way it can really be done in an open source/freelance environment like this.

epic4GEE said:
Yeah I agree as well, however these are regular guys and gals that do this in their own free time and if they compile one thing at a time I believe it becomes way more time consuming. It could literally take months or even years to completely shake down a build, going one by one. Bleeding edge is the only way it can really be done in an open source/freelance environment like this.
Click to expand...
Click to collapse
your not compiling line by line...your just compiling 1 feature at a time...it may take more time to compile, but you also end up saving time on debugging.
I mean its up to the devs to do their own thing, we can't exactly tell them what to do..but we can offer our suggestions..its up to them if they wish to try it that way or not.
And bleeding edge is not how its done in an open source environment..in an open source environment a feature is tested 1 at a time by forking the tree..then when its been properly finished and tested it gets merged back into the main tree for a release. If it fails to hit stable by time of main release it rolls over to the next release.
Of course everyone has different development policies but the above is a very common one.

Definitely agree about being real careful with undervolting just to squeeze a few percent out of the battery life. Top Nurse for not-an-engineer you are essentially correct about disrupting circuits especially transistors and diodes that function on a specified voltage drop. I, myself, thought I bricked twice only to find out I had undervolted my sleep speed of 200 Mhz by 125 mV essentially bringing it to 100Mhz. The interesting thing is Genocide has all this undervolting and 1.4Ghz speeds and yet I have not heard of any rash of bricks there. Maybe that kernel should be used as a comparison baseline.
Do you BONSAI?

If I remeber right Genocide dosnt UV the RAM...
Sent from my SPH-D700 using XDA Premium App

ecooce said:
If I remeber right Genocide dosnt UV the RAM...
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Does it undervolt the display?

mattallica76 said:
Does it undervolt the display?
Click to expand...
Click to collapse
no it doesnt, but i dont think display is the issue..also genocide doesnt have BFQ..only CFQ

mattallica76 said:
Does it undervolt the display?
Click to expand...
Click to collapse
No vision kernel was the first kernel publicly released that uv the screen and ram
Sent from my SPH-D700 using Tapatalk

MysteryEmotionz said:
No vision kernel was the first kernel publicly released that uv the screen and ram
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I do believe the bonsai beta 4.1.0b9 kernel had the display undervolted as well, and I believe the BFQ was enabled by default...someone correct me if I'm wrong. More commonalities I'm sure.

mattallica76 said:
I do believe the bonsai beta 4.1.0b9 kernel had the display undervolted as well, and I believe the BFQ was enabled by default...someone correct me if I'm wrong. More commonalities I'm sure.
Click to expand...
Click to collapse
I found this changelog for bonsai:
- Voodoo color
- Undervolting in several modes including Screen and RAM at certain cpu frequencies
- Overclocking and underclocking configuration for 100mhz-1120mhz is now standard
- Read_ahead tuning to 4096 bytes
- Volume switch provides silent and vibrate control
- Upgrade to CWM 3.0.2.4
- Reduced battery % limit to 5% for Camera, VideoPlayer, and MusicPlayer.
- Increased windowsmgr refresh events_per_sec from 60 to 68
- Updated Maps.apk
---
I dont see BFQ..unless they always had it...
One thing I do notice with Genocide vs VisionKernel is on Genocide kernel 100mhz never really worked...and i odnt mean crashing...I used CPU Spy and it never showed 100mhz..on VisionKernel I did have it hit 100mhz a few times..
Edit: I see BFQ was added on the 31st - r458 - Add BFQ scheduler from Paolo Valente

gTen said:
I found this changelog for bonsai:
- Voodoo color
- Undervolting in several modes including Screen and RAM at certain cpu frequencies
- Overclocking and underclocking configuration for 100mhz-1120mhz is now standard
- Read_ahead tuning to 4096 bytes
- Volume switch provides silent and vibrate control
- Upgrade to CWM 3.0.2.4
- Reduced battery % limit to 5% for Camera, VideoPlayer, and MusicPlayer.
- Increased windowsmgr refresh events_per_sec from 60 to 68
- Updated Maps.apk
---
I dont see BFQ..unless they always had it...
One thing I do notice with Genocide vs VisionKernel is on Genocide kernel 100mhz never really worked...and i odnt mean crashing...I used CPU Spy and it never showed 100mhz..on VisionKernel I did have it hit 100mhz a few times..
Click to expand...
Click to collapse
On the stock Bonsai 4.0.1 kernel, it would not scale down to 100mhz with the conservative governor, but it would with interactive. The 4.1.0 b9 kernel fixed the issue and it would scale to 100mhz with no problem. (other than bricking your phone)

mattallica76 said:
On the stock Bonsai 4.0.1 kernel, it would not scale down to 100mhz with the conservative governor, but it would with interactive. The 4.1.0 b9 kernel fixed the issue and it would scale to 100mhz with no problem. (other than bricking your phone)
Click to expand...
Click to collapse
Hmm..does any other kernel achieve 100mhz?
When I was looking at CPU Spy usually at max it would be like a few seconds on the 100mhz frequency...I would think when shutting down a phone 100mhz frequency might be used during a short interval..the only other person who claimed he got same thing and not on power down but at lock screen..which I know after waking it hits 100mhz...there might be a pattern here :/

So there are a lot of similiarities between the 2 bricking kernels and differences to genocide. Since there is no charging light when plugged in, it is still some catastrophic failure. Would RAM or video failure be enough to prevent the phone from charging? Or turn on the charge light?
Do you BONSAI?

kennyglass123 said:
So there are a lot of similiarities between the 2 bricking kernels and differences to genocide. Since there is no charging light when plugged in, it is still some catastrophic failure. Would RAM or video failure be enough to prevent the phone from charging? Or turn on the charge light?
Do you BONSAI?
Click to expand...
Click to collapse
I find it very very very very unlikely that the screen would do this..usually the screen is a separate component..In a pc for example ive had pc not turn on due to bad ram though...

gTen said:
I find it very very very very unlikely that the screen would do this..usually the screen is a separate component..In a pc for example ive had pc not turn on due to bad ram though...
Click to expand...
Click to collapse
Wasn't thinking the screen, I was thinking the video components on the circuit board due to LCD undervolting. But was def thinking dead RAM as a possibility.
Do you BONSAI?

With just Voltage Control my phone would hit 100 every blue moon. In conjunction with SetCPU on conservative it now idles fine at 100mhz and UV'd by 125. It seems to automatically revert to noop whenever I set it to bpq.

[Q] [Opinions] Undervolt Settings.

First off, I would like to apologize in advance in case a thread like this exist and I can't find it.. :/ (Search is down, tried Googling) also, if anyone believes this to be in the wrong forum.
ANYWAYS! This is intended to be a preference/opinions thread centering around your OC/UC and Undervolt settings. Feel free to post your current set-up in Voltage Control (or any app of the like) and what Kernel you are running! I wanted to start this to get an idea of what everyone else is setting their UV and CPU clocks to, and possibly give a few of them a try on my own device. :]
Personally all of my clock speeds are at their defaults except for 1000Mhz @ 1200mV. (-75mV). I am also rocking Genocide v1.0 and getting a decent 30hrs of battery life with pretty moderate use.
Post away!

It is kind of pointless since every phone is different so cannot do exactly the same as others. Most can't do 1.4Ghz and most don't wake from sleep at 100 Mhz. All depends what you use your phone for. Mine runs fine at 1.3Ghz except for some TV apps will freeze.
Do you BONSAI?

kennyglass123 said:
It is kind of pointless since every phone is different so cannot do exactly the same as others. Most can't do 1.4Ghz and most don't wake from sleep at 100 Mhz. All depends what you use your phone for. Mine runs fine at 1.3Ghz except for some TV apps will freeze.
Do you BONSAI?
Click to expand...
Click to collapse
I believe that would be my point however.. curious as to what other people are running as far as cpu and voltage is concerned. Their success and failures. What people can get away with and remain stable. I, and others, could then try their setup (taking precautions of course; ie Nandroid backup.) And see what we get. Who knows, maybe I might adapt a set up that runs better on my device than my current one.
Sent from my SPH-D700 using XDA Premium App

Yes, every phone is different, but that is just more of a reason to collect data - perhaps a baseline can be established, which would be helpful in determining if a particular phone is messed up or just at the low end of the scale. Right now it is hard to determine if a particular phone's troubles are caused by low quality or by damaged hardware.
I keep all voltages at stock, and don't use any OC - my phone runs fine as is, and the battery life actually seemed worse with UV (and my screen felt hot with the screen UV).
Sent from my SPH-D700 using XDA App

My phone wakes from 100 but won't do 1.4ghz for even a couple seconds before reboot but 1.3ghz lasts about 20 minutes before reboot and 1.2ghz is stable. As for undervolts it can handle -25 on 1.2ghz and -50 on 1 and 1.1ghz -50 on 800mhz and that's it otherwise becomes unstable and reboots. Battery life and performance seem to meet at 800mhz with a -50 undervolt games run smooth too and 12 hours of battery. Oddly enough benchmarks are consistantly higher on 1.12ghz than on 1.2ghz I wonder if I'm the only one?
Sent from my midnight rom 5.2 genocide 1.0 epic [email protected] using xda premium app

xopher.hunter said:
My phone wakes from 100 but won't do 1.4ghz for even a couple seconds before reboot but 1.3ghz lasts about 20 minutes before reboot and 1.2ghz is stable. As for undervolts it can handle -25 on 1.2ghz and -50 on 1 and 1.1ghz -50 on 800mhz and that's it otherwise becomes unstable and reboots. Battery life and performance seem to meet at 800mhz with a -50 undervolt games run smooth too and 12 hours of battery. Oddly enough benchmarks are consistantly higher on 1.12ghz than on 1.2ghz I wonder if I'm the only one?
Sent from my midnight rom 5.2 genocide 1.0 epic [email protected] using xda premium app
Click to expand...
Click to collapse
Just to throw it out there. Aggressive undervolts will do more harm than good to your battery life. By that, I mean you'll drain your battery even more.
Sent from my SPH-D700 using XDA Premium App

I can only use Genocide kernel to get 1.3ghz at stock voltage with since all the other choices are uv'd. My last two Epics were able to handle uv'd 1.4ghz by 50mV but I'm not really complaining as I think this is a new phone they gave me and not a refurb. I currently have 100-400 uv'd by 100mV, 600-1000 uv'd by 75mV and 1300 at stock.

My phone can handle 1.4 Ghz but only with the stock voltages. If I try to touch it even by 25mV it locks up.
Who all has enabled the 100Mhz step? I noticed when I did my phone went into Deep Sleep a lot less by a noticeable amount. Staying at 100Mhz a lot.

Always interesting to hear about all this theory behind the reasons for undervolting OC and UC, then to hear about the issues (at times extreme) some have. I would also like to know who uses the 100 step and if it is noticeably better on battery life than the 200? Unfortunately I am missing out on it if I am. Still running Genocide here, but with 1.0 at -50mv 800 @ -50 and 600 @ -25. Very stable and still at 30+ battery life. Having 1.0 down 75 made me nervous. although I hear people dropping it down -100mv successfully.
Sent from my SPH-D700 using XDA Premium App

Good tip about "aggressive UnderVolting"...didn't know that actually drains your battery more. Might explain why 6 hours into my day, my battery is down to 30% already!!! I had it set at 1120Mhz UV to 1175mV (Stock = 1300)...
So now I'm going to try 1200Mhz only UV by 50...see what my battery life is after this!

Custodian said:
Just to throw it out there. Aggressive undervolts will do more harm than good to your battery life. By that, I mean you'll drain your battery even more.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Can you explain how this is so? Is this based on any actual research, experimentation, or online documentation, or is this just your own opinion?
Unless your undervolt causes the CPU to hang (I've seen mine start to warm up when it's hung, until a battery pull), I don't understand how providing less voltage to the cpu will cause it to drain the battery faster.

If you change the voltage settings please don't blame the rom developers when you phone bricks...
Sent from Bonsai 7.1.3.1

I'm running Twilight Zone v 1.1.1 RC1-Hajime Taisho, Vision kernel v 1.2
SetCpu-1.450 max
-1.450 min
Quadrant-2377
Linpack-20.577
Voltage Control-1.450
Uv -100
Quadrant-2346
Linpack-21.495
I ran SetCpu, benchmarks, ran VC, benchmarks..... This Epic runs super fast, with no FC's or any other problems at all. I'm currently using VC with the uv-100. As far as excessive battery use, I have Mugen 3200 mah battery. This battery lasts all day in heavy use with no problem.
Sent from my SPH-D700 using XDA Premium App

Possible fix for random reboots on Gingerbread

Here are my current stable settings:
SetCPU
Min: 100mhz
Max: 1000mhz
Governor: Ondemand
Profile: Screen Off
--Min: 100mhz
--Max: 200mhz
--Priority: 100
--Governor: Ondemand
Tegrak:
Governor: Ondemand
Scaling: 100-1000mhz
Optimization:
--200mhz Core Voltage: 1025mv
--100mhz Core Voltage: 925mv
Both SetCPU and Tegrak are running side by side.
No random reboots for over a week.
Battery should last between 20-25 hours with normal usage.
Certain phones might need a higher voltage, you may need to do some experimenting to get things stable.
Old text
Anyone experiencing random reboots should try using SetCPU or Tegrak to set the CPU to 1000mhz-1000mhz instead of 100mhz-1000mhz.
I was previously getting 3-4 reboots per day. I set my CPU to 1000mhz-1000mhz using Tegrak four days ago and have not had a single reboot since.
Sure, my battery only lasts about 10 hours vs 20 or so, but at least I can rely on my phone.
Of course I could just be lucky, and who knows it might just randomly reboot any time now.. So, obviously there is no guarantee it will work for anyone else.
Just as a note I also tried 200-1000 and 400-1000, but still had random reboots every few hours.
I am currently testing 200mhz-200mhz with the screen off and 1000mhz-1000mhz with the screen on using SetCPU. I will update this thread in a few days or if it randomly reboots.
Update: 200mhz during screen off causes the phone to not wake up (happened three times). I'm currently testing 400mhz.
Update 2: I got a random reboot last night while asleep using 400mhz. I will see if it continues.
Update 3: Got another reboot at 400mhz. I am now testing 100mhz-1000mhz at 1.275v Core and 1.100v Internal for all frequencies, this should rule out any voltage issues.
Update 4: Made a spreadsheet with my findings, it does not seem to be a voltage issue.
Update 5: Scratch that, I have been using a [email protected] screen off profile for the last 20h... No black screen of death or random reboots. Next up is [email protected]
Update 6: [email protected] is unstable, rebooted after 3 hours. Testing [email protected], 6 hours in and no reboots yet.
Update 7: [email protected] seems to be stable, 24 hours and no reboots yet.
Old text
Click to expand...
Click to collapse
Here is a spreadsheet of my current findings.

My random reboots always came while in deep sleep so this will not work for me. I switched back to a EG22 ROM and get no reboots.
Sent from my SPH-D700 using XDA App

kennyglass123 said:
My random reboots always came while in deep sleep so this will not work for me. I switched back to a EG22 ROM and get no reboots.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Same here, but for some odd reason this (seems to have) fixed it for me. Although, on EG22 I also got a lot of random reboots, so maybe I have a different issue.
I did not get reboots on ED12, EE03, or EF02..
EG22, EH06, and EH17 randomly reboot for me.

I thought it might be similiar to the sleep of death phones would get going from 100 Mhz to deep sleep and also tried boosting to 200 Mhz on EH17 but it didn't help. It may be related and your discovery may aid Devs in fixing the problem If it is still there when source is released.
Sent from my SPH-D700 using XDA App

I think the problem lies in the voltage settings that deep sleep runs on, like in tegrak overclock if the internal voltage is too low the phone will reboot.
Maybe some samsung devs tried lowering the voltages in deep sleep to optimize battery life but only tested it for like a couple hours and didn't notice it.
Are there any ways to edit these values somewhere in the kernel because I know tegrak nor setcpu can do anything to deep sleep.
Sent from my SPH-D700 using xda premium

xopher.hunter said:
I think the problem lies in the voltage settings that deep sleep runs on, like in tegrak overclock if the internal voltage is too low the phone will reboot.
Maybe some samsung devs tried lowering the voltages in deep sleep to optimize battery life but only tested it for like a couple hours and didn't notice it.
Are there any ways to edit these values somewhere in the kernel because I know tegrak nor setcpu can do anything to deep sleep.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
+1 That's what I think.

That would explain why my phone never reboots with the screen on.

I think we may be onto something in this thread.
Sent from my SPH-D700 using XDA App

Agreed. My phone has always randomly rebooted when the screen is off. I set the minimum to 400 Mhz as well. Will let you know what goes down.

Someone should point the SamSprint devs to this thread lol. That would be amusing if it was in fact the problem/solution to random reboots.
Sent from my SPH-D700 using xda premium

Ok, so far 400mhz screen off has been stable, 12:56 on battery, and 1:01 screen on time.
I noticed something.. Here is what CPU Spy says:
1000mhz: 00:55:03
400mhz: 1:35:09
Deep Sleep: 9:22:42
I reset the stats once, which is why 1000mhz is 6 min different from the screen on time.
The phone was asleep for 11:55, but it was only in deep sleep for 9:22, what this tells me is when the screen is off and the phone needs to "do something" (I have Skype open 24/7, and 3 accounts in k9)it will jump up to 400mhz (or normally, anywhere between 100-1000mhz) for a time until it is finished, and then drop back into deep sleep.
It might be worth a try to bump up the voltage for 100mhz and 200mhz and see if that helps anything.

So I played around with the clock settings a bit in the last 24 hours. Here's what I've found:
If I set the minimum to 200Mhz or lower, and leave the phone alone, it continues to have random reboots. With the minimum set to 400Mhz, it sleeps fine all day long. I also tried adding in the profile to enable a minimum and maximum of 200Mhz when the screen is off. In the 4 hours that was set I didn't get any random reboots, but when I went to wake the phone up, it rebooted. And with the min/max set to 200 on the screen sleep profile on, if the screen turns off and I try to turn it back on, it would reboot. What I found to work best is if the screen off profile min and max is set to 400, and then the mains are at 200 min and 1000 max, it runs (so far for me) with out any reboots and the phone will wake up like normal again. This has been good for the last 10 hours, so I will continue to let it simmer and will see how it goes.
So I know that the 100Mhz and 200Mhz states were active and working in Froyo. If they aren't working correctly here, could it possibly be because Samsung set the voltages of those two freq's too low in GB?

when looking at the voltage settings for 400, they are lower in GB versus Froyo by -50. maybe thats causing the issue?

If its really this simple as far as clock and voltage how the hell does Samsung not find that.
Sent from my SPH-D700 using xda premium

What software are you guys using to adjust these settings, SetCPU? Is there a free alternative that does the same thing? Since I've been reading this thread, my phone has slept to death several times (EH06) - I'm hoping this solves it.

ss4rob said:
What software are you guys using to adjust these settings, SetCPU? Is there a free alternative that does the same thing? Since I've been reading this thread, my phone has slept to death several times (EH06) - I'm hoping this solves it.
Click to expand...
Click to collapse
SetCPU is free for xda members
Sent from my SPH-D700 using Tapatalk

I recently downgraded to EC05 due to the reboots, but left the EH17 Modem.
I still get reboots, and now believe the reboots are related to the modem, GPS issues, and general updating, as new e-mail notifications would sometimes be followed with an immediate reboot.
I'm gonna flash the EF02 Modem onto EH17 to see if it works, I have nothing to lose at this point as i'm returning my epic today. Stupid B and V dont work on my keyboard

radugb said:
So I played around with the clock settings a bit in the last 24 hours. Here's what I've found:
If I set the minimum to 200Mhz or lower, and leave the phone alone, it continues to have random reboots. With the minimum set to 400Mhz, it sleeps fine all day long. I also tried adding in the profile to enable a minimum and maximum of 200Mhz when the screen is off. In the 4 hours that was set I didn't get any random reboots, but when I went to wake the phone up, it rebooted. And with the min/max set to 200 on the screen sleep profile on, if the screen turns off and I try to turn it back on, it would reboot. What I found to work best is if the screen off profile min and max is set to 400, and then the mains are at 200 min and 1000 max, it runs (so far for me) with out any reboots and the phone will wake up like normal again. This has been good for the last 10 hours, so I will continue to let it simmer and will see how it goes.
So I know that the 100Mhz and 200Mhz states were active and working in Froyo. If they aren't working correctly here, could it possibly be because Samsung set the voltages of those two freq's too low in GB?
Click to expand...
Click to collapse
What scaling are you using?

This sounds more like a band-aid than a fix. Perhaps the system doesn't scale the clock speed properly when waking, and keeping the clock speed artificially high in sleep mode masks the problem.Not an ideal solution because it kills battery.

omair2005 said:
when looking at the voltage settings for 400, they are lower in GB versus Froyo by -50. maybe thats causing the issue?
Click to expand...
Click to collapse
Good catch. Here are the voltages on EH06 (as reported by Tegrak):
1000mhz
Core Voltage: 1275mv
Internal Voltage: 1100mv
800mhz
Core Voltage: 1200mv
Internal Voltage: 1100mv
400mhz
Core Voltage: 1050mv
Internal Voltage: 1100mv
200mhz
Core Voltage: 950mv
Internal Voltage: 1100mv
100mhz
Core Voltage: 950mv
Internal Voltage: 1000mv
Could someone list out the stock voltages on EC05?
Lord-Anubis said:
I recently downgraded to EC05 due to the reboots, but left the EH17 Modem.
I still get reboots, and now believe the reboots are related to the modem, GPS issues, and general updating, as new e-mail notifications would sometimes be followed with an immediate reboot.
I'm gonna flash the EF02 Modem onto EH17 to see if it works, I have nothing to lose at this point as i'm returning my epic today. Stupid B and V dont work on my keyboard
Click to expand...
Click to collapse
That is what I thought at first... But then I tried the EF02, and EE03 modems and still experienced reboots (I am currently on the EE03 modem).
poit said:
This sounds more like a band-aid than a fix. Perhaps the system doesn't scale the clock speed properly when waking, and keeping the clock speed artificially high in sleep mode masks the problem.Not an ideal solution because it kills battery.
Click to expand...
Click to collapse
While this is true (for now) it could lead to a more viable fix. If the voltage actually is lower in GB, that could be at least part of the problem.

[TWEAK][Siyah Kernel 4.1.1+][Extweaks] Get up to 7 hours of screen usage

WARNING: Use this settings at your own risk. I am not responsible for what will happen to your phone.
So, Siyah Kernel 4.1.4 has been released, and since 4.1.1 and its new features I have struggled for obtaining maximum battery life without loosing smoothness.
I tested these settings on 5 phones (Galaxy S2 GT-I9100): mine and my friends' ones, and we all got the same (more or less) results: it's awesome!
Screen usage can get up to 7 hours. I did these tests with mobile data on for all phone usage, and not in deep sleep. When I was at home I switched to Wi-fi.
My ROM is AOKP M6 (ICS 4.0.4), other tests were made on Resurrection remix JB, stock XWLPF (ics), CM9 stable (screen usage: about 6 hours, no more), and AOKP JB (latest).
Extweaks settings:
CPU:
GENTLE FAIR SLEEPERS: ON
CPU HOTPLUG: (default)
CFS TWEAKS: Linux kernel defaults
CPU IDLE MODE: AFTR+LPA
SMOOTH SCALING LEVEL: 800 mHz
MAX CPU LOCK: Dual core mode
CPU UNDERVOLTING: - 50mV (if you get freezes, set -25mV)
CPU STEP COUNT: 16 (all available)
GOVERNOR: pegasusq
MAX FREQ: 1200 MHz
MIN FREQ: 200 MHz
GPU:
MALI TOUCH BOOST LEVEL: Step 2/Step 3
GPU STEP 1: 44 MHz
GPU STEP 2: 66 MHz
GPU STEP 3: 100 MHz
GPU STEP 4: 200 MHz
GPU VOLTAGE LEVEL 1, 2 AND 3: 800 mV
GPU VOLTAGE LEVEL 4: 950 mV
THRESHOLDS: default values
AUDIO:
HEADPHONE AMPLIFIER: 0 (set this value as you want and as you ears can stand it, it doesn't affect battery life unless you listen to music)
SCREEN:
TOUCHMOVE SENSITIVITY: 3 pixel
ALL OTHER SETTINGS: default values
mDNIe negative toggle: off
BLN:
BLN: off
NOTIFICATION TIMEOUT: never timeout
BLN EFFECT: set what you want, cause BLN is disabled
LED TIMEOUT: use ROM defaults
LED FADEOUT: on
LEDS ON WITH TOUCH: off
LED VOLTAGE LEVEL: 2700 mV (2750/2800 mV if led lights are dim)
MISC:
ANDROID LOGGER: off
DEFAULT I/O SCHEDULER: cfq/noop
ALL OTHER SETTINGS: default values
I think they are not too aggressive values, but if you get freezes, I recommend you reset your extweaks settings via CWM recovery and then use less aggressive ones.
In the attached screenshots, battery stats analysis starts from 91% since I had to restart my phone, and when it was at 10% I plugged the USB cable in to transfer a .zip file in my SD card, but I don't think that this 15-second charge affected my test (I'm sure it didn't!).
Phone usage was high today, I used Tapatalk, created a new UCCW skin, did some long phone calls, Facebook, messaging, e-mail checking, and other stuff I don't remember since the battery stats don't even report them (lol).
Notice that this is an extreme test. 7 hours of screen usage is not a myth, reality instead, but you cannot get them with the so called 'everyday usage'.
Screenshots of test made on my usual phone usage will come soon
THANKS:
gokhanmoral : the men who created THE kernel, the Siyah kernel.
geko95gek : author of MagicConfig. He found out the perfect balance between GPU frequencies and voltages.

I think you forgot the most important part : the extended battery

Extended battery? so what we can get on normal? 4h?

minidou-77 said:
I think you forgot the most important part : the extended battery
Click to expand...
Click to collapse
I have a 1650 mAh battery... never had extended 2000 mAh

I don't think these settings are good for performance... I have used even higher settings and there was lagg in some cases. But that was all on my phone

This seems largely similar to my MagicConfig thread.
Sent from my HTC One X

7 hrs screen time with 1200mhz max frequency and stock battery.. how much more if it's set on 800mhz.. 8-9 hours probably on stock batt?
you could have atleast included what you were doing in those 7 hours screen time like browsing, texting, facebook, etc, also the brightness of the screen, battery chart..

gb.yolo said:
I have a 1650 mAh battery... never had extended 2000 mAh
Click to expand...
Click to collapse
I saw u're using XXKH3 modem as it's also my favourite... can u please share with me XXKH3 RIL ? It was what I've been looking for & nobody could provide it w/ links or a drop box.. thanks..
Sent from my GT-I9100 using xda app-developers app

I only have 3 steps on my gpu?
Sent from my GT-I9100 using xda app-developers app
Just updated my siyah. Goin to try this config

Adam Hui said:
I saw u're using XXKH3 modem as it's also my favourite... can u please share with me XXKH3 RIL ? It was what I've been looking for & nobody could provide it w/ links or a drop box.. thanks..
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
My modem's XXKH3, and i downloaded it here: http://www.ziddu.com/download/19200730/Modem-XXKH3-CWM-DragoN3252.zip.html
hope this helps
cheers!

saywhatt said:
My modem's XXKH3, and i downloaded it here: http://www.ziddu.com/download/19200730/Modem-XXKH3-CWM-DragoN3252.zip.html
hope this helps
cheers!
Click to expand...
Click to collapse
Thanks for reply mate..
I already have XXKH3 modem, I mean I need XXKH3 RIL (radio interface layer) to match modem with as it was the only method to avoid RIL crashes & RILJ wakelocks which prevents phone go to deepsleep.. do u have it sweet?
Sent from my GT-I9100 using xda app-developers app

Dark Emotion said:
I don't think these settings are good for performance... I have used even higher settings and there was lagg in some cases. But that was all on my phone
Click to expand...
Click to collapse
As you said, it was all on your phone. This is why with someone's settings nobody get exactly the same results: I get lags, you don't get lags, but he sometimes gets lags and sometimes not
geko95gek said:
This seems largely similar to my MagicConfig thread.
Click to expand...
Click to collapse
MagicConfig was my starting point for GPU voltage levels, how cannot I admit? I always used those frequency steps (first post) but I've never found the right voltages to avoid lags, especially when turning screen on. And I forgot to thank you. I say sorry mate
Tricks25 said:
7 hrs screen time with 1200mhz max frequency and stock battery.. how much more if it's set on 800mhz.. 8-9 hours probably on stock batt?
you could have atleast included what you were doing in those 7 hours screen time like browsing, texting, facebook, etc, also the brightness of the screen, battery chart..
Click to expand...
Click to collapse
In the first post:
Phone usage was medium-high today, I used Tapatalk, created a new UCCW skin, did some long phone calls, Facebook, messaging, e-mail checking.
Click to expand...
Click to collapse
@Adam Hui sorry if I can't help you, but I don't have a RIL matching the XXKH3 modem. I have XXLPW, and since it is all going well with it (deep sleep is ok, wakelocks are ok [more or less]) I didn't much care about it

Try GetRIL
Adam Hui said:
Thanks for reply mate..
I already have XXKH3 modem, I mean I need XXKH3 RIL (radio interface layer) to match modem with as it was the only method to avoid RIL crashes & RILJ wakelocks which prevents phone go to deepsleep.. do u have it sweet?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Try the GetRIL app, it should be able to find the RIL for you.
But if I understand correctly, KH3 is a Modem from the GB firmwares, and you're running and ICS Firmware, the RIL is part of the Firmware and I don't think you can install a GB RIL on ICS... but try the app.

Need to test this. The magic config thread was slightly outdated and with new Siyah v4+ releases, it never got updated.
Sent from my GT-I9100 using Tapatalk 2

rakeshishere said:
Need to test this. The magic config thread was slightly outdated and with new Siyah v4+ releases, it never got updated.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
It will once I get some testing results.
As I have mentioned before I do not possess an s2 anymore so it makes the process of updates slower. Doesn't hurt to be a bit patient right?
Sent from my HTC One X

geko95gek said:
It will once I get some testing results.
As I have mentioned before I do not possess an s2 anymore so it makes the process of updates slower. Doesn't hurt to be a bit patient right?
Sent from my HTC One X
Click to expand...
Click to collapse
No offense mate. I'm aware that you no longer own S2 and moved to HOX. I just gave my opinion about magic config thread and it wasn't towards you.
Sent from my GT-I9100 using Tapatalk 2

Great ! I'll try it.

Looks great, must try....................:good:

Thanks gb.yolo
I configured my phone with your settings and it's running nice.
I can't really feel a difference in "smoothness" and it's the first time I change GPU frequencies and UV... but I still can't really tell a difference... what should I expect from changing GPU params, other than battery life?

buddy i cant find Siyah Kernel 4.1.1+ do you have any dwonlad that.