yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] ChronoMonochrome:
I uploaded new build. There is no changelog, I just tried to make more stable build. I've plan to upload builds for all android version, but my internet is very slow for now. Here is only builds for 4.1.2 and 4.2.2. Maybe I'll upload other builds tomorrow.
[Galaxy Ace II Android Development] danny19901:
Its a shame anykernel mod doesn't work on Ace 2 it would saved a lot of time for kernels the mod is by Coush (All Cast, Clockwork mod dev etc...)
[Galaxy Ace II Android Development] RootPegasus:
for last build , always random reboot, I'm using stockrom ! :(:)
[Galaxy Ace II Android Development] pedroleon99:
Try 12/08 build.I'm using that and works fine: no reboots and the phone is super fast

Inviato dal mio GT-I8160 utilizzando Tapatalk
[Galaxy Ace II Android Development] RootPegasus:
I will try, thank you :)
[Galaxy Ace II Android Development] danny19901:
OK latest EXT4 kernel shows 998MHZ instead of 1GHZ/1000Mhz
[Galaxy Ace II Android Development] ChronoMonochrome:
Yeah, there was a reason for it.
[Galaxy Ace II Android Development] ace2nutzer:
@ people with reboots:

i hope your phone is not broken like mine... :(

[MENTION=4962787]fluffi444[/MENTION]

greenify is a very bad idea on an android OS.. just use for example: Autorun Manager... it's enough.

Addidionally u can use Firewall .. then u can block the internet acces for some apps.. at the same time the adds aren't showing anymore and saves battery.

@ Chrono

u wrote always poor ram management.. but i don't believe that is the reason for reboots.. ram management is for months very good and stable.

Ram is always 90% used.. that is normal.. OOM LMK .....:good:

IMHO reboots are related by OC and UV.. !
[Galaxy Ace II Android Development] manthes:
screen tearing for s6d driver is still present for kitkat roms. until now 24/7 build was the best (i have tried only builds with twrp)
[Galaxy Ace II Android Development] ChronoMonochrome:
I need to know a latest kernel build where bluetooth worked normally.
[Galaxy Ace II Android Development] borkins:
[MENTION=5695278]ChronoMonochrome[/MENTION],

I've tested r4.2.8 and my issue with the Wi-Fi appears on it. Seems, that is the reason why the patch not fixed it.

It takes some time to catch the issue, and looks I've skipped or not tested enough, some of the builds from r3.0 to r4.6.

Edit: Strange, I tested some of this builds before, but now they have the problem. :/

This is found so far:

All to r3.7 (excluded) + r4.2.9 - OK

From r3.7.1 (excluding r4.2.9 ) to r5.4 - Wi-Fi issue:

- the Wi-Fi looses the connectivity randomly

- only restarting the Wi-Fi adapter restores the normal functionality.

According to these changelogs, it's a mystery for me (if it's only a driver issue, why the stock on r4.3 is faulty for me, but on r4.2.9 is fine):

Changelog r4.2.8

Changelog r4.2.9

Changelog r4.3

Thank you a lot for your time and work on this (even when the others doesn't have that issue)! I appreciate it!

I'll be glad, if you can help me further.
[Galaxy Ace II Android Development] ChronoMonochrome:
New release r5.4.1 is up!

Changelog

r5.4.1

fixed bluetooth bug on android 5.1.1 and older versions

wifi driver update from i9305 kernel *

mcde: partial revert to r4.3 kernel (should fix some reported issues with the display)

crypto: enabled some kernel configs

janice display drivers update **

* with this update wifi on stock will probably be not working. If there are still some stock users, let me know, I'll make a compatible with stock build.

** again, if there are some janice users, can build a new test release on a request.

Enjoy!
[Galaxy Ace II Android Development] Pdevo:
Chrono, I think me and [MENTION=7779223]sm_adil[/MENTION] too would be glad to test a janice build when you will get some time to compile one
[Galaxy Ace II Android Development] ChronoMonochrome:
Ok, uploaded r5.4.1 release for janice. http://xda.mister-freeze.eu/XDA-files/ChronoMonochrome/misc/chrono_kernel_r5.4.1-janice.zip

Now should (hopefully) work with any CM-based (from CM10.1 till CM14.1) ROM.

I still need installation and boot logs ( /ramdisk/last_kernel_install.txt and /ramdisk/last_boot.txt ). A second one needs to be taken when the phone in a recovery bootloop - you can flash a stock kernel and take the log as I've described a few posts ago. Thanks for testing.
[Galaxy Ace II Android Development] borkins:
Great work chrono!

I can confirm that the Bluetooth is operating quite well on r5.4.1 and CM11.

The Wi-Fi is working fine too. But I'll test it a little bit more, to confirm.

I hope that there is no problem for others too.

P.S. I don't remember to have problems with the Wi-Fi on builds below r4.0, and I've began to

think that it is carried when switching between the builds. Also I forgot to wipe the ramdisk.

Now I'm wondering if my Wi-Fi adapter is original, why it have problems with the stock drivers.

Actually the mainboard was replaced once in an authorized service.

I doubt that the Wi-Fi adapter is replaced too for some reason. Not sure how to check it, but whatever.
[Galaxy Ace II Android Development] Pdevo:
Chrono, can still work also with stock rom on janice or need a cm rom?
[Galaxy Ace II Android Development] ChronoMonochrome:
Stock should still work, though wifi likely won't be working.
[Galaxy Ace II Android Development] borkins:
No problems with the Wi-Fi so far, but I got one SW and one SW -> HW reboot.

Not sure, but maybe it was due to not enough RAM in that moment.
[Galaxy Ace II Android Development] ChronoMonochrome:
Ok, I think it must be due to the wifi driver is not a robust enough to handle such extreme conditions caused by OOM.

Can you test the following build and report if issue is still there?

http://xda.mister-freeze.eu/XDA-files/ChronoMonochrome/misc/chrono_kernel_r5.4.1-test.zip
[Galaxy Ace II Android Development] borkins:
Hmm, yeah. I tested it (r5.4.1-test) and I got another SW reboot that I predicted. I've waited for low RAM ~45MB, ZRAM ~10 MB and I opened a huge app to see if it will reboot , and then it rebooted to CM logo. Before that it worked fine a whole day.
[Galaxy Ace II Android Development] ChronoMonochrome:
I've added a few NULL pointer checks, but now another "stock" checks were triggered:

It's like playing cat-and-mouse game with this driver. Since it can't work reliably in OOM condition, I'll probably have to update / revert to another version of dhd module.

UPD. By the way, it seems that there are a plenty of variants on how to update BCMDHD module. I've just tried wifi driver from Nexus Mako kernel and it seems to work! I'll try updating it to some most recent Nexus device. Don't know why I never tried that before and was relying on crappy Samsung drivers.
[Galaxy Ace II Android Development] :
Hey Chrono, I founded that I cannot change lcdclk frequency to 'custom'. Also I don't see 'Lagfree' governor in /system/lib/modules

How can I get that? Someone can help me?
[Galaxy Ace II Android Development] ChronoMonochrome:
1. You don't need to explicitly choose a "custom" lcdclk entry. It's automatically chosen when you write LCDLCK frequency (not the entry index) to lcdclk interface. To get started you typically need to select a required lcdclk entry index: echo 0 > /sys/kernel/mcde/lcdclk .

2. Lagfree CPU governor is not supported by the current release.

Oh, I'm afraid that was too quickly. Mako's wifi driver can show an available networks but actually fails to connect to any of them and crashes randomly. A good thing is that it's still possible to use a non-stock driver (though, re-implementation of some stock driver configs will be required).
[Galaxy Ace II Android Development] :
Can I convert Ace2nutzer's 4.4.4 ROM from EXT4 to F2FS? I hear Ace2nutzer said that this ROM is not compatible with F2FS. I will do:

1. Convert his ROM to F2FS (use manual way)

2. Install ChronoKernel

3. Install ROM

4. Install Aroma Gapps

5. Install his kernel (I don't know that his kernel is compatible with F2FS or not)

Is this correct?
[Galaxy Ace II Android Development] ChronoMonochrome:
Nope, you can't use kernel that doesn't support F2FS with F2FS-formatted partitions.
[Galaxy Ace II Android Development] techusthad:
I have a doubt geek,Any i9070 roms using this kernel?

I am on Resurection remix Lolipop,My phone is i9070
[Galaxy Ace II Android Development] ChronoMonochrome:
New release r5.5 is up!

Changelog

r5.5

PM subsystem: revert to 3.0

net/wireless: reset to 3.0.101

CPUidle: revert to old 3.0 implementation

Improved battery life in deepsleep

PLLDDR OC: now should be fully reboot-safe *

* only with scripts provided:

http://xda.mister-freeze.eu/XDA-files/ChronoMonochrome/misc/pllddr_oc.zip

Disclaimer: use it on your own risk.

Installation howto:

1. Extract pllddr_oc.sh from pllddr_oc.zip and put in /ramdisk, give permissions 755 for file /ramdisk/pllddr_oc.sh

2. Extract 0000pllddr and put in /system/etc/init.d, give permissions 755 for this file.

As far as I have been testing it about week I never had reboots, but your millage may vary. Known issue are possible graphical artefacts at the startup. As a normal consequence of using this script, during the bootanimation the display will be turned off then enabled in 7 seconds - after that you might or might not have graphical glitch, in the case of which it's enough to turn off / turn on the display with the power button.

Feel free to change the default OC frequency (1050000 kHz) defined in /ramdisk/pllddr_oc.sh if necessary (don't use too high values if unsure) and report how is it stable for you.

Enjoy!
[Galaxy Ace II Android Development] borkins:
My experience with r5.5 so far:

The Wi-Fi disappears in a new way, usually when i left the phone to sleep, and when i wake it the Wi-Fi is gone, and can't be turned on.

Similar issue happens with the mobile operator network signal, but more rarely. I'm not sure whether it's from the tower cells. If it happens again, I'll reboot to confirm.

PLLDDR OC:

I didn't got a reboot so far, but I always got a glitches and the power on/off key doesn't remove them.
[Galaxy Ace II Android Development] ChronoMonochrome:
Ok I think it might be related to the recent CPUidle update.

Be sure to wait until a bootanimation is finished and not to press power button too quckly - a display should get suspended to get rid of glitches.
[Galaxy Ace II Android Development] borkins:
It doesn't help, the glitches appears in 1-10 sec after the screen gets on, no matter how long I wait on screen off.
[Galaxy Ace II Android Development] ChronoMonochrome:
Ok, I think I've fixed this issue. Scripts attached works without glitches for me, but the result may vary depending on android OS version (tested on 6.0.1 only so far).

UPD. Hmm, 4.4.4 really has some problems with OC. The image just dissapears from the display after some time. Is this also happens in your case?

UPD2. Reloaded scripts - not sure whether these works fully stable, but already better than previous ones.
[Galaxy Ace II Android Development] borkins:
Thanks!

I'll try it, if I can fix my phone - today it got "self-bricked" or something.

I left it to sleep for the night with 50% battery. But this morning I've saw that is powered off.

And when I turned it on, the phone started to bootloop to Ace 2 logo. In recovery there was a message for mounting the:

/data, /system, /efs, /ramdisk, /modem - "Invalid arguments". I've decided to flash a kernel through Odin, but now there is no enough power,

to turn on the phone, even plugged for charging. Maybe the battery is defective (it's only 1 year old). But I hope it's not some hardware issue.

Edit:

When I got to Download mode, the custom binary counter was 1 (i think for a first time).

Then I've tried the 3-part firmware of XXMB4 and the flashing process was OK.

But after the boot, nothing was flashed. Looks the nand memory is dead.
[Galaxy Ace II Android Development] ChronoMonochrome:
Sorry to hear that. So you can't boot into recovery even after flashing 3-part firmware?
[Galaxy Ace II Android Development] borkins:
After the flash it stuck again on the Ace 2 logo, so I booted to recovery, which for surprise was still TWRP 3,

and I think that everything on the partitions was intact.

I was able to get in these directories with the terminal and to create .txt files with information and then to access that information.

But when I tried to reboot, to see if they are still there, the phone didn't start anymore, even with a plugged charger.

Well, I got some logs before the end (and as far as I understand the dmsg.log, there is a serious problem with the mmc).
[Galaxy Ace II Android Development] ace2nutzer:
Battery level is very low... only 3%.

Boot to recovery and charge the battery.

On Download mode it doesn't charge at all.

Then try again to flash 3-part rom.

Good luck !
[Galaxy Ace II Android Development] borkins:
I measured the battery and it was 3.2 V, which means it's totally exhausted.

So, I putted the old original battery (4.0V ~ 60%), but the phone won't start.
[Galaxy Ace II Android Development] ace2nutzer:
Yeah it's clear. Now try to flash 3-part rom.

If it can't boot anyway, u can try to force flash with heimdall.

That's what i would try.

2 Years ago i had also a read-only emmc.

Then i tried 15 - 20 times to flash stock rom by trying every time another usb port (i've 3) then suddenly it worked again and so far it's still working good.

I think there's a "programmed dead" in order to force people to buy a New phone.
[Galaxy Ace II Android Development] :
U said you use a trick to force flash! But maybe I will try it to rescue my bricked phone :) I will report to u if it works...
[Galaxy Ace II Android Development] ace2nutzer:
As long Download-Mode works, there's always some chance to get it to work .. even if it's not so easy.

Good Luck Guys !
[Galaxy Ace II Android Development] borkins:
Thank you!

But, as I mentioned twice, I can't turn on the phone anymore. So it got worst. It doesn't vibrate, when holding the power key.

Also, the PC detects a device, but can't install a 'U8500 USB ROM' driver successfully, so Odin can't recognize it.

Seems even the bootloader is affected. I don't know how, because after the flash of the 3-part firmware, the phone turned on, and I got in recovery.

Even if something is screwed up with the partitions in the recovery, the bootloader should be fine. But when I rebooted, the phone didn't turn on anymore.

I think that a copy of the stock bootloader should be kept in a separate chip as a backup, not only in the main mmc-chip.

But the companies forces you to by a new phone.

(Meanwhile I'm planning to get another Ace 2).

Sorry if it goes too offtopic!
[Galaxy Ace II Android Development] ace2nutzer:
Ah ok, then something went wrong with the flash procedure. Maybe a bad USB Contact during writing the new Bootloader or Battery was too low and ruined the Bootloader during re-writing it.

Yeah unfortunately there's no hard-bootloader, so even using a USB-JIG wont help.

Only way is now a Riff-Box(if the mmc is still ok) or simply replace the Board or buy a new one.
[Galaxy Ace II Android Development] techusthad:
Hello friends,

I saw undervolting is just a myth in some websites.

Does undervolting improved battery life in your codina?
[Galaxy Ace II Android Development] mirhl:
Soo.. I just discovered about the Snowball and linaro origins of the code.

I was wondering if your majestic work couldn't be pulled back there in mr. Poirier's now outdated trees?

Also, I realized there's no malloc/CMA for GPU. Shouldn't that be supported?

Also also, did you check if one of Linus Walleij's st-ericsson.git branches couldn't have some juicy idea?
[Galaxy Ace II Android Development] ChronoMonochrome:
Depends. You can much more improve a battery life by using a properly tuned for this platform governor. One of such governors already included in these builds (and enabled as default one), Dynamic. Nevertheless, a reasonable undervolting will never hurt.

It already supports some kind of dynamic GPU memory allocations (HWMEM + CMA hybrid memory allocator). If you are interesting, you can look at commits

https://github.com/ChronoMonochrome/Chrono_Kernel-1/commits/hwmem

This support is quite limited, because CMA doesn't seem to work properly. So a dynamic allocations are mostly possible at the early boot stage, when there is a plenty of contiguos free RAM. Otherwise, dynamic allocations through CMA will usually fail and allocation will be processed through HWMEM API.

UPD. Most of the vendor solutions comes to some platform-specific fixes around this. I was thinking about building some custom kernel from source of device that already has a properly enabled CMA support, but currently this project is frozen.
[Galaxy Ace II Android Development] mirhl:
I thought CMA's job was exactly reserving contiguous RAM?

Allocation failures should be only due to pinned pages in the CMA area they shouldn't be expected to be. As I posted in the related thread, Allwinner guys seem just happy about it.

Guess like you could check 'modern' workarounds tho?

Also.. Didn't mali had a MMU?
[Galaxy Ace II Android Development] techusthad:
I am on dynamic and tweaked it for battery life according to instructions from mkaluza github page.But can anyone give me screenshot/attachment of init.d uv script, which will be almost stable in all devices.

Thanks in advance
[Galaxy Ace II Android Development] ChronoMonochrome:
I'm not sure if it's due to pinned pages. The problem is that, CMA areas aren't even allocated at the boot time. I don't remember an exact errors in dmesg, but the message was smth like "failed to allocate X KiB pool for atomic coherent allocation". Thus, it makes CMA work worst since it has to allocate a memory not from its areas which isn't that easy task, therefore it fails almost everytime. I'm not expert in a DMA / CMA stuff, maybe you know what's wrong with the CMA setup on the platform side (I believe the problem might come from the device-specific configuration)?

I was trying to manually allocate CMA area ( https://github.com/ChronoMonochrome/Chrono_Kernel-1/commit/697e12c2e0185b8e0d19699f0301849dcf9f1b71 ), but that always fails. I'm not sure if it's proper to call dma_contiguous_reserve_area from the board side, though I don't remember if dma_declare_contiguous worked with this CMA implementation, too.

I was trying to implement GCMA, but either I failed to backport it properly for LK 3.4 or it just didn't work with the same issues as CMA (don't remember). I also doubt if I can implement some a modern fixes like a second one suggested - to get it work properly it will almost certainly need some dependencies that would be not that easy to implement cause of kernel version difference (LK 4.12 vs LK 3.4). I think first I need to find a way to get it properly with LK3.6 / 3.16 CMA backports, like in the kernel source, which my implementation of HWMEM + CMA allocator was heavily based upon. Another issue with this approach is that I can't seem to find a patchset of CMA backport from LK3.16 for 3.4. Using another device kernel source isn't easy enough due to some vendor hacks that makes harder to boot such a kernel.

Yep, U8500 platform devices has MMU. But HWMEM users (camera, video etc) needs a physically (not virtually) contiguous memory. Just for fun, I was trying to use an usual malloc / free as an allocator backend - for the instance, video playback had issues like green artefacts (it should be due to that a memory was physically fragmented).

You can't find an undervolting config that would work stably on every device. It depends on the quality of the CPU, which varies from device to device.
[Galaxy Ace II Android Development] mirhl:
AFAIK, CMA areas should be allocated on boot.

And later released for everything that is movable to use afterwards. If that ain't working.. I guess it's broken to the core?

Then I cannot really claim to have gotten into the code. I just skimmed at quality summaries.

(I think I only now got that every device needs its own mmu)

But I too was thinking to something device-specific, though after a quick check to dma-mapping.c history.. My god what a long way we have gone through

How far are we from 3.10? :D (also stares at commits 36d0fd2198da3fd16b0e0da50ece05b4d295d2f1 and 21caf3a765b0a88f8fedf63b36e5d15683b73fe5)
[Galaxy Ace II Android Development] AkosPaha:
Hey [MENTION=5695278]ChronoMonochrome[/MENTION]!

I have a question, I saw the new ROM, and saw the Chrono kernel 5.6.zip in the download folder, my question would be that the CK5.6 supports the ace2nutzer 4.4 ROM? Or just Android 8.0?:)
[Galaxy Ace II Android Development] ChronoMonochrome:
It supports all ROMs from 4.1.2 to 8.0.0. You might need to remove A2N control app to avoid conflicts.
[Galaxy Ace II Android Development] AkosPaha:
I know I need to remove it if I change Kernel.

Thank you!
[Galaxy Ace II Android Development] techusthad:
How to disable touchboost(input boost)

/sys/kernel/cpufreq/input_boost_freq
[Galaxy Ace II Android Development] Spexxos:
The Galaxy Ace II confuses me. I flashed several kernels, roms etc. on different devices before but for this one I am confused. I would greatly appreciate if someone could give me a hint or two.

I have a completly stock Ace 2. So first I wanted to install TRWP. However TRWP needs this kernel. How do I flash a kernel without a custom recovery? Odin? If so: How? I was not able to find a tutorial for that.

EDIT1: Nevermind got it working.
[Galaxy Ace II Android Development] AkosPaha:
Hey [MENTION=5695278]ChronoMonochrome[/MENTION]!

Your kernel supported to KCAL?:confused:
[Galaxy Ace II Android Development] ChronoMonochrome:
No, this hardware doesn't support such a feature.
[Galaxy Ace II Android Development] sm_adil:
Well I was able to boot LOS 11 on janice just by replacing ramdisk & the display bug is still present!!!.

I've Attached the logs, just hav look at it if you have time:)

and Chrono can you share janice source for kernel 3.4.113 I'm bit confused which branch are you using???
[Galaxy Ace II Android Development] ChronoMonochrome:
I believe it was a branch "master" at the moment of building a kernel for janice. You only need to pick up an appropriate kernel config (janice_defconfig).

It's quite difficult to fix things on a device that you don't own. I don't see anything in logs that might indicate that something goes wrong with the display part. Can you probably play with the display gamma adjusting (these interfaces normally should present with Janice display driver)?

UPD. There actually was one missing codepath on the display part I didn't notice initially. Can you test whether a display bug is still present in this build?
[Galaxy Ace II Android Development] ChronoMonochrome:
New build r5.6 is up!

Changelog

r5.6

security updates from Android 8.0.0 kernel

binder: updates from google common kernel

PLLDDR OC: reworked overclock algorithm *

janice display drivers updates

* OC now is done at the device boot stage. To apply overclock settings, create file /ramdisk/.pllddr_oc_freq and type 1050000 (the frequency in kHz).

For now only this frequency is tested and works stably. In the case of any instabilties you might encounter, just reboot to recovery and remove/rename file /ramdisk/.pllddr_oc_freq .
[Galaxy Ace II Android Development] sm_adil:
Well yeah it booted properly:laugh:

And the display bug is fixed.

If possible i would like to continue this project for janice.

Again thanks Chrono:highfive:
[Galaxy Ace II Android Development] ChronoMonochrome:
Sure, I'm releasing a relevant changes on my github repo right now.
[Galaxy Ace II Android Development] isaak:
I'm playing with your kernel on S Advance.:)

Can you confirm it's normal to have 800Mhz as min and max frequency in dynamic governor as default?

It looks odd and I don't see the logic behind it.
[Galaxy Ace II Android Development] ChronoMonochrome:
No, it's not normal. Normally min freq should be resetted to 200 MHz when the system is booted, but for some reason it doesn't happen (in your case). What OS are you using?