yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] ChronoMonochrome:
Probably because of outdated recovery. If it's TWRP, always install as newer recovery, as it's possible, esp because old recoveries are untested with newest build and even didn't expected to work. Maybe I can do something in kernel to make old recoveries working - but it's much easier just install latest recovery. This one should work http://xda.mister-freeze.eu/XDA-files/ChronoMonochrome/ramdisk/recovery/twrp_2.7.1.0_for_R2.12.zip .
[Galaxy Ace II Android Development] ChronoMonochrome:
R2.14

New build is up :)

Changelog:

- fixed reboots, caused by broken CGROUPS implemetation

- fixed installer. If it's not first installation, then recovery should be untouched now. Installation process simplified now - no longer needed to flash anything except kernel and recovery (if needed).

- fixed LPM on CM11

- LiveOPP: new varm recalibration - based on algorithm by [MENTION=3329816]mkaluza[/MENTION]

- new touchbooster interfaces /sys/module/bt404_ts/parameters/*

cd /sys/module/bt404_ts/parameters/
echo ? > bt404_ape_boost
echo ? > bt404_ddr_boost
echo ??? > bt404_ape_opp
echo ??? > bt404_ddr_opp

bt404_ape(ddr)_boost - 1, 0

bt404_ape(ddr)_opp - 25, 50, 100

There's no CPU freq setting since it was already implemented in interface /sys/kernel/cpufreq , and some governors has its own cpufreq touchbooster. By default enabled only APE_OPP boost (APE100).

- CM11 profiles now are used to switch between governor dynamic profiles

http://xda.mister-free…hrono_kernel_r2.14.zip
[Galaxy Ace II Android Development] shaqman89:
Really satisfied with the performance of 2.14 compared to 2.12 or 2.13. It's really smooth and fast. Great job [MENTION=5695278]ChronoMonochrome[/MENTION] :D

I noticed some new script in init.d folder and one of them is kmsg dump. Is it necessary to have that in init.d? I mean, usually we could do that on request rather than every time at startup
[Galaxy Ace II Android Development] ChronoMonochrome:
Thanks to toochbooster for great performance :D it's even not necessarily to set aggresive APE/DDR settings via LiveOPP, since touchbooster can set APE100 on every touch :)

Probably it's not so necessarily. But it won't work anyway, because of missing working directory :)
[Galaxy Ace II Android Development] seanmalto:
Dunno why, but i've got an error message when flashing twrp_2.7.1.0_for_R2.12.zip (Installaton Aborted)

But since new build was released, i just flash the latest kernel r2.12.4

No bootloop at twrp recovery anymore.

thanks :D
[Galaxy Ace II Android Development] nikolas1274:
Thanks for new version chrono, I Ann using carbon Rom and after I flash latest version I have new settings under memory settings, it calls them, not killable user settings, not killable system settings and KSM (that comes with 2.10 I think)
[Galaxy Ace II Android Development] manthes:
After latest kernel you must close this topic. You can't do anything better. I hope it will not appear any problem but it is fast and a very little tearing that it had with previous builds now have gone (s6d)
[Galaxy Ace II Android Development] ChronoMonochrome:
Fun thing, I didn't expect that this setting will appear due to just new interfaces :)

maybe you're right. at the moment I do not know what else can be added or improved. But if something interesting comes up, I'll return to this, and so leave the topic open. :)

UPD. damn it, service auditd was accidentally re-added after some modification of 4.4.x ramdisk. Will upload fix soon.

http://xda.mister-freeze.eu/XDA-fil...amdisk/bootscripts/4.4.x_auditd_fix_R2.14.zip
[Galaxy Ace II Android Development] ChronoMonochrome:
I must have messed something with latest builds if it still reboots sometimes :/ will revert some changes and see if it helps.
[Galaxy Ace II Android Development] shaqman89:
Haven't got a reboot so far here :D

Upd: [MENTION=5695278]ChronoMonochrome[/MENTION] I tried the fix but it can't be installed for some reason. The error that was shown was Installation aborted.
[Galaxy Ace II Android Development] ChronoMonochrome:
It's non-flashable zip. All zip which I upload to ../ramdisk/bootscripts are non flashable. You've to extract 4.4.x.cpio and manually put in /ramdisk/boot.cpio.
[Galaxy Ace II Android Development] fluffi444:
Was for about 2 weeks offline and manny things happens in the meantime here :) Good work.

I'm still on R2.10-refresh and very happy with it.

But of course I what to try R2.14. I read that some version of bootscript/recoverys are not compatible with R2.14.

For now I'm a bit lost in the meantime what versions are the correct one for R2.14...

Maybe one of you can advice which Versions of what are the correct ones for:

Codinap / Full F2FS / R2.14
[Galaxy Ace II Android Development] ChronoMonochrome:
There no need to flash anymore except kernel :) The package contains all needed things to be installed by simple flashing. Installing recovery is optional (but if it's TWRP, latest version is recommended, because old recoveries may cause TWRP loop). Codina p is untested so far, but this kernel supposed to be compatible with both of codina(p) versions :fingers-crossed:
[Galaxy Ace II Android Development] heml0ck:
what 4.4.x.cpio i will download? the one in google drive?
[Galaxy Ace II Android Development] shaqman89:
You are right, random reboots still happens:(:(

Do you need kmsg logs to trace the errors?
[Galaxy Ace II Android Development] ChronoMonochrome:
If not difficult - post it here.

P.s. I already uploaded new build - I hope I finally find out what's cause of random reboots. Once again reverted varm recalibration (used to increase voltage only), and NEON optimization also reverted (it might conflicts with other optimization flags).

http://xda.mister-freeze.eu/XDA-files/ChronoMonochrome/kernel/chrono_kernel_r2.14.1.zip
[Galaxy Ace II Android Development] shaqman89:
Sure.

Here is the log: https://docs.google.com/file/d/0Bzo3MSxg_YFCbTdOMDhrNm9LS1k/edit?usp=docslist_api

I'll try out the new build :D
[Galaxy Ace II Android Development] ChronoMonochrome:
According to log, it should be kernel scheduler fail. Btw, why do you use GPU 730 MHz? It also doesn't work stable.
[Galaxy Ace II Android Development] shaqman89:
Hmm.. That's funny, I don't remember setting gpu to 730,its usually 710 or 690. That might be the culprit then.

I am on the new build now, and have changed that to 710.

Thanks. :)

Speaking of which, I think I noticed that the governor is always going to on demand even though I set dynamic to be set on boot through performance menu. Is this intended behavior?
[Galaxy Ace II Android Development] ChronoMonochrome:
That's strange, never met it. Default governor(in kernel) is ondemand, but ramdisk should anyway set Dynamic. In the next build I'll set it as default governor for sure :). Try to enable CM11 profiles for now, which are used for profiles of Dynamic.
[Galaxy Ace II Android Development] shaqman89:
Sorry for this stupid question, but, by cm11 profile, you mean the one that says home, default, etc, right?

Or you mean the performance profile which has balanced, performance and powersaving?
[Galaxy Ace II Android Development] ChronoMonochrome:
I probably wrongly phrased - ofc I wanted to say performance profiles :)
[Galaxy Ace II Android Development] shaqman89:
Sure, I will try it :)

Thanks :)
[Galaxy Ace II Android Development] ace2nutzer:
But this is from phone to phone different.. i've here an ace2 what can handle 770Mhz for GPU ;)
[Galaxy Ace II Android Development] ChronoMonochrome:
According to that log it was not stable.
[Galaxy Ace II Android Development] nikolas1274:
chrono, any idea where is the performance profile at carbon rom?

thanks
[Galaxy Ace II Android Development] ChronoMonochrome:
Don't remember if it has.. I haven't used them on carbon.
[Galaxy Ace II Android Development] fluffi444:
R2.14.1 / Full F2FS / TWRP 2.8.0.0 / CodinaP

Works realy good :good:

and for me without any LiveOPP tweaks (but activated touchbooster to DDR/APP 100 - of course :o)

Only thing to mention ist PLLDDR OC

With simple script (like in OP) I got freeze instantly very often...

echo 0x0005017f > /sys/kernel/liveopp/pllddr # 975 MHz

Setting it via init.d is not possible this way...

This is acctually the reason why I got R2.14 not to work first time... PLLDDR init.d made system stuck on circeling boot logo...

With enhanced PLLDDR script with max freq settings (of R2.7 to 2.9) without these "wakelock parts" it works more often but also not perfect.

Have to set an very long sleep time before PLLDDR init.d script ...
[Galaxy Ace II Android Development] zizoumadrid:
i'm didn't use any script to change in cpu or gpu or ddr or somthing like that

it's sure needed to set those script to get more performance or smoothness thank's
[Galaxy Ace II Android Development] monstro78:
Last build until now stable as rock at 1200
[Galaxy Ace II Android Development] shaqman89:
Yeah, had this same issue here.

But since it works quite well even without OC DDR, I currently decided not to use it for the moment.
[Galaxy Ace II Android Development] ChronoMonochrome:
Seems it became unstable exactly after I did SDMMC freq fix. Have no idea how to fix it, but since it works with that script (with wakelock parts) and since we can't let SDMMC OC, use of that script is only way...
[Galaxy Ace II Android Development] fluffi444:
This is what I'm using right now - It's [MENTION=5695278]ChronoMonochrome[/MENTION] works - I did nothing special - I only removed the not needed stuff of doubletap2wake...

Please note the quite high sleep time of 150 - I use this as init.d and for me it works the best if the script runs after Phone is booted completely.

This is for 975 Mhz - For higher freq. remove the hashes but leave the value before the higest also active (don't hash them).

To list 798 is not needed at all - I just leave for the records and possible down settings during phone is on.

#!/system/bin/sh
set -x
sleep 150

MINFREQ="/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq"
MAXFREQ="/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq"
MINFREQVAL=`cat $MINFREQ`
MAXFREQVAL=`cat $MAXFREQ`

echo $MINFREQVAL > $MAXFREQ

echo 1 > /sys/kernel/abb-ponkey/emulator
sleep 2

# echo 0x50168 > /sys/kernel/liveopp/pllddr # 798 Mhz
# sleep 0.5

echo 0x5017f > /sys/kernel/liveopp/pllddr # 975 Mhz
sleep 0.5

# echo 0x50180 > /sys/kernel/liveopp/pllddr # 983 Mhz
# sleep 0.5

# echo 0x5018f > /sys/kernel/liveopp/pllddr # 1098 Mhz
# sleep 0.5

echo 1 > /sys/kernel/abb-ponkey/emulator
sleep 2

echo $MAXFREQVAL > $MAXFREQ
#
[Galaxy Ace II Android Development] junnickbefore14:
Is it possible to do fstrim in our device ?

Because whenever i tried to trim /data partition, there is an error message " not a typewriter"
[Galaxy Ace II Android Development] borkins:
I updated the init.d OC_DDR scripts. Now the time for OC depends from the CPU usage after the boot.

20150116
[Galaxy Ace II Android Development] fluffi444:
Thx for your script, borkins! Seams to be the more secure way to set OC - But two things to mention regarding your script (for init.d)

Variable for OC_DDR log in script is not correct evertime.

has to be $SDcard/OC_DDR.log and you wrote only OC_DDR.log three times.

Furthermore I stuck at min = max Freq after script finisched. That means the min freq is not restored and is the same as max freq.

EDIT

After correction of the log variable and placing the "min freq to former value"-string at the very end, the script works flawlessly...
[Galaxy Ace II Android Development] borkins:
Thanks for reporting! It's my fault. I messed up something in the script folder, and looks i put the wrong scripts. I do everything on the phone :)

I'll update the scripts as soon as I can. Thanks again!

OC_DDR Scripts Update - 20150118
[Galaxy Ace II Android Development] riyosakura:
I tried to install 2.14.3 and 2.14.1 kernel.

but it failed.

What is the requirement?

I dont see further requirement in OP.

I've already flash make-ramdisk, full f2fs recovery. and bootscript is unneeded with 2.12 kernel later. So what is wrong?
[Galaxy Ace II Android Development] shaqman89:
I am not sure about 2.14.3 but 2.14.1 installs fine and normally for me. I installed it from 2.13
[Galaxy Ace II Android Development] ChronoMonochrome:
Do you mean it caused bootloop, or installation was aborted? If first, please post last_kmsg here.

UPD. OC_DDR script update (non-init.d only)

Changelog:

- small code optimization

- used generic wakelock interface, instead of dt2w one

- killed process media in order to decrease CPU load

- added step 1190 MHz. Because some users reported, that it was stable for them, I added this step. Static GPU freq helps a bit with that, though it was anyway unstable on my device. If you use static GPU freq, remember also increase APE50 voltage:

echo 20 > /sys/kernel/mali/mali_gpu_vape_50_opp

Thanks [MENTION=5151049]borkins[/MENTION] for original script.
[Galaxy Ace II Android Development] riyosakura:
Installation failed or aborted.

Im using twrp recovery.

Its displaying install os etc, until it displaying set_perm and it failed.

Or maybe i must use another recovery?
[Galaxy Ace II Android Development] ChronoMonochrome:
Will try clean install... maybe I missed something (probably it tries to set permission to non-existing file).
[Galaxy Ace II Android Development] manthes:
First blackscreen with 2.14
[Galaxy Ace II Android Development] blastos01:
[MENTION=5695278]ChronoMonochrome[/MENTION] if I flash the latest hybrid kernel could i go back to stock jellybean? And how? Just flashing stock JB via odin is enough??
[Galaxy Ace II Android Development] ChronoMonochrome:
Yep.
[Galaxy Ace II Android Development] riyosakura:
Im updating from 2.10-refresh kernel. Maybe there is some file missing updating from that version?
[Galaxy Ace II Android Development] borkins:
I doubt that, coz i flashed r2.14.1 from r2.10-refresh too - without any problems.

Edit:
[MENTION=5695278]ChronoMonochrome[/MENTION],

In my test with OC_DDR, i think is more unstable when trying with GPU static frequency - I got more reboots with every frequency.

And I decided to leave only the CPU at static clock in the OC script.

For the old DDR OC scripts I didn't add the 1190 MHz clock, because i don't know how to reduce the SDMMC clock for it.
[Galaxy Ace II Android Development] blastos01:
thank you [MENTION=5695278]ChronoMonochrome[/MENTION]
[Galaxy Ace II Android Development] ChronoMonochrome:
I got some reboots during changing GPU freq(sometimes with graphic corruptions), and when set static clock only apps FC sometimes happened. I think reducing DDR freq should solve apps FC, though I didn't spend much time at that.
[Galaxy Ace II Android Development] vacziferi:
Hello,

can somebody tell me how to use these scripts? Are they working on older kernel versions (r.2.10)?

On 2.14, my phone did not booted (cm.10.2), with old bootscripts it has booted but has serious bugs (e.g. battery indicator freeze).

thanks
[Galaxy Ace II Android Development] ChronoMonochrome:
R2.14.5

Because I had soft-reboots with latest build, I rebased some changes onto R2.10.2, which are:

- touchbooster interfaces

- lcdclk management

- installer is from R2.14.x

- abb-fg: new interfaces average_current and instant_current. p.s. use scripts from attachment - extract them to /system/xbin, give 755 permissions, and type from terminal:

current

Other changes:

- PLLDDR OC: added calibration of peripheral regulators (usb, camera etc.) and MCDE (video subsystem)

I should again repeat here - use DDR OC at your own risk. It's unknown yet if DDR OC still cause FS corruption, but one user had fs corruption on /cache partition. Though don't know if it's itself faulty F2FS.

- removed 04LMK script - this cause OOM sometimes

- disabled ZRAM by default, because after ~ day of using this might cause lags. Enable it only if it is really needed (old scripts without loading zram.ko should work).

- because some changes were reverted, there are no some kernel optiizations. Boot time has been increased to ~8200 ms on F2FS build (~8000 on ext4).

full changelog

http://xda.mister-freeze.eu/XDA-files/ChronoMonochrome/kernel/chrono_kernel_r2.14.5.zip

@up, try this build. If I remember correctly, I included fixes to cm10.2 bootscripts.
[Galaxy Ace II Android Development] shaqman89:
Trying it, and it works okay. So far it's smooth but I've only been trying it for 10 minutes or so.

Btw, what effect should be expected from abb-fg in performance and powersaving terms? I understand from cocore's kernel that it's related to lowbat wake lock and cycle charging control, but I'm not sure how that affects performance or battery life.

Great smooth performance and also for me boot time is still good (7918).

Thank you :)
[Galaxy Ace II Android Development] ChronoMonochrome:
Did you mean those new interfaces (average/instant current)? Here's nothing to do with powersaving, actually it only shows power consumption(it's same, what shows CurrentWidget, but here's also showing average current), that should help with debugging some powersaving features (you can apply some changes and see if power consumtpion has been changed after you did it).
[Galaxy Ace II Android Development] borkins:
These scripts are not bootscripts! These scripts are for PLL DDR overclock.

For kernels before r2.14 you must use the right recoveries and bootscripts.

After r2.14 there is no need to flash recoveries and bootscripts with the kernel.
[Galaxy Ace II Android Development] mars_army:
Guys, somebody can spend a few time and translate or correct it? View attachment strings.zip

The archive contains three files: arrays.xml, strings_en.xml and strings_ru.xml. These files are language lines for the "ChronoKernel Settings" app. Now it almost stable, but isn't enough english (for english-speaking users).

It's necessary to correct translated lines in arrays.xml file, strings_en.xml - autotranslation of "Google Translate", strings_ru.xml - original file. Please, correct translation in strings_en.xml (or translate it).

Sorry, I haven't time for the translation. I doubt that my knowledge of english allows me to support this language too.

When english translation will be ready, I'll post "ChronoKernel Settings" app here.

Regards.
[Galaxy Ace II Android Development] vacziferi:
I know, maybe I described wrong...

So, I can't install r2.14 on CM10.2, because it not booted - stuck on cm boot logo (yes, I tried to install kernel and recovery only)

Than I installed bootscript from previous versions, but I had some bugs... Finally decided to move back for r.2.10

BUT, now I need info, how to install PLL DDR OC scripts.
[Galaxy Ace II Android Development] zizoumadrid:
I'm teried the last build 2.14.5 it's not good for me i had some lag with it i'm with stock rom jb 4.1.2 i think 2.14.2 it's the best build till now very smooth and stable

Configuration: max 1ghz min 200 mhz

Gov:dynamic

Schu:sioplus

Thank's [MENTION=5695278]ChronoMonochrome[/MENTION] you'er amazing :good:
[Galaxy Ace II Android Development] borkins:
For CM10.2 i never try it with Chrono's kernels, and I can't help you about that. :\

I'm on CM 11 and flashed r2.14 from r2.10 without problems before 4 days.

About the OC DDR scripts you need to use OC_DDR_old scripts for kernel r2.10.

Installation is quite easy:

If you want to OC DDR after boot - use the init.d script "OC_DDR_old".

Just paste the script in "/etc/init.d" folder and then set 755 permissions, Owner 0: root, Group 2000: shell to the script.

After reboot the script will set 975 MHz for PLLDDR clock. Don't panic when the screen go off suddenly. That means the script start the OC process.

The screen will go on again in about 3 sec. If not, then in the most cases that will be followed by reboot.

In that case the init.d OC process is unstable for you. If you want, try with another CPU governor. For example with Lionheart.

The OC delay after boot will be around 300 sec (~5min.), while for a governor Dynamic is around 1min.

That is not enough some times and the CPU still do a lot work after the boot, which make the OC unstable...in theory.

You can check the OC delay in the file 'OC_DDR.log' in internal SD card.

The other script ("OC_DDR_old.sh") is designed for Smanager app.

You can place the script in internal or external SD card.

Start Smanager and find the script with Smanager's file manager, click on the script and above you'll see some icons.

Click on 'su' and 'save' once, and then the script is ready to be used, by click 'Run'.

When start the script, you'll see a primitive option to choose the clock by typing '1,2, 3...' and then 'enter'.

The display will be turned off for a moment while the script setting the new PLLDDR clock.

After that, the screen will be unlocked automatically, if you are already set 'menu' button to unlock the screen in ROM settings.
[Galaxy Ace II Android Development] shaqman89:
[MENTION=5695278]ChronoMonochrome[/MENTION]

I was trying to see logcat again just now, I have loaded put logger.ko in autoload like it was done in previous version of kernel, somehow logcat can't be used.

I got this error:

Unable to open log device '/dev/log/main': No such file or directory

Am I missing some other configuration?

Thanks

Update:

Done. It turns out that the logger.ko I was using might be from previous version making it not able to load.

After copying logger.ko from module folder, it worked now. :)
[Galaxy Ace II Android Development] mars_army:
ChronoKernel Settings

ChronoKernel Settings 0.9 beta

- with system privileges - View attachment ChronoKernelSettings-09-beta.apk (just copy it in /system/app and set "0644" permissions).

- for stock firmwares and etc - View attachment ChronoKernelSettingsforStock-09-beta.apk

Full changelog (in great and mighty russian).

If you will find any bugs or inaccuracies in translate and you want to help, please, write me.
[Galaxy Ace II Android Development] Bastiary:
Great will test it right now
[Galaxy Ace II Android Development] manthes:
Can i remove novathor apk and use only this app? Because i see that it is a modified version of novathor
[Galaxy Ace II Android Development] mars_army:
Yep, you can remove NTSettings.
[Galaxy Ace II Android Development] Kiras_PL:
Your app seems to be working :) great job !
[Galaxy Ace II Android Development] xo.en:
Damn, this is insane, i just checked 4pda forum, i cannot believe, that a2 can make >15k antutu score, i am with this machine for long enough time to remember 8.5k at best, lol...

btw, great job, mars_army, it is just what i needed to finally check 4.4.x rom with chronos kernels..
[Galaxy Ace II Android Development] nikolas1274:
Hello, for bln notification we still need initd script to enable the wakelock?

I saw all the other options for bln but not this one at your app

Thanks
[Galaxy Ace II Android Development] fluffi444:
First, an idea: What's about an dark theme?

Second: Well done! :good: :highfive:

Third: Maybe its needed to open an new thread for it on XDA?!

1) Screen: Enable Touch boost: This set "only" APE boost to ON - Maybe an switch for DDR boost (bt404_ddr_boost) and an switch for each value for APE/DDR (25/50/100) would also be nice.

2) I/O: read_ahead_kb values are not set correctly - This was and is an error which was in NTsettings since beginning

3) CPU Undervolting: This could be a bit dangerours because the original setting of Chrono is already well optimized - even -12,5/25 could force reboot - Especially for the higher freq from 800-1200. Maybe its better only to undervolt the lower steps (further testing needed)
[Galaxy Ace II Android Development] manthes:
[MENTION=5695278]ChronoMonochrome[/MENTION] maybe it is better to replace instructions from the third post with this one simple script from fluffi444. I used it to convert liquidsmooth and rom is much smoother with F2FS