yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] ace2nutzer:
Fo me it's working great.

It works only if u plug the charger during screen ON ... later u can turn the screen ON with dt2w.

It works also if u're playing music with screen OFF ... or u're using OG-YouTube App with screen OFF...

It also works if u'll use any live stream app with screen OFF .. i.e. Radio stream ...

works perfectly here.

Then only thing what is not working is just when BLN is ON or blinking .. (due of notification) and the dt2w is actually not working...

we're trying to find an solution.

But to make it fully working u've to activate the wakelock ... but then there is no deep sleep at all :)
[Galaxy Ace II Android Development] junnickbefore14:
Is it possible to have multiple zram in our device?
[Galaxy Ace II Android Development] ChronoMonochrome:
It's possible to have a multiple zram blocks but IMO it makes no difference at all being compared with an one block with the size, equivalent to a summ of sizes of a several blocks. It's also possible to use a several compression streams(instead of multiple zram devices), but I haven't actually tested it. If anyone wants to test it:

echo ? > /sys/block/zram0/max_comp_streams

? - number of streams. This number must be set before a zram device initialization.
[Galaxy Ace II Android Development] junnickbefore14:
So in our case, there are 2 cpu cores..

Should I write 2 there?

Edit: well, it doesn't work, the value remains 1

Anyway if it possible to have multiple zram blocks, how to do that?

Since I just turned on hyperthreading in my netbook and there are 2 zram blocks, well i see a positive performance improvement..

Hehe

Anyway thanks for your quick response :thumbup:
[Galaxy Ace II Android Development] ChronoMonochrome:
Probably yes, but it might require a testing to determine whether it's appropriate.
[Galaxy Ace II Android Development] junnickbefore14:
I have a question...

My device doesn't have any module named zram.ko and why I still have zram enabled?

Chrono kernel r3.7 AICP android 5.1.1
[Galaxy Ace II Android Development] ChronoMonochrome:
Zram driver is built not as module, built-in. Check your init.d scripts if you want to disable it.
[Galaxy Ace II Android Development] ChronoMonochrome:
New build r3.7.1 is UP!

Changelog

touchscreen freezes fixup

dt2w/s2w slight code optimization, also exported some dt2w tunables to an userspace

merged [MENTION=5840412]ace2nutzer[/MENTION] recent fix for blackscreen issue on S6D

optimized WS2401 video mode tunables - thanks to ace2nutzer

probably fixed LPM blackscreen issue on S6D (not tested)

Full changelog
[Galaxy Ace II Android Development] gothicVI:
Is the kernel app still compatible?

Gesendet von meinem GT-I8160 mit Tapatalk
[Galaxy Ace II Android Development] ChronoMonochrome:
Yes, but it misses some recently implemented features (LMK management, wakelocks white-/black- list, playback control feature and maybe some more).
[Galaxy Ace II Android Development] LyrixTheDj:
Can't receive notification about SMS until manually (wake up) turn on display on r3.7.1

UPDATE: For experiment decided try OmniROM 5.1.x by your, with kernel r3.7-dirty inside. So, same issue. If phone with screen off and no "active mode" (deep sleep?), have no notification about SMS, if presence "active mode" (wifi is on or some APPs work in background) all notification work fine.
[Galaxy Ace II Android Development] Kiras_PL:
Yep, the same here :/ I think that deep sleep step = 4 is too much. Please take a look in it.
[Galaxy Ace II Android Development] ChronoMonochrome:
Sorry, that was my bad. I can assure, it's not due to deepest sleep state 4, it can work perfectly here. Maybe will upload an update soon.
[Galaxy Ace II Android Development] ChronoMonochrome:
New build

New build R3.8 is ready to go!

Changelog:

speed up display wakeup time on WS2401

There is probably possible some more speedup, which may or may not work stable, but so far I decided to stick with this config.

You can play around wakeup delays, which are exposed in a file /sys/devices/pri_lcd_ws2401.0/display_settings

example:

echo sleep_out_delay=15 > /sys/devices/pri_lcd_ws2401.0/display_settings
echo power_on_delay=40 > /sys/devices/pri_lcd_ws2401.0/display_settings
...

Stability of these delays seem to depend on a LCDCLK freq. I was able to achieve a following working config

echo 0 > /sys/kernel/mcde/lcdclk
echo sleep_out_delay=5 > /sys/devices/pri_lcd_ws2401.0/display_settings
echo power_on_delay=20 > /sys/devices/pri_lcd_ws2401.0/display_settings

by increasing lcdclk freq to 57MHz.

kernel scheduler: disabled some unneeded sched features(better battery life)

various fixes/improvements from android mainline kernel

fixed notifications not being received issue

RAM console auto-correction

Since this build there are two kernel version are available:

chrono_kernel_r3.8.zip - a standard version, 632Mb RAM available

chrono_kernel_r3.8-nodebug.zip, version without RAM console enabled and with reduced HWMEM size - ~645Mb RAM. This is currently considered as an experimental version, please note that.

Full changelog

Enjoy!
[Galaxy Ace II Android Development] shaqman89:
ChronoMonochrome, what is this RAM console is actually for?

I'm gonna try the experimental one, but wondering what functionality is at risk without that RAM console.

If I understand it correctly, I won't be able to get kmsg?

Anyway, really impressive change log. :good: :good:
[Galaxy Ace II Android Development] ChronoMonochrome:
You only won't be able to get last_kmsg. RAM console persistently use 1 Mb(and unfortunately it seem there are no way to reduce it), so I was thinking it would be a good idea to have version without it...
[Galaxy Ace II Android Development] LyrixTheDj:
Now i'm use CM 12.1 with r3.4 all was fine, until i installed ChronoKernelSettings-0991-beta.apk (from backup of CM11). Now again have no notification in deep sleep. (In Chrono settings deep sleep = 3 default). But i find one thing: when enable than disable and again enable BLN from APP, notification work from deep sleep. May be it is same in CM11 (r3.7), i will try to check this later if will be have enough time.
[Galaxy Ace II Android Development] shaqman89:
I see. Well, hopefully I won't be needing to get a last_kmsg then.

Anyway, installation went smoothly, and now I've got 644mb of RAM, with a boot time of 7330. Really impressive :)

Anyway, I'll give it a test and hopefully the experiment will go Okay.
[Galaxy Ace II Android Development] xo.en:
When this bug was introduced, which kernel version had it, first?

This is VERY important for me to know.

Here's the thing - I felt that I am not receiving unanswered calls notifications after waking machine from airplane mode, obviously - it is a SERIOUS problem..I simply have no notifications, zero....shoudn't my operator's info about unanswered calls show as notifications?

I think it f'ed up my relations with my father, since he tells me that he called me and i do not know this next day I turn cell on....you know..
[Galaxy Ace II Android Development] ChronoMonochrome:
It was r3.7.1 r3.7.
[Galaxy Ace II Android Development] xo.en:
...hm..I hope so, I am still uisng some older one(than 3.7.x)..But I am still worried, it really happens for me, not sure about reason of that..quirk.

If it is my operator issue, then it is seriously f'ed up situation...since I simply do not know, if someone called me, when I am turning airplane mode off, ffs.
[Galaxy Ace II Android Development] ChronoMonochrome:
Have you tested r3.8? It works here for sure...
[Galaxy Ace II Android Development] xo.en:
Will do, thanks for your work, man.
[Galaxy Ace II Android Development] LyrixTheDj:
I confirm. r3.8 notification work well after 2 hours in deep sleep (no active mode in battery stat) on CM 12.1_r6.

Благодарю!
[Galaxy Ace II Android Development] ace2nutzer:
@ Chrono

this was the notification problem ?

https://github.com/ChronoMonochrome/Chrono_Kernel-1/commit/bfa3620e0367b78eefb32d833d759dec194738aa
[Galaxy Ace II Android Development] ChronoMonochrome:
Yep, that was kinda stupid and thoughtless decision :P

It was even worse that didn't notice it immediately since I rarely recieve/send SMS.
[Galaxy Ace II Android Development] ace2nutzer:
Noo ... that just things what can happen when we're trying to reduce the power consumption more than possible :D

We're breaking all levels... after one Year of extra development... i'm still wondering that we sometimes still found some tweaks in order to increase the performance or just decreasing the power consumption. Not so bad ! Ace2 never die !
[Galaxy Ace II Android Development] xo.en:
Weird - I am unable to connect machine with PC, zero reaction, cards are not visible.

Hmm, also - LAN connection by total commander with pc crashes app now....

..oh god, twrp cannot see cards, again....what was that file name to fix this, again?

hm, twrp.fstab is present in /ramdisk...
[Galaxy Ace II Android Development] shaqman89:
Works fine for me. Using the latest experimental version with vanir.
[Galaxy Ace II Android Development] xo.en:
upd: ok...my backup disappeared, so nvmd..

Also, reinstalling kernel had wiped my issues so far.

Weird.

Now I am using nodebug version.
[Galaxy Ace II Android Development] shaqman89:
Do you have issues regarding web view with the no debug version?

I seem to have an issue, but I can't really say if it's because of kernel changes or something else? The issue that I mean is that it triggers OOM, and thus killing all previous apps.
[Galaxy Ace II Android Development] xo.en:
You mean browsing?

No, I do not have any issues for now, but I am using my own lmk/vm settings...and ondemandplus/zen.
[Galaxy Ace II Android Development] shaqman89:
No, not when browsing actually. But when logging in to Facebook on some apps. It loads web view on a floating window, and that did caused OOM.

But it was an issue of OOM. I had like 120 apps with some 40 of them having services. After I cleaned up some of those services it works normally.
[Galaxy Ace II Android Development] xo.en:
Ahh, so you overloaded our poor a2 then...
[Galaxy Ace II Android Development] shaqman89:
Lol. I actually am wondering what's the limit of this phone.

So far with 100+ apps with the right configuration, it works quite well, as long as I avoid the hungry RAM apps.

I do have to admit the tweaks from ChronoMonochrome and ace2nutzer are big.

On the beginning I can't use 40 apps comfortably, but now it's loaded with 100+ of apps, and the phone is still comfortably usable. Just wow.
[Galaxy Ace II Android Development] xo.en:
It's all about background services, "passive" apps are neutral to this.

I am not user of instagrams, facebook apps, gapps and I've never encountered OOM situations(even with 176 apps loaded into this device, lol).

Btw, apk named DisableService helps to keep unneeded services on a leash(you know, things like billingservice, campaigntrackservice and so on).

Also, I'd recommend finding small, funny app named fastreboot(34kb or so).

Click, boom, lots of mem is freed in gentle way.

btw, my settings, init.d:

#!/system/bin/sh
#chmod -R 755 /system/etc/init.d
chown root:root /proc/sys/vm;
# 1. Main vm tweaks.
echo "30" > /proc/sys/vm/swappiness;
busybox chmod ugo+rw /proc/sys/vm/vfs_cache_pressure;
echo "50" > /proc/sys/vm/vfs_cache_pressure;
echo "2000" > /proc/sys/vm/dirty_expire_centisecs;
echo "1500" > /proc/sys/vm/dirty_writeback_centisecs;
busybox chmod ugo+rw /proc/sys/vm/dirty_ratio;
echo "90" > /proc/sys/vm/dirty_ratio;
busybox chmod ugo+rw /proc/sys/vm/dirty_background_ratio;
echo "75" > /proc/sys/vm/dirty_background_ratio;
# echo "0" > /proc/sys/vm/dirty_bytes;
echo "512" > /sys/devices/virtual/bdi/default/read_ahead_kb;
echo "10" > /proc/sys/fs/lease-break-time;

# 2. Misc vm tweaks.
echo "4" > /proc/sys/vm/page-cluster;
echo "5360" > /proc/sys/vm/min_free_kbytes;
echo "8" > /proc/sys/vm/min_free_order_shift;
echo "0" > /proc/sys/vm/oom_kill_allocating_task;
echo "1" > /proc/sys/vm/overcommit_memory

busybox sysctl -w kernel.random.write_wakeup_threshold=256;
busybox sysctl -w kernel.random.read_wakeup_threshold=1376;

#!/system/bin/sh

chmod 0644 /sys/module/lowmemorykiller/parameters/adj
echo "0,3,6,10,12,15" > /sys/module/lowmemorykiller/parameters/adj;

chmod 0644 /sys/module/lowmemorykiller/parameters/minfree
echo "1024,2048,2560,4096,6144,8192" > /sys/module/lowmemorykiller/parameters/minfree;

chmod 0644 /sys/module/lowmemorykiller/parameters/debug_level
echo "0" > /sys/module/lowmemorykiller/parameters/debug_level;

Of course, they may be obsolete now, but work fine for me, just that.
[Galaxy Ace II Android Development] shaqman89:
Yes, that's true :)

Disable service was what I used to manage the services when I had OOM. So, I could still use all of the apps to my needs.

Wow. You use more apps than I do lol.

I wonder, how do you manage the between ROM flashes? Titanium backup?

Fast reboot? Isn't that the same functionality as soft reboot on ROM?
[Galaxy Ace II Android Development] xo.en:
Nah, I was talking about my first experiences with this machine, I literally installed everything I found, lol.

Now I have small batch of most needed apps for daily use...

About fastreboot - I will post that apk later, since there's another one named like this(that one is BAD). You will try...

upd: that one:

http://speedy.sh/gty6V/com.greatbytes.fastreboot.apk
[Galaxy Ace II Android Development] PolishVodka:
Chrono

Is a possible to load custom recovery cpio from /preload partition? But I'm not talking about removing from kernel image stock recovery, but I wanna add a possibility to load custom recovery if "something=true on /preload + is recovery.cpio here than load it".

I was trying to make this like you for kernel2 partition (in init script) but something is wrong and kernel cannot boot at all, no custom recovery, no stock recovery and no boot.
[Galaxy Ace II Android Development] gothicVI:
I had really awful battery drain after flashing [MENTION=4881398]PolishVodka[/MENTION]'s 20.09 cm 12.1 build that got paired with a lot of systemui fcs after flashing 3.7.1 but 3.8 seems to fix it. Thx [MENTION=5695278]ChronoMonochrome[/MENTION] [emoji2]

Gesendet von meinem GT-I8160 mit Tapatalk
[Galaxy Ace II Android Development] ChronoMonochrome:
In short - yes, it's possible.

Depending on how do you do it... Maybe you have unpacked both recovery images(or neither of them), what messed up all things.

Try to override load_image here: https://github.com/ChronoMonochrome/Chrono_Kernel-1/blob/master/usr/u8500_initramfs_files/init#L71

busybox mkdir -p /preload
busybox mount -t ext4 /dev/block/mmcblk0p9 /preload
if busybox test -f /preload/recovery.cpio.gz ; then
load_image=/preload/recovery.cpio
fi

Make sure that later your init script have following:

if busybox test -f ${load_image}.gz ; then
busybox zcat ${load_image}.gz | busybox cpio -i -u
fi

Thus, /preload/recovery.cpio.gz will be loaded instead of /preload/recovery.cpio .

UPD. also remove /preload from fstab file, since /preload already mounted in init script and will fail to mount again.
[Galaxy Ace II Android Development] PolishVodka:
I was doing the same but without mkdir preload, and recovery image isn't gzip'ed, just recovery.cpio.
[Galaxy Ace II Android Development] ChronoMonochrome:
Then there is only possibility to know, what went wrong, is to look into file boot.txt. Copy boot.txt to somewhere after this line ( https://github.com/ChronoMonochrome/Chrono_Kernel-1/blob/master/usr/u8500_initramfs_files/init#L99 ), e.g.

busybox cp /boot.txt /ramdisk/boot.txt

Also, last_kmsg might be helpful.
[Galaxy Ace II Android Development] ace2nutzer:
:good:
[Galaxy Ace II Android Development] heldix:
I tested the 3.8 no debug. Scrolling in my favourite news app (SPIEGEL online) is much much less smooth now. With 3.7.1 it was like super smooth (like the versions before too). Now scrolling still works but much more stuttering. Its like 20 fps now while scrolling before worked with ~50fps.

Wiped cache/dalvik before .Didnt change settings from 3.7.1 to 3.8.

Greetings, heldiX
[Galaxy Ace II Android Development] ace2nutzer:
probably wrong video.modes or lcd_clk
[Galaxy Ace II Android Development] borkins:
I'm still on r3.7.1 and think, that it's more smooth than some of the older versions.
[Galaxy Ace II Android Development] shaqman89:
I don't actually feel that it's more sluggish per se. But I agree that at times it could be really slow. But at most of the times, it's quite smooth.

Anyway, I think 3.8 is better overall since it drains less battery (in my case) and also more ram means I could switch between more apps more comfortably.
[Galaxy Ace II Android Development] kuba130000:
If the latest version will work with stock ROM? ;)

nevermind, I found info in 1st post :P
[Galaxy Ace II Android Development] heldix:
I'll stick with the 3.8 for now too. The worse scrolling performance isnt to important too me.
[Galaxy Ace II Android Development] ace2nutzer:
Fix Laggs

As for Laggs or weird performance on scrolling.. use such Tunables:

[WS2401]

LCD Freq: 57Mhz (echo 0 > lcd_clk)

video_mode.hbp = 8 (echo hbp=8 > mcde_chnl) + (echo update > mcde_chnl)

video_mode.hfp = 8 (echo hfp=8 > mcde_chnl) + (echo update > mcde_chnl)

Not best possible solution, but better than actually default Values.

[S6D27A1]

LCD freq: 44Mhz (but because 44Mhz is missing here, use 33Mhz instead.... (echo 4 > lcd_clk)

Best solution (with 44Mhz)
[Galaxy Ace II Android Development] xo.en:
What is this about MHz there?

I cannot get it, is this some other thing than Hz and screen refresh value there(i.e. 60Hz for s6d)?

Just cannot get it tbh.

I am using chronokernel with s6d, 60Hz and I have perfect scrolling, what do you mean by using MHz?

Is this something independent from screen refresh?

Btw, how can I check what value I really have then(that you are talking about, specifically)?

Any lag I have seen was related to bad lmk/vm values so far tbh.

I am not here to argue, just cannot get what are you talking about, just that.
[Galaxy Ace II Android Development] ace2nutzer:
check sysfs lcd_clk ... it should be in /sys/kernel/mcde .....

Yeah it's refresh rate (approx.) .. 40Hz is = 33Mhz

See:

https://github.com/ChronoMonochrome/Chrono_Kernel-1/blob/master/drivers/video/mcde/mcde_hw.c#L1219

btw: 60Hz = 50Mhz .. and i know, it runs really good ... but it's very high overclocked ... and drains max. power.

But 44Mhz works even better (as well) .. and at the same time it drains a bit less power ;)

I think Chrono will implement this missing freq on next build :)
[Galaxy Ace II Android Development] xo.en:
Damn, this is tricky..

Hm I have 49920000 there now...so it is 60Hz,

39936000 is for 50Hz.

Mmmm, good to know, that chronokernelsettings works fine then, yet, it has not 44Mhz setting(I have no idea about kernel, though)....

So, for s6d I should leave 50Hz, yes?

Damn, if it is real 50Hz, it would help Amiga emulation, then(PAL).

p.s. so sad, that chronokernelsettings is not updated anymore, it is lacking few of freq's...damn....I checked link that you posted and now I can see how it works, need to check, if freq tables are stored in editable format there, OR if it is probing kernel capabilities(second option would be the best).
[Galaxy Ace II Android Development] ace2nutzer:
49920000 = 49,92Mhz ... the Values u see are in Hz ... but again it doesn't mean the real Refresh rate in Hz .. what u know from PC Monitors ...

Here on the Phone it's bit different.

Stock S6D ist 30Mhz ... so u've overclocked 30 @ 50Mhz ... this is really high... but usually nothing can happen as long it runs stable...

If u'll get screen freezes, then u know why ;) :D

For me 50Mhz is max stable .. i can't use 57 on s6d ... it's simply too much.

So for now, u can keep the 50Mhz ... it's smooth... if next build will have 44Mhz ----> 55Hz ... then use this.. works slightly better ;)

For who want to save battery.. use as i said 33Mhz instead for now.

---------- Post added at 10:40 PM ---------- Previous post was at 10:27 PM ----------

I'm not sure.. but i believe that u're able to use an custom lcd freq on chrono kernel... ..even if the freq is not in the table...

of course if the freq is valid ....

Check my Table:

https://github.com/ace2nutzer/Samsung_STE_Kernel/blob/3.0.101/drivers/video/mcde/mcde_hw.c#L1199

So u can try to set this 44Mhz freq like this:

echo 44373333 > lcd_clk
[Galaxy Ace II Android Development] xo.en:
Thanks, great info.
[Galaxy Ace II Android Development] ChronoMonochrome:
echo lcdclk=44373333 > lcdclk

is correct.
[Galaxy Ace II Android Development] heldix:
[MENTION=5840412]ace2nutzer[/MENTION]thx for the solution ill try it later the day.

Did some performance test with Antutu:

View attachment 3501613

View attachment 3501614

It seems that everything is running well. My i8160 @ 1000 is faster than stock in every part. Except for 3D performance. Dont understand that, because i havent touched any setting within the Mali part of chronokernel. But 3D doesnt matter to me too much, so its fine.
[Galaxy Ace II Android Development] ChronoMonochrome:
But besides of GPU freq there are some more tunables such as DDR/APE OPP states. Also GPU performance seem to highly depend on CPU governor due to current implementation of DDR/APE OPP switching mechanism.
[Galaxy Ace II Android Development] xo.en:
All my issues are gone with newest(modded) vanir+newest chronokernel so far.

Meanwhile, I made some moronic tests:

11871 antutu pts. @ 800 mhz,

13581 @ 1gHz,

14230 @ 1.1gHz(Oo),

14794 @ 1150mHz,

crash @ 1.2gHz.

Ondemandplus+sioplus, ddr_opp 25, APE_OPP 25, lowered voltages for cpu/gpu, gpu set to 256-480mHz(since our gpu just sucks), hmm, not bad, not bad at all...

Setup made for ebooks reading(200-800mhz) mainly...

Only drawback of latest Vanir - Nova 4.x.

While it is easier to keep trebuchet to allow user to add nova 3.x, we have no choice there...

Nova 4.x is f'ed up, if you prefer dark colors.
[Galaxy Ace II Android Development] RootPegasus:
I cant installing DEODEX ROM with TWRP, he say "no md5 file found", but with CWM it;s normally no error ,,,

any solution ?
[Galaxy Ace II Android Development] biggstreet:
a use I8160XXMG2 deodexed rom, and kernel 08/08/2014

with Cocore manager

OC 1200 - 100 conservative noop

OC GPU 580

everyting is ok !

my score in antutu
[Galaxy Ace II Android Development] xo.en:
Dude...

http://xdaforums.com/showpost.php?p=54035112&postcount=201

No gpu oc, old rom. It doesn't proove anythin'/

You just need to feel this machine.
[Galaxy Ace II Android Development] biggstreet:
sorry but can you explain me

I understood nothing, sorry i dont speak english verry well so ... :(
[Galaxy Ace II Android Development] danny19901:
I recently updated from 3.1.1 kernel to latest 3.1.10 and I have really bad battery life and doesn't seem as smooth I flashed over the top no wiping is anyone else having same things ?
[Galaxy Ace II Android Development] farru1981:
I confirm it, but in fact the stability for me it's much better.

I am sure that in further releases battery life will get improved. :fingers-crossed:

regards,
[Galaxy Ace II Android Development] ChronoMonochrome:
@up, a few pages earlier have written that battery life is OK. Understand, it depends on the settings of CPU (not only min/max freq but and governor too), GPU, screen brightness, etc. and activity of use.

Here you may be right. Because I plan to decrease the voltage of display, WiFi, and other stuff. I do not know whether this is the appropriateness, and will benefit from it, but I want to try.
[Galaxy Ace II Android Development] Asus-Tek:
I use last kernel and my anutut skore is low 8500. When I used stock kernel from CM11 TC 4.4.2 my untutu was 10100 and max 10300.

Where is the problem?

CPU 100 - 1Ghz -- noop and pegasusq

GPU 540Mhz

I did not do wipe cache only flash kernel via CWM and reboot.