Develop Bugs

[KERNELS][ICS][I9000] The ICS Kernel Benchmarking Project -Update: Devil

Goal of this little project is to dispel myths and hearsay and trying to assess the elusive performance of custom kernels for our beloved SGS I9000.
So far this has proven quite challenging as there is no single good benchmark on Android (yet):
a lot of people have been misled by ridiculous Quadrant scores: ridiculous because, with some small tweaks which do not affect real performance in any way, shape or form, it is possible to boost the Quadrant score by factor 3x.
You're free to believe that your SGS I9000 which scores 3000+ on Quadrant is faster than a SGS II, but then please leave this thread and move on.
some kernels may seem smooth with some games, and get high scores on some synthetic benchmark, yet the UI appears "laggy" and stutters a lot in comparison to other kernels which score lower on the same benchmark
some popular benchmarks give results with unacceptably low reproducibility, i.e. if you run them multiple times without changing a thing on your system, you get scores varying by 50% of more, in a completely random fashion
most popular benchmarks do not measure or take into account multitasking and CPU contention with other applications, yet on a typical usage one has background tasks such as the media scanner or synchronization which kick in often and unpredictably
So this will be mostly a work in progress, i'm testing several benchmarks and several kernels in multiple combinations, trying to analyze which benchmarks offer certain criteria which make them useful, namely:
Reproducibility of results: running the same tests multiple times, should result in a very small variance of the final score
Performance separation: benchmarks which are too "synthetic" and show only a dependency on clock speed are not useful to discriminate "fast" kernels from "slow" kernels
Performance representation: we all know when a kernel "looks" or "feels" fast or smooth. If a benchmarks shows you that a "laggy" kernel scores higher than a fast and responsive one, it's likely that the benchmark is not well designed
I'll work more on this thread explaining my (current) choice of tests and what they're good for.
But for now i'll just post a link to the summary table, and give a brief recommendation concerning popular ICS kernels; recommendation which i'll explain in the coming days.
Base ROM:
Slim ICS 2.8
(because is fast, smooth and has the least background stuff of all ICS ROMs which i tested)
Test Conditions:
Whenever possible, i tried to overclock the kernels to 1.2GHz which most / all phones should have no trouble achieving.
In case of Semaphore i had to use the bus / live overclock but it wasn't fully stable at 1.2GHz on my phone so i ran most of the tests at 1.14GHz.
Tested Kernels:
Stock Teamhacksung V17
Devil 1.1.6b BFS
Devil 1.1.6b CFS
Icy Glitch V14 b
Semaphore ICS 0.9.5b
Recommendation:
Devil 1.1.6b CFS, Icy Glitch V14b (with SmartassV2 and FIOPS), and Midnight ICS (with a tweaked Conservative) are trading blows for the fastest kernel.
At the time of testing, Midnight is slightly worse in terms of overclocking though, apparently due to different voltages, also it doesn't allow overclocking beyond 1.2GHz.
But what's interesting is that it achieves great performance while using a tweaked conservative governor.
Devil 1.1.6b BFS is good but obviously inferior to its CFS brother.
Semaphore has the lowest cache and memory latency in the multithreaded test, it also has impressive sd card read speed and in general appears super responsive, but it's a bit worse in 3D gaming and especially it lacks "true" overclocking, "live overclocking" changes the bus clock and is way more unstable, in fact on my phone i couldn't run it stable at 1.2GHz.
All kernels are significantly faster than the stock teamhacksung's kernel, so you have no excuses not to upgrade to one of the popular custom kernels!
ICS 4.0.4
Started testing Android ICS 4.0.4 kernels on Slim ICS 3.2.
All tested kernels are "huge mem" versions with 380+MB of available RAM, without breaking video playback or 720p recording.
Summary:
the stock kernel from Teamhacksung is now a very respectable performer, unless you plan to overclock probably you don't need to install one of the other kernels
Semaphore, Midnight and Devil are all very fast and smooth
Results table:
https://docs.google.com/spreadsheet/ccc?key=0AuBUEB4dGFSSdHIyN2VIeWU4QnhLOFpJejFPWDh5S1E

Res 1
One request for the kernel developers:
could you please post me what are your preferred / recommended settings in terms of Governor and I/O Scheduler?
Only one configuration per kernel please, as running these tests is rather time consuming.

Test Settings
So for anybody who wants to follow the same methodology as I used to test kernels, please pay attention that in some tests i didn't use stock settings, to try to improve the reproducibility of the results.
Before all test, i put the phone in flight mode, and disable all synch services.
Antutu: DB I/O and SD Write and Read have poor reproducibility. So i run these tests separately 5 times, and take the best scores.
RealPi: the number of iterations is increased by factor 10x i.e.: 100000 digits
MPAC: lots of customization here. Also be careful as it's not very stable and some settings will make it crash.
All tests: 8 threads (or 8 producer / consumer pairs)
CPU: 10000000 iterations, use case: integer (i'm considering to add logical too)
Memory: stock apart for nr of threads. Repeat the test 5 times and get best numbers
Cache: 40 iterations

Res 3
With this should be enough.

Judging from those results, CFS Devil looks really promising.

Semaphore live oc stability issues happen only on Slim ICS indeed. On ICSSGS I have perfect stability at 1.2 ghz. And performance is just great, paired with very good battery life.
GT-i9000 / ICSSGS 4.2 / Semaphore 0.9.0

A quick question: did you lock the max freq to eliminate the "governor" variable?
Because each kernel could have governor's tweaks that the other don't.
Based on what you posted here, the differences between Glitch and Devil is practically none.
I tested both and didn't feel any tangible difference, in the end, it comes down to the unique features of each kernel.

Overclocking bus vs adding an extra step aren't even slightly comparable. Maybe do tests not overclocked?
Also there is a new glitch build with 100% working bln.
Sent from my GT-I9000 using xda premium

+1 for tests without overclock. Majority of us, users do not overclock. Maybe a seperate test for overclocking could be nice , but comparisons should be done with stock speeds imho.
Thanks for the time and effort. We needed this.

Overclocking bus Vs adding an extra step isn't an apple to apple comparison, I agree.
However my goal was to use each kernel in the best possible way, and if some kernels have the possibility to use higher multipliers / extra frequency steps, that is an advantage for the user, compared to the kernels who only offer live overclock.
Don't get me wrong, i love Semaphore and i've been using it for a long time.
And i have no doubt that some users can get it stable with live overclock to 1.2GHz.
But that is the ceiling, while with other kernels even my phone can reach stable overclocks of 1.5GHz, and that is something to consider.
I chose as the basis for my tests an overclock of 1.2GHz because it's something which practically everybody can use, without massive battery drain, overheat or shortening the life of the device.
I'll try to add measurements at stock speeds for those who don't like to overclock.

cba1986 said:
A quick question: did you lock the max freq to eliminate the "governor" variable?
Because each kernel could have governor's tweaks that the other don't.
Click to expand...
Click to collapse
I didn't want to take the governor variable out.
Because, as you said, each kernel could use (and often does) governor tweaks which make the kernel "special" or different from the others, and that has to be taken into account in evaluating them.
Because nobody will use the phone locked at the maximum frequency.
So for me the governor and its tweaks is part of the user experience of a certain kernel, and a distinctive factor.
At the end, all kernels are coming from almost the same sources, so it's the little things which make the difference.

phzi said:
Also there is a new glitch build with 100% working bln.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
That's great!
This test i run is not the "be all end all", it was just a recommendation at the time of writing.

Pipperox said:
Overclocking bus Vs adding an extra step isn't an apple to apple comparison, I agree.
However my goal was to use each kernel in the best possible way, and if some kernels have the possibility to use higher multipliers / extra frequency steps, that is an advantage for the user, compared to the kernels who only offer live overclock.
Click to expand...
Click to collapse
Agreed but, then again, benchmarks should be done at original CPU clock IMHO.
Otherwise, results are distorted.

HiKsFiles said:
Agreed but, then again, benchmarks should be done at original CPU clock IMHO.
Otherwise, results are distorted.
Click to expand...
Click to collapse
agreed. Especially since stock team hacksung seems to be clocked at 1GHz
what's the point of the comparison? Really?
As expected, there is no noticeable difference between all 1.2 GHz kernels.
It's not as if there was a real difference between them anyway.

zorxd said:
agreed. Especially since stock team hacksung seems to be clocked at 1GHz
what's the point of the comparison? Really?
As expected, there is no noticeable difference between all 1.2 GHz kernels.
It's not as if there was a real difference between them anyway.
Click to expand...
Click to collapse
That's not quite true.
If you look closer, you'll see that Devil CFS has quite a distinct advantage over all others in 3D tests.
The point of the comparison between stock hacksung @1.0GHz and the others, who can overclock, is to show what kind of benefit you get from switching to kernels which are overclock friendly.
Especially considering that you can't assume that a 20% clock speed increase will bring a 20% performance speedup across the board.
At last, i'd say that you may have "expected" that the kernels tested at 1.2 GHz don't have such a difference in performance.
But expectations have to be verified.
I tried to answer the questions:
On Devil's kernel, is BFS really better than CFS?
The "popular belief" is that BFS is faster than CFS.
According to my tests, CFS results faster instead.
Another question may be, what kernel gives you the best gaming performance.
If you pay attention to the An3D Bench XL, you'll see that Semaphore 0.9.5b, even overclocked a 1.2GHz, is significantly slower than Devil.

If i recall correctly Semaphore Author claimed that some kernel developers overclock GPU, and he didn't. Idk anything about it, but i recall something about it.
Is it possible to overclock only GPU, without overclocking CPU??

zipgenius said:
so you should benchmark them without setting anything. Average users don't overclock and don't change governor or scheduler: they flash the new kernel and stop.
Click to expand...
Click to collapse
I completely agree on benchmarking every kernel at the same frequency (stock 1Ghz max) but I think there are two different options for further benchmarking:
1) Benchmark kernels configured as similar as possible regarding CPU governor, IO scheduler, readahead -> comparable results for all kernels.
2) Benchmark kernels with default settings (only makes sense if all compared kernels are optimized for similar purpose like performance, does not make sense if a kernel does *not* focus on max. performance and uses e.g. Conservative CPU governor as default setting.
@Pipperox: Would it be possible to check my Mindnight-ICS dev version with your benchmark suite? I'd be really interested in the results as you use the same setup for all kernels (1.2Ghz would not be a problem, does not use LiveOC but old school 1/1.128/1.2Ghz OC).

Interesting thread... I never used devil's CFS version, always BFS. Will try CFS out now.
@Mialwe Where can we get your ics kernel?

mialwe said:
I completely agree on benchmarking every kernel at the same frequency (stock 1Ghz max) but I think there are two different options for further benchmarking:
1) Benchmark kernels configured as similar as possible regarding CPU governor, IO scheduler, readahead -> comparable results for all kernels.
2) Benchmark kernels with default settings (only makes sense if all compared kernels are optimized for similar purpose like performance, does not make sense if a kernel does *not* focus on max. performance and uses e.g. Conservative CPU governor as default setting.
@Pipperox: Would it be possible to check my Mindnight-ICS dev version with your benchmark suite? I'd be really interested in the results as you use the same setup for all kernels (1.2Ghz would not be a problem, does not use LiveOC but old school 1/1.128/1.2Ghz OC).
Click to expand...
Click to collapse
Sorry guys, i understand your logic but i do not fully agree with it.
I'm not comparing overclocked kernels with heavy tweaking of voltages and special settings with which they only work.
I did the "poor man"'s overclock, setting to 1.2GHz using NSTools, a setting where 95% of phones should have no problem working.
I think that if some kernels offer you this possibility while others do not, it is fair to use this "advantage" that they have over the other kernels.
Because a lot of users will have the possibility to do the same as i do, without esoteric knowledge and with just a couple of clicks in the menus.
That being said, "due to popular demand" i will also try to retest those kernels at 1.0GHz as soon as i get a bit of time.
BUT in my recommendations, i will also consider the overclocking capabilities.
@mialwe: sure, i'll give a run to your kernel as well!

mialwe said:
@Pipperox: Would it be possible to check my Mindnight-ICS dev version with your benchmark suite? I'd be really interested in the results as you use the same setup for all kernels (1.2Ghz would not be a problem, does not use LiveOC but old school 1/1.128/1.2Ghz OC).
Click to expand...
Click to collapse
Dude, sorry but i don't seem to find your ICS kernel anywhere.. can you provide a link?

[Q] Which Kernel to use Galaxy S3

I am running CM10 M2 on my Samsung Galaxy S3 I747
Now my question is which kernel do i use because i would like to OC my phone but it has to have some speed and keeps some battery life.
I don't want to have a lot of speed with hardly to no battery life, i need a little speed plus good battery life if possible.
So if anyone has any suggestions please post

Leandre20 said:
I am running CM10 M2 on my Samsung Galaxy S3 I747
Now my question is which kernel do i use because i would like to OC my phone but it has to have some speed and keeps some battery life.
I don't want to have a lot of speed with hardly to no battery life, i need a little speed plus good battery life if possible.
So if anyone has any suggestions please post
Click to expand...
Click to collapse
You can try all that work with CM10. It's a preference thing. I'm using ktoonsez. You can OC and UC.
Sent from my SAMSUNG-SGH-I747 using xda premium

Im not saying there aren't any others as i have only used ktoonez's kernel, http://forum.xda-developers.com/showthread.php?t=1756776 simply because there is, IMHO, no need to. He has versions for each of the available android versions for the i747...obviously you would want to use the AOSP JB based kernel under CM10. Packaged along with the kernel is ktweaker which is an app that gives you control over the clock speeds, under volting, governors, schedulers, plus a bunch of other options. If you overclock your processor you are going to drain the battery faster, you can compensate for this by under volting the frequencies however pushing the CPU too hard can shorten the life expectancy and under volting too far will cause severe system instability. Im not sure how much experience you have with OC/UV'ing but its basically trial and error until to find the right balance of speed and stability that is right for you.Just be sure to read and follow his instructions carefully and dont mess with anything in ktweaker you aren't 100% sure what it does, and as always make a backup in your recovery before messing with system files.....happy OC'ing.

dntesinfrno said:
Im not saying there aren't any others as i have only used ktoonez's kernel, http://forum.xda-developers.com/showthread.php?t=1756776 simply because there is, IMHO, no need to. He has versions for each of the available android versions for the i747...obviously you would want to use the AOSP JB based kernel under CM10. Packaged along with the kernel is ktweaker which is an app that gives you control over the clock speeds, under volting, governors, schedulers, plus a bunch of other options. If you overclock your processor you are going to drain the battery faster, you can compensate for this by under volting the frequencies however pushing the CPU too hard can shorten the life expectancy and under volting too far will cause severe system instability. Im not sure how much experience you have with OC/UV'ing but its basically trial and error until to find the right balance of speed and stability that is right for you.Just be sure to read and follow his instructions carefully and dont mess with anything in ktweaker you aren't 100% sure what it does, and as always make a backup in your recovery before messing with system files.....happy OC'ing.
Click to expand...
Click to collapse
I'm still learning since it's the first one I tried.
Sent from my SAMSUNG-SGH-I747 using xda premium

There is a thread dedicated to ktweaker settings on the i747 HERE that would be a good place to start and get an idea of what you are doing. There are also several topics that discuss the different governors and schedulers, what the differences are, advantages/disadvantages to each etc. You can also search google for a plethora of information regarding OC/UV'ing, although most of it will pertain to desktop processors and video cards. While the voltages and frequencies will be significantly lower the same principles apply with mobile device chips.

[Q] governors and schedulers

I was wondering which governors and schedulers are the best for say performace or battery? I've done a little research on my own, but what do you prefer on your HTC One V? I've got aokp JB running on my cdma one v
Thanks!

I am a kernel dev, so naturally I know whats behind this code Lionheart is my favorite as it has aggressive scaling. No lag is also good, in some cases. On demand is great with battery though. I can get roughly 8 hours mid use with on demand. I hope this helps with deciding your governors.
Sent from my One V using Tapatalk 2

simonsimons34 said:
I am a kernel dev, so naturally I know whats behind this code Lionheart is my favorite as it has aggressive scaling. No lag is also good, in some cases. On demand is great with battery though. I can get roughly 8 hours mid use with on demand. I hope this helps with deciding your governors.
Sent from my One V using Tapatalk 2
Click to expand...
Click to collapse
Hey Simon! I'm actually running your 3.0.46 sick kernel JB with AOKP. It's wonderful!! haha so far, I've been running OC at 1708 with the performance governor and noop scheduler... it's lasted 11 hours and I'm at 73% battery, medium to light use with wifi on the whole time, but it's pretty snappy!
Is Lionheart pretty much a performance governor? You mentioned aggressive scaling, so it's snappy when it needs to be, but saves for battery when you're not using it?

BTW I didn't see a "no lag" governor... not sure what that is, so can you clarify? Also, is performance actually the best for snappiness, or will lionheart be even better? I used to use [email protected]$$v2 on my optimus v, but I'm just not sure what's best here?

Nolag is a new addition. I have been hard at work removing even more htc things Lionheart is a bit nicer on battery then performance, because it will scale to your minimum of its not needed. Perfoance stays at full no matter. Cpu spy will be a good tool to help with battery as well
Sent from my One V using Tapatalk 2

Oh kool! Well I don't see it in the latest kernel, so will it be in the next kernel? Thanks dude, you're awesome!

I'll fill everyone in on this thread on the work.
We are :
Patching to Linux 3.0.49
Removing htc additions that are hacks and ics specific.
Cleaning Bluetooth and header files up
Updating WiFi drivers
Updating GPU drivers
Overhauling the mmc drivers
We also have a driver dev that's working on camera and maybe eventually an lcdc driver which will allow us to use the experimental caf display needed for cyanogen mod10 and full project butter
Sent from my One V using Tapatalk 2

Wow that sounds ridiculously awesome!!

Kernels to use with All Star Rom

Just made the switch from Jedi Knight 5 to All Star Rom 4 for the massive increase in features and customizations (minus the Jedi themes which I liked and the wifi calling that I rarely used). I love it so far...
The only issue I have is battery life - e.g. last night my battery ran down 13% (usually only ran down 3% with JK5) while sleeping with it underclocked to a maximum of 1Ghz.
I've read good things about the KKO kernel - has anyone tried this with any success with All Star Rom?
Any other hints/suggestions so that I can get a full day out of this thing with moderate use and not have it run like it was made in 2007? (Powersaving mode in ROM control under AOKP isn't cutting it- quite laggy).
Thanks in advance!

Because I am one of the devs behind the ROM, I can say that the h0tcakez kernel goes great with the ROM. To get batter battery life, enable CPU Sleeper and your phone shouldn't lose as much battery life overnight. Also, I am using ondemand governor with noop I/O.

android88 said:
Because I am one of the devs behind the ROM, I can say that the h0tcakez kernel goes great with the ROM. To get batter battery life, enable CPU Sleeper and your phone shouldn't lose as much battery life overnight. Also, I am using ondemand governor with noop I/O.
Click to expand...
Click to collapse
I was hoping maybe someone as experienced as a dev would have some input, and I got a dev himself! Thanks a ton for helping this noob out.

[KERNEL][Stock 224/253][Z5/Z5 DSDS][6.0.x]OM5Z 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"
}
I am NOT resposible for any damage done to your device, your neighbor, or any other things you like/hate.​
Introduction:
@oshmoun and I were in need for a custom stock kernel to mess with. Since all the available Options were not fitting our needs, or gave us bad experience on some aspects, and we knew about Zombie Kernel from Tom, we decided to start working on that. So I brought up support for the Z5, we ported Kexec to it, updated it to 224 and added various things. Since the kernel gave us very good experiences, we decided to make it accessible to the public.
About:
This Kernel is based on @Tommy-Geenexus Zombie Kernel. He was ok with us continuing/porting his projects, so oshmoun, and me started to create the "oshmoun Myself5 Zombie Kernel" aka OM5Z Kernel.
Features and Commit History:
Check 2nd Post!
Installation Instruction:
THIS DOES ONLY WORK ON UNLOCKED BOOTLOADER!
You can either flash the provided boot.img via fastboot, or flash the zip in recovery.
Additional Information:
The Kernel is underclocked by default. Both Cluster are underclocked to 1,344/1,536 GHz respectively, resulting into HUGE Temperature improvements. However, due to public demand, V2 features the ability to disable the underclock (in case you need to make some baked Eggs real quick, whatever). All you need to do is run this code after boot (Kernel Adiutor has the abilty to execute scripts at startup, just a reminder).
Code:
echo "0:4294967295 1:4294967295 2:4294967295 3:4294967295 4:4294967295 5:4294967295 6:4294967295 7:4294967295" > /sys/module/msm_performance/parameters/max_cpu_freq
What it effectively does, is resetting the max clock limit for each core to the default (unset) values, allowing you to set whatever frequency (from the ones available ofc) you want.
Download:
For Dual SIM phones download the sumire_dsds Versions.
OM5Z Kernel (Release Versions)
https://dl.myself5.de
OM5Z Kernel (Testing Versions)
https://testing.myself5.de
Thanks/Credits:
Tommy-Geenexus - You can guess why
oshmoun - for obvious reasons
FreeXperia Team (especially Jerpelea) - for too many things!
CarbonRom Team - for too many things!
phaseburn - for being a good friend and helping me with almost everything !
infected_ - for help with SM!
My Big Brother Eric - for helping me keeping focused on Development!
My friend Silas - for letting me use his servers and being awesome!
If I forgot you, please tell me.
If you think we deserve a donation, I won't stop you
To Donate to Tommy-Geenexus:
To Donate to me:
To Donate to oshmoun:
PM Spam him to create a PayPal Donation system, he doens't have one yet
Thanks a lot to those who have donated!​
Additional Information:
As you might have seen in my MultiROM Thread, some stock kernels require different Recovery Images than AOSP Kernels. We set an end too this, and fixed init_sony, rather than using some very outdated software which somehow works. This means, you might need to use a different recovery with this kernel if you're currently on a "stock" recovery. We're hoping that other stock kernel devs adapt our solution, so we can set an end to the old scripts.
XDA:DevDB Information
OM5Z Kernel, Kernel for the Sony Xperia Z5
Contributors
Myself5, oshmoun, Tommy-Geenexus
Source Code: https://github.com/Myself5/android_kernel_sony_msm8994_OM5Z
Kernel Special Features:
Version Information
Status: Stable
Created 2016-06-25
Last Updated 2016-07-16

Reserved
Latest Version: V2.0
Changelog:
Version 1:
Add kexec-hardboot
ramdisk: use init_sony, no outdated bootrec scripts
ramdisk: fix USB on Stock when using MultiROM
Remove broken Sony MHL driver
Update to 32.2.A.0.224
Merge caf/LA.BF64.1.2.2_rb4.40
Various CVE Fixes
Initial Z5 and Z5C bringup, based on Zombie Kernel with these features
Bug fixes for touchscreen / fingerprint / scheduler drivers
Stripped unnecessary debug nodes, legacy code and disabled KSM
Turquoise LED when EOC is reached (when battery is fully charged)
CPU-Speedbin visible in debugfs node (sys/kernel/debug/msm8994_cpuinfo/*Speedbin)
Calibrated JDI Novatek Panel to 6500K Color Temperature and 2.2 Gamma
Tomtom-Codec Digital Speaker-, Mic- and Cam-mic-Control
Underclocked both Cluster to 1,344/1,536 GHz respectively, resulting into HUGE Temperature improvements
Version 2:
Ability to disable the underclock (added on public demand) See OP for instructions
Removed TomTom Audio
Update to 32.2.A.0.253
Update init_sony
include DRM Fix by @tobias.waldvogel
Add support for sumire_dsds (E6633 and E6683). Thanks to @tOrNadO™ for testing
For a detailed Changelog, check the Github Commit history:
https://github.com/Myself5/android_kernel_sony_msm8994_OM5Z/commits/

sounds cool! I'll give it a try.

Does it works for z5 dual?
Brilliant work anyway!

is it possible for you to make a build for Z3+/Z4 ? as both Z5 and Z4/Z3+ are similar mostly and Zach's kernel is ported similarly.
Thanks

JerryLaiHMmmmmm said:
Does it works for z5 dual?
Brilliant work anyway!
Click to expand...
Click to collapse
Yes it should. I was not able to test it, but we picked necessary code for compatibility with both devices.
GryTEcHoG said:
is it possible for you to make a build for Z3+/Z4 ? as both Z5 and Z4/Z3+ are similar mostly and Zach's kernel is ported similarly.
Thanks
Click to expand...
Click to collapse
It would be possible, but I don't want to do that. I don't have a Z3+/Z4, so I would not be able to test things prior to releasing it. Thats not what I want to do. Even with testers, I couldn't guarantee on my own that things work, and thats not ok for me.
Sent from my E6653 using Tapatalk

Is ıt work on E6603?
Thanks for kernel

Lptrex9 said:
Is ıt work on E6603?
Thanks for kernel
Click to expand...
Click to collapse
It should workflawless with all Z5 variants (E6603, E6653, E6633, E6683), I am only able to test it on a E6653 though, so please report if it doesnt work on the E6603.

Hi,
I've just proved that it works on the Dual model (e6683)
And it should work on E6633 as well.
Thanks for your hard work!
EDIT:
Oh……… No SD card detection.

JerryLaiHMmmmmm said:
Hi,
I've just proved that it works on the Dual model (e6683)
And it should work on E6633 as well.
Thanks for your hard work!
EDIT:
Oh……… No SD card detection.
Click to expand...
Click to collapse
Needs to be compiled separately for the Dual devices,
otherwise the microSD detection is toast

JerryLaiHMmmmmm said:
Hi,
I've just proved that it works on the Dual model (e6683)
And it should work on E6633 as well.
Thanks for your hard work!
EDIT:
Oh……… No SD card detection.
Click to expand...
Click to collapse
Do me a favour and test if V1.1 here (https://testing.myself5.de/sumire/OM5Z Kernel/) works please.
Thanks in advance.

Myself5 said:
Do me a favour and test if V1.1 here (https://testing.myself5.de/sumire/OM5Z Kernel/) works please.
Thanks in advance.
Click to expand...
Click to collapse
Good to see some development going on for the device..

What recovery should I use for this kernel?

Myself5 said:
Underclocked both Cluster to 1,344/1,536 GHz respectively, resulting into HUGE Temperature improvements
Click to expand...
Click to collapse
I want a powerful device, so I'll wait until you remove this restriction, I even want a OC kernel as Zach's one did. I heard about your kernel a lot but didn't have chance to try it, on Z2 I tried yours but got Android is upgrading on every booting. But, I don't know what your kernel's aim to? Zach's one is aiming to as close stock as possible with fixing and improvement.

RyTekk said:
I want a powerful device, so I'll wait until you remove this restriction, I even want a OC kernel as Zach's one did. I heard about your kernel a lot but didn't have chance to try it, on Z2 I tried yours but got Android is upgrading on every booting. But, I don't know what your kernel's aim to? Zach's one is aiming to as close stock as possible with fixing and improvement.
Click to expand...
Click to collapse
This kernel aims for the best performance and temperatures on the Z5. Its known, that the Z5 sometimes has heating issues, or turns off 4k Recording after short times. I needed to abort my 4k testings after a straight 40min of recording, not because my phone got hot, but because I was running out of space. The "extra" performance other kernels promise you, will result into heat and therefore thermal throttling, which ends up the same as Underclocking it slightly from the beginning, if not worse.
Also: @infected_ was one of the early adopters of my Kernel (before the release, he gave feedback and stuff). After the release, he asked me since when there is a Underclock as he never really experienced any performance drawbacks, so he didnt notice that there actually IS a underclock. (Let running Benchmarks aside here, we all know thats just for showing off).
GPU is running at full speeds btw, so no drawbacks in games whatsoever.
V2 (which will be completely reworked on Top of Toms reworked Kernel) might as well allow setting the default clock with tools like Kernel Auditor, but will most likely be underclocked by default again.
Sent from my E6653 using Tapatalk

RyTekk said:
I want a powerful device, so I'll wait until you remove this restriction, I even want a OC kernel as Zach's one did. I heard about your kernel a lot but didn't have chance to try it, on Z2 I tried yours but got Android is upgrading on every booting. But, I don't know what your kernel's aim to? Zach's one is aiming to as close stock as possible with fixing and improvement.
Click to expand...
Click to collapse
Myself5 said:
This kernel aims for the best performance and temperatures on the Z5. Its known, that the Z5 sometimes has heating issues, or turns off 4k Recording after short times. I needed to abort my 4k testings after a straight 40min of recording, not because my phone got hot, but because I was running out of space. The "extra" performance other kernels promise you, will result into heat and therefore thermal throttling, which ends up the same as Underclocking it slightly from the beginning, if not worse.
Also: @infected_ was one of the early adopters of my Kernel (before the release, he gave feedback and stuff). After the release, he asked me since when there is a Underclock as he never really experienced any performance drawbacks, so he didnt notice that there actually IS a underclock. (Let running Benchmarks aside here, we all know thats just for showing off).
GPU is running at full speeds btw, so no drawbacks in games whatsoever.
V2 (which will be completely reworked on Top of Toms reworked Kernel) might as well allow setting the default clock with tools like Kernel Auditor, but will most likely be underclocked by default again.
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
ill subscribe what @Myself5 said.
your device doesn't stop being "powerful"... does a snapdragon 810, 8 core device that reaches 1.3Ghz on the LITTLE cores, and 1.5Ghz on the big cores, stop being powerful?
image it as a car. let's say the "car engine" was adjusted for the best air intake/fuel intake/thermal handling.
you don't notice the underclock, the phone is fast, fluid, responsive, and excellent on the thermals.
make a test, see how much time you can record 4K (one of the most demanding and heating stuff on the phone) with stock kernel.
then try OM5Z kernel, and compare.
regards.
ps: you can even make a stress test with antutu (15m), and compare the thermal/core shutdown/frequency throttling, of both kernels.

Myself5 said:
This kernel aims for the best performance and temperatures on the Z5. Its known, that the Z5 sometimes has heating issues, or turns off 4k Recording after short times. I needed to abort my 4k testings after a straight 40min of recording, not because my phone got hot, but because I was running out of space. The "extra" performance other kernels promise you, will result into heat and therefore thermal throttling, which ends up the same as Underclocking it slightly from the beginning, if not worse.
Also: @infected_ was one of the early adopters of my Kernel (before the release, he gave feedback and stuff). After the release, he asked me since when there is a Underclock as he never really experienced any performance drawbacks, so he didnt notice that there actually IS a underclock. (Let running Benchmarks aside here, we all know thats just for showing off).
GPU is running at full speeds btw, so no drawbacks in games whatsoever.
V2 (which will be completely reworked on Top of Toms reworked Kernel) might as well allow setting the default clock with tools like Kernel Auditor, but will most likely be underclocked by default again.
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
infected_ said:
ill subscribe what @Myself5 said.
your device doesn't stop being "powerful"... does a snapdragon 810, 8 core device that reaches 1.3Ghz on the LITTLE cores, and 1.5Ghz on the big cores, stop being powerful?
image it as a car. let's say the "car engine" was adjusted for the best air intake/fuel intake/thermal handling.
you don't notice the underclock, the phone is fast, fluid, responsive, and excellent on the thermals.
make a test, see how much time you can record 4K (one of the most demanding and heating stuff on the phone) with stock kernel.
then try OM5Z kernel, and compare.
regards.
ps: you can even make a stress test with antutu (15m), and compare the thermal/core shutdown/frequency throttling, of both kernels.
Click to expand...
Click to collapse
Actually I don't stress my phone a lot, but I need all tasks to be done in the fastest way, about 4K recording, I don't use it since I don't have a 4K display, but I can handle it by my custom thermal-engine (you can find it in General section). I belong to what kind of people, you know, instead of I buy a normal motor for daily and a powerful motor for long trips, I'll just buy a powerful one for both, that's me , I always choose a higher requirement thing for a lower task that it's required.

@Myself5 @infected_
I use this mod by Rytekk now for a while, and I have to say, sometimes the phone feels a bit warm indeed but I'm monitoring GPU and cpu temperature in statusbar with cooltool and it barely exceeds 65°c on intensive jobs like 4K recording and timeshift video.
(btw, aside from that, it seems timeshift video heat up the phone much faster than 4K)
So when our chip is spec'd up to 85°c as max emmc temperature, 65°c is nothing.
The phone might feel hot or warm but it's the heatsinking doing its job.
If it would stay cool on timeshift video it'll probably shows the message to close the app in no-time because it can't dissipate the heat.
In that case, the thermal paste between the emmc and the heatsinking isn't applied correctly or doesn't make enough contact.
But if it's applied correctly, and emmc runs up to 65°c, ofcourse the phone feels warm.
Imagine a boil of water, 60°c, put your hand in it.
Now my second point, I was monitoring temperature for a few weeks and what I noticed is the GPU heats up faster than cpu0 and Cpu1 almost every time, on every task.
So you might want to throttle GPU if u like lower temperatures but in my opinion, when emmc doesn't exceed 65°c, there's nothing to worry about.
Cheers!
Sent from my E6653 using XDA-Developers mobile app

What RyTekk efficiently did, was adjusting the thermal throttling curve. This at no point however means, that the phone will always stay at the stock frequency. Effectively it will probably result in the same throttling as Underclocking the device does.
I know the whish of having the fastest things,my build PC has a i7 5820k overclocked to 4GHz, BUT that one also has a proper cooling solution, and is not known across the world as a easy overheating CPU. Until you show me a usecase, where you can clearly experience performance drawbacks (other than Benchmarks) I wont accept the fact that you really "need" 2GHz on the S810.
Sent from my E6653 using Tapatalk

Hmm, I can't show you so you just do whatever you think it's right, your restriction is just "masking" device that it's at 52 Celcius (JK :laugh: ). Btw, I pushed request, hope you would take a look on it, and also fix SD card not detected on dsds devices.