yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] mars_army:
In theory, wakelock is automatically activated when you select "Enable BLN". Please check it.

1. The application uses other libraries (appcompat:21 for example) that are adapted for 5.0.2. I think that creating a dark theme is possible, but it may be will be made later.

2. Thank you :)

3. Oh, yeah, indeed I should create a new thread. [MENTION=5695278]ChronoMonochrome[/MENTION], приношу свои извинения.

Please refrain from questions about the app in this thread.

Regards.
[Galaxy Ace II Android Development] nikolas1274:
I check it, it doesn't enable it
[Galaxy Ace II Android Development] mars_army:
Yes, you're right, there was a mistake. For now, after rebooting bln wakelock turns on automatically.

Request to all: please, wait for when I create a new thread. This thread is devoted to ChronoKernel, rather than my app (and etc). I hope for your understanding.
[Galaxy Ace II Android Development] ChronoMonochrome:
Не нужно извиняться, все равно вопросы касаются, по-большей части, разработки. Хотя создание нового топика было бы хорошей идеей.

Don't need to apologize, anyway questions are related to the development. Although, creation a new topic would be a good idea.
[Galaxy Ace II Android Development] S.AMU:
Someting went wrong with my phone....

Does anyone know how to repair 00:00:00:00:00 Mac-Adress??

Restoring my nv-backup or reinstallng the ROM did not help.
[Galaxy Ace II Android Development] mars_army:
Try to flash the baseband. If this doesn't help, try to flash to 2.3, then flash 4.1.2.

Had a similar problem on MIUI.

ChronoKernel Settings thread: http://xdaforums.com/galaxy-ace/ace-2-apps/app-chronokernel-settings-v0-9-t3014123
[Galaxy Ace II Android Development] acrocosm:
If this doesn't work or as an alternative flash the official 3-part russian gb rom. This will fix everything. Then upgrade step by step to cm11 or whatever it is that you like
[Galaxy Ace II Android Development] ace2nutzer:
Mac Adresses for Wifi and BT and Serial are Stored in /efs

i don't believe a full 3-parted will help... u just need to edit with the text editor the proper files.. save and reboot.. that's it !

Take a look into /efs/bluetooth/addr.txt and bt_addr

and for wifi:

/efs/wifi/.mac.info ;)
[Galaxy Ace II Android Development] S.AMU:
Thank you.

I took a look into it and the normal mac adress was there... (only wifi was the problem)

But restoring stock rom with pit file helped finally.

I think trying out if the

rm -rf /*

command is working on android wasn't a good idea... :angel:
[Galaxy Ace II Android Development] acrocosm:
3-part ru has saved my ass quite a few times ^_^

--------

Off topic. Do you guys have live streaming issues with this kernel while on dalvik or art?
[Galaxy Ace II Android Development] fluffi444:
Yes - swiss knife for most problems - For thoese who don't have this 3-parted ones:

http://xdaforums.com/showpost.php?p=53921158&postcount=8

sry for off topic :o
[Galaxy Ace II Android Development] shaqman89:
If by live streaming, you mean like youtube, then no, I don't.

It's actually working well with the youtube app.
[Galaxy Ace II Android Development] acrocosm:
Not only youtube, live streaming in general. And not in youtube app but in browsers, non-full screen too.

Like what it used to be with official roms and pre-cm11 custom roms. Anyone still remember what that magic used to be? [MENTION=6107065]wolfensg[/MENTION] reported it working like that using ace2nutzer's last rom and jedi hacker [MENTION=4881398]PolishVodka[/MENTION]'s kernel. But it seems that kernel is only ext4. So I was wandering if chrono got it right?
[Galaxy Ace II Android Development] ishtiaque9:
[MENTION=5695278]ChronoMonochrome[/MENTION]: i'm building cm-12 for my codina and am trying to build it with the Chrono Kernel. but for some reason, my kernel build fails with this error out of nowhere:

Makefile:130: recipe for target 'sub-make' failed

make[1]: *** [sub-make] Error 2

make[1]: Leaving directory '/home/ishtiaque/CM12/kernel/samsung/u8500'

build/core/tasks/kernel.mk:209: recipe for target 'TARGET_KERNEL_BINARIES' failed

make: *** [TARGET_KERNEL_BINARIES] Error 2

any workaround? I'm using the stock toolchain that comes with cyanogenmod...
[Galaxy Ace II Android Development] ChronoMonochrome:
Sorry, don't think I can help, because I never was familiar with ROM building - my laptop is too weak for it. You can build the kernel separately, or just give people a link to the kernel.
[Galaxy Ace II Android Development] ishtiaque9:
okay then would you please tell me which toolchain you used to build your kernel? i'll try doing that. thanks :)
[Galaxy Ace II Android Development] ChronoMonochrome:
I use GCC 4.9.0 from novafusion site.
[Galaxy Ace II Android Development] ishtiaque9:
i tried it... faced this error:

/home/ishtiaque/Documents/Chrono_Kernel-stable/scripts/gen_initramfs_list.sh: Cannot open 'source/usr/u8500_initramfs.list'
/home/ishtiaque/Documents/Chrono_Kernel-stable/usr/Makefile:67: recipe for target 'usr/initramfs_data.cpio' failed
make[1]: *** [usr/initramfs_data.cpio] Error 1
Makefile:948: recipe for target 'usr' failed
make: *** [usr] Error 2

:(
[Galaxy Ace II Android Development] ChronoMonochrome:
Define the target folder in BUILD variable and use

BUILD=/path/to/somewhere/build
make O=$BUILD -j2 codina_defconfig
make O=$BUILD -j2

to build the kernel.
[Galaxy Ace II Android Development] ishtiaque9:
completed building in CM environment. applied some minor changes:

-> replaced the drivers/gpu folder with the one from TeamCanjica's STE Kernel

-> built with GCC-4.8 toolchain

let's hope the new CM-12 works with your kernel :)
[Galaxy Ace II Android Development] ChronoMonochrome:
You shouldn't revert this change https://github.com/ChronoMonochrome/Chrono_Kernel/commit/70463e36e9d9c97609b6075599d94a9ab2f8e382

Otherwise mali boost won't work properly with enabled touchbooster.
[Galaxy Ace II Android Development] ishtiaque9:
added the commit. thanks for the hint! :)

compiled successfully :) :good:

moving on to main build
[Galaxy Ace II Android Development] Bastiary:
Nice, can you share your build if it boots?☺
[Galaxy Ace II Android Development] ishtiaque9:
i plan to do just that :) wish me luck :D
[Galaxy Ace II Android Development] ishtiaque9:
[MENTION=5695278]ChronoMonochrome[/MENTION] one last question: when your kernel is compiled from source, is the cwm/twrp recovery created as a different file which flashes on /dev/block/mmcblk0p17?

if not I think you should try implementing the idea :)
[Galaxy Ace II Android Development] ChronoMonochrome:
Yep, it's already done.
[Galaxy Ace II Android Development] ishtiaque9:
no worries then. let's hope we end up with a bootable and usable zip :)
[Galaxy Ace II Android Development] fluffi444:
Do you mean this (when you say "old zRam script")?

#!/system/bin/sh
set -x

echo $((113 * 1024 * 1024)) > /sys/block/zram0/disksize
mkswap /dev/block/zram0
swapon /dev/block/zram0
[Galaxy Ace II Android Development] ChronoMonochrome:
Yes.
[Galaxy Ace II Android Development] seanmalto:
This is the best kernel(for me) with s6d driver and cm11 rom.

No more black screen that always present when i used standard cm11 kernel or another.

Stable at 1200Mhz cpu freq too, fast, smooth, and maybe perfect(for me) :D

Thanks for your great work sir :D
[Galaxy Ace II Android Development] fluffi444:
[MENTION=5695278]ChronoMonochrome[/MENTION]

mkaluza is talking about optimizing touchboost/APE/mali parameters in this kernel thread:

http://xdaforums.com/galaxy-s-advance/orig-development/kernel-mk-kernel-t2978377

Battery life improvement options

set touchboost delay to a bit more (100-200ms) than mali_utilization_sampling_rate

But i didn't find the option for touchboost delay in your kernel. Do we have this option at all?
[Galaxy Ace II Android Development] ChronoMonochrome:
Ours bt404's touchbooster doesn't have it at all. However I don't think that porting this settings will be very difficult, although I also found that ours toochbooster implementation cause freezes in very rare cases. For now I thinking about moving APE/DDR boost part into cpufreq input boost, which also has delay setting.
[Galaxy Ace II Android Development] invalidpoint:
Yeah , as S6D user i can confirm that blackscreen bug on lockscreen is gone . Good job Chrono :good: , i thought this issue will never be fixed since bgnazor's CM 10 :D
[Galaxy Ace II Android Development] ChronoMonochrome:
@up, did you mean that s6d bug doesn't appears on R2.14.5? Lol, I already did one more fix to s6d in R2.15, so I think it should go away for ever :D

Btw, new build is up :)

R2.15

•	Re-applied NEON optimization, disabled some useless/unused kernel features

•	Added support for some filesystems

•	interface mcde_screenon reimplemented on s6d27a1 display

•	one more attempt to fix black screen bug on s6d

•	APE/DDR boost part moved to governor Dynamic(since I had rare freezes with “standard” touchbooster). There are no functional changes, all interfaces are in /sys/module/cpufreq_dynamic.

UPD.

TWRP has a bug with not mounting /system. Please mount it manually before you install kernel.
[Galaxy Ace II Android Development] manthes:
With 2.15 after every reboot settings change to dynamic 200/800
[Galaxy Ace II Android Development] ChronoMonochrome:
Can't reproduce it. Dynamic 200/800 MHz are defaults, but nothing overrides user settings (except performance profiles, which set governor dynamic).
[Galaxy Ace II Android Development] manthes:
I am using liquid smooth 4.4.4 which doesn't have performance profiles. Probably is a bad combination rom with latest kernel but not a big problem because 2.14.5 is very good
[Galaxy Ace II Android Development] Kiras_PL:
I can't see autoload folder. Should i add it on my own or it will be no more supported ?
[Galaxy Ace II Android Development] shaqman89:
Autoload folder still present for me. And looking from init.d scripts, it seems that it is still supported.

[MENTION=5695278]ChronoMonochrome[/MENTION]

I just wanna say that this build is really good for me. It's even stable on 1245 using dynamic from previously only 1200. I believe I could say for certain that it's stable without reboots since I'm already running it for 2 days now. :D

Great work.
[Galaxy Ace II Android Development] fluffi444:
Same here! First time phone seams to be stable at 1245 Mhz (on Dynamic). Tested a few benchmark runs and daily usage (for now aprox 24 hours). Normally phone can't hande 1245 at all and reboots after few minutes - even without higher usage.

But now... Looks this build does something magic :D

But even without this plus of OC the phone runs really great. Good work (as usual), [MENTION=5695278]ChronoMonochrome[/MENTION] :good:

Found nothing to complain :o
[Galaxy Ace II Android Development] zizoumadrid:
what version of cm11 you use i'm with ace2nutzer 20141118 and my phone drain battery as hell

and when i'm traying 2.15 i get bootloop in samsung logo but with 2.14.5 work fine

pls can you share with me your battery use and how long time you get on screen on thanks a lot :)
[Galaxy Ace II Android Development] ChronoMonochrome:
Glad to hear that even 1245 MHz works stable, but I think that here are nothing magical. Usually the governor dynamic tries to reduce use of high freqs. Here are two params, which controls use of overclocked freqs - max_non_oc_freq and oc_freq_boost_ms.

For more, read the wiki https://github.com/mkaluza/project-zen/wiki/Dynamic-governor

Which recovery have you used to install the kernel?If you use ext4, on twrp you need to mount /system before you install kernel. It's my bad, I too long time have used f2fs to notice that normally installation works only with /system formatted to f2fs. I still thinking how to fix it and for now only solution(for ext4) is don't use TWRP (or manually mount system, before install anything).
[Galaxy Ace II Android Development] fluffi444:
Got an reboot with 1245... reducing to 1230 :)... So nothing magic (as Chrono said already) . What a pity :D

EDIT

Back to 1200 - For me it was only placebo effect - got again an reboot with 1230 - hopefully it was because of 1230/1245 :)
[Galaxy Ace II Android Development] matthias1976:
Reboots gone

Reboots completly gone in 2.15. Stable at 1200mhz !!

Freezers and hangers gone too.

Good performance and good battery life.

Battery eqal to 10.1 without oc.

But much less than stock 4.1.2, but much better performance in cm11.

Thx chrono for such good work.
[Galaxy Ace II Android Development] shaqman89:
Guess I am luckier *grin*

Still haven't got a reboot yet so far.
[Galaxy Ace II Android Development] seanmalto:
Hey, how you get 15% only at screen usage precentage?

i always get 60%-100% :(

i'm using cm11 + r.2.15, any suggestion for setting? GPU maybe?

thanks.
[Galaxy Ace II Android Development] matthias1976:
cause im no heavy user.

only 2 h 8 min screen on time the whole battery load.

and screen brightness control with llama.

when im at home or at work, screen brightness set automatic only 20%, all other aerias 80% brightness.

screen cost most battery, good to reduce brightness !!
[Galaxy Ace II Android Development] Ave_Hornet:
Hi, [MENTION=5695278]ChronoMonochrome[/MENTION] any changelog for r2.15.1?
[Galaxy Ace II Android Development] ChronoMonochrome:
There's actually only fix for bad ping when using 3G.
[Galaxy Ace II Android Development] fluffi444:
Sound like we are the point that only minor things are still to optimize - R2.15 (2.15.1) ist really very good as it is! :good:

Or do you have still extraordinary ideas? ;)
[Galaxy Ace II Android Development] ChronoMonochrome:
The big problem is half-working DDR OC, I tried to do something with it, but it still randomly reboots. I actually trying to rebase samsung changes into some newest kernel version - we actually have working LK3.1, compiled from android sources, but unfortunately it has some major issues.
[Galaxy Ace II Android Development] mkaluza:
Yo!

I'm more less done with my tablet for now so I'm back to STE - thanks for all the work you did with LK3.1 - I'll try to build it for janice and see if I can fix some things.
[Galaxy Ace II Android Development] ChronoMonochrome:
I also created wiki - hope this can also help https://github.com/ChronoMonochrome/kernel_common/wiki

As it turned out, the bootloop fix "transforms" into already known commits - https://github.com/ChronoMonochrome...62...13760e7dbc7fbae31969c3342981aa1fe5d34203

so, mostly missing commit "ARM: 7325/1: fix v7 boot with lockdep enabled " was a reason for bootloop.

We also have commits, which introduces same changes like diff from android's 3_0_31 and XXLQL - not XXLQL, but root-commit of TC's kernel.

(yes, I think it's good to have known changes instead of patches found by diff):

https://github.com/ChronoMonochrome/kernel_common/wiki/Splitted-arch-arm-*-patches

For now only changes in arch/arm/*, though the list above isn't full - some changes in arch/arm/mm and arch/arm/vfp are probably missed (and of course list doesn't include samsung changes, since they are can't be found anywhere).
[Galaxy Ace II Android Development] avithohol:
Hi Chrono,

Thank you for the great work you have done for this device :good: ,

last build is really impressive f2fs + ram overclock are giving another push to this device performance figures,

Keep up with the good work, have you thought of updating the mali driver to the latest available binary blobs, i have read mostly possitive comments from devs and users using them on different SoCs ?

Bench results :
[Galaxy Ace II Android Development] ChronoMonochrome:
I've tried to update mali sources to r3p2 two months ago, but unfortunately, this also requires to replace user-space libraries. Libs taken from official r3p2 mali package didn't worked. Although I haven't tried yet to use libs from Dorimanx's kernel which uses r3p2. I think that this is possible to update mali sources, only problem for now is lack of knowledge...
[Galaxy Ace II Android Development] bebolint98:
Hello everybody!I want to flash this universal kernel.I read the install method but I don't understand very well.So with this process is good?:

1.flash make-ramdisk.zip

2.flash codina_cwm_6.0.5.0_ext4.zip

after

3.flash codina_bootscript_4.4.x_ext4.zip

4.finally flash r2.15.1 kernel.

Thanks!
[Galaxy Ace II Android Development] ChronoMonochrome:
Don't use this outdated method. You can install latest build by simple flashing kernel.
[Galaxy Ace II Android Development] bebolint98:
Thanks!I flashed simple and working.

---------- Post added at 05:12 PM ---------- Previous post was at 04:30 PM ----------

I have get last question.To change the GPU frequency I need to change in 01optimization file?
[Galaxy Ace II Android Development] ChronoMonochrome:
Where did you found it? I think you're talking about file from ace2nutzer's CM11 biuld. You can adjust GPU and all the rest settings via ChronoKernel settings app.
[Galaxy Ace II Android Development] bebolint98:
I found it in system/etc/init.d,and my whole phone is laggy.
[Galaxy Ace II Android Development] ChronoMonochrome:
Well, this is not kernel problem, since on my system it's running smooth even on GPU 256/400 MHz settings. Try to use dynamic governor, because APE/DDR boost part moved to this governor (coz I had some problems with original touchbooster), and I didn't implement this part to other governors.
[Galaxy Ace II Android Development] bebolint98:
I try to do a clean install wipe data factory reset wipe system and install ace2nutzer cm11 after flash this kernel and now I stuck on samsung logo and I can't go to recovery and odin not recognise my phone .What can I do?:(
[Galaxy Ace II Android Development] ChronoMonochrome:
This is strange, since I recently did same procedure and now I use same ROM. Check whether /ramdisk/boot.cpio exists(you can do it via adb or use aroma file manager for CWM, or just use TWRP which has file manager), and also send me last_kmsg:

cat /proc/last_kmsg > /sdcard/last_kmsg
[Galaxy Ace II Android Development] bebolint98:
I cant use aroma file manager or twrp because I cant go to recoverz so now I need to set up the adb because I cant do this before
[Galaxy Ace II Android Development] ChronoMonochrome:
sorry, didn't read this carefully. Flash kernel for odin from google drive (you can find it in OP).
[Galaxy Ace II Android Development] bebolint98:
But the odin not recognise my phone.
[Galaxy Ace II Android Development] ChronoMonochrome:
Do you have at least installed drivers for samsung phones?
[Galaxy Ace II Android Development] bebolint98:
Yes!
[Galaxy Ace II Android Development] ChronoMonochrome:
I don't think I can help, coz I never had problems with odin or kernel booting - even more, this is a first report about bootloop, so I think that you did something wrong. Try to ask in troubleshooting thread or google.
[Galaxy Ace II Android Development] bebolint98:
I think the U8500 rom driver which i need to install I can download it somewhere?
[Galaxy Ace II Android Development] avithohol:
Hello,

After 3 days of extensive testing i can confirm that 1190 mhz on ddr ram is completely stable on my device, i have tested with antutu and epic citadel for several hours and there were no crashes or reboots. The max stable cpu clock is still 1200 mhz, anything higher leads to reboots after some time. Maybe we can test with 1300 mhz for ddr just for the fun.

DDR overclock isn't working well with Dynamic governor, the bench scores are awlays lower becouse of ddr scaling with cpu and hence rendering it useless somewhat, dinamic scaling of ddr is not very helpfull with screen on but a good power saving feature with screen of or when device is used for reading and cpu is set to lowest frq.

Regards :good: .
[Galaxy Ace II Android Development] bebolint98:
Hello!The odin recognise my phone so I flashed the odin kernel and my phone is working.Now I want to flash CWM recovery,where I found? and what I need to wipe or format before install recovery?After I want to flash another kernel because with this odin kernel the WI-FI not working and what I need to wipe or format before I install kernel?
[Galaxy Ace II Android Development] ChronoMonochrome:
R2.16

New build is up!

Changelog:

completely rewritten PLLDDR OC module, unfortunately overclock over 975 MHz still causes reboot sometimes

added interface pllddr_oc_on_suspend - usage is same as with pllddr interface, difference is only that PLLDDR will be changed on suspend. PLLDDR will be changed only with CPU workload(workload = frequency * load) <= 20000 kHz, adjustable via /sys/module/db8500_prcmu/idle_cpu_workload; and only when MCDECLK and SDMMCCLK are disabled(first disables on suspend, second - when the phone doesn't reads/writes on MMC). Changes above is for safety. That it works only with Dynamic, because I don't know how to get workload not via governor, will fix this in next build.

LiveOPP improvements [cocafe]

adjusted extra min free [cocafe]

adjusted sched mc/smt power saving settings [ace2nutzer]

small config optimizations

LiveOPP, mali: added functional of commands like

echo varm-=5 > /sys/kernel/liveopp/arm_step00

or

echo 0 vape-=5 > /sys/kernel/mali/mali_dvfs_config

Warning! Don't run scripts like above few times, otherwise UV/OV will be cumulate!

Simplest method of blocking multiple running is below(voltages below might work unstable on your phone. test it by yourself, but don't change few values at the same time, otherwise you won't know, which frequency is causing reboots)

if [[ -f /tmp/uv ]] ; then
echo "this script have already running"
exit
fi

echo varm-=21 > /sys/kernel/liveopp/arm_step00
echo varm-=11 > /sys/kernel/liveopp/arm_step01
echo varm-=8 > /sys/kernel/liveopp/arm_step02
echo varm-=8 > /sys/kernel/liveopp/arm_step03
echo varm-=4 > /sys/kernel/liveopp/arm_step04
echo varm-=4 > /sys/kernel/liveopp/arm_step05
echo varm-=4 > /sys/kernel/liveopp/arm_step06

touch /tmp/uv

Of course, you can use usual "echo varm=?? > /sys/kernel/liveopp/arm_stepXX", as always.

added support for gzipped ramdisk (put recovery.cpio.gz / boot.cpio.gz instead of recovery.cpio / boot.cpio, respectevely, to save some space on ./ramdisk)

http://xda.mister-free…hrono_kernel_r2.16.zip
[Galaxy Ace II Android Development] ChronoMonochrome:
Hi!

CWM you can find here http://xda.mister-freeze.eu/XDA-fil...ery/cwm_6.0.4.9_f2fs_codina_for_R2.7.cpio.zip

This archive is not flashable, so anually extract it to /ramdisk (at first you need to install latest kernel). You need to wipe/format anything after each installation.

Thanks for testing!

I don't see any problems with Dynamic. Just enable CM11's performance profiles and use high-performance profile, this will disable soft and hardlimits used by Dynamic.

Hm, you are right. Will look what I can do to with this.

ATM I don't believe that phones can handle it :) but you can try to reduce DMACLK/ACLK, at first overclock DDR to 1190 MHz, then underclock DMACLK/ACLK:

echo dmaclk=0x18[b]5[/b] > /sys/kernel/liveopp/pllddr_cross_clocks
echo aclk=0x18[b]5[/b] > /sys/kernel/liveopp/pllddr_cross_clocks
echo on > /sys/kernel/liveopp/pllddr_cross_clocks

p.s. only latest number does matter, this is divisor of PLLDDR frequency.

UPD. Uploaded R2.16.1 with removed CPU workload workaround - anyway it doesn't make much sense...
[Galaxy Ace II Android Development] Ave_Hornet:
Thanks [MENTION=5695278]ChronoMonochrome[/MENTION] i'll test it :D

ps. for me PLLDDR 975 MHz Stable but drain battery as hell :D
[Galaxy Ace II Android Development] ace2nutzer:
:D

This is because PLLDDR oc many other freqs (the half phone) instead only DDR Freq (RAM) or i'm wrong @ ChronoMonoChrome ?

That's why i still don't have implement it in my Kernel ... :)
[Galaxy Ace II Android Development] ChronoMonochrome:
In the last implementation it touches not so many things. Actually it overclocks only DMACLK and ACLK - since UI performance also depends on them. All the rest regulators are recalebrates to default (or less ) frequencies.