Also included in this release are advanced communications and infrastructure improvements to more fully integrate with Fisher ROC and ROC Plus Controllers providing customers with enhanced interoperability.
Android 3.x Honeycomb for the Samsung Galaxy Tab Download Rom: - (New development thread.) The Alpha 2 Series Archive Alpha 2.5 Download & Installation: GSM: Download the installation guide for specific instructions. Download the rom. CDMA: Download and instructions page. User submitted tips, tricks, mods, apps and notes for 2.5: (if you wish to add to this list, PM your additions to me) jjhiza's amazing app post: Ssserpentine: “Tired of that red border?
Android 3.2 Honeycomb Download
1) Open up Dev Tools 2) Go to Development Settings 3) StrictMode Visual Indicator - turn it off 4) back out of app and now open it again. 5) If this doesn't get rid of MOST of the red borders, REBOOT and open app again.” Ssserpentine: “WANT IMPROVED UI, LESS RED BORDERS, LESS FC'S AND SCROLLING AND SOFT KEYS THAT PLAY NICER? Try adw launcher. For some reason just having it installed helps just as much as using it.” mattman83: 'to mount UMS if you have no external SD then use the below line. Same changes as above. Echo /dev/block/mmcblk0p1 /sys/devices/platform/s3c-usbgadget/gadget/lun1/file' corodius: 'if you have an external sd, by extending the commands to: su mount -t vfat /dev/block/mmcblk0p1 /mnt/sdcard/ mount -t vfat /dev/block/mmcblk1p1 /mnt/sdcard/externalsd/ This will mount the cards the way they are originally mounted in the samsung/overcome roms.' Anfalas: 'get Gallery3D to play nice by going into settings, applications then 'Clear Data' - works great, can change wallpaper etc.
Only downside is it has to be done each reboot.'
LAST UPDATE: 6/21/2011 (alpha 6.0) STANDARD DISCLAIMER: USE AT YOUR OWN RISK. By running this firmware mod, you agree that there is the possibility that you may brick your device and neither myself, Slatedroid nor Viewsonic are responsible for supporting you if that occurs. In this case, it is required that you learn and setup nvflash prior to running this mod. A BIG THANK YOU TO MRGUY, DJSTEVE, Clemsyn, Pershoot and all the Adam and VEGA developers, for this excellent port!!!!! Most of this port comes from what they've created.
I'm just tweaking it a little for GTAB users and packaging it. The alpha 6 is a mashup of both HC16 and the VEGAComb 1.5.1 beta (I'm still calling it an alpha, given the OpenGL issue). Their forum is here: What this is This is the 'HoneyCreamAdam' HC mod port for the 1.2-based GTab. This will flash your boot.img, recovery, bootloader and system, so be aware of this.
You are also REQUIRED to wipe your user data after you flash to this ROM, so please BACKUP ALL DATA before attempting this. The 1.2 GTAB dev branch and the Adam dev branch seem to be the same exact branch, and the kernels are (mostly) compatible. And we are currently using Clem's HC-compatible kernel, which is 1.2 branch based. UPDATE for alpha 2.2 - nvflashing is no longer required. The space has been reduced to the point that a vanilla GTAB can now be flashed to run this. Recommended Pre-requisites 1. Setup and learn how to use nvflash.
This is your backout in case something bad happens, so I would recommend you understand how to use this, in advance. Link details: nvflash is specific to Tegra 2 devices only.
For users on 1.1-based ROMs (ie. Stock, VEGAn, gADAM TNT Lite 4 etc.), learning nvflash is HIGHLY recommended as the risk of a soft-brick is higher. Have your device on a stock 1.2-based ROM / mod baseline. For example, build 4349 is the latest 1.2-based stock ROM, as of this writing. Details on how to return to a stock 1.2-based ROM are here: Other 1.2-based ROMs should also work safely (ie.
Century Eyes, Mountain Laurel, Brilliant Corners). A 1.1-based source is more risky (see below) but is possible and I have tested 3588 stock to BOS directly, with no issues. Installation for 1.2-based stock/mod users (ie. TNT Lite 5 / TwoTapsX / 4349 stock / Century Eyes / Mountain Laurel) - Extract the RAR to the root of your internal memory. So, you'd have a recovery folder and an update.zip on the root of the mounted drive. Reboot into recovery.
The update should occur automatically (click on the Home button to see the build details while it's running). Once completed, it should reboot automatically. The device should take some time to initialize (two to three minutes, so be patient), then will boot into the GUI. If it gets stuck (and it likely will if you came from a different ROM), reboot into recovery one more time and wipe data / factory reset and reboot.
I would NOT recommend setting up any Wifi at the initial setup screen, wait until the after the setup before doing that (some users, myself included, have had issues doing this at the initial setup screen so I would skip it). Installation from previous versions of Bottle of Smoke / HoneycreamAdam Since there's no mount to PC option yet, you can upgrade to each new version via clockworkmod. As of alpha 2.2, cwm is flashed with the HC ROM. So this is my recommendation on how to upgrade: - Download new version of HC, and extract the update.zip from the RAR file. Run cwm (as of alpha 2.2, I added it to the ROM). Go to Mounts and Storage, then mount USB.
The internal memory should now mount to your PC. Add the new update.zip somewhere to your internal memory. What I usually do is create a 'backups' folder, drop the version in there and rename it to something more readable like 'BOSAlpha2.2.zip'. Unmount the device PC from your PC, then unmount from cwm. Then run the update.zip as you normally would and choose that file you just added.
Btw, as long as you stay on the 1.2 dev branch, you can add 4349 stock or any other 1.2 based ROM in there and use cwm to install, without risk of brickage. Installation for 1.1-based stock/mod users (ie. TNT Lite 4, VEGAN-Tab, G-Harmony, Calkulin's ROM etc.) - Ensure that your device is running build 3588 standard recovery. This is a requirement to minimize the risk of a soft-brick - I cannot stress this enough!
GADAM 1.3.0+ and TNT Lite 4.3.0+ have a Recovery Pack built-in to allow you to easily add standard recovery, if you are using clockworkmod. Do NOT use clockworkmod to flash up to a 1.2-based ROM or you WILL soft-brick your device. For other 1.1-based mods, you can install the 3588 Recovery Pack or flash 3588 standard recovery via an update.zip file. Or, flash to 3588 stock (with stock recovery) for the safest baseline. I want to stress this, as this is important - BE VERY CAREFUL on a 1.1 source. If you flash with clockworkmod from a 1.1 ROM to a 1.2 ROM like Bottle of Smoke, YOU WILL SOFT-BRICK your tablet 100% of the time.
If you are not sure if your device has 3588 stock recovery, don't take the risk - flash to 3588 stock before you attempt this HC mod! Other than these caveats, the installation is the same as 1.2 users, above. Backout This is a 1.2-based mod and I would recommend that you backout to the latest stock ROM (4349, as of this writing). Please see this post on instructions on how to flash to a stock 1.2-based ROM: If you want to backout to a 1.1-based ROM or mod, you MUST have a standard 1.2-based recovery (like 3991 or 4349). Since this ROM installs a 1.2-friendly clockworkmod, then you need to remove it - see the 'Recovery Pack' section on how to backout to standard recovery.
Again, running stock 4349 is your best best to get to a 'gateway' 1.2 ROM before you jump back to a 1.1 ROM/mod. Once a standard 1.2-based recovery is confirmed installed, you can use any of the following ROM's to backout to a 'legacy' 1.1-based firmware: 3588 stock, TNT Lite 4.3.0+ or gADAM 1.3.0+. You would just use the standard instructions for these (ie. Add the update.zip and recovery folders to the root of your drive, and reboot into recovery).
Other 1.1-based ROM's may not work (ie. VEGAn or any of the GB ROMs), so PLEASE tread carefully here!
I have tested all of these scenarios and the backout does work, most of the time. However, as always, there is a risk here so I would HIGHLY recommend that you setup and master nvflash BEFORE you attempt backing out. That's just in case the backout fails and you need an emergency procedure to unbrick your device. NOTE FOR TNT LITE 4.3.0+ / gADAM 1.3.0+ - recovery will be broken, after the downgrade. In this case, just run their Recovery Pack and you can fix it (see the TNT Lite first post on XDA, for details).
Also see gojimi's post on backing out from a 1.2-based ROM to a 1.1-based ROM: 1.2-Based Recovery Pack I have included part of the 4349 recovery pack in the last few alphas in case you need to backout to standard recovery. To do this, either use adb or a Terminal Emulator, then type 'su' and then this: fixrecovery.sh (this adds back standard recovery) cwmrecovery.sh (this adds back cwm recovery) - Downloads alpha6.0 Link: md5sum: 77887b14bd16e5df085d729cafeebe66 (updated 6/21/2011) Changelog: (a6.0) Added Pershoot GB kernel. Seems stable so far, adds USB mounting (thus cwm was removed from the ROM, no longer required) (a5.2) Based of HC16 - Gmail possibly working better(?), media scanning is working, Gallery is working for me. (a5.1) Still based on a5.0, but fixed the blank browser. (a5.0) Update was pulled, due to issues. Updates to reflect Adam HC15 changes (storage is fixed, but we lost the enhanced shutdown screen) (a4.1) Sound Settings now work (storage does not, however), tweaked the app selection a bit.
(a4.0) First attempt to combine aspects of VEGAComb beta 1.5.1 and Adam HC14. (a3.3) Tweaked lowmem settings (thanks newbe5!) and added ACER buttons back (thanks absorber!) (a3.2) Sleep improved, constant restarts after a data wipe seems to be corrected, as well. (a3.1) Fixed the messy dalvik heap size. (a3.0) Updated to Adam u14 (this moves from an ACER UI to the ASUS UI). (a2.4) Small additions to /data/app (for standard recovery users only, adds additional apps to user data). Added run-parts for Clem. Updated cwm to rev5.
(a2.3) Updated to Adam u13, moved Books, Maps, Street to /data (won't install with cwm, keep in mind). This freed up another 15MB of space on /system. Gmail / Email are now working, thanks to u13 and the VEGA devs! If you are using cwm, you can sideload the data apps later or get them from the Market. (a2.2) Updated to Adam u12, adds the new mod name. Also adding 1.2 bootloader and cwm 3.0.2.8 recovery, for 1.1 jumpers.
(a2.1) Gapps! At least the Market, and YouTube (again, a big thanks to MrGuy for making that happen!) updated to be based on the Adam update10 image. (a2.0) Version 11 Clemsyn kernel added for HC, gsensor fixed (thanks to Zebwen for the tips!), newer snapz54 boot logo. (a1.2) Sound!
(thanks to HomerSP for the fix, and newbe5 and blazingwolf for testing!), standard video might work (I tested an mp4). Audio includes EQ, which is actually superior to any vendor build I've used. (a1.1) Added root (thanks to Koush for the Xoom su!), a few additional apps, better boot screen (thanks snapz54!) (a1.0) First release - Issues / Workarounds (this is still an alpha version with some items outstanding) See this TR Wiki for an updated list of issues:. Ours will be very similar. But to summarize: - Camera isn't working (pulled out the app for now) - Browser is working, but OpenGL is disabled for it to work. That means no Flash video on the stock browser.
(High-def) video playback does not work, yet. For the Market, REBOOT after setting up your Google ID for the first time. This seems to be needed for alpha 6, at least. I would recommend turning off Compatibility Mode (which is why I added the Spare Parts apk). It will correct screen issues for some apps, and over in XDA it's been said that it might improve Market downloads as well. For overclocking, you can use 'CPU Master', in the Market (thanks Note that CPU Master free does not install to load on boot like the paid version. You have to set the CPU speed manually each time you start up.
So I am excited and want to try. Is it me or is the link not up yet?
I'm building it out. Pre-req is nvflashing to 4349, first. This is an absolute requirement as the Honeycomb port is actually larger than what a default GTAB setup can handle. In my 4349 nvflash setups, I actually upped the system.img to 250MB (from 192MB), which will be enough for now.
I might need to up that further, later on. This is mostly the Adam devs. All I've really done is tweaked the boot logo and fixed the power / volume buttons. We're using their kernel for now, which is compatible with a GTAB as long as you are on the 1.2 dev branch. Edited by roebeet, 09 May 2011 - 03:16 PM.
Thanks for the early look, I'll be following along as it matures. When it gets to beta stage, I'd be happy to jump in as a tester, but I need something reasonably functional since I do use my gtab for its intended use Seriously though, looks awesome. Is the 512mb memory an issue for HC, or will it be OK do you think? I think it will be OK. The bigger issue is the storage space, but if we take some from the cache partition, I think we will be OK there as well. That's why we need to nvflash our devices as a pre-req. Thanks for the early look, I'll be following along as it matures.
When it gets to beta stage, I'd be happy to jump in as a tester, but I need something reasonably functional since I do use my gtab for its intended use Seriously though, looks awesome. Is the 512mb memory an issue for HC, or will it be OK do you think? I'm thinking it will run good with 512mb since the nook color runs HC, plus nook color only has a single core at 800Mhz CPU and the G Tablet has a dual core at 1Ghz, should see a great improvement over nook color.
My android devices running versions their makers never intended: droid X(gingerbread), Gtablet(honeycomb) If not for the hard work and dedication of a few, this would be a harsher statement: SERIOUSLY CONSIDER WHAT YOU ARE DOING before you EVER purchase another viewsonic product. Viewsonic is a big evil company like the rest of them that will promise you whatever they have to to get your money and then backout with no intention of fufilling the contract you enter into as buyer-seller. Whenever you tell people how great your Gtab is, don't ever forget to tell them, just how BAD viewsonic is too. 'moderators are great, but only in moderation' -anonymous.
The Karbonn A2 owners may also want to keep their device up-to-date. The boondocks vf saison 1 episode 2. So we thought of giving you a tutorial of how to upgrade Karbonn A2 to Android 3.1 Honeycomb. With new version of android operating system on your device, you will have more benefit. Your device will have more feature, more secure, more fast performance, and more cool he.3x. But prior to telling you how to install Android 3.1 Honeycomb on Karbonn A2, let’s see what do you want in order to be able to perform the installation.
You will have to download 3.1 Honeycomb Karbonn A2 ROM. You will also have to root your Karbonn A2 to prepare it for Android 3.1 Honeycomb upgrade. Discover how to root Karbonn A2 and install Android 3.1 Honeycomb from here.
Here are the download links of the files you want to update Karbonn A2 to Android 3.1 Honeycomb. Just before beginning to upgrade your Karbonn A2 to Android 3.1 Honeycomb don’t forget to backup your information, as contacts, text messages and the apps installed from Google Play Store who maybe lost when the installation finishes. Now let’s see how to update Karbonn A2 to Android 3.1 Honeycomb: 1. Install the ROM Manager on your Karbonn A2. Get it from Google Play Store, then install the clockwork mod recovery. Connect your Karbonn A2 to your PC employing the USB information cable.
Copy the “Karbonn A23.1 Honeycomb.zip” file you downloaded to the SD memory card. Restart your device in the recovery mode using ROM Manager. As soon as in Recovery Mode, go to ROM Manager and select backup / restore to back-up your information.
From the Recovery Menu do a total data erase (including Delvik Cache). When completed, go back to Recovery Principal Menu and choose Flash ROM from SD Card. Navigate the location you copied the ”Karbonn A23.1 Honeycomb.zip” file and follow the directions for installing Android 3.1 Honeycomb on your Karbonn A2. As soon as the installation is over, just reboot your Karbonn A2 device, and here you go, you’ve just upgraded it to the new Android 3.1 Honeycomb.
Description of Root Android Mobile We love Android, but rooting your phone can give you the opportunity to do so much more than your phone can do out of the box, With the help of free and best android root checker app you can root android smartphone like smart phone. 97% android devices are supported this method. You can verify root using our app and android root app provide the facility of android root checker. Install free application and follow the instructions given in the application. How To Root Android 1/8: 1. Popcap zuma's revenge download.
Install the Root exe from this link 2. Download android root app windows base application from this link. Connect your smart phone in debugging mode via USB with PC 4. Start the desktop root application and wait until driver installation is completed 5. Click on the Next or Root Button 6.
Wait until rooting is completed 7. Restart your Device and enjoy 8. After android root Verify Root: Open our app and click on the check button. After few seconds you can see the details about your smart phone.
The Karbonn A2 owners may also want to keep their device up-to-date. So we thought of giving you a tutorial of how to upgrade Karbonn A2 to Android 3.1 Honeycomb. With new version of android operating system on your device, you will have more benefit. Your device will have more feature, more secure, more fast performance, and more cool he.3x.
But prior to telling you how to install Android 3.1 Honeycomb on Karbonn A2, let’s see what do you want in order to be able to perform the installation. You will have to download 3.1 Honeycomb Karbonn A2 ROM. You will also have to root your Karbonn A2 to prepare it for Android 3.1 Honeycomb upgrade.
Discover how to root Karbonn A2 and install Android 3.1 Honeycomb from here. Here are the download links of the files you want to update Karbonn A2 to Android 3.1 Honeycomb. Just before beginning to upgrade your Karbonn A2 to Android 3.1 Honeycomb don’t forget to backup your information, as contacts, text messages and the apps installed from Google Play Store who maybe lost when the installation finishes. Now let’s see how to update Karbonn A2 to Android 3.1 Honeycomb: 1. Install the ROM Manager on your Karbonn A2.
Get it from Google Play Store, then install the clockwork mod recovery. Connect your Karbonn A2 to your PC employing the USB information cable. Copy the “Karbonn A23.1 Honeycomb.zip” file you downloaded to the SD memory card. Restart your device in the recovery mode using ROM Manager. As soon as in Recovery Mode, go to ROM Manager and select backup / restore to back-up your information.
From the Recovery Menu do a total data erase (including Delvik Cache). When completed, go back to Recovery Principal Menu and choose Flash ROM from SD Card. Navigate the location you copied the ”Karbonn A23.1 Honeycomb.zip” file and follow the directions for installing Android 3.1 Honeycomb on your Karbonn A2. As soon as the installation is over, just reboot your Karbonn A2 device, and here you go, you’ve just upgraded it to the new Android 3.1 Honeycomb.