yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] ChronoMonochrome:
I think my mistake is in undervolting CPU for steps 0-3. As far as i can see, it isn't stable for all users. Try to increase voltages for these steps. Default values is: 200 MHz - 0x18, 400 MHz - 0x18 , 600 MHz - 0x20, 800 MHz - 0x24. Or just wait for next release, I'll revert back CPU voltage to stock values.

Did you wipe modemfs partition? O_o

I know some people that faced this problem after them "wiped everything".

Maybe this topic can help you http://xdaforums.com/galaxy-ace/ace-2-help/baseband-xxxx-t2802864 .
[Galaxy Ace II Android Development] ChronoMonochrome:
New build is UP!

I hope it will work for all users, because now it uses default CPU voltages(except 1100-1250 MHz steps) :)
[Galaxy Ace II Android Development] teogepe:
On last 4.1.2 build wifi doesnt work...

:(
[Galaxy Ace II Android Development] xo.en:
Aaaaand, newest one for 10.2 works for me, finally!

So UV won't work with this one? I mean at <800mhz, specifically 600mhz i am using most of the time?.

Hm, weird thing - performance control is not able to change second core settings(mhz), it's stuck with 800mhz, slider is inactive..also something is overriding my dirty_writeback_centisecs from init script. Besides, everything is ok so far.
[Galaxy Ace II Android Development] ace2nutzer:
u can not set different speeds for cpu0 and cpu1.

Something else:

i wanna try to use F2FS.. can we format /system as F2FS also ? I think this improve performance also.
[Galaxy Ace II Android Development] xo.en:
Look, i dare to say otherwise. I mean - perfctrl has since last few versions such possibility, and today's kernel locks second core weird way(i CAN see that 1st is set i.e. to 600mhz but second one has still 800 mhz). Maybe it's perfctrl sudden incompatibility, need to check this...

And this is interesting - dirty_writeback_centisecs disappeared after reboot completely, so dynamic dirty writeback is new way for old method?

If so, dynamic dirty page writebacks + old dirty_backgorund_ratio together work as old centisecs now?

Ah, i see this now - if dynamic is off, then system is using old, static values.

But, still, my init value is changed into 500 for some reason..

upd: hm, machine hung at antutu 2d test at 800mhz ondemand/sioplus with dynamic writebacks on, damn.
[Galaxy Ace II Android Development] ChronoMonochrome:
Isn't there bootscripts for 4.2?

Temporarily OC via NT app disabled, to avoid possible wrong voltage overriding.

You can adjust GPU boost freq via:

chmod 644 /sys/kernel/mali/*
echo idx=21 > /sys/kernel/mali/mali_boost_high
chmod 444 /sys/kernel/mali/*
[Galaxy Ace II Android Development] str3tch72:
[MENTION=5695278]ChronoMonochrome[/MENTION]

I can see only bootscripts for 4.4 ext4 and f2fs. And I must rewrite all code and with "*" I must write GPU frequency?
[Galaxy Ace II Android Development] ChronoMonochrome:
nope, leave that code in its original form, change only idx=X, where X is number from file mali_dvfs_config.

Download it from here https://drive.google.com/folderview?id=0B_OwIFfWQnj_QkJ0Nm16UE43SGM&usp=sharing and install as it mentioned in OP.
[Galaxy Ace II Android Development] miryn:
[MENTION=5695278]ChronoMonochrome[/MENTION]

Hey, i installed 4.3 rom with Your older kernel r2.7-hybrid f2fs. Then i installed Your newest universal 2.7.4 kernel (make ramdisk->flash recovery->bootscripts[with boot.cpio for 4.3] -> 2.7.4 kernel). Ramdisk folder is empty (is it right?), and name of kernel in settings is still r2.7-hybrid, like in the picture. What may causes that i can't install that kernel?:confused::
[Galaxy Ace II Android Development] ChronoMonochrome:
There's no difference in kernel line (so 2.7.4 shows as 2.7 - it's ok).
[Galaxy Ace II Android Development] fluffi444:
Its not empty but not mounted - to see (and modify) both files in there you have to mount it (via ADB or Terminal)

mount -t ext4 -o rw /dev/block/mmcblk0p17 /ramdisk
[Galaxy Ace II Android Development] borkins:
I have some questions about the last kernel. Till now i used r2.2.

How to make GPU clock static? There is no "mali_auto_boost" file, and how to ctrl ape_opp?

In kernel 2.7.4, the autoload script not loading all governors and schedulers. Only the content in autoload folder.

Is it wrong to load everything in folder modules?

I tried 1200 MHz for about 45 mins and no reboots - like on r2.2 and some of the older kernels. I'll test it over 1200 MHz.

I don't see a significant difference in battery draining so far. Wich is good for me. Now recharging... :)

Overall: Nice kernel!
[Galaxy Ace II Android Development] ChronoMonochrome:
it's better to leave it dynamic, since static OC might work unstable. But sure, you can lock GPU freq:

chmod -R 644 /sys/kernel/mali/
echo idx=10 > /sys/kernel/mali/mali_boost_high
echo idx=10 > /sys/kernel/mali/mali_boost_low

P.S. 02mali_NT_workaround is unneeded :) it was added just to be sure that NT doesn't cause reboots due to voltage overriding.

It's better to OC GPU along with DDR - thus improves GPU performance a lot. Its perfomance also can be increased by forcing CPU 1200 MHz - unforunately, I stuck with automatic switching to max CPU freq(when GPU already reaches max freq) - for now it work unstable.

It's not wrong, but redundant - especially if most of them are unused - then they're just occupy some RAM.
[Galaxy Ace II Android Development] miryn:
[MENTION=5695278]ChronoMonochrome[/MENTION]

Something is wrong with vibrations on latest kernel (android 4.3); buttons vibrate with double power sometimes (like 2.0, when i have vibration multiplier 0.8 in settings). Beside of that i had 4 random reboots within 30 minutes. I sent You logcat via PM.
[Galaxy Ace II Android Development] manthes:
[MENTION=5695278]ChronoMonochrome[/MENTION] with 2.7.3 after many builds i don't have black screen but i have with 2.7.4.

I hope it help to find what it causes it for next builds
[Galaxy Ace II Android Development] fluffi444:
I had an random reboot on R2.7.4 / DYNAMIC while phone was on sleep... Didn't saw it - Just noticed the PIN enter screen after a while...

last_kmsg attached
[Galaxy Ace II Android Development] lars85destroyer:
I have a bug with clock. When I set its position on center, it sometimes diseppear, after a reboot for example, I need to set it back to default and then again to center to get it working back.
[Galaxy Ace II Android Development] fluffi444:
Have this also... I never paid too much attention to it :)
[Galaxy Ace II Android Development] fluffi444:
After I wrote this I had a second random reboot some few hours later - again in sleep/screen off....

After that I changed back to ONDEMANDPLUS and phone is active without issues for 18 Hours...

Maybe DYNAMIC is not yet optimized for our phone...
[Galaxy Ace II Android Development] miryn:
[MENTION=5695278]ChronoMonochrome[/MENTION]

What is the reason of such a low 'ram speed' on 4.3 kernel? Formerly, benchmark showed 400-450 ram speed, now its barely 280.
[Galaxy Ace II Android Development] matthias1976:
Dynamic

Testing Dynamic since 24h, no problems so far. Will report.

Ondemandplus got freezes in applications. Screen froze, no button workin, screen no reaktion, screen dont go off. Complete frozen. Long powerbutton for restart.

Bummer no ksmg.txt
[Galaxy Ace II Android Development] manthes:
For me Ondemandplus don't have any problems and with pegasusplus are the smoothest
[Galaxy Ace II Android Development] fluffi444:
Arg ? that didn't make it easier. Thanks for your reports.
[Galaxy Ace II Android Development] matthias1976:
same as u !!

damn i swear, direct after wrote this turn screen off and few seconds later got reboot.

kmsg.txt attached

*thx fluffi for helping with kmsg.txt*

whats ur preferences ?

min max CPU freg, iosheduler, min max screenoff, inputboostfreq ?
[Galaxy Ace II Android Development] borkins:
I don't have reboots so far. I'm using Lionheart governor - 200-800 MHz. GPU Static clock 500 MHz.

CPU Screen Off - 100-400 MHz. I'll try with lower Screen Off CPU MHz to test the stability.

I remember that on r2.2 at 46-276 MHz Screen Off i didn't got any reboots. The varm value for 46 MHz was 0x16. Here for the range 30-50 MHz is 0x1a.

If i got reboot with 0x1a i'll try with lower varm.
[Galaxy Ace II Android Development] ChronoMonochrome:
I remember some reports, that it drops by 1/4 especially on kernels with LiveOPP.

did test in Antutu 4.1.6 - 395 (DDR 796 MHz), 452 (DDR 975 MHz). Make sure your max. cpu freq uses DDR_100_OPP, otherwise its frequency is half.
[Galaxy Ace II Android Development] manthes:
200/1000 cpu

sioplus

And for memory settings i choose very aggressive. I don't make any other changes but i use carbon rom
[Galaxy Ace II Android Development] nikolas1274:
i am using carbon too, with screen off 100-400, screen on 275-1200, default freq boost, sioplus and governor i have use interactive/zenx without reboots
[Galaxy Ace II Android Development] miryn:
Is there an option to change it on version r2.2? If so, where it is, i can't find it, there's no pllddr in /sys/kernel/liveopp..
[Galaxy Ace II Android Development] ChronoMonochrome:
Sure, this is possible, but pretty difficult.

PLLDDR can be changed following way:

echo 0x8c 0x50169 > /sys/kernel/prcmu/prcmu_wreg
sleep 0.01
echo 0x8c 0x5016a > /sys/kernel/prcmu/prcmu_wreg
sleep 0.01
echo 0x8c 0x5016b > /sys/kernel/prcmu/prcmu_wreg
sleep 0.01
....
echo 0x8c 0x5017f > /sys/kernel/prcmu/prcmu_wreg

pllddr interface doing it almost same way.

(maybe anyone can write more elegant shell script for this?)
[Galaxy Ace II Android Development] Devel0per95:
can anyone please help me!

make a video about how to install the universal kernal on android JB & KK

thanks!
[Galaxy Ace II Android Development] Devel0per95:
Dude i need a video tutorial about how to install universal kernel !!
[Galaxy Ace II Android Development] Bastiary:
Thanks man, really glad that you and [MENTION=5840412]ace2nutzer[/MENTION] still develop for this phone
[Galaxy Ace II Android Development] nikolas1274:
i am using 2.7.5, first impression iis good, i am usinng both recommended tweaks (pllddr & mali) and i am still tasting

Thanks man

Edit: Is the NT conflict with the mali tweaks?

Because I have screen clinching, freezing and then I have to reboot, I am using carbon Rom
[Galaxy Ace II Android Development] ChronoMonochrome:
Maybe it conflicts with NT(check mali_dvf_config). But also try to lower GPU or/and DDR settings.

Firstly it was stable for me, when I did tests, but then it caused mentioned problems.

I'm currently testing

0x5018d (PLLDDR) and still 716 MHz GPU (so far it somehow works stable) - nope, doesn't work stably. Maybe 704 MHz will work properly - it still needs some time to turn out optimal DDR/GPU parameters.

I'm also increased up threshold - it seems 128 is too aggresive

...
echo threshold=150 > /sys/kernel/mali/mali_boost_high
...
[Galaxy Ace II Android Development] matthias1976:
2.7.4

reboot with screen off
[Galaxy Ace II Android Development] ChronoMonochrome:
sorry guys, I believe I messed up the GPU scaling algorithm in latest kernel. I'm uploading fix (R2.7.6) - temporarily dynamic_scaling algorithm is removed (dynamic algorithm used by default).
[Galaxy Ace II Android Development] nikolas1274:
can we use same pll and mali tweaks?
[Galaxy Ace II Android Development] ChronoMonochrome:
I don't know why, but it immediately reboot when I run pllddr script above. It worked like charm yesterday, that makes me wonder just stronger. :(

UPD, okay, it works only via adb, don't use script above, it's very unstable.:

(before you start, you should manually turn off display)

cd /sys/kernel/liveopp/
echo 0x5017f > pllddr
echo 0x50180 > pllddr
echo 0x5018f > pllddr
[Galaxy Ace II Android Development] nikolas1274:
Wait I lost you. Did you upload 2.7.6. ?

And can you explain better what are you saying above?

And by the way I have the same problem as you with pll, first time ok but then when it become unstable and I had to reboot when I try to tweak it again I had immediately reboot
[Galaxy Ace II Android Development] ChronoMonochrome:
Okay, somehow it wasn't uploaded, now reuploading.

I mean first script above can't be executed now, it stucks on line with '0x50180 ...'

Do exactly same, i.e. wait until the media scanner finish its work, lock max cpufreq(set gov. performance or set i.e. 1200-1200 MHz), then turn off screen and run script(via adb) from previous post line by line. After that you can unlock cpufreq.

By the way, have anyone problems with playing the sound with these MALI/DDR tweaks (maybe sound shuttering or stopping playing?)

I had on previous version, and still don't know if it's fixed on 2.7.6.
[Galaxy Ace II Android Development] nikolas1274:
Do you mean adb from pc ?
[Galaxy Ace II Android Development] fluffi444:
Which mali_boost_high / mali_boost_low threshold values do you have? Looks like Chrono use much more conservative values as they were in 2.7.4... maybe an reason for all thoses freezes/reboots/suck after sleep (which I had also...)
[Galaxy Ace II Android Development] Kiras_PL:
Do we need to use init.d scripts with mali wotkaround and zram disabling? Im on 2.7.6 now.
[Galaxy Ace II Android Development] Devel0per95:
guys can anyone please reply to me -_- !!!!!!!!
[Galaxy Ace II Android Development] fluffi444:
Using also R2.7.6 and had problems to run pllddr also:

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

in my "optimization" init.d script... It gave me corruption of grafix and freeze while CM Bootlogo...

After I put this part (to set pllddr) in my "after kernel" script with an additional wait time of 120 it works again!

Maybe we need to let the kernel do his thing and set the pllddr after all is loaded...
[Galaxy Ace II Android Development] ChronoMonochrome:
I think it's better to use init.d instead... it's really unneeded to hardcode these things in kernel.
[Galaxy Ace II Android Development] fluffi444:
Never said something else :) If I talk about scripts I mean init.d scripts...
[Galaxy Ace II Android Development] ChronoMonochrome:
I mean it's better to leave these things to init.d(not kernel), as you previously said. The kernel don't "know" when the system is completely loaded - and even if I'll use same timeout (120 sec.) it cannot guarantee stability in 100% cases. It's better to leave that tweak to userspace, what I exactly meant.
[Galaxy Ace II Android Development] fluffi444:
I think we missunderstood eachother :D... I dont want to say that we need to include it in kernel... I just wanted to say that an additional wait time of 120 in init.d script does the trick for me... nevermind...

In older versions the pllddr was accepted without issues even without additional wait time... But R2.7.6 seams to need it...
[Galaxy Ace II Android Development] matthias1976:
never changed em, so i think its stock chrono kernel 2.7.4 values !?
[Galaxy Ace II Android Development] fluffi444:
If I remember correctly the value were a bit to agressive - try the defaults (192/64)

http://xdaforums.com/showpost.php?p=57207113&postcount=1774

If it works you can adjust them a bit lower ...I'm trying 128/64 right now... But not for a long time...

Or take a look what ChronoM is using (if its still the current state :))

http://xdaforums.com/showpost.php?p=57335604&postcount=1807
[Galaxy Ace II Android Development] ChronoMonochrome:
still trying to deal with performance and powersaving :D

the problem is, when not playing games, then it's unneeded to use such aggresive values :)
[Galaxy Ace II Android Development] matthias1976:
chmod 644 /sys/kernel/mali/*

echo threshold=192 > /sys/kernel/mali/mali_boost_high

echo threshold=64 > /sys/kernel/mali/mali_boost_low

chmod 444 /sys/kernel/mali/*

these lines in init.d 00autoload if i want them load by default !?

i never playing games !!

just want stable phone with most powersaving
[Galaxy Ace II Android Development] miryn:
[MENTION=5695278]ChronoMonochrome[/MENTION]

Hey, Your kernel is still not compatible with performance control; cpu freq changed once, can't be changed later. What's the reason of that?
[Galaxy Ace II Android Development] str3tch72:
[MENTION=5571055]miryn[/MENTION]

Try SetCPU. Working good.
[Galaxy Ace II Android Development] miryn:
Yep i know about this app, but if i remember, it doesnt even have adjustable i/o scheduler. Performance Control is an all in one app.
[Galaxy Ace II Android Development] nikolas1274:
At R2.7.6 I can not tweak Mali or pll, my phone reboots after adb commands
[Galaxy Ace II Android Development] ace2nutzer:
I'm using high=128 and low=16 without problems.. but don't forget these Values must be adapt. with the Min. GPU Freq..

The Values what i wrote here are optimized for min GPU 400Mhz.
[Galaxy Ace II Android Development] nikolas1274:
I can not change parameters for mali neither from NT, it cause me freeze my phone at R2.7.6, i roll back to R2.7.4 till new realise
[Galaxy Ace II Android Development] str3tch72:
Need any screen to trust me bro? I'm using it right now :)
[Galaxy Ace II Android Development] fluffi444:
In which way they must be adapted? :confused:
[Galaxy Ace II Android Development] nikolas1274:
When I try to roll back to R2.7.4 I had to much freezes and when i flash again I reboots after pin enter, so I format system and then I flash again Rom, gapps and R2.7.4, and more it's all ok, sorry I can not take log cat
[Galaxy Ace II Android Development] 1N4148:
Maybe the PLL is getting unstable with a too low multiplier (80). So try a matching combo of divider (4) and multiplier (>80)
[Galaxy Ace II Android Development] ChronoMonochrome:
The problem is, the change of divider also cause reboot :(

Unfortunately, we can set only multiplier that lower or higher by 1 than current PLL (e.g. 0x50168 -> 0x50169 -> .. -> 0x5017f). This is that does current DDR OC algorithm. But thanks for idea, I'll try to set 0x5017f, and then just skip 0x50180. Not sure that it'll work, but I'll try.

Somehow NT App became fully incompatible with new GPU algorithm and now this app cause reboot, when trying to read/write some mali interfaces. I'll provide temporarily workaround asap (it seems we can just disallow its access to mali sysfs by removing its permissions in device_tunables.rc).
[Galaxy Ace II Android Development] ChronoMonochrome:
pllddr_oc script update

#!system/bin/sh
set -x

# Abb-ponkey doesn't have its own wakelock
# so as temporary dirty approach, we use there dt2w wakelock while the script running.

echo Y > /sys/module/doubletap2wake/parameters/use_wakelock
echo 1 > /sys/module/doubletap2wake/parameters/enable

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 0x5017f > /sys/kernel/liveopp/pllddr
sleep 0.5
echo 0x50180 > /sys/kernel/liveopp/pllddr
sleep 0.5
echo 0x5018f > /sys/kernel/liveopp/pllddr
sleep 0.5
echo 1 > /sys/kernel/abb-ponkey/emulator

echo $MAXFREQVAL > $MAXFREQ

echo N > /sys/module/doubletap2wake/parameters/use_wakelock
echo 0 > /sys/module/doubletap2wake/parameters/enable

Abb-ponkey doesn't have its own wakelock, so as temporary dirty approach, we use there dt2w wakelock while the script running.

UPD. Unfortunately, still cause reboot sometimes.
[Galaxy Ace II Android Development] fluffi444:
I still got freezes. Manly after Phone was one for approx 20-24 hours. Don't know really why. Not logcat_kmsg available because I had to hard reboot phone after freeze (Phone stuck without any response)

R2.7.6 -> CPU 200-1200 / GPU 320-560 (up/down 128/64) / DDR 975
[Galaxy Ace II Android Development] borkins:
If someone wants to try it, in the zip package is mine script method for pll ddr clock change.

In short:

The script set the CPU at max and static freq.,turning OFF the display, sets 975 MHz, turning ON the display again and unlock it.

Well, it's not elegant, and maybe it's funny, but working for me. It's written for Smanager, but also working as init.d script.

P.S. - when I use it as init.d the screen is not turning OFF for some reason, but in my tests i don't had reboots.

Look here:

http://xdaforums.com/showpost.php?p=57395364&postcount=1846
[Galaxy Ace II Android Development] S.AMU:
So I just tried it out, but the script says that the new frequency is the old one.

I didn't took a look to the script, and perhaps it is working, but only displaying the wrong value.
[Galaxy Ace II Android Development] borkins:
PLL DDR OC Scripts / Last Update: 20160208

1. "OC_DDR" as init.d script - set 1000 MHz DDR clock by default. Time to OC ~ 6 min.

2. "OC_DDR.sh" for manual overclock with SManager app.

(!) Smanager's script is configured for 'Swiftkey' keyboard app and 'Menu' button unlocking the screen -> enabled...

____________________

How to use:

1. Place OC_DDR script in '/system/etc/init.d' folder with permission 755, 0, 0.

2. Start OC_DDR.sh, and once you agree a list with the available frequencies will show up.

3. To unlock the OC_DDR script - press 'i' and the init.d script menu must show up.

4. To select other frequencies - start 'OC_DDR.sh' script and then press 's' to enter in the advanced settings.

Disclaimer: I'm not responsible, for any of the consequences by using this scripts,

such as: data lost, hardware damages, or etc.! Use it on your own risk!!!

____________________

What's new:

OC_DDR - init.d script:

- The operation will be aborted at 2nd CPU usage check, if the system load is high more than 5 min. after reboot.

- Minor changes in the log file.

OC_DDR.sh - Smanager's script:

- More frequencies to set.

( There is hidden advanced option, if you want to set other frequencies )

- User can manually cancel the operation, during the CPU usage checks.

- New UI

OC_DDR & OC_DDR.sh scripts:

- Disabling Mobile Data & Wi-Fi during the OC ( for even more stable DDR OC process ) - thanks to [MENTION=4962787]fluffi444[/MENTION] for the idea!

- CPU usage in percents, for more precision by using the lowest system load, during the OC.

- BLN signal, and pause of the OC process ( as reminder to disconnect the charging source, for less system load )

*Note: The scripts are not tested by me on android above 4.4.4!

* Send a PM to me for problems, questions or advices and etc. about the scripts.
[Galaxy Ace II Android Development] S.AMU:
For me it is working like a charm now. :)
[Galaxy Ace II Android Development] ChronoMonochrome:
4.4.x f2fs bootscripts (fix for Novathor App)

Now GPU settings won't work, but I had to do it, to fix reboot issues, which happens when use shell commands.

https://drive.google.com/file/d/0B_OwIFfWQnj_YUpYTzNmd0ZHcFU/view?usp=sharing
[Galaxy Ace II Android Development] zipperX:
Are you interested with this http://xdaforums.com/android/software-hacking/kernel-tap2unlock-tap2wake-feature-t2965344 [MENTION=5695278]ChronoMonochrome[/MENTION] [MENTION=5840412]ace2nutzer[/MENTION] ? I think we can get this feature for our codina
[Galaxy Ace II Android Development] nikolas1274:
With new boot script I manage to flash R2.7.4 kernel without reboots.

So what script can I use now to tweak pllddr and Mali?
[Galaxy Ace II Android Development] ChronoMonochrome:
I'm using standard up/down thresholds and pretty satisfied with settings from signature.
[Galaxy Ace II Android Development] matthias1976:
Same here !!

never happend when phone above 50% charging and under 24 h ontime.

I restart when i charge. Phone work like charm till 24 h ontime and 50% battery.

After that phone gets unstable. Mostly restart when deepsleep or screen freeze no reaktion of everything. Powerbutton press for loong time to restart.

R2.7.4 -> CPU 200-1200 screenoff 100-200/ GPU (up/down 192/64) ondemandplus
[Galaxy Ace II Android Development] ChronoMonochrome:
Will look what I can do asap.
[Galaxy Ace II Android Development] fluffi444:
Interesting theory... Will also take a look on that charging thing, too - Otherwise absolutly the same behaviour as you reported...

For testing I remove now DDR OC and set also CPU up/down thres to standard...

codinaP - I'm on R2.7.6 / CPU 200-1200 / Off 200-350 / GPU 320-560 / Interactive

Lets see what another day will show (or not) :D

Thx for looking into it, [MENTION=5695278]ChronoMonochrome[/MENTION]