yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] ChronoMonochrome:
New build R3.12 is UP!

Changelog:

added cm-13.0 support (thanks to SergeyL for ramdisk)

fixes and improvements from common marshmallow kernel

re-applied binder driver update, should work fine now

make governor Dynamic aware about GPU usage (improved gaming performance). Thanks to [MENTION=5840412]ace2nutzer[/MENTION] for governor parameters tuning!

If someone wants to play with a new Dynamic parameters, these are available in /sys/module/cpufreq_dynamic/parameters . Parameter mali_high_utilization_threshold stands for GPU usage limit when which is reached, Dynamic will perform CPU scaling more aggressively(the same will happen if mali is boosted, regardless of GPU usage). By default this value is set to 192.

Enjoy this build!
[Galaxy Ace II Android Development] ChronoMonochrome:
No, it's not related to the binder update. It should have probably come from disabled SELinux, since it's spamming logcat with security errors. As for a binder update itself, I don't know, how it behaves on 4.4.4. On 5.1.1, there are no problems with increased battery drain, but on an older android version it might work unexpectedly.
[Galaxy Ace II Android Development] ChronoMonochrome:
New build R4.0 is UP!

It probably has been a while since a real development here :) Be prepared before seeing the biggest backport/update you've ever seen before, :laugh:

Changelog:

Updates:

Memory Management(SLUB, compaction, vmscan, vmalloc, ashmem, swap, writeback etc): synced with android-3.4 branch (thanks to [MENTION=3332811]faux123[/MENTION] for update to LK3.3-rc3)

Improvements/fixes to memory management by Code Aurora Forum from https://github.com/CyanogenMod/android_kernel_oneplus_msm8974

Power Management, QOS, freezer: updated to android-3.4

Completely Fair Scheduler(CFS), RCU etc: fully updated to android-3.4

Cpufreq: update to android-3.4 (and dropped some governors)

File systems: update to LK3.3-rc3 (thanks to faux123), dropped support for nilfs, cifs, nfs, udf and probably some more

Time Keeping: synced(mostly) with android-3.4

Security: small updates from android-3.4

Low Memory Killer: fixes by CyanogenMod from oneplus kernel (thanks to SergeyL for bringing the patches to my attention)

Misc changes

reduced amount of modules

block-based 7z compression of ramdisks/recovery inside the kernel package (to reduce package size)

Some of changes might be not listed here :)

Because now it's more LK3.4-based kernel than LK3.0, maybe later I even will consider changing this number in kernel version line, lol :p

Full changelog

r3.12...r4.0

A few small notes at last: if you are intending to use this build on ROMs that is not supported by kernel(refer to OP), note that bootscripts are moved(compressed) to archive "ramdisk.7z" inside a package.

And second, if you are downgrading from this version to any other, please wipe /ramdisk partition (use TWRP for that) or manually remove the file /ramdisk/boot.cpio, which will left from this build. In case of any problems with installation/booting, please attach file /ramdisk/last_kernel_install.txt. And last, but not least, enjoy this build! :good:
[Galaxy Ace II Android Development] DetroX:
We can hope for nodebug version of 4.0?
[Galaxy Ace II Android Development] Ave_Hornet:
[MENTION=5695278]ChronoMonochrome[/MENTION]

Just Insane Changelog !!
[Galaxy Ace II Android Development] dixee:
nice update chrono.

just installed r4.0 but displayed version still 3.12
[Galaxy Ace II Android Development] ChronoMonochrome:
I had booting issues on nodebug version on CM-13.0. I will upload this version, when I find a root cause of this.

Yea, it's a bug of an implemented versioning system. When changing a major version number, it still display lower version.
[Galaxy Ace II Android Development] xkvegans:
would this kernel compatible with [TeamCanjica] Ace2Nutzer CM11 150714
[Galaxy Ace II Android Development] ChronoMonochrome:
Why shouldn't it be? As long as it's kitkat-compatible kernel, yes.
[Galaxy Ace II Android Development] shaqman89:
[MENTION=5695278]ChronoMonochrome[/MENTION]

I got one reboot two hours back then. Too bad I can't provide logs since I only just realized it now.

Anyway the reboot seems to cause some apps lose its configuration (noticed whatsapp and SwiftKey shows initial setup screen again).

Speaking of which, I think CK app sometimes loses cpu configuration. I noticed that the frequency are now always reset to 800 after a reboot even though I set it to 1150.
[Galaxy Ace II Android Development] ChronoMonochrome:
Hmm, it's likely due the lack of the incremental patches applied to VFS (3.4.x), so the first of all I'll focus on upgrading VFS layer upto android-3.4. I was afraid, it wasn't a good idea just to left the current state of VFS layer as of LK3.3-rc3. I noticed too a few warnings about orphaned ext4 inodes in logs, after doing some experiments which were causing crashes, though so far I didn't have problems with apps.
[Galaxy Ace II Android Development] littledude072:
id like to report a bluetooth share bug on 4.0. it constantly keeps crashing so i had to freeze it with SD maid

i was using sergeyls CM12.1 01/03 build, then reflashed with 01/13
[Galaxy Ace II Android Development] [-GuTi-]:
delete godmode script in system/etc/init.d/ and reboot, new kernel is not fully compatible with it
[Galaxy Ace II Android Development] Noxialis:
What does "God mode" do exactly?
[Galaxy Ace II Android Development] shaqman89:
Something like su but without any confirmation.

Afaik, ChronoMonochrome created it as a su alternative since some su operation is a bit slow. I haven't used it much yet though.
[Galaxy Ace II Android Development] ace2nutzer:
root access without asking for permission. (i think so)
[Galaxy Ace II Android Development] shaqman89:
Where did this script come from?

I didn't find any godmode script both in vanir and cm13 using latest ck.
[Galaxy Ace II Android Development] [-GuTi-]:
It come from CM12.1 by SergeyL, quetion was about it

It is not created by Chrono
[Galaxy Ace II Android Development] ChronoMonochrome:
New build R4.1 is UP!

Changelog:

Fixes:

fixed bluetooth issue with enabled God Mode

fixed ext4 instability issue

Updates:

Added KEXEC hardboot support from Xperia u8500 phones (FULL credit goes to munjeni)

VFS(and most of the supported file systems) is updated to android-3.4

Implemented Asynchronous Fsync from HTC phones by faux123

Asynchronous I/O improvements by faux123 (backport from Linux Kernel 3.6)

F2FS is fully updated to Linux Kernel 4.4 (full credit goes to arter97)

FUSE is replaced by Sdcard FS (from samsung phones) for better battery life and performance

ZRAM is replaced by VNSWAP from samsung phones (backport by faux123)

ZSWAP backport from Android-3.18 by me

Enabled SCHED_AUTOGROUP for better multitasking

Low Memory Killer: enabled adaptive LMK

Interrupt handling: improvements from android-3.4

/* Kexec hardboot */

Kexec is a linux kernel feature which allows to boot from another kernel without need to flash anything.

Some uses of this:

MultiROM. I'm not planning implementing Tassadar's MultiROM right now, but it should be at least possible now, since the lack of kexec support was a pitfall until now.

Overriding a default kernel command line. I'll just show some examples I was using recently(you'll need to download kexec-tools from the link below and install kexec binary to /system/bin ):

On debug kernel version, to increase available RAM(like on non-debug one):

Be sure to reboot into the same kernel version (as none of previous supports kexec), and pass the correct parameter lcdtype (you can determine it by using cat /proc/cmdline )!

Analogically, running from non-debug kernel, you might want to restore original size of HWMEM:

Theoretically possible independence on the internal sdcard. Let's imagine you've a dead internal flash memory, which is performing read only. Before it'll die, you can set up a default kernel, so that it boots from another kernel in an external sdcard and loads ROM from there. I'm saying "theoretically", because some work would be needed to implement something like that, and as of now it is just some random thoughts about possible kexec use.

Another thing that should be considered is that, you can't predict when SD card will die, unlike HDD it doesn't have S.M.A.R.T. capability to track its health status. "The problem is not that it is mortal, the problem is that it's suddenly mortal" (c) . You would have to use external memory constantly, without knowing about how long can perform an internal one.

For more details, see http://xdaforums.com/showthread.php?t=2104706 .

Some changes might be not listed here.

Full changelog

r4.0...r4.1

Enjoy this build! :good:
[Galaxy Ace II Android Development] bebolint98:
[MENTION=5695278]ChronoMonochrome[/MENTION] Thanks for this update! It's recommend to enable the KSM in cm11 which is in settings/performance/memory managament or I can disable it?
[Galaxy Ace II Android Development] ChronoMonochrome:
Lol, it should not be even showing in the settings because of a recent removal of this. Personally I wouldn't suggest using KSM on android phones due its inefficiency.
[Galaxy Ace II Android Development] bebolint98:
I'm using ace2nutzer cm11 0714 and It's still have this option.So I disable it.Thanks!

---------- Post added at 01:14 PM ---------- Previous post was at 12:54 PM ----------

I try to install the R4.1-nodebug but it's stuck at samsung galaxy ace 2 show some second and the phone reboot and still show this.I come from r3.12 nodebug.What is the problem?I reinstall the r3.12 nodebug and the phone boot up.
[Galaxy Ace II Android Development] ace2nutzer:
lol ... actually KSM is disabled on both kernels since at least one year ... so something is very wrong with your ROM or kernel.

u shouldn't see that menu option at all ... :highfive:
[Galaxy Ace II Android Development] bebolint98:
I don't know why but I see:
[Galaxy Ace II Android Development] ace2nutzer:
really strange ... check installed kernel version ... not that it's using outdated kernel from the rom itself lol

if ok, u should wipe data .....
[Galaxy Ace II Android Development] bebolint98:
I didn't use outdated kernel.I use r3.12 nodebug.But as I write I try to install r4.1 nodebug but the phone didn't booted up.Maybe [MENTION=5695278]ChronoMonochrome[/MENTION] know what is the problem?
[Galaxy Ace II Android Development] shaqman89:
[MENTION=5695278]ChronoMonochrome[/MENTION]

4.1 wont boot for me. Here are the logs from last_boot. I tried it with both 4.1 and 4.1 no debug version.

Also last_kernel_install.txt
[Galaxy Ace II Android Development] fluffi444:
So you made the same experience? That phone did not go to deep sleep after full charge?
[Galaxy Ace II Android Development] ChronoMonochrome:
It's not only my work... :) I think you should thank TeamCanjica, who made it happen :)
[Galaxy Ace II Android Development] muxa1980:
Which version is the best for stock rom?
[Galaxy Ace II Android Development] monstro78:
Yes. Happen to me 2 times. I had to reboot to have deep sleep.
[Galaxy Ace II Android Development] fluffi444:
No deep sleep happens again seconds ago... Without full charging... Still dont know what causes this...
[Galaxy Ace II Android Development] miryn:
[MENTION=5695278]ChronoMonochrome[/MENTION]

Something is wrong with latest kernel (sources, more specifically..); after few hours in deepsleep, tearing starts to show and it's really bad (I have animation turned off). After reboot everything backs to normal, again just for few hours..
[Galaxy Ace II Android Development] manthes:
After installing latest build of the rom i use i lost deep sleep so i believe that it is not kernels problem.

Edit...

It still loosing deep sleep so unfortunately it's kernels fault and i am using the first kernel with twrp
[Galaxy Ace II Android Development] danny19901:
OK I installed latest EXT4 kernel on latest Liquid smooth but oddly I kept getting cannot move app error when try to move apps to SD so I full wiped and reinstalled without kernel and move to SD works fine
[Galaxy Ace II Android Development] Alwer:
On last kernel f2fs with CM 11 deep sleep work prefect
[Galaxy Ace II Android Development] pijen:
is there any noticeable performance when using F2FS on our ace2?
[Galaxy Ace II Android Development] ChronoMonochrome:
New build is UP!
[Galaxy Ace II Android Development] pedroleon99:
Why you switched back to CWM? [emoji24]

I loved so much TWRP :(
[Galaxy Ace II Android Development] ChronoMonochrome:
Because not everyone likes this. I decided to make sometimes builds with CWM.

Edit. I uploaded 4.1.2 build with TWRP.
[Galaxy Ace II Android Development] manthes:
i tried first the build with cwm to see if the problem with black screen in recovery have been solved with undervolting but no luck. Also i had bootloop with cwm build. With twrp it boot normaly.

p.s. it still lost deep sleep after reboot. i don't know if it happens only on specific governors. For sure it happens with pegasusqplus and lionheart
[Galaxy Ace II Android Development] gogoo88:
I had bootloop with cwm build too:(
[Galaxy Ace II Android Development] xo.en:
4.3.x, liquid, as usual - no cpu2 control in perfctrl, still - tearing in 2d.
[Galaxy Ace II Android Development] pedroleon99:
Ok I understand thank you very much :)
[Galaxy Ace II Android Development] Hummer951:
+1 bootloop with CWM build
[Galaxy Ace II Android Development] str3tch72:
Anyone tried latest version on AOSP?
[Galaxy Ace II Android Development] ChronoMonochrome:
Can you share your EGL libs ? Maybe problem in this combination(i.e. not original EGL libs + my kernel).
[Galaxy Ace II Android Development] bebolint98:
Same here!
[Galaxy Ace II Android Development] garak elim:
The same here too. I upgraded 4.0 kernel. After updating to 4.1 I dont see external SD card in TWRP too.
[Galaxy Ace II Android Development] ChronoMonochrome:
Sorry guys, a wrong 7z binary was included in the uploaded build causing errors during installation. Both kernel version were re-uploaded.
[Galaxy Ace II Android Development] littledude072:
thanks. it did seem a bit buggy since android system still used the usual 'grant root access' screen

will wait a bit longer
[Galaxy Ace II Android Development] shaqman89:
Could confirm that installation is working, for no debug version. Thanks [MENTION=5695278]ChronoMonochrome[/MENTION].

Chrono, related to change from fuse to samsungfs, does it means that we need to format the sd card? Or am i missing somerhing.

Currently internal memory (which is swapped) is mounted but shows no storage.

Thanks.
[Galaxy Ace II Android Development] ChronoMonochrome:
No, there's no need to format sdcard. Both FUSE(and Sdcardfs), in a simple terms, is a kind of a layer between the real file system(e.g., fat32) and android.

Does it mean that applications doesn't work properly because of not recognizing a storage? I don't know, maybe it's something specific to KitKat, because on Lollipop I haven't seen any side effects related to this.

P.s. change to sdcardfs only required some changes in the ramdisk. Now it's done dynamically (ramdisk is being "patched" at boot). If someone wants to switch back to a FUSE fs, remove in the file /ramdisk/10monkey_patch everything below line:

busybox cat /stage1/init.rc >> /init.rc

Be sure to not remove anything else.

The resulting file should look so:

busybox cp /init.rc /stage1/

busybox echo "import /init.kernel.rc" > /init.rc
busybox echo "" >> /init.rc

busybox cat /stage1/init.rc >> /init.rc
[Galaxy Ace II Android Development] borkins:
I have some problems with CK r4.1- no debug (CM 11 - KK 4.4.4):

1. '/storage/sdcard0' is empty ( 0.00/0.00 B ). But '/mnt/media_rw/sdcard0' is OK.

2. Wi-Fi not work.

Tried reboot, but it's the same. :/
[Galaxy Ace II Android Development] shaqman89:
Actually it seems that the whole OS doesn't recognize storage.

Seeing in settings storage, internal storage (/storage/sdcard0) shows only 0byte.

Opening it from link2sd, it says that it is mounted but with 0 byte storage. Also it gave me a warning about linking to a non fuse storage type.

In effect, yes all application doesn't work properly if it has something to do with sdcard0 (eg: screenshot).

Should I include a log, [MENTION=5695278]ChronoMonochrome[/MENTION]?

---------- Post added at 11:09 AM ---------- Previous post was at 11:04 AM ----------

Yeah, I could confirm both.

So could it be a mounting issue? Have you tried doing a remount?
[Galaxy Ace II Android Development] ChronoMonochrome:
No, there's no need in logs. It seems that kitkat has a poor support for sdcardfs. See the edited post to switch back to fuse fs.

As for not working wifi, I can confirm that this is not working on non-debug version, but on debug one it's working. I'll compare configs of these releases to investigate this.
[Galaxy Ace II Android Development] shaqman89:
[MENTION=5695278]ChronoMonochrome[/MENTION]

Just out of curiosity:

Does the order of that matters?

I mean, in the case of sdcard1 with sdcardfs, it works since it's executed after the vold device. But in the case of sdcard0, the vold device comes after sdcard0 with sdcardfs.

Just curious about it a bit.
[Galaxy Ace II Android Development] ChronoMonochrome:
Yes, it might be a culprit, but anyway I'm not sure about a root cause of this.
[Galaxy Ace II Android Development] shaqman89:
Well, I thought it might be because of loading time. Just a wild guess which I couldn't prove.

But anyway, the last version really gives a visible performance increase. Both loading app time and multi tasking feels much better now. :good::good::good:
[Galaxy Ace II Android Development] DetroX:
TWRP cant mount f2fs partitions. On ext4 everything works fine.
[Galaxy Ace II Android Development] ChronoMonochrome:
Strange, it worked fine for me. Are you using 2.8.6.0?
[Galaxy Ace II Android Development] DetroX:
Yup. I found temporary solution. On 4.0 everything works fine. After restore system,cahce,data + instal 4.1 again. System start up fine but twrp still say "can't mount" for system,cache,data (f2fs).
[Galaxy Ace II Android Development] ChronoMonochrome:
There's probably some mess with modules on nodebug version. For some reason some of them just can't be load by kernel. I would suggest install a debug one until I fix it.
[Galaxy Ace II Android Development] nikolas1274:
With that trick, it works for me

Στάλθηκε από το GT-I8160 μου χρησιμοποιώντας Tapatalk
[Galaxy Ace II Android Development] shaqman89:
Just wanna say, that this last built is really promising, [MENTION=5695278]ChronoMonochrome[/MENTION]. I have said that performance and multitasking is visibly better. And since I've been using it for almosf a day, I could say that battery drain is much better now. Great job [MENTION=5695278]ChronoMonochrome[/MENTION]
[Galaxy Ace II Android Development] shaqman89:
[MENTION=5695278]ChronoMonochrome[/MENTION]

I got one reboot just now. It turns out that I /proc/last_kmsg doesn't exist. Was it disabled somehow?

Anyway, are there any other logs I could check?

I am using CK 4.1 (not the non-debug version) on VanirKK.
[Galaxy Ace II Android Development] Noxialis:
For some odd reason, Wi-Fi isn't working after I flashed the nodebug version of 4.1

Will try the other version.
[Galaxy Ace II Android Development] borkins:
Yeah, no last_kmsg, i got reboot too.
[Galaxy Ace II Android Development] ace2nutzer:
flash normal vesion and wait for reboot .. after that catch last_kmsg, then u can flash no-debug version again.
[Galaxy Ace II Android Development] borkins:
I flashed the normal version yesterday, because on nodebug - no Wi-Fi.
[Galaxy Ace II Android Development] shaqman89:
@up

Yeah,that was the normal version.
[Galaxy Ace II Android Development] ChronoMonochrome:
It was disabled accidentally. I've got recently some reboots too, but too bad I can't fix it now, cause my laptop is broken. Trying to compile it from of the ssh servers, provided for free, but it's anyway going to be a challenge to make any significant changes from there due to an obvious incovencies using ssh from mobile.
[Galaxy Ace II Android Development] shaqman89:
Ouch. Sorry to hear that.

I hope you could have your laptop back soon.
[Galaxy Ace II Android Development] ChronoMonochrome:
New build R4.1.1 is UP!

A small bugfix update after the recent changes.

Changelog:

fixed a wrong modules being used on nodebug build(fixes wifi)

fixed hrtimer insconsistent with the upstream state (I believe, was a reason for some of the reboots)

reverted to zram from vnswap, due to the slowness of the latter

reverted to FUSE from Sdcard fs for now (eventually will re-enable it for LP ROMs)

increased minfree a bit

re-enabled RAM console with the autocorrection setting on debug build

re-enabled ABB fake DMFS devices (fixes an incorrect battery percentage showed in recovery)
[Galaxy Ace II Android Development] bebolint98:
With this version sometimes some lines appear in the bottom of the screen when I unlock the screen.
[Galaxy Ace II Android Development] TheLiquidGuy:
My phone stuck on Ace 2 sign on CM13 by sergeyL
[Galaxy Ace II Android Development] ChronoMonochrome:
Which ROM you're using and what display type (ws2401, s6d27a1) do you have?

Can anyone confirm? Unfortunately, I just have removed CM13 and installed Vanir, because I need PPPoE to work.
[Galaxy Ace II Android Development] bebolint98:
My display tipe is ws2401 and I use ace2nutzer latest 0714 cm11 ROM. With r3.12-nodebug this problem not appear.
[Galaxy Ace II Android Development] Noxialis:
How to determine display type?

Because that thing happens to me, and more (takes multiple tries just to get the screen to display things, half of the time, it lights up but it's just all black) (random appearance of misplaced bar at the bottom of the screen, like it displays things but that particular bar is out of place, will SC when it happens again).

I take it it's because the phone has suffered some drops but, could it be possible that it's just a kernel issue?
[Galaxy Ace II Android Development] shaqman89:
Check in /sys/devices/pri_lcd_xxxx

The xxx should tell you what your LCD type is.

What ROM are you using? With vanir I have no issues like so with the exception of extremely slow loading when downloading apps from play store.
[Galaxy Ace II Android Development] ChronoMonochrome:
I doubt it's kernel bug. As you know, since R3.12 I was only working on bringing up various updates from android-3.4. So, if you're fine with R3.12 you should be so with R4.1.1 too, since from that release MCDE and display related stuff remained untouched. Nevertheless, I'll reset display delays to theirs stock defaults in the next release just in case.
[Galaxy Ace II Android Development] ace2nutzer:
Maybe too high LCD Freq is set in CK APP
[Galaxy Ace II Android Development] Noxialis:
LCD type is ws2401.

Rom: CM12.1 (Sergeyl)

All CK display settings are on default.

Yeah it may be hardware issue, thanks for hearing me out though. No need to change anything display related (come to think of it, display settings on default doesn't trigger that odd bar I mentioned, well, so far that is).

Though I just might take this to a service centre and have the board fixed xD 2 nasty drops that I remember, something must've taken quite a hit internally.
[Galaxy Ace II Android Development] ace2nutzer:
i would anyway check the actually LCD Freq under /sys/kernel/mcde/lcd_clk (or similar ..)
[Galaxy Ace II Android Development] bebolint98:
For me it write: 49920000

And I have this line sometimes.
[Galaxy Ace II Android Development] TheLiquidGuy:
With SergeyL's CM 12.1 I had this line on the bottom of the screen appearing and disappering whenever it wants. I thin I was with R3.12 but I don't remember. I think that even in KK I had it with chronokernel. I don't know if its kerner or hardware issue, but the phone is old so...
[Galaxy Ace II Android Development] ace2nutzer:
yep 499.... is original freq. for ws2401

then check video.modes Values .... it's known that some sort of combinations can cause for some LCD's such lines ... or blinking...

Check Values and post here.
[Galaxy Ace II Android Development] bebolint98:
Where I can check the video.mode values?
[Galaxy Ace II Android Development] ace2nutzer:
Check /sys/devices/pri_lcd_ws2401/mcde_chnl