Related
tribute to xda.
tuning parameters for cpufreq_interactive & core_ctl & hmp_sched & some more
for MIUI and LOS, RR, AOKP, MoKee, Bliss (all zwliew's forks).
v.4
- conception is changed (again)
sometimes 1 big + 2 little is not enough. so now i offer you 1 big + 3 little or 2 big + 2 little at your choice.
all these combination is very individual and i want you will make your own good config.
now it's much simpler to customize - all configs are in separate patches.
just download zip, unpack it, correct config, pack it back. that's all.
if you will find better configuration, please, give your advices here in this thread.
i recommend you to use good monitoring and profiling tool from Qualcomm https://play.google.com/store/apps/details?id=com.quicinc.trepn
for custom rom (!!!zwliew's sources based) users:
you can apply cpu_tuning* patches direct on your native kernel, you dont need to change kernel, it will work (may be even better, who knows).
or you can apply patch with new LOS kernel from fedosis with very light undervolting, new low frequences and some more improvements.
(all kernels are zwliew's sources based, compatible)
so,
1. install "lineage-13.0-20170202-UNOFFICIAL-land-kernel.zip" (kernel only)
2. install "cpu_tuning-4-1x3-cm13.zip" (config only)
if you skip 1st step, it will repack your present boot (only "init.qcom.power.rc" will be replaced) and will work with your old kernel, but without low freqs, etc. you can test this case also.
!!!backup your "boot" partition.
for MIUI users:
there are patches with similar settings for you.
just install "cpu_tuning-4-1x3-miui.zip". only "/system/etc/init.qcom.post_boot.sh" will be replaced.
!!!backup "/system/etc/init.qcom.post_boot.sh"
(there are also patch with original MIUI "/system/etc/init.qcom.post_boot.sh", if something will go wrong)
https://drive.google.com/drive/folders/0B1G5yP4fi63mbEpzNHREVVB6a00
and later i will add something about thermal config, there are also some points to change
v.3
- conception is changed:
now 1 big + 2 little cpus are permanent online (offline-to-online is not cheap).
permanent also means, they are always the same: cpu0 (big master), cpu4 (little master), cpu5 (little master's friend). all others are lazy, they stay offline most times and go online and work only if these three are very busy. "core_ctl" was patched to implement this logic.
- (not for MIUI) low frequences was added. 768 and especially 960 are too high for low load.
- (not for MIUI) light cpus boost on screen touch was implemented.
v.2
now 8 cpus sleep more (in active mode) and wake faster.
LITTLE cluster for little tasks (at least 1 active), big cluster for big tasks (mostly sleeps).
awaiting of your impressions and results about working time and performance before and after.
we will tune it
one more thing:
i think xda is for advanced users. it's all experimental.
and better do nothing if you dont understand what are you doing.
will this work in mokee rom??
Subhampaul12 said:
will this work in mokee rom??
Click to expand...
Click to collapse
may be late. these are most popular.
thanks for the mod. But, why i feel CPU load is a bit bigger then before i applying the mod?
i'm using latest MIUI global developer
RinzImpulse said:
thanks for the mod. But, why i feel CPU load is a bit bigger then before i applying the mod?
i'm using latest MIUI global developer
Click to expand...
Click to collapse
may be. i dont know. thats why i want you to test it. but you need more time to make right compare results.
RinzImpulse said:
thanks for the mod. But, why i feel CPU load is a bit bigger then before i applying the mod?
i'm using latest MIUI global developer
Click to expand...
Click to collapse
CPU load is bigger because the task focused only on one core and sleep another core so that they may use upto 100% of one core rather than dividing it to another core (MAYBE, IT'S JUST HYPOTHESE)
I don't even know how it works ?
Will try, thanks for your work.
Thanks for this mod. I'll try, I hope this mod will update reguraly.
Sent from my Redmi 3X using Tapatalk
Could you please make a version for Bliss rom too ? Thnaks!
My redmi lags with the mod my friend.. Im using de latest weekly
Enviado desde mi Redmi 3S mediante Tapatalk
Crissdua said:
My redmi lags with the mod my friend.. Im using de latest weekly
Enviado desde mi Redmi 3S mediante Tapatalk
Click to expand...
Click to collapse
Same
Wysłane z mojego Redmi 3S przy użyciu Tapatalka
miui people report about lags. thanks.
im working on it. if you want to solve this problem fast, just try to make 1 change in "/system/etc/init.qcom.post_boot.sh"
add one little cpu always online at line 1502:
Code:
echo 2 > /sys/devices/system/cpu/cpu4/core_ctl/min_cpus
or more radical
add one big cpu always online at line 1494:
Code:
echo 1 > /sys/devices/system/cpu/cpu0/core_ctl/min_cpus
or even try both changes together, why not
ps.: not bad if you will report about power consumption changes (if any) also. means power consumption in acive mode (display on).
it often stucks only on one core enabled which cause lags. RR ROM
difr said:
miui people report about lags. thanks.
im working on it. if you want to solve this problem fast, just try to make 1 change in "/system/etc/init.qcom.post_boot.sh"
add one little cpu always online at line 1502:
Code:
echo 2 > /sys/devices/system/cpu/cpu4/core_ctl/min_cpus
or more radical
add one big cpu always online at line 1494:
Code:
echo 1 > /sys/devices/system/cpu/cpu0/core_ctl/min_cpus
or even try both changes together, why not
ps.: not bad if you will report about power consumption changes (if any) also. means power consumption in acive mode (display on).
Click to expand...
Click to collapse
yes, mine feels lag too, but only at the start after long sleep. it's fine after some minutes/hours regular use
Got a great battery life improvement after using this mod. Arround 8,5 hours SOT (remaining at 8%) full 4G data with heavy browsing & some gaming use
Waiting for more feedback, thanks for making this mod!
first post updated. please, take a look.
Bliss added.
difr said:
Bliss added.
Click to expand...
Click to collapse
Thanks! I'll update this post after trying it out.
with rr antutu score is 40k, when use your latest mod, my antutu score decrease to 36k.
Can you mod it for only 1 small core online? i want only battery life. Or just guide me how to do it
I want to know how to disable CPU cores to save power. It was possible on my nexus 5. but on my nexus 6p and now on my htc 10, I'm not sure if it's possible. I read that it's would need a kernel rewrite or something along those lines.
So does anyone know how to do this? I'm running latest LeeDroid ROM if that helps. thanks :good:
That's what I also wanted to know about the 10.
I had the mind before and there I could run with only one core, if not needed the other three cores. But if I needed power, the 4 cores are running.
It would be great, if there is an option in kernel settings to run all the cores only if they are really needed.
So the 10 is only a battery eater... Especially with sense roms I don't come through the day without charging.
On CM 14 or AOSP the battery is much more better, but with better core management it would be famous.
anyone got any info on this?
less cores doesn't mean better battery life, look at u11, "octa-core" and getting better battery life than 10 and anything else. it's een like if you have less cores, the cores which are online have to do all the work and might end up with locked max freq which will result in heat and more drain. so just keep the core control like it is and maybe just underclock
drago10029 said:
I want to know how to disable CPU cores to save power. It was possible on my nexus 5. but on my nexus 6p and now on my htc 10, I'm not sure if it's possible. I read that it's would need a kernel rewrite or something along those lines.
So does anyone know how to do this? I'm running latest LeeDroid ROM if that helps. thanks :good:
Click to expand...
Click to collapse
It is possible to disable cores with the custom kernel, and I believe force them to remain off at boot, but the HTC 10 uses a big/little cluster CPU setup and disabling cores isn't how you want to conserve power in my humble opinion.
The HTC 10 and some other modern devices uses BIG.little core ARM processor technology.
So the hardware and software is optimized to use all the cores to chase the best battery life and performance. I'm guessing that unless it's very specific usage scenarios, if you manage to force disable the cores with a custom kernel, you'll see both performance and battery life drop.
I would highly recommend installing a custom kernel, and tweaking the kernel settings while letting the hardware make full use of the BIG.little cluster system for efficiency. For high performance, I'd recommend one of the sense based kernel's that uses the HTC PnP Manager system. Something like Flar's ElementalX or TBalden's cleanslate kernel.
For battery efficiency, since you're really wanting to customize things for the best efficiency and battery life, try out the Helix kernel, by zeroinfinity. It's using a technology to optimize control of the processor based on "EAS" technology. EAS stands for "Energy Aware Scheduling" and zeroinfinity has written his "Helix Engine" to control the power profiles and thus power consumption of different apps, and you can customize the profiles to put any other apps you have in the profiles you want them.
This was a very basic and non technical summary, you can find tons of info on the kernels in the OP of each kernel thread. I would recommend making a backup with TWRP and trying both ElementalX and Helix kernels and seeing what works best in your usage scenario, before you start trying to force disable cores.
Here's a quick article I found on google, I'm at work and only briefly skimmed it, so no promises it's any good, but you can google BIG.little procs on Android mobile devices to find more imformation. https://community.arm.com/processors/b/blog/posts/ten-things-to-know-about-big-little
CharliesTheMan said:
It is possible to disable cores with the custom kernel, and I believe force them to remain off at boot, but the HTC 10 uses a big/little cluster CPU setup and disabling cores isn't how you want to conserve power in my humble opinion.
The HTC 10 and some other modern devices uses BIG.little core ARM processor technology.
So the hardware and software is optimized to use all the cores to chase the best battery life and performance. I'm guessing that unless it's very specific usage scenarios, if you manage to force disable the cores with a custom kernel, you'll see both performance and battery life drop.
I would highly recommend installing a custom kernel, and tweaking the kernel settings while letting the hardware make full use of the BIG.little cluster system for efficiency. For high performance, I'd recommend one of the sense based kernel's that uses the HTC PnP Manager system. Something like Flar's ElementalX or TBalden's cleanslate kernel.
For battery efficiency, since you're really wanting to customize things for the best efficiency and battery life, try out the Helix kernel, by zeroinfinity. It's using a technology to optimize control of the processor based on "EAS" technology. EAS stands for "Energy Aware Scheduling" and zeroinfinity has written his "Helix Engine" to control the power profiles and thus power consumption of different apps, and you can customize the profiles to put any other apps you have in the profiles you want them.
This was a very basic and non technical summary, you can find tons of info on the kernels in the OP of each kernel thread. I would recommend making a backup with TWRP and trying both ElementalX and Helix kernels and seeing what works best in your usage scenario, before you start trying to force disable cores.
Here's a quick article I found on google, I'm at work and only briefly skimmed it, so no promises it's any good, but you can google BIG.little procs on Android mobile devices to find more imformation. https://community.arm.com/processors/b/blog/posts/ten-things-to-know-about-big-little
Click to expand...
Click to collapse
was a good read, thanks! based on the quote from below from that website sounds like the little cores can drive the most battery savings the most .... which is my goal.
The LITTLE cores can be implemented to target lower leakage and a more moderate performance point, independently from the physical implementation of the big cores that are often tuned for higher frequency.
Click to expand...
Click to collapse
and seeing that you were a tester for helix htc 10 kernel, is it designed to with stock based ROM or just any magisk based ROMs? I did see that ASOP is not supported.
drago10029 said:
was a good read, thanks! based on the quote from below from that website sounds like the little cores can drive the most battery savings the most .... which is my goal.
and seeing that you were a tester for helix htc 10 kernel, is it designed to with stock based ROM or just any magisk based ROMs? I did see that ASOP is not supported.
Click to expand...
Click to collapse
Stock based sense roms. I just use it with regular rooted builds of leedroid or viper. It works with magisk and has been built to be fully compatible, however I use it for my normal modded system rooted sense based rom with supersu. I don't use or set up magisk, I'm still kind of old school.
But if you were to use magisk, @ZeroInfinity is running magisk as his daily since the last several builds, and I don't believe it's got any bugs or anything that doesn't work in the magisk build. One of the other team members @p50kombi knows a lot about magisk if you need to know anything further, I just have very limited magisk knowledge I'm general.
Sent from my HTC 10 using Tapatalk
CharliesTheMan said:
Stock based sense roms. I just use it with regular rooted builds of leedroid or viper. It works with magisk and has been built to be fully compatible, however I use it for my normal modded system rooted sense based rom with supersu. I don't use or set up magisk, I'm still kind of old school.
But if you were to use magisk, @ZeroInfinity is running magisk as his daily since the last several builds, and I don't believe it's got any bugs or anything that doesn't work in the magisk build. One of the other team members @p50kombi knows a lot about magisk if you need to know anything further, I just have very limited magisk knowledge I'm general.
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
magisk version works same as the version which writes to system
CharliesTheMan said:
Stock based sense roms. I just use it with regular rooted builds of leedroid or viper. It works with magisk and has been built to be fully compatible, however I use it for my normal modded system rooted sense based rom with supersu. I don't use or set up magisk, I'm still kind of old school.
But if you were to use magisk, @ZeroInfinity is running magisk as his daily since the last several builds, and I don't believe it's got any bugs or anything that doesn't work in the magisk build. One of the other team members @p50kombi knows a lot about magisk if you need to know anything further, I just have very limited magisk knowledge I'm general.
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
Great I also use supersu not magisk, probably same old school thing...also too tough getting things to play nice with magisk IMO. So for supersu do i just install v012 r1 systemless kernel and it should just work w/ leedoird? did you notice any functions on lee droid not working?
also do you underclock? recommend any kernel managers?
drago10029 said:
Great I also use supersu not magisk, probably same old school thing...also too tough getting things to play nice with magisk IMO. So for supersu do i just install v012 r1 systemless kernel and it should just work w/ leedoird? did you notice any functions on lee droid not working?
also do you underclock? recommend any kernel managers?
Click to expand...
Click to collapse
It's version 17, you'll download it from this post https://forum.xda-developers.com/showpost.php?p=73068312&postcount=1216 , sorry that link you had shouldn't be there, but systemless is the magisk version but now there's only one version, and the Aroma installer will let you choose the normal non-magisk version.
In the installer, there's a question that asks about installing custom scripts, I use the @ZeroInfinity script, the one from @roger81 and @TotallyAnxious are good too so you can't really go wrong, but I recommend starting with zero's, and you can reflash to experiment once you get going good with it. Rogers is great for battery life but his is a little more custom and extreme, which is why I'd start.
I use EXKM kernel manager, but I really recommend not changing many settings at first. Definitely leave the governor default with this kernel. I would run it like it comes out of the box, and see how your apps and battery life goes, and if you have apps causing a lot of drainage, maybe add them to the helix engine profiles before you start changing clock speeds.
You'll notice with EXKM the core frequencies reported in real time will look different from how it looks with a stock based kernel, but don't let that scare you.
My only other recommendation is if you use any other power saving apps like greenify or doze (I don't use any of them personally but some do) I would first get used to the kernel without them, so you kind of have a better idea of baseline.
CharliesTheMan said:
It's version 17, you'll download it from this post https://forum.xda-developers.com/showpost.php?p=73068312&postcount=1216 , sorry that link you had shouldn't be there, but systemless is the magisk version but now there's only one version, and the Aroma installer will let you choose the normal non-magisk version.
In the installer, there's a question that asks about installing custom scripts, I use the @ZeroInfinity script, the one from @roger81 and @TotallyAnxious are good too so you can't really go wrong, but I recommend starting with zero's, and you can reflash to experiment once you get going good with it. Rogers is great for battery life but his is a little more custom and extreme, which is why I'd start.
I use EXKM kernel manager, but I really recommend not changing many settings at first. Definitely leave the governor default with this kernel. I would run it like it comes out of the box, and see how your apps and battery life goes, and if you have apps causing a lot of drainage, maybe add them to the helix engine profiles before you start changing clock speeds.
You'll notice with EXKM the core frequencies reported in real time will look different from how it looks with a stock based kernel, but don't let that scare you.
My only other recommendation is if you use any other power saving apps like greenify or doze (I don't use any of them personally but some do) I would first get used to the kernel without them, so you kind of have a better idea of baseline.
Click to expand...
Click to collapse
Bonus points for being the least confusing AROMA installer I have used! and I used zero's as well. thanks for all your help! and one last thing.. isn't doze built into android nougat? or am I highly misinformed.
drago10029 said:
Bonus points for being the least confusing AROMA installer I have used! and I used zero's as well. thanks for all your help! and one last thing.. isn't doze built into android nougat? or am I highly misinformed.
Click to expand...
Click to collapse
It is you're correct, but there's a lot of "super doze" and dozingest doze around" sort of mods and tweaks people use, it's the extra modified stuff I would avoid for now, until baseline is established. However once you get things ironed out, @RogerF81 (if I spelled that Right) has tons of good info on further tweaking. He once tweaked his battery life to something like 7 or 8 hours screen on time with the Helix EAS kernel. That's just showing off.
Glad you like the Aroma installer, it nearly killed the poor dev trying to get it set up when he first started implementing it, he still probably throws keyboards if I ask for a black theme lol.
Sent from my HTC 10 using Tapatalk
Introduction:
Hello everyone!
The idea to this 'project' did blossom after having an conversation with @pkgnex about the general idea of creating something else that follows what he started with his PK's Tuning Script but with a twist, mainly as a complement to his own thread that you can find here, but also with a completely different vision and focus on what the script itself should achieve (and deliver) for kind of results for myself and for all of you personally, of course, that wants to try it out and use it as a "daily driver".
Shortly explained.
This script is created with the goal of improving both the battery life and performance of our Pixel 2 (XL) devices, and after a whole range of configurations and various set-ups, I've come up with something that, in my eyes, is worth sharing with you so that you can try it out yourself and judge on your own, with constructive feedback on what can be improved or added in future releases - if desired. My philosophy is, and will always be, this:
If something can be improved or altered in a positive way so the average user can feel and see a difference, then go for it. Non stop.
The latest release can be found here.
Disclaimer:
This is presented as "what if". If this modification screws up or breaks anything for you, I am not the one to be held responsible. It's a free will to try out this kind of changes/modifications/addons/tweaks, just don't blame the inventors for eventual bad results and/or screw-ups.
Note: This script is not recommended to be modified or customized by the user.
Features:
Reduced battery consumption
Device specific enhancements for best possible balance between battery life & performance
Enabled, and fully configured, Boeffla generic kernel wakelock blocker
Disabled a lot of useless stuff at kernel level (Improves battery life as well as performance)
CPUSet improvements & optimizations
Schedtune tweaks (Improves responsivness)
Power efficiency enhancements
Wide IO block tuning (Reduces the possibility of hiccups, lags and overhead)
Possibly other miscellaneous things I've forgotten to write down here, both big and small.
Requirements/what you need for getting this script fully working:
An unlocked bootloader
Your own specific choice of kernel
Latest possible version of Magisk
Busybox for Android NDK (by @osm0sis) and SQLite for ARM aarch64 devices (by @ianmacd) Magisk Modules
Patience
Installation/How-To use & abuse:
1) Download the attached ZIP
2) Extract the scripts
3) Move both scripts to the following location;
/data/adb/service.d and give both of them the following permissions (0775)
4) Reboot your phone, let Android boot to the launcher and let Magisk boot service do its crucial magic (takes a few seconds before the scripts is fully up and running around behind the scenes)
5) Enjoy!
Note: If you still are unsure how to do for making my kernel configuration / modification work & be up and running behind the scenes, then please read @Phalanx7621 phenomenal guide here or check out @Phalanx7621 in-depth video here. The installation method is the same for both the first generation as well as the second generation of Pixels!
Credits:
@nathanchance for his contributions with his Flash Kernel
@franciscofranco for all the information on which kernel wakelocks that is safe to block
@Phalanx7621 for his phenomenal how-to guide
@Lord Boeffla for his awesome generic kernel wakelock blocker
@pkgnex for inspiring me walking into this partially unknown territory.
@flar2 for his excellent EXKM application and ElementalX Kernel
@osm0sis for his Magisk Busybox module
Everyone that I've forgotten to mention here
Telegram:
If you want to try out betas / previews of my script before they are officially released, or just hangout and chat a little, then join the official Telegram group here
To-Do list:
Port this project to all of my additional devices
Include kernel specific scripts for every released P2(XL) custom kernel Done
- Even for stock kernel with SafetyNet patch by @iissmart Done
Optimize and properly tune things even further for best possible balance between battery life, system responsivness and performance Done
Sidenote:
If you optionally want to donate a beer or five as a way to show your appreciation for all the dedicated hours and work that I am putting into this mod on a daily rate - then this link is the way to go!
Contributors:
@xFirefly93
Created: 2018-09-18
Last updated: 2019-11-04
EDIT: My changelog dedicated post have exceeded 30000 characters, so I have decided that the changelog will only be included in the respective update posts from now on!
So you all know how the situation is.
xFirefly93 said:
Changelog:
Note: This version is only tuned for Flash kernel. Next release/update will contain more scripts, specially tuned for each of the released kernels for the whole Pixel 2 line-up.
v1.0 (Initial testing & feedback release):
- Initial release.
Click to expand...
Click to collapse
Nice addition my friend. Cya at telegram
Nice work!
:good:
Short note
If you have any kind of specific wishes or suggestions on changes and/or tweaks, either kernel specific or universal across the whole released kernel line-up for Pixel 2 (XL), that the pretty soon up-coming v1.1 should include (can be something that you have read about somewhere else or it is maybe something that I've missed) - send me a personal message asap and I'll take a deep look into it and see what's possible to do and achieve.
Or leave a comment here in the thread about it, if you prefer it that way.
Can we have this running along with PK's tuning script? I mean can we install both...
ram4ufriends said:
Can we have this running along with PK's tuning script? I mean can we install both...
Click to expand...
Click to collapse
It is nothing that I am recommending because I am using a lot of settings that is tuned to deliver the opposite to what @pkgnex is using in his script. It can cause conflicts or issues down the road, in a worst case scenario, like battery life regressions or reduced performance because of an uneven mix of settings.
Some of my tweaks will be overridden by his, and naturally the opposite. Just for making it simple for you:
As I and pkgnex discussed a couple of days ago through PM regarding this "situation"..
- If you want a strict cutting edge performance boost, then use his script.
- If you want a balanced boost that enhances both performance and battery life as far as possible, then use my script.
But not both of them at the same time, because of the reason mentioned here above.
Nice to see! Kudos
xFirefly93 said:
Changelog:
Note: This version is only tuned for Flash kernel. Next release/update will contain more scripts, specially tuned for each one of the released kernels for the whole Pixel 2 line-up.
v1.0 (Initial testing & feedback release):
- Initial release.
Click to expand...
Click to collapse
Hi, Please help me how to go location where we have to move tweaks file.
pushpendrayadav said:
Hi, Please help me how to go location where we have to move tweaks file.
Click to expand...
Click to collapse
Move 01tweaks to the following location;
/sbin/.core/img/.core/service.d and give it the following permissions (0755)
I would recommend you to use the awesome FX Filebrowser with the root addon for this, just don't forget to enable so you can show hidden folders.
See attached screenshot for how to do it.
xFirefly93 said:
*]3) Move 01tweaks to the following location;
/sbin/.core/img/.core/service.d and give it the following permissions (0755)
I would recommend you to use the awesome FX Filebrowser with the root addon for this, just don't forget to enable so you can show hidden folders.
See attached screenshot how to do it.
Click to expand...
Click to collapse
Thanks for quick reply, I will try and revert if any thing required.
xFirefly93 said:
Changelog:
Note: This version is only tuned for Flash kernel. Next release/update will contain more scripts, specially tuned for each one of the released kernels for the whole Pixel 2 line-up.
v1.0 (Initial testing & feedback release):
- Initial release.
Click to expand...
Click to collapse
Can i use this on flash v2.58 since I'm still on Oreo?
Sent from my Google Pixel 2 XL using XDA Labs
Prattham said:
Can i use this on flash v2.58 since I'm still on Oreo?
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
I have only tuned this for Pie/9.0 builds of Flash kernel.
You can always try it out and see if it works with the same (or better) results on Oreo 8.1, just don't hold me responsible if something gets screwed up in any kind of way(s).
EDIT: See my 'Disclaimer' note in the OP, @Prattham.
Prattham said:
Can i use this on flash v2.58 since I'm still on Oreo?
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
It should work... you should try it and report back.
If it doesn't, I know the script in my thread works on Oreo and Flash Kernel. This script and mine aren't that different... yet.
---------- Post added at 07:22 AM ---------- Previous post was at 07:17 AM ----------
ram4ufriends said:
Can we have this running along with PK's tuning script? I mean can we install both...
Click to expand...
Click to collapse
You can, but the way the scripts are numbered will mean that my script will over-write a few of the values tuned by this script. It should still be OK, and it might even work great, but it hasn't really been tested by either of us. It would better to try both and pick the one that you like best for your usage case and personal preferences.
As @xFirefly93 has stated, we have slightly different goals with our scripts. But, in truth, there is still a lot of commonality so finding a drastic difference between them is still unlikely.
Update!
v1.1 First major release
- Initial releases for every released custom Pixel 2 kernel.
- Added a few additional settings for further battery life, as well as, performance improvements.
- Shortened a few lines which explains what the parameters changes does.
- Packed everything into a single ZIP file with specific names for each kernel tuning script.
- See attached script below (and in the OP)
Enjoy!
Is there anyway to check if the script is running in the background? Also, I'm assuming we don't need to do anything after a kernel update.
praveen6585 said:
Is there anyway to check if the script is running in the background? Also, I'm assuming we don't need to do anything after a kernel update.
Click to expand...
Click to collapse
I'll include a minor fix, that creates/pushes an output file to the internal storage after the script have been executed and is up and running, with v1.2.
Until then, you can always go to (for taking an example) the /proc/sys/fs/dir-notify-enable path and see so the parameter is set to 0, which is the value that I've set it to. Just as an easy & simple "fail safe".
Out of curiosity. What will happen if i don't have busybox?
Should my screen be super dim and not really adjust to ambient light anymore?
arvylas said:
Out of curiosity. What will happen if i don't have busybox?
Click to expand...
Click to collapse
Some parts of the script won't execute at all without it.
jbarcus81 said:
Should my screen be super dim and not really adjust to ambient light anymore?
Click to expand...
Click to collapse
I have enabled, and tuned, backlight dimmer for kernels that includes it. That's why the screen is a little bit dimmer/darker.
Thermals, Kernel Managers and their affect on short and long term battery life.
As requested, by fellow LePro 3 owners, I created this thread for a discussion on the benefits of thermal management, using manual thermal settings, and sharing flashable thermals and user settings. To be clear I am not yet an expert on this subject, so I am learning along with everyone else. But, why not share the experience?
Of course we want our phones to last, while also pushing them to their limits, but in a safe and efficient manner. Recently our developers have shared their ideas on thermal management, and they have been gracious enough to allow us access to their own settings, that can be used across multiple builds. See the link below to download the first set of flashable thermal management options.
Recently, some of us have encountered shutdown issues, with some roms having battery stats reporting issues, unexpected shutdowns, and unrelated unrelated lockscreen issues. We users have found that often these troubled builds can be fixed by flashing a fix. Such as the thermals from a previous or other builds that did not have the same issue. Fortunately, it appears that we can use alternate perf and thermal management files that have not only offered a quick fix for some of these current issues, but also offers a longterm solution for using old, new, and future roms builds...collectively. :good:
The plan is to make this discussion much more extensive and simple
So consider this initial post to be an ever changing rough draft.
The end goal is to make it much easier for people to access and share their thermal management files or settings in one easily found central location, and hopefully for everyone to share their suggestions along the way
Helpful to Gamers who want safe power and speed.
Helpful to Non-Gamer's who want simply want stable performance, long battery life
Help everyone by helping us learn to optimize our phones to last for the longterm.
For me, no more repeating the same stuff over and over on various Rom threads, or private messages. No more having trouble digging through threads to find a recommended thermal or setting. So please participate, we can keep the OP updated whenever anything new comes along. Should I get access to something new I will add it to the Megadrive and make a post
Inventory
So far we have the thermals from Lineage, AEX, Balkan, AICP, EUI and in my view one the best is the latest by Jabashque. The idea of this post is to share the thermal settings so that they can be used on whichever ROM you want to try out.
Finally, you do not necessarily need to use these thermals unless you have an issue with general usage, heat or battery life. However, you will immediately notice the benefits.
Edit ( Updated Info)
Regarding kernels: Personally, I use BlackScreen 6.3, it has a long list of governors and I like options.
Currently the best thermal option is the Jabashque edit ( Thermal Fix 7 ) Get it Here: https://forum.xda-developers.com/showpost.php?p=78717015&postcount=18
These thermals work!
Over the past 2 weeks, I have gone back and tried several old ROMs, and these thermal and profiles make those old Roms perform so much better! For example, the September 3rd JMXL version of DotOS.: Yes, Its outstanding with the Sergey thermal. BootLegger's is also much improved, and it was already pretty great as it was. The Miui ROMs, are significantly improved by far! etc.
Of course we have so many great Roms. Occasionally, we get a build that is experimental and it may have unexpected issues. We have seen over the past week that flashing an alternate thermal is a perfect way to save the installation without having to revert to an earlier build. I mentioned old Roms above, they also work on every single Pie Rom.
Here is My Mega Drive Link for all of Thermals that I have collected so far
https://mega.nz/#F!9EokAQTb!Au6cBnJaCJXZrUlaXSLjhg
Alternate Link with key
Link: https://mega.nz/#F!9EokAQTb
Key: Au6cBnJaCJXZrUlaXSLjhg
Jabasque's thermals are in the Jabashque folder. Version 1 and 2 :
Probably shouldn't result in any difference if not gaming.
"Most likely, it would only be noticeable if you're not throttled down to 1440/1900MHz and you're running something that's using 100% cpu" ( Jabashque)
What to use
If you are wanting long battery life and low temperatures use Sergey's thermal or JaBashque version 1
If you want stock EUI faster throttling but slightly higher temps use the ShivateJappedi EUI thermal.
If you want to leave your cores unchanged from the default setting with higher temp throttling, more full power access and yet still safe while use JaBashque 6 Its a rework of the EUI 30s thermals designed to work better on modern Pie Roms : See more information here: https://review.lineageos.org/c/LineageOS/android_device_leeco_zl1/+/238809
Soon, I will create a post in the reserved section below to deeply define the details and differences between these thermals. Because while they all have similarities, they are also very different from one another.
In addition, I plan to add various kernel manager settings for various uses : Gaming, Long Life etc.
Finally, even when moving to another Rom. kernel manager programs such as Ex Kernel Manager will allow you to import and use saved profiles. It seems that it is possible to save the best of each of these thermals by saving the profiles of each. We can share those settings! Then later you can manually choose within your kernel manager which settings you want to use by simply importing choosing a preferred profile.
I hope this clears up the confusion. As mentioned this is a work in progress that was requested by 3 people. This is just the beginning of this discussion that will help everyone understand how to use Kernel Managers and the add-on thermals patches. I need to do some further research to make it all worthwhile . For example, although I love the elementalX governor, I haven't researched it enough to explain why I think it's better. So I plan to find out specifically what it's actually doing vs what other governors do, and how does changing sample rates, and wake locks affect performance and battery life etc.
If there are any experts out there? Please chime in and contribute.
See Updated information from Jabashque, which explains the differences between patch 1 and patch 2
https://forum.xda-developers.com/showpost.php?p=78670166&postcount=2
Installation
Dirty flash the patch that you want to use..thats it.
If you want to try a different patch, dirty flash the Rom, reflash Magisk and dirty flash the patch
You can manually adjust settings by going to /vendor/etc/thermal-engine.conf
Update from JaBashque Edit April 21 2019: ( I use ThermalFix7, its my personal favorite/ it is the best and the safest period.)
@tsongming
Hey, after seeing your thread about thermals, I felt I should write an explanation about how my v1 and v2 differ from stock EUI thermals that you could add to that forum post, since the one you have on there was me describing the difference between v1 and v2, not stock EUI: "JaBashque"
There are two different set of sensors that the original config monitors for the CPU:
the CPU temp sensors (tsens_tz_sensor{4,6,9,11}) and xo_therm_buf. The CPU temp sensors measure the temps of the cores themselves. xo_therm_buf measures what seems to be some sort of overall temperature, though I'm not sure what in particular. However, xo_therm_buf does correlate more directly with how hot your phone feels.
Original:
thermal-engine rapidly throttles your CPU down to 902MHz on the little cores and 825MHz on the big cores when any one of the cores hits 95C, and stops only when the hottest core drops back to 65C. When xo_therm_buf gets to 43C, thermal-engine slowly throttles all your cores to 902MHZ little and 825MHz big until xo_therm_buf drops back to 40C.
Patchset 1:
thermal-engine rapidly throttles your CPU down to 902MHz on the little cores and 825MHz on the big cores when any one of the cores hits 85C, and stops only when the hottest core drops back to 65C. When xo_therm_buf gets to 37C, thermal-engine throttles all your cores to 1440MHZ little and 1900MHz big until xo_therm_buf drops back to 34C. When xo_therm_buf gets to 43C, thermal-engine throttles all your cores to 1132MHZ little and 1363MHz big until xo_therm_buf drops back to 40C. When xo_therm_buf gets to 50C, thermal-engine throttles all your cores to 979MHZ little and 1132MHz big until xo_therm_buf drops back to 43C.
Patchset 2:
thermal-engine throttles your CPU down to 1516MHz on the little cores and 2054MHz on the big cores when any one of the cores hits 95C, and stops only when the hottest core drops back to 65C.
This change was made because I realized that the previous version still had a situation where the CPU performance can tank unpredictably. xo_therm_buf-related CPU throttling is same as Patchset 1.
Thanks to JaBashque for sharing his work! Patch-set 2 is my personal preference. Although the Sergey Perf + Combo is also very good.
@tsongming
Thank you very much for listen us and always give your help.
Rigth now I am on BaikalOS 28th December 2018, if I want to flash any Profile of those, what I should to do (Clean flash? This first, later that etc... and Wich of them I should ti flash for best battery, I do not play on movil)
I am very curious for test this...
I have x722, I do not play. I am now on aex 5.7 oreo. The most depends on the battery, so which zip to flash ? This is a great topic.
kukuteku said:
@tsongming
Thank you very much for listen us and always give your help.
Rigth now I am on BaikalOS 28th December 2018, if I want to flash any Profile of those, what I should to do (Clean flash? This first, later that etc... and Wich of them I should ti flash for best battery, I do not play on movil)
I am very curious for test this...
Click to expand...
Click to collapse
You can dirty flash these thermals.
Personally I like Sergey and Jabashque version 2 the best so far on Pie roms.
The Shivate patch works really well on Marshmallow, Nougat and Oreo.
The Sergey patch works really well on Oreo and Pie, I haven't tried it on Nougat Roms yet.
You can manually adjust settings by going to /vendor/etc/thermal-engine.conf and In this same folder ( vendor/etc) you can also make audio changes, and I am not talking about policies and Tasha.xml files, although you would make changes to those files too, if wanted. This will be something that we can discuss in more detail soon.
gsiwy said:
I have x722, I do not play. I am now on aex 5.7 oreo. The most depends on the battery, so which zip to flash ? This is a great topic.
Click to expand...
Click to collapse
Either the Sergey or the JaBashque 2 with be perfect, depending on what you want.
Use Sergey if your goal is battery saving.
Use JaBashque 2 if you want better gaming performance.
@tsongming thank you for this useful thread. I just have one question. I noticed that sergey's thermal file you uploaded comes also with perf so do you know is it maybe EUI perf and if not is it possible to upload just sergey's thermal without perf? Thanks.
I'm using aex 6.2 and i play a lot of games, but i looking for something that gives the power to run the games and after that (of course after some time without using the cellphone to cooldown) use the phone without worry of him overheat with simple use like 39 or 37 ºC. Do you have something like that?
I have a x722
MnMchill said:
@tsongming thank you for this useful thread. I just have one question. I noticed that sergey's thermal file you uploaded comes also with perf so do you know is it maybe EUI perf and if not is it possible to upload just sergey's thermal without perf? Thanks.
Click to expand...
Click to collapse
Sure, I can extract the perf, I will do that and add it to a separate folder so that there are two options.
Edit: Here is the Sergey thermal only
I removed the perf and added the additional key edit options from the Jabashque patch. So this a combo patch.
Use at your own risk
However, I have tested this and it works fine. I wanted to give the caveat that I am a Noob at this! But its okay. FYI: all I did was remove the perf, so now the perf will come from the rom and I added the Moshe key feature, which some Roms such as AICP includes anyway.
https://mega.nz/#F!ZVpXBQjC!PpXn1ZtLEHJb72Gbw7nWqg
Heitor Lima said:
I'm using aex 6.2 and i play a lot of games, but i looking for something that gives the power to run the games and after that (of course after some time without using the cellphone to cooldown) use the phone without worry of him overheat with simple use like 39 or 37 ºC. Do you have something like that?
I have a x722
Click to expand...
Click to collapse
Use the Jabashque 2
See updated in depth info from JaBashque : here: https://forum.xda-developers.com/showpost.php?p=78670166&postcount=2
So, thank you for your work!!One question,i am at the last AICP Pie,do you believe is better to flash one of these or stay with the settings of AICP?
Thanks in advance!
Don't work
I used to play pubg and the big stay on 1,4 ghz and little on 1,0 ghz
tsongming said:
Sure, I can extract the perf, I will do that and add it to a separate folder so that there are two options.
Edit: Here is the Sergey thermal only
I removed the perf and added the additional key edit options from the Jabashque patch. So this a combo patch.
Use at your own risk
However, I have tested this and it works fine. I wanted to give the caveat that I am a Noob at this! But its okay. FYI: all I did was remove the perf, so now the perf will come from the rom and I added the Moshe key feature, which some Roms such as AICP includes anyway.
https://mega.nz/#F!ZVpXBQjC!PpXn1ZtLEHJb72Gbw7nWqg
Click to expand...
Click to collapse
Works good, thanks.
geo307cc said:
So, thank you for your work!!One question,i am at the last AICP Pie,do you believe is better to flash one of these or stay with the settings of AICP?
Thanks in advance!
Click to expand...
Click to collapse
If you are not having any issues, then don't install any of these.
However, if you want to try it, keep a record of your existing performance, battery life, heat levels for battery and CPU (when idle) and compare that against using these thermals.
If you flash one of these thermals and don't like it. You can quickly return to your previous settings by dirty flashing your rom, or by restoring the system part of a nandroid backup.
Heitor Lima said:
I used to play pubg and the big stay on 1,4 ghz and little on 1,0 ghz
Click to expand...
Click to collapse
So which one of the 5 thermals did you try? Some of them include perf
Understand that you still have to setup your kernel manager. If you are wanting to use it for Gaming use the JaBashque version 2 to and leave the cores on the highest setting.
Yes, it works. It works for me a and a lot of other people on Telegram
If you want low temperatures and long battery life underclock the cores at idle my battery hovers around 85 F and the CPU are around 100-105F
Just so you know you can access your thermal.conf file and edit it manually to increase your thermal limit in /vendor/etc/thermal-engine.conf
Next, save a copy of your existing current setup as a profile, so you can easy switch from one to another with ease and easily compare it to the changes of using an alternative file. You can tweak it to the settings that you are wanting...Just keep safety in mind or you could burn up your CPU.
UpDate!
@jabashque has spent time recently improving his thermals further, and released several new versions .
The latest and greatest is now version 6!
Get it here: https://mega.nz/#!pFoSRaQA!R068WV-YltbQAFzuc3aH72z_OPyrN2uBjgsux2h0dNY
If you like it, please thank him!
Anyone who is using the last build of Jabashque 6 . It has a small error with he tthermal.
Flash this zip file from my Mega drive.
https://mega.nz/#!UZwhAQwY!GDUYQX2Ewcj92jjhs2t-oYnVcUKSbu9WfaOyAJjaKzs
The file adds a GPU setting to the Thermal
Repair by Jabashque: https://mega.nz/#!UZwhAQwY!GDUYQX2Ewcj92jjhs2t-oYnVcUKSbu9WfaOyAJjaKzs
Reference : https://review.lineageos.org/c/LineageOS/android_device_leeco_zl1/+/239612
I want to install Bootleggers os 8.1 on x722 and I have a question: after installing romu and gapps and initial configuration I can flash BS5.1-r3 AND thermal.zip a magisk mantle? will thermal.zip not interfere with BS? Thank you.
gsiwy said:
I want to install Bootleggers os 8.1 on x722 and I have a question: after installing romu and gapps and initial configuration I can flash BS5.1-r3 AND thermal.zip a magisk mantle? will thermal.zip not interfere with BS? Thank you.
Click to expand...
Click to collapse
Sorry I haven't been on XDA much recently, and never received the notification.
If you use Bootleggers, the stock kernel is fine. But blackScreen 6.3 will work fine and it gives you more options. You flash the thermal at anytime. I recommend the Thermal-fix7 which is Jabashque 6 that I edited to fix a typo. No there is no conflict
Purpose
I have been jumping from one UI to gsi's to back to one UI. I just want to know what are yall experiences with different roms and maybe stock one UI and what mods/workarounds or apps do you use to solve problems. Any custom kernel etc. I'll start with mine here
My Current Configuration:
(i edit this op when i switch a gsi or attempt further mods)
OS: YAAP GSI
Device: SM-A325F
Firmware version: A325FXXS4DWD4
Rooted with KernelSU.
Using OrangeFox from here.
Mods:
1. Custom kernel:
I made my own permissive custom kernel from A325FXXS3CWB3 Samsung's source from here.
It has a lot of changes which include removing entire security and knox debloat as it is not used in GSI.
It also has changed default ram compressor to lz4 instead of lzo-rle which should be faster.
I have tested this kernel on A325FXXU3DWB8, A325FXXU2CWA6, A325FXXU2CVK3.
It also boots on one UI.
It was possible all thanks to @KrutosVIP and his amazing work here.
You can download it from here.
Just flash it in twrp with no additional steps required. Make sure to backup boot in case it doesn't boot.
NOTE: i switched to my kernelsu kernel which is available here on a32 threads. it still offers the same features but it has kernelsu
2. Penguin Gcam and FreeDcam:
I currently use Penguin Gcam from here.
It includes needed features. The only thing broken is slow motion.
I use FreeDcam Inorder to get access to all the other cameras including Ultra wide, depth sensor and macro camera. It works great. The only problem as of my writing on this thread is that changing the ISO manually crashes the app.
Fortunately @uluruman has created the files and presets for this app which work amazingly. You can check it out from here.
You can check out FreeDcam on the F-Droid store from here or on github from here.
3. Workarounds in Phh settings
Samsung Features:
1. Enable extended brightness range (fixes brightness issues)
2. Double tap to wake (optional. But you can use it if you like)
3. Enable access to all cameras (Important for FreeDcam)
4. Enable extra sensors
Misc Features:
1. Use alternate way to detect headsets [fixes headphone jack] (Optional in roms built after or during march patch since they already include my overlay.)
2. Force FPS (set to your desired refresh rate) [i use 90] (NOTE: some gsi's have issue with this on android 13 firmware. There is no fix to this. Upgrade to march patch because project elixir seems to have this fixed on march spl. Or try switching to another gsi or downgrade firmware)
3. Force alternative backlight scale, Allow setting brightness to the lowest (needed to fix brightness bar)
4. Force Enable Camera2API HAL3 (To make FreeDcam work)
5. Force Disable AD2P offload (Fixes bluetooth audio for android versions 12 and below.)
6. On newer gsis Bluetooth is broken. To fix Enable Use systemwide bt hal.
Reboot after changing settings is recommended.
4. Magisk Modules
1. Audio Modification Library, Dolby Atmos from Moto G Pro (NOTE: Moto core is required for this.) [Just a dolby atmos port i like]
2. Fullscreen/Immersive Gestures (Q-T) (Removes keyboard space bar at bottom)
3. mindetach, Youtube Revanced Extended (Youtube revanced extended and to detach it from playstore which prevents updating.)
4. Safetynetfix MOD, Shamiko (Dealing with safetynet issues and bypassing root checks in applications)
5. LSPosed - Zygisk (Mostly to get broken face unlock back since broken face unlock on gsi's due to unknown issue with android 13 vendor.)
5. Xposed Modules
The only Xposed module i use is universalauth. Using this module i can get face unlock back on every gsi due to a unknown issue with android 13 firmware or vendor. It works reliably.
Note: It broke in android QPR1 so dev posted a custom xposed link here.
Its broken on QPR2 again. The current workaround is to disable auto dismiss lock screen in face unlock app.
If it happens on QPR updates just remember the workaround.
Since It is unable to download the apks for libraries. You need to download Moto face unlock from here.
Then import it.
To allow restricted settings go to app info of face unlock app. press three dots on top right and allow accessibility. Entered pin if prompted.
Enjoy face unlock.
Over all Experience:
I am happy with using it. Its super smooth. Bugs are of course expected in generic system images. But they are good enough to use daily. Gaming performance in some cases is amazing. Enabling allow higher fps in games in some roms like crdroid unlocks many settings. e.g. i could play cod at 90Fps at medium. The fps hovered around 60-90 fps. It was amazing. If you set the performance mode to performance in game space in roms that have it, It works amazingly. A game restart is required and it works. Actually bumps the fps by a lot. I still do switch from gsi's to gsi's since sometimes i get bored or the gsi lacks some important things. For now In my opinion using a GSI is far better than stock firmware for me. The gsi's i would recommend are crDroid, Elixir, Pixel Experience, EvolutionX, LineageOS (TD based)
you can find more GSI's from here.
Hoping to hear about what you use on your device and how your experience is.
For One UI users. i have a thread on floating tweaks which enable many features and small tweaks to help phone run a lil bit faster check it out from here
Another camera app which can use all the cameras is Open Camera. It is more convenient than FreeDCam, has almost all the same features and even more, for example HDR and panoramas, but unfortunately, like FreeDCam, cannot shoot video from extra cameras out of the box. I tried to edit the settings file manually but it didn't help as it did with FreeDCam, I suppose there should be something else fixed in the app itself, but still I'm going to try again editing the settings in the future.
uluruman said:
Another camera app which can use all the cameras is Open Camera. It is more convenient than FreeDCam, has almost all the same features and even more, for example HDR and panoramas, but unfortunately, like FreeDCam, cannot shoot video from extra cameras out of the box. I tried to edit the settings file manually but it didn't help as it did with FreeDCam, I suppose there should be something else fixed in the app itself, but still I'm going to try again editing the settings in the future.
Click to expand...
Click to collapse
I used it before. i actually got the cameras to work once. i dont know how. I ditched freedcam for it. But idk maybe after i switched roms or an update they broke again? i think if you look in info it says Only 2 cameras present. Our limited camera2api only shows 2 cameras. While freedcam forces to use the camera no matter what.
I may be wrong i saw something abt this somewhere.
Maybe downgrading to an older apk might help. But i sadly dont have enough time for that
I also recommend using No-frills CPU Control CLASSIC to lower the min CPU frequency to 500 MHz and set govenor to "shedutil" (if it's not already). Also set Android System battery usage to "Restricted" (Settings > Battery > Battery Usage > Android System). That should reduce the battery consumption in the doze mode.
Captain_cookie_200 said:
I used it before. i actually got the cameras to work once. i dont know how. I ditched freedcam for it. But idk maybe after i switched roms or an update they broke again? i think if you look in info it says Only 2 cameras present. Our limited camera2api only shows 2 cameras. While freedcam forces to use the camera no matter what.
I may be wrong i saw something abt this somewhere.
Maybe downgrading to an older apk might help. But i sadly dont have enough time for that
Click to expand...
Click to collapse
Open Camera can now shoot photos from all cameras, only shooting video does not work.
uluruman said:
I also recommend using No-frills CPU Control CLASSIC to lower the min CPU frequency to 500 MHz and set govenor to "shedutil" (if it's not already). Also set Android System battery usage to "Restricted" (Settings > Battery > Battery Usage > Android System). That should reduce the battery consumption in the doze mode.
Click to expand...
Click to collapse
i have noticed big cores are alr at schedutil. although some roms report efficiency cores using "null" like no governer at all. But kernel manager says they use schedutil. I mostly set my governer to ondemand.
uluruman said:
Open Camera can now shoot photos from all cameras, only shooting video does not work.
Click to expand...
Click to collapse
idk that small popup for switching cameras is gone. and it cant use the other cameras
So i just installed crdroid 9.2 looks like gms was going crazy in the bg eating my cpu. The fix i found is to run this command.
su -c pm disable com.google.android.gms/.chimera.GmsIntentOperationService
this seems to fix it and i dont see anything broken. I searched it and looks like this issue does happen for alot of users.
Captain_cookie_200 said:
So i just installed crdroid 9.2 looks like gms was going crazy in the bg eating my cpu. The fix i found is to run this command.
su -c pm disable com.google.android.gms/.chimera.GmsIntentOperationService
this seems to fix it and i dont see anything broken. I searched it and looks like this issue does happen for alot of users.
Click to expand...
Click to collapse
That's only if you're using a gapps version. I am using the vanilla version of LOS, so there are basically only two com.google.android.[something] packages in my system: com.google.android.apps.googlecamera.fishfood and com.google.android.networkstack.tethering.overlay
uluruman said:
That's only if you're using a gapps version. I am using the vanilla version of LOS, so there are basically only two com.google.android.[something] packages in my system: com.google.android.apps.googlecamera.fishfood and com.google.android.networkstack.tethering.overlay
Click to expand...
Click to collapse
yeah i m talking about people who use gapps. they are quite important in my day to day life otherwise i'd get rid of em
Just to update here. I tried magisk v26 and seems like it works fine. Although it had issues with my Dolby Atmos mods so i got rid of it and downgraded to v25.2 again. Otherwise all of my other modules were working fine and i didnt see any issues.
I have lineage os 20, but bro, don't have phhsetings haha
ApiYoshi said:
I have lineage os 20, but bro, don't have phhsetings haha
Click to expand...
Click to collapse
using light i see.
Captain_cookie_200 said:
using light i see.
Click to expand...
Click to collapse
Yep, it was a error hahaha, im now on another lineage gsi which have phh
Bro, you know if on Crdroid, the SD works normal? For me, as the SD is on exFAT, many gsi don't recognize it
ApiYoshi said:
Bro, you know if on Crdroid, the SD works normal? For me, as the SD is on exFAT, many gsi don't recognize it
Click to expand...
Click to collapse
i dont use a sd card. even tho I need one badly. it would save alot of time for me when switching gsi's
Captain_cookie_200 said:
i dont use a sd card. even tho I need one badly. it would save alot of time for me when switching gsi's
Click to expand...
Click to collapse
Oooh, well... Yes, a SD is so useful for that, in the SD I backup almost everything
ApiYoshi said:
Oooh, well... Yes, a SD is so useful for that, in the SD I backup almost everything
Click to expand...
Click to collapse
I will test the gsi, is stable?
ApiYoshi said:
I will test the gsi, is stable?
Click to expand...
Click to collapse
yes. march patch (qpr2) just came out today. give it a go