yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] ace2nutzer:
Kernel Update 20180303:

Changelog:

Kernel 20180303:

Re-added USB Power Interface (output voltage to the usb port)

Reduced kernel size a bit

Disabled all the usb host & otg stuff (lack of proper driver)

Disabled tv-out feature (not supported)

Changed and updated Native Language Support to European Languages inlc. € (it's for properly showing file names)

Increased/Updated lpa/vape2 voltage - should fix wake up issues and improve Sound Quality (louder + cleaner)

Removed tunable "extra_free_kbytes" once again - it doesn't make things better :)

Re-enabled compaction-retry - forced compaction on high memory pressure to avoid oom

Updated ramdisk

A2N Kernel Control [GT-I8160] V3.4

Re-added USB Power - ability to connected some gadgets to your phone (no otg)

Version Info:

Memory Management should be better now.

Kernel is now configured to issue an kernel panic on oom (of-of-memory) .. so on oom after 1 sec. the machine will reboot.

After the reboot u can check last_kmsg if the reason was really a kernel panic caused by oom or something else.

If u even want to see what caused the oom condition, u can write in your init.d script in /system/etc/init.d/99_user the following line of code:

echo 1 > /proc/sys/vm/oom_dump_tasks

Also updated Post #1 & Post 3# (fixed chaos with 3-parted stock rom how-to lol)

And uploaded latest Stock ROM for I8160L to our FTP Server for fast Download.

Now we've ALL needed Stock ROM's for the Ace 2 :good:

Enjoy your favourite Kernel :)
[Galaxy Ace II Android Development] Kunii:
LCD Type: S6D27A1

it happens when the screen is off for a little bit long, but it came back to normal for about 4-7mins
[Galaxy Ace II Android Development] :
Why activate panic on OOM?? If one use big apps like Facebook, FB Messenger, and do high multitasking, then they may have reboot! It will be an inconvenience...

But it is really useful for developers to debug. How about making a button in Debug list in A2N Kernel Control app for disabling/enabling "Panic on OOM"? It is better for user that does not want to debug.

I forgot to read the changelog carefully.

Also, thanks for your steps how to upgrade to Samsung 4.1.2 ROM :)

But link is dead in:
[Galaxy Ace II Android Development] ace2nutzer:
It's hardware bug, but u can workaround it.

Update to the latest kernel and see if it's better.

Did u enabled "Tuned Freq" ? if yes, then disabled it, if not, then enable "Chuck Norris mode"

Because it's better to stop the system after an oom. Forcing to run after a oom will only cause more filesystem errors than needed, also the system will not work properly at all, so it's better to reboot.

Normally oom should never happen, if u don't change memory management related things.

If u try to run an app that need more ram than the device has, (and swap/zram is disabled)

then the app will not start at all or it'll simply force close after some time of running .. and that's it!

oom condition only happens if the kernel or rom is wrong configured or the sources are buggy.

Yep, i've forgot to uplaod it at all xD
[Galaxy Ace II Android Development] ace2nutzer:
not needed modules.. they was needed for sdcard.. (drivers) but that caused problems with sdcard.. therefore in latest build the drivers for sdcard are built-in the kernel itself.. maybe if don't delete this files u'll have problems with sdcard...

it's no problem with older builds.. in every build are all needed modules.. that means u can delete all modules from /system/lib/modules (all files with *.ko) and then flash the kernel.. that is also possible.
[Galaxy Ace II Android Development] shadow252:
I think that [MENTION=5840412]ace2nutzer[/MENTION] said that he didn't test his kernel on Android 5.0.x but you can try it. Before that it's better to make a copy of your current system in CWM. ;)
[Galaxy Ace II Android Development] Moonly:
Once again, I can't flash the latest kernel because some files need to be modified or deleted. Once again, I can't delete the files required even if I authorized the root access to the file explorer... I'll stay with 12/20 build until those modifications will not be needed anymore...
[Galaxy Ace II Android Development] ChronoMonochrome:
In fact, not so important whether these files are removed or not :) Since these modules will not be loaded by system, it should not cause problems :)
[Galaxy Ace II Android Development] MarquesYOLO:
I feel more lag on latest build, also wake up is slower. For the moment I think 20141220 is the best f2fs kernel. However great work.
[Galaxy Ace II Android Development] MrBlackCore:
I did try that and the phone didnt boot. I was stuck at samsung logo.
[Galaxy Ace II Android Development] shadow252:
Then enter the CWM by pressing and holding menu, volume up, power buttons and after Ace II logo show up releasing them. Then restore your backup created in CWM earlier.
[Galaxy Ace II Android Development] galaxypep:
Lollipo

Hi I just want to ask where did you get lollipop for our galaxy ace 2?? And also hmm it is stable and good enough for daily use? I mean WiFi calls sms bluetooth etc. thanks in advance
[Galaxy Ace II Android Development] ace2nutzer:
Thanks, i'll check interactive parameters again.. it's not easy to make it smooth but at the same time trying to don't waste too much power... But it's possible. :)

Other that, everything ok with latest build here ????????
[Galaxy Ace II Android Development] galaxypep:
best build yet

For me personally best build yet. Very smooth, very powersave. Great work. Thanks! :)
[Galaxy Ace II Android Development] shaqman89:
You may check out this thread:

http://xdaforums.com/showthread.php?t=2989178
[Galaxy Ace II Android Development] Alex_Gamer:
Dear kernel user, i will share with you guys my experience...

first of all, i really recomend a fresh install of the rom whith this kernel, i have a awesome experience on this kernel, the battery duration its really good and the performance too, but if you wanna get a better graphics performance you need to do this:

set in NT-APP mali pre allocated memory size @ 32MB.

Type in terminal:

su

echo 40 > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load

This only works on interactive governor.

and in /system/etc/init.d u see the file: 01optimization .. read everything .. then u know how to OC the GPU.

I suggest to copy proper command and then execute in term. em.. just to see if it is stable.. when u've find the stable max GPU freq.. then u can save this value in your optimization file in init.d.. then it will be automatically execute at every booting.. (reboot required) remember: GPU OC in NT-APP in not working, it works only over scripts.

and another little thing, I recommend interactive governor for all, but if yu really want a better power save set the max cpu freq to 800mhz or use the conservative gov. but only if you going to do a lower demmand tasks ;)

Thanks to [MENTION=5840412]ace2nutzer[/MENTION] for all the info :)
[Galaxy Ace II Android Development] ace2nutzer:
thanks for the great report.

But more powersave is not on conservative.. but on ondemand.

And u forget to say: in optimization file .. there are 2 different commands for minfree values... by default is only activated the minfree values for multitasking.. that means games will run with bad speed but multitasking is very good. to have it reversed.. , more speed for games and less multitasking u need to edit the optimization file.
[Galaxy Ace II Android Development] Alex_Gamer:
No problem friend ;), and thanks for mention that, I forget for a moment :)
[Galaxy Ace II Android Development] Tree4ever:
delete for 20150112-Kernel under /system/lib/modules/

@ ace2nutzer: only delete the 3 modules from your #815(usb-mon,usb-storage,usb-acm(I don´t have this last one: usb-acm)or modules as in your #821 (all files with *.ko : bthid.ko,cdc-acm.ko,dhd.ko,exfat.ko,hwreg.ko,j4fs.ko,param.ko,rng-core.ko,usb-storage.ko and usbmon.ko ;total 10 I have ):confused::confused:
[Galaxy Ace II Android Development] VW22:
When I installed codina_kernel_cm11_20150107_f2fs_ace2nutzer.zip

or the codina_kernel_cm11_20150112_f2fs_ace2nutzer.zip

the camera stopped working when I want to startup the app.

Switching back to the codina_kernel_cm11_20141220_f2fs_ace2nutzer.zip the camera works fine. Anyone having same problem or idea what's wrong?
[Galaxy Ace II Android Development] bidug:
hi, here is my feedback :

I installed latest version (ext4) a few hours ago, after issuing many many "app is not responding, quit ? wait ? ... ?" messages with the previous build.

I OC the CPU at 1100MHz, passed a "stability test" in Antutu, and got a random reboot minutes after that. So I went back to 1000MHz which seems to work fine.

I set the CPU gov. to Conservative from now on :)

also no problem with the Camera.
[Galaxy Ace II Android Development] Alex_Gamer:
I suggest you to set interactive gov and paste in terminal the script on my shared experience :)
[Galaxy Ace II Android Development] bidug:
hi, thanks for the advice.

actually I don't really care much about battery life since I own a 4Ah battery which I bring almost everywhere. So I think I'll stick with Conservative cause performance is more important to me for now.

I also set pre-allocated GPU mem to 16MB. (The pre-alloc. GPU mem is in RAM right ? so if I reduce it, I got more RAM ? I set it to 16MB because I don't use games).

About your experience :

I don't perfectly understand what does:

echo 40 > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load

(I mean, what sort of setting is stored in that file ? what's the default value ?)

Why doesn't GPU OC work in NT app ? (maybe stupid question...)

If I OC the GPU by editing files as you explain, if it's unstable, and as it's set at boot, maybe I won't be able to perform a complete boot to change the freq back to a more stable value... right ?

When you write: "Type in Terminal", do you mean locally, using a dedicated app ? or on the computer via ADB, through the USB cable ? (I'm runing OS X so, no problem to use the Terminal). sorry for this newbie question :)

I just don't want to try something I don't fully understand, hence the many questions !

thank you
[Galaxy Ace II Android Development] ace2nutzer:
New Build is Up !!

Changelog:

20150115:

More Smoothness (tweaked interactive gov)

Yeah.. only the 3 modules.. and yes i meant cdc-acm.ko .. sorry .. at the end u'll have 7 Modules.

this is maybe due to memory management.. can u pls install gain latest build (01/15 from today).. and see again ? if the camera stop working again.. then try this:

in the 01optimization file.. just add an "#" before the echo command.. like this:

# Set custom Minfree Values (Memory Management for Multitasking)

echo 5120,6400,7680,8960,10240,11520 > /sys/module/lowmemorykiller/parameters/minfree

in

# Set custom Minfree Values (Memory Management for Multitasking)

[B][COLOR="Red"]#[/COLOR][/B] echo 5120,6400,7680,8960,10240,11520 > /sys/module/lowmemorykiller/parameters/minfree

save changes and reboot the phone.. and tell us if this fix your camera problem.

Yes.. this is right. :cowboy:

That is for more smoothness for interactive gov... but this Value: 40 .. is now kernel default on latest build here.. therefore no more needed for u all. ;)

Because of changed GPU / CPU and voltages algorithm.. NT-APP should be reworked / update.. but nobody do this :D

But it's not really needed.. it's not complicated.. u just need to change one number.. save and reboot.

It is better to edit the command (but don't save) then copy and paste the new command with the new gpu freq in term. emu. (stock app) and type:

su [ENTER]

and paste the command.. [ENTER]

test what is the highest stable freq... at the end edit the optimization file and save.. reboot.. that's it ! (then the new freq is automatically setted by default (on boot) )
[Galaxy Ace II Android Development] Kunii:
Yes sir, I tried enabling the tuned freq and the chuck norris mode and also updated to the latest kernel...but didn't fix the thing :(

hope this issue will be fixed..thanks :) I like the rom and kernel very much because of its very smooth performance
[Galaxy Ace II Android Development] :
Typo?

I've rechecked and the link is living again :)

But in the screenshot I see you are using Windows XP... I have newer drivers on newer Windows version. I am using Windows 10 for now and 100% no problem about connection... But on Windows XP sometimes I have troubles with flashing emergency kernel in Odin.
[Galaxy Ace II Android Development] ace2nutzer:
Ah ok that's a bit painful.

If even Chuck norris mode can't fix this, then u can try to play around with LCD Values ...

Use ADB (over PC) or use terminal emulator app to play with values.

In the end if u did find a stable solution, u can move your values to init.d.

The following example is for terminal emulator app:

First of all, super user:

su

LCD Freq.:

cd /sys/kernel/mcde
cat lcd_clk

now u see list of available lcd freqs and which freq is actually in use .. .. just try to change it..

e.g.:

Set 1 (30,72mhz)

echo 1 > lcd_clk

If no one freq fix your issue, u can even try to play with video.modes values .. .like this:

cd /sys/devices/pri_lcd_*
cat mcde_chnl

now u see the current video.mode config.. in my case i've s6d type .. and for that lcd model the actually config is this:

(when chuck norris mode is disabled)

[s6d27a1 MCDE Channel]
hbp: 6
hfp: 6
hsw: 6
vbp: 6
vfp: 6
vsw: 6

INFO: valid values are 1 - around 80 (more is also possible, but not recommended)

i suggest to group it in 2 Blocks and use the same value in that group ..

so, example given:

echo vsw=8 > mcde_chnl
echo vbp=8 > mcde_chnl

next block:

echo hsw=10 > mcde_chnl
echo hbp=10 > mcde_chnl
echo hfp=10 > mcde_chnl
echo vfp=10 > mcde_chnl

and finally apply the new values to the lcd:

echo update > mcde_chnl

The above example Values (lcd freq + video-modes) are even more fail-safe than the chuck norris mode in Kernel Control App.

If even those Values will not fix your Issue, then try some other values and feel free to post stable values for you. (maybe i can do something to implement it in app or so)
[Galaxy Ace II Android Development] Kunii:
I tried changing the lcd freq using the codes you have given, but value did not change. Sorry sir but this is my first time using terminal emulator. :) and also don't know how to move the values to init.d. Thanks :)
[Galaxy Ace II Android Development] ace2nutzer:
Oh, my fault. Use "1" instead "30720000".

Init.d is to make this change effect even after reboot. So try first if it helps at all.
[Galaxy Ace II Android Development] ace2nutzer:
Kernel Update 20180307:

Changelog:

Kernel 20180307:

Wifi: [re-added] reduced wakelock time of RX packet by half - thanks @ zwliew

Revert: "disable sia & sva wakelock" - caused reboot

[re-added] Fix "Dirty Cow" vulnerability - thanks @ Linus

Enjoy ! :)
[Galaxy Ace II Android Development] Kunii:
Okay sir, i have changed the value. :) but did not move the values to init.d yet. I will observe first if that fix my problem before i move it. Thank you very much! :) i'll update you once it fixed my problem

also updated to the latest kernel...
[Galaxy Ace II Android Development] :
I have seen "Fix "Dirty Cow" vulnerablity" somewhere old in your changelog. But why you re-add it again? Maybe you had removed before?

Anyways, thanks for this update!

But I see this problem: even on your newest ROM + kernel, I got blackscreen when I press button to wake my device up. (When I put my device to deep sleep for 3 - 5 minutes, then wake it up) It shows a blackscreen with many black vertical lines running extremely fast :( And when I turn the screen off then turn on again, the screen works again. But when I return back to stock the problem has gone :confused: (With stock kernel)

Do you have any clues of this problem?

And I have a small question: Who is the creator of the temp CWM on your server?
[Galaxy Ace II Android Development] ace2nutzer:
Yes, it was removed during the cleaning process of the sources :)

Check some posts before .. i wrote how to play with LCD Freq and video.modes.

I'm trying since Years to configure it that way that works for both lcd models and all lcd quality (mostly worse quality). But it seems that it's not possible. Not because i'm too stupid, but it's a lack of proper driver. and in addition the quality of the LCD Chips are very different.

On Stock ROM it works almost always, even worsest Chips, but it's because the Stock Driver is very fail-safe configured. U can try Stock Values .....probably it'll fix it, but later don't complain that it lags like hell :D

Search in this Forum (ace 2 development) for "temp cwm" u'll find a thread .. there u'll se where is the Developer.

It's only on my "FTP Account" just for fast download speed and in order to have all relevant Ace 2 Files in ONE PLACE.

This is also what the Owner of the FTP Server want, to have all the files on one place.
[Galaxy Ace II Android Development] :
As I promised, video of how-to install this ROM + Kernel is coming soon. :)

But for now it is very hard to record... As I am busy in school exams.

And also my video is only recorded by the Galaxy J7 one (only have 13MP) and my English speaking is also hard to hear (I'm a Vietnamese people). And I don't have any video editing app on my phone :(

Anyone have any app on Play Store that allows me to edit video, then please tell me :) [MENTION=5840412]ace2nutzer[/MENTION], thanks for your infomation. How can I return back to stock ROM without having to flash with Odin? And how can I do a Nandroid backup with stock ROM?
[Galaxy Ace II Android Development] ace2nutzer:
:good:

There's actually no other solution. sorry.

The "normal" way is still with ADB .. so u still need a Laptop.

Or if u flash TWRP u'll be able to do it over TWRP, by flashing ODIN kernel with TWRP recovery.

There are always 2 Variants of doing backups..

Variant 1:

normal backup of /system, /data, /boot /recovery.

Variant 2:

FULL Backup .. so the whole emmc of your Phone, which is reccommended if u want to switch between stock ROM and any custom roms. (so u'll not mess it up with the partitions)

Personally i use both, cwm & full backups.

Full backup of cm11:

Unmount everything except the microsd

Mount micro sd card over cwm or if it doesn't work, mount it by hand:

mount -t vfat -o rw /dev/block/mmcblk1p1 /storage/sdcard1

Full backup:

dd if=/dev/block/mmcblk0 of=/storage/sdcard1/backup/fullbackup_cm11.img bs=4096

Restore the full backup f needed:

again, unmount everything and mount only micro-sd.. and start restoring the img:

dd if=/storage/sdcard1/backup/fullbackup_cm11.img of=/dev/block/mmcblk0 bs=4096

Now u maybe install stock rom .. and want to make a backup ..

mount micro-sd:

mount -t vfat -o rw /dev/block/mmcblk1p1 /sdcard

full backup:

dd if=/dev/block/mmcblk0 of=/sdcard/backup/fullbackup_jb.img bs=4096

and later if u need to restore it:

(always the same, unmount everything and mount sdcard:

mount -t vfat -o rw /dev/block/mmcblk1p1 /sdcard

restore:

dd if=/sdcard/backup/fullbackup_jb.img of=/dev/block/mmcblk0 bs=4096

As u can see, it's always the same procedure and commands ... the only difference is just the mount point of the micro-sd card .. this is from ROM to ROM or from Recovery to Recovery a bit different.

One more example, (so u get it for sure)

Now u'Re on Stock rom an want back to CM11:

Unmount it all and mount sdcard:

mount -t vfat -o rw /dev/block/mmcblk1p1 /sdcard

restore cm11:

dd if=/sdcard/backup/fullbackup_cm11.img of=/dev/block/mmcblk0 bs=4096

Important notes:

* Before u start the backup or restore process, always make sure with command:

df

that every partition is really unmounted ! .. only ramdisk filesystem are allowed like:

/dev
/
/tmpfs

eg. u see /ramdisk is still mounted .. .then unmount it with simple command:

umount /ramdisk

then check the result with "df" and continue your work.

* immediately make sure that u only do a backup or restore if /system partition is really unmounted !

If not, u'll have later a read-only /system. Only proceed if there's really no other way to unmount it!

If "umount /system" fails, u should try it again with another recovery.
[Galaxy Ace II Android Development] :
Now I am giving to everyone a great new... The video of how to install this ROM have been recorded successfully! I am now preparing to modify the videos... As the videos is cutted in 3 parts. Just wait a little bit more... then the video will be uploaded! :good:
[Galaxy Ace II Android Development] Culateralligator:
Deleted. Wrong thread.:p
[Galaxy Ace II Android Development] :
Wow, you had killed my thoughts. I was seeing the "Next version" and thinking that you will upload a newer OS... but after you said on I had surprised :crying:

There are lots of AOSP 4.1.2 in our device's thread...
[Galaxy Ace II Android Development] ace2nutzer:
Yes that's right, but it's needed to build first AOSP 4.1.2 ROM in order to know how things works.

After that i'll start building latest AOSP.

There are also a lot of reasons why i decided to build AOSP 4.12 as next ROM.

We've from samsung only latest device drivers for 4.1.2.

Those Drivers are very important to get Multimedia working at its full speed.

That means commonly Hardware-Codecs, which are needed for perfectly working live video streaming in stock web browser, without to decrease Functionality, stability, performance and battery lifetime ! - (That's the problem actually on CM11 here ... we don't support some of the hardware codecs, also some websites with live-stream don't work at all and will just crash the system and reboot will happen)

The kernel itself is fully optimized to use the hardware properly, but it has nothing to to with the lack of proper codecs .. which is a ROM problem, not kernel.

Of course this ROM has also the binary code optimizations in order to use the hardware properly, instead to use software emulation for math processing, but this has also nothing to do with the codecs problematic. Actually on CM11 the missing hardware codecs are simply replaced with Software-Codecs .. in order to get live-video-stream to work at all ... but with bad performance.

You can compare the speed of Soft/HW-Codecs if u try to play a YouTube Video on Stock Browser once on CM11 and once on Stock ROM 4.1.2, u'll see that it works much better on Stock ROM ! (yes even with slower stock kernel lol)

Also the 4.1.2 ROM is very simple and fast to build for me ... because i just need to apply the samsung patches without to modify them .. then simply adding my ROM optimizations from CM11 .. and that's it ! - The AOSP 4.1.2 ROM will work (very probably) faster and hopefully completely bug free and battery lifetime should also better.

Then i'll try to port samsung patches to the latest AOSP ROM .. but that can take some time probably. Also actually i even can't say if i'll manage to do that at all ... i mean i don't know if it'll work as good as 4.1.2 and or if it'll have some of the bugs .. maybe like u already know how it's when some latest roms are released .. then some things don't work at all or are buggy... so --> BETA :)

Anyway later u can hopefully enjoy a great rom while u wait for a latest AOSP ROM.

If something is unclear or somebody has some questions, feel free to ask here.
[Galaxy Ace II Android Development] jupiez:
why the phone can't access the mass storage device when plug on cpu (just the charging the battery) ??

Nb: CM11 ROM 20180128 + Kernel 20180303
[Galaxy Ace II Android Development] ace2nutzer:
It's fixed on latest Version ... so just flash it. (no need to wipe anything) ;)
[Galaxy Ace II Android Development] jupiez:
flash rom / kernel bro?

Nb: Now my phone with the rom 20180128 & the kernel (latest version) but same problem can't access mass storage device
[Galaxy Ace II Android Development] ace2nutzer:
Yes, because the fix only works after wipe data. But if u don't need a clean Installation. go simply to settings ----> Storage ----> pc connection, and toggle the usb mode.

It'll fix instantly.. Noo need to reboot.
[Galaxy Ace II Android Development] jupiez:
mass storage (UMS) cecklist?
[Galaxy Ace II Android Development] ace2nutzer:
Yes, just choose mtp and then ums mass storage. That's it !