Thank you very much for your continued efforts manR61 was focused on smooth scrolling, fast reaction and better battery life, at the cost of lower bench score in multi-core.
R62 will fix that, without to loose the other benefits from R61.
Rollback is not possible at this moment.
Sorry for the inconvenience.
Yes I am. But I have some serious stability issues right now, may just be my silicon, may be the kernel. No panics, no demsg.Ooh nice you're making an A13 Custom Kernel with Ace's sources?
to me the processor easily reaches 95 degrees without losing performanceCiao Dev! Ho una domanda per te
La nuova versione ha il limite di temperatura predefinito della CPU (o il limite di temperatura di avvio, idk come si chiama) a 57c?
Sento che il telefono è piuttosto lento prima che si applichino le impostazioni A2N, quindi controlla la temperatura della CPU con AIDA64 e la temperatura raggiunge il picco a 57 e la velocità di clock è molto bassa su un core grande.
Mi piacerebbe che la temperatura predefinita aumentasse a 65 o 70 °C, quindi sarà più veloce.
Grazie mille!
A13 is very different from A9. It creates a series of new problems to deal with.Yes I am. But I have some serious stability issues right now, may just be my silicon, may be the kernel. No panics, no demsg.
Yes already fully optimized except LTO as it's not supported with our sources. I don't want to add further bugs. The kernel doesn't need such extreme low-level code optimizations since it's smart enough. But applied to the ROM LTO can make big performance improvements, especially for performance sensitive binaries like ffmpeg and the other software codecs.Ace does the Kernel already make use of compilation flags (o3, thinlto, etc), arm optimized asm for mem ops, etc, to improve CPU performance? Or can this stuff not be implemented?
No, sorry, it's max 60 °C to avoid overheating after wiping dalvik-cache.Hi Dev! I have a question for you
Is the new version has the CPU default temp limit (or boot temp limit, idk what it is called) at 57c ?
I feel that the phone is quite sluggish before the A2N settings apply, so I check the CPU temp with AIDA64 and the temp is peaked at 57 and clock speed is very low on big core.
I'd love to have the default temp increase to like 65 or 70c, so it will be faster.
Thank you so much!
I see, that's also okay. that answer the question why my phone is weirdly cool during the optimization (I always put it on top of my air purifier after the dalvik-cache wipe since it should be quite hot lol)No, sorry, it's max 60 °C to avoid overheating after wiping dalvik-cache.
Hi Guys,
even the fact that I'd stated that I'll no longer update this kernel ....
But I couldn't let it be and therefore ....
HERE WE GO AGAIN:
Changelog
A2N Kernel R61
- RAM: improved memory management and fixed bug
- USB: fixed tethering instability issue (needs more testing)
- GPU: trigger kernel panic on GPU fault instead to issue a soft-reset
- Removed buggy gaming_mode
- GPU power-policy: force to use "coarse_demand" on suspend if "always_on" is enabled - saves battery (around 30 mA!)
- CPU/GPU DVFS: reduced "gpu_dvfs_sleep_time" from 8 to 4 ms
- GPU: fixed soft-reset issue caused by buggy HMP driver - this should fix GPU freezes and lags!
- HMP: fixed bugs and adjusted tunables to be more aggressive - (faster and smoother)
- CPU: updated ondemand gov
- CPU: updated input-booster driver to be more efficient (more smooth, less battery draining!)
- GPU: disabled shader cores hotplugging for better performance!
- Updated ramdisk
A2N Kernel Control V61
DOWNLOAD KERNEL
- CPU/GPU DVFS: added ability to check "Peak Temperature"
- Misc: LED-RGB: added power control
- CPU-BIG: removed CPU-Hotplug feature (redundant)
- GPU: replaced "Gaming Mode" with "Boost"
- GPU: added power-policy for "Always On"
- CPU-BIG: merged "Input Booster" into "Boost"
- CPU-LIT: removed "Boost" (redundant)
- Audio: moved "PM-QOS" to "Debug" menu
- Fixed bugs and improved performance
Flash and enjoy!
Sure you get around + 1 - 2 MB RAM if you compile the boot.img with -O2 instead of the higher optimizationslevel -O3 lol.@ace2nutzer try and beat this amount of ram! (Thanks to Ivan Meler)
The zImage or AIK? Just saw this and was like lol. Ivan(the los dev) did this.Sure you get around + 1 - 2 MB RAM if you compile the boot.img with -O2 instead of the higher optimizationslevel -O3 lol.
zImage ....The zImage or AIK? Just saw this and was like lol. Ivan(the los dev) did this.
Eeh... don't feel like it's worh it, boot is already taking ~30s is it faster in your kernel? If so, how did you manage to lower boot times?zImage ....
Ramdisk you could use gzip compression instead of LZ4 to save some more RAM... but that will make booting as slow like the Samsung stock kernel.
As I already said, you can compress your ramdisk with LZ4 in AIK (if not already), instead like in stock kernel with slow gzip compression.Eeh... don't feel like it's worh it, boot is already taking ~30s is it faster in your kernel? If so, how did you manage to lower boot times?
Impressive. Very nice. Now let’s see some benchmarks@ace2nutzer try and beat this amount of ram! (Thanks to Ivan Meler)
I have lineage boot logo bc rom, but yes i think it is compressed with LZ4 already.As I already said, you can compress your ramdisk with LZ4 in AIK (if not already), instead like in stock kernel with slow gzip compression.
For me the first SAMSUNG boot-logo disappears 2x faster.
So far I didn't change the source code since R62. But R63 is planned as a final release. It'll solve some regression in HMP and GPU driver. In addition it'll bring back some removed features as requested by some users from Play Store.
Like the a2n app loads a default profile and you need to load the wanted profile yourself?I think that A2N Kernel Manager app needs to change the way profiles are applied. For example, due to my weak battery, if I run Big at 2652MHz and I crash while I'm at it, once I reboot and A2N Manager tries to apply the settings, my phone immediately crashes again, and it starts doing this cycle infinitely. In my humble opinion, I think people should have the chance to use the more traditional Profiles menu where they can choose separately the one they want to load from the ones they make AFTER the A2N Manager loaded and did the license check. That way the phone won't crash in these circumstances unless the user makes it happen again.
Check in debug menu. There are 2 options. Read carefully what they do.Correct. Because currentl the A2N App simply loads the latest config and that causes me to crash endlessly and forces me to wipe app data.
No, it'll not. Read the changelog.Thing is that option will completely reset my profile. At the end of the day it's the same as wiping app data. My point here is that I don't want to lose all my settings to an unstable CPU frequency. Resizing ZRAM is a pain everytime.
Either way I understand that implementing a profiles system in the app would probably be very taxing. So that's no big deal. This "disable restore settings" options will still come in fairly useful. Thanks for pointing it out![]()