yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] ChronoMonochrome:
This is a normal behaviour since r4.5. Disabling internal storage mount point saves a bit of boot time, for those who really needs this sdcard to be mounted, can disable storage swap in /ramdisk/fstab_specs.txt, reflash kernel and swap storages via CK app.

Seems that vmalloc size set in the latest kernel is too small for modules. Can you try kernel linked below with vmalloc=168M: https://depositfiles.com/files/63tvdg61q ?

Thanks.
[Galaxy Ace II Android Development] shaqman89:
I tried enabling internal storage, and internal and external storage was mounted as normal. When I swapped via ck app, both were mounted and swapped but external shows 0b.

Also, I tried rebooting a few times, from around 5 reboots, once didn't load the wifi module. I could say that it's better than before, but it still occur sometimes.

Unfortunately, no logs were available. Somehow last_kmsg wasn't created, and kmsg seems to work only for events recorded when we start to read it. This is different from the usual way that kmsg shows a lot of message (all the way to the beginning of starting up the device on relative short usage). Could it be related to some buffer size being too small?

Anyway, I like the implementation of latest lmk better. Makes multitasking better and it seems to utilize ram more effective (using with zram of 450 right now)
[Galaxy Ace II Android Development] ChronoMonochrome:
Hmm, that's weird. I have to admit that I haven't used this method of memory swap since a long time, though. Maybe, in further releases I'll have to leave an internal sdcard disabling opt-in (without having to sacrifice storages swap).

Seems that vmalloc size is still too small, probably will have to revert its size to the smaller tested (and working) so far - 192Mb.

Usually reading kmsg results that the further attempts will show not the full kmsg log, but only messages printed since the latter log reading. Unlike this, dmesg always shows a full log. Currently kmsg buffer size is set to 64kb, which is quite enough (of course, if something like LMK isn't spamming to kmsg log).

Good to hear that!
[Galaxy Ace II Android Development] Mr.Adalbert:
Is it possible to enable Short GI in wifi adapter? Our device connects always at maximum 65Mbps. With short GI 802.11n can work at 72Mbps with 20MHz channel. I dont suppose our device to support 150Mbps at 40Mhz but maybe it's worrth checking too.
[Galaxy Ace II Android Development] ChronoMonochrome:
Are there any devices with BCM43* wifi adapter family that supports it? I can take a look into tuna kernel source, but I'm not sure if I ever saw anything like that so far.
[Galaxy Ace II Android Development] ChronoMonochrome:
New release r4.7 of Chrono Kernel for Galaxy Ace 2 is up!

Changelog:

Changed vmalloc size to 192M (any issues with wifi should be now resolved)

Disabled a bunch of debugging options (now the non-debug kernel build is available as well)

Reduced kernel size (632.7 Mb of RAM is available on the standard version, 634.7 Mb on a non-debug one)

Compiled a non-performance critical parts (about 80-90%) of kernel in Thumb2 mode (this provides smaller size of the code while keeps about 97% of ARM performance)

Disabled IPV6 on a non-debug kernel

Disabled buggy SVNET whitelist code

Disintegrated Janice support for now - if anybody ever needs this again, please write me!

Re-added internal sdcard mount point again - use "use_intsdcard=0" option in /ramdisk/fstab_specs.txt to disable (re-flashing of a kernel is required after doing so)

Speed up a kernel installation a bit by changing 7-zip compression options

IPV6: compiled with -Os optimization level

Included CM14 ramdisk (no support in a kernel for the Nougat's init binary itself for now!)

P.s. the only downside of a non-debug kernel build compared to the standard one is that the network monitor menu is disappeared now in an Android settings app, due to disabling of IPV6 support. Please don't report about this - it has to be fixed in ROMs (if at all). Beside of that, please test and report about any issues found in these builds.

Thanks!

Download links are available below: http://ultimaterom.h1n.ru/downloads/chrono_kernel/
[Galaxy Ace II Android Development] shaqman89:
Strange thing happen when I try to download kernel using latest desktop Firefox, whenever I click the link, the tab closes itself. In effect, I can't download it using Firefox. Tried using latest Chrome and it worked.
[Galaxy Ace II Android Development] ChronoMonochrome:
Strange thing indeed, I'll check soon on this.

I've updated links to a new builds since I was experiencing a weird issues wirh maps loading in Yandex navigator app - seems that disabling IPv6 for now in its current state is really a mess even if apps aren't using it.
[Galaxy Ace II Android Development] spurr:
Issue from my end.. Both links for 4.7 are currently redirecting to http://www.poishi.com , 4.6 and 4.5 seem ok.
[Galaxy Ace II Android Development] ChronoMonochrome:
My bad, both liks were with a typo. Now links should work normally.
[Galaxy Ace II Android Development] ChronoMonochrome:
New release r4.8 of Chrono Kernel for Galaxy Ace 2 is up!!

Changelog:

Fixed A2DP broken in the suspend (i.e. when the display is off)

Added sdcardfs support for Android 6.0 (needs an update in a ROM so wait for a new releases!)

Fixed UID_CPUTIME support as required by Marshmallow

A2DP: we've been tracking this bug for a while, and now it was finally fixed thanks to testing by SergeyL@4pda. The problem was that A2DP wasn't working when user was listening to the music via bluetooth with the display powered off. As it turned out, the culprit was a some of CPUidle debugging code that was disabled since r3.8.1 in an effort of reducing the size of the kernel.

UID_CPUTIME: this is a module that now on Marshmallow does per-apps tracking of the power consuming. The fixes are minor, and are backports of some changes from Android Kernel 3.10. Not sure if the battery stats now are working better (I assume that the battery stats are generally somehow bugged on MM, so I was doing these backports in order to check that), but at least we have as complete support for this feature as it's possible on LK3.0 :)

Fave a fun and happy flashing!

Download links are available here.
[Galaxy Ace II Android Development] slayer_007:
Link Not Working: Account disabled by server administrator
[Galaxy Ace II Android Development] ChronoMonochrome:
Alright, the account was disabled due to the inactivity, but now the blog is available again.
[Galaxy Ace II Android Development] Far'z:
how to unpack and repack boot.img to ace 2 Can someone help me thank you in advance
[Galaxy Ace II Android Development] ChronoMonochrome:
Generally speaking, it's possible to repack boot.img in theory, A method that is currently used by the installer is way too tricky, has some limitations, and not guaranteed to work in 100% of cases, and thereby, is deprecated. In practice, it's too complicated to implement a proper method of repacking kernel image.
[Galaxy Ace II Android Development] Far'z:
maybe you could teach me to his way
[Galaxy Ace II Android Development] ChronoMonochrome:
This is not something that is easily done from the userspace. In the fact, even in the current implementation that is used by an installer one trick is involved - the kernel gets uncompressed during the compilation on the host, and further it gets compressed (packed) back to boot.img during the installation.

p.s. what are you trying to achieve by repacking the kernel?
[Galaxy Ace II Android Development] Far'z:
I actually wanted to make cwm for samsung mobile SM-J100F J1. I've been looking at cwm for samsung google it but nothing and finally I decided to port from a mobile ace 2 belongs to my brother. Can you help me to make it?
[Galaxy Ace II Android Development] ChronoMonochrome:
You can't use recovery (CWM in a particular) from another phone, thus, you'd have to compile it from the sources.

However, you can find some of TWRP builds on 4pda: http://4pda.ru/forum/index.php?showtopic=689574&st=540#entry46882731 , http://4pda.ru/forum/index.php?s=&showtopic=689574&view=findpost&p=42867645

(you need an account to download those files).

p.s. I haven't tested those builds, so be aware of the possible issues.

removed - this is actually another phone.
[Galaxy Ace II Android Development] Far'z:
how can I get the source cwm for my device :(

I do not know anymore how to root my device :( :(
[Galaxy Ace II Android Development] ChronoMonochrome:
New build r4.8.1 is up!

Changelog

Reverted LTO optimization (implementation is broken), by doing so, the kernel size was reduced by ~100kb

VPN and TTL editor apps now should work again (needs to be confirmed)

Cleaned up sdcardfs workarounds, disabled some logging

Personally, I have only tested VPN in the app Opera Max.

Download links are available here.

Enjoy!
[Galaxy Ace II Android Development] atakan33:
The media server had died error

Camera didn't work Chrono.What can I do ?

Edit : Problem fixed chrono. I uninstall chrono kernel settings .

Chrono I use Rox's cm11.Can you release Chrono Kernel Settings apk on your ftp server ?
[Galaxy Ace II Android Development] Far'z:
What does this new version suitable for MIUI 6?
[Galaxy Ace II Android Development] ChronoMonochrome:
I don't maintain Chrono Kernel Settings, you can get the latest app version here: http://xdaforums.com/galaxy-ace/ace-2-apps/app-chronokernel-settings-v0-9-t3014123 .

If you originally meant here whether this build is suitable for MIUI 6, then better to ask peolple that use this ROM / or read the corresponding topic.
[Galaxy Ace II Android Development] ChronoMonochrome:
New release r4.8.2 is up!

Changelog

Dirty Cow vulnerability (CVE-2016-5195) fix

The Dirty Cow is a privilege-escalation vulnerability, that potentionally can allow malicious processes to gain root access by modifying system files. (Read more in article: http://www.xda-developers.com/9-yea...-dirty-cow-can-root-every-version-of-android/ )

Download links are available here.

Enjoy!
[Galaxy Ace II Android Development] shaqman89:
Thanks, that was really fast :D :good::good::good:
[Galaxy Ace II Android Development] Bogazicili90:
Guys does this compatible with the Stock 4.1.2 MG2 ROM?
[Galaxy Ace II Android Development] ChronoMonochrome:
It should be still compatible with stock, however I'm not sure how much is it suitable / comfortable to use on 4.1.2.
[Galaxy Ace II Android Development] Farzin 073:
Hi . I have 2 quistions ;

1-whats different between debug and non debug ??

2-i want to repart my storage and I use twrp recovery ... can I use ace2nuzer repartion.zip with your kernel ??
[Galaxy Ace II Android Development] shaqman89:
1. Debug contains more debugging traces, while non debug got most debugging traces disabled

2. Yes, you can.
[Galaxy Ace II Android Development] fonzacus:
im using ace2nutzers 20160718 (pre repartition).

ive been using your 4.8.2 nodebug for a few days, and im running into no network and sometimes no sim card bug. ill try using the normal version and see if the problem persists.
[Galaxy Ace II Android Development] YelloneK:
Hi, what happened to your party? I wanted to download the kernel and ROM, and your page has been deleted :(.
[Galaxy Ace II Android Development] ChronoMonochrome:
@up

The blog was moved to http://chrono.insomnia247.nl .
[Galaxy Ace II Android Development] ChronoMonochrome:
New release is up!

Hey there!

Haven't been active here for a long time :cyclops:

A couple of latests weeks I was working on the kernel updates, so now I felt it's ready for the release. The main thing I was working on is an update to google's android-3.4 sources - not a partial updates or backports, but rather a full switch to the LK3.4. I'm not going to excitedly exclaim, though it's difficult to overestimate this. Since the first attempts to use LK 3.4 sources on these devices, now it's a lot of time has passed since branches android-3.10, 3.18 and even 4.x were released by google, but nevertheless it's still better than an ancient LK3.0 sources :p

Changelog

based on google's android-3.4 branch

backport of CMA (Contiguous Memory Allocator) from android-3.18

changed HWMEM allocator API to a hybrid (CMA + HWMEM) allocations - (WIP currently)

reduced HWMEM size to 68Mb (648.9 Mb of RAM is available)

some adjustments in the memory management: changed vmalloc size to 240Mb, disabled HighMem

reduced the memory used by kexec hardboot to an actually required one RAM page (4k), instead of 1Mb

(the way it was done wasn't allowing to use less than 1Mb, so now this page is moved to the RAM space allocated by RAM console, thus RAM console buffer size is reduced accordingly)

moved the most of the networking features as modules

reduced the kernel boot time - it actually might vastly vary, but an average is ~7900 ms

PLLDDR stability updates. Now it also possible to directly write the frequency in kHz to the PLLDDR sysfs interface (rather than specifying raw pllddr value, i.e. you can type 975000 instead of 0x5017f )

Known issues

db8500 regulators fails to initialize, strangely, it doesn't lead to any serious errors

IRQ (interrupts) might be mishandled by some drivers such as proximity sensor

All the device-specific sources (USB, MMC, DMA, ... etc) aren't updated to LK3.4 yet

I would want to say it's stable enough, but probably it's not entirely true - please report bugs if you find them!

Download link: http://www.xda.mister-freeze.eu/XDA-files/ChronoMonochrome/kernel/chrono_kernel_r5.0.zip

P.s. ATM android 7.1.1 (CM14.1 and RR 7.1.1) is not supported.
[Galaxy Ace II Android Development] Tebex:
I'm installing it right now. I'll test it for a few hours and tell how stable it is.
[Galaxy Ace II Android Development] 3liteking148:
Is this for real?????

But seriously, congratulations for porting Linux 3.4 to a U8500 device!!!
[Galaxy Ace II Android Development] ChronoMonochrome:
Took a lot of a time to find the coolpripts that wasn't allowing to boot it up :silly:

The main part of the bringup commits are https://github.com/ChronoMonochrome/Chrono_Kernel-1/commits/dacc0fb3347b4d641b5ab4294761c45f18ef881b - particularly, there were two pitfalls:

commits "ARM: move iotable mappings within the vmalloc region" and "ARM: add generic ioremap optimization by reusing static mappings"

U8500 seems to use some device static mappings that are outside of the vmalloc space. Thus, after applying the first commit those mappings were overlapping with the vmalloc causing the kernel to crash. Some more recent commits reverted too, in order to have these two mentioned be reverted cleanly.

P.s.

The sources are available here: https://github.com/ChronoMonochrome/Chrono_Kernel-1/commits/0f85a7bec63d9b615275acb3e4ab50890724aba2 (there are some more changes that I'm currently cleaning up).
[Galaxy Ace II Android Development] ChronoMonochrome:
[MENTION=5840412]ace2nutzer[/MENTION], [MENTION=7606633]3liteking148[/MENTION], [MENTION=4400604]Meticulus[/MENTION], [MENTION=5011036]New Macław[/MENTION], [MENTION=5371721]Epirex[/MENTION], and maybe anyone else who might be interested in the following...

I've pushed the LK3.4 bringup commits: https://github.com/ChronoMonochrome/Chrono_Kernel-1/commits/android-3.4 . This kernel supports codina / janice only, but it's a matter of adding the device-specific drivers and applying a compilation fixes to them, if you want to upgrade your device kernel to android-3.4. Most of the linked commits are bringup part, it was intentionally that there are as little an unrelated commits as possible, Have a fun!
[Galaxy Ace II Android Development] borkins:
Hello friends!

Anyone with issues on r5.0?

I decided to try it, but on boot some screen glitches appears on the bottom of the screen.

Then it gets stuck on the CM11 logo (the animation stops immediately) and boot loops.

After flashing an older kernel, everything is fine again.
[Galaxy Ace II Android Development] ChronoMonochrome:
I follow this question. I'd be glad if anyone can test how this build goes on android 4.4.4 and upload logs (last_kmsg, logcat - the latter if it's possible to get the logcat during the boot). I have some ideas about what could be causing these bugs, but I'd like to check logs before I try fixing them.

I don't currently have any 4.4.4 ROMs installed, so this OS version got untested. The only tested OS versions so far - 6.0.1 and 7.1.1. Nevertheless, if anyone having issues on other android versions, please don't hesitate to report them and attach logs, this can help the development.
[Galaxy Ace II Android Development] 3liteking148:
Hi [MENTION=5695278]ChronoMonochrome[/MENTION]

I started porting the 3.4 kernel to golden and managed to make it build but it won't boot.

The defconfig is based from codina_defconfig but modified for golden. I also replaced the sound folder with one from 3.0.101 as arm-linux-androideabi-4.9 crashes with:

arm-linux-androideabi-ld: internal error in thumb_branch_common, at /tmp/AOSP-toolchain/build/../binutils/binutils-2.25/gold/arm.cc:4166
make[4]: *** [sound/core/snd-pcm.o] Error 1
make[3]: *** [sound/core] Error 2
make[3]: *** Waiting for unfinished jobs....

There's also no last_kmsg file being generated.

All Sources: https://github.com/3liteking148/Chrono_Kernel-1
[Galaxy Ace II Android Development] ace2nutzer:
@up

which Toolchain are u using ??

I got it now xD.

I suggest to use the latest Linaro:

https://releases.linaro.org/components/toolchain/binaries/latest/arm-linux-gnueabihf/

This is so far the best Toolchain i ever used.

Edit:

as for the boot problem:

it wont boot due of various reasons probably.

i did only i quick check up to your latest commits

try the following:

disable

CONFIG_DB8500_LIVEOPP

CPU OC Driver by cocafe, maybe for your Hardware there are different PLL's

and probably u also want to remove Mali-400 GPU OC Driver by cocafe for the same reason.

Try to remove this:

CONFIG_CMDLINE=" ......

(then it'll use the default cmd_line from the bootloader)

or at least try to adapt it properly to your own command line from your Bootloader ...

i.e. board_id=12 is probably different for your Hardware.... and so on ... :)

Also make sure to use the proper ramdisk ....

Here u've to adapt it to your own initramfs.list.

Maybe i forgot some more things, but Chrono will tell u.
[Galaxy Ace II Android Development] ChronoMonochrome:
But why you've started from the branch "master", not from android-3.4? The latter should be easier to boot up, as it's both cleaner and there is not that much commits on the top of the latest android-3.4 commit. I'd suggest starting with the following:

https://github.com/3liteking148/Chr...1~...0b5c8113223429771f88843bddf2d32d535ee2f0

These commits adds all the device-specific drivers. Just add these from stock golden 3.0.31 kernel in the similar way - you've to ensure that you haven't missed any driver else it might not boot (repeat those commits - there are also some drivers headers modified, so if you're not sure which files to reset to the stock source, use git diff COMMIT~ COMMIT --name-only ). Some commits aren't really reset to the stock source (

for the instance, https://github.com/3liteking148/Chrono_Kernel-1/commit/a971b84447604763f2cf0f68a3762b47f2da2bd0, https://github.com/3liteking148/Chrono_Kernel-1/commit/7d65e0127b922a24cb9e780df80e6d0cc2cb04d0, https://github.com/3liteking148/Chrono_Kernel-1/commit/f0609532b38f0971a4ef31f4a3669780c673e000 ), so just cherry-pick them.

Yep, like [MENTION=5840412]ace2nutzer[/MENTION] said, you have also be careful not to use LiveOPP (in the general, all the prcmu code that is specific to codina / janice) as this code isn't compatible with golden. Once done with the adding sources, merge the rest commits (don't forget about commits that are preceding these ones). About the toolchain, again, android-3.4 branch should be easily buildable compared to master branch - I've removed here any aggressive Makefile optimizations.
[Galaxy Ace II Android Development] ashwi_:
[MENTION=5695278]ChronoMonochrome[/MENTION] Does the 3.4.x kernel boot with segeyL's 7.1.1? Is it recommended?

Also I'm not using Ace2 as my daily driver. So minor hiccups would be fine. If not 3.4.x, then which one of the 3.0.x kernel would you recommend?
[Galaxy Ace II Android Development] ChronoMonochrome:
Just use the one included in CM14.1 (the most of the times it already has the latest chrono kernel included). This build currently doesn't support 7.1.1 as stated in the changelog, the support will be added in the next build.
[Galaxy Ace II Android Development] borkins:
I've succeeded to boot with r5.0 on CM11 somehow.

Just flashed it without wipe of cache / dalvik. But it still crashes on boot, and after boot.
[Galaxy Ace II Android Development] ChronoMonochrome:
I've got a chance to test 4.4.4, unfortunately I can't reproduce your issue (tried both Vanir and latest CM11 build from ace2nutzer). Can you retry with a clean ROM installation just to see if it's not the software fault? Was logcat (adb) available that early at the point when the crash occurs? If not, you ca try the following init.d script:

busybox insmod /ramdisk/modules/autoload/logger.ko
logcat > /ramdisk/log.txt &
[Galaxy Ace II Android Development] ChronoMonochrome:
New build r5.1 is up!

Changelog

removed the core architecture hacks previously needed to get the static IO device mappings to work

vmalloc layer setup is no longer different than on other platforms - now all the setup (vmalloc size, VMALLOC_END, PAGE_OFFSET etc) is a "stock" LK 3.4

reduced the number of hacks needed to boot up LK3.4 (for devs only - https://github.com/ChronoMonochrome/Chrono_Kernel-1/commits/android-3.4-clean )

reverted some google's backports from a higher kernel versions

all the networking features are again compiled built-in, not as modules

applied THUMB2 optimization to most of drivers and a networking code

applied THUMB2 to the kernel decompressor code - for the faster decompression / bootup

LiveOPP improvements (thanks to [MENTION=4832589]cocafe[/MENTION] for some ideas and suggestions)

Added support for android 7.1.1 (AICP build by SergeyL is only tested so far)

Downloads here.
[Galaxy Ace II Android Development] borkins:
I've installed again the latest CM11 of our friend and flashed r5.0. For now there is no boot loops. I've tried that script too, but it didn't save any log.txt in ramdisk.

I can see a lot of errors during the boot with the LiveBoot app. It must save a log during the boot in cache partition, but something happened with the partition - it's always empty.

No crashes for now, but here is some logs I've made with the SysLog app.
[Galaxy Ace II Android Development] ChronoMonochrome:
I can't do much about those errors - it's just how module insertion script works (the order of module insertion is not fully correct for now, so some errors might pop up in log, though subsequently it gets all the modules loaded). It was reverted in r5.1 anyway. About memory allocation failures - it's something I've tried to fix, but forgot to add these changes in the release. It's absolutely normal that CMA allocations might fail sometimes (given to the alloc size and the free CMA memory), in this case it retries with a HWMEM allocator, so the warnings just needs to be suppressed.
[Galaxy Ace II Android Development] borkins:
I have problems with the Wi-Fi connection to the Internet. If I restart the Wi-Fi it works again for some time.

I thought that the Wi-Fi adapter is dying or something, but the phone is connected to the router, and on older kernel such as r3.0 it works fine.

I'm not sure, but I think the problem appeared after r4.5. Maybe some problems with the modules on KitKat?

Currently I'm on CM11 & r5.1, and overall the kernel is stable and I feel it a bit faster.
[Galaxy Ace II Android Development] ChronoMonochrome:
No, probably the problem is a kernel internal. I'll just probably try with the stock bcmdhd (wifi) module sources - the difference introduced in r4.5 is a relatively small, but who knows.. Thanks for reporting.