yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] Alwer:
Few pages back, I saw somebody had problem with formatting cache I think it it because min volume size supported is 104857600 :)

BTW on stock, new kernel works superb also on cm11, but still no luck on 10,2 :D
[Galaxy Ace II Android Development] xo.en:
Let's talk about this...you know, i am rather layman in math, so..is this one too small? Shouldn't be...though, i cannot format it.

Hmmm.
[Galaxy Ace II Android Development] Alwer:
I had same size cache as You - and same problem, now I have 150 mb and no problems with formatting. But I think that 120 mb also will work :). And I know that is surprising that about 110 mb is still not enough, but that value in fact was message error when I try format cache in adb, also You can try look at log in cwm after format cache (advance menu).
[Galaxy Ace II Android Development] xo.en:
Tell me, can You see any significant difference with f2fs over default filesys?
[Galaxy Ace II Android Development] Alwer:
[MENTION=5933530]xo.en[/MENTION] It is hard question. To be honest, from one side I didn't use Mono ext4 kernel on CM11, but on other side my first impression after clean install Rox CM with Mono f2fs kernel (and 25 apps that I use in everyday life) was - something like - " s**t it's way to fast for me" ;). But now I'm testing ART so in fact I had little chance know better how 'clean' f2fs works.

Despite my lack of experience I can say that f2fs will be on my phone for months. And I can not say that about ART I try this mode few times earlier and every time makes my phone laggy as hell. Surprisingly now its work smooth and really fast, but sometimes its freeze for 2-5 sec - hope that ART is responsible for that not f2fs).

Summing, I think that f2fs is definitely worth a try :)
[Galaxy Ace II Android Development] xo.en:
So, f2fs have more sense with art, than with dalvik?

Hm, maybe it's flushing that way(it may be optimizable then)..
[Galaxy Ace II Android Development] Alwer:
No I do not think is connected, but many people says that ART is faster then Dalvik so once again I gave it a try :).

PS Sorry for confusing You - my English isn't as good as it should be.
[Galaxy Ace II Android Development] acrocosm:
I'm using this kernel with latest PA rom. It's unbelievably smooth and fast, almost like I bought a brand new superior phone. But something causes insomnia to my phone. I get about one day out of this combination. about 2/3's of that time without deep sleep.

Wakelock detector with advanced settings enabled doesn't point out the culprit. How can I nail the cause? Any suggestions?
[Galaxy Ace II Android Development] 10BIT:
Successfully installed f2fs on latest omni,do i need to format /data and /cache to f2fs again when i want to install a new ROM?
[Galaxy Ace II Android Development] ChronoMonochrome:
I believe it's not related to kernel. Try to install deep sleep battery saver(or same module for xposed) or similar app.

I don't think it's necessary. Probably wipe cache is enough.
[Galaxy Ace II Android Development] monstro78:
Wow great performance. I'm with latest PA and art.

Thinking to go to f2fs just for testing
[Galaxy Ace II Android Development] ace2nutzer:
When u make every time a ROM or kernel Update WITH F2FS than, all is ok and u have always F2FS to data and cache..

But if u change the rom without F2FS support then u need to format data and cache @ EXT4 and then u can restore your CWM Backup ! That works !
[Galaxy Ace II Android Development] ChronoMonochrome:
New version is UP! :)
[Galaxy Ace II Android Development] zizoumadrid:
wifi doesn't work in stock rom 4.1.2 with latest build 0408
[Galaxy Ace II Android Development] ChronoMonochrome:
Please check again. I already reuploaded fixed build.
[Galaxy Ace II Android Development] xo.en:
4.3.x, liq, dirty flash.

My "report" is not important, but...

- VERY weirD tearing, here and there, this kind is new for me - since cm10.1 there was tearing - it occupied area next to hardbuttons - new kind is..crawling all over screen, randomly, BUT, i can feel, that it's generally good progress, because, sometimes i feel that insane gb feeling of fluidity.

BUT - at this stage it is unbearable and frustrating, like screen was at edge of total sync loss.

Still cpu in perfctrl cannot set up second core at all and it's only kernel with such interesting effect..

I try to check how would kk kernel behave, when i get kk liquid(clean flash, full wipe)..
[Galaxy Ace II Android Development] ChronoMonochrome:
@up, I really do not know than it can be caused. I've never got anything like this.
[Galaxy Ace II Android Development] pedroleon99:
I confirm now all is working perfectly wifi included. But why the 1000 Mhz step changed to 998?

Just curiosity
[Galaxy Ace II Android Development] Ave_Hornet:
I have great battery life on R2.19.3 im using it 2 days with cm12 [MENTION=4881398]PolishVodka[/MENTION] AKA Straciatella and i have 62 %. (4,3h screen time) I use phone to browse the internet . sometimes playing the game. and it is a good result for already 3 years old phone: D . previously held up to 8-12 hours . I am very Happy , thanks [MENTION=5695278]ChronoMonochrome[/MENTION]
[Galaxy Ace II Android Development] ace2nutzer:
I think this is due to default clock 50MHz for lcd .. it makes a difference for ca. 10% of power consumption..

Stock TC Clock was 57MHz ... only 7MHz difference ... but that change is also affected on refresh rate for lcd ... that's the reason ... ;)
[Galaxy Ace II Android Development] monstro78:
2.19.3 is good. Better from previous versions 2.19.x
[Galaxy Ace II Android Development] fluffi444:
Is there any reason not to run 60+ or 60++ in mcde_lcdclk?

I understand that standard is good for most and powersaving but can 60+ or 60++ damage something?
[Galaxy Ace II Android Development] ChronoMonochrome:
Probably it can damage to LCD. That's why those modes marked in mcde_lcdclk as unsafe.
[Galaxy Ace II Android Development] ace2nutzer:
Usually only wrong configured timings / refresh rate etc. can damage the LCD ..

i think 50 & 57Mhz is safe enough, but i don't know exactly wich refresh rate we will have .. such things like 60+ 60++ etc serves nothing... a precise refresh rate is important.. till now i found some (maybe) useful informations all about LCD:

1. we can calculate max. possible refresh rate by this way (just approxx but works) Pixel Clock / 2,25 = theoretically max. stable refresh rate... that means we've a pixel clock freq of 160Mhz / 2,25 = approxx 70Hz is possible on our phone

(probably we're using actually 60Hz with 50mhz of lcd clock)

2. On Stock GB and JB Sources the LCD clock is @ 50Mhz but on JB we have laggs + screen tearings.. also on CM11 ....

3. Rox did a commit in July 2014: "Fix screen tearings" and he set the LCD Clock @ 57Mhz. - From this Point the tearings + laggs was fixed. - But the "blackscreen bug" was started :D

But the "fix" is not the super +7Mhz for LCD CLock.. but it's just a difference in refresh rate what caused randomly the right sync between LCD and GPU = correct vsync = No tearings and no laggs.

4. On GB we've no tearings and laggs.. that means the vsync is right.. (actually i'm trying to find the difference in Sources between GB and JB)

5. The fact is: a wrong refresh rate don't cause only tearing + laggs, but also fuzziness during scrolling etc.

6. I've tried all LCD freqs from 33 - 80Mhz .. and it looks like only 2 Freqs are useful: 50Mhz (Default) for fixing blackscreen bug and 57Mhz (Boost) to make the Phone smooth and without tearings... but with that freq we've a bit lesser sharpness....

all other freq are laggy or it decrease the sharpness a bit more than with 57Mhz ..

- If somebody know additionally informations about LCD / our Phone, so pls u're welcomed :)
[Galaxy Ace II Android Development] fluffi444:
Confirm - 2.19.3 runs really good for several days now... several days on without any issue....

Looks like that nothing was damaged due to HWMEM - btw: I'm also away from HWMEM - even if less and only after 1/2 days of use some apps starting to FC sometimes with HWMEM...

Good work Chrono - as usual.

Yes - in mcde_lcdclk of chronokernel 60+ Hz is 54.186.666 Clock (54 MHz) and 60 Hz is 48.768.000 Clock (48/49 MHz)
[Galaxy Ace II Android Development] ace2nutzer:
Hmm that's strange.. did u check this Values with OC'ed DDR ?? Because default Values are:

49920000 Hz lcd clk for 60Hz refresh rate and 57051428 Hz lcd clk for 60+ Hz of refresh rate.

Pixel Clock should always 159Mhz ....

Maybe with OC'ed DDR we've a lower Pixel Clock and this result in smaller lcd clk ... :)
[Galaxy Ace II Android Development] fluffi444:
:) I suppose that you know that.... 975 OC DDR... Sure! :D

Yeb - its as you said - with DDR 798 (non OC) its 57051428 for 60+...
[Galaxy Ace II Android Development] ChronoMonochrome:
Pushed R2.19.4 and R2.20-beta.

Changelog:

R2.19.4

applied some kernel optimizations

enabled UKSM

R2.20

dynamic fsync replaced with implementation by faux123

New interfaces are obtainable at /sys/kernel/dyn_fsync/

added, but disabled by default dynamic management of dirty page writebacks [Christopher83]

memcopy and string libs implementations replaced with optimized ones

updated RWSEM algorithm

added frandom module

Zram and zsmalloc code synched with Linux Kernel 3.17 (credits to mikeNG)

various fixes and improvements
[Galaxy Ace II Android Development] shaqman89:
Trying it out. First impression, it's really fast and smooth though boot time increased (8k to 11k).

I wonder if it's just me, but it feels that touch screen also became more sensitive and responsive. Quite surprised that unintentional swipe happened just cause of a light touch. I'm not saying, it's bad, but it certainly is a pleasant surprise :D

[MENTION=5695278]ChronoMonochrome[/MENTION]

Btw, I couldn't find this folder /sys/kernel/dyn_fsync/. Are we supposed to create it by ourselves?
[Galaxy Ace II Android Development] ChronoMonochrome:
UKSM spends these 3 secs on memory scanning.

Nope, probably I forgot to enable it :facepalm:

Will enable in next build, probably tomorrow, because enabling this option now will require to rebuild kernel wholly :silly: Though, as fast fix, I can re-enable old implementation. :)

Maybe due to recent kernel optimizations :)
[Galaxy Ace II Android Development] Ave_Hornet:
R2.19.4 no problem so far

i see this also on 19.4

Good work as usually
[Galaxy Ace II Android Development] Alex_Gamer:
Man, you gotta try R2.20 beta :D
[Galaxy Ace II Android Development] Ave_Hornet:
really is that good?

I use the phone on a daily basis . and i don't want to surprises
[Galaxy Ace II Android Development] Alex_Gamer:
Me too, if I saying to you is for something [emoji4]
[Galaxy Ace II Android Development] Ave_Hornet:
okay :D this is wierd . My phone is like Fu*king ROCKET now

WTF [MENTION=5695278]ChronoMonochrome[/MENTION] what have you done ? :F
[Galaxy Ace II Android Development] shaqman89:
And for a moment, I thought it was just me :D

I agree, this 'beta' version is quite awesome :D
[Galaxy Ace II Android Development] manthes:
2.20 looks very good until now.
[Galaxy Ace II Android Development] bebolint98:
Hi everybody.I came from ace2nutzer kernel and flashed the 2.20 beta kernel.From etc/init.d folder which script I need to delete?Now I have this scripts:
[Galaxy Ace II Android Development] fluffi444:
01opt...

Or just look into Ace2nutzer kernel zip file in folder \system\etc\init.d

EDIT

and deinstall (or freeze) NT app and use ChronoKernel Settings app

http://xdaforums.com/galaxy-ace/ace-2-apps/app-chronokernel-settings-v0-9-t3014123
[Galaxy Ace II Android Development] bebolint98:
Thanks!And which cpu governor do you recommed for ballanced performance?
[Galaxy Ace II Android Development] fluffi444:
DYNAMIC for balanced/powersaving and ZENX for gaming and max preformance.
[Galaxy Ace II Android Development] pelya:
[MENTION=5695278]ChronoMonochrome[/MENTION] I've seen you merged USB keyboard/mouse gadget patch, so I've added a link to this kernel to USB Keyboard app description.

Could you please include this patch into your next release?
[Galaxy Ace II Android Development] ChronoMonochrome:
Can't port it to LK3.0 so far(or maybe find anyone who already did it), so I had to revert it for now. Maybe later I'll try to port it.

Got it https://github.com/pelya/android-keyboard-gadget/blob/master/kernel-3.1.patch - didn't read the project carefully.

Nice feature btw :D :good:

Uploaded R2.20.1, for those, who already downloaded it, please, re-download.

Changelog:

enabled dynamic fsync support

set LZ4 compressor for ZRAM by default

added patch to use the phone as mouse/keyboard (credits to pelya )
[Galaxy Ace II Android Development] greeceeeee:
can you write your recommended best settings for the kernel?
[Galaxy Ace II Android Development] fluffi444:
Hey [MENTION=5695278]ChronoMonochrome[/MENTION] could u pls take a look into last_kmsg attached? Had an sudden reboot without any reason with R2.20.1.

http://d-h.st/Rg0P
[Galaxy Ace II Android Development] Alex_Gamer:
I don't know but I feel more smoothness on beta realize.
[Galaxy Ace II Android Development] ChronoMonochrome:
[cpufreq_limits] new cpufreqs are 200000 - 1215000 kH

Don't see kernel panic, therefore it should be related to too high CPU frequency.

But something is strange with MCDE,

[ 742.142303] mcde mcde: wait_for_flow_disabled: channel 0 timeout
[ 742.142364] mcde mcde: Fifo no empty chnl=0
[ 742.142395] mcde mcde: FLOEN at stop chnl=0

Since this happened right after DDR OC, I can guess, that in very rare cases even 975 MHz can cause reboots. But honestly, it's hard to say, what caused reboot - DDR or CPU OC, or maybe its combination.
[Galaxy Ace II Android Development] Alex_Gamer:
Forget that I said ? R2.20.1 is a long way better :)
[Galaxy Ace II Android Development] monstro78:
Yes I confirm... 2.20.1 is fast and smoother.
[Galaxy Ace II Android Development] Hummer951:
Do you mean its faster and smoother than 2.20.1.1 ?
[Galaxy Ace II Android Development] monstro78:
Sorry for the misunderstanding... 2.20.1 is fast as 2.20 but a little bit smoother
[Galaxy Ace II Android Development] manthes:
I have reboots with 2.20 and 975 ddr oc. With 2.20.1.1 i have artifacts if it is the correct word and screen is blinking.
[Galaxy Ace II Android Development] Alex_Gamer:
I had screen blinking since 2.19.4 :(

---------- Post added at 01:52 PM ---------- Previous post was at 01:36 PM ----------

@ChronoMonochrome R2.20.1.1 changes?
[Galaxy Ace II Android Development] shoxieJESUS:
@up

Disabled UKSM.
[Galaxy Ace II Android Development] Alex_Gamer:
Thanks :) I suppose with this the phone gests more smooth.
[Galaxy Ace II Android Development] ChronoMonochrome:
Can you guys set refresh rate to 60+ Hz and report whether it helped?

echo 1 > /sys/kernel/mcde/mcde_lcdclk

Then press 'power' button twice to make sure that settings has been applied correctly.
[Galaxy Ace II Android Development] manthes:
app for chronokernel has setting for refresh rate if i am right. I have it at 45 HZ for battery saving but i will try

.............................................................................................

for some reason it can't load ddr oc script and i can't know if changing to 60+ helped or not
[Galaxy Ace II Android Development] Alex_Gamer:
@up chrono app don't set frequency above 60hz I don't know why so.. You better use terminal command.
[Galaxy Ace II Android Development] Hummer951:
There are 60+ Hz and 60++ Hz options in the chrono app, I think that is what he means CMIIW.
[Galaxy Ace II Android Development] Alex_Gamer:
Yes that's right but I saying the chrono app don't set that values, or its just me.. Before I set 60+ the mcde file still on default frequency, maybe permission problem.
[Galaxy Ace II Android Development] ChronoMonochrome:
CK app fails to change lcdclk because its interface was moved to /sys/kernel/mcde/mcde_lcdclk.
[Galaxy Ace II Android Development] Alex_Gamer:
No more blinking on 60hz+ ?
[Galaxy Ace II Android Development] ayas02:
blink when playing game in R2.19.4 until R2.20.1.1

hi [MENTION=5695278]ChronoMonochrome[/MENTION] why im playing games suddenly my screen has blink how can i fixed it

my position JB 4.1.2 deodex and R2.19.4

thanks ^_^
[Galaxy Ace II Android Development] ChronoMonochrome:
[MENTION=5740966]ayas02[/MENTION], can you simply read last posts? Because answer in few posts above.

OP updated. Hope, that it'll more clearly answer on questions about recommended settings.
[Galaxy Ace II Android Development] ayas02:
you mean this [MENTION=5695278]ChronoMonochrome[/MENTION]
[Galaxy Ace II Android Development] borkins:
Chrono,

maybe the following default varm voltages are wrong:

0x20 for 400 MHz, 0x30 for 800 MHz, 0x36 for 1 GHz, 0x38 for 1.2 GHz.

As far as I remembered them in a few kernel versions back, they was:

0x1a - 400 MHz, 0x24 - 800 MHz, 0x30 - 1 GHz, 0x37 - 1.2 GHz.

Maybe that is a reason for some of the reported problems with reboots.

:\

Edit: Here is one 'Smanager' solution to control the LCD clock.
[Galaxy Ace II Android Development] ChronoMonochrome:
They're definetely wrong :/ Which version of CK app do you use? Honestly, I haven't tested its CPU UV setting, because I still use init.d script for it. Try to freeze it.
[Galaxy Ace II Android Development] ayas02:
okay im trying in TE and still blink screen how can i fixed it
[Galaxy Ace II Android Development] fluffi444:
My CPU OC 1215 was stabe for weeks even with 975 DDR (custom varm settings - no stock and no app usagge here).

But thanks to pointing me to MCDE direction. Maybe its because I set VSYNC to 3 (/debug/mcde/chnl0/vsync_mode)

But anyway - no reboots since now anymore... Thanks for looking into it.
[Galaxy Ace II Android Development] bebolint98:
Hi [MENTION=5695278]ChronoMonochrome[/MENTION].Today my phone is doing very strange things.I plug my phone from 87% of battery and about 20 minute later the battery decreased to 83% ,while the phone is charging.I plug to another socket and about 5-7 minutes later I have 93%.What do you think why this do the phone?I use 2.20.1.1 kernel.If you need here is the dmesg:http://d-h.st/2v1X

and kmsg http://d-h.st/Squ7
[Galaxy Ace II Android Development] borkins:
I didn't test it too. I have CK 0.9 Beta, but I use script to control the uV of all CPU steps.

Actually I'm working on script to control manually the arm steps, and also to set the changes in init.d script.

I'll share it here, as soon as I finish it. May be useful for some.
[Galaxy Ace II Android Development] greeceeeee:
The settings are preconfigured on this kernel or do we have to do them on our own??? i make the changes on chronokernel app but it doesn 't keep them....
[Galaxy Ace II Android Development] str3tch72:
How to apply other value for DDR OC? Because for me 975mhz is not stable. Or how to disable it?
[Galaxy Ace II Android Development] Ave_Hornet:
just run Pllddr oc script by [MENTION=5151049]borkins[/MENTION] http://xdaforums.com/galaxy-ace/ace-2-develop/custom-kernel-t2793420/post57395364#post57395364 with Script Manager https://play.google.com/store/apps/details?id=os.tools.scriptmanager&hl=pl

and type 1 :D
[Galaxy Ace II Android Development] ChronoMonochrome:
Thanks for logs, will look into this later.

UPD.

ab8500-fg ab8500-fg.0: ab8500_fg_reenable_charging, unfortunately charger is disabled even though s/w doesn't do it

Maybe bad charger?

As for fast charge, e.g. from 83% to 93% - it's known bug. Unplug charger and refresh battery stats via

echo 1 > /sys/kernel/abb-fg/fg_refresh

And it should show real charge after few seconds.
[Galaxy Ace II Android Development] bebolint98:
I think the charger is not bad because I use the stock charger.

echo 1 > /sys/kernell/abb-fg/fg_refresh

I need to do in term.emulator or it is the same which is in chrono kernel setting in power-->refresh battery stat
[Galaxy Ace II Android Development] ChronoMonochrome:
Yes, it's same.
[Galaxy Ace II Android Development] borkins:
[MENTION=5695278]ChronoMonochrome[/MENTION],

I found that by chance, and I'm not sure why is that.
[Galaxy Ace II Android Development] manthes:
How can we make permanent this setting and isn't is possible 60+ to harm our phone?

Also i checked and 60++ and i see that i have black screen. Just reporting it if it will help you in the future (s6d)
[Galaxy Ace II Android Development] ChronoMonochrome:
Use init.d to make it permanent. I can't guarantee that it won't harm phone and nobody can. But I agree with this

- CPU/GPU OC may be even more dangerous - therefore do (or don't do ) it at your own risk.

I forgot to remove these modules from /ramdisk/modules/autoload. Moreover, they are duplicates ones from /system/lib/modules and can be removed.
[Galaxy Ace II Android Development] ChronoMonochrome:
R2.21-beta

updated F2FS implementation (Oct 2014)

dynamic fsync: added new interface Dyn_fdatasync_active to enable/disable fsync via fdatasync (default enabled)

Disabling can improve I/O performance at the cost of higher chance of data loss.

added interface to allow to disable syncing of filesystems on suspend (thanks to zwliew for pointing to original code) - syncing disabled by default. Disabling improves battery life.

re-enable:

echo 1 > /sys/kernel/pm_sync/pm_sync_active

disabled software CRCs by default

added init.d script to clear VFS cache after boot

enabled ZRAM by default and set swappiness to 100

enabled dynamic management of dirty page writebacks

disabled dirty page writebacks on resume [zwliew]
[Galaxy Ace II Android Development] Alucard:
Wich version of the kernel is for stock jb and wich for cm11?Also how do i root?
[Galaxy Ace II Android Development] shaqman89:
Does anyone experience wake lock on latest version? Somehow phone wont go into deep sleep.

Tried restarting but no effect.

This is my bbs logs, just in case

https://docs.google.com/file/d/0Bzo3MSxg_YFCeEVmZ25mank1QzA/edit?usp=docslist_api
[Galaxy Ace II Android Development] matthias1976:
think its not problem of latest version !!

i was on 2.19.4 deepsleep workin normal.

over night phone wont go to deepsleep.

didnt change anything.

then i update to 2.21 no change

system.update.service (google play service) holds phone awake.
[Galaxy Ace II Android Development] shaqman89:
Yeah, the thing is that I was from 2.20, and it was fine.

Somehow without any changes in my configuration or application, deep sleep suddenly doesn't works in 2.21.

Edit:

Issue seems to disappear in 2.21.1
[Galaxy Ace II Android Development] ChronoMonochrome:
Uploaded R2.21.1,

changes only in Block Layer, that's updated to LK3.4. Main reason for this - new I/O scheduler FIOPS.

p.s. not highly tested yet. Most ioscheds removed due to block layer update, if anyone need it, will re-add them in next build.
[Galaxy Ace II Android Development] Ave_Hornet:
+1

I use for one day and no issues. This is a good compromise Perfomance and Powersaving.
[Galaxy Ace II Android Development] fluffi444:
Also confirm - I have not only "no issues" - I have the best preformance (for me) ever on my Phone... :highfive:

Even if I do not count to much on benches - but its still good to have an short overview of system prefomance.

With newest Kernel R2.21.1 I have the very first time over 16.000 Antutu score.

This with my 24/7 settings - which are not completely maxed out to the top...

CPU 200/1215 - GPU 300/600 - DDR 975 - ZENX - FIOPS (and countless :) other tweaks - mainly all what Chrono recomended)

As you know these high numbers are possible only with dynamic fsync - looks like now new implementation works very well. :good: