yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] ffolkes:
Empirical testing has revealed these slice divisions, which are not where I thought they'd be. Can anyone confirm they are correct? I'm not sure if it's something wonky in my kernel, and I'm about to fall asleep.

First slice is <=200 (covering 200MHz and below)

Second slice is <800 (covering 300-700MHz)

Third slice is <1600 (covering 800-1500MHz)

Fourth slice is >=1600 (covering 1600MHz and beyond)

This was confirmed by setting the slices to 850/800/750/700 and then stepping through them while checking /sys/devices/system/abb/arm/abb_info for each one, and seeing where they changed.
[Galaxy S III Original Android Development] rulala:
alpha22.3 (init.d support) doesn't work with my some test.....

Right ?

thank you.
[Galaxy S III Original Android Development] sacapo:
Hi there!

I wonder if you guys could share your settings in order to improve battery life a bit (oc/uv)

Mine are although I don't get very good battery life.

Kernel flies by the way, thanks for your hard work

Governor :sio

Enviado desde vete tu a saber
[Galaxy S III Original Android Development] JYJY:
There's a thread regarding undervolting in the general section.
[Galaxy S III Original Android Development] s3ct0r:
How do you figure?

On Average I get 5 hours of screen on time during a full day.. That's pretty good :)
[Galaxy S III Original Android Development] robogo1982:
I can't wait anymore :D will upgrade to JB and flash this ASAP. :)
[Galaxy S III Original Android Development] fylim:
This is my UV settings in init.d. Running cool.

#! 1400 1400 1350 1288 1125 1100 1075 1025 1000 950 900 875 850 825 775 750 725

echo "1400 1400 1350 1288 1125 1100 1075 1025 1000 950 900 875 850 825 775 750 725 " > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
[Galaxy S III Original Android Development] plutozz:
Hello, I have a minor bug to report concerning sound output from stock FM Radio and any Music player. For example, if one use stock FM radio app then switch to Music player there won't be any sound unless the phone is rebooted. This doesn't happen with wanam's DLI8 insecure kernel. So I assume this minor bug comes from Perseus ( and happen to Siyah's 1.6RC2 as well ). Thanks.
[Galaxy S III Original Android Development] AndreiLux:
It may have to do with Voodoo, I'll talk with Gökhan about it.
[Galaxy S III Original Android Development] codo2003:
Thanks for the kernel. When I installed it the wifi is not connceting at all. It keeps trying but without luck. 3G is working. Everything else is working perfect.

Any idea to solve this problem. I am on Omega JB DLIB ROM.

Thanks for any help.
[Galaxy S III Original Android Development] gee2012:
Does this kernel support boot animation?
[Galaxy S III Original Android Development] Chillz88:
I know the ram has been increased.. so the stock video app doesnt work with this kernel ..right?
[Galaxy S III Original Android Development] grafwasserrutsche:
Can somebody please nake a fkashable zip of this kernel to flash in cwm?
[Galaxy S III Original Android Development] diego9016:
Take a look at this
[Galaxy S III Original Android Development] AndreiLux:
Fine dammit here you go you lazy CWM *****. I hope I won't hear about this again. :silly:
[Galaxy S III Original Android Development] robogo1982:
Finally moved to JB and am currently using Perseus. All is well so far :)
[Galaxy S III Original Android Development] brenogbi:
You should consider to make a .zip with this great kernel
[Galaxy S III Original Android Development] garyd9:
Can you make a nandroid compatible version of this? ;)

(I'm kidding, of course)
[Galaxy S III Original Android Development] beaver2233:
Lol.... Some people, never gonna learn. Anyway, enjoying your kernel, cheers.
[Galaxy S III Original Android Development] mmse88:
Thanks for your information mate.

I will take a try on this kernel, due Siyah has some conflicts with V27 :(
[Galaxy S III Original Android Development] AndreiLux:
Sorry, but I'll do it in the next release, I didn't want it in in this one as I didn't like the interfaces and want to improve a bit on it, and LCDFREQ took me more time to test.

Anyway, update out.
[Galaxy S III Original Android Development] rickoslyder:
Yep, that should be it.
[Galaxy S III Original Android Development] MuertoKo:
According to OP it's different, second slice is 300-800, third 900-1400, fourth 1500+

Enviado desde mi GT-I9300 usando Tapatalk 2

---------- Post added at 07:09 PM ---------- Previous post was at 07:07 PM ----------

Typo, third 900-1600, fourth 1700+

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] AndreiLux:
No... see MuertoKo's comment above.

I did make a typo on the last slice in the OP which I fixed now but the labels in STweaks are correct: "CPU: Divided into four slices, with frequency ranges of 200], 800], 1600] and ]1600 Mhz."

Are people not familar with [x (inclusive) and ]x (exclusive) notation?

In any case, you can change the slice delimiters per sysfs if you wish so.
[Galaxy S III Original Android Development] DidyMond:
Hello to all.

I'm having problems with the new kernel version (Perseus alpha 36.2) and the notification LED. Without touching any settings in STweaks (compared to the alpha version 35), the LED light intensity seems to be less than before. Is a problem only mine?
[Galaxy S III Original Android Development] -PM-:
Me too. I have the same issue.
[Galaxy S III Original Android Development] mnickkk:
I found values, which are pretty stable for me - tested every on them at Antutu Benchmark - stability test. What else could I do to play with them? Lowering Slice 2 body voltage will result in high leakage, but due to lowering voltage i should get lower power consumption for 200-800 freqs?
[Galaxy S III Original Android Development] pistoke:
What ASV do you have?
[Galaxy S III Original Android Development] mnickkk:
ASV5
[Galaxy S III Original Android Development] shanky887614:
where is the deal with title? cant find that version.

nice work on this awsome kernel
[Galaxy S III Original Android Development] mattiadj:
Can anyone tell me the best way to tweak autobrightness? I don't understand well the new options added in latest kernel and how can I improve and use these.

Any explanation?

From universe with my gs3
[Galaxy S III Original Android Development] habylab:
The top two values. Set them to what you want, same value.

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] ManDone.vRs:
CRT off animation not supported :(
[Galaxy S III Original Android Development] mattiadj:
Not problem here about crt

From universe with my gs3
[Galaxy S III Original Android Development] Obagleyfreer:
Yesterday installed Perseus 36.2 and have been having random shut downs quite a lot.

My phone has always been rock stable on previous versions of Perseus but this latest one isn't stable at all.

I didn't make any adjustments in STweaks, just flashed the update and kept all my old settings.

Anyone else experiencing loss of stability?
[Galaxy S III Original Android Development] fjfcb:
Since i flashed perseus kernel i'm experiencing some Sleep of Death (I turn my screen off and it never comes back to life and i have to reboot the phone)
[Galaxy S III Original Android Development] ManDone.vRs:
very quick drain battery .... i ll keep siyah ... :good:
[Galaxy S III Original Android Development] STAticKY:
Does anybody have an opinion on this before i give it a try???

Sent from my portable powerhouse
[Galaxy S III Original Android Development] miwanr:
Yeah, anyone knows? How to lower the brightness lower than original setting?
[Galaxy S III Original Android Development] STAticKY:
Use the new digital brightness reduction feature. Read the OP

Sent from my portable powerhouse
[Galaxy S III Original Android Development] miwanr:
Do you mean by installing app Custom Auto Brightness?
[Galaxy S III Original Android Development] STAticKY:
No i mean by using stweaks with perseus kernel. There are settings for digital brightness reduction that were introduced in the latest updates... it works via mDNIe. You can set the values at which it takes over from the normal brightness control along with a few other tunables. Like i said... read the OP

EDIT: if you are having trouble understanding it then read..read..read. Look up the terminoligies of everything if you have to....

Only once you understand what changes you are making and how they affect your device you can set most kernels up right... its up to you...

Sent from my portable powerhouse
[Galaxy S III Original Android Development] miwanr:
This kernel always remove Messaging shortcut at my homescreen.
[Galaxy S III Original Android Development] STAticKY:
I fail to see how the kernel could be doing this. What made you come to this conclusion?

Sent from my portable powerhouse
[Galaxy S III Original Android Development] miwanr:
I don't know, but my Messaging shortcut @ my homescreen always disappear after flashing custom kernel.
[Galaxy S III Original Android Development] STAticKY:
Its more likley that its a problem with your rom than anything else if it happens with "every" kernel you flash and not just this one...

Sent from my portable powerhouse
[Galaxy S III Original Android Development] miwanr:
Yeah maybe, last kernel I install is Adam Kernel, it remove the shortcut too after kernel installed then reboot. I'm not sure it is ROM related because I'm on Official 4.1.2 ROM.
[Galaxy S III Original Android Development] STAticKY:
I think you will find if you do a nandroid, wipe everything then install the rom again then flash kernel then it wont happen, eliminating the kernel from the equasion

Sent from my portable powerhouse

---------- Post added at 03:10 PM ---------- Previous post was at 03:08 PM ----------

Any thoughts on this [MENTION=4167023]AndreiLux[/MENTION] ?? Does anybody know someone that has tried this before?

Sent from my portable powerhouse
[Galaxy S III Original Android Development] davtse:
Im on temaseks kernel, but since its thanks to andreilux that we have ABB to play with, i thought id share my observstions in this thread as well. something I noticed when fooling around with ABB settings. Too big an RBB might negate any potential battery savings. I was at - 400mv RBB for 200mhz( I'm an asv 07) and it appeared to drain the battery slightly faster than before. Right now I'm trying out a much smaller value RBB with an extreme under volt to see if there's a difference. Will report when I can confirm my findings.
[Galaxy S III Original Android Development] RohanAJoshi:
That's what Andrei said, too much will give negative effect and too low also will give negative effect.

So we need to balance it.
[Galaxy S III Original Android Development] RedDevils88:
I tried to set the zram size yo 512mb but after I restart my phone, it will be reset to 200mb once again. How do i set it on boot? Thanks
[Galaxy S III Original Android Development] STAticKY:
By using either stweaks or rlorange's swap control app

Sent from my portable powerhouse
[Galaxy S III Original Android Development] AndroidGX:
Small message to let you guys know that I'am getting the best battery life ever with this 36.2 than any older previous perseus version.

Good job Andreilux :good:
[Galaxy S III Original Android Development] Kemby13:
Hmm, how about some details? You cant just say that and "walk away" :)

Btw, i had better battery life with perseus 35 compared to 36, although i did change the scheduler to deadline and increased swap to 400 instead of 200...
[Galaxy S III Original Android Development] Kaydin:
I have ASV 3. Here are my settings. Is this right? Any corrections I can make?
[Galaxy S III Original Android Development] ffolkes:
So then I guess there is something wrong for me. I am able compensate for it by setting arm_slice_3_freq to 900000 and arm_slice_4_freq to 1704000, then I get the values described by MuertoKo and you. It's almost like somewhere there is a < instead of a <=

As always, I have spent hours on this before asking for your advice. I don't see anything that would be causing me to be off by 1 frequency step. I have 4 extra steps in my kernel, but since I am only off by 1, I don't think that has anything to do with it. I have also scaled the L changes in cpufreq-4x12.c to match my actual frequencies. Thank you very much for any suggestions.
[Galaxy S III Original Android Development] pistoke:
If you have under or over clocked/volted there may be stability problems, because there's totally new feature(ABB) which affects to it. You should go back to default settings or check your settings. But, this is my opinion, which may not be the whole truth. ;)
[Galaxy S III Original Android Development] AndreiLux:
Are you sure? Because according to this guy it's horrible horrible battery life:

I guess I'm noob!

I checked the code again and you're probably right:

slice = abb_slices[target] + slice_size - 1;

do {
ret_volt = slice->volt.value;
} while ( (slice > abb_slices[target]) &&
(target_freq <[COLOR="Red"]=[/COLOR] (--slice)->freq.value) );

return ret_volt;

Should produce the correct lookup for the slices, check it yourself. Correct me if this is a red herring.

I'll update a hotfix version later in the afternoon.
[Galaxy S III Original Android Development] davtse:
ROFL. Different preference I guess? But having gone through almost every kernel available to AOSP and Sammy roms, I have this to say. If I'm on AOSP, I'd be on temasek, If i were on Sammy, I'd be on Perseus. :good:
[Galaxy S III Original Android Development] MuertoKo:
Finally looks like your effort was worth as you were right :D I just searchg through the thread, not checked the slider values on my device, so as you said you did your testings you'd probably be right! So we were setting something wrong in the border values then :D (Lucky I use same body voltage value for now at slide 2 3 4 but anyway, thanks for exploring deep in Andrei's work
[Galaxy S III Original Android Development] papakaliati:
Can we edit the error ourselfs? Where is that part located?
[Galaxy S III Original Android Development] ffolkes:
Thanks! I have confirmed the slices now properly scale.
[Galaxy S III Original Android Development] pat357:
No, I guess you have to lower the body voltage to be able to lower the gate voltage.
[Galaxy S III Original Android Development] ffolkes:
No, you cannot as it is in the code and would need to be compiled.
[Galaxy S III Original Android Development] AndreiLux:
You can fix it by manually increasing the frequency walls by +1.

But I'm uploading 36.3 now:

36.3: (Recommended upgrade!)

- Fixed slice lookup issue on ABB: It's recommended you put your slices back to default before flashing if you changed them to borderline stability values.

I'm gonna upgrade the Note 2 folks in a few hours.
[Galaxy S III Original Android Development] AndroidGX:
Yes, definitely (according to my second cycle) :)

Moreover, I precise I let everything stock (except calibrated screen + some EQ sound) :good:
[Galaxy S III Original Android Development] pat357:
Remember that the factory reset was not required to resolve to bootloop.

It would have cost me less than 2min to resolve the bootloop from ADB-recovery or from recovery using the Aroma fileman, without loosing any data.

If you're not familiar with ADB, I strongly recommend to learn the basics.

Manuals/sticky's/quick starts are here available on XDA.
[Galaxy S III Original Android Development] alberber:
I can't change the speaker settings in audio tab. Well, when I do it, it applies the changes but after a few seconds it sounds like stock settings again. Why is this happening? :(

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] pistoke:
In the version 36.2 slices are like ffolkes says:

First slice is <=200 (covering 200MHz and below)

Second slice is <800 (covering 300-700MHz)

Third slice is <1600 (covering 800-1500MHz)

Fourth slice is >=1600 (covering 1600MHz and beyond)

Those should be like earlier said and it's fixed in the version 36.3.

First slice is <=200 (covering 200MHz and below)

Second slice is <=800 (covering just above 200MHz-800MHz)

Third slice is <=1600 (covering just above 800-1600MHz)

Fourth slice is >1600 (covering just above 1600MHz and beyond)

When flashing to the 36.3, I should test my undervolting stability again at 800MHz. And if I use 1600MHz that should be tested again too. Did I understand this right?
[Galaxy S III Original Android Development] shr95:
hello guys! this is the best kernel i have ever used! been using 33.2 for over a month had excellent battery life with over 4 hours of screen time every time with more than a day standby.. just updated to 36 couple days back and notice a dip in battery life .. I didnt make any changes to the new ABB feature or anything else other than sound tweaks, :confused: Any ideas?

Thanks a lot AndreiLux for this kernel! :good::good:
[Galaxy S III Original Android Development] habylab:
Should be the same, really. Give it another day, and report back!

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] pistoke:
-500 bias looks too low to mee, but if everything is working then it have to be okay. ;) Lower body bias is less power leakage but slower gate switches.

And yes, you should be able to have lower gate voltage(lower power consumption) by lowering body voltages. Anyway, too much is too much. It stops working when you're too low.

I have used this guide http://xdaforums.com/showthread.php?t=2072087 to test my undervolting. I used StabilityTest and STweaks instead of SetCPU.

There are few things, which I've been thinking of. After I have found good voltages, should I try lower body voltage(and rise body bias) to achieve faster gate switching or should I try higher body voltage to decrease power leakage? How easily I can notice power leakage in this case? :confused:
[Galaxy S III Original Android Development] Handeman707:
Someboy has a daily default.profile with good performance settings for daily use for me?
[Galaxy S III Original Android Development] pat357:
Wireless recharging ?? Are you talking about the same gt-i9300 as I have ?
[Galaxy S III Original Android Development] TheMrcool212:
You can refer to this thread. Or just install Speedmod kernel
[Galaxy S III Original Android Development] AndreiLux:
I have a general question here, it doesn't really have to do anything with the kernel.

I've monitored this over the last several weeks: Every time the battery goes below 33-30% it causes a, what I believe is userspace-origined wakelock/wakeup/alarm trigger. This makes the device wake up in a high frequency pattern obliterating battery life, until you actually wake the device up after which the behaviour stops and doesn't get triggered again below 30%. Basically you get massive drain from 33% down to possibly zero if you leave the device just idle and don't touch it.

This is idiotically similar to the fuelgauge bug we had on the S2 but this time I can't seem to pin-point the cause. If any of you have this behaviour or noticed something similar please report back.
[Galaxy S III Original Android Development] shr95:
i did have it! was on 33.2 for long where i wud get 4hours of screen time by 30% with over a day standby and it wud drain faster after that! just updated to 36 couple days back and theres a drain starting at 100 itself :( could leave it settle for a day or 2 more!
[Galaxy S III Original Android Development] cba1986:
I use aroma File manager. But when i delete .perseus folder the phone stuck on Samsung logo. I use this to get rid of the bootloop:
[Galaxy S III Original Android Development] FD10:
Led colors are ok again
[Galaxy S III Original Android Development] pat357:
This doesn't seem a valid test : the reason for the bootloop is not because the 1 core/200MHz config is unstable, but because your "Max 200 MHz" limiting itself.

The phone bootloops because your blocking the governer to do its job (go to higher freqs) ; upon booting, the phone is normally at much higher freqs. (even 1.4 - 1.8).

The "200MHz/single core limitation" doesn't allow the phone to boot properly : it just needs more power (MHz's) to boot.

Your testing procedure influences the final result, what makes it a bad testing procedure.

---------- Post added at 08:04 PM ---------- Previous post was at 07:46 PM ----------

Why did you buy a quadcore phone for ? :p

A mono-core phone would have been much less expensive :laugh: ;)
[Galaxy S III Original Android Development] alberber:
If I understood correctly what you said, this happens to me too. It's really annoying, I didn't know that it also happens to other people. My phone usually lose about 10 % (from 30-20 or 25-15 %) of battery in less than an hour in stand by, and then it goes back to normal (1% per 2 hours). The difference is huge.

So in fact is like our phone had only a 90 % of battery to use, right?

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] yogosun:
I was reading this thread because I was bored. I don't have this kernel, but jet I wanted to thank AndreiLux for his dedication! My compliment
[Galaxy S III Original Android Development] pat357:
For the "high" frequencies it seems OK to me, but for the lower, you're better of with RBB (negative = reversed body bias) than FBB.

RBB on lower frqs will save power when CPU is idle.
[Galaxy S III Original Android Development] alberber:
Please, could anyone check this? Just press volume up button with stock configuration, then increase speaker volume with the two sliders and press volume up button again, you'll see the difference. Wait a few seconds and press it again? Does it still sounds louder?

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] AndreiLux:
That's a bunch of nonsense. The phone can boot at whatever frequency, it just takes longer. If it crashes due to undervolting then it's due to undervolting and nothing else.

Yes. It almost exclusively happens around the 33-30% mark when this behaviour gets triggered. I'm suspecting some bug in some application or firmware that monitors the battery levels or something but I don't have a clue yet what it is. It's definitely a scheduled alarm/wake-up source and not a persistent wakelock or similar. The battery isn't only 90%: it just starts draining during that period until you turn the screen on again. If you're actively using the phone over that threshold then it doesn't happen.
[Galaxy S III Original Android Development] Erahgon:
I follow a similar procedure.

After finding stable undervolt voltages, I set the settings in the ABB tab to match the stock bias as far as possible, keeping in mind to let the lowest frequencies have a greater RBB (negative bias), for greater power efficiency.

[MENTION=4167023]AndreiLux[/MENTION] : I do the same for the GPU using Nenamark2 to painstakingly test to get the most FPS at each frequency step.

In my quest, I found that the frequencies 350 MHz and 440 MHz (as far as my testing goes, could be also for higher frequencies), doesn't seem to register the voltage changes. Either that or my GPU works remarkably well at 600mV at 350+ MHz, when the lower limit for 250 MHz is 800mV.

Could be an error on my end too, so just asking you (and others) to check please!

Sent from the present, which is now in the past.
[Galaxy S III Original Android Development] t4d73:
For what it's worth it happens to me too on the note.
[Galaxy S III Original Android Development] Erahgon:
I have noticed a similar behavior where I see my battery drain pretty fast below 20% or so (that's when I notice rather). I don't notice anything unusual in the "partial wakelocks" tab in BBS, could it be a kernel wakelock?

Sent from the present, which is now in the past.
[Galaxy S III Original Android Development] jeebspawnshop:
Just taking a stab in the dark here, but isn't it approximately around that level that the Samsung Battery Saving thingy kicks in (assuming you have it enabled)?

Perhaps they botched some part of the code that monitors that, and perhaps it executes & monitors regardless of whether you have it enabled or not.

:confused: