[ROM - 1.2] BETA ICS 4.0.X - Team DRH (Update 07/02/12)

fosser2 · Mar 1, 2012

CLICK PIC FOR TEAM HOMEPAGE

Now for the moment you all have been waiting for...

Team DRH (Dirty Reset Hole) is proud to announce the public beta for Ice Cream Sandwich. The name "DRH" came from the hole that all of the developers had to drill into the back of their tablet to access the on-board reset button. As you all probably know, development for this project started back in August and has finally developed into a mostly stable release. Ice Cream Sandwich is a huge jump for the G-Tablet community because along with the building of ICS specifically for SMBA1002 (G-Tablet), the Linux kernel backbone had to be reworked from the ground up.

DISCLAIMER
Attention commuters of the intertubes! The group of individuals known as Team DRH take absolutely NO RESPONSIBILITY for any DAMAGE that YOU cause to YOUR device! This "labor of love" we call and Android ROM comes AS IS and is not an official release by any means. If you have not already SOILED your device by flashing a custom ROM then to do so will VOID any WARRANTY you may have left. Team DRH and its affiliates are not responsible if your G-Tablet does any of the following: Explodes, Flies off to space to battle the Flying Spaghetti Monster, Is generally awesome, solves world hunger or explodes... again. (OK We take responsibility for you Tablet becoming Awesomesauce.) So in essence... Flash this totally rad ROM at your own RISK and prepare to Spontaneously Combust with AWESOMENESS!

WHAT WORKS

WIFI
Hardware Acceleration
Sleep!
WiFi
Bluetooth
Sensors
Sound
USB/MTP (If you plug in USB while your tablet is asleep you will have a SOD)
Capacitive Buttons
Hardware Buttons
USB Flash Drives
Proper SD Card Mounts
HD Videos
More to come...

WHAT'S NOT WORKING

Camera
Microphone (Works but drops after 6-8secs)
Possible ROM Slowdowns
HDMI Audio
More to come...

List of Common ICS Problems
http://xdaforums.com/showthread.php?p=23146434

HOW TO INSTALL

Boot into current version of CWM and "Wipe data/factory reset"
Partition Internal SD Card (2048M/0)
Turn tablet off
Download the following file <--- Seriously don't skip this step unless you are 100% positive that you have a 250M system partition
NVFLASH the file following the instructions that are included for Windows/Linux users
Upon reboot of tablet let T&T fully boot and then shut it down
Reboot into recovery
Flash the Rom/Gapps
Enjoy

HOW TO INSTALL VIA DRH NEWS APP
1. Open DRH News App (You Will be notified that you have an update)
2. Download Update
3: Reboot into CWM
4: Wipe Data and Cache
5: Flash Update.zip
6: Flash Your Gapps
7: Reboot
8: Enjoy

FINAL THOUGHTS
This build has been tested but not to the extreme. It is called a "beta" test for a reason. Sleep is properly working and I have not had to use my reset button in weeks. I'm not trying to scare anyone but the possibility of a kernel panic is still there. This build is very stable and deserves the beta tag but if you find yourself in a snag you might have to press the internal reset button. Here is a picture of where to find the button if you are really in a bind. PICTURE If you have the balls to open your tablet, just drill the reset hole while you're in there. You already voided your warranty

DOWNLOAD LINK
ROM/GAPPZ Package: TeamDRH ROM
ROM (Includes GPS Mod): TeamDRH GPS ROM <-- Only use if you physically installed the internal GPS mod as documented here. This rom is not updated to 1.3 yet.
Remember this is a beta build. It will run nicely for the most part but I'm sure that there will be glitches a quarks that we have not seen. I will keep the what works/doesn't work section updated so we don't have tons of posts cluttering the thread. Also these links will be updated pretty regularly when we have new builds to release.

CHANGE-LOG

The ROM's system folder was very close to the max size our system partition could handle on the G-Tablet and with any bad blocks, it was more than the G-Tablet could handle and installing GApps made it even worse. So on initial boot everything was fine, because all the apps that make temporary files don't make them until after initial boot, but in the process of making those temp files it corrupts system files that are already loaded and running, so on a reboot the system fails because the files are now corrupted. This also effected the overall speed of the ROM. This should be fixed with the increased system partition from 200M to 250M.

TeamDRH-ICS-Beta-1.3.zip 07/02/12

Kernel changes to help stability
Wifi Updates (latest bcmdhd android code)
Changes to sound (should reduce audio lag)
Mic Partially Working (Will record for roughly 6 - 8 seconds)
Dock Support with HDMI and Ethernet (No Sound over HDMI yet) This includes a dock clock mode
"Blinkies" Have been fixed
Updates to CM9 code. Now includes lots of the CM9 features
Overall stability improvement
New Boot Animation
Added Sound to Boot Animation (Optional)
New Default Wallpaper (created by annel)
Installer Updated
Gappz Changes
Updated Google Plus
Updated Google Books
Updated Google Chrome Browser
YouTube Updated
Google Drive Updated
Google Play Updated
Google Currents Updated
Added Google Magazines (From JellyBean)
Added Google Ears (From JellyBean)
Probably more changes too this is just all I could remember

HOW TO INSTALL MTP DRIVERS
Open Device Manager and find the offending TeamDRH MTP device.
Right-Click and choose Update Driver Software
Then choose Browse My Computer for Driver Software
Then click Let Me Pick From a List of Device Drivers on My Computer
Then choose All Devices
When that list populates choose Standard MTP Device followed by MTP USB Device
Click Yes to the warning and VIOLA!

Hope you all enjoy the TeamDRH gTablet ICS preview!!

POSSIBLE MARKET ERROR
Upon start up Android Market may give you an error when you try to download an app. The fix for this is to go into settings/applications and force close market. Upon doing that clear app data and you should be good to go.

IF ALL ELSE FAILS (Only do this If I tell you too)
Try doing what is posted here

If you like this project and appreciate the extreme amount of time that the devs put into this please donate:

Donate to TeamDRH: LINK

If you would like to donate to single people:
Ch3vr0n5: LINK
Treznorx: LINK
Fosser2: LINK
The3dman: LINK
Plastikman: LINK
Mayday_jay: LINK
Dwagner:
Tlb1961: LINK
Busa_blade:
Jaybob413:
Clemsyn: LINK

(This is not a complete list yet changes are still being made)

Information on G-Tablet Camera!!!
http://www.slatedroid.com/topic/290...update-040112/page__view__findpost__p__346429

Video (courtesy of pagantek):

Pictures:

fosser2 · Mar 1, 2012

TeamDRH Change-log:

TeamDRH-AOSP-Preview-1e-LDPI.zip 02/08/12

USB/MTP
Vold.fstab
USB Flash Drives work if plugged in when tablet is off, then booted
SystemUI notification toggle bug
TeamDRH Welcome in Trebuchet
3g Icon
Few other little adjustments...

YAGP_GummyBear_Jay_GAppZ_v2.zip 02/08/12

Few extra added apps
Google Maps
Google Chrome Beta

TeamDRH-AOSP-Preview-1F-LDPI.zip 02/16/12

USB/MTP Now works even if plugged in on boot. If your tablet is asleep and you plug in USB your tablet will get SOD!!!
USB Flash Drives work should work if plugged whenever
New Touchscreen driver (should be more responsive)
New Battery Driver (should perform better. Has a charging icon issue.)
Capacitive keys should now fully work
Bluetooth now works
Few other little adjustments...

3DGtaB_GAppZ_v6b.zip 02/16/12

Few apps added/deleted
Tweaked Permissions
Should perform faster

TeamDRH-ICS-Preview-2A.zip 02/29/12

Added ROM control in settings.
Adjusted Dalvik Cache sizes for better performance (thanks community)
Much faster Read/write speeds (probably better than Froyo)
Many i2c/clock changes to the kernel to improve stability
Amount of system ram increased from 295M to 359M!
Other various tweaks and speedups built into the ROM
Games should play better in this release

3DGtaB_GAppZ_v6c.zip 02/29/12

Few apps added/deleted
Tweaked Permissions
Should perform faster

TeamDRH-ICS-Preview-2B.zip 03/01/12

Moved some apps to the /data folder to reduce the size of the /system folder
New Boot Img - Fixes cache size
Added FakeIMEI to the framework so some apps that request one don't crash (ex. XDA App)

3DGtaB_GAppZ_v7A.zip 03/01/12

Moved some apps to the /data folder to reduce the size of the /system folder

3DGtaB_GAppZ_v7A_LiteEdition.zip 03/01/12

Added a new version of GAPPS
Very minimal app install (includes: Calender, Music, Youtube, Gmail, Gallery, Market)

3DGtaB_GAppZ_v7B.zip 03/17/12

Added new market/music Google play apps

3DGtaB_GAppZ_v7B_LiteEdition.zip 03/17/12

Updated Google applications

TeamDRH-ICS-Beta-1.0.zip 03/17/12

Changed ROM naming convention for future use
Overclocking (max 1.2GHz for now)
ROM is reworked and running on CM9 as a base
Noticeable speed improvements
250M system partition is a MUST now
Stability is improved
In-ROM battery stats should now be fixed for almost everyone

3DGtaB_GAppZ_v7B.zip 03/17/12

Added new market/music Google play apps

3DGtaB_GAppZ_v7B_LiteEdition.zip 03/17/12

Updated Google applications

3DGtaB-GAppZ-LiteEdition-8.0.zip 03/18/12

New DRH-News App
Added Play Store (Google Market)

3DGtaB_GAppZ_8.1.zip 04/01/12

Added Play Store (Google Market)
All Google applications are now updated and latest

TeamDRH-ICS-Beta-1.1.zip 04/01/12

Performance enhancements (based on some SuperCharger settings)
Kernel updated with new governors
Kernel updated with new i/o schedulers
Android updated to 4.0.4
Rom control has additional performance settings

3DGtaB-GAppZ-8.2.zip 04/07/12

Updated Gmail to 4.0.4
Update to Google Books
Fixed calender sync issues some people were having
Added the new installer that TeamDRH will now be using! (it's awesome!!!)
GAppZ full and lite will now be an all inclusive package. Just flash and follow the instructions.

TeamDRH-ICS-Beta-1.2.zip 04/21/12

ROM has been updated to include various performance tweaks
Kernel has added touchscreen fix (hopefully fixes most games)
Most i/o schedulers removed for now due to incorrect throttling
Rom control has additional performance settings and is reorganized
WIFI modules updated
Incorporated TeamDRH Aroma installer (now includes ROM and GAppz)
ROM does have issue where at times, will not go to sleep (screen will turn off then flash back on) aka "blinkies"

alneez2000 · Mar 1, 2012

Wow I bought my Gtab Yesterday and this is the first thing I have tried... it is mind blowing !! If the Out-of-the-box feeling of this tab disgusted me to 50% this has excited me to 200%

Keep up the good work guys !!

Just one thing - the text on my gTab appears kind of blurry is it a resolution thing or is it because of the screen.

Overall superb !! Thanks a million for making my $275 INVESTMENT worth it !!

Some Donation Definitely Headed Your Way.!!

fosser2 · Mar 1, 2012

For those of you who are really struggling to install this build here is a (most likely) fail-safe method of getting it to work. It is lengthy and sucks, but is most likely worth it in the long run.

NVFLASH the following http://www.mediafire.com/?brd9u48iefdqcc7 Upon reboot, boot into recovery and partition sd card. 2048M/0M
Turn off tablet
NVFLASH the following (full 1.1 stock) http://www.mediafire.com/?48roksff1xji3y0
Fully boot into TnT (yes, you have to do this!)
Turn tablet off
NVFLASH this (full 1.2 stock) http://www.mediafire.com/?0rgkcd0k4v30z4u
Let TnT fully load yet again
Next NVFLASH TeamDRH recovery found here http://www.slatedroid.com/topic/28751-kernel-12-clockworkmod-5504-touch-recovery-team-drh/
Boot into recovery
Mount usb and delete all folders that were made from TnT. Then copy on ROM and Gapps.
Flash our current build of ICS (found in OP)
Cross fingers and hope it boots

The technical aspect behind this is supposedly TnT tags bad blocks in the nand and moves them. This method got me out of a nasty bootloop spree the other night, so it does work. If this works for you, let me know.

rajeevvp · Mar 1, 2012

fosser2 said:
The technical aspect behind this is supposedly TnT somehow re-allocates bad blocks in your internal sd card.

Very unlikely.

The internal SD card is not a "raw" NAND device, so any bad block handling will be done, transparently, by the hardware. I doubt if TnT can get to that layer. In any case, most of those steps only touch the built-in 512MB NAND flash.

fosser2 · Mar 1, 2012

rajeevvp said:
Very unlikely.

The internal SD card is not a "raw" NAND device, so any bad block handling will be done, transparently, by the hardware. I doubt if TnT can get to that layer. In any case, most of those steps only touch the built-in 512MB NAND flash.

Could that re-allocate bad blocks in the NAND?

rajeevvp · Mar 1, 2012

fosser2 said:
Could that re-allocate bad blocks in the NAND?

What kind of bad block? Factory-marked bad blocks on raw NAND devices are not reallocated. The filesystems (YAFFS2, JFFS, UBIFS) for these raw NAND/NOR MTD devices are designed to skip marked bad blocks. CWM and the utilities that come with it (dump_image, erase_image, flash_image) do this too.

BTW, fosser2, can you use the gtablet.cfg in this post instead of roebeet's version for people enlarging their system partition and installing the 1.2 bootloader.

fosser2 · Mar 1, 2012

rajeevvp said:
What kind of bad block? Factory-marked bad blocks on raw NAND devices are not reallocated. The filesystems (YAFFS2, JFFS, UBIFS) for these raw NAND/NOR MTD devices are designed to skip marked bad blocks. CWM and the utilities that come with it (dump_image, erase_image, flash_image) do this too.

BTW, fosser2, can you use the gtablet.cfg in this post instead of roebeet's version for people enlarging their system partition and installing the 1.2 bootloader.

For example these are the bad blocks I'm talking about:

Code:

<6>[    3.334646] yaffs: dev is 32505859 name is "mtdblock3" rw  
<6>[    3.334798] yaffs: passed flags ""  
<7>[    3.334890] yaffs: Attempting MTD mount of 31.3,"mtdblock3"  
<7>[    3.441293] yaffs: block 1393 is bad  
<7>[    7.661086] yaffs: yaffs_read_super: is_checkpointed 0  
<6>[    7.661433] yaffs: dev is 32505860 name is "mtdblock4" rw  
<6>[    7.661520] yaffs: passed flags ""  
<7>[    7.661613] yaffs: Attempting MTD mount of 31.4,"mtdblock4"  
<7>[    7.733488] yaffs: block 1255 is bad  
<7>[    7.733613] yaffs: block 1256 is bad  
<7>[    8.188697] yaffs: yaffs_read_super: is_checkpointed 0

full dmesg here http://pastebin.com/tyPm3DpH

As for expanding the system partition: As far as I know, we aren't doing that. We are using "stock" values.

the3dman · Mar 2, 2012

We have updated the ROM and GApps, be sure to check them out, the links are in the OP. The change log for the updates are listed here: Team DRH Changes

fosser2 · Mar 2, 2012

OP Updated again. New rom, minor changes.

plastikman187 · Mar 2, 2012

Dammit now I have to check here and SD lol

karl0ss · Mar 2, 2012

i know your rom's not designed for Hannspad, but I have been flashing your roms, and they work fine, with our Hannspad kernel, though, with this latest version 2b, the wifi won't switch on, is this a known issue with all tablets on this rom? or is this somthing specific that has been introduced in this latest version, only effecting the Hannspad?

great work guys, keep it up.

serialplague · Mar 2, 2012

I don't know much but I read lots

but I do believe they moved to bcmdhd 14 days ago which may not be supported in your kernel

the3dman · Mar 2, 2012

serialplague said:
I don't know much but I read lots
but I do believe they moved to bcmdhd 14 days ago which may not be supported in your kernel

This is correct, and is the reason why it would not work.

Posted from my G-Tablet running Team DRH ICS

rajeevvp · Mar 2, 2012

fosser2 said:
For example these are the bad blocks I'm talking about:

That looks to me like YAFFS2 doing its job.

As for expanding the system partition: As far as I know, we aren't doing that. We are using "stock" values.

Then the 2A ROM install with full Gapps v6c will overflow the system partition--one with or without bad blocks. I see from the changelogs that you've moved some of the apps from /system/app to /data/app in 2B, so now a 200MB stock system partition should suffice for the ROM proper.

There is another bad bug in both 2A and 2B, though. You're overriding the bootloader-supplied kernel command line with one in the boot.img. This is a very bad idea--see point 2 of this post where its caused problems before.

From your dmesg.txt (from a 2A ROM kernel?) on pastebin:

Code:

Kernel command line: mem=512M@0M video=tegrafb console=ttyUSB0,115200n8 androidboot.console=ttyUSB0 tegraboot=nand mtdparts=tegra_nand:16384K@[B]7424K(misc)[/B],16384K@62208K(recovery),16384K@79104K(boot),204800K@96000K(system),222464K@301312K(cache),4096K@[B]24320K(bootbmp)[/B],32768K@28928K(logodata)

The NAND partition assignment is pretty peculiar. On first glance it looks like the partition layout on my gTab which has a switched "misc" and "bootbmp" partition. However, most of the gTabs shipped by VS have their "bootbmp" first and "misc" next.

The boot.img in 2B is worse:

Code:

mem=512M@0M video=tegrafb console=ttyUSB0,115200n8 androidboot.console=ttyUSB0 tegraboot=nand mtdparts=tegra_nand:16384K@[B]7424K(misc)[/B],16384K@62208K(recovery),16384K@79104K(boot),[B]256000K@96000K(system)[/B],[B]171264K@352512K(cache)[/B],4096K@[B]24320K(bootbmp)[/B],32768K@28928K(logodata)

In this both the partitions and the sizes are being overridden. It is, in fact, a very peculiar layout--a enlarged system partition along with the switched "misc" and "bootbmp". Somebody with the standard stock partition layout and sizes will eventually have problems when things get overwritten--their tablet might not even boot.

Seriously, Andrew, don't override the bootloader-supplied command line in this fashion.

fosser2 · Mar 2, 2012

rajeevvp,

You are right, we are over-riding the bootloader w/ our own command line. Without the change to the command line our system ram goes to 295M instead of 365M. That's a big change. We're working on fixing this issue right now and it will most likely be fixed in the next release.

jaybob413 · Mar 2, 2012

As I am certain you must be aware, this effort is still a fairly early work in progress, but you may not know that there is additional effort underway to move to a more comprehensive set of changes regarding partitioning.

In the near term the intent would be to provide an updated nvflash configuration that would modify the partition table to expand system at the expense of cache. A similar approach (firerats) has been used for quite some time on other devices that are resource constrained like the G-Tab. This would entail a one-time nvflash that we are not quite ready to provide at this point.

The principle reason for this is that 200M is quite small to support newer software versions like ICS without requiring significant effort from a build/packaging perspective, that takes time and effort from the primary goal which is to deliver improved functionality to the end users.

Anyone who has performed an nvflash using either bekit or roebeet gtablet.cfg (likely a large portion of the community), already has a "non-standard" partition table (where system may already be closer to 250M than 200M), so while things like the misc/bootbmp swap may be different from the vendor standard, they are certainly not unique or even uncommon in the gtablet community that is not using tap'n'tap.

There is also really not much concern about whether the cache partition is large enough to hold an ota update from viewsonic, as that would certainly deliver significantly reduced functionality, and is precisely what most end-users are trying to get away from.

Of course, anyone that is not happy with the choices the developers make, can choose not to use it, and are certainly welcome to build their own rom and use partition sizes that they find more aesthetically pleasing.

Common courtesy might suggest that your ideas on how another developer's work should be modified would best be communicated via PM. This would provide the opportunity to understand the rationale behind certain decisions, rather than declaring them a "very bad idea" out of hand, or instructing them on how to proceed.

rajeevvp said:
That looks to me like YAFFS2 doing its job.

Then the 2A ROM install with full Gapps v6c will overflow the system partition--one with or without bad blocks. I see from the changelogs that you've moved some of the apps from /system/app to /data/app in 2B, so now a 200MB stock system partition should suffice for the ROM proper.

There is another bad bug in both 2A and 2B, though. You're overriding the bootloader-supplied kernel command line with one in the boot.img. This is a very bad idea--see point 2 of this post where its caused problems before.

From your dmesg.txt (from a 2A ROM kernel?) on pastebin:

Code:

Kernel command line: mem=512M@0M video=tegrafb console=ttyUSB0,115200n8 androidboot.console=ttyUSB0 tegraboot=nand mtdparts=tegra_nand:16384K@[B]7424K(misc)[/B],16384K@62208K(recovery),16384K@79104K(boot),204800K@96000K(system),222464K@301312K(cache),4096K@[B]24320K(bootbmp)[/B],32768K@28928K(logodata)

The NAND partition assignment is pretty peculiar. On first glance it looks like the partition layout on my gTab which has a switched "misc" and "bootbmp" partition. However, most of the gTabs shipped by VS have their "bootbmp" first and "misc" next.

The boot.img in 2B is worse:

Code:

mem=512M@0M video=tegrafb console=ttyUSB0,115200n8 androidboot.console=ttyUSB0 tegraboot=nand mtdparts=tegra_nand:16384K@[B]7424K(misc)[/B],16384K@62208K(recovery),16384K@79104K(boot),[B]256000K@96000K(system)[/B],[B]171264K@352512K(cache)[/B],4096K@[B]24320K(bootbmp)[/B],32768K@28928K(logodata)

In this both the partitions and the sizes are being overridden. It is, in fact, a very peculiar layout--a enlarged system partition along with the switched "misc" and "bootbmp". Somebody with the standard stock partition layout and sizes will eventually have problems when things get overwritten--their tablet might not even boot.

Seriously, Andrew, don't override the bootloader-supplied command line in this fashion.

Abu-7abash · Mar 2, 2012

Wonderful, finally this has arrived here xD

Does the latest release fix TiBa bug in restoring?

Sent from my HD2 using Tapatalk

fosser2 · Mar 2, 2012

Abu-7abash said:
Wonderful, finally this has arrived here xD

Does the latest release fix TiBa bug in restoring?

Sent from my HD2 using Tapatalk

People have had success in restoring w/ TiBa. I guess you're gonna have to try it and let us know your experiences.

Abu-7abash · Mar 2, 2012

fosser2 said:
People have had success in restoring w/ TiBa. I guess you're gonna have to try it and let us know your experiences.

Glad to hear, been downloading it when I first saw it ut thought I ask and test so I would try even harder if it didn't work for me while being fixed.

Sent from my HD2 using Tapatalk

[ROM - 1.2] BETA ICS 4.0.X - Team DRH (Update 07/02/12)

Senior Member

Attachments

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Retired Recognized Developer

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts