yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] habylab:
Tried out Siyah with the new Mali drivers, so much smoother than this, has to be said. I hope you will too Andrei, as the battery and everything else on this is pretty amazing.

Sounds impossible/placebo?!

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] cba1986:
Maybe. But considering the UV applied that would be a bonus.
[Galaxy S III Original Android Development] nfsmw_gr:
Newer mali are only used on CM10.1 afaik.

On sammy firmware the latest from sammy's sources are used (again afaik).

(also +1 on your sig man. ;) )
[Galaxy S III Original Android Development] tyrtok:
Hello, im not sure if this is a ROM or Kernal problem, anyone facing any problems with 'WIFI powersave' toggle? im unable to connect to peap network after my device sleeps when the toggle is set to on. but toggle goes back to on from off position after a restart. May I know if there are any wifi policy that I can hard code on?
[Galaxy S III Original Android Development] pistoke:
I thought that too, but why everything works at -100mV and at - 50mV not? I think it was because I locked my CPU to use only 200MHz and during the test phone wanted to communicate, sync or something, but there were not enough power. This made my phone extremely slow and I thought it freezed... On the second day I did everything again. Now with wlan, gps and mobile data off. I have lower V and 50% longer test run. No freezing. Now a few days in use, wlan or mobile data and gps always on. No freezing.
[Galaxy S III Original Android Development] yhrn:
I have a few questions about STweaks. Since a couple of Perseus versions back I always get an update from Google Play for STweaks after I've flashed a new version of the kernel. Not thinking too much about it I accepted the update (since I like to be able to use the "Update all" button) and STweaks always seemed to work afterwards. However, last time I rebooted the phone (I didn't flash anything, just a normal reboot) the phone booted up then something went wrong so it automatically did a "hot reboot" again and then started normally. After that the STweaks update was back in Google Play so it seems the version that comes with the kernel overwrote the update from Play or something.

Does anybody know why that happened? And what are differences between the Play version and the version that comes with the kernel? And finally, if the conclusion is that I should stay away from the Play update does anybody know how I can get rid of it (I tried detaching STweaks from Google Play using TB but that had no effect)?
[Galaxy S III Original Android Development] STAticKY:
The playstore version only removes the donate butt i think.

Sent from my portable powerhouse
[Galaxy S III Original Android Development] habylab:
Galaxy S, best community!

And siyah has the new Mali drivers according to the changelog. The battery life is so much worse, but I'm pretty sure it is the new mali drivers - temaseks is smooth too with them, and it is essentially a copied version of this.

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] nfsmw_gr:
I know,i've read the changelog. :)

What i'm saying is that the newer drivers are used only when the kernel boots cm10.1.

When it boots a sammy rom it uses sammy source drivers afaik.

Anyway,the best thing to solve this is to ask Gokhanmoral himself,because this is a bit off topic i think. ;)
[Galaxy S III Original Android Development] bxlogic:
[MENTION=4167023]AndreiLux[/MENTION]

this is the most powerful Kernel ever made about the battery matter for SGS3, i used this kernel when i used 4.1.2 now i am using 4.2.1 version of rom i was wondering to ask do you plan to make a release for 4.2.1 ROM? :D

thanks in advance, keep the good work up! :D
[Galaxy S III Original Android Development] nfsmw_gr:
I'm pretty sure he won't do a 4.2.1 version of the kernel.

Not atleast sources are out. :)

Anyway,i'd suggest you to go to a 4.1.2 android version,because the 4.2.1 was an old leak and the latest 4.1.2 are better overall. ;)
[Galaxy S III Original Android Development] cba1986:
Well. I had my first crash while installing an app. I decreased the second slice from 950 to 900 to give more room to breath to the freq range [800..300]. Believe it or not, this range is to unstable for UV surely because that frequencies are already RBB.
[Galaxy S III Original Android Development] KKTHX:
bla bla bla.

Fixed ^__^
[Galaxy S III Original Android Development] Tokarin:
Hi Andreilux

I wonder where can I change the touch boost from original 800mhz to 1ghz? I understand the flexrate and all, but I guess it's not touch boost.

I changed the max freq to 1ghz and also flexrate force rate to 15000microS but still whenever I touched the screen, it still seem to get up to 800mhz only/first

Sent from my GT-I9300
[Galaxy S III Original Android Development] habylab:
True,

On that note, how can I remove these slight lags? I don't have them in Siyah, and as discussed this is not due to new GPU drivers.

Am I looking at keeping the GPU higher? Quicker up threshold? Thank you.

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] nfsmw_gr:
Personally i use 266mhz undervolted as minimum step for smoothness and it's very smooth like this.

Also the battery life is about the same as the deafault...:)

Plus another one,this isn't for smoothness but for battery...i upped the threshold to 85%-90% so the higher steps will only be used when needed..;)

Give those settings a go and post back mate.

If you want i could upload my whole STweaks profile(without uv of course,so that your phone won't freeze) so you could take a look at my settings,i've also tweaked other things.
[Galaxy S III Original Android Development] habylab:
I've noticed Sched_something is set to two, is this decremental to speed?

I've done the same. I've lowered the up threshold to 65 and the down differential to 25 for GPU, smooth!

[/COLOR]

I've never understood flex rate force rate, or some other values on the cpu page, but what does it do, simply?

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] Tokarin:
It quickly ramp up the CPU to process things, in circumstances it can make the phone smoother because many hardware renders happens on the CPU, not the GPU. Also some calculations are made when you touch the screen too, because obviously you touched the screen to change something right?

Flex rate is better than normal scaling because it goes from minimum straight to that frequency at very fast rate and then get back to minimum quickly too.

Sent from my GT-I9300
[Galaxy S III Original Android Development] habylab:
Okay, thank you. So what about the very bottom value? What difference does that that make?

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] MattBooth:
Sorry if this is getting tiresome now, but ABB.

I have ASV5. I knocked 50mv off each value and managed another 50mv undervolt on all steps (200-1400).

The lower the ABB (RBB) the better it is for power leakage reduction and lower voltages?
[Galaxy S III Original Android Development] Tokarin:
That's the thing I'm asking andreilux duh :D

Normally an s3 touch boost is 800mhz, gokhanmoral allow the modification of this value to 1000mhz while andreilux allow us to increase or decrease the value, which effectively would reduce the touch boost frequency to save battery but get minor stutters/lags. What I wanted to ask is how to raise this touch boost value because the flex rate force rate option doesn't do that for you...

When you set max freq flex rate to 1ghz, you'll still get 800mhz when you touch, where I get minor lags in launcher, small scrolling and such which hardly a GPU task so I thought increasing touch boost would help.

Sent from my GT-I9300
[Galaxy S III Original Android Development] habylab:
So would increasing the flex rate force rate make it quicker or slower? Thanks again.

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] Tokarin:
Should be slower, logically I think so but not sure. Because you can only set it more than 10ms to work which means naturally or logically the original flex rate request rate is lower than that.

Sent from my GT-I9300
[Galaxy S III Original Android Development] ffolkes:
I don't think this setting works the way you think it does. From what I understand, the max rate is essentially the point at which requests are ignored since presumably the user has started interacting with the device and the cpu governor is now best suited to take over.
[Galaxy S III Original Android Development] psyntific:
yea mate can you upload your profile plz???
[Galaxy S III Original Android Development] nfsmw_gr:
Yes mate,here you go. :)

My profile is tuned for good battery life,but with smooth ui and performance when needed. ;)

There's two profiles inside.

The one that says UV on the title is undervolted with my stable values,the other one without the UV is with stock voltages!

I'd suggest using the non-undervolted one.

Use at your own risk,i'm not responsible if you freeze your phone. ;)
[Galaxy S III Original Android Development] KKTHX:
Perseus 36.3 is strange. In Geekbench 2 test score is always near 1500p, in saving mode near 1100p.

On stock kernel from MR7 rom, score is always 1750p to 1780p, in saving mode near 1500p.

All setting in Perseus 36/36.3 are default (voltages of cpu,gpu, memory int/ext, swap etc)

WTF is wrong with this kernel ?

Perseus have great and unique setting but why have so much slow down sgs3 ?
[Galaxy S III Original Android Development] STAticKY:
You cant trust benchmarks for anything. They have no relivance to real world speed of the device.. even computer benchmarks....

Sent from my portable powerhouse
[Galaxy S III Original Android Development] Lucmuzz:
Banchmarks don't matter if your phone feels fast and smooth. Just to let you know, I use Perseus with Omega 44.3, and get 2050 - 2100 in Geekbench. CPU overclocked to 1704 and GPU overclocked to 533. Bit of UV on both, but quite moderate.
[Galaxy S III Original Android Development] nfsmw_gr:
Anyone tried this? (i saw 32 views on the file so i'm asking)
[Galaxy S III Original Android Development] psyntific:
Yea I did mate... all good till now.. I picked some settings from yours n rewired mine.. thank you man
[Galaxy S III Original Android Development] WiwiPouPou:
Asv04 uv/oc abb

https://docs.google.com/spreadsheet/ccc?key=0AnxSTLdr7ZaAdHpScDc4MnZCMzZUSlJYWnM3SkNPZHc&usp=sharing

Here are my current values for an ASV04 chip ! Pretty stable, -0.3% / h overnight, (CarbonRom and Temasek kernel)

I wonder what is better for slice 1 ? 800 or 900 ?
[Galaxy S III Original Android Development] habylab:
We should be using override profiles now, less risky.
[Galaxy S III Original Android Development] nfsmw_gr:
I didn't get you,could you explain it a bit? :)
[Galaxy S III Original Android Development] habylab:
Sure, here's what Andrei said on the tweaks thread:
[Galaxy S III Original Android Development] nfsmw_gr:
Woot woot!

That looks fantastic!

Thanks habylab! :highfive:
[Galaxy S III Original Android Development] jose_p90:
PROFILE

hi man can you share your profile, i don understand yet how that works, im asv 4 too but i have ultimarom
[Galaxy S III Original Android Development] WiwiPouPou:
ASV 04 results

I think i found balance for my ASV04, sheet still updating if change are made, but these value seems good for me !

https://docs.google.com/spreadsheet/ccc?key=0AnxSTLdr7ZaAdHpScDc4MnZCMzZUSlJYWnM3SkNPZHc&usp=sharing
[Galaxy S III Original Android Development] cba1986:
To anyone interested i created a thread to specificly share profiles and ask question about ABB.

http://xdaforums.com/showthread.php?p=40893859#post40893859
[Galaxy S III Original Android Development] sergiuvolo:
the sudden death fix is from alfa31 to the last release or only that release?
[Galaxy S III Original Android Development] vladmir:
Since alfa 31, this kernel have sudden death fix.
[Galaxy S III Original Android Development] sergiuvolo:
thank you man.:good:
[Galaxy S III Original Android Development] reS28raM:
What about the augmented max brightness by 50cd, is that available from the slider control in the notification area?

I use Lux, an userspace app which controls brightness via a complex auto-calibrating mechanism: by putting it to the max it seems to me I can get more light from the screen, but dunno if it is a placebo effect or the real thing, I don't have any instrument to measure it objectively.

Also, being an auto-calibrating app maybe Lux is not the best for this test. I didnt see any comment on this important patch to the kernel (thanks AndreiLux, you rocks!).
[Galaxy S III Original Android Development] tolis626:
So...I have a hunch that leakage isn't as insignificant in higher frequencies as we thought.I may be wrong as it's a subjective matter,but I think that at 1704MHz my CPU produces more heat when I use 1300mV gate/900mV body voltage than when I use 1325mV gate/1150mV body voltage.I tested it only two times,so it can be random.If more people test high clocks with high FBB we may get to a conclusion.My device is ASV3,just for the record.

Anyway.. [MENTION=4167023]AndreiLux[/MENTION]

Seeing that ABB worked as intended,I would suggest that you add 2 more steps for the CPU,1.9GHz and 2GHz,and to divide the third slice in two ( say [800,1200) and [1200,1600) ),as the behavior of >1200MHz clocks is quite different from <1200MHz ones.Also,it would be wicked if you could make thermal throttling thresholds configurable.I used to think that it's too dangerous,but we can already fry our devices easily as it is,so why the hell not?Let's see what the S3 can do. ;)
[Galaxy S III Original Android Development] habylab:
Disabling the thermal controls is just asking for trouble. It is there for a reason, seriously.

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] tolis626:
Who said anything about disabling them?Quite the contrary,usually I'm the first to say that they must not ever be disabled.I just think that it may be a good idea for us to be able to adjust them by a few degrees.It's as I said,we have more effective ways to fry our phones if any one of us is so inclined.
[Galaxy S III Original Android Development] amppen:
Hey, guys

If someone's interested, here's a research paper about body biasing. Light reading (not).

Texted with my Nokia 5110
[Galaxy S III Original Android Development] habylab:
It isn't quite the contrary: you want to adjust it son it becomes less safe. The performance gains from this would be minimal, otherwise it would already have been done with a big fat "warning" slapped on it.

Anyway, I don't like argument, I'll play nice.

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] STAticKY:
What about all the people that live in places that are very cold all year long. Maby extra protection can be coded in so the thermal limits can scale with battery temp a little...

Sent from my portable powerhouse
[Galaxy S III Original Android Development] habylab:
Really? You know the phone temperature won't change because the phone has it's own case. The thermal limits are related to temperature, it doesn't matter where you live, it is the safe limit for the phone.

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] STAticKY:
Well from what iv read so far from the pdf [MENTION=4042238]amppen[/MENTION] posted it should make a diffrence

Sent from my portable powerhouse
[Galaxy S III Original Android Development] habylab:
Okay.

Back on topic: how's the latest kernel running for people? Any problems?

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] Kemby13:
Not exactly problems, but i do have an observation. I notice that with the latest kernel my phone isn't as smooth as it was with lets say v35. And the battery life is definetly not as good... I even fresh-installed my rom again. All the settings are identical within the Stweaks, except the ABB tab - which i left unchanged. I'm not exactly sure what is causing this, but i think it's the new feature, or to put it better, ABB settings along with my UV/OC settings is not giving me the same experience i had with v35. I hope that's understandable. So, if anyone can point me to v35 DL link, i would be very gratefull. I just wanna test this... Btw, i have an ASV3.
[Galaxy S III Original Android Development] Olioaglio:
Here you go, m8. I upped it to my dropbox as cwm file: http://db.tt/xxcQwOGj

Always better to have a little local archive just in case :D

Cheers, Olioaglio
[Galaxy S III Original Android Development] aiurs.fury:
Weird problem

I am having a problem. I'm not entirely sure its Kernel related but this is my best guess at the moment.

I am running Perseus alpha35 with Omega Rom XXEMC3 and latest JKay Deluxe Framework (14.94).

My first suspicion is that my phone was too heavily undervolted, and in fact I could not reproduce the problems with stock voltage, however I used the same undervolting voltages on older versions of Perseus (33 and older) other kernels and never had any problems (Siyah, Boeffla). Even with only slight undervolting (max -75 mV on 200 MHz, average -25 to -50 mV) the problem persisted. My "heavy" undervolted settings are tested for stability and have been used for months without problems.

No to the actual problem:

The problem that occurs is hard to reproduce (it happens approx. once a week), but if it happens my Alarm does not go off properly (app is Alarm Clock Xtreme). In fact it goes off but I do not hear the sound. Once I wake up the phone, the sound reappears. Today I also noticed that I has a Partial Wakelock "AudioOut_2" over the hole night. I did a reboot recently before that which I suspect to have triggered the wakelock.

I suspect it could have something to do with the new audio controls since alpha34.

Any tips and help would be greatly apreciated.
[Galaxy S III Original Android Development] Kemby13:
Thx m8 :)
[Galaxy S III Original Android Development] nfsmw_gr:
I had the same problem..:/

I messed around with the voltages a bit and now this won't happen anymore...(until now,lol :p )

Check your gpu voltages too mate...i haven't found the solution for this yet!
[Galaxy S III Original Android Development] jose_p90:
Profile

Buddy can you Make a profile and share it?
[Galaxy S III Original Android Development] jimbo77:
I've got to say, the kernel is damn good and both the ABB and color configurations are a most have, however I'm having issues with Audio playback.

It is something that happens out of no where, I.e I'm listening to some music and the audio starts to break if I try to wake up the screen it lags like hell

I've tried removing Perseus folder and reflashing the Kernel but.nothing helps, I've wiped data and installed all apps but.once the issue has happened only a full wipe (including system) fixes it.

Any clue what might be causing the issue? Is anyone having the same problem..??

EDIT: I forgot to mention the issue doesn't happen on Siyah, Stock or Shark. It also happened on Devil kernel which is based on Perseus sources so I think is kernel related.
[Galaxy S III Original Android Development] psyntific:
Possibly because of too much undervolting?????
[Galaxy S III Original Android Development] mmse88:
I just flashed 22.3 few minutes and now 23 has released. Great!!! I love flashing. LOL

Thanks mate!!!
[Galaxy S III Original Android Development] tvhak:
thanks andreilux. going to download and flash it
[Galaxy S III Original Android Development] gee2012:
Thanks for a great kernel AndeiLux, just downloaded alpha23 and will report back on batterylife :good:
[Galaxy S III Original Android Development] SETdown:
I flashed now but i see a bit of blink on the screen.

Maybe a bug?

Thanks for this great work.
[Galaxy S III Original Android Development] naveediftikhar:
Ok can anybody tell me that is there any app thru which i can uv the gpu or will i havto script it!
[Galaxy S III Original Android Development] dereknas:
The screen flickers quite badly in v23.
[Galaxy S III Original Android Development] Bushido76:
Hey AndreiLux,

I really like people, who think outside the box ... and you and gokhan are two of them. :) Thanks for your great ideas...

My first impression concerning alpha23:

I'm using SPB-Shell as home screen replacement and it was running very good with alpha 22.3. Now with alpha23 something seems to prevent the system from reacting as snappy as it has been alpha22.3. Switching between homescreens/menus stutters very often. I'm not really sure, whether the reason ist the freshly implemented powermanagement below 500mhz or the the time the regulator needs to switch from one screen freqency to another (or any other frequency sync problem with gpu).

Thanks,

Bushido
[Galaxy S III Original Android Development] gee2012:
I don`t xperience this issue, have you cleared the cache and dalvik cache after the installation. And at least reboot 2-3 times after the flash.
[Galaxy S III Original Android Development] ajoi57:
+1
[Galaxy S III Original Android Development] onurerler:
on stock kernel everythings is buttery smooth but have strange freezing problems.

on this kernel there is no freezing problem but scrolling is not smooth, very lagy. (by the way alpha23 a bit better than alpha22 on scrolling performance).

I mean it seems like project butter still doesnt work %100.
[Galaxy S III Original Android Development] dereknas:
Strangely after going back to v22.3 then reflash back v23 seems fine now.

# spoke too soon.. Flicker came back.. Trying to wipe cache, reboot and see.

## well, no luck even after wiping cache...reverting back to v22.3
[Galaxy S III Original Android Development] fylim:
Got this problem as well. Notice it against white background in flip board.
[Galaxy S III Original Android Development] jothi2lingam:
Just flashed alpha23 after wipe cache & dalvik .....Screen flickering even in home screen.... After flash alpha22.3 its gone
[Galaxy S III Original Android Development] scheichuwe:
I flashed alpha23 about 2h ago, no problems here.

I didn't change anything (no oc, no uv, nothing...), the only thing I noticed is the cpu running at max freq for the first 3-4 minutes after reboot.

Edit:

I forgot to say thanks, so...

Thanks for this kernel :)
[Galaxy S III Original Android Development] jenicekk:
Menu and back buttons dont ligt on 23... After flash alpha22.3 its gone
[Galaxy S III Original Android Development] hazri1974:
Same here....hope it will be fix on next build...
[Galaxy S III Original Android Development] ristokoo:
I don't think clearing caches or rebooting has any effect on how the kernel works.

And I also confirm the screen flickering problem. To andreilux, thanks for your great work!
[Galaxy S III Original Android Development] currydude:
no screen flickering here (jellybean LIB build) but back light for menu buttons not working
[Galaxy S III Original Android Development] dereknas:
Its a matter of time before the flickering occurs. It is most obvious on white background and less on the home screen, but it is there.
[Galaxy S III Original Android Development] robogo1982:
Sitting on stock with 22.3 and have no problems with very good battery life. When I say very good, I mean a drastic improvement over ICS. :)
[Galaxy S III Original Android Development] jimbo77:
I thought about it but the issue also appeared even with no UV at all, I was using default values...
[Galaxy S III Original Android Development] alberber:
Have you tried default configuration of the kernel? Maybe you touched something you shouldn't have.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] yugoport:
Any updates on this test You were doing? I have the same issue with v36..
[Galaxy S III Original Android Development] jimbo77:
I think I nailed my issue. I found that without too much over clocking the GPU and with no Undervolding it the issue seems to be gone.

I'll continue to monitor tomorrow and let you all know