yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] ChronoMonochrome:
Good, but having no issues like bad performance/battery life not always mean that it can't be further improved. Even with no counting UV that can support 200 MHz, you can more benefit from reducing of usage higher CPU freq, where it's possible. That's why I use exactly Dynamic, other governors mostly uses too high CPU freq, when it can be reduced without causing lags. Some words about GPU(or, rather, APE boost) - instead of boosting CPU to e.g. 600 MHz, almost same effect could give boosting APE=100(with CPU freq 400 MHz), but IMO in terms of powersaving it's better than boosting only CPU. Or, rather, its effectiveness - with lower GPU freq you still have good UI performance, so no need for extreme GPU OC in some cases.
[Galaxy Ace II Android Development] ace2nutzer:
Yeah i know what u mean, it's maybe strange.. but @ 200Mhz and 400Mhz tested with varm = 1V and one time with 1,15V .. and still no difference in power consumption.. the same for GPU Clock .. from 100 - 400Mhz Zero difference, therefore i see no reason to decrease performance ;)

The difference beginns if u're using for min freq. a higher vbbx Voltage as 300mV .. ----> (400mV u can see difference in consumption.)

The Power consumption from 400Mhz @ 600Mhz both @ APE/DDR 50% is the same like same freg but changed APE 50% @ 100%.

But i'll test if scrolling whatsapp contacts is also smooth with 400Mhz and DDR/APE 100%.. and wich GPU freq i should use for that ??

There is also no need to use dynamic gov. for using 400Mhz at scrolling... u can do the same thing with the good old interactive gov.. just set min cpu freq @ 200Mhz, then go_hispeed_load from 600Mhz @ 400Mhz and adapted go_hispeed_load Value ... then u'll have the same :o and even better (more smooth).. because that input boost, touch boost etc. is only working good if u're touching the screen ... when the phone perform other visual things without need to touch the screen, then u'll have laggs because freq reamain @ 200Mhz with APE/DDR 50% :)

For example: Touch booster don't work when u're pressing the Home button or touching the back softkey .... :)
[Galaxy Ace II Android Development] ayas02:
40 , 45 and default 60mhz is stable but when im change cpu freq my phone goes reboot plz how can i fix it [MENTION=235339]chrono[/MENTION]
[Galaxy Ace II Android Development] xo.en:
Erm, funny thing - files i posted are same as yours, i am moron - i realized i did not have to edit these since i changed rom, dammit...

On the other hand, posting my old files has no sense, as some things changed since early 4.2.x roms...ehh, sorry for flawed try, sigh.

I thought it may inferere in your case, you know..i was not precise - i thought about turning off feature of wifi-based location(i.e in /settings/location), not wifi itself..
[Galaxy Ace II Android Development] S.AMU:
Yeah, but the sisconf file didn't exist in my rom.

Ah ok :) This is enabled on my rom. I will turn it off and going to do an outdoor test now.
[Galaxy Ace II Android Development] ChronoMonochrome:
Im my case setting min GPU freq to 200 MHz was only way to get that result of SOT(6.5 hours when watching video), that I've done few months ago. With GPU 400 MHz and APE50/DDR25 this can give approx 5-5.5 hours (I haven't did second test wholly, but after first hour of testing charge has dropped from 100% to 82%). Note that it's only about situation, when GPU is almost in idle and tests above confirms that.

Just did simple test with Nova launcher and fps meter (following GPU freqs are static):

1) 400 MHz - ~60fps

2) 360 MHz - ~55-56fps (60 fps constantly when scrolling)

3) 256 MHz - ~44fps (scrolling - same 60fps)

4) 192 MHz - ~35-37fps (the fun fact - even 192 MHz shows 60 fps when scrolling)

I've done test above also with game angry birds. For some reason, it always show 60 fps, but ofc you can notice lagginess with 192 and 256 MHz. Only with 400-540 MHz(low, high thresholds = 48, 200 respectively) it runs smooth enough.

fps in xplore, when scrolling - 30-45fps with these settings(which is still smooth as butter).

p.s. test were done on CM12, YMMV.

p.p.s don't use APE100/DDR100 constantly - it'll drain battery significantly more than even boosting CPU to 600 MHz. Boosting DDR serves nothing, you can let it stay as low as 50OPP.

p.p.p.s.after looking at input_boost_freq it turned out, that I've used 300 MHz (instead of 400 MHz) all that time :) input_boost_ms = 100 ms.

No laggs for me. You're probably talking about boosting only CPU.

Did you look at the code before saying that? I can say exactly opposite - it's binded also on some buttons https://github.com/mkaluza/project-...0dd41b7cc1455aca356637/cpufreq_dynamic.c#L994

As I said, Interactive doesn't fit my needs, since it uses signifantly higher freq than it needs.But I admit, it is a matter of preference. The same can be said and about everything above.
[Galaxy Ace II Android Development] ace2nutzer:
@up

this is very weird and it doesn't match with my tests ...

I just say especially "scrolling whatsapp contacts" because it seems that needs the most power to perform very smooth !

For Nova Launcher is even enough CPU static @ 300Mhz ! (and GPU don't remember .. it's long time ago ..) and DDR/APE 50%, if i remember me correctly.. but this is pointless because it's not enough for the other things, like settings scrolling, whatsapp scrolling etc...

Even with my mentioned settings some users are still complaining about not fully smoothess ...

see here latest post:

http://xdaforums.com/showpost.php?p=59591574&postcount=1628

if i would set your recommended settings, then users will kill me :D

It looks like that some users can't have enough about performance... Maybe we should set in kernel following by default: Min CPU 800Mhz max: 1100Mhz, DDR/APE 100% for all steps, and static GPU 500Mhz :D But then of course a 3600mA Battery is really needed :laugh:
[Galaxy Ace II Android Development] ChronoMonochrome:
Yep, it's impossible to get max performance and max powersaving at the same time :) Maybe good solution would be using a smanager scripts with optimizations for better performance or for better powersaving :)
[Galaxy Ace II Android Development] jhafner:
mAh

Hi;

When you guys talk about mah, what is the lowest(when phone is in deep sleep), and the highest(full load) a phone should withdraw?
[Galaxy Ace II Android Development] borkins:
For the fun, I started one script. :) The script extends the CPU clock, if the clock stays at max freq. for amount of time.

For example, when using the phone continuously ( for ex 8 sec ), the CPU freq. range will be extended to 1200 MHz and the GPU to 600 MHz,

and when the CPU clock is min for about 2 sec, the CPU will be locked to max 800 MHz, and the GPU max 400 MHz.

The amount of time ( time to OC / UC ) can be set by the user needs, so that would be something like a governor.

The whole idea of the script in the beginning was to extend the CPU freq. range ( for ex. 200-800 to 200-1200 MHz and also to OC the GPU ) automatically.

But the script is still on alpha stage, because I'm concentrated to finish the arm steps editor, which is working,

and now I'm trying to make it more regular user friendly, but overall it will be for advanced users, because the changes are in real time.
[Galaxy Ace II Android Development] greeceeeee:
Hi after flashed the latest version I install ace player + acestream engine and the app force closes...any thoughts?
[Galaxy Ace II Android Development] xo.en:
Hmmm, blackscreen bug started to happen again, after day since last reboot, just out of sudden...this is weird. There was no issue, then it just started to happen again..

On the other hand i am impressed by battery - "the DROP" is still there(loss of 8-10% in 2 minutes from full load is still present for me), BUT then batt lifetime is just...great(20% for 2 days, 0.8ghz/0.2ghz, zenx/fiops, lots of scripts used).
[Galaxy Ace II Android Development] gothicVI:
Same for me on kernel version 2.21.2...
[Galaxy Ace II Android Development] xo.en:
...issue is gone after reboot.

BUT it WILL be here, again, soon.

Now, why I am considering it as an issue - meet reboot drop - user, this is reboot drop, reboot drop - this is user, have a nice day:
[Galaxy Ace II Android Development] Alex_Gamer:
@up what screen type you have?
[Galaxy Ace II Android Development] xo.en:
s6d..

upd: whole day passed by - zero BS since last reboot. Isn't it weird?

Btw is it normal, that chronokernel app is not keeping its settings after reboot? It is not set to safemode, but it behaves like it was.
[Galaxy Ace II Android Development] ayas02:
hi [MENTION=235339]chrono[/MENTION] i have soem problem with my script in 2.21.2

here my script

#!/system/bin/sh

#GPU OVERCLOCK#

echo 0 > /sys/kernel/mali/mali_auto_boost

echo 1 > /sys/kernel/mali/mali_gpu_fullspeed

echo idx=17 > /sys/kernel/mali/mali_boost_high

echo idx=13 > /sys/kernel/mali/mali_boost_low

echo 640000 > /sys/kernel/mali/mali_gpu_clock

echo 0 > /sys/kernel/mali/mali_boost_delay

echo 48 > /sys/module/mali/parameters/mali_l2_max_reads

echo 50331648 > /sys/module/mali/parameters/pre_allocated_memory_size_max

#CPU UNDERVOLT#

echo varm=0x18 > /sys/kernel/liveopp/arm_step00

echo varm=0x18 > /sys/kernel/liveopp/arm_step01

echo varm=0x18 > /sys/kernel/liveopp/arm_step02

echo varm=0x1e > /sys/kernel/liveopp/arm_step03

echo varm=0x1e > /sys/kernel/liveopp/arm_step04

echo varm=0x22 > /sys/kernel/liveopp/arm_step05

echo varm=0x23 > /sys/kernel/liveopp/arm_step06

echo varm=0x30 > /sys/kernel/liveopp/arm_step07

echo varm=0x34 > /sys/kernel/liveopp/arm_step08

echo varm=0x34 > /sys/kernel/liveopp/arm_step09

echo varm=0x35 > /sys/kernel/liveopp/arm_step10

#ZRAM 200MB#

echo $((200 * 1024 * 1024)) > /sys/block/zram0/disksize

mkswap /dev/block/zram0

swapon /dev/block/zram0

#SWAPPINESS"

echo 100 > /proc/sys/vm/swappiness

#DEEPSLEEP STATE#

echo 3 > /d/cpuidle/deepest_state

#AGGRESSIVE LOW MEMORY KILLER#

echo "2560,4608,5888,26368,28928,31488" > /sys/module/lowmemorykiller/parameters/minfree

#FIX BLINK SCREEN IF YOU NEED#

echo 3 > /sys/kernel/mcde/lcdclk

i cut and paste in init.d then i executed and i restart is not work , im trying execute my script in SM manager its work but im restart my phone , and i try press my home button its not work , im trying play my movies same not work

how should i do [MENTION=235339]chrono[/MENTION] thanks ^_^

sorry if my english is bad

NB : oh here my kmsg
[Galaxy Ace II Android Development] nikolas1274:
What Rom are you using?
[Galaxy Ace II Android Development] xo.en:
Slimkat 9.0 by Straciatella/Vodka with system apks/framework repacked + ton of scripts.

21th hour without reboot - no blackscreen issue so far...this is really..weird.

Btw, battery usage is insane, i got less than 10% drop for 21 hours now.

Perfect stability, zero fc's, zero reboots..impressive.
[Galaxy Ace II Android Development] shaqman89:
Wow!!

Out of curiosity, dont you use your phone? [emoji14]

I admit that battery usage has greatly improved in my case, but my best hours is roughly 40 hrs max for a whole single charge.
[Galaxy Ace II Android Development] xo.en:
You know, my usage is non-typical. Short actions only.

Machine serves as..well, phone(2g, few calls daily at best), bit of gps, some photos, news reading through wifi/2g, ebooks for few minutes(Alreader!), some speed tests, some radio and music listening, some Amiga/ST/zx/c64 emulation...low screen backlight indoors(and 50% outdoors)...

System is set for lowspeed(ondemandish cpu profiles with 200-800mhz, no gpu OC, some uv) - which with this kernel has different meaning, than before - now it means - still FASTER than old fullspeed profile).

For longer actions i am using tablet novadays..

For a2 it is more important KNOWING, that long usage is possible, than usage itself now.

Tbh - i am considering using 100-500mhz for daily usage(i found it perfectly usable).
[Galaxy Ace II Android Development] str3tch72:
Are you going to update TWRP to 2.8.4.0? :)
[Galaxy Ace II Android Development] ChronoMonochrome:
I don't build TWRP from source. So, if nobody compiled it for any u8500-based device yet, I can't port it.
[Galaxy Ace II Android Development] xo.en:
f twrp...
[Galaxy Ace II Android Development] Alex_Gamer:
What do you mean with system apks/framework repacked?
[Galaxy Ace II Android Development] xo.en:
Every adequate apk from system i am using is repcacked.

Probably - it has ZERO logical effect, but, trust me, this is my way...
[Galaxy Ace II Android Development] Alex_Gamer:
Sound interesting, how you do it?
[Galaxy Ace II Android Development] xo.en:
I will send you PM, when i get off that drunk stupor i am actually in(+twin peaks, looped). I am not sure, if what i am talking about would be useful for others, so...

Anyway - Chrono - you are into very interesting piece of work here. Thank you, what can be said more...
[Galaxy Ace II Android Development] miryn:
[MENTION=5695278]ChronoMonochrome[/MENTION]

Right now on your kernel and ace2nutzer's there's a very little problem with 2D on all lcd freqs.. It's just not ideal smooth, as it was previous.

Btw. Best game to test that is impossible game and flappy..
[Galaxy Ace II Android Development] ace2nutzer:
Weird.. i've also one 2D Game and it's running smooth with interactive gov. and 57Mhz of LCD ...

If u want to help us, post till wich build was working good, and on wich build the problem started.. without that informations we can do nothing.

best way: Chrono kernel versions, and builds date of my kernels ...
[Galaxy Ace II Android Development] Alex_Gamer:
Thank you I'll be waiting :)
[Galaxy Ace II Android Development] heldix:
I had Chrono 2.21.2 68M running on two phones (ws2401). Clean install, clear init.d scripts .

I got 2 issues until now: After ~24-36h of usage the blackscreen bug appears. Means: Screen doesn't wake up when pressing powerbutton. It needs many presses until it wakes up. But after this the phone stays very reponsive and does not lag! After some more hours apps begin to get terminated and you have to reboot the phone.

My thoughts: There is some memory leak which leads to some buffer overflow and mentioned problem. I switched to the NON 68M version on one phone which show no problems until now (24h).

Second issue which might depend on the same trigger: Some days ago i used google maps several hours. At some point google maps displayed only the outlines of streets and no landscape, no streetplates etc. Routing didnt function anymore. Issues gone after reboot.

I tend to think that the 68M version works well in first place, but raises some problems on the long run.

EDIT: Configuration: cpu 200/1100 dynamic fiops gpu 600 ddr 975 fsyncdynamic
[Galaxy Ace II Android Development] shaqman89:
I beg to differ. I've been using it for more than 72 hours and still no issues.

But I think what ChronoMonochrome says before was correct. It might not work for every one. I am kinda curious though what are the deciding factors.

My configuration: cpu 200/1200 dynamic fiops gpu 700 ddr 975
[Galaxy Ace II Android Development] ChronoMonochrome:
With what configuration?

Btw. try ZenX if you are using another governor.
[Galaxy Ace II Android Development] miryn:
On every governor the same problem.. already tried all of them. I think it's related to all this "mess" with lcd freq, but that's only my 'imo'.
[Galaxy Ace II Android Development] Bogazicili90:
Guys I have a problem again. In call volume is so low even I have trouble to hear the opposite. I tried volume+ app and increased speaker volume a bit but in call volume is still the same. Interestingly when I make the call the volume is really high and good but when someone call me I can't even get the voice. What should the problem be?
[Galaxy Ace II Android Development] fluffi444:
Had the same behaviour with FC apps after some days of use and no reboot. Thats why I went back to normal HWMEM. ChronoMonochrome also mentioned this. Thats why HWMEM versions are abandoned actually.

Maybe its also app dependant and how the app uses HWMEM.
[Galaxy Ace II Android Development] xo.en:
Kernel with default hwmem(i think): 2 days, 9 hrs since last reboot - blackscreen is not present(set lcd freq to s6d now), batt status: 63%(from 90% since last reboot, still on 200-800mhz setup).

Nice, zero FC, zero problems, no sound loss, gps works great..I will deplete battery, then i am about to check 200-500mhz setup, i really wonder, if it may have ANY real effect on battery usage(in my case of coz..).

Can someone post screenhot of i/o tab from chronokernel app? It crashes for me there;/

Btw, it seems there is problem with fsync activation in chronokernel - perfctrl has option to use it, and both programs differ in reporting, if it is set, or not, since, perfctrl never had wrong read so far, i wonder, if chronokernel app has.

Alex, sorry for late response, check pm...
[Galaxy Ace II Android Development] ayas02:
hi [MENTION=235339]chrono[/MENTION]

in R2.21.2 im make a own init.d script

my script :

#!/system/bin/sh

#GPU OVERCLOCK#

echo 0 > /sys/kernel/mali/mali_auto_boost

echo 1 > /sys/kernel/mali/mali_gpu_fullspeed

echo idx=17 > /sys/kernel/mali/mali_boost_high

echo idx=13 > /sys/kernel/mali/mali_boost_low

echo 640000 > /sys/kernel/mali/mali_gpu_clock

echo 0 > /sys/kernel/mali/mali_boost_delay

echo 48 > /sys/module/mali/parameters/mali_l2_max_reads

echo 50331648 > /sys/module/mali/parameters/pre_allocated_memory_size_max

#CPU UNDERVOLT#

echo varm=0x18 > /sys/kernel/liveopp/arm_step00

echo varm=0x18 > /sys/kernel/liveopp/arm_step01

echo varm=0x18 > /sys/kernel/liveopp/arm_step02

echo varm=0x1e > /sys/kernel/liveopp/arm_step03

echo varm=0x1e > /sys/kernel/liveopp/arm_step04

echo varm=0x22 > /sys/kernel/liveopp/arm_step05

echo varm=0x23 > /sys/kernel/liveopp/arm_step06

echo varm=0x30 > /sys/kernel/liveopp/arm_step07

echo varm=0x34 > /sys/kernel/liveopp/arm_step08

echo varm=0x34 > /sys/kernel/liveopp/arm_step09

echo varm=0x35 > /sys/kernel/liveopp/arm_step10

#ZRAM 200MB#

echo $((200 * 1024 * 1024)) > /sys/block/zram0/disksize

mkswap /dev/block/zram0

swapon /dev/block/zram0

#SWAPPINESS"

echo 100 > /proc/sys/vm/swappiness

#DEEPSLEEP STATE#

echo 3 > /d/cpuidle/deepest_state

#AGGRESSIVE LOW MEMORY KILLER#

echo "2560,4608,5888,26368,28928,31488" > /sys/module/lowmemorykiller/parameters/minfree

#FIX BLINK SCREEN IF YOU NEED#

echo 3 > /sys/kernel/mcde/lcdclk

i execute is success , after i playing games and reboot suddenly my button home is not working how can i fix it

thanks [MENTION=235339]chrono[/MENTION]
[Galaxy Ace II Android Development] ChronoMonochrome:
@up, you are changing many things at the same time, try to split it to few scripts and test them separately.

Don't use swappiness=100, I suggest to decrease it to 40 or 30.
[Galaxy Ace II Android Development] ayas02:
Finally ^_^

thanks chrono i will trying
[Galaxy Ace II Android Development] xo.en:
Definitely.
[Galaxy Ace II Android Development] ayas02:
but how can i execute my script in init.d folder ?

previously im running my script in SM manager

thanks
[Galaxy Ace II Android Development] xo.en:
init.d script is executed after boot, ONCE per boot.

upd: unless it has some kind of...timed restart/loop script part inside :)
[Galaxy Ace II Android Development] ayas02:
and permissions should I choose '
[Galaxy Ace II Android Development] xo.en:
755 or if you like weird way of same: -rwxr-xr-x

Then make reboot, voila.
[Galaxy Ace II Android Development] ayas02:
its not work im trying some script and not changing
[Galaxy Ace II Android Development] ChronoMonochrome:
New build R2.22 is ready to go!

LiveOPP: reworked PRCMU QoS part (added interface prcmu_qos_performance)

(parameters explained)

apeopp=xx

ddropp=xx

default minimum APE/DDR OPP stats, used by LiveOPP.

pow_opt_idx=x

power optimal idx (frequency), when CPU is above this freq, APE100/DDR100 will be used. Idx means number of CPUfreq step.

ape50_opp_idx=x

ddr50_opp_idx=x

when is above these thresholds, APE50/DDR50 will be used.

ddr100_mali_threshold=xxx

ape100_mali_threshold=xxx

Allows to use APE100/DDR100 only if GPU usage exceeds threshold xxx (0-256). Disabled by default, enabling can save power at the cost of I/O and RAM performance.

PRCMU QoS: added interfaces to allow "ignore" some QoS APE requirements

/sys/module/prcmu_qos_power/parameters/

By default all QoS requirements such as USB, SVA and FILE are enabled. Disabling allows to use even lower APE OPP value, to save some power.

Re-added I/O scheds BFQ v7r7, Zen and VR

Re-enabled UKSM

Lowered DDR OPP to 25 by default

Fixed slow UMS mode speed on CM12 (and probably improved on all ROMs) – thanks to PolishVodka for hint.

Original idea is in setting ro.vold.umsdirtyratio to higher value. Unfortunately, this didn't work on CM12, somehow it overrides dirty_ratio and sets it to 0, causing low UMS speed. I've fixed it by disallowing dirty_ratio to be set to 0(default 20 is used now instead).
[Galaxy Ace II Android Development] ayas02:
Really Re-Enable Again UKSM
[Galaxy Ace II Android Development] Ave_Hornet:
Good Changes !! Thanks [MENTION=5695278]ChronoMonochrome[/MENTION]

1k THANKS lets CELEBRATE !!!
[Galaxy Ace II Android Development] ayas02:
[MENTION=235339]chrono[/MENTION] im trying put new script in init.d folder , i set 755 permission and i reboot after reboot i check is not work but strangely im trying play ppsspp game with 1,1ghz max and 200mhz min governor : ondemandplus and i/o : sioplus is very" smooth why chrono give me explanation

thanks
[Galaxy Ace II Android Development] borkins:
To be sure about that the script is executed after reboot you can put this at the end of the code:

echo "$(date +%T) OK" > /sdcard/script_name.log

If there is script_name.log file on internal sdcard, that means the script is executed.

Chrono-kernel app makes some changes after reboot, so if no changes are made by your script,

that would be the reason I think. If that is the case, you have some options:

1. Put 'sleep 300' at the begin of the code. ( But that may not be enough, when cache is wiped in recovery ).

2. Put waiting function at the begin of the code:

a) Wait for process 'settings' + 'sleep 25'

wait() {

if [ ! "$(pgrep - l settings)" ]; then

sleep 1 ; wait

fi

}

wait

sleep 25

b) Wait for process 'mars_army.settings' + 'sleep 5'

wait() {

if [ ! "$(pgrep - l mars)" ]; then

sleep 1 ; wait

fi

}

wait

sleep 5

3. Put permissions + waiting function at the end of the code:

chmod -R 444 /sys/kernel/mali

wait() {

if [ ! "$(pgrep - l settings)" ]; then

sleep 1 ; wait

fi

}

wait

sleep 25

chmod -R 755 /sys/kernel/mali

find /sys/kernel/mali -type f -exec chmod 644 {} \;

I'm using 3rd option.
[Galaxy Ace II Android Development] xo.en:
..ok, i avoided f2fs, but my interest is growing now.

Can i restore data, or whole cwm backup after conversion somehow(how exactly cwm handles restoration - does it format partitions to same as backuped ones, or just uses what ever partition format is?)?

My point is, that i would like to avoid full wipe...is there any way to do it?
[Galaxy Ace II Android Development] monstro78:
Another fine kernel from chrono...

2.22 works great. Thanks
[Galaxy Ace II Android Development] miryn:
Wifi doesn't work on the latest kernel..

At 2.21.2 worked well. Carbon 4.4, wipe cache + dalvik.
[Galaxy Ace II Android Development] ayas02:
2.22 its great in 4.1.2 good job chrono thanks
[Galaxy Ace II Android Development] LS.xD:
- Make a nandroid backup.

- Format the partitions as f2fs

- rename the backup files from ...ext4... to ...f2fs...

- restore the backup