Google Android power saving tips

battery

It’s a common complaint (or misconception?) that Android devices are power hungry, and some people claim not to manage a full working day from their smartphone.

By my reckoning default system settings and apps are often configured to showcase capabilities, rather than optimise usage and resources for individual needs. With a few minor tweaks you can reduce overall power consumption and in some cases gain hours extra battery life.

First of all I hope it goes without saying that you should switch off connectivity features that you’re not actively using. You wouldn’t leave a light on at home all day, and in the same way being conscientious about managing Wi-Fi and Bluetooth connections can make a big difference to the power consumption of your device.

I don’t generally use Wi-Fi when I’m away from home, so I use an event driven task manager (Locale) to automatically switch Wi-Fi off for me when I leave my home geo-fence.

For when you do use Wi-Fi, check that you’re using these settings:

Settings > Wi-Fi > Advanced > Network notification > OFF

Settings > Wi-Fi > Advanced > Wi-Fi optimisation > ON

Most people rarely (if ever) use the NFC or Android Beam feature, so don’t leave it switched on permanently:

Settings > Wireless & Networks > More > NFC > OFF

If like me you travel on public transport then your device will frequently leave cellular network coverage. When this happens it will scan frequency ranges for available operators and consume significant battery resources in doing so. Below are some tricks that help to minimise this.

Unless I travel abroad I spend all my time on my home cellular network, so I manually select my mobile operator to prevent unnecessary registration attempts:

Settings > More > Mobile networks > Network operators > Search networks > manually select your mobile network operator

I also lock my device to use WCDMA (3G) only so it doesn’t try scanning the GSM (2G) bands. This is a bit extreme, but if you want to do this use the Android Field Test menu:

Go into the Phone app and tap in this code: *#*#4636#*#*

You will be presented with a ‘Testing’ screen. Tap on ‘Phone information’, scroll down to ‘Set preferred network type:’ and select WCDMA only.

This network settings change will remain until you next power-cycle your device.

Sound and display settings can also make an appreciable difference if you spend a lot of time tapping away on your device. Since haptic feedback uses a tiny vibration motor, switching it off altogether can save precious battery power. Using a static image for your background instead of a fancy ‘live’ wallpaper also saves CPU cycles.

Settings > Sound > System > Dial-pad touch tones > OFF

Settings > Sound > System > Touch sounds > OFF

Settings > Sound > System > Screen lock sounds > OFF

Settings > Sound > System > Vibrate on touch > OFF

Settings > Display > Brightness > Automatic

Settings > Display > Wallpaper > choose a static wallpaper

GPS and location lookups are a big cause of battery drain. If you only want to know your location when you actually need it, switch off Google’s location tracking and the location feature of any other apps you have installed:

Apps > Google Settings > Location > Location History > OFF

Apps > Twitter > Settings > Location > OFF

Popular apps like Play Store and Twitter usually default to synchronising data in the background. If you’re only interested in checking for updates when you open an app, switch off notifications and background usage:

Apps > Play Store > Settings > Notifications > OFF

Apps > Play Store > Settings > Auto-update apps > OFF

Settings > Accounts > Google > disable any data synchronisation that you don’t use

Apps > Twitter > Settings > (account) > Sync data > OFF

Apps > Twitter > Settings > (account) > Notifications > OFF

Finally review your widgets and remove those that you don’t need. Often replacing a widget with a shortcut to the app is just as effective and much more power efficient.

By using all these optimised settings I easily manage 24 hours from my device, with no compromise in functionality of performance.

Advertisements

Google Play Music: Saving to SD card

Having switched from Amazon MP3 to Google Play Music, the most annoying omission in Google’s offering is the inability to save music tracks to SD card instead of internal storage.

Since version 5.1 of Play Music the capability is actually there, although the feature has not yet been exposed via the user interface. Here’s a neat trick you can use to switch it on manually.

First you’ll need to make sure you have the latest version of Google Play Music, then download and install the free Apex Launcher app from Google Play.

After Apex Launcher has been installed, fire it up and you’ll see a new and hopefully fairly empty home screen (don’t worry, your existing home screen has not been lost!). Tap and hold on the home screen, select Shortcuts and then Activities.

Scroll down until you come to Google Play Music, then tap on it to expand to a list of activities. Scroll down until you come to .ui.SDCardSelectorActivity, tap on it and you should find a new Google Play icon appear on the Apex home screen.

Tap on this new Google Play icon and you’ll be presented with a ‘Download Storage Location’ dialogue box. Simply tap on ‘SD card’ and you’re done!

You can now uninstall Apex Launcher if you wish.

Although the switch has been made, it only applies to music that you ‘Keep on device’ from now on, so you’ll need to unpin and pin all your previously downloaded albums again to move them to SD card.

I’m guessing Google will expose this new capability in a future update, but for the time being this is a very welcome workaround.

In case you’re interested, the saved files are stored on your SD card in the Android/data/com.google.android.music/files/music folder.

Smart bins are watching you

timthumb

It’s intriguing how news stories can bubble under the surface for a while and then explode into the public eye, with significant consequences for everyone involved.

Today’s example is the case of the Renew London waste recycling bins, which have been appearing on City of London streets since January 2012. As well as being a regular waste bin they are equipped with a large screen on each side for displaying digital advertising.

Up until recently that’s all we thought they did, until an article in Quartz magazine brought a darker side to the public attention.

Up to a dozen of these smart bins have been secretly scanning for passing mobile devices and storing this data to compile a database of the movement of individuals around the City of London. All of this was done without consent, although the trial details have been published on the Renew London web site.

How do they do this you might be wondering? Every device capable of using Wi-Fi has a permanent hardware (MAC) address which uniquely identifies the device and often even the make and model. If your mobile device has Wi-Fi enabled then your unique MAC address is broadcast periodically when your device scans for access points.

The Renew London smart bins can listen out for these signals and record the MAC addresses that it ‘sees’. According to the published trial data they captured nearly a million devices on just one day in June!

They would probably still been doing this if it wasn’t for the sensationalist claims from the Renew London CEO Kaveh Memari, who went a little too far in explaining just what his technology is capable of.

Memari said he was working on a proposal for a bar that would install five tracking devices: one by the entrance, one on the roof, one near the cash register, and one in each of the bathrooms. That would allow the bar to know each person’s gender (from the bathroom trackers), how long they stay (“dwell time” is the official metric), and what they were there for (a drink outside or a meal inside). And targeted advertising for the pub could follow those people around London on Renew’s omniscient recycling bins.

It would seem that the City of London Corporation was not aware of exactly what Renew London had been up to and the adverse publicity has caused them to swiftly deal with the situation.

THE collection of data from phones and devices carried by people passing sophisticated waste bins in Square Mile streets should stop immediately, says the elected City of London Corporation, which provides local authority services to the global business district around St Paul’s.

A spokesman said (Monday): ‘We have already asked the firm concerned to stop this data collection immediately and we have also taken the issue to the Information Commissioner’s Office. Irrespective of what’s technically possible, anything that happens like this on the streets needs to be done carefully, with the backing of an informed public.’

The bombproof waste and recycling bins, which also carry TV screens with public information, were installed as a way of re-introducing waste bins to City streets.

‘This latest development was precipitate and clearly needs much more thought – in the meantime data collection – even if it is anonymised – needs to stop,’ added the spokesman.

An official statement from Mr Memari has also confirmed a cessation of the ‘trial’:

During our initial trials, which we are no longer conducting, a limited number of pods had been testing and collecting annonymised and aggregated MAC addresses from the street and sending one report every three minutes concerning total footfall data from the sites.  A lot of what had been extrapolated is capabilities that could be developed and none of which are workable right now.  For now, we no longer continue to count devices and are able to distinguish uniques versus repeats. However, the process is very much like a website, you can tell how many hits you have had and how many repeat visitors, but we cannot tell who, or anything personal about any of the visitors on the website.  So we couldn’t tell, for example, whether we had seen devices or not as we never gathered any personal details.

Future developments will, however, not just depend on technology, but also, most importantly, on people being comfortable with interactive technology – much as has happened over the course of the weekend on the internet.

This is a somewhat less ebullient statement than one of Memari’s previous quotes:

“The chances are, if we don’t see you on the first, second, or third day, we’ll eventually capture you,” he said. “We just need you to have it on once.”

What can you do to protect yourself from this gross invasion of privacy? Disable Wi-Fi (and Bluetooth) if you aren’t actively using it when you’re out and about. Doing this will help save your battery too. You can also register your MAC address and opt-out of data collection via the Presence Orb web site.

It’s interesting to note that since this story broke the Renew London bin screens have been conspicuously devoid of any advertising. Evidently advertisers don’t want to be associated with this trial either.

Renew London waste bin


Dumb binUpdate: 12-Feb-2015

London’s ‘smart’ bins have been unceremoniously decommissioned, as you’ll see in this photo.

The RenewLondon.com domain name was sold in June 2014 and it now resolves to an accounting blog.

The former Renew London business seems to have disappeared without a trace, disproving the theory that where there’s muck there’s brass!

Corrupted SMS on Android

For a couple of weeks I have been receiving strangely composed SMS from a friend. It was as if two totally separate conversations were being mixed together into one long message.

At first I thought my friend might have been inebriated when he sent them (not unusual for him!) but as the messages continued to come through in this strange fashion I wondered if perhaps he was suffering from a split-personality.

Eventually I called him up and we compared messages. It turned out that the messages I was receiving on my Android device bore little resemblance to the messages he was sending. At first I thought this could be due to a corrupt SMS database on his iPhone, but after some searching I came across an Android bug report which perfectly described the issue I was experiencing:

» Issue 17769: Multipart SMS getting mixed up with old messages

The first post on this thread is dated June 2011, so the problem has been around for quite a while! I was pleased that I wasn’t alone in experiencing the issue, but what was the cause and how could I fix it?

Another Android bug report – Issue 28697 – had the answers:

Under certain circumstances, SMSDispatcher can incorrectly construct multi-part SMS messages, resulting in a corrupted message being dispatched to the applications. The corrupted message contains parts from previously received multi-part SMS messages instead of the corresponding parts from the newly received message.

In this more recent report, the author Ian Payton has identified the problem to be partly due to the way in which multi-part SMS is implemented, and partly to how Android processes multi-part messages.

If you want all the details then head on over to Ian’s detailed explanation, but the quick version is that an Android device can sometimes end up with orphaned SMS which it doesn’t know what to do with. These are usually the result of a message being retransmitted by the network because it did not receive a delivery acknowledgement from your device. This can occur if you are in patchy cellular coverage for example.

The SMS protocol uses an internal reference number to help reassemble a concatenated message, but this reference is not unique and if you have one or more of these orphaned messages on your device then in some circumstances the message parts can get mixed up to erroneously construct a new Frankenmessage!

This has the effect of your being presented with a message which is made up of some of the new message and some of an old message which has been hanging around in limbo on your device.

That’s all very well, but how can you fix this situation?

Ian has kindly written SMS Multi-Part Cleaner, a small Android application which finds all the orphaned SMS on your device and allows you to review and delete them manually. Alternatively you can download the very similar Orphaned Texts app from Google Play.

If you are prone to patchy cellular coverage and frequently receive long SMS then you be advised to run this application every few weeks to check for orphaned messages.

Printing to a Samsung ML-1210 on Mac OS X

Although Samsung stopped providing official Mac OS drivers for the ML-1210 laser printer long ago, it is still possible to use this venerable old laser printer with the latest Mac OS X.

First download the latest Open Source Samsung-GDI for Mac OS X and GPL Ghostscript for Mac OS X packages from The Linux Foundation.

Next you’ll need the Foomatic-RIP package, but don’t download the latest version!

You need to use Foomatic-RIP version 3.0.2 (dated 30th January 2008), otherwise your print-outs will include a top margin which you can’t remove. Fortunately the older working version is still available from OpenPrinting.org.

Open each downloaded disk image in turn and run the installers. When all three packages have been installed you are ready to add the printer.

Connect your printer using an appropriate USB cable. Now go to Mac OS X System Preferences and select ‘Print & Scan’. Click on the ‘+’ button and a new ‘Add Printer’ window will open.

Assuming your printer is connected you should see ‘Samsung ML-1210’ already in the printer window. Click on that printer name and then open the drop-down list of printer drivers next to “Print Using”. Select ‘Samsung ML-1210 Foomatic/GDI’ and then the ‘Add’ button.

Your printer has been added. Legacy printer revival achievement unlocked!

Gmail attachments not working?

I’m assuming you’ve found your way here because you too are having difficulty viewing image attachments in the Gmail app for Android?

I found that thumbnail previews of images were displaying fine, but when I tapped to view the full image the progress bar would scroll around indefinitely.

In my case the problem was caused by Android’s Download Manager, and the solution was relatively simple.

Go into your Android Settings screen, select Apps, swipe to the ALL tab and scroll down to Download Manager.

Tap on Download Manager and then Clear data.

Download Manager

Exit the settings, go back into Gmail and hopefully you should now find that attachments are working again.

Apps Publishing Security Policy

BSkyB has become the latest high-profile victim of a security blunder which has caused them to suspend all their Sky Android applications from the Google Play app store.

The hackers would appear to have used a combination of phishing and social engineering techniques to compromise a trusted computer and steal corporate login details for third-party sites such as Google and Twitter.

The storefront for Sky’s Android mobile apps was defaced, with the app descriptions changed and screenshots replaced.

Sky Go defaced

To make a bad situation even worse for Sky, one of their official Twitter accounts was also compromised and the hackers used it to draw more attention to their handywork.

skyhelpteam

Fuelled by the ‘official’ Twitter misinformation, customers were led to believe that the apps had also been tampered with, although this has been subsequently denied by Sky on their Help Forum:

We have temporarily removed our Apps from the Google Play store following a security alert.

All Sky Apps were unaffected and any Sky Android apps previously downloaded by customers are safe to use. There is no need to remove them from your android device.

As soon as we have restored the apps on Google Play we will post up an update.

In a related security breach, Twitter has locked access to @SkyHelpTeam, which is why we are currently unable to tweet from this account. However, help and info is available via @SkyHelpTeam1Facebook and here on the Sky Help Forum.

The tweet that was made from the @SkyHelpTeam twitter, in the early hours of Sunday morning, advising customers to unistall their apps was NOT an official tweet from Sky. Twitter security immediately detected this vogue messaging and locked account as part of agreed standard security process.

Sky have suffered this humiliation as a result of sloppy security practices. With a robust security policy the damage from this attack could have be limited or prevented entirely.

My recommendations for an apps publishing security policy:

  • Use a dedicated Google account for the Google Play Developer Console, not an account used for other Google services. Do not divulge the email address of this account.
  • Enable 2-Step Verification on your Google account and use Google Authenticator to login. Make sure that you properly sign out of your Google account when you have finished each session.
  • Only use a bookmarked https link to access the Developer Console. Never click on links contained in emails or on other web sites.
  • Tightly limit access to the Developer account. Only permit access to those directly involved with apps publishing, usually just the Apps Manager and their deputy.
  • Wherever possible use discrete private keys to sign each application – see the Signing Strategies section of Android Developer Tools. This limits the damage should the private key for an individual app be compromised.
  • Store your signing keys securely, preferably using a hardware-encrypted USB flash drive (such as an IronKey). Physically store the keys in a locked safe.
  • Use a standalone computer for code signing and never connect it to a network. Treat all networks as untrusted, even your corporate LAN.
  • Have a well rehearsed contingency plan to ensure business continuity if the worst does happen.