yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9500 Original Android Development] iede:
[MENTION=4167023]AndreiLux[/MENTION], do you have any plan to bring the flexrate request, sampling factor, up treshold differential, and cpu hotplug like the perseus S3 did? I'm used to use that feature on my S3 and that was great feature compared to other kernel.

Hope you bring that feature again to S4. Thanks :highfive:
[Galaxy S 4 i9500 Original Android Development] Alberto96:
Hotplug isn't need on our CPU.
[Galaxy S 4 i9500 Original Android Development] carlosm15:
As far i know 5410, doesn't need that feature because the powergating in the SOC...
[Galaxy S 4 i9500 Original Android Development] Alberto96:
Less software features that controls cpu is always better. Powergating is done by hardware directly. An useful feature would be different leakages (choose able via stweaks) for cpu voltages. My cpu have really low default voltages and a15 stable overclock is really hard to reach. Now I finally found best a7 voltages for 750 mhz overclock. Running really really stable. A15 overclock nothing, its just partially stable.

Another great feature would be Dynamic Fsync for best I/O performance.
[Galaxy S 4 i9500 Original Android Development] iba21:
Exactly

Exactly since this octa doesen't have the hotplug logic
[Galaxy S 4 i9500 Original Android Development] alawadhi3000:
Whats in red is plain wrong, power efficiency goes way worse when you increase the frequency and voltage.

Refer to this Exynos power consumption data that Andre posted on B3D forums:-

Speed /CPU/Consumption per core
1600MHz A15	1860mW
1500MHz A15	1619mW
1400MHz A15	1293mW
1300MHz A15	1043mW
1200MHz A15	841mW
1100MHz A15	704mW
1000MHz A15	571mW
900MHz A15	455mW
800MHz A15	387mW
1200MHz A7	182mW
1100MHz A7	146mW
1000MHz A7	118mW
900MHz A7	94mW
800MHz A7	75mW
700MHz A7	60mW
600MHz A7	45mW
500MHz A7	35mW

The CPU under full load will consume 7.44W under full load [MENTION=1796504]1600[/MENTION]MHz, but will only consume 1.55W running @ 800MHz, so theoretically speaking if a task needs one hour to complete @ 1600MHz it will 7.44Watts, but if the max frequency is 800MHz it'll need two hours to complete and therefore consume only 3.1Watts, thats a big difference.

Of course you'll not see that big of a difference in battery life because the CPU rarely hits 1600MHz, but you'll notice a difference if you cap your max frequency to 1.2GHz (Like I do) and get rid of the high, power inefficient frequencies, most battery life increase will come from UV the highest A7 step (600MHz A7) and the lowest A7 step (250MHz A7) since the CPU will spend a lot of time there.
[Galaxy S 4 i9500 Original Android Development] iba21:
Wait.. what you sad is right.. but.. you have to remember one thing, more freq = less time to compile that thing.. so.. less time in cortexA15..

You spent more energy at that moment, but, system goes to idle earlyer..

If you read tom's hardware or similar you'll see more tests about it..

Btw.. i don't understand why someone whould get a little undervolt.. a good governor will not grow up to maxfreq if it's not really necessary (as like a similar as conservative governor)
[Galaxy S 4 i9500 Original Android Development] sorg:
It would be true if 1600MHz will consume only 2 times of energy need for 800MHz.

if table above is correct then you can see:

1600MHz - 1860mW

800MHz - 387mW

so, it's almost 5 times!

So, even if 800MHz will require 2x time to finish the task, it will consume twice less power!

Where 1600MHz can work 1hour, 800Mhz can work almost 5hrs.
[Galaxy S 4 i9500 Original Android Development] matheus_sc:
Thanks i try that, which rom you use?
[Galaxy S 4 i9500 Original Android Development] iba21:
Yep.. what you wrote is true.. but.. remember.. there's not the cpu in the hardware..

an example.. you have to open an app witch use a lot of performance.. a faster cpu can do it earlyer, so, less time spent to aliment gpu, ram, nand, sd, screen..

With 1/2 of power in theory you have 1/2 of performance, in theory..

A simple example.. you have to open a game.. nand has frequency too.. suppouse you underclock of 1/2 of all.. cpu gpu nand and ram

With a normal situation you load the game in 20 seconds..

With this new configuration you could spend more than 40 seconds.. 20+ seconds of free screen on

Screen has a power consuption as cpu has..

Understand what i'd want to say?

If you underclock the cpu, nand will be used for too mouch time at higher freq than idle, till "job" is finished, the same for screen

those situations ONLY with high tasks.. because.. for low tasks a GOOD governor will not ramp up at maxfreq..

That's why i sad it's unusefull to underclock..

If all is ok, if governor is good, with nornal usage you'll not go out of the A7.. or change on the first freq of A15.. with high tasks, faster is the computation, faster system goes to deep sleep

Another example.. you have to open a web page.. a big web page

If you load it in 1 seconds, and spent 10 seconds by reading.. you used the screen for 11 seconds.. and system goes to max power consuption for 800ms.. the other in idle..

In an ipotetic underclock.. the page is load in more than the double.. dont you think? Try..

You spent 6-7 seconds in low power consuption + 10seconds of reading..

16-17 seconds of screen on with 6-7 seconds of nand, gpu, wifi chip etc etc..

Sure.. cpu consuption was less, you only spent more time of other hardware for nothing

You have to remember, an half of cpu freq has a performance theory of an half od the nominal maxfreq.. in real.. try..

An half of cpu means slower cache, slower predictions, all is slower..

And sure.. tasks!! If you have a slow core linux will have some problems to compile tasks.. all is slower..

I hope you understand.. i can't do it better without using my mother lenguage.. it's so difficult right now..
[Galaxy S 4 i9500 Original Android Development] matheus_sc:
I try lower to 1.2 GHz and reduce volts of a7
[Galaxy S 4 i9500 Original Android Development] sorg:
CPU, actually SoC, which includes GPU as well, is most power hungry component. Other components can be disregarded if we are not talking about idle and very low power modes.
[Galaxy S 4 i9500 Original Android Development] alawadhi3000:
What??!

It doesn't need a power scientist to figure this out, as sorg said, the CPU consumes five times the power for twice the performance by going from 800MHz to 1600MHz, capping the max frequency will make the phone more efficient power wise and consume less energy even if it took more time.

Idling is irrelevant since they're both the same processor and consume the same when idling.

undervolting every step helps with the battery life.

Try what? These were the power consumption figures, not voltages.

With 1/2 of power in theory you have 1/2 of performance, in theory.. << Wrong.

Your example is also flawed, if you need one sec to render a webpage [MENTION=1796504]1600[/MENTION] MHz, in theory you'll need only two seconds to render the same page @ 800MHz, not 6-7 seconds like you said, the screen will stay on for one more seconds, which will consume much less than the CPU.

The CPU consume about 7.44W full load, the screen will only consume about 0.5W-2W (depending on brightness and colors).

Also NAND and RAM and the rest of staff doesn't matter, since the load will be the same anyway.
[Galaxy S 4 i9500 Original Android Development] iba21:
Try :thumbup:

Tom's hardware did those tests.. but.. i found it in italian..

Sure.. did those with an intel i7.. but.. the situation is quite similar

Btw.. we are offtopic.. i'll stop with this
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
As similar as a bicycle is to a motorbike.
[Galaxy S 4 i9500 Original Android Development] iba21:
Ye.. for the performance, yep :D
[Galaxy S 4 i9500 Original Android Development] gdonanthony:
Welcome back Andrei :) maybe some kernel problems of cm10.2 will be solved now a days (I hope so)
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
No.

Your rhetoric on using some tests done on a completely different architecture with vastly different power management to deduct a similar outcome is just wrong.
[Galaxy S 4 i9500 Original Android Development] iba21:
That's right.. but the problem was.. is right to underclock to have a less consuption? In theory yes.. but.. if governor do what it has to do, maxfreq will reach only in some condictions, so, the power efficiency will not be so different..

I can say one thing.. i had oneX.. and i create a mod for stock kernel witch locks the maxfreq from 1.5 to 1.3..

The screen on time changes from 2h30 to about 3h30

Than, i installed xm kernel, with mpdecison + smartmax governor.. with maxfreq at 1.5ghz (and all cores at 1.5ghz)

with that situation i could do 4h of screen on..

If i underclocked the cores to 1.3ghz, i didn't have more from my settage..

But the situation in simple.. stock tegra3 kernel used ondemand logic witch goes at maxfreq everytime.. so.. with an underclock i'll have more time in the underclocked maxfreq and not in the nominal maxfreq.. so.. less power usage

With modded kernel i used a similar conservative governor + mpdecision.. a pegasusQ like.. and my screen duration increses even if i didn't do an underclock

So.. do an underclock is usefull only if kernel has a poor ondemand logic.. but.. with a conservative one, it's quite unusefull.. it slow down system when it needs more power, and sure, it steals energy from hardware when system has to compilate that thing and user has to wait the acompleshed of the computation..

more time spent by waiting with screen on is time spent to aliment screen for nothing
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
You're giving me a headache, please stop comparing other architectures. Your examples don't even have anything to do with what we're discussing. This is not Tegra 3 which didn't even have any kind of proper idle (Or Exynos 4 for that matter). There's a dozen variations of Ondemand, the only one that ever went to maxfreq were those from 2+ years ago, and even then, that's just the initial burst scaling after which it scales down to a on-demand (hint hint) frequency.

Power per clock goes up with rising frequency. Cap the top frequencies and your power efficiency will go up. Simple as that.
[Galaxy S 4 i9500 Original Android Development] hathara:
andrei i not sure if you saw my post so i gonna ask againg

is a request by the way

in siya kernel on s3 there a option to change mah comes for usb and ac charger to make the battery recharge faster

do you think is possible do that do our s4 ?

exemple: change the mah comes from usb to 500 to 900!
[Galaxy S 4 i9500 Original Android Development] Alberto96:
In attachments you can find latest Perseus Kernel compiled from sources with Linaro Toolchain (2013.07 4.8.2) with Cortex A15 optimized flags.

Enjoy!
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Did you test the exFat modules on that?

Edit: That .img refuses to flash via Odin over here.
[Galaxy S 4 i9500 Original Android Development] Alberto96:
I flashed it via cwm :/
[Galaxy S 4 i9500 Original Android Development] mashaal95:
It doesnt work mate :(

Got stuck on bootloop for me...went back to the original 7.2!
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Something's wrong with that kernel if it doesn't pass Odin's integrity check. I never flash via CWM because of the sensorhub firmware shenanigans.

In any case, I haven't used GCC >4.6 because it gives alignment faults when loading the exFat modules.
[Galaxy S 4 i9500 Original Android Development] Alberto96:
Maybe bad upload, reuploading. Sorry :(

Well, im using exfat microsd and it seems working.

UPDATE: Reuploaded, check attachments.

UPDATE 2 : KERNEL REMOVED
[Galaxy S 4 i9500 Original Android Development] alandd86:
ist contain sound glitch fix?
[Galaxy S 4 i9500 Original Android Development] Alberto96:
Please explain something about this bug :confused:
[Galaxy S 4 i9500 Original Android Development] alandd86:
,, on perseus 7.2 was using youtube and the sound wasnt good like not clear !!but am in stock now and its normal again
[Galaxy S 4 i9500 Original Android Development] Alberto96:
I dont have this bug. Try my latest compiled kernel, maybe glitches are fixed for you.
[Galaxy S 4 i9500 Original Android Development] alandd86:
if u try it with maximum volume it appears as if ur phone's speaker is damaged !!
[Galaxy S 4 i9500 Original Android Development] Alberto96:
Here if you disable Speaker Tuning and set 0 DB Speaker Gain all is perfect :D Especially with my latest kernel, all seems smoother. I hope this isnt just a placebo effect.
[Galaxy S 4 i9500 Original Android Development] HassanM:
[MENTION=2386505]Alberto96[/MENTION]

Mate im gonna try your version of Perseus 7.2...
[Galaxy S 4 i9500 Original Android Development] alandd86:
stuck in bootloop ur kernel [MENTION=218829]ALBERTO[/MENTION] !!!
[Galaxy S 4 i9500 Original Android Development] sorg:
Can u give the link for exact toolchain you've used?

Post changes in compilation flags for A15 you've used.

Thanks!

---------- Post added at 05:58 AM ---------- Previous post was at 05:41 AM ----------

Can you explain this issue? I always flash through dd (using script from PC) - so may be i'm missing something important.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Kernels offload the sensorhub firmwares onto the sensor microcontroller each time they detect a mismatching version. Each time you enter recovery, the delay is caused because the device is flashing the chip. Exiting recovery flashes again the live kernel version for another delay.

This can be simply fixed by having the recovery bundled with a kernel which disables the sensorhub drivers, as I recommended to recovery maintainers on the Note 2. bigbiff had no issues in adopting this in TWRP and worked fine. But since on this device the only active recovery being developed is by Phil, and he blatantly refuses to do this or touch the kernel as if it's some kryptonite.
[Galaxy S 4 i9500 Original Android Development] sorg:
Ah, i see.

I compile TWRP by myself and use the same perseus sources for kernel.

I guess in this case sensorhub FW not updating each time i enter recovery.

---------- Post added at 07:03 AM ---------- Previous post was at 06:38 AM ----------

so i just need to remove this:

CONFIG_SENSORS_SSP_SENSORHUB=y

to avoid firmware update?
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Yes. Of course you need it in the live kernel for the sensors.

Here's a AOSP compatible dual-kernel of 7.2. However it breaks the touchscreen and I didn't yet figure out why or how. If somebody wants to look into it it would be welcome. The ramdisk is the main thing updated, didn't touch the kernel code so I have nothing to push.
[Galaxy S 4 i9500 Original Android Development] sorg:
I don't use AOSP/AOKP/CM (and have no interest to use them at all), so i won't be able to find the source of problem with touchscreen this time, unfortunately.

I hope you won't go with AOSP/AOKP/CM deep customization inside kernel sources like it was in Siyah kernel (several video drivers, gadget drivers, dual booting, etc..) - it was thrashed so much! I hope Perseus will remain as simple as it is.
[Galaxy S 4 i9500 Original Android Development] matheus_sc:
I really want aosp support, because touchwiz is no update with time.
[Galaxy S 4 i9500 Original Android Development] iamsachin:
Thrashed? Gokhan was praised a lot for it. Still remains one of the best kernels for S3 and S2 CM/AOSP
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
The modifications are minimal or non-existent for now, after things get working I don't plan on anything more with it. Intervigilium kept things clean.

Guess why I never supported CM on the S3. The whole thing was a convoluted mess. One of the reasons I even started my own kernel.
[Galaxy S 4 i9500 Original Android Development] iamsachin:
Poor documentation leads to convulated hacks. The problem this time is that most of the regulars of teamhacksung are on i9505. Right now only intervigil is working on it.
[Galaxy S 4 i9500 Original Android Development] sorg:
I9505 doesn't require any teamhaksung actually. CM was available on SD600 version right from start. Nothing to hack there since it's more or less generic QC SD phone. There is no teamhacksung anymore.
[Galaxy S 4 i9500 Original Android Development] bala_gamer:
[MENTION=4167023]AndreiLux[/MENTION]

Any ideas for adding dual boot support? That might be the only big thing I would love to see on the aosp side:)
[Galaxy S 4 i9500 Original Android Development] Alberto96:
Do not flash my kernel! Isn't working. For me it was working because i copied the incorrect one on my phone (BIG FAIL) (Same zip name but with stock 7.2 boot.img -_- ).

I see that kernel problem is in boot.img packaging.

[MENTION=4167023]AndreiLux[/MENTION] : What do you use for boot.img packaging ? (commands like cmdline, base address and utility).

UPDATE: I removed kernel from my post. I will release it when i fix boot.img packaging problem
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Please don't jump on the documentation bandwagon without knowing what it's all about. It literally had nothing to do with it.

Told you your packaging was wrong. I don't even use any parameters, the defaults are fine. I may suggest kernel basics 101 ...
[Galaxy S 4 i9500 Original Android Development] Alberto96:
Okok. Seems that cmdline isnt need. So i don't know whats the cause of incorrect boot.img packaging. I tried to unpack and repack kernel with Android Kernel Kitchen. Maybe is zImage the problem...
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Last version in terms of CM compatibility for now, I'm going back to Samsung. You can debug the touchscreen with an OTG mouse if needed. Everything else seems to work.
[Galaxy S 4 i9500 Original Android Development] chapruk:
thx andrei for your amazing kernel!

ive been waiting for your update..

is it work for samsung ROM? any changelog?
[Galaxy S 4 i9500 Original Android Development] gdonanthony:
so touchscreen will not work using that kernel ?
[Galaxy S 4 i9500 Original Android Development] Nasty_z:
It won't. You can connect a mouse via otg cable though. This kernel, I think, is released for other devs to debug and fix for cm
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
It's a dual kernel for both Samsung and CM. No functional changes. The Samsung side works fine.
[Galaxy S 4 i9500 Original Android Development] sorg:
I've just tried to compile using Linaro 4.8 2013.07 version without any changes in options.

Kernel doesn't boot. I see starting "Samsung Galaxy S4" logo flashing once in 3-4 seconds. Even, no boot animation.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Yes, told you this last time you asked me about it on Github about two months ago.
[Galaxy S 4 i9500 Original Android Development] Alberto96:
We have to try maybe with linaro 4.7.4. Im fixing this boot.img problem and then I can try.
[Galaxy S 4 i9500 Original Android Development] Nasty_z:
Andrei won't be working on cm kernel anymore. He released a last version of CM compatible kernel but flashing this breaks the touchscreen controls.

His exact words:

Here's the link to the kernel mentioned above:

https://www.dropbox.com/s/fh2hsaj62r81cga/Perseus-alpha8pre1-i9500.tar
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Can you people stop being ambassadors? I don't need PR representatives.

And I said last kernel for now, until the touchscreen thing is fixed.
[Galaxy S 4 i9500 Original Android Development] PsyCLown89:
Hi Andrei,

So I flashed Wanam's ROM which has his Adam kernal and some of the features are thanks to you. Since he isn't replying to my messages hoping you'll be able to assist me - a bit backwards, I know. It is your work, but at the same time it isn't really. Not sure whether he has changed anything etc.

The notification LED control through STweaks, how exactly does that work? I cannot seem to find anything under STweaks which relates to the LED notification?

Am I being daft and missing something?
[Galaxy S 4 i9500 Original Android Development] REVERSiN:
Andrei is right we need to stop the b******t CM isnt even stable and they might need to change drivers since gpu os laggy as I saw its not for a daily use so we can wait till he fixes it and release a new version for now I think CM users are better of with stock since it may have less issues than Perseus in regard of CM since 7.2 is great live with it its stable 98%
[Galaxy S 4 i9500 Original Android Development] Nasty_z:
Posted it in the wrong thread. It was supposed to go in the cm discussion thread. Well, whatever. No use to put it there anymore.
[Galaxy S 4 i9500 Original Android Development] gdonanthony:
i think something new is coming... F5 F5 F5 F5 :)

EDIT: can someone give [MENTION=4443334]Grarak[/MENTION] the kmsg for stock and perseus kernel ? i have no idea what is that and maybe he is willing to do something about Perseus CM... thanks
[Galaxy S 4 i9500 Original Android Development] lian_diary:
well done! I love the negative toggle, now I can use a "night mode" in Chrome and any other apps!
[Galaxy S 4 i9500 Original Android Development] maranello69:
Option to disable camera shutter sound is gone after v8 update, it wasn't working anyway, no worries...

Is there any proper way to disable that sound without setting the phone to vibrate or silent?

Maybe an option added to Stweaks?
[Galaxy S 4 i9500 Original Android Development] FireWall123:
I believe yes there is , but am not sure if this is the way you want it.

Using a root Explorer of your choice , goto /system => media => ui , scroll down and you'll see them v rename them or move to a safe place in case you want the sound back.

Edit : almost forgot , there are also other sound if you wish to disable for camera v

Hope this helped!

Vocaloid fan? Check out this thread!

http://xdaforums.com/showthread.php?t=2376692
[Galaxy S 4 i9500 Original Android Development] mw86:
Andrei this latest kernel is running great, I had not seen any reports of how it is. I think it is running phenomenal, keep up the great work. I'm not sure if placebo but I think you are doing good tuning the memory.
[Galaxy S 4 i9500 Original Android Development] noideaforusername:
It seems like the negative screen option cancels the smear fix.

Sent from the octa planet in the fourth galaxy
[Galaxy S 4 i9500 Original Android Development] Alberto96:
[MENTION=4167023]AndreiLux[/MENTION] I see that you fixed gcc 4.8 problems. That's great :) I will send you some pull requests about optimizations for cortex a15.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Don't bother.

The toolchain needs to be custom compiled for A15 due to conflicts with ARMv7-a and for the compiler to actually evict A15 specific code like IDIV. mtune also causes again bootloops.
[Galaxy S 4 i9500 Original Android Development] Alberto96:
Oh. Well I already compiled a linaro toolchain specific for cortex a15 but I set tune for cortex a15..... so it wont work. If you need some custom toolchain, let me know. Here is all ready for compiling. I will send you soon some other pull for other optimizations that wouldn't create problem with boot.
[Galaxy S 4 i9500 Original Android Development] jeromechrome1:
That sig tho... :thumbup::D
[Galaxy S 4 i9500 Original Android Development] gio_b:
No update to improve in ear dound in next release? Its all .the maxim for wolson dac?

Tks gio.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
I don't see much that could be done in terms of exposing (useful) hardware features.

You can always wait for Supercurio to release something in 2015.
[Galaxy S 4 i9500 Original Android Development] gio_b:
sig...:but did you intend 2014...i hope....

tks giovanni.
[Galaxy S 4 i9500 Original Android Development] prodigyX:
Delete or rename /system/media/audio/ui/shutter.ogg :good:
[Galaxy S 4 i9500 Original Android Development] NOORHASHIM:
Andrei why UBUBMG9 kernel is bug !? when i flashed it my phone is bug and no netowrk found and the imei is unknown and baseband too !!

thx ;)
[Galaxy S 4 i9500 Original Android Development] cgvelmax:
U Could use ViPER4Android

Enviado desde mi GT-I9500 usando Tapatalk 4