Related
Which is the best one out there?
On my Hero I used Power Manager and it was ok, but not been updated forever.
Juice defender I wasn't very keen on and i've not found too many other good options.
What is everyone using?
juice defender as it was reccomended. what didnt you like about it?
juice defender works fine for me
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
Are you using the free version or the paid one?
the free one.
There's one handy widget that you can download called "Power Control" from the Android Marketplace. It allows you to toggle wifi, changing backlight and so on the home screen.
It's also been discussed that by applying simple things, like a black wallpaper, can save battery life as opposed to a colour intensive/live wallpaper.
Am i right in stating that it seems that these programs will effect how push emails/messages (GTalk).
It would be good if there was an app out there that changed the connection from 3G to 2G if the screen was off or phone was inactive for x amount of time, this way, the phone can still function as it was designed to and still achieves the goal of saving battery power.
Does anyone know how to control the brightness better in Windows 8? I know that you go and disable/reenable the driver to fix it but I was wondering if there was a more permanent solution, as that is the main thing keeping me from switching completely to the preview as my main OS (with my Win7 partition there for backup)
I am on a 2011 Sony Vaio SA 2.4GHz i5 4GB ddr3 ram, more or less standard
Hope someone has an answer!
Windows 8 DP is not designed to be a main OS. That's why it's a developer preview.
Hover over the Start Button, select settings, and brightness will be one of the settings in the sidebar that slides out.
duh
I KNOW it isn't made to be a main OS, and if you read my post you would've known that. Besides, that's not what I was asking. Most if not everyone using the DP knows how to do that by now.
Please don't reply in such a smug way if you don't know what I am asking
yeh, im having the same problem too, there are some applications online that could do it, but the problem is that it isnt hardware controlled, as in when you use the program to dim the brightness, your actual screen brightness stays the same, i suppose you can call it a tint, but it doesnt effect battery life in anyway, so it is a major issue that microsoft needs to fix fast.
technolust109 said:
yeh, im having the same problem too, there are some applications online that could do it, but the problem is that it isnt hardware controlled, as in when you use the program to dim the brightness, your actual screen brightness stays the same, i suppose you can call it a tint, but it doesnt effect battery life in anyway, so it is a major issue that microsoft needs to fix fast.
Click to expand...
Click to collapse
Your brightness control most likely isn't supported by Windows 8... My software brightness controls change my brightness just fine. Not tinting, I mean actual brightness control.
Brightness Control
GazaIan said:
Your brightness control most likely isn't supported by Windows 8... My software brightness controls change my brightness just fine. Not tinting, I mean actual brightness control.
Click to expand...
Click to collapse
Which software is that?
___________________________________
Phone: LG Optimus V (VM670)
ROM: IHO CM7.2 RC0 MiRaGe build
CPU: 245/768 SmartassV2
Satisfaction:
Hmmmmmm i have no issues with it!
because i have to uninstall the drivers and install them again inorder to use them, is it just for intel Graphics cards? or people haveing issues with AMD and Nvidia cards too?
I can control the brightness just fine after disabling/enabling the WDDM 1.2 Driver
thats not the problem, the thing is, we are all trying to find a way to control it WITHOUT disabling the driver.
no duh
That's the EXACT REASON I posted this question -__-. . . . .
From my understanding, the sensors API and the way OS behaves broke compatibility with the W7/Vista Sensors API, things like brightness sensors and accelerometer drivers need to be rewritten to (properly) support Windows 8, and that will require hardware makers to either do it, or release the specs.
Hello everybody! The purpose of this guide is to show you some free ways to greatly increase your battery life on the Droid X. First this guide assumes you have the Gingerbread kernel, root access, and are comfortable with ClockworkMod Recovery. If you have not installed a few roms, SBF’ed, or backed up your phone, learn how to and practice it a few times. I am not responsible if you fubar and have to SBF your phone. This guide is specifically written for the Droid X, but since the Droid 2 uses the same innards, you can probably use this guide interchangeably with that phone. Not all the steps in this guide only apply to the Droid X so I will say something on the steps that can be used on other Android devices.
First I'm going to start with basic things you do not want to do if you plan on saving battery. (All Devices)
Battery Saver Apps: Battery saving apps like Juice Defender are bad ideas. As I will explain later, many apps expect an always on data connection and prevent your processor from going into deep sleep when they are waiting for that data connection to come back on. Not to mention a battery saver is just another app and service that is running in the background potentially using battery.
Wipe Battery Stats: A Google developer has confirmed that the batterystats.bin does not hold battery calibration information. It holds information to compute battery usage information. The same information you see under “Battery Usage” in settings. Wiping this file just wastes your time.
Hungry Apps: Apps that use excessive notifications keep the processor from going into deep sleep. Facebook is the number 1 culprit here. Go into the app settings and turn of notifications. Use your back button to exit apps when you are done.
Automatic Backlight: On the Droid X, the Automatic Brightness setting is useless. Minimum brightness is too high by default. Either turn it off and set brightness manually or take the step I did that comes up later in this guide.
Wifi: Wifi when you are in range of a router uses less power than your 3G connection and is faster anyways. Wifi when you are not in the range of a router is a battery killer and should be avoided. Use your notification toggles if you have them. Get a widget if you don’t.
GPS: GPS should be turned off at all times unless you are actively using it. Nobody cares where you were when you posted on Facebook.
App killers: App Killers are good for hunting down and killing an app once in a while but are usually pointless. Android automatically loads apps into free memory for quicker starts. Why have your app killer wake up the phone from its idle, kill all of your apps to free up memory, and then have Android automatically reload most of those apps back into memory?
Bluetooth: Bluetooth headsets are best left in the car where you have your phone on a charger. If you need to use one off the charger, don’t forget to turn off your Bluetooth when you are done.
Charging: Charge as often as possible. Follow the same battery saving strategies you usually do when your phone is off the charger. It makes your phone charge faster. Keep in mind the mA rating on the charger. The stock one is 850mA. Do not exceed this rating. USB is ~500mA depending on other devices attached to the computer. The higher the rating, the faster the charge. Do not let the battery get very hot. Do not let your battery level drop below 10 very often. Low charge levels on Li-Ion batteries can damage them. Alternately, do not reputedly plug and unplug your phone once your battery shows 100. Android charges to 100 and lets it use up battery for a few percentages before it starts charging again. This is to prevent overcharging and damaging your battery. If you plug and unplug it repeatedly, it tricks Android into charging it more and more. Keep in mind that li-ion batteries lose capacity over time whether you use them or not. Replace them when they are no longer keeping you happy.
Step 1. Selecting a Rom
Liberty 3 forum topic: http://forum.xda-developers.com/showthread.php?t=1368049
Really for the purpose of this guide the only rom worth picking is Liberty 3. This rom is based on Motorola code which is known for good battery life and has init.d support baked in. It also has the power toggles in the notification bar and has pretty good customization. The 2nd-init roms that have init.d will work too but have issues with battery life. From this point forward I am going to assume you are going to be using Liberty 3 but the steps should work the same for other roms as long as there is init.d support.
Step 2. Installing the Rom
Use CWM to install the rom like you normally would. Start up and follow the usual setup wizard. Once you are able to get to settings, click on Liberty Settings, then Performance, then Start-up Tweaks, then uncheck everything except "Enable start-up tweaks." These settings interfere with the next step and are going to be duplicated by the next step.
Step 3. Install jakebitesmod
Jakebitesmod forum topic: http://rootzwiki.com/topic/3435-mods-jakebitesmods-v18-for-d2-ota-gb-kernel-all-roms-mods/ (Please consider donating to this developer as this script helps a lot of people.)
Jakebitesmod has some good scripts to optimize many things in Android. Pretty much anything that speeds up Android can have a small improvement on your battery life. We are specifically going to use his script to under volt the processor and set the governor at boot without using an app. Copy the linked file to your SD card and boot into CWM again to flash this. Restart your phone like normal.
Step 4. Configure jakebitesmod
Open Terminal Emulator and type “su”. This should prompt Superuser for root permission. Allow the permissions and move on. Type “modcentral”. This should bring up a little text menu of things to do. The menu option we are gonna be looking for is “1”. Read the safety issues and if you want to move forward press “Y”. From here we are going to select “1”. This option will leave you with the stock processor speeds but change the voltages on the processor to lower settings. This is generally safe because lower voltages should only cause problems with freezing and crashing, but should not physically be harmful to the processor. Voltage also makes much more of a difference on power than clock speed so this should save us a good chunk of battery. Push “Y” to continue and set the voltages and speeds at boot. Press enter a couple times and it should tell you it succeeded. Yay. From here we want to go to menu option “3”. Governors control when the processor jumps up or down in speed based on some magic formula that takes into account how much work your processor is expected to be doing. Personally I agree with jakebites and I chose interactiveX. It jumps up in speed fast enough not to appear like the phone is laggy and drops back down fast enough to save battery. It also automatically drops down to the lowest speed while the screen is off. After you have made your choice push “Y” and enter a few more times. Once we are back to a menu we can just hit the back button and exit the Terminal Emulator.
Step 4. Adjusting the Backlighting (All Devices)
The Droid X’s backlight settings is a real pain. The lowest brightness setting it will dip down to is 20. This is way too bright for darkness. You know what I mean if you have browsed at night in bed. Luckily there is an app for that. Download “Custom Auto Brightness” from the Market and install it. It ends up being called LogGraph in the app drawer for some odd reason. Open this and hit you menu key and then select “Preferences”. Select calibrate sensor and follow the directions on the screen. Then go to check brightness range and follow the directions on the screen. Then back out to the main screen and make sure “Demonstrate….” is checked. Push the left “Select sensor reading” and observe the line on the graph move. These are the levels of light the ambient light sensor are going to report at. So say you have the sensor reading slider set to 10. You move the bottom slider to a value of 2. This means that your backlight will be at its lowest level when your sensor says the light in the room is at a level of 10. You can adjust these to what you prefer, but for the best battery savings turn your readings at 1 and 10 to a value of 2. This will keep your backlight nice and low while you are in a dark room but still let your backlight jump up while you are outside. Once these are set head back into the preferences and make sure that all of the checks are enabled except “Foreground mode” and “Bypass hysteresis”. Once that is done hit the back button until you close the app and then turn your screen off and on. If you brightness is way lower than it was before you are golden. If not double check the guide.
Step 5. Install Your Normal Apps (All Devices)
The next steps require your normal apps to be installed and signed into those apps like normal.
Step 6. Set Your Sync Times (All Devices)
Install the app “AutoSync Account Activator” from the Market. Open and accept the agreement. Now you should see some apps listed. I get “Google” and “Facebook” but yours may vary depending on what you have installed. The process should be similar for each app. First off, click on “Google”. The first page called “Connections” lists you connections. Click on connections you would like your account to be able to sync on. Cellular is an obvious one but really you should have your wifi on and have it activated in this while you are home. The next screen, “Periodic Sync”, controls how often your apps sync. Unless you use your Google Calendar often, set that to “1 day”. Contacts should also be “1 day”. Gmail should be set accordingly to how often you care about your email. Others may show up. Set them to according to your judgment. Just keep in mind the more often you sync, the more battery you will use. If you do not use the service at all you can select “No period”. If you have one set to no period you should also set it in the next page to “Always off”. All of the rest should be set to auto.
Step 7. Observing What You Apps Are Doing and What to Do About It (All Devices)
This step is subdivided for the benefit of your eyes.
XDA Edition BetterBatteryStats forum topic: http://forum.xda-developers.com/showthread.php?t=1179809 (The link is at very bottom of 2nd post. Please purchase from the developer on Market if you use this more than a few times.)
A. This final step will ultimately probably figure out why you were getting bad battery. Android’s power management relies on what are called “wake locks”. Wake locks are things apps can create to tell Android’s power management to prevent the phone from going into deep sleep. Deep sleep is a state your processer goes into to basically shut itself off. A good example of a wake lock is when you are playing an mp3 and your screen is off. Normally when your screen is off your device wants to get into deep sleep asap. The audio service creates a wake lock to prevent your processor from entering deep sleep, because this would stop the mp3 playback. Most of the naughty apps out there use wake locks to keep data connections alive and use them to keep updating and keep notifications going. They tend not to give up that wake lock when they should and keep your phone from going to sleep. Apps that shut off your data connection, like Juice Defender, will cause even good behaving apps to freak out and keep their wake locks active while they wait for the data connection.
B. To look for these wake lock hogs we have a couple apps to get. The first one is from the link. It’s the XDA Edition of BetterBatteryStats. The second is CPU Spy from the Market. To use BetterBatteryStats just dump it on your sd card, use a file explorer to open it, enable Unknown Sources, and install it. Then open it, plug in your phone, unplug your phone, and use it like normal for a few hours. When you are ready, open the app, click on the first drop down, and select “Partial Wakelock”. Make sure the second drop down says “Since Unplugged”. Whatever apps are listed at the top are the apps that are keeping your phone from sleeping. My top 3 are DownloadManager (I was using Market and turned off my screen.), PowerAMP scan, and the PowerAMP service, but only the DownloadManager used any significant time. CPU Spy can be used to see how often your processor is going into deep sleep. Once you find your bad apps, you can look around in them and see if there are any settings in there to either turn off notifications, increase the time between updates, or anything else you may think is keeping the app busy.
C. If there is nothing there you can change, you can consider preventing it from starting. If you do not have ROM Toolbox Lite, download it. Open it and click on “Auto Start Manager”. Then scroll the screen sideways to get to the menu that says “Applications”. Click on apps and you will see two actions that we will be looking at. They are “boot completed” and “connectivity changed”. Apps like games, media players, internet radios, Facebook, etc, do not need to be started at boot and do not need to be started when connectivity has changed. Unselecting these will keep apps like Facebook from starting when you turn your phone on and when you switch from 3G to wifi.
D. If you ultimately can’t figure out why an app is keeping its wake lock for so long you may have to consider if the app is worth the lost battery life. Unfortunately there are just those apps out there that are poorly written. Consider sending an email to the developer explaining your problem and ask what you can do to fix it. If they don’t replay politely give them some poor feedback with a good explanation in the Market. They may look into the problem and correct it.
In Closing...
Thanks to everyone for reading, or at least skimming, my guide. I really hope this helps and saves time for a lot of people. If there are any issues anybody runs into I’ll try to help and explain the best I can. I apologize for any mistakes, errors, or bad sentence structure. If anybody has anything to add I will definitely consider adding it as long as it is free, easy to do, and produces results. If I broke any forum rules please notify me before deleting this topic. I’ll be happy to fix the issue.
About wake locks: http://forum.xda-developers.com/wiki/Wakelocks
Li-Ion batteries: http://en.wikipedia.org/wiki/Lithium-ion_battery#Battery_charging_procedure
Batterystats.bin information: http://www.androidcentral.com/wiping-battery-stats-doesnt-improve-battery-life-says-google-engineer
(Edit 1: Added instructions to delete default init.d scripts installed with Liberty. They seem to conflict with jakebitesmod's voltage settings. They didn't want to stick through reboots. All of the script's functions are duplicated by jakebitesmod anyways.)
(Edit 2: Turns out that deleting the init.d scripts isn't needed. Instructions updated.)
Really great advice. I don't even have a Droid X. I have a One X but this is still very relevant.
Thank you
Great guide. You should include CPU Governor such as BoostedASSv2. It helped me get good battery life (as so others).
I want got a Asus ux31 touch in black, and simply love it. There is one thing though, I am to be able to disable the touchscreen because I have heard that there is a very large increase in battery life when you do that. I am just wondering because I went to control panel-hardware and printing devices-pen and touch but there is not option to disable the touchscreen. Is there any program that will do this for you because I heard you can increase the battery life by one hour by doing this.
Typically, that's something you would do either in the BIOS/EFI setup program, or in Device Manager (simply select the driver and disable it, although I can't promise that will give the power consumption back).
There was a setting to disable touch screen on earlier version on windows 8. I don't know why that setting has been removed. Is there any program that disables touch screen?
Sent from my RM-820_nam_att_100 using Board Express
first and foremost, special thanks to alecbl for his initial device tree and kernel source. this build would not be possible without his kernel work.
This is LineageOS 13.0 for the Alcatel Idol 3 4.7" variants
as always, full device, vendor, and kernel trees available at github:
https://github.com/stayboogy/stayboogy_lineage13_idol347
all changes in detail: https://github.com/stayboogy/stayboogy_lineage13_idol347/commits/master
This build is not the same as alecbl's, mine has some various changes to make it a more proper build for this specific device.
Updates will be coming as time progresses and new features are added.
FEATURES:
tap2wake & tap2sleep
double press power button opens camera
triple press power gives brightness boost
call recording available
lineage.yahoo.weather provider now installed by default
notepad included by default
typical apps and functionality of CM / Lineage roms
SPECIAL NOTES
1) wrist/tilt sensor (accelerometer) is used for the missing motion sensor for doze settings
2) speech to text / voice typing requires the Google app and for microphone permissions to be activated in settings/apps/Google/permissions then it will work correctly
3) smart lock settings work and persist over reboots--you must have the play store updated, play store services updated, the Google app installed, and Maps installed for all settings to work in smart lock settings.
4) flip cover has not been activated in the device tree yet--if people want it, post and if enough want it i'll add it back
5) battery light pulse option is no longer available, battery light itself when plugged in is active; notification light pulses by default, it's speed can no longer be edited because it doesn't work correctly--this was an executive decision because i don't like options that don't work correctly, these will not be added back, versions 1.1 and higher are incompatible with 1.0 framework so don't try to replace.
6) selinux is enforcing
RELEASE 1.1
click here
RELEASE 1.0
click here
Hi stayboogy - looking forward to trying this out
Great to see a new dev picking up this device, looking forward to test your work!
sorry last build had an error, new link will be up later tonight
link is live now.
post anything i might have missed. so far i think it is fairly polished
@stayboogy - I'm Testing it now - No root access for apps ? only adb option.
k500zm said:
@stayboogy - I'm Testing it now - No root access for apps ? only adb option.
Click to expand...
Click to collapse
not missing, that's how modern security works and should be.
install superuser from recovery, that's standard mode of operation for everything after kk.
@stayboogy , Will you build lineage os 14.1??
A few issues I found on my day using this rom, I will provide logs on monday if you need, I'm out for the weekend and don't have a pc right now.
-Sometimes the power button instead of locking the device it boosts the screen brightness to max for a few seconds.
-I still find the smartlock issue with bluetooth devices, I do have google app and maps installed
-WiFi speed seems lower than on other devices connected to the same network, but since I'm not on my own house it might be a network issue, will confirm this when I get back home.
Phantom410 said:
A few issues I found on my day using this rom, I will provide logs on monday if you need, I'm out for the weekend and don't have a pc right now.
-Sometimes the power button instead of locking the device it boosts the screen brightness to max for a few seconds.
-I still find the smartlock issue with bluetooth devices, I do have google app and maps installed
-WiFi speed seems lower than on other devices connected to the same network, but since I'm not on my own house it might be a network issue, will confirm this when I get back home.
Click to expand...
Click to collapse
1) you're double pressing the power button then, and you have the "double tap power to open camera" option off in settings/buttons/
--either stop double pressing the power button which is what boosts brightness
--or turn on double press for camera option to turn off brightness boost
--or stop double pressing your power button
--pressing once will NEVER EVER produce brightness boost--i've been using the rom since before it was released so i'm sure of this
--your power button may be worn and more susceptible to register a double press when it wasn't
2) smart lock works for me in every option--make sure you're not using some crappy third-party lockscreen app or lockscreen security app that could be interfering with this.
--also there is a slight bug where bluetooth devices that are paired are not remembered upon a power cycle--i'm working on this as i type
3) this must be where you are--i have no issues whatsoever regarding wifi or networks period. of course i have 1GB/min speeds on bad days, and 2GB/min speeds on good days so idk
Thanks for Sharing, and this is the correct way for people to voice their finds and opinions, so thank you for that
alecbl said:
It does not have it by default but retains the option to enable it. I have enabled it. The day cyanogen/lineage starts needing to be rooted is the day I start building some other rom.
Click to expand...
Click to collapse
A message from alecbl from his build....
k500zm said:
A message from alecbl from his build....
Click to expand...
Click to collapse
you're arguing about nothing--engineering builds (ie. lineage_idol347-eng) are the only build that will have su enabled for apps and adb by default
userdebug builds and user builds do not have this enabled by default--only adb root access is made available standard by the system in developer settings.
again, the freaking su is NOT MISSING. I chose to leave the system as it is, because that's how it's supposed to be, and your problems are just stupid childish whining because you don't how current android works.
if you want root, use superuser from recovery which again is standard operating procedure for everything after KitKat. why you can't get this through your thick ****ing skull is beyond me. you obviously are not a developer and have no business making any claims as to what is standard or what is the right way for a rom to work when you aren't building any and have no experience or even basic knowledge of how the build system works or the hundreds of security revisions that have been introduced since kk that make non-systemless rooting a vulnerability...
stayboogy said:
1) you're double pressing the power button then, and you have the "double tap power to open camera" option off in settings/buttons/
--either stop double pressing the power button which is what boosts brightness
--or turn on double press for camera option to turn off brightness boost
--or stop double pressing your power button
--pressing once will NEVER EVER produce brightness boost--i've been using the rom since before it was released so i'm sure of this
--your power button may be worn and more susceptible to register a double press when it wasn't
Click to expand...
Click to collapse
Yeah, it's most likely my button being worn out, because I had disabled the double press to open camera since it was randomly opening when I pressed the button, I just didn't know double press for brightness was a feature (it's a useful one actually)
2) smart lock works for me in every option--make sure you're not using some crappy third-party lockscreen app or lockscreen security app that could be interfering with this.
--also there is a slight bug where bluetooth devices that are paired are not remembered upon a power cycle--i'm working on this as i type
Click to expand...
Click to collapse
After every power cycle I get the notification to pair it and confirm that the codes match and on the bluetooth device itself I get a new 6039A device on the paired devices list after it happens, so it might be that issue you mentioned. (I attached a pic of how the devices list looks on the bluetooth device)
Thanks for Sharing, and this is the correct way for people to voice their finds and opinions, so thank you for that
Click to expand...
Click to collapse
Well, I know and appreciate the free time from your daily life you take to develop and share your work. Hopefully certain type of entitled idiots who think they deserve everything their way and for free don't discourage you to keep up with your amazing work!
Versions 1.1 release
download link the OP
hopefully bluetooth paired devices retention is working now
stayboogy said:
Versions 1.1 release
download link the OP
hopefully bluetooth paired devices retention is working now
Click to expand...
Click to collapse
Is now camera included?
I think there is some confusion among users a camera is included just not the stock one
stayboogy said:
I think there is some confusion among users a camera is included just not the stock one
Click to expand...
Click to collapse
I was talking about stock camera, sorry for the omission
USB bug
After installing I cant transfer files from my device to pc.
In developer options you cant change the USB option from just charge to MTP, PTP or any other it stays in just charge
UPDATE: At the USB Configuration select MTP and keep touching the option to change it
NOTE: Enable Developer options before connecting the device for the first time to the pc
BlackDantex said:
After installing I cant transfer files from my device to pc.
In developer options you cant change the USB option from just charge to MTP, PTP or any other it stays in just charge
UPDATE: At the USB Configuration select MTP and keep touching the option to change it
NOTE: Enable Developer options before connecting the device for the first time to the pc
Click to expand...
Click to collapse
yes, i'm aware you can't change in developer options while it is not attached to pc,
and it bugs out sometimes when it's attached to pc
--this is a problem in the lineage source, not the device tree and therefore out of my control
--use the notification in the status bar to choose how you want the device to connect PTP, MTP, Charge only--this works perfectly and as expected
Somewhere along the way, CM/Lineage has messed with the Bluetooth stack in the source code, and there seems to be possibly some missing component service that needs to be running in order for fine location access to be given to bluetooth in order for it to work correctly, and this is also related to smart lock.
at this time, upon every reboot of your device, you will have to re-pair any bluetooth device you have used previously. auto-connect is broken in the bluetooth service stack somehow. also, your device is created anew each time it is rebooted due to a security measure enacted by google a while back that randomizes your bluetooth mac address so that your device location can't be sniffed by third-party apps. there's a whole long bulletin about it somewhere, but i guarantee this is why bluetooth auto-reconnect is broken after a power cycle.
i have discontinued all use of lineage 13 personally because of this reason alone.
i'll still be work on this rom though.
just don't expect a fix for bluetooth from me because it will have to come from upstream aosp and then made known to everyone.