yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] AndreiLux:
No.

Currently we have 2 different ways to feed the clock to the GPU, one is to revert to the Orion platform method which would be the same as the Galaxy S2, including having clocks only going up to 400MHz, or in other words having quotients of integer divisions of 800MHz. The other one is the one currently on the S3 and that one is currently very ... strange. Currently there isn't any successful way of changing clocks to any meaningful frequency besides the stock ones. We don't have any documentation or information available on the clock generators or dividers and the drivers are haphazardly enigmatic about that.

Furthermore, I think we have fine-grained frequencies enough for the GPU. There's a step roughly 90MHz and it should be enough for all available games no matter how old they are; there is no point in having finer grained steps as we don't really have the same type of scaling as on the CPU. Keep in mind that the GPU has it's own separate integrated power management which turns off pixel processors in low load so we have internal hot-plugging on top of DVFS and lowering the first frequency step doesn't seem to bring as much power efficiency as previously thought. On the S2 I couldn't measure hardly any difference in idle.

It's a pity because it would have been neat to push the GPU to some higher ridiculous frequency for fun, but for now that's not possible and you will have to make due with undervolting only. Maybe we'll find a way later on.
[Galaxy S III Original Android Development] knights.JayTana:
Thanks for the heads-up... Miss your updates;)
[Galaxy S III Original Android Development] Siberian Tiger:
Hi, this Kernel it's featured on the Index of KERNELS http://xdaforums.com/showthread.php?t=1674286

Any observation please send me a PM :)
[Galaxy S III Original Android Development] AndreiLux:
New version, changelist in first post.

This should help battery consumption by some bit, at the cost of some fluidity. I tried my best to balance the two to some nice level, but I'm sure there's some tweaking needed.

I would appreciate criticism and evaluation of the smoothness of the kernel and how it compares to others.
[Galaxy S III Original Android Development] simone201:
Great update Andrei, but i was wondering why u have removed the "touch boost" feature, that is also now included into Android 4.1 in some way....this is what makes our phone so silky smooth :)

For the rest, great update really, i might take a look too at those flexrate options
[Galaxy S III Original Android Development] nickwarn:
Was going to try the new kernel but i cant download it, getting the - 404 Not found - error from link. Please check
[Galaxy S III Original Android Development] AndreiLux:
XDA seems to be having some problems, not my fault.

Here's a mirror in the meantime as long as that doesn't work: https://www.dropbox.com/s/x21yj374lkpt08b/Perseus.alpha16.tar
[Galaxy S III Original Android Development] hazri1974:
Is it compatible with aosp/aokp rom or stock sammy rom only?...Tq...
[Galaxy S III Original Android Development] AndreiLux:
Stock only for now.
[Galaxy S III Original Android Development] nobnut:
So far... so damned good.

Me likey the latest beta!

Thank you.
[Galaxy S III Original Android Development] AndreiLux:
By the way, usually I regard alpha as being something feature-incomplete, and beta something "to-be proofed before release". Right now I have a certain set of functions in mind but that won't be complete for a long time, so don't be alarmed by the "alpha" tagging, as it's just some personal naming-scheme. I'm running the kernel as a daily driver and have absolutely no problems with it, and so far I've received no bug reports in 2 weeks.
[Galaxy S III Original Android Development] zodiaxe66:
Are all xda links down.I get a 404 request error.from the links I've tried

Dam, I need to lean how to read. Thanx m8
[Galaxy S III Original Android Development] nobnut:
My bad... my enthusiasm caused me to jump to the second letter of the Greek alphabet, totally overlooking the first. Hence the 'Beta', rather than the 'Alpha' :)

EDIT: I'm extremely impressed with the overall user experience, smoothness and scaling... sleep is this kernel's second nature. Graphics and CPU intensive tasks are executed effortlessly. I have a feeling that battery efficiency will be great given time to test.

Benchmark junkies might as well stay away though. I could score higher on Antutu using the digits on both my hands... not sure why (and I don't really care), but a very low score (5xxx).
[Galaxy S III Original Android Development] sawgent:
thanks
[Galaxy S III Original Android Development] xmRipper:
Please make a version for Clockwork Recovery. Easier to install.
[Galaxy S III Original Android Development] leftheodo:
No it's not if you use Mobile Odin
[Galaxy S III Original Android Development] Ariozo:
Great work on latest update, Andrei.

Flashed it last night and so far very smooth and quick.

Keep upp the Great work...

Btw. For mobil odin, i should say all folks that like to flash their Phone should get that one... :)

Skickat från min GT-I9300 via Tapatalk 2
[Galaxy S III Original Android Development] AndreiLux:
Yes you fall under the same category as the S3 users.
[Galaxy S III Original Android Development] Frag1le:
Can you tell us more about this new thing you're working on?

Sent from my GT-I9300
[Galaxy S III Original Android Development] AndreiLux:
I'm trying to find out how Samsung bins their chips out of the factory, and to see the correlation between the ASV voltages and applied body bias voltages. The whole thing is a bit complicated and I'll have a thorough explanation once its tested and done. Most of the important data will come from the Note 2 though.

In short, in the end you'll be able to undervolt even lower and overclock higher.
[Galaxy S III Original Android Development] Frag1le:
That sounds very interesting. I need me to do some reading.

Sent from my GT-I9300
[Galaxy S III Original Android Development] Stivikivi:
Intresting that you can undervolt lower from 200 - 400 than me and from above not :eek:
[Galaxy S III Original Android Development] AndreiLux:
The difference is only 50mV between our two chips at those frequencies, the rest you're way below me. I ran the phone at 687.5mV stable during the first few weeks, but as it aged I had to raise it a bit. I could potentially explain why yours can't handle 300 & 400 higher, but that would go against what is happening with 200.... Anyway I need more data, and especially from the 4412 Prime / Note 2 users.
[Galaxy S III Original Android Development] mamba720027:
How to determine which ASV group you're in ? Like what to look for? Closest matching ASV group that correspond with user UV?

Sent from my GT-I9300
[Galaxy S III Original Android Development] omniwolf:
compare your stock voltages with the table here:

https://github.com/AndreiLux/Perseus-S3/blob/master/arch/arm/mach-exynos/cpufreq-4x12.c#L374
[Galaxy S III Original Android Development] AndreiLux:
Just put in your default voltages for 1400 and 1300 as how STweaks displays in the label description and I'll fill in the ASV group for you.
[Galaxy S III Original Android Development] mamba720027:
Thanx i figured it out,stock voltage of 1400mhz &1300mhz in Stweaks,whichever ASV group it corresponds with thats gonna be the ASV group I'm in :)

This also helped me to figure it out because I forgot Stweaks displays the default voltages.

Sent from my GT-I9300

---------- Post added at 07:22 AM ---------- Previous post was at 06:25 AM ----------

I was doing some reading myself to find out about what Andrei mention and so far I came across a .pdf with some explanations and interesting things which I linked below.

http://db.tt/bAHPjSug

http://db.tt/Zx5ieGBa

Sent from my GT-I9300
[Galaxy S III Original Android Development] eden1988:
Hi Andrei, I would like to help you in data collection, my default voltage is ASV2 under "asv_voltage_step_12_5[CPUFREQ_LEVEL_END][12]".

I've tried -100mv for all the frequencies ranging from 200mhz to 1400mhz but it wasn't stable and I had random reboots at times. Now I'm currently at -87.5mv and haven't had a single random reboot yet, hope this helps you :)
[Galaxy S III Original Android Development] Tenacious:
Phone was charging over night and this morning everything is fine phone didn't reboot I'm still using my costume voltages, not sure is this something random or it's becose of uv.

@Andrei anything in kmsg that I posted?
[Galaxy S III Original Android Development] habylab:
You say most will come from Note 2, is this other info or the same you are asking of us but to Note 2 users? Far less data from them at the moment.
[Galaxy S III Original Android Development] omniwolf:
if you get reboots or freezing, AND you undervolt, the first step is to remove any undervolting and test for a few days. There is no point reporting crashes if you modify the default settings of the kernel. set it back to stock and see how you go.

he's asking for the same info on the Note 2. unfortunately at the moment there are way more SGS3 users than Note2 users. just the way it is.
[Galaxy S III Original Android Development] Tenacious:
That is not the issue here.

Little summary.

It was discussed that possible cose of this is uv, but like I said in my previous post I keep my uv the same as when I had this happen and it didn't repeat so maybe there is something else cosing this.
[Galaxy S III Original Android Development] fastcx:
Can I know the reason to not have FIOPS? is it very similar to cfq?
[Galaxy S III Original Android Development] mamba720027:
Read the op please and do s search in this forum

Sent from my GT-I9300
[Galaxy S III Original Android Development] simmer14:
why is my phone seeing the usb charge current as 899 mA,it is in actual 450 mA ..

please explain .. because it is not possible to achive that much output from usb 2.0 port without any hardware modifications ..
[Galaxy S III Original Android Development] danarama:
It allows people with USB 3.0 not to be stuck at < 500 mA. If you have USB 2.0, you have nothing to care about as the mod is not really for you.
[Galaxy S III Original Android Development] MuertoKo:
You can't see the real charging rate on a Samsung device. On HTC you could check the mA with current widget and so on, here those will just show the value which the device sets, not the real charging value.

If you charger gives 450 and your device can charge up to 900 it will be charging at 450 or less, just showing the max. Allowed value on the añp

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] nikhil18:
Op can you please keep the maximum gpu frequency to 700mhz because if I overclock the gpu to 740mhz glithes start occurring on the screen
[Galaxy S III Original Android Development] fastcx:
I'm asking why it's not included anymore, and is it because it's very similar to cfq. FIOPS isn't common in most custom kernel, why it was included in the first place and why it's taken off now.

You aren't helping, and ROW certainly isn't the better performer even compares to cfq in smoothness with IO load, e.g. installing apps, background updates, etc. Our in built nand memory perform very well in read, we do not need further prioritizing read, what we need is better logic in prioritizing write which cfq logic able to reserve priority for write without noticeable lag compares to ROW is daily usage.

Benchmark usually do not tell the whole story especially in real world usage, and I repeat, write is more important than read in our current system. Any scheduler that prioritize read just aren't what we really need.

P.s. our system may run flash drive, but the performance isn't SSD level, bandwidth around 25mb/s write and 60mb/s read isn't spectacular by any means. I've tried noop,deadline, zen, row, none of them perform well under load compares to cfq.
[Galaxy S III Original Android Development] mamba720027:
Its already mention why FIOPS was taken out in your quote. As for what you think is better that's your opinion no one is asking u to use row or any u dislike if its not up to standard for you. And cfq Is their for you to use.

Sent from my GT-I9300
[Galaxy S III Original Android Development] Anakha56:
If memory serves, the reason why it is not included is because of issues with exfat file system. Andrielux (sorry if I spelt the nick wrong :P ) mentioned that he would look at porting it in but I have no idea how far along he is with that.

Side question how can I stop the battery getting hot while charging? Either while its in use (navigation mainly) or just sitting idle. I have already applied undervolting by 75 increments on the cpu, will applying the same to the gpu keep the temps down? Or must I just live with 45-50'C? :P
[Galaxy S III Original Android Development] mamba720027:
Try the default kernel configuration first then if your phone overheat on charge,undervolt and see if it helps.

Sent from my GT-I9300
[Galaxy S III Original Android Development] boulek:
Is it ok if I clock maximum gpu to 550mhz ? Or it is much for it ?
[Galaxy S III Original Android Development] mamba720027:
First clock it without UV then run phone few hours and see if its stable. If stable proceed to do anything else.

Edit And yea if its stable then its not too much. Also do not check "set on boot" when testing for stability.

Sent from my GT-I9300
[Galaxy S III Original Android Development] ElixR:
EDIT: wrong thread, lol sorry
[Galaxy S III Original Android Development] mamba720027:
Not possible cause,it is one of the cause of such problem. Which is why you should try default stock voltages before reporting such problem. It can be caused by a random activity in the background and cause the phone to go into sod. That's why when undervolting it takes lots of time to test for stability.

Sent from my GT-I9300

---------- Post added at 07:14 PM ---------- Previous post was at 06:53 PM ----------

Their is another method that you can use to get 700mhz using terminal emulator. The instructions are in the OP. Also 640mhz is not that bad if 740 does not work for you.

Sent from my GT-I9300
[Galaxy S III Original Android Development] Anakha56:
Thanks for the response :). The reason I tried uv was because it was getting hot. If I uv to deep do I just re flash the kernel from recovery to reset the settings?
[Galaxy S III Original Android Development] mamba720027:
In Stweaks,just go to the last tab to the right and theirs the option to reset all settings to default. Also you can look at the default stock voltage listed right next to each frequency and adjust them accordingly.

Sent from my GT-I9300
[Galaxy S III Original Android Development] Anakha56:
What I meant was if I undervolt to far too the point of the phone not booting into the OS would a kernel re flash sort me out or would it have to be a nandroid restore? Never really played with undervolting and I am getting more and more curious about it every day. So besides the normal tip of small increments over a couple of days, any other tips? And no worries the links from a couple pages back are bookmarked for further reading when I get home from holiday. :)
[Galaxy S III Original Android Development] mamba720027:
Lolz,reading is good :p. You can download the zip from the link below and flash in cwm to restore profile to default if that should happen. Thanks to "Gundal" for creating the flashable zip and uploading it for us,which is also found a few pages back if people "read". :D

http://db.tt/OuLkjEfx

Sent from my GT-I9300
[Galaxy S III Original Android Development] duhhh:
sorry for this question,but supported ICS or not?
[Galaxy S III Original Android Development] sduford:
Read the opening post.
[Galaxy S III Original Android Development] siavash_Skh:
After flashing the lasted version (29.2) I had two suddenly reboot !

Before this I was on 29.1 and didn't have any problem.

Is it a known issue of last version ? I didn't change any setting !
[Galaxy S III Original Android Development] MuertoKo:
Pull your lasy_kmsg logs after the random reboot so he can watch them

I had a random reboot as well due to the cpu being unable to go to sleep or kinda (Andrei answered via PM) but he couldn't track the reason.

Every log will help :)

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] mamba720027:
Also use rootexplorer to go "system/etc/init.d" and check if their is any rom scripts in their with CPU settings and delete it. Could possibly also contribute to random reboots.

Sent from my GT-I9300
[Galaxy S III Original Android Development] boulek:
But the Stweaks has default settings direct button
[Galaxy S III Original Android Development] mamba720027:
That reset STweaks profile flashable zip is for if you screwup and end in a bootloop or stock on the boot screen and can not boot into phone to press the default button.

Sent from my GT-I9300
[Galaxy S III Original Android Development] siavash_Skh:
Perchance I had a random reboot and after about 10 min I made this lasy_kmsg log, I uploaded it.

There are some files, which one I should delete ?

All three reboot Happened when I was changing between active app by holding home button.
[Galaxy S III Original Android Development] mamba720027:
Well when useing a custom kernel those scripts mean nothing,I normally delete all so you can go ahead and do that then reboot.

Edit: normally 98complete would have CPU settings to apply on boot,and dunno what the GPU script is for,shouldn't be usefull with perseus. So yea delete all.

Sent from my GT-I9300
[Galaxy S III Original Android Development] siavash_Skh:
I deleted all files and reboot. And now wait and watch :)

Thank you so much. I will tell you the result.
[Galaxy S III Original Android Development] AndreiLux:
Please keep such replies out of the thread, I find them more cluttering than the posts they are responding to. Just answer the question.
[Galaxy S III Original Android Development] www1:
Andrei does s beam working on your kernel?

This kernel is awesome!!!!!

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] mamba720027:
I think it works,but just try it with someone when possible. Don't see why it shouldn't work.

Sent from my GT-I9300

---------- Post added at 01:10 AM ---------- Previous post was at 01:05 AM ----------

As far as I know it only supports jelly bean 4.1 and up.

Sent from my GT-I9300
[Galaxy S III Original Android Development] Bogazicili90:
[Assesment]

AndreiLux, thank you so much for your hard work! Your kernel is the best in terms of both performance and battery life! I detailly compared it with Siyah 1.8.6 and in terms of battery consumption they are the same. But in terms of performance and benchmark results. With the other settings remain the same your kernel has 2000 point higher at the 1400 MHz. However at that point i compared them with changing the I/O Schedulers. Because the points coming from the cpu and gpu performance are almost the same without changing the I/O scheduler. Your kernel gets 16600 point at 1400 MHz with sio scheduler ( It gets the higher) and it gets 18900 point at 1704 MHz with sio again. With other schedulers point is much more less. I tested them on NeatRom XXELL5. Battery has still 81% power even passing 24 hours. (I listened 45 min. music and used it 30 min. to make some settings and then put it for wait, no simcard inserted, wifi on, syc. on, no plane mode) Simply the best!
[Galaxy S III Original Android Development] duhhh:
where is download link for Alpha21 :eek:
[Galaxy S III Original Android Development] Pretzel Kleo:
Older versions are not supported anymore.

Enviado desde Samsung Galaxy S3 GT-I9300 con OMEGA v35 usando Tapatalk 2 Premium.
[Galaxy S III Original Android Development] duhhh:
Am I blind? I do not see it
[Galaxy S III Original Android Development] mamba720027:
Please learn to read and search before posting useless things like "wheres a download link",the post above yours already reply that old kernel versions are not supported and as such their is no download link in the OP.

Sent from my GT-I9300
[Galaxy S III Original Android Development] rulala:
Sorry, I see "Perseus alpha25 (23/10):

Raised and fixed USB, MISC charging rate to 900mA."

so ....Perseus alpha29.2 now is also USB, MISC charging rate = 900mA :confused:

anyone can tell me 29.2 charge_AC rate is how much mA? please....

and it's possible to let users to have a chance to change ?

sorry I ask this question...
[Galaxy S III Original Android Development] danarama:
The change log for each version only lists changes made in that specific version.

If you see a change in an older version, it continues to be in all newer versions too, unless it is mentioned that it was removed in the change log for a newer version.
[Galaxy S III Original Android Development] mamba720027:
Hi Andrei I notice the "Dynamic Screen Frequency Scaling" feature was removed as I do not see it as an option in setcpu anymore. Was wondering why the change and if its not a good idea to leave it to conserve power and keep the CPU cool at same time when user enable it.

Sent from my GT-I9300
[Galaxy S III Original Android Development] siavash_Skh:
Hi

LED indicator was working fine

But suddenly from morning it didn't work anymore ! !

I didn't change anything.

What happened ?
[Galaxy S III Original Android Development] AndreiLux:
I removed it since nobody was using it because of the flickering. It was a neat experiment but didn't work out.
[Galaxy S III Original Android Development] mamba720027:
Within rom go settings/display/led indicator. Check make sure the options are ticked off

for what you desire it to do.

Yea I figure and i used it a few days,hard to tell if it had any impact on battery. The flicker I notice mostly with white backgrounds like when reading. Interesting theory behind it though.

Sent from my GT-I9300
[Galaxy S III Original Android Development] granets:
USB transfer broken on alpha 29.2, at least for me. I can't copy anything neither in MTP nor in PTP mode. That pushed me to go back to Syiah. I'd love to come back to Perseus as I think this is the better of the two kernels. Keep up the good work.

p.s. I flashed the kernel again, rebooted my PC twice and re-installed all the drivers, but no dice. With syiah 1.8.6 - worked with no hassle
[Galaxy S III Original Android Development] xpandnz:
Where can I get stweaks that work with this kernel please?
[Galaxy S III Original Android Development] siavash_Skh:
I checked it before posting.

All options are checked.
[Galaxy S III Original Android Development] flinkebernt:
You can get this from playstore I believe.
[Galaxy S III Original Android Development] mamba720027:
From the playstore you can download the "led color tester" app and use it by entering a hex code such as "00ffff", set to test and turn off your screen to see if the led lights up as to know if it works or not.

I never encounter this prob before so if it doesn't work then I'm not sure if its kernel related,a bad indicator ,rom,etc. Maybe someone else may have better expertise on it.

Sent from my GT-I9300
[Galaxy S III Original Android Development] siavash_Skh:
Thank You

I will try it.

but when I turn the phone off the LED lights up.
[Galaxy S III Original Android Development] mamba720027:
Lights up with the app,then your led is fine. Can always reboot your phone,fix permission,just to make sure whatever apps use the led indicator works ok.

Sent from my GT-I9300
[Galaxy S III Original Android Development] nfsmw_gr:
Andreilux could you update post number 2 to include all of governor parameters if it's possible please?

Thanks.
[Galaxy S III Original Android Development] AndreiLux:
Some other time when I rewrite most of that, I'll need to do a big write-up fit the next version. The explanations in STweaks describe them fully, although it's very condensed, so just read them three times over when trying to understand.