I just read this over on phonearena and wondered if anyone else saw it and has tried it.
http://www.phonearena.com/news/How-...-visibility-of-the-LG-G3-without-root_id58888
Im tempted to try it but hesitant too.
It'll increase the overall performance of the phone, at the cost of a little bit battery life, since turning off thermal mitigation allows the cpu to clock at a higher speed more often while ignoring the heat.
I cant decide if its worth it. For the most part I dont have any complaints about the brightness but I also use Lux.
While it was a different phone I did this same thing with my LG G Pro with no adverse effects to the phones operation in just over a year. It is still going strong in fact, so I dont fear phone damage by doing this but on this phone I havent seen the need for it yet.
I've been using this setting for some time now. I see no decrease in battery life, indeed I've seen nothing negative from it.
Sent from my LG-D850 using Tapatalk 2
I've had both thermal settings off for a while now as well, it only powered down from heat once and that was because I was chrome casting Netflix and playing a intensive 3d game. Other than that it's fine, however I would expect it to get hot doing 2 large processes anyway. Battery life is still 4-5hiues SOT
By doing this my phone over heats and the turns itself off. Was running fine for a while with it on but I guess it was to much for the phone to handle.
Hi Guys I see that no device can do 60fps butter smooth all the time, there's always a dropped frame stutter or lag, even on a nexus 6 or whatever new device comes along, doesn't matter how powerful it is, even at max clock speed the thing just drops a frame or something anywhere. Like no company has ever come up with a perfect device until now, even iOS which is always "smooth" drops frame in the UI from time to time. If you explicitly tell an app to lock the UI at 60fps it will always drop somewhere in between. Why is that?
tichs said:
Hi Guys I see that no device can do 60fps butter smooth all the time, there's always a dropped frame stutter or lag, even on a nexus 6 or whatever new device comes along, doesn't matter how powerful it is, even at max clock speed the thing just drops a frame or something anywhere. Like no company has ever come up with a perfect device until now, even iOS which is always "smooth" drops frame in the UI from time to time. If you explicitly tell an app to lock the UI at 60fps it will always drop somewhere in between. Why is that?
Click to expand...
Click to collapse
1. CPU getting hot
2. Bad OS
3. Bad apps
4. Bad flash memory
5. Bad RAM management
6. RAM getting low
7. GPU throttle
8. You've think your phone like a computer
This thread is intended to have power users post their best configurations so as to guide the rookies in optimizing their MXPs once they get unlocked and rooted. It's also intended to compare the best setups for battery, performance, gaming, multitasking, etc.
My main interest is in battery life, although lately I've been on the XDA Labs app like crazy and it's hurting my drain.
Constructive criticism welcome on how to improve the below records!
ROM: Stock MM Canadian
Kernel: Ultra Kernel R3
Governor: Smartmax
Frequencies: 200 big, 800 little
Xposed Framework modules: Force Fast Scroll, Lucky Patcher, GravityBox (duh!), Use USB For Marshmallow, Xposed GEL Settings
Best SOT: 8 hours
Best Drain (100% to 0%): 120 hours
Other miscellaneous tweaks: Shake Flashlight as a system app instead of double-chop (works great, just don't let go)
Launcher: Still figuring that out...but Nova and DarkLauncher are worthy contenders right at the moment
Voice Assist/Google Now on long-press Home: Disabled thanks to @pijes. Settings > Apps > Gear icon > Default Apps > Voice and Assist > None
Post below, power users! What's your best setup so far?
Bro, I would like you use Greenify and DS Battery saver
As you have xposed framework installed you can use boost mode in greenify and also
DS Battery saver also has a module so activate them and then choose slumberer and phew see your battery stats
Coming to launcher, right now Arrow launcher is good and smooth and I prefer that
Thank you!
ashwath230 said:
Bro, I would like you use Greenify and DS Battery saver
As you have xposed framework installed you can use boost mode in greenify and also
DS Battery saver also has a module so activate them and then choose slumberer and phew see your battery stats
Coming to launcher, right now Arrow launcher is good and smooth and I prefer that
Thank you!
Click to expand...
Click to collapse
Cool man thanks. I'll try the Greenify and DS you recommend. I've seen Greenify a lot around XDA. I'm excited to try it.
Tesla rom(seems faster/smoother then stock/anyother rom) plus Squid kernel. Governor is set to Lionfish and I/O scheduler is set to Row with 512kb readahead. Minimum frequency for the Big cluster is 800mhz and 499mhz for the little cluster. NFC and location disabled. Best battery life I ever got was with stock with the same kernel/settings configuration, had 9 hrs SOT and nearly 24 hrs overall.
xtremeed2705 said:
Tesla rom(seems faster/smoother then stock/anyother rom) plus Squid kernel. Governor is set to Lionfish and I/O scheduler is set to Row with 512kb readahead. Minimum frequency for the Big cluster is 800mhz and 499mhz for the little cluster. NFC and location disabled. Best battery life I ever got was with stock with the same kernel/settings configuration, had 9 hrs SOT and nearly 24 hrs overall.
Click to expand...
Click to collapse
What do you mean nearly 24 hours overall - how long before you had to recharge?
I need to learn more about I/O scheduling. I've changed to Row and 512 as you recommend but where will I see the difference? When I connect to my PC? When apps access internal storage?
I've changed my governor back to lionfish. Smartmax wasn't doing it for me. 200 big 800 little. I'll look into that Tesla ROM too.
I was hoping this thread was gonna be more popular. I hope some people have gotten use out of it so far! Grow little thread, grow!
It would be awesome to see more growth in this thread! It would enable prospective buyers to talk to current owners, and figure out what they might want before they sink money into the device!
*cough*cough*
Which is exactly what I was hoping to do! Does anyone know if sweep to wake/sleep is possible with the Moto X Play? It's honestly one of the most useful features I've ever seen from rooting et al.
I'll post my setup. Been using it this way for like 2 weeks so I feel it's stable.
I'm currently running this:
Unlocked BL obviously
Stock Canada firmware (MPD24.65-18)
Rooted
Xposed Framework installed
Squid Kernel r14b
I have gravity box installed and that's really it as far as tweaks and stuff.
Averaging 5 or 6 hours SOT down to about 25% or 30%. Really depends on what I do and what network I use. Performance is great too.
I'm gonna mess around with some of this stuff tonight and see what I can do with it.
Sent from my XT1563 using Tapatalk
I'm trying the interactive governor in Squids kernel, some of the stuttering issues have disappeared. Like when I clear all recents in the task switcher screen or scrolling big web pages.
Sent from my XT1563 using Tapatalk
Marshmalux. Rooted. Xposed. Greenify. Powernap. Amplify.
Getting sot around 5.5 hours for my usage. Happy with that squid kernel latest r15. Lionfish on both cores
Sent from my XT1563 using Tapatalk
JohnHorus said:
It would be awesome to see more growth in this thread! It would enable prospective buyers to talk to current owners, and figure out what they might want before they sink money into the device!
*cough*cough*
Which is exactly what I was hoping to do! Does anyone know if sweep to wake/sleep is possible with the Moto X Play? It's honestly one of the most useful features I've ever seen from rooting et al.
Click to expand...
Click to collapse
Hey hey. Thanks for posting!
I'm sure sweep to wake is possible on the phone in some way, likely through a combination of rooting and Xposed modules. I know that GravityBox has a double tap on status bar to sleep feature.
One of the nicest features of the X Play is the Moto Display. It's nice to have the phone screen come.on showing notifications without fully waking the phone. Check out the Moto Display app on the Play Store. It's a totally sexy feature.
I'd say this phone is absolutely worth it for the battery alone. I personally feel the camera to be laggy especially with focus, so consider that if you're a shutterbug. I am very hopeful that software updates will being out the power of the camera but it doesn't have optical image stabilization so blir happens more frequently, at least for me. That could be my shake fingers though.
Feel free to ask any further questions!
brian10161 said:
I'm trying the interactive governor in Squids kernel, some of the stuttering issues have disappeared. Like when I clear all recents in the task switcher screen or scrolling big web pages.
Sent from my XT1563 using Tapatalk
Click to expand...
Click to collapse
Good stuff. Interactive does appear to handle web pages better. I did a Wikipedia search for The Simpsons and got a huge page. I flicked down to scroll it all at once and then Chrome froze. Hahahaba. Same with Lionfish though. Maybe I'm getting greedy thinking this phone is as powerful as my PC.
Lionfish was giving me great SOT results. Like I mentored in the OP: 8 HOURS! Was so happy to see that. Blew the socks off my Nrxus 4. I average between 6.5 and 8 usually, but WhatsApp and XDA Labs are hurting those scores now.
I haven't had to Greenify any apps yet - I only hsvr geeky ones installed anyway so they never keep the phone awake.
Gopinath15 said:
Marshmalux. Rooted. Xposed. Greenify. Powernap. Amplify.
Getting sot around 5.5 hours for my usage. Happy with that squid kernel latest r15. Lionfish on both cores
Sent from my XT1563 using Tapatalk
Click to expand...
Click to collapse
I think @squid2 deserves a lot of credit for extending the X Play even further. His kernel and work on TWRP make the X Play even more attractive than it is out of the box.
I prefer Ultra kernel personally because I believe the dev for that (@technoander) takes the latest releases of squid's and adds features to them. I may be mistaken but that's my impression. I'll try to clarify and report back. I should do a direct comparison of Ultra and squid's latest to be as objective as is possible with a subjective test. Hahaha.
I guess I should specify a bit further - sweep/tap2wake is really only effectively useful when the phone supports some kind of low-power state for the touchscreen, otherwise the screen has to remain on in order to use it.
I'm sure sweep2sleep would be possible, but if there's no low-power state for the screen, it wouldn't really matter for me in the end. Moto display sounds like exactly what I'm talking about, though I don't know if it includes any low power mode for the touch features, as well as the display.
I'm gonna look into this a bit more, and see if I can dig up any info. It would be a hardware feature, designed-in, so it definitely should be discoverable. I figure if I can find out all the information for one of the people who have written kernels for the phone, they shouldn't have a problem emulating the feature. It's popular enough, and with the low-power state, shouldn't be too complex to implement.
JohnHorus said:
I guess I should specify a bit further - sweep/tap2wake is really only effectively useful when the phone supports some kind of low-power state for the touchscreen, otherwise the screen has to remain on in order to use it.
I'm sure sweep2sleep would be possible, but if there's no low-power state for the screen, it wouldn't really matter for me in the end. Moto display sounds like exactly what I'm talking about, though I don't know if it includes any low power mode for the touch features, as well as the display.
I'm gonna look into this a bit more, and see if I can dig up any info. It would be a hardware feature, designed-in, so it definitely should be discoverable. I figure if I can find out all the information for one of the people who have written kernels for the phone, they shouldn't have a problem emulating the feature. It's popular enough, and with the low-power state, shouldn't be too complex to implement.
Click to expand...
Click to collapse
Cool - definitely report back - it would be nice to know if this is embedded in the hardware somewhere. I hope it is, unlike optical.image stabilization. Damn!
XxMikeMasterxX said:
What do you mean nearly 24 hours overall - how long before you had to recharge?
I need to learn more about I/O scheduling. I've changed to Row and 512 as you recommend but where will I see the difference? When I connect to my PC? When apps access internal storage?
I've changed my governor back to lionfish. Smartmax wasn't doing it for me. 200 big 800 little. I'll look into that Tesla ROM too.
I was hoping this thread was gonna be more popular. I hope some people have gotten use out of it so far! Grow little thread, grow!
Click to expand...
Click to collapse
Yes nearly 24 hrs before I had to recharge. As for Row you should notice it with both situations. I use it because of other phones I had before people were saying it was one of the better I/O schedulers.
Actually I have a picture of when I got it. Was nearly 23 hrs not 24 but still.
Hey developer,the banking apps I have does run after flashing a custom rom.Is there any workaround for this?.have to reflash stock after trying any custom rom.Its a pain in the as*.
xtremeed2705 said:
Yes nearly 24 hrs before I had to recharge. As for Row you should notice it with both situations. I use it because of other phones I had before people were saying it was one of the better I/O schedulers.
Actually I have a picture of when I got it. Was nearly 23 hrs not 24 but still.
Click to expand...
Click to collapse
Row is essentially the best scheduler. Benchmarking is weird, because by design it's an optimized test case and not a use case. Use cases will always be variable, but generally with a smartphone writes aren't too latency-sensitive. That's why Read Over Write generally works the best once your phone is settled, because reading is most of what it does. Doesn't write too often.
There are lots of custom governors, not so many custom schedulers, and lots of suggestions, but generally stock *IS* best, and if you don't understand it, you should not change it. Governors are fun to play with but even they can cause issues if poorly coded. Changing governors will give you a huge impact on battery, but also a relative impact on performance. It all depends on the use context. You'll rarely get much battery life without a performance hit unless you custom-tune settings for your own use context.
As for read-ahead, that value is iconic of exactly what I'm talking about. It is the "chunks" of data that your OS reads in one go. So if it needs 2k, or 2m, it reads a different number of chunks, but each chunk will be the size set by I/O read-ahead. Google likes 512 best. I've been told by the dev for the EX Kernel that internal Motorola devs like 128 best. Benchmarks like the biggest value possible, because they present the OS a massive pile of data and ask it to read it all as fast as possible. In that context, a large chunk size saves time. In most contexts, you read more than you need half the time. So a low value like 128 saves battery and memory.
---------- Post added at 09:10 AM ---------- Previous post was at 09:08 AM ----------
kiran91 said:
Hey developer,the banking apps I have does run after flashing a custom rom.Is there any workaround for this?.have to reflash stock after trying any custom rom.Its a pain in the as*.
Click to expand...
Click to collapse
Android pay does this too, it's a "security" feature built-in by the devs to stop hacking. Not really necessary, but then neither are smartphones, so you take what you can get I guess. No ROM developer can work around this for you. The app is detecting any modification whatsoever. Even root may cause it.
xtremeed2705 said:
Yes nearly 24 hrs before I had to recharge. As for Row you should notice it with both situations. I use it because of other phones I had before people were saying it was one of the better I/O schedulers.
Actually I have a picture of when I got it. Was nearly 23 hrs not 24 but still.
Click to expand...
Click to collapse
Badass dude. 9 hours SOT is wicked.
I'm finding the phone app drains the battery like crazy. Is this to be expected?
Hey @JohnHorus - thanks for your informative post. I'm currently trying Row 128 and will report back but I doubt I'll see any real-world difference in use. Memory and battery are two soft spots for me so I'm hopeful 128 will maintain solid performance.
Looking forward to reading about others' setups!
XxMikeMasterxX said:
Badass dude. 9 hours SOT is wicked.
I'm finding the phone app drains the battery like crazy. Is this to be expected?
Click to expand...
Click to collapse
Yeah in my experience it drains the battery more then doing other things for some reason. As you can see in my 9 hrs picture I only used the phone for like 2 minutes lol.
### Shield app optimization tutorial
Shield app optimization = BS!
Just tested the Shield **app optimization** with the benchmark 3Dmark and I can tell you no matter the setting the performance is bad. Universally bad!!
### My advice:
forget about the Shield **app optimization**. Turn it off. Never look back.
Instead, manage the apps/tablet performance with the **Processor Mode** under Shield Power Control.
For gaming **Optimized** or **Max** are great. For anything else My **Power Mode** 2 CPU cores are just fine; it safes some battery power.
How to safe more battery: deactivate **Adaptive brightness** under Display. Because no matter the ambient lighting, it's always too bright. Hence, better set it manually.
You're on point mate.. I just tried testing my K1 with the setting off and it seems to have worked beautifully. Before it'd stutter in apps and in between, now after trying this for more than a few hours I've had almost no stutters or lag AFAIK.
You should be on top. Kudos for the tip mate ?
@RJ*n, thank you.
You know, I couldn't find any explanation of what the difference between **Optimized** and **Max** are, and I assumed **app optimization** is the very same thing just apps specific, so began benchmark testing it all. To my surprise **app optimization** does no good but just slows everything down; no matter the settings! I was sure not everybody knowns about that. And instead just complains about bad performance or quick battery drain.
Conclusion: the difference between **Optimized** and **Max** are marginal. **Max** may give you a few more fps whereas **Optimized** scores a tiny bit higher in the overall performance.
By the by, I played Asphalt 8 with only 2 cores and it still runs absolutely smooth.
I agree, this should be a sticky.
Hello XDA community,
As I am sure a few of you have experienced, the Razer Phone will drop the maximum device brightness substantially as a result of even a moderate system temperature increase. For me, this occurs consistently after I am running any GPU intensive game for more than 5-10 minutes (CSR 2, Black Desert Mobile etc.)
Is it possible to change or turn off this function in any way? The maximum NITS of the device is not impressive to begin with. Having the brightness potential effectively cut in half whenever I run Youtube in HD is rather ridiculous. I have read conflicting reports that some users brightness potential will 'default' after a period of lite use, but this is not the case with my device. I am forced to restart the device entirely to regain its original maximum brightness capability.
Does this community have any thoughts on a potential fix? Are there many other users out there experiencing this problem as well?
Yes same issue even when just watching video or YouTube. It drives me nuts. It's like brightness is turned down half way. It bloody awful and needs sorting. Would prefer the device to underclock rather than dim the screen. ?
**UPDATE** Possible fix for this issue.
Good morning XDA,
I have been spending some free moments working on a solution to this problem and I may have found it.
I recently rooted my device and installed Kernel Auditor to edit my build.prop....KA also allows the modification of pretty much any value you can think of--this includes the enable/disable of thermal profiles. When I toggled off ALL thermal profiles I no longer experienced the screen dimming phenomenon--the negative byproduct of course is that your phone will turn into a hot pocket. More testing to follow, but for those that are rooted I would appreciate it if you could try and replicate my results!
tl;dr -- Kernal Auditor > Thermal category > disable all 3 thermal profiles > no screen dimming/phone turns to lava.
No don't do it. Turning the throttling off completely will fry the main board and CPU / memory chips. Don't do it trust me I killed my last phone doing the same thing. It's the CPU that needs to throttle back not the screen brightness. Really don't understand why they would lower brightness rather than just throttle back the CPU.
arnookie said:
No don't do it. Turning the throttling off completely will fry the main board and CPU / memory chips. Don't do it trust me I killed my last phone doing the same thing. It's the CPU that needs to throttle back not the screen brightness. Really don't understand why they would lower brightness rather than just throttle back the CPU.
Click to expand...
Click to collapse
They do throttle the cpu but it takes enough heat.
The reasom the screen dimms is because of the heat pipe that is connected the back of the display. Disabling such mechanism might put the backlight LED to risk. But that seems less likely.
iliais347 said:
They do throttle the cpu but it takes enough heat.
The reasom the screen dimms is because of the heat pipe that is connected the back of the display. Disabling such mechanism might put the backlight LED to risk. But that seems less likely.
Click to expand...
Click to collapse
Do you have a source for that information? I have seen from tear-down videos that the heatpipe is indeed attached to the back of the lcd panel, but I have not found any information on the specific mechanism of action that causes the thermal screen dimming.
Any information anyone can provide would be greatly appreciated.
-R
Rumaea.Timbre said:
Do you have a source for that information? I have seen from tear-down videos that the heatpipe is indeed attached to the back of the lcd panel, but I have not found any information on the specific mechanism of action that causes the thermal screen dimming.
Any information anyone can provide would be greatly appreciated.
-R
Click to expand...
Click to collapse
I do not have any source but i have seen other phones di the same thing due to heat. The LED might burn i guess but i do not see that likely.although that would such to have a half lit desplay.
The same thing happens to me!!
After 10 minutes of playing the screen looses a big amount of brightness!
I masst to restart the phone to make the screen to be at his full brightness!
This is annoying!! Is not like it is a cheap phone!
They should fixed this problem a while ago!
But they don't!!