yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Bushido76:
Hey AndreiLux,

thanks for your detailed response. Enclosed my thoughts to the mentioned problems:

1) This is definitely a problem since screen controllers will never be as optimized for "state changes" like mobile CPUs. So I think we have to deal with it and reduce it to an absolute minimum (the count of the state changes and the time for the state change). How do you change the pixel clock at runtime - are you using the set_lcdfreq_div-function or are you setting the regs directly?

2) It's possible and would be great for battery life. ;) I remember some android kernels devs (for the SI) who reduced the display voltages as well, but I'm not really sure that the display controller has it's own voltage table (according to the frequency table).

At the moment I haven't give up hope, that our problem isn't caused by 1) and 2). In my eyes the flickering could be caused by problem 3) too... ;)

3) To many state changes in a defined time interval: In your pegasusq-logic you use two different main trigger events (cpu-frequency, display-touch). As the active governor module is in a constant loop there are load calculations all the time. This can lead to very fast load changes what can in turn lead to fast frequency changes. So it's possible, that your cpu jumps around 500MHz for maybe some seconds. Your idea to reduce the correlating display freq changes with the kick_in_delay is very useful/necessary for this point.

When you touch the display, your "second" trigger will be active. But it could be the case, that touching the display doesn't raise the CPU-frequency over 500 MHz. So the pegasusQ-logic instantly (after the kick in delay) will switch to around 40 Hz. When this delay is too short this can cause visible "interferences" too.

So how to reduce this state changes:

a) Increasing the kick in delay further: I did some tests with value 100 (instead of 20) and the flickering was completely gone on my phone. This supports 3) in my eyes but is more likely a workaround.

b) Trying to use only one trigger event: In my eyes this event should be the cpu-frequeny. In this case it should be the "real actual frequency" of the cpu and no "rapidly changing" freq_next-value in pegasusq. To get the touch-component into this equation you could use a touch-boost function like gokhan does in his kernel. When everything is "controlled by cpy frequency" we could do some tests which kick in delay maybe a good compromise for everyone.

Hope that helps a little,

Bushido
[Galaxy S III Original Android Development] androidfreak007:
+1
[Galaxy S III Original Android Development] mmse88:
Just want to share my SetCPU setting

Dear all,

This version of SetCPU which I have been paid so it's the latest version.

Have been using this kernel of version 23.3 almost 24 hours or more. Really amazing for it's stability.

I have lowered the voltage to over -100mV and it still running very smoothly. Unbelievable :)

I am playing with Poweramp, Dolphin browser beta, XDA, Quadrant to test the scores and the stabilty, Youtube and watch movies with Rock player...etcs.

Honestly, 100% no crashes or freezes at all :D

P.S: I don't play games:p
[Galaxy S III Original Android Development] nicregi:
Thanks for sharing buddy!
[Galaxy S III Original Android Development] tincmulc:
The screen voltage hack was reverted by almost all kernel devs, beacuse running the screen at a lower voltage inscreased the amps it drew to display the same brightness. As we know more amps = more waste heat.

I agree on your other points and would like to add in another idea:

If it is possible to detect when video is playing (which probably can be, because all video playback is hardware accelerated?) to lock to a lower refresh rate. You don't need 60 Hz to play a 25-30 fps video. This could help a lot when watching whole movies, series episodes or long youtube videos on the phone - they can increase the frequency of the cpu to over the current treshold, which might cause flicker and reduce the time the screen is in the lower refresh rate state.
[Galaxy S III Original Android Development] Bushido76:
This kind of posts I normally expect in development sections... But such discussions are really rare... ;)

I did not follow the SI screen voltage problem to the end, but thanks for the clearification. So at the end the lower voltage meant higher battery usage.. ;)

But indeed great idea to use a reduced screen frequency for video playing. In my eyes you are facing two problems:

1) I think you have to sync screen frequency and video fps when you lower the frequency near the video fps.

2) You have to "investigate" whether a video is running in full screen mode. So in my eyes this shouldn't be done in the cpu-governor code, because the checks could interfere with other things like fast cpu scaling on heavy cpu load.

Bushido
[Galaxy S III Original Android Development] tincmulc:
I was thinking about 1) too but I can't guess what happens. Vsync is on anyway so tearing shouldn't be an issue, jitter on the other hand... I'll try some tests with the current implementation - setting the max allowed lcdfreq to 1400 should give a constant 40 Hz when not touching the screen right?

Also the Samsung "Power save mode" which lowers the refresh rate too, has no problem playing videos. (this is for fully stock roms, I'm aware that this kernel might override that.)

On your second point, I wasn't thinking about doing any checking for video playback full screen or not - if a video is playing there is good chance the user isn't doing anything interactive anyway. When hardware accelerated video starts playing there should be some calls to the kernel to get this working(my guess is based on the fact that using a wrong a kernel in the cm world can result in HW accelerated video playback to stop working). If we have the source of the code that does this, maybe we can sneak in the lcd frequency change.

One more thing: All this might be just a waste, because in most situations with video playback the user isn't touching the screen so normal operation of lcdfreq should work fine. I would only change it so that if the screen wasn't touched for say 10 seconds to ignore the cpu frequency part of the code. Or maybe something like a scale up mechanism combined with a no touch for 10 seconds so that small spikes in cpu freq don't kick you out of 40 Hz and than you wait for step down to 40 again. Again my only concern here is that playing video in the current implementation probably doesn't have optimal "time in state" for 40 Hz.
[Galaxy S III Original Android Development] silvio82:
I'm on -50mV and all is ok, with games too (i think asphalt 7 is a good stress test) :D

Will try -75....:)

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] AndreiLux:
1) I put some hooks and wrappers in the lcdfreq driver for which are called by the governors, but basically the logic is still the standard one being used in the default code with lcdfreq_lock and lcdfreq_lock_free which both fowards to set_lcdfreq_div as you said.

2) This was kind of a failure on the S2, I would have to test it again here but I'm pessimistic about it.

3) I've already tested that and it's not the case, the flicker occurs on a switch no matter how often the switching is done, you can play around with the variables to have it basically lock to 40Hz by a very big cpu freq value and also a huge kick in delay, since that gets overridden anyway by the touch boost.

a) Your flickering was gone with 100 kick in delay for the sole reason that the delay is way too high and it never achieves the condition and you remain at 60Hz always. Repeat this test but keep an account of time_in_state of the 40Hz step. It won't increase.

b) I don't quite understand what you're suggesting here. We're using thresholds so the arbitrary next_freq gets roughed out anyway, and with 100MHz grained frequency tables, it wouldn't matter. It's already as optimized as it can be in that regard. Also you're suggesting me to put back in a frequency touch booster when I specifically wanted to remove that away from this kernel and replace it with the flexrate mechanic, which I reckon, is pretty successful and quite better.

Maybe I could detect activity on the MFC in the kernel but it's a very, very bad way of doing it because video acceleration can also happen outside dedicated players like on embedded players on webpages, and there you don't want 40Hz for sure. This needs to be userspace controlled, and I am drawing plans for an application which does this.

What? It's the first time I heard of power saving mode doing that, it doesn't. At least not for me. Remember I put the time_in_state accounting in if you want to convince yourself.

You can force the display to low frequency by echo 1 > /sys/devices/platform/samsung-pd.2/s3cfb.0/graphics/fb0/lcdfreq/level, high frequency by echo 0. Be sure to disable the governor logic though else it gets overridden. It is not a viable state for anything interactive playing on the screen, and you really need userspace driven logic to force it for things like video, because that is a user-case which simply doesn't fit the internal logic right now.

As I said, if you mean kernel-space, then that's a no-go. If you want to modify AOSP code, well then good luck.

Edit: I added the commits to my Github.
[Galaxy S III Original Android Development] qwerty12:
Here's a Jelly Bean adbd binary built from the android-4.1.1_r6 branch (adb install works fine) that runs as root. Please consider replacing your current adbd binary with this one for your next update. I can put up the source, but I (literally) only changed one character.

EDIT: Removed binary since it's in Perseus now.
[Galaxy S III Original Android Development] nicregi:
Back to this kernel from others. Got to say love the smoothness. Battery still early to say.

@Dev

Like the way to respond to others. Respected and good job buddy!

---------- Post added at 12:01 AM ---------- Previous post was at 12:00 AM ----------

I am on - 75mV and everything good. Amazing. Thinking if I should go - 100
[Galaxy S III Original Android Development] joe_donkor:
+1
[Galaxy S III Original Android Development] Striatum_bdr:
As I'm new in this phone didn't have time to test but STweaks (search it's thread on xda) should do it perhaps.
[Galaxy S III Original Android Development] EViollet:
I just had to say thank you for making this phone exactly what I expected it to be : very fast...

Running Omega and this kernel is really an awesome combination.

Regards

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] codo2003:
Hi there

I flashed the latest version of this kernel with Omega JB ROM and everything seem to work well. Except my WIFI connection is not working, It keeps trying to connect to my modem without luck.

Help me to solve this problem and keep this nice kernel.

Thanks in advance for your help.
[Galaxy S III Original Android Development] EViollet:
What channel does your Wi-Fi router use?

Try a channel < 12. Should work everywhere.

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] AndreiLux:
* Removed.

New hotfix version 23.4:

- Fixed GPU threshold sysinterface displaying wrong values

- Update Wifi drivers from Note 2

- Fixed packet filter settings (Unicast & mDNS again)

- Insecure adbd
[Galaxy S III Original Android Development] codo2003:
I tried the hotfix 23.4 and still the same, NO LUCK.

I tried siyah kernel and it is working fine..

I love the memory size...

Please HELP.
[Galaxy S III Original Android Development] AndreiLux:
Did you try the one I made before my post edit or the one I uploaded on the first page? Because that one is now identical to Siyah in Wifi.
[Galaxy S III Original Android Development] codo2003:
I tried the one on the first page and it's not working. Any suggestion?
[Galaxy S III Original Android Development] mariosraptor:
Is this with every router? How come we don't have any?
[Galaxy S III Original Android Development] codo2003:
I have a router with channel 11 and a repeater with channel 6.

Both are not working.
[Galaxy S III Original Android Development] 9Lukas5:
Now I'm using the pro version of voltagecontrol. Now I'm able to set it lower, thanks.

L

Gesendet von meinem GT-I9300 Galaxy SIII
[Galaxy S III Original Android Development] tvhak:
just flashed 7.2 all went well

wifi is working.

voltage in setcpu cant be set to 600

voltage in voltage control van be set to 750

great thanks
[Galaxy S III Original Android Development] 9Lukas5:
@AndreiLux, could you make bootanimation.zip's working?

L

Gesendet von meinem GT-I9300 Galaxy SIII
[Galaxy S III Original Android Development] Warm_ice:
I installed this kernel but honestly i have no idea how to make use of it. My benchmarks are stil the same :p
[Galaxy S III Original Android Development] jake:
Dude you have no idea how stoked i am to see you here, again :D
[Galaxy S III Original Android Development] Tectas:
Noticed a small thing, maybe just a view issue, but want to report anyway.

Antutu information shows with your kernel a triple core instead of the quad core.

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] Anthropologic:
Uhm, how I can flash this kernel? Via Odin??

Sorry, but it will be my first right samsung. :rolleyes:

Friendly greetings
[Galaxy S III Original Android Development] Tectas:
Yes Odin or mobile Odin.

Just use pda at Odin or kernel at mobile Odin.

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] AndreiLux:
The cores turn on an off often and sometimes the apps catches it with the core off and reports it having less cores than really there, don't worry. If you benchmark something fast then you'll see that the score is still as it should be.

Odin under PDA. Don't use it if you don't know what you're doing.
[Galaxy S III Original Android Development] AndreiLux:
Latest version now has overclocking up to 1800MHz. Please do not ask for 1900 or 2000MHz as those are not stable at all.

Keep in mind that running such high frequencies will eventually trigger thermal power control and downclock your device, so do not be surprised if suddenly benchmarks are lower.

I strongly advise against using more than 1600MHz (hell even more than stock frequencies), as the power requirements are growing exponentially. And we just don't need that kind of performance. If the phone is not stable, it is not my problem as it wasn't binned to run at such speeds.
[Galaxy S III Original Android Development] Cristiano Matos:
Probably silly questions, but there it goes

Auto root?

Instal recovery?

Triangle away works?

Thanks in advance.
[Galaxy S III Original Android Development] MrPhilo:
Flashed using Mobile Odin, all good so far.

Imo it's stupid to overlook the cpu, it's already fast enough. Anyways you think we can achieve higher than 500Hz for the gpu, I mean tegra 3 is 533mhz the gpu on a 40nm..
[Galaxy S III Original Android Development] AndreiLux:
I don't consider root essential as that can be done in the recovery package that for example Chainfire provides. We have separate recovery and kernel images on the S3.

Triangle away works.

I agree that it's stupid, still people ask for it, this is just to stick a sock in their mouth and for pedagogic purposes to learn what the CPU is capable of. GPU overclocking is already in the kernel, but probably as with the S2 it only accepts certain valid frequencies, which we haven't found yet, feel free to test it.
[Galaxy S III Original Android Development] js8:
Personally on a monster performer like the S3 I like the idea of UC/UV much more than OC. Would be great to see the phone last a week on a single charge :))

Andrei - Thank you for this great early effort on the kernel.
[Galaxy S III Original Android Development] ptichalouf:
Work great with omega v4, great job :-)

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] tvhak:
isn't this great? just look @this..
[Galaxy S III Original Android Development] silitek:
+1 nice benchmark;)
[Galaxy S III Original Android Development] F1tty:
thanks 4 kernel runs well :)
[Galaxy S III Original Android Development] sak500:
Great stuff, i've done @ 1.6ghz slightly lower than ur score. What speed u're using?
[Galaxy S III Original Android Development] tvhak:
note sure what the speed was there.

if i use 1700 and PegasusQ/noob with 500min and max 1704 i have 16333
[Galaxy S III Original Android Development] AndreiLux:
How about this.
[Galaxy S III Original Android Development] kenzolo:
We have to flash 23.4 or this One? (23.5)

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] AndreiLux:
This is just for the Wifi guy for testing. Versions for general release are in the first post.
[Galaxy S III Original Android Development] codo2003:
Still the same my friend..

Even Franco Kernel does not connect..

Siyah Kernel connect as soon as I start my device.

(( I can try any fix you post ))
[Galaxy S III Original Android Development] KennyLegend:
Weird... No wifi issues here on wireless modem or 2 different wireless routers in my house. Also works on my sisters modem and router.

Have people tried setting static ip addresses?
[Galaxy S III Original Android Development] tvhak:
Not sure if its of any help but. A lot of people have Wi-Fi problems since JB.

even i had it. I solved it by putting Wi-Fi on phone on static and put my modem on automatic channel. It did not matter wich kernel i used. And had it only with JB

Ps. You can allso try the free app. Wifi fixer
[Galaxy S III Original Android Development] jayden2009:
Dont have issues either...maybe it's the modem it self ...you can try and set it to wpa only see what it does ?

Verstuurd van mijn GT-I9300 met Tapatalk
[Galaxy S III Original Android Development] kenzolo:
Coming from 23.3 in the system/etc/init

I have only

s92omega

s99supercharger

1)Is It normal that there is no script related to your kernel?

2)Which file should I erase before installing the 23.4?

Thanks in advance

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] AndreiLux:
I don't push anything into init.d, no. You don't have to delete anything.

Personally, I advise against using Supercharger. I don't know what the Omega script does.
[Galaxy S III Original Android Development] mariosraptor:
Why should there be a script for the kernel?

The kernel supports init.d. you can add your own scripts there for whatever you wanna do.
[Galaxy S III Original Android Development] codo2003:
Now it connect to my modem, but takes time to connect.

It does not connect to my repeater (hotspot from the modem).
[Galaxy S III Original Android Development] nodstuff:
Why not?

if you don't mind me asking.
[Galaxy S III Original Android Development] kenzolo:
23.4 so smooth!! :eek:

Great work:thumbup:

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] AndreiLux:
All it does is to **** with the memory values and screw with some priorities, if that even works on latest Android. zeppelinrox acts like a 15 year old scriptkiddie which he probably is and I find it a pity people use his churned out nonsense. I mean, just look at this crap. Stay away from it. Anyway that's just my opinion and you do what you want.
[Galaxy S III Original Android Development] androb0t:
It seems a lot of people got wifi connection problem since JB whereas I never got one... Hmm
[Galaxy S III Original Android Development] :
A little rough, but I think it's true. There's no such thing as magics. I've stopped using scripts of the kind a long time ago.

One good example of false promisses, in which most people still believe, is the one where you limit your screen-off freqs with scripts and apps to save battery. That's a myth, it's tested that it can even make things worse.
[Galaxy S III Original Android Development] eric-filth:
I agree 100%

This scripts are false "true"

Enviado do meu GT-I9300
[Galaxy S III Original Android Development] mattiadj:
Is this kernel smother than siyah?

How can I set tweaks expecially in sound as if siyah?

Thanks

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] SleemLDJ:
I don't have one either. Just installed 23.4 and I'm still good on ARHD 11.0.0
[Galaxy S III Original Android Development] AbuYahya:
thanks for the kernal (22.3) running smooth.

going to try the more recent one but concerned about the screen flickers.

Is it due to a default setting or only if the buggy feature is enabled (screen freq I read somewhere) ?

also Is there a way to wipe init.d scripts when getting into reboot cycles. (other than a restore or hooking up to a PC ) ?

thanks
[Galaxy S III Original Android Development] nicregi:
Hard to say. Self preference I would say. Give it a try and you will know. Pretty good I would say.
[Galaxy S III Original Android Development] androb0t:
23.x has no more flickering screen nomore....
[Galaxy S III Original Android Development] mmse88:
I have ZERO problem with this kernel:p
[Galaxy S III Original Android Development] ginzo:
23.4 flashed and I noticed 1 more line on My Wi-Fi icon :D

And I have the modem on 2nd floor and I am where usually receive 1 or 2 lines....! Thanks a lot!

《live!》from my Galaxy S3

Rom: Wanamlite 3.7

Kernel: Perseus 23.4
[Galaxy S III Original Android Development] yokbob:
Is it possible to use eargasm with this kernel???

Envoyé depuis mon GT-I9300 avec Tapatalk

---------- Post added at 07:56 AM ---------- Previous post was at 07:50 AM ----------

Is it possible to use eargasm with this kernel???

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] kenzolo:
I can confirm ..I have better wifi signal

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] GrimPivo:
Sorry, not found in OP: is there any app for Perseus kernel configuration included?
[Galaxy S III Original Android Development] leamoor:
No,but you can via setcpu and script to mangement:p
[Galaxy S III Original Android Development] Chris_84:
http://xdaforums.com/showthread.php?p=32174646

Throwing out of the window from my flying Ferrari killer S3 :P
[Galaxy S III Original Android Development] gazou_hb:
Dear all,

It's possible that i install this new kernel with the official stock rom xxdlib?
[Galaxy S III Original Android Development] yokbob:
Many thanks!!! but it is a bit complicated for me... where could I find the eq?? Is it in the settings of my music app or with dsp??

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] beaver2233:
Yes.
[Galaxy S III Original Android Development] Ttblondey:
This is my first time using perseus kernel with Omega Rom.Well it works. Need to try fora few days.
[Galaxy S III Original Android Development] nodstuff:
OK that makes a lot of sense, I always found the supercharger a little dodgy to be honest but you always see people saying how great it is, blah, blah, blah.

It's good to get an honest and educated opinion on it and put the myth to bed once and for all.

Thanks man.
[Galaxy S III Original Android Development] Ttblondey:
It doesn't work with Extweaks.:confused:
[Galaxy S III Original Android Development] mmse88:
I am using your Kernel and thanks for your work.

But I don't think you have the right to comment or insult anyone's work even they are good or crap. Or else you have any full data or to prove it's definitely crap then I will agress your words.

Otherwise, that sounds you are very uneducated. *sigh*
[Galaxy S III Original Android Development] JYJY:
Care to explain why you insult gokhamoral's work? Oh the irony.
[Galaxy S III Original Android Development] mmse88:
Did I insult him?

Did I ever say his work is crap kid? He is the one who call his supporters asking stupid quesrion.

Be reasonable kid.
[Galaxy S III Original Android Development] gazou_hb:
find the link with DSP Audio

http://xdaforums.com/showthread.php?t=1709497