The custom firmware, Slim Bean Beta 1 ROM, also brings a number of customization features to Galaxy S3. Apart from that, the Android 4.2.1 Jelly Bean exclusive features include multi-user support, gesture typing, new quick settings option, lock-screen widget, new camera app, photo sphere, improved Google Now, new daydream feature, miracast display and many more, according to Android Jinn.
The report states that the custom ROM in question is known for low file size and fast speedy nature. However, it is still under development and therefore the users might face some issues and bugs. All the issues are expected to be fixed as development progresses.
Here is a list of key features of the Slim Bean Android 4.2.1 Jelly Bean Beta 1:
- Dotted Battery Mod and color picker
- Battery bar mod
- Notification Background customization
- Notification row transparency
- Quick Settings option
- Network mode tile
- Profile Tile
- Dismiss on toggle
- Updated APN + SPN
- Wi-Fi name in notification drawer
- Power widget
- Device Parts
- Performance Settings (need to tap build number a few times)
- Cursor control using volume keys
- Disable full screen keyboard
- Alternate app chooser
- Clock styles and color chooser
- ADB over Wi-Fi
- Camera power shutter mod
- Wi-Fi country specific settings
- Notification IME selector
- SMS quick reply mark as read from notification
- All MMS features
- All Contacts feature
Below is a tutorial showing how to install Android 4.2.1 Jelly Bean on Sprint Samsung Galaxy S3 (SPH-L710) using Slim Bean Beta 1 ROM. Before going ahead, take a look at the preciosities that need to be aware of.
- Backup your data.
- The device must have at least 80 percent battery power.
- USB driver must be installed for Samsung Galaxy S3 (SPH-L710) in your PC.
- USB Debugging must be enabled.
- Backup your EFS Folder.
- Flashing this ROM on Galaxy S3 L710 will increase your binary counter.
- Don’t skip Nandroid backup as it’s very helpful if this custom ROM doesn’t work the way you wanted.
The users should also keep in mind that this tutorial is only for Sprint variant of the Samsung Galaxy S3. Therefore, it should not be implemented on any other Android device. In addition, IBTimes cannot be held responsible if anything goes wrong. The users should proceed at their own risk.
1. Slim Bean Beta 1 4.2.1 Jelly Bean ROM For Galaxy S3 L710 [Filename: Slim-4.2.1.Beta.1-d2spr-20121222-0812-OFFICIAL.zip]
2. Google Apps [Filename: Slim_Gapps.zip]
How To Install
Step 1: Connect your Sprint Galaxy S3 to PC using USB cable.
Step 2: Copy downloaded files to the SD card of your phone without extracting them.
Step 3: Disconnect USB and turn off your phone.
Step 4: Boot into ClockworkMod recovery in your Galaxy S3 by pressing and holding the Volume Up, Power and Home buttons together until the Samsung logo appears on screen.
Step 5: Leave the buttons and hold then again. You will get ClockworkMod recovery screen soon. Now browse between options in recovery using Volume keys while using Power key to select an option.
Step 6: Carry out a Nandroid backup of your existing ROM by selecting Backup and Restore, then on the next screen, selecting Backup again. Once back up is complete, go back to the main recovery menu.
Step 7: Now perform the data wiping task. To do so, select wipe data/factory reset, then select Yes on next screen to confirm your action. Wait for a few minutes till the data wipe is completed.
Step 8: Select install zip from SD card, then select choose zip from SD card. After that, locate the Slim-4.2.1.Beta.1-d2spr-20121222-0812-OFFICIAL.zip file and select it by pressing Power button (tap on it if using touch version).
Confirm installation by selecting Yes – Install _____.zip on the next screen. The ROM installation will begin.
Step 9: Once the ROM installation is done, repeat step 8 but choose the Slim_Gapps.zip file instead of ROM zip to install the Google apps package.
Step 10: After the installation is completed, go back to the main recovery menu and select reboot system now to reboot the phone and boot up into customized Android 4.2.1 Jelly Bean ROM Slim Bean Beta 1. The first boot will take time.
[Source: Android Jinn]
SMS quick reply and marks as read from notification
All MMS features
All contact features
To learn more about bugs and device-specific issues, head to the source page.
Galaxy Note users who wish to upgrade their devices with SlimBean Android 4.2.1 Jelly Bean custom ROM may follow the tutorial below. IBTimes UK reminds its readers that it will not be responsible for any damage to the device. Users are advised to verify the model number of their devices since the Jelly Bean ROM works only on the Samsung Galaxy Note N7000 but not on any other variant.
1) Download USB Drivers for Samsung Galaxy Note and enable USB Debugging Mode.
2) Back up all your important data.
3) Ensure the device is rooted and ClockworkMod (CWM) Recovery is installed.
4) Ensure the battery of the device has more than 80 per cent of charge.
Steps to install SlimBean Android 4.2.1 Jelly Bean ROM on Galaxy Note N7000
1) Download Slim Bean Android 4.2.1 Jelly Bean ROM on Galaxy Note N7000
2) Download Google Apps package
3) Connect your Galaxy Note to the computer using the USB cable and copy both the downloaded zip files to the SD card of your phone
[Note: Do not extract any file.]
4) Disconnect the phone from the computer. Then boot into ClockworkMod recovery by pressing and holding Volume Up, Power and Home buttons together until the Samsung logo appears. Then leave all three buttons for half a second and hold them again. You should see CWM Recovery soon. Alternatively, you may try for Recovery mode without key combination
5) In CWM Recovery, perform a Nandroid backup of your existing ROM which you can restore later. To do so select Backup and Restore; then select Backup again on the next screen. Return to the main recovery menu once the backup is completed
6) Now perform data wiping by selecting Wipe Data/factory Reset then select Yes on the next screen to confirm the action. Wait until the data wipe is complete
7) Using the Power button select ‘Install zip from SD card’; then again press the Power button to select ‘Choose zip from SD card’ and locate the Slim Jelly Bean ROM zip file which you have copied to the SD card. Select it using the Power button and confirm installation by selecting Yes on the next screen
After the ROM is installed, repeat the same procedure to flash the Google Apps package
9) Once the installation process is complete, return to the main recovery menu and select ‘Reboot System Now’ to reboot the phone and boot up into the customised Jelly Bean ROM. The first boot will take some time
Note: If you wish to return to your previous ROM, then boot into recovery, select Backup and Restore and restore your previous ROM by selecting it from the list.
SlimBean beat 1 custom ROM featuring Android 4.2.1 is now installed and running on your Samsung Galaxy Note N7000. Navigate to Settings About Phone to verify the software version running on your device.
[Source: Android Jinn]
To report problems or to leave feedback about this article, e-mail:
To contact the editor, e-mail:
1) Download USB Drivers for Samsung Galaxy Note 10.1 and enable USB Debugging mode.
2) Back up all your important data before proceeding.
3) Ensure the Galaxy Note is rooted and ClockworkMod Recovery is installed.
4) Ensure the device is factory unlocked.
5) The battery of the device should have more than 80 per cent charge.
Steps to install CM10.1 Android 4.2.1 Jelly Bean on Galaxy Note 10.1
2) Download Google Apps package
3) Connect the Galaxy Note to the computer using USB cable and transfer both the downloaded zip files to the SD card of your device
4) Turn off the Note. Now reboot into recovery mode by pressing and holding Volume Up and Power buttons together until the screen turns on. Then leave the Power button and continue holding the Volume Up button until you enter CWM Recovery
5) In recovery mode, perform a Nandroid back-up of your existing ROM, which you can restore later. To do so select ‘Backup and Restore’ and select Backup again. Once the action is completed, return to the main recovery menu
6) Perform data wiping by selecting Wipe Data/Factory Reset and confirm the action on the next screen. Wait until the data wipe is complete and return to the main recovery menu
7) Using the Power button, select ‘Install zip from SD card’ and again press the Power button to select ‘Choose zip from SD card’ and locate the Jelly Bean ROM. Select it using the Power button and confirm installation on the next screen
Once the ROM is installed, repeat the same procedure to install Google Apps package
9) Once the installation is completed return to the main recovery menu and select ‘Reboot System now’ in order to reboot the device and boot up into the customised ROM
CM10.1 based on Android 4.2.1 is now installed and running on your Samsung Galaxy Note 10.1 N8000. Navigate to Settings About Phone to verify the software running on your device.
[Source: Android Egis]
To report problems or to leave feedback about this article, e-mail:
To contact the editor, e-mail:
The Google Nexus 4 made by LG has been more successful than anybody could have imagined and one of the reasons for its success was that being a Nexus device it offers a pure vanilla Android experience, great for those who like to customize their phones. It will also be one of the first in line to receive future Android operating system updates. Today we have news of a software mod that will enhance video recording and more news about a LiquidSmooth Jelly Bean ROM.
Demand for the Nexus 4 is still outstripping supply but for those fortunate enough to have already got their hands on one it offers plenty of opportunities for tweaking and the use of custom ROMs. Firstly one of the ingenious hackers/developers over at XDA, mohit1234, has come up with a mod that will gift significant advances to the Nexus 4’s video capture capabilities with a clearer picture and also less noise than with the default setting.
The software mod will increase the default bitrate of 12mbps to 20mbps, now that’s some improvement. You will require a Nexus 4 that has been rooted and has its bootloader unlocked and access to the system partition via a root file manager app. The only downside is that your new video files will be larger in size, something to bear in mind when considering the rather limited storage on the Nexus 4, a good point made by Phandroid. If you want to check this out then head to this XDA link where you will find full instructions and the dev responsible has also included a zip file for flashing.
Please remember to do a backup of your data, apps and settings before you begin. At this point we’ll give you our usual caution that at Phones Review we never recommend tampering with your device and if you choose to do so it is entirely your own responsibility and at your own risk if something goes wrong. However, we know that many of our readers, and particularly Nexus device owners, enjoy this aspect of owning a smartphone and so like to bring you the latest information.
We also have news of a new LiquidSmooth Jelly Bean 4.2.1 ROM for the Nexus 4, aimed at making your device performance smooth, stable and highly customizable. This custom ROM comes from yet another XDA developer, tspderek, and your Nexus 4 will need to have ClockworkMod recovery installed and have an unlocked bootloader. You can find the LiquidSmooth Jelly Bean ROM download at this XDA link and you can find out much more as well as see full instructions and installation guide at Android Soul here. Once more we’ll remind you that if you choose to use this then it is entirely your responsibility as in our earlier caution.
We have a feeling that a lot of Nexus 4 owners may be entertained this weekend modding their devices. We’re always interested to hear from our readers so let us know of your Nexus 4 experiences. Will you try out either of the above methods? If so we’d like to hear if it all went smoothly for you and what you think of the finished results? Let us know by sending your comments.
Step 1: Download the latest version of Liquidsmooth Jelly Bean ROM
Step 3: Copy both the ROM and Google Apps (GApps) zip files to the root folder on your phone’s SD card.
Step 4: Power off your phone and boot into bootloader mode. To do so, press and hold Volume down and Power buttons together until the display comes on. NOTE: Use Volume buttons to navigate and Power button to select an option in Recovery.
Step 5: Browse to the Recovery mode option and select it using the Power button to boot into CWM Recovery.
Step 6: Take a NANDroid Backup of your existing ROM so that you can restore it later if something goes wrong with the new ROM. To take a backup, select Backup and Restore and then hit Backup again. Return to main recovery menu once backup is done.
Step 7: Choose wipe data/factory reset and click Yes to confirm. Wait for the data wipe process to complete (it will wipe only installed apps and settings, but the files on the SD card will be left intact).
Step 8: Choose Install zip from SD card and then click Choose Zip from SD card. Browse to the location of ROM file you copied earlier and select it. Click Yes to confirm ROM installation on next screen.
Step 9: Once ROM is installed, click Choose Zip from SD card again, but select GApps file to install Google Apps as well.
Step 10: After GApps is installed, return to the main recovery menu and hit Reboot System Now to reboot the phone into Liquidsmooth ROM. The first boot may take about 5 to 7 minutes. So, leave it alone.
Updating to Newer Versions of the ROM:
The ROM will receive periodic updates as part of development progress. So, to install newer versions, download the latest ROM, copy it to the device, reboot to recovery, repeat step 8 to install the update and then reboot the phone.
NOTE: It is not necessary to reinstall Google Apps or wipe data once again while updating to a newer version, as it is required only when installing the ROM for first time.
Liquidsmooth Jelly Bean ROM is now successfully installed on your Nexus 4.
[Source: The Android Soul]
To report problems or to leave feedback about this article, e-mail:
To contact the editor, e-mail:
Linaro’s efforts have boosted Android’s performance, delivering an improvement of 30 to 100 percent in various benchmarks. They achieved these impressive gains by adapting Android 4 so that it could be built with their improved GCC toolchain.
We first wrote about Linaro in 2010 when the non-profit organization was founded by a consortium of hardware and software companies, including ARM, Samsung, TI, and Canonical. Linaro has worked to improve the quality of Linux on the ARM architecture, focusing largely on hardware-enablement and tooling.
The group is closely aligned with Ubuntu, but the improvements that it is driving offer benefits for the broader ecosystem of platforms and distributions that are deployed on ARM hardware. They have done a lot of work upstream in GCC (the GNU Compiler Collection) to open the door for better ARM optimization in Linux and other open source software.
Linaro’s GCC improvements have been producing measurable performance advantages over Google’s stock Android environment and build toolchain since late last year. Google is reportedly accepting some of these improvements in the upstream Android Open Source Project and independent developers are also looking to put them to use.
As a recent blog post at Liliputing pointed out, Linaro improvements are being merged in Cyanogen, a popular third-party ROM that is maintained through a community-driven process. Enthusiasts have already started generating device-specific builds that incorporated the Linaro patches. A Linaro build for the Galaxy Nexus, for example, was published this week on reddit (disclosure: reddit is a cousin site of Ars).
If you are looking for more information about Linaro, or want to get involved, you can find out more by visiting the organization’s website or checking out the Linaro projects that are hosted on the Launchpad collaboration site.
Update: updated to indicate that Google is merging the improvements, based on a Google+ comment made by Google engineer Jean-Baptiste Queru.
Today marks the 27th day of my Android challenge and with three days left, attempts to really integrate Android into my life have risen to another level. At this point I’m neck-deep in wading through the wonders and disappointments of the Android platform. Most notable is my sudden commitment to finding the perfect launcher/lock-screen combination which has taken up far too much of my time.
Before I get into that, I want to once again continue my praise for Swiftkey and its recent notification that I’ve saved 10,000 keystrokes. Whether or not that number is 100% right is really irrelevant to me — I know for a fact it has saved me keystrokes. The real number of saved keystrokes while interesting, doesn’t make me love the app more or less, I just love it. I swear I’m not being paid to promote this app, but I do have to wonder how this challenge would be turning out without Swiftkey, an app I’m not entirely sure I can ever give up.
Moving on and echoing my earlier reports, I’m still in love with default app switching and have settled on Firefox Beta as my browser of choice on Gingerbread and Chrome Beta on Ice Cream Sandwich. I’ve been back on the HTC One S for the last week and I’ll likely continue with it for a few more days as I complete the challenge.
The addition of Comcast’s Xfinity app in the past 48 hours has also made my Android experience more on par with that of my iPhone. I know prospect of watching a lengthy television show on a smaller screen isn’t appealing to everyone, but choice is choice and I’d rather have the option of doing so than not at all. At the very least it lessens the game between apps that I both want and need on my iPhone and have been unable to get on my Android device.
One thing that I did want to discuss in this post briefly since I’m going to make it short as my last report will come in the next couple of days is that of customization. One of the greatest assets of the Android platform is your ability to completely customize the device. In my eyes, that’s both a blessing and a curse. The iPhone 4S I have is unlocked, purchased unlocked directly from Apple so I had no need to jailbreak it prior to unlocking. That wasn’t the case with the iPhone 4 I sold before purchasing my 4S. When jailbroken, I spent hours endlessly customizing the icons, wallpapers, lock-screens, widgets and all the fun little tweaks one can have while jailbroken. While you don’t need to jailbreak your Android device to customize, (unless you want custom ROM’s, then you have to root), customizing the device is equally frustrating for me.
First, let me clarify my definition of the word frustrating, it’s not frustrating in the sense that I’m angered or upset, I’m frustrated because I can take up so much time looking for the perfect set-up. I’m frustrated because I’m never happy with one particular look. I’ve customized my icons, lock-screen, wallpaper, and widgets almost every day I’ve had a device in my hand the last 27 days. Perhaps I’m just obsessive with trying to find that “one” look that will keep me happy, or maybe I’m just hard to please. Either way, customizing my Android device has taken up far more time than I would care to admit.
So again, when I say the word “frustrated,” you’ll have to ignore the first definition that pops in your mind and recognize I’m frustrated because the options are so plentiful, so refreshing that it’s causing me to get — frustrated. First world problems right?
In any event, my challenge is almost over and while I know many of you are emailing, tweeting and wondering if I’ll stick with Android, do a 30 day Windows Challenge or go running back to my iPhone, check out the final report in the next few days and you’ll find out all the answers!
Over at the quietly brilliant manufacturer HTC’s Android 4.0 Ice Cream Sandwich list expansions are happening everywhere with new phones added to the list and phones already on the list getting updated schedules. This list is what HTC considers its nearly-definitive list of Android 4.0 Ice Cream Sandwich updates and can therefor be trusted about as far as you can trust any list on earth. Notably absent from the list are all of the HTC tablets released to date – you’ll have to go rogue if you want that kind of hardcore underground tasty treat action. HTC has added quite a few of their 2011 smartphones to the list, with such beasts as the HTC Sensation already grabbing the update before this list expires their expectation for update dates. For example the HTC Sensations expected update range is between March and June of 2012, while our T-Mobile (4G) version has it already. This means you can expect your update for these devices on the list well before HTC promises you’ll have them. DROID Incredible 2 by HTC : To be determined (by the end of August) The folks at HTC have noted specifically that devices with 512MB of ROM or less will not be upgraded to Android 4.0 Ice Cream Sandwich. This includes smartphones such as HTC ChaCha, HTC Salsa, HTC Wildfire S, HTC Explorer, and several more older, less awesome phones. HTC has also let the world know that the tablets HTC Flyer, HTC EVO View 4G, and HTC Jetstream will remain on their current version of Android, that being Android 3.0 Honeycomb. HTC is also clear to make the differentiation between support and upgrades: “Upgrades are not the same thing as ongoing support. Devices not being upgraded to Android 4.0 will still get software improvements, security fixes, and technical support as needed.” – HTC So don’t fret, those of you with the Facebook phones and the tablets galore, HTC will still help you move forward, just not to a new dessert! Along with this also comes the fact that many phones getting Android 4.0 will not get Sense 4.0, instead working with Sense 3.6, another less needy version of the software. The HTC Sensation is one example of a device that HTC Sense 4.0 cannot exist on due to its requirements for some certain bits of dedicated hardware. Imagine that! [via HTC]
HTC Amaze 4G : May-June
HTC Desire S : June-July
HTC Desire HD : July-August
HTC EVO 3D : June-July
HTC EVO 4G+ : May-June
HTC EVO Design 4G : June-July
HTC Incredible S : June-July
HTC Sensation : March-June
HTC Sensation 4G : March-June
HTC Sensation XE : March-June
HTC Sensation XL : April-Jun
HTC Rezound : June-July
HTC Rhyme : June-July
HTC Thunderbolt : July-August
HTC Velocity 4G : March-June
HTC Vivid : March-June
Over at the quietly brilliant manufacturer HTC’s Android 4.0 Ice Cream Sandwich list expansions are happening everywhere with new phones added to the list and phones already on the list getting updated schedules. This list is what HTC considers its nearly-definitive list of Android 4.0 Ice Cream Sandwich updates and can therefor be trusted about as far as you can trust any list on earth. Notably absent from the list are all of the HTC tablets released to date – you’ll have to go rogue if you want that kind of hardcore underground tasty treat action.
HTC has added quite a few of their 2011 smartphones to the list, with such beasts as the HTC Sensation already grabbing the update before this list expires their expectation for update dates. For example the HTC Sensations expected update range is between March and June of 2012, while our T-Mobile (4G) version has it already. This means you can expect your update for these devices on the list well before HTC promises you’ll have them.
DROID Incredible 2 by HTC : To be determined (by the end of August)
The folks at HTC have noted specifically that devices with 512MB of ROM or less will not be upgraded to Android 4.0 Ice Cream Sandwich. This includes smartphones such as HTC ChaCha, HTC Salsa, HTC Wildfire S, HTC Explorer, and several more older, less awesome phones. HTC has also let the world know that the tablets HTC Flyer, HTC EVO View 4G, and HTC Jetstream will remain on their current version of Android, that being Android 3.0 Honeycomb. HTC is also clear to make the differentiation between support and upgrades:
“Upgrades are not the same thing as ongoing support. Devices not being upgraded to Android 4.0 will still get software improvements, security fixes, and technical support as needed.” – HTC
So don’t fret, those of you with the Facebook phones and the tablets galore, HTC will still help you move forward, just not to a new dessert! Along with this also comes the fact that many phones getting Android 4.0 will not get Sense 4.0, instead working with Sense 3.6, another less needy version of the software. The HTC Sensation is one example of a device that HTC Sense 4.0 cannot exist on due to its requirements for some certain bits of dedicated hardware. Imagine that!
The firmware for Samsung’s Galaxy S III has leaked just over a week ahead of the device’s release. While you can’t flash the ROM to another phone just yet, developers are able to poke around inside and could be bringing elements of the TouchWiz Nature UX experience to a wider audience at some point. The first major finding to come out of the leak, however, is an APK for S Voice, Samsung’s Siri-style voice control application. It seems to work on any device running Android 4.0 — we tested the app on a Galaxy Nexus and a Sharp Aquos Phone, and got it up and running largely without issue barring a couple of crashes.
It’s clear that S Voice has been modeled very much in Siri’s image
Obviously, we don’t want to pass anything resembling a final judgement on leaked software that was designed for different hardware. It’s clear, though, that S Voice has been modeled very much in Siri’s image, right down to the near-identical microphone icon at the bottom. The software hooks into Android and lets you set calendar events, send messages to contacts, get Wolfram Alpha-powered answers to questions, find out weather forecasts, and so on. Voice recognition was mostly solid, but we had a few problems getting it to parse various names, and “The Verge” remains a common stumbling block for this kind of software. S Voice’s voice itself is a coldly mechanical female affair, some way away from Siri’s personable and slightly coquettish mannerisms (or indeed the dulcet male tones found in the British version).
It also seems that S Voice isn’t quite as attuned towards natural speech as Siri. For example, whereas Apple’s service will helpfully respond to vague statements like “I’m in the mood for Italian food,” S Voice won’t offer any advice beyond suggesting a web search. Even a more direct question like “Where’s a good Italian restaurant?” sends you to Google, and the tutorial advises using much less fluent syntax such as “Text Katie message are you free tonight for dinner.” S Voice doesn’t make much effort to indulge more esoteric queries, either, though it does at least tell you that the meaning of life is 42.
Overall, S Voice is the closest approximation of Siri we’ve seen (in English, at least), but it’s not quite as fluid — at least in its current form. We’re looking forward to giving it, and the rest of Samsung’s Nature UX, a fuller workout when we review the Galaxy S III itself.
Google Chrome for Android arrived earlier this month and this week, it saw its first software update. The browser for Ice Cream Sandwich, or Android 4.0, devices gained a few new features, some bug fixes and availability in more countries; the complete list of supported regions is here. But some handset owners aren’t happy with the update because the browser no longer works on their device.
In the software release notes, Google points out that “Compatibility checks to ensure system prerequisites for Chrome are met.” The browser is specifically made to run on Android 4.0, which at this point only runs officially on two commercially available devices here: the Galaxy Nexus smartphone and the Asus Transformer Prime tablet. Handset owners using custom Android 4.0 ROMs on other phones are experiencing problems: After this update, the browser no longer runs for them.
The issue can’t be specific to all custom ROMs, however. I know this because I’m running an Android 4.0.4 custom ROM on my own Galaxy Nexus. People using a CM9 ROM appear to be having an issue because that ROM appears to Chrome as a version of Gingerbread, not a version of Ice Cream Sandwich. Hopefully, these issues get resolved as needed because Chrome for Android is by far, my favorite browser on any mobile device. It’s shame that some folks are unable to experience these features in Chrome:
The annual Mobile World Congress event is kicking off this weekend and aside from some potential Windows Mobile developments, Android is certain to take center stage. Several manufacturers have already pre-announced some of their Android devices, including LG and ZTE to name a few. I have a complete rundown of what devices we know are debuting at MWC along with others that we suspect will appear.
Two big Android questions loom in my mind, however: Will Intel finally enter the mobile market with an actual device announcement and will Google introduce a small tablet of it’s own. I’d think Intel has to use MWC or the upcoming CTIA event in May to debut its first Android smartphone; likely with Lenovo or Motorola at this point. The company has the chip for such a device; I saw it running Android 4.0 in a tablet last month. The Google tablet is a rumor at this point, and I suspect that if Google is planning a 7-inch slate, it would introduce one at its mid-year Google I/O developer event.
Android device owners looking for more cloud storage gained a big chunk of free capacity this week: Box announced its updated Android client along with a whopping 50 GB of free storage for life to go with it. Found in the Android Market, the new Box 1.6 software adds bulk uploads, commenting on files, shared folders and support for new languages, making it a worthy upgrade.
Since my 16 GB Galaxy Nexus doesn’t have a memory card expansion slot, I jumped on this deal right away; you can never have too much storage in the cloud! Even without the free 50 GB, the new client looks fantastic; take a peek at the interface and new productivity features:
Related research and analysis from GigaOM Pro:
Subscriber content. Sign up for a free trial.