HTC locked their stock kernel with a "perflock" to prevent users from underclocking the kernel. Well, good news is that a new function in the SetCPU app will now allow you to underclock your Evo and get you a real, tested increase in battery life.
According to my tests, my Evo with the screen off should theoretically get a 64 hour battery life!
{
"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"
}
Know what you're doing? Short version: Get latest SetCPU (version at least 2.0.0) and use Menu -> Perflock Disabler in the Main tab to enable underclocking.
Don't know what I'm talking about? Good, follow this tutorial:
Prereqs:
You need to have ROOT. Unrevoked root method is confirmed to work, and so is Toast's root method. Usually I wouldn't recommend using Unrevoked, but it's just so fast to set up, and perfect for those who have no clue what ROOT means.
Buy SetCPU from the market, or download it from XDA forums for free. Please support the developer of this incredible app! The version must be at least 2.0.0
Be on the STOCK kernel. If you're on a custom kernel, chances are that perflock has already been disabled, and you won't need this tutorial to underclock. Some custom ROMs come with the stock kernel (like Fresh 0.5.3) and some don't (like Baked Snack .9.6)
Alright, got the prereqs down? Lets start this.
HOWTO:
Open SetCPU and give it root permissions as necessary. As a control, go into the Info tab and do the Long Bench a few times. You should get around 1000ms.
Go to the Main tab, hit MENU, hit Perflock Disabler (read the warning!), and hit Disable Perflock Beta: May crash!
It will work for a while, and then say it's successful. You can then click the X on the top right to exit the Perflock Disabler.
Go into the Main tab and drag Max: all the way down to 245000 (245Mhz). Make sure the green xxx max xxx min label above the sliders show 245 for both and also disable any Profiles you've set. Go to Info tab, then hit Long Bench again. This time you'll get something ridiculous like 5000ms, meaning that the Perflock Disabler has worked!
Change your settings Profile tab to something similar to my settings. You can mess around with the Battery < xx% profiles to fit your needs. Your exact Profile priorities do not matter, it's only important that some have HIGHER priority than others. On the Main tab, set Max all the way to the right (998400) and Min all the way to the left (245000), Scaling to ondemand, and check Set on Boot. Do not check Set on Boot yet if you're the super careful kind. You can check it later when you've tested that your phone isn't crashing
Congratulations you're now able to underclock your Evo!
Comparison:
The only applicable parts is after the charging finishes (after the solid green bar ends)
Before Perflock Disabler:
After Perflock Disabler:
See that little dip at the end? That's when I was turning the screen on and messing with the phone for this tutorial. What a difference.
Disadvantages:
Yes, not everything is happy and pretty. As the Perflock Disabler warning says, you HAVE to apply the Perflock Disabler on every boot. If you forget, then your SetCPU settings will have no effect on the Evo. Install a custom kernel that already has Perflock disabled if you do not want to do this on every boot.
Also, since this clocks the Evo down when the screen is off, you may get a slight (super slight!) delay when you turn the screen back on. This is because the profile changes from Screen Off to Battery < xx% and SetCPU needs to clock the CPU from 245mhz to 998mhz.
FAQ:
What is Perflock Disabler?
HTC added a "perflock" in their stock kernels to prevent over/underclocking. SetCPU's Perflock Disabler, like its name implies, disables this restriction.
How come your screenshots show that you can go down as high as 1.19Ghz and as low as 128Mhz?
I'm using this custom kernel.
Will this work with OTA update xxx.xxx.xxx.xxx?
Yes, as long as you have root, and don't lose it when you update (do your research!) then this will work.
What are your settings?
Wifi ON, Bluetooth OFF, GPS ON, Mobile network Data OFF (ATT contract with dumbphone still not over), Screen Timeout 1MIN, Brightness AUTO, Advanced Task Killer Pro set to SAFE kill tasks when screen is off.
What is that cool looking battery monitoring app?
That's SystemPanel, paid on the market. A free alternative is JuicePlotter, also on the market. Screenshots were taken with Drocap2.
Thanks for this, I'll try this now.
engagedtosmile said:
Thanks for this, I'll try this now.
Click to expand...
Click to collapse
Let us know if it works for you!
Thanks man. Looking good so far
Sent from my PC36100 using XDA App
Awesome, Something to tinker with all night.
download link for setcpu plz...
kthejoker20 said:
download link for setcpu plz...
Click to expand...
Click to collapse
Trust me, it's so goddam easy to find. It's even on this forum!
I was putting in the info exactly the way you had it in your screen, now I'm attempting to put the "screen off" setting into the profile and every time I try it reboots the phone. I'm running baked snack 9.6 the normal volted (Flashable ZIP - Normal-volted kernel v5.1.1 for use with 2.1 (Eclair) ROMs) kernel.
Any ideas what could be causing this and how to fix it?
---> clicking on the widget also causes a reboot
davida72 said:
I was putting in the info exactly the way you had it in your screen, now I'm attempting to put the "screen off" setting into the profile and every time I try it reboots the phone. I'm running baked snack 9.6 the normal volted (Flashable ZIP - Normal-volted kernel v5.1.1 for use with 2.1 (Eclair) ROMs) kernel.
Any ideas what could be causing this and how to fix it?
Click to expand...
Click to collapse
Whao, weird. Try enabling Notifications on the Profiles tab to see if it tries to change into a certain profile that's clocked too high or low.
pingpongboss said:
Whao, weird. Try enabling Notifications on the Profiles tab to see if it tries to change into a certain profile that's clocked too high or low.
Click to expand...
Click to collapse
I can't, as soon as I tap the Profiles tab it reboots, just tried it...
davida72 said:
I can't, as soon as I tap the Profiles tab it reboots, just tried it...
Click to expand...
Click to collapse
Which version of SetCPU do you have? 2.0.1? Don't know if it's going to help, but try something in between 2.0.0 and 2.0.1 like 2.0.0b.
Does it happen only after you do the Perflock Disabler? Or does it happen every time you use SetCPU.
Try another kernel. There are tons. Maybe try this one that I'm using here http://forum.xda-developers.com/showthread.php?t=711964
pingpongboss said:
Which version of SetCPU do you have? 2.0.1? Don't know if it's going to help, but try something in between 2.0.0 and 2.0.1 like 2.0.0b.
Does it happen only after you do the Perflock Disabler? Or does it happen every time you use SetCPU.
Try another kernel. There are tons. Maybe try this one that I'm using here http://forum.xda-developers.com/showthread.php?t=711964
Click to expand...
Click to collapse
That is the kernel I have, normal volted one - Normal-volted kernel v5.1.1 for use with 2.1 (Eclair) ROMs
I am using 2.0.1, I'll see if I can find an earlier version and see if that works...actually I'll try reinstalling this one and giving it a try again and see if that works first.
Edit : It tells me I don't need to do the perflock
davida72 said:
That is the kernel I have, normal volted one - Normal-volted kernel v5.1.1 for use with 2.1 (Eclair) ROMs
I am using 2.0.1, I'll see if I can find an earlier version and see if that works...actually I'll try reinstalling this one and giving it a try again and see if that works first.
Click to expand...
Click to collapse
Yea that's really bizarre. we have almost the same setup. Except I'm running the under-voltaged one.
Edit: Actually, that kernel already has Perflock Disabled by default. You shouldn't have to follow this tutorial. SetCPU should "just work" with your kernel.
pingpongboss said:
Yea that's really bizarre. we have almost the same setup. Except I'm running the under-voltaged one.
Click to expand...
Click to collapse
just got another reboot, maybe I'll try the under-voltaged one and see how that goes
davida72 said:
just got another reboot, maybe I'll try the under-voltaged one and see how that goes
Click to expand...
Click to collapse
Flashed the under voltaged kernel and it still rebooted on the profile tab....time to uninstall setcpu for now I suppose?
davida72 said:
Flashed the under voltaged kernel and it still rebooted on the profile tab....time to uninstall setcpu for now I suppose?
Click to expand...
Click to collapse
I guess so. Since this custom kernel already has perflock disabled, you can use another app like OverclockWidget to underclock the CPU. Try it out and let us know maybe.
pingpongboss said:
I guess so. Since this custom kernel already has perflock disabled, you can use another app like OverclockWidget to underclock the CPU. Try it out and let us know maybe.
Click to expand...
Click to collapse
appears as thought the overclockwidget works...just wish it had the profile setup like setcpu does.
I'll look and see if I can find an earlier version of setcpu.
davida72 said:
appears as thought the overclockwidget works...just wish it had the profile setup like setcpu does.
I'll look and see if I can find an earlier version of setcpu.
Click to expand...
Click to collapse
Nice, glad it worked out. OverclockWidget has very basic profiles, but they do the job. Any version of SetCPU should work for you, since you dont need the Perflock Disabler with that kernel.
ok, I got setcpu 2.0.0c and started doing the profile like yours, got to the second seting about the charge/full and saved, got the reboot...
davida72 said:
ok, I got setcpu 2.0.0c and started doing the profile like yours, got to the second seting about the charge/full and saved, got the reboot...
Click to expand...
Click to collapse
Lol I don't know what to say man. Something's screwy.
Related
Trying to figure out what the optimal settings for CM7 on the EVO Shift.
CM7 is a very advanced ROM that gives you control over a LOT of settings and it can be very hard to understand and frustrating to get the optimal settings.
Cyanogenmod 7 latest nightlies and change log available here:
http://cm-nightlies.appspot.com/?device=speedy
As of this time the latest "official" gapps is 828 and is available here: http://www.goo-inside.me/gapps
If you're feeling adventerous CrashV2010 has a new gapps with newtalk and market 3.2 included here:
http://forum.xda-developers.com/showthread.php?t=1311342
How to flash:
1) Get rooted with Clockwork recovery.
2) Download/Open ROM manager, flash clockwork recovery.
3) Reboot into clockwork recovery
4) Upgrading to a new nightly: wipe dalvik cache, /cache partition, /system partition, and battery stats
Clean install: Choose wipe/data factory reset and wipe dalvik cache, /cache partition, /system and data partitions anyway (just to be sure).
5) Partition the sd card how you like (wanna do this on first installs only usually, this will erase your sd card, so copy all necessary files off sdcard to computer before doing this and then copy them back)
6) Choose zip from SD card -> Flash CM7 zip file
7) Choose zip from SD card again -> Flash google apps.zip and then google apps new talk.zip. As of this time the latest gapps is 828 and is available here: http://www.goo-inside.me/gapps
If you're feeling adventurous flash CrashV2010's gapps zip located here: http://forum.xda-developers.com/showthread.php?t=1311342
7a) Flash a custom kernel if you have one.
8) Reboot phone
9) Wait 5-10 minutes for dalvik cache to rebuild and phone to load
10) Once phone boots skip google account setup and get connected to wifi
11) Menu settings -> privacy UNCHECK automatic restore
12) Menu -> settings -> accounts + sync -> add account -> google, sign in.
13) Open market: search for "pub:Google Inc." to find all the google apps
14) IMPORTANT: After installing GMail go to accounts + sync settings -> google account and check the gmail check box. Otherwise gmail will not sync!
15) Flashing a kernel: Download kernel manager lite from the market, open kernel manager lite, load kernel list, allow super user request, menu -> advanced options, uncheck "Automatically flash", back, choose AOSP kernel, download, reboot in to recovery of your choice (clockwork in my case, wipe cache, wipe dalvik cache, install zip from sd card, go to sd-ext dir, kernelmanager, choose kernel zip file and install.
You should be good to go at this point and you can start tweaking CM7 using my settings below or however you want.
At the time of this writing I am running nightly 224, Crash V2010's Google Apps with Market 3.2 and new talk included and Scarystable kernel, latest Clockwork Recovery, Patriot 16GB Class 10 SD card on Sprint. Also, using Google voice for text/voicemail and Launcher pro as my launcher.
I'll usually reboot once every day or two just to make sure it's working properly.. I blame this more on bugs in CM7 than the kernel. Then again I haven't run toastcfh's (stock) kernel in a long time.
4G works
Wifi works
overclocking works
phone is fast
battery life is good
ONLY use ScaryGhoul's governors. (SCARY, TOASTY, BATTERYSAVE!)
ALL OTHER GOVERNORS HAVE STABILITY ISSUES! (interactive, ondemand, performance, etc. etc.)
2 things to take notice of: There is a notification power widget (which goes in your notification/status bar) and a power control widget (which goes on your home screen).
What I'm really not sure about is which takes precedence over the other and what network modes to use.
Update 10-6-2011: I am ALMOST 100% sure the power control widget that you add to your home screen takes precedence.
A lot of settings taken from here:
http://forum.cyanogenmod.com/topic/22620-settings-to-optimize-battery-on-cm7-last-updtd-may-8-2011/
Further explanation of settings here:
http://wiki.cyanogenmod.com/wiki/CyanogenMod_Settings
So here are my settings as of this time:
CYANOGENMOD7 settings (THE IMPORTANT STUFF!)
Application settings
Allow application moving: checked
Install location: automatic
Permission management: unchecked
Phone goggles: off
Display
Automatic backlight
Enabled: off
Light levels (updated 10-17-2011, didn't find this really beneficial and/or don't know how it works)
Use custom: unchecked
Screen dim level: 12
Edit other levels..: ???
Allow light decrease (??): unchecked
Screen-on animation: off
Screen-off animation: off
(saves battery off)
Accelerometer rotation:
0 degrees: checked
90 degrees: checked
180 degrees: unchecked
270 degrees: unchecked
Input settings
Long-press home settings: whatever you want
Long-press menu settings: whatever you want
search key behavior: whatever you want
Haptick feedback tweaks
Haptick feedback main: unchecked
Volume rocker wake: unchecked
Volume button music con: unchecked
(saves battery off)
Interface
Power prompt: checked
Notification power widget
Notification power widget: checked
Hide on change: unchecked
Hide indicator: unchecked
Hide scrollbar: checked
Haptic feedback: off
Widget buttons:
Everything unchecked except brightness, GPS, flashlight, sound, wifi, wifi AP, WiMax
Network modes (???): DO NOT TOUCH!
Screentimeout modes: 30s/2m/5m
Sound modes: Sound+Vib/Vib/Silent
Flash mode: High/Death Ray
Performance
CPU Settings:
Governor: Scary
Min CPU frequency: 184 mhz
Max CPU frequency: 1600 mhz
Set on boot: checked
Compcache RAM usage: disabled
Use JIT (??): checked
Use 16bit transparency: unchecked
Enable surface dithering (??): checked
Allow purging of assets (??): unchecked <-- beter performance unchecked
Lock home in memory(??): unchecked
Lock messaging app in memory(??): unchecked since using google voice now
VM heap size: 48m
Sound
Notification focus: unchecked
Silent state: checked
Vibrate during calls: unchecked
Always play on speaker
Notifications: checked
Ring tones: checked
Alarms: checked
System:
Anonymous statistics
Enable reporting: unchecked
POWER CONTROL WIDGET:
Get to this by going to menu -> add -> widget -> power control on your home screen.
Everything unchecked except the following:
Wi-Fi, Portable wi-fi hotspot, GPS, Mobile data, Wimax, Brightness, Flashlight, Round corners, Wi-Fi disables 3g, Wi-Fi enables 3G, Vibrate as ON
Network mode: 2G/3G only/3G+2G
Ring modes: Sound+Vib/Vib/Silent
Brightness levels: Auto/25%/100%
Screen time out 30s/2m/5m
======================
ANDROID settings:
Wireless & Networks:
Wi-Fi settings:
Network Notification: OFF
In this screen hit the menu button -> advanced
Regulatory domain = 14 channels (BUG: SEEMS TO NOT BE SAVING THIS SETTING ANYMORE)
Wi-Fi sleep policy = NEVER
Mobile networks:
Data Enabled: Checked
International data roaming: Checked
National data roaming: Checked
System select: Automatic
Display
Brightness
Automatic brightness: checked
Auto-rotate screen: checked
Animation: No animations (saves battery off)
Screen timeout: 30 seconds
Call settings:
Voicemail service: Google Voice (when you flash a new CM7 build you will need to delete your sprint number and re add it to google voice in order to get the Google voice choice back. Google voice will call you and you will enter a 2 digit code. Wait for Google voice to hang up on you and then you will be able to choose Google voice as your voicemail carrier.)
Google voice settings from http://voice.google.com :
Sprint integration: enabled
Receive text message on this phone: checked
Notify me of new voicemails via text: checked
These settings will allow you to use the android messaging app or google voice app to send texts and will also back up your SMS.
Vibrate on answer: off
Vibrate every 45 seconds: off
Vibrate on hangup: off
Vibrate call waiting: off
Keep screen awake: off
Always use proximity: off
Always back to call log: on
Missed call LED notify: off
Show nick/organization: off
Left-Hand mode: off
(explanation of left handed mode per otaking71: "It biases the presses/taps. Like if it's off...and you use the touchscreen keyboard......it biases the touches more to the right..vs to the left. Think about how you'd use your thumb one handed. it alters the bias of that.")
Enable sensor rotation: off
Incoming call in background: off
Hide hold button: off
Voicemail notifications: off
Voice Privacy: off
Use internet calling: only for internet calls
Location & Security
Use Wireless Networks: Have had problems disabling this
Use GPS satellites: checked
Use visible pattern: unchecked
Use tactile feedback: unchecked
Visible passwords: unchecked
Accounts & sync settings:
Background data: checked
Auto-sync: checked
(Per otaking71, autosync is not necessary for your accounts like google, facebook, and whatsapp to update. That is what background data is for. This will save you a considerable amount of battery life.)
^^This is wrong, you NEED auto-sync! And I don't know what code for strikethrough is obviously.
UPDATE: Auto-sync needs to be checked in order to receive gmail push notifications.
Background data is what apps like Facebook and Twitter use to sync data in the background.
In order to preserve battery life you should tweak the refresh interval in each application if possible. Other than that you are pretty much stuck with leaving both of these on unless you don't mind manually updating your applications.
Privacy
Backup my data: checked
Automatic restore: unchecked
(ANNOYING setting that will start downloading all your market apps all over again once you reflash!)
=============================================
Explanation of governors:
Quote
From XDA-Dev & setCPU :
CPU governors control exactly how the CPU scales between your “max” and “min” set frequencies. Most kernels have “ondemand” and “performance.”
ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.
userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
interactive- The 'interactive' governor has a different approach. Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when coming out of idle. When the cpu comes out of idle, a timer is configured to fire within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.If the cpu was not 100% busy, then the governor evaluates the cpu load over the last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down to.
smartass (Available only in certain CFS kernels. Not usually avaialble in BFS kernels like CM.): - Based on interactive, but better. Performance is on par with the "old" minmax and smartass is a bit more responsive. CPU spends much more time at the lower frequencies. Smartass will also cap the max frequency when sleeping to 245Mhz (or if your min frequency is higher than 245 - why?! - it will cap it to your min frequency). Lets take for example the 998/245 kernel, it will sleep at 245. No need for sleep profiles any more!
Scarykernel specific governor explanations:
Governor exlainations
Toasty makes one transition to the max speed and stays there(benchmarks only usually)
Batterysave! sits at the bottom and when the cpu load increases past the threshhold it scales up to the next speed and takes another load sample and keeps doing that(best on battery life/performance ratio)
Ondemand sits at the bottom and when the cpu load increases past the threshhold, it scales ot the max speed then takes another load sample and scales down accordingly
Powersave makes one transition to the bottom speed and stays there
Smartass(Quoted from another author http://www.ziggy471.com/2010/11/07/s...-governor-info ) - "is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works – by taking over the idle loop – is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the “old” minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 – why?! – it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!"
Scary - A new governor I wrote based on conservative with some smartass features, it scales accordingly to conservatives laws. So it will start from the bottom, take a load sample, if it's above the upthreshold, ramp up only one speed at a time, and ramp down one at a time. It will automatically cap the off screen speeds to 245Mhz, and if your min freq is higher than 245mhz, it will reset the min to 120mhz while screen is off and restore it upon screen awakening, and still scale accordingly to conservatives laws. So it spends most of its time at lower frequencies. The goal of this is to get the best battery life with decent performance. It will give the same performance as conservative right now, it will get tweaked over time.
===============================================
CHOICES OF KERNELS:
To download/flash a new kernel download kernel manager from the Market.
Differences between kernels are speed/battery savings/overclocking/underclocking/undervolting.
Right now I prefer ScaryKernel Stable. It is way faster than the stock CM7 kernel.
AOSP/CM7 based:
ScaryKernel SUV - ScaryGhoul
ScaryKernel Stable - ScaryGhoul
GirlyKernel - ScaryGhoul
V8 aka Pershoot - SparksCo
Tiamat_Shift - cayniarb
x99kernel-CM7 - x99percent
bcblend VR tinyRCU v - bcnice20
Official CyanogenMod 7 Kernel - toastcfh
You can use Antutu benchmarker (available from the market) to see the performance differences between the different kernels. I got over 4000 on Antutu with Scaryghoul's SuperStable kernel (which is available for download in the dev forum or kernel manager lite app, make sure you are on wifi before downloading through kernel manager lite) on Toasty governor at 1900mhz.
Your results will vary with performance. Not all phones can OC to 1900mhz and all phones will eventually get HOT running at 1900mhz constantly. There ARE different hardware versions of the phone. Mine is version 0004. You can check your hardware version ONLY with a Sense based ROM.
Sense based (DO NOT FLASH ON CM7!!):
ScaryKernel SUV - ScaryGhoul
ScaryKernel Stable - ScaryGhoul
Dodgekernel - dodgejcr
x99kernel-Sense - x99percent
Stock 2.2 Sense - Dodgejcr
Backups:
TITANIUM BACKUP OR BUST!
Please post your settings differences.. also if you could offer an explanation of the stuff I marked in ??? and which takes precedence the power control widget or the power notification widget that would be appreciated. Also provide the kernel you are running, nightly build number, and provider.
{
"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"
}
Credits:
toastcfh
ScaryGhoul
riggsAndroid
jesusice
otaking
xIndirect
CrashV2010
ChaoticSheep
Everyone in #htc_evo_shift
This is great!
Yeah just going to come out and say this, I didn't read all of it but you SHOULD/MUST take your phone off of toasty.
Toast is performance renamed. It spends all of the time clocked at the max speed....So you've been spending all this time at 1.9ghz. I recommend either dropping your clock speed down to 1ghz -1.2ghz or doing that & changing governors. Should never spend a long period of time at high speeds/voltages.
Scaryghoul said:
Yeah just going to come out and say this, I didn't read all of it but you SHOULD/MUST take your phone off of toasty.
Toast is performance renamed. It spends all of the time clocked at the max speed....So you've been spending all this time at 1.9ghz. I recommend either dropping your clock speed down to 1ghz -1.2ghz or doing that & changing governors. Should never spend a long period of time at high speeds/voltages.
Click to expand...
Click to collapse
Updated the governor suggestion to Scary. I like having it at max CPU settings in case the phone needs to burst up to that speed.
In fact on either toastcfh's kernel or Tiamat's kernel Jesusice noticed that setting the max cpu speed to the highest actually improved his battery life. I don't know maybe it's different with your kernel.
VICODAN said:
Updated the governor suggestion to Scary. I like having it at max CPU settings in case the phone needs to burst up to that speed.
In fact on either toastcfh's kernel or Tiamat's kernel Jesusice noticed that setting the max cpu speed to the highest actually improved his battery life. I don't know maybe it's different with your kernel.
Click to expand...
Click to collapse
Having the max set higher is not a problem as long as your phone is stable at that speed. Personally I don't like to go above 1.5 but each device is different. The problem is having the governor set to Toasty or Performance. With those governors you're not going just get a quick boost to the max when your phone needs it, it's actually gonna stay at the max all the time. Currently I'm using Smartass on Tiamat's. Scary can correct me if I'm wrong but I believe Smartass scales to your max when actually using the device but scales all the way down to the minimum when screen is off. I believe Scary is a modified version of Smartass.
ALL HAIL OTAKING71, THE RAPER OF HBOOT!!!
Oh, and as far as performance settings I used to have purging of assests and lock home in memory checked and VM heap changed to 48 but lately I've gone back to the stock setting (unchecked with 32 VM heap) and I think I like it better. I've noticed no loss in performance and have noticed that Tapa used to require me to restart it frequently or it wouldn't refresh but now I don't have that problem. No comment on Compache since I'm not on Scary's kernel and that's the only kernel I've noticed that adds those settings.
ALL HAIL OTAKING71, THE RAPER OF HBOOT!!!
jesusice said:
Having the max set higher is not a problem as long as your phone is stable at that speed. Personally I don't like to go above 1.5 but each device is different. The problem is having the governor set to Toasty or Performance. With those governors you're not going just get a quick boost to the max when your phone needs it, it's actually gonna stay at the max all the time. Currently I'm using Smartass on Tiamat's. Scary can correct me if I'm wrong but I believe Smartass scales to your max when actually using the device but scales all the way down to the minimum when screen is off. I believe Scary is a modified version of Smartass.
ALL HAIL OTAKING71, THE RAPER OF HBOOT!!!
Click to expand...
Click to collapse
Tiamat's kernel kept freezing on me. I could try it again soon sometime.
As of right now Scary governor + ScaryStable kernel has not frozen at all. Running good.
@Jesusice, could you take a look at the rest of the settings and let me know what you think?
How's about the data and sycn buttons? I turn off the sycn thought it'll save battery.
Sent from my PG06100 using XDA App
dumper1234 said:
How's about the data and sycn buttons? I turn off the sycn thought it'll save battery.
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
You can do that if you like, but I didn't really notice much of a difference..I find they are more trouble than they are worth and sometimes my sync stops working. The bigger question is notification power widget vs power control widget.. it's like 2 places to put in some of the same settings. Anyone know about this?
VICODAN said:
You can do that if you like, but I didn't really notice much of a difference..I find they are more trouble than they are worth and sometimes my sync stops working. The bigger question is notification power widget vs power control widget.. it's like 2 places to put in some of the same settings. Anyone know about this?
Click to expand...
Click to collapse
Using both the notification widget and the power control seems kind of pointless. Unless you would rather have the widget set for different toggles because you don't like scrolling the notification widget. I don't know...
Sent from Gingerbread Speedy 4G
crump84 said:
Using both the notification widget and the power control seems kind of pointless. Unless you would rather have the widget set for different toggles because you don't like scrolling the notification widget. I don't know...
Sent from Gingerbread Speedy 4G
Click to expand...
Click to collapse
There are settings you can change in power control widget that you cannot change in notification power widget settings. Add the widget to your homescreen and see for yourself since you ARE running CM7 after all.
Most of the settings you list are subjective and there's not a "best" setting or "better" setting. So, I'll just go over some of the settings that I have enabled and enjoy.
This is how I have my homescreen and power widget set up:
I don't have 2G/3G toggle enabled because I don't believe it actually does anything on our phones. I wish it did though. And I don't think you have to worry about which widget (power or status bar) takes precedence, they work together. For the status bar widget I have my media controls (prev, play, next) and my torch.
I've been using Tiamat 1.1.2 since release and have kept all performance settings at stock default. 1ghz max w/Smartass governor. I also use AutoKiller Memory Optimizer set to Optimum preset (40, 50, 60) with all the Advanced System Tweaks enabled except "Remount all partitions as noatime". I did have that enabled for a while but then I noticed that when using Gameboid it wouldn't keep track of my quick save correctly.
For me, the beauty of CM7 is in CyanogenMod Settings. There's just some small tweaks available that I don't think I've found in any other ROM that's not based off of CM7. (And I don't feel the need to use a ROM based off of CM7 when I can just skip the middleman and use CM7.) For example, long pressing volume keys while screen off to skip tracks is freaking awesome! (Big up to Bobtsunam for enabling it on MIUI, thereby removing one of the dozens of reasons that prevent me from using MIUI). Also, incoming calls in the background is genius. There is a small bug with it when using apps that exclude the notification bar since it locks the home button but otherwise it's awesome sauce.
If you turn off auto brightness then you can slide along the notification bar to adjust brightness. The long press action for Home, Menu, and Search can all be customized to open whatever app you want. I have my Menu set to bring up Subsonic when held. Whenever I want to leave an app that doesn't provide an easily accessible exit button I just long press Back and BAM!, app killed.
Oh, and I've also been using ViperMod and lowered voltages by -50mv yesterday and haven't had a problem yet. It may be a fluke or because I just wiped battery stats at 100% but I've been getting amazing battery life today. About half and half on wifi and 3G with moderate usage I've gone 7hrs 15mins and am still at 66% =)
I am on nightly #178.
BTW: To any new users reading this, you really shouldn't even bother with the CM7 RC for the Shift. That thing is way behind the curve. I know it's the only CM7 posted in Development but you should really check out the nightlies. 178 is my recommendation. The nightlies thread is in General if you have any questions.
ALL HAIL OTAKING71, THE RAPER OF HBOOT!!!
UPDATE:
I found that you DO need the Power Control WIDGET on the home screen. I was having problems after turning off switching from Wifi to 3G.
Still researching 4G/3G, updated some other settings.
updated, changed allow purging of assets to be unchecked. better performance.
THANKS!
Thank you Vico! It was a pleasure to meet you the other night =)
I am still trying to figure out if they have a Voicemail app that works well now..
Best
konichwa said:
Thank you Vico! It was a pleasure to meet you the other night =)
I am still trying to figure out if they have a Voicemail app that works well now..
Best
Click to expand...
Click to collapse
Google voice! Nice meeting you too!
VICODAN said:
Google voice! Nice meeting you too!
Click to expand...
Click to collapse
I love arguing voicemail! Lol, i personally use YouMail... Many nice features
Teleported from my Shifty Speedy using Tapatalk
updated the instructions, will make some more updates later today.
Updated how to flash instructions, added some more info, screenshots, and added credits to the people that have educated or helped me and contributed to the original post.
VICODAN said:
Google voice! Nice meeting you too!
Click to expand...
Click to collapse
Google voice won't stop the annoying text messages all the time, just a fyi.
Sent from my PG06100 using xda premium
Thats right
this rom is amazing but there is ONE big problem and that is Battery Drain while the phone is in deep sleep!
you allways gets around 80% deep sleep and 20% at 200mhz CPU usage.
i have found what causes it and there is two apps running that eats power.
1: Maps
2: Samsung Push Service
{
"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"
}
The easiest way is just to do a Force Stop on both then the problem is gone.
but i have not found what settings to use to stop them from running in deep sleep.
maybe someone can figure it out?
i want Google Maps but not Samsung Push Service
just killing Google Maps every time isnt right
Would autostarts work?
This post was pulled out of my arse.
Yeah me too facing the same thiing its mostly on 200mhz and the battery is dieing like hell
Edit i used titanium backup and froze both the apps
Hmm my battery life for today kinda idle usage but I tried with power saver mode on no visible decrease in performance too
Sent from my GT-I9100 using xda app-developers app
Actually I don't get the Samsung one on mine only maps
Sent from my GT-I9100 using xda app-developers app
i have done some more testing but im not 100% sure what causes the drain.
it has nothing to do with Samsung Push Service that for sure.
i use Better Battery Stats instead of CPUSpy to see more details and the only app that woke up the phone was maps.
but only if Google Now was on
i think its has something to do with Google Now and "Location and Google search" under Location Services
something bugs it out.
just disable Google Now and untick "Location and Google search" and restart the phone
then you should have your deep sleep at 90% or more
now its cool
this is just 2minutes so the % will rise for a longer time..didnt have time to test longer
you should not have any alarm for the MAPS here
i had two of them before
this one is still there but causes no problem
Set Google Now to OFF and untick Location and Google search and restart
i hope they fix this
you shouldnt disable apps to get decent battery life
where is the google now settings to turn it off?
http://support.google.com/nexus/bin/answer.py?hl=en&answer=2669986
neuropsychosis said:
Would autostarts work?
This post was pulled out of my arse.
Click to expand...
Click to collapse
I have the push service frozen. I used autostarts on Maps and disabled it every place I found it. Everything location based still works fine, course and fine. The only bad thing is that once you use the Maps app, you have to go and kill it and kill it out of the cache and make sure its done quick enough that it doesn't respawn. I'll be really happy when holding down the back button kills it entirely. It might be worth making a widget for that now that I think of it. Also, as posted, turning off Google Now is needed since it opens Maps (I think; its been a while since I trialled it).
It's a test version, it's for test purposes, if you decide to use it as your daily rom you must accept it's issues.
So, IMO this topic seems useless to me, a new version will be launched in a while.
Its not worthless. This helps people isolate what causes the drain and perhaps come up with ways to fix it.
This post was pulled out of my arse.
sergini said:
It's a test version,
Click to expand...
Click to collapse
nah its the real deal remember
sergini said:
It's a test version, it's for test purposes, if you decide to use it as your daily rom you must accept it's issues.
So, IMO this topic seems useless to me, a new version will be launched in a while.
Click to expand...
Click to collapse
new version of this leak?are you saying?
Have the same problem with deepsleep. I'm using original stock odexed rom and battery drain in deep sleep is around 1% per hour which is too much. On my previous rom I've used - MIUI ICS it was around 1% per 8 hours! This is a big difference and something is wrong with it. What's strange on this situation is that CPU spy shows 99% in deepsleep overnight, therefore there should be no big drain. Has anybody encoutered such problems? Just check the battery level when you go sleep and check in the morning by how many % it droppped... Besides this, the rom is almost perfect. Very smooth and stable.
UPDATE: After turning location services off, the battery in deep sleep is superb. No drain anymore. Not sure if it is because of that but now it works great. The best rom ever, even in beta stage! Looking forward for official.
This may be harder on Touchwiz since it apparently doesn't support shortcuts. Its worth looking into I suppose; I haven't any experience with Touchwiz apart from deciding I want to use another launcer. I use nova launcher which works well, others would be fine but my best experience is with Nova and Apex. Both should suffice.
For maps, I've disabled it everywhere in autostarts, then for using it and killing it on exit, so that it doesn't run as a service persistantly, I've used Smanager and Swidgets (you need both installed or another app that will run a shell script) to create a script that kills maps when it isn't the foremost app displayed. Note that this kills maps if you try to background it.
https://play.google.com/store/apps/details?id=os.tools.scriptmanager&hl=en
https://play.google.com/store/apps/details?id=os.tools.smwidgets&feature=more_from_developer
Credits to this post; and most likely someone will bother to make a better solution that doesn't kill it when its backgrounded, with the info given there. As you can see, I didn't bother trying out the kill process the way it's layed out in the post but just freeze and unfreeze maps instead.
http://forum.xda-developers.com/showpost.php?p=30175170&postcount=3
I didn't bother messing around all that much and take note that you could just as easily have smanager automatically freeze maps on startup and not worry about autostarts. In any case, the script just unfreezes maps, checks every 2 seconds to see if its running as the foreground displayed app, and if not, freezes it. As such, you lose your maps icon and need to get an icon or icon pack with maps on it to use for your widget.
The script is as follows:
Code:
#!/system/bin/sh
pm enable com.google.android.apps.maps
am start com.google.android.apps.maps/com.google.android.maps.MapsActivity >/dev/null
while [ "`dumpsys activity top | grep '^TASK.*' | cut -d ' ' -f2`" = "com.google.android.apps.maps" ] ; do
sleep 2
done
pm disable com.google.android.apps.maps
Copy and paste the above to somewhere on your sdcard. It can run on the FAT filesystem with the given app. Other approaces would just need the interpreter to call the app (sh or bash if you have it installed), and that might work.. if not then putting it on the /data filesystem would be fine since its ext4 but it'll be gone when wiping data for an upgrade.
Pretty basic after reading the linked post.
pm enable: Unfreezes maps in the case that it is.
am start: Starts maps.
while, sleep, done: Checks every 2 seconds for Maps being in the foreground.
pm disable: Freezes maps app.
Much room for improvement but it suits me really well.
For Smanager and Swidgets, open Smanager, select root if needed, allow root, navigate to script (save it with a .sh file extension when pasting, though not sure if this is needed or not), tap on script, select little root icon so it runs as root, select "is script" if not already selected. exit Smanager but don't kill it. It will want to run as a cached process for starting it on boot, if you kill it on some point just open and close the app again.
Select to add a shortcut in launcher, choose SMshortcuts, select the script. Don't bother giving it a custom icon; best to do it in the custom launcher since it doesn't seem to scale the default one correctly I'm assuming it might not scale one you give it correctly.
Done.
If you wanted to use Smanager (or an alternative app, init.d script assuming it works on this rom, etc) to just freeze maps at startup and not wory about apps like autostart or Gemin, you'de just use:
pm disable com.google.android.apps.maps
That should remain frozen on a reboot, so ideally you'de want to test first to see if its already frozen or it would exit with an error but this might not be a bother for many people.
Paranoid Android (Jelly Bean) for Samsung Galaxy S2 HD LTE (SGH-I757M)
This is a fairly new ROM built from the Paranoid Android 2+ source code.
I do not develop this ROM nor do I provide support for it.
I felt that we needed a new topic to talk about this PAndroid ROM as the CM10 topic was getting pretty hefty and unorganized.
Since the development for this ROM is new, don't expect it to be as stable as CM9. Check "What Doesn't Work" for a list of what's broken!
If you still don't know what ClockWorkMod Recovery or Paranoid Android is, Google it or search XDA.
WARNING! Do not flash this to a different device model from the one it's meant for. It will not work with the other Galaxy S2 iterations, so don't try it with the Bell Galaxy S2 I9100M (non-HD). DO NOT flash it on the Asian variant of the GS2 HD (SHV-E120) either, as it uses slightly different internal hardware - the ROM will be unstable and the phone component will not work. If you are sure you have the CANADIAN Bell Galaxy S2 HD LTE (SGH-I757M), you may continue.
Click to expand...
Click to collapse
{
"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"
}
Flashing The Recovery Menu
Do you have the stock recovery menu installed? If so, move to step two. If you already have CWM installed, move to "Flashing Paranoid Android"
Download Odin from here: bit.ly/WXpnCN AND download CWM Recovery here: bit.ly/WXpfDA
Start your SGH-i757m in 'Download Mode' (Shut off device. Hold the Volume Down key while powering the phone on. The device will vibrate and soon you will see a Warning screen, where you will need to press Volume Up to enter Download mode.)
While in Download Mode, start up Odin and connect your phone to the PC via USB. You should see a status message in Odin saying your device was "added".
In Odin, press the 'BOOTLOADER' button and select the CWM TAR file you downloaded from step two.
In Odin, press Start. Once Odin is done it should say "PASS". If it doesn't finish or is stuck, try re-downloading the recovery file.
Your device will reboot.
Flashing Paranoid Android
Download the latest version of PAndroid from Socim's Dev-Host: bit.ly/WK042w AND G-Apps from: bit.ly/117KEsZ
Place both *.zip files on your Micro-SD card. Do NOT Extract Them!
Start your phone into CWM Recovery mode. To accomplish this hold down the Power Button to turn the phone on, and then immediately hold down Volume Up + Volume Down at the same time. Let go of the buttons at the exact moment you see the "Samsung" Logo.
Select "Wipe Data/Factory Reset"
Then choose "Install Zip" then "Chose Zip From External SDCard" and select the PAndroid version you downloaded in step one. Do this TWICE just to be sure.
Next flash the G-Apps file you downloaded from step one the same way.
OPTIONAL: If you need to install the Stock Bell ICS Modem, now would be the time to do it. You can get it from dsixda's Dev-Host: http://bit.ly/Wu4SJe
Reboot your device.
What Doesn't Work
Some GUI elements (ie. Youtube Controls) become hidden behind content
Some camera apps display as unintended (ie. Instagram)
No touch-to-focus for camera. Regular focus does work though
"Random" crashes
Sources and Acknowledgements
Huge thanks to Socim for getting the ball rolling on this device again! bit.ly/Vc3j7d
Also, I based most of my instructions off of dsixda's posts. bit.ly/UavsHn
And to the community for not letting this amazing phone go to waste!
Click to expand...
Click to collapse
thank you so much for the ROM. A quick question though, the white flash at my hardware keys (navigation bar) remain always on. I think the light should only be activated on use.
legendofjon said:
thank you so much for the ROM. A quick question though, the white flash at my hardware keys (navigation bar) remain always on. I think the light should only be activated on use.
Click to expand...
Click to collapse
They should only stay on when charging.
Sent from my SGH-I757M using xda app-developers app
legendofjon said:
thank you so much for the ROM. A quick question though, the white flash at my hardware keys (navigation bar) remain always on. I think the light should only be activated on use.
Click to expand...
Click to collapse
I suppose it because I set touchkey autobrightness to true in framework config, so you guys who doesn't turned on autobrightness will encounter this.
Home and Search buttons don't work
ROM looks good so far, just flashed this morning. Only issue I have noticed is the home and search buttons don't work.
[UPDATE]
I reinstalled and looks like something that loaded when I restored with Titanium backup caused the home button issues. Everything looks good now.
ljdizzo said:
ROM looks good so far, just flashed this morning. Only issue I have noticed is the home and search buttons don't work.
Click to expand...
Click to collapse
Everything working great for me including the home and search buttons...this looks to be a very stable ROM...
Sent from my SGH-I757M using xda premium
im getting a status 7 error in cwm any reasons why?
Thank you for this.
Sent from my SGH-I757M using Tapatalk 2
skodazek said:
Thank you for this.
Sent from my SGH-I757M using Tapatalk 2
Click to expand...
Click to collapse
No problem! Really gave me time to truly get used to the post editor! :laugh:
Is this rom still being worked on? I have a t989d and the jb roms for it are amazingly stable and still being improved. Would love to see a jb rom for this phone become a stable daily driver.
Gonna flash this either way and check it out!
Working Good here. Great work!!!
The phablet mode 600px with a defualt DPI of 290 works great and looks great for most apps! Some may need individual adjustment. The only app that will need adjustment after reboot is the launcher. This is what you do.
You head into paranoid settings,
hit the Apps button on the left.
Then choose Trebuchet and adjust the DPI to exactly 228. Hit Apply.
This makes everything look right again. In both the drawer and on the home screen. Otherwise your apps in drawer will not fill the screen properly, and icons start looking to small. On the home screen, for some reason if you have 5 coloumns or less, you lose your last two icons on your launcher. You will also need to do the following.
head into the launcher settings,
click home screen.
Adjust the rows to your choice.
But the coloumns need to be 6 or more.
While you are in there you will also want to
enable Resize any widget
and disable wallpaper scrolling.
I also changed alot of my dpi for other individual apps, making things look even better. This rom has made my phone work and look more awesome than it was ever destined to be! Thanks to everyones continued efforts on this phone.
Only issues I have are backlight keys sometimes do not want to come back on when you unlock phone. They do come back on later tho, never really timed it. Also andom reboots. Maybe like one or two a day.
Also I should mention DO NOT install the latest gapps
gapps-jb-20121128-signed.zip
I installed it and it broke my keyboard. If you just gotta try it..... then make sure you have a nand backup done first.
To get the backlights to come on just adjust your screen brightness...lights come on, for me anyway. I have the slider in notification bar so it's not a big deal.
Sent from my SGH-I757M using xda premium
I tried it for a few minutes and half way through restoring the apps and settings, the phone got extremely hot. So now I'm back to CM10, but if anyone knows what's wrong, I'd love to try it out again.
Siavash8 said:
I tried it for a few minutes and half way through restoring the apps and settings, the phone got extremely hot. So now I'm back to CM10, but if anyone knows what's wrong, I'd love to try it out again.
Click to expand...
Click to collapse
I suggest not restoring your apps and settings using Google's wizard. Sometimes it breaks a lot. Instead, just restore your apps manually using the Play Store OR a previous Titanium Backup.
Sent from my SGH-I757M
CharlieMPK said:
I suggest not restoring your apps and settings using Google's wizard. Sometimes it breaks a lot. Instead, just restore your apps manually using the Play Store OR a previous Titanium Backup.
Sent from my SGH-I757M
Click to expand...
Click to collapse
Agree. For example some touchkeys won't work if you come from cm10.
---------- Post added at 05:26 AM ---------- Previous post was at 05:20 AM ----------
rukusx7 said:
Also I should mention DO NOT install the latest gapps
gapps-jb-20121128-signed.zip
I installed it and it broke my keyboard. If you just gotta try it..... then make sure you have a nand backup done first.
Click to expand...
Click to collapse
When we got Android 4.2 we will need it.
Hey guys just an update on my phones experience. The rom is pretty stable for me as well. However I have had a few sudden reboots and system ui crashes. As well the latest gapps do not work correctly for me for some reason so I flashed the gapps from cm9 and that works.
The sudden reboots happen mainly when watching a video or changing wallpapers and the system ui crashes out of no where.
Now I have wiped cashed partition and delvik cach which solves the above mentioned two issues it for awhile but continues again. As well re flashing the PA rom from Nov 22.
Sent from my SGH-I757M using xda premium
CharlieMPK said:
I suggest not restoring your apps and settings using Google's wizard. Sometimes it breaks a lot. Instead, just restore your apps manually using the Play Store OR a previous Titanium Backup.
Sent from my SGH-I757M
Click to expand...
Click to collapse
Actually that's what I always do. At first, I let the Play Store downloads all the apps again, and then I restore the user apps data using Titanium Backup. This way, I don't have to tap "Install" for every fricking app. But it got so hot in the middle of downloading the apps, that I kinda freaked out and got back to CM10. It may be related to the settings and configuration connected to my Google account. I'll try again without entering my user name and password at the start and see how it goes.
I ran the ROM for the better part of 16 hrs (workday testbed) other than the play store crashing here and there, I had no issues, I was very impressed. I noticed the benchmark scores were low but if anything we know they're nothing more than a number in most cases. I did have the same heating up issue with heavy file transfers but honestly couldn't give you a value of PA vs dsixda's ICS rom. Performance "felt" much smoother and more fluid. Gallery, lights and what not worked like a charm.
PA question - Where do I turn on display battery %? I'm going to run it another day with all my automated & battery apps running, see how battery life is.
Thanks for the dev on the ROM guys, really gave new life to the device. I was seriously debating axing it for another, at my own expense since its a work phone.
Everything except for the Paranoid settings, adjusts the same way as CM10. You can find the option for battery % under System Settings/system/Status Bar.
I forgot to mention one thing that had caused me issues. When I installed PANov23 I had high useage on the app named "media". I killed it have not had a problem since. I also prefer the noop or deadline scheduler and have heard that the CFQ scheduler can sometimes take some time to scan your sdcard causing high CPU useage upon bootup. I also recommend spending the money on the PRO version of Titanium Backup. If you are a frequent Flasher, and not a dirty flasher, then you SHOULD have a paid copy of this app!!
I also use GSam Battery Monitor to watch what eats my battery. Its like Better Battery Stats, but more robust. Check it out.
rukusx7 said:
Everything except for the Paranoid settings, adjusts the same way as CM10. You can find the option for battery % under System Settings/system/Status Bar.
I forgot to mention one thing that had caused me issues. When I installed PANov23 I had high useage on the app named "media". I killed it have not had a problem since. I also prefer the noop or deadline scheduler and have heard that the CFQ scheduler can sometimes take some time to scan your sdcard causing high CPU useage upon bootup. I also recommend spending the money on the PRO version of Titanium Backup. If you are a frequent Flasher, and not a dirty flasher, then you SHOULD have a paid copy of this app!!
I also use GSam Battery Monitor to watch what eats my battery. Its like Better Battery Stats, but more robust. Check it out.
Click to expand...
Click to collapse
Should have mentioned I've never been a CM10 user. I started off with Android only very recently with an S3 first and the dev wasn't there for a daily driver, then I swapped that in for a Note 2, so again, little dev atm. And then i757, so again, even less dev.
I recently put together a very "rudimentary" widget to quickly toggle slide/sweep to wake functionality on the kernel I am running.
I originally just created it for myself, but figured why not share with the community in case anyone else might find it of use. Since this was mainly for my own use, it has no special configuration options, etc, just a cut and dry widget to use to toggle as opposed to shell commands / scripts, etc.
Since I originally posted it in the thread for the kernel I am using, I will link to that specific post for downloads (so as to maintain a single download point).
The widgets (choose between sweep2wake or doubletap2wake versions), should work on any kernel supporting either:
/sys/android_touch/sweep2wake
/sys/android_touch/doubletap2wake
as the mechanism for enabling / disabling this option.
It's nice for random times when you know you are not going to be using your phone and want to save some battery (and don't prefer / want to use scripts, tasker, locale, etc).
At any rate here's the link:
Download Here --> Download Post
{
"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"
}
For questions, comments, etc, let's use this thread, instead of the post thread, so as to not clutter that thread with off-topic stuff. Thanks!
And thanks to the kernel devs who made this feature available in the first place!
nice ..
I would suggest putting the apk's here and linking the post in the kernel thread to this thread.
munchy_cool said:
nice ..
I would suggest putting the apk's here and linking the post in the kernel thread to this thread.
Click to expand...
Click to collapse
Thanks. When / if I update the toggles, I'll move them over then, since I'll have to reload / reset anyway.
PS:-works like a charm
munchy_cool said:
PS:-works like a charm
Click to expand...
Click to collapse
Great. Thanks for the confirmation. It seems so far, I'm in the minority for when I originally created the widget just for "sweep2wake" (in terms of download count at least).
Do I need to be rooted? Does it work on stock Android if I just install it via APK installer app ?
rbs_uk said:
Do I need to be rooted? Does it work on stock Android if I just install it via APK installer app ?
Click to expand...
Click to collapse
I'm not sure you can install a custom kernel on an un-rooted phone (can't say I've ever tried though).
Since the widget requires a custom kernel that supports the wake feature, root is required (as well as so the widget can write to the necessary /sys/ file as well).
This is a very nice and well realized idea, thanks op, I'm testing Dt2w right now and it seems to work flawlessly.. One question: can we use both of widgets at the same time? For example, s2s to turn the screen off and Dt2w to turn it on?
Ps. Choosing Franco as supported kernel it's the best choice ever
Inviato dal mio Nexus 5 utilizzando Tapatalk
memnoc said:
This is a very nice and well realized idea, thanks op, I'm testing Dt2w right now and it seems to work flawlessly.. One question: can we use both of widgets at the same time? For example, s2s to turn the screen off and Dt2w to turn it on?
Ps. Choosing Franco as supported kernel it's the best choice ever
Click to expand...
Click to collapse
Thanks. Screen off is not controlled by the widget, as this can be enabled via other configuration flags. Since it does not have any impact on battery, I don't / didn't see the point in creating a toggle for it (once it's enabled, there's really no reason / need to toggle frequently).
So, you can manually enable the s2s to turn the screen off and leave it that way, and use the d2tw widget for that piece.
JsChiSurf said:
Thanks. Screen off is not controlled by the widget, as this can be enabled via other configuration flags. Since it does not have any impact on battery, I don't / didn't see the point in creating a toggle for it (once it's enabled, there's really no reason / need to toggle frequently).
So, you can manually enable the s2s to turn the screen off and leave it that way, and use the d2tw widget for that piece.
Click to expand...
Click to collapse
Nice, I'll try it in combo with Trickster mod and I'll report back.. The problem I always had with third party apps is that after few hours of stand by the Dt2w is just being disabled.. I hope your workaround doesn't suffer from the same issue
EDIT: sweep to sleep isn't working even if selected through Trickster mod.. Sweep to wake instead it's perfect.. I guess there is a specific module for s2s isn't it?
Inviato dal mio Nexus 5 utilizzando Tapatalk
memnoc said:
Nice, I'll try it in combo with Trickster mod and I'll report back.. The problem I always had with third party apps is that after few hours of stand by the Dt2w is just being disabled.. I hope your workaround doesn't suffer from the same issue
Inviato dal mio Nexus 5 utilizzando Tapatalk
Click to expand...
Click to collapse
Unless there is some other setting somewhere in place writing to the /sys/ file, it should stay on/off until you toggle once again. If not, something else is coming into play.
JsChiSurf said:
Unless there is some other setting somewhere in place writing to the /sys/ file, it should stay on/off until you toggle once again. If not, something else is coming into play.
Click to expand...
Click to collapse
See the edit to my previous post
Inviato dal mio Nexus 5 utilizzando Tapatalk
memnoc said:
See the edit to my previous post
Inviato dal mio Nexus 5 utilizzando Tapatalk
Click to expand...
Click to collapse
What specific kernel are you using? Though this is technically out of the scope of this thread, I've seen that the implementation for enabling (I don't use) varies by kernel and perhaps trickster mod is not compatible as a result.
JsChiSurf said:
What specific kernel are you using? Though this is technically out of the scope of this thread, I've seen that the implementation for enabling (I don't use) varies by kernel and perhaps trickster mod is not compatible as a result.
Click to expand...
Click to collapse
I'm using the Franco r33 test version from your op (the link I followed through) Said that, it's not really an issue, as far as I'm concerned your mod with this kernel doesn't suffer from battery drain. I tried every single kernel supporting those gestures and the drain was always remarkably high. On a side note, the widget comes really in handy if you want to save battery and this is very important. Just so you know, Trickster works with bricked from show-p, both for s2s and s2w (and for Dt2w obviously) but it's not sustainable as the battery drain is quite unbelievable sometimes. Sorry for the ot, if you'll ever spend some time on this I'll be grateful, but there's no really need to. Keep up the good job here.
Inviato dal mio Nexus 5 utilizzando Tapatalk
memnoc said:
I'm using the Franco r33 test version from your op (the link I followed through) Said that, it's not really an issue, as far as I'm concerned your mod with this kernel doesn't suffer from battery drain. I tried every single kernel supporting those gestures and the drain was always remarkably high. On a side note, the widget comes really in handy if you want to save battery and this is very important. Just so you know, Trickster works with bricked from show-p, both for s2s and s2w (and for Dt2w obviously) but it's not sustainable as the battery drain is quite unbelievable sometimes. Sorry for the ot, if you'll ever spend some time on this I'll be grateful, but there's no really need to. Keep up the good job here.
Click to expand...
Click to collapse
I'm not sure what trickster mod writes to, but if you issue from a shell prompt for the franco.kernel derivative:
Code:
echo 1 > /sys/android_touch/s2w_s2s
This will manually enable sweep2sleep, by running your finger from right to left across the bottom navigation bar.
And to enable permanently, add the following file to your /sdcard:
Code:
/sdcard/fkSettings/fks2s
Doing the above will give both (in combination with the widget) of what you are looking for / want (sweep to wake AND sweep to sleep).
JsChiSurf said:
I'm not sure what trickster mod writes to, but if you issue from a shell prompt for the franco.kernel derivative:
Code:
echo 1 > /sys/android_touch/s2w_s2s
This will manually enable sweep2sleep, by running your finger from right to left across the bottom navigation bar.
And to enable permanently, add the following file to your /sdcard:
Code:
/sdcard/fkSettings/fks2s
Doing the above will give both (in combination with the widget) of what you are looking for / want (sweep to wake AND sweep to sleep).
Click to expand...
Click to collapse
I finally did it now I'm able to place both of your widgets in my home (Dt2w and s2w) so I can enable/disable them as I need, plus through the shell and a common file manager it's very easy to set s2s permanently, so I can get rid of hardware buttons once for all and wake/put to sleep the N5 just using the touchscreen. Most importantly, I have zero battery drains with Franco r33 kernel you built to work with the modules, and it's quite an achievement. If you plan on making a donate version I'll be your first paying customer
Inviato dal mio Nexus 5 utilizzando Tapatalk
memnoc said:
I finally did it now I'm able to place both of your widgets in my home (Dt2w and s2w) so I can enable/disable them as I need, plus through the shell it's very easy to set s2s permanently, so I can get rid of hardware buttons once for all and wake/put to sleep the N5 just using the touchscreen. Most importantly, I have zero battery drains with Franco r33 kernel you built to work with the modules, and it's quite an achievement. If you plan on making a donate version I'll be your first paying customer
Click to expand...
Click to collapse
Awesome, glad you got it going!
but you need a custom kernel?
fraussantin said:
but you need a custom kernel?
Click to expand...
Click to collapse
Yes, I've not seen a stock kernel that supports the sweep or tap to wake feature.
I've updated the thread title for those that may not realize this
Ok thanks.
what kind of kernel do you recommend to use to only have this mod?
Thank
So I know I'm not the only one having problems with notifications. The issues I have found with every firmware up to 137 are:
1. Regardless of Doze settings, enters IDLE in five minutes.
2. Sometimes, regardless of Doze settings, never gets out of IDLE into IDLE_MAINTENANCE
So to work around these issues, the only way to do it is to disable Doze. Disabling Doze will potentially cost you battery life, but you will get notifications from email client and any other software, as if it were Lollipop.
So what's a good way to do this easily? Tasker is the best answer I've come up with.
Here are the instructions which worked for me. This has solved all the notification issues I have had, but it's a little bit of a pain.
1. Make sure your phone is rooted. Purchase and install Tasker.
2. Create a task. Action category is Code-> Run Shell. Command is -- dumpsys deviceidle disable --. Check Use Root. Then click the lower right hand corner to make an icon, and go back to Tasks menu. Long press the task you made to highlight it, then choose the menu in the upper right and choose export. Export it 'As App' (it may prompt you to install something)
Run this app every time you start up your phone, or set it to auto run in the app settings. Make sure it has root permission. If you did this correctly, it will disable doze until the phone reboots, and Doze won't interfere with notifications anymore.
Hopefully all these issues get fixed soon!
duraaraa said:
So to work around these issues, the only way to do it is to disable Doze.
Click to expand...
Click to collapse
Have you also tried selecting the Performance plan?
Performance setting still won't work.
Sent from my HUAWEI NXT-AL10 using XDA Premium 4 mobile app
Maybe it can help.
{
"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"
}
Sent from my HUAWEI NXT-L29 using Tapatalk
somboons said:
Maybe it can help.
View attachment 3632622
Sent from my HUAWEI NXT-L29 using Tapatalk
Click to expand...
Click to collapse
How did you get in that setting? I can't find it in my phone 'setting'
snugroho3 said:
How did you get in that setting? I can't find it in my phone 'setting'
Click to expand...
Click to collapse
That is greenify app.
Sent from my HUAWEI NXT-L29 using Tapatalk
Is greenify working ok without xposed?
sure thing, xposed only enables some extra functions. been using greenify without xposed for a long time now
I have to hand it to you. This worked. I was skeptical, but as soon as I disabled doze using this method, all of my notifications became instant. Absolutely no delay. It's a shame to have to give up doze to get notifications to work correctly, but it makes the phone 100% more usable. Thanks, man. This thread hasn't had anywhere near enough attention.
Making apps system apps, whitelisting, performance mode, locking apps in memory, and turning off doze for individual apps (not to mention tweaking the doze settings) - None of that worked. Doze is seriously broken on this phone. None of my other phones on 6.0 have this issue. Thanks for figuring this out. I was going to park the phone until an ASOP or Cyanogenmod ROM came out.
duraaraa said:
So I know I'm not the only one having problems with notifications. The issues I have found with every firmware up to 137 are:
1. Regardless of Doze settings, enters IDLE in five minutes.
2. Sometimes, regardless of Doze settings, never gets out of IDLE into IDLE_MAINTENANCE
So to work around these issues, the only way to do it is to disable Doze. Disabling Doze will potentially cost you battery life, but you will get notifications from email client and any other software, as if it were Lollipop.
So what's a good way to do this easily? Tasker is the best answer I've come up with.
Here are the instructions which worked for me. This has solved all the notification issues I have had, but it's a little bit of a pain.
1. Make sure your phone is rooted. Purchase and install Tasker.
2. Create a task. Action category is Code-> Run Shell. Command is -- dumpsys deviceidle disable --. Check Use Root. Then click the lower right hand corner to make an icon, and go back to Tasks menu. Long press the task you made to highlight it, then choose the menu in the upper right and choose export. Export it 'As App' (it may prompt you to install something)
Run this app every time you start up your phone, or set it to auto run in the app settings. Make sure it has root permission. If you did this correctly, it will disable doze until the phone reboots, and Doze won't interfere with notifications anymore.
Hopefully all these issues get fixed soon!
Click to expand...
Click to collapse
I made and run this app but i dont know If it has root permission and doze gets disable or not. How can i control if it has root permission and doze gets disable or not after i run this app?
HUAWEI NXT-AL10 cihazımdan Tapatalk kullanılarak gönderildi
johnweber7375 said:
I made and run this app but i dont know If it has root permission and doze gets disable or not. How can i control if it has root permission and doze gets disable or not after i run this app?
HUAWEI NXT-AL10 cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
You can check using adb.
I don't have the phone now (it's bricked) so I'm sorry to say I can't be sure the command is right, but I think you should see something like disabled if you run
adb shell dumpsys deviceidle
Then you will know that it worked.
greyhulk said:
I have to hand it to you. This worked. I was skeptical, but as soon as I disabled doze using this method, all of my notifications became instant. Absolutely no delay. It's a shame to have to give up doze to get notifications to work correctly, but it makes the phone 100% more usable. Thanks, man. This thread hasn't had anywhere near enough attention.
Making apps system apps, whitelisting, performance mode, locking apps in memory, and turning off doze for individual apps (not to mention tweaking the doze settings) - None of that worked. Doze is seriously broken on this phone. None of my other phones on 6.0 have this issue. Thanks for figuring this out. I was going to park the phone until an ASOP or Cyanogenmod ROM came out.
Click to expand...
Click to collapse
I spend a LOT of time figuring it out, but it was definitely Doze.
The dead giveaway is that Hangouts (high priority message so Doze doesn't matter) worked fine.
I'm happy it works for you. Let's hope Huawei fixes this. Most Chinese users don't really care about Google Cloud Messaging and get their notifications through other services which Doze doesn't affect, so I'm thinking they're not likely to fix it, but we'll see.
Anyone that disabled doze can check how big of an impact it is on battery life?
Also anyway to fix without root?
I solve this issue by giving priority to the important apps notification and all warking perfect now
My device is L29 with kangvip rom
somboons said:
Maybe it can help.
View attachment 3632622
Sent from my HUAWEI NXT-L29 using Tapatalk
Click to expand...
Click to collapse
Thanks mate it helped me solving the notification issue without needing to root my phone.
This does indeed work. Have a look at this thread as well.
http://forum.xda-developers.com/android/apps-games/root-doze-settings-editor-android-t3235130
I wonder if there is some parameter in an apk or in the kernel I can edit so when you flash a ROM doze is disabled by default.
Thanks buddy for that doze thread!
I disabled hangouts and the battery life got much much better
Other notifications I have set via the settings--->notification panel---->notification manager and set according to the app use
bibiner said:
Anyone that disabled doze can check how big of an impact it is on battery life?
Click to expand...
Click to collapse
No difference at all for me. Standby time is just as good. Huawei's own "Doze" still works if you want it to, also.
bibiner said:
Also anyway to fix without root?
Click to expand...
Click to collapse
Yes you can run that command with ADB without root and it will work just as well. Just be sure to have USB debugging enabled in developer options. The part about root is so that you can use Tasker to automate the process instead.
somboons said:
That is greenify app.
Sent from my HUAWEI NXT-L29 using Tapatalk
Click to expand...
Click to collapse
Thanks for the greenify hint mate!