yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] jahula:
hi,

just today bought ace 2 in great condition

on oryginal 4.1 android its perfomance was ... quite poor

quick check on xda - and there it is, still alive rom with very promising kernel

so, i download everything You mentioned in "how to",

and step by sted did exacly as you decribed

went flawless,

when done, the first thing i notice was system response

it is 100% better even without any oveclocking

tomorrow i will test how it work in apps

and what i can tweak in Your kernel app

btw: for the first second i was a little upset that kernel app was a demo

but i start thinking - so much work, and only 4 PLN to thanks

so i think it is ok, everyone who liked and is using this system and kernel

can say thank You by this way

ps: You mentioned about working about 4.1 android for ace 2, hmm, why lower? not higher?

ps2: i found camera app really horrible,

the way menu is working, makes me always use different option

than that one i was "craving" (really, it is so hard - to that point)

it is soooooo bad, that i am going to look for any way to replace that app ;/
[Galaxy Ace II Android Development] ace2nutzer:
Any reason why u use that old version from 28.03.2018 ?

I suggest to update to the latest Verion.
[Galaxy Ace II Android Development] jahula:
so, while testing it today, Google maps (latest version from google store): 'Unfortunately Google Maps app has stopped'

after downloading older version 9.80.0 from internet - it seems to work nice, quite slowly but no problems ocured

seems like something was changed with one of latest update

soo, what is the best Google maps version to use?

this is one of prime funcionality in phone for me - as it many times saved my life on long bike trips,

i will be very thankfull for answer :)
[Galaxy Ace II Android Development] ace2nutzer:
Wait for CM11 Update .. maybe it'll fix it. .. If not, i suggest to install Stock ROM 4.1.2 with ODIN and then to flash temp_cwm_6028.zip and then a2n kernel for 4.1.2 rooted or normal version.

Strange, but i think it's rom bug.

Latest one should be fine :)

@ ALL

i've uploaded new kernel for Stock 4.1.2 .. rooted and normal version .. with that kernel SafetyNet will PASS!

And with the rooted version it'll not pass, but it'll immediately pass if u disable root in super user apk !

Later if u need root again, u've to enable it again in the super user apk and u need to reboot the phone ... then root is back again :)

Later i'll upload new kernel for 4.4.4 and new CM11 .... and Yeah .. SafetyNet will PASS AS WELL! :D

Change-log later ....

Stay tuned ;)
[Galaxy Ace II Android Development] :
So I don't need to use lots of my workaround again... ;)

Because SafetyNet passed on kernel level :victory:

Finally we can play PK Go and use banking apps :)

I'm very curious: How did you make it possible?
[Galaxy Ace II Android Development] ace2nutzer:
New Builds are Up !!

Changelog:

CM11 ROM 20180809:

Fixed SafetyNet - Passed :o

SafetyNet will PASS even with root enabled like it's done on "Magisk" :D

Reworked the whole SuperUser implementation

Play Store: Phone is now "Certified"

incl. A2N Kernel 20180809 - normal version

AUTO wipe cache and dalvik-cache

Kernel 20180809:

block/deadline-iosched: reset to AK3.0.72 and patched

Reworked all APE/DDR OPP requirements

PLLDDR OC Module: tiny updates - should fix boot animation failures when using it

Mali 400 GPU: reduced Voltages

Reduced also Voltage for LowPowerAudio

Cleaned Source

Updated EOC BLN

Updated BLN

Removed "sva" kernel wakelock - battery drain fix on suspend!

cpufreq: added suspend_max_freq interface

Use APE/DDR 25% OPP even for screen ON on idle

Reduced LCD Freq*

Fixed most of the compiler warnings for cleaner code

Updated Ramdisk in order to hide su binary - SafetyNet Fix

* = "Tuned Freq" disabled means stock lcd freq and will work stable,

but with enabled "Tuned Freq" it can cause some screen glitches caused by 25% OPP,

on the other hand, lower lcd freq and lower OPP states will save a lot of battery power.

A2N Kernel Control [GT-I8160] V4.6

misc: fix zram on 4.1.2 stock

A2N Kernel Control [GT-I8160] V4.5

CPU: add suspend_max_freq control

A2N Kernel Control [GT-I8160] V4.4

Fixed Support for GT-I8160L

Storage: Fixed compatibility

Misc/PLLDDR OC: fix restore on boot

source update

A2N Kernel Control [GT-I8160] V4.3

Updated API to 28

Tip:

if u still can't pass SafetyNet, then format /system before you install the ROM.

Enjoy ! :D
[Galaxy Ace II Android Development] :
It should be:

:confused::confused::confused:

:good::victory::victory::good:
[Galaxy Ace II Android Development] ace2nutzer:
Nope, it's right :)

You mean that with "Tuned Freq" enabled it's more smooth, that's right.

But unfortunately "Tuned Freq" requires APE OPP at least running at 50% in order to don't mess it up with the video output.

So in order to save more power, we use now 25% OPP with screen ON .. but it's only 100% stable if "Tuned Freq" is not enabled.

(otherwise it can mess it up).

In the next releases i'll try to fix micro lags on a different way .. so by changing MCDE clock, pixel clock and video modes.

Increasing the LCD Freq seems to be pretty unstable and caused for some users even that the screen don't wake up properly after a suspend.

Yeah :)

I had to experiment 2 Days ... but in the end i've managed to make it perfectly working.

Quick Guide:

removed su binary from

/system/bin

/system/sbin

/system/xbin

then moved, hiding and renamed su to:

/system/.root/t454r44r

an created a symlink to

/system/.sbin/su

Then added this new path to the PATH Variable in ramdisk and adjusted paths for the su daemon ...

Finally replaced unofficial "fingerprint" and "description" wit the stock one ... and voilá SafetyNet Passed :)

This is exactly the way how Magisk works .... so now we have native "hidden su" support.

It works even with SELinux in permissive mode. lol

I've also changed back /system from "rw" to "ro" .. but i can't say if this stock change is required to make SafetyNet pass.

Anyway it makes it more secure :)
[Galaxy Ace II Android Development] :
If you type this in command (without giving terminal su permission):

and there is no output, then the su is hiding properly.

Anything else shows the su is still shown.
[Galaxy Ace II Android Development] ace2nutzer:
It still can find it, but SafetyNet works .. so ... ;)
[Galaxy Ace II Android Development] :
Yeah, it's because you put the su in other place which SafetyNet does not check. :good:
[Galaxy Ace II Android Development] :
Confirmed SafetyNet working at 2018/08/13. :good:
[Galaxy Ace II Android Development] Fabbb2:
problem with the app Mi FIt

Hello, i have a problem with the app Mi Fit (to manage a smart band). It used to work properly but now it crashes when i try to open some parameters (not all). I tried to go back to a previous version of the ROM+Kernel but it is the same. It works normally on another phone.

Here is the logcat

08-16 16:11:49.155 E/AndroidRuntime(24233): Process: com.xiaomi.hm.health, PID: 24233

08-16 16:11:49.155 E/AndroidRuntime(24233): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.xiaomi.hm.health/com.xiaomi.hm.health.ui.smartplay.MiBandAlarmActivity}: java.lang.SecurityException: No permission to prevent power key: Neither user 10126 nor current process has android.permission.PREVENT_POWER_KEY.

08-16 16:11:49.155 E/AndroidRuntime(24233):	at com.xiaomi.hm.health.baseui.d.b.c(SystemBarTintManager.java:440)

08-16 16:11:49.155 E/AndroidRuntime(24233):	at com.xiaomi.hm.health.baseui.d.b.a(SystemBarTintManager.java:363)

08-16 16:11:49.155 E/AndroidRuntime(24233):	at com.xiaomi.hm.health.baseui.c.b.a(BaseTitleActivity.java:187)

08-16 16:11:49.155 E/AndroidRuntime(24233):	at com.xiaomi.hm.health.baseui.c.b.a(BaseTitleActivity.java:178)

08-16 16:11:49.155 E/AndroidRuntime(24233):	at com.xiaomi.hm.health.ui.smartplay.MiBandAlarmActivity.n(MiBandAlarmActivity.java:152)

08-16 16:11:49.155 E/AndroidRuntime(24233):	at com.xiaomi.hm.health.ui.smartplay.MiBandAlarmActivity.onCreate(MiBandAlarmActivity.java:102)

08-16 16:11:50.655 F/ProcessStats(1971): Starting service ServiceState{4302fdc8 com.xiaomi.mipush.sdk.MessageHandleService pkg=com.xiaomi.hm.health proc=4302fdc8} without owner

08-16 16:11:50.768 F/ProcessStats(1971): Starting service ServiceState{4310a9c0 com.xiaomi.mipush.sdk.PushMessageHandler pkg=com.xiaomi.hm.health proc=4310a9c0} without owner

08-16 16:11:50.805 F/ProcessStats(1971): Starting service ServiceState{4251d030 com.xiaomi.hm.health.device.service.HMCoreService pkg=com.xiaomi.hm.health proc=4251d030} without owner

08-16 16:12:00.632 E/WindowManager(1971): Starting window AppWindowToken{42f3e4c8 token=Token{42c036e0 ActivityRecord{42eb4778 u0 com.xiaomi.hm.health/.activity.MainTabActivity t46}}} timed out

Can i do somthing or is it related to ROM or Kernel ?

Thanks in advance
[Galaxy Ace II Android Development] ace2nutzer:
This ROM seems to be buggy. - I'll fix it ASAP.

If u're still on this CM11, can u pls post the full logcat after the app is force closing ?

It'll help to debug the ROM.

Anyway, in the meantime u can switch to the latest CM11 from Chronomonochrome (u can still flash A2N Kernel if u like it)

Actually i'm on stock 4.1.2, but "Mi Fit" isn't compatible with 4.1.2 ... I'm using it since 1 month (with A2N Kernel) and so far no random reboots nor force close apps! :good:
[Galaxy Ace II Android Development] lace_hvc:
I was about to install your latest ROM and kernel. I always perform a backup before doing so. This time the backup in recovery fails every time at around 80% of backing up data. I tried different sd cards and also ran chkdsk /f /r on them without any errors found. Free space is more than enough (9GB).

Im on Kernel 20180711 and CM11 ROM 20180601.

Any idea why the backup doesnt complete?
[Galaxy Ace II Android Development] ace2nutzer:
Maybe u've filesystem errors or broken files on /data.

Try to flash latest kernel, then reboot the system, and then finally try to create the cwm backup.

If it doesn't help, i suggest to lunch kmsg over ADB during the backup ... then u can see what happens when it fails.

If u can't fix yourself, post the log here.
[Galaxy Ace II Android Development] lace_hvc:
The backup completed after installing your latest kernel, but there were issues with some apps and root access cause of your chances regarding superuser. So I installed your newest ROM as well, even u say it's buggy. Works fine for me so far.

Thanks!
[Galaxy Ace II Android Development] ace2nutzer:
Root for apps & adb should work fine and SafetyNet should be green.

Which apps doesn't work anymore ?? - Probably only CM FileManager ? - Right ?

If so, this built-in app unfortunately expect the su binary in /system/xbin which i had to remove due of SafetyNet bypass.

But if u want u can still fix it (but breaks SafetyNet) by simply adding a symlink like this:

su
ln -s /system/.sbin/su /system/xbin/su

it'll survive a reboot ... and maybe even a rom update ... unless format /system is performed.

Actually i'm not sure if it's really ROM bug that cause random FC or maybe just a bug in ramdisk.

Maybe only "sdcard_only" kernel is affected, so normal version maybe works fine.

Anyway i'll do a full check of the ramdisk today...

kernel update next week ;)
[Galaxy Ace II Android Development] lace_hvc:
CM FileManager works, but it doesnt show system and root folders anymore.

Adaway (couldnt find su binary because of ur changes) and Wakelock Detector didnt work after installing the kernel, and 'superuser' didnt appear in settings. But after installing the latest ROM, these issues are fixed. All apps are working.

One new thing: Everytime before rebooting from recovery, it says that my phone is missing root access and requests to root my device. I choose 'yes' of course.
[Galaxy Ace II Android Development] ace2nutzer:
As i said in my previous post, u can fix it by creating a symlink for the su binary :o

(use ADB or terminal emulator app)

Yeah, the kernel removes all su related stuff in order to bypass SafetyNet, then the ROM installs proper su method.

Forgot to mention: cwm recovery is now outdated, and it'll show that message everytime ... even if u say "yes".

Anyway i've at least managed to update the su stuff on cwm ,... that means: if u mess it up with the root access then no need to install again the ROM, just reboot in cwm, say "yes" and root + SafetyNet is fixed again. :o
[Galaxy Ace II Android Development] :
This would break SafetyNet, of course.

If I modify these line in your kernel installer to not to flash the kernel (it will just flash the su to pass SafetyNet) then I would have a "SafetySU"? :D

Why not using TWRP? It's under heavy development and it have touchscreen support.
[Galaxy Ace II Android Development] ace2nutzer:
Nope, it'll just cleaning the /system, removing su binary:

# cleanup
ui_print("-- cleanup");
delete("/system/bin/su");
delete("/system/sbin/su");
delete("/system/xbin/su");

after that, no root, but safetyNet should pass.

(little guide .... experimental!!!)

then if u want to flash root:

u need the root binary in system/.root/ ..... (take from the rom package)

and an empty folder /system/.sbin/

both .root and .sbin folder with the dot before... so it's hidden.

Then continue with:

symlink("../.root/t46hf7h5", "/system/.sbin/su");
set_metadata("/system/.root/t46hf7h5", "uid", 0, "gid", 0, "mode", 06755, "capabilities", 0x0, "selabel", "u:object_r:su_exec:s0");

Now replace

ro.build.description
and
ro.build.fingerprint

with any from the stock build.prop (latest)

Now the implementation is of 99% complete.

The last thing u need is a change in ramdisk ... which is stored in the boot.img

U can try to unpack the boot.img with AIK-Linux, modify and repack it, but no warranty that it'll work at all... i've never tried it. (i'm using way different method which is too hard to explain here)

If it's not possible to modify the ramdisk, then u can try (also never tried) to modify it at runtime, so "on-the-fly"

with ADB:

so the command would be:

(run this immediately on a running system .. no root required! and note the output)

echo $PATH

let say the output looks like this:

/sbin:/xbin:/system/bin:/system/sbin:/system/xbin

then in rooted recovery:

add /system/.sbin to the PATH Variable:

su
export PATH=/sbin:/xbin:/system/bin:/system/sbin:/system/xbin[B]:/system/.sbin[/B]

Tip: add it to init.d scripts .. .then it'll update the PATH on every boot. (since it's not saved in ramdisk when using the "on-the-fly" method ;)

Now u should have working root and safetynet :) But as i said some of the mentioned steps are untested ... so u've to experiment yourself.

Yeah, but actually it's not urgent, as long we can do everything with cwm.
[Galaxy Ace II Android Development] informatico91:
installation problem

Hello. I tried twice to install this ROM but at the end of the procedure the phone remains locked on the power on screen (Samsung Galaxy Ace 2 GT-I8160). How is it possible? :(

One strange thing I noticed is that the installation of the ROM is really fast (about 10 seconds). It's normal?
[Galaxy Ace II Android Development] :
Check your download. And redownload the ROM again.
[Galaxy Ace II Android Development] Fabbb2:
You want the full logcat ? I posted only the Errors in the logcat in my previous message. I am now back to cm-11-20170522-UNOFFICIAL-FULL-codina but still the same.

I am going to try Chronomonochrome ROM (is it this one : CyanogenMod 11 - 30/07/2015 ?). Many apps need at least 4.4 to work...

Thanks
[Galaxy Ace II Android Development] ace2nutzer:
Yes :)

Yeah, that's possible that some bugs still persists since long time ago.

Yes :)

Please let me know if all apps works properly on that CM11 and especially "Mi Fit".
[Galaxy Ace II Android Development] Fabbb2:
Same problems with Mi FIt using that ROM...
[Galaxy Ace II Android Development] Fabbb2:
Another thing, with the latest ROM, i can not backup, it is stuck at data back up (i let it run the whole night)
[Galaxy Ace II Android Development] ace2nutzer:
Thanks for testing!

Did u try with all 3 kernels? - Namely: Chrono Kernel, a2n kernel, a2n kernel sdcard_only.

Please test and report.

Thanks for your Report! - Later i'll check it ... to see what's wrong.
[Galaxy Ace II Android Development] informatico91:
Thanks for the reply but after four attempts I managed to finish the procedure. Perhaps, but I'm not sure, in previous attempts I forgot to do "wipe data" in step 0.

In any case, all the difficulties for the installation have been repaid because this ROM is really good. It is fast both at start up and in use and does not consume a lot of battery.
[Galaxy Ace II Android Development] Fabbb2:
Bootloop with Chronokernel...
[Galaxy Ace II Android Development] ace2nutzer:
OK, then it's likely CM Bug. (or not CM compatible app).

Tested right now with both kernel variants and it works fine here.

It's likely that u've filesystem errors (or broken files, mostly media) on both /data or /storage/sdcard1.
[Galaxy Ace II Android Development] leonardalps:
hi guys i just installed this rom (latest version) and everything works fine except mobile network doesn't work. when i try to set an apn it does not allow me....pls help
[Galaxy Ace II Android Development] stefanoscheda:
Gapps FC

I reinstalled this ROM after trying Lineage 15.1 (too heavy) but com.google.process.gapps and Google Play Services FCs continuously. To stay safe I started back from stock 4.1.2 and I'm quite confident I followed all the installation steps so can't understand what could be wrong.

The package is the recent open_gapps-arm-4.4-pico-20180822.zip.

TIA
[Galaxy Ace II Android Development] ace2nutzer:
Later i'll upload new build with hopefully fixed FC issue :)
[Galaxy Ace II Android Development] gepel:
Hey, did you removed the root access on cm file explorer? I can't find it the option for it
[Galaxy Ace II Android Development] ace2nutzer:
New Builds are Up!

Changelog:

CM11 ROM 20180901:

Optimized Dalvik

build.prop tweaks

Fast boot

added ART Flags*

incl. A2N Kernel 20180901 - normal version

AUTO wipe cache and dalvik-cache

*= ART is still experimental in 4.4.4 ROMs and actually it's not compatible with open gapps.

Try to use different gapps if u want to test ART, also don't report bugs if u use ART, thanks.

Kernel 20180901:

Fixed Apps crash

MCDE: WS2401: improved stability

cpufreq: updated suspend_max_freq interface

Mali: driver update & fixed memory allocation failures

Tiny Kernel update & tweaks

A2N Kernel Control [GT-I8160] V4.8

reduced overhead on boot

A2N Kernel Control [GT-I8160] V4.7

GPU: removed mali_pre_allocated_mem_size_max - it's now 32MB by default

Screen: removed "Tuned Freq" & "Chuck Norris mode" - rebasing driver ....

Misc: added "Advanced Root" for CM11

Tiny Bug fixes

Enjoy :)
[Galaxy Ace II Android Development] :
It's really good for me to have ART...

But which Gapps I have to install to be compatible with ART?
[Galaxy Ace II Android Development] ace2nutzer:
Yes removed in order to bypass safetynet compatibility test.

In latest builds u can re-add su binary to /system/xbin with my App.

If u don't have the license, just write this to the terminal emulator:

su
mount -o remount,rw /system
ln -s /system/.sbin/su /system/xbin/su
mount -o remount,ro /system

if u don't need it anymore, revert back and safetynet will pass again:

mount -o remount,rw /system
rm /system/xbin/su
mount -o remount,ro /system

try with latest build. i've tested it on a clean install using latest open-gapps and it works perfectly now!

Please try latest CM11 here and let us know if Mifit works now :)

U can try with mardon's gapps :)

If they don't work too,(after the second reboot 6 Apps will again and again optimize and location service won't work at all, and google play services will crash) then search for different gapps.
[Galaxy Ace II Android Development] Fabbb2:
Same...

I've bought a new phone (same as you), so dont worry if it's just for me !
[Galaxy Ace II Android Development] Mac Oneil:
What is better f2fs or ext4?
[Galaxy Ace II Android Development] shaqman89:
You should try it yourself :D

Personally, I think f2fs is better in term of performance
[Galaxy Ace II Android Development] primewell:
I am trying ext4 20150112 kernel, upto now no problems @ OC 1 GHz... :good:

Stupid question: if I am currently on ext4 and want to switch to f2fs, is it sufficient to simply flash a f2fs kernel, or do I have to flash CM as f2fs completely from scratch?
[Galaxy Ace II Android Development] shaqman89:
Well, if done properly, you don't have to reinstall cm, just do a format for the partitions you want and everything should be okay. Before format you should do a backup and restore the backup after you format the partition.
[Galaxy Ace II Android Development] MarquesYOLO:
For the moment, 0115 build has the same smoothness that 1220 build, so the "problem" with 0106, 0107 and 0112 has gone. Thank you very much [MENTION=5840412]ace2nutzer[/MENTION] .

However, you say that we have 10 modules, but before flashing last build I saw that I had 11. It's all right?
[Galaxy Ace II Android Development] primewell:
I just flashed 15012015 and have the same... after first 60 minutes, great kernel - no issues. And just stepped up OC from @1 GHz to @1,1 GHz - all stable :D

EDIT: Also here 2 random reboots @1,1 GHz, back to 1 Ghz, but still running like hell!:good::good::fingers-crossed:
[Galaxy Ace II Android Development] bebolint98:
[MENTION=5840412]ace2nutzer[/MENTION], in the last kernel which is the best highest GPU frequency?
[Galaxy Ace II Android Development] ace2nutzer:
Yeah it's right.. same CPU / Gov. logic like 1220 .. it's till now still the best.. i'm also pretty satisfied :o

I don't see 11 Modules.. Modules are .ko ;)

btw: what about Blackscreen issue ?? It's gone in latest build ???

haha... thanks ! That was just wondering me.. if it's stable @ 1,1Ghz.. because i don't change anything in CPU Table... but now it think it's time for the stability Guys :D - I'll beginn to fix the stability. :)

Nobody know how good is Your GPU Quality... i've here 2 ace2.. devices.. on the 1. ace2: 690Mhz .. and on the second ace2: 770Mhz ;) so u need to test it ....
[Galaxy Ace II Android Development] Tree4ever:
ace 2 nutzer 20150115-Kernel

I hope the procedure for the 20150115 kernel is the same as for 20150112 (from your cm 11 20141118 with kernel 20150107,full f2fs):under /system/lib/modules/ have been 11 entries,but 10 with *.ko.Now to delete 3 of them:usbmon.ko,usb-storage.ko and cdc-acm.ko.After particular deleting Total Commander wanted to mount,I choose yes(a kind of saving entry?).Then boot into cwm and flashing your 20150115-Kernel.So far everything works fine,the current frequencies are 800/600/400/Deep Sleep.:good:
[Galaxy Ace II Android Development] ace2nutzer:
Everything correct ! The System Partition is always in Read-only mode mounted.. .. to delete files it's needed to re-mount in read-write mode.. but if u using the stock FileManager.. .. when u try to edit some files or deleting files in system part. then this app do it all automatically.. (the remount things) this is why i can't understand why we have here still users that can't edit the system partition.. it's not complicated-- just activate root access in FileManager and grant Root rights.. then it works for ever very well. it's not needed to use 3.rd-party apps for fileManager ... But of course it's your decision :);)
[Galaxy Ace II Android Development] VW22:
[MENTION=5840412]ace2nutzer[/MENTION]

in the 01optimization file.. just add an "#" before the echo command.. like this:
Code:
# Set custom Minfree Values (Memory Management for Multitasking)

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

After flashing the 15012015 kernel I did add the # in the code of that file, rebooted the phone, but still no succes.

The camera stops working as soon as the camera app is launched.
[Galaxy Ace II Android Development] shaqman89:
Hey, could it be that your storage is full? I had that issue once and the cause for me was the SD card is full