Skip to main content

Samsung S3 and the poor battery life

I have had my Samsung S3 phone for a bit over a year, and the most annoying thing for me is its poor battery life. I mainly use my phone for work email, with the occasional phone call or text message, and the minimum Internet browsing, and despite that light usage, I can barely survive a day on a single battery charge.

I used every trick possible, from power savings mode, to manually syncing emails and accounts, and finally through installing Juice Defender, an Android application that turns off most of the unnecessary radio antennas when the phone is not in use to maximize battery life. The most I got was almost 10 hours of usage without charging. Better than nothing but not ideal.

I attribute the poor battery life to the poor software that runs on the device, including Samsung's and AT&T's add-ons, that I cannot uninstall after their latest update. Most of that background software eats up the battery in no time. Barring a software fix, a hardware answer would do.

An Amazon search opened up the wonderful world of extended batteries. The official S3 battery is roughly 2100mAh, but there are a lot of higher capacity ones online. The downside of the higher capacity batteries is that they need a new case for the phone, because they are thicker than what the original plastic back can accommodate.

I liked the Hyperion 7000mAh battery, and I figured with such a high capacity I should get at least 2 days on a single charge without worrying about losing power. When the battery arrived I was surprised at how thick it is, and after installing it with the new honeycomb back, my phone looked like a brick phone from the early 90s, and weighed probably as much. The battery came nearly uncharged, and the instructions recommended charging it overnight for 8 hours for 4-5 battery cycles till the battery is conditioned. After that break-in period, a normal charging cycle is good enough.

I am still at the early days with this high capacity battery, but so far all signs look positive, despite the thick form factor. I only wish device makers and network providers wrote better software.

Comments

Popular posts from this blog

Kindle Paperwhite

I have always been allergic to buying specialized electronic devices that do only one thing, such as the Kindle, the iPod, and fitness trackers. Why buy these when technology evolves so fast that a multi-purpose device such as the phone or a smart watch can eventually do the same thing, but with the convenience of updates that fix bugs and add functionality? So, I was shocked when this weekend I made an impulse buy and got the newest Kindle Paperwhite—a special purpose device for reading eBooks. I was walking past the Amazon store in the mall and saw that the newest Kindle Paperwhites were marked down by $40 for the holidays. The device looked good in the display, so I went in to look at it closely. The Paperwhite is small and light, with a 6” screen that is backlit and waterproof.   The text was crisp and readable, and in the ambient light, it felt like I am reading a printed book. I was sold and bought it on the spot. At home I have struggled to put it down. The bo...

A paper a day keeps the doctor away: NoDB

In most database systems, the user defines the shape of the data that is stored and queried using concepts such as entities and relations. The database system takes care of translating that shape into physical storage, and managing its lifecycle. Most of the systems store data in the form of tuples, either in row format, or broken down into columns and stored in columnar format. The system also stores metadata associated with the data, that helps with speedy retrieval and processing. Defining the shape of the data a priori, and transforming it from the raw or ingestion format to the storage format is a cost that database systems incur to make queries faster. What if we can have fast queries without incurring that initial cost? In the paper " NoDB: Efficient Query Execution on Raw Data Files ", the authors examine that question, and advocate a system (NoDB) that answers it. The authors start with the motivation for such a system. With the recent explosion of data...

A paper a day keeps the dr away: Dapper a Large-Scale Distributed Systems Tracing Infrastructure

Modern Internet scale applications are a challenge to monitor and diagnose. The applications are usually comprised of complex distributed systems that are built by multiple teams, sometimes using different languages and technologies. When one component fails or misbehaves, it becomes a nightmare to figure out what went wrong and where. Monitoring and tracing systems aim to make that problem a bit more tractable, and Dapper, a system by Google for large scale distributed systems tracing is one such system. The paper starts by setting the context for Dapper through the use of a real service: "universal search". In universal search, the user types in a query that gets federated to multiple search backends such as web search, image search, local search, video search, news search, as well as advertising systems to display ads. The results are then combined and presented back to the user. Thousands of machines could be involved in returning that result, and any poor p...