yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] manthes:
I am using ondemandplus 200/1150, gpu 440 and ddr 975mhz. I don't know about dynamic

With previous kernel i had 11700 antutu score. With 12.6.2 it goes to 12600 score. But the most important is the feeling of the phone that is really faster and not only the scores
[Galaxy Ace II Android Development] ChronoMonochrome:
Normally wipe cache is unnecessary unless you encounter apps FC.
[Galaxy Ace II Android Development] fluffi444:
Only for CODINAP/8160P with ChronoKernel Universal (with Recovery on /RAMDISK)

I made a short script for converting codina into codinap in recoverys

The phone will be recognized correctly as codinap in recovery and installed as GT-I8160P in Windows out of Recovery.

This is only cosmetic and for most not really needed - was playing around a bit and tought maybe usefull for other, too.

This will change all "codina" and "GT-I8160" to "codinap" and "GT-I8160P" in recovery_default.prop.

Flashable from Recovery (tested for TWRP and above mentioned restictions)
[Galaxy Ace II Android Development] ChronoMonochrome:
Oops, did I leave "codina" entries for codinap in recovery_default.prop? This thing was untested and since nobody reported about that, I thought that it works correctly.
[Galaxy Ace II Android Development] fluffi444:
they have diffentent values?... though you left this as it is... :) Than take it as report :D

30 mins wastless work for me then - but it was fun anyway to get it work :)

The file in Kernel (osfiles\codinap\recovery_default.prop) is OK but may be not copied correctly during install...

And I think this never came up becaue MTP never worked correctly on last TWRPs.

Tested this again by flashing kernel once more... it went back to codina/GT-I8160 in recovery_default.prop again....
[Galaxy Ace II Android Development] ChronoMonochrome:
Hm, they are surely different.

Never had problem with it. It shouldn't be problematic unless you have already changed by accident codinap -> codina, and then installed kernel. Was it a purpose for writing this script? Thanks anyway for your efforts :)
[Galaxy Ace II Android Development] fluffi444:
As I wrote (edited) in last post... it even goes to codina/GT-I8160 if the recovery_default.prop was corretly set to codinap/GT-I8160P.

I know that this is really not as important - Only for those who want to go back to another 8160P kernel which is not universal 8and have assert check.
[Galaxy Ace II Android Development] ChronoMonochrome:
Now I got it. Well, it's odd, that even with "codinap" entries in default.prop the phone still recognized as codina. Will add this script in OP :)
[Galaxy Ace II Android Development] fluffi444:
Only that we understand each other :)

Phone is recognized as codinap if the entries are codinap. Manually changed or by script.

But if you flash the kernel (R2.16.2) the recovery_default.prop is back again to codina.

That's the story...
[Galaxy Ace II Android Development] fluffi444:
I think I found the solution.

Check:

osfiles_install.sh

#!/sbin/sh

set -x

mount /system

DEF_PROP="recovery_default.prop"
DEV_SCRIPT="init.samsungcodina.rc"
DEVICE=$(cat /system/build.prop | grep "ro.product.device=" | cut -d "=" -f2)

VERSION_LINE=$(cat /system/build.prop | grep "ro.build.version.release" | cut -d "=" -f2)
VX=$(echo $VERSION_LINE | cut -d "." -f1)
VY=$(echo $VERSION_LINE | cut -d "." -f2)

I just changed the DEVICE check to system/built.prop and moved mount system upwards....

the check on default.prop (as it was before) results everytime in codina during kernel install...

Now it works here....

Could you check and confirm this?

Gesendet von meinem GT-I8160P mit Tapatalk 2
[Galaxy Ace II Android Development] ChronoMonochrome:
Sorry, I was too sleepy to understand anything :silly:

Thanks for the fix!

I've checked original DEVICE check line in recovery - as turned out I forgot to replace /default.prop with a symlink to /ramdisk/default.prop, therefore solution should be trivial. Will do it in next release...
[Galaxy Ace II Android Development] ayas02:
Why im stuck in samsung logo after flash R2.16.2 how can i fix it thanks
[Galaxy Ace II Android Development] ChronoMonochrome:
last_kmsg, please. With only knowing that you've got stuck at samsung logo I can't say anything.

Reboot into recovery and run following commands using adb:

cat /proc/last_kmsg > /*path-to-sdcard*/last_kmsg

In various recovery path to sdcard may vary. In case if can't boot into recovery, use odin kernel from OP (you can find it in google drive).
[Galaxy Ace II Android Development] avithohol:
Hello Choro,

After some testing with the tables in ddr_cross clock and investigating trough the sources of the platform, i think there are some additional optimisation that can happen for the platform :

CLK_MGT_ENTRY(PER1CLK, false)-peripheral clock generator 1, maybe not in use, no performance gain or loss with oc,uc

CLK_MGT_ENTRY(PER2CLK, true)-same as above.

CLK_MGT_ENTRY(PER3CLK, true)-same as above.

CLK_MGT_ENTRY(PER5CLK, false)	/* used for SPI */, no performance loss with lowes possible frequency.

CLK_MGT_ENTRY(PER6CLK, true)-no gain maybe not in use.

CLK_MGT_ENTRY(PWMCLK, false)-?

CLK_MGT_ENTRY(IRDACLK, false)-?

CLK_MGT_ENTRY(IRRCCLK, false)-?

CLK_MGT_ENTRY(HDMICLK, false)-hdmi clock generator, not in use.

CLK_MGT_ENTRY(APEATCLK, false)-used for debugging maybe it can be disabled, no gain or loss with oc/uc.

CLK_MGT_ENTRY(APETRACECLK, true)-used for debugging maybe it can be disabled, no gain or loss with oc/uc.

CLK_MGT_ENTRY(MCDECLK, true)- used for the lcd, seting different values lead to instant reboot, do not touch.

CLK_MGT_ENTRY(DSIALTCLK, false) - Display serial interface shoud not be touched, related to lcd.

CLK_MGT_ENTRY(DMACLK, true) - direct memory acces interface, can be set to 00f, no performance loss or UI problems.

CLK_MGT_ENTRY(B2R2CLK, true)- internal job scheduler driver, need more tests !

CLK_MGT_ENTRY(TVCLK, false) - not used

CLK_MGT_ENTRY(RNGCLK, false) - ?

CLK_MGT_ENTRY(SIACLK, false)- related to MMDSP Debugger - Lauterbach, used for camera do not change if you want working camera app.

CLK_MGT_ENTRY(SVACLK, false)- related to MMDSP Debugger - Lauterbach, maybe it can be disabled, to save power

CLK_MGT_ENTRY(ACLK, true) - system bus, can be set to 360 mhz with the default voltage and ddr 1090, but it's not stable, has possitive effect on overall performance, maybe max stable at the moment is 330 mhz(not tested).

Setting lowest possible static frequence(+ uv), or completely disable some of the clock generators that doesn't have a use should bring more stabillity and power saving. I'm using 1200 mhz ddr oc without issues at the moment with these voltages :

One more suggestion the scaling option for the pll_drr and ape, should be related also with mali boost_hight logic, and when mali_boost hight is used the pll_ddr and ape shoud be set to 100 and only scale down when both mali and cpu have scaled down. Mali use the same resources, interface as the cpu (ram/system bus after all they are SoC system), and when they scale down, because the cpu is not fully loaded(cpu load is 400 or 600 mhz, etc...), it deteriorates the performance of gpu. :) :good:
[Galaxy Ace II Android Development] S.AMU:
Sorry that I wasn't online over the weekend...

When I made the report, I already made an completely fresh install (to be exact it was even the second one)

So when I have time I will restore my old backup with the 15.x kernel and install 16.2 there to loom what's going on.

I played a little bit with my phone...

For the moment I changed some values in

/sys/devices/system/cpu/cpufreq/dynamic/ overclocked my CPU to 1245mhz and GPU to 320-700mhz and RAM to 0x0005019b (1190400 kHz).

Also GPU is undervolted by 25mV and when I have time I will try to undervolt the CPU and the GPU even more.

The phone is running like this now since four days like the hell except when the governor not scales up from 400mhz. But as I said I will take a further look into this.

Just for fun:

Oops, since the update of Tapatalk there is a problem with image attaching...

Still the same... so no screenshot.

But with those settings above Antutu shows me a score of 16617 :D
[Galaxy Ace II Android Development] S.AMU:
[MENTION=5695278]ChronoMonochrome[/MENTION]

I found the solution why my phone stucks on 400mhz...

Every time I'm making a clean install (tried it several times) I have really strange settings in /sys/devices/system/CPU/cpufreq/dynamic.

For example "power_optimal_freq" is set to 200mhz, "oc_freq_boost_ms" = 100 and "max_non_oc_freq" is set to 400mhz.

This is only with clean installs. When I restore a backup and then flash the 16.2 version the settings in this folder seems normal. (Max_non_oc_freq is 1ghz, oc_freq_boost_ms is 1500 and power_optimal_freq is 800mhz)

So there is a remaining question: When I make a clean install, I'm always flashing all the packages without booting between. Should I do an boot after installing the ROM and gaaps before flashing chronokernel?

Perhaps someone can answer me the question, because I don't want to start trying again.. Its late here....
[Galaxy Ace II Android Development] ChronoMonochrome:
Thanks for the info! :highfive:

I was aware about APEATCLK and APETRACECLK(these are disabled by default), but I didn't know that SIACLK and SVACLK are used for debugging. Though, according to its names (SIACLK, SVACLK), these are should be related to Image and Video subsystems, respectively.

MCDECLK can be changed when MCDE system is powered down - i.e. when screen is off. It's well known that MCDECLK(or maybe also some other clocks) causes reboots when you change PLLDDR 0x5017f -> 0x50180. After some thoughts I came to conclusion that entire of the last byte (0x80) - multiplier - can't be stored immediately. Because 0x7f is 1111111 in binary representation, and 0x80 == 10000000, probably, it zeroes last seven bits (and temporarily sets byte to 0x00), and then sets first bit to 1. However, opposite scenario also possible. If it stores first bit at first, it temporarily cause multiplier = 0xff, thus causing reboot due to too high clocks. Don't know if I can do anything with it. Maybe I can add new interface to play a bit with bits of PLLDDR.

P.s. PLLDDR OC module recalibrates almost all clocks that depends on it (except DMACLK/ACLK), but anyway good to know that some clocks can be underclocked. :good:

Did you mean that when mali scales up it should use APE_100_OPP/DDR_100_OPP ? It's already done.

It doesn't seem that you need to boot to system after installing the ROM. Honestly, I don't know what messes parameters of Dynamic. :confused:
[Galaxy Ace II Android Development] avithohol:
Hm, i didn't try using cam corder, but apparantly if you change sva clock down too much, the cam corder stops working :), but can be set static to default frequency .

Yes, that's what i mean. Sometimes there is lag and lower scores on same benchmarks when when using 200-1200, but when cpu is set to 1000-1200 or APE_100_OPP/DDR_100_OPP, the lag is gone, and cpu is not utilized, because benchmark is gpu heavy, can be observed in epic citadel and antutu html tests. Maybe the problem is cpu overhead of constantly changing to much frequencies and voltages leading to lag. :good: :highfive:
[Galaxy Ace II Android Development] fluffi444:
This sound very familar to me. And it sounds like Gov DYNAMIC.

We discussed this already some pages before. Try to use ZenX Gov (or any more aggressive Gov)

Or you can adapt the lower liveOPPs Steps (400 and up) to APE 100.
[Galaxy Ace II Android Development] seanmalto:
Hi [MENTION=5695278]ChronoMonochrome[/MENTION] i want to ask something about GPU tweak.

how the GPU freq will be set automatically at 400/716 MHz when i want to playing a game or something like high GPU usage.

i mean, when i just using my ace2 normally (no need high GPU freq) it will be set at default GPU's freq.

Or just set it manually?

I think i ever seen a tutorial to tweak GPU at earlier time on the first page that

maybe

related to my question, but it's gone now

there are a scripts or whatever i can't remember :p.

btw thanks :D
[Galaxy Ace II Android Development] ayas02:
Problem with R2.16.1

hi ChronoMonochrome here my ksmg and my screenshot when i used R2.15 until R2.16 i allways have a same problem
[Galaxy Ace II Android Development] ChronoMonochrome:
What you've seen probably is changed GPU OC algorithm. It worked unstably for most users, therefore I removed it. So, returning to the question, shell scripts is only method to set different GPU settings. Maybe we can use CM performance for it (take a look at the end of the file /ramdisk/init.u8500.rc), but honestly, I don't know whether it'll use high performance profile in all games or not.

Did you mean that tun.ko doesn't work? I don't use it at all, so I even don't remember since which release it became broken. Maybe anyone remember?
[Galaxy Ace II Android Development] seanmalto:
Unstable right?

So i should set it manually when i want to play some game with high GPU usage.

Thanks.

At CM performance, what should i do?

I can see some script there but i don't know what to do hehe.

I found tun.ko file in system/lib/modules.

A few weeks ago, my phone couldn't connected trough openvpn. Then i found the solution from thread at xda.developers to move the tun.ko file to system/lib/modules/autoload folder. Mine(openvpn) is working fine until now.

Cmiiw
[Galaxy Ace II Android Development] avithohol:
Hi Chrono,

Have you tried using o2 or o3 optimizations when building with GCC :

https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html

also there is more infro here:

http://xdaforums.com/showthread.php?t=2754997

Are you able to boot a build with THUMB2 ?

Regards. :)
[Galaxy Ace II Android Development] ChronoMonochrome:
I use -O2 since -O3 doesn't give any noticeable improvements but only needlessly increases kernel size. I'm not able to build with THUMB2 - needed compiler that supprort ARM-specific build flags. For now I can find such compilers only for x64.

Add these lines(in the example below are GPU limits 400-710 MHz)

write /sys/kernel/mali/mali_boost_low idx=5
write /sys/kernel/mali/mali_boost_high idx=21

after lines

# High performance
on property:sys.perf.profile=2
....

and so on for other profiles. I haven't checked whether it works, this was just an idea.
[Galaxy Ace II Android Development] ChronoMonochrome:
Pushed R2.17 to FTP.

Changelog:

R2.17

LiveOPP: added ability to disable cpu freq steps

echo enable=0 > /sys/kernel/liveopp/arm_step??

Disabled step will be still shown under settings, but won't be actually used.

access to arm_steps parameters via arm_summary

echo 200000 varm-=?? > /sys/kernel/liveopp/arm_summary
echo 200000 vbbx=?? > /sys/kernel/liveopp/arm_summary
....

added 100 MHz step but disabled by default, disabled 200, 300, 500, 700 MHz steps.

So actually min freq is 400 MHz.

If you found it quirky, re-enable these steps using:

echo 200000 enable=1 > /sys/kernel/liveopp/arm_summary
echo 300000 enable=1 > /sys/kernel/liveopp/arm_summary
echo 500000 enable=1 > /sys/kernel/liveopp/arm_summary
echo 700000 enable=1 > /sys/kernel/liveopp/arm_summary

ARM VFP: enabled NEON mode in kernel (faster mode used in encryption)

VFP: updates from LK3.4

Enabled power efficient worqueue by default [zwliew]

RCU: switch to TREE_PREEMPT_RCU with RCU_FAST_NO_HZ for better power saving

Reimplemented Sweep2wake && Doubletap2wake [Meticulus]
[Galaxy Ace II Android Development] fluffi444:
Phone (8160P) is again 8160 in recovery after flashing... :o do you forget the fix?
[Galaxy Ace II Android Development] ChronoMonochrome:
Fixed in Philz, will do same fix in TWRP. Probably found one more mess in kernel installer :)

UPD. now it should be fixed. I reuploaded build with the same name. :fingers-crossed:
[Galaxy Ace II Android Development] fluffi444:
Yeb - fixed! Many thanks for that. :good:

Some words regarding de-activating steps...

Even if step00 (100000) is shown as de-activated (0) in arm_summary and not listed in arm_summary_enabled its still in CPU settings available, selectable and working... Or did I missed something?

To all: Also one remark to ChronoSettings app - this needs to be updated according to new steps - I recommed do manual uV and do chmod 444 /sys/kernel/liveopp/arm_step* afterwards that ChronoSettings cannot change it after phone booted....
[Galaxy Ace II Android Development] ChronoMonochrome:
Yep, everything as it should be. That's why I said that someone may find it quirk :D

As I said, disabled steps are still shown via settings, cpustats etc, but not actually used by LiveOPP. You can check actual ARM PLL value via:

cat /d/prcmu/regs | grep 0x0088
[Galaxy Ace II Android Development] fluffi444:
Arg - you got me - next time I have to read your changelog twice before writing... sorry...
[Galaxy Ace II Android Development] borkins:
Sorry for the big delay, guys!

The new scripts for OC DDR are here.
[Galaxy Ace II Android Development] seanmalto:
What the meaning of "reimplemented" for Sweep2wake && Doubletap2wake ?

is this has a special configuration to activate?

At latest build, both of them don't work with my device.

I activated them via novathor setting.

i'm sure that both of them are checked.

thanks.
[Galaxy Ace II Android Development] ace2nutzer:
I think it's just new Sources of s2w and dt2w .. because the old sources was removed .. because it was half broken.

(That's why i've it also removed) Usually this is a really useless feature so long it can't work without wakelock...) ;)
[Galaxy Ace II Android Development] ChronoMonochrome:
Yep, I've removed old implementations. New ones are available at /sys/modules/sweep2wake / doubletap2wake .
[Galaxy Ace II Android Development] fluffi444:
Wow - massive script with tons of functions - Good work - Works very good! :good: - like the idea to confim OC by blinking if the screen was already off!

One thing to mention: If I have DYNAMIC Gov in autoload of ramdisk, DYNAMIC was set as Gov in system, no matter what was set as Gov in System before... Lets say I have ZENX as Gov, after reboot and init.d DDR_OC the Gov is set to DYNAMIC.

If I remove DYNAMIC from autoload of ramdisk (and put the same into it as i have in system autoload) then the Gov settings are OK - even after reboot. This happens only at reboot - if the script is running out of booted system - this never happens.

I think the scribt grabs "to fast" the Gov settings at reboot and picks DYNAMIC as it is the standard in kernel - or something similar...

But as I said... Having the same Govs in autoload of system and ramdisk (and especially not DYNAMIC in autoload of ramdisk - if you don't want to use it) solves this behavior.
[Galaxy Ace II Android Development] borkins:
Thanks for your report!

The default governor is 'dynamic' after reboot. The problem is that the script didn't know what is the user's choice for CPU governor, so it use the default gov. after reboot. Did you tried to set your governor in 'settings - > performance - > processor' and set on boot activated? ( Actually that not works ) :/

I can solve that with option to choose the CPU governor in the 'init.d' option in next update.

Temporal solution:

Open the init.d script "OC_DDR" with text editor ( but not with ES file explorer ), find the variables "cpu_def_gov=$cpu_gov" ( it's under the function Get CPU governor ) and change the "$cpu_gov" with the desired governor for example "ZenX" (type exactly the governor name - it's case sensitive ) and save.
[Galaxy Ace II Android Development] fluffi444:
Sure - this is obvious but to manual interaction for me :) And if you change gov you have to change script also... And I love automatic settings :)

As often an simple sleep command at the beginning of the script also helps (sleep 90). That lets the system boots, load the users Gov and then start the script...For sure this is nothing for a script that is suited for a booted system but for an init.d it won't hurt...
[Galaxy Ace II Android Development] seanmalto:
Hmm..

Is the way i change the s2w is wrong?

I set 'enable' file inside /sys/module/sweep2wake/parameters to '1'

I have changed the permissions too.

And 'use wakelock' file is set to 'Y' by default.

Sweep2wake still doesn't works for me.
[Galaxy Ace II Android Development] ChronoMonochrome:
For me it works like a clock :) it works only when you swipe left to right.
[Galaxy Ace II Android Development] seanmalto:
Oh my bad [emoji13]

Now it works

I swiped from bottom to the top before.

Well thanks.
[Galaxy Ace II Android Development] ayas02:
So can i flash it ?
[Galaxy Ace II Android Development] shoxieJESUS:
@up

Yes.
[Galaxy Ace II Android Development] ayas02:
but why im flash kernel R2.16.x until R2.17 always stuck in samsung logo and cant boot though im follow all step in page one

- flash ramdisk

- flash kernel

- reboot

can i help me plz thanks
[Galaxy Ace II Android Development] ChronoMonochrome:
Removed it from OP.
[Galaxy Ace II Android Development] ayas02:
what mean of OP chrono ?
[Galaxy Ace II Android Development] ChronoMonochrome:
OP == Opening Post
[Galaxy Ace II Android Development] ayas02:
oh sorry im sleepy so i only flash new version kernel and done right ?
[Galaxy Ace II Android Development] ayas02:
but why bootloop after i flash R2.17 how i fixed it

my position JB 4.1.2 stockrom
[Galaxy Ace II Android Development] Ave_Hornet:
R2.18 is Ready to use? :confused::confused::rolleyes::rolleyes::eek:

@up Try to use [MENTION=5695278]ChronoMonochrome[/MENTION] Odin Kernel
[Galaxy Ace II Android Development] ayas02:
HI [MENTION=5695278]ChronoMonochrome[/MENTION]

im tested 4 chrono kernel in 4.1.2 stockrom and im flashing with new step in Opening Post

Only flash this kernel and reboot

here the kernel : R2.15.1 , R2.16.1 , R2.16.2 and R2.17

and my problem is when im flashing R2.15.1 and R2.16.1 in 4.1.2 stockrom with new step in Opening Post it works , but when im flashing R2.16.2 and R2.17 in 4.1.2 stockrom my phone stuck in samsung logo (i think is bootlop)

is new build not support in JB 4.1.2 stockrom ?

thanks [MENTION=5695278]ChronoMonochrome[/MENTION] sorry if my english is bad
[Galaxy Ace II Android Development] ChronoMonochrome:
R2.18

Changelog:

SIOPlus: update by boype

RCU, NOHz: mainly merged changes, introduced in android-3.4 branch

Futexes: cherry-picked selected commits from mainline

CIFS: fixed error, introduced after VFS layer update

VPN interceptor: same fix as above

NFS filesystem: fixed and backported to current VFS layer. Btw, anyone uses network filesystems? I haven't tested, I only checked that it correctly loads by insmod. To load NFS, you need to insmod modules in following order: sunrpc.ko, lockd.ko, nfs.ko.

UHID: probably fixed UHID broken by adding various modules for specific devices

Bluetooth: possible fix to broken data send. Needed test.
[Galaxy Ace II Android Development] ChronoMonochrome:
Check this out, now it should work.
[Galaxy Ace II Android Development] ayas02:
you mean R2.18 how flash it?
[Galaxy Ace II Android Development] shaqman89:
Looks good for a beta. It's seems that it's working well.

Confirmed working. :good:

*funny that I didn't had the slightest thought that the kernel was causing this when I tried it last week and failed :D
[Galaxy Ace II Android Development] ayas02:
im trying and still stuck in samsung logo :crying:
[Galaxy Ace II Android Development] seanmalto:
[MENTION=5695278]ChronoMonochrome[/MENTION]

One more thing.

How to set Swipe2wake permanently? I mean, when the phone is rebooted, the parameter at sys/module/sweep2wake is reset to "0" again (default).

Or i have to move the sweep2wake folder to some folder like autoload?

Thanks
[Galaxy Ace II Android Development] shaqman89:
Have you tried using init.d script?

echo 1 > /sys/module/sweep2wake/parameters/enable
[Galaxy Ace II Android Development] Kiras_PL:
How about cpu frequenties ? Is 200MHz available now ? I mean in r2.18.
[Galaxy Ace II Android Development] shoxieJESUS:
Only if you enable this freq.
[Galaxy Ace II Android Development] seanmalto:
Well, now it works even after reboot by using init.d script.

Thankyou "bang" from jekardah :D
[Galaxy Ace II Android Development] ayas02:
so any solution how fix flashing R2.18 in stock 4.1.2 because im trying new step in OP but stuck in samsung logo