yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9500 Original Android Development] Steve_max:
The A7 CPU clocks are mapped to A15 CPU clocks at half speed. In other words, if your CPU is set to 600MHz, it will actually be running on the A7s at 1200MHz. When it jumps to, say, 800MHz, the A7s will be off, and you will have the A15s at 800MHz.

So, the A7s run at 500MHz (?) to 1200MHz; but the kernel treats that as speed steps from 250MHz (?) to 600MHz. The A15s run from 650MHz (?) to 1600MHz, with the kernel readings mapping directly to their frequency.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
The A15's start at 800 MHz, there's nothing between 600 and 800. Otherwise correct.

By the way: /sys/devices/platform/exynos5-tmu/curr_temp seems to be a better path for temperature readings, it shows the four temperature sensors on the chip. I don't know their physical layout though.
[Galaxy S 4 i9500 Original Android Development] mw86:
Thank you Bala, Steve and Andrei. This is very cool how they run, I appreciate the run down on their mhz structure with cluster migration.

Andrei I can't wait to see the amazing additions you have in store once that mess of code is sorted. I hope it goes easier here on for you. The development of kernel is more than a lot can appreciate as in the time put in and the head banging moments.... Thanks for stepping up for the GT-I9500 which need some love indeed.

I kind of hope you will go back to implement OC steps even at 50mhz over stock as I've been observing this throttle setup is actually outstanding (of course i am sure you can modify to be further improved) and does a good job at chugging along kn a workload at whatever it can manage to keep within the cpus TDP. Indeed these A15 are incredible.

Thank you Andrei, this journey on this phone is not so rocky with such a great developer.

I know benchmark mean little in some ways I want to say this kernel does bench good even though there has only been slight adjustments as of yet. Indeed with Andrei at the helm it will be much more.

See spoiler for quadrant and antutu on a peak run
[Galaxy S 4 i9500 Original Android Development] sachinaik:
1.2Ghz : Ambient 30 : Ourside temp 22 :

Ran Antutu benchmark:

Temp avg : 78

Temp peak : 86

Score : 25k.

With 600 Mhz temps were really low : 62.

Score : 17k.
[Galaxy S 4 i9500 Original Android Development] DrReD:
wich soft for change clocks?
[Galaxy S 4 i9500 Original Android Development] sachinaik:
Android Tuner pro.
[Galaxy S 4 i9500 Original Android Development] mw86:
Or Voltage Control, Android Tuner (same maker as system tuner), rom toolbox, trickter mod, setcpu, kernel tuner, cpu tuner and many more.
[Galaxy S 4 i9500 Original Android Development] bala_gamer:
Ambient 30+c, outside 33c, @1.2 Ghz max temperature I got is 72(only during cpu integer performance test), score 25.2k

---------- Post added at 09:36 AM ---------- Previous post was at 08:44 AM ----------

Saw the changes in your github, thanks for your patience and contribution
[Galaxy S 4 i9500 Original Android Development] adyscorpius:
What Andreilux is making on his github could make porting CM so much easier for the CM guys. He's actually making the kernel from scratch by putting together the latest sources from everywhere. Amazing commitment Andrei. Really amazing...
[Galaxy S 4 i9500 Original Android Development] sachinaik:
Hmmm.... I got 14 deg more...:what:

Bala pls tell me if you were using the below custom counter :

/sys/class/thermal/thermal_zone0/curr_temp
[Galaxy S 4 i9500 Original Android Development] bala_gamer:
[MENTION=4124536]sachinaik[/MENTION]

this and the previous one andrei posted differs only by some milli seconds if im not wrong. yes im using curr_temp
[Galaxy S 4 i9500 Original Android Development] hamdogg:
Its possible.... under volting while overclocking to 1.7ghz.. (if its stable) But even then it may only work on 5-10% of chips..

So while fingers are crossed, reality is still at the fore front of our minds.
[Galaxy S 4 i9500 Original Android Development] drziddo:
[MENTION=4642591]hamdogg[/MENTION] Thanks a lot man.

Didnt post it in the other thread as I was thinking it is kernel related.

Thanks again for your help.
[Galaxy S 4 i9500 Original Android Development] matheus_sc:
in kernel 0.2 there a process kcompcached draining battery in standy
[Galaxy S 4 i9500 Original Android Development] brenogbi:
Can we expect a version for 9505?
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
I don't have the money nor time for the i9505.
[Galaxy S 4 i9500 Original Android Development] brar.arsh:
Thanks for your time fir 9500.. :thumbup:
[Galaxy S 4 i9500 Original Android Development] Easton999GS:
What if we all donated a ton of money so we could buy you a i9505 Device? i would gladly help you get one. This kernel looks kickass. unless time is still an issue =/ you seem like an Exynos oriented type of dev by looking at your past kernels
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
I don't want advance donations (nor are they allowed), donate for work already done. About 2/3 of my 9500 was paid by people who enjoyed the S3 and N2 kernel over the last year.

The Qualcomm ecosystem is filled with "developers" doing nothing else than pulling things off CAF with little or rare originality in terms of features, so for that matter I prefer the Exynos as a playground because the signal-to-noise (useful-to-bullshít) ratio is lower. It looks like the 5410 won't have nearly as much of a userbase as the 4412 and the S4 will be the sole device with it, it's a bit disappointing, but what's done is done.
[Galaxy S 4 i9500 Original Android Development] Rahulrulez:
Finally, glad you are contributing to I9500 community. I wanted to know if you managed to implement / did some proof of concept around In Kernel Switcher (IKS) in I9500 kernel sources?

Will try your kernel tonight..
[Galaxy S 4 i9500 Original Android Development] StoneRoses:
Only 2/3!!! Can't believe it. Your time and energy you put in this project should worth far more than that.

I use your kernel on Note II (now belong to my wife) and now waiting for the greatness of your kernel on i9500.

Thank you.

0EN02684P1679872E
[Galaxy S 4 i9500 Original Android Development] MuertoKo:
Hum sorry to come to this threat to share an OT question, but as far as you mentioned the fact that S4 will be the only device with 5410 I felt I could ask this here. Are you assuming then the rumours involving Note 3 to come only as SnapDragon 800 device + LTE as a posibility? It looks quite disappoiting... I expected something as Note 2, with 2 nice variants so as they did with S4...
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
The S800 rumour matches with the information I've got about the current state of their LSI business and what the mobile division decided. The S800 should be superior to the Octa in every aspect (Reasonably so for coming half a year later), so I don't see them doing two variants with such a difference between the two.
[Galaxy S 4 i9500 Original Android Development] MuertoKo:
Great I expected to get an answer like this actually, adding some info to the rumours :D Great to hear then, hope they do some nice piece of work to get one on October... We'll see, only bad is I guess I won't have Perseus there as Qualcomm seems to be boring for you :P

Thanks for the answer, and btw, in one of your posts I remember readinga bout A15 being superior to Krait 400 in terms of performance, which afaik is S800, and Krait 400 to be worse than A7's on consumption... Wouldn't it then be still better a REAL Octa-core than S800? Well, guess it's some techincal stuff that is preventing them to build a proper big.LITTLE chip able to run core migration so we'll have to wait maybe another year for the real experience...

We'll see! Thanks ones again
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
It is and probably still will be, but we're talking 1.6Ghz vs 2.3Ghz here. I'm not sure about power consumption between the two at those levels. But in any case the Adreno 330 will be faster (50% reportedly) and the chip's HEVC decoder is something of a big deal.
[Galaxy S 4 i9500 Original Android Development] MuertoKo:
Yep seen stuff about 4k capability... anyway I stop the OT here, and I can't but just hope they release the device we are waiting for this time... Even if those who got i9500 won't need that device, the ones who stay with i9300 may... "merchandisingly" need it (Hand-up here!). Had no idea about the Adreno 330 (hoping to be included in Note 3) to be such an improvement over the GPU of i9500, just wow! (As usual, nearly 95% of usual use won't use it really, but hey, that 5% is nice as well !)

Regards,

PS: Yes, 1.6 vs. 2.3 might be quite a difference, let's just expect it doesn't heat like hell, most annoying thing imho on nowadays smartphones, even S3 on Perseus heats after some Gps-game playing :P
[Galaxy S 4 i9500 Original Android Development] wwwwww22:
I'm no specialist but

Exynos octa is "overheating" as is snapdragon 600 in SGS4 & HTC One, tested with stability test. So modern approach is to build powerfull cores and let them work at 100% power for max 2 minutes (then chip is lowering clock due to temperature), it is good for benchmarks and for example browsing web.

Funny thing is that in almost every browser test Exynos is much faster than S600 and I don't get it. Tested stock browser and chrome, S600 can't even come close to 3700 in Octane, 8500 in Kraken, (650ms in SS). Even my Note 2 [MENTION=4149147]1.8[/MENTION]GHz is faster than S600 (and S4 pro) in these tests.
[Galaxy S 4 i9500 Original Android Development] mw86:
True both chips suffer high heat under load at max clock. What I noticed myself though is the exynos is setup for mor endurance at high mhz even throttled. The s600 is dropping clocks lower than the exynos needs so would seem endurance type loads are pulling the exynos ahead. Lool at Antutu, the sheer heat the exynos is taking and still chugging along is showing to give it one edge there. These chips may overheat but they aren't just shutting off without quite an effort where as i do believe woth the i9505 throttle it is hitting thermal shutoff more so in tests than the i9500.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Your questions are too far away in the future.
[Galaxy S 4 i9500 Original Android Development] bala_gamer:
[MENTION=4167023]AndreiLux[/MENTION]

any info on the progress? :)
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
I upload to Github whenever a large chunk is done. There's some things left though (just check the big temp commit). It's slow but it'll pay off in a few months when upstreaming to newer kernels. Wouldn't be possible otherwise. I'm also falling victim to my own stubbornness, I started doing exact commits for various things and actually updating to official code instead of using Samsung's drop. The last round of commits are all new and overwriting things from Samsung.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
I'm closing the thread until I actually release a new version. The last dozen pages have been totally useless and have nothing to do with the kernel itself.

I'm also disappointed in the kind of feedback that people have been reporting: This kernel is almost functionally equivalent to a clean stock kernel, there's nothing special to it and better would be better off with Wanam/Adam for the time being: I'd like to point out a G+ post that Entropy512 made a few weeks ago, I think the first paragraph appropriately hits the mark.
[Galaxy S 4 i9500 Original Android Development] bala_gamer:
[MENTION=4167023]AndreiLux[/MENTION]

was tracking all your work in github... kudos for all your efforts, frankly 9500 is nothing without you.

Resisted myself from posting this since i dont know whether you like this unwanted posts n all but couldnt resist anymore after seeing you finishing majority of your works in github and opening back this thread.. if im not wrong a kernel release is somewhere very near.. thanks once again.

Edit:

will report bugs and issues in this thread instead of useless posts like this :)
[Galaxy S 4 i9500 Original Android Development] razer1224:
i really like this commit

it would improve users battery life atleast

https://github.com/AndreiLux/Perseus-UNIVERSAL5410/commit/6b3011f115454843e64995e6e36714c61a47f1c3
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
I don't think you really understood what I did with the sources or what that commit is supposed to be. Just please stop wasting energy and making claims...

Now [MENTION=228377]Bala[/MENTION] and everybody else: Release will come when I fix some issues. My above post is still valid: Getting tired of reading nonsense.
[Galaxy S 4 i9500 Original Android Development] razer1224:
Sorry Andrei as i told this is a last day of using this device

Bye. -_-

So you have will one less shi..wateva
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Now on more serious matters:

What should have been a half-hour piece of work is starting to reveal itself as an enigma.

Added undervolting support per the usual interfaces, after screwing around with the IKCS way of publishing the fake virtual frequency table and handling that correctly, things start to get stupid after actually setting the values.

Patch is found here: https://github.com/AndreiLux/Perseus-UNIVERSAL5410/commit/8be104283da30bab440f0ba73f7be10db44bb7cc but is filled with debug outputs.

After trying to update voltages (even with the same values), the phone crashes on the next frequency up-scaling:

Considering the pre- and post-values are identical, this goes beyond my mortal comprehension of why it fails. If the assignment is removed, then it works.

I'm taking a break for today, so maybe some more insightful soul might figure out what I miss or do wrong.

Edit: Fixed it. I was sanitizing the trunkated millivolt values wrong and the new Samsung PMIC doesn't do sanitation in the regulator driver as we're used to in previous Maxim ones.

I'll release new kernel later today.

For anybody who pulled the non-working undervolt commit, I overwrote it on the repository with the new one.
[Galaxy S 4 i9500 Original Android Development] :
Anything new about getting this kernel to work on i9505? Loved your work on note 2
[Galaxy S 4 i9500 Original Android Development] MuertoKo:
Completely different device, different CPU and everything, you have a big bunch of devs on i9505 such as faux for example, go for them

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S 4 i9500 Original Android Development] :
Yup im using KT at the moment. Anyways hope that someday I could put this kernel cuz its the best one so far. Keep up the good work andrei
[Galaxy S 4 i9500 Original Android Development] cmd512:
Andrei already addressed this. PLEASE stop filling this thread with non-dev discussions about random bull$hit, I for one don't want to see this thread locked again!
[Galaxy S 4 i9500 Original Android Development] REVERSiN:
Iam sorry for answering instead of Andrei but currently the poor guy is BANGing his head on the table dealing with the Octa Exynos so a little time guys hopefully as he said when he comes through with these steps he is working on now he will start compiling kernels faster lets give him some time cause for the time being he is very busy (way too busy for us)
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Kernel is out. Report any bugs please.
[Galaxy S 4 i9500 Original Android Development] Xphoid:
everything seems to work... but whether you choose 1600MHz or 2000MHz while on antutu test CPU dont go beyond 1400MHz... and maybe scores dont mean anything, but with alpha 0 i was getting 30k+ but now 27k+ which is most probably directly related to being stick at 1400MHz

Edit: using Trickster Mod app to set UC/OC and UV values... UC at 1000MHz sticks... -75 for UV seems stable, -100 reboots...

and monitored cpu related things from cool tool while testing.
[Galaxy S 4 i9500 Original Android Development] skivnit:
Correct. Cool tool cpu monitor is stuck at 1400mhz.

Swyped from another galaxy
[Galaxy S 4 i9500 Original Android Development] matheus_sc:
Now can overclock a15 a 2000mhz?

edit: i test and really do overclok, but shutdown in final of antutu.

a bug i have in boot, when screen shows there no way to unlock, after screen is off unlocks normally(have this in v0 too)
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Sorry, forgot about that change:

Samsung cheats during benchmarks by enabling a thermal boost mode which raises the throttling temps by 10°C (90° -> 100°C). I disabled the permissions to this. Practical effects is things like Antutu will give lower scores. This is more realistic of actual performance and I will leave it as such. Benchmark freaks can enable the boost mode manually: /sys/class/thermal/thermal_zone0/boost_mode .

The first throttling speed is 1400MHz and that's why it spends a lot of time there during benchmarking.

Effectively, overclocking on this device makes very little sense unless you can achieve more thermal headroom with undervolting. I personally couldn't get over 1.8GHz on random loads, and couldn't get over 1.7GHz on benchmarking (Antutu 31300).

Nevertheless, the option is there for people who want to stick their phones into their freezers. For everybody else, stop being concerned about numbers.

This seems to affect only a rare number of people and I still don't know the cause. Just cycle the screen once and be done with it.
[Galaxy S 4 i9500 Original Android Development] Xphoid:
oh, dont get me wrong... i never concerned about scores or OC... just tested as per your saying and gave feedback... otherwise as far as i understand from your explanation this situation is completely normal... and if i leave at 1600MHz and UV than i will have fluid experience...
[Galaxy S 4 i9500 Original Android Development] machhho:
Every thing is perfect , thanks alot .
[Galaxy S 4 i9500 Original Android Development] Xphoid:
can you try smart pause while watching video?

smart scroll works perfectly but i guess there is something with smart pause...
[Galaxy S 4 i9500 Original Android Development] Trek55:
yes..I just tested smart pause..it worked. .
[Galaxy S 4 i9500 Original Android Development] machhho:
it is working
[Galaxy S 4 i9500 Original Android Development] cmd512:
Just flashed, everything looks to be working, including Smart Stay. UV'd every step 100000uV off the bat and no crashes yet!
[Galaxy S 4 i9500 Original Android Development] bala_gamer:
just finished flashing.. tried undervloting -75mv via nstools and all is good so far,uv does have some impact on temperature glad to see it reduced to some extent. tried 1.7ghz on antutu , it dosent crosses 1.4 ghz despite the temp below the throttle limit.
[Galaxy S 4 i9500 Original Android Development] Rahulrulez:
Disabling thermal_boost will cause any performance degradation? I don't give a f*** to any benchmarking tools.. I don't care really. All I need is smooth performance..
[Galaxy S 4 i9500 Original Android Development] Xphoid:
Performance is smooth, all is working including smart Screen pause everything...

No UC/OC but successfully UV'd - 90mV...

-100mV gave hotreboot while watching video...

One thing I realized is the values I set with Trickster Mod, does not affect values in S-Tweaks.apk... I guess S-Tweaks came with the kernel, isn't it? Which shall i count on?

And busybox pro.apk gives me "more than one copy of busybox is installed" notification when I run it...

SwiftKeyed from SGS4 [i9500]
[Galaxy S 4 i9500 Original Android Development] skivnit:
Idling is great I lost 3 prct overnight (8h40 minutes) with wifi on. Performance is smooth. However can't take screenshots anymore with palm swiping. Can anyone else try please?
[Galaxy S 4 i9500 Original Android Development] cmd512:
User error, I'm taking screenshots fine with my palm. Make sure you double check your settings to see if it's still enabled.
[Galaxy S 4 i9500 Original Android Development] B!GBOY:
how can we actually set cpu frequency? as you said i turned the boost mod on but now the maximum is 1200mhz

my previous kernel was fine working at 1600mhz
[Galaxy S 4 i9500 Original Android Development] bala_gamer:
no, its just limiting the thermal throttle to 80 or something instead of 90+ which will simply reduce 200mhz in steps from 1.6ghz, you wont loose anything whatsover in performance
[Galaxy S 4 i9500 Original Android Development] venorme:
Noticed improvement in charging speed

was from 5% to 100% in 2 hours and a bit

now from 5% to 100% in 1hour 35 mins

Also changes made by stweaks are not displayed in any other system monitor I have (android tuner, trickster)
[Galaxy S 4 i9500 Original Android Development] Xphoid:
I uninstalled Trickster and Android Tuner... Cause since tuned values for UV with Trickster Mod does not seen with S-Tweaks and S-Tweaks come with the kernel (re-installs on every reboot after you delete it with Root Explorer) including more detailed frequency distribution (little cores-big cores) it felt like more reliable to me...

And to check my setting, i installed SetCPU (since AndreiLux mentioned it in OP) after tuning with S-Tweaks and SetCPU gives the right values that has been set with S-Tweaks...

One more thing, just out of curiosity, i manually enabled boot_mode... and run Antutu @1,7GHz... still Cool Tool shows max 1,4GHz... rebooted the phone to see whether if this manually changing "boot_mode" start to show effect after reboot, bu realized it on reboot boot_mode value get backs to "0"...
[Galaxy S 4 i9500 Original Android Development] skivnit:
So-75mv on every step should be stable? On big and little cores?
[Galaxy S 4 i9500 Original Android Development] mflow:
the new kernel is working pretty nice :) . -75mV in S-Tweaks for 1,6Ghz, and it's pretty stable :) (and the rest too)

i can't seem to enable boost_mode tho, or my method of enabling it is wrong? (changed the '0' value to '1')
[Galaxy S 4 i9500 Original Android Development] gun@id:
zram

can't find zram.. is it diabled?
[Galaxy S 4 i9500 Original Android Development] venorme:
zram is not supported yet I guess
[Galaxy S 4 i9500 Original Android Development] GSeeker:
Alpha 1 was so good!

Until i tried to UV -100mV in STweaks, the phone became unstable and rebooted itself.

Then it stuck in bootloop.

I tried to flash back to ME1 stock kernel, the phone booted up normally.

And when i tried to flash Alpha 1 again, i failed. Everytime i tried, i failed, the phone stuck in bootloop.

But Alpha 0.2 is OK which i'm on.

I also tried to delete the data/cache of STweaks and even delete the app, it won't help, can't flash Alpha 1 again.

Any idea? Thanks~

update: delete data/.perseus folder, solved.
[Galaxy S 4 i9500 Original Android Development] so_ony:
make a fullwipe and flash again mate :)

wipe data & factory reset

wipe cache

wipe dalvik cache and flash again rom + kernel
[Galaxy S 4 i9500 Original Android Development] GSeeker:
Thanks mate i think this will work.

It would be better if there is a way not to fully wipe the phone though.:good:
[Galaxy S 4 i9500 Original Android Development] MuertoKo:
Delete perseus stweak folder, if you tick set on boot and flash alpha 1 it may be aplying the "bad" voltages and preventing you from booting. It's something in data/.perseus (hidden folder!)

Btw, -10mV shouldn't ever cause random reboots :S That's too little margin! U sure you hadn't applied -100mV UV? That would make more sense to me
[Galaxy S 4 i9500 Original Android Development] hamdogg:
Alpha 0.1

Peaked @ 100 degrees @ 1.6 Ghz.. ANTUTU 29215

Alpha 1

Peaked @ 94 degrees @ 1.4 Ghz... ANTUTU 27461

I'll have to fry my eggs on my stove from now on... cheers!
[Galaxy S 4 i9500 Original Android Development] GSeeker:
You're the man! Solved! Thanks so much bro~:good:

It was -100mV UV, my typo, sorry~
[Galaxy S 4 i9500 Original Android Development] Xphoid:
-87,5mV by S-Tweak app on all frequencies is all good &stable with me...