yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] ChronoMonochrome:
r3.1

Ok, r3.1 is up!

Changelog:

management of "not lockable" wakelocks.

This feature is written by me and lets user-space specify sets of wakelocks, which should be prevented from keeping the system awake.

There are four new parameters(inside folder /sys/module/userwakelock/parameters):

- wakelock_blacklist and wakelock_whitelist, are the flags to disable/enable wakelocks blacklist/whitelist, respectively;

- wakelock_blacklist_names, is the list of wakelocks to be prevented from keeping system awake;

- wakelock_whitelist_names: if wakelock_whitelist is enabled, only wakelocks from this list may keep system awake.

allowed some system wakelocks to be disabled (see /sys/module/wakelock/parameters)

adjusted battery voltage-capacitance table (probably should be fine now - see screenshot below)

management of not killable processes

Originally written by Christopher83 and modified by me for codina. Difference between original patch and this:

- reworked so that only minimal lmk code is touched, in hope don't mess it too much :)

- processes are "truly" not killable (meant, lmk can't kill protected processes, but for some reason sometimes processes gets killed anyway)

- removed donotkill_sysproc and donotkill_sysproc_names parameters

- once LMK tries to kill protected process, its oom_adj is automatically set to 0

There are two new interfaces (inside folder /sys/module/lowmemorykiller/parameters):

- donotkill_proc, is the flag to enable / disable this feature for the processes chosen by the user

- donotkill_proc_names, is the list of process names (comma separated) chosen by the user to be preserved from killing

new zram config based upon script by STE

https://github.com/pauldmps/vendor_st-ericsson_u8500/blob/master/u8500/zram_config.sh

[r3.1] Full changelog

About battery table recalibration, I haven't tested it heavily, but since 4 hours after full recharge, the gauge haven't dropped even by 1%!

I was able to recalibrate table thanks to [MENTION=5840412]ace2nutzer[/MENTION] hint about max voltage 4.2V and some formula that I have found previously.
[Galaxy Ace II Android Development] str3tch72:
One question: r3.1 supports Vanir?
[Galaxy Ace II Android Development] ChronoMonochrome:
Of course, I personally use Vanir with r3.1.
[Galaxy Ace II Android Development] xo.en:
Works great with (modded) Vanir.

This is insane, if you think about it - for two years we suffered from this 95% issue...now it seems to be solved - 5 hours passed by - i have 99% of battery, 2g is on.

BUT, this is interesting - restart of systemui immediately drops battery...for 5%(NOT full restart)...damn.

It looked like this: 99%->systemui restart->94%->reboot->93%.

Sigh.

Anyway, another observation: performance control nicely shows every added function of kernel - whitelist showed after flashing 3.1.

It is crucial addition to chronokernelsettings, imho. What's weird - CKS and PC ksm settings seems to be contadictionary - one shows it is on, another - off. One of them must be wrong, right?

Imho, it is perfctrl in this case(it still shows that it is working, even, if states it is not ON).
[Galaxy Ace II Android Development] d4v_lnks:
On last version r3.1 my camera fail to start, i'm using stock rom 4.1.2

Sent from my GT-I8160
[Galaxy Ace II Android Development] borkins:
Ace2nutzer, Chrono,

I think this maybe helpful for You.

The 4% drop comes from the age and the count of charge/discharge cycles.

The new battery is charged to 4.35 V to reach the capacity of 1500 mAh.

So, the older batteries can't reach it.
[Galaxy Ace II Android Development] xo.en:
..95% "bug" was present with new machines and custom kernels since 2013 or so.

Interesting article, it partially agrees with my idea of SLOW charging, but from different PoV.

But it is getting more clear after reading article..

So, it is about some kind of backed up capacity REuseable when battery is getting older, that is.

Concluding: that 95% "bug" may actually prolong our batteries life...

and it's related to keeping battery from wobbly overcharging(related to batt aging, i .e.).

Hm, this is scary:

http://www.batteryuniversity.com/_img/content/lithium2.jpg

So, what's your thoughts?

p.s. Anyway - r3.1 seems to have nice batt usage, regardless of anything.
[Galaxy Ace II Android Development] borkins:
Now I'm wondering how "capacity_level_raw" ( the floating percent level) is calculated in kernel, because there is some difference

between "capacity" (percents) and "capacity_level_raw".

When charging, in "capacity_level_raw" shows 100 %, in "capacity" file is still 99 %.

The same thing i saw before, when discharged to 0 % in "capacity_level_raw", but still 1 % in "capacity".

As far as I understand it, the "capacity_level_raw" must show more accurate level left in percents than in "capacity", coz of the floating point.

But the phone rebooted when in the statusbar ( or the value in "capacity") showed 0 %.

Here is the path of this files:

"/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg"

Also the "energy" files there seems to be inaccurate.
[Galaxy Ace II Android Development] TheLiquidGuy:
Gj man! Nice work!
[Galaxy Ace II Android Development] heldix:
How can u give so much importance to 95% 100% 92% battery level numbers... How an u even speak of "bugs". These % numbers are just indicators. Getting them accurate is kinda "rocket science" and its not even necessary to get them accurate.
[Galaxy Ace II Android Development] xo.en:
Look, if it is unimportant for you, then ignore my posts, ok?

This is dev forum and i am bored, so i am trying to make loose talk, I am not begging for a-ny-thing a'ight?

I am perfectly happy with my device.

And btw, latest chrono's one is behaving better, than 3.0, despite of that unsolved mystery is still not solved.
[Galaxy Ace II Android Development] exodius48:
Wow,,what is your rom?
[Galaxy Ace II Android Development] heldix:
Well i guess i will just do what i heard of already many others do concerning your wierd personality. Thx@ignore function XD

Now back to topic!
[Galaxy Ace II Android Development] TheLiquidGuy:
CM11 TC
[Galaxy Ace II Android Development] xo.en:
Sorry.
[Galaxy Ace II Android Development] zizoumadrid:
after i'm flashing the latest build 3.1 coming from ace2nutzer kernal i have a bootloop phone still in samsung boot logo what wrong i'm doing ??
[Galaxy Ace II Android Development] ace2nutzer:
[MENTION=5151049]borkins[/MENTION] and others:

Thanks for all your input in order to provide information about Charging Li-ion batteries .. we (chrono and i) are building a new charger driver that will support ALL 3rd-party 3.6 and 3.7V and of course also the original 3.8V Batteries including perfect battery gauge ! .. For me upcoming driver is tested and works really great ... it goes from 100% to 99% after 10:40 (yes over 10h) Phone was in deep sleep + airplane mode .. and this with a 2,5 Years old orginal battery... 1500mA.

We'll reduce termination voltage from 4.35V @ 4.25V = 86% capacity.. but we'll reduce termination current from 150mA @ 60mA .. and this will recover some capacity .... so at the end the real capacity is approx 90 - 95% but it'll DOUBLE the cycle life !!! :good::good::good:

btw: this graphic:

http://www.batteryuniversity.com/_img/content/lithium2.jpg

is related to the 4.2V Battery ... we've 4.35V ;) It shows only what happens if you do overcharging ...

so see the table before .. 4.2V(4.35V) is 300 - 500 cycles and is 100%..

then reducing of -0.10V = 4.1V(4.25V) --> 600 - 1000 cycles and is 86%

About Charging current:

That means between: 1500 * 0.5 = 750mA and 1500 * 0.8 = 1200mA

I suggest charging current 600 - 800mA

But our NovaThor U8500 limit this to max. 900mA

Edit:

Tip:

use only the org. samsung battery 1500mA ---> 3.8V

OR:

if u don't want to by org. battery .. because of expensive ... u can also buy a very cheap battery.. but only this Voltages: 3.6V or 3.7V .. but here 3.7V is recommended and battery Gauge will work correctly !

Notes:

3.8V non-original batteries will also work, but with reduced capacity and false battery gauge !!
[Galaxy Ace II Android Development] ChronoMonochrome:
Hey, I didn't say it yet :cyclops: Anyway I don't have time right now for these experiments, will test it later.

Maybe it's a CWM's busybox issue, at least some time ago I have encountered bootloop after switching kernels too. It looks like it's better to make kernel installer independent of the ramdisk busybox by using prebuilt one..
[Galaxy Ace II Android Development] xo.en:
...tell me, don't you think, that such high current may lead to quite high temperature within our machines?

Even 600mA seems to make some heat there...from article i assumed, that temperature of battery is generally leading to quicker death of one...

Look - i never considered replacement of battery as an issue, since it SEEMED, that i can get an ORI-GI-NAL one, but....getting original battery is just not possible, so...

My battery is >2 y.o. and i cannot see it is weared so far...i always used slow charging you are trying to dismiss as proper way of maintaining...well..hm...2 days of idle(well, few sms'es, some wifi, some gaming while sittin' on throne..) - 80% left. Current charge set to 400mA.
[Galaxy Ace II Android Development] borkins:
How 800 mA of charging current is possible, if the charger output current is max 700 mA? :/

Also charging over 500 mA is not possible for the older batteries, because of the high internal resistance of the old batteries, also

when the phone is working, it using some power ( average 140 mA ) , especially if its turned on and used.

For example: My battery is charged with ~100 - 380 mA max, even if i set it over 400 mA.
[Galaxy Ace II Android Development] xo.en:
...more: how >500mA is possible for usb charging, since it seems to work(oO), charging is insaneously fast, but..it is scary.

Sometimes..i am baffled wth, don't you?

Chronokernelsettings seems to block that insane values, so..use it, if you have any concerns, like me.

I do.

Sorry, my lap is overheated now, it seems to lose "t" and "s" letters sometimes.... :(

Even rmclock is not able to help me(probably gpu/NB chip is badly soldered, ffs)...
[Galaxy Ace II Android Development] ace2nutzer:
What i say and what the kernels do is related to an new battery .. or do u really think we'll adpt every month the kernel according to the age of our batteries ?! :highfive:

btw: pls read some informations on wikipedia about lithium io-on before posting wrong infos ..

btw2: an old battery will cause more heat than an new battery like [MENTION=5151049]borkins[/MENTION] said .. so u've to regulate charging current in NT-APP ...

and what is high temp?? During charging up to 35° or max. 40° C is NOT High.. this is just normal operanting temperature range.

btw3: charging an lithium batt. under 20° is also not very well ... so WTH ? ;)

Tested by me/mycase: 2,5 Years old.. batt. and with the org. charger.. max.700mA ..

The Charger can provide up to 800mA.. believe me... but between 800 and 900mA i didn't see any difference.. probably due to my old battery or because the charger real limit is 800mA. But i can't suggest to charge with this very small charger over 700mA .. it'll DIE because of simply overheating.

600mA is optimal for the org. charger.. don't use more. I was meant 600 - 800mA with an proper charger ... or an org. USB Charger with 1A output current. Actually i've also an cheap USB Charger with 1A .. but it looks like smtg stop the current @ 500 - 550mA .. i'm trying to hack this in Source so that even 900mA is possible.

Well, i can say: the Phone uses when is in airplane mode + Brightness very low.. approx 100mA +-5% (my kernel) and when i'm charging with 600mA the App shows me 420mA are flowing into the battery ...so let's calculate:

420 + 100 = 520mA .. but 600 - 520 = 80mA lesser .. i know that missed 80mA are coming because it's just old battery...

If i set 800mA it shows me 600mA so + 100mA for the device = 700mA real charging +100mA for old battery = 800mA flow from charger but of course only 700mA flowing into the battery (with screen OFF !) ;)
[Galaxy Ace II Android Development] shadow252:
Hi! Have anyone know where can I download google play services fix? I'm currently using Omni 5.1.1 from Chrono. Because I'm not sure if latest build had this fix or not...
[Galaxy Ace II Android Development] borkins:
I'm talking only for the original charger and batteries.

If the charger's factory max output is 700 mA +- 50 mA, you can't get more with software code.

When the phone sleeps it draining only ~ 20 mA.

So, 100 mA load - 20 ( drain on sleep) = 80 mA less drain, then 420 + ( 100 + 80 ) = 600 mA of max charging current.

But that is the charging current without load.

In conclusion:

The apps shows you the charging current + the load.

As you said, you get 420 mA of charging current with the load. High load ( mA drain) = less charging current and vice versa.

For more charging current you need to leave the phone in sleep mode.
[Galaxy Ace II Android Development] ace2nutzer:
For me: it can drain 800mA .... it showed for me 600mA with screen ON .. so @ screen OFF = 680mA .. and the missed 120mA is due of old battery + 20mA for screen OFF. If u can't reach this then your Battery is more broken as mine :o

EDIT:

User doctormord did several tests .. and he was able to measure 900mA current ... see here:

http://xdaforums.com/showpost.php?p=57182380&postcount=505

He just didn't mentioned the max. current with the org. AC charger ... i think because his charger is simply broken or what ever ;)
[Galaxy Ace II Android Development] shadow252:
Please. Can someone post link to the fix for Lollipop?
[Galaxy Ace II Android Development] xo.en:
I am not sure where I am wrong.

High battery temperature is killing it, period.

But let's leave it, because i do not want to be bashed by..people, again.

Look, ace2nutzer - i am using Chrono's kernel for a reason, not yours, ok?
[Galaxy Ace II Android Development] Noxialis:
Reporting in.

Unusually high temperature is felt from the phone when in use.

I was using it as a music player via YouTube earlier, put it in a pouch.

Minutes later, when I took it out to select a different song, the surface heat was noticeably greater than what we're used to, I'd say... Above 40 degrees centigrade perhaps.

Any ideas why?
[Galaxy Ace II Android Development] gothicVI:
Noticed the same with 3.0. Also during charging.
[Galaxy Ace II Android Development] aprofomo:
Hi community,

today I wanted getting started with my cardboard on this device but unfortunately it didn't work as expected.

So I found out that the magnetic field sensor isn't working as you can see on the attached screenshot. There's even no folder in /sys/devices/virtual/sensors.

My question is now: Is this disabled by kernel or is my phone broken? I'm using CM 12.1 by Lupus@dei and kernel version 3.1.

Thanks, aprofomo
[Galaxy Ace II Android Development] Noxialis:
When charging it up, there's no problem with heat.

Never had 3.0 since I read the bugs it had, avoided it. Didn't think there'd be any problems xD
[Galaxy Ace II Android Development] ChronoMonochrome:
Check CPU usage first. Second thing - if there's heavy 3G usage no need to wonder if battery temperature goes too high.
[Galaxy Ace II Android Development] Noxialis:
Can confirm that 3G usage is nil, nada, zero, nothing, abyssmal, absurd, ah~... (insert more lulz here xD)

Anyway...

The phone is used as nothing more than a YT music video player, it doesn't have a sim, nor is GPS being used.

Will check CPU stats, and probably try to use it on a lower frequency.

Will check back in in a few.
[Galaxy Ace II Android Development] damian12332146:
I think there is something wrong with the kernel. In older versions I've used cardboard with working magnetic sensor. Not in google cardbord app, but in other applications works fine.

BTW. Do other sensors are working for you? I cant move camera in some apps, I think this is because the phone does not have a gyroscope.

//sorry for my bad english >.<
[Galaxy Ace II Android Development] Noxialis:
Reporting in...

CPU stats show that it constantly runs 800 when using YouTube.

I find this odd but, I guess, that's just how YT works for it.

Dropped the Max freq. to 600, going to see if that helps with anything. Will be back soon enough.
[Galaxy Ace II Android Development] ChronoMonochrome:
Generally speaking, I do not think that this is the norm. Did a quick test - I had 400MHz average cpufreq when playing video via YT with governor Dynamic and GPU freq 300/400 MHz. Have enabled "CPU usage" option in developer settings to find out what is causing enormous load on CPU.
[Galaxy Ace II Android Development] aprofomo:
Both other sensors, acceleration and proximity, are working fine.
[Galaxy Ace II Android Development] damian12332146:
[MENTION=5705172]aprofomo[/MENTION]

OK, I tested it. And magnetic sensor works corectly. I saw that folder, and yes, there is "magnetic_sensor", so its something wrong with your rom. I use Lupus@dei's AICP. Maybe I can give you that folder and you will copy to your phone, but not now.
[Galaxy Ace II Android Development] aprofomo:
Thank you for testing but i think sending folder doesn't solve the problem
[Galaxy Ace II Android Development] S.AMU:
Can someome say me if this phone supports 64gb SD cards?

Does someone use a 64gb card? Which one do you use?
[Galaxy Ace II Android Development] shadow252:
[MENTION=4947931]Rox[/MENTION] said sometime ago that 64 GB microSD cards works on this phone so it should work.
[Galaxy Ace II Android Development] ace2nutzer:
+ @ up:

Yes.. Last Year Rox said 64GB works ...

I'm using a 32GB Class 10 card .. and works perfectly .. even with 2 partitions .. (vfat + ext4) + swapped storages :o

So i think 64GB should work as well .. and maybe even bigger cards can also working ... who knows ?

According to this:

it's activated ....

https://github.com/ace2nutzer/Samsung_STE_Kernel/blob/3.0.101/block/Kconfig#L26

https://github.com/ChronoMonochrome...842c73/arch/arm/configs/codina_defconfig#L179

Even 2TB+ should work .. but it says depends on 64Bit .. so maybe for us "only" 1TG (1000GB) possible ;)
[Galaxy Ace II Android Development] xo.en:
http://s29.postimg.org/5ty3yrukn/Screenshot_2015_07_27_16_21_01.png

Sounds good...thx, bye...perfect kernel for lonely idiot...

Vanir.

Vanir+maxxaudio+viper+braviav4 alltogether activated there...., cam works superb...

OpenCamera crashes after getting a vid, but this is only issue there(vid is saved, though), besides of...flashlight bug.

Thx, Chrono.

btw, flashlight bug is especially funny, until it's not.

Funny thing: if your flashlight is stuck ON..go...into... 'ABOUT' to..turn light off, definitely, puzzling, funny thing...damn thing has a weird bug, imho. It's definitely troubling thing at night(0 flashlight control, that is).

I am so fcking happy, that flashlight widget works ok(until you get pernament on-issue, if so, go into..flashlight's 'about' to unstuck. ..unusual thing. :S).
[Galaxy Ace II Android Development] ChronoMonochrome:
Yes, camera bug is annoying one. Had a try to compile new build of vanir - believe you or not, but with exactly same fixes which I used in cm11, here camera is completely broken. Had also try to use blobs from cm11, but WTF, camera anyway doesn't work(with or without all necessary wipes, no matter). Sad to say, but for now I gave up.
[Galaxy Ace II Android Development] manthes:
How can i change swap size? I am using 2.23 build and i have 92mb swap. I want to increase it to see if it will help more
[Galaxy Ace II Android Development] ChronoMonochrome:
Open zram init.d script and edit zram size as you want.
[Galaxy Ace II Android Development] PolishVodka:
Chrono

49920000 freq for S6D give me visible tearing (on yours Omni LP), so maybe better is to change it to stock 30720000 for this driver?

I know everybody can change this in mcde interface, but on default it is 4992.. and maybe someone doesn't know.
[Galaxy Ace II Android Development] ChronoMonochrome:
Okay, you can probably expect new build today, only need to test some changes before I'll upload it.
[Galaxy Ace II Android Development] ace2nutzer:
Are u sure?

By default S6D Freq is already 30,7Mhz:

https://github.com/ChronoMonochrome...8/arch/arm/mach-ux500/board-codina-mcde.c#L41

so check init.d scripts and ck-settings :)
[Galaxy Ace II Android Development] ChronoMonochrome:
Those #defines in indeed became obsoleted and no longer used, since they are being overriden by lcdclk code. Anyway, r3.2 is up!

Changelog:

set lcdclk freq to 30.72 MHz for S6D. I was afraid touching lcdclk code(since the last attempt it didn't work properly), this "hack" is done by scripts 00userinit and 00recovery in /ramdisk partition.

removed zram config(it didn't work properly on some ROMs - use ck app to enable zram)

introduced interface /sys/kernel/abb-chargalg/termination_vol. Default termination voltage isn't changed - adjust(decrease) if needed(but not less than recharge_vol). The less termination voltage - than longer battery life(more count of recharge cycles till battery will die), but lesser its maximum charge.

TWRP 2.8.6.0 is used as default recovery. Philz has some problems with scripts used in kernel installer.

Dynamic governor profiles (init.d/10dynamic).

curr_profile="performance"
#curr_profile="default"

There are two profiles. Performance profile is enabled by default, uncomment second line, If you prefer default(previos) tunables of Dynamic.

some changes in installer

Full changelog
[Galaxy Ace II Android Development] shadow252:
Can I flash ChronoKernel r3.2 on latest Omni LP? Or I have to swap osfiles first?
[Galaxy Ace II Android Development] ChronoMonochrome:
Swap bootscript first, as usually.
[Galaxy Ace II Android Development] nikolas1274:
It's this version ok for vanir?

Στάλθηκε από το GT-I8160 μου χρησιμοποιώντας Tapatalk
[Galaxy Ace II Android Development] ChronoMonochrome:
Yes, every version here that can be installed on cm11, can be also installed on vanir. Latest vanir build by me has same configuration as cm11, so that it's more usual cm11 with modded UI, than vanir :)
[Galaxy Ace II Android Development] xo.en:
I need to ask, since i see some...very deep developement here:

What differs latest vanir's kernel from v.3.2?

Also, is s6d really working at 30.72MHz???

I remember stock, 2.6 gui was very fluid, now, with sophisticated kernels and new roms i do not see such fluidity, regardless of overall progress...

Is this desync syndrome, or just roms?
[Galaxy Ace II Android Development] ChronoMonochrome:
The difference between vanir's r3.1 is written in changelog of r3.2. I don't remember configuration of r2.6, and can't remember what was different from newest kernel in such old ones...
[Galaxy Ace II Android Development] xo.en:
Sorry, I was not precise - i meant 2.6 ROM, stock, not 2.6 kernel of yours, lol... it was so fluid, despite of lack of real power...that is.

So, in latest vanir you included r.3.1?
[Galaxy Ace II Android Development] ChronoMonochrome:
Yes, because r3.2 was released later.
[Galaxy Ace II Android Development] xo.en:
3.2 works nice with latest Vanir :)

Thank you.

Interesting thing - gui fluidity with 3.2 and OLD chronokernelsettings settings i was using is insane(interactive/sioplusx2, 0.8gHz max and some...lmk/mem customs used).
[Galaxy Ace II Android Development] Alex_Gamer:
Twrp won't recognize external sd card, what can I do now? That recovery never worked to me :/

Enviado desde mi GT-I8160 mediante Tapatalk
[Galaxy Ace II Android Development] manthes:
Any solution to install kernel with liquid smooth 4.4? From build 3.0 i have the problem that it stucked in samsung logo and i can't try it. I am using 2.3 at the moment
[Galaxy Ace II Android Development] ChronoMonochrome:
Try flashing a cwm recovery - https://drive.google.com/file/d/0B_OwIFfWQnj_SzBEbDViQUU2b1k/view?usp=sharing . But beware, I don't care about those old recoveries from google drive, so I haven't even tested if they still works on newest kernels. As for not recognized sdcard in recovery, I can't fix something I haven't faced so far.

@up, you need proceed installation for not supported ROMs(read in OP). But I assume you already did it?