yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] manthes:
For me all of 2.24.x are very stable. Could it be rom problem?
[Galaxy Ace II Android Development] gothicVI:
So you don't support this specific version of cm12?

I always went back to 2.20.1.1
[Galaxy Ace II Android Development] fluffi444:
In my opinion 2.24.4 is slower as 2.24.3. I mean the general ui performance.
[Galaxy Ace II Android Development] shaqman89:
Which ROM are you currently using?
[Galaxy Ace II Android Development] manthes:
Liquid 4.4 July build. I don't have problems with different kernels. I have performance differences but not problems
[Galaxy Ace II Android Development] xo.en:
..Chrono, what do you think about this:

http://xdaforums.com/android/help/qa-multisystem-android-t3102389/post60583585
[Galaxy Ace II Android Development] slv96:
How's this kernel with my aosp kitkat Rom?
[Galaxy Ace II Android Development] ChronoMonochrome:
If I ever try to implement it, then not now, too busy. At the moment, I am satisfied with the dualboot implementation I have described here - not very comfortable and probably totally non-userfriendly, but fits for testing the second ROM, without the need to remove the old one.

I am not sure what causing this. I could blame recent HZ change and some related changes, but so far I haven't found any confirmation to this. About battery level - AFAIK it never worked properly. This happens because after plugging the charger it slightly increases battery voltage - and this leads wrongly showed percentage.
[Galaxy Ace II Android Development] mkaluza:
the best thing would be to have a kind of boot manager that looks like cwm recovery - you just swipe and select which system you want to boot. But since it's more a gimmick than a useful tool, it'll probably have to wait a looong time... but who knows... something like this has been on my mind for very long - maybe someday (or night) I'll look into it.
[Galaxy Ace II Android Development] xo.en:
You know, while it is semi-useless for ace2, such thing could be great for tablets...
[Galaxy Ace II Android Development] fluffi444:
Hey Samu... My GPS sucks also. Could you remember were those plugs are located on Mainboard?

My phone is not open jet... But I opened it some weeks ago to get rid of the dirt of 2 1/2 years :)

My girlfriends Ace2 (absolutey same CM11/Kernel/configuration) has 10/12 after seconds... Mine none or only 3-4 after minutes..

gps.conf is 100% same also...

I guess that the kabels are ripped of - Maybe happend last time I opened it....
[Galaxy Ace II Android Development] S.AMU:
If you remove the first back cover you will see a small rubban at the top of the phone. Thats the GPS-Antenna.

Now open the screws and gently remove the backplane. The GPS-Antenna has two connections. One connection is made in one corner at the bottom where there is a screw. The other connection is on the left or right side of the camera (if I remember it right :D)

It is just ome kind of a small golden piece of metall on the board.

But I cleaned all the small connectors. So also the one from the speaker and the bottom antennas.
[Galaxy Ace II Android Development] fluffi444:
Just to be sure... I attached two pic's... Is it the blue one on the pcb? And the Antenna is the red one on the backcover?

Anyway I think I'am going to clean and tighten all of then to be sure...
[Galaxy Ace II Android Development] S.AMU:
It should be the blue one. Also on the top of the PCB, where the blueline is crossing there is the other conecctor (the golden surface). Be sure to clean this one also.

The red one is the Wifi,Bt,Radio Antenna.

Are you sure that the green one are conectors (I can't see it on the photo)? Because I remember that just under the LED there were two LED driver. But I forgot if it was on the front or back side of the pcb.
[Galaxy Ace II Android Development] fluffi444:
That was the trick! I found out that there was bluish plastics from one scews (this screw secureing stuff - marked it blue on the attached picture). Maybe I took the wrong one for this place during my last openeing procedure.

After cleaning I got 10-12 satellites with quite good signal after seconds!

It's a pity that I ripped off one screw from the side during reassembling :eek:

(complete head is away - and the rest of the screws is fixed in its thread - and furthermore its the one with this securing plastics - pahh!)

Now I fixxed this with strong superglue. But on next opening I think I'll drill it out and use bigger screw...

A used phone can look used also inside :D

Thanks again for you valuable help.

(Sorry that I was offtopic - But I wanted to stay in the thread in which S.AMU posted his oringial post)
[Galaxy Ace II Android Development] bebolint98:
[MENTION=5695278]ChronoMonochrome[/MENTION]

What is the changelog in r2.24.5?

Thanks.
[Galaxy Ace II Android Development] shoxieJESUS:
@up

Some chaneges in LP ramdisk.
[Galaxy Ace II Android Development] str3tch72:
I cannot boot it on Omni 5.1.
[Galaxy Ace II Android Development] shoxieJESUS:
@up

If i don't wrong, there are some diff. things in omni ramdisk
[Galaxy Ace II Android Development] ChronoMonochrome:
You shouldn't use ramdisk from cm12.1 on omni, it won't work. The ROM installer has its own ramdisk, you can use it instead of ramdisk for 5.1.x provided in kernel installer.

Yes, but besides of 5.1.x ramdisk update, there's also change HZ @ 500, so it should be smooth than 2.24.4. Using dynamic governor is recommended (it's only optimized for recent HZ change), there are also some more changes to governor in script /etc/init.d/40dynamic - if you feel it makes the system a bit laggy, then just delete it.
[Galaxy Ace II Android Development] nikolas1274:
At omni 5.1.1, i am using zenx and it is very fast, without lag, its great there
[Galaxy Ace II Android Development] jordirpz:
Can i use last kernel in omni? Thnks
[Galaxy Ace II Android Development] nikolas1274:
Omni by chrono (14/05/2015) is using last kernel (2.24.5)
[Galaxy Ace II Android Development] manthes:
Maybe it is faster than 2.24.4 but i have some apps fc. I am using zenx governor
[Galaxy Ace II Android Development] ChronoMonochrome:
Yeah, performance should not be problem here, I was afraid, that it can result much worse battery life than before.

What exactly apps? Can you post logcat?
[Galaxy Ace II Android Development] manthes:
Next time i will do it (it happens rarely but it happens). You mean last_kmsg?

Apps are Habbit browser, Navigon and i have it once with cam app although i don't use your cm 11 but liquid smooth and i didn't have such a problem especially with camera
[Galaxy Ace II Android Development] borkins:
Strange, but I got boot loop on SGA2 logo, when flash codina kernel r2.24.5 on CM11.
[Galaxy Ace II Android Development] bebolint98:
Yes is strange because for me the r2.24.5 on cm11 and now on cm12.1 works I haven't got bootloop after flash.
[Galaxy Ace II Android Development] shaqman89:
Yes, I also got bootloop on CM11. I tried removing all scripts and clearing cache, but it didn't help.

It does works on CM12.1 though.
[Galaxy Ace II Android Development] ChronoMonochrome:
No, I mean logcat, however dmesg also may be useful.

Sorry, I've noticed some extraneous changes to ramdisk, which were applied by accident. For now use ramdisk from 2.24.4, later I'll fix it.
[Galaxy Ace II Android Development] xo.en:
Hm...something creepy just happened to me.

I had 47% of batt, did softreset and i saw..19%. Then 20, then after seconds...21%. It stays like this right now.

Weird, never ssen anything like this before...

I was browsing some sites with 2g before reboot and batt gauge was ok.

You know, i am not entirely sure, if it is on rom side, or kernel, but it is unusual behaviour, if you ask me.
[Galaxy Ace II Android Development] shoxieJESUS:
[MENTION=5695278]ChronoMonochrome[/MENTION]

Any changelog for R2.24.6?
[Galaxy Ace II Android Development] ChronoMonochrome:
This happened because interface fg_refresh was triggered... it's written in initramfs script and done to preserve battery gauge from incorrect percentage showing. By default we have following behaviour: charge may drop after reboot and stay at some point for a while(sometimes very long, because percentage is showing incorrectly) before it'll decreased again. fg_refresh tries to recalibrate gauge.

Just playing with kernel optimizations... Probably later you can expect one more build with even more optimizations, thanks [MENTION=5840412]ace2nutzer[/MENTION] for investigating into it :)
[Galaxy Ace II Android Development] borkins:
For me, r2.24.6 have the same problem with ramdisk, like on r2.24.5
[Galaxy Ace II Android Development] ChronoMonochrome:
Checked it - somehow ramdisk was corrupted after transfer via MTP. Will upload new build soon.
[Galaxy Ace II Android Development] shoxieJESUS:
[MENTION=5695278]ChronoMonochrome[/MENTION]

For me there is no problems with R2.24.5 and R2.24.6

CM11, CM12.1 and BlissPop booted and worked normaly
[Galaxy Ace II Android Development] Bastiary:
[MENTION=5695278]ChronoMonochrome[/MENTION] i tried to use your omni but when i backup my rom on CWM it always fail in backup data, it shows error and then stop. Do you have any solution

Thanks

Edit: it solved. I dunno what happen, but maybe it related titanium backup
[Galaxy Ace II Android Development] str3tch72:
Latest version working on SlimLP?
[Galaxy Ace II Android Development] shaqman89:
Unfortunately for me, 24.5-24.7 gives bootloop in cm11. It works smoothly in Cm 12.1 though
[Galaxy Ace II Android Development] ChronoMonochrome:
Latest version already included on SlimLP.

Try to wipe /ramdisk partition before installation - maybe some remaining files interferes with installation(don't forget to make backup before that). Btw, debugging such behavior may be much easier with last_kmsg.
[Galaxy Ace II Android Development] NeosHaruki:
niccce
[Galaxy Ace II Android Development] nikolas1274:
But I think that when I flash slim yesterday I saw 2.24.5 as kernel.

I can not see now because I restore omni

sent from tapatalk using GT-I8160
[Galaxy Ace II Android Development] xo.en:
Yup, i thought so, anyway it was scary :)

Btw, can we trigger it manually?
[Galaxy Ace II Android Development] niicko96:
I have a problem with this kernel, I do not receive notification messages wathsapp when not in a long time ... to receive notifications have to turn off and on the internet or do I have to enter in the app ...

i now use CM11 ROM and this kernel, but also happened with AOSP 4.4 with this kernel

why?
[Galaxy Ace II Android Development] shoxieJESUS:
@up

Maybe problem not in kernel?
[Galaxy Ace II Android Development] niicko96:
I have this problem only with this kernel and do not understand what is wrong ... I'm sorry for this because this is a great kernel ... I asked here to tell if it's just my problem
[Galaxy Ace II Android Development] matthias1976:
I got same problem
[Galaxy Ace II Android Development] ChronoMonochrome:
Yes, it can be triggered via sysfs interface /sys/kernel/abb_fg/fg_refresh (just write something in this file).
[Galaxy Ace II Android Development] sleepless9:
Looks like I soft-bricked my phone and can only enter download mode. Searching older posts I see there was an odin flashable kernel in google drive, but the google drive link no longer exists in the OP. Can someone send me a link to download it? An odin flashable f2fs-enabled TWRP would probably be fine too...

EDIT: Also, do I need to do extra steps since I use f2fs? Maybe revert to ext4 somehow? Or use some modified version of Odin?
[Galaxy Ace II Android Development] ChronoMonochrome:
https://drive.google.com/folderview?id=0B_OwIFfWQnj_Y2dxMDJJcVRUV3c&usp=sharing

p.s. use f2fs version.
[Galaxy Ace II Android Development] sleepless9:
Thank you. I recovered my phone with no problems using the f2fs cwm version.
[Galaxy Ace II Android Development] manthes:
I have a strange problem and i don't know if it is kernels problem or not. While trying to install some roms they recognize my device as codinap and they stopped the installation.
[Galaxy Ace II Android Development] shoxieJESUS:
@up

I had this problem too.

Redownload kernel from codina folder, in TWRP format ramdisk partition and flash kernel

Profit.
[Galaxy Ace II Android Development] manthes:
My mistake. I was touching codina ftp but probably because i am using 210 lcd density it was loading codinap folder.
[Galaxy Ace II Android Development] mars_army:
If anybody didn't forget about ChronoKernel Settings, here you can find the new version.
[Galaxy Ace II Android Development] xo.en:
Material skins are great. Program seems to work perfectly.

Btw: boot time with 2.24.7 and modded/optimized slimkat: 7974msecs.

Amazing 2d performance, big maps' tiles in locus load so fast...heavy sites in habit browser work insaneously fluid...canabalt works totally great(s6d, lcd set to 60hz) here.

Interesting thing: 2.24.7 can run my device at 1.2ghz, while older ones could not.

What is interesting: 1.150mhz seems to work better, than 1.2ghz here...anyway: antutu(dalvik) at 1.2ghz+560gpu: 14782(weirdly same as with 1150mhz).

Great i/o performance.

In real life 700mhz max works better, than old 800mhz.

Overall thought: a-ma-zing.

One weird thing: i cannot switch to ART with slimkat..hm.

You will not push this baby much further, Chrono, i am afraid :)

Sidenote: someone ported half-life exe to android(so we can run hf like an original one), game runs at 35-75 fps at 800 mhz, DAMN!

Even config.cfg/autoexec seems to work. msaax4 is not working, tho.

USBhost..where are you...

(screenshots made before IQ bump)
[Galaxy Ace II Android Development] ChronoMonochrome:
Glad to hear that it works fine :)

Sounds like generic issue.. I tried to compile SlimKat and one reason why didn't pushed it(besides of camera that I messed up) was not working ART.

I'm currently working on memory management optimization - so maybe later I'll push release(without any promises though - cause this is really difficult to not make it worse rather than better). After I read your posts I started to think, that this is quite inoptimized.
[Galaxy Ace II Android Development] xo.en:
Hmmm, that's interesting. So you knew about slimkat's art issue then :) system seems to copy lib needed to switch, but..hmmm,maybe it is NOT? If it is simple lack of proper lib exchange, it could be easily..fixable(definitely art lib is not activated/copied)?

But your personal opinion is needed here: does art really changes...anything?

I mean compatibility of software/stability vs speed/batt gain?

Is it worth it?

I mean i know that google is pushing it as future way, but some older android fanatics are considering it as ...semi-way(not exactly linux way, that is), even - wrong way(at this stage of developement, i mean).
[Galaxy Ace II Android Development] ChronoMonochrome:
It wasn't due to not switching lib. Something was wrong with ART implementation, and I'm afraid it's too difficult to say what exactly. In my opinion ART is working great in compare with dalvik. This difference is quite noticeable even without benchmarking. I can't say much about compatibility of apps - probably there are still chances that some app might not work, but many of them are compatible with ART.

I don't quite understand it - ART simply better because apps are running in native machine code when dalvik - not, that's it.
[Galaxy Ace II Android Development] xo.en:
Yup, this is obvious.

Yeah, until it works. :)
[Galaxy Ace II Android Development] zizoumadrid:
can you share with us your full settings cpu/gpu thanks
[Galaxy Ace II Android Development] xo.en:
Actually:

dalvik, dynamic fsync, 60hz(default), 192dpi, cpu 800mhz(or 700mhz), gpu 480mhz,

interactive/tripndroid(or zen), gpu: -12.5mV, mali l2: 48kB, malimem: 24mb, disabled spi crc, NO zram, reduced number of clusters, (u)KSM on, minfree set to "light", repacked apks and framework,

and LOTS of init.d scripts(i.e. for custom VM settings).

Antutu:12307.

OC was made with same settings, just 1.2ghz cpu, 560mhz gpu.

Antutu:14848.

Soft used: chronokernelsettings+performance control.
[Galaxy Ace II Android Development] xo.en:
Hm, i noticed small bug - 2.24.7 shows itself as 2.24.6?
[Galaxy Ace II Android Development] str3tch72:
For me too.
[Galaxy Ace II Android Development] str3tch72:
Will it work on RootBox 4.2? I think this kernel causes bootloop on this ROM.
[Galaxy Ace II Android Development] ChronoMonochrome:
Yes, just forgot to change version number)

Yes, it should work - read manual about kernel instalation on not supported(by default installer) ROMs.
[Galaxy Ace II Android Development] str3tch72:
MAybe I am really noob, but can You send me this file for 4.2?

---------- Post added at 10:43 PM ---------- Previous post was at 10:42 PM ----------

Or better do special verision of kernel, I'm really dissapointed. On all 4.4 ROMs it worked really good.
[Galaxy Ace II Android Development] ChronoMonochrome:
Yes, if you can upload rootbox's 4.2 kernel somewhere I can extract ramdisk from it.

This is really not good idea - there are so many ROMs so it's almost not possible to create installers for them. That's why I even didn't create kernel versions for SlimLP or Omni ROM.
[Galaxy Ace II Android Development] str3tch72:
In a minute bro, uploading.

---------- Post added at 10:58 PM ---------- Previous post was at 10:55 PM ----------

https://www.dropbox.com/s/ox66bl52etzaex9/boot.img?dl=0

---------- Post added at 11:00 PM ---------- Previous post was at 10:58 PM ----------

And if You do it, please tell me where I should paste this ramdisk file in zip with kernel, thannks Chrono, You are great! :)
[Galaxy Ace II Android Development] ChronoMonochrome:
Attached ramdisk below - use it at your risk - I haven't tested it.

Sorry - as I explained already, it's actually pain to create installers for every ROM. This is not difficult at all - you only have put this file in /ramdisk after you've installed chrono kernel. Easier way is use TWRP for that since it includes filemanager.
[Galaxy Ace II Android Development] str3tch72:
Thanks, it... just works. :D
[Galaxy Ace II Android Development] Alex_Gamer:
Why do you install a jb rom?
[Galaxy Ace II Android Development] manthes:
Some times after reboot wifi isn't working. It happens with latest build and with 2.24.6
[Galaxy Ace II Android Development] xo.en:
..something weird had happened to me today - i got into airplane mode for a night, then, after few hours airplane mode off led me to total signal loss, needed to reboot to get it working. Never seen this with older line of kernel.
[Galaxy Ace II Android Development] fluffi444:
Have this also. But this happens only (with my phone) if phone does an reboot because something went wrong

(because of DDROC :) - happens only if I fiddle around with phone during phone boot and DDROC script running)

With self made reboot or shutdown and boot I do not have this.

But I quite sure that I have this behaviour for quite a long time over many kernel versions.
[Galaxy Ace II Android Development] xo.en:
Hmm, it seems, that we have new chronokernelsettings.

Ok, here is newer one:

http://xdaforums.com/showpost.php?p=61197839&postcount=3142
[Galaxy Ace II Android Development] borkins:
[MENTION=5695278]ChronoMonochrome[/MENTION],

I'm trying to make DDR OC more stable, but I'm still not sure why it causes reboots.

Once i made the script to OC for about 35 min between 798, 975, 1098 without reboot.

I added mob. data and wifi control and changed the CPU usage calculation for optimal time for OC - when the CPU is at minimal usage. But later the same sctipt causes reboots. :/

I think the CPU usage is crucial, but there is always some process that may appear in that moment. I'm trying to solve this somehow.

But maybe there is something else that may brings instability when switching the clock.

Any information about the pll ddr clk and how the other clk are caculated when OC - may be helpful.

I searched about that, but i didn't found helpful info.

I'm wondering about another thing: Why 975 MHz, but not 998 MHz? You said, that above 975 MHz may cause data corruption.

I tried clocks under 1190 MHz, and i got some corruption in FS at about 1150 MHz.

So, looks its really useless to OC above 1098 MHz. :] I didn't test 1098 MHz for a longer time - maybe that clk can cause corruption too. IDK.

If there is no problem with the other clocks when oc pll ddr, I can add some pll ddr clocks between 975 - 1098 MHz in the script.

If you have some time, any help is welcome. :)
[Galaxy Ace II Android Development] ChronoMonochrome:
I believe there is no way to make it stably with only exception of wholly rewriting DDR OC things in kernel. The main problem is that PLLDDR can't be changed on-the-fly without causing side effects to the system - too many things are dependant on it. Another way is rebasing all dependent CLKs on PLLSOC1 - however that way LCDCLK doesn't work well (resulting freq is too low, and I haven't managed to OC it). But I don't know whether rebasing CLKs to PLLSOC1 is better than just OCing DDR usual way - still requires display to be disabled, since SDMMCCLK, LCDCLK, MCDECLK or/and HDMICLK (I can't remember which exactly - last time I messed with this stuff few months ago) can't handle any change to it when are enabled.

Because aforementetion CLKs doesn't handle OC over 975 MHz when they are enabled. LCDCLK, MCDECLK and HDMICLK can be safely disabled by simple turning off the display, but I doubt if there's way to forcibly disable SDMMCCLK - probably this itself might cause data corruption.

Why exactly 975 MHz? I still can't explain this, I have only some guesses about that. 975 MHz (PLL = 0x0005017f - divisor is highlighted with red, multiplier - blue). In binary representation 0x7f == 01111111 . Every pll being changed bit-by-bit, there is no way another than that. When we are trying to change it to 0x80 - it may lead two possible cases:

1) value bit-by-bit changed to 00000000 (0x00). - PLLDDR is set to zero.

2) value changed to 11111111 (0xff) - much more than 1200 MHz, too high!

Somehow changing divisor leads to immediate reboot. I have managed change it to 0x03, after rebasing all PLLDDR dependant clocks to PLLSOC1, but as I said, it didn't appear that these clocks are working properly (sometimes it causes weird artifacts, besides of that LCDCLK is too low).
[Galaxy Ace II Android Development] borkins:
I tested tsome of these:

0x00050180 = 982 MHz

0x00050182 = 998 MHz

0x00050186 = 1029 MHz

0x00050188 = 1044 MHz

0x00050189 = 1052 MHz

0x00050196 = 1152 MHz

0x00050197 = 1159 MHz

So these freqs are showed in pllddr, but they are not the real ones?

Thank you for your time!
[Galaxy Ace II Android Development] ChronoMonochrome:
Why? They are real. These can be set, but only when aforementioned CLKs are off. That's why OC over 975 MHz mostly very unstable.
[Galaxy Ace II Android Development] LS.xD:
Does Chrono Kernel 2.24.7 support SELINUX ? I tried BlissPop v3.3 and the description says that I need a custom kernel /w SELINUX support.
[Galaxy Ace II Android Development] Lupus@dei:
We need kernel that can read selinux contexts. We don't need full selinux support. CK can do that, ace2nutzer's can't.
[Galaxy Ace II Android Development] xo.en:
Well, since nobody posted it here yet, there's newer version of chronokernelsettings available...

Replace old version(copy it to /system/app/*, and remove old one), then set apk to 644, reboot.

It should use previous settings, so you do not need to set it all up from scratch:
[Galaxy Ace II Android Development] fluffi444:
Hey ChronoMonochrome.

I tried recently to install 2.24.7 P kernel to girlfriend's phone.

But it does not work.

Tried then 2.24.6 P but the same.

Then I used 2.24.3 P which she hat installed before and it works.

Both not working gave me stuck at Samsung logo. No CM bootlogo.

Any idea?

CM11 05.05.2015
[Galaxy Ace II Android Development] borkins:
Maybe is the same problem like on my codina ( CM11 28.04.15 ).

Kernels from r2.24.5 to r2.24.7 bootloops on SGA2 logo.

I tried to wipe everything, but nothing helped.

It's strange, but for the most devices there is no such problem.
[Galaxy Ace II Android Development] fluffi444:
Exactly the same. It's also here stuck and then boot loop before CM logo comes.

And 2.24.4 is the last working one...