yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] :
Do that mean you will start build other for this phone soon? :victory:

But then how can people with damaged HW key can use your app ? :eek:
[Galaxy Ace II Android Development] ace2nutzer:
Yeah :D

It's very unlikely that it will get broken, btw it's touch-soft-key not HW key.

In a case that at least 10 users have problems with the Soft-keys i would re-add that feature. :o
[Galaxy Ace II Android Development] lace_hvc:
Im getting reboots with the last 2 kernel. Mostly happens when SIM and mobile data is on after a phone call. Suddenly I see my phone asking for SIM PIN. This, and the information in betterbatterystats, tells me it rebooted.

I set RAM compression to 0 and 100. reboots on both.
[Galaxy Ace II Android Development] ace2nutzer:
without last_kmsg i can't do much.

[MENTION=6710464]lace_hvc[/MENTION]

if the random reboot happened on the previous session, then u can still open my app go to debug menu and press "last_kmsg", logs will be saved on the sdcard0.
[Galaxy Ace II Android Development] joslanqq:
First of all, thanks for your work.

My main mobile phone in water (ups!)...........return to ace2 (good)..........clean install with repartition (sd only) last rom, kernel (sd only) and gapps, but....

I can not Introduce the google account........searching thread and.....the same word by word as our pal 'divinesurfer' in his message #8603.

I have tried different gapps, but nothing. Any idea?
[Galaxy Ace II Android Development] :
I got the same. But I noticed that in phone setup, the google account login page shown up and then crashes itself. After that it won't work anymore :confused:
[Galaxy Ace II Android Development] ace2nutzer:
it works for me ... if u want i can upload the opengapps package i'm using.

Edit: [MENTION=5285498]divinesurfer[/MENTION] [MENTION=7935481]joslanqq[/MENTION]

uploaded tested and working gapps package here:

http://xda.mister-freeze.eu/XDA-files/ace2nutzer/GT-I8160/Android_4.4.4/Misc/
[Galaxy Ace II Android Development] UnknØwn:
Solved!
[Galaxy Ace II Android Development] fonzacus:
having a test drive just before the 1023 build

kind of having issues with older apps using safetynet ok root. which build was the latest non safetynet root?
[Galaxy Ace II Android Development] ace2nutzer:
u've to flash latest cm11 and a2n Kernel.

then in my app enable "Advanced root".

note: this ROM is not optimized to work well with chrono kernel.

root works properly for me .. on both cm11 and stock jb 4.1.2.
[Galaxy Ace II Android Development] lace_hvc:
It rebooted again after an attempted phone call. almost every time after calling someone, the phone reboots.

I added a last_kmsg. Quite a bit file. 1MB. So I had to zip it. Hope its useful for you.
[Galaxy Ace II Android Development] ace2nutzer:
There's nothing wrong ... it's just a dirty reboot caused by the battery driver.

That means battery was too weak.

Try when it's fully charged .. i bet it'll not reboot.

U can Fix it by replacing the battery :cowboy:

Reference according to your log:

# Battery Level 17% .. Voltage 3,657 V ....
healthd: battery l=17 v=3657 t=22.0 h=2 st=3 c=-240 chg=

# starting a call (requires much power)
[ABB-Codec] EarDigGain widget

# Battery voltage dropped below the threshold .. which is the minimum
ab8500-fg ab8500-fg.0: Battery voltage is below LOW threshold
ab8500-fg ab8500-fg.0: Battery voltage OK again
ab8500-fg ab8500-fg.0: Battery voltage is below LOW threshold

# Low Threshold is 3,300 V

https://github.com/TeamCanjica/Sams...ch/arm/mach-ux500/board-codina-battery.c#L483

When Voltage drops below 3,3V the Phone will shutdown. But if the battery is too old reboot is possible.

I'm actually updating the Charger/Battery Driver ... so maybe it can help a bit, but of course it can't fix a broken battery. Later i'll upload.
[Galaxy Ace II Android Development] lace_hvc:
Thanks. It's still the original battery from 2012 :D

It still lasts for days or 3h screen on time, but I know it's time to replace the battery.

Today, I got another reboot after turning on airplane mode. The battery had roughly 60% left. So it's because of the voltage?

I attached another last_kmsg.
[Galaxy Ace II Android Development] ace2nutzer:
Yeah .. same here ... mine is also still OK. At least it's stable even on 1% battery !

Before u replace it, i suggest to try with the coming kernel update. ;)

Check at the end of the log ... this is what happened just before it rebooted:

ab8500-fg ab8500-fg.0: Battery voltage is below LOW threshold

Yes, that's due to too low Voltage drop on load.

But wait for update, i've fixed many bugs in charger and battery driver.

Also it'll charge faster and lasts more time.
[Galaxy Ace II Android Development] makreitor:
Hi, After installing the last ROM and Kernel, I am having the Gapps problems mencioned a few messages ago for some user. I've tried the last gapps and the one you are using and could not managed even to log in bcz it crashed. Then, tried an older version I had and could log in my google account, but then it starts to pop up a lot of messages form gapps, services or google play stoping process. After a while sometimes WIFI conection disapears and wont be able to conect again. Also have had soft reboots after trying to install or uninstall some apps from apk. I have atached the debug files from your app in chase they can help. The installation was clean (including format and wiping cache and dalvik). What can be the issue?

Thanks in advance and for this great ROM.
[Galaxy Ace II Android Development] ace2nutzer:
Hi!

This ROM is now outdated .. and the gapps-core package support is quite poor as well.

That's why Google Play Services crashed all the time.

It works stable only with certain older gapps ... for me the package i've uploaded to the FTP works stable.

As for the Random Reboot ... i'm not sure but it seems that PLLDDR OC wasn't successful for your Phone.

Maybe [MENTION=5695278]ChronoMonochrome[/MENTION] can give us more informations what went wrong? (see last_kmsg)

PLLDDR OC @ 1 GHz.

Anyway, in the meantime can u try if it's stable without PLLDDR ? Also don't undervolt or OC CPU/GPU manually. Just use one of the 3 Performance Profile... Using "performance" profile is recommended as it gives good performance and still good battery lifetime.

Personally i'm using performance + PLLDDR OC .. and gives good performance and battery lifetime.

btw: for me it works quite stable the PLLDDR OC @ 1 GHz.
[Galaxy Ace II Android Development] ChronoMonochrome:
Looks like so. Despite of all attempts to fix it, it's still not fully stable. Probably there are no chances to change PLLDDR registers fully safely from the kernel (only bootloader can safely set some initial values).
[Galaxy Ace II Android Development] :
This is why I do not like 4.4.4 except it's performance.

Edit: One more reason is that WiFi Direct is not working at all...

Because this I can't use my device for wifi repeater...

Yes the Gapps in FTP work fine... but I do not use it much.

Undervolt lvl1 + PLLDDR OC @ 1.1 GHz is stable for me. :good:

Thanks for this damn stable kernel :silly:
[Galaxy Ace II Android Development] ace2nutzer:
FINAL Kernel Update !!

Changelog:

Kernel 20181105:

Charger: updated the whole Driver. - Relaxed a lot of limits to be able to charge up to 1500 mA Current for any Chargers AC/USB. - Added better support for 3.7 V (optimized for 1700 mA) 3rd-party batteries. - Better Support for very old Batteries from 2012 - 2013. - Refresh and recover some lost Battery power and update the Battery Gauge to Stock. - Driver Clean up .. removed useless sysfs interfaces and added new interface for checking actual real current drawn from the power source.

- fixed also occasionally wakelock issues after unplugging charger cable (battery drain fix).

USB Gadgets power: set in kernel proper max drawn current to 300 mA

Charger: enable BLN on eoc_real instead of eoc_first if suspended (if enabled in the App or over init.d script)

MCDE / LCD: tiny stability fix for s6d27a1

A2N Kernel Control [GT-I8160] V5.2

Power: Added Check (real) input Current Button

Layout update

Flash and enjoy your Ace 2 properly ;)
[Galaxy Ace II Android Development] ace2nutzer:
[MENTION=7536125]lv-xda[/MENTION]

go to CM settings --> SuperSU and enable root access for Apps.

If u can't see it in Settings, then go to Developer options and set it from there.

Then u need to reboot the Phone.

Then Finally in A2N App disable advanced root and re-enable it again.

Now open File Manager and it should show Root Options like before.
[Galaxy Ace II Android Development] lv-xda:
Root Access (apps and usb debugging) is/was already enabled in SU. So, strictly following your instructions, i:

1. enabled it only for apps

2. rebooted the phone

3. disabled A2N advanced root

4. rebooted the phone

5. enabled A2N advanced root

6. rebooted the phone.

NO, it didn't help.
[Galaxy Ace II Android Development] ace2nutzer:
How did u flash the update?

First ROM and then kernel is right.

Hmm try to flash latest kernel again ... and then repeat above steps, btw. reboot is only required after enabling root in SuperSU settings.

If it still doesn't help to fix root then flash ROM and then kernel in a row.. and repeat finally the steps for enabling root.

U Could also test what happens when u try to call the su binary in terminal emulator app with "su"
[Galaxy Ace II Android Development] lv-xda:
Hmm, pretty sure i flashed the ROM first and then kernel, but i'll try again.

su in terminal emulator gives 255:

user@codina:/ $ su
255|user@codina:/ $
user@codina:/ $ which su
/system/bin/su
[Galaxy Ace II Android Development] lv-xda:
Well, after reflashing ROM and then kernel, just before reboot, phone asked to root the phone, because root was absent. And here we go: SU kind of works now

(at least for some apps, like Spirit UL, Titanium Backup), BUT it doesn't work for CMFileManager (i can't even see a menu option for choosing safe/root access)... :(
[Galaxy Ace II Android Development] ace2nutzer:
It usually not needed to fix ROOT with CWM .. because it'll do exactly the same what the kernel updater-script would do.

I know that because i've programmed it that way.

Well, now basic root works, now u need to re-enable Advanced Root in the App.. then File Manager will work properly.

Note: after re-enabling the advanced root, no need to reboot ... instead simply press home button and clear all the recent apps.

Now open File Manager and it'll run in Root Mode.
[Galaxy Ace II Android Development] lv-xda:
Hmmm, nope, it did not work :(

Enabling it, re-enabling it, re-enabling SU with reboot and then re-enabling advanced root in A2N...

And what's strange: CFM menu option for choosing root/safe/ask access is gone...
[Galaxy Ace II Android Development] ace2nutzer:
That's strange :(

it should work.

Note: every time u flash kernel or u say YES for ROOT in recovery then Advanced Root is lost again... even if it's still checked in the app.

But re-enabling will fix it.

Other that that, did u modify something?

If it's not that painful u can also try a clean install ...

Or at least did u tried to format /system before u flash the rom ???

Maybe /system partition is too full.
[Galaxy Ace II Android Development] lv-xda:
I see; i'll try to reflash kernel without cwm reroot'ing. I'm sure, that i haven't modified anything; it was pretty straightforward update process as usual: grab latest rom & kernel and reflash.

/system has ~130 MB free. I'll try to format it. Maybe just CFM settings got screwed up (because SU works for other apps and in CFM i can't even try root access, because that menu option is missing, though it was there just an hour ago :))?
[Galaxy Ace II Android Development] ace2nutzer:
I've checked again carefully the ROM, kernel and recovery for the Root stuff.

/system/bin/su

is completely wrong .. it shouldn't be there.. but instead in /system/.sbin/su because all installers from me will deleted the su in that location .. in order to bypass safetynet ....

Check, this is what all installers from latest rom, kernel and recovery will do .... (yes also when u perform rooting over CWM saying YES)

#cleanup
rm /system/bin/su
rm /system/sbin/su
rm /system/xbin/su

cp /sbin/t46hf7h5 /system/.root
chmod 6755 /system/.root/t46hf7h5
ln -sf /system/.root/t46hf7h5 /system/.sbin/su

As u can see, root is then only in /system/.sbin/su as a symlink.

Now basic root is there and safetyNet is OK.

But CM File Manager expect to have su in /system/xbin/

So when u enable advanced root in my App the it'll do the following:

# remount /system rw
mount -o remount,rw /system

# add root to /system/xbin
ln -s /system/.sbin/su /system/xbin/su

# remount /system ro
mount -o remount,ro /system

Now we've su in /system/xbin/ as a symlink ...

CM File Manager works now in Root mode ... but SafetyNet will not pass anymore.

To Pass SafetyNet again, just disable "Advanced Root" no reboot needed... but CM File Manager will run again without Root mode.

Anyway during checking everything i found one small issue ... so maybe that's also one cause why it didn't work properly. So once u did all steps, and CM File Manager is still not running in Root Mode (don't forget to remove it from recent Apps before u open it) then open terminal emulator or use ADB and type this:

adb shell #for adb over the computer or directly in term. emul. app:
su
export PATH /sbin:/system/bin:/system/.sbin:/system/xbin

That's right, but it was:

export PATH /sbin:/system/bin:/system/xbin:/system/.sbin

So maybe this was forcing to use the su in /system/.sbin instead to use the su in /system/xbin. :o

U get it? :cowboy:
[Galaxy Ace II Android Development] lv-xda:
Well, somehow it was there (maybe from and old ROM/kernel or even some SuperSU app installation; can't remeber what i was doing with my phone year ago...). Strange, that it wasn't deleted by you kernel

installation script. After second reflashing it's gone. Now everything is as it should be (and you wrote), except that /system/xbin/su

is missing

. Somehow A2N advanced root fails to create symlink; here is relevant logcat messages:

W/System.err(24031): java.io.IOException: Error running exec(). Command: [-c, echo Demo Version of A2N Kernel Control APK] Working Directory: null Environment: null
W/System.err(24031): at java.lang.ProcessManager.exec(Unknown Source)
W/System.err(24031): at java.lang.Runtime.exec(Unknown Source)
W/System.err(24031): at java.lang.Runtime.exec(Unknown Source)
W/System.err(24031): at com.ace2nutzer.settings.device.demo.fragments.n.run(Unknown Source)
W/System.err(24031): at java.lang.Thread.run(Unknown Source)
W/System.err(24031): Caused by: java.io.IOException: No such file or directory
W/System.err(24031): at java.lang.ProcessManager.exec(Native Method)
W/System.err(24031): ... 5 more

Here is some info:

root@codina:/ # ls -l /system/xbin/su
/system/xbin/su: No such file or directory

root@codina:/ # which su
/system/.sbin/su

root@codina:/ # ls -l /system/.sbin/su
lrwxrwxrwx root root 2018-11-13 17:21 su -> /system/.root/t46hf7h5

root@codina:/ # ls -l /system/.root/t46hf7h5
-rwsr-sr-x root root 443232 2018-11-13 17:21 t46hf7h5

If i create /system/xbin/su symlink manually from adb shell (suppose also in terminal emulator):

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

root@codina:/ # which su
/system/xbin/su

it works, and CFM gets root access. Bingo! :)

Seems like now you/i should investigate why A2N advanced root fails...

---------- Post added at 09:19 PM ---------- Previous post was at 09:05 PM ----------

Maybe it doesn't work just because it's a demo (not a purchased version)?
[Galaxy Ace II Android Development] ace2nutzer:
Yes, in demo version only the "debug" menu works.

All the other menus are "read-only". ;)
[Galaxy Ace II Android Development] lv-xda:
Mea culpa. Some older A2N versions were with a limited functionality and now i just didn't notice, that nothing really works...

Anyway, doesn't A2N (default ROM/kernel upgrade) break root in some kind of sense? If it's a demo after upgrading one cannot get root access in CFM and doesn't know why, and the only user friendly possibility is to purchase A2N... :) Not that it's a problem, but user should know why root is not working. At least advanced root should be enabled by default, don't you think so?

Anyway, big thanks for your work and help.
[Galaxy Ace II Android Development] ace2nutzer:
Nope, i had never released a demo Version with half of the features working.

So i don't know what u mean ...

On a full Version everything works properly.

Yes and No :o

Root works, it's just for CM File Manager. Also enabling it by default breaks SafetyNet Compatibility ... and that's even more painful. :highfive:

But you are right! - Enabling Advanced Root should be "free" .. so i'll put that switch in the Debug Menu in next Update.

:good:
[Galaxy Ace II Android Development] lv-xda:
I'd say it should be in SuperSU menu... :)
[Galaxy Ace II Android Development] ace2nutzer:
New Build is Up !!

Changelog:

Kernel 20181117:

Charger: updated charger logic - set ac current max @ 700 mA by default,

- improved security aka SIOP, - driver cleanup

A2N Kernel Control [GT-I8160] V5.3

Power: updated Charger Control

------------------------------------------------------------------------------------------------------------------

Version Info:

Charger Control is now a bit different ...

Usage:

# Set max AC/USB charge Current

# Plug the Cable

# Done

Optional

# How to charge as fast as possible aka "Fast Charging"

# increase the Charge current in small steps

# check stable current ... if it didn't decrease .. then unplug the cable, set higher current and check again

# Find out what's the max stable current ....

# Reduce it by -100 mA (to be safe, to keep care of the power source)

# Set it

Optional #2 for the lazy people lol (not recommended)

# Set highest Current

# Plug the Cable

# The Driver will adapt down automatically to an stable current ...

# Check stable Current

# Done

Last one isn't recommended because the resulted Charge Current will be lower than the method if u tune it step by step (+100 mA),

on the other hand, because of the lower charge Current, it's safer.

Once again, don't charge with the max stable current, as i said before subtract 100 mA (or even 200 mA) to be safe.

Also check the Battery Temperature (up to 37° C is OK) from time to time when charging with higher Currents than the defaults.

Usually nothing can happen ... there are a lot of security checks.. of course also for too high temps .. but better to be safe ... ;)
[Galaxy Ace II Android Development] lace_hvc:
I still get reboots. According to last_kmsg it doesnt seem to be the battery now. I replaced my battery with a battery from a Galaxy S3 Mini. Only to test. Then i set this RAM compression back to 100% cause of heavy apps like google maps.

Im on latest ROM and kernel.

Btw I cant access the kernel app when Im only connected to mobile data. It only works on wifi. So I can create a last_kmsg once Im back home.

Another problem I came across. I use an FM Transmitter in my car with a usb port for charging. I can charge every phone with it except this one and that S3 Mini. Any idea why?

Thanks!
[Galaxy Ace II Android Development] ace2nutzer:
Yeah Battery is fine now.

But now i see PRCMU issue.

I've enabled some tracing to the failing function.

Later i'll upload an update.

Oh, i'll check it! - Of course it should work as well with mobile data.

As an workaround: u can use the demo version to create the Logs ... since the "Debug" Menu works normally.

Only the other menus are "read-only".

On the coming update u can open the A2N App (works even on demo) and check the "stable Current" on the "Power" menu, it should show u how much mA it draws from the power source. So it'll be in the Version 5.4.

In a case it shows "0", then re-connect the cable and wait 15 - 30 seconds.
[Galaxy Ace II Android Development] lace_hvc:
Thanks for the support!

I also saw a 2.5h wakelock called low_bat_wakelock. Whats the point of that? Seems counterproductive :D
[Galaxy Ace II Android Development] ace2nutzer:
No, it's not counterproductive. :)

The wakelock on low_bat voltage is required so that it can perform a clean shutdown instead a hard_poweroff by prcmu when the phone is in deep sleep. Means also it prevents data loss by a dirty shutdown. ;)

But 2.5h seems to be too much.

I've reduced it now. :)

Edit:

uploaded new Kernel and App !
[Galaxy Ace II Android Development] ace2nutzer:
btw i had forgot to unlock "Adcanced Root" from the Demo Version.

Appended in this Post ----> Demo V5.6.

Changelog:

- skipped V5.5

- moved and unlocked "Advanced Root" from "misc" to "Debug"

- added missing permissions

// off-topic

released a2n kernel for samsung galaxy s8 :D

kernel for s8+ soon available.
[Galaxy Ace II Android Development] lace_hvc:
I had 2 more reboots but accidentally overwrote the first last_kmsg with the newer one.

Many battery related issues: "Battery voltage is below LOW threshold. Battery voltage OK again."

I dont know if that was the cause of the reboot or PRCMU because there are so many PRCMU entries.

I really need to replace the battery, but its not really worth it for such an old phone.
[Galaxy Ace II Android Development] ace2nutzer:
Is it possible to upload it as .zip ? Because i can't unpack .rar here on Linux OS.
[Galaxy Ace II Android Development] lace_hvc:
Here you go
[Galaxy Ace II Android Development] ace2nutzer:
Seems very likely that it's related to the very old/broken Battery.

In your latest Log u've quite a lot of such messages:

ab8500-fg ab8500-fg.0: [B]Battery voltage is below LOW threshold[/B]

which means the battery is broken when u see such messages on Batt levels > 5%.

because low threshold is = 3300 mV which means Batt Level = 0%.

PRCMU can't work stable if the battery voltage is < 3300 mV ..

that's why u see this:

Returning from ApDeepSleep. PRCMU ret: 0x31 - [B]Fail![/B]

and the Phone do a reboot.

As reference i've checked my Log after discharging my battery down to 4% .. and i don't have such messages.
[Galaxy Ace II Android Development] lace_hvc:
The problem is I also face reboots with a better battery.

Today I had 2 reboots within a few hours.
[Galaxy Ace II Android Development] ace2nutzer:
Right, now it seems to be related to the memory management and / or zRam driver.

Since i don't use zRam, i never faced such reboots.

I've only occasionally reboots caused by filesystem errors on /data caused by corrupted eMMc Flash drive.

No way to fix it, since it's Hardware issue in my case.

Anyway, in your case there's some chances to fix it.

I've uploaded new Kernel .. See Changelog in Post #2.

Try if it'll fix reboots, if not, try as well if it's fixed if u simply disable zRam and report here.
[Galaxy Ace II Android Development] lace_hvc:
I turned off zram and installed the kernel. Next reboot though.

Maybe I have a similar hardware issue as you.
[Galaxy Ace II Android Development] ace2nutzer:
This time the problem isn't catched at all.

Try again on next random reboot.