yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] ChronoMonochrome:
Ok, it was my mistake with shebang line in genfstab - /system/bin/sh wrongly was used before, but /system may not be mounted during installation. This is fixed by using precompiled sh file - in some recovery's default one (/sbin/sh) anyways doesn't work for some reason.

But what is strange - it shouldn't cause problem with boot, even if genfstab is failed to run(it will, only if /ramdisk/fstab doesn't exist).
[Galaxy Ace II Android Development] Noxialis:
What changes have been made in R3? Changelog pls?
[Galaxy Ace II Android Development] zizoumadrid:
R3.0

reworked genfstab - now it's more friendly for non-standard fstab's, e.g. with swapped sdcards or those ones which used for dualboot

universality is back - one package for codina/codinap

f2fs update (thanks to XperiaSTE team)

various fixes and improvements

reverted previous Makefile optimizations
[Galaxy Ace II Android Development] gothicVI:
Hope it's not too difficult to fix :)

What exactly is "wrong" with this built? Is is just cosmetics or unsafe to use?
[Galaxy Ace II Android Development] shaqman89:
Cosmetics I believe. To be exact, installation may cause a boot loop for some reason, but I think it affects just a specific configuration. I've tried it both on cm11 and cm12.1 and it flashed correctly. It might be similar to 22.4.7 issue when some could flash it successfully while some other got stuck in a boot loop. I myself got stuck at first but after changing kernels a few time, it finally worked.

It's actually better than previous release in both performance and battery drain, at least from the 6 hrs I've been using it. Another great release ChronoMonochrome. :)

Now, I'm curious to try on f2fs again since there is an update, but too bad I can't try it yet for now.
[Galaxy Ace II Android Development] gothicVI:
Changing between different versions you mean, I suppose. Between which versions?

Will give the new version a try once I'm home :D
[Galaxy Ace II Android Development] shaqman89:
Well, in my case, it worked directly from 2.24.7, but when I was installing 2.24.7, I got stuck and only succeeded after installing it from ace2nutzer kernel. I previously tried from 2.24.1, 2.24.3 and 2.22.x but did not succeeded. I'm not sure what's the logical explanation for that. :D
[Galaxy Ace II Android Development] xo.en:
Migration from 2.22.5 is succesful.

For some reason 100% of battery drops quickly to 94% now(not 95%, as usual...).

Anyway, so far, so good.

Btw - sioplus seems to be most battery efficient i/o scheduler...hm.
[Galaxy Ace II Android Development] manthes:
You upload new build? Because i tried again but it still stucked in samsung logo. I tried also and a clean install 4.2.2 rom and it worked after copying a previous boot.cpio.gz to ramdisk folder
[Galaxy Ace II Android Development] ChronoMonochrome:
Too bad, I can't reproduce bug. Better if someone would make backup of "bad" /ramdisk partition via TWRP(and attach here), or provide last_kmsg log.

Fixed genfstab, but apparently it wasn't causing bootloop.
[Galaxy Ace II Android Development] shaqman89:
Well, in my case it is solved. I couldn't make a kmsg at that time due to USB connection having issues.

But right now I'm happily using 3.0. It's running great. :)
[Galaxy Ace II Android Development] matthias1976:
for me no problems updating from 2.24.7 to 3.0

codinaP ext4 chronocm11 twrp
[Galaxy Ace II Android Development] borkins:
It's normal. My battery now drops to 92 %, sometimes even 89 %, before 6 months it drops to 96 - 94 %.

In my observations:

When i bought my phone ( 2.5 years ago ) the charger stops charging at 4.405 V,

and when unplug the charger, the voltage dropped ( ~ 50 mV ) to ~ 4.350 V ( which is the stock voltage of my original battery ).

Now on charging it reaches 4.334 V, and when unplug the charger, the voltage drops ( ~ 150 mV ) to ~ 4.200 V.

So, it looks like we need back thoose 150 mV on unplugged charger, not on charging. But I'm afraid it's impossible now.

Between, I'm working on battery monitor script. I hope it would be helpful for some observations.

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

Sorry for my bad English!
[Galaxy Ace II Android Development] xo.en:
F this.

Real usage is the point.

Nope. It is not normal.

95% is normal(ok, - cwm drain, so far nobody checked cwm for battery drain...it is scary, SCARY).
[Galaxy Ace II Android Development] damian12332146:
Wifi doesn't work after installing R3.0 ;_; AICP 10.0 (5.1.1) How to make it working?
[Galaxy Ace II Android Development] shaqman89:
It worked here without doing anything.

I'm also using aicp 10.0
[Galaxy Ace II Android Development] damian12332146:
shaqman89, Are u doing any wipes while instalation?
[Galaxy Ace II Android Development] shaqman89:
Nope, I just flashed the latest kernel directly. Done.
[Galaxy Ace II Android Development] damian12332146:
So, I don't know what happend ;_; On R2.24.7 everything was ok. :/
[Galaxy Ace II Android Development] Lupus@dei:
Check free space in /system. If there is zero free space - delete someting unneded. AICP OTA, for example. Then reinstall the kernel.
[Galaxy Ace II Android Development] damian12332146:
No, I have 475/603 MB :/ I tried to instal R2.24.7 again and it works, so problem it's on kernel, I think.

Any ides to fix it? :c
[Galaxy Ace II Android Development] Lupus@dei:
For now - no. Previosly optimizations of kernel caused wi-fi problems for me. So I removed them almost at all. Anyway, next build will include latest version of kernel. But when - I don't know. I want to play a little with this.
[Galaxy Ace II Android Development] damian12332146:
Oh, thank you for spending time to our phone. Definitely, i prefer working cam recording, than working wifi on r3.0 >.< So don't worry about AICP users XD Focus on camera and do everything what you can! :D
[Galaxy Ace II Android Development] xo.en:
Precious observation, anyway - can you agree, that this issue, more or less is persistent for this machine?

For two years?

C'mon, this issue is real since beginning...
[Galaxy Ace II Android Development] ace2nutzer:
Yes i agree, this is normal on old battery ! - For me also: when i charge to 100% on offline .. and then boot the phone i've only 86% .. but that it can stay for very long time @ this state. To Avoid such big drops:

1. Buy a new battery ;)

or just keep the Phone on.. but in Airplane mode and charge to 100% and wait until u've reached Real end of charge.. (NT-APP)

4.40V is definitely overcharged .. are u really sure ?? I can remember me on old times with Rox some CM11 Build had this issue with overcharging ... but later it was fixed. The Correct stop Voltage is according to the Stock Battery: 4.35V but in source i've programmed 4.34V .. and it shows exactly 4.35V .. for some reason the charger adds +0.01V :cyclops:

After full charged and directly unplugging the cable the Voltage drops after some seconds -0.10V .. this is normal.

And now the most important and interesting thing what happens when the 4.35V are reached and the charger is still connected:

the charger stop charging @ 4.35V and when currency flow is under 150mA (real end of charge).. and then the battery is discharging faster because of connected cable .. and when the Voltage is @ 4.21V (95%) it'll recharging again to 4.35V (100%) and so on ...

Last is to avoid to keep the battery all the time @ 100% and this just prevent damaging battery very quickly :)

That means it's just luck if u unplug the charger at the right moment ---> 4.35V to have REAL 100% charged battery .. otherwise at at worse moment it'll show anyway 100% but it'll drop very quickly @ 95% .. so no need to worry.. everything normal ... my kernel and this kernel uses the same charger algorithm :)
[Galaxy Ace II Android Development] borkins:
I think the problem is with the charging on the stock configuration of the phone.:confused:

Now we have cycle charging and etc., but our batteries are already damaged.

I don't have new battery to test what is the highest voltage on charging, and when unplug the charger with the custom kernels.

I know that the Li-ion battery "don't like" the heat, the continuous voltages near the maximum, or near the minimum.

So, what happens then, if you decide to leave the phone in the night on charging with the stock kernel?

=> Continuous recharging ( over the maximum of 4.35 V ) + some unnecessary heat. That kills the Li-ion battery quickly.

Like I said, the first voltages while charging my phone was 50mV over the maximum of 4.35 V ( 4.40 V ),

only 4 months later the charging reaches 4.368 mV on charging, then I saw the first drops of 4% ( 100 - 96 % only for a few minutes ).

But I'm sure that i don't had this problem when i bought the phone. I had many logs, but i lost them when i wiped the SD card by mistake. :/
[Galaxy Ace II Android Development] Culateralligator:
Hello. And what about NovaThor Settings? Worth using the charge cycle control?

Enviado desde mi GTi8160 KK AOSP
[Galaxy Ace II Android Development] ace2nutzer:
Nothing to do with old/new battery .. the internal charger on phone charge the battery till the coded termination voltage in kernel ...

And if it's to high, it can even explode lol

yes, but "heat" is only during charging .. so let say 0 - 90% .... and from 95 - 100% the battery will stay cold.. because there is no more high currency flow. And the heat u can regulate it by yourself by using different current ...

On stock GB:

termination voltage: 4.26V and recharge voltage: 4.25V:

https://github.com/ace2nutzer/Samsu....7/arch/arm/mach-ux500/board-codina-bm.c#L280

On Stock JB:

termination voltage: 4.26V and recharge voltage: 4.25V:

https://github.com/ace2nutzer/Samsu...31/arch/arm/mach-ux500/board-codina-bm.c#L308

As u can see, on Stock kernels the battery is LESS charged.. but shows more % as it's .. due to different (lower) Voltage table ..

And according to the Voltage table (the second) it charge-recharge from 96 - 100% ;)

check this Table from Stock JB:

https://github.com/ace2nutzer/Samsu...31/arch/arm/mach-ux500/board-codina-bm.c#L106

and from both custom kernels here:

https://github.com/ace2nutzer/Samsu...01/arch/arm/mach-ux500/board-codina-bm.c#L106

As u can see, there is on high percentage mostly a difference of 0.10V approx .. and after the first Voltage Table on Stock Kernel, there is a second Table but with different Voltages .. and we're using 2 times the same Table.. and to be honest a really don't know why 2 different Table ...

But who knows ... maybe this is our Problem with the "drops" ?? I can try to make a test build with this 2 Voltage Table from Stock JB Kernel .. maybe drops are then minimized or even gone :fingers-crossed:

Not really .. a bit cycle charging is alway there --> 95 - 100% ..

But if u really like to to smthg good for your battery, then use it only from the range: 30 - 80% ... and use cycle charging 75 - 80% ...

But this is very painful to have only 50% of battery instead of 100% :)
[Galaxy Ace II Android Development] borkins:
Maybe the tables are two, because the first is for unknown type battery, and the second - for the original 1500 mAh Li-ion battery.

The kernel knows the type of the battery and use the right table. I think that for original battery it use the second.

Overall, the difference here between GB and JB is the termination current:

GB - 1st: 100 mAh, 2nd: 60 mAh

JB - 1st: 160 mAh, 2nd: 120 mAh

For new original battery we need 4.35 V, without plugged charger - to be sure, that is fully charged.
[Galaxy Ace II Android Development] xo.en:
???

Can you post photo of your battery?
[Galaxy Ace II Android Development] ace2nutzer:
hmm i was wrong.... termination current is 4.35V on stock JB kernel:

https://github.com/ace2nutzer/Samsu...31/arch/arm/mach-ux500/board-codina-bm.c#L377

of course with the org. battery ... u're right... first element is always for unknown battery type :D

Well, now i know what i need to do fix finally charger .. i'll adpt most important Values to the Stock JB Kernel ...:good:

termination voltage is meaning when the Charger is plugged.

After unplugging the charger the voltage will drop to approx 4.25V and represent 96% battery :

https://github.com/ace2nutzer/Samsu...31/arch/arm/mach-ux500/board-codina-bm.c#L140

but it'll show for some time still 100% .. but when using the phone it'll go fast to 96% .. finally we got this damn problem ^^

The default operating Voltage @ load is 3.82V:

https://github.com/ace2nutzer/Samsu...31/arch/arm/mach-ux500/board-codina-bm.c#L376

See also this auction:

http://www.ebay.de/itm/Original-Sam...33?pt=LH_DefaultDomain_77&hash=item4aeac313c9

Take a look at the battery.. there are 2 Voltages... 3.8V and 4.35V

btw: for us german people we can buy a org. battery for under 8€:

http://www.ebay.de/itm/Original-Sam...67?pt=LH_DefaultDomain_77&hash=item1c3df8d20f
[Galaxy Ace II Android Development] borkins:
I'll use ace2nutzer's links:

Look here:

http://www.ebay.de/itm/Original-Samsung-Galaxy-S3-Mini-i8190-Akku-Ersatzakku-mit-NFC-EB-L1M7FLU-1500mA-/321766233033?pt=LH_DefaultDomain_77&hash=item4aeac313c9

and here:

http://www.ebay.de/itm/Original-Samsung-Galaxy-S3-Mini-i8190-Akku-Ersatzakku-Battery-EB-F1M7FLU-1500mA-/121298801167?pt=LH_DefaultDomain_77&hash=item1c3df8d20f

My battery is the same.

[MENTION=5840412]ace2nutzer[/MENTION],

this nominal voltage ( 3,82 V ) is equal to 50% of battery charge/discharge.

4350 mV ( max ) - 3300 mV ( min ) = 1050 mV

50 % 1050 mV = 525 mV

4350 mV - 525 mV = 3825 mV
[Galaxy Ace II Android Development] ace2nutzer:
Yes this is very interesting thing ! Never see this before :o

So, when battery is full.. and u'll give 1.5A load .. then the voltage should drop @ 3.8V and it can provide the 1.5A for 1 hour .. then it's empty .. ---->1500mAh / 1.5Ah :)

But on half charged battery we've the nominal voltage on idle.

Another example:

1,2V NiMH Battery:

1.2V nominal

1.45V = termination Voltage

1.0V = empty. on load ..and empty on idle @ 1.2V !!

btw: an fully charged NiMH Battery has on idle 1.35V (if not, it's broken)
[Galaxy Ace II Android Development] fluffi444:
R3.0 runs very good! No problems with install at all.

Even on girlfriends phone (which didn't accept Kernel R2.24.7 for instance) it installs (and works) without problems! :good:

Well done! Worth to call it 3.0 ;)
[Galaxy Ace II Android Development] ace2nutzer:
[MENTION=5151049]borkins[/MENTION]

i've fixed all problems on charger according to stock jb kernel .. but some values i've optimized it a bit and i've also added full support for the 1700mA Battery* :D But other 3rd-party 3.7V Battery will also working better than before...

https://github.com/ace2nutzer/Samsung_STE_Kernel/commit/be5ca3c5c738f5162a56eca5f7a4cb47887bfb9c

* By using the "unknown" profile :o

Big THX to u ! :good::good::good:
[Galaxy Ace II Android Development] heldix:
Is this issue fixed in 3.0? http://xdaforums.com/general/general/fix-fix-systemupdateservice-wakelock-t3060548

I personally dont like these high voltages on loading lipo cells. I come from rc hobby and we are quite heavily involved in using these cells. Idd more like to just use 4.2 as termination voltage because u highly increase the number of cycles the cell will achieve without degrading. The increase of capacity u gain by pushign the voltage that high is quite neglectable.

Also there are reports that nearly every "original" cell on amazon and ebay are fakes. Heise checked this 3 months ago and EVERY cell they bought was a fake. http://winfuture.de/news,86703.html Just german sorry. http://www.heise.de/ct/ausgabe/2015...chgebaute-Akkus-als-Originalware-2604617.html.

And those fake cells all are 3.6/3.7/4.2 lipo cells. So if u already replaced ur cell u will have some fake **** now. And these fake cells DONT like to be charged to 4.35V. 4.35V cells are high tech and near to nowhere to get in rc sports. And ppl who use them know that they will degrade fast when really pushing to 4.35V. There are diagrams that 4.35V cells pushed to 4.35V will have lower capacity than 4.2V cells after around ~50 charges.

Also i dont know whether u saw an exploding cell already. With real big rc cells u have to renovate ur room. Most ppl put their rc cells into fireprevent metal cases. "Little" 1s0p 1500er cells are not that powerful but still dangerous. Consider this when u increase termination voltage on "unknown" cells which i oracle to be just 4.2V cells and nothing more. 4.35V cells are not highly distributed.

Just my 2 cents,

heldix
[Galaxy Ace II Android Development] gothicVI:
I'd like to report on the latest release:

Upgrade onto v.3.0 was fine - no problems at all - using op's twrp built

Phone runs stable - no fc or sudden reboot

BUT: enormous battery drain! I removed my phone from charger at 100% ca. 100min ago, updated one app via wlan and did a bit reading using xda app. All together no longer then 40min and I'm on 76% battery! Furthermore I realized that CPU goes to max frequency (1GHz) almost instantly on starting any arbitrary app AND stays on that freq. even on closing all apps, hence CPU load is almost always max which is a huge difference w.r.t. the previous version... :confused:
[Galaxy Ace II Android Development] xo.en:
Man..you really should take control over your machine...hint: chronokernelsettings app(governor, etc)...also, you can make wifi using less power with this app, too...
[Galaxy Ace II Android Development] gothicVI:
I try to but am not that firm with the android internals but learning.

I do use choronokernelsettings, that's how I increased the max CPU freq. from 0.8GHz to 1GHz...

ANY suggestions regarding governor or I/O are highly welcome but please bring them with a (short) explanation :)

Thanks ahead... man :cool:
[Galaxy Ace II Android Development] ChronoMonochrome:
Hey, this isn't kernel issue, so why it should be fixed here? But by coincidence I has developed something similar which could prevent the system from keeping awake by any wakelock https://github.com/ChronoMonochrome/Chrono_Kernel-1/commit/39555eb4e00a853542dd34d3b15102617c186915

This isn't included in r3.0, but most likely will be in r3.1.

It sounds like so-called 1GHz bug. You can use any app that shows CPU usage, e.g. top or just enable CPU usage showing in developer settings.
[Galaxy Ace II Android Development] xo.en:
He set cpu to 1ghz....but he did not choose proper governor...

Btw, here's a thing i do not like - chrono - your kernel seems to have charging set to 600ma as default.

But definitely - it is not default for ace2.

Charging is fast, but imho, faster charging = worse batt performance AND quicker wearing of battery, in general.

Advice for users: et chronokernelsettings' option to ease this 600ma to 400ma - it may have good effect for your battery woes, guys...

Also - do not make conclusions about batt usage until you charge battery at least twice...
[Galaxy Ace II Android Development] ChronoMonochrome:
It maybe not that simple. There is only one governor that can keep max freq even in idle - performance(I assume most of governors weren't loaded furthermore).

Once I has encountered similar issue - even with Dynamic governor CPU freq was always at max. What do you think was wrong? Somehow Nova launcher was causing 95-99% load on CPU, it turned out after enabling aformentioned option in dev. settings. Upgarding(or clearing data, don't remember exactly) solved this issue.
[Galaxy Ace II Android Development] xo.en:
Dynamic sucks ass, imho.

Look, i am aware, what performance is, since he did not set it manually, there is NO way, that performance could be set just like that without user input, right?

C'mon...
[Galaxy Ace II Android Development] ChronoMonochrome:
At least not me enabled this by default ;P But okay, next build will have 500 mA by default (isn't it codina default?).
[Galaxy Ace II Android Development] xo.en:
500ma is default max for usb charging

(win usb driver restriction, and imho, it is too much for usb cable for smartphones, but NOBODY CARES, salary works),

From my experience - 400ma is optimal - battery seems to last longer, than with quick charge)obvious..ok?).

But, users' usage types may force using fast charge..ok...

I was literally scared seeing that 600ma setting...it is unnecesary, it is damaging, it it BAD.
[Galaxy Ace II Android Development] ChronoMonochrome:
It's just matter of preference... personally I use 800 mA for almost 2 years since I has buyed the phone, and I still able to achieve 3-5 hours SOT(depending on usage).
[Galaxy Ace II Android Development] xo.en:
Post your screen usage, then(screen on, that is).
[Galaxy Ace II Android Development] ChronoMonochrome:
I mostly use phone for wifi tethering, so that screen is almost always off. I have to force HSPDA for mobile data because EDGE sucks(at least, with my service provider), thus battery charge sometimes drains very quickly. Ok, I will post screen usage, when I will use it more actively.

Unluckily, 400 mA current is not for me, otherwise I will have to let phone charging constantly xD what is worse by itself.
[Galaxy Ace II Android Development] ace2nutzer:
[MENTION=6299476]heldix[/MENTION]

nice information .. that's is really logically.. it was all the time for me very suspect that an org. Battery is so much cheap ! But most of people will never see this.. because when u by such new battery (fake) then u're happy that the battery- lifetime is great again ... in comparison to the old broken battery ... of course it's better.. but most of people can't compare the new brought fake battery with a NEW org. SAMSUNG Battery ... so they never see the difference.

But anyway even this is no problem... we have 2 Profiles for battery recognition.. the first profile is for the "unknown" battery type.. and the second for the real org. samsung battery.

in that case the second profile have:

3.8V

4.35V

and the first profile:

3.7V

4.2V

then it's OK ... the only thing i need to adjust is just the Voltage table of that 2 Profiles...

Actually i did a release with 1:1 Samsung JB Kernel Voltage Table .. and now it's more terrible than before !

Yesterday i charged exactly till Real end of charge (2nd_termination_current 150mA) ---> 4.36V and then unplugged the charger .. Voltage drops immediately @ 4.25V .. and after 4 hours offline mode, screen off... ---> 94% (usually i had 96% with my custom table) and Voltage was @ 4.20V !

Unfortunately i also haven't here an new org. battery.. so i can't test if this is exactly the same scenario .... but i think YES.

So that battery gauge was never perfect.. so i'll try to calibrate them again... this time i'll use 4.200V for 100% .. this is more realistic instead samsung default of 4.328V ;)

btw u guys can't damage your batteries by charging @ 600mA or more.. also it makes not as much sense to charge with 400mA.

and also u'll not have a more charged battery because u charge this "slower" ...

Immagine u've a 1L bottle and u want to fill it with water... u can fill the bottle slow or very fast ... try to fill it very slow.. do u think it can fit more than 1L water ?? i say no ;)

A Lithium Battery is able to charge at 1C (1500mA according to our 1500mA battery) without damaging the cell.

But u can damage it by simply overcharging .. so let say @ 4.60V and this even with only 100mA charging current ... yes !
[Galaxy Ace II Android Development] borkins:
Maybe there is something wrong with the percents level calculation. I think, we must use a stock table, but maybe it's need only a little correction somewhere.

I'm not sure what is this for: "lowbat_threshold = 3300". If it's the lowest range of the voltage, maybe it must be 3250.

Then the range 4350 - 3250 is exactly 1.1 V, so we would get 3.8 V for nominal voltage not ( 3.82 ). :\
[Galaxy Ace II Android Development] ace2nutzer:
@ up

no.. the problem is from 90-100% or at least 95-100%.. of course.. voltage-percent is wrong on this range.. that's why it goes fast from 100 to 95 without using the phone.

as i said actually i'm using stock battery voltage table from JB.. and it's worse than before ^^

If u don't believe, try this: 14/07 kernel from me and see by yourself or just compare my actually battery table from my github with the org. from JB.