{
"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"
}
CurbThePain's RevKernel - Desire 510 Ed.
"A Brutal Kernel"
Disclaimer
I am NOT responsible for anything that happens to you, your phone, or anything as a result of flashing this kernel. It is of your choice to flash said kernel and or proceed to root your phone. So dont blame me if your phone is dead, it is YOUR fault.
Features:
Code:
F2FS Filesystem support
Write Protect Removed
Less aggressive interactive gov
Overclocked Ram to 566MHz
Overclocked Gpu to 477Mhz (will not be visible) test this and tell me if you get any performance jumps in gpu intensive games.
To do:
Add better touch drivers (maybe)
Add ram space and trim already used ram.
Add any optimizations possible.
FYI's
Code:
Requests,
You guys should request any feature you want added! :D I'll get around to
trying to add all of it!
Give me time.
I am a very busy person, I have school and a almost full time job. I'll work as
hard as I possibly can on all of this but you have to be patient.
I am sorry if I say something will be uploaded and its not. I don't have a way
to do builds and its hard to work on ROM's without constant access to a pc.
I will try to update the OP if plans change.
Fixed (Cameras, WiFi, any lags or old bugs)
XDA:DevDB Information
RevKernel, Kernel for the HTC Desire 510
Contributors
CurbThePain, Rbheromax
Version Information
Status: Beta
Created 2014-12-09
Last Updated 2015-3-07
How is this different than your other kernel other than added Boost Mobile support?
http://forum.xda-developers.com/des...print-virgin-mobile-stock-desire-510-t2958969
Kolma said:
How is this different than your other kernel other than added Boost Mobile support?
http://forum.xda-developers.com/des...print-virgin-mobile-stock-desire-510-t2958969
Click to expand...
Click to collapse
Look at the tags. Im working on adding dt2w and the smartass gov. cpuboost (better power to performance managment) wheatly and intelleactive are already working. me and rbheromax are trying to get this all sorted out. His current builds have broken wifi. Mine had wifi at first and i didnt modify any wifi drivers so it SHOULD in theory work.
All in all at the end of the day (not today) the kernel will end up featuring dt2w, 3 new govs, overclock, maybe voltage control, and support lots and lots of file systems. Oh cant forget write protect is removed lol.
Reserved
Sent from my 0PCV1 using XDA Free mobile app
Faux sound support?
Hmmm feature request...well fauxsound, row scheduler(others), I think this kernel can be throttled up to 1.5 or 1.8 ghz per core, but for battery saving, 1.5, maybe seeing if you can update some of the drivers(personally when I hit them c++ books(c) I would modify), screen configurations if possible like faux, but I do not think HTC allows developers to mess with the display driver, and possibly extfat4 partitioning.
Shryvone21 said:
Hmmm feature request...well fauxsound, row scheduler(others), I think this kernel can be throttled up to 1.5 or 1.8 ghz per core, but for battery saving, 1.5, maybe seeing if you can update some of the drivers(personally when I hit them c++ books(c) I would modify), screen configurations if possible like faux, but I do not think HTC allows developers to mess with the display driver, and possibly extfat4 partitioning.
Click to expand...
Click to collapse
As for the kernel level cpu oc at the moment its not possible. Every attempt has resulted in a non booting kernel. For now my development will be slow until i can get my hands on a laptop. Sorry guys. Ill update my kernel and rom in unison from here on out (usually) but its gonna be a while. Sorry again everyone. Thanks for the suggestions though I will get to do some tinkering this saturday and next saturday. Ill report back then.
New image uploaded!!! (It is in the downloads section) If you cant download it heres another link:
http://www.mediafire.com/download/5d1iwc4brvey8z0/boot100.img
@ anyone running this please post me the output of /sys/kernel/debug/msm_cpufreq
Where's the download link
Will this work for Boost Mobile?
Flashing this kernel gets rid of all Roaming related options from the phone, before I used to see the option to enable roaming, plus enable/disable roaming guards and enable roaming for domestic and internationally, all that is gone after flashing this kernel. Since I have a roaming agreement with Sprint and I travel alot, I can't do without the ability to roam, therefore I restored my /boot nandroid backup and that brought back all roaming related options.
Question: Why did the OP remove roaming from this kernel? Many people NEED this, Or is there something that I was supposed to do in order to bring it back?
Related
First of all, id like to thank Gokhanmoral and Simone for the support... Special mention to TotallydubbedHD and Studiominal for the great contribution and to all who tested and helped...
The idea was first toasted by Gokhanmoral via PM, that it has something to do with idle status and not with hot-plug issue. Then Simone201 also posted about this on "official sound quality thread" which leads me to test dif configurations and combos... Then i came up with this little Fix:
1. You have to be rooted of course...
2. Flash Siyah Kernel (Sorry for this, since i only tested it with Siyah 1.3.3b and 1.3.7b)
3. Download & Install exTweak by Darek.Xan from the Playstore (Free one will do)
4. Grant Superuser
5. Navigate through the CPU Tab and set the CPU idle mode to; IDLE ONLY
6. Reboot
It was first tested with Siyah kernel 1.3.3b and was confirmed by Studiominal thru his "sinewave" that there were no crackling found in the graph. It has also been confirmed that it also work with 1.3.7b... I cant comment on other kernel since the test was thoroughly done with Siyah...
Hope this help... ENJOY!!!
For more info and progress about this finding, please read thru the thread
http://forum.xda-developers.com/showthread.php?t=1633685&page=75
{
"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"
}
Evidence provided
It seems like something in IDLE + LPA, AFTR + LPA, AFTR only causes the audio codec to suffer from power shortage that leads to turning the codec on and off really fast.
And.. to clarify, I only changed the cpu idle mode to IDLE ONLY, and disabled all the audio options that come pre-enabled both to see whether the idle mode is the culprit and wait for the new Voodoo Sound.
Thanks for the graph Pal...
Thanks guys for sticking with this and finding the problem.
Now that the culprit has become more obvious(likely the DAC being not able to perform properly with that low current set by stock setting), we'll see more developers here digging down the kernel with power profiles
Changed the setting to see what the impact on battery life is, i am not sure what lpe and aftr does, so not sure what effect we will see. Probably someone with more insight could clear this up...
–—–—–—–—–—–—–—–—
tapatalked from Galaxy SIII
So far, its been good with mine... Good deepsleep... When playing music, stayed on 200Mhz according to CPUspy..
jaytana said:
Then i came up with this little Fix:
Click to expand...
Click to collapse
Russians found this fix in June)
http://translate.google.ru/translat...howtopic=343482&st=2140#entry13910007&act=url
Hope its been posted here earlier to save our time and effort testing every bit of it...
jaytana said:
Hope its been posted here earlier to save our time and effort testing every bit of it...
Click to expand...
Click to collapse
but this is not the solution, it is a crutch
more of a temporary fix...
Iv never come across this problem but I use player pro and have never tried using the stock player, also, I use it with the lock screen player on which keeps a partial wake lock, perhaps this is what stops me having the problem.
I know the phone is awake because my nfc works when screen is off and player is playing.
Sent from my GT-I9300 using Tapatalk 2
Does this only effect Siyah Kernel?
Cause if its across the board on all current kernel sources what would be the solution to any any other kernel besides Siyah and using exTweak? A Script?
Also, I get choppy audio on almost all games and the same clicks on other audio related apps, could this be the same issue? This behavior almost sounds like latency problems of a low default audio pre-buffer...
JF-GINO said:
Also, I get choppy audio on almost all games and the same clicks on other audio related apps, could this be the same issue? This behavior almost sounds like latency problems of a low default audio pre-buffer...
Click to expand...
Click to collapse
So do I! It comes and goes but it's frustrating
Sent from my GT-I9300 using xda app-developers app
Are u two overclocking your CPU probably? Please give more details on your system, noone can help u this way.
–—–—–—–—–—–—–—–—
tapatalked from Galaxy SIII
According to Andreilux
LPA causes the CPU to be clock-gated, meaning the clock to the CPU is cut-off. I imagine that when power resumes, or actually is cut, it either causes a drop or spike in the power supply which interferes with the DAC and amplifier. This is inherently a hardware problem; they could have prevented it if they had put adequate filters on the PMIC, or whatever is in-between them which causes the interference. LPA is idiotically power-efficient and turning it off can cause worse idle battery life, so turning it off it in my opinion not a very viable option. The only options to fix it are already available to everybody already through changing of the idle states. If there's something to be done on the DAC-level itself, I don't know. CPU noise is a pain in the ass and wide-spread (Think about on-board sound on computers) and sadly there's not much to do about it if it's badly designed.
Click to expand...
Click to collapse
thanks for this, finally i've found the solution
Hi, this FIX is featured on the Index of FIXES http://forum.xda-developers.com/showthread.php?t=1674286
Any observation please send me a PM
Thanks...
I have been using, CM9 20120708-NIGHTLY with Ninphetamin3-1.1.1-test + Awesome Beats v3 (just beats boost active). No Crackling/Clicking Issue while listening to music with Apollo player.
I dont OC nor UV.
has someone undervolted is his atrix hd if yes then how and what were the rom and kernel settings kindly please help me
mega_man said:
has someone undervolted is his atrix hd if yes then how and what were the rom and kernel settings kindly please help me
Click to expand...
Click to collapse
You're lucky I remembered I uploaded my screenshots to G+ with my voltage table
{
"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"
}
See where it starts going down in 25mV intervals, do that all the way to the bottom (the app there is Kernel Tuner). The top two frequencies can be dropped by 25, but from there and any lower on the top two and you'll get an undervolt forced reboot. Some of the low end freqs might be able to go a bit lower than what my scale gives, you'll just have to test yourself since every phone is different in the undervolt department. And do not set it to activate on boot until you've pushed your phone a bit and know those voltages work. It is possible to undervolt brick a phone forcing you to do a factory reset to remove the saved undervolt values (or a full rom install if you save bad undervolt settings in an init.d script).
skeevydude said:
You're lucky I remembered I uploaded my screenshots to G+ with my voltage table
See where it starts going down in 25mV intervals, do that all the way to the bottom (the app there is Kernel Tuner). The top two frequencies can be dropped by 25, but from there and any lower on the top two and you'll get an undervolt forced reboot. Some of the low end freqs might be able to go a bit lower than what my scale gives, you'll just have to test yourself since every phone is different in the undervolt department. And do not set it to activate on boot until you've pushed your phone a bit and know those voltages work. It is possible to undervolt brick a phone forcing you to do a factory reset to remove the saved undervolt values (or a full rom install if you save bad undervolt settings in an init.d script).
Click to expand...
Click to collapse
so are these values arlready lowered or are these stock values ? and which rom were these settings made ?
mega_man said:
so are these values arlready lowered or are these stock values ? and which rom were these settings made ?
Click to expand...
Click to collapse
Rom shouldn't be an issue, this a kernel feature to undervolt cpu.
mega_man said:
so are these values arlready lowered or are these stock values ? and which rom were these settings made ?
Click to expand...
Click to collapse
Guessing at the rom....probably PAC 4.4, but like Techno said, that really doesn't matter. And those are lowered.
skeevydude said:
You're lucky I remembered I uploaded my screenshots to G+ with my voltage table
See where it starts going down in 25mV intervals, do that all the way to the bottom (the app there is Kernel Tuner). The top two frequencies can be dropped by 25, but from there and any lower on the top two and you'll get an undervolt forced reboot. Some of the low end freqs might be able to go a bit lower than what my scale gives, you'll just have to test yourself since every phone is different in the undervolt department. And do not set it to activate on boot until you've pushed your phone a bit and know those voltages work. It is possible to undervolt brick a phone forcing you to do a factory reset to remove the saved undervolt values (or a full rom install if you save bad undervolt settings in an init.d script).
Click to expand...
Click to collapse
Thanks, mate! It was trial and error, wasn't it? Is it too noticeable the battery save?
mauchito said:
Thanks, mate! It was trial and error, wasn't it? Is it too noticeable the battery save?
Click to expand...
Click to collapse
It doesn't make a big difference for me, but you should just try and see it yourself.
Hey guys and gals,
I've been searching AHD forums for a while now and I could find zip zero result on custom kernels even though I'm sure that I've read people write about Aaargh kernel before... [his user name's spelling ain't really helping either....]
So here I ask: where can I find it (or other custom kernels?), read what people have to say about it and what results are to be expected?
Lastly, what are you guys settings? I mean what voltages are you guys using? I understand that no phone/cpu reacts the same to undervolting, but I'd like to get an idea on how low I could expect to go...
I'm not really after overclocking as I find my AHD's performances acceptable at stock values; I'm just after better battery performance really.
Thanks in advance for your replies; I will be offline for the next few days, but will sure give thanks hits upon my return.
Cheers
/AL
[] AL [] said:
Hey guys and gals,
I've been searching AHD forums for a while now and I could find zip zero result on custom kernels even though I'm sure that I've read people write about Aaargh kernel before... [his user name's spelling ain't really helping either....]
So here I ask: where can I find it (or other custom kernels?), read what people have to say about it and what results are to be expected?
Lastly, what are you guys settings? I mean what voltages are you guys using? I understand that no phone/cpu reacts the same to undervolting, but I'd like to get an idea on how low I could expect to go...
I'm not really after overclocking as I find my AHD's performances acceptable at stock values; I'm just after better battery performance really.
Thanks in advance for your replies; I will be offline for the next few days, but will sure give thanks hits upon my return.
Cheers
/AL
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1893050
Ok thanks for the link.
I wasn't searching at the right place and on the wrong device forum...
So in an attempt to make this thread useful, I'd ask again: anybody wants to share their experience with that kernel on AHD?
I mean other than getting a phone that can basically now running up to 2GHz and down to 96 MHz, what did you get from it?
- How (and how much) undervolting did you do?;
- Any noticeable and verifiable battery saving doing so?;
- Any before/after benchmark results to share?
- any observations, bugs or just general opinion on the subject?
Personally, I've noticed once or twice that the phone had a hard time waking up when I used 144MHz (forgot the exact value) as min cpu frequency (no undervolting). The screen would not turn on with either volume rocker or power button...it only did after a lot of insisting... And that was just within a couple hours of testing.
I've since reverted to CM11 kernel since I was eager to find out if a semi-dirty (no stock rom reflashing first) nand backup restore would switch the kernel back. And it did, but then I've also re-installed CM11-M8 for other reason/issues... (that too brought back CM kernel - at least that's what the "about phone" is giving).
Anyhow, the debate is open on the usefulness of that custom kernel. If no one dare to pitch in here, I'll just ask a moderator to delete the thread...
But I'm still eager to find out about how to undervolt as I always did on my Defy.
Cheers
/A
I'm also curious about any battery-saving benefits that can be gained with Kernel adjustments; especially when screen is on (since I drive a lot with the screen on all the time). I have no interest in Overclocking, and would rather have the phone last as long as possible and still be useable.
Currently using arrrghhh's kernel (May 23 version) with:
1. Min 384000 (default)
2. Max 1458000
3. Scheduler: deadline
4. Governor: smartassV2
5. App: Trickster MOD
Also, the only way I've been successful in changing anything is by using the Trickster MOD app. Between CarbonROM and the CM11 (epinter) that I'm using now, I've never been able to get the kernel changes to stick. Didn't matter whether I used the default kernel or arrrghhh's, any modifications in my settings always reverted back at some later time.
Trickster MOD uses some workarounds to get it to stay, and I haven't had any issues since.
quasihellfish said:
I'm also curious about any battery-saving benefits that can be gained with Kernel adjustments; especially when screen is on (since I drive a lot with the screen on all the time). I have no interest in Overclocking, and would rather have the phone last as long as possible and still be useable.
Currently using arrrghhh's kernel (May 23 version) with:
1. Min 384000 (default)
2. Max 1458000
3. Scheduler: deadline
4. Governor: smartassV2
5. App: Trickster MOD
Also, the only way I've been successful in changing anything is by using the Trickster MOD app. Between CarbonROM and the CM11 (epinter) that I'm using now, I've never been able to get the kernel changes to stick. Didn't matter whether I used the default kernel or arrrghhh's, any modifications in my settings always reverted back at some later time.
Trickster MOD uses some workarounds to get it to stay, and I haven't had any issues since.
Click to expand...
Click to collapse
do you mean may 25?
{
"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"
}
sliker90 said:
do you mean may 25?
Click to expand...
Click to collapse
No. "CLICK TO SHOW CONTENT", then download the latest version (May 23) that doesn't use SaberMod. Only reason I was using that was because arrrghhh mentioned that SaberMod thing was experimental and may have issues. So I just chose the safe option.
ok thank you
sliker90 said:
ok thank you
Click to expand...
Click to collapse
Since you're a new xda member, I'll remind you that there is a button specially made to thank people... Look at the bottom left of the post useful to you...
As far as the undervolting goes, I found that the free app called "Trickster Mod" can do voltage changes. So I've done a bit more testing with the May 23rd anykernel and my results weren't that great....
First, I went too aggressively and try to lower the voltage by 150mV for every cpu frequency and that made the phone reboot as soon I applied it. I mention this because the lesson here is to
*** NEVER SET THE "apply settings on boot" OPTION UNTIL YOU ARE ABSOLUTELY SURE THAT YOUR NUMBERS WORK FINE. ***
Not doing so might make your phone unbootable and you might not even be able to boot to recovery/bootloader mode to revert kernel/settings....
Ok, that being said and since I'm after battery saving while the phone is in use*, I then went ahead and lowered by a more reasonable 50mV for each frequency (the app let's us move by 25mV steps). That 'worked' fine and I've experienced no sudden reboot. BUT, after some time (30 minutes), I've noticed some slowdowns and I've also had issues with an app that stopped creating video thumbnails. So all in all, that called for the end of my testing and I restore my CM11-M8 nandroid as I'm not going to live with such drawbacks for some slight (still yet to be proven) battery improvements.
So no custom kernel for me afterall.
.... Should this thread be deleted???
You guys tell me.
Cheers
/AL
- - -
*: hence I see no point of lowering the minimum cpu frequency: my phone does not take excessive power when on iddle, it deepsleeps fine and I use airplane mode at night..
*': some have argued that increasing the max cpu frequency allows the phone to complete tasks faster and return to a low power state sooner resulting in a lower overall battery use. I have my doubts on this and I'm pretty sure that it depends on what kind of task the phone is mainly doing. Anyhow, this is not something worth testing at this time... My AHD does its job just fine at the stock max cpu f.
ElementalX Kernel
for OnePlus 6
{
"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"
}
ElementalX is designed for maximum stability.
It is made for people who depend on their phone every day.
Features
Wake Gestures support (sweep2wake & doubletap2wake)
Sweep2sleep
Sound control (headphones, earpiece and mic)
Backlight min setting
Adjust or disable vibration
Advanced Color Control and K-Lapse
Option to disable gesture vibration
LED settings
Block wakelocks
FIOPS, CFQ, deadline, noop, maple and SIO i/o schedulers
NTFS r/w, CIFS and NFS support
WireGuard support
Option to disable fsync
Performance and power optimizations
Pass SafetyNet (with Magisk)
Installation
1. Flash in TWRP recovery or flash directly in EX Kernel Manager
Notes
Stay up to date with EX Kernel Manager. The latest security updates are always available through the app, usually within hours of the latest OTA. EXKM can be used to configure settings, backup and flash zips and img files, run scripts and install kernel updates quickly and easily. EXKM is compatible with all devices and kernels and is the best and most complete kernel manager available.
You can also use High Brightness Mode so you can see your phone in the sun. This app unlocks the hidden hardware setting that makes your screen much brighter than stock. HBM requires root.
Downloads
OxygenOS/Stock-based ROMs(Android 10)
ElementalX-OP6-4.00
OxygenOS/Stock-based ROMs(Android 9)
ElementalX-OP6-3.18
OxygenOS/Stock-based ROMs(Android 8.1.0)
ElementalX-OP6-1.15
Source code
Github
XDA:DevDB Information
ElementalX-OP6, Kernel for the OnePlus 6
Contributors
flar2
Source Code: https://github.com/flar2/OnePlus6
Kernel Special Features:
Version Information
Status: Stable
Created 2018-06-03
Last Updated 2020-05-01
Reserved
I've been experimenting with dynamic stune boost from @joshuous with good results. Seems to be some improvement in battery. If you want to try it, I've put all the necessary settings into one place in the latest version of EX Kernel Manager (version 3.56 and later).
Go to the CPU screen and select "Boost Settings" to open the Boost Settings screen
-Disable MSM Touchboost
-Change Dynamic stune boost to 15 (or somewhere between 10 and 20)
-Set all Input boost frequencies to 0 MHz (i.e. disabled)
-Change Input boost milliseconds to 1500 (might be unecessary, feel free to experiment)
Latest EX Kernel Manager: https://play.google.com/store/apps/d...xkernelmanager
Reserved
Great to see you here bro
Woot! You're here! I was holding out hope but had no idea if you were going to bother with this phone.
Finally! Good to see you here.
What about KCAL?
Ronak Chandak said:
Finally! Good to see you here.
What about KCAL?
Click to expand...
Click to collapse
The video driver is completely different on this phone, I will study it.
iElvis said:
Woot! You're here! I was holding out hope but had no idea if you were going to bother with this phone.
Click to expand...
Click to collapse
Wow, great to see you here
Im in love
flar2 said:
Wow, great to see you here
Click to expand...
Click to collapse
I stuck with my M9 for longer than usual but it finally died of some random power fault like my other HTC phones. I'm done with HTC, which leaves OP or Pixel if I want to keep modding.
Now we got a kernel! :good:
iElvis said:
I stuck with my M9 for longer than usual but it finally died of some random power fault like my other HTC phones. I'm done with HTC, which leaves OP or Pixel if I want to keep modding.
Click to expand...
Click to collapse
I can't believe you stuck with the m9 that long. I still like HTC, but I'm not getting the U12+ this year. There are a lot more users on the OnePlus and Pixel forums these days.
I've just updated EX Kernel Manager to support the OnePlus 6. EXKM version 3.51 adds speaker, headphone, earpiece and mice gain adjustments, HBM, CPU frequency adjustment and kernel downloads for this phone
https://play.google.com/store/apps/details?id=flar2.exkernelmanager
And, I also updated High Brightness Mode to support the OnePlus 6. This phone does not automatically use high brightness mode, it's now a hidden hardware setting. I've updated High Brightness Mode app to support the OnePlus 6. You will need root to unlock brightness about 10% higher than the max stock setting. You can use this app to enable HBM automatically in the sun, using a widget or with quick settings.
https://play.google.com/store/apps/details?id=flar2.hbmwidget
Great to see you here!
How do i know if it installed, because my kernel says 4.9.65 [email protected] Shouldn't say elementalX in it somewhere?
JazzieBoi said:
How do i know if it installed, because my kernel says 4.9.65 [email protected] Shouldn't say elementalX in it somewhere?
Click to expand...
Click to collapse
If you installed it, it would say ElementalX-1.00
Good to see you here man!
Finally the great kernel Dev is here, won't regret buying OnePlus 6 was about to exchange for pixel 2 Xl. But now OnePlus 6 will rock
Oh yes ! He's here ? Thank's !
I switched from a Nexus 5X, where I always ran ElementalX kernel on with any ROM. Glad to run that legacy in this device also.
Welcome to op6!
Has anyone been able to figure this out?
What does this app do to "boost" performance?
Use a lot of cpu cycles, heat up the phone... that's about it.
Useful for burn in when you first get the phone, you know help get the cpu heatsink properly seated
My stock 10+ OS load is over a year old, still fast and stable without using that app.
SD Maid, using the old Device Care cleaner (firewall blocked) and clearing the system cache occasionally is all I do.
It seems that it may be compiling the app for your target device.
This might shed some light...TL;DR of TL;DR: not much if you're patient, the OS would do the same things in a few days.
“Magic Trick” of Galaxy App Booster
I happened to try an app called Galaxy App Booster that is a part of Galaxy Labs released by Samsung. It claims that it can optimize all apps on device and boost the overall performance by 5% to 15%…
itnext.io
nixnixnixnix4 said:
It seems that it may be compiling the app for your target device.
Click to expand...
Click to collapse
Ipse_Tase said:
This might shed some light...TL;DR of TL;DR: not much if you're patient, the OS would do the same things in a few days.
“Magic Trick” of Galaxy App Booster
I happened to try an app called Galaxy App Booster that is a part of Galaxy Labs released by Samsung. It claims that it can optimize all apps on device and boost the overall performance by 5% to 15%…
itnext.io
Click to expand...
Click to collapse
Interesting. Perhaps mine was already optimized although I ran it the first or second day after reloading.
On my 10+/Pie I didn't notice any difference the couple times after I ran it.
It's usefulness seems limited to being a hand warmer in the winter.
I have also noticed that turning on any power management tends to create issues and not help battery life. Problem apps are best addressed directly. About all I do otherwise is close apps when done with them.
In the end Android Pie on this device manages its self very well (after heavy reconfiguration).
My current OS load has seen heavy usage but doesn't show it... I'm impressed to the point where a reload seems like it be a waste of time even after over a year.
Snake oil?
It actually runs the shell command in the picture below to compile the apps in speed-profile mode.
{
"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"
}
You can also manually compile the apps you need via adb:
adb shell cmd package compile -m <MODE> -f <PACKAGE>
In fact, I think that using the speed mode will have better performance than the speed-profile mode, but it will take up more storage space.
More about the compile mode, see:
https://source.android.com/devices/tech/dalvik/configure#compilation_options
https://source.android.com/devices/tech/dalvik/jit-compiler#force-compilation-of-a-specific-package
@functionxxx What does the "repair apps" option in the recovery do? I thought these were one and the same
0rigin said:
@functionxxx What does the "repair apps" option in the recovery do? I thought these were one and the same
Click to expand...
Click to collapse
I guess it should be similar to the Clear dalvik-cache option in the previous version of recovery, which will "undo" the optimization of all apps so that the apps can be re-optimized after reboot, just like a FOTA did.