In 2015, Galaxy S3 is a quite old device. It was introduced in 2012, with a lot of supporters around the world. I think it is the best smartphone of Samsung ever. And in 2015, it is still a good phone with latest software update from other developers
These are my combinations of roms, kernels, mods and tweaks of my Galaxy S3 (i9300). I think it is the best combination ever, with good performance and experience. Remember that this is my own opinion, so maybe it won't appropriate with somebody. Anyway, let's get start!!!
ROM
Cyanogenmod is undoubtedly the most popular and best-performance rom ever. It is based on Stock Android, so it runs very smooth and has brilliant performance, especially in Benchmark Test. Android 5.0 Lollipop is released, then our S3 has a very good CM12 rom with latest software version. I have used this rom for 4 months, and I do not expect anything more about my phone because it runs PERFECTLY.
Link for Cyanogenmod 12 rom: http://forum.xda-developers.com/galaxy-s3/development/wip-cyanogenmod-12-t2936990
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
KERNEL
Since Siyah kernel is end-of-development, Boeffla Kernel is a perfect alternative. This kernel brings us a lot of things : change CPU governers, overclock CPU (up to 1600 Mhz) and GPU (640 Mhz), sound tweaks, undervolt CPU and GPU, etc. It lets us to control our devices freely and effectively. It also gives us brilliant battery performance.
Links for Boeffla Kernel i9300: http://forum.xda-developers.com/gal...rnel-boeffla-kernel-2-2-stable-27-03-t2449408
MODS
When I bought my Galaxy S3, I soon realized that is had a poor sound experience. So I looked for a sound mods that it improves my phone speaker. And fortunately, I have found a thread that had an amazing work: ACID Audio Engine. It gives me many positive improvements with i9300 sounds, and I have the best sound experience ever.
Link for ACID Audio Engine mod: http://forum.xda-developers.com/galaxy-s3/development/mod-acid-audio-engine-v5-0-samsung-t2002197
APPS & GAMES
I am a student, so I do not have much working or business apps. These app below are mostly entertaining apps : music, games,…
Google Camera: easy, simple and functional interface
https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera
Inbox by Google: a beautiful Material Design email app, and officially published by Google
https://play.google.com/store/apps/details?id=com.google.android.apps.inbox
Google Keep: easy for taking notes with texts, images and many cute symbols…
https://play.google.com/store/apps/details?id=com.google.android.keep
Zedge: up-to-date beautiful wallpapers, ringtones and other stuffs.
https://play.google.com/store/apps/details?id=net.zedge.android
Wolfram Alpha: as a student, I have to do a lot of calculating exercises. This app is my perfect assistant at school, especially in Maths lessons.
https://play.google.com/store/apps/details?id=com.wolfram.android.alpha
Fenix: my daily Twitter app
https://play.google.com/store/apps/details?id=it.mvilla.android.fenix
Seeder: it is undeniable that many Android devices become slower and slower after long time using them. Seeder helps us to prevent this problem. It gives us a smooth experience with no lags and FC’s.
http://forum.xda-developers.com/showthread.php?t=1987032
Xposed Installer + Gravity Box(LP) : best apps for interface editing, mods, and tweaks
http://forum.xda-developers.com/showthread.php?t=3034811
Ram Manager Pro: a lot of RAM options, swap RAM (up to 2GB), friendly interface.
https://play.google.com/store/apps/details?id=com.smartprojects.RAMOptimizationFree
FIFA 15: Since FIFA 16, in my opinion, is not as good as FIFA 15 (graphics problems, worse user interface,…), I am still playing with my own Ultimate Team. Best Sport app ever.
https://play.google.com/store/apps/details?id=com.ea.game.fifa15_row
Asphalt 8: Racing games with a lot of cars, roads and game modes, brilliant graphics.
https://play.google.com/store/apps/details?id=com.gameloft.android.ANMP.GloftA8HM
Leo’s Fortune: This is the best graphics games ever…
https://play.google.com/store/apps/details?id=com.leosfortune
TWEAKS & SELF-EXPERIENCE
CPU governer: ondemand
I/O Scheduler: deadline
Max freq: 1400 Mhz
Min freg: 200 Mhz
Undervolt CPU: -75mV
GPU freq: 160/266/350/440/533
GPU undervolt: -75mV
Build.prop tweaks:
Fast Reboot
persist.sys.purgeable_assets=1
Render UI with GPU
debug.sf.hw=1
Increasing It Will Make Mobile Smoother
windowsmgr.maxevents_per_sec=150
Video Acceleration Enabled
video.accelerate.hw=1
Increase Performance
debug.performance.tuning=1
Disable Sending Usage Data
ro.config.nocheckin=1
Deeper Sleep / Better Battery Life
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
Disable BootAnimation
debug.sf.nobootanimation=1
Faster Scrolling
ro.max.flingvelocity=12000ro.min.fling_velocity=8000
sorry for this,but,either u are not informed on whats going on these days,or just lack of knowledge.
this version you chose as your rom is EOL state,and its much worse than any rom IMO (memory leaks,stagefright not patched etc). the best rom right now is AD latest or B19 from archi as well.
kernel-wise,boeffla is EOL state again,he only update ramdisk,so this is just for campatibility still active.while things starting to end for this phone,archi wow us every single time,and archikernel latest is the most "optimized" for this phone along with his roms...
I/O sheduler-wise, deadline and noop is known to low speeds and performance crippling..best shedulers for our phone are BFQ latest,and CFQ.
ROW is better generally but not for I9300.it sucks.
You should never undervolt processor especially -75!! GPU as well. games will lag.
But this guide is,from my point of view,battery life driven.
but i would not get crazy for battery life anymore because anyways battery is fcked up so many years,especially stock.the only thing u will achieve is at best half an hour screen on time.not worth it for me
as for build prop tweaks,dont even touch it anymore,its not worth it,plus archi have better build prop tweaks and generally well made Roms.
*flies away*
My best setup is Archidroid + ArchiKernel
Cpu voltages table:
1400 1.1375V
1300 1.1V
1200 1.075V
1100 1.025V
1000 0.95V
900 0.925V
800 0.9V
700 0.875V
600 0.85V
500 0.825V
400 0.8V
300 0.8V
200 0.8V
GPU:
700 - 1.175V
600 - 1.0625V
440 - 0.9375V
300 - 0.8375V
150 - 0.7375V
CPU Governor: lulzactiveQ
CPU States: IDLE + LPA + AFTR
eMMC/SD Governor row/cfq
I think, that we can undervolt our SoC much lower, but not by setting same '-xx mV' value for all profiles, i spend about 2 hours for testing voltages on every profile. I descended to 0.8V on CPU, lower values were giving me a lot of freezes and lags. On GPU i set 0.7V (Boeffla kernel) and image went away. My ASV level is 3. I also tried it on other i9300 @ 2LVL ASV, GPU was working with same voltages. But CPU wanted extra 25mV for every profile from my table.
I also saw one more thing, ArchiKernel requies higher voltages, but it's harder to freeze phone (especially GPU) than on Boeffla.
Sorry for my bad english, i'll improve that - i promise
i wish i didnt sold my s3 :/
How to undervolt?
Sent from my Be_Pure using XDA Free mobile app
The Funky Pear said:
sorry for this,but,either u are not informed on whats going on these days,or just lack of knowledge.
this version you chose as your rom is EOL state,and its much worse than any rom IMO (memory leaks,stagefright not patched etc). the best rom right now is AD latest or B19 from archi as well.
kernel-wise,boeffla is EOL state again,he only update ramdisk,so this is just for campatibility still active.while things starting to end for this phone,archi wow us every single time,and archikernel latest is the most "optimized" for this phone along with his roms...
I/O sheduler-wise, deadline and noop is known to low speeds and performance crippling..best shedulers for our phone are BFQ latest,and CFQ.
ROW is better generally but not for I9300.it sucks.
You should never undervolt processor especially -75!! GPU as well. games will lag.
But this guide is,from my point of view,battery life driven.
but i would not get crazy for battery life anymore because anyways battery is fcked up so many years,especially stock.the only thing u will achieve is at best half an hour screen on time.not worth it for me
as for build prop tweaks,dont even touch it anymore,its not worth it,plus archi have better build prop tweaks and generally well made Roms.
*flies away*
Click to expand...
Click to collapse
Hi The Funky Pear!!
Can you post here your complete kernel config on synapse?
Thanks in advance
_nEoN_ said:
Hi The Funky Pear!!
Can you post here your complete kernel config on synapse?
Thanks in advance
Click to expand...
Click to collapse
of course! feel free to ask anything!! will post screenshots because its easier
what is "ad latest" rom?
mkdr said:
what is "ad latest" rom?
Click to expand...
Click to collapse
here u go: http://forum.xda-developers.com/galaxy-s3/development/rom-archidroid-v2-4-6-power-hands-t2354859
Related
★ ☆ [Kernel] NuK3RN3L | s2w+s2s | 01-21-14 | 1,900MHz | 3.0.84 | Sense/AOSP | ☆ ★
-NuK3RN3L-
OVERCLOCKED
Edition
Now added!
Santod's Mecha ICS Sense/AOSP Kernel
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DOWNLOAD:
NuK3rn3l mecha Final
sweep2wake
sweep2sleep
16 Governors
TCP Controls
Zram/Swap
Linaro
OTG
01-20-14
Use Trickster Mod to enable Wake options
You need an updated version of Busybox from the Play Store to use Trickster Mod.
Once that's installed, open it and run the installer.
Then you can install Trickster Mod, grant it su permissions, and use it to enable s2w+s2s and adjust all other kernel settings and tweaks.
Trickster Mod can be found here.
-NuK3RN3L-
stock frequencies
current build
~ or ~
NuK3RN3L-
Overclocked Edition
1,516MHz Default/Max
current build 6-25-13
+ LagFree
-NuK3RN3L-
Aosp NuK3RN3L, with working wifi on Aosp ICS and Jelly Bean.
Only use this for this one on Aosp roms. (CM9/CM10)
[URL="http://www.androidfilehost.com/?fid=23017610006233856"]NuK3RN3L ICS/JB Aosp OC Edition
[/URL]
These have been well tested, but use at your own risk!
I am not responsible for you or your device or anything that you do to it!
Included Governors:
SavagedZen
lulzactive
adaptive
hyper
scary
skywalker
brazilianwax
fantasy
SmartassV2
interactive
conservative
userspace
powersave
lionheart
ondemand
performance
How to install:
Flash zip in Recovery
Wipe cache and Dalvik cache
Reboot
This can be flashed to any current ICS roms!
Sense and AOSP!
NuK3RN3L was initially built for Sense roms, it has been confirmed to be working on Joe Black's latest CM9 build, though it needs a little camera patching...
Looks like we may have an AOSP/Sense ICS Hybrid Kernel.
On Aosp, Data and Netflix do work, camcorder not yet.
Will work on things with Joe to improve this.
Click to expand...
Click to collapse
I will try and update my git repo every 7-90 days until I automate it into my buildbox process...
Compiled using the 4.4.3 gcc toolchain.
Big thanks to my buddy Ziggy for his help and inspiration.
XXPachaXX for his work on msm7x30
Flemmard for his work on msm7x30
Also to HTC for finally releasing the source code...
HTCDEV Source files: my copy
FAQ:
Hopefully this answers some common questions.
I will add to this as kernel changes are made.
On UnSenseROM Jelato, there is a script in /system/etc/init.d called 00_vdd_levels if I recall the name exactly.
It's essentially a text file that should be either deleted, or remove the ## from the name of it so it doesn't run at boot.
Then whatever app is used to control governors and clock speeds will not get reset upon rebooting, whether you use the built in CPU Controls or No Frills, etc,..
On my other roms, the same rule applies, if there is a script in /system/etc/init.d with vdd levels in the name, remove it or rename it.
On NuSenseX ROM you should be careful touching anything in init.d, or you could break your wifi connection.
Soon, I intend to have kernels that will be baked into each rom, and there will be no need to concern oneself with any of this, and it's really nothing of much concern anyhow.
But I think that about covers most cases...
____
GOVERNORS
1) Ondemand:
Default governor in almost all stock kernels.
One main goal of the ondemand governor is to switch to max frequency as soon as there is a CPU activity detected to ensure the responsiveness of the system.
Effectively, it uses the CPU busy time as the answer to "how critical is performance right now" question.
So Ondemand jumps to maximum frequency when CPU is busy and decreases the frequency gradually when CPU is less loaded/apporaching idle.
Even though many of us consider this a reliable governor, it falls short on battery saving and performance on default settings.
One potential reason for ondemand governor being not very power efficient is that the governor decide the next target frequency by instant requirement during sampling interval.
The instant requirement can respond quickly to workload change, but it does not usually reflect workloads real CPU usage requirement in a short enough time and it may cause it to frequently change between highest and lowest frequency.
2) Conservative:
A slower Ondemand which scales up slowly to save battery.
The conservative governor is based on the ondemand governor.
It functions like the Ondemand governor by dynamically adjusting frequencies based on processor utilization.
However, the conservative governor increases and decreases CPU speed more gradually.
Simply put, this governor increases the frequency step by step on CPU load and jumps to lowest frequency on CPU idle.
Conservative governor aims to dynamically adjust the CPU frequency to current utilization, without jumping to max frequency.
The sampling_down_factor value acts as a negative multiplier of sampling_rate to reduce the frequency that the scheduler samples the CPU utilization.
For example, if sampling_rate equal to 20,000 and sampling_down_factor is 2, the governor samples the CPU utilization every 40,000 microseconds.
3) Interactive:
(currently my recommended governor for best overall battery and performance)
Can be considered a faster ondemand. So - more snappier, less battery!
Interactive is designed for latency-sensitive, interactive workloads.
Instead of sampling at every interval like ondemand, it determines how to scale up when CPU comes out of idle.
The governor has the following advantages:
1) More consistent ramping, because existing governors do their CPU load sampling in a workqueue context, but interactive governor does this in a timer context, which gives more consistent CPU load sampling.
2) Higher priority for CPU frequency increase, thus giving the remaining tasks the CPU performance benefit, unlike existing governors which schedule ramp-up work to occur after your performance starved tasks have completed.
Interactive - It's an intelligent Ondemand because of stability optimizations. Why??
Sampling the CPU load every X ms (like Ondemand) can lead to under-powering the CPU for X ms, leading to dropped frames, stuttering UI, etc.
Instead of sampling the CPU at a specified rate, the interactive governor will check whether to scale the CPU frequency up soon after coming out of idle.
When the CPU comes out of idle, a timer is configured to fire within 1-2 ticks.
If the CPU is very busy between exiting idle and when the timer fires, then we assume the CPU is underpowered and ramp to max frequency.
4) Userspace:
Instead of automatically determining frequencies, lets user set frequencies.
5) Powersave:
Locks max frequency to min frequency.
Can not be used as a screen-on or even screen-off (if scaling min frequency is too low).
6) Performance:
Sets min frequency to max frequency.
Use this while benchmarking!
7) SmartassV2:
Version 2 of the original smartass governor from Erasmux. Another favorite for many a people.
The governor aim for an "ideal frequency", and ramp up more aggressively towards this freq and less aggressive after.
It uses different ideal frequencies for screen on and screen off, namely awake_ideal_freq and sleep_ideal_freq.
This governor scales down CPU very fast (to hit sleep_ideal_freq soon) while screen is off and scales up rapidly to awake_ideal_freq (500 mhz for GS2 by default) when screen is on.
There's no upper limit for frequency while screen is off (unlike Smartass).
So the entire frequency range is available for the governor to use during screen-on and screen-off state.
The motto of this governor is another option for balance between performance and battery.
8) Lulzactive:
Basically interactive governor with added smartass bits and variable (as opposed to fixed amout) frequency scaling, based on currently occuring cpu loads.
Like smartass, it has a sleep profile built-in.
9) Lagfree:
Lagfree is similar to ondemand. Main difference is it's optimization to become more battery friendly. Frequency is gracefully decreased and increased, unlike ondemand which jumps to 100% too often. Lagfree does not skip any frequency step while scaling up or down. Remember that if there's a requirement for sudden burst of power, lagfree can not satisfy that since it has to raise cpu through each higher frequency step from current. Some users report that video playback using lagfree stutters a little.
____
So, Governors can be categorized into 3/4 on a high level:
1.a) Ondemand Based:
Works on "ramp-up on high load" principle. CPU busy-time is taken into consideration for scaling decisions.
Members: Ondemand, OndemandX, Intellidemand, Lazy, Lagfree.
1.b) Conservative Based:
Members: Conservative, Lionheart, LionheartX
2) Interactive Based:
Works on "make scaling decision when CPU comes out of idle-loop" principle.
Members: Interactive, InteractiveX, Lulzactive, Luzactiveq, Smartass, SmartassV2, Brazilianwax, SavagedZen.
3) Weird Category:
Members: Userspace, Powersave, Performance.
Click to expand...
Click to collapse
___
Changelog:
__
062513
Updated 1,516 OC'd Edition!
Added Governors:
LagFree
Lulzactive
SmartassV2
7 more modules built in
062213
Added 1,516 OC'd Edition!
Adjusted cpu frequency tables
Adjusted voltages
Enabled 1,516 MHz Overclock as Default
062113
Powersave governor added for those of you trying to squeeze more out of the battery, or only using the device on wifi.
062013
Interactive governor added for better response time, keyboard reaction, etc,..
Reserved...
NuK3RN3L is also now booting with AOSP JellyBean.
Stay Tuned!!!!
santod040 said:
NuK3RN3L is also now booting with AOSP JellyBean.
Stay Tuned!!!!
Click to expand...
Click to collapse
Any chance of a dual boot setup?
Check out the Devil kernel and recovery for the note 2......
Would be nice to have a slimmed down AOSP ROM and a Sense one for when you wanted it.
I'm not trying to be rude to anyone but let's keep the feature requests to a minimum until he gets the more important aspects worked out. There is a lot of testing going on with just what this kernel can do as we speak. I'm sure once things calm down the other features can be implemented.
Sent from my ADR6400L using Tapatalk 2
Says AOSP in the title. Can this be used with the CM9 in this thread?
Sent from my NusenseX Bolt using Tapatalk 2
arizonaomnia said:
Says AOSP in the title. Can this be used with the CM9 in this thread?
Sent from my NusenseX Bolt using Tapatalk 2
Click to expand...
Click to collapse
This can be flashed to any current ICS roms!
Sense and AOSP!
NuK3RN3L was initially built for Sense roms, it has been confirmed to be working on Joe Black's latest CM9 build, though it needs a little camera patching...
Looks like we may have an AOSP/Sense ICS Hybrid Kernel.
On Aosp, Data and Netflix BOTH work, camcorder not yet.
Will work on things with Joe to improve this.
Congrats on RLS brosif these guys are lucky you are still carrying the infected flame for this phone !!!!
santod040 said:
This can be flashed to any current ICS roms!
Sense and AOSP!
NuK3RN3L was initially built for Sense roms, it has been confirmed to be working on Joe Black's latest CM9 build, though it needs a little camera patching...
Looks like we may have an AOSP/Sense ICS Hybrid Kernel.
On Aosp, Data and Netflix BOTH work, camcorder not yet.
Will work on things with Joe to improve this.
Click to expand...
Click to collapse
Anyone know if it fixes the Gmail whiteout? I can live without the camcorder but the Gmail thing was too much.
Sent from my NusenseX Bolt using Tapatalk 2
Virus said:
Congrats on RLS brosif these guys are lucky you are still carrying the infected flame for this phone !!!!
Click to expand...
Click to collapse
Good to see you here @Virus.
I haven't seen you since my EVO days!
i flashed both the stock and oc'd versions of this kernel over joe black's cm9 (which was also clean flashed... even wiped my sd) and wifi isn't working. it flat out won't turn on.
i don't have my tbolt in service anymore, so without wifi, i can't use it at all. wifi worked with the included kernel on joe's cm9 rom.
i'm a little pressed for time at the moment, but if a logcat would be helpful, lemme know and i'll post one when i'm back from vacation at the end of the upcoming week.
namurt said:
i flashed both the stock and oc'd versions of this kernel over joe black's cm9 (which was also clean flashed... even wiped my sd) and wifi isn't working. it flat out won't turn on.
i don't have my tbolt in service anymore, so without wifi, i can't use it at all. wifi worked with the included kernel on joe's cm9 rom.
i'm a little pressed for time at the moment, but if a logcat would be helpful, lemme know and i'll post one when i'm back from vacation at the end of the upcoming week.
Click to expand...
Click to collapse
Yeah that's a known issue with flashing it seperate.
There's a couple things not included in the kernel zip, that have to be changed Rom side.
These changes are easily made and Joe should have an update posted soon with this kernel in it and the needed Rom files to have WiFi working.
Sorry for the inconvenience.
It's just become known it would work as well as it does.
Fixes and improvements to his Rom and this kernel are coming.
If he doesn't have it up soon, I'll post a patch for using this on his Rom.
Sent from my HTC6435LVW using xda app-developers app
sweet jesus, you are one amazing dev!
that was a lightning quick response, hah.
it's so nice to see our bastard child of a device still getting some love.
santod040 said:
NuK3RN3L is also now booting with AOSP JellyBean.
Stay Tuned!!!!
Click to expand...
Click to collapse
You know....if you WANTED to....you know, just for sh1ts and giggles.....you COULD post the version of this without working data, just to give a preview and let people play with it. I remember that Liquid did something similar with an early build of OCS for the Thunderbolt. Or not. Whatever you want to do is fine, of course.
*drooling*
Sent from my NusenseX Bolt using Tapatalk 2
namurt said:
sweet jesus, you are one amazing dev!
that was a lightning quick response, hah.
it's so nice to see our bastard child of a device still getting some love.
Click to expand...
Click to collapse
Yep, santod is the man, no doubt about it.
This device launched more than 2 years ago with froyo, was upgraded to gingerbread, eventually got ICS, and may yet see unofficial jellybean!? That's an amazing run for any phone IMHO.
santod040 said:
NuK3RN3L is also now booting with AOSP JellyBean.
Stay Tuned!!!!
Click to expand...
Click to collapse
where i can find thunderbolt aosp jelly bean ROM...
olredi tried this kernel on Jelato ROM and make ma fone awesomely blasting fast :good:
guinzo said:
where i can find thunderbolt aosp jelly bean ROM...
olredi tried this kernel on Jelato ROM and make ma fone awesomely blasting fast :good:
Click to expand...
Click to collapse
AOSP jellybean hasn't been released yet, they're still working on it.
quickdraw86 said:
Yep, santod is the man, no doubt about it.
This device launched more than 2 years ago with froyo, was upgraded to gingerbread, eventually got ICS, and may yet see unofficial jellybean!? That's an amazing run for any phone IMHO.
Click to expand...
Click to collapse
+1
Santod, Chief Executive Officer
Sent from my ADR6400L using xda app-developers app
Can anyone please test and see if Onavo works with this kernel? Thanks.
https://play.google.com/store/apps/details?id=com.onavo.android.onavoics
Hi guys and gals, so I started doing some benchmarks a while ago on my moto x after seeing how poorly mc5 preformed on both it and my old Droid Maxx. My goal was to find the absolute best settings and kernel/ROM combination possible. It just so turns out that n5xpa was the absolute fastest ROM available for our device. Not only is it stock aosp/pa with all the pa beta features but it has a couple of extras added on. There is also a custom AOSP CAF kernel that is also over clocked with fast charge built right in.
If you want to boost your in game fps download resolution changer in the play store and set the resolution to 583 x 1024 and set your dpi to 240.
Attached are my benchmarks in antutu 5.2.0 and all my settings. P.S. I do use seeder.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Feel free to post the settings and apps you use and your highest benchmarks.
This was using n5xpa? What version? Link?
Heres a link http://n5x.mobi/motox
There are two versions of the ROM. The paranoid android version and cyanogenmod version. Cm is the only one posted in the xda forums.
Updated benchmark
Those are really impressive scores. It is hard for me to break 29000 on my Maxx overclocked to 1.944 GHz running Faux's kernel. Well done.
This is using Interactive governor for CPU and on demand for GPU, stock voltage, fiops for I/O scheduler. I ran this setup for a few months but currently running on Intelliactive governor to see if there is a noticeable difference on battery life. But with how big the battery is on the Maxx, I don't think it matters. Antutu score suffers greatly when on intelliactive. Usually scores around 27000 but the phone is just as snappy.
Johnny Wong said:
Those are really impressive scores. It is hard for me to break 29000 on my Maxx overclocked to 1.944 GHz running Faux's kernel. Well done.
This is using Interactive governor for CPU and on demand for GPU, stock voltage, fiops for I/O scheduler. I ran this setup for a few months but currently running on Intelliactive governor to see if there is a noticeable difference on battery life. But with how big the battery is on the Maxx, I don't think it matters. Antutu score suffers greatly when on intelliactive. Usually scores around 27000 but the phone is just as snappy.
Click to expand...
Click to collapse
I run a lower res around 563 x 1024 to 583 x1024 and I get major bench scores. And yes you really don't need a battery saving kernel on the maxx with its crazy battery. I had a locked maxx for a while. Just couldn't stand not having
cm or pa on it so I got a moto x
Sent from my Moto X using XDA Free mobile app
What app are you using in the screenshot that shows your kernel's governor and clock speeds?
I don't see how crippling your device's functionality makes it better, outside of your benchmark score. Lowering a device's native screen resolution just to show off to all your friends some amazing benchmark score is pointless.
I couldn't keep my battery drain down on n5xpa ROM. For AOSP I've found Liquid to be the best stablity/speed + battery once I set it right, intelliactive bfq with intelliplug on, mpdecision off. I'm finally back to stock now that there's a custom kernel option for sprint users finally. And to be honest stock is much better all around for me. It's faster, good ole stock touchless and active Features and my battery is doing quite well.
Sent from my XT1056 using XDA Premium 4 mobile app
I have a small issue regarding contacts while trying to import my list from SIM. It simply says No Contacts anyone know why or how to fix? Also selecting 2G and the signal disappears 3G and LTE are the only working options. This is on PA 4.0 version.
So...you crippled your Moto X by flashing a custom ROM (removing any unique Moto features), lowered its screen resolution, overclocked it, and used a placebo application (Seeder) to get a slightly higher benchmark score.
And then made a post about it.
Good job.
Don't listen to imnuts or Lyokacanthrope. They always p1ss on anyone who actually does something.
Pathetic.
Sorry? It seems pretty pointless to reduce the functionality of a flagship smartphone just to get 3000 more points in a useless synthetic benchmark.
Doing this, your screen clarity will be drastically reduced, your battery life will go to hell, and you'll lose most of the features that make this phone interesting.
I love tinkering as much as the next guy, but this is just plain silly.
Quantumstate said:
Don't listen to imnuts or Lyokacanthrope. They always p1ss on anyone who actually does something.
Pathetic.
Click to expand...
Click to collapse
Did something? It is completely crippling the phone just to get better benchmark numbers. I'll stick to my low benchmark, but still usable phone over anything mentioned in the OP. Installing AOSP is one thing, but the rest of the stuff that was done offers no increase in usability and is solely for increasing you e-peen.
You two just criticize and find fault, while never offering an alternate solution. This is the lowest and sickest (in the old sense of the word) mindset, afaic.
Researchers must explore new methods and boundaries in order to make breakthroughs, which are always unforeseen by you ignorant lot.
Oh, you happily take advantage of new developments, which you'd impeded right up until they mature, and never give credit nor acknowledge your role in discouraging innovators.
Good job there.
I see everyone's point here. Though i feel it is very important that someone browsing this forum understand in order to get the "speed" gains that are being promoted, features are being removed and shortcuts are being taken. Nothing wrong with that. "Knowing is half the battle" - G.I. Joe
Alternate solution: Leave your phone stock so it's actually usable. I'm not sure what you're looking for here, or in other threads with similar topics. There are times where alternate solutions are not useful, like this thread where the OP is illogical.
Turning down the resolution on a smartphone is like trying to get somewhere in a race car during rush hour traffic. Sure it goes fast, but what's the point?
Maybe it seems overly critical, but there isn't anything left when there are unreasonable, illogical, or some other similar post made.
Sent from my Moto X
does it impact battery positively?
i can see using a 800x600 resolution on days that all i want is 24h of voice gps and texting.
Quantumstate, you treat this whole thing like it's some major scientific breakthrough that will cure cancer.
It's just getting a higher benchmark score on a year old phone. (while, of course, outright gimping it)
Nothing more.
It's akin to buying a brand new PC and slapping Windows XP on it because it uses less RAM.
Actual, GENUINE, improvement would probably be something along the lines of getting increased real-world framerates and stability while not sacrificing any functionality. Say, a rewrite of the kernel hotplug driver and GPU governor. That'd be neat to see.
No. Experimenting with various aspects of Android and taking a characteristic to an extreme, often leads to surprising results. It's the way science has always been done. If you perpetually follow the well-beaten path, you will always get average results.
This is what a few of you can not understand. But you go further than just dismissing these experimenters -- you go out of your way to criticize them. And that's when y'all deserve to be slapped, or else the whole development environment suffers.
It doesn't matter if you don't recognize the value. Take your frustrations out on something else.
gcbxda said:
does it impact battery positively?
i can see using a 800x600 resolution on days that all i want is 24h of voice gps and texting.
Click to expand...
Click to collapse
No, changing the resolution doesn't really do anything appreciable for the battery. You might get a little more due to the CPU and GPU working a little less, but nothing statistically significant.
Quantumstate said:
No. Experimenting with various aspects of Android and taking a characteristic to an extreme, often leads to surprising results. It's the way science has always been done. If you perpetually follow the well-beaten path, you will always get average results.
Click to expand...
Click to collapse
How is doing what's always been done differ from what is a given? I'd be more concerned if all of the changes in the OP decreased performance. You do all of that stuff, you are guaranteed to get better benchmark scores, I'd say that is lower than average results.
Quantumstate said:
This is what a few of you can not understand. But you go further than just dismissing these experimenters -- you go out of your way to criticize them. And that's when y'all deserve to be slapped, or else the whole development environment suffers.
Click to expand...
Click to collapse
I encourage legitimate development, but none of that ever shows up g here anymore. Legitimate experimentation would be getting significantly better benchmarks without hurting the hardware, battery life, or functionality of the device. Installing AOSP is one thing, kernel another. All credibility went out the door when the screen resolution was lowered and benchmarks used as the only measure of results.
Quantumstate said:
It doesn't matter if you don't recognize the value. Take your frustrations out on something else. Take up sports, if you're not too fat.
Click to expand...
Click to collapse
I go to the gym regularly, as long as my schedule permits. Maybe you should try taking some classes in engineering, critical thinking, and logic, your posts suggest they are needed.
Sent from my Moto X
Hi all,
I've recently installed the overclocked kernel from squid and am having some trouble reaching the same benchmarks that he has hit. I am running stock MM with row 128 I/O and adreno-tz on the GPU. CPU is lionfish with min frequencies 800 on both clusters. I think squid is running CM13.
I consistently score between 680-740 single and 2680-2800 multi. Does this look about right for stock MM with the overlooked kernel?
Any help maximizing this would be greatly appreciated. I know these scores have (probably) very little to do with real-world use but if I can get more out of my device then why not.
Thank you for any insight!
XxMikeMasterxX said:
Hi all,
I've recently installed the overclocked kernel from squid and am having some trouble reaching the same benchmarks that he has hit. I am running stock MM with row 128 I/O and adreno-tz on the GPU. CPU is lionfish with min frequencies 800 on both clusters. I think squid is running CM13.
I consistently score between 680-740 single and 2680-2800 multi. Does this look about right for stock MM with the overlooked kernel?
Any help maximizing this would be greatly appreciated. I know these scores have (probably) very little to do with real-world use but if I can get more out of my device then why not.
Thank you for any insight!
EDIT: Moderator - could you please edit the title of the post and correct the typo? GeekBench, not Brnch. Thanks!
Click to expand...
Click to collapse
Try with simple on demand in gpu.
I will try this app today.
Sent from my XT1562 using Tapatalk
K.khiladi said:
Try with simple on demand in gpu.
I will try this app today.
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
Hey pal. Thanks for your feedback. Nice to see your response. I'll try it out as you suggest. I've been running a bunch of tests and it's looking like I hover around 740-50 single and 2700-50 multi. I've changed the configuration to default squid, so interactive governor and aggressive frequency settings. Needless to say the performance sure is snappy. Hahaha.
I'll likely revert to lionfish 800 on both clusters but this interactive snappiness is tempting...
Exactly 700 and 2700 with the oc kernel, stock brazil mm. Not even kidding. Although i sincerely doubt anything but a "native" extension can accurately measure a device performance, there is too much virtual machine and abstractions between hardware and software. Then again, this limitation applies to almost all apps, eg the normal usecase...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My score
Sent from my XT1562 using Tapatalk
K.khiladi said:
My score
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
Looks to be about mine as well. What's your setup?
I got similar scores with lionfish, 800 both clusters. OCed kernel.
AtomicStryker said:
Exactly 700 and 2700 with the oc kernel, stock brazil mm. Not even kidding. Although i sincerely doubt anything but a "native" extension can accurately measure a device performance, there is too much virtual machine and abstractions between hardware and software. Then again, this limitation applies to almost all apps, eg the normal usecase...
Click to expand...
Click to collapse
What's your setup, Atomic?
Running
Temasek's CM 4.1
OC Kernel with interactive and row 256kbps
XxMikeMasterxX said:
Looks to be about mine as well. What's your setup?
I got similar scores with lionfish, 800 both clusters. OCed kernel.
Click to expand...
Click to collapse
Interactive. Base frequencies on both clusters 200. Overcharged squid kernel.
Sent from my XT1562 using Tapatalk
---------- Post added at 09:11 PM ---------- Previous post was at 09:08 PM ----------
TxaEkis said:
Running
Temasek's CM 4.1
OC Kernel with interactive and row 256kbps
Click to expand...
Click to collapse
Cm seems to be set for higher benchmarks.
Sent from my XT1562 using Tapatalk
Yeah does it ever. Stock gives me max 770 single 2815 multi. I'm not sure if it's worth the hassle of ROM switching to get those extra points. Would I really see the performance difference?
Although I am tempted to try a new ROM. Would be fun...so long as I use Titanium Backup properly. Hahaha
XxMikeMasterxX said:
Yeah does it ever. Stock gives me max 770 single 2815 multi. I'm not sure if it's worth the hassle of ROM switching to get those extra points. Would I really see the performance difference?
Although I am tempted to try a new ROM. Would be fun...so long as I use Titanium Backup properly. Hahaha
Click to expand...
Click to collapse
If you are happy with stock don't bother as you won't even notice those extra points in the benchmark. I changed roms for the extra features and cm themes and i was getting random lag until i changed to interactive and row, now is very smooth and zero lag
TxaEkis said:
If you are happy with stock don't bother as you won't even notice those extra points in the benchmark. I changed roms for the extra features and cm themes and i was getting random lag until i changed to interactive and row, now is very smooth and zero lag
Click to expand...
Click to collapse
Interactive is a great governor yeah. Thanks for your response regarding the ROM. I hear that CM13 is still a little shaky on the X Play but maybe I'll try the next release just to compare. I'll try a full discharge from 100% with default squid's OC kernel values. If I can still get >7 hours SOT with that setup and snappy performance I'll be thrilled.
XxMikeMasterxX said:
Yeah does it ever. Stock gives me max 770 single 2815 multi. I'm not sure if it's worth the hassle of ROM switching to get those extra points. Would I really see the performance difference?
Although I am tempted to try a new ROM. Would be fun...so long as I use Titanium Backup properly. Hahaha
Click to expand...
Click to collapse
This is miniscule difference. It doesn't create a great performance difference between stock and custom Roms. The benchmarks most of the time shows the raw power of the device but the optimisation of the software also is needed.
You can try custom Roms to get extra functionality but there are still bugs in them.
Sent from my XT1562 using Tapatalk
K.khiladi said:
This is miniscule difference. It doesn't create a great performance difference between stock and custom Roms. The benchmarks most of the time shows the raw power of the device but the optimisation of the software also is needed.
You can try custom Roms to get extra functionality but there are still bugs in them.
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
Nicely said. Performance and stability are key for me. Battery life too. Haha. I just love the X Play for that battery. 5 hours SOT and 21%. So lovely.
I had carefully tuned CM13 to get the best performance out of this device, so it and derivatives will give better performance than the defaults in stock. You can see some of my configuration here: https://github.com/moto8916/android_device_motorola_lux/blob/cm-13.0/rootdir/etc/init.target.rc Beyond that, some higher level parts of the ROM are better optimized on custom ROMs than stock, so that also improves performance.
For reference, here is my last score with the new (OC) kernel:
squid2 said:
I had carefully tuned CM13 to get the best performance out of this device, so it and derivatives will give better performance than the defaults in stock. You can see some of my configuration here: https://github.com/moto8916/android_device_motorola_lux/blob/cm-13.0/rootdir/etc/init.target.rc Beyond that, some higher level parts of the ROM are better optimized on custom ROMs than stock, so that also improves performance.
For reference, here is my last score with the new (OC) kernel:
Click to expand...
Click to collapse
Hey squid,
Looks interesting. I think CM13 is definitely worth a look. I think I'll try the next release. Thanks for explaining the customizations/optimizations you've done.
Frankly, i couldn't care less about some number a synthetic benchmark spits out. The number 1 consideration is how long the battery lasts, then (a long way off) how quickly "heavy" apps such as firefox launch. Last i read CM13 isn't as good as stock at conserving power.
AtomicStryker said:
Frankly, i couldn't care less about some number a synthetic benchmark spits out. The number 1 consideration is how long the battery lasts, then (a long way off) how quickly "heavy" apps such as firefox launch. Last i read CM13 isn't as good as stock at conserving power.
Click to expand...
Click to collapse
Battery life is quintessential for me, too. I was hoping to strike a balance between performance and battery (hence the Optimal Setup thread) and am still trying to discern what the best setup is to meet my requirements.
I'd like to try a custom ROM at some point, but that's my curiosity more than anything.
Battery life on the X Play can't be beat! That's why I got it.
Moto x play is no slough, I just ran a test between my nexus 6 and MXP,
Most apps actually open faster on the moto x.
Scrolling through Web pages and g+ the nexus 6 is smoother
flashallthetime said:
Moto x play is no slough, I just ran a test between my nexus 6 and MXP,
Most apps actually open faster on the moto x.
Scrolling through Web pages and g+ the nexus 6 is smoother
Click to expand...
Click to collapse
Yep. I'd expect that. Still though - if properly customized this phone can really fly.
As a CM13 osprey user I found myself a little confused about the usefulness of custom kernels compared to the kernel bundled with cyanogenmod releases. There are many custom kernels available for the osprey, compatible with CM13. They mainly boast better performance & battery life and usually a lot of other features.
The purpose of this test is to measure the performance benefits and battery life benefits of the most popular custom kernels, if any. I want to find out if I should bother to use them myself, since the bundled kernel comes with the natural advantages of an easier install, better testing by the cyanogenmod devs and is updated, or has the potential to be updated, in line with the nightly releases. Perhaps some others will find the results interesting.
Setup
I'm testing on my 1 year old well used osprey running cyanogenmod 13.0-20160901-NIGHTLY-osprey.
All tests are single runs unless stated otherwise, phone in airplane mode. No special configuration is done to any kernel, so we're looking at their default settings.
Kernels
CM Bundled kernel
Squid r17
AGNi pureMOTO 3.2
FireKernel 5.6
Optimus R14
Shield r4
Explosion Reborn R24
Features
Custom kernels invariably come with many new features, sometimes a dizzying amount of stated improvements. I've highlighted some of the interesting differences that could affect performance, and a count of the bullet point features the kernels advertise.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Only Squid & Explosion (based on Squid) deviate from the linux base version of 3.10.49. All custom kernels except Squid & Shield provide higher max CPU clock states. AGNi pureMOTO, Explosion and FireKernel provide a higher GPU max clock.
FireKernel boasts an impressive 91 feature worth bullet pointing, while AGNi pureMOTO doesn't feel the need to advertise any feature or even a mission objective. Well I'm assuming better performance, battery life and stability is at least a concern of all kernels.
Tests
PCMark emulates real phone usage, and is the performance test I'm most interested in to indicate general performance.
AGNi pureMOTO, FireKernel and Shield perform noticably worse than the bundled kernel. The other kernels are roughly in-line or a little lower than the bundled kernel, with only Explosion providing a hint of better performance.
It seems the kernels are providing higher max CPU clocks don't appear to be using them by default.
I didn't expect much difference in internel nand performance, but wanted to check for regressions. No kernels provide real storage i/o performance benefit. AGNi pureMOTO and Optimus have small performance regressions on sequential writes.
With 2D graphics mostly covered by PCMark, I'm simply checking 3D performance with a test provided by PassMark. Running at around 20fps on the bundled kernel, it seemed a good performance to spot any differences.
I was surprised to see poor performance from AGNi pureMOTO, FireKernel & Explosion. The other kernels are in-line with the bundled kernel. Kernel GPU clock differences seem to have no effect, certainly no good one.
To isolate processing performance I used a blend of multicore tests provided by Vellamo. All custom kernels performed worse than the bundled kernel, although Squid, Optimus and Explosion are very close. It's a disappointing showing from AGNi pureMOTO, FireKernel and Shield. As before higher CPU clock states do not seem to be used.
Looking at the figures I can't help but conclude that no custom kernel provides a worthwhile performance improvement over the bundled cyanogenmod kernel at their default settings. While this is somewhat disappointing, performance stats have little meaning without looking at battery life. This brings me to the most important and time consuming test, do custom kernels improve battery life?
Update: Battery tests completed 6-Sep-2016
Finally, after many hours of testing I have the battery test results. I used PCMark's battery test which runs the work usage test continuously until the battery reaches 20%. The test includes lots of emulated real world usage & lots of idle time. It also provides a geometric mean score for the entire run.
From the results we can see all kernels performing roughly similarly, but no custom kernel convincingly surpasses the bundled kernel for performance and battery life. Only Squid actually ends up with better average performance over the run, and at a small battery life cost.
Interestingly on viewing the CPU clock stats I saw the bundled, Squid, Optimus & Shield clocked between 800-1363MHz, whilst AGNi pureMOTO, FireKernel & Explosion clocked between 400-1363Mhz, and made more use of intermediate clock states. However, the lower clocks just haven't translated into battery life increases.
Concluding thoughts
All the kernels have performed decently, and without any stability issues during my testing. But it's the CyanogenMod bundled kernel that has surprised me by being front runner in speed & battery life.
For those of you enjoying unique features offered by custom kernels, you can take heart that the custom kernels aren't that much worse. But for me, considering the natural advantages of using the CyanogenMod's kernel, I'll be switching back to the bundled.
nice research its weird that firekernel isn't #1
HelpMeruth said:
nice research its weird that firekernel isn't #1
Click to expand...
Click to collapse
no its not weird
Great work @alexheretic
alexheretic said:
Kernel GPU clock differences seem to have no effect, certainly no good one.
Click to expand...
Click to collapse
So this really does mean that going from 465 MHz to 720 MHz makes 0 difference, when it should considering it's supposed to be delivering a 50% performance boost.
sticktornado said:
So this really does mean that going from 465 MHz to 720 MHz makes 0 difference, when it should considering it's supposed to be delivering a 50% performance boost.
Click to expand...
Click to collapse
That is the case for me yes. The higher clocks are stated as features, and max gpu clock is observable as a setting using Kernel Adiutor. However, looking at the results I'd guess the gpu & cpu just aren't actually being clocked to max.
great work.. waiting for battery life...i think some other roms gives good battery life other than cm13
alexheretic said:
That is the case for me yes. The higher clocks are stated as features, and max gpu clock is observable as a setting using Kernel Adiutor. However, looking at the results I'd guess the gpu & cpu just aren't actually being clocked to max.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2765469
https://www.reddit.com/r/Android/comments/26tqck/overclocking_possibly_dead_for_currentpast_gen/
It might be just a placebo
I think best kernel was Chriszuma Kernel. It was the first OC kernel. I also had make some test in antutu benchmark app.
Cm 13 kernel 28000 score
Firekernel 31000 score
Chriszuma Kernel 35000 score
@alexheretic can you also try Chriszuna kernel please (forum.xda-developers.com/2015-moto-g/orig-development/osprey-chriszuma-kernel-v4-t3400303)
Sorry for bad english
Nikos dima said:
@alexheretic can you also try Chriszuna kernel please (forum.xda-developers.com/2015-moto-g/orig-development/osprey-chriszuma-kernel-v4-t3400303)
Click to expand...
Click to collapse
I'm going to test the battery life performance of these kernels over the next few days, after that I can take a look at more kernels.
Nikos dima said:
I think best kernel was Chriszuma Kernel. It was the first OC kernel. I also had make some test in antutu benchmark app.
Cm 13 kernel 28000 score
Firekernel 31000 score
Chriszuma Kernel 35000 score
@alexheretic can you also try Chriszuna kernel please (forum.xda-developers.com/2015-moto-g/orig-development/osprey-chriszuma-kernel-v4-t3400303)
Sorry for bad english
Click to expand...
Click to collapse
you had 31000 with firekernel ? that's strange i tested yesterday an got 34897
pmjferreira said:
you had 31000 with firekernel ? that's strange i tested yesterday an got 34897
Click to expand...
Click to collapse
Maybe the new version of firekernel 5.6 is beter.
Very interesting. Overall it seems stock cm kernel is a better choice. Would be interesting to see how stock Moto stacks against stock cm on these tests.
I'm onto the 3rd kernel battery test. The good news is PCMark provides a nice geometic mean performance score of the entire run, so I should end up with pretty good figures for performance vs battery life.
so whats the best kernel right now
alexheretic said:
As a CM13 osprey user I found myself a little confused about the usefulness of custom kernels compared to the kernel bundled with cyanogenmod releases. There are many custom kernels available for the osprey, compatible with CM13. They mainly boast better performance & battery life and usually a lot of other features.
The purpose of this test is to measure the performance benefits and battery life benefits of the most popular custom kernels, if any. I want to find out if I should bother to use them myself, since the bundled kernel comes with the natural advantages of an easier install, better testing by the cyanogenmod devs and is updated, or has the potential to be updated, in line with the nightly releases. Perhaps some others will find the results interesting.
Setup
I'm testing on my 1 year old well used osprey running cyanogenmod 13.0-20160901-NIGHTLY-osprey.
All tests are single runs unless stated otherwise, phone in airplane mode. No special configuration is done to any kernel, so we're looking at their default settings.
Kernels
CM Bundled kernel
Squid r17
AGNi pureMOTO 3.2
FireKernel 5.6
Optimus R14
Shield r4
Explosion Reborn R24
Features
Custom kernels invariably come with many new features, sometimes a dizzying amount of stated improvements. I've highlighted some of the interesting differences that could affect performance, and a count of the bullet point features the kernels advertise.
Only Squid & Explosion (based on Squid) deviate from the linux base version of 3.10.49. All custom kernels except Squid & Shield provide higher max CPU clock states. AGNi pureMOTO, Explosion and FireKernel provide a higher GPU max clock.
FireKernel boasts an impressive 91 feature worth bullet pointing, while AGNi pureMOTO doesn't feel the need to advertise any feature or even a mission objective. Well I'm assuming better performance, battery life and stability is at least a concern of all kernels.
Tests
PCMark emulates real phone usage, and is the performance test I'm most interested in to indicate general performance.
AGNi pureMOTO, FireKernel and Shield perform noticably worse than the bundled kernel. The other kernels are roughly in-line or a little lower than the bundled kernel, with only Explosion providing a hint of better performance.
It seems the kernels are providing higher max CPU clocks don't appear to be using them by default.
I didn't expect much difference in internel nand performance, but wanted to check for regressions. No kernels provide real storage i/o performance benefit. AGNi pureMOTO and Optimus have small performance regressions on sequential writes.
With 2D graphics mostly covered by PCMark, I'm simply checking 3D performance with a test provided by PassMark. Running at around 20fps on the bundled kernel, it seemed a good performance to spot any differences.
I was surprised to see poor performance from AGNi pureMOTO, FireKernel & Explosion. The other kernels are in-line with the bundled kernel. Kernel GPU clock differences seem to have no effect, certainly no good one.
To isolate processing performance I used a blend of multicore tests provided by Vellamo. All custom kernels performed worse than the bundled kernel, although Squid, Optimus and Explosion are very close. It's a disappointing showing from AGNi pureMOTO, FireKernel and Shield. As before higher CPU clock states do not seem to be used.
Looking at the figures I can't help but conclude that no custom kernel provides a worthwhile performance improvement over the bundled cyanogenmod kernel at their default settings. While this is somewhat disappointing, performance stats have little meaning without looking at battery life. This brings me to the most important and time consuming test, do custom kernels improve battery life?
Battery Life - In Progress: 4/7 kernels tested
I'm currently testing battery life using PCMark, since these test take hours and I have 7 kernels to test and 1 phone, this could take some time...
While we're waiting for the battery tests, please let me know if I'm missing out any important tests.
Performance tests conducted: 3-Sep-2016
Click to expand...
Click to collapse
it really matters how the kernel is set up.
i have conducted similar tests, (but more real world tests) and have concluded differently.
Acidfire.TM said:
it really matters how the kernel is set up.
i have conducted similar tests, (but more real world tests) and have concluded differently.
Click to expand...
Click to collapse
Great reply, no not just great, stunningly epic reply mate backed with nothing. Nice, you totally dismissed all evidence here, great job.
here the backing on my statement.
it's just some simple benchmark etiquette
don't benchmark kernels using their max oc frequency as not everyones device Will be able to perform well on the specific custom kernels defaults
(due to minor cpu/gpu quality inconsistency)
also custom kernels usually have different io,
cpu, hotplugging and zram settings and parameters set by default.
it's better practice to set the cpu and gpu to the same frequency and governor, Same Io scheduler
and readahead etc. same zram settings.
then test these settings across the kernels to see which kernel has more efficient system management+ Performance
otherwise it's just a case of which kernel has the best default parameters and settings.
Hey Guys I Have A Big Issue With Custom Kernels Every Time I Flash Any Custom Kernel My Phone Gets So Laggy
youssef0789 said:
Hey Guys I Have A Big Issue With Custom Kernels Every Time I Flash Any Custom Kernel My Phone Gets So Laggy
Click to expand...
Click to collapse
can you be more specific
: technique used for flashing (clean flash? etc)
: your kernel adiutor settings
: any extras you have installed (eg. xposed)
and then what do you mean exactly by laggy, what s the situation in which this happens
it will be great if u add the best rom too. like performance and battery life withits stock kernal
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I will not be held responsible for anything that happens to your device after flashing this kernel. If you don't know how to bring your dead device back to life please don't make any modifications and stay with stock MIUI. Also, if you think that overclocking can harm your device, overheat-it and possibly brick-it, send me a message and I'll be happy in informing you that My kernel's are SAFE.
MODEL INFORMATION
It seems that there's two different variants of the global model MEG7, one that has a more durable silicon in the chips and one with poor hardware construction, that results in very low capability to overcloking.
let's refer to these "sub-models" as:
MEG7-Endurance
&
MEG7-Static
Static means no change on the clocks, and Endurance for good resistance on higher RPM
If you find any problems with the codec overclocking version like reboots, freezes, or any of similar problems, do not use it, wait for a release of a non overclocked version. This will solve some bigger issues with this kernel.
My name is Luan, I live in a small city near the capital of my state in Brazil, I'm really young to be developing kernel for this phone, maybe even the most young recognized developer in xda :victory: . I'm 16 years old and I love to compile kernels and reach the limits of the smartphone i'm using (in this case redmi 5 plus). I can also speak both English and Portuguese Brazillian, which is my "default language :laugh: ".
Kernel info
LH Kernel (aka HexaTurbo) kernel is meant to be simple with only cool features added on top of CAF kernel. Kernel source will always be kept in sync with new caf and mainstream linux (3.18.y) updates. Okay enough of the intro let's move on to the features!
Telegram LH Kernel discussion group! Come join us!
*linux version 3.18.116
*GPU overclock support upto 800MHz (NOTE: This overclock is a PURE CLOCK, which means that the frequency displayed is the one the GPU regulator is sending to the chip, on Xprise kernel the frequency was with wrong multipliers, so the 855mhz displayed actually were 755mhz :silly: )
*stereo sound control for headphones
*Custom I/O schedulers: sio and zen
*KCAL advanced color control
*Crc check switch
*FS: F2FS & sdcardfs support
*reduced load average
*Enable sha256/512
*UKSM and KSM enabled
*Vibration control
*Using Xiaomi drivers
*Better audio drivers (Thanks to @LuizPauloDamaceno)
*Optimized
*Arch power option
*Gentle fair sleepers
*Better GPU usage and optimization
*CPU modded to go up to 2208mhz BIG and 2208mhz Little (Again, these are PURE CLOCKS, since our chipset dosn't seem to have a frequency table with multiplier voters, we can't go higher then 2208mhz {2400mhz will have the same performance as 2208mhz, test yourself} )
*Zram
*Zwap
*Frontswap
*Zcache
*ZSmalloc
*Optimized regulators for thermal effiency
*Disabled BCL hotplugging
*Increase BUS Width for better capability
*Crypto bus OC to 160mhz
*Slimbus OC for better audio response
*A bunch of stuff here and there
-Download the zip file and save it into the root directory of internal/external storage
-Reboot to recovery mode and flash the zip file
-Reboot device
2018-23-07
Download Kernel
2018-23-07
Download Kernel TREBLE
@LuizPauloDamaceno thanks for helping with quality and audio related stuff
@osm0sis for his amazing AnyKernel2 script
@rainforce279 for his awesome features
@mdeejay for making this possible!
@Ashish94 for providing such useful scripts
XDA:DevDB Information
LH KERNEL OFFICIAL FOR VINCE, Kernel for the Xiaomi Redmi Note 5 / 5 Plus
Contributors
LuanHalaiko, LuizPauloDamaceno, Yousef Algadri and all the other developers I cherry-picked commits
Source Code: https://github.com/LuanHalaiko/msm-3.18
Kernel Special Features: GPU/CPU OC and much more!
Version Information
Status: Alpha
Created 2018-06-20
Last Updated 2018-10-18
Screenshots in the attachment
-----Old Changelog-----
2018-23-07
For both treble and non-treble
-Linux 3.18.116
-Add cooling device property to msm8953 msm gpu
-Add missing CPU code lines for overclocking and features
-Optimize some lines of code
-More Undervolting for the CPU
-Fixed Black YouTube glitch
-Reduce Tasha voltages for less amplifier heat
2018-21-07
-Added a Treble version compatible with Android P
2018-21-07
-GPU Overclock is now more stable (790mhz instead of 800mhz, but still showing 800mhz becouse it's cooler)
-Added USB Fast charging
-Enabled wcd9335 HiFi mode
-Better power delivery for the wcd9335 amplifier
-Kernel Linux 3.18.115
-Cleanup old clock-gcc lines
-Undervolt the CPU
-Reduce all the Inovative overclocks:
*Camera ISP Overcloking from 465mhz to 581mhz
*Video Codec Overclocking from 465mhz to 600mhz
-BIMC DRR Overclocking enabled
-Removed useless HotPlugging
-And many more
2018-22-06
-New GPU steps (800,750,700,600)
-HexagonDSP Overclocking to 375mhz to 500mhz
-Camera ISP Overcloking from 465mhz to 620mhz
-Video Codec Overclocking from 465mhz to 600mhz
-General Fixes and optimizations
DOWNLOADS ARE AT THE MAIN POST
Attention note!
Screenshots and benchmarks are being uploaded!
God is here to help us...!!
Hi Luan. Thanks for the kernel. Just flashed and noticed one thing while using CPU Hotplug. I used AiO and when i choose 1 big core to be online, only one little core stays online and vice versa. Big and little cores has been swapped i guess. Just letting you know. Please look at the screenshots for info.
kaleavi said:
Hi Luan. Thanks for the kernel. Just flashed and noticed one thing while using CPU Hotplug. I used AiO and when i choose 1 big core to be online, only one little core stays online and vice versa. Big and little cores has been swapped i guess. Just letting you know. Please look at the screenshots for info.
Click to expand...
Click to collapse
Oh yeah, forgot to change that, it will be in the next build! Also Screenshots uploaded!
what is cpu aio hotplug?
F2fs support? So i can change the partition to f2fs?
Hi Luan, thanks for this kernel. I like it but if i set gpu freq to 800Mhz my game wont open, but if i set to 560Mhz my game can be played again and i didn't see 650Mhz on gpu freq.
Sorry for my bad english.
nurhadina said:
Hi Luan, thanks for this kernel. I like it but if i set gpu freq to 800Mhz my game wont open, but if i set to 560Mhz my game can be played again and i didn't see 650Mhz on gpu freq.
Sorry for my bad english.
Click to expand...
Click to collapse
Ur device got some problem then lol.
U said same to xprise but different way
Sent from my Redmi 5 Plus using Tapatalk
ekowanz said:
F2fs support? So i can change the partition to f2fs?
Click to expand...
Click to collapse
Only if the rom and recovery supports it
Yousef Algadri said:
Ur device got some problem then lol.
U said same to xprise but different way
Click to expand...
Click to collapse
Nah i just tried it and got same problem and i hope i got 650 freq back so i can run my games again. Because i didn't fint 650Mhz at gpu option on this kernel.
Yousef Algadri said:
Ur device got some problem then lol.
U said same to xprise but different way
Click to expand...
Click to collapse
Yeah, his device don't like overclocking
nurhadina said:
Nah i just tried it and got same problem and i hope i got 650 freq back so i can run my games again. Because i didn't fint 650Mhz at gpu option on this kernel.
Click to expand...
Click to collapse
800mhz is overlapping 650mhz in this version, it will be fixed in the next ones
LuanHalaiko said:
800mhz is overlapping 650mhz in this version, it will be fixed in the next ones
Click to expand...
Click to collapse
And i forgot to tell you, when i use this kernel my phone said my sd card was corrupt but when i go to recovery my sd card was fine and it was fine too on xprise kernel.
nurhadina said:
Hi Luan, thanks for this kernel. I like it but if i set gpu freq to 800Mhz my game wont open, but if i set to 560Mhz my game can be played again and i didn't see 650Mhz on gpu freq.
Sorry for my bad english.
Click to expand...
Click to collapse
Confirm too. When i set gpu to 800mhz game is crash, 560mhz work fine,hope you add 650mh again
does anyone know why my phone doesn't cross 1689mhz?
thinhx2 said:
Confirm too. When i set gpu to 800mhz game is crash, 560mhz work fine,hope you add 650mh again
Click to expand...
Click to collapse
Your device doesn't like to do Overclocking.
There are many devices has the same issues. And many doesn't. It depends on luck when getting device with fully OC support xD
Sent from my Redmi 5 Plus using Tapatalk
Can i use it on MIUI 9 Nougat?