yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] Andrewbons:
I don't like TWRP... it can't mount my external SD, i can't do other things.

CWM is the best
[Galaxy Ace II Android Development] pedroleon99:
But it can mount external sd, I'm sure...
[Galaxy Ace II Android Development] ace2nutzer:
for not u can mount ext sd even over ADB:

adb shell "mount -t vfat -o rw /dev/block/mmcblk1p1 /sd-ext"

or:

adb shell "mount -t vfat -o rw /dev/block/mmcblk1p1 /storage/sdcard1"
[Galaxy Ace II Android Development] ChronoMonochrome:
For some reasons it doesn't work with exfat. I'll to try fix it, but without hopes.
[Galaxy Ace II Android Development] Andrewbons:
I suggest to do not force the use of TWRP. I like this kernel but i don't want TWRP.
[Galaxy Ace II Android Development] zizoumadrid:
hi !

special thank's to [MENTION=5695278]ChronoMonochrome[/MENTION] for that awesome hard work and all who make effort to make this kernel awesome fast and stable

i had question: what is the fastest kernel between this kernel and stock tc cm11 kernel ?

can someone tell me what is the best stable fast build in this kernel

i had tc cm 11 with stock kernel

thank's again !

:)
[Galaxy Ace II Android Development] fluffi444:
Short question:

Are there any other changes in chrono_kernel-P_r1.5.2_4.4.x_twrp_f2fs.zip compared to chrono_kernel-P_r1.5.1_4.4.x_cwm_f2fs.zip besides the change to TWRP?
[Galaxy Ace II Android Development] ChronoMonochrome:
Nope.
[Galaxy Ace II Android Development] manthes:
With 1.6 twrp we can convert and system to f2fs?
[Galaxy Ace II Android Development] ChronoMonochrome:
No, we still can't.
[Galaxy Ace II Android Development] zizoumadrid:
can someone help me plzz thank's
[Galaxy Ace II Android Development] fluffi444:
The last available for each version ...: :angel:
[Galaxy Ace II Android Development] ChronoMonochrome:
New build is UP!

Builds for 4.2.x and codinap coming soon :)
[Galaxy Ace II Android Development] fluffi444:
Phew.... Removing 1100 could be not so funny for some who uses this as maximum freq.

Argee with 1050 and 1250... 1050 is kinda useless and 1200 should be the max recommened....

25? this works??? :D
[Galaxy Ace II Android Development] ChronoMonochrome:
I'll add 1100 MHz again. Probably 700 MHz is not so needed as 1100.

Yes :D don't set 25 MHz as min/max freq, I waste 1-2 minutes to set it back to 300/1200 MHz :D However, it has benefit of power save when screen is off and any wakelock is enabled. :)
[Galaxy Ace II Android Development] crisis_trustee:
Will be chrono_kernel_r1.6.3_4.4.x_cwm_f2fs ?
[Galaxy Ace II Android Development] Kiras_PL:
Why did You removed 1250mhz step? :(

---------- Post added at 11:33 PM ---------- Previous post was at 11:27 PM ----------

And how about twrp ext4 version? :)
[Galaxy Ace II Android Development] ChronoMonochrome:
It anyways not stable at all... or at least not stable for most users. And we cannot have more than 12 CPU freq steps (found out empirically).

It will be when I will have free time.
[Galaxy Ace II Android Development] shaqman89:
Great job :D

I hope you won't leave out the cwm_f2fs users :D
[Galaxy Ace II Android Development] ace2nutzer:
@ Chono

u are the Nr. 1 freaky user of ace 2 !! U are so amazing ! 25Mhz for screen OFF ! hahaha :D :highfive:

But for me,

I think the best way for the moment.. until cocafe will fix the 12 steps limitation:

200

300

400

500

600

700

800

1000

1100

1150

1200

1250*

exactly 12 Slots.. more is at the moment not possible......

* real 1250Mhz ! instead 1230MHz ! thanks [MENTION=5695278]ChronoMonochrome[/MENTION] for generating the PLL. :good:
[Galaxy Ace II Android Development] ChronoMonochrome:
hahaha, probably it's true :D

I think we should thank [MENTION=4832589]cocafe[/MENTION], not me :)
[Galaxy Ace II Android Development] cocafe:
Maybe it is a good idea to use a low frequency in off-screen.

And for real 1250MHz, the PLL is 0x00040182 (1248MHz)

And where did you guys get LK 3.2?

来自我的 C6902 上的 Tapatalk
[Galaxy Ace II Android Development] Devel0per95:
Twrp-F2fs not working with my phone please can u make a new one as ext4
[Galaxy Ace II Android Development] borkins:
Why is that? :silly: In zvliew's last kernel (v1.5) - there are 15: 100, 200, 300, 400, 500, 600, 700, 800, 900, 1000, 1050, 1100, 1150, 1200, 1250.
[Galaxy Ace II Android Development] ChronoMonochrome:
I implemented all (or almost all) features from http://kernelnewbies.org/Linux_3.1 (as [MENTION=5093942]KINGbabasula[/MENTION] tried more than half year ago) and http://kernelnewbies.org/Linux_3.2 . But I still not sure if there's all commits of LK 3.2, because not all of them were announced on kernelnewbies.org . However, I also updated all file systems to LK 3.2, I mean updates which can be found on https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git (few commits still not implemented, because for some reasons it causes CWM loop, random reboots, spam in kmsg due to errors in FS, etc...).
[Galaxy Ace II Android Development] Kiras_PL:
I've never had problems with 1250mhz step :) would be great if You could bring it back :) BTW, thanks for Your hard work!
[Galaxy Ace II Android Development] ace2nutzer:
when we fix steps limitation, we can also add 1,3Ghz step i think.. maybe somewhere have a good CPU and it can run stable.
[Galaxy Ace II Android Development] manthes:
I am not very sure but i think that previous build for 10.2 was faster.
[Galaxy Ace II Android Development] riyosakura:
The smoothest kernel so far.

I used it on LS Rom and very good. :D

And finally data arrow is now available.

Thanks man.
[Galaxy Ace II Android Development] ChronoMonochrome:
I'm not so sure. Because we can't run it on 1.3 GHz, even if we use performance as governor.
[Galaxy Ace II Android Development] str3tch72:
Is there any chanse to have TWRP latest kernel with ext4?
[Galaxy Ace II Android Development] exodius48:
[MENTION=5695278]ChronoMonochrome[/MENTION] could you recommend which is the best settings for 4.4.4 rom? governor, i/o, and so on.
[Galaxy Ace II Android Development] ChronoMonochrome:
is not a question that can be answered unequivocally. My preference you can see in my signature.

I hope it will be today. Problem is that my laptop too slow to make many builds.
[Galaxy Ace II Android Development] Kiras_PL:
Please add 1250mhz step :) it was great for me! :)
[Galaxy Ace II Android Development] ChronoMonochrome:
I'll add it if cpufreq limitation will be fixed. Btw, cocafe PMed me, he will change LiveOPP algorithm soon. But it's unknown, will be it stable or not.
[Galaxy Ace II Android Development] Kiras_PL:
Great! Thanks a lot :)
[Galaxy Ace II Android Development] ace2nutzer:
I meant for other users with good cpu quality.. i think 1,3Ghz is possible.. but with good cpu quality.

For me max. rock stable CPU freq is 1150Mhz.. it can run without problems for 4 hours @ CPU GPU Stress test ! (I've stopped the test after 4 hours..)

Well, but u can set 1200 Mhz.. is almost the same.. because 1250Mhz step is real: 1228Mhz !!

I think is better to add later real 1250Mhz and 1300Mhz.. then everything is fine :)
[Galaxy Ace II Android Development] ChronoMonochrome:
Are you sure if there's at least one CPU with good enough quality to run 1.3 GHz stable?
[Galaxy Ace II Android Development] ace2nutzer:
How ? Nobody knows, because this freq. was never available, therefore when can add this and wait if any users report that 1,3Ghz is stable. :) But when 1228Mhz run for many users stable, why not 1250 and 1300 ? this is not a big difference :)
[Galaxy Ace II Android Development] manthes:
With 1.5 builds i have black screen (s6d) for first time. When it will released 1.6 for 4.2 i will report if the problem exists. But with the builds before 1.5 everything was fine
[Galaxy Ace II Android Development] borkins:
Maybe real 1250 MHz would be more stable apparently to 1228 MHz. About 1300 MHz, I'm not so sure,

but it will burn the CPU and the battery too much for no reason.

My experience, with lots of tests, telling me that my CPU just don't like to be over 1050 MHz.

So, if you guys make the steps more stable, my CPU will prove it soon.

For me stable 1100/1150/1200 MHz would be more than i can hope for. I wish you luck!!! :good:
[Galaxy Ace II Android Development] ChronoMonochrome:
Maybe because of different quality CPUs. About 2-3 months I never got reboots related to overclocking to 1200 MHz, but 1228 MHz always cause reboots, whatever varm/vbbx voltage I tried to use.
[Galaxy Ace II Android Development] Eselter:
What's new in ver. 1.6.4?
[Galaxy Ace II Android Development] borkins:
I think so. If I'm right, and for example the CPU can't hold 1100 MHz on Performance governor,

that means it never can be stable in that frequency, right? I suppose that every frequency have some voltage range, but I can't find a voltage that not cause reboots for steps over 1050 MHz.
[Galaxy Ace II Android Development] ace2nutzer:
try to set for ALL steps: vbbx=0x8f and varm=0x39

then try again... for first test only with performance gov.. just to find the max. stable freq.

if with performance gov. for. ex.: 1100Mhz is very stable.. but with min. 200 and max. 1100Mhz is not stable at ondemand gov. then your Voltage regulator or Clock regulator is already broken !

My Phone is like this.. one of the two things is broken.. now it can run only stable @ min. 200 max. 800 with ondemand, interavtive etc... when i set max. over 800Mhz i've in 3 minutes 1 reboot... but @ performance gov. it runs very stable @ 1150Mhz !!

At the beginning of OC / UV i dont have this problem.... This is the reason why i will remove UV.

I believe that setting a different voltage for every step, is too much stress for the hardware.... it killed.
[Galaxy Ace II Android Development] exodius48:
But you're using cm 10.2 f2fs, I'm using cm11 TC ext4. Is the setting same?

And please make cwm_ext4 for latest kernel.
[Galaxy Ace II Android Development] ace2nutzer:
there is a difference.... filesystem is no matter.

CM11 is generally faster and smoother... perhaps because of other display driver...

that the reason because with CM11 u can reach more points than cm 10.2 in antutu

Using SIOplus is always good.. gov.. i'm testing for now....

I've implemented lots of gov. from Chrono's sources.... just testing...
[Galaxy Ace II Android Development] exodius48:
Ok bro.

Just asking, why this kernel still using cwm 6.0.5.0, do you know the reason? On latest cm11 built by TC already used cwm 6.0.5.1.
[Galaxy Ace II Android Development] ace2nutzer:
okk. This is why we can't (for the moment) not unpacking LZ4 compressed Ramdisk.

But Chrono will find a way.. it is still in development and maybe (if this works) uncompressed kernel.. for fastest booting and less power usage at the same time.. but with no hoping.
[Galaxy Ace II Android Development] borkins:
Last night I made a test with "Stability Test" - CPU/GPU. I don't know what is going on with the quality or the CPU voltage regulator,

but no reboot for 7 hours ( canceled by me ).

Here is the setup of the test:

CPU: 200-1150 / Pegasusq

varms: 200 MHz - 0x18; 400-800 MHz - 0x24; 1000 MHz - 0x2f; 1050 MHz - 0x33; 1100, 1150 - 0x35;

vbbx: 0x8f for all

GPU: 441-560 MHz / Auto Boost ( only 2 freqs );

I/O: 512 KB / SIOplus

Kernel: 3.2.0-Chrono-r1.6_4.4.x_twrp_f2fs

ROM: TC CM 11 20140807

The phone heats up to 44C for some hours, the last hour i cooled it down to 34C, just to see, if the phone likes the hot, but no reboot.

So, I decided to stop the test. But I don't rely to this test so much, because i made so many similar tests with the app. Once i got 3 hours at 1200 MHz with reboot in the end, but in the most cases the phone reboots in the first hour.

I was disappointed of my CPU quality and leave it to max 1000 MHz.

But in another hand, the last test is a record for me. I'll try to use the phone like before, but with the setup above for some time. Because my phone rebooting often, over 1050 MHz, when using it for browsing, reading and etc.

--------------------------------------

Sorry, for my bad English!
[Galaxy Ace II Android Development] gRaB@:
Chrono I remeber that u made also kernel for Janice stock 4.1.2, but on dev-host i dont see it, can u upload, i need for my mum stock :D

(if it works)
[Galaxy Ace II Android Development] Bastiary:
[MENTION=5695278]ChronoMonochrome[/MENTION] could u make 16.4 ext4 cwm version for 4.4..?

Because i have backup on cwm and i don't want to lose it.
[Galaxy Ace II Android Development] ace2nutzer:
Yes... as i said: set it all to 0x39.. and try again @ 1,2 Ghz. if it's stable for 4 hours @ CPU / GPU test, then this is stable... don't worry.

But as is said... in normal use, if u got reboots.. even with all steps @ 0x39..(in this case your hardware is already broken) then i suggest to set min. 200 and max. 800Mhz.. and use a script to set manually 1,2 Ghz @ performance gov.. when u need it.. for ex. for a good 3d game etc...

Because for daily use max. 800mhz is sufficient.
[Galaxy Ace II Android Development] doctormord:
Are you serious? Doing system engineering all day long, this sounds like nonsens to me.

I must admit, that Chrono-Kernel 1.6.3 is highly unstable on my phone with latest TC 4.4.4 ROM on every voltage setting. Even 400-800 will result in reboots, while the stock kernel is running nearly stable with 200-1150. Older builds (like those from month 07) are even more stable but lack a bit of fluidity.

Regards,

doc
[Galaxy Ace II Android Development] fluffi444:
Are you serious saying this? If everyboday would think the same (as you) we would still live in caves! :D

Some of "us" are interestet in "such stuff" and doing this for fun and hobby. Hard to belive but it is like it is. :angel:
[Galaxy Ace II Android Development] borkins:
So, it's safe for the hardware to run 100 MHz at varm=0x39 ( max voltage )? I tried all to 0x39, but got reboot in 4 minutes. Now trying with 0x35 to all.
[Galaxy Ace II Android Development] ace2nutzer:
Yes exactly! let it @ max voltage.. and try step for step to minimize the max. freq.. u will find stable freq.

Then post it here.. wich max. freq by scaling is stable...

0x39 for 100mhz - 1150mhz is better than 0x18 - 0x39.. the voltage regulator don't need to regulate the voltages so many times up and down.. this is the trouble. At the end set the stable voltage for your max. freq for the rest of steps...

For ex.: 1000Mhz is max. stable.. then find out at wich voltage is 1000mhz stable.. and add + 50mV ( 2 Varm steps ) and set this varm to all steps.. that's it !

For me is 800Mhz.. and it was very stable @ 0x22 .. therefore 0x24 for 200 - 800Mhz.
[Galaxy Ace II Android Development] doctormord:
I don't get the point what you are trying to say here?

A broken clock-gen (PLL) wouldnt even put out a stable signal on a fixed frequency. I.e. what makes the difference between 200-800 dynamic scaling with fixed freq-steps compared to one fixed freq?

Both scenarios needs to be stable/locked on the desired frequency. As those clock-gens are PLL based, they always settle to the right frequency in a specified time. (Voltage/Temp/Frequency drift will be regulated)

How does this belongs to "live in caves"? Maybe you got me wrong, as i didn't want to offend somebody - just wondering.

:confused:

For the whole voltage/frequency thing, i must say, problems with instability/reboots are related to high-dynamic load switching/over-/undershoot/settling time. Thats why "slower" governors normally perform better on somewhat instable voltage-rails. Having an old/drained battery will also cause problems.

(I also read some postings about problems with reboots on flat battery)

Having an old/drained battery will raise its output-resistance, which will lead in a bigger voltage-drop on load-change. More voltage-drop will result in more gain in the voltage-regulator control loop, which will/may result in a bigger overshoot and increased settling time. Having an aggressive frequency scaling will finally result in instability.

So these problems are (in my opinion) not related to failed voltage/frequency-regulators but rather in system/hardware design and changing/degrading operating parameters.

I don't know how much those scaling can be adjusted from kernel-side, but having a bigger gap between voltage/frequency scaling would/should increase stability on used hardware.

Cheers

doc
[Galaxy Ace II Android Development] ChronoMonochrome:
It doesn't work for some reasons. I only can advice to install CoCore.

Use 1.6.3. There's no big difference between these versions.
[Galaxy Ace II Android Development] borkins:
I do my tests with charger plugged in for the same reasons. I think the same way, but once I found that the phone is powering off at 3,00 V. Before the voltage of the battery dropped to 3,00 V, no matter how I used the phone, with scaling frequencies and voltage regulator, I don't saw any instability. Maybe the phone is designed to hold the power for every element ( CPU, GPU, Display and etc ) to specific voltage. In my case 3,00 V. The battery is almost 2 years old. And is not in the perfect condition.
[Galaxy Ace II Android Development] doctormord:
Yeah, it depends on phone/battery/temperature/board revision/tolerances etc. If the system layout/calculation is done right it can compensate this for the most. It's like with the cpu, some do 1250, some even wont do 1000Mhz.

Is someone needs more information about the used AB8500 PMU used here, check this PDF:

https://web.archive.org/web/2013061...M1031_AB8500_user_manual-rev5_CTDS_public.pdf

There you will find all power-routes, LDO connections etc. "Clock generator, clock management and RTC" is left out. :/

For clock-generation and PLL stuff you may refer to:

https://web.archive.org/web/2012052...s/DM00030004_AP9500_reference_manual_rev1.pdf

page 35ff.
[Galaxy Ace II Android Development] crisis_trustee:
Hi ChronoMonochrome,

There are your new kernels r1.6.4 in https://drive.google.com/folderview...&usp=sharing&tid=0B_OwIFfWQnj_V2kzV3JKcUlhU1U , but there isn't changelog about ones.

Thank you un advance!

Good luck!
[Galaxy Ace II Android Development] ChronoMonochrome:
there is nothing new besides of step 1100 MHz.
[Galaxy Ace II Android Development] miryn:
[MENTION=5695278]ChronoMonochrome[/MENTION] what is wrong with your kernel that CPU freq still can't be changed in Performance Control?
[Galaxy Ace II Android Development] ChronoMonochrome:
No problems on CM10.2. Don't know about other ROMs.
[Galaxy Ace II Android Development] riyosakura:
It should be okay changing cpu freq on performance control.

I've already tried it on LS KK.
[Galaxy Ace II Android Development] MarquesYOLO:
I've had some problems with last and previous build for codina 4.4.x (cm11 teamcanjica):

- A bit of "general" lag.

- Reboots at 800 and 1000 mhz. (not many)

- bad screen response.

I come back to stock cm11 kernel and i feel better. Otherwise good job [MENTION=5695278]ChronoMonochrome[/MENTION] I'll keep following your work.

Sorry for my bad English ?
[Galaxy Ace II Android Development] ChronoMonochrome:
Can you post last_kmsg / dmesg(when screen loses usual response) ?
[Galaxy Ace II Android Development] MarquesYOLO:
this is whit stock kernel, i've just made, when i had reboot with 800 mhz i install directly stock kernel, whithout making last_kmsg, sorry.

i feel lag on screen touch when i unlock the device and enter to apps box (with nova launcher), the first touch, to move into pages, didn't response.

I hope this information serves you, thanks.

View attachment last_kmsg.txt
[Galaxy Ace II Android Development] crisis_trustee:
Has anybody flashed r1.6.4 kernel?
[Galaxy Ace II Android Development] ChronoMonochrome:
I only see spam messages

In my kernel I just shut it up, but unfortunately it still needs in appropriate fix.
[Galaxy Ace II Android Development] MarquesYOLO:
I don't know, I think I did well.
[Galaxy Ace II Android Development] ChronoMonochrome:
Lol, I didn't say you did it not well. I just said there's obviously something wrong with this, since it cause a lot of spamming messages.
[Galaxy Ace II Android Development] fluffi444:
Am I blind or do we not have the possibility to mount USB (Mass Storage Mode) out of TWRP 2.7?
[Galaxy Ace II Android Development] MrBlackCore:
I have this bug with the latest build.... when I speak with some1 via phone or viber, the volume is really really low. Settings are set to max volume, but still the volume is very low. Anyone with the same problem or a fix?
[Galaxy Ace II Android Development] ChronoMonochrome:
A small preview of my next release: https://drive.google.c…RlbEU/view?usp=sharing (4.4.x, F2FS)

Just want to be sure that there's no any bugs before I release it for other ROMs.

Changelog:

Cleaned kernel source tree from doubtful commits, reverted ASM changes again to fix reboots issue

Huge LiveOPP improvement by [MENTION=3329816]mkaluza[/MENTION]:

improved overclock stability, added all extended steps

added state APE_25_OPP, used only with screen off(originaly introduced by mkaluza, adapted for codina by me)

allowed change APE_OPP and DDR_OPP from LiveOPP

changed step 1228 MHz -> 1248 MHz (may cause reboots, need to find out optimal voltage)

Mali improvements by mkaluza

All credits for LiveOPP/mali/etc. improvements goes to mkaluza.

UPD. I noticed TWRP loop. Probably I messed something in FS when I cleaned source tree. Please do not reboot into recovery until I release new build.

UPD2. removed. It's too buggy for now.
[Galaxy Ace II Android Development] borkins:
Best stable kernel I've tried so far is r1.6 4.4.x f2fs.:good:

And looks I was wrong about the max frequency of the cpu of my Ace 2. I was sure that my phone can't hold frequencies over 1050 MHz. But 10.5 hours at 1200 MHz on test with StabilityTest-CPU/GPU... The temperature of the battery reached 46C. So, when i sow it i needed to use a hairdryer to cool it to 32C :laugh:

But seems 1228 MHz is too unstable. Can't reach even 30 min with StabilityTest app.

[MENTION=5840412]ace2nutzer[/MENTION], [MENTION=5695278]ChronoMonochrome[/MENTION], if that is helpful, here are the varm values ( of the highest freq. ) for max stability of my Ace 2:

Frequency | max varm / vbbx

1250 MHz, no stable values

1200 MHz, 0x37, 0x8f

1150 MHz, 0x35, 0x8f

1100 MHz, 0x35, 0x8f

200/1050 MHz, stable with the highest values.

100 MHz, I forgot to test it with highest voltages, but it's stable with 0x18, 0x8f ( for me works good for screen off freq. )
[Galaxy Ace II Android Development] ChronoMonochrome:
Thanks for your tests!

I believe there is no needs to set highest values. It is not only my opinion, I think there is good reason for this because [MENTION=4832589]cocafe[/MENTION] and [MENTION=3329816]mkaluza[/MENTION] never used it in their kernels. why am I so sure? Because these guys know a lot more and much better than us how it all works. And it seems that it will be possible to UV 100-200 MHz to 0x12(975 mV), but only when we'll add APE_25_OPP state(it is already implemented with latest LiveOPP update, but actually used only APE_50_OPP and APE_100_OPP, that is reason why we should set varm @ 0x18 for 100-400 MHz).

[MENTION=5840412]ace2nutzer[/MENTION], are you still using ape_opp=100% ? I'm not sure but maybe that is reason why you can use 1150 MHz stable only with highest voltage.