yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] ace2nutzer:
Nope, it's probably equal like previous build .. because i've reset the video.mode @ stock .. that's like OC ...
[Galaxy Ace II Android Development] lachezar1990:
Everything seems ok with this build and also maybe a little bit better performance :)

I hope this bug with losing network connection after end call is fixed :)
[Galaxy Ace II Android Development] greeceeeee:
I saw big difference on charging while using the phone,with previous version the charge percentage wasn't going up while I was using the phone.
[Galaxy Ace II Android Development] nikolas1274:
[MENTION=5840412]ace2nutzer[/MENTION]

I don't know if you remember that I complain for not receiving notifications for some apps like tapatalk?

After flashing latest built I start receiving notifications from tapatalk and Facebook

Στάλθηκε από το GT-I8160 μου χρησιμοποιώντας Tapatalk
[Galaxy Ace II Android Development] ace2nutzer:
@ up

yes i remember .. but it was really strange .. because only u or just 2 guys had this problem.. but it's nice to hear that's working good now.

thanks for all "thanks".. up to now 20x times for the release .. not so bad .. u're great Community ... one love !!! :good:
[Galaxy Ace II Android Development] cjustin12:
PLS Help me ,after i flash this rom and kernel my ace 2 cant detect my sim card PLS HELP ME:(:(:(:(
[Galaxy Ace II Android Development] :
More RAM will not be ?
[Galaxy Ace II Android Development] ace2nutzer:
u need first Stock ROM 4.1.2 as base (latest)

then make sure that u've flashed the right ROM .. there is one for codina (without NFC) and one for codinap (with NFC)

Only the kernel is universal ....

Nope.. RAM is already pushed to the max... we've 628MB + 300MB zRam = 928MB ;)

But next Build will have better Battery Lifetime.. and fixed wrong Battery Gauge from 100 - 90% (drops). ;)
[Galaxy Ace II Android Development] Craxor:
can i flash this over previous build ?
[Galaxy Ace II Android Development] nikolas1274:
Yes just wipe CACHE & DALVIK CACHE
[Galaxy Ace II Android Development] greeceeeee:
For me facebook notifications does not work.... :(
[Galaxy Ace II Android Development] nikolas1274:
For me sometimes work some not
[Galaxy Ace II Android Development] Fabbb2:
still 555 MB of ram

I just flashed the last version (i had a version of november 2014 for the rom and january for the kernel). I had some google gapps FC, now it seems ok.

But i still have 555 MB of RAM... How can i increase it to 628 MB ?

Thanks again to Ace2nutzer for this huge work
[Galaxy Ace II Android Development] ace2nutzer:
Have u codina or codinap ?
[Galaxy Ace II Android Development] greeceeeee:
can anyone tell me how is it possible to expand internal space to install games like pes manager??
[Galaxy Ace II Android Development] shadow252:
You have to swap storages. You can use ChronoKernelSettings app to do that.
[Galaxy Ace II Android Development] ace2nutzer:
nope, he can't on this kernel, but he can use NovaThor-Settings to swap storages ..

of course needed sdcard ...
[Galaxy Ace II Android Development] greeceeeee:
Thanks!I thought it was something to do with f2fs because I have yet to understand about it
[Galaxy Ace II Android Development] Fabbb2:
i use codinap for NFC
[Galaxy Ace II Android Development] ace2nutzer:
Yes that's right, but have u really an GT-I8160P ???

Because u can't use Sim-card + NFC on a non-P-Model ;)

And as i said u need to flash first Stock ROM 4.1.2 (latest) with ODIN ...
[Galaxy Ace II Android Development] Fabbb2:
Sure i have the P model, i use NFC.

I have to flash 4.1.2 before flashing your kernel to get more RAM ?
[Galaxy Ace II Android Development] ace2nutzer:
ODIN:

http://d-h.st/Jze

u've to flash this 3-parted Stock JB with ODIN:

do first wipe data

http://d-h.st/v6N

for help settings like this:

http://xdaforums.com/attachment.php?attachmentid=2223552&stc=1&d=1377881842

now u've 624MB RAM :)

and then flash latest Stock JB with ODIN:

Do first wipe data:

http://samsung-updates.com/device/?id=GT-I8160P

use one of the MG2 Firmwares ;)

Then flash over recovery first temp cwm:

http://d-h.st/2td

then wipe data and format system

then the ROM:

http://xda.mister-freeze.eu/XDA-files/ace2nutzer/CM11/codinap/cm-11-20150714-UNOFFICIAL-codinap.zip

now u've 628MB RAM + 300MB zRam xD

Kernel is already up-to-date on this ROM.

And for coming kernel update just flash the kernel over recovery and done ! ;)
[Galaxy Ace II Android Development] giginski:
hi ppl, today i got strange battery drain, since i unpluged my phone over 6 h i have sva kernel wakelock, what is that and how to fix it. thx for help
[Galaxy Ace II Android Development] ace2nutzer:
New Kernel is Up !!

Changelog:

20150722:

Battery Gauge: Calibration of voltage-percentage table - thanks [MENTION=5695278]ChronoMonochrome[/MENTION] for help - Fixed Battery Gauge drops after full charging

Battery Life extender ---> Double charge cycles

Charger: Completely new charging algorithm, now the charger driver supports 2 types of Batteries: 3.8V original SAMSUNG & all 3.7V 3rd-party Batteries (the Driver activate automatically the correct algorithm)

Better Battery lifetime

Clean Build

Download:

http://xda.mister-freeze.eu/XDA-fil...e2nutzer.kernel.4.4.x_20150722_codina.p.l.zip
[Galaxy Ace II Android Development] xkvegans:
The version before 20150722 released over all are good, ram management, performance, battery life and many more.

But sometimes random reboot apear in my case (my device).

Maybe I have to try the latest 20150722 versions.

But once more as I said above over all is amazing.

Thank you [MENTION=5840412]ace2nutzer[/MENTION]
[Galaxy Ace II Android Development] ace2nutzer:
Post last_kmsg after facing an random reboot :)

But probably it's related to CPU Voltages .. so maybe u've to increase the Voltages linear for every step. U can do this over init.d script or just wait for updated NT-APP .. then i'll make UV/OV working again and u can simply increase the CPU Voltages ... but it'll take some time till it's ready.

Because an Default UV is already enabled by default in order to save some power... looks like it's working stable for everybody .. so your Report is actually the first.

btw: On wich CPU Freq the reboot happens ??

@ all:

can pls somebody do one test with this latest kernel ?? I need to know if the new Charger Driver is working properly ...

Only make this Test, if u've an 3.7V Battery not from SAMSUNG.....(to check this, u need to check Voltage on the battery printed)

Install an App what is showing u the Battery Voltage as for example: A1 CPU Tool, and charge @ 100% and check the Battery Voltage.. and post the Voltage here in the thread..

It Should be 4.10V for 3rd-party Batteries....

And 4.25V for org. SAMSUNG 3.8V Battery .. if u like to check also org. battery ;)
[Galaxy Ace II Android Development] borkins:
My observations that may be helpful for you and Chrono ( Chrono-kernel r3.1 ):

+ may save around 50-100 cycles for old battery, and maybe 200-250 for a new batt. :)

+- We'll see level 100% for a long time with newer battery ( but actually a fake level, if charging is only to 4.25V)

- the level gauge is inaccurate apparently to the voltage ( ~ 7% - before at ~ 76% = 4.0V, now at ~ 83% = 4.0V )

- the voltage drops to 3.0V at level ~ 0%, which if it's right, it can damage the battery ( the max V-drop must not be lower than 3.3 - 3.25V).

There is relation between the charging voltage and the current.

If the current is lower, then the charging would be slow, but more efficient. The voltage must not be high ( 4.35V) for a long time, or it will decrease the life of the battery.

If the current is high, the charging is quicker, but bring more heat,

so in the time it will decrease the life of the battery too, and after the charging the voltage will drop rapidly ( not efficient charging ).

Not sure, maybe: 1st termination current ~ 140 mA ; 2nd termination current ~ 100 mA

P.S. Maybe it's better, if you and Chrono can do it so, that everyone to be able, to set the needed values by NT-app, CK-app,

or via Terminal Emulator, by their own will.

Doing so, they can charge the battery to whatever level they want - to save some cycles, or to use the max capacitiy.
[Galaxy Ace II Android Development] gex mordillo:
Original battery [emoji6]

Inviato dal mio... dal mio... Bho!
[Galaxy Ace II Android Development] ChronoMonochrome:
Thanks for your investigations!

This is exactly what I've done some days ago and tried explain to [MENTION=5840412]ace2nutzer[/MENTION] necessity of such posibility to adjust those values manually. This is already implemented in my kernel, but not released yet because I was yet too lazy to test it(well, actually it's almost impossible to charge battery fully when phone is almost constantly used for wifi-tethering with mobile data enabled).
[Galaxy Ace II Android Development] ace2nutzer:
It's even more :) By reducing of every 0.10V it'll always double the cycles ;) See Table 4:

http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries

Nope, it's real .. and correct.. because i'm using termination1st= 60mA and 2nd= 0mA .. instead 200/150mA ;) so at the end real cap. is around 95% ... and this is absolutely right for Mobile Phones .. thinking about that most of users charge in the night .. = after 2-3hours the batt is full .. but after waking up in the morning the Battery was for approx 5 hours @ max. voltage .. = killing battery .. that's why 95% --> and having lesser max. Voltage is much better for such long charging times :)

No one Phone of the world has an exactly Battery Gauge... it's just an approximation ... and it's calculated with this Formula provided from [MENTION=5695278]ChronoMonochrome[/MENTION] :

(later i've adpt it according to the voltage for 100%)

Nope, u can't damage it ;) Even with completely miss-configured charger-driver :) Because the Battery has is own electronic and hard programmed limits for max/min Voltage and also for dangerous temperatures .. it'll simply cut the contacts and all is OK ..

The battery begins to damage if the Voltage is lower that 2.50V ...the Battery itself cut the contacts @ 2.70V (tested by me) and in this kernel 0% battery + clean shutdown is @ 3.30V ... tested and works. So if your Voltage drops @ 3.0V this is normal and no problem for some seconds .. that will not happen on an new battery ;)

See also:

http://batteryuniversity.com/learn/article/premature_voltage_cut_off

Yes/no, There are some specs... for Charging Current and Temperature Range. A Lithium Battery was not invented to charge it very slow. The (good) old Times of NiCd are gone :) An very standard Lithium Battery (not fast-charge capable!) is designed to be charged between 0.6 - 1C without big problems ... see here Figure4:

http://batteryuniversity.com/learn/article/bu_808b_what_causes_li_ion_to_die

As u can see, @ 1C = 650mA charging current for an 650mA standard lithium battery then capacity loss is "only" 100mA after 500 cycles :highfive:

And if u like to minimize that capacity loss nearly to the "zero" this article helps:

http://batteryuniversity.com/learn/article/how_to_increase_the_runtime_of_your_wireless_device

or short here:

So if choose the absolutely minimum of recommended 0.5C .. then it's just the Battery capacity /2 = our charging current in an green range: 750mA so we can use 700 - 800mA without Troubles :) But i decided to use better 700mA since the org. charger spec is 700mA

I hope it'll not fry :D But at least that small charger can even provide 800mA .. so if we use 700mA there is still 100mA as Reserve ... that should be OK :cool:

About Charging Temperature:

Normal operating range: 0–40° C

But optimal Range is: 18-25° C
[Galaxy Ace II Android Development] giginski:
to be honest great kernel, great battery life time, but when i started using network 2g/3g battery goes down quite fast. from full to 20 % in 9 h and only maximum 2-3h using network, rest it was deep sleep. I think we need get use to it. Anyway thx for You and Chrono for doing great job.
[Galaxy Ace II Android Development] ace2nutzer:
Great to hear that ;)

Power consumption on 2/3G is just high .. this is normal .. and if u use the Profile "performance" (OC) then it's more, low signal = more battery draining too. And if Your Battery is over 2 Years old .... just normal behaviour ;)

Try with a new org. Battery .. (but not the cheap version for 8€ .. they are just fake cells..) it can help in this case :)

btw: nobody uses a 3rd-party battery with 3.7V ?? I need to know if the driver works correctly... just tell me if charging voltage @ 100% is = 4.10V :o

Next Version:

Faster charging...

AC Limit 900mA @ 1500mA (max. supported on our Board)

Default Charging Current for AC: 600 @ 700mA

Default Charging Current for USB: 450 @ 500mA

Removed 500mA limit for USB.

With Proper Laptop, at least USB 2.0 and proper Battery, charging @ 1.5A possible without any Problems .. How ?

Simply as that:

Laptop/PC with min. USB 2.0 and min. 3x available USB Ports ...

= 3 x 500mA = 1500mA ...

That means if u like to charge @ max. 1.5A then u should use only one USB Port .. the other 2 Ports = leave it unused during charging...

because u'll use the max. possible current of 1.5A... so no more power left for connecting other usb devices .. (even if non-charging devices!)

Battery: power battery with 3500mA ;)

Not tested but it should work :)

Quick Charging Current recommendation for 3 Different Batteries:

org. Battery 1500mA = 700mA Charging current

1700mA Battery = 800mA Charging Current

3500mA Battery = 1500mA Charging Current
[Galaxy Ace II Android Development] ace2nutzer:
New Kernel is Up !!

Changelog:

20150725:

Charger: Faster Charging

AC Limit 900mA @ 1500mA (max. supported on our Board)

USB Limit 500mA @ 1500mA (max. supported on our Board)

Default Charging Current for AC: 600 @ 700mA

Default Charging Current for USB: 450 @ 500mA

Clean Build

Notes:

Check previous Post for more information about charging current ;)
[Galaxy Ace II Android Development] Alex_Gamer:
I'm wondering if faster charging are too high values to keep a good health to our batteries
[Galaxy Ace II Android Development] ace2nutzer:
Ok, now i think that kernel is fully optimized... so now it's time to update NovaThor App :D
[Galaxy Ace II Android Development] Ave_Hornet:
And then?. :D What are your plans?
[Galaxy Ace II Android Development] ace2nutzer:
Dunno ;)

First let me Update that App.... so adding maybe new features and removing non-used things, fixing bugs, adapting etc...

So that, CPU UV/OV will work properly.. and GPU OC and so on ... :o

btw: latest commit is now exactly 1 Year old ... so it's quite old ...

https://github.com/ace2nutzer/android_packages_apps_DeviceSettings
[Galaxy Ace II Android Development] xo.en:
...while ChronoKernel's users are still using...hm... chronokernelsettings... quite..outdated, thus working...

You know what, i need a beer...
[Galaxy Ace II Android Development] :
[MENTION=5840412]ace2nutzer[/MENTION], when you release newest version of kernel with working sound?

Wysłane z mojego Samsung Galaxy Ace 2 (GT-I8160) za pomocą programu Tapatalk
[Galaxy Ace II Android Development] ace2nutzer:
Today ;)
[Galaxy Ace II Android Development] :
Ok mate :D We are waiting for this (people from polish android forum and I) ;)

Wysłane z mojego Samsung Galaxy Ace 2 (GT-I8160) za pomocą programu Tapatalk
[Galaxy Ace II Android Development] crisis_trustee:
And where is your newest kernel now? Wait it very much! ;)
[Galaxy Ace II Android Development] ace2nutzer:
Sory Guys for long waiting.. but i had problems...

But now, everything is OK...

Changelog:

20141113:

Fully fixed and optimized abb-charger V2.3

Fixed Sound scratching on Screen OFF

Reverted APE_25% OPP for Screen OFF

Improved CPU Stability on OC

Optimized CPU / GPU Voltages

CPU Frequencys: 50Mhz - 1400Mhz !

LiveOPP 2.2 thanks [MENTION=4832589]cocafe[/MENTION] [MENTION=3329816]mkaluza[/MENTION]

Updated Kernel Sources

Online in Dev-host in some Minutes !!

Enjoy this Great Build :D
[Galaxy Ace II Android Development] str3tch72:
Booting, I will test 1,4ghz frequency :D
[Galaxy Ace II Android Development] shaqman89:
1400 is really there. :D you are insane. And here, I was thinking that being stable 1300 was already insane.

Great job :D
[Galaxy Ace II Android Development] str3tch72:
I think 1250mhz for all phones or 1200mhz should be stable enough.
[Galaxy Ace II Android Development] :
Yea! I can normally hear music on my smartphone :D 50-1200MHz works very stable for me. Thanks [MENTION=5840412]ace2nutzer[/MENTION] :D
[Galaxy Ace II Android Development] chimaeragh:
Does this new kernel support f2fs
[Galaxy Ace II Android Development] ace2nutzer:
Sounds great guys !! :D:D:D

Somebody can break the Record of 1300Mhz ?!! :D:D:D

[MENTION=4973320]str3tch72[/MENTION] And can your Phone running @ 1350 or even 1400Mhz ? :D :D :D

For me is 1,2Ghz stable :D I'm really happy with that :)

F2FS coming soon... i think next build, will have it finally :)
[Galaxy Ace II Android Development] str3tch72:
Instant reboot after set 1400mhz :(
[Galaxy Ace II Android Development] ace2nutzer:
Okay.. it's really to high :)

And what about 1350Mhz ?!
[Galaxy Ace II Android Development] h4cxxc0r3:
sorry for noob question. should i do something before flashing this kernel over Chrono's kernel?? or just flash it. thank's

sorry for bad english.
[Galaxy Ace II Android Development] ace2nutzer:
Just wipe cache...
[Galaxy Ace II Android Development] gRaB@:
I had 4 days batery life with screen off with your first p1 build, now its time to check this new build :D
[Galaxy Ace II Android Development] h4cxxc0r3:
can we change the GPU freq in this kernel??
[Galaxy Ace II Android Development] doctormord:
[MENTION=5840412]ace2nutzer[/MENTION],

i checked the charging control with the latest kernel version in NT:

Set charge current vs. measured charge current:

100mA 88mA

200mA 182mA

300mA 282mA

400mA 380mA

500mA 404mA

600mA 407mA

700mA 407mA

800mA 407mA

900mA 407mA

Charge current control off: 404mA

Tested with a 2.1A capable powerbank and 2 batteries, first was 1% second was 44%.

The powerbank does not identify itself to the phone to be a high-current-charger (DCP or CDP) and charge current is abit lower than expected. An Ipad, on the same port, juice ~1600mA. (With no modification or DCP/CDP resistor hack)

Phone is stating to be charged via AC-charger (settings/about -> loading (AC)).

When modifiing the test-port to "enumerate" as an USB-Port, nothing else changes, except the phone is now stating to be connected to USB.

Max. charge current is the same.

Hacking/Modifying into a DCP/CDP-Port gives (33k/10k hack):

500mA 476mA

600mA 570mA

700mA 670mA

800mA 770mA

900mA 850mA

The effective max charge current is also limited by monitoring the vbus-voltage, so if vbus is going under a defined/hardcoded threshhold, charge current is reduced until vusb-voltage-drop is back to proper levels.

So higher settings of charge-current (600mA+) wont burn out your charger if the charger can't deliver this power or is not enumerating properly. (I.e. setting 900mA and using a dumb charger wont result in more that ~400mA charge current)

Regards,

doc
[Galaxy Ace II Android Development] ace2nutzer:
[MENTION=1130928]doctormord[/MENTION]

Thanks for this professional measurements !

As i can see it looks like that the Phone stuck @ 500mA .. the difference from 500 --> 400 so 100mA is the Power what goes to the Phone and not in the Batt. (as u P'med me ;) )

I believe u don't have changed the Current, properly... it's a bit tricky...

Please use this Method, and try again:

http://xdaforums.com/showpost.php?p=56321125&postcount=3

@ GPU:

Yes u can. just set permission in some Files in /sys/kernel/mali to system:system 644 and u can OC over NT-APP.
[Galaxy Ace II Android Development] soko3:
My charger is 0.5A original Samsung's charger...

What values should i enter in nova thor app??

Because, i have problem, cannot charge phone after flashing your kernel..

battery is almost new, i bought it four months ago
[Galaxy Ace II Android Development] shaqman89:
Just an idea, though, wouldn't it be great if both kernel use the same app? I mean most of the interfaces are the same, right?
[Galaxy Ace II Android Development] ace2nutzer:
Thanks for idea, but exactly this is the problem .. both kernels are using different sysfs interfaces and completely different CPU/GPU Tables .. and of course also different Voltages .. so one same app for both kernels will never work properly :)

I now that most of users are switching always between both kernels .. so it's a bit annoying job to switch every time the Settings app ...

I suggest to test kernels without such apps ... then it's much easier .. after deciding which kernel u want to use.. then install the proper App..

Even i tested Chrono kernel (for 2 days).. i did just freeze NT-APP .. and then use it... Great battery Lifetime but for my needs it was a bit slow and laggy, i didn't change anything .. just kernel defaults .... i don't say it was crappy, i was just too lazy to make some init.d scripts with a bit more aggressively Settings :)
[Galaxy Ace II Android Development] ChronoMonochrome:
Exactly same :) I have tested one of your earlier builds, but have found kernel defaults too much aggresive for this phone. It's just matter of preference. Btw, rigth now I have two installed ROMs, vanir kitkat and omni LP), and should admit that even lightweight vanir runs a bit laggy in compare with omni(on which ck r3.1 runs very smooth btw - with same kernel settings!). What for I mentioned this? In every ROM you'll face diffirent smoothness/performance with same settings of kernel. Rather than adapting kernel settings for each case, I just use settings I used to use(pardon the pun :) ).
[Galaxy Ace II Android Development] greeceeeee:
Facebook notifications work for you?On my phone they don't work...
[Galaxy Ace II Android Development] shaqman89:
Yeah, I also have similar experience. Using both AICP 12.1 and cm11, somehow I feel that aicp 12.1 runs better (which I thought might be just placebo). I did not realize that ROM effects would be this significant.
[Galaxy Ace II Android Development] ace2nutzer:
Yes u're right.. it's just preference. btw: i also tested a older build .. so 3 moths old or what ever ... and probably u tested an kernel from me with the old/buggy interactive gov... that gov. did drain much battery and it was NOT nice smooth like now with dynamic gov. ;)

So u should give a new try :o

btw: R3.0 / R3.1 is not tested by me ... do u think it can beat ace2nutzer kernel in performance by using stock Freqs? so CPU800 and GPU400 ? :D

But not Static freqs .. that's boring ... it should work great with an gov. .. so which gov. u can suggest for performance and also good battery lifetime ??

Then i'll test :) As for Scheduler i'll choose same SioPlus for better comparing :)
[Galaxy Ace II Android Development] ChronoMonochrome:
Hey, I don't trying to participate in that race. And definitely, racing in performance with your kernel wasn't my purpose - this is nearly impossible since I don't trying to use aggresive governor settings. As for me, they are already tuned for good battery life and possibly max performance(with such settings). Later tuning for much performance will cause a negative effect in battery lifetime, which isn't wanted for me, since those defaults already gives good performance for daily usage, and enough good gor me.

I thought answer should be clear... Definetely, it's Dynamic. But I'm trying to not focus on only one governor(as only possible and good in usage). Here are good compromises - OndemandPlus, ZenX, Interactive. Those are good in gaming performance, but less effective in terms of battery lifetime.