yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] mamba720027:
2 or 3 pages back I Posted last set of screenshot of battery on normal light and heavy usage with the above settings mention which was about 16hours and over 7hours screen time. I use my phone aggressively.

The only thing I forgot to mention was that I had change under "cpu scaleing menu" where it have "frequency for responsiveness" to 300mhz and "frequency for fast down" 700mhz, "flexrate max freq" 1000mhz. Not sure if that made a difference cause my aim was to just make 3 cores go offline faster and stay in single core most times and only use those core when really needed.

So when I look at "cpu spy" I notice the CPU scaled mostly in 200mhz,300mhz,1000mhz and barely touched all the others in between including the 1700mhz. While maintaining optimal performance by utilizing the cores when more load was applied.

My conclusion was that with a few tweaks the cpu does not necessarily need to use the highest frequencys to complete a task although set at high frequency 200-1700mhz because of the 3 other cores helping to reduce the load and complete task.

Edit: the 2x animation thing is just my preference,cause I like how smooth it makes apps look opening and closing.:p

Sent from my GT-I9300
[Galaxy S III Original Android Development] rugolt:
Exynos Abuse says phone is still exploitable. Is it wrong?
[Galaxy S III Original Android Development] Frag1le:
Yes, this was already answered a few pages back. You'll probably get an error if you try to fix the exploit with the app.
[Galaxy S III Original Android Development] Drizzy xS:
Hey could you post a link to the s tweaks settings that you use please as I've looked a few pages back but I can't seem to find them. Cheers :)
[Galaxy S III Original Android Development] mamba720027:
Rom - Omega V35

Kernel - Perseus v29.2

launcher - Atom Launcher

Stweaks Settings

CPU* - 200MHZ/1700MHZ* UV -100 from 200-1400mhz and -50 from 1500-1704mhz

CPU Scaling* - frequency for responsiveness 300, Frequency for fast-down 700mhz, Flexrate Max Freq 1000mhz

CPU Hotplug - Hotplug freq from3 cores to online 1400mhz, runqueue depth from 3 cores to online 275,runqueue depth from 4 cores to offline 175, cpu online load bias count 1,cpu online bias up threshold 85%, cpu online bias down threshold 50%

GPU - 160mhz/440mhz UV -75

I/O - Both internal and external scheduler "Row"

settings/developer options - transition animation scale 2x

So thats all the settings i have currently.

Sent from my GT-I9300
[Galaxy S III Original Android Development] MuertoKo:
Got a random reboot, last_kmsg sent via PM.

Hope it helps and you can share what happened!
[Galaxy S III Original Android Development] Schmiddi1008:
Are this Settings stable?
[Galaxy S III Original Android Development] hgyula87:
I setted this and it was epic with anono v19 rom. Lost 14% battery in two hour with 92% screen on and heavy usage with whatsapp and camera.. wifi on, auto sync off.
[Galaxy S III Original Android Development] Schmiddi1008:
Hehe nice to hear;) - How can i set this UV exactly? - Can Only 25-50-100..... Maybe someone can post screens for me? :D

Cheers
[Galaxy S III Original Android Development] erto90:
And is fast or you lose smoothness?
[Galaxy S III Original Android Development] mamba720027:
It is stable for me but it can get unstable if UV too much and your phone canot handle it and just reboot.

Goes like this -25...-25...-25...-25. Don't do a full -100 if you don't know your phone UV limit,just go -25 and let it run approximately an hour to see if operates stable,if it does go another -25 etc. Also do not check "set on boot" in Stweaks when doing any UV untill you run a full day and know your settings is stable.

Also if you're unfamiliar with UV please don't try doing it and use the search and read alot before practicing anything.

Sent from my GT-I9300
[Galaxy S III Original Android Development] Schmiddi1008:
I want to take your settings :). But i dont know how i set all the UVs in STweaks. Can i use a cfg file or something? - Maybe you can post Screens for me so i can copy & paste it :D
[Galaxy S III Original Android Development] behemot24:
I can't believe how much the battery consumption improved since I flashed this kernel. And the phone speed is still great. I'm using 1,6 GHz for the CPU. Thank you, Andrei!
[Galaxy S III Original Android Development] hgyula87:
Fast, smooth, no lags, i wait when the battery left only 1-3% then make some screens and post it.

Already try lot of roms and kernels but this combination is awesome.
[Galaxy S III Original Android Development] hgyula87:
A quick screen.. tomorrow i post few more with stats when i use "normaly" the phone.

The "ébrenlét" is the screen awake.. tomorrow i change the language ;)
[Galaxy S III Original Android Development] fylim:
Anyone encounter phone hang after full overnight charge. I have encountered this for 3 consecutive nights. Will normally hang/ see big battery icon on screen or Galaxy SIII startup image. I am on Wanamlite 5.2 ROM

Tq
[Galaxy S III Original Android Development] bl4ckdr4gon:
Nope but I experienced something similar, after rebooting, mine got stuck on the Samsung Galaxy S3 I9300 screen. Had to reflash WanamLite then Perseus kernel. Problem is gone, for now. Couldn't determine the cause though.

Sent from my Wanam-ish Galaxy S III
[Galaxy S III Original Android Development] mamba720027:
Make sure to check with rootexplorer or any file manager that system/etc/init.d does not have any cpu configuration scripts. If it does then it should be deleted before flashing custom kernel.

Sent from my GT-I9300
[Galaxy S III Original Android Development] bl4ckdr4gon:
Sorry for the noobish question, do I delete the init.d file itself?

Edit: Just checked, mine contains S97WanamLite file.

Many thanks.

Sent from my Wanam-ish Galaxy S III
[Galaxy S III Original Android Development] mamba720027:
No not the init.d file itself,just the script s97wanamlite then reboot.

Sent from my GT-I9300
[Galaxy S III Original Android Development] 0asis:
As always with the UV I have some questions: for the CPU by-100 you mean -100000 right ? And for the GPU it's really-75 because it's in mV right ?

Envoyé depuis mon GT-I9300
[Galaxy S III Original Android Development] mamba720027:
Correct.

Setting/developer options is from within the ROM not part of Stweaks.

Sent from my GT-I9300
[Galaxy S III Original Android Development] 0asis:
Thanks. Shame on me you got the developer thing before that I realised that was not in Stweaks :D

Envoyé depuis mon GT-I9300
[Galaxy S III Original Android Development] mamba720027:
Lolz its my mistake cause of how its written in combination with Stweaks setup.

Merry Christmas :)

Sent from my GT-I9300
[Galaxy S III Original Android Development] bl4ckdr4gon:
Merry Christmas mamba720027, very fast responses to those needing help. Enjoy the holidays. :)

Sent from my Wanam-ish Galaxy S III
[Galaxy S III Original Android Development] 0asis:
Totally agree! Merry Christmas too. :)

Envoyé depuis mon GT-I9300
[Galaxy S III Original Android Development] habylab:
Any chance of adding touch wake to this? It was wonderful on my galaxy s. Just switched the screen off and held a wake lock for how ever many seconds the user sets. Could be useful?

I'm using screebl at the moment instead of stay awake, working well!
[Galaxy S III Original Android Development] Infy_AsiX:
Hotplug frequency X to online, above 1000 locks cpu at 1000 when battery is 43°C and higher when I tested. It won't clock down? I set it at 1000 for all cpus.

I find frequency for fast down at 300 lets the frequency reflect load better and in effect a higher percentage of the frequency is utilised. Rather than seemingly sitting at 1400 more and only utilising ~50%. The free app perfmon I find highly useful for testing and showing this in real time.

Bias threshold down at 100% works fine for me! Drops cpu as fast as possible and can't really say I feel much difference in performance. I think bias threshold up increased, increases rate of hotplug up which goes against how you're trying to save power?

With a plethora of aggressive power saving tweaks I can get my demanding live wallpapers running on single core after waking compared to staying on quad when default. No real feel of extra lag and you get the eye candy without the massive power costs :)

Ok so these are extreme values but I'm just a noob reading descriptions and applying what little basic knowledge I have on how CPUs scale trying to maximise power savings whilst considering usability. Please help me note and kindly help me along in the right direction if these are in fact stupid settings to use. :)

?????? Galaxy S3 ??????
[Galaxy S III Original Android Development] iridaki:
There is no such thing as "stupid settings"... :confused:

You need to experiment and find out which work best for you.

These may be too aggressive for you, while at the same time optimal for someone else.

There has been a long discussion in this thread regarding STweaks settings, so all the help you need is already here.

You just need to *drum-roll* search and read. ;)

Merry Christmas!
[Galaxy S III Original Android Development] mamba720027:
I had the same concept in mind when I start useing the gs3 and as my first quadcore device but I found out different threw real life usage and slightly adjusting settings and getting to know the device hardware components such as the CPU.

Saying single core saves more energy than 4 cores is not true because the load that 4 cores can complete and time it takes,the single core will have to do it in a higher frequency and take More time thus useing more power to complete the same task. Also why have all the CPU muscle if it will never be used.

I only slightly fine tune the CPU to work how I feel it should for me and so far I have notice a battery performance increase rather than a decrease. The figures u mention,I have no idea if they would impact CPU performance negatively or positively but you're free to try them and see how it works for you.

Sent from my GT-I9300
[Galaxy S III Original Android Development] giammo:
Maybe I found a bug in 29.2. Earphones not working after using FM radio. This not happens with latest siaya kernel
[Galaxy S III Original Android Development] Tenacious:
Merry Christmas guys and gals.

All the best to you and your family's.
[Galaxy S III Original Android Development] Fearxpc:
Hey,

after flashing 29.2 yesterday i recognised @evening that when i wake up my phone i had often a blue screen for about ~0,5sec and then the normal screen. Someone got this, too? (it was not everytime)
[Galaxy S III Original Android Development] :
I remember seeing the blue screen once but have not seen it repeat.

Sent from GT-I9300
[Galaxy S III Original Android Development] LenAsh:
Discussed many times before. Go look... or search even.
[Galaxy S III Original Android Development] LaZyDood:
turn off direct DAC under audio in stweaks
[Galaxy S III Original Android Development] Oleh:
Hi AndreiLux, merry Christmas to you!

The Perseus is definitely the best kernel for Android 4.1 so first of all thank you for developing it. Based on my experience with all Perseus versions the fastest one I identified is version 28. I’ve made various comparisons to come to this conclusion. There is also a quick way to identify how versions after 28 are slower. It takes only 10 minutes – load Fly Boy from Play Store and start using power save mode. It is easy to notice that versions prior to 28 work smoother and without lags compared to later (28.1) versions. What in your opinion might be a reason for that? I’m still loading and testing every new version of Perseus and at the moment v28 works best for me. Thanks again for your great job and an awesome kernel.
[Galaxy S III Original Android Development] Frag1le:
What do you test for it to be noticeably slower?

One single game 'Fly Boy' isn't really a proper test.
[Galaxy S III Original Android Development] Oleh:
Fly Boy is just a fast, easy and clearly way to notice the lags and delays.

I can notice the same (always by power save mode) in many another apps e.g. by leaf through or scrolling in Nova Launcher.
[Galaxy S III Original Android Development] ibanezq:
How to back to stock kernel?

Wysyłane z mojego GT-I9300 za pomocą Tapatalk 2
[Galaxy S III Original Android Development] ahac85:
Hi I don't know if it's kernel that is making this happen but when I charge phone it randomly switches itself off or reboots. How do I produce a logcat. When not charging it's fine. Using mamba270026 settings and latest 29.2 kernel
[Galaxy S III Original Android Development] Chris_84:
Reflash your rom without wipe.

Throwing out of the window from my flying Ferrari killer S3 driven by a proud omega team member :P
[Galaxy S III Original Android Development] atomic339:
If I want to update for 29.1 to 29.2 I have to reset STweak setting?
[Galaxy S III Original Android Development] crash_194:
Please could you tell me what app you are using here?

Thanks in advance.
[Galaxy S III Original Android Development] kachrukamble:
can any one post 4 digit CPU voltage steps for 7-8 digit each voltage steps?? I am solid confused with 1375800 like voltage digit.

I know its like 1375.800 but but if i want CPU scale down to -50 its hard atleast for me..
[Galaxy S III Original Android Development] tribemac:
No you don't

Skickat från min GT-I9300 via Tapatalk 2
[Galaxy S III Original Android Development] Schmiddi1008:
It would be very nice if someone can help us;)

Cheers Merry X Mas
[Galaxy S III Original Android Development] simmer14:
m on 29.2 sometimes my touch screen does not responds bt the soft keys r working fine to reenable the touch i have to press the power key lock the screen nd then unlocking it solves the touch poblem .. anyone else having the same prob ..
[Galaxy S III Original Android Development] IamIrene:
Anybody can tell me how to charge faster when using usb ?

I can't find it under stweak app
[Galaxy S III Original Android Development] iridaki:
Here's what you need to do. It's a dirty way that my Maths teacher would be sad to see me use, but here it is:

1375800, you should treat it as 1375 and 800, which will stay the same.

So 1375800 for a -50 UV will become 1325800. So basically, ignore the last 3 digits, leave them as is, and substract the amount from the remaining.

If that makes sense at all. :D
[Galaxy S III Original Android Development] mamba720027:
If you have UV the phone as stated in the setting like I mentioned in previous posts and only then the phone turns itself off then you should try using default Perseus settings by resetting Stweaks because your phone may not be able to handle the UV settings and is not consider a bug.

Sent from my GT-I9300

---------- Post added at 10:58 PM ---------- Previous post was at 10:48 PM ----------

Do you mind giveing a breif description of what youre useing for example

Rom,if default kernel settings are used etc. If default and latest kernel setting is being used I suggest recording a logcat and post it so the dev or someone with knowledge on reading it can help solve the problem.

I think its hardcoded into the kernel and not an option in Stweaks.

Sent from my GT-I9300
[Galaxy S III Original Android Development] ahac85:
Your right I uv -100mv on 1500 and 1600 freq. Now uv -50 all is ok
[Galaxy S III Original Android Development] Schmiddi1008:
Have no idea atm :D - I thought i know it but i don´t know:D Maybe you can show us screens from all UV´s so its easier to set it

Thanks

Edit: Or post all Uvs^^
[Galaxy S III Original Android Development] BioVolt:
System Tuner Pro
[Galaxy S III Original Android Development] Bogazicili90:
Hello guys. I need some comments about perseus and siyah kernels. Which one is the best in terms of both battery consumptions and smoothness? I tested both of them with different frequencies and I got maximum 18600 Point on Antutu with Perseus at 1704 MHz. And 16600 Point with Siyah at 1704 MHz. I tested battery consumption of Siyah and it is remarkebly good compared to stock kernel. But I haven't test Perseus and don't know how it is in terms of battery performance. Do you have any idea or comments about it?
[Galaxy S III Original Android Development] mamba720027:
Ok here's what its like for me on the CPU.

Sent from my GT-I9300
[Galaxy S III Original Android Development] omniwolf:
you're almost there, mate. now that you've tested* the performance yourself, test the battery yourself! There's not much point asking others how their battery life is, as everyone uses the phone differently and will have different results. For me Perseus might be great and Siyah not as good, but with your usage patterns Siyah might be great and Perseus not as good.

* everyone knows benchmarks are no good at rating real life experience, but if these numbers make you feel better about the kernel then that's your prerogative
[Galaxy S III Original Android Development] Stivikivi:
It's strange you have other default values than I have hmm
[Galaxy S III Original Android Development] omniwolf:
it's actually not strange, depending on the quality of your CPU, the kernel will set different default voltages. Higher quality CPUs can deal with lower voltage per frequency.

the various voltages of the different quality of CPU can be found here
[Galaxy S III Original Android Development] cruzargel:
Anyone getting wifi drops? Im sure that it's not a router problem. Not sure how to pinpoint the cause
[Galaxy S III Original Android Development] mamba720027:
Not having that problem with WiFi on here but you can read this article linked below and try the suggested to see if it works.

galaxys3reviews.net/samsung-galaxy-s3-wifi-problem-fix

Sent from my GT-I9300
[Galaxy S III Original Android Development] Pitiklin:
yes, here the same. with other kernels I haven't this problem
[Galaxy S III Original Android Development] Tenacious:
This happened to me this morning after I left my phone to charge overnight, here is last kmsg http://db.tt/ZRgmWAc0

Edit

This is on 29.2 and null rom.
[Galaxy S III Original Android Development] Frag1le:
No such problems here. I've charged it overnight several times with AC from 10~20% to full.
[Galaxy S III Original Android Development] Tenacious:
Good for you but two of us have this so there is something, forget to mention this was on usb charging. Will see how will it go on next charge.
[Galaxy S III Original Android Development] danarama:
Me too but not just on perseus. Set your voltages default if they are not already. I'm not convinced this is a perseus issue. I had it in siyah too.
[Galaxy S III Original Android Development] Tenacious:
Will do one more charge on my current voltages and see will it happen again if it does I'll reset them to default and see will it happen on default voltage.
[Galaxy S III Original Android Development] danarama:
I'm still testing at higher voltages. Thing is, I still had same voltages I used in 4.0.4 which easily could now be too low. Few days so far so good but will be 2 weeks before I'm happy its "fixed"
[Galaxy S III Original Android Development] habylab:
Anyone using pimp my ROM with this? I have all the network tweaks and most I/o comes enabled, anyone else?
[Galaxy S III Original Android Development] erto90:
i got it.. but honestly don't know if them works or not :rolleyes:

haven't noticed any difference..

the only thing is that the app locking in memory fails all times
[Galaxy S III Original Android Development] Raugote:
Hi

I'm resently trying this kernel, but I'm unable to fin USB or wall charger rate under STweaks application, according to the changelog, USB is up to 900mA, wich I consider is a little too much, and wall charger, I Couldn't find the setting, so I was wondering if someone can give me a light on this

thanks
[Galaxy S III Original Android Development] David Braund:
i installed this and now its just in a loop on the samsung logo

what did i do wrong?
[Galaxy S III Original Android Development] KS_Ho:
1. You sure you flashed it for the right phone [i9300/i9305]?

2. Are you on CM/AOSP/AOKP? This Kernel is for Samsung Based ROMs only
[Galaxy S III Original Android Development] habylab:
Well depends what you're locking in I guess, numbers wise? Or just home launcher?
[Galaxy S III Original Android Development] mamba720027:
This was answer just 2 pages back. Always good to do a quick brushup reading like 5 pages or so at least before posting.

Anyways,its not an option built into Stweaks like it is in siyah kernel.

And 900ma is not too much,besides battery's are cheap like 99cents to one on eBay :p

Sent from my GT-I9300
[Galaxy S III Original Android Development] AndreiLux:
Attention my dear lab-rats.

I'm currently working on something new, but I am in need of more data. I'm searching for people who undervolt their devices to the maximum possible. I'm requesting that those who have found out their minimum voltages to please fill out the spreadsheet linked below. It is important that you fill out your ASV group or at least give the stock voltages for a few frequencies so that I can find out your groups. Thank you in advance.

https://docs.google.com/spreadsheet/ccc?key=0AnstDauz_DTTdHZEU0hWOXZVTjA1cTduNFczY0k2OUE
[Galaxy S III Original Android Development] omniwolf:
Andrei, do you want i9305 users to fill it out as well?

ps - anyone interested in working out their ASV group can look here:

https://github.com/AndreiLux/Perseus-S3/blob/master/arch/arm/mach-exynos/cpufreq-4x12.c#L374

I have added mine in - i'll keep trying to push the boundaries to see if i can reduce the voltage too to get more accurate stats.
[Galaxy S III Original Android Development] rlorange:
I never had a problem fixing touch screen frequency lock to 200mhz using kmemhelper on the S2. 800mHz lock on the S3 seems like mega overkill from Samsung.

Since the ARM voltage can handle huge undervolting on the S3 I'm quite excited to find out how far internal, bus, screen and ram undervolting can go.

I assume these variables first need to be identified and then exported before kmemhelper can control it... fun times ahead!
[Galaxy S III Original Android Development] AndreiLux:
I'm just going to make interfaces for those voltages anyway, no need to screw around with kmemhelper. Screen undervolting proved to be a stupid thing to do on the S2. Furthermore there's a new rail called MIF voltage somehow replacing the internal bus voltage, while the latter is still present, not really sure between the differences of the two.

I was planning to try some unused parts of code with regard to the screen lock frequency but that needs to be tested...
[Galaxy S III Original Android Development] luke05dee:
hiya AndreiLux I heard you were exploring the mali driver. Hope you don't mind me asking but do you think it's possible to rewrite the part of the driver that controls the available frequencies so it would be possible to have more control over intermediate and overclocking GPU frequencies instead of a few fixed frequencies, with very little control over them? I really appreciate all your work, thank you :D