Thread closed.
Last edited:
For those using TWRP Recovery, I've updated the installer (v1.5a) to make it compatible with TWRP.
It still works totally fine with CWM as well, so you can use your preferred recovery
If you already are on v1.5, no need to reflash, there's nothing new in the kernel / Aroma Menu.
JP.
For those using TWRP Recovery, I've updated the installer (v1.5a) to make it compatible with TWRP.
It still works totally fine with CWM as well, so you can use your preferred recovery
If you already are on v1.5, no need to reflash, there's nothing new in the kernel / Aroma Menu.
JP.
I flash it and even the installation went OK when I go in About phone it shows the Kernel I used before flashing this one. Since I used Franco's kernel it still says that I am on that Kernel.
Is this only happen to me?![]()
Can you flash it again and save the logs (button in aroma after flashing) and post the logfile for me to have a look ?
JP.
Sent from my HTC Sensation Z710e using xda app-developers app
Sorry, sorry, sorry...![]()
It was my mistake. And I saw that when tried to flash it again. At the end of installation I selected Flash script and not flash kernel and that was my mistake. Now I choose the right one and it's all OK.![]()
Sorry for this...I will test it a few hours and give you my feedback.
![]()
Lol Ninolina just a guess but I think you don't have to sorry for anything!We are all learning in here
Maybe from this Yank could add a "(default)" on that option? or kinda to avoid mistakes¿
Lol Ninolina just a guess but I think you don't have to sorry for anything!We are all learning in here
Maybe from this Yank could add a "(default)" on that option? or kinda to avoid mistakes¿
Btw yank, before sleep time, what you think about the readahead buffers some lower by default? I had some handups when multitasking hard and using 3Mb, on 512Kb still no related issue for nowEven the "benefits" are hard to detect (even they are there I swear!) the "hickups" are easily detected
You could try yourself by switching to maybe even higher lvl's if you hadn't done it already. What you think on putting them a little bit down for the common user who has no clue on how this works?
PS: Multitasking meaning using internet or whatsapp while downloading some huge item like a film, where you have the SD card burning![]()
Can do. I used to have them at 2Mb, upped them to 3Mb on the Sammy. Might be a bit too much ... if you do sequential reads it should help, but if it's random access it sure will generate unnecessary overhead.
What value works best for you ? 512 ? Have you tested 1024 ?
JP.
Sent from my custom ARHD 11.0.0 / Yank555.lu JB kernel v1.5a Aroma (Linux 3.0.38) powered Samsung Galaxy S3 using xda premium
Nt yet, initially I tested 256 and all went good, now up to 512 for some days, may go up to 1Mb if u wish
Any ideas on how to test the "good" situation to use it (for benefits) and the "bad" (for the "hickups")? You know way better than me how this works P And even if it's nearly unnoticeable all learnt is welcome![]()
Based on PegasusQ. Introducing cpu frequency limitations based on the number of cores online.
sysfs additions :
- cpu_max_freq_1 : max. freq. applied when running on 1 core (defaults to 1.0GHz)
- cpu_max_freq_2 : max. freq. applied when running on 2 cores (defaults to 1.1GHz)
- cpu_max_freq_3 : max. freq. applied when running on 3 cores (defaults to 1.2GHz)
- cpu_max_freq_4 : max. freq. applied when running on 4 cores (defaults to 1.4GHz)
- cpu_max_freq_current : currently applied max. frequency (read-only)
NB: hotplug frequencies and rq thresholds have been revised up to keep the device running on as little cores as possible.