5 Ways to Improve Battery Life on Android KitKat

There I was, showing off my new HTC One to a friend when “plink!” the low battery alert sounded. Considering it wasn’t yet lunchtime, this was potentially embarrassing. With under 20% charge left, I had to act fast.

Charging An Android KitKat Phone

Getting the phone charged up was my priority – but what could I use?
Looking around, I saw a wall outlet, and my USB adaptor just happened to be in my bag (not a surprise, as I also carry a Surface Pro in there). Fortunately, throughout the demo I was able to keep the phone plugged in and charging as I showed off photos, videos, games, and the slick HTC Sense 5.5.

Heading back home, I decided to keep the phone charging in the car. Using my cigarette lighter-powered charger, I found that rather than charging the phone at the usual rate, the charger was giving a current akin to the trickle charge that you get from USB connectors on your desktop computer.

That is, a charge that wasn’t going to make any considerable impact on the low battery.
It was then that it struck me. A couple of weeks into life with my new phone – and new to KitKat – it was time to start managing its battery use more effectively.

Using A Battery Saver Mode

Although unavailable on stock Android 4.4 KitKat devices (rather limited to OEMs like HTC and Samsung, such as the HTC One and the Galaxy S5, which has Ultra Power Saving Mode), using the built-in battery saver tool was my first port of call.



You can open Settings > Battery Settings > Power on some devices (labelling can differ from manufacturer to manufacturer) to check your battery level and to activate Battery Saver mode. The HTC Battery Saver mode is configurable, enabling you to enable or disable further elements such as your data connection, vibration feedback, screen brightness, and CPU usage.



Meanwhile, use the App Usage list (or equivalent) to find out which apps are using resources. These can be tapped to open their app details screen, and the app can be disabled if required.
If your Android 4.4 KitKat device isn’t a Samsung or HTC, you’ll need to find a battery saver app in the Play Store.
DU Battery Saver and Battery Doctor should be the first apps you try, both of which have been updated and optimised for KitKat.

Managing Connectivity: Location Mode

You should probably be aware that one of the key causes of low battery on your Android device is connectivity.

GPS, for instance, is used widely these days with many apps taking advantage of localization data to serve information based on your current whereabouts. This can prove hugely convenient or terribly inconvenient, depending on when you need to use your phone.



Introduced in Android 4.4 KitKat is the Location mode screen, a feature that enables you to select the accuracy of your localized data, with the least accurate method using only GPS and less battery than the most precise option, which employs Wi-Fi and mobile networks. The Location feature can also be disabled.
Other battery savings can be made by using Wi-Fi over mobile Internet. Although a good option, even in 4G areas, be aware that open wireless networks are almost always non-secure, so don’t use these connections for any sensitive tasks such as online banking or shopping.
Using a tool like Trigger to switch to favourite Wi-Fi networks instead of your mobile Internet automatically as soon as they are in range can help here.

Deal With Always-On Wi-Fi Scanning

As well as switching off Wi-Fi when no connectivity was needed, I also discovered that there is an additional wireless networking setting that can also contribute to battery drain. Hidden away in the Settings > Wi-Fi > Advanced menu is a feature that helps your phone’s location be pinpointed by apps, games, and Google Play.



Disabling the Scanning always available feature will help reduce the speed with which your battery runs down, but it will also reduce the effectiveness of Google Now.

Google Now Launcher: Killing Batteries?

The “OK Google” voice control feature of Google Now is probably its most popular and visible element, but the app is constantly busy working away in the background to find information that it deems relevant to you based on your profile.
So if you’ve already disabled its ability to accurately determine your whereabouts, why not go further and reduce its impact on your battery further?



You should probably know already that the “OK Google” hotword can be disabled. If not, head to Google
Now, scroll down to the bottom and tap the menu button to open Settings. From here, tap Hotword Detection and switch to Off.



What you may not know is that the whole Google Now service can also be disabled. Via the same Settings menu, toggle the Google Now switch to disable the service, then Turn off to confirm your choice. You might also check the box to delete location history.

Note that if this seems too extreme, you can skip this and leave Google Now activated but with limited battery impact (and relevance from the information it finds for you) from the disabled location services.

Don’t Use ART To Reduce Battery Use

Introduced with Android 4.4 KitKat is ART, the Android Runtime that is included as an alternative to the default Dalvik runtime. We previously explained how to enable ART, and the potential speed improvements of doing so, but if you’ve followed that guide or any similar steps to switching your KitKat’s runtime to ART, you may have unwittingly made your battery run down quicker.



At this point, the jury is still out on ART, but that shouldn’t matter at this stage as it is a beta runtime, not yet intended for full production use. Although many apps may launch and run quicker, impact on battery drain overall is unclear, based largely on what apps and services you use.

If you’re looking for a “hacker’s option” for reducing battery use in Android KitKat, why not install a custom ROM with built-in tweaks? There are guides here on MakeUseOf for installing custom ROMs, and once you’re familiar with the basics you will find further help – and custom ROMs to download and flash – at the XDA-Developers forum.

You Shouldn’t Be Recharging Twice A Day!

The tips listed here are specifically for Android 4.4 KitKat devices. Battery saving tips for earlier Android versions may also work.

Ultimately, you shouldn’t be charging your phone more than once a day; you could even squeeze two days out of some phones with moderate use. Since disabling Google Now alone, my HTC One runs for an additional 2-3 hours on average – not a bad result.
How often do you recharge your Android 4.4 KitKat handset? Let us know your thoughts below

android Ember CM11 AOKP Theme

Ember CM11 AOKP Theme

Apply the system theme and reboot. Now select my theme & apply.
You may get an error: 'Sorry, this theme is missing assets for your device's screen size'.
Ignore that and apply it anyway and REBOOT.CM9 CM10 CM10.2 CM11 & AOKP THEME
ROOT and a custom ROM like CyanogenMOD needed.
For HDPI,XHDPI and XXHDPI phones only.
This a minimalistic matte grey colored theme.
This theme has xxhdpi(1080p) assets and will look sharp on newer 1080p resolution phones such as Galaxy S4, HTC One, LG G2 and Nexus 5 etc.
The battery icon cannot be themed in Kitkat 4.4.

 

 Download them 


For search: Android Ember CM11 AOKP Theme, android, theme, free theme, themes, theme for android

Online Petition by Google Nexus KitKat Contest Winners

Last week, we reported how two winners of the Kitkat Nexus contest were unfairly rejected by Nestle India. And now other winners across the country are supporting Mayur Patil and Parimal Sen with an online Petition asking Nestle India to give them their rightful prizes.

The petition filed at Change.org is seeking 1000 signatures and is quickly gathering supporters with many winners signing it. The petition says the agency handling the contest (GroupM India) along with Nestle, has not managed the documents and wrappers properly which has ultimately led to Mayur and Parimal getting disqualified. Many have been supporting the cause and posting on Kitkat's Facebook page, but have received no response from Nestle India or GroupM so far. 

Through this online petition, supporters are hopeful that Nestle would take the right steps and quickly send out prizes to these two winners who have been anxiously waiting. ComboUpdates has been following this contest right from the start and we request Nestle India to be just and fair to these deserving winners.

You too can do your bit in helping them get their prizes. Sign the online petition on Change.org
Link: https://www.change.org/en-IN/petitions/justice-for-kitkat-nexus-7-contest-winners-of-india

Do your bit now !!!

Nestle and Kitkat mess up the contest again...two participants are denied their just and legal prize

The Google Nexus KitKat contest which started in India in September 2013, has still not been brought to its logical conclusion. Many Winners are yet to receive their Google Nexus 7 2013 as promised by Nestle Kitkat.  

It has been a extremely controversial contest right from the start, with its organisers facing a lot of complaints and to an extent even online campaign from winners who are extremely unhappy with the way the contest has been organized by Nestle India, Google and managed by  GroupM Media, Gurgaon.

As the readers must be knowing, Nestle in assistance with a organising agency called GroupM had organised a campaign to coincide with the launch of Android 4.4 KITKAT in India.

Now Nestle India and the KitKat winners team are gearing for another battle, where two winners of the competition, Mr. Parimal Sen and Mr. Mayur Patil’s contention and claim have been rejected after waiting for their prizes for nearly more than four months. When contacted, Nestle have said that “According to the  Terms and Conditions the wrapper of the winning KitKat bar must be included along with the documents sent by winners”.  Nestle allegedly say the wrappers are missing for these two winners and hence has cancelled the claims of the above two contestants. 

But according to Parimal and Mayur, they had sent the winning wrapper along with the documents as directed by Nestle in their Terms & Conditions, which have reached the Nestle /GroupM office as seen in Courier details below.

Mayur had a discussion with the Nestle customer care Exec and here is a Youtube video giving the audio transcript of the conversation which occurred.

Despite of the fact that both the contestants have proof of their respective packages reaching Nestle/GroupM, the organizers claim that they have not received the same and have been asking both these winners to send to all over documents again. This shows a lot of inconsistency on part of the organisers including the top Kitkat hierarchy, where at one end the winners are producing Courier Tracking proofs showing the documents have been delivered and at the other, the organizers,  Nestle/GroupM is allegedly not received their packages.   Rather than solving this problem amicably, the organizers, who have already faced a lot of heat on account of discrimination against Indians are persisting with their stand, thereby resulting in both Parimal and Mayur not getting their genuine prizes.

Both the winners also said Nestle made them wait for more than four months before informing them about the above package problems.  It seems that the organizers deliberately dragged the issue to such an end that they were sure other winners would have received their own Google Nexus 7 2013 and lost interest about the contest.  Nestle/GroupM informed both Parimal/Mayur only on 6th Feb of their alleged non receipt of packages, a whole 4 months after the contested was concluded,  A long wait as this for any contest winner can be frustrating,  especially when you come to know that you are disqualified only at the end.

Such a controversy is not the first to hit Nestle India during the Contest. Neslte India were previously giving winners a year older version of the Nexus 7, after winners came together and protested and the incident being reported by various Top blog sites including comboupdates, Android Police, Phandroid. Nestle took cognisance of the huge uproar this created and backtracked on its decision and decided that Indians would indeed be getting the latest version of the Google Nexus 7 like the winners in other parts of the world.

Another inconsistency noted is the very poor communication or sometime lack of it on behalf of the organizers.  Also the use of English language in the communication has been very horrible with emails coming from a not so professional id ‘nestlekitkat1@gmail.com’. See this for example:

The Facebook group created by the Google Nexus 7 2013 winners to fight against the discrimination pointed out above, is again up in arms for their comrades.  Comboupdates sincerely hopes that Nestle/Kitkat would heed to the requests of the two winners and despatch their prizes to them immediately.  It would be a great sorrow if Nestle were to disqualify these two by hiding behind the excuse of some stupid mistake on part of the desk clerk sitting at Despatch of Group M.

Android 4.4.2 KITKAT leaked firmware I9505XXUFNA1 now available for Samsung Galaxy S4 GT-i9505

Samsung may release the Android 4.4.2 Kitkat firmware for the Samsung Galaxy S4 at its own leisure but the Sammobile guys have released a leaked stable firmware for it.  The firmware having No.I9505XXUFNA1 is now available for your Samsung Galaxy S4 Model GT-i9505.

To install the leaked firmware you have to visit the Sammobile website for instructions.  Kindly remember that this is a leaked version and not official version of Samsung.  Samsung will be releasing the final firmware of Android 4.4.2 Kitkat within the month end.  So if you are not familiar with the rooting process do wait until the official copy is out.

For those who are interested in this firmware, this is the first Android 4.4.2 KitKat test firmware for Samsung Galaxy S4 so you might be the first ones to use a Android Kitkat operating system on your S4.  Do remember this firmware is for the Samsung Galaxy S4 GT-i9505 popularly known as the European version.  

As per Sammobile, this test firmware has been in testing for several days and is pretty stable.  The firmware update will bring some minor UI changes like new status bar icons to your Samsung Galaxy S4.  But the essence of upgrading to Kitkat really lies in the overall improvement in the way your S4 will work.  The benchmarks have established that the new firmware is far better than Android 4.3 now running on your S4.  You will also get a new keyboard from Samsung alongwith this firmware.  The new keyboard is more fluid, easy and gesture friendly.  In the camera options, Samsung has now included a camera shortcut directly to your lock screen so you have that extra second to click that awesome snap.

Additionally you will get all the features that the Android 4.4 Kitkat will bring to table.  

Enhancing the speed and Extending your battery life in Android 4.4 KITKAT using the AndroidRunTime (ART) instead of Dalvik runtime

One of the few things that the latest release from Google, the Android 4.4 KITKAT has brought to the table is a nice option to choose the runtime you want for your Android device.  Earlier Android versions upto the Android 4.3 used the Dalvik runtime. But with this release Google has given users options to choose between the AndroidRunTime (ART) or Dalvik Runtime.

Before you select your runtime, here a background check on the runtimes. The AndroidRunTime (ART) is available only on Android 4.4 KIKAT version so its good for you if you have a Nexus or Google Play Edition device or have customised your ROM to Android 4.4 KITKAT.  It is important to note that Dalvik will remain the default runtime on Android smart phones for a foreseeable future.  If you manage to delete the Dalvik runtime somehow you risk breaking your Android implementations and third-party applications (there are many Apps which dont support ART as of yet)

Of the two runtimes are now available, the existing Dalvik runtime filename is libdvm.so and the ART is libart.so. A device can be built using either or both. (You can dual boot from Developer options if both are installed.)    Dalvik which is named after a Icelandic village, has been the default runtime ever since Android OS was launched.  AndroidRunTime or ART has been developed and introduced with Android 4.4 KITKAT and may soon be the default runtime in future Android versions.  

ART has a distinct advantage over Dalvik because Dalvik runs on the principle of 'Just-in-time' (JIT)  to compile a process which means it has to transform app source code into an executable program every time it starts.  Whereas the newly developed ART uses the mechanism called 'Ahead-of-time' (AOT) process for compilation.  In layman language this means that the ART does the compilation or conversion only once when the App is installed where as the Dalvik converts the Apps everytime you switch them off and on.  

Using ART, a specific App can get launched or converted twice as quickly as the existing Dalvik conversion.  In non technical terms this means that your Apps open up in a jiffy using ART giving you not only better speed but also extended battery life. The side effect of one time AOT processing makes your Apps launching a less resource intensive.  Which in effect means that your smart phone doesnt have to work that hard and this increases the battery life. The advantages of using ART may not be immediately visible to you but over time you will notice significant change in your battery charging structure as Apps which run in the background will now do so more efficiently.

Though it is being touted by the developers as the future of runtimes on Android devices but it does have some distinct disadvantages over Dalvik. One of the worst disadvantages is that it is a storage hogger.  Yes due to its AOT process compilation, it will cause your installed Apps to use more storage unlike Dalvik which has a on-demand need for space.  The rough cost estimate is that it will eat around 10 to 20 percent more space per App.  So, the users who have their smart phones filled with Apps and Games may not like this fact.   Larger Apps and Games means they will also take a little longer to install and you will get a inflated internet bill in case you are using limited data plans.  There is also a case for incompatibility. The older Android Apps just cant run on ART.  It is fine in case of big Apps like WhatsApp, Instagram etc. which are updated regularly but what about the small Apps launched by indie developers.  You certainly cant use them unless the developer updates them for AOT runtime.   Google has made things easy for users by putting out a list of ART compatible Apps. You can read the full list here.

Now that you have understood what AndroidRunTime (ART) is you can give it a try by heading over to Settings > Developer Options > Select Runtime > Use ART (AndroidRunTime)

If you do give it a try, come back here and tell others about how you felt using ART.

Easy step guide to install the new CyanogenMod CM 11 Nightlies on your Nexus 7 2013 Wi Fi tablet

No techie in their right mind likes the default Android interface provided by Google.  The Nexus 7 2013 is a fabulous piece of engineering but to master its full potential, you need to root the tablet.  CyanogenMod CM 11 Nightly for Android 4.4.2 KITKAT has been released and is pretty stable version.  So if you are really into rooting your Nexus 7 2013 and installing the best CM there is on it, read on.

First and foremost you have to root your Nexus 7 2013 and it is a very easy process.  To root it you should download this two files

1. TWRP Image if you want earlier TWRP images visit this site

2. SuperSU (This is the latest one kindly visit this page to read more)  

Now that you have downloaded the above two files, you should back up your Nexus 7 2013 before you embark on any adventure. Back up your contacts using your Gmail account, back up your SMS, images, songs, settings etc.  Also ensure that your Nexus 7 2013 is fully charged up before you begin this process.

Next head over to the Settings Menu in your Tablet to enable USB debugging. 

“Settings > Applications > Development > USB debugging”

Once you have enabled the USB debugging proceed as under. 

Copy the TWRP image into the fastboot folder, and the SuperSU into the device’s internal memory, then turn off your device.

Boot your Nexus 7 into Fastboot Mode by pressing and holding Volume Down and Power keys together until some text appears on screen.

Connect your device to your PC and open a command prompt in the fastboot folder (hold Shift and Right-click on desktop and then choose Open Command Prompt).

Type : fastboot flash openrecovery-twrp-2.6.3.1-flo.img (or change the image name to whatever image you may use)

Once the command is executed, choose RECOVERY from Fastboot menu and enter Recovery Mode.

From there choose Flash Zip from SD card, and choose the SuperSU zip file that you had copied into the memory earlier.

Once the process is done, select go back, and then “reboot system now”.

Once the device reboots, congratulations, you have rooted your Nexus 7 2013. In case you get stuck in the process just long press the power button and follow the process again.

Now that you have rooted your Nexus 7 2013, you can install the CyanogenMod CM 11 Nightly very easily.  To do so you have to download this two files :

1. Nightly Custom ROM (This is the latest one, you can download the older one if you wish from this page but the latest the merrier)

2. Android 4.4 GAPPS package

Once you have downloaded the above two files, lets proceed with putting the CM11 Android 4.4.2 Nightly on your Nexus 7 2013.

Connect the tablet to your computer. Move both zip files to the tablets internal storage. After the files are copied, disconnect your tablet from your computer. Don’t unzip any of the files.

Power off the tablet.

Boot your 2013 Nexus 7 into recovery mode. Make sure that you are using the most recent version of your preferred custom recovery so that it will be able to flash Android 4.4 ROMs.

To be safe, create a NANDROID backup. Just tap on Backup and swipe to confirm the process. (Those using ClockWorkMod recovery can tap ‘backup and restore’, name your file, and save it)

Factory reset your tablet. For TWRP: press Wipe, then swipe to confirm. For CWM: select ‘wipe data/ factory reset’, confirm.

Install the CM11 Nightly ROM. If you have used the TWRP as I have said above, you need to press Install, browse and go to the CM Nightly Zip File you have saved in the internal storage and then swipe to confirm installation.  Those using CWM to root their tablets : tap ‘install zip from sdcard’, then ‘choose zip from sdcard’ and navigate to the CM 11 Nightly zip file. Confirm to install.

Install the Gapps zip after the new ROM is installed. Like above TWRP: press Install, find Gapps zip, confirm the process; CWM: select ‘choose zip from sdcard’ once again, find the Gapps file and confirm the process.

When both files are installed, come back to the main recovery screen and reboot your tablet (TWRP: press Reboot, then System/

CWM: select ‘reboot system now’)

Congratulations, you now have the CyanogenMods CM 11 on your Nexus 7 2013. You can now use the Nexus 7 2013 to install your choicest Apps, launchers, themes and other goodies.

Disclaimer : Rooting voids warranty and may brick your Nexus 7 2013, the above information is given for educational purpose only.  comboupdates will not be responsible for any mishap that occur.

United States users get Android 4.4 KITKAT update for their Motorola Droid ULTRA, MAXX and Mini and firmware update for Samsung Gear

Users in United States owning the Motorola Droid Ultra, MAXX and Mini are getting a Christmas present from Verizon.  It has announced that the owners of Droid Ultra, MAXX and Mini are getting Android 4.4 KITKAT update for their smart phones.

Verizon posted this message on Twitter announcing the phased updates for the above phones.

Starting today: Android 4.4, #KitKat is being pushed out in phases to #DROID Ultra/ Maxx/Mini http://t.co/mM9owtBrg0 pic.twitter.com/pdv1Ywts6K
— Verizon Wireless (@VZWnews) December 19, 2013

You can visit this website get further detailed instructions on updating your smart phone

support.verizonwireless.com/support/system_update/droid-maxx.html

The sad news is that there is no mention of Motorola Razr in the scheme of things.  Anyways, Droid ULTRA, Droid MAXX and MINI users can get their smart phones updated.  Among other things update also adds the new Droid Zap sharing utility with a new UI.  

In a separate news, Samsung has also announced the firmware update for its flagship smartwatch, the Samsung Galaxy Gear.  The firmware update which was already available for Europe much earlier has now come to the US shores.  The change log states the following changes

Improved range and connection: Samsung says the Gear can now stray a little farther from the phone before losing its connection. That’s good — it felt pretty short before. The automatic connection feature has been improved as well.

Improved battery life. Again, that addresses one of the chief complaints about the Gear. We’ll have to see how much longer it lasts.

S Voice search should be faster.

Your Gear’s performance has been improved and its features have been enhanced.

If you own a Samsung Galaxy Gear, you can update the firmware through the App on your device.  If you fail to get the device updated, you can use the Samsung KIES PC software via USB without any problems