Galaxy Tab Rom Ported To Iconia A500 – TouchWiz UI Lovers, Rejoice!

Those who bought any of the first 3 Honeycomb powered tabs are likely happy with the launcher. However, for those truly addicted to their Android devices due to the ability of customizing it and its behavior, it gets boring after a while. Since there are now other players in the field (Samsung), a not-so-new UI has emerged: TouchWiz UI. However, it is only available for the Galaxy Tab as it is part of the rom. Well, if you have an Acer Iconia A500 and would love to get some TouchWiz on it, you are in luck because XDA Recognized Developer m-deejay has successfully ported the Galaxy Tab rom over to the Iconia. Aside from a few bugs, which are currently being fixed, the port works really well. It includes features such as improved ext4 performance, Virtuoso CPU scaling scripts, 3G modem support via Huawei USB dongle, and much more. Up until yesterday, there was a bug where the rear camera would only shoot up to 3 MP. The good news is that this was fixed by the dev and can now shoot in all of its magnificent 5 MP glory.

Please try this one out if you have an Iconia and let the dev know if you find any bugs or if you have any suggestions.

- 100% stock Galaxy Tab 10.1 P7500
- Awesome TouchWiz UX
- Multilanguage
Improved EXT4 performance
Ultra Fast
- Virtuous CPU scaling scripts – READ MORE
- Deodexed
- Zipaligned
- 216-1200MHz default
- Photo Editor
- 3D Photo Browser
- Asus weather widget
- Busybox / Superuser
- 3G modem support (Huawei)
- Nano text editor support
- Bash command shell support
- and more

You can find more information in the port thread.

Want something published in the Portal? Contact any News Writer.

How To Root Stock 3.1 On Your Iconia A500

There are good and bad things about official updates for our devices. The good thing is that they come loaded with the latest OS versions (unless there are newer leaks), updated drivers, better apps, and many more things. The bad part is that more often than not, the updates come with patches for security holes that end up relocking our devices and thus we have to wait until someone can come up with a way to crack them again. It seems that non-phone devices like tabs also suffer from this predicament as it was seen by Iconia A500 users when the 3.1 update hit this past week. Luckily, the new lock did not last too long as it was quickly rooted once again. For those who decide to keep stock but do want all the root goodness in your, XDA member sc2k has posted a guide on how to accomplish this task. The way to root is very simple and it can be achieved as quickly as installing an apk and running it.

Please leave your feedback if this method worked for you.

This tool installs su and superuser.apk for stock HC 3.1

As the old root method does not work anymore I created this new tool.

You can find more information in the guide thread.

Want something published in the Portal? Contact any News Writer.

Acer Iconia A500 Receives ClockworkMod Recovery and Ported 3.1 ROM!

Last week, the Acer Iconia A500 was the lucky recipient of quite a few pieces of development work by various talented forum goers here on XDA. Perhaps the two most notable releases were ports of XDA member Koush‘s useful ClockworkMod Recovery and an Android 3.1 ROM originally meant for the Asus Eee Pad Transformer.

The ever popular recovery was ported by XDA forum member thor2002ro. However, for those who aren’t keen on using terminal on either the device itself or through ADB, forum member Euclid’s Brother has created a simple app, which automates the process… Take that, Father of Geometry!

With the blessings of thor2002ro, I bring you an easy to use app for installing his (or any other) recovery image.

It has his rev1.2 built-in, along with a Stock USA 1.141.07_COM_GEN1 recovery image. It can also install a recovery.img from the external sdcard.

It gives an option to backup your current image (for later rollback) and runs itsmagic (built-in) when it’s finished installing a recovery image.

Let me know if anyone finds any problems with it. I have not tried it under PRIMEE 1.4. But I have flashed between thors recovery and stock recovery several times using stock HC 3.0.1.

What to do with a shiny new recovery? Install a new ROM, of course! To that end, XDA  forum member Dexter_nlb was able to bring Android 3.1 to the A500 by porting the PRIME! v1.4 Honeycomb ROM, originally by Roach2010.

I have ported the PRIME v1.4 (honeycomb 3.1) rom to Iconia A500.. It originate from Asus early beta 3.1 release custom rom prime v1.4 here by Roach2010
We are still waiting for the kernel source, so limits of a stock kernel apply, which is one, using the new feature PS3 controller joypad’s. Until source is out, these functions are missing.

Fun times await A500 owners out there. Be sure to check out the recovery and ROM threads (and automated recovery installer app post) to get your fill.

[Thanks brunsbanjo and Egzthunder1 for the tips!]

Acer Iconia A500 Tablet Forum Added

It looks like Honeycomb tablets are finally beginning to make their way into the market, right after Motorola broke the ice with the Xoom. The second available bee-droid equipped device to hit the market was the ASUS Eee Pad Transformer for which we added a forum a few weeks ago. Now, it is the time for the third incarnation of Honeycomb and it comes in the shape of the Acer Iconia A500 Tab. This device is very similar in terms of specs to the Asus one (minus the keyboard and a few other things). It comes equipped with dual cameras, 1 GHz Tegra dual core processor, 1 GB DDR2 RAM, and much more. The best part is that as per an article that we published a bit earlier today, it has joined the ranks of the rooted. Needless to say, there is still a lot to do before full customization can take place, but at least you will be able to have Superuser and Busybox in your device.

Do you have one yet? If so, please leave some feedback or if you find out how to do something cool with it, please share your findings.

You can visit the Acer Iconia A500 home on XDA here.

Want something published in the Portal? Contact any News Writer.

Acer Iconia Tab A500 Rooted!

Merely days after its release earlier this month, Acer’s Iconia A500 Android Honeycomb tablet has been rooted! The tablet, which features a unique Acer UI skin, front and back facing cameras, and a 1GHz dual-core Tegra2 processor, will now allow superuser permissions as a result of some clever work from XDA member monki-magic (original post here)

This was achieved by using XDA moderator  Chainfire‘s newly released Gingerbreak rooting tool.

 

As many of you will know, the rooting process is a stepping stone on the way to completely customising the device’s software. To have this achieved so quickly can only mean good things for the developmental future of the Iconia Tab.

To find out for yourself how to root the A500, read the instructions in this thread, created by Slowie911.

TWRP 2.4 Adds Impressive New Feature Set

Regardless of what the US Government and the PAC behemoth CTIA would have you believe, choice is a good thing in the wireless industry. And when it comes to having choices for different types of software you want to run on your devices, it is a great thing. TWRP (TeamWin Recovery Project) is one of those options for recovery on many different types of devices, with over 80 being officially supported at this time.

TeamWin has been very supportive of the community, from providing instructions on how to build TWRP for devices they don’t officially support, to actively participating in online and forum discussions assisting users with the usage and porting of TWRP. Their source code is completely open source and doesn’t require that you purchase an app in order to utilize the OpenRecovery scripting functionality, unlike other options available.

As of late, they have been hard at work adding various features that add value and continue to set TWRP apart from the other recoveries. Version 2.4.0.0 brings with it new features like using libtar instead of busybox’s tar implementation for better backup options, exFAT sdcard support, decryption of Samsung TouchWiz encrypted devices, updated ADB sideload functionality, and much more. You can view their site for a full list of supported devices or visit some of the device-specific threads below:

If you spot an official TWRP thread that we’ve left out, please let us know, and we’ll promptly add it in!

Huawei Ideos S7 Gets a Dual-Boot Kernel

In the past, we have seen devices such as the HD2Desire HDNook Color, Xperia Play, Motorola Defy, Droid RAZR, Iconia A500, Galaxy Note, Optimus One, Evo 3D, Galaxy Tab 2 7.0 and a few others getting dual-boot support. Today, the Huawei Ideos S7 tablet joins the club, thanks to a dual-boot kernel that allows you to install two Android ROMs on the device.

This dual-boot kernel for the S7 was developed by XDA Forum Member hal_2000 with the help of XDA Senior Member irfanbagus, who brought dual-boot support to the Galaxy Y earlier this year. It is basically the stock 2.6.32.9-ideos Froyo kernel, with no additions other than dual-boot features. Your device must have the stock kernel in order to go ahead with the process. The complete process involves installing this kernel and preparing your SD card to run the second ROM.

For more details and to get on with dual-booting, head over to the forum thread.

And the First 4.2 Port Goes to…

As we have mentioned in the past, the need for our devices to be up-to-date is no longer a luxury or even a necessity, it is an addiction. Because of this, whenever something like this happens, everyone’s eyes shift focus to developers who work on AOSP-based ROMs. People become static, glued to their PCs with sweating palms and foreheads, and with a few extra keyboards due to potential F5 key breakage. All of the sudden, a new thread emerges with a title that has a little something which stands out (no, not Off-Topic)… “4.2.” Boom! Happiness and joy fill our hearts, as we click on the download links as fast as humanly possible to try and get a hold of the new goods.

The dealer of happiness this time around happens to be XDA Recognized Developer randomblame, who has ported 4.2 from the newly  dropped AOSP source onto the aging (but still fighting) Acer Iconia A500. As you would likely expect (and the dev makes this painfully obvious in the first sentence of his OP), the build is a first and as such, is riddled with bugs and things that do not function properly or at all, such as access to the SD card, audio, camera, and Bluetooth. On the flip side, WiFi works, so you will still be able to enjoy the online experience, regardless of the broken device features.

If you do download it and flash it, please understand that the build is nowhere near final, but will become more usable as time goes by. Please report issues and feedback to the dev (if they are in logcat form, it would be better). Happy flashing!

This is a first build there are issues which will be sorted throughout the next several days. This is proof of concept.

You can find more information in the original thread.

Want something published in the Portal? Contact any News Writer.

[Thanks randomblame for the tip!]

Team Win Recovery Project Updated to 2.3

The last time we brought you news about TWRP, it was to announce that TWRP 2.2.2 had been released. It had fixed a lot of bugs from the initial release of TWRP 2.2 and added a few new features. Very recently, TWRP has been updated again to version 2.3.

There were a whole bunch of awesome improvements with TWRP 2.2 and a lot of unique and brand new features as well. TWRP 2.3 promises no less. The official change log includes:

Rebased onto AOSP Jelly Bean source code
Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
ADB sideload functionality from AOSP is included in 2.3, see this link for more info
Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
Faster boot times
Added charging indicator while in recovery (only updates once every 60 seconds)

Additionally, XDA Recognized Developer Dees_Troy has reported that there is now support for spaces in backup names. Before, if you added a space to the name of a backup, it would not restore. Now users can use whatever naming convention they want.

One of the biggest changes, though, is all of the TWRP being rewritten in C++ and its move to recovery API 3 instead of API 2. With the code rewrite, it will allow TWRP to update more quickly and with more stability. With the API 3 change, it means that some flashable zip files may stop working because the developer needs to update the update-binary. If you don’t want to wait for the developer, or the developer has ceased working on the project, you can find one to use on TWRP’s official website. To install the latest TWRP, you can use the Goomanager application. Simply open the application, hit menu, and install open recovery.

If you want to check out the latest TWRP recovery for your device, check one of the links below.

TWRP 2.2.2 Update Brings Several Improvements and Bug Fixes

Team Win Recovery Project was recently updated to bring several improvements and bug fixes to the popular custom recovery. For those unfamiliar, TWRP is a custom recovery with an impressive touch-based GUI that packs quite a punch and makes recovery operations a flash, no pun intended.

TWRP is officially available for dozens of Android devices, and is quickly becoming the custom recovery solution of choice for many enthusiasts. It is an open source project and utilizes the open source Open Recovery Script, which Team Win created.

This is the third update to TWRP in the recent months, after 2.1 and 2.2 that we previously featured. According to the official changelog, the changes made in this 2.2.2 update include:

  • Significantly improved sd-ext handling (ext partitions on sdcards)
  • Changes to kinetic scrolling in file selectors
  • Fixed a problem with using periods in backup names
  • Fixed problems in XML layouts with mounting system and USB storage
  • Fixed a problem with unmounting a partition before formatting during restore
  • Add Jelly Bean decrypt support
  • Updated 320×480 theme to match others (thanks to Llewelyn)
  • Improve “symlinking” of /data/media to either /sdcard or /emmc
  • Added sanitizing of device IDs for invalid characters (thanks to bigbiff)
  • Fixed free space calculation when switching backup devices on /data/media devices
  • Fixed a problem with using OpenRecoveryScript to create a backup without providing a backup name

Want to grab TWRP 2.2.2 for your device? Head over to the appropriate forum thread link below for your device:

You can also install TWRP 2.2.2 directly to your device using GooManager or download it from the TWRP website, where it may be available for more devices than listed above.

Jelly Bean for the MyTouch 4G Slide, Desire HD, and Motorola Defy

Since its release, Jelly Bean has found it’s way onto dozens of phones. This won’t stop any time soon, with even the legendary CyanogenMod offering a CM10 preview.

Among the newest devices to receive Jelly Bean include the T-Mobile MyTouch 4G Slide, Motorola Defy, and the HTC Desire HD. These devices are all a little older than some would expect to be receiving ports. But if the HTC HD2 can get it, newer devices should be able to as well.

The MyTouch 4G Slide Jelly Bean ROM was developed by XDA Senior Member xmc wildchild22 and is built from source. XDA Senior Member Quarx is responsible for the Motorola Defy ROM, and XDA Recognized Developer randomblame (also responsible for the Iconia A500 JB ROM) brought Jelly Bean to the Desire HD.

For all three ROMs, there’s a comprehensive list of things working and not working. For the MyTouch 4G Slide, here’s what isn’t working:

Camera
Radio
Sound
Notification LED
Charging
Sdcard
Wifi
onscreen keyboard (I have to wait for the patches form CM for our hard keyboard phones)
Auto brightness

For the Desire HD, which has a much shorter list:

camera
mic – works in calls but crashes apps
audio routing – in phone calls audio comes out the rear speaker and when headset is plugged in audio comes out of both headset and speakers

There isn’t a running list of what’s not working on the Motorola Defy, but there is a list of things that are working:

 

Phone
Mobile Data
USB
Mass storage
Sensors
Camera(Photo)
GPS/AGPS
Audio (thanks to maniac103)
Video rec/play
Panorama
FM-Radio

 

For the MyTouch 4G Slide and the Motorola Defy, the list of things not working is still pretty long—so they cannot yet be considered daily drivers. They are stable enough to try out, however, to see what Jelly Bean is all about. The Desire HD ROM, on the other hand, seems to be a bit more suitable for every day usage.

For additional information, download links, and more, click the corresponding link below:

Update: Between the time of writing and publishing, the Defy port has made incredible progress, now even featuring hardware acceleration. It is now suitable to many as a daily driver.

Unofficial CM10 for the Kindle Fire and Original Galaxy Tab

We are well into the march of Jelly Bean, and the number of devices that have gotten Google’s latest and greatest is quite staggering. There are so many, in fact, that we are dedicating entire XDA TV episodes to it. A couple of the latest devices to get Jelly Bean—more specifically unofficial CM10 builds—are the Amazon Kindle Fire and the Samsung Galaxy Tab.

The Amazon Kindle Fire was given unofficial CM10 by XDA Senior Member twa_priv, and the Galaxy Tab was given its goods thanks to XDA Recognized Developer cdesai. In both instances, as has become typical for new builds, the ROMs have quite a bit working and quite a bit broken.

No list of things not working is provided for the Kindle Fire, but given that the change log is based almost entirely around adding features and fixing bugs, it’s safe to say that twa_priv is well on the way to fixing everything. Things not working in the Galaxy Tab port include:

Auto-Rotation animation looks weird.
Isn’t really smooth
External sd doesn’t work (isn’t mounted)
Will add more as they are discovered

The Kindle Fire version also features some additional modifications to include features from the SGT7 project. However, one should note that while they are fun to play with, neither of them is really geared yet for daily use.

For additional info, check out the Amazon Kindle Fire JB thread or the Samsung Galaxy Tab JB thread.

SGSII i9100 Joins i9100G, Gets Jelly Bean

Jelly Bean is seemingly spreading like the plague—no matter what you do, someone finds a way to give it to your device. However, unlike the plague, we actually look forward to Jelly Bean spreading.

We told you a few days ago how the Galaxy SII i9100G (OMAP) had received Jelly Bean. Now thanks to XDA Forum Member kalgecin, the original, Exynos-bearing variant of the Samsung Galaxy S II is now welcome at the Jelly Bean party.

So far the ROM is in the early Alpha stages of development and features:

WORKING
[-] Boot
[-] Bluetooth (reconnects sometimes)
[-] GSM/DATA

NOT WORKING
[-] Sound
[-] WiFi
[-] 3G
[-] Camera
[-] H/W accelerator
[-] ADB debugging doesn’t start automatically if switched on with cable pluged in

As always when using an Alpha stage, source build remember that there are unexpected bugs that will creep up and cause problems. Also, as this is not a daily driver ROM, the developer request that you submit logcats and know how to use ODIN (or Heimdall) in case the ROM fails to boot.

If you’re a developer looking to contribute and get this bad boy fully functional or a user looking to be a tester, head on over to the original thread and give it a go.