Related
As we know, overclocking MSM is possible now. Just check :
http://forum.xda-developers.com/showthread.php?t=725290
Click to expand...
Click to collapse
But the thread is over 1400 post & most of them are about blackstone, Rhodium, etc.. I think it's about time we make a thread about overclocking our Touch Pro(s)
I use GSM unbranded TP100 & TAEL v.5 ROM.
I'll start with my experience :
What Works
Click to expand...
Click to collapse
1. grab the v.2 file from the thread above. (1st page)
2. Install it to phone Memory.
3. Open the Msm7kCpuSpeed & You can see the current CPU speed in Real Time.
4. Whatever speed you select when on Battery Power, it will revert back to 528Mhz because of the Windows component that make sure the clock speed is 528 Mhz every (xx) second.
5. The only way you can overclock is when u plug your USB to Laptop / Stock Charger. Only then you can move the slider to any speed supported by your device.
6. Every device's speed are varied from the ROM used & quality of the MSM in your device. Try what speed are the best speed in your phone before it locks up. I use TAEL v.5 & I can achieve 768 Mhz in AC (original Charger / USB in Laptop/PC) on 787 i get random lockup
7. If you unplug your Raph from USB / Charger on ANY freq other than 604.8 Mhz, your raph will LOCK UP. So, when unplugging / pressing power button make sure u change the freq to 604 Mhz first. (604 Mhz is special Freq that don't Lockup our device)
8. A couple of seconds after we unplug our Raph in 604 Mhz freq it will revert back to 528 Mhz freq.
What almost works
Click to expand...
Click to collapse
From the explanation above we can use Overclock in Our Raph, but only when plugged into a charger / laptop / PC.
In this
PHP:
http://forum.xda-developers.com/showthread.php?t=725290&page=120
thread Qzytor in post 1191 found a way to overclock our MSM devices when using battery power. But in my experience, it ALWAYS lockup a few seconds after opening the phone dialer, coreplayer (playing video for a few second the lockup), SMS messaging, and Teeter (lockup when level up)
I'll write my experince using above method :
The method is : (Credit goes to Qzytor)
Code:
Install NetRippers Msm7kCpuSpeed V.2 App. in your Device
Install SetCpuSpeed v1.0d on SD card. --get it @ http://forum.xda-developers.com/showpost.php?p=7426966&postcount=1000 --
Take SD card out and soft reset the phone.
Open registry.
Go to HKLM\Software\Msm7kCpuSpeed.
Edit the values as below:
BootTime = 90000 (This is important. This value gives enough time for the
phone to fully boot up. The phone has to fully boot up
before the OC kicks in)
CheckTime = 20 (Stable at 20, otherwise yoyos between base and OCed
cpu speed)
Command = 0
PerfomanceLevel = 35 (This speed is stable for me without SOD)
ScreenOffPerfomanceLevel = 27
SettlingTime = 10
Close Registry editor, insert SD card in the phone and soft reset the phone.
Once the phone has fully boot up, give it a minute before opening NetRippers Msm7kCpuSpeed and you should see your OCed cpu speed.
If your OC cpu speed isnt stable then take your SD card out,soft reset the phone and registry edit PerfomanceLevel to a lower value.
To restore back to phone default speed:
Open File Explorer.
Go to Windows\Startup folder and delete SetCpuSpeed.
Soft reset the phone and phone default speed will be restored.
Before deleting SetCpuSpeed from Windows\Startup folder , save it in Documents folder so if you want to overclock again, copy and paste it from Documents folder to Windows\Startup folder.
1. Performance Level 35 is overclocking @ 672 Mhz
2. Add 1 level means add 19.2 Mhz in clock speed
3. The best speed i reach in AC power (USB / Laptop) is 768 Mhz = performance level 40
4. I change my performance level into 40 & I can see in MSM7kCpuSpeed that i'm running 768 Mhz after 90 seconds from the bootup as written above.
5. a few programs can run ok in 768 Mhz or any speed in that matter, but most causes lockup. This does NOT happen in Blackstone / Rhodium
6. Even on performance level = 35 (672 Mhz) or even in Performance level = 27 i still got a lockup opening phone, SMS, coreplayer, teeter, & FPSECE (only when exiting). they work fine on AC power.
7. I dont know if it's because of my ROM (TAEL v.5) or if all RAPH experience the same Issue.
I hope we can continue to improve overclocking our RAPH to the point it can perfectly works ^^
Another OC program
There is also this Overclock Tool:
http://forum.xda-developers.com/showpost.php?p=7463284&postcount=162
I haven't tried it yet, but it should work with our Raphael, and also on battery power.
I'm using touchpro and newest energy cookie rom.
Tried the method mentioned by b0z0k. Set level 35 for the 1st trial
Apps tried list:
Youtube
Opera
text message
File explorer
excel mobile
google mpas
teeter
window media player (not the music tab in sense)
lockup when playing teeter and music (the sense one). However, for other programs, it was just working brilliantly.
Really hope my experience can help.
After turning it to level 35, the device looks quite stable but i haven't tried any levels upper than that.
zai_hkman said:
I'm using touchpro and newest energy cookie rom.
Tried the method mentioned by b0z0k. Set level 35 for the 1st trial
Apps tried list:
Youtube
Opera
text message
File explorer
excel mobile
google mpas
teeter
window media player (not the music tab in sense)
lockup when playing teeter and music (the sense one). However, for other programs, it was just working brilliantly.
Really hope my experience can help.
After turning it to level 35, the device looks quite stable but i haven't tried any levels upper than that.
Click to expand...
Click to collapse
Yes, i just tried Energy ROM 1-2 days & Overclock works like a charm. Don't hestitate to use higher freq.. i found out that the best stable freq in my device are @ 748.8. 787 will instantly freeze my TP, 768 works but many apps crashing, 748.8 works very well with FpseCE
What i did, is try the newest energy ROM (rel. 23673, GTX, dinik version) & it all work like a charm. Sure, i still got occasional SOD but it's waaaaaaayyyyyy better than having to OC in Laptiop USB only..
So i think the issue i had earlier is definitely with the ROM (I think TAEL rom has some kind of energy saving script that keeps telling the CPU what clock it's running -- even when setCPUspeed already installed)
After i change to Energy Rom rel. 23673, on battery power, MSM7kCPUspeed+setCPUspeed v1.0d runs just as smoothly as AC power. I get occasional SOD only when exiting Fpsece (it makes the CPu drop to 384 Mhz then it froze). Using WMP, TCPMP, & other apps that usually crashes on TAEL v5 did NOT give me the "freeze"
@ 748.8 Mhz FPSEce gives me 5-8 fps boost with no frameskip , with frameskip i can play Final Fantasy Tactics @ 50 fps with no noticable errors (about 29 fps in landscape no frame skip)
And that makes me...
--> very happy TP owner
p.s. a little trick when having a non OC applicable ROM is to use your GPS programs (garmin, sygic, etc), minimize them, & run MSM7kcpuspeed to OC your device. this usually works ok.. Just a very bad battery consumption
& dont forget to change back to 604 Mhz before shutting down your GPS program & then u can power off the screen -- or else u get the SOD.
An update on usage:
I've just flashed to the updated rom for energy(Aug18 Cookie 23678)
After that, I overclock the device by the previous method.
I found that the device freezes everytime when i receive calls. Therefore,I have to remove the setcpu.ink in the window to stop overclocking. Anyone has figured out why the device freezes on some program but behave normal for the most of the time?
zai_hkman said:
An update on usage:
I've just flashed to the updated rom for energy(Aug18 Cookie 23678)
After that, I overclock the device by the previous method.
I found that the device freezes everytime when i receive calls. Therefore,I have to remove the setcpu.ink in the window to stop overclocking. Anyone has figured out why the device freezes on some program but behave normal for the most of the time?
Click to expand...
Click to collapse
This is the biggest problem I have. Theres certain parts of the day while working that I use my phone a lot, and the SOD's with phone can cause me to miss calls or be unable to place a call (SOD while dialing).
Im still waiting for some sort of option to totally disable itself when a named program is run.
hartleyshc said:
This is the biggest problem I have. Theres certain parts of the day while working that I use my phone a lot, and the SOD's with phone can cause me to miss calls or be unable to place a call (SOD while dialing).
Im still waiting for some sort of option to totally disable itself when a named program is run.
Click to expand...
Click to collapse
Just about 2-3 days now i have SOD while dialing too.. I don't know what's causing it, but i can confirm that after a fresh ROM flash (energy build 23673) i CAN dial in my phone while overclocked @ 768 Mhz.. After a lot of install, trial, etc now i have SOD EVERYTIME i dial in phone dialer.
p.s. before SOD's occured i just set up my GPRS/3G connection for my carrier.. i wonder if this is the cause?
b0z0k said:
Just about 2-3 days now i have SOD while dialing too.. I don't know what's causing it, but i can confirm that after a fresh ROM flash (energy build 23673) i CAN dial in my phone while overclocked @ 768 Mhz.. After a lot of install, trial, etc now i have SOD EVERYTIME i dial in phone dialer.
p.s. before SOD's occured i just set up my GPRS/3G connection for my carrier.. i wonder if this is the cause?
Click to expand...
Click to collapse
Maybe.. I do the carrier auto-setup once i boot a new rom. (AT&T USA). It might be some settings in there messing with it.
The test I do to see if it freezes is this: Call my voicemail (google voice) and just keep hitting "7" a bunch of times and see if it freezes.
Ive also tried various phone canvases. Have tried the new one currently being cooked into NRG roms (aug 18th) before it was cooked in, will try again now to see if anything has changed.
edit: I have also been following and trying all versions of iwfratz's overclock tool, and compatibility actually seems to get worse with each new release. the original version would crash after a while at the stock 650, which on my TP its much more stable at 633. But with current versions (1.5) it crashes immediately after setting the overclock, a version or two ago it would run, but would still crash when using the phone app.
i use nrg rom 21914 and overclock with msm7kcpu speed +setup cpu 1.0d.
4 "bugs/[email protected],6Mhz":
-phone works great, untill i receve a call, than the phone hangs.
-also the phone hangs, when i will use nitrogen 1.1 to listen to music.
-and the phone hangs, when my alert goes on and i have the lockscreen activatet.
-when i receve a mms and downloaded it, the phone hangs also
after the hang, i need to put the batterie out of the tp to restart....
@ ~746 the phone starts but sense restarts again and again...but in the 6.august of nrg rom, i thought this speed works also ...
maybe someone know an answere.
I love the speed i wouldn't miss it...i already sold my Acer s200, because it is crap
New Method, No Freeze in Phone dialer, but battery more inefficient
New Method, No Freeze in Phone dialer, but battery more inefficient
I have tried SetCPUspeed v1.0d & it made the Overclock working BUT i dont know why every time I open dialer screen or an SMS came, it always freezes.
I think it has to do with the fact that WinMo in our TP consistantly checking the speed/ frequency of our MSM.
The only way we can bypass this :
1. When we connect to our laptop (activesync) -- when we connect Raph to PC & it starts sync-ing in activesync, the speed/ freq check disabled, this is an exploit that we can use to overclock safely. BUT..
We do need our laptop / PC to do this (we can't overclock when we're traveling & want to play FpseCE in full speed ^^)
2. THE NEW METHOD -- more battery draining though.. We can bypass the freq check using GPS module. When the GPS is ON, the speed check is disabled. This way, even when we're traveling, we can still Overclock our Raph safely (wont freeze when opening dialer / receivinf SMS.
But, it's still opening GPS module, it's a battery drainer. In my experience it's about 20% faster draining the battery. Use HTC GPS tool & choose "open port"
What i do is :
when the phone is not used (deep sleep), i don't use the Overclock. When i want to use something in my phone & i want to boost it's speed i will turn on HTC GPS tool & overclock my phone to 729,6 (the most stable for me). When i'm done & want to put my phone to sleep, i made my MSM7kCPUSpeed to 604 Mhz (safe speed, wont freeze) & i turn off the GPStool.
When i press the power button the freq will change to 528 Mhz again & the battery consumption became normal again. ^^
It's a turn around from the problem we're facing.. but Hey, i got to play Final Fantasy Tactics @ nearly full speed ^^
After a little testing, no freezes anymore.^^
However, if we disable the frequency check, we are not able to stablize the frequency.
What I mean is that sometimes after a call or running some programs, the frequency will drop to about 355 and I have to open MSM7kcpuspeed again to adjust the frequency.
Anyway, this is really a breakthough for overclocking out TP.
still got bugs
I love the increase of speed, when the device is overclocked.
But i got still bugs.
When i want to listen to music, it hangs after about 1-2 secounds. i don't know why.
Maybe you can help me with this problem, because i dont want to have only 527mhz.
my settings:
my BootTime = 90000
CheckTime = 20
Command = 0
PerfomanceLevel = 38
ScreenOffPerfomanceLevel = 27
SettlingTime = 10
best regards
i know it's an old thread, but is any new way public to overclock the touch pro?
atm i need to use it @ normal speed, because it is really buggy @ overclocked=/
Hi,
Have used since 1.0.20 NSCollab and no problems like this ..
Before with 1.0.23 setcpu runs fine with screenoff profile 100-200.
Now i upgrade to 1.0.31 and it freeze the phone after switch screen off.
Only battery pull bring it back to life.
All other profiles are fine.
Even an rising from the frequency to 200-200 change nothing.Only screen off profile disabling help.
Have noticed after switch screen then on (without screen off profile ..) an green taint over the GFX for a 1/10 second and then the gfx go normal ....
Regards
R-TEAM
Raise your screen-off Max.
Hi,
even by 100-400Mhz the phone freeze - and see no point to have screenoff seperate frequencys with nearly no advantage over the screen-on settings ...
BTW. in the past (NSCollab 1.0.23) screenoff with 100-200 works fine and get me good battery runtime ...
(if the screen off i dont care need the phone for an task 0,5sec or 1,5sec ...)
So anything musst happen with NSCollab (or CM7.1 ....) .....
Regards
R-TEAM
Then don't use NSCollab. I'm using it and it's perfectly fine. If for done reason you are having problems, switch to another ROM.
Sent from my NS running NSCollab 1.0.31 cuz I. STILL can't find my tin cans and string ....
Hi,
i am very fine with NSCollab.
Have before Axura ROM - but it is discontinued and so i switched to NSCollab.
(yes - i know - ATM Axure will "mabay" updated .....)
Its only - i have from the beginning an screenoff profile and it works fine.
So - if it never working, anything with the new build musst be wrong.
Have read in the dev forum over the "green Tinte" effect i have too - so i am not full alone ...
I think the forum is for reporting bugs ... and this is the first serious i have with the nexus.
Have it rootet and CW 3.1.0.1 installed.
Have wiped all,(and backuped with TitaniumBK) before jumping from NSCollab 1.0.23 to 1.0.31.
Regards
R-TEAM
Hi,
have found that its only not freeze, if the max screen off freq set at 800 or above ... curious ......
Regards
R-TEAM
Hi,
o.k. - it looks an bug was in SetCPU.
With the new 2.2.0 version all is running normal....
(can make screen-off profiles with any low frequency ...)
Regards
R-TEAM
Problem Reproduction:
1. Boot the device.
2. No problems during normal usage or when charging.
3. Let the device go to sleep for a couple 2-4 hours
SOD:
When pressing the power button after opening the lid the screen turn on but instead is a black screen, device still seems operational, but screen does not come on, only happened two times since flashing and randomly with nothing I can pin-point it to have a theory from some research, but do not know if it is related.
RR:
Device not reboot unless reboot is initiated, TF101 is rebooting randomly during deep sleeps.
Neither RR or Deep Sleeps occur when the tablet is charging or in active use.
Specifics
Tablet: TF101 Tab and Dock, 16 GB WIFI
Recovery: TWRP 2.3.2.3
ROM: EOS 4 Nightlies Build 99
Kernel: KatKernel_96_JB4.2_Lidpatch
Specific Customization Apps:
K.A.T_V1.2.7 - using KAT Audio, KAT Media Service, GPS fix installed, and adblock hosts file in place.
SetCPU - Profile 1 (screen-on priority 50): Overclocked to 1504Mhz with Smartassv2 govenor, min setting 312 MHZ (read some people do this prevent SOD and RR for the min setting)I/0 Scheduler SIO (also read on XDA others have been very stable with this setup). Profile 2 (Battery less than 38%, priority 75): Stock Max to 312 Mhz Min with conservative governor and SIO scheduler.
**Note: All SOD and RR have occured while SetCPU is in profile 1.
Ram Manager Pro: Minfree setting set to More RAM for devices with over 512MB Memory. JV Heap set to 64MB
Lux Dash: Used to fix auto-brightness setting being too low on transformers. Have it set to dynamic update brightness.
Other settings
Disabled Hotword detection for Google Now fix.
Removed test keys from build.prop and renamed SuperSU to SU in system/apps to get around the Root checks of the TimeWarnerCable live streaming app.
Background: My transformer was in on stock ICS OTA update and was so slow it was barely usable and used battery like crazy. I followed all the procedures on XDA (http://forum.xda-developers.com/showthread.php?t=2063406) and http://public.timduru.org/Android/tf101/eos4/ for wiping, i wiped and formated everything (dalvick, cache, system, factory)besides the externalSD card. Flashed the 99 nightly build and was impressed with how smooth everything was, was like a brand new tab. Did some bench marking and saw the good reviews on KAT kernel, so I flashed KAT kernel and installed KAT app and was even more impressed with performance, benchmarks jumped significantly. Tested everything I could think possible and did not see any major bugs so I figured this would be a good settling point. I did not re-install any of my apps from the Titanium or My Backup Pro or system settings, i installed everything from the market and configured systems settings, after I stopped all the update activities that when I noticed the SOD and RR issues (due to android assistant showing startup times when I had not initiated a reboot). Two days or so ago I installed Reboot Logger to keep track of the RRs. I noticed one SOD on the 18th after 2 hours of inactivity and one on the 19th around the same amount of time of inactivity. There was four RRs on the 19th and two on the 20th. Last night I was doing some digging and saw a bunch of feedback for JB on disabling the location services in setting and app settings, so I implemented that last night as well as removed the dock SD card after before leaving the device in a state of inactivity. After those two changes there was only two RR vs the four the prior day (Although if this is a semi-fix it is a pain not being able to use auto-location for apps) and no SODs again YET.
Let me just say that I love the ROM and KAT Kernel and KAT app, I am extremely impressed with all of it with the way to performs and how buttery smooth it is compared to stock. Lots of Kudos to the developers. If possible I would like to leave KAT Kernel in place because of the performance benefits. If I could get eliminate or minimize the SOD and RRs to an extreme minimum this would be a perfect/Rock solid solution. Attached are the Kmsg and logcats before the last RR and a screenshot of the RR from the Reboot Logger (note the RR/soft boots do not have a restart timstamp next to them, the ones that do are initiated reboots. .
Do you think the latest preview (175) or nightly 100 help the SODs or RRs? Also since the previews are compiled in Linaro and this is the native format for the TF101 be slightly more stable (I did a lot of digging on XDA but could not find a lot one way or the other to justify one direction or another), any empirical data from testing? Just curious. Thanks
Turning on Fsync in KatKernel
pursleyt said:
Problem Reproduction:
1. Boot the device.
2. No problems during normal usage or when charging.
3. Let the device go to sleep for a couple 2-4 hours
SOD:
When pressing the power button after opening the lid the screen turn on but instead is a black screen, device still seems operational, but screen does not come on, only happened two times since flashing and randomly with nothing I can pin-point it to have a theory from some research, but do not know if it is related.
RR:
Device not reboot unless reboot is initiated, TF101 is rebooting randomly during deep sleeps.
Neither RR or Deep Sleeps occur when the tablet is charging or in active use.
Specifics
Tablet: TF101 Tab and Dock, 16 GB WIFI
Recovery: TWRP 2.3.2.3
ROM: EOS 4 Nightlies Build 99
Kernel: KatKernel_96_JB4.2_Lidpatch
Specific Customization Apps:
K.A.T_V1.2.7 - using KAT Audio, KAT Media Service, GPS fix installed, and adblock hosts file in place.
SetCPU - Profile 1 (screen-on priority 50): Overclocked to 1504Mhz with Smartassv2 govenor, min setting 312 MHZ (read some people do this prevent SOD and RR for the min setting)I/0 Scheduler SIO (also read on XDA others have been very stable with this setup). Profile 2 (Battery less than 38%, priority 75): Stock Max to 312 Mhz Min with conservative governor and SIO scheduler.
**Note: All SOD and RR have occured while SetCPU is in profile 1.
Ram Manager Pro: Minfree setting set to More RAM for devices with over 512MB Memory. JV Heap set to 64MB
Lux Dash: Used to fix auto-brightness setting being too low on transformers. Have it set to dynamic update brightness.
Other settings
Disabled Hotword detection for Google Now fix.
Removed test keys from build.prop and renamed SuperSU to SU in system/apps to get around the Root checks of the TimeWarnerCable live streaming app.
Background: My transformer was in on stock ICS OTA update and was so slow it was barely usable and used battery like crazy. I followed all the procedures on XDA (http://forum.xda-developers.com/showthread.php?t=2063406) and http://public.timduru.org/Android/tf101/eos4/ for wiping, i wiped and formated everything (dalvick, cache, system, factory)besides the externalSD card. Flashed the 99 nightly build and was impressed with how smooth everything was, was like a brand new tab. Did some bench marking and saw the good reviews on KAT kernel, so I flashed KAT kernel and installed KAT app and was even more impressed with performance, benchmarks jumped significantly. Tested everything I could think possible and did not see any major bugs so I figured this would be a good settling point. I did not re-install any of my apps from the Titanium or My Backup Pro or system settings, i installed everything from the market and configured systems settings, after I stopped all the update activities that when I noticed the SOD and RR issues (due to android assistant showing startup times when I had not initiated a reboot). Two days or so ago I installed Reboot Logger to keep track of the RRs. I noticed one SOD on the 18th after 2 hours of inactivity and one on the 19th around the same amount of time of inactivity. There was four RRs on the 19th and two on the 20th. Last night I was doing some digging and saw a bunch of feedback for JB on disabling the location services in setting and app settings, so I implemented that last night as well as removed the dock SD card after before leaving the device in a state of inactivity. After those two changes there was only two RR vs the four the prior day (Although if this is a semi-fix it is a pain not being able to use auto-location for apps) and no SODs again YET.
Let me just say that I love the ROM and KAT Kernel and KAT app, I am extremely impressed with all of it with the way to performs and how buttery smooth it is compared to stock. Lots of Kudos to the developers. If possible I would like to leave KAT Kernel in place because of the performance benefits. If I could get eliminate or minimize the SOD and RRs to an extreme minimum this would be a perfect/Rock solid solution. Attached are the Kmsg and logcats before the last RR and a screenshot of the RR from the Reboot Logger (note the RR/soft boots do not have a restart timstamp next to them, the ones that do are initiated reboots. .
Do you think the latest preview (175) or nightly 100 help the SODs or RRs? Also since the previews are compiled in Linaro and this is the native format for the TF101 be slightly more stable (I did a lot of digging on XDA but could not find a lot one way or the other to justify one direction or another), any empirical data from testing? Just curious. Thanks
Click to expand...
Click to collapse
Turned on Fsync in KatKernel for additional testing on SODs and RRs.
pursleyt said:
Turned on Fsync in KatKernel for additional testing on SODs and RRs.
Click to expand...
Click to collapse
1 RR while tablet was asleep, plugged in and charged to 100%.
Solved
pursleyt said:
1 RR while tablet was asleep, plugged in and charged to 100%.
Click to expand...
Click to collapse
After Upgrading to preview version 181 and turning Fsync on with K.A.T kernel the TF101 is 100% stable with no RR or SODs after 48 hours.
pursleyt said:
After Upgrading to preview version 181 and turning Fsync on with K.A.T kernel the TF101 is 100% stable with no RR or SODs after 48 hours.
Click to expand...
Click to collapse
1 RR with SD CARD in dock, know problem with EO4/Kat Kernel removed SD card from dock when not in use, stable again.
pursleyt said:
1 RR with SD CARD in dock, know problem with EO4/Kat Kernel removed SD card from dock when not in use, stable again.
Click to expand...
Click to collapse
using preview 181 kk96 dock sd removed getting RR during sleep, I tried with fsync=on, rr's stopped but that prevented tab from entering deep sleep. now trying with microsd removed. still docked
Hello,
Many of us have issues with the battery standby (or SoT) like most of the rooted user here I have also tried a lot of tricks from disabling CPU cores to removing most of the removable bloat-ware from the original firmware because (while I still was non-rooted user) many times I start the day off charger at 7AM I end up with 3:25 hours SoT and 35% battery at 7PM, then something comes up (like going to the pub) and after 3-4 hours I found my battery at 7-9% without even turning the screen on during that period of time and no clue of what drained the battery.
The idea of this discussion is to track and reveal on what usage (and with which apps) the device is having that specific drain to help non-rooted users find the sweet spot and be helpful for the rooted users.
Also some/all the suggestions in this discussion my not work with your device and ever cause it to misbehave or even hardbrick it if not done with caution and further thinking - experiment on your own risk and no one is responsible for any damages!
What is my daily usage:
Apps: Facebook / Google Play Music / Facebook Messenger / WhatsApp / Viber / SnapChat / Google Chrome / Inbox / Gmail (with POP3)
What I did as non-rooted user:
- Factory Reset
- Stopped using Moto Voice and Double Twist
- Disabled every app that is from Motorola (and it is allowed to be disabled)
- Stopped WiFi scan (not sure because even when turned off the green bar was still visible in the battery graph)
- GPS and NFC are off when not used
note: those changes helped me to get through a day with normal usage and from 7AM to 7PM I end up with 3:35 SoT and 37% battery
Continuing with root:
- Changed the CPU governor from interactive to ondemand (since interactive boosts the clocks at the highest on touch)
- Ultra Kernel (adreno idler does a great job)
note: those changes helped me to get through a day with normal usage and from 7AM to 7PM I end up with 4:10 SoT and 45% battery and until 6.0.1 came out
Yesterday (without the root changes) after some music stream through GPlay Music in the morning after a few hours (~4) my battery was at 60% with 1:50 hours SoT and GPlay Music on the top with 23% battery use and 2 hours later the battery drop on 11% with 2:45 hours SoT and GPlay Music with 6hours CPU use. The only difference with the other days and yesterday was using the MicroSD card as cache for streamed music (note that the card is class 4)
So sometimes could be the MicroSD card('s slow speed) to blame or maybe the Google Play Music App itself.
Suggestions for root user are welcomed too like CPU Tweaks, Removing unnecessary apps, etc. and will be separated from the non-root suggestions
For replay with suggestions please use the following form
What is my daily usage:
Apps: [list of the mostly used apps]
What I did as non-rooted user:
[suggestions]
note: [please add a note or screenshot from the battery using the [ HIDE ] tag
Continuing with root:
[suggestions]
note: [please add a note or screenshot from the battery using the [ HIDE ] tag
I really hope to make some good discussion about tweaking the Standby time (SoT) on the stock firmware 6.0.1.
*reserved*
NON-ROOT
- Factory reset and start from scratch (do not do restore)
- Stop using Moto Voice and Double Twist
- Disable all the apps from Motorola and others that you don't use (and it is allowed to be disabled)
- Stop WiFi scan (not sure because even when turned off the green bar was still visible in the battery graph)
- GPS and NFC should off when not used
______________________________________
ROOT
- Changing the CPU governor from interactive to ondemand (since interactive boosts the clocks at the highest on touch)
- Installing custom kernel
* Squid Kernel
* Ultra Kernel (Squid Kernel plus a few tweaks like "Adreno idler" which does a great job in low graphic environment)
@Sickaxis79
When using squids kernel with the lionfish governor you can reach 8 hours with light usage,but its not as smooth as the interactive governor.
-----------------
For INTERACTIVE governor
Im using squid r16 kernel with stock rom 6.0.1.
Cpu max freq i use is 1708mhz and minimal is 200mhz.
Enter the next values into the cpu governor tunables for the big cores.
above hispeed delay 20000
align windows 1
boost 0
boostpulse duration 80000
go highspeed load 99
hispeed freq 345600
io is busy 0
max freq hysteresis 0
min sample time 20000
target loads 98 345600:77 400000:67 533333:60 800000:83 960000:77 1113600:74 1344000:82 1459200:87 1497600:81 1651200:86 1708800:95
timer rate 20000
timer slack 80000
use migration notif 0
use sched load 0
Click to expand...
Click to collapse
First of all STOP USING GMAIL AND PLAY MUSIC
Gmail is a big culprit when it comes to stand by time ... so is play music ... ( i have disabled both )
Use Typemail ( it works without Sync on ) and any other music player of your choice
also Use Greenify to hibernate apps which you usually don't use ...also you can select ur music apps in those list ....
I am Non Rooted btw
Facebook app is known for major battery drainer
Actually Facebook is not much of a battery drainer now.... Tested and tried...
Yes it does eat a lot of RAM
pijes said:
Facebook app is known for major battery drainer
Click to expand...
Click to collapse
100rabh7791 said:
Actually Facebook is not much of a battery drainer now.... Tested and tried...
Yes it does eat a lot of RAM
Click to expand...
Click to collapse
I can confirm that too! A month since Google Chrome added the API to get notifications Facebook started to drain less and less battery with every update.
Even with all day use of the APP it still does not go over 8-9% battery consumption
Since I flashed stock 6.0.1 and previous 6.0 for my MXP the battery life was superb. About 6-8 h sot with above 30-40h+ of overall usage. My settings are with power saving in mind though.
Wysłane z mojego XT1562 przy użyciu Tapatalka
Woke up at 4:30 AM. Turned off wifi and turned on mobile data. Have used about 30 minutes of web browsing using chrome Beta. Im at work so phone is in my pocket mostly. It is now 10:30 am (6 hours later) and I lost 5 %.
Stock 6.0.1
100rabh7791 said:
First of all STOP USING GMAIL AND PLAY MUSIC
Gmail is a big culprit when it comes to stand by time ... so is play music ... ( i have disabled both )
Use Typemail ( it works without Sync on ) and any other music player of your choice
also Use Greenify to hibernate apps which you usually don't use ...also you can select ur music apps in those list ....
I am Non Rooted btw
Click to expand...
Click to collapse
Personally I don't get enough important emails to leave sync on auto mode. Created a quick toggle using power toggle and I synch on a needed basis with a simple click. Today I was on the road (working) and I turned mobile data on at 4:30 am and just turned it off @ 7:00 pm. During that time I browsed internet incl Facebook, used maps GPS, streamed a little music to car with Google music, checked email with Gmail, updated apps from play store... For a Total screen time over 3 hours on a 15 hour span (mobile). Right now 72% battery left to go.
---------- Post added at 11:28 PM ---------- Previous post was at 11:23 PM ----------
Only thing I really notice is adguard using more juice on mobile vs. WiFi but it still helps otherwise
Did you guys disabled moto apps or any app?
When I was stock I did all the usual battery saving tricks and I would get between 4 and 6 hours sot by the time I hit 15% battery.
Now with root and squid kernel I noticed that battery drains a bit faster but setting the min core frequency as low as it can go helps as well as greenify. I still get my 4 to 6 hours by the time I hit 15% battery. Im on stock 6.0 marshmallow before and after rooting. After rooting the phone I Uninstalled some Google Apps but kept all the Moto apps.
My usage is like this:chrome, whatsapp, typemail , Gmail, poweramp(music player), youtube(a lot of youtube)
On the weekend its completely different story. I spend the whole day on YouTube, playing games and watching offline video files. With that usage I get 3 to 3.5 hours sot by the time I hit 15%
Its normal to only have 3 hours sot playing games.Brightness is the best battery saver and disabling or greenify all the google crap also helps a little.Mostly I have around 6/7hours sot using wifi and browsing the internet around 30/40% brightness. When using squids kernel with the lionfish governor you can reach 8 hours with light usage,but its not as smooth as the interactive governor. If you like a snappy and smooth device with a good sot (6/7 hours) you can tweak the interactive governor. I flashed squids r16 kernel and tweaked the interactive governor with kernel adiutor so that the big cores only kicks in when needed with no lost of performance and great battery life. It just depends on how you use your phone and how you tweak with the kernel settings.
Is it safe to disable 'Apps usage' access of Moto care ?
ProudRed said:
Is it safe to disable 'Apps usage' access of Moto care ?
Click to expand...
Click to collapse
Yes
Automated reply by JARVIS
I have never seen such a device with so conflitcing problems amongst users in what concerns battery life. Simply amazing... -.- i can't decide if i am a heavy user, and the battery does indeed drains a lot or if my phone has problems.
I havent rooted yet.
I have:
- disabled moto apps and Google apps + Google search(with adb)
- changed dpi(adb)
- the same thing before.
Sickaxis79 said:
Its normal to only have 3 hours sot playing games.Brightness is the best battery saver and disabling or greenify all the google crap also helps a little.Mostly I have around 6/7hours sot using wifi and browsing the internet around 30/40% brightness. When using squids kernel with the lionfish governor you can reach 8 hours with light usage,but its not as smooth as the interactive governor. If you like a snappy and smooth device with a good sot (6/7 hours) you can tweak the interactive governor. I flashed squids r16 kernel and tweaked the interactive governor with kernel adiutor so that the big cores only kicks in when needed with no lost of performance and great battery life. It just depends on how you use your phone and how you tweak with the kernel settings.
Click to expand...
Click to collapse
Can you share with me the governor tunables you changed for getting better battery life in interactive governor?
Automated reply by JARVIS
It's definitely an app issue. I uninstalled tapatalk because it would drain the phone like stupid. GMail (with 3 email accounts) doesn't seem so bad. I also use Whatsapp and Skype, so those aren't too bad either. Also use Play music (as offline mp3 player basically) so that's not it, either. From your list, facebook and snapchat look like they may sync too much and drain the phone. Have you analyzed your battery usage with gsam battery or similar?
I think the best app to analyse your battery drain in standby mode is this one: https://play.google.com/store/apps/details?id=com.WazaBe.android.BatteryDrain
I use it for several years. It does not cause any drain and allows me to see if I lost too much battery during the night.
For example, with Moto X Play, I'm at -0.3% /hour with wifi enabled (and connected), 4G, bluetooth, location services, auto-sync, no exposed, but with CM13.
On Moto G3, it's the same (-0.3%/h), except Moto G3 has smaller battery. I expected more for Moto X Play, but it's still very good compared to other smartphones (Galaxy S4 for example).
K.khiladi said:
Can you share with me the governor tunables you changed for getting better battery life in interactive governor?
Automated reply by JARVIS
Click to expand...
Click to collapse
Sure, but first before you apply these settings i can advice you to read this awesome guide first.
http://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557
Im studying this guide for a few days and learned a lot from it.It teaches you how to calculate your min and max target loads which you need later to tweak the interactive governor. Im still learning , but i never knew interactive governor was so higly tweakable. If you understand all of this guide you can tweak your kernel just how you like it. Its a universal guide with examples for the nexus 5 and 6 and the most useful guide i have found so far about this governor.
I have the big cpu's tweaked so it stays at 200mhz and ramps up when needed. This are the settings i used and they work nice so far, but remember im still learning
Im using squid r16 kernel with stock rom 6.0.1.
Cpu max freq i use is 1708mhz and minimal is 200mhz.
Enter the next values into the cpu governor tunables for the big cores.
above hispeed delay 20000
align windows 1
boost 0
boostpulse duration 80000
go highspeed load 99
hispeed freq 345600
io is busy 0
max freq hysteresis 0
min sample time 20000
target loads 98 345600:77 400000:67 533333:60 800000:83 960000:77 1113600:74 1344000:82 1459200:87 1497600:81 1651200:86 1708800:95
timer rate 20000
timer slack 80000
use migration notif 0
use sched load 0
HEATING:
Heating while charging isn't an issue pls. You can let your phone cool down before charging it in a cool place. You can either power it off or put it on Airplane mode while charging. (This will reduce the charging time and also some activities by apps which slow the charging) Heating is normal while charging owing to the Quick Charge x.0 capability of Qualcomm Snapdragon 617 (MSM8952). It will heat up. Heating is reduced in the latest builds, especially while recording video via the camera. This semi-budget oriented processor isn't designed for heavy gaming pls, despite 3GB of DDR3 RAM available to it. If you're a hard core gamer or someone who likes to overclock stuff, this isn't the right phone.
If you feel your phone is heating with normal usage too, consider removing apps which are useless and clear the cache followed by a reboot. See to it that the apps are updated. You can switch to WiFi instead of Mobile Data (keeps my athene cool idk why). If nothing works, consider a factory reset; else shift to a custom ROM if you can and test.
PERFORMANCE:
General phone performance of Nougat has been better than Marshmallow for sure, but for many, 7.0 has had the notification drawer stuttering issue in some cases and Bluetooth being turned on automatically after turning Airplane mode ON. Overall experience is smooth. But many people do not like stock ROM very much, because of the lack of features. AOSP and LineageOS based ROMs are much better that stock in terms of speed. For god's sake don't use the task killer apps or battery savers like CCleaner / CleanMaster/ DU Battery Saver. Apps staying in the memory (RAM) are good for your device until your phone is lagging. Clearing the things from the recents panel will force them to start again from scratch, consuming the CPU and of course the battery.
BATTERY & CHARGING:
Stock N wasn't very good in terms of battery after all in comparison to MM despite the improved doze mode introduced in Nougat. Well this is the case in almost every android OEM that the battery performance went down in transition from one Android version to another. However, the March 1 update is said to fix a bit of battery and security issues. Android has the habit of collecting garbage (but that makes it smart too) and this can be one of the reasons why battery and performance issues occur after an OTA. The best thing after a "dirty/problem causing" update is to do a factory reset. Anyways, it is advised to clear the cache before and after doing an update. For god's sake don't use the task killer apps or battery savers like CCleaner / CleanMaster/ DU Battery Saver. Apps staying in the memory (RAM) are good for your device until your phone is lagging. Clearing the things from the recents panel will force them to start again from scratch, consuming the CPU and of course the battery.
Battery Saving and charging Tips:
Please understand the difference between Screen On time of a complete cycle and the usage time. People start judging the battery from the estimated time left after the first charge itself. A tip is to fully charge the battery after a clean flash and then let it drain till 15%. Do not let the battery drain completely, Li-ion batteries lose their capacity over time and are designed to run between 20-100 percent. Battery life of your phone is completely dependant on your usage. Turning off Auto-Rotation, WiFi, Bluetooth, Sync, Mobile Data, Location Services and scanning (almost everything ) when not needed can give you the best battery life possible. You can consider using Greenify although you should avoid any such thing. Android learns how you use it, no need to comment about the 2 H SOT you're getting after a clean flash. You might also want to uninstall the useless apps and block the wakelocks (which you understand) if possible. Turn off the SIM card if it's in very low network. If nothing is helping you, you might consider doing a factory reset too.
Checkout this amazing thread by @rirozizo and the video by XDA TV.
https://www.youtube.com/watch?v=3Zt2j8lFbJQ
Ghost Touch: Your touchscreen is at fault. Visit the service center please.
Screen Retention: Your display is defective. Turning the phone off for a while and then setting blue light filter at 5% for Black colour or changing the RGB values is a temporary fix. Visit the service center please.
Random Reboots: Try factory resetting your device, see if you installed something wrong and flash latest stock firmware, just in case, you know. Else the service center only can fix the issue if still present.
For not being called a noob:
1. Read XDA and other forums and think before you do anything to your phone.
2. Ask in the community if you have doubts. (Read Rules and XDA University's New User's guide first)
3. Always make backups before flashing new things. (Use TitaniumBackup and TWRP backups)
Check the videos by XDA-TV and Rootjunky ( @Tomsgt )
https://www.youtube.com/watch?v=_rEsgCrvEqY
https://www.youtube.com/watch?v=nyr3FstDKH0&index=1&list=PLgLZvFga2ml4Atl32E4c_ZslfrTJJDUfr
https://www.youtube.com/watch?v=j-i59R51Cys
4. See this video by XDA-TV:
https://www.youtube.com/watch?v=JmvCpR45LKA
5. Stop using useless apps and be patient pls.
Valar Morghulis!
Good thread, I'll add a couple of my tips here.
- ohmergerd, there's thousands of ROMs for the G4! Which ones are the best???? Nearly every single ROM for the G4 subtracting perhaps GZR ROMs and RevivorOS/optimized stock is LineageOS based (Invicta is basically Lineage with MM kernel blobs and faux/OMS integrated). There's basically no performance differences, just feature differences based on the discretion of the dev.
- If heating is STILL an issue for you, disable the 4 big cores. There isn't a significant difference in everyday use- the LITTLE cluster handles the UI and basic apps anyway.
- Haven't noticed notification bar lag since the 7.1.2 builds. If you have lag (depending on your ROM), using blur or transparency helps trick your eyes into seeing no lag. If lag persists, force enable scrolling cache and speed up the animations.
- If you have a custom kernel and your RAM usage isn't an issue, disable KSM, Adaptive Memory Killer, and/or ZRAM and Kernel Adiutor/EXKM. While useful if you let your memory use skyrocket, if you are conservative in your memory use these memory killers just suck up CPU cycles.
- Build prop tweaks/L Speed/HEBF don't work. Completely placebo, except for governor tweaks.
- USB-OTG is great, I recommend getting a dongle if you're a flashaholic. Much easier and quicker to simply plug in your USB to flash instead of plugging in your phone, transferring the ROM, flashing, etc.
- Use a trickle charger, and save that fast charger for emergencies (camping, flights, etc.).
- Disable a bunch of Google's **** in settings- I advise going through Activity controls as Google takes snippets of keyboard input, voice, web history, video history, etc. This adversely affects battery life especially if you have a weak signal, as Google Play Services continuously attempts to push through their telemetry data. This is also why you get 2hrs of SoT after a clean flash.
- On stock-based ROMs (to eliminate lag), boot the ROM once, then reboot to recovery and flash the latest Aroma GApps package with the apps you want. Then, mount /system, and start deleting all apps in /system/app or /system/priv-app that begin with "3c". This effectively removes Motorola updates and telemetry, and also updates your GApps- the stock GApps are very old, and updating them caused Play Store errors and miscellaneous battery sucking services.
- Mr. Shield Protectors suck. Badly cut-out, misaligned, etc.
Hard reset: A term with the common misconception here in the group. Hard reset means nothing in android smartphones. It is only a term for older computers where you manually had to reset the old electrical parts from the charge they held.
Factory reset via the settings is equivalent to the Wipe Data/Factory reset available in the stock recovery.
Also, always sign out from your Google account before doing the wipe, else chances are your device may enable Factory Reset Protection and lock the device.
Normally my phone was using two BIG cores (and the four LITTLE ones). Each core was utilized around 40-60%.
Withing kernel manager I have set the minimum value for the BIG cores to 1 and I have lowered the minimum frequency value for that core. Now the utilization on that core is close to 100%.
Now the phone is cold all the time (except when charging with the Fast Charger) and I have no lag issues whatsoever.
Oh, btw, on some kernels (EX 1.07, Vegito), workqueue power saving is built in which iirc tries to schedule tasks on the fewest cores as possible, so on these kernels which tend to turn off cores and lower frequencies while asleep the wakeup action, especially while dozing, the wakeup action will be met with significant lag/delay.
If you have a delay when turning on your phone with these kernels (or even stock kernels for some ROMs), disable the setting called wq_power_saving.
I have the solution for random reboots. But only for those devices that reboots 4 or 5 times every day. Just open your device and disconnect the battery for 30 minits. Or also you can change the battery (confirmated it works)
negusp said:
Good thread, I'll add a couple of my tips here.
- ohmergerd, there's thousands of ROMs for the G4! Which ones are the best???? Nearly every single ROM for the G4 subtracting perhaps GZR ROMs and RevivorOS/optimized stock is LineageOS based (Invicta is basically Lineage with MM kernel blobs and faux/OMS integrated). There's basically no performance differences, just feature differences based on the discretion of the dev.
- If heating is STILL an issue for you, disable the 4 big cores. There isn't a significant difference in everyday use- the LITTLE cluster handles the UI and basic apps anyway.
- Haven't noticed notification bar lag since the 7.1.2 builds. If you have lag (depending on your ROM), using blur or transparency helps trick your eyes into seeing no lag. If lag persists, force enable scrolling cache and speed up the animations.
- If you have a custom kernel and your RAM usage isn't an issue, disable KSM, Adaptive Memory Killer, and/or ZRAM and Kernel Adiutor/EXKM. While useful if you let your memory use skyrocket, if you are conservative in your memory use these memory killers just suck up CPU cycles.
- Build prop tweaks/L Speed/HEBF don't work. Completely placebo, except for governor tweaks.
- USB-OTG is great, I recommend getting a dongle if you're a flashaholic. Much easier and quicker to simply plug in your USB to flash instead of plugging in your phone, transferring the ROM, flashing, etc.
- Use a trickle charger, and save that fast charger for emergencies (camping, flights, etc.).
- Disable a bunch of Google's **** in settings- I advise going through Activity controls as Google takes snippets of keyboard input, voice, web history, video history, etc. This adversely affects battery life especially if you have a weak signal, as Google Play Services continuously attempts to push through their telemetry data. This is also why you get 2hrs of SoT after a clean flash.
- On stock-based ROMs (to eliminate lag), boot the ROM once, then reboot to recovery and flash the latest Aroma GApps package with the apps you want. Then, mount /system, and start deleting all apps in /system/app or /system/priv-app that begin with "3c". This effectively removes Motorola updates and telemetry, and also updates your GApps- the stock GApps are very old, and updating them caused Play Store errors and miscellaneous battery sucking services.
- Mr. Shield Protectors suck. Badly cut-out, misaligned, etc.
Click to expand...
Click to collapse
Thanks for the tips.
Using Root explorer I deleted the 3c stuff and updated the Gapps via Aroma installer (never knew this Aroma version existed).
Where do I find the Activity controls thing?
bluegrass55 said:
Thanks for the tips.
Using Root explorer I deleted the 3c stuff and updated the Gapps via Aroma installer (never knew this Aroma version existed).
Where do I find the Activity controls thing?
Click to expand...
Click to collapse
It's in settings>Google, first 3 menus iirc.
i just had to unroot, re-lock my boot, and flash the latest firmware because someone has been hacking my phone. I purchased a Samsung phone and been switching the SIM between phones. I wish custom ROMs were more secure, flashing every ROM available, some took longer then others. After seeing that the Samsung KNOX wasnt able to be hacked, i decided to flash your stock N package. They are yet to get in my XT-1644 since earlier after the flash.
Am i stuck on the Stock ROM or is there a way to keep from getting a rooted with unlocked bootloader, hacked?