yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] fluffi444:
Hey Borkins...

there is an issue with DDR/APE OPP... Newer Kernels of Chrone hasn't the DDR/APE value in LiveOPP steps anymore.

Looks like that the script ran into erros because of this part:

if [ "$crt_ddr_opp" -lt 100 ]; then
ddropp_spc=" "
fi
if [ "$crt_ape_opp" -lt 100 ];
then
apeopp_spc=" "
fi

This is the output

LiveOPP ARM Steps Editor
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Loading the ARM Steps Data...
/storage/sdcard0/_CM/Script/ARM_Steps_Editor.sh: line 265: [: : integer expression expected
/storage/sdcard0/_CM/Script/ARM_Steps_Editor.sh: line 268: [: : integer expression expected
/storage/sdcard0/_CM/Script/ARM_Steps_Editor.sh: line 265: [: : integer expression expected
/storage/sdcard0/_CM/Script/ARM_Steps_Editor.sh: line 268: [: : integer expression expected
/storage/sdcard0/_CM/Script/ARM_Steps_Editor.sh: line 265: [: : integer expression expected
/storage/sdcard0/_CM/Script/ARM_Steps_Editor.sh: line 268: [: : integer expression expected
/storage/sdcard0/_CM/Script/ARM_Steps_Editor.sh: line 265: [: : integer expression expected
/storage/sdcard0/_CM/Script/ARM_Steps_Editor.sh: line 268: [: : integer expression expected
/storage/sdcard0/_CM/Script/ARM_Steps_Editor.sh: line 265: [: : integer expression expected
/storage/sdcard0/_CM/Script/ARM_Steps_Editor.sh: line 268: [: : integer expression expected
/storage/sdcard0/_CM/Script/ARM_Steps_Editor.sh: line 265: [: : integer expression expected

LiveOPP ARM Steps - Table
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
AS CLK Voltage Varm / Vbbx DDR/APE OPP
1 200 MHz 850 mV [0x0c] [0xdb] [] []
2 300 MHz 900 mV [0x10] [0xdb] [] []
3 400 MHz 975 mV [0x16] [0xdb] [] []
4 500 MHz 1050 mV [0x1c] [0xdb] [] []
5 600 MHz 1075 mV [0x1e] [0xdb] [] []
6 700 MHz 1125 mV [0x22] [0xdb] [] []
7 800 MHz 1162.5 mV [0x25] [0xdb] [] []
8 1000 MHz 1350 mV [0x34] [0x8f] [] []
9 1100 MHz 1375 mV [0x36] [0x8f] [] []
10 1150 MHz 1375 mV [0x36] [0x8f] [] []
11 1200 MHz 1387.5 mV [0x37] [0x8f] [] []
12 1215 MHz 1387.5 mV [0x37] [0x8f] [] []
13 1220 MHz 1387.5 mV [0x37] [0x8f] [] []
14 1245 MHz 1387.5 mV [0x37] [0x8f] [] []
Enter ARM Step (1-14):

Anyway - the script is working... even with this output....
[Galaxy Ace II Android Development] borkins:
Sorry I didn't know that this part is removed from newest kernels.

I'm still on r2.21.
[Galaxy Ace II Android Development] ChronoMonochrome:
R2.23

New build is up.

Changelog:

lcdclk: added 30,72 MHz mode (default one on s6d)

probably fixed problems with screen blinking on s6d as 49,92 MHZ no longer forced for it

added patch that allow us to edit HWMEM size directly in zImage - http://xdaforums.com/showpost.php?p=60357264&postcount=29

http://xda.mister-freeze.eu/XDA-files/ChronoMonochrome/kernel/chrono_kernel_r2.23.zip
[Galaxy Ace II Android Development] str3tch72:
Can I install it on CM12.1 without any problem?
[Galaxy Ace II Android Development] Ave_Hornet:
Yes in r.23 bootscripts for 5.1 are included.
[Galaxy Ace II Android Development] xo.en:
Damn...chronokernel app became even more outdated now...(no 30.72 selectable)...if it was windowsmobile, i'd hexedit exe...hm, need to check how table is implemented in apk.
[Galaxy Ace II Android Development] shoxieJESUS:
@up

Terminal command or init.d sript... or you lazy for doing it?
[Galaxy Ace II Android Development] xo.en:
I know that...I am reporting another sad news, just that. Yeah, i am lazy...ok.

btw, is this me, or that version is..slower or something? Scrolling seems to be worse, kinda jerky(as with old cm).

Also - entering to cwm is weirdly..delayed/slowed, hard to say what this is tbh.

Both things may be related.

Or i am just seeing things, i do not know now.

S6d onboard here.

Going back to 22.5, which works perfectly for me...
[Galaxy Ace II Android Development] ChronoMonochrome:
I believe I did a stupid mistake. I've reuploaded fix(same link), now s6d uses lcdclk=36 MHz. Probably it even doesn't so matter, what frequency is used, but when stock LCDCLK algorithm used, both of displays suffers of tearings. There is now applied fix, that will (hopefully) allow to avoid tearings even with such low freq, as it was on R2.22.5. I also need to ask users of s6d post here output of lcdclk interface:

cat /sys/kernel/mcde/lcdclk

There is added lcd type detection, I need to know, whether it works properly. Thanks in advance.
[Galaxy Ace II Android Development] ace2nutzer:
Check those commits:

https://github.com/ace2nutzer/Samsung_STE_Kernel/commit/c16aab01fd07b7cad83350c9a457c8a9291e9ca3

https://github.com/ace2nutzer/Samsung_STE_Kernel/commit/702c4d84b869e665d4bed805e86efcd7d5c5a199

https://github.com/ace2nutzer/Samsu...db8#diff-7f92e916b1f11a25727be19b75820fb2L138

S6D Don't have screen tearings .. but it's laggy when freq 31Mhz, and 33Mhz is used..

With 36Mhz + the optimizations above it's smooth like hell... ..

And with Stock LCD Freq for WS2401 + Optimizations, tearings are fixed.. and may even nearly smooth like 57Mhz ...

Worked the half day for this Optimizations :o
[Galaxy Ace II Android Development] ChronoMonochrome:
Yeah, actually I looked at these changes and came to conclusion in previous post.

lcdclk_usr isn't initialized here:

https://github.com/ace2nutzer/Samsu...455e74d712/drivers/video/mcde/mcde_hw.c#L1221

and because of that, following line always works:

https://github.com/ace2nutzer/Samsu...455e74d712/drivers/video/mcde/mcde_hw.c#L1379

(when unitialized, lcdclk_usr will almost never be 0)

I just explicitly forced this update of LCDCLK when on suspend.
[Galaxy Ace II Android Development] ace2nutzer:
It's not needed, when the user don't touch anything, then it's running all the time @ kernel defaults like in board_codina_mcde.c ...

50Mhz for WS24 and 36Mhz for S6D

and when the user do a init.d script, with for example 57Mhz on WS2401.. then it stays on 57Mhz .. or i'm wrong ?? Every time on suspend rebasing LCDCLK to kernel defaults.. and on resume again user CLK ??

But even if it's wrong i've zero problems here on s6d .. :) And user interface is working properly.
[Galaxy Ace II Android Development] ChronoMonochrome:
Nope, I didn't say it's wrong, anyway, as the saying goes, if it ain't broken, don't fix it. I just mean it works quite different from what was supposed. http://en.wikipedia.org/wiki/Uninitialized_variable

In this case by default kernel will (almost) always rebase LCDCLK, despite of lcdclk_usr was supposed to be 0.

UPD. nope, just forget everything above, this is not that case, where lcdclk_usr doesn't get 0 by default. It will always 0

as lcdclk_usr is declared as static. Therefore everything works as was supposed, however having unitialized variables may sometimes cause bugs, which very hard reproducible.
[Galaxy Ace II Android Development] ace2nutzer:
okay, u're right.. if i set here:

https://github.com/ace2nutzer/Samsu...455e74d712/drivers/video/mcde/mcde_hw.c#L1221

36305454

Then it's okk ??

I choose for kernel default 36Mhz.. because in case of messed up with LCD detection ws24 or s6d.. that freq will work always stable .. because 36Mhz works on both LCD without problems .. (at lest no screen freezes or blinking) but 50Mhz is too risky to use @ S6D ...
[Galaxy Ace II Android Development] ChronoMonochrome:
Nope, you don't need to. I edited previous post, lcdclk_usr is always 0, then it's ok. You only can explicitly assign 0 to it (but this won't make any changes in code).
[Galaxy Ace II Android Development] xo.en:
I, uh, let me say this:

22.5 vs 23.0.

Difference is tremendous.

Latest one REALLY feels different.

Tearing in 2d, everywhere. Feeling of slugishness, etc.

Again - canabalt is the best test, btw...

You may laugh at me, but i really can recommend this title to feel rom/kernel differencies.

I remember line of cm with similar behaviour, weird shimmering while scrolling, broken 2d...lag. Feels similar now.

C'mon, don't you feel this difference, guys?

btw - i can recommend removing zram init.d after flash(and reboot, of course).

This device really works better without that one.

NO zram, or change swappiness to 20 there(with proper lmk/vm settings, of course).

zram is the killer, imho..

Look - this machine may be considered as weak one, but there is a catch - it works nice when it is set to as passive as can be(again, proper lmk/vm, and LOW caches for int/ext mem)..

Ondemandplus/tripndroid user, repacked apps/framework, zero gapps here, s6d.

22.5 is great.
[Galaxy Ace II Android Development] Ave_Hornet:
For me its even better than previous build or placebo, but this is small changes.Do not expect to much. 400-1220 /Fiops/ 320-700[uv-12]

Again thanks [MENTION=5695278]ChronoMonochrome[/MENTION]
[Galaxy Ace II Android Development] str3tch72:
For me it isn't placebo. Even on 800mhz and no GPU Oc phone running so smooooth. UI is smooth as butter, apps running without any lags. I tested only one game (Pixel Dungeon, great 8-bit RPG game) and I does't have any glitches etc in interface. :D
[Galaxy Ace II Android Development] ChronoMonochrome:
What about lcdclk=49,92MHz?

Anyone's else experience?
[Galaxy Ace II Android Development] heldix:
Z-Ram isnt even enabled at genuine unmodified 2.23...

Tested it some hours until now very happy with it.
[Galaxy Ace II Android Development] shaqman89:
I agree.. Its smooth and fast. Nothing to complain about so far.
[Galaxy Ace II Android Development] manthes:
It is working (s6d)
[Galaxy Ace II Android Development] fluffi444:
Also for WS2401... btw... R2.23 is running very good. No issues found so far... :good:

But RAM is decreasing ;) 628 MB here...

IMHO there are too much modules (Govs/IO) loaded but default. Don't if this make a difference actually.
[Galaxy Ace II Android Development] ChronoMonochrome:
This is due to selinux... you know, cm12.1 requires it to be supported in kernel. Later I'll make build without selinux.

There are only ondemandplus/interacive and bfq.
[Galaxy Ace II Android Development] ace2nutzer:
Wow, SELinux is sucking 2 - 3 MB RAM ?? :cyclops:

@ fluffi

Less RAM doesn't mean always "less optimized" or "less performance" because we can build the kernel with some optimizations related to our Cortex-A9 CPU and optimize the Code for e.g. FPU, (floating point unit) ; NEON Virtualization; vectorinzing etc.. what will result in a bigger Code (less ram available) but increase the Performance due to the optimizations .. ;)

(OFFTopic: That's why my next release will have 629MB instead of 630MB RAM) :cool:
[Galaxy Ace II Android Development] shaqman89:
[MENTION=5695278]ChronoMonochrome[/MENTION]

I have a strange issue with logcat with your kernel. Is it somehow disabled for application? The logger module is loaded, and through adb it is viewable but not for any apps at all. I have tried both with dalvik and art and neither actually helps.

Here is my log from logcat: https://docs.google.com/file/d/0Bzo3MSxg_YFCMVplN2MzZUJCWEE/edit?usp=docslist_api

Thanks.

Edit: it is not exclusive in the latest kernel but when I tried [MENTION=5840412]ace2nutzer[/MENTION] kernel it works fine.
[Galaxy Ace II Android Development] ChronoMonochrome:
That looks really odd. But maybe this is due to logger built as module, not built-in. Btw, what app you can suggest for logcat testing? I've moved logger.ko to /ramdisk/modules/autoload/ , to have it loaded ASAP, and now I've in logcat messages from system apps like SettingsProvider, BluetoothAdapter etc. But so far I haven't found any user app, that print smth to logcat.

AFAIK, build with -Ofast flag "eats" ~2MB and selinux - less than 1.
[Galaxy Ace II Android Development] shaqman89:
It might be so, but if I remember correctly, the first builds works Okay when the module is loaded. Too bad I can't actually pinpoint yet when the issue started. I might try to go some versions back to see later.

What do you mean by testing? If you mean for grabbing then I am using AndyLog. But as for the results, I usually try with bbm or any app that takes location (they usually print quite much of a log).
[Galaxy Ace II Android Development] ChronoMonochrome:
No, I didn't mean app for grabbing logcat :D terminal is enough for me and I really prefer it than GUI apps. I mean, what apps does print something to logcat.

UPD. ok, I'll try bbm.
[Galaxy Ace II Android Development] ace2nutzer:
@ Chrono

Just an idea... i've compared my CFLAGS with yours and i saw that some used flags in your makefile can cause less tracing / debugging information...

But i'm sorry that i can't post here the specific flags.. it was late in the night and i was very sleepy :eek:
[Galaxy Ace II Android Development] xo.en:
..another day, 600mhz ondemandplus with s6d set to 50hz.

This is insane - fluidity is perfect.

It is like slowing device down makes it...better, i mean.

2.25 here(since i am lazy to make 15th init script to make 2.3x useful).

600 mhz...damn.

This is so fkin impressive...yeah yeah i am boring, i know..

btw, i wonder, how slimbean 4.2.x would work( slimmer, miryn :) ).
[Galaxy Ace II Android Development] aj10:
[MENTION=5695278]ChronoMonochrome[/MENTION] i switched back to this kernel after trying [MENTION=5840412]ace2nutzer[/MENTION]s. i think i read that i should delete the contents on init.d folder before flashing the kernel - so i did. during phone use, the screen goes black at times and the phone lags (2.3 kernel).

also, deep sleep does not seem to work as well as in [MENTION=5840412]ace2nutzer[/MENTION] kernel for me. on his kernel, i would unplug my phone from 100%, not use it, and it would report it is still on 100% a while later. on your kernel, the battery level reports it decreases by about 6% after some time. i use bbs but it doesn't seem to report anything unusual. is it just that your kernel reports battery % differently?

before i installed this kernel, i wiped cache and dalvik cache. i can live with the battery decrease, but the black screen bug is annoying. should i run logcat?
[Galaxy Ace II Android Development] ChronoMonochrome:
Did you mean 2.23? Because 2.3 is an outdated build.

There is no problem with deepsleep. Check whether google services keep device awake. About battery level, it still makes me wonder, since we are using same volltage table. As far as I'm aware this battery drop right after charge is no more than only visible change, it doesn't mean that charge drops to level, which is showed. You can try to use this kernel till battery fully discharged, and compare battery life time with one that you've on ace2nutzer's kernel.

As for bs bug... logcat is unneeded, but you can tell me your display driver and try to use same LCD freq which you've used before.

cat /sys/kernel/mcde/lcdclk # show lcd type and freq

to set different lcdclk freq:

echo lcdlck=xxxxxxxx > /sys/kernel/mcde/lcdclk

If this won't help, I'll consider to look whether default GPU voltage needs to be changed.
[Galaxy Ace II Android Development] aj10:
[MENTION=5695278]ChronoMonochrome[/MENTION]

thank you for your reply.

sorry - yes, i meant 2.23 kernel.

in privacy guard, i have disabled almost everything for google play store and services (example, keep awake denied - 76773 times, allowed 50 times - ?). play services also used cell scan 12881 times (!). it seems i cannot disable cell scan.

lcd is currently on ws2401 default (60hz). frequency is 49920000. what frequency should i change it to?
[Galaxy Ace II Android Development] ChronoMonochrome:
So, you answered on your question about deepsleep then.. I cannot suggest anything, cause I don't use google services.

There is no need to change lcd freq then. I should ask what's type of black screen bug have you faced. First, most typical, is when you see black screen after unlocking, or second, more non-typical, when you getting screen messed (it gets "black" even when phone is unlocked).

Secondly, are you using default GPU frequency? You can try to increase GPU voltage to see if this helps

cd /sys/kernel/mali
echo 5 vape=26 > mali_dvfs_config
[Galaxy Ace II Android Development] aj10:
i guess so.

my black screen issue only happens sometimes when i open an app, and/or switch from one app in memory to another (say, check email, then switch to web browser). what also happens is: i open an existing app in memory/task switcher, and it opens another app (say i switch to web browser, it wold open whatsapp instead). i also sometimes get a black screen when trying to unlock the phone - this is very rare though.

i am using default gpu frequency, yes. i will edit it as you suggested and let you know.

thank you very much for your help.
[Galaxy Ace II Android Development] ChronoMonochrome:
This probably means that phone running out of memory, but this also maybe due to badly tuned kernel scheduler. Do you use any init.d scripts?

Btw, you can also try to install this CM11 build. Not that it has better memory management, but according to my feelings it's by far faster than older CM11 builds - therefore there are chances, that switching between apps will be faster.
[Galaxy Ace II Android Development] ace2nutzer:
Sounds like overloaded RAM ;)

Probably other Minfree Values can help .. :)

Actually i use: 20,30,40,50,70,90 Values in MB .. if they didn't help.. try increasing linear of +10MB .. like this: 30,40,50,60,80,100 MB ;)
[Galaxy Ace II Android Development] aj10:
thank you both for your reply.

chrono - i am not using any scripts. i will try your suggestion, and if that 'fails', i will try ace's.

thanks again.
[Galaxy Ace II Android Development] ChronoMonochrome:
Changing minfree values is probably good advice too :) It's most dependent on usage, however, and I didn't mess with minfree yet, because I rarely run into OOM like in post above. But if you often face OOM, then you definetely can try change minfree to see whether it helps.
[Galaxy Ace II Android Development] ace2nutzer:
Are u using maybe ART ??!!
[Galaxy Ace II Android Development] ChronoMonochrome:
R2.24

It was a long time since there were any significant changes, now, R2.24 is up.

Changelog:

disabled selinux again

vmalloc size decreased to 192M

ARM: 7746/1: mm: lazy cache flushing on non-mapped pages - increased performance in some test cases by 25%

ARM: 6998/2: kernel: use proper memory barriers for bitops

sync: added synchronization framework

backported ashmem from hammerhead - thanks [MENTION=4615478]boype[/MENTION]

ARM: mm: Optimise the v7 Dcache flush all routine

Enabled CONFIG_MMC_BLOCK_BOUNCE (thanks to [MENTION=5840412]ace2nutzer[/MENTION] !) - according to Quadrant, I/O performance has increased by 13%

zcache: updated to LK3.11 and enabled by default, backport by [MENTION=943196]k2wl[/MENTION] (thanks [MENTION=3329816]mkaluza[/MENTION] for figuring out how to make zcache work)

zcache: enabled LZ4 compressor instead of LZO as it's more efficient

cpufreq: dynamic: increased input_boost_ms to 250ms in order to fix little stuttering

various fixes

Download

Note, that this build doesn't support android 5.1 and higher as selinux is disabled!
[Galaxy Ace II Android Development] Ave_Hornet:
:/

It will be a version of SELINUX ? or if there is a workaround for this Barrier.?To run 5.1.x Android without Selinux.

As Always Many Thanks for hard work. :D
[Galaxy Ace II Android Development] ChronoMonochrome:
As far as I'm aware, selinux should be disabled in ROM, to allow it be disabled in kernel, at least I've seen some ROMs with tomoyo as default security. Don't know though, is there way to get rid of any security. As for now, since switching between selinux and non-selinux builds becomes a bit messy, I decided to return to 4.4.x. Besides of uselessness of selinux on android, AFAIK, there are some issues with selinux on 5.x.x, that makes me more unwilling to make builds with it and use it.
[Galaxy Ace II Android Development] manthes:
I am not sure if it has any difference in performance. I think is the same with previous
[Galaxy Ace II Android Development] str3tch72:
Everything works fine with this kernel?
[Galaxy Ace II Android Development] Nathanabrahams:
Battery life is worse but it is very stable and haven't have any reboots so far (fingers crossed)
[Galaxy Ace II Android Development] ChronoMonochrome:
Can anybody confirm this? I get average screen on time of 4 hours on my normal usage.

Yes, but only for versions with ext4 because I have not found twrp with f2fs support.

Hmm, interesting information. I'll try to play with it at a leisure.
[Galaxy Ace II Android Development] teogepe:
How did you enable the 16-bit transparency on stock...

I cant find that option. :o:confused:
[Galaxy Ace II Android Development] hmzh:
Here my battery usage
[Galaxy Ace II Android Development] Nathanabrahams:
My battery problem wasn't kernel it was my battery... It needed to be taken out and put back in.... It's the usual usage now..... Sorry for that
[Galaxy Ace II Android Development] manthes:
My feedback for the kernel from the link didn't solve the problem with black screen on cwm. Also with latest build of liquid rom i have black on lockscreen only while i am charging (of course i am using kernel with twrp)
[Galaxy Ace II Android Development] miryn:
[MENTION=5695278]ChronoMonochrome[/MENTION]

What program do You use to change CPU freq, gov, etc.?
[Galaxy Ace II Android Development] zizoumadrid:
I recommend you to use nofrills cpu or setcpu :)
[Galaxy Ace II Android Development] judas1977:
Strange thing - performance control, nofrills, perf ctrl from slimkat seems to stuck on 800Mhz... when i choose another frequency and leave abovementioned app - it gets back to 800...BUT it seems that chosen freq stays despite of that... more tests soon...

EDIT: i'm talking about seflcompiled kernel, but only difference is changing that lines i spoke with serge...
[Galaxy Ace II Android Development] miryn:
Nofrills too? I had the same problem (Xoen also talked about it long time ago) on last two

Chrono's

4.3 kernels.. After changes it still returned to the previous (800Mhz) state; That's the reason i asked a question about app for cpu controlling..
[Galaxy Ace II Android Development] danny19901:
Use kernel tweaker for OC etc... Best app I use with no issues if can't find on Playstore I will upload it
[Galaxy Ace II Android Development] borkins:
I got one reboot on 3.1.1 kernel ( JB stock 4.1.2 MG2 ). CPU 400/1000 MHz - pegasusq ( varm 0x24 for 400, 600, 800 MHz, 0x2f for 1 GHz ).

The same settings i used successfully on build 29/08. :/

Here is the last kmsg log:
[Galaxy Ace II Android Development] ChronoMonochrome:
Yeah, It's known problem. It's related to CFQ scheduler, I just need to revert few last changes in CFQ or update it to version that uses in 3.1 kernel.
[Galaxy Ace II Android Development] forbidden8:
Pimp my rom have that option.
[Galaxy Ace II Android Development] Bastiary:
[MENTION=5695278]ChronoMonochrome[/MENTION] i tried your latest 3.1 kernel on AOSPA but got bootloop, any chance you will make aospa version,.?
[Galaxy Ace II Android Development] danny19901:
I have been using F2FS kernel for a while but determined to try EXT4 but my memory card isn't EXT4 formated does it matter or not also should i format system to EXT4 as well as cache etc...
[Galaxy Ace II Android Development] ChronoMonochrome:
Which version did you try to install(F2FS, EXT4)?

It does not matter formated your sdcard to ext4 or not. If you use ext4 or F2FS version, /system should be formatted to ext4.
[Galaxy Ace II Android Development] danny19901:
OK thank you
[Galaxy Ace II Android Development] ChronoMonochrome:
Did you some measurement or came to this conclusion due to subjective feelings? I guess, it won't show any visible improvements simply because those optimized part of code runs not so often to notice significant difference. Nevertheless, if it can benefit anywhere it's better to have those changes, it won't hurt anyway.
[Galaxy Ace II Android Development] manthes:
Just feeling. Anyway the performance was already very good and maybe only who they play games will understand something more
[Galaxy Ace II Android Development] ChronoMonochrome:
Yeah, you are probably right, performance is almost maximized here, however it's not limit yet :) Today I continued to play with some kernel options and somehow reduced boot time to ~9 sec. However, don't know yet how it will impact on battery life - I need to test it. So, more goodies coming soon :)