yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] ace2nutzer:
New Builds are Up !!

Kernel 20171031:

BLN: Allow separate on/off delay to be configurable (over the App)

Sweep2Wake: Tiny Update

MCDE: Some Optimizations (more smooth)

Userramdisk: move from p9 to p17 Partition (more space)

Abb-charger: Split AC/USB Charge Current for userspace

Higher Kernel Security

Increased Userspace VM from 912 MB to 2960 MB

Inkl. A2N Kernel Control [GT-I8160] Demo V3.0

A2N Kernel Control [GT-I8160] V3.0

Misc: BLN: added on/off delay control

Profile: Optimized the switch behaviour

Screen: removed s2w wakelock button (enabled by default if s2w is enabled)

Power: Charger Control: Split AC/USB Charge Current

CM11 ROM 20171031:

Fixed memory allocation failure

Fixed all Apps & GPS Issues

Enabled all powersaving features for GPS

incl. A2N Kernel 20171031 - normal version

Inkl. A2N Kernel Control [GT-I8160] Demo V3.0

AUTO wipes, except factory reset

Version Info:

Uploaded also new reparted scripts (not mandatory to update it if u're running the previous version)

Uploaded also new ODIN Kernel

CM11 ROM is still compiling ... it'll be online in around 2 - 3 Hours !

Enjoy ;)
[Galaxy Ace II Android Development] Yønn:
After a few minutes of usage with latest ROM & Kernel, everything seems to work like a charm. :victory: I will do further tests tomorrow with Waze.

Thanks a lot [MENTION=5840412]ace2nutzer[/MENTION] for these updates!
[Galaxy Ace II Android Development] Sidebandit:
Tested new version. Did not GPS as a don't use this or location tracking. Performance. Tested again on Epic Citadel & managed to run it on default settings of 800mhz & GPU 400! Amazingly smooth. Well done, never thought Epic would ever run on default.
[Galaxy Ace II Android Development] Yønn:
I made a few drives with Waze, except a broken GPS issue the very first time I used it (fixed by rebooting), it is working fine for the moment.

Maybe an additional reboot was needed to work properly after ROM installation...

I use Link2sd (with some apps installed on my external SD card). So to perform a ROM update, I have to do the following (it might help some others) :

- save Nova settings

- reboot to recovery

- install ROM update (and others needed zip files)

- reboot a first time (dalvik cache is initialized only for internal storage apps)

- once reboot (1) is done, I get a warning from Link2sd telling me to create again mounting scripts and reboot

- I create again mounting scritps and reboot a second time (dalvik cache is initialized for external storage apps)

- once reboot (2) is done, I have to restore Nova settings to get all my apps icons back

Maybe a third reboot is needed to get everything working properly, I have to check.

Anyway, I am happy my phone is again fully functional! :victory:
[Galaxy Ace II Android Development] ace2nutzer:
@ up

Link2sd is not needed with sdcard_only Version! U can safely use native Solution from the ROM.

And u even don't need to create a second partition with ext4 ! Just use one Partition as vfat, is enough.
[Galaxy Ace II Android Development] AkosPaha:
[MENTION=5840412]ace2nutzer[/MENTION]!!

Please help me !!!! The phone was upgraded but the "end of system boot" did not go on !! Now it is not turned off, Odin mode is there, recovery with button are not working !!, offline charging works! Something you can ???:confused::(
[Galaxy Ace II Android Development] AkosPaha:
Fixed all problems!!!:victory: Recovery is there, but there are two stripes, what can you do with it? sometimes there are, sometimes there are no two stripes!

Looks at the photo!
[Galaxy Ace II Android Development] ace2nutzer:
Lcd issue.

Lcd Typ ?
[Galaxy Ace II Android Development] AkosPaha:
Typ:WS2401

Edit:Could somehow improve this, until now, there were no lines, only now they appeared?:confused:

To update is much better performance than it was before, bigger apps are going smoothly on the phone! Just so if the updates are so good then everyone is happy.
[Galaxy Ace II Android Development] jschomchoey:
Can't connect to computer.

In the last ROM(20171031) I can't connect to my computer. Please fix it. Thank you. :D:D
[Galaxy Ace II Android Development] ace2nutzer:
Ok, anyway i've updated MCDE Driver, so it should reduce such lines in recovery (or fix them completely) in next build.

btw: is Real Racing 3 working smooth for u with the default settings and just using Performance Profile + zRam ?

In my case since they updated the App, it's running very bad ... it lags like hell.
[Galaxy Ace II Android Development] Yønn:
Hi there,

I have still to report some GPS broken issues. Here are a logcat and dmesg log files. I have tried to wipe /data/gps directory but no success.
[Galaxy Ace II Android Development] AkosPaha:
The 2 lines on the display are fixed and I want to check if it really works. The overall performance is better than it was, but the phone hangs several times! The games are pretty good at the performance, RR3 Factory Graphics works for me well, it does not lags , it goes very smoothly!:victory:

CPU 1200mhz + GPU 650mhz + zram!:)

Thanks for this good update!:highfive:
[Galaxy Ace II Android Development] ace2nutzer:
Hi, it's still the same issue... are u sure u're using latest ROM & kernel?

It's fixed for me.
[Galaxy Ace II Android Development] Yønn:
Yes. ROM 20171031 and Kernel 20171031, zram activated.

Should I try to Wipe Cache and Dalvik or anything else?
[Galaxy Ace II Android Development] ace2nutzer:
Ok, if u didn't modified the ROM package then it's not needed to wipe dalvik cache, because the installer do this automatically, otherwise if it didn't happened for some reason, then do it.

Otherwise it's possible that it's another different issue.. that should be fixed (hopefully) in next Kernel Release ;)
[Galaxy Ace II Android Development] Yønn:
I didn't modified anything, so I hope it's related to the potential issue you mentioned, and not to hardware issue.

I will wipe cache & Dalvik just in case, and then wait for next release.

Thanks for your feedback.
[Galaxy Ace II Android Development] ace2nutzer:
No Problem. It's for sure not an Hardware issue according to the Logs.

btw: Wipe cache isn't needed. (cache partition is only used by recovery to store logs)
[Galaxy Ace II Android Development] :
The problem with the screen is now disappear... Thanks for this great build!

Let's see how much performance is there in this build..
[Galaxy Ace II Android Development] xEmre66:
Can anyone give me the NovaThor Settings apk? I searched everywhere but couldn't find anything. Dev-Host also doesn't work...
[Galaxy Ace II Android Development] AkosPaha:
Use the A2N kernel control from Play Store!
[Galaxy Ace II Android Development] Sidebandit:
Not sure what mileage you'd get from NovaThor app over A2N app. Development on Thor app ceased sometime back. I used NT app on my Galaxy S3 mini with mixed results. Lollipop kernel with NT app settings surpport but it wouldn't boot the app. I had to create a init.d script for it to work. The only thing I'd like to see on A2N app is graphic memory setting added like on chrono kernel control app. This may help with more demanding games.
[Galaxy Ace II Android Development] ace2nutzer:
AFAIK it's not possible to change it on userspace. It's hardcoded in sources & cmdline. It's already good configured by default.
[Galaxy Ace II Android Development] lace_hvc:
On latest ROM & kernel, line app is always staying in RAM together with InAppBillingService from Google Play Store and SafetyNetClientService from Google Play Service. Its not even cached. Constantly requiring around 90 MB of RAM. After removing line from recently opened apps, it still stays in RAM (see attachment 1).

I have had this issue with Contacts/Android Core Apps after opening contacts or phone app. It kept being in RAM along with the usual Google Play Services until I did a reboot (see attachment 2).

Anything I can provide to give you more information regarding this issue?

I will roll back to an older ROM to make sure it doesnt happen there, but I never noticed that issue on older versions.
[Galaxy Ace II Android Development] ace2nutzer:
It's usually not an issue. It depends on how the app is programmed, looks like it has an auto-start receiver (re-start) behaviour, which almost all android apps have.
[Galaxy Ace II Android Development] lace_hvc:
Line update was just released. Installed it and at the same time Google play services updated. Problem hasn't appeared so far :)

But these Google play services are annoying. They require 60-70MB of RAM if you don't disable any services. After disabling, I had 1 process with 2 services (gcm and Lockscreen) running with only 16MB average. In this update, they split this into 2 processes with 1 service each running together at over 30MB. Then there is this measurement service running with over 30MB but I have disabled this one and a few more for months, saving me some RAM and not causing any problems.
[Galaxy Ace II Android Development] ace2nutzer:
i've never heard about this App "Line" .. but as i can see it's like WhatzApp, so it's normal that it'll stay all the time in RAM, otherwise it can't work properly.. (like WhatzApp).

btw u really don't need to take care about running Apps and Services in the Background. It's right that they eats some RAM.. but first: there's almost a reason why they stay in RAM (for proper functionality) and second: if u launch an App that needs the full amount of RAM on the Device, then the low-memory-killer will kill almost everything that'll so far not cause any system crash or that makes the system unstable....

That's what the LMK kills:

- User/system Apps & Services.

So really no need to mess it up :)

If u've still some Doubts, post your Problem to the "Line" Development Thread (if there's any)
[Galaxy Ace II Android Development] lace_hvc:
Its all fine now. the update of line or google play solved it. line is not permanently in RAM together with 2 other services. Its appearing in cached processes as it should be and did so for several years. Probably a coincidence that this happened after updating ROM and kernel.

Line is used by roughly a billion users, mostly in Asia. Its a much better alternative to that crap called whatsapp.
[Galaxy Ace II Android Development] ace2nutzer:
How it goes with the GPS broken issue? Still the same?
[Galaxy Ace II Android Development] Yønn:
Yes, still issues but I realized it only happens using Waze after about 5 minutes. GPS status seems to work OK.
[Galaxy Ace II Android Development] ace2nutzer:
New Build is Up!

Kernel 20171110:

MCDE: added fail-safe config for WS2401 for Recovery & LPM

Added latest STE Codina Patch

Audio: enabled config SND_SOC_UX500_AB8500_MID_WIDGET - Thanks to the STE Patch

Enabled config UX500_SUSPEND_DBG_WAKE_ON_UART - should fix BT Audio on Suspend

zRam: Sources Sync 3.10.0 --> 3.10.103

Sweep2Wake: enabled by default if it's charging - both AC/USB (also on LPM)

Improved Performance & Battery Life Time

Compiled with Linaro 4.9.4

Inkl. A2N Kernel Control [GT-I8160] Demo V3.0

Version Information:

Just flash it without any wipes.
[Galaxy Ace II Android Development] Sidebandit:
Storage space issue back from a few builds back. "Insufficient storage space" install apps error. Rolled back to previous kernel.
[Galaxy Ace II Android Development] :
I have tested this version just now and I found this problem: The problem with black screen comes back. Previous version is really perfect. But I am not sure about it.

Why not to add to updater-script a code to ignore installation of A2N Kernel Control [Demo] when paid version is already installed?

This code should be like this:

if [-f "/data/app/ com.ace2nutzer.settings.device-1.apk"] then echo Paid version already installed. Ignoring install Demo version...
else (I forgot how to do here :))
[Galaxy Ace II Android Development] lace_hvc:
You can simply remove the demo file from the zip before installing it. That's how I do it.
[Galaxy Ace II Android Development] ace2nutzer:
oops :o accidentally reverted this fix. It's again fixed on next build :cowboy:

Didn't touch LCD Config for Lockscreen, be aware that your LCD only works properly with "chuck norris mode" enabled.

As for demo Version: U Guys can simply delete this app by opening the app, tap on "get the full version" --> "'i already have it!" This will delete the app and for the first time u just need to grant root permission. That's it!

@ all:

I'm cleaning the Sources of the whole Kernel (very old commits from Team Canjica) to get the following benefits:

- clean sources :D

- more close to Stock Sources ;)

- better stability, Speed & Battery lifetime

- higher chance to upgrade the whole kernel (or single drivers) without painfully difficulties

So Actually it's downgraded to 3.0.31 (samsung stock, but with (some) useful commits from Team Canjica kernel and a lot of commits from me)

In Total it contains around over 800 commits ... starting from Samsung stock Source 3.0.31 :cowboy:

So in that process some useful/unuseful/broken features will be removed.... one is e.g. the EXFAT Driver.

If Someone really need the EXFAT Driver, so please just post it here, then i'll implement an updated Version of it.

We've still memory allocation failures .... that's why i've cleaned the whole Kernel Sources ...

But so far the mem fails are still there ... so i've to assume that it's 100% ROM Bug.

EDIT:

Nope :) I did now several tests. ROM is fine. It's just a bad Dalvik & LMK Config that causes OOM for no reason :o

Need to re-configure ...

So stay tuned :highfive:
[Galaxy Ace II Android Development] Fabbb2:
Hello ,

i had 2 reboots today (with the pincode of the sim to enter). I have the last ROM but not the last kernel.

How can i see the cause of these reboots ?
[Galaxy Ace II Android Development] xEmre66:
Take logs (needs root). You can use apps to take logs (e.g: MatLog from Play Store). If you can't get into the system it's useless anyway. ace2nutzer might help you ;)
[Galaxy Ace II Android Development] ace2nutzer:
Sounds like u're using Chrono-kernel settings APK with A2N Kernel or viceversa.

Another cause of the reboot is that u may be use an incompatible A2N Kernel Control Version with the Kernel.

Anyway, to avoid Random reboots use always the latest kernel and Control App, if not, then use the control app version that was coming with the kernel version u're using ... but then make sure that'll not update to the latest version from play store ... otherwise u've the same problem again.
[Galaxy Ace II Android Development] hackuletz16:
slow charging

The cpu is running at 500 mhz when charging, making the phone heat up, this my only problem even in the previous builds. This might cause damage to the battery and also slower charging.
[Galaxy Ace II Android Development] seanmalto:
i still have a bug with latest build, the case is :

when i open some app, then i force it to sleep mode, and wake up again the phone by pushing power/home button,

sometimes black screen appear(not always). I have to reboot the phone to boot normally.

my cpu gov is interactive

cpu frex min-max : 400-800

allow purging of asstes inside memory management is checked.

In NT-app

i disable autoboost GPU and GPU full speed.

also i follow the instruction from first page to set :

Mali Boost Delay: 0

Mali up threshold: 128

Mali down threshold: 16

Mali pre-allocated Memory: 32MB

========================================

Hopefully on the next build, this issue will fixed.

one more thing, i have s6d lcd driver that maybe cause this bug.

thanks :D
[Galaxy Ace II Android Development] ace2nutzer:
@up

if u're running latest build, then u've min cpu 500Mhz.. but next build is min 300Mhz ;)

What did u mean with: allow purging of asstes inside memory management is checked. ?

I hope blackscreen for s6d users is fixed again in next build...

Nope, completely wrong. - The heat on charging has nothing to do with the min cpu freq 500Mhz.. it has smthg to do with charging current.. .. default is 600mA .. u can check this in NovaThor App .. but if u don't touched nothing.. then it is by default... and this is fully normal when it's a bit warm.. till 30 - 40° C is normal on charge.. but maybe u've running Apps in background what causing full CPU load.. then of course the heat is more...

U can also charging your battery with 1200Mhz on CPU .. but in IDLE.. this is no problem at all :cowboy:

@ all

i think u'll have later a new release... :)
[Galaxy Ace II Android Development] seanmalto:
i mean, settings>performace>memory management>allow purging of assets is checked.

imo, i've got more black screen when CPU min freq is 500Mhz

i change it from 400Mhz to 500Mhz just now, and my phone got black screen again.

now i set it back to 400Mhz and waiting for the next build.
[Galaxy Ace II Android Development] lewsa17:
Your kernel is compatible with KitKat miui IF not is it possible IF you release?
[Galaxy Ace II Android Development] ace2nutzer:
@up

it should work... try it simply ... ;)

Oh okay.. then immediately uncheck this pls .. with that unchecked the Phone runs much better.

I do now new build with min cpu freq 400Mhz .. and re-add 600Mhz step again.. I'm not satisfied with min 300 and directly to 800Mhz..

I've tested nearly 2 whole days with different min freqs.. from 50 - 600Mhz ..and of course for every attempt i've adapted the gov... and till now best performance and smallest power consumption is with 400, 600, 800Mhz. ;)

so long ..
[Galaxy Ace II Android Development] hackuletz16:
It is clear that it wont get into deep sleep when charging, then it will be running at 500 mhz while charging, that is the problem. Sorry for having so many questions. Please respect.
[Galaxy Ace II Android Development] ace2nutzer:
Yeah it's normal.. while charging is no deep sleep. I don't see any problems with min cpu freq.. .. on latest build here is min. 500.. and on coming build is 400Mhz.., but again: it has nothing to do with charging. ;)
[Galaxy Ace II Android Development] doctormord:
It won't get any better, the whole frequency stuff is f***ed up. Did all worked in the past with 200-1150 stable. Would be best to just start over than having "more speed, more smooth... "
[Galaxy Ace II Android Development] hackuletz16:
Can you make a kernel with 100 mhz? if it is okay with you ? For me not to be paranoid :D
[Galaxy Ace II Android Development] ChronoMonochrome:
There's no point in adding 100 MHz - since it requires same voltage as 200 MHz. But 200 Mhz probably make sense.
[Galaxy Ace II Android Development] werindam:
[MENTION=5840412]ace2nutzer[/MENTION] I have idea. You should make 200 and 400mhz step but as default set 400 and 200 to people who just want it (maybe for more powersave) and.. enable undervolting in NT settings.. your phone may be stable at "x" vape and other phone may be stable on "x-12mv" stable ofc for example. (hmm and increase a bit vape on all steps for more stability)

And what about make ondemand more powersave and conservative more perfomance (setable via CM profiles)

..And I have question, do you know why my phone is stable at 1150mhz in chrono kernel but on you i cant set over 1000 :'C
[Galaxy Ace II Android Development] ace2nutzer:
yeah.. and 400Mhz can also run without problems @ 1V .. there is really no reason to make the phone laggy and less responsive... the only thing is between 200 and 400Mhz is just a little more power consumption .. i did measurements.... with 200Mhz is ~94mA and with 400MHz is 98mA .. this is a difference for max. 4% during the whole battery usage from 100% - 0%.. but then the phone is very laggy and slowly. I like it really smooth and quickly responsive ( like new phones :) )

U maybe don't believe me.. i did spend nearly 3 whole days to test many things.. with various min. freqs: 50, 100, 200, 300, 400MHz (also with various APE/DDR states.. screen ON 25, 50, 100%) and for every test with adapted interactive gov.. to reach the smoothness.. and also controlling the power consumption during IDLE and also by playing music...

Best result in overall: performance, smoothness and smallest power consumption ist with 400, 600, 800MHz steps.

This is an very intelligent, and user-friendly kernel.. it's good for newbies.... the only thing u need to do is just: flash, find max. stable freq. for CPU and GPU.. that's all !

About UV in NT-APP etc...

i'm not able to adjust the NT-APP to make it working with this kernel.. i don't have the needed files on my laptop here.. i've just an old laptop with small HDD etc.. This kernel have already stable / undervolted Voltages for GPU and CPU .... there is no need to UV a bit more.. may cause instability and blackscreen issues.. (also on ws2401 lcd driver)

For CPU / GPU: for OC Freqs.. they Voltages are already to the MAX. on high freqs: CPU from 1100Mhz - 1400Mhz and GPU: 500 - 800Mhz

As u can see, there is nothing to do.... actually i've an bug in stability by OC more than 1Ghz.. there is a bug in the driver.. or at least on Voltages..

But what i want to say? U can't fix this issue by simply moving an slider in NT-APP ... :highfive: It's hard coded.. and also there is maybe an bug in hardware.. that means it'S very difficult to fix this by software.. but it's possibly.. that needs simply some tests ... just be patient.. i do it all for me and u all.. just chill :D
[Galaxy Ace II Android Development] ChronoMonochrome:
But, probably, with same voltage?

Just out if curiosity, how did you found that CPU UV cause blackscreen issue? I'm not trying to say smth against, since I never asked users to do some tests with UV, to check if it is true or not. But I can at least say, that blackscreen never happened to me - with whatever CPU UV settings.

However, I don't know about s6d drivers - there probably at least one more reason for blackscreen(maybe hardware bug?).
[Galaxy Ace II Android Development] ace2nutzer:
New Build is Up !!

Changelog:

20150112:

Fixed issues with sdcard - thanks [MENTION=5695278]ChronoMonochrome[/MENTION]

Removed 500Mhz step and re-add Steps: 400 and 600Mhz

Re-calibrated interactive Governor (more powersave + smooth)

Minor Kernel Fixes, sdcard speed, 3D-speed

Updated 01optimization File

abb-charger: adjusted 1.st and 2.nd termination current for more battery life (150/130 @ 200/150mA)

Reduced LCD-Brightness for Offline-charging, CWM and booting for more powersaving - thanks [MENTION=5695278]ChronoMonochrome[/MENTION]

Notes: before installing this kernel go to /system/lib/modules/ and delete the 3 modules: usb-mon, usb-storage, usb-acm ...

Yes.... always 1 V.

I've ws2401 driver.. and for me UV more than 1V for min freq.. cause sometimes.. when the Phone was many hours alone a blackscreen for some seconds.. that also confirmed here some users since i've removed 400Mhz step with 1V and added 500mhz step with 1V also for min. freq.. users experienced more blackscreens. I don't think it's Hardware Bug.. s6d LCD needs just more Voltage to run properly.. that's all.

I'm not 100% sure, but i think that varm Voltage is not only for CPU .. but maybe also for Chipset or even for Screen .. (not GPU)

This is maybe strange.. but if we think that vape is not only for GPU.. but also for Sound-Chip etc ... :)
[Galaxy Ace II Android Development] ChronoMonochrome:
Thanks for answer. But isn't better use AVS varm as min voltage? On some phones it's a bit more than 1V. In next build I probably will check it...
[Galaxy Ace II Android Development] Devel0per95:
can i use CPU SPEED= 1100 ?

or still having random reboot problem?
[Galaxy Ace II Android Development] ace2nutzer:
Yeah my Plan is: if with min freq @ 0x18 users having anyway blackscreen issue, then i'll try it with 0x1a .. this is from the AVS File for all Phones the same :)

EDIT:

Bugs and issues are writed on Post #2 ... but anyway i didn't test it.. try it... and tell me pls . ;)
[Galaxy Ace II Android Development] Devel0per95:
I will

btw can install it on lollipop ?
[Galaxy Ace II Android Development] soko3:
i didn't experienced any blackscreen issues until last build. this build doesn't fix this bug...

in my case blackscreen bug occurs only on high cpu load like playing darkness reborn or incoming call (which is sooooo laggy and annoying)

everything else looks good, better than last build