Just got a flash update on N1, anyway to update G-tab? - G Tablet General

Have got the version of flash that's in the CWM sticky, but noticed my N1 today got an upgrade, and am wondering if there is a way to pull that over to my G-tab? Or do I just need to be a little patent and someone will post an update in a day or two?

EwanG said:
Have got the version of flash that's in the CWM sticky, but noticed my N1 today got an upgrade, and am wondering if there is a way to pull that over to my G-tab? Or do I just need to be a little patent and someone will post an update in a day or two?
Click to expand...
Click to collapse
You can try but the flash seems to be device specific in some cases so it may just bork your flash. Make a backup so you can restore it if you try

EwanG said:
Have got the version of flash that's in the CWM sticky, but noticed my N1 today got an upgrade, and am wondering if there is a way to pull that over to my G-tab? Or do I just need to be a little patent and someone will post an update in a day or two?
Click to expand...
Click to collapse
Since you mention CWM I will assume you have root.
Get a free Dropbox account and install on your N1 and gTab. Then it's as easy as copying the Flash apk into the Dropbox folder on your phone and then downloading it from your Dropbox folder on your gTab.
Doesn't get much easier.

I saw the flash update on my N1 this morning. I read the release notes for 10.1.106.16. It states:
Flash Player (10.1.106.16) impacts new users only and is not a mandatory update for existing users. It SHOULD NOT be installed on devices/tablets with the NVIDIA Terga 2 Super Chip including the LG Optimus 2X, Dell Streak 7, and Motorola ATRIX. The pre-installed version of Flash Player is optimized for Tegra 2 (this is my addition... if only there was a pre-installed version of the Flash Player installed on the gtab...) Future updates will include these optimizations. If you are unsure as to whether your device includes the NVIDIA Tegra 2, please consult your device owner's manual.
Maybe the versions prior have the same stipulation I don't know (this is the first time I saw this), but it's probably best to stick with what works for now. Probably won't be a lot of change until the release with the official Tegra 2 support is made available.

sjmoreno said:
Since you mention CWM I will assume you have root.
Get a free Dropbox account and install on your N1 and gTab. Then it's as easy as copying the Flash apk into the Dropbox folder on your phone and then downloading it from your Dropbox folder on your gTab.
Doesn't get much easier.
Click to expand...
Click to collapse
The update says in it's notes that it isn't for tegra devices... kinda useless to us.

Related

[ROM-DEV] Android 2.0.1-r5v0.6 (Dead)

Android 2.0.1-r5v0.6
Dead:
==============
After spending some time and looking over this rom and ways to make it work with out any legal issues. The most viable option was to build something like what cynanogen has built. His process takes the proprietary bits (all google apps including sync) and copies them off onto the SD card before doing a update. After the update it copies them back to the newly installed rom. This method basically does a automated backup/restore of your licensed applications. I can't do this for several reasons including that we are supposed to be coming from a 1.5 OS to a 2.0.1, which isn't compatible with the older application set.
Temporarily Offline:
==============
I am sorry to have to do this but we are now having more then just a small handful goofing with this ROM and I need to take this offline while I inspect each of the parts and make sure all licensing is in order since its a bit more then the google Opensource framework. I know that several other ROM creators have not paid much attention to it as I am going to now but I really don't want to upset any IP holders like what happened to Cynanogen a couple months back.
I will put it back up but I want to make sure that I am totally covered and don't have any issues.
version 0.6: download (offline)
==============
-fixed wifi thanks to http://forum.xda-developers.com/showthread.php?t=593620
-Now starts up with Android stock keyboard. (No longer needs HTC_IME.apk for second keyboard)
A few have asked for this ROM so I thought I would put it up here for anyone that wants to contribute to or take from it.
This ROM is only compatible with the Sprint CDMA HTC Hero. It is not finished and still requires some work but its good enough for my day to day use and I am sure others may find the same potential.
This ROM is vanilla android and what it takes to actually get it running on a CDMA phone. It is built off of this GSM variant. I am going to try and work to remove the google bits so that you can use Cynanogens method of extracting your own and then doing a follow up update to install them. My efforts for this is not to build a better rom but to build a cleaner base that has limited to no proprietary IP.
Credits to all on this forum how have helped or contributed in any way to building the roms that are here. I would point out names but there are to many to name. I am positive that anyone that pays attention to this forum will know who you are. I used many parts of these ROM's and many others on XDA to build this one.
This is my first ROM and was primarily made for myself to help me learn how to create a custom ROM.
Here is the link to my blog where I originally posted about this and a video of it booting.
Here is the Youtube video of it booting: http://www.youtube.com/watch?v=tRTh-rXKe-E
*Warning*: Don't attempt to flash this ROM onto anything else unless you know what you are doing! I am not responsible for any device malfunctions or "Bricks".
Notes on Installing:
- Run a Nandroid backup before you do anything.
- Make sure you do a full wipe first. (Sorry )
- Run the update zip found * Version 0.6 *(offline) from the recovery console.
To get the HTC keyboard installed: (Now Optional as of Version 0.6)
- Follow the instructions here.
Things that don't work:
- Gallery some times has issues.
- Camera
- Wired or Wireless Tethering (Now Testing)
- Orientation
- Trackball light
- Trackball click (Rolling and moving are fine)
- (Let me know if something else needs to go here.)
Possible issues that are not repeatable:
- speaker not working on out bound calls? I made 30 test calls to my home phone and was not able to replicate this issue. Needs to be verified (see here)
Awesome! Thanks! disregard my PM lol.. Great timing.
VoXHTC said:
Awesome! Thanks! disregard my PM lol.. Great timing.
Click to expand...
Click to collapse
LOL I was just getting to replying to you!
im trying it now nice work
Let me know if any of you have issues flashing. I still have it all right here in front of me if I need to make a change.
FYI: The first boot takes for ever as it registers all the APKS.
i just get the HTC_IME fource close i installed the one from the site like you said and installed it and i get this
thorracing1 said:
i just get the HTC_IME fource close i installed the one from the site like you said and installed it and i get this
Click to expand...
Click to collapse
So you installed both the HTC_IME.apk and the Clicker.apk? Did you do a adb push or a adb install?
Try and go into settings --> Language & Keyboard --> Touch Input --> Text Input?
I think its a force of habit with out really thinking to go there and calibrate but just going there may help.
Try that and let me know.
i just flashed it and pushed the keyboard and calibration app through adb and all is well. its working awesome. Thanks!!!
2.0t03speed said:
i just flashed it and pushed the keyboard and calibration app through adb and all is well. its working awesome. Thanks!!!
Click to expand...
Click to collapse
Awesome, keep the feed back coming as you have it!
please take note orientation doesnt work. please put in first post.
otherwise, great work!
should i do adb install or adb push?
blankd3ckskat3r said:
please take note orientation doesnt work. please put in first post.
otherwise, great work!
Click to expand...
Click to collapse
Got it listed now, that one bugs me... Must have been to worried about building this to remember it.
BTW thanks for the feed back!
thorracing1 said:
should i do adb install or adb push?
Click to expand...
Click to collapse
I would do an install or transfer them to your SD card and grab a app like Astro from the market to install them. Don't worry we will get you worked out.
dchadwick said:
Got it listed now, that one bugs me... Must have been to worried about building this to remember it.
Click to expand...
Click to collapse
lol well its a common problem, cant wait for a fix. really like what you did with this build
dchadwick said:
I would do an install or transfer them to your SD card and grab a app like Astro from the market to install them. Don't worry we will get you worked out.
Click to expand...
Click to collapse
Not able to get a working Keyboard Now I'm stuck in a boot loop. Tried installing through droid explorer.. no go.. tried installing from astro ..no go.. now it loads lockscreen.. dead... reboot..rinse and repeat
removed SDcard.. boots now trying to push.. but where do I push the apk files to?
blankd3ckskat3r said:
lol well its a common problem, cant wait for a fix. really like what you did with this build
Click to expand...
Click to collapse
Thanks, but I really can't take to much credit. Its a "Pick and Pull" from several ROMs. This one actually came from our GSM Brothers and then I used the CDMA tricks in this form to make it work.
I keep watching and playing with the Google Nexus Dumps. I would really like to get one of them up and running.
Based on your posting and replies I assume you are re-using the 2.6.27 kernel like the other roms?
VoXHTC said:
Not able to get a working Keyboard Now I'm stuck in a boot loop. Tried installing through droid explorer.. no go.. tried installing from astro ..no go.. now it loads lockscreen.. dead... reboot..rinse and repeat
Click to expand...
Click to collapse
Wow thats allot in a little space.
What I gather is that it originally booted, then after trying to install via droid explorer and then astro it now just dies after the lockscreen.
I am not sure where to start. I would just say to do a full wipe, then a clean install. Then if you have the sdk try the ADB install method as Cynanogen's post talks about.
I am working on trying to get the stock Android keyboard to work. If we can figure out that then we don't have to mess with the HTC one.
ok i got it i just adb pushed them to system/app works great
obelisk79 said:
Based on your posting and replies I assume you are re-using the 2.6.27 kernel like the other roms?
Click to expand...
Click to collapse
Yeah, actually some of your work if I remember correctly, thats why its got the same issues. My first goal when I built this for my self was to get past the blasted google bits sync loop. The more I worked into it the more I moved on to the 2.0.1 build with some of your stuff in it.
Your welcome to anything I have learned, its really not my work.

Few Questions...Plz Help

Hi I'm new here and have a few questions. I downloaded some apps off the web but when they are updated I cannot update them using the market. Is there any way for me to update them or add them to the "My Downloads" list in the market? If I root my phone, but do not install a custom rom will I still get ota updates, be able to install market apps, and so on?
Details:
Phone: Nexus One (T-Mobile Version)
Android Version: 2.2 FroYo FRF50 (love it)
If you guys need baseband and kernel information let me know. Also, what it different in stock froyo vs cyanmod vs any other rom? Sorry if this is in the wrong place to post this and the length.
Hi there, as of right now all that I can point you towards for you apps would be an app called apktor that can be found in the market the rest you will have to figure out on your own. Or you could also just redownload these apps through the market...
From what I have read besically when you root your phone you give up any chance to be able to OTA update. BTW I have a Telus Milestone so I am not sure about the phone you have because it might be different but I think it would be a global rule of Rooting= No OTA... Although while being rooted you can install apps from the market.
About the custom roms you will have to do some reading untill the Milestone's boot gets cracked I won't have a chance to play around with any roms, I guess best advice would be read read read and read some more. And after you have done all that reading, choose a couple of roms that interest you try each one for atleast a day and find the one that you like. If there was a best rom, there wouldn't be such a wide variety of them...
~PsyCl0ne
Nope, even if your phone has root you can still update apps via the market. I know because I updated my apps via this way. 2 Rules apply though.
1) The apps that you downloaded off the web are freeware and are also on the market.
2) The apps that you downloaded off the web AREN'T warez. (I'd suspect that's what you're trying to do, but do correct me if i'm wrong)
It is highly unlikely that in following these 2 simple rules you still can't update via market.

[Q] Problem SDcard and Apps [XDAndroid FRX06]

Hello,
I have a HTC Touch Diamond 100 and I installed the "Froyo FRX06 XDandroid NEW system update" review in the post "[prj] [XDANDROID] [AOSP] [FroYo | GINGERBREAD] [31.03] System Update" and everything works fine except that it doesn't recognize SDcard applications.
There's no Error Message in the screen, is just that the system doesn't recognice anything in the SDcard. I put my apps in the folder: AndroidApps-> Other. I think it's not the common fault that I have read many people have "Waiting for SDCard error. For people who have problems with sdcard message, add this to your startupmsmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave" because for instance the phone let me save the pictures i've take with the camera phone or install and recognice any app from the market.
I 've Format the card with the HP tools after initial installation and then i had restore all the files in the internal storage.
P.S. Sorry for my possible spelling mistakes but English is not my native language
Keep in mind if you put the apk in anything other than the AndroidApps folder you will need to install them yourself. See THIS FAQ for further explanation. As far as the wating on sd card message you get when you are booting into Android, I get those all the time and have no problems with taking pictures. I would suggest that you use the full bundle from THIS post to ensure you have the latest. Unless you know what you are doing
R^7Z said:
Keep in mind if you put the apk in anything other than the AndroidApps folder you will need to install them yourself. See THIS FAQ for further explanation. As far as the wating on sd card message you get when you are booting into Android, I get those all the time and have no problems with taking pictures. I would suggest that you use the full bundle from THIS post to ensure you have the latest. Unless you know what you are doing
Click to expand...
Click to collapse
Oh what A noob mistake xD I didn't know that apps in the "Other" folder doesn't follow the "typical rules" for instaling apps (i've come from previous releases of Android, Eclair specifically, and in that version it was only place in this folder to install apps).
I'm using froyo instead of gingerbread builts because HTC touch Diamond it's quite old and i don't know if the performance would be better or slower than froyo performace but if you recomend me to use that gingerbread bundle i would use it.
Thanks R^7Z.
Honestly, Gingerbread is "better" but it is alpha release at the moment. Yes, this means that there are quite a few more "improvements" to under-go! I only recommend it if you like the idea of Android. The latest releases for FroYo aren't bad but it seems there are a few hard instability hits it has taken since FRX03 (last time I really enjoyed running a FroYo build from the XDAndroid project). Since then, I've been playing around with a few things and builds to include but not limited to this new idea of CWM (clockwork mod/Gingercherry tutorial) which is posted in the neopeek forums. So, unless you've got an idea as to how neopeek variants work, it's suggested to stick with the XDAndroid builds...
R^7Z said:
Honestly, Gingerbread is "better" but it is alpha release at the moment. Yes, this means that there are quite a few more "improvements" to under-go! I only recommend it if you like the idea of Android. The latest releases for FroYo aren't bad but it seems there are a few hard instability hits it has taken since FRX03 (last time I really enjoyed running a FroYo build from the XDAndroid project). Since then, I've been playing around with a few things and builds to include but not limited to this new idea of CWM (clockwork mod/Gingercherry tutorial) which is posted in the neopeek forums. So, unless you've got an idea as to how neopeek variants work, it's suggested to stick with the XDAndroid builds...
Click to expand...
Click to collapse
I see what you say but honestly, right now, I'm looking for stability and performace, if you know that gingerbread build GBX0A have better performance (i supose that it's less stable because it's an alpha) than FRX06 i'll choose Ginger
Thanks again R^7Z.

[ROM INFO] CM7 Nightlies Discussion

maxdamage2122 said:
Since "official" nightlys have not been compiling for the g-tablet, I have been compoiling them myself on my personal computer. I'll compile the source every so often and upload it here https://www.dropbox.com/s/w3vhon1u5a2orsk/smb_a1002/kang?v=l. The time stamp in the file name (MMDDYYYY-HHMM) is the time that the repo sync was done.
In the meantime I'm setting up an old computer that I have as a buildbot to automatically compile every night for us. I'll let you guys know when I have it up and running.
Click to expand...
Click to collapse
I thought it might be nice to get a thread going for discussion on the CM7 port for harmony for our gtablet device. There are nightly builds which are starting to incorporate some great things such as video acceleration and the new google release of 2.3.4 could be around the corner. In fact some 2.3.4 code made it into nightly#60.
I am in no way associated with CM7. If someone from CM7 or someone in some way associated with CM7 wants to run this thread or create a similar one please do so.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Rule #1 of CyanogenMod: Don't ask about release dates.
CM7 Harmony Stable Releases
http://mirror.teamdouche.net/?device=harmony&type=stable
CM7 Harmony Nightly Releases
http://mirror.teamdouche.net/?device=harmony&type=nightly
Changelog
http://cm-nightlies.appspot.com/?device=harmony
Tablet Tweaks II (original TT is already incorporated)
http://forum.xda-developers.com/showthread.php?t=1002000
For firsties...
How-To Guide:
(slightly edited from Wiki http://wiki.cyanogenmod.com/index.php?title=Viewsonic_G_Tablet:_Full_Update_Guide)
Before you do anything — Make a backup
Don't forget to back up your data. If you have synced the device with a Google account, then the contacts, calendar, Gmail & select other Google-related data will not be lost and will come back after the next sync. However, you should backup anything you want to keep that is not stored on the SD card:
Bookmarks,
Applications; use Titanium Backup or the Astro File Manager, for example,
Any application data not on the SD card.
It would also be a good idea to backup everything stored on the SD card in the rare case the SD card must be formatted to resolve any major problems.
Backup for Root Users is a free application that can assist with backing up your data.
Installing ClockworkMod Recovery
For this guide, it is not necessary to root the Viewsonic G Tablet in order to flash CyanogenMod. You can simply install ClockworkMod Recovery & continue on.
Warning: Installing ClockworkMod Recovery on the Viewsonic G Tablet will void the warranty.
Download the ClockworkMod package: Download
Unzip the ClockworkMod package & copy the recovery folder & the update.zip to the root of the internal memory (NOT in any folders & NOT to the removable SD card).
Power off the Viewsonic G Tablet and reboot holding the Volume Up button and the Power button until the device is in the stock recovery.
While in the stock recovery, use the Volume buttons to navigate to the apply update.zip & press the Home button to select it.
Once the it the update.zip is applied the Viewsonic G Tablet will have ClockworkMod Recovery. Please continue to the next section.
Flashing CyanogenMod
*******************
adampdx said:
...according to this tweet we're not supposed to flash between the stable releases and the nightlies. ....
Click to expand...
Click to collapse
*******************
jerdog said:
Echoing the above -
DO NOT USE ROM MANAGER ON THE VIEWSONIC GTABLET!!!!! IT WILL BORK YOUR DEVICE 99% OF THE TIME. MAGIC VALUE MISMATCH AND OTHER ASSORTED ERRORS.
We've been dealing with these issues for months now - don't discount because you think you know better because you've used it on XYZ phone.
IT CAUSES ISSUES ON THE GTABLET. PLEASE EDIT YOUR OP TO REFLECT THIS. THERE ARE POSTS ALL OVER HERE DETAILING THIS. PLEASE ALSO POST A LINK TO BEKIT's CWM .8 - THAT IS THE ONE THAT WAS MODIFIED TO WORK WITH THE GTABLET GIVEN THE MULTIPLE QUALITY CONTROL ISSUES ASSOCIATED WITH THE PARTITIONS AND WHAT NOT.
Click to expand...
Click to collapse
Place the CyanogenMod update.zip file on the root of the SD card.
Optional: Place the Google Apps .zip on the root of the SD card also.
Boot into the ClockworkMod Recovery.
Once the device boots into the ClockworkMod Recovery, use the side volume buttons to move around, and either the power button or the trackball to select.
Select the option to Wipe data/factory reset.
Then select the option to Wipe cache partition.
Select Install zip from sdcard.
Select Choose zip from sdcard.
Select the CyanogenMod update.zip.
Optional: Install the Google Apps by performing steps 7 - 9 again and choosing the Google Apps update.zip.
Once the installation has finished, select +++++Go Back+++++ to get back to the main menu, and select the Reboot system now option. The Viewsonic G Tablet should now boot into CyanogenMod.
Having issues with finding your Internal Storage?
Check your fstab. CM has a different paradigm. See below from maxdamage2122
maxdamage2122 said:
This is a flashable zip file that I have created to backup the vold.fstab file and replace it with one that mounts the internal storage as /sdcard.
http://goo.gl/DS8u9
Click to expand...
Click to collapse
Edit: Thanks and props to the CM team and all involved. No thanks to me, I am just a copy/past whore.
Edit: Removed RomManager Method (thanks badfrog and jerdog)
Edit: Added reference to fstab mod. Thanks maxdamages 2122
Do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
Great job Oozura. Make sure Mad-Murdoch links this thread in his post in the nook forum. I had volunteered to do the same but he didn't get back to me. I'm a long time CM nightlies user on Droid, and now on GTab as well. I'll post as much as I can here.
And that bad frog is right. Use bekit's 0.8 GTab recovery and forget about Rom Manager. You'll just end up having to nvflash...
Thanks!
MC
thebadfrog said:
Do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
Click to expand...
Click to collapse
Are you sure about this? If so I dont mind editing that part of the CM instructions.
Echoing the above -
DO NOT USE ROM MANAGER ON THE VIEWSONIC GTABLET!!!!! IT WILL BORK YOUR DEVICE 99% OF THE TIME. MAGIC VALUE MISMATCH AND OTHER ASSORTED ERRORS.
We've been dealing with these issues for months now - don't discount because you think you know better because you've used it on XYZ phone.
IT CAUSES ISSUES ON THE GTABLET. PLEASE EDIT YOUR OP TO REFLECT THIS. THERE ARE POSTS ALL OVER HERE DETAILING THIS. PLEASE ALSO POST A LINK TO BEKIT's CWM .8 - THAT IS THE ONE THAT WAS MODIFIED TO WORK WITH THE GTABLET GIVEN THE MULTIPLE QUALITY CONTROL ISSUES ASSOCIATED WITH THE PARTITIONS AND WHAT NOT.
Search for the endless threads on hard bricked and soft bricked tabs from using rom manager on the gtab. And before all you fanbois jump in and tell me you had no problems understand this....there are at least 2 different partitioning setups on the Gtab from the factory. Sometimes you can't even boot after flashing Gingerbread roms without nvflash.
MicroChip said:
Great job Oozura. Make sure Mad-Murdoch links this thread in his post in the nook forum. I had volunteered to do the same but he didn't get back to me. I'm a long time CM nightlies user on Droid, and now on GTab as well. I'll post as much as I can here.
Thanks!
MC
Click to expand...
Click to collapse
Been a long time droid, dInc user. I had sent you a PM about half way through the OP but decided what the heck. I hope this helps keeps discussion in one place for our gtab and CM7 (soon to be 7.1)
Oozura said:
Are you sure about this? If so I dont mind editing that part of the CM instructions.
Click to expand...
Click to collapse
Yes, I'm sure he is sure about this. Do NOT use Rom Manager to install any of the roms or to update CWM. Only use bekit 0.8 recovery.
I don't even install Rom Manager on my Gtab.
thebadfrog said:
Search for the endless threads on hard bricked and soft bricked tabs from using rom manager on the gtab. And before all you fanbois jump in and tell me you had no problems understand this....there are at least 2 different partitioning setups on the Gtab from the factory. Sometimes you can't even boot after flashing Gingerbread roms without nvflash.
Click to expand...
Click to collapse
Sounds good to me. I will take it out. As long as the other method works then no need to make anyone cry over a bricked tab.
+10000 I learned this the hard way on day one.
Sent from my CM7 GTablet
Oozura said:
Sounds good to me. I will take it out. As long as the other method works then no need to make anyone cry over a bricked tab.
Click to expand...
Click to collapse
Please - don't just take it out - add a warning about it. And provide the link to the known working CWM (Bekit .8).
RomManager method removed
OP Edited. Thanks.
jerdog said:
Please - don't just take it out - add a warning about it. And provide the link to the known working CWM (Bekit .8).
Click to expand...
Click to collapse
I quoted your post. Link was already there to correct version in the clockwork mod package. thanks.
Thank you. There is something flakey about these devices and they don'y like Rom Manager
So who is using the latest nightly? I'm running 60 and seems stable. I occasionally get a stall on browser apps after a long sleep. But can't find any other issues.
Sent from my ADR6300 using Tapatalk
Oozura said:
So who is using the latest nightly? I'm running 60 and seems stable. I occasionally get a stall on browser apps after a long sleep. But can't find any other issues.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
I am. No issues to report, camera is still grainy. Video playback is still great.
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
Hardware Decoding?
So I installed AOSP the other day (the one in the Dev forum) because it was claiming hardware acceleration. It loaded up and was super laggy, but also didn't play the same video files that Vegan 5 played. I loaded up CM7 today and found the same thing. It's not nearly as laggy as the AOSP build, but still does not play video. I get volume, but no sound. Am I mistaken is thinking that we in fact have hardware acceleration now?
adampdx said:
So I installed AOSP the other day (the one in the Dev forum) because it was claiming hardware acceleration. It loaded up and was super laggy, but also didn't play the same video files that Vegan 5 played. I loaded up CM7 today and found the same thing. It's not nearly as laggy as the AOSP build, but still does not play video. I get volume, but no sound. Am I mistaken is thinking that we in fact have hardware acceleration now?
Click to expand...
Click to collapse
Progress is being made but we aren't there yet. Did you try mobo player? Engage software decoding and you'll be good to go.
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
I've been using RockPlayer and havent had any issues. Most notably for me though was YouTube HD videos now play with no lag.
I think Irs421 is right. Its progress but not complete hardware acceleration until Nvidia releases GB drivers I would guess.
I figured as much. Progress, even slow progress, is good. I'm liking CM7 so far any how.

[ROM/WIP][ICS/US 9.2.1.11] 4.0.3 Minimal

This is my first attempt at a custom ROM for any Android device, so bear with me. I did not build this from AOSP source, or any other source code. It's entirely from ASUS. This ROM is intended for those who don't like the stock ASUS apps, similar to KRAKD/FROZN, except I've not optimised any of the APKs or anything else. Hopefully this can be a useful base ROM for another dev, taking the tedious part out of the equation. It's completely based on US, not WW or TW.
It's large(300Mbyte) because I used a binary blob. I'm working on shrinking it down with a proper update sript.
Apps I removed:
Amazon Kindle
MyCloud
ASUS File Manager
MyLibrary
MyNet
Netflix
News & Weather(and their widgets)
PolarisOffice
PressReader
MyZine
Tegra Game Zone
Web Storage
Zinio
PC Sync
ASUS Software keyboard(the touchscreen one, not the dock keyboard)
DMClient(related to ASUS updates, from what I understand)
ASUS software update(so no annoying OTA notifications that you can't use anyway)
SuperNote
-any others not included that I forgot to list
How to install:
1. A complete data wipe(at least dalvik & cache, data is optional) is strongly recommended if you're coming from Honeycomb.
2. Flash the zip from CWM.
3. Enjoy your new ICS.
You should be able to flash from any ROM if you clear at least dalvik and cache.
Features:
-Pre-rooted for your convenience, with busybox, su, and SuperUser.
-ALL bloatware removed, hopefully improving performance
-Closer to an AOSP experience due to all bloat being removed.
What this ROM does NOT have:
-Custom kernel
-Stock ICS buttons(it has the crummy ASUS back, home, recent app buttons)
-Zipaligned APKs
-Deodexed APKs
-A name, since it doesn't really need one right now.
How I created it(roughly, not a step by step):
1. I reverted from a custom ROM(krakd) to the latest US .21 HC release, with stock recovery
2. I Rooted with nachoroot and then used OTA keeper to unroot
3. I updated to US ICS via OTA.
4. I reapplied root with OTA keeper
5. I used ES file manager and terminal to remove the apps
6. I used ES file manager to add SuperUser to /system
7. Installed busybox at some point during these steps, I forget when.
8. Used dd to image the /system partition(mmcblkp0) to a file on my MicroSD
9. Replaced the LNX and APP blobs of a Honeycomb update(.21) with the ICS ones
10. Flashed it, and it worked.
So it's not a "proper" update, broken down into directories and such, but it does work.
Links:
ROM: http://dev-downloads.com/asus-tf101-romwipicsus-9-2-1-11-4-0-3-minimal/
Trebuchet CM9 launcher: http://dl.dropbox.com/u/31118/signed_TrebuchetCWM.zip (thanks to whitekidney/wk on #asus-transformer irc)
Here is the MD5 for the ROM zip: 0B9BC1C83C271DF26501CF533A046CB1
And the SHA1: B7BBC2C3AB33844E46CC8D8D2900E2AF1C68EFB5
Credits:
Whitekidney for the Trebuchet launcher upload
Have you tested this at all?>
Yes, why? It worked fine on my TF101.
I think everyone is always a bit skeptical of a ROM that someone says openly is their first attempt and they have less than 10 posts on here..you are after all talking about potentially rendering a $500 device useless..people are usually right to exercise caution..when the developer cannot post in the dev section because his post count is too low!
But hey, that is how Paul Burton started here, though it was not his first ROM I am quite positive..
daxtsu said:
Yes, why? It worked fine on my TF101.
Click to expand...
Click to collapse
After flashing, not booting anymore, and as I I know what I am doing...unless my power cord just broke.
thanks I guess, but I can remove my own apps From a rom ......
luna_c666 said:
I think everyone is always a bit skeptical of a ROM that someone says openly is their first attempt and they have less than 10 posts on here..you are after all talking about potentially rendering a $500 device useless..people are usually right to exercise caution..when the developer cannot post in the dev section because his post count is too low!
But hey, that is how Paul Burton started here, though it was not his first ROM I am quite positive..
Click to expand...
Click to collapse
Fair enough, I do admit I'm new to Android development, but I wouldn't release something without testing it on my own device first.
DTgreat said:
After flashing, not booting anymore, and as I I know what I am doing...unless my power cord just broke.
Click to expand...
Click to collapse
Did you do a full wipe? I installed it at least 5 times today during testing removing apps with no major issues..
BTW: Here is the MD5 for the zip: 0B9BC1C83C271DF26501CF533A046CB1
And the SHA1: B7BBC2C3AB33844E46CC8D8D2900E2AF1C68EFB5
Yes, although like I said. I know what I am doing. My power cord in fact, may have just broke. (Although I doubt it.)
IF YOU cant post links yet it's for a reason
cool, where did you get the source code from asus?
timbit123 said:
cool, where did you get the source code from asus?
Click to expand...
Click to collapse
It sounds like he got the ROM and removed the third party apps, not that he got the source code to build it to AOSP.
its more a list of apps that are safe to remove with TB...... IMO anyway. Happy to wait and see if it leads to something a bit more though.
Lets make sure that no one will ever want to dev for us anymore by slapping the new guy around who took the time to try something himself. I recall Paul didnt have enough posts to start a thread in dev but he seems to know what hes doing. Why not just ban anyone whos new from ever posting any kind of dev work ever. Because what we need are more people making fun of and trashing someones work instead of people actually willing to take their time and try to make YOUR device nicer. Any wonder if this is why devs are leaving xda every day?
BTW..Just flashed this and it booted just fine. I did a system wipe first.
Maybe you should be the guy to add onskreen framework to a rom....hint
DTgreat said:
Yes, although like I said. I know what I am doing. My power cord in fact, may have just broke. (Although I doubt it.)
Click to expand...
Click to collapse
It's possible. I've had a few reports of it working so far.
KingDavid63 said:
IF YOU cant post links yet it's for a reason
Click to expand...
Click to collapse
I know. It was because my post count was too low.
timbit123 said:
cool, where did you get the source code from asus?
Click to expand...
Click to collapse
I didn't, sadly. I kludged it together somewhat by dding the fully updated ICS /system partition(adding busybox, su, Superuser beforehand) and making it into a blob that's flashable.
robojerk said:
It sounds like he got the ROM and removed the third party apps, not that he got the source code to build it to AOSP.
Click to expand...
Click to collapse
Correct.
Thanks for the feedback guys. If you want anything added, I'll try to accomodate with flashable zips since they're smaller to upload. My upload is horrible, so I can only upload a large ROM every once in a while(it takes over an hour!). I'm not discouraged, I know how it is to be the new guy. I know this rom's probably nothing special, but I just wanted to share what I'm enjoying with others.
daxtsu said:
Yes, why? It worked fine on my TF101.
Click to expand...
Click to collapse
Hey man at least you are the first to have out a custom rom, can't wait to test it out later
Sent from eee pad Transformer running ICS
Lantek23 said:
Hey man at least you are the first to have out a custom rom, can't wait to test it out later
Sent from eee pad Transformer running ICS
Click to expand...
Click to collapse
Haha, it's not that custom, more of a repack with a bunch of removed apps, but I'll look into making it deodexed and stuff. I'm still learning how to do that.
Popping into a best buy and trying a different power cord when my friend gets here. Not trying to naysay. Just trying to troubleshoot.
DTgreat said:
Popping into a best buy and trying a different power cord when my friend gets here. Not trying to naysay. Just trying to troubleshoot.
Click to expand...
Click to collapse
Oh, I know. It's cool.
Hope you get it sorted out soon.
I'll try it out later (I got too many projects going on), but I appreciate your contribution.
As someone who has been around these forums and been messing around with ROMs for a while now (but has never posted before), I applaud the effort. THANKS.

Categories

Resources