Database Develop

[Q] Is their any advantage to staying at 1.0?

I bought a nook color yesterday so I could get in on the rooting and roming fun as well. It came with 1.0, which I've already rooted and am now running HC from an SD card. A bit slow, so I'm planning on trying to install it internally. 2 Questions:
1. Is their any reason I should stay at 1.0? Or should I upgrade to 1.01 or 1.1? Will I be able to go back to 1.0 if I want using the 8 reboot method?
2. If I install HC to the internal memory, will I be able to restore to stock? I'm not sure I'm going to keep this device yet so I don't want to do something that will make it impossible to return to stock.
Thanks

1: No, there is no benefit to staying at 1.0.0. If you want to stick with stock eclair then upgrade to 1.1.0, the update fixed some WiFi issues. To revert back to an older "save" install clockwork mod via rom manager and make a backup. That backup can be reflashed whenever from whatever.
2:I don't know what you're confusing GB for but so far only Eclair/Froyo/HoneyComb currently run on the nook color. Yes you can revert back to any older CWM backup from any install on your eMMC. There are stock flashable images in the dev forum, so don't worry about not being able to go back to stock.
Good luck. Have fun.

woot1524 said:
1: No, there is no benefit to staying at 1.0.0. If you want to stick with stock eclair then upgrade to 1.1.0, the update fixed some WiFi issues. To revert back to an older "save" install clockwork mod via rom manager and make a backup. That backup can be reflashed whenever from whatever.
2:I don't know what you're confusing GB for but so far only Eclair/Froyo/HoneyComb currently run on the nook color. Yes you can revert back to any older CWM backup from any install on your eMMC. There are stock flashable images in the dev forum, so don't worry about not being able to go back to stock.
Good luck. Have fun.
Click to expand...
Click to collapse
sorry, typo, i meant HC not GB. who can keep them straight these days? thanks for your answers. i've read reports of people having various problems with 1.1.0, it seems the consensus is 1.01 is the version to be on.

OneStepAhead said:
sorry, typo, i meant HC not GB. who can keep them straight these days? thanks for your answers. i've read reports of people having various problems with 1.1.0, it seems the consensus is 1.01 is the version to be on.
Click to expand...
Click to collapse
I think the problems you're talking about stem from upgrading an already rooted 1.0.0 or 1.0.1 with clockwork mod installed. If you start with a fresh(no root/CWM) 1.0.0 install then upgrade to 1.1.0 via b&n, then root it; you're in the clear.
But why bother with all of that when nookie Froyo 6.8 on eMMC is stable and performing beautifully.

OneStepAhead said:
I bought a nook color yesterday so I could get in on the rooting and roming fun as well. It came with 1.0, which I've already rooted and am now running HC from an SD card. A bit slow, so I'm planning on trying to install it internally. 2 Questions:
1. Is their any reason I should stay at 1.0? Or should I upgrade to 1.01 or 1.1? Will I be able to go back to 1.0 if I want using the 8 reboot method?
2. If I install HC to the internal memory, will I be able to restore to stock? I'm not sure I'm going to keep this device yet so I don't want to do something that will make it impossible to return to stock.
Thanks
Click to expand...
Click to collapse
1. none that I could ever see... must've fixed something to warrant two updates although I believe that both were mostly for WiFi but I never had problems with 1.0 or 1.01...
...now I'm just wondering where the new B&N updates are as IIRC they had TWO slated for February and it's getting to be kind of late in the month to push out two updates... might just as well do one big one now... hope that they're skipping Android 2.2 and going straight to 2.3 or 3.0...

woot1524 said:
I think the problems you're talking about stem from upgrading an already rooted 1.0.0 or 1.0.1 with clockwork mod installed. If you start with a fresh(no root/CWM) 1.0.0 install then upgrade to 1.1.0 via b&n, then root it; you're in the clear.
But why bother with all of that when nookie Froyo 6.8 on eMMC is stable and performing beautifully.
Click to expand...
Click to collapse
Well the only reason I bought a Nook Color was to play with Honeycomb, dont have much interest in running Froyo, I can do that on my EVO already

One reason to stay with one of the stock ROMs is if you want to use the B&N reader and B&N kids functionality, which are not part of the froyo or HC ROMs. I personally use it a lot and hope they'll get ported over.

eyecrispy said:
One reason to stay with one of the stock ROMs is if you want to use the B&N reader and B&N kids functionality, which are not part of the froyo or HC ROMs. I personally use it a lot and hope they'll get ported over.
Click to expand...
Click to collapse
Im sure thats important to many people, although I strictly bought this to play with Honeycomb. Now that I've got it running, I'm wondering what I'll actually use this device for? I can already do all this stuff on my EVO and the screen size isn't that much bigger. It sure had been fun messing with it though! Why B&N didnt enable some of this functionality out of the box I'll never understand!

[Q] Honeystreak Help![Clockwork Recovery]

got honeystreak rc 2.1 on my dell streak 7 and i have no clue how to get clockwork recovery on it with honeystreak, so when i get rom manager and flash clockwork it works, then i reboot into the original recovery then i choose software upadate.pkg then when i click it nothing happens it just has the dell logo then it just powers up like it normally would so i cant get clockwork i need help!!!

CWM and Honeystreak are not compatible.

Same thing happened to me, the root was easy with gingerbreak, had root so I could run rom manager and flashed that to the clockwork recovery and backed up. Installed honeystreak using the nvflash and didnt like the instability of it so I wanted to go back but didnt realize the way back was another nvflash the breaks the device and then you have to recover from the cwm back up. I returned it at that point.
I've learned some more about nvflash since then, it seems its the official way they install the os's to the tegra devices. But without the official install files needed for your device, it has to be rigged. Which is why the honeystreak is unstable and the flash back to stock is broken and has to be recovered from a back up.
Windows, ubuntu are such easy installs compared to android. Everythings on a disc(that you can setup on a usb stick), there arent 14 or how ever many separate files you have to download(for the nvflash). And it just starts the install, you dont need separate program to install. They really made the process needlessly complicated for installing android.
I just find it hard to believe, non developers have to RELY on the hacker community to perform fresh(or not so fresh) installs because google/the middlemen dont provide installation media. Oh wait they provide the source code... which if your not a developer is no help to the uninitiated that just want a clean install, install newer versions.
http://forum.xda-developers.com/showthread.php?p=16257823#post16257823
http://forum.xda-developers.com/showthread.php?t=1018809&highlight=nvflash

papermate said:
Same thing happened to me, the root was easy with gingerbreak, had root so I could run rom manager and flashed that to the clockwork recovery and backed up. Installed honeystreak using the nvflash and didnt like the instability of it so I wanted to go back but didnt realize the way back was another nvflash the breaks the device and then you have to recover from the cwm back up. I returned it at that point.
I've learned some more about nvflash since then, it seems its the official way they install the os's to the tegra devices. But without the official install files needed for your device, it has to be rigged. Which is why the honeystreak is unstable and the flash back to stock is broken and has to be recovered from a back up.
Windows, ubuntu are such easy installs compared to android. Everythings on a disc(that you can setup on a usb stick), there arent 14 or how ever many separate files you have to download(for the nvflash). And it just starts the install, you dont need separate program to install. They really made the process needlessly complicated for installing android.
I just find it hard to believe, non developers have to RELY on the hacker community to perform fresh(or not so fresh) installs because google/the middlemen dont provide installation media. Oh wait they provide the source code... which if your not a developer is no help to the uninitiated that just want a clean install, install newer versions.
http://forum.xda-developers.com/showthread.php?p=16257823#post16257823
http://forum.xda-developers.com/showthread.php?t=1018809&highlight=nvflash
Click to expand...
Click to collapse
so your saying its not possible to get cwm on honeystreak

azoller1 said:
so your saying its not possible to get cwm on honeystreak
Click to expand...
Click to collapse
Its possible to get cwm(the app) ON honeystreak. What doesnt work on honeystreak is the clockwork recovery boot up menu as you have noticed yourself. Dont ask me why, I dont know. And the only current "fix" for it is to nvflash to stock where the clockwork recovery boot up menu works.
I have an open question for anyone, does clockwork rom manager work properly on honeycomb and thereby make the problem isolated to honeystreak? Or does it not work properly on honeycomb at all.

Honeystreak requires NVflash to install because it completely repartitions the nand.
nandroid depends on knowing ahead of time what the partition layout is, it's not gonna work if it'd different depending on what rom is installed.
If someone made a HC compatable clockwork it wouldnt be compatable with the stock rom either

so when the official honeycomb comes out for the dell streak 7 will clockwork mod actually boot up correctly?

azoller1 said:
so when the official honeycomb comes out for the dell streak 7 will clockwork mod actually boot up correctly?
Click to expand...
Click to collapse
When clockwork rom manager is updated to work on HC it will work... thats what I understood from his post, considering the partition layout is different on HC from previous versions.
There needs to be a partition editor and usb/sd card install-able android media like with ubuntu/windows too do away with these crippled ways of doing this. This modern os cant even perform the basics of installation that desktop os's have performed for a decade?. Maybe when Ice cream source code comes out, this is exactly what someone will do. Til then this is ridiculous. They have so hamstrung the ability to control the os on your hardware. What good is open source software if they control how it gets on the hardware. This is not a methodology I would support.
I'll have to see how windows 8 is handled on arm hardware. Might be the only os you can install and update on your own without the hassle. Or I just wont buy any arm devices and stick to flip phones and laptops for mobility.

papermate said:
When clockwork rom manager is updated to work on HC it will work... thats what I understood from his post, considering the partition layout is different on HC from previous versions.
There needs to be a partition editor and usb/sd card install-able android media like with ubuntu/windows too do away with these crippled ways of doing this. This modern os cant even perform the basics of installation that desktop os's have performed for a decade?. Maybe when Ice cream source code comes out, this is exactly what someone will do. Til then this is ridiculous. They have so hamstrung the ability to control the os on your hardware. What good is open source software if they control how it gets on the hardware. This is not a methodology I would support.
I'll have to see how windows 8 is handled on arm hardware. Might be the only os you can install and update on your own without the hassle. Or I just wont buy any arm devices and stick to flip phones and laptops for mobility.
Click to expand...
Click to collapse
The only reason the HC builds all require repartitioning is because they're based off system dumps form other devices. As the majority of the source isnt available the only way to get them to work is to make the device more closely resemble the donor rom device instead of making the rom more similar to the reciving device.
If/when HC lands it's either going to use the 2.2's partition map or require a pc to install that has a streamlined version of nvflash bundled. The only thing that would happen if users were able to manually repartition devices is seeing the rom completely break and require a un-repartitioning as android is hardcoded to take a specific partition layout, as device makers have the source they can change the hardcoded values.
Being able to repartition would be more akin to being able to shuffle around the layout of your pc's bios more then being able to repartition windows. There's no generic version of android (nexus devices might be considered generic, but nexus roms wouldnt boot on any other device anyway), it requires it to be ported to a specific device to work. you COULD play around with your bios to the point that you can shuffle stuff around but unless you had a good reason to there's no point.

Being Linux based, I would like to see Android loaded as modular as opposed to monolithic, and then the device manufacturers could simply release open source modules for their hardware. Of course, maybe this would slow things down for processing; but I'd really like a simple way to just port the OS on any device. This would be a great boon for the open source community.

could it be pssible to port over clockwork from another device to this? or is the only way to flash it

The original clockwork is a port, there would need to be 3 versions total to cover every rom:
2.2
3.1
3.2
as the HC roms are based off multiple device dumps and neither are compatable with eachother

[Q] Please don't flame - CW Recovery on VZW TAB?

I can't seem to find the answer - I've purchased the VZW Tab Bootstrapper, which at this point only seems to brick my tab - after Heimdalling, I installed Oldmacnut's Rooted Gingerbread Rom - ROM Manager says that CWR 3.0 is installed - if I push flash new recovery, the only devices i can select from are Galaxy i900 - assuming that the rom was built from this device - so, what do i need to do to get clockwork properly installed? If i volume up/power up, I get stock recovery - if I use ROM Manager, it gives me the triangle with a progress bar for a second or two, then reboots - don't want to reboot with the bootstrapper program again, as i don't want to re-brick my tab - unless I'm crazy, there doesn't seem to be an easy solution - am I crazy and/or blind? There seems to be a possible kernal solution, but I have to flash it, and I can't flash it if i can't get clockwork recovery going - i think. help....

yeah, all the bootstrappers only work for Froyo.
I released a CWM + EXT4 kernel with V1 of my Gingerbread roms, only the kernel doesnt have 3G.
I also started on a new kernel for both, 3G being an issue when i ran head first into CM7 for the tabs.
I then decided to hold off on the kernels as i was building a kernel for CM7, I thought I could release a new one.
Now, last night I thought about making a thread with all forms of "recovery" from Froyo to GB for people who need to reflash a tab back to stock, and offer a bone stock version, and a rooted version. I just need to finish uploading the remaining roms to my server for hosting before i can post it all.
I thought of this as alot of people ask where they can find X rom or X kernel, which is why i started on that mirror.
No reason to flame, the issue of CWM for GB and the bootstrappers have never been addressed publicly

Is there a way to stay on rfs with your cwm kernal you posted?

oldmacnut said:
yeah, all the bootstrappers only work for Froyo.
I released a CWM + EXT4 kernel with V1 of my Gingerbread roms, only the kernel doesnt have 3G.
I also started on a new kernel for both, 3G being an issue when i ran head first into CM7 for the tabs.
I then decided to hold off on the kernels as i was building a kernel for CM7, I thought I could release a new one.
Now, last night I thought about making a thread with all forms of "recovery" from Froyo to GB for people who need to reflash a tab back to stock, and offer a bone stock version, and a rooted version. I just need to finish uploading the remaining roms to my server for hosting before i can post it all.
I thought of this as alot of people ask where they can find X rom or X kernel, which is why i started on that mirror.
No reason to flame, the issue of CWM for GB and the bootstrappers have never been addressed publicly
Click to expand...
Click to collapse
Thanks - at least I know I'm not nuts - I honestly don't know that it's necessary to mess with the kernal that's in the GB rom you compiled - it works great as is - I'm just so used to flashing stuff through Clockwork from all the android phones I've had - new to the samsung/tab world, trying to get myself up to speed -
Thanks again for getting back to me, and please, PLEASE take care of yourself and family - this android world is supposed to be fun, not just for us that take advantage of the work that devs like yourself put in, but fun for the devs too - now put your feet up, pour yourself something cold, and watch some football.
Just make sure to have all the ROM's you started finished by morning...
My name is Jack, and I'm a romaholic.

Here is the thread you need to read first..
http://forum.xda-developers.com/showthread.php?t=1099036

TheATHEiST said:
Here is the thread you need to read first..
http://forum.xda-developers.com/showthread.php?t=1099036
Click to expand...
Click to collapse
Oops - copy that - thanks for the heads up.

Thread moved to Galaxy Tab Q&A.

Oldmacmnut,
I can't seem to get Heimdall working (or USB at all, for that matter) on my Tab. I have root, and I can reboot into recovery, although it isn't CWM recovery. I tend to believe that the problem is in a corrupt ROM install of some sort, and would like to either flash a stock ROM to get back to square 1 or a rooted ROM. Problem is, I think I need to figure out a way to do that through recovery as USB doesn't seem to work at all on any computer that I have tried. If you have a CWM Recovery that works, is it flashable in the stock recovery?
Thanks,
Seth

[Q] Is Enoms 1.6 rom still the overall best for the G1?

After 3 years, I am still rocking the G1 as my MAIN everyday general use android phone. (Because honestly.. aside from a G2 HTC nothing has come out that really replaces the overall usefulness of the G1)
I still use Enoms 1.6 rom. I checked before about updating, but back then, everyone had gripes or issues, or slowdowns that didnt really make it worth updating from. Anyways, just checking on if anything is different now. For someone who uses a partitioned sd card, apps installed to SD card automatically (not just moved) and so, is there really something worth upgrading to or is enoms rom still overall the better stable rom for us G1 users? Thanks. =)

you will always get the best speed and stability out of donut roms, there are lots of good ones to chose from so take your pick there. if you want to stick with 1.6 then you still might consider the 2708+ updated radio/spl that allows for 14 more megabites of ram, you will definitely notice this! after the update just reflash your rom and a compatible kernel over it.
there nice 2.1, 2.2, and 2.3 roms out there, plenty good enough for a daily driver but there are some lags compared to any good donut rom. if you want a taste try froyobylaszlo if you like it than there are lots more new roms that compare well to that.

2708+ updated radio/spl?
Usually I have about mid 20s-30 for memory free. Which seems decent for the most part, since everything else runs off the sd card. Only reason its lower since I use that compcache stuff.
As for the info, thanks, yea, figured donut is still better least for a every day use and general purpose.

Pls don't mix up RAM and internal memory. Internal memory is comparable to the hard disk of your PC, while RAM is memory which is used for executing programms.
The 2708/0013d combo will give you more RAM (112MB instead of 97MB), so most likely you can renounce on using compcache, but you will need an adapted kernel otherwise you will get bootloops.
Sent from my Gingerbread on Dream using XDA

Ah ok. Is enoms rom able to work with this new spl? Not even sure what would be the best way to do this.. Nandroid backup, flash new spl, and nandroid restore?

always do a nandroid.
the method i would do is backup everything via titanium backup, back up any sms or my call log via sms backup +, then i would make sure i have all the requirements and then flash the updated radio and spl. after this i would flash whatever rom i choose (stick with your donut if youd like) then i would flash rom and a compatible kernel over it, reboot, restore and be happy. also i would make sure i have all the files i need ahead of time, this being amon_ra (may need it) radio, spl, orange.nbh (in case of emergency) my rom of choice, and kernel of choice (if needed)
this is the way i'd go about it, you can try any method youd like there are tons of threads about this update so i would recommend reading a few first
oh and even if it sounds complicated its well worth it

I know, G1 was the 1st I ever did heh, now I do alot of em, The others I dont stress about as they arent my main everyday device.. I am just protective of my G1 lol.. My main device.
Does anyone know of enoms works on this new spl radio.

hanvet used enoms with the new radio/spl but i have used other 1.6 roms with it so im sure this will be fine too. just make sure you flash the appropriate kernel over the rom. if you take a look at ezterry's thread on kernels or even on the 2708+ page you will find plenty to choose from

Mysticales said:
I know, G1 was the 1st I ever did heh, now I do alot of em, The others I dont stress about as they arent my main everyday device.. I am just protective of my G1 lol.. My main device.
Does anyone know of enoms works on this new spl radio.
Click to expand...
Click to collapse
Yes, it works. I've tried it just some minutes ago. Not sure if everything works, because I did only a quick check, but it's booting, you can log in browser is working, ...
The only thing you need to do is flashing a different kernel which supports the 2708 radio on top of the ROM. I flashed Terry's BiffTest Kernel but also the newer one should work.
If you like to get some more internal memory you could also use MTD-Partitions set to [67,2] which would give you a data partition size of almost 145MB
Btw.: I suppose I could not run such a ROM as my daily driver, it looks like it's already 10 years old ...

Hah found better rom called supertinhte 2.2 rom. Based on T-Mobile myTouch 3G.
Very Very fast ,comes with 82.19 free internal space.I think it is faster than froyo by lazlo with ramhack. Type it in google cant post link cause i am new here

I really like two [email protected] ROMs on my two G1s. I use them as my daily drivers.
I use SuperFroyo on one and I use SuperCDSIv4 (Donut) community edition (looks soooo much better than Mlign, etc...) on the other.
They are both great. I uninstalled virtually everything from SuperFroyo that I could. I can verify that you have no issue with deleting Talk, News and Weather for sure. Also, if you use another keyboard, you can delete the android keyboard. I did that on another installation. I delete stuff to have all apps internal.
SuperCSDIv4 is a little faster most of the time, but the niceties of Froyo are good too so I use and really like both. I recommend Lightning Launcher, then unistall ADW and LauncherPro if you go with Superfroyo. That launcher is hard to set up, but it is really light. Just go into themes and select "Zune" and try that. It is a cool theme and fast.

I think 2.2 is more fit for G1. some apps can't work on 1.6 ROM

True but the fastest 2.2 is slower then the fastest 1.6, if all you need is speed then donut is the way to go. You can push some apks onto donut roms that aren't found in the market but if you need some apps and other things froyo offers then you may need to move up
Sent from my HTC Vision using xda premium

Apps for 2.2 arent really needed on the G1 screen, cept maybe those Authenticator apps. I have a diff android if I need those higher end apps.

I am a very proud G1 user too!
But I will suggest going too the CyanogenMod 5 Mod. With the proper tweaks, it reallly runs like a charm. Super E and Super F are also good ideas. Just google them up and look how to install them!!!!

So are people still using the volume increase thing for their G1 as well? I rem using the script and so to tweak that.

To be honest this GinSense rom is very fast and stable, its 2.3.7 using a cyanogenmod base.
There is that one problem with watching movies on it (were the sound keeps going but the video resets) but that's because its a problem with the cyanogenmod base, I know because every cyanogenmod rom I had, had this problem.
I would go to a 1.6 for speed, but then I would lose out on all the apps, and this is a quite snappy rom.
Sent from my GinDream/GinMagic using XDA

So question, to flash that ram increase radio. I could do that and do a nandroid restore afterwords?

No I'm pretty sure you would need to flash your rom again from scratch and then flash a compatible kernel over that
Sent from my HTC Vision using xda premium

Well I see the kernel in this thread I should be flashing, but I am very confused. Ok, my SD card has its apps installed to it, the rom auto uses it for storage. I dont know if I should just be relying on Titanium backup for a backup and restore or nandroid.
Im "open" to the idea of upgrading the rom if its speedy. I just dont wanna lose all the apps and work I had on this rom already. Just so confusing atm. Been a LONG time since I had to flash or work with the G1. (Never need to mess with something that works flawless) My other androids I flash the **** out of and update heh. My g1 is my baby, so always was careful. I wouldnt mind that extra ram tho if it really helps.
So what do you all think is the best way to secure keeping my stuff and easily update this?
Edit: Gonna be basing my study off this. http://forum.xda-developers.com/showthread.php?t=831139
Just wondering how my apps 2 sd will be, since on Enom, I did this the old school way and not the apps2sd thing. Which makes me think Titanium backup is the best way to restore apps on to a new rom (without data or should I be able to backup with data and restore with data, so used to not restoring with data)
Edit 2: Ok is is possible to do this, based on that thread. I use nandroid to backup, then do the steps, restore using nandroid and before I boot into the phone, I flash that biff any kernel thing, THEN reboot into the phone. Would that work and not lose anything?

[Q] I think I messed up the ROM

Ok, I think being a NOOB, I have messed up. Slightly or catestrophically I'm not sure...
So, I decided to install he Overcome system. I forgot to do the bootloader patch, or rather, I couldn't work out how (and I did look fir instructions) so I just skipped it. I realised after I had wiped and formatted that it was a simple application installed from the Android desktop. The TO install went well and I started installing apps. I thought, OH I better do that patch. As soon as I did, I got a kaleidoscope of colours on reboot and also when I selected Settings.
I used odin to flash the overcome tar and that saw kaleidoscope dissappear when selecting settings, but still appears upon reboot. I thought my next step would be to do the nowipe but I cannot access the tab from my PC using Kies or Explorer although the TAB does show the USB Kies screen, and the PC does recognise it as a USB conected device, but is not accessible by WE in Mass Storage mode.
What do I need to do to fix this?

Boot loader patch only for froyo.
Overcome is GB so it wont work.
You messed up, so start from scratch.
Restock to Stock Safe v5 using odin.
Sent from my GT-P1000 using XDA

Ok, did that and all I got was the 'GALAXY TAB' and SAMSUNG logos indefinitely. Reflashed the CWM and that got me back to the CWM command list. I then reran the 'Overcome_7_Series_v4.0.0_Wipe.zip' from there and after that installed, rebooted and back to the brick screen again.
Where to now?
Perhaps I have used one of gthe wrong bin's or placed something in the incorrect 'Files [Download]' section? PDA, Bootloader etc.
I will learn but for the moment, I am somewhat confused about the terms ROM, Bootloader, Kernel, PDA, Stock, Restock etc and I have no idea what CSC is.
Is there a thread I can read that explains what each one is and what part of this OverCome Installation is replacing/upgrading/installing?
------------------------------
Well, looks like I missed a file, so it was obviously just going nowhere after boot. Once I did that, it was all good. Instructions on the Overcome site are a bit hard to follow. Needs to be reformatted into a wiki I reckon.

Glad you got it solved.
I think overcome guide is very easy to follow step by step apart fr the broken image.
But phloke has made a cached copy for all to see.
http://forum.xda-developers.com/showthread.php?p=20974872
Sent from my GT-P1000 using XDA

Apart from a few minor niceties in the graphics and some improvments in Google maps, I am yet to see what the fuss is about in moving from 2.2 to Overcome. I guess time will tell. I mainly use this TAB for NAV and web and in my work vehicle.
Does the new OC OS give my TAB USBOTG or HDMIoMHL or anything like that, or are these hardware limitations (which I suspect is the case).?
The Overcome TWEAK link goes nowhere, so I don't know what else I can play with to make my experience better.
Is there any real advantage in going to ICS?
One day I may use it for business emails and perhaps invoicing, but I think a larger, say 10" TAB, would be better suited for that anyways.

I am not entirely sure about what I am saying here (didnt research enough), but here is the advantages over 2.2
- froyo may have protected bootloader issue
- overcome uses ext4 compared to rfs. I think ext4 is faster
- overcome kernel has fairly new CwM recovery. Great for flashing new stuff
- froyo cant run flash
- stock kernel doesnt support vpn
- stock kernel doesnt support overclocking and dont have addition schedulers and governers
Anyway, I think overcome is a good stepping stone your next custom rom.
Many custom roms instruction includes flashing overcome first.
I am now using Acudroids with Red Pill kernel.
Excelent battery life and super stable.
Sent from my GT-P1000 using XDA

priyana said:
I am not entirely sure about what I am saying here (didnt research enough), but here is the advantages over 2.2
- froyo may have protected bootloader issue
- overcome uses ext4 compared to rfs. I think ext4 is faster
- overcome kernel has fairly new CwM recovery. Great for flashing new stuff
- froyo cant run flash
- stock kernel doesnt support vpn
- stock kernel doesnt support overclocking and dont have addition schedulers and governers
Anyway, I think overcome is a good stepping stone your next custom rom.
Many custom roms instruction includes flashing overcome first.
I am now using Acudroids with Red Pill kernel.
Excelent battery life and super stable.
Click to expand...
Click to collapse
Sounds like it was worth it.
Speaking of next custom ROM, what advantages would I get for going to Honeycomb or ICS? I read bits of another thread saying that certain hardware was not yet supported in ICS such as GPS, Camera and Blutooth.
Is this also the case with Honeycombe and have these issues been solved?

Honeycomb is a half thought effort by Google.
Just forget it and move to ICS.
Both TE4M CM9 and AOKP are ICS and they are in tablet mode.
I don't know what is the advantage, I guess if you like your Tab to work as tablet and like the latest OS, then go for it.
If I am not mistaken, only back camera has issue. The rest should be ok.