yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] ChronoMonochrome:
Check it once again. Finally, it should be fixed - I've got report from stock users that it works.
[Galaxy Ace II Android Development] shadow252:
Is it me or on 2.18 oc ddr to 975 MHz is not stable? It works only by OC_DDR.sh script but after some time my phone reboot. On 2.17 it worked well. Even init.d script.
[Galaxy Ace II Android Development] borkins:
Once the init.d script fails to oc ddr, you must re-enable the script with Smanager's script (OC_DDR.sh), or by deleting the log file 'OC_DDR.log'.

Don' t forget to check the log before that, because if you 'force - enable' it - that will wipe the log.

What's in the log:

1. The wating timers: The first is not so important (it's always around 1.5 min), but the second must be at least 2.5 min.

2. First CPU-DDR info: Look at the CPU governor ( first governor is the current: must be 'Lionheart' or conservative', in '[ ]' is the default governor ).

If you don't have these governors loaded, the script will use the first governor after boot - 'Dynamic', which is not good to be used in that moment.

3. Second CPU-DDR info: The CPU clock must be static - '[ freq1 = freq2 ]'.

4. Third CPU-DDR info: If available the CPU clock must be default, CPU governor - user's, DDR clock - user's.

If the DDR OC fails that would be followed by a reboot, so the log may not be full.

After reboot the script will be disabled with message "Disabled' due to problems!" at the end of the log.

If you want try the init.d script with Smanager to set the clock after boot.

Or you can run it with Smanager and copy the entire console message to a file and upload it here. Maybe helpful.

But if the reboot is later, after the new DDR clock is setted, i don't know how to help :\
[Galaxy Ace II Android Development] fluffi444:
Be sure that you do not use screen off clocks ("CPU freq Limit") with low settings. This leads often to a reboot because low clocks were set (with screen off), even the phone is still under load during booting... It also helped a bit to add "sleep 80" at the beginning of the script.

If you still want to use CPU freq Limit start it after DDR OC (manual or via script at the end of DDR_OC)

Anyway - DDR_OC is still not 100% stable during activating. But imho borkins's script is still a bit more sucsessfull as build in OC on suspend.

[MENTION=5151049]borkins[/MENTION]: I deactivated this whole enable/disable part in the script on my phone. In lets say 1/10 cases phone reboots but I don't want to change the script to "Enable" and deleting the log all the time :) - But anyway - its a nice feature for most.

Most stable way is (for me) to boot the Phone, don't push any key, do not enter PIN, wait untill the screen went off and wait again untill the script let the phone blink 3 times... push home button and enter pin... done...

BTW: No difference regarding DDR_OC between R2.17 and 2.18 here...
[Galaxy Ace II Android Development] ayas02:
how flash it ChronoMonochrome? im trying in all region 4.1.2 stockrom still stuck in samsung logo plz tell me :crying: i want UHID tested
[Galaxy Ace II Android Development] manthes:
That's why i had some reboots with cpu 200/400 screen off? But probably i can confirm that reboots starts after 2.16.2 kernel. I am using now this kernel with this settings and without problems
[Galaxy Ace II Android Development] fluffi444:
Just try it and report - All what I wrote are only my personal experiences... And not completly proven....

And for me DDR OC was way more stable during activating without CPU freq Limit for screen off during boot.

But this is only vaild - if you let the boot up without any touching...
[Galaxy Ace II Android Development] ayas02:
Yipeee Finally works in R2.18 Very Thanks [MENTION=5695278]ChronoMonochrome[/MENTION] , now time to trying UHID :o :o :o :o :o :o
[Galaxy Ace II Android Development] bebolint98:
Hi everibody!Somebody please write it how can I enable this in cm12 becase the multitasking is poor I use the r2.18 version.:

1) fix for poor multitasking performance on 5.0.2

LMK=/sys/module/lowmemorykiller/parameters

chmod 666 $LMK/*

echo 1024,2048,4096,8192,10000,14000 > /sys/module/lowmemorykiller/parameters/minfree

chmod 444 $LMK/*
[Galaxy Ace II Android Development] ChronoMonochrome:
Have you already tried to use init.d script with the code above?

P.s. this won't help with problem with processes being killed on suspend - they aren't getting killed by lowmemorykiller, but by CM12's activity manager - it's LP bug.
[Galaxy Ace II Android Development] bebolint98:
I never use init.d script.Please write it how can I use this code or this not too necessary to increase the multitasking? Sorry for the noob question.
[Galaxy Ace II Android Development] ChronoMonochrome:
Just copy/past a code to an empty text file, name it somehow like "01minfree", put it in /system/etc/init.d and set 755 permissions, that's it. If this causes some problems then I'm afraid I can't help - read somewhere about an init.d and some basic android things.
[Galaxy Ace II Android Development] jiguan:
It is good idea to use init.d script as chrono said below. But I usually do run this script manually. Paste scripts to a text file. and name it what ever (i. e. taskfix.txt). save in sdcard.

Open Terminal and write -> sh sdcard/taskfix.txt. Done. For me this is safe, because if anything goes wrong just edit script in text file, and run again.
[Galaxy Ace II Android Development] ayas02:
UHID: probably fixed UHID broken by adding various modules for specific devices

i think not fix because im trying with ipega all button it still not works or maybe there is trick to enable it ?

sorry if my english is bad
[Galaxy Ace II Android Development] shaqman89:
Yes, this is for sure. Always do test the scripts first, but creating them in init.d directly wouldn't do any harm since it will only been triggered after a reboot.
[Galaxy Ace II Android Development] psidco:
Sorry if this already asked/noob question/oot ,so if i flashed twrp and i want revert back to cwm, i just need to flash cwm.zip from twrp and get cwm recovery sir? Thanks before
[Galaxy Ace II Android Development] borkins:
New Update of the DDR OC scripts.

[MENTION=4962787]fluffi444[/MENTION], I am not so sure, but when a wake lock is active, the "CPU freq. limits on suspend" is not working.

In CM 11, the min time is 15 sec, after the screen go off.

if no wake lock is enabled after that time, the CPU freq. limits will be enabled ( if it's status is 'on' ).

The problem is when the "CPU freq. limits on suspend" are enabled and the phone wakes and sleeps during the OC.

That may change suddenly the CPU freqs and the time for OC, which may cause a reboot.

Because of that, I decided to disable the freq. limits during the OC, and after that to restore them in default state.

Hope that will help for the stability.
[Galaxy Ace II Android Development] fluffi444:
Tried your script during booted phone - for some reason CPU freq. limits are not set to original state "on" - after script it's alwasy "off".

I tried to find out why... But i got lost in this bunch of checking and logging :) ... Maybe its better if you take a look inside...

EDIT

I thinks its because of "cpu_susp_chk" after setting original state of CPU freq. limits. It jumps again to the beginning and set it again to off.
[Galaxy Ace II Android Development] borkins:
Yep, it's exactly there. I missed it.

I'll fix it soon...

EDIT: OC DDR Scripts Update - 20150303
[Galaxy Ace II Android Development] ChronoMonochrome:
R2.19 has been uploaded.

Changelog:

reduced size of HWMEM to 74M (640M of RAM are available)

Hopefully later I can increase available RAM a bit more. So far I've got some reports about some issues with graphical system on s6d with HWMEM=68M.

cherry-picked selected commits from android-3.4 to fix issues with binder

lowmemorykiller update by boype (pulled commits from android-3.4)

some minor fixes from mainstream
[Galaxy Ace II Android Development] fluffi444:
Is it possible to use R2.19 with HWMEM 68M? As far as I understood its (hard)coded in kenrel...
[Galaxy Ace II Android Development] xo.en:
What kind of issues? I am using custom kernel(not yours) with 68m and s6d and can see no issues..
[Galaxy Ace II Android Development] ChronoMonochrome:
Nope, it's hardcoded in kernel. Though, it's not imposible - I've an idea to store hwmem size in somewhere like last_kmsg and then read it from here. Unforunately, ramconsole being initialized(and probably procfs too) after passing cmdline to kernel - so far I don't have so far any ideas how to implement an idea above. Maybe later I'll compile builds with various sizes of HWMEM.

Don't know exactly what it's. Below is quotation of report

original: http://4pda.ru/forum/index.php?showtopic=369612&view=findpost&p=38402424

Some users reports about not working network(I've also faced issue with losing signal). Lastly, I've faced dissapearing of sound when was listening music.
[Galaxy Ace II Android Development] xo.en:
Ehh, eternal black-wake-up-screen....nightmare of every s6d user.

This is interesting - i had it on totally different machine too(i think it started to happen AFTER adding some tweaks to build.prop), and only solution was pressing vol up/dn ONCE to wake screen immediately, if issue occured(so, power-and-vol btn then). Need to check, if it is working for a2..

HMM, this is interesting as i got sound loss too - was it sudden loss, of lack of sound AT ALL after boot?

I got total sound loss too @68m, and only solution was reboot(if sound is ok after boot, sound keeps ok, but sometimes there's no sound after boot and everything that uses sound, phone included locks up(not fc, weird freeze) then).

Only solution was checking if sound is working after every boot.

Still do not know if it is related to viper or kernel tbh...

btw, i am incredibly impressed by your and Atze work.

Nobody could imagine such progress before.

It made changing machine useless(i mean a bit better devices are actually worse than a2).

p.s. wow, 0.97 chronoks on 4pda is posted :)
[Galaxy Ace II Android Development] ChronoMonochrome:
Yep, the same here :/
[Galaxy Ace II Android Development] xo.en:
..but tbh, i had it even with older, 4.3.x roms. It is annoying, but, it can be at least avoided, to some extent;

like i said - only method is checking snd after boot - i noticed, that if it works, it won't break until next boot(well, at least i hope so :) ).

I am wondering - this bug did not exist before first OC kernels, i do not remember such thing earlier.

I wouldn't link this issue with hwmem, btw. HMM, i mean, until default settings are borked too, generally.

Well, it is issue, I can live with, but it is weird, actually.
[Galaxy Ace II Android Development] ayas02:
wew HWMEM = 68M its possible chrono?

anyway same my problem when im flashing R2.19 stuck in 4.1.2 stockrom
[Galaxy Ace II Android Development] manthes:
I have black screen with 2.19 at the end of a call. S6D lcd.

Back to 2.16.2 the best kernel for me
[Galaxy Ace II Android Development] Ave_Hornet:
Good Work [MENTION=5695278]ChronoMonochrome[/MENTION] ,but U delete ZenX gov?
[Galaxy Ace II Android Development] ChronoMonochrome:
Don't remember that I deleted it - just check /system/lib/modules - it's probably isn't in autoload folder.

P.s. default gov is again Dynamic. Those who wants more gaming performance, can still use Interactive/Zenx/Ondemandplus.
[Galaxy Ace II Android Development] miryn:
Yeah i don't think it's related with HWMEM too, I also have this bug.. After some reboots i don't have sound and every now and then phone looses setted ringtones..
[Galaxy Ace II Android Development] shadow252:
There's any changelog for 2.19.1 version?
[Galaxy Ace II Android Development] ChronoMonochrome:
Yeah, but there's actually one fix to networking config - to avoid bug with downloading files via wifi, that's possibly was introduced in 2.19. Also fixed bootup on stock (once again).

It's offtop in CM11 thread, so move discussion to this topic.

There's no ramdisk for custom ROMs based on stock, so you need to make one yourself:

(reboot to default kernel that is used on 4.1.2 Kyrillos v9 first)

cd /
find . -xdev | cpio -o -Hnewc | gzip -9 > /ramdisk/boot.cpio.gz

this will create boot.cpio.gz on /ramdisk. Then copy this file to my kernel installer(replace file osfiles/4.1.x/boot.cpio.gz) and flash it.
[Galaxy Ace II Android Development] ip3000:
4.1.2 stock wi-fi don't work with latest kernel (2.19.1) and some governor disappeared
[Galaxy Ace II Android Development] shoxieJESUS:
@up

To enable governor need to copy, for example file cpufreq_fantasy.ko to /system/lib/modules/autoload and reboot. If no this folder, copy file to /ramdisk/modules/autoload.

E:But i don't test with folder in /ramdisk
[Galaxy Ace II Android Development] Bogazicili90:
I made an odin stock flashing. Rooted and cwm recovery installed. I have this time a really weird issue. My simcard isn't initializied. There seems no bug in the rom. I have stock kernel. After booting it doesn't ask for sim pin. When i clicked contacts there is no contacts. When click to display contacts it says sim card initializing but it isn't. I toggled plane mode searching dor networks etc. Nothing works. Sim cars works on another old phones. What is the reason for this weirdest issue?
[Galaxy Ace II Android Development] borkins:
[MENTION=5695278]ChronoMonochrome[/MENTION], I made a little "correction" of the init.d scripts.

In some scripts there was missed "/" in the shebang line ( #!/system/bin/sh ).

Also i got some error messages when tried the 00autoload script with Smanager ( like "std_gov : Not such file or directory" ).

I wasn't sure, what is the idea of "std_gov" string, because it's not exist as PATH in my autoload folder,

so I just made it to create 3 folders inside "autoload" folder:

- "std_gov" - where to put the desired cpu_governor.ko file

- "std_io_sched" - where to put the io_scheduler.ko file

- "std_tcp_cong" - where to put the tcp_algorithm.ko file

And the rest is like before - putting the desired modules in the "autoload" folder.

The "fi" was missed at the end of the code of "20s6d_lcdclk_fix" script.

I checked the kernel versions from r2.16.1 to the latest, and looks the script never do it's job. :/
[Galaxy Ace II Android Development] ayas02:
i tested R2.19.1 in 4.1.2 nb1 stock and still stuck in samsung logo T_T
[Galaxy Ace II Android Development] ChronoMonochrome:
Sorry, my bad :p

Settings like "std_gov" are outdated now - at least, I don't think that anyone use it. But honestly, it was too lazy for me just remove this part. Its original idea was to allow set these options if ROMs' settings failed to be applied for some reason.

As for 20s6d_lcdclk_fix - since it's default setting in chronokernel app, it also should be removed.
[Galaxy Ace II Android Development] ayas02:
im sorry [MENTION=5695278]ChronoMonochrome[/MENTION] fix it in jb 4.1.2 im tried download once again and working from 4.1.2 thanks for your great job :)

by the way R2.19.1 HWMEM change to 74M right [MENTION=5695278]ChronoMonochrome[/MENTION] ?
[Galaxy Ace II Android Development] artur1131:
[MENTION=5695278]ChronoMonochrome[/MENTION]

What is the best configuration for powersave without making our phone lagger? Actually my ace is working on 100/1200mhz with dynamic governor, Screen refresh ratio - 40hz, gpu clock is static 360mhz.

My battery is on 40% with 1h30m screen on (im rather using high brightness) and 1h40m with music on (screen is off). Generally i keep 3g transmission on.
[Galaxy Ace II Android Development] ChronoMonochrome:
R2.19.2

Changelog:

fixed LCDCLK interface and moved to /sys/kernel/mcde/mcde_lcdclk

reverted changes in lowmemorykiller introduced in R2.19

Nohow. It's hardcoded in kernel.

I can suggest to use 2G/wifi whenever it's possible, because 3G drains battery like hell. Undervolt GPU and CPU - this also can help a bit.

Don't change voltage of both GPU/CPU at the same time - otherwise if you'll get reboot if won't know what it caused. The same is for different frequencies - if you'll change voltage of too many steps you won't know which frequency caused reboot. It's not easy process, though, following method makes it much easier: https://github.com/mkaluza/i9070_kernel_CoCore-E/wiki/Undervolting-janice . Probably I should write it in OP, because it's not first time when I answer on such questions.

P.s. almost forgot it - I'm about CPU freq of 100 MHz - don't enable it unless it uses the same voltage as 200 MHz. The same is for the rest frequencies - until some of them uses same voltage, no point to enable steps with lower freq. I've added 100 MHz just to further make some tests with it once again. It can't use lower varm than 200 MHz - that's why it's disabled by default. Furthermore, not all phones well keep undervoltage, that's why 100-400 MHz steps uses same stock voltage varm=0x1a.
[Galaxy Ace II Android Development] ip3000:
Have you fix wi-fi in this new kernel?
[Galaxy Ace II Android Development] ChronoMonochrome:
I don't use stock and I also don't remember that someone else reportred about not working wifi.

Try to insmod wifi module manually:

insmod /system/lib/modules/dhd.ko

And upload dmesg output here:

dmesg > /sdcard/dmesg.txt
[Galaxy Ace II Android Development] Ave_Hornet:
On R2.19.2 with andro 5.0.2 Bootloop
[Galaxy Ace II Android Development] ChronoMonochrome:
Last_kmsg, please. Why you guys simply don't post logs when reporting smth?
[Galaxy Ace II Android Development] Ave_Hornet:
http://www31.zippyshare.com/v/YOaWlKQ7/file.html
[Galaxy Ace II Android Development] ip3000:
If i can help in 2.18 wi fi work
[Galaxy Ace II Android Development] ChronoMonochrome:
Idk why it caused bootloop. Following solves it as well: reboot to recovery, remove all files from /ramdisk:

cd /ramdisk
rm -fr *

Then install kernel.

This should mean that something was messed in this partition. Later I'll look into kernel installer.
[Galaxy Ace II Android Development] shaqman89:
No bootloops for me :good:

But, I did notice that in the version it's still 2.19.1. Did you forget to change the version [MENTION=5695278]ChronoMonochrome[/MENTION]?

No big deal, just wondering if it was correctly updated or not.

:good:
[Galaxy Ace II Android Development] Ave_Hornet:
THIS STRANGE PROBLEM presented with TWRP RECOVERY installed the kernel with phillz and running, ahead of questions , everything was mounted

with R2.19 i had no problem

i don't test it with cm11
[Galaxy Ace II Android Development] ChronoMonochrome:
Yep, just forgot to change it.
[Galaxy Ace II Android Development] riyosakura:
you tried it on cm12??

btw, i wanted to ask, sorry if im OOT. Is it installing full f2fs and latest chrono kernel on cm12, really boosting cm12 performance?

i'm using cm12 right now, and it very laggy on some of the apps, especially on facebook, google+. if its normal behaviour, reverting to cm11 is much better idea for me.

what do you suggest?
[Galaxy Ace II Android Development] Ave_Hornet:
I don't see any difrence between ext4 <> f2fs in cm12
[Galaxy Ace II Android Development] Alex_Gamer:
R2.19.2.1 changes?
[Galaxy Ace II Android Development] ChronoMonochrome:
It's test build. I've reduced LCDCLK frequency to original and did some changes in MCDE system. And also reverted HWMEM change - it seems a buggy - sometimes camera gives a FC and the phone looses signal(not the both bugs at the same time - bug with camera occurs relatively rary, but second bug is almost after every boot on CM12. Don't know though, if it's ROM related).

Please report if you've screen tearings.
[Galaxy Ace II Android Development] shaqman89:
Yes, I have. It did give some boost, but still too slow for my liking. So, currently I'm still using CM11.

Facebook & google+ does uses huge RAM, so it's not surprise if it lags there. It also lags in CM11 as a matter of fact, though I found that the effect would be dramatic only when I multitask.

For me, it did give some boost, but not really that much.
[Galaxy Ace II Android Development] fluffi444:
Iam still on HWMEM 68M R2.18 with CM11 and without any issue since you released it.... Not a single FC of any app nor camera failures of any kind...

If you need logs... Call...
[Galaxy Ace II Android Development] ChronoMonochrome:
I've seen logs already. Sometimes camera(or rather, the CM engine) fails to allocate memory. Maybe I can manage by two variants of builds - with 647 MB of RAM and 631.
[Galaxy Ace II Android Development] Alex_Gamer:
You can make three? :D the third for gamers.. With more hw mem
[Galaxy Ace II Android Development] ChronoMonochrome:
This won't give any noticeable improvements, afaik (or maybe it does?).

I've uploaded build with hwmem 68M. I've noticed another side effect - the GPU performance drops drasticly with reduced hwmem (don't know, with 68 MB or less). Unfortunately, simple restoring back to original kernel doesn't solve problem - only restoring full CWM helps. That thing I cannot explain...
[Galaxy Ace II Android Development] S.AMU:
And what If we make a clean install? It should be the same as restoring a CWM backup?
[Galaxy Ace II Android Development] ChronoMonochrome:
Probably same, I didn't check it.
[Galaxy Ace II Android Development] fluffi444:
Tested this and after few hours firsts apps starting to FC. Back to R2.19.2.1 without reduced HWMEM.

Hopefully the FC is away. But I am a bit aware because you said that only CWM backup will solve this... We will see...
[Galaxy Ace II Android Development] ChronoMonochrome:
Sorry guys, I think I've messed something on latest builds, since I've problems with some apps too. I uploaded R2.19.3 which is build from R2.18 sources but with recent changes to MCDE and stock LCDCLK frequency.
[Galaxy Ace II Android Development] LS.xD:
Every time i try to flash 2.19.3 my phone softbricks. I can't even enter recovery. Just flashing via ODIN helps. Tried three times, everytime i get a softbrick :(
[Galaxy Ace II Android Development] ip3000:
and now with latest build wi fi work again :good:
[Galaxy Ace II Android Development] LS.xD:
Tried again with no success. Flashing the 2.19.3 kernel ends up in a softbrick for me. So all I can do is looking forward for the next release :crying:
[Galaxy Ace II Android Development] ace2nutzer:
same here... for me this way works_

flash any odin kernel and then reflash the same chrono build again.. and the phone will boot normally.. first in philz recovery and after "reboot system" the phone will boot CM ...

Chrono already now that.. i think that bug is coming only if a user is switching from ace2nutzer to chrono kernel ...

btw: chrono and i are thinking about to develop a flash-able .zip to deinstall our own kernel.... that means for Chrono Kernel:

Modules, init.d scripts and Chrono-App

And for ace2nutzer kernel:

Modules, init.d scripts, NT-APP

But to make it fully clean, the user should also remove (manually) their own custom init.d scripts, at least if those scripts are kernel specific...

(for ex. script for DDR OC for Chrono kernel what will not work on ace2nutzer kernel)

But anyway this is not the Fix for Samsung Bootloop.. it's just to avoid confusion between both kernels and to keep the System clean.
[Galaxy Ace II Android Development] Ave_Hornet:
[/COLOR]

Guys try to switch from TWRP to CWM for me it works no bootloops etc.
[Galaxy Ace II Android Development] LS.xD:
[MENTION=6227052]Ave_Hornet[/MENTION] [MENTION=5840412]ace2nutzer[/MENTION]

CWM is only available for codina. I have codinaP .

I can't really face any relevant speed differences between the two custom kernel of [MENTION=5840412]ace2nutzer[/MENTION] and [MENTION=5695278]ChronoMonochrome[/MENTION] BUT the main reason for using Chrono is that I really hate the crappy CWM and TWRP is just great.
[Galaxy Ace II Android Development] ace2nutzer:
try to flash after bootloop an odin kernel.. then again 2.19.3 .. for me it works !
[Galaxy Ace II Android Development] zipperX:
Chrono, i have random reboot, this is my last kmsg, i hope it will help, thanks.
[Galaxy Ace II Android Development] ChronoMonochrome:
@up, there is still something wrong with the memory management. I'm trying to fix it, but it seems nothing works.