yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] fluffi444:
Same... Looks like Phone does not go to deep sleep... (YES - I tried already the activation of UpdatesServices :D )

BetterBatteryStats gave me this as possible reason... It's active in Kernel Wakelocks for the whole time since Charger deplug 4h ago......

BLN_KERNEL_WAKE_LOCK

And I have BLN deaktivated in NT settings....

EDIT

After Reboot the issue is away - Deep sleep is worling again... Will keep an eye on it what this BLN_KERNEL_WAKE_LOCK causes...

Maybe it has something to do with fully charged and depluged etc....
[Galaxy Ace II Android Development] pedroleon99:
How many times should we repeat that benchmarks have no sense?

You have to see if the phone is faster and battery friendly, not do useless benchmarks

---------- Post added at 01:26 PM ---------- Previous post was at 01:00 PM ----------

All works fine on stock rom interactive-sioplus 200-1000 mhz
[Galaxy Ace II Android Development] ChronoMonochrome:
Thanks for this information. I thought we already reverted all BLN stuff. I'll try to find which code causes this derp.

Check with CpuSpy plus, which freqs phone uses. I'm not sure, but CPU OC can became broken for stock.mistake. i didn't read it carefully. CPU OC works fine for me on CM10.2.
[Galaxy Ace II Android Development] exodius48:
Anyone have tried it on vanirasop?
[Galaxy Ace II Android Development] Bilgets:
its able to be used on PA & CM + Derivative, so it maybe able to fit that..
[Galaxy Ace II Android Development] Artha_CR:
[MENTION=5695278]ChronoMonochrome[/MENTION] > thanks for this project..:good: maybe I'll try this kernel for my rom if allowed.. :D
[Galaxy Ace II Android Development] pedroleon99:
Wow man so you are saying you'll update jetstream after a lot of time it was abandoned? It would be awesome [emoji4]
[Galaxy Ace II Android Development] str3tch72:
It'll be awesome with some S5 or S4 goodies :>

But stop OT, latest version working fine with AOSP, stable OC, great performance, great job :>
[Galaxy Ace II Android Development] ChronoMonochrome:
Btw I can't confirn that. I tested the deepsleep as you say(i.e. after charger depluged I just left the phone alone for five hours and found no problem). As far as I can see, it's CM11 software problem.
[Galaxy Ace II Android Development] fluffi444:
Same here... now... I charged again full and no probs during the day... I thing we can leave this behind..

If it ocurs again I will give an logcat... Thanks that you took a look into this...:good:

Righ now I can not say what causes the prob. Maybe some cache remainders from former kernel... don't know...
[Galaxy Ace II Android Development] monstro78:
OK test this.

Full charge your phone. Unplug the charger. Go to CPU spy and reset timers. Screen off. Let the phone with no use so to go do deep sleep.

After 5 minutes check CPU spy. Did it went to deep sleep??
[Galaxy Ace II Android Development] biggstreet:
after 3 days, all i can say is this verry awsome !

Your kernel make the stock rom very useful, Performance for an ace 2 it's Good, battery drain is good also, 3d games run smoothly, no lags, without one time but it was my fault,

THANK YOUUUU (y) REALLY GOOD JOB
[Galaxy Ace II Android Development] shaqman89:
[MENTION=5695278]ChronoMonochrome[/MENTION]

Could you check this logcat please?

I am wondering whether this is something like a too aggressive LMK or something.

So, basically what I am doing is just using some apps, but whenever I trigger something that uses WebView, it somehow goes frenzy and kills almost all apps. Sounds like something with OOM.

Initially, I thought it's because I was using too many apps, and it did dissappear for a while after I removed some apps, but strangely it's still happening, sometimes.

Right now I am using CK 3.8-nodebug, and latest VanirKK.

Thanks for the help.

https://drive.google.com/file/d/0Bzo3MSxg_YFCQ181Z1k4UzdyTU0/view?usp=sharing
[Galaxy Ace II Android Development] ChronoMonochrome:
Sounds like a vanir's webview issue. It might be helpful to set lowmemorykiller debug level(/sys/module/lowmemorykiller/parameters/debug_level) to 2 or higher to see whether apps are getting killed by LMK or something else.
[Galaxy Ace II Android Development] shaqman89:
Where do I see the logs ChronoMonochrome?

I checked kmsg, and logcat and it seems it's not logging.

Does it need to be reboot?

Other than that, is it expected behaviour if network exception (like when a http failed is rejected due to host file blocking) to trigger LMK?

I tried to activate webserver in adaway to reduce network exception in log, and somehow the killing apps by web view doesn't occurs as much as before.
[Galaxy Ace II Android Development] ChronoMonochrome:
Sorry it seems that I forgot to re-enable logging for such modules as LMK after a most debug removal. Maybe will release soon a new version.

It's weird.. Maybe a network exception causes webview to allocate much more RAM than it's actually needs.
[Galaxy Ace II Android Development] shaqman89:
Yeah, I was thinking along that line as well, but can't really prove it for now.

Anyway, it does seems that the web view issue is somehow related to rejected network connections. Now, after half an hour I can't even reproduce the error anymore, but as soon as I let the network exception be, it will soon (usually 1-2 attempts of opening the app that uses web view ) trigger the killing of apps.

Somehow sounds like a memory leak somewhere in the web view.

Edit: anyway, if it's certain that the web view is a ROM bug, I have to say the latest kernel no debug version is really good. Multitasking is way much better, and battery life is better for me. This is even after I add around 10 more apps. And so far, I haven't encountered any issue at all, and that also includes camera. Thanks for your efforts. :)

:good: :good:

One more thing that could be improved (if possible) is the speed of the camera. I wonder if the slow speed of auto focus and taking pictures is entirely sensor related or is there a configuration we can try?
[Galaxy Ace II Android Development] ChronoMonochrome:
New build r3.8.1 is UP!

Changlog:

decreased kernel size (632.3Mb available on standard version and 644.9 on nodebug)

disabled debug FS

decreased boot time a bit by forcing max CPU freq during boot

reverted WS2401 videomode tunables to their defaults(overclock LCDCLK to 57MHz in cases of tearings in 2D graphics)

allowed forcible disabling of the proximity sensor:

echo 0 > /sys/module/tmd2672/enabled

It will disable a sensor until a reboot.

WS2401: allowed more flexible tuning of a wakeup delays.

Here were added two more tunables, sleep_out_delay_1st and sleep_out_delay_2nd. You might want to set sleep_out_delay_1st to 0 to speed up wakeup a bit(echo sleep_out_delay_1st=0 > /sys/devices/pri_lcd_ws2401.0/display_settings ). My config on Omni LP is following

power_on_delay=0
reset_delay=0
sleep_in_delay=50
sleep_out_delay=1
sleep_out_delay_1st=0
sleep_out_delay_2nd=1
display_off_delay=0

Somehow it works stably on 5.1.1, but unfortunately I can't suggest using such config on 4.4.4 - it will cause glitches. If you're using 5.1.1 ROM, you might want to try such config as above.

Enjoy!
[Galaxy Ace II Android Development] ChronoMonochrome:
In some camera apps it's allowed to disable autofocus. It there in a CameraPro, idk, maybe some other apps has this feature as well. As for speed of autofocus itself, probably yes, it's slow due to hardware limitation(please correct me if I'm wrong).
[Galaxy Ace II Android Development] ace2nutzer:
I believe in camera settings it's possible to adjust the focus time ... (on stock camera 4.4.4)
[Galaxy Ace II Android Development] shaqman89:
What settings is that?

I haven't found a setting like so so far.
[Galaxy Ace II Android Development] TheLiquidGuy:
Why did you remove performance governor and I/O scheduler tripndroid? Without them my phone is laggy and super slow. I want them back and until they are back I will use only r.3.6. I don't know what you have changed but it is not good. Even if I set 1200Mhz on min and max still is laggy (CM 4.4.4). I'm sorry but I will not use the new versions until you bring them back again. Sorry for this but I had to tell you.
[Galaxy Ace II Android Development] shaqman89:
I beg to differ. 2.8 & 2.8.1 is really good in my experience, and this is when I'm using dynamic, and only 1100 of frequencies.

Making them not all load automatically have the advantage of lowering boot time, also less RAM usage.

Also, I really don't know why you're upset. Just load the modules automatically on boot. I just tried it out, and performance, and tripndroid is back.
[Galaxy Ace II Android Development] nikolas1274:
You do it yourself,

go to system/lib/modules find cpufreq_performance.ko & tripndroid-iosched.ko copy them to the system/lib/modules/autoload

restart your phone and you will have them back
[Galaxy Ace II Android Development] dixee:
installed r3.8.1 without problem on cm11 again :D

is there any plan to update cm11?

thank you chrono..
[Galaxy Ace II Android Development] ace2nutzer:
in stock camera app: settings ----> extended settings ... then u see 2 different settings for Focus ... but for automatic Focus the smallest Value is 5s
[Galaxy Ace II Android Development] ChronoMonochrome:
Not interesting in this project anymore. Maybe [MENTION=5840412]ace2nutzer[/MENTION] can update it.
[Galaxy Ace II Android Development] ace2nutzer:
Yes, i'm actually working on it ... :)
[Galaxy Ace II Android Development] borkins:
[MENTION=5695278]ChronoMonochrome[/MENTION], if you have time, can you revert the changes in "capacity_level_raw" calculation formula?

Because after kernel r3.0, there is some problem with it. Its value drop, or rises not by 0.1% ( by default ), but with 1% - 100, 99.4, 98.4...

[ The problem with it, is that, the value on charging showing 100%, before 1st termination current, which is not logical.

And also on discharging the value in "capacity_level_raw" showing 0%, before the value in "capacity". ]

Thank you!
[Galaxy Ace II Android Development] ChronoMonochrome:
Okay, will revert this in the next build.
[Galaxy Ace II Android Development] shaqman89:
Chrono, what are the practical use of disabling the proximity sensor? I mean, wouldn't it actually make our phone less useful?
[Galaxy Ace II Android Development] ChronoMonochrome:
In my case, it was a forced measure. Somehow a proximity sensor on my phone became broken(perhaps, after the fall) and no longer works properly. After I receive the call, I was not able to wake the display until a call is ended.
[Galaxy Ace II Android Development] ace2nutzer:
i had exactly the same after the first replacement of my LCD from service. ... temp. fix is to press in the near of the sensors .. then screen wakes up .... try it ;)

But this also sucks, after the sencond/last LCD replacement, it was finally working properly ... maybe u just need to screw up the screws ....
[Galaxy Ace II Android Development] shadow252:
Is there someone like me who thinks that OC DDR don't work on kernel 3.8.1?
[Galaxy Ace II Android Development] borkins:
What is the problem - something specific? You got reboots, or something else.

I tried to OC DDR ( to 975 MHz ) on r3.8.1, CM11, and the OC works.
[Galaxy Ace II Android Development] shadow252:
On OmniLP in terminal emulator using your sh script when typing oc numbers (1,2,3,4) and then pressing enter nothing happens. After that I can press enter many times and still nothing. It's weird because when I select "i", screen with init.d settings shows up. And when I choose "0", script closes. Also tried init.d script and nothing happens, still 798 MHz.
[Galaxy Ace II Android Development] ChronoMonochrome:
Check CPU usage. Script won't OC DDR while CPU usage is too high, because of a high probability of a reboot.
[Galaxy Ace II Android Development] shadow252:
My CPU usage is normal. The only governor I can choose is dynamic.
[Galaxy Ace II Android Development] borkins:
The OC DDR scripts are trying to find the CPU governors "Lionheart", or "Conservative".

And that is my fault, because at that time, I thought that nobody would remove them at boot.

In my tests, I found that these governors are better for finding the moment, when the CPU is less loaded, for more secure DDR OC.

But actually that part ( with the governors ) is not needed anymore. I'll make new update of the scripts.

Hope, that it will remove yours and such problems.
[Galaxy Ace II Android Development] ace2nutzer:
@ up

i never worked for OC DDR .. but it's just very interesting what u guys are developing for that .... i just follow this thread and read the DDR things...

The problems u're describing sounds like that OC DDR can't work stable or properly when CPU Load is high ... well what happens when CPU load is high ? - Usually then APE/DDR OPP are higher than 25-50% ...because of higher CPU freq step. maybe that's the reason...

If so, u can just edit your OC DDR Script that in the time that the script is running in order to change DDR Freq .. it should set min/max CPU Freq @ 200Mhz and so it forces to stay on APE/DDR 25-50% .. now CPU load it doesn't matter .. and this trick should work for every governor ...... after the DDR freq is set, then set again max cpu freq @ 800Mhz .. or try to find a way to restore the custom max cpu freq .. that should more useful ....

UPDATE:

beware that on very high cpu load even on fixed 200Mhz .. it's also possible that the system will change APE/DDR State .. so the real "force" is to set APE/DDR @ 50% manually .... but actually i don't now if it'll stay for ever @ 50% .. after executing this command:

echo 50 > /d/prcmu/ape_opp

and

echo 50 > /d/prcmu/ddr_opp

just found out what is the better way to change this states ...
[Galaxy Ace II Android Development] ChronoMonochrome:
All this is already done - with only exception that DDR and APE OPP states are forced to their maximums while OCing, aiming to prevent a sudden APE/DDR state switch which might cause a crash. But I should admit, this is an interesting idea to force APE/DDR OPP to 50_OPP instead of 100_OPP. The default PRCMU QOS API allows to force maximum states of DDR/APE OPP, but not 50(or 25), and this was a reason why maximum is used instead of a minimum.

P.s. commands above won't work on r3.8.1 due to disabled debug FS. Maybe will later reiplement these interfaces via sysfs, because mostly I don't need the whole debug FS stuff.

Unfortunately, not everything is that simple. From what I remember CPU load (better to use "DDR load" term, but because we can't directly measure DDR load, CPU load is used instead) always mattered, and the much CPU workload (CPU freq * load), the higher chances to get a sudden reboot.
[Galaxy Ace II Android Development] ace2nutzer:
yeah or so . :) Just force it... but to be honest i really don't know how to revert this "forced" OPP states .. i believe only an reboot fixed this.. but of course, then it makes no sense ...

Check: prcmu-qos-power.c if there is an command for "default" ... .. maybe echo "0" or echo "25" will revert to "normal"
[Galaxy Ace II Android Development] ChronoMonochrome:
I believe for the default APE/DDR states is used -1 value. Don't remember though whether echoing -1 to that interface ever worked at all.
[Galaxy Ace II Android Development] borkins:
Well, in my observations while "echo 0", that restore the ape/ddr states.

I tried with all states of ape/ddr opp to oc ddr,

but that is not enough to make the ddr oc more, or fully stable.

In most of my tests the CPU usage is better to be lower than 5%.

The CPU works with the ram constantly, that's why less cpu usage = less ram operations while oc.
[Galaxy Ace II Android Development] ace2nutzer:
well then it looks like that it's not really possible to change this DDR Freq on the fly while the system is working.

Maybe there is an command to freeze all tasks .. = 0% CPU load .. and so also no RAM traffic at all.

If this is not possible, maybe better to make separate builds with overclocked DDR Freq.
[Galaxy Ace II Android Development] ChronoMonochrome:
First is not such simple as said. This condition with frozen tasks is met, when device is right before switching to deep sleep, but it wouldn't simple to make anything this time just because of a critical timings and many other things that should be taken into account. Second is totally not possible because DDR freq is hardcoded in the bootloader, not in a kernel.
[Galaxy Ace II Android Development] heldix:
I suffer from a problem that appeared suddenly. Every 5-10 Seconds i get the message "google play services has been shutdown, press ok" (bad translation sry). The only workaround is to put GPS to "only device". But then google maps isnt working anymore.

This problem really came from the sudden. I tried reflashing codina and kernel. Still persistent.

I really dont wont to again wipe to whole device.

Thx in advance, heldiX
[Galaxy Ace II Android Development] shaqman89:
This is a real old issue, afaik.

Did you block the permission of keep awake and wake up for play services?
[Galaxy Ace II Android Development] heldix:
Yes i did. I tried switching it off and on. No solution. The only thing that kinda helps is setting GPS to "only device".
[Galaxy Ace II Android Development] shaqman89:
Try to setting it to keep awake allow, wake up disallow
[Galaxy Ace II Android Development] xo.en:
+1, I laughed so much :) nice, nice....funny set of words...
[Galaxy Ace II Android Development] shaqman89:
I know ? . As strange as it sounds, it worked in my case.

I've got none fc at all this last two weeks, and that's with any GPS mode.

After thinking of it, it kinda makes sense.

Note the word, 'kinda' :D
[Galaxy Ace II Android Development] Culateralligator:
There was a temporary fix for CM11. What ROM are you using?

It also works at least on AOSP 4.4.4. Have you seen it?

http://xdaforums.com/showpost.php?p=61034998&postcount=230
[Galaxy Ace II Android Development] heldix:
Hi! Works like a charm! Dont know whether its really this specific setting or just time solved it.

Thank you mate. I'll check this one out in case i get this problem again!

heldiX
[Galaxy Ace II Android Development] shaqman89:
In my case, it's that specific one. Turn both off and the issue would come back in minutes.
[Galaxy Ace II Android Development] jadega:
[MENTION=5695278]ChronoMonochrome[/MENTION] Since Ace 2 and Galaxy S Advance shares almost same Hardware so can you build this Kernel for S Advance too :)
[Galaxy Ace II Android Development] ChronoMonochrome:
I could try, but I need some assistance of testers. I even have a build script version modified for this device, but the most problem is adapting of an installer(and without some logs it's unlikely that I can fix it). So, if you or anyone else from Janice forum is interested in that, PM me.
[Galaxy Ace II Android Development] ChronoMonochrome:
New build r3.9 is UP!

Changelog:

SuperUser replacement: implemented God Mode V1.0

This feature enables an unautorized user to access/modify/execute files which usually only root is allowed to. What are benefits of using this feature instead of supersu? Seeing how slowly responding SU to its requests I decided to allow avoiding SU usage at all, aiming to improve performance which usually is decreased when some operations being done using SU (as example writing or deleting files from system partition).

You can blame me in security worsenings (since with god mode ON every app can, literally speaking, do everything it want), but remember that I wrote this feature mostly for myself and I don't enforce using this mode(by default it's disabled).

How to enable this feature?

echo 1 > /sys/kernel/god_mode/god_mode

Only do this if you know what you do!

Freed some more RAM by implementing a dynamic memory allocations for modem through memblock API

On nodebug version currently 649.4 MB RAM is avalaible, debug one should also have +4.5 MB RAM more. Currently it's in a testing, but so far I didn't notice any side effects.

Most of this memory is still in use by a various devices, so there is still remained some work to do.

Two interfaces provided to forcibly close/free up resources of those devices:

echo x > /sys/module/shrm_char/parameters/shrm_close_by_idx
echo x > /sys/module/shrm_char/parameters/shrm_free_by_idx

x - number of device, 2-9, excluding 7.

Note that this isn't well tested and is not recommended to do since it might end up with reboot or another side effects.

Most reason of writing this feature for me was learning some usage of a dynamic memory allocations(so maybe later HWMEM can be switched to DMA as well).

Kernel clean up, removed unused code, small fixups

Patch-set for ARM CPU Topology (improvements of SCHED_MC power savings)

Adjust HZ to 400

HWMEM: small update from Sony xperia u8500 devices

Full changelog
[Galaxy Ace II Android Development] shaqman89:
Sounds good :)

If using this, would there be any conflicts with supersu? I mean, is it better to disable afterwards, or just letting it be should be fine?
[Galaxy Ace II Android Development] heldix:
Has someone already downloaded 3.9? I cant find it on the ftp. Is it just me or is this version located somewhere else?

heldiX
[Galaxy Ace II Android Development] shaqman89:
I have. It's inside the normal ftp directory.

Edit: strange, it's not there anymore. [MENTION=5695278]ChronoMonochrome[/MENTION], did you removed it?
[Galaxy Ace II Android Development] ChronoMonochrome:
I did remove it as I encountered a weird issue with apps data loss after a reboot. New build build will be uploaded soon, sorry for an incovenience.

It should not have any conflicts with supersu. It works more or less transparently for an user.. Only issue I found that I could not edit sysfs files directly from X-plore file manager (gave ENOENT error with a no reason), though terminal works properly.

UPD. Uploaded a fixed versions. These builds has a bit less RAM, but hopefully should work properly now.
[Galaxy Ace II Android Development] shaqman89:
Umm. Noted. I'll revert back to previous version, just to be safe.

Thanks for the heads up.
[Galaxy Ace II Android Development] shaqman89:
[MENTION=5695278]ChronoMonochrome[/MENTION]

The 3.9 kernel installation had some issues in my case. First of all, it seems that it was stuck in a bootloop (waited for 10 minutes and nothing) after first install. Assuming that the installation might be corrupted or something, I reflashed the same zip and then it was successfully booted.

Now I am using the 3.9 after the fixed you mention, and it had the same issue as above. Did a reflash, and then it successfully booted, only this time it seems the whole system got FC and then it soft-rebooted itself. Again, it got stuck in a bootloop. So, I went into recovery again, reflash 3.8.1 and then reflash 3.9 twice. Now it worked and rebooted normally, but I got a warning saying "Vanir - Inverted failed to install". Other than that, it is working normally.

Unfortunately, this is the non debug version, so no kmesg.

Update: It also caused imei number to dissappear thus disabling call and sms functionality.
[Galaxy Ace II Android Development] ChronoMonochrome:
It might happened that data partition was already corrupted after an installation of a non-fixed version of build. I had to restore TWRP backup, so far testing - did a several reboots - don't encounter this issue anymore.
[Galaxy Ace II Android Development] ace2nutzer:
It's also very important to format /data before restoring the backup ... (Dunno if twrp or cwm do this automatically) in order to repair also filesystem errors.. (If there are any)
[Galaxy Ace II Android Development] ChronoMonochrome:
Once again I had to reupload latest build because issue with data loss seemed to persist. It was a really bad idea to switch modem to dynamic memory allocations, it crashes causing data corruption. For now this is reverted to a standard code with a static memory allocations. My apologies..
[Galaxy Ace II Android Development] shaqman89:
Chrono, how was this data lost actually? Was it the whole data partition or just some apps?

I thought I didn't experience any, but it turns out I've lost my chat history in whatsapp. No big deal, since I've got backups, but I just thought it as strange behaviour.