Android News | A Story About Li-Ion Batteries

So after noticing how much of a difference people get in their battery lives, I've decided to do some research and make a guide-line that will give us all we need to know about properly using our batteries. First part is a general information and usage techniques for LIBs, second part is taken from Google materials on Android-powered devices (G1, Magic, Droid, Nexus One, etc).

General Lithium-Ion Battery (LIB) Usage:

• Discharging your LIB fully (or less than 2.4 Volt per cell) is bad for the battery.Every time you do that, it can be said that small part of your battery (some cells) dies (they forever lose their charge). Do not store your batteries depleted, there's a high chance they will die completely or will become very "weak".
• You cannot restore bad LIBs by overloading/heating/praying. You gotta go buy a new one. They DO degrade overtime, some cells naturally lose the ability to gain/give electricity.
• Although it is said that LIBs do not have memory, it's not entirely true. LIBs have gauges that monitor performance of cells, and if you do a lot of small charges, it won't let those gauges to monitor a full battery potential, causing an invalid indication of charge level. A complete charge/discharge should be made when battery capacity seems reduced, that will calibrate gauges and they will provide your phone with correct charge level status. A full charge/discharge cycle should be done every 30 (or so) partial charges.
• LIBs have a shelf-life. Do not buy them to store them. Use them early, use them often, they will die whether you use them or not. Do not buy LIBs to use them in 6 months/year/etc, buy them right before actually using them.

• LIBs have short lives (in comparison to NiCa batteries, etc). You should expect to buy a new battery in 2-3 years after being manufactured. It is caused by internal oxidation and there's nothing you can do to stop or prevent that.
• Worst LIB treatment is to keep it at 100% charge level at high temperature (think laptop/phone under direct sunlight, like car dashboard).
• Best LIB treatment, or LIBs "favorite" charge level - 40%. That's also the usual charge level you buy them with.
• LIBs don't like heat. For example, while always at 100%, typical LIB in a laptop, at temperatures of 25C (77F) will lose 20% (twenty percent!) of full capacity per year. That capacity loss is reduced to 6% (six percent) at 0C (32F), and increased to 35% loss at 40C (104F). So, keep them cool (LIBs like fridges), don't let your devices sit in the sun or overheat at charge. Also, keep in mind that while in use, battery will be significantly hotter than phone/outside environment
• LIBs like frequent partial charges/discharges more than they like full charges/discharges.

• Car "fast-chargers" overtime degrade your battery a little, as they give too much energy to the battery too fast (high voltage). Trickle-charge (USB) is best. They do provide an initial higher capacity charge (high-voltage), but do degrade the long-term battery capacity. General idea is that the slower the charge - the longer (long-term) battery will serve you.
HTC/Google-specific advice:

• Although this part is somewhat controversial, they do recommend having a complete, full FIRST charge to be made. If time allows, a preferred time for the first charge is 12 hours. This may have more to do with the OS than the battery.
• Battery on a Android device, in average, will last about a full day with normal use (some videos, mail, calls). That's what you should kind-of expect.
• Speaking in averages, "idling" 3G/EDGE connection (when phone is sleeping and no data is transferred through 3G), drains almost no energy. Just a little more than having 3G/EDGE radio off completely. So when no apps are using 3G, you don't need to keep it off.
• Same goes to WiFi connection - although it's on, if there is no data flowing through it, it uses almost no energy.
• At full throughput (100% data flow), EDGE is using significantly more energy than 3G. 3G is much more energy-efficient than EDGE.
• WiFi is using more energy than 3G (when both are at 100% use), but since it transfers files much faster and then goes to "sleep", it's actually recommended to use WiFi whenever possible. Since it'll "sleep" more often than 3G, overall it will use much less battery than using 3G.
• Some bad apps or widgets can use android's "WakeLock", keeping CPU at 100%, screen always-on, or both. I myself have encountered such widget (I won't mention the name, it's in the market) that used a WakeLock to keep CPU spun-up at 100% all the time. That makes a huge impact on battery life. My advice - use a CPU profiling app to monitor the CPU - make sure that CPU slows down by itself when it's not used. So, beware of such widgets/apps. To check for CPU cycles, many recommend OSMonitor (free from market, install it, go to options, sort by "Load" in descending order. It'll give you "busiest" processes at the top). At rest you should be getting about 10-20% for OSMonitor itself, and 1-10% Android System. At rest, everything else should be 0-1%.
• Android (at least on Nexus One) slows down CPU when not in use by itself, as a built-in feature. Apps that throttle/change CPU frequency, are not necessarily needed.
Sources:
Wikipedia - http://en.wikipedia.org/wiki/Lithium-ion_battery
BatteryUniversity - http://www.batteryuniversity.com/parttwo-34.htm
Google IO Conference 2009 - http://www.youtube.com/watch?v=OUemfrKe65c
Electropaedia - http://www.mpoweruk.com/life.htm

Installing Ubuntu on Your Motorola Xoom Tablet

UPDATE 4/10/11: Now you can enlarge your Xoombuntu install! http://trsohmers.com/2011/04/10/how-to-expand-xoombuntu-disk/UPDATE 4/2/11: Here’s the fix! http://trsohmers.com/2011/04/02/ubuntu-for-xoom-fix/
UPDATE 3/20/11: OK, so there are a couple of modified steps to make the system a bit faster, and to be releasing a small path tonight to fix some issues people have been having with the install.
This is simplified instructions for unlocking the bootloader and rooting the Motorola Xoom on Mac OS X, and today I have full instructions on how to install and run Ubuntu on your Motorola Xoom tablet. The method this uses is to install Ubuntu in a chroot“jail” to keep it separate of all Android processes… similar to how a Virtual Machine (Virtualbox, Parallels, VMware) runs an x86 operating system (Windows, OSX, Linux) on an x86/x64 machine. Since the Xoom and most Android devices run on an ARM processor,  you can only run an operating system made for ARM, so I am using the ARM version of Ubuntu version 9.10.

INSTRUCTIONS

NOTE: Even though this is running in a chroot jail, and I am 99.9% sure this will not cause any harm to your device, I can not be held responsible for anything that may happen to your device. Just by rooting and unlocking your device (which you have to have done already to do this) COULD void your warranty and/or brick your device. Then again, you COULD be struck by lightning 42 times the next time you walk outside your house… it is highly improbable unless you go outside in a thunderstorm with a lightning rod.
NOTE 2: The install files for this are about 660mb zipped, and once expanded the files are about 2.5gb.
STEP ONE: Setting up your enviornment
NOTE: I will be writing this from the viewpoint of a Linux/Mac user. If you are running Windows, just remove the ‘./’ from the commands.
NOTE 2: My Android SDK folder is /AndroidSDK/… please insert whatever the name of yours is.
1. I am assuming you have the Android SDK from when you rooted… if you do not, download it.
2. Please download this zip… this is the 660mb one, so it may take a while. Get your favorite drink, have a snack, and if you want you can skim through the rest of this  while it is downloading.
3.OK, now that you have the ubuntu.zip file, extract it to AndroidSDK/tools/
4.Take the busybox and installbusybox.sh files and copy/move them to the root of the sdcard on your device… you can do that manually by plugging your xoom into your computer and browsing the directories (on the Mac you have to use the Android File Transfer application provided by Motorola).The other way is to use ADB push, and that is what I will explain.
(Make sure you have USB debugging enabled in Settings > Applications > Development)

4a.Open up your terminal application, and change the directory to your AndroidSDK/tools

4b.Type in ./adb push busybox /sdcard (It should tell you when it has done transferring)

4c.Type in ./adb push installbusybox.sh /sdcard (It should tell you when it has done transferring)

4d.Type in ./adb shell (This allows you to access the terminal on the device itself)

4e.Type in su (This gives the terminal Super User privileges. If you get the error “Permission Denied”, you have not rooted your device)

4f.Type in cd /sdcard (Changes the directory to the device’s sdcard. NOTE: The Xoom doesn’t really have an sdcard at release… but Motorola seems to have made a virtual one so devices that require an sdcard still run.)

4g.Type in sh installbusybox.sh

After that is complete, busybox should be installed. Try entering a command like cp and see if it displays anything. If not, reboot the device (./adb reboot) and try the cp again.

5. Now that busybox is installed, lets get to actually installing Ubuntu. You now have to move all the files in the Ubuntu folder (minus busybox and installbusybox.sh) to /sdcard/ubuntu …. you can do this using a method other than ADB push, but I will explain it the ADB push way.

5a.Type in ./adb push fsrw /sdcard/ubuntu (It should tell you when it has done transferring)

5b.Type in ./adb push mountonly /sdcard/ubuntu (It should tell you when it has done transferring)

5c.Type in ./adb push ubuntu.sh /sdcard/ubuntu (It should tell you when it has done transferring)

5d.Type in ./adb push ubuntu.img /sdcard/ubuntu (It should tell you when it has done transferring)

NOTE: This file is over 2gb’s! It will take a while to transfer, and on average it takes 25-30 minutes. Time for another snack break.

5e.Type in ./adb push unionfs /sdcard/ubuntu (It should tell you when it has done transferring)

STEP TWO: Installing Ubuntu
6. OK, lets get this installing. You are going to be going to be going into the shell again, so follow these commands:

6a.Type in ./adb shell (This allows you to access the terminal on the device itself)

6b.Type in su

6c.Type in cd /sdcard/ubuntu

6d.Type in sh ./ubuntu.sh

It will give some errors, but as long as it gets to “To enter the Debian Linux Console type in ‘bootubuntu’”, you should be good. Congratulations, Ubuntu is now installed.
7. OK, now that Ubuntu is installed… you want to turn it on, right? now Type In: bootubuntu and you should give you a new line saying “root@localhost:/” Congratulations, Ubuntu is now running. If it is not running, try to Type in su bootubuntu and thenbootubuntu again. If that does not work, try rebooting your device and do it again… if it is still not working, try going through steps 5-7 again. If you have any more issues, feel free to comment here and I will try to help you.
STEP THREE: Setting up Ubuntu
8. You should still be in the shell and at the root@localhost entry. You are now entering commands through your terminal, into Android’s terminal, which is entering into Ubuntu’s terminal (What is this, Inception?). Like all operating systems, you need to update them… but with Ubuntu, this is quite easy.

8a.Type in apt-get update

8b.Now we are going to add a “head” to this “headless” OS. Since Android is the main operating system on here and Ubuntu has nothing to display on, we are going to output X windows (The GUI Linux OSs) to VNC. Type in apt-get install tightvncserver

8c.Once tightvncserver is installed, type in apt-get install lxde

8d.Type in export USER=root

8f.Type in vncserver -geometry 1280×800 (Resolution of the Xoom’s display. You can experiment to find a resolution you like.. you can type this command whenever to change the resolution)

8g.It should ask you for a password for your VNC… you can use something simple like 123 since you are the only one who can access it since it is only on your device.

9.Now we are going to change some settings to make the VNC experience better….

9a.Type in cat > /root/.vnc/xstartup
9b.Type in #!/bin/sh
9c.Type in xrdb $HOME/.Xresources
9d.Type inxsetroot -solid grey
9e.Type in icewm &
9f.Type in lxsession

10.Press CNTRL+D, and then enter this…

10a. cat > front
10b. export USER=root
10c. cd /
10d. rm -r -f tmp
10e. mkdir tmp
10f. cd /
10g. vncserver -geometry 1280×800

11.Hit CNTRL+D again, and enter this…

11a. cat front /root/.profile > temp #Thanks David Tangye

11b. cp temp /root/.bashrc

12. Now you can exit out of the Ubuntu terminal by typing exit
13.Reboot your device

13a.Install a VNC app from the market such as this Android VNC (Free)

13b.Install a Terminal Emulator app from the market like this Better Terminal Emulator Pro (3.99) or Android Terminal Emulator (Free)

13c.Now you can use the ADB shell again, but I suggest doing this on the device using one of the Terminal Emulators.

13c.cd /sdcard/ubuntu

13c.su (If the Superuser app asks for permission, press yes)

13c.bootubuntu

13c.OK, you should see the same thing as you did on your computer screen. Now go back to your homescreen, and  open your VNC client.

13d.Now, in the Nickname spot, put ‘Ubuntu’ or whatever you want.

13e.In the password spot, put whatever you put for a password earlier.

13f.Leave the address blank.

13g.Set the port at 5901.

Set the color format to 256 colors (1 bpp) for the best results.Then you press the Connect button, and you are on Ubuntu!
14. Some information:

1.Tap to click, pretty simple.

2.Double tap for right click.

3.You can switch in and out of ubuntu… just click your home button or the task manager button.

4.You should be automatically connected to the internet since it shares the device’s internet connection. So this will work on 3G, 4G, Wifi, or not having any connection. I am also going to see if I can transfer files between Android and Ubuntu since they should be on the same ‘network’.

That about wraps it up! Hope you will enjoy Ubuntu on your Xoom!

Read the original article here!

ViewSonic ViewPad 10 Dual-Boots Windows 7 And Android OS, Now Available For Sale!

ViewSonic just announced that it’s dual-boot capable ViewPad 10 tablet PC is now available for sale. The ViewPad 10 was originally announced later last year and has since then been considered as one of the first high-performance dual-boot enabled tablet PCs.
The ViewSonic viewPad 10 features a 10.1-inches LED-backlit capacitive touch display which renders a display resolution of 1024×600 pixels. It packs in an amazing agglomeration of technical specifications in an elegant-yet-sturdy looking form factor.
The most interesting thing about the ViewPad 10 is its ability to boot two different operating systems. Yes, the ViewPad 10 is designed to support both Microsoft’s Windows 7 and Google’s Android operating systems under a single hardshell.
Under the hood, the device is packaged with a 1.66GHz Intel Atom processor, 2GB of  DDR3 RAM, a 1.3megapixel front-facing camera for video calls, Bluetooth, Wi-Fi connectivity and plenty of SSD storage.
There’s also a microSD card slot for up to 32GB of additional storage space. The ViewPad 10 comes preloaded with Word, Excel, PowerPoint and Adobe Acrobat  among other business and productivity applications besides social networking apps like Facetook and Twitter.
According to Adam Hanin, Vice President of Marketing for ViewSonic Americas -
“The lines of professional and personal life are blurring, which creates a need for devices that are suited for both sides. The ViewPad 10 delivers just that by enabling users to merge business productivity with personal enjoyment anywhere, anytime. We are proud of our 10-year tablet history and are dedicated to further extending our tablet product portfolio to meet every individual need.”

The device is available with either of Windows 7 Home Premium (with a 16GB SSD hard drive) or Windows 7 Professional (with a 32GB SSD hard drive) for respective ESPs of $599 and $679 and Google Android 1.6 OS.

Let The Tablet Wars Begin, Attack of the Android

It has been said, by many a blogger with greater authority than me, that 2011 is the Year of theTablet. As the recent slew of Android-toting tablets on offer at recent expos such as MCW and CES, the battle for tablet dominance is heating up, and the ubiquitous iPad may lose its throne.
Having taken a big chunk out of Apple's dominance of the smart phone market, the Android is now looking to do the same to the iPad. With Android Honeycomb, Google have built an operating system specifically aimed at the tablet market. They know that the likes of HTC and Samsung will build amazing tablets that run Android. The HTC Flyer and Motorola Xoom are both early offerings. It will be interesting to see, with the right pricing, how popular they are. From the initial pictures of the HTC Flyer, I am convinced it will win over tablet fans.
And yet, if we digress and go back a year or so ago, it was all about the netbook. Then, there was no "need" for a tablet. Indeed, tablets had been attempted by PC manufacturers before, but failed miserably.
I once read that when Sony introduced the Walkman, in the early '80s, Sony did not research the market for what consumers wanted. At the time, the idea of listening to music privately while walking around was not something the man in the street had been demanding. But the fad for jogging and keep fit had become really popular, and the suddenly the ability to listen to music privately with a small device seemed ideal. You had a serendipitous meeting of technology and change in culture, and the rest is history.
So it is with the tablet. There was no consumer demand at the time for a tablet, after all, the netbook served as well as an-on-the-go computing device. But Apple created a desirable object that people wanted to own but do not necessarily "need". And now a market has been created.

So, the Tablet War has begun, and with Android Honeycomb being available to the manufacturers, suddenly we will all be toting a tablet in our bags. I for one am really excited by the Android tablets that go beyond the capabilities of the (current version of) the iPad. Once again, all eyes will be on the iPad 2. Manufacturers will look at what Apple will do, and then do something better.
Let battle commence!
Read more: http://technorati.com/technology/android/article/let-the-tablet-wars-beginattack-of/#ixzz1H7tAFwCY

Market Share of Android - Apple Causing Google’s Android to “Think Different”?

Since the beginning of the Android operating system’s development, one of the cornerstones of the movement has been the fact that the OS has remained open source in nature. What this means is that interested developers and hardware manufacturers have had direct, free access to the source code of the OS, enabling them to custom tailor it to their needs. With the Release of Android 3.0 (Honeycomb), Google has so far decided not to release the source code, in a move that is sure to provoke irritation for vendors and developers worldwide.
Google has stated that it doesn’t have a timeframe yet for releasing the Android 3.0 source, because they have developed it specifically for the tablet market. At this point, they appear to be concerned that the tablet-specific features they’ve integrated wouldn’t translate well to mobile phones, leading to a bad user experience on such devices. By taking this position, Google may have concluded that the closed nature of their biggest competitor, Apple’s iOS, is forcing them to retain tighter control over where and how their software is used.
It’s understandable that the fierce competition in the tablet and handheld OS race is beginning to give Google a sense that they must assert greater control, or run the risk of becoming an also ran. The counter argument is that device manufacturers have just as much to lose by releasing mobile devices with a badly integrated version of Android 3.0, and would probably not be likely to allow such mistakes to happen.
The giant advantage that Apple has developed in the mobile computing space is that it has absolute control over its platform, leading to a nearly identical user experience across all Apple devices.  While Google can’t possibly achieve such uniformity for Android, due to the enormous list of devices and manufacturers using it, they are appearing to be hesitant to waste the opportunity that the Android 3.0 system presents.
The enormous downside to this latest twist of events is that Google may be effectively stifling the growth of their own OS, along with that of their manufacturing partners, at a time when the race is Apple’s to lose. So far, there have been few Android devices that have drawn complaints, and the very openness of the platform has been the biggest engine in its development. Google would be wise to trust the judgment of the very developers and manufacturers that have pushed Android to the top of a market that seemed almost impenetrable only a few short years ago.
Read more: http://technorati.com/technology/android/article/is-apple-causing-googles-android-to/#ixzz1IUejx817