yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] Many40:
There are a few possibilities:

1. This option is the easiest one (available in ICS 4.0.3, should be in your rom as well): "settings/display/Auto adjust screen power" option. - it toggles power_reduce value;

2. Script:

#!/system/bin/ sh

echo "1" > /sys/class/lcd/panel/power_reduce

locate file in /etc/init.d folder and set privileges RWX R-X R-X

for me doesn't work - probably another script or rom settings changes this back during boot sequence

In my case script works if started during boot by script manager (this is being done at the and of boot sequence).
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
which minimal frequency are you set on (freq_min) ?

If it's 25 or 50Mhz, that might be the problem....
[Galaxy S II Q&A, Help & Troubleshooting] TheStigx:
I cannot find that option in extweaks.
[Galaxy S II Q&A, Help & Troubleshooting] Many40:
CPU / Scalling_Min_Freq

Edit: OK with ExTweaks minimum is bloked to 100MHz. Do you use Voltage Control or other UC/UV app?
[Galaxy S II Q&A, Help & Troubleshooting] TheStigx:
Thanks,

It says

100000 mhz

---------- Post added at 08:07 PM ---------- Previous post was at 08:02 PM ----------

Nope, I only have the extweaks "pro".
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
100 freq_min should be ok ...you can have a look at GPU tab and see what freq the first gpu step is on (probalby 40Mhz, and raise this up a bit ; try 133)
[Galaxy S II Q&A, Help & Troubleshooting] TheStigx:
Thanks,

But it doesn't help.
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
There's one other possability :

under CPU tab : cpu idle mode ; set to idle only

this might save some less juice (some say not), but it keeps the system more reactive coming from an inactive state.

It also depends on what you find 'slow'

Is it when it's been off for at least 5 minutes (so when turning screen off, and screen back on again, it reacts ok?) or is it consistently?

It could be rom related.
[Galaxy S II Q&A, Help & Troubleshooting] Many40:
Exactly he hasn't stated how long does it take to wake up. Normal time for ICS is about 1s. BTW john, if idle helps maybe he could check something in the middle: Idla+LPA to save more juice then?
[Galaxy S II Q&A, Help & Troubleshooting] TheStigx:
Well, it is fast when you turn it off and on right after you turned it off. But after 5 minutes it takes 1-2 seconds. But the idle options didn't help :(

I didn't know the time for ICS to turn on the screen is 1 second.
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
is an option..then I would choose one above idle ---> AFTR only

this way cpu is clocked off but cpu cache remains, and other hardware parts remain semi-active, ready to go

LPA would power down cpu after a while (something along the way of 3-3.5 minutes) and enter deep sleep...which is what might be causing a slight lag

like you siad +/- 1 sec. ; I don't find that a problem.....

EDIT: just read the post above

...then it's normal, ICS behaviour, like Many said....
[Galaxy S II Q&A, Help & Troubleshooting] TheStigx:
Oh ok then, I thought it was a problem, but I guess not, but thanks for the help guys :)
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
screen undervolting

I've been testing screen undervolting (on stock & AOKP) using :

kmemhelper -n ldo13_init_data -t int -o 8 2700000

kmemhelper -n ldo13_init_data -t int -o 12 2700000

which writes the init-voltages of the screen voltage regulator to the kernel

result (powersaving) : zilch! - 0 - nothing!

have checked whether these values are actually being writen to the respective structures, and they read back just fine

I can think of serveral scenarios

1. these values are intiaited once very early in the boot proces and will not be applied later, even when changed

2. somehow you can change them, but they have no effect, until some action is taken (soft-reboot, maybe?)

3. changing these values (even to an extreme 2500000 uV) have no effect at all (would be strange..)

4. these are values that can only be changed by compiling them into the kernel (hard-coded), eventhough they are exposed and readable with kmemhelper

Any which way, nothing to gain here, sadly enough....

What I did discover is that there seems to be a huge difference in stock roms among eachother and AOKP concerning screen battery usage.

One thing was very obvious: stock roms have a very overpowering green accent, which even when screen is at it's darkest, tends to glow out.

This suggest that samsung is probably using a different color correction table/filter for the screendriver, which in turn could be the cause that stock roms tend to use more (screen)power under equal conditions than AOKP (and probably AOSP/CM9) up to 40-60% more. (or maybe it's just HydrogenICS??? being that power-firendly? - don't really think so, but you never know...)

Another thing was the difference in powerconsumption in general between different stock rom version (I was using LPQ, am now on LPD, which is a big difference LPD having less power usage ; bigger than I expected) and now I will be trying some other stock version and see if there's a difference compared to what I've already tried....

Anyone care to comment ? Having had similar experiences? Any suggestions?

I am thinking of trying LP7, LPG and/or LPW (being version used in the nearby regions, so should be compatible with local networks)
[Galaxy S II Q&A, Help & Troubleshooting] duykhang524:
Had that issue which stopped since I switched to the ported S3 music player :) much better with shuffle songs and music square.
[Galaxy S II Q&A, Help & Troubleshooting] bervin:
I was referring to something more aggressive in terms of battery savings as you had recommended those settings to save battery. I wasn't looking to play with my colours.
[Galaxy S II Q&A, Help & Troubleshooting] Oso Polar:
user_cb & user_cr are only responsible for screen color balance, not for power saving. They control amount of blue and red (in relation to green that is fixed, I presume it is always 128).
[Galaxy S II Q&A, Help & Troubleshooting] #illidan:
Well I had a similar observation with screen uv as in there was no difference in power consumption at all & I'm just not sure why. Maybe it could be for the reasons you gave. Btw johnbeetee have you tried setting values for pegasusq depending on screen state to see if it helps improve battery life. I'm trying that right now but it would be helpful if someone else also could test that.

You can't possibly save power by tuning screen colour. If you want to save power on the screen you would need to set /sys/class /lcd/power_reduce to 1. Mind you that you would get a yellowish tint on the screen especially visible on white backgrounds which you could compensate by setting a higher blue value (cb) of 135.

Afaik there is no green in mdnie settings cause if it were there then gm would have implemented it along with the present 2 colours.
[Galaxy S II Q&A, Help & Troubleshooting] Oso Polar:
Yes, there is no green and it is not necessary because color balance is defined by proportion of each color and to change proportion two values out of 3 are sufficient. Green value is fixed but you can still make everything greener by reducing both red and blue values and vice versa.
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
did try something similar before, using other governors, and it's definitly worth looking into using pegasus. With other governors I had to be careful not to stifle the system to much, because like pikachu01 indicated, things will take longer to complete and will have an adverse effect (I noticed eg syncing not being completed in the time interval I determined for it, wifi taking a lot longer to connect, and even calender alarms not sounding), but maybe with pegasus it will behave different ; will have a look at it soon ; right now I'm testing eugene373's Cpu sleeper script which I have adapted for pegasus, disabling 2nd core when screen is off. This will take some battery cycles to compare, to be sure it's not placebo effect.
[Galaxy S II Q&A, Help & Troubleshooting] Many40:
Hi, You meant disabling 1st core, right? Regards
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
no..2nd core (CPU1) 1st core being CPU0 ( I know, it's a bit confusing sometimes :) )
[Galaxy S II Q&A, Help & Troubleshooting] Many40:
Thanks, looking forward to see your results.
[Galaxy S II Q&A, Help & Troubleshooting] yanagiba:
'button battery cell' a.k.a 'backup battery' galaxy s2 get rusty because overheat ?

hi guys, i want to ask about my galaxy s2 problem

previously i've asked the same question in

'[GUIDE] How to Dual Boot using the Siyah Kernel' thread, but thanks to many40 who gave me advise to ask here

this is the problem,

2 week ago when i woke up i found that suddenly my gs2 out of power / dead and can't be turned on at all, it was strange because before i sleep it still has about 25 % on battery.

it can't be charged so i went to the samsung service centre (ssc) ask 4 the solution.

the technician said because it was rooted device so the software/custom rom was the most possible thing that cause the overheat (around 70 celcius right after booting), create rust in 'button battery cell' as anandtech name it in his review of galaxy s2 international, section 'inside the sgs2' the 11th picture

and device refusing to be charged.

but it was wrong,after back to stock firmware another day, the problem stay the same ( i start thinking that she just guessing about custom rom causing that extreme overheat).

so in my next visit to service centre she said the most possible solution is that the whole machine/pcb (pict 4 in anandtech review) should be replaced by the new one.

as an addition, my gs2 last condition before i got the problem is criskelo v11.2 for 1st rom and resurrection remix V2.4 for 2nd rom with siyah 3.3.2.

after that I could return it to the stock firmware dxki2 GB 2.3.4 official for indonesia from sammobile.

please give me some advise to handle this problem.

thanks alot
[Galaxy S II Q&A, Help & Troubleshooting] CamoGeko:
Probably not helpful but did you try using another battery?
[Galaxy S II Q&A, Help & Troubleshooting] carlos67:
power_reduce on AOKP Rom

This particular topic has been very interesting reading :good:

I am on RR 2.5.1 (it's brilliant, smooth and stable with 96% deep sleep and great battery;)) which is an AOKP Rom so it doesn't have the "auto adjust screen power" setting that Sammy Rom's do. So, I have checked to see what the power_reduce is set to and it was set to "0". I then placed a script (echo 1 > /sys/class/lcd/panel/power_reduce) in my init.d folder and this setting is now "1" (script works fine). I haven't messed with the _cr values because I can't notice any discernable change in screen hue (no yellowness so to speak).

So, I guess it's just a case of seeing if it makes any difference to my already very good battery life when actively using the screen. I've always felt, particularly on this AOKP Rom, that although battery usage is tiny when screen off, when screen on it does drop more than can be expected. So, maybe, just maybe, this tweak will improve this.

Fingers crossed.

PS: For those of you looking for a second Rom if dual booting with Siyah and you already have a Sammy based Rom as your primary Rom, I can't recommend Resurection Remix highly enough. It's so good that I have now swapped Wanamlite with RR so that my daily Rom is now Resurection. Yep, Wanam (as good as it is) has been demoted to secondary Rom status.

PPS: Sorry for OT with the last bit but may help someone decide. :)
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
are you asking whether the service center people are right or wrong?

I think their diagnoses is probably correct, and if it is the backup-cell, then for some reason it has been overheated, by itself or a component nearby.

If that is the case, then it has become leaky, and this is causing the 'rust' due to the chemicals in the cell leaking. But this also means your motherboard is being affected bit by bit and maybe causing electrical shortage. This will cause considerable drain of the battery (even when turned off, if the circuit it affects is in near contact to the main power circuits), and this is probably what's happening. The high temperature it's reporting is coming from an on-battery chip, giving the battery temperature. Meaning the solution would be (if possible) changing the backup-cell and cleaning the circuit board and making sure there's no shortage (could be impossible, due to very miniaturized components and circuitry) or changing the motherboard as a whole.

Now, if you're asking what could have been the cause of the overheating?

That's very difficult to answer...it can be both ways:

it could have been a faulty component, that at some point deteriorated and caused the overheating, but there are possabilities that some very rare situation in the software (rom,kernel) could have produced it. Under normal conditions I would say If there are little to no reports of others using the same combination of software, and you haven't done anything extreme out of the ordinary, then it was likely to have been faulty component, but again, this is very hard to prove.

How to handle this? Chances are the service center already noted your situation and cell serial number, so you won't be able to get it back for regular service (making sure it's back to original rom and flash counter state) and telling them that it happenend during a very hot day, while you were playing a heavy loaded game or something....

Don't know if this was helpfull, but I hope you get it sorted out soon....(and hopefully to your satisfaction)
[Galaxy S II Q&A, Help & Troubleshooting] sayatsugu:
Hi, I was trying out your pegasus script and I get syntax errors for "fi;"

It say, "syntax error: unexpected "fi" (expecting "then")

I ran this using Script Manager tho, not in init.d

Could that have made a difference ?
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
hmm...can't find anything wrong here (exact same script content)

just runned it with terminal emulator, no errors...

Did you copy and paste the content? or typed it over?

I would expect the first...

then it must be Script manager not interpreting it right ??? don't know (i don't have/use Script manager)

...the only sense the error makes is that scriptmanager is missing the "then" clause ; maybe it expects it on a new line or witout ';'

maybe you can try this:

#!/system/bin/sh
(while [ 1 ]
do
AWAKE=`cat /sys/power/wait_for_fb_wake`
if [ $AWAKE = "awake" ]
then
sleep 2 && echo 0 > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_lock
AWAKE=""
fi

SLEEPING=`cat /sys/power/wait_for_fb_sleep`
if [ $SLEEPING = "sleeping" ]
then
sleep 2 && echo 1 > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_lock
SLEEPING=""
fi
done &)

(more or less clean code, c-convention)
[Galaxy S II Q&A, Help & Troubleshooting] sayatsugu:
I'll try it with the terminal emulator and update you again later =D
[Galaxy S II Q&A, Help & Troubleshooting] yanagiba:
i did.but the problem still exist, nothing changed.

what a great analysis mate, i'm curious with several point, so i bold a few things

1.if the back up battery become leaky,i think it's my bad luck :crying:

2.do you mean that inside the back up battery there is chip to manage the temperature threshold, and when the cell damaged,electricity from the 1650 Mah battery is out of control?

3.almost similiar with no.1, maybe i get the faulty, weak back up battery...so do you think we can hope that it is covered by warranty?

4.i think my device has been reported as a rooted device by the technician:(

actually i really want to write whole story from the beginning so that the problem is clear, but i think it could be very long, so i decide to use attachment.
[Galaxy S II Q&A, Help & Troubleshooting] lauriv:
GT-9100M does not charge in off mode with v3.3.2

Lauri
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
quick reply to your points:

1. like I said: the question is why ; was it faulty or some other component caused it to completely discharge or overcharge (more likely) and become leaky (no simple way to tell) ; the backup-cell is a gas-tight package, but can become leak by overheating. looking at the pictures you refered to, I can't see any component nearby, that can cause heat, so it most probably was caused by some overcharge (again difficult to prove)

2. no the chip reporting temperature is in the main battery ; the fact that it reports such high temperatures, indicates that there's a shortage somewhere, which makes the main battery heat up (discharge) quickly ; the chip being there to monitor such events (Li-ion battery are known to burn violently when overheated and even can explode, so it's also a safety feature)

3. if they didn't know any better of the rooting, they would have assumed that was the case and not given it another thought ; after the fact it's hard to prove the backup-cell was faulty (or other component) ; samsung service centers sometimes adhere very strictly to their policies once they have a slight indication of proof

4. from what i gather from your story, I'm afraid so

Sadly enough, knowing it now, after the fact, you would have been better off buying a new battery at once and get it back to it's original state and submitting it as waranty-service ( but that is in hind-sight). The best you can hope for now is for them to try and help you and at least give you some discount. So I would give it a try, and send them a letter of protest ; you never know, it might help

Really wish I could have given you an effective way to prove your right, but technically it's almost impossible, because of so many things (variables) that could have been the cause (maybe some forensic scientist would be able to prove it, but that would cost more than 10 new phones, so that's not practical)
[Galaxy S II Q&A, Help & Troubleshooting] sayatsugu:
johnbeetee, you're right. The script executed, I guess Script manager is the one at fault

Thanks for the script, will be testing it out via init.d instead !
[Galaxy S II Q&A, Help & Troubleshooting] robertobsc:
Hi John and guys,

I'm very sorry, I have to disappoint you guys and say sorry.

When I published my post about changing internal voltages I was so sure that I had made a super discovery. Applying internal voltages of phenomenal in Siyah. Now I know that almost every of that's tweaks are completely useless. And I'll tell why.

I'm developing a little for siyah now. In fact I'll submit my sources to gokhan tomorrow. One of my goals is to be able to undervolt gpu a little more. In that moment I got what was a regulator about.

A regulator is a constraint. It doesn't change any voltage at all. When we change it he just allows the "driver" of that group changes it voltages between the min_volt / max_volt specified on regulator.

Example. I want to undervolt gpu to 750. But the gpu is "ruled" by a regulator. If I want to undervolt I must change gpu voltages and also change the min_volt of the regulator to 750. When I change it I tell that the gpu can be undervolted to 750, but I didn't undervolted in that moment. Got it?

So, the great internal voltages made in regulator of phenomenal are useless.

I'll update my post with that explanation. So the only thing that really do work in my post is the cpu asv voltages.

So, that's all folks. We could try undervolting gpu less then 800 by changing it file + changing it's min_volt regulator with kmemhelper. But I think you guys will not need to try. Think an update is coming nearby.
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
Hi roberto,

first of all, no need to apologize at all

no harm done, on the contrary, the whole fun of it all is to discover, find, try, confirming or rejecting and learning along the way.

To be honest, the whole concept seemed logical to me too, that's why I decided to try it and see it's impact....

The fact that the values were constraints (bounderies), was already clear to me (going through the source codes in GM's and fenomeno83's github).

And clearly these can be changed using kmemhelper.

So the only conclusion I can deduce right now is that the driver doesn't look at these values, and uses it's own hardcoded ones (not exposed) or that these values are read and copied at the very first beginning of the system start and cannot be changed dynamically during run-time.And not being familiar with the hardware components and how they are wired, maybe it's even hard-wired to a certain level and not configurable at all ; the code being present in general for use with other systemboards/displays? I don't know....

The fact remains that it was fun trying, and dicovering that trying to use it in this way is of no use.

There still remains a lot to investigate and uncover, so ....just keep on going, and have fun!
[Galaxy S II Q&A, Help & Troubleshooting] yanagiba:
i really appreciate with your help and also your explanation john:good:.

i will just try to make the letter and hoping the best result, eventhough he said that it will took about 1 month from the head office.

and i hope nobody here get the problem like me and also make sure that you always doing something carefully to your expensive phone, the second, keep away from the service centre and don't forget to return it to stock when you have to go there.:D

thanks
[Galaxy S II Q&A, Help & Troubleshooting] vertrag:
#!/system/bin/sh

(while [ 1 ];
do
AWAKE=`cat /sys/power/wait_for_fb_wake`;
if [ $AWAKE = "awake" ]; then
sleep 2 && echo 0 > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_lock;
AWAKE=;
fi;

SLEEPING=`cat /sys/power/wait_for_fb_sleep`;
if [ $SLEEPING = "sleeping" ]; then
sleep 2 && echo 1 > /sys/devices/system/cpu/cpufreq/pegasusq/hotplug_lock;
SLEEPING=;
fi;
done &);

Hi johnbetee just want to get your confirmation if this script using infinite loop to check 'wait_for_fb_sleep' it will trigger a wakelock, isnt it?

I mean while scr off with deep sleep and 2nd core off, does ur script trigger wakelock? sorry for noob question does infinite loop need cpu cycle to run?

gonna try this hehe ^^
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
Ahhhh...very good!...that was my initial reaction too, until pikachu01 pointed out to me that wait_for_fb_wake and wait_for_fb_sleep funcionalities are that pauses the script until the event occurs (wake or sleep) (event triggers, so to speak..) and i have checked that and it's totally correct ; once it checks for the occurence it will pause until it happens and then it will resume, so the majority of the time the script does absolutely nothing but wait....(meaning answer is : no wakelock problem).

A mechanism you can use to put al sorts of things in between the if statement, which you want done when the device awaken or goes to sleep ; only limited by your imagination :)

---------------------

As I'm already busy typing, I can present my conclusions about this tweak (as I have been testing it):

this tweak is not a power saver on it's own ; it depends on how aggresive your settings are performance-wise or battery-wise (governors,min max freq, etc)

If you are using very performance oriented settings (lots of dual-coring), then this aggresive dual-coring will be contained when screen is off, so then you'll notice more savings.

If you are using very battery oriented settings (like me) which allow some dual-coring when needed, but will keep it to a minimum, then when screen is off, there's by default relatively little dual-coring taking place, so your savings will be less noticable.

But as this script uses very little resource, and does no harm in any way, I'll keep on using it, for the event I shift my settings a bit in the future....
[Galaxy S II Q&A, Help & Troubleshooting] vertrag:
Okay i get it thanks :D i use very batt oriented but im not sure pegq will turn off 2nd core while scr off imo.. i've found ur post and would like to test it hehe..