Related
What's YOUR Set-Up?
Hello everyone, like most people here on XDA, I enjoy switching between ROMs and Kernels while keeping an eye out for a daily driver that I like best. If you have any other ROM/Kernel combinations that you enjoy and think others might also enjoy, please feel free to share them here and explain why it's awesome!
:laugh: :good:
This thread is for the Nexus 6P only
Currently I'm running:
Device: Nexus 6P - 32 GB - Aluminum (If you're curious )
ROM: Chroma (11/22) latest with SElinux Enforcing
Kernel: ElementalX (0.08) latest [SElinux Enforcing option ticked.]
Small Cluster - 1555 MHz (stock)
Large Cluster - 2054 MHz (Max)
Govenor - ElementalX
Min. CPU Frequency - 600 MHz
Max. CPU Frequency - 1824 MHz
GPU: Max = 600 MHz / Min = 180 MHz / Governor = msm-adreno-tz <------------- Anyone recommend a different governor? One for performance and the other interactive?
Color Setting Recommendations? (ElementalX App Only)
I/O Scheduler - FiOPS <----------------------- Anyone recommend a different I/O? BatterySaver/Performance/Interactive?
I'm also curious about the color fixes that Kernels purport to solve (washed out blacks? other issues?) and how to apply these fixes if someone can point me in the right direction or provide their own instructions and values for the color options (Everywhere I look just says tune to your liking but I need somewhere to start, and frankly, I don't know where to start)
I'm really enjoying this ROM/Kernel combo but I am having Battery Drain to the likes I've never seen before, which is probably my fault.
I'll attach logs from BetteryBatteryStats as well as the Battery Stats from Stock 6 or so hours after the posting of this thread (for accuracy).
Any 'Standard' or 'Conventional' logs needed to convey insightful information? for BBS or for anything else? Let me know.
Please let me know if you need any other information and perhaps how I can retrieve it for you (kinda noobish, but not extremely bad lol)
I'm certain it's a user issue but I don't know how to find and correct the issues myself, so any help would be greatly appreciated.
I'm running Chroma ROM for some of the simple customizations and its speed (I don't care about Layers [probably cuz I don't know how to use them]).
I'm running ElementalX simply for the Overclock/Underclock CPU options and the advanced color control (once I learn how to use it) but I don't care about any of the gestures, sweep2sleep,
NTFS r/w and exFAT support (no clue what this is), and Option to disable fsync (don't know what this is/does)
Lastly, what I'm looking for out of a ROM/Kernel combo is great battery life and great performance, with some fun features but definitely minimal. So if feel your setup matches these wants, and you don't mind sharing it here with me, as well as others who may be looking for a similar setup, please do so!
I, as well as most others on this forum, would also be happy to help troubleshoot any problems you may be experiencing with your ROM/Kernel combo to the best of our abilities but we cannot guarantee that we will be able to fix your phone and the responsibility of the device lies with you, the user.
Stock rooted rocks for the first 3 months until development picks up, kernel developers make enough changes and rom developers fully implement most features into their roms.
Enjoying Stock Rooted smoothness... for now!
No need to create multiple threads on exact same thing.
http://forum.xda-developers.com/nexus-6p/general/roms-kernels-running-t3257280/post64009263
Please stick to one thread.
Thanks! Thread closed.
Darth
Forum Moderator
As every MM rom is plagued with countless bugs, I don't see it very logical to stop LL development when everything related to MM isn't even working properly. What's even worse about that is that, some nice features (like OC) have emerged not a long ago, and there's no dev working anymore to bring them back to LL. Personally I refuse to use any MM rom due to the endless bugs and overall slowness.
What I'm trying to do is to build a kernel with basic custom features (faux audio, msm hotplug (or any other hotplug), intelliactive (or any other custom governor), usb keyboard, gpu OC and mainly cpu OC, which I was able to accomplish). However, using github, and all the coding stuff is really a pain. I know that I'm gonna face a lot of problems since I'm not even a dev, I just started this 3 days ago and the only knowledge I have is basically nothing. But, it'd be great if someone could help me, both for the good of the users and to speed up the development of this.
I'll be doing some research to make this go further, and, if I ever make a stable build, I'll be making a thread in the respective development section.
What I've done so far:
- Build it successfully without major errors
- Add cpu OC support (Thank you @zakee94 and @h2o64 for the commits)
To-do list:
- Fix no media playback (If someone could tell me if this is general and it's not just me, it would be nice)
- Add MSM Hotplug... or any other hotplug
- Add intelliactive governor... since I want this kernel to be perfomance-driven, this governor is so damnly good over any other gov.
- Add gpu OC and simple_ondemand as its governor.
- Add faux's sound control
- Add usb keyboard/mouse support
- Learn to use github, inb4 sorry for not posting source code
Consider me a beginner. I need your help, experienced guys.
P.S: If you try the test build, please be aware that this is a super-extremely-alpha version. It's intended only for feedbacks, so don't forget to backup your current kernel.
Hello, i'm thinking of flashing a custom kernel to my MXP, but I don't really know which kernel should I choose cause I don't know which is better.
There are 2 kernels that which very popular around here are Squid and Ultra kernel.
I'm trying to flash a kernel which support for great gaming performance and extend the battery life a little bit, and giving less heat up my beloved phone. I've heard there's a kernel that can overclock past 1.6GHz, so I want to try (To be honest I've never overclock a modern generation phone's CPU before so I don't want to in over my head, plus I don't want to overclock it because I don't really want to because I've been out of the game for so long since I did it with my Sony X8).
I'm opening this thread hoping you guys (the Pros) can teach me, show me or recommend me about this.
Thank you
So as far as I know there are two kernels available for marshmallow. Squid's and Ultra. Squid was the first around here and has kept updating and improving. That is the one that you can overclock, as a matter of fact is overclocked as soon as you flash it. Most people use Kernel Adiutor to tweak it. Ultra kernel on the other hand expands on Squid's but it hasn't been updated in a while and some of the governors available on Ultra create crashes and bootloops. In reality the only way to go is stock (as in the one that comes with whatever ROM you flash) or squid's. Some people might disagree with me but I would suggest making your own opinion by reading through the threads. Most questions, issues and concerns are addressed within. Otherwise, good luck.
[deleted]
one question... how to REALLY TEST and compare a kernel?
sometimes adding and modding the phone with custom rom, kernel, greenify and other manual modded cpu governor etc...... it's almost IMPOSSIBLE to understand if the perfornance, or battery life is affected by a kernel or something else.
A person could obtain a bad battery life but the culprit could be ANYTHING.....
so IMHO the easiest way to compare a kernel is the numbers of features and OPTIONS that allows it.... something like how many governor, i/o schedulers , tcp algorithms, dt2w..... and so on... because a PERFECT kernel... could be perfect in some roms.... and worse on others.....
there are too many complications about the number of apps, which apps, to use greenify or naptime/forcedoze , and a possible incompatibility with a specific ROM with specific kernel.
after all........ maybe the simpler test is to keep the same configuration of the rom for at least 1 week, make a nandroid twrp backup, flash 1 kernel, keep it 1 week ( and see results), then restore twrp with stock kernel/rom , then flash the second one kernel, keep 1 week, then restore backup, test 3rd kernel.... and so on? making it sure NOTHING CHANGE, no greenify change... no gaggressive doze setting change....
it would be nice if other people would write here they combination of precise KERNEL + ROM used to achieve a great battery life and SOT.......
No doubt all these kernels are well tuned and devs are making them better & better every day. I always use RADON KERNEL and it works with every rom just perfect, never tried AGNI though, two days back I flashed ElementX and Franco kernel but I noticed two big cores are either going "offline" or shutting them off permanently. @franciscofranco replied those two cores were thermal throttled or something (may be....) but after RADON I didn't noticed that issue, all 6cores are back online . So for now I'm sticking with radon I'll flash FrancoKernel next week and see if thingd sorted out..
Most off all I think we kenzo users are blessed to have all these big names in development thread.
Why isn´t Lineage Os on the List (a.k.a Cyanogen Mod)
I certainly like Radon best . Save battery and not lose performance .
I don't like AGNi . Because it update too frequently sometimes and little waste battery .And that ,I don't like the AGNi Controller ,One reason :For users who use other languages, this apk is difficult to translate . But , I can't deny it is a good kernel .
About Other kernel , I did not use them for a long time . So I do not understand.
realista87 said:
one question... how to REALLY TEST and compare a kernel?
sometimes adding and modding the phone with custom rom, kernel, greenify and other manual modded cpu governor etc...... it's almost IMPOSSIBLE to understand if the perfornance, or battery life is affected by a kernel or something else.
Click to expand...
Click to collapse
Battery and performance are undeniably affected by your kernel.
For example, the battery life on Nitrogen OS kernel is amazing, and the reason for that is, reduced performance. It's not slow, it's smooth really, but it's slower than Radon's balanced configuration.
And I think your argument that a kernel can be judged by the number of features, governors and schedulers it includes is wrong, because you don't need multiple governors or schedulers to get a good experience.
At one time, you'll only be using one, and that's why the stock configuration of the kernel matters.
I think every custom kernel has their advantages and disadvantages.
All we need to do is tuning it.
For example, I use Franco kernel and I changed the input boost ms for better responsive.
Or I use nitrogen kernel and tuning the governor for better performance.
However, I choose latest ex kernel manager app to tuning the kernel. It's more friendly ui and more reliable.
And the best thing is latest version of radon/franco/exkernel/nitrogen/agni has unified fp support.
I purchased a Google Daydream a month or two after I got my Pixel XL, and have used it off and on for some low intensity stuff (mainly Netflix VR, which is fantastic.) I have tried a few games, but didn't find them incredibly compelling, nor did I find them worth heating my device up to ridiculous temperatures. Over the time I've been using the Daydream, I've noticed that the visual performance on stock 7.1.1 is wayy better than with most custom ROMs. Even with custom kernels, performance modes, and GPU/CPU overclocking, I still experience more frame tearing, more blur, and in most cases, more heat, than with stock. Does anyone have any tips for mitigating any of these factors with custom ROMs? Has anyone had any success increasing visual performance, or reducing heat with custom ROMs? Are there any ROM/kernel settings that make things better?
In terms of heat, I've seen many users' solutions involving shoving ice packs, fans, etc. into the headset behind the phone, and I found most of them too cumbersome. My personal solution doesn't apply while using the Daydream, but instead addresses cooling the device before and after. Essentially, I built a stand for my phone that holds a large, thick piece of aluminum behind the phone, and runs a small desk fan over the whole setup. I recently upgraded the stand to hold an icepack behind the fan, so that the air could be cooler, without introducing condensation. I'll include pictures in a subsequent post, for anyone interested.
The Pixel was built to run stock Android and I didn't find any custom Roms that ran as well as stock when I was playing with roms. On top of that custom kernels and rom kernels for the Pixel don't offer the same performance customization options that were available on other phones.. On the Nexus 6P there were not only a bunch of different kernel governors that changed the way the phone performed but there were numerous custom profiles within the governors that tweaked performance further. On the Pixel there's one governor, sched. Any custom rom you use utilizes the same kernel governor and any custom kernel you use utilizes the same kernel governor and devs haven't offered any tweaks or profiles for it. To me that's an admission that devs don't really know how to improve performance on what Google already wrote for the Pixel. That lack of what would be considered basic and essential knowledge for devs on other phones means custom rom devs and custom kernel devs may offer features and customization options that you can't get on stock but they don't have the slightest idea how to actually improve performance and stability over stock. I doubt that you will find better Daydream performance on any custom rom.
jhs39 said:
The Pixel was built to run stock Android and I didn't find any custom Roms that ran as well as stock when I was playing with roms. On top of that custom kernels and rom kernels for the Pixel don't offer the same performance customization options that were available on other phones.. On the Nexus 6P there were not only a bunch of different kernel governors that changed the way the phone performed but there were numerous custom profiles within the governors that tweaked performance further. On the Pixel there's one governor, sched. Any custom rom you use utilizes the same kernel governor and any custom kernel you use utilizes the same kernel governor and devs haven't offered any tweaks or profiles for it. To me that's an admission that devs don't really know how to improve performance on what Google already wrote for the Pixel. That lack of what would be considered basic and essential knowledge for devs on other phones means custom rom devs and custom kernel devs may offer features and customization options that you can't get on stock but they don't have the slightest idea how to actually improve performance and stability over stock. I doubt that you will find better Daydream performance on any custom rom.
Click to expand...
Click to collapse
I definitely agree with you on a couple points, but I think that the less substantial development you're noting is probably not due to incapable developers, but rather to the fact that the Pixel/XL is significantly different from any other device. The partitioning methods, kernel, governors, etc. threw everyone for a loop, and I think that as more devices like this are released, and with Android O development, there will be significant improvements.
On the other hand, right now, stock does seem to be the best option as far as I can tell, so that's likely what I'll be going back to.
SonarMonkey said:
I definitely agree with you on a couple points, but I think that the less substantial development you're noting is probably not due to incapable developers, but rather to the fact that the Pixel/XL is significantly different from any other device. The partitioning methods, kernel, governors, etc. threw everyone for a loop, and I think that as more devices like this are released, and with Android O development, there will be significant improvements.
On the other hand, right now, stock does seem to be the best option as far as I can tell, so that's likely what I'll be going back to.
Click to expand...
Click to collapse
The Pixel has been out for a while and the development situation for the Pixel hasn't really improved so it doesn't seem like devs are making any notable progress in terms of understanding how the Pixel functions and offering anything other than cosmetic adjustments to stock. Not being a dev I'm not sure why that is but it just doesn't seem like it's going to happen --at least not on this phone.
jhs39 said:
The Pixel was built to run stock Android and I didn't find any custom Roms that ran as well as stock when I was playing with roms. On top of that custom kernels and rom kernels for the Pixel don't offer the same performance customization options that were available on other phones.. On the Nexus 6P there were not only a bunch of different kernel governors that changed the way the phone performed but there were numerous custom profiles within the governors that tweaked performance further. On the Pixel there's one governor, sched. Any custom rom you use utilizes the same kernel governor and any custom kernel you use utilizes the same kernel governor and devs haven't offered any tweaks or profiles for it. To me that's an admission that devs don't really know how to improve performance on what Google already wrote for the Pixel. That lack of what would be considered basic and essential knowledge for devs on other phones means custom rom devs and custom kernel devs may offer features and customization options that you can't get on stock but they don't have the slightest idea how to actually improve performance and stability over stock. I doubt that you will find better Daydream performance on any custom rom.
Click to expand...
Click to collapse
For the point in governors you are at least incorrect on that front, at least the kirisakura kernel includes more than just sched, in fact the default governor is shedutil. The reason why you are not seeing as many governors, and profiles is probably because of eas not because they haven't figured it out, just it's probably not as necessary to tweak as much any more
Sent from my Pixel XL using Tapatalk
kkeith said:
For the point in governors you are at least incorrect on that front, at least the kirisakura kernel includes more than just sched, in fact the default governor is shedutil. The reason why you are not seeing as many governors, and profiles is probably because of eas not because they haven't figured it out, just it's probably not as necessary to tweak as much any more
Click to expand...
Click to collapse
I know that's the excuse that people are using including devs--sched is so perfect and efficient that there's no reason to even develop other kernel governors. I was mocked in the official ElementalEx thread (including by the dev) for daring to suggest that devs were dropping the ball by not developing other governors for the Pixel. But as far as I can tell sched is the eas equivalent of the On Demand governor. The temperature of my phone battery jumps from around 80F idle to 100F almost instantly as soon as I pick it up and the screen comes on, which suggests to me that sched maxes out the CPU as soon as it detects activity like On Demand did. Most people on pre-eas smartphones who used a custom kernel didn't stick with On Demand as their governor even though it provided maximum performance (which is why phone manufacturers used it by default) so why are Pixel owners so satisfied with sched when it appears to function in the same way? It makes zero sense to me and as someone who has experienced overheating problems with my Pixel (which Pixel support freely admits is one of the two most common complaints they encounter, the other being poor battery life) I would personally appreciate being able to use the eas equivalent of a balanced governor.
I haven't heard of the custom kernel you cited but I have seen schedutil mentioned somewhere and tried to find out what kernel offered it. Do you know what the difference is between stock sched and schedutil?
jhs39 said:
I know that's the excuse that people are using including devs--sched is so perfect and efficient that there's no reason to even develop other kernel governors. I was mocked in the official ElementalEx thread (including by the dev) for daring to suggest that devs were dropping the ball by not developing other governors for the Pixel. But as far as I can tell sched is the eas equivalent of the On Demand governor. The temperature of my phone battery jumps from around 80F idle to 100F almost instantly as soon as I pick it up and the screen comes on, which suggests to me that sched maxes out the CPU as soon as it detects activity like On Demand did. Most people on pre-eas smartphones who used a custom kernel didn't stick with On Demand as their governor even though it provided maximum performance (which is why phone manufacturers used it by default) so why are Pixel owners so satisfied with sched when it appears to function in the same way? It makes zero sense to me and as someone who has experienced overheating problems with my Pixel (which Pixel support freely admits is one of the two most common complaints they encounter, the other being poor battery life) I would personally appreciate being able to use the eas equivalent of a balanced governor.
I haven't heard of the custom kernel you cited but I have seen schedutil mentioned somewhere and tried to find out what kernel offered it. Do you know what the difference is between stock sched and schedutil?
Click to expand...
Click to collapse
Post number 2 about half way down there is an explanation as to the differences and why schedutil is a little better, as well as an explanation on some other eas governors.
https://www.google.ca/amp/s/forum.x...nt/kernel-kirisakura-kernel-0-1-t3554330/amp/
Sent from my Pixel XL using Tapatalk
jhs39 said:
I know that's the excuse that people are using including devs--sched is so perfect and efficient that there's no reason to even develop other kernel governors. I was mocked in the official ElementalEx thread (including by the dev) for daring to suggest that devs were dropping the ball by not developing other governors for the Pixel. But as far as I can tell sched is the eas equivalent of the On Demand governor. The temperature of my phone battery jumps from around 80F idle to 100F almost instantly as soon as I pick it up and the screen comes on, which suggests to me that sched maxes out the CPU as soon as it detects activity like On Demand did. Most people on pre-eas smartphones who used a custom kernel didn't stick with On Demand as their governor even though it provided maximum performance (which is why phone manufacturers used it by default) so why are Pixel owners so satisfied with sched when it appears to function in the same way? It makes zero sense to me and as someone who has experienced overheating problems with my Pixel (which Pixel support freely admits is one of the two most common complaints they encounter, the other being poor battery life) I would personally appreciate being able to use the eas equivalent of a balanced governor.
I haven't heard of the custom kernel you cited but I have seen schedutil mentioned somewhere and tried to find out what kernel offered it. Do you know what the difference is between stock sched and schedutil?
Click to expand...
Click to collapse
yeah, someone replied to you and* provided the same link as the guy below you in this thread.
https://forum.xda-developers.com/pixel-xl/help/sched-2-t3630966
---------- Post added at 02:39 PM ---------- Previous post was at 02:03 PM ----------
jhs39 said:
I know that's the excuse that people are using including devs--sched is so perfect and efficient that there's no reason to even develop other kernel governors. I was mocked in the official ElementalEx thread (including by the dev) for daring to suggest that devs were dropping the ball by not developing other governors for the Pixel. But as far as I can tell sched is the eas equivalent of the On Demand governor. The temperature of my phone battery jumps from around 80F idle to 100F almost instantly as soon as I pick it up and the screen comes on, which suggests to me that sched maxes out the CPU as soon as it detects activity like On Demand did. Most people on pre-eas smartphones who used a custom kernel didn't stick with On Demand as their governor even though it provided maximum performance (which is why phone manufacturers used it by default) so why are Pixel owners so satisfied with sched when it appears to function in the same way? It makes zero sense to me and as someone who has experienced overheating problems with my Pixel (which Pixel support freely admits is one of the two most common complaints they encounter, the other being poor battery life) I would personally appreciate being able to use the eas equivalent of a balanced governor.
I haven't heard of the custom kernel you cited but I have seen schedutil mentioned somewhere and tried to find out what kernel offered it. Do you know what the difference is between stock sched and schedutil?
Click to expand...
Click to collapse
mocked after you said this....
jhs39 said:
I can't possibly disagree with you more. The stock governor sched on the Pixel XL is the equivalent of the On Demand governor on the old Nexus devices but on steroids. Picking up my phone and the screen coming on is enough to raise the temperature of my Pixel XL battery by 20F almost instantly. The simple act of reading emails or surfing the Internet causes the CPU to max out as if you were doing heavy gaming. That isn't my idea of optimized and I think it's disgraceful that ElementalEx would even release a kernel for the Pixel XL where the only governor you can actually use is sched. This isn't a new phone. Everyone doesn't want their Pixel XL to burn out like the Nexus 5X or Nexus 6P but with the sched governor the Pixel XL consistently runs at a higher internal temperature than either of those phones did. Mine has already shut down multiple times because of overheating which wouldn't happen with a more balanced kernel governor that didn't constantly push the CPU so hard even when it's completely unnecessary for what you are actually doing with the phone.
Click to expand...
Click to collapse
jhs39 said:
Multiple people on XDA who have actually bothered to check the temps that their Pixel operates at have reported being alarmed and RMA'ing their devices only to receive a refurbished device that operates at the exact same high temperatures. Because the phone doesn't feel hot to the touch doesn't mean the temperature isn't very hot inside.
Pixel overheating is such a common problem that if you do a Google search on Pixel XL problems overheating will be on every single list that comes up....
With the Nexus phones you could easily flash a custom kernel and change the governor from On Demand to Interactive. After you did that the phone would run cooler inside, the battery would last longer and there would be no perceptible drop off in performance because 95% of users don't need the maxed out kernel settings that Google uses by default. But you can't do that with the Pixel because devs of custom kernels for the most part didn't create any other governors that work with the Pixel--it's mostly sched or nothing and sched is an On Demand style governor whether XDA owners in these threads realize it or not.
I don't have any personal kernel tweaks. I'm not a developer and wouldn't really know where to start. I expected the development community to actually develop other governors that work with the Pixels but they have largely dropped the ball.
With the Nexus communities on XDA people were more than willing to discuss the shortcomings of the devices. With the Pixel XL community if you suggest that maybe the phone actually has some flaws that devs should really be addressing you typically get attacked by Google fanboys who are in a complete state of denial where this phone is concerned and are unwilling to admit that the device isn't perfect.
If you think the sched governor is the greatest thing ever and absolutely love it that's your privilege, even if I think you are in denial about how hot the sched governor makes this phone run internally. But I think there should be a choice of kernel governors like there was on previous Nexus devices for people like me who aren't actually thrilled with Google's stock governor. That choice does not exist with this phone.
I can't honestly fathom how the developer of a major recognized kernel like ElementalEx could make a kernel for the Pixel XL but not offer a single alternative governor that actually works with the phone--or the fact that Pixel users on XDA seem to have no problem with that at all.
Click to expand...
Click to collapse
1) 5 other people, multiple users have suggested you contact Google to have your device replaced as it is behaving differently than others. Anyone who disagreed with you was called a fanboy by you...
2) If you go looking for problems, of course you'll find them. However until you entertain Google and actually RMA your device you will not know what the resolution to your issue is, only what other's experiences were.
3) sched is an event-driven DVFS (Dynamic Voltage & Frequency Scaling) governor that biases the OPP (Operating Performance Points, essentially the tabulated frequency-and-voltage steps) higher or lower based on the workload. So when the load is low, it biases the OPP as low as possible, lowering the frequency *and* the voltage to be used per frequency tl;dr it offers the performance found from an interactive governor while saving power in comparison.
4) if you can not develop yourself, do not expect anyone else to actively develop for you on their own free time for free, especially with the gratitude you show. You called me a fanboy because I suggested you try replicating your problem on stock instead of on the beta, which is funny since all you run is stock now...
5) man I can see why they mocked you out, you went into the thread trying to call the developer lazy because he didn't develop what you wanted