Forgive me if this is a completely stupid question, since we're able to hack/root/whatever the nook color, why can't we install the latest android OS on it?
Check the dev thread. They are already booting an alpha version of froyo.
Sent from my SAMSUNG-SGH-I897 using XDA App
The latest is Gingerbread (2.3), not Froyo (2.2). The problem is that it is only officially released as source and the Nexus S. There's little developed driver support yet. As more official and user developed Gingerbread builds get released, there's a lot more to work with.
I think it's cool that they are working with Froyo, rather than Eclair though!
Hello everyone,
I was just curious how all these gingerbread ROMs for the Captivate are being released, and Cyanogen 2.3 for the Capitivate, having been worked on for months, is still only in pre-beta. I am not trying to be impatient, I know the devs are working hard to get cyanogen out ASAP, I was just curious why this was.
Thank you.
rcllcr said:
Hello everyone,
I was just curious how all these gingerbread ROMs for the Captivate are being released, and Cyanogen 2.3 for the Capitivate, having been worked on for months, is still only in pre-beta. I am not trying to be impatient, I know the devs are working hard to get cyanogen out ASAP, I was just curious why this was.
Thank you.
Click to expand...
Click to collapse
simply put CM7 is being written and developed from "scratch" and the jvb jvh roms are ported.
Not to mention that the CM7 for captivate is running 2.3.4 so technically "we're" behind CM7
betadan said:
Not to mention that the CM7 for captivate is running 2.3.4 so technically "we're" behind CM7
Click to expand...
Click to collapse
Not for long Most of the Devs are already working on JVH
AOSP is the way to go in the long run as more Samsung drivers get ported over. 2.4.x will probably never be ported to the Galaxy S phones by Samsung, but unless there are major kernel changes, upgrading CyanogenMod to 2.4 will happen relatively quickly.
nkrick said:
AOSP is the way to go in the long run as more Samsung drivers get ported over. 2.4.x will probably never be ported to the Galaxy S phones by Samsung, but unless there are major kernel changes, upgrading CyanogenMod to 2.4 will happen relatively quickly.
Click to expand...
Click to collapse
I see, so once it is caught up with the other cyanogen supported phones, it will be on the same update cycle, and therefore be more sustainable when it comes to new releases of android?
Frankly cm7 is actually being developed, where as the other ginger bread releases are being cooked/tweaked. Samsung did 80% of the work then xcal kicked in the next 15%.
So to answer your question, the reason it is "behind" is because they are not using a pre optimized build, and they are developing from the ground up.
Sent from my SGH-I897 using XDA Premium App
Please suggest 2.3 rom whiich is the most stable and fast
Sent from my E16i using XDA App
Don't ask for ETA's!
Read the forum rulez!
EDIT: Yeah, change the title and everything and make me look like an idiot.
Firstly, ICS isnt android 2.3, its android 4.1, android 2.3 is Ginger Bread, currently, all the ICS developments are still in beta stages and arent really recomended for daily use because they are still very buggy and need a lot of work before they can really be complete.
However if infact youre looking for a Ginger Bread ROM then there are a few different ones on our side of the forum that are all complete in their own ways, so youll get mixed responses from everyone on what they think is the 'most complete' ROM, just try a few out for yoirself and if youre up for it try some of the kernels that are in development and see what suits you best, its probably the best way of finding out really.
Beans
Sent from my X8 using XDA Premium App
I though HP released all source?
Sent from my Galaxy Nexus using xda premium
I believe the one they released was for Gingerbread or Honeycomb, not ICS. The kernel in ICS is basically being built from scratch.
The mysterious Touchpads that shipped with Android had Froyo on them and I believe everything wasn't even working on Froyo. I'm guessing Android was chosen as a test OS. By the time HP released the source work was being done on CM9 so Froyo source wasn't really helpful.
My buddy has a cappy and the poor soul is still running 2.1. Now that he no longer has a warranty on it, he wants to root and upgrade it.
My question isn't what's the best ROM because I understand that is highly subjective, but rather, what is the most stable ROM?
ICS on the HTC Inspire only recently hit mile stone release status and, while fairly stable prior to this, still had it's bugs. This was fine for me, but I don't want to bring my friend into this awesome world with a ****ty experience right off the bat plagued with random reboots, bootloops, or non working functions.
So what ROMs are rock solid stable and are good for daily drivers?
And like I said, I'm not looking for "I like this ROM" and I'm not trying to ask what is the best ROM. Only asking about stability.
Thanks guys
Still subjective...but my 2 cents --
Stability wise I would suggest that he upgrade to the Gingerbread 2.3.5 i897ucKK4 release, get Root and then Debloat it completely. Let him run that for a while. He will be pleasantly surprised i think, especially compared to eclair 2.1 that he has been running. Afterwards if he wants to move on to a Developer's Rom, then there are plenty of KK4 based Roms to choose from. He will just have to do some diggin in the Dev forum.
The other Roms ICS, JB, AOSP, CM, MIUI and those similar are very good...but still subjective to each individual user as to what is stable and fit for a daily driver, etc.
Sent from my SGH-I897 using xda premium
Sounds good. I appreciate the reply.
I do have one last question though. As far as doing this, it looks like I just need to get him updated via the Samsung website updates and then use SuperOneClick for root. Is this correct?
I ask because holy crap are there a lot of traps to accidentally fall in to...
He could do the mini kies route to froyo then gb Or he/u could use the kk4 one click odin or heimdall with bootloaders and then get Root through the [Utility] KK4 Easy Root by Red_81 --- both of these u can find in my signature link below.
Sent from my SGH-I897 using xda premium
The Heimdall followed by Easy Root seems the best way to go then (less steps). Thanks so much. I appreciate it.
Now to find that page with the drivers again.... lol (no need to post the link, I'll find it haha)
Here ya go, it was close by... http://forum.xda-developers.com/showthread.php?p=33577757
Sent from my SGH-I897 using xda premium
That's not the page I was looking at before. lol
I was looking here: http://forum.xda-developers.com/showthread.php?t=858765 That and, of course, installing the SDK on his computer.
But after reading the Heimdall page and that post you pointed me to, it seems I was looking in the wrong direction. I know the SDK won't hurt anything though, so that is still getting put on there, if for no other reason than ADB. (I'm a fan of ADB. It's gotten me out of more than a few binds before.)
4-2ndtwin said:
Still subjective...but my 2 cents --
Stability wise I would suggest that he upgrade to the Gingerbread 2.3.5 i897ucKK4 release, get Root and then Debloat it completely. Let him run that for a while. He will be pleasantly surprised i think, especially compared to eclair 2.1 that he has been running. Afterwards if he wants to move on to a Developer's Rom, then there are plenty of KK4 based Roms to choose from. He will just have to do some diggin in the Dev forum.
The other Roms ICS, JB, AOSP, CM, MIUI and those similar are very good...but still subjective to each individual user as to what is stable and fit for a daily driver, etc.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Completely agree with this. Your buddy will need to experience and learn a lot of stuff through this transition, therefor, making the jump to JB from Eclair could make a mess.
Although, once he reaches that point, I have to say that I've been very pleased with AOKP (now on milestone). I was quite hesitant to use it as my daily ROM cause I was so used to stability over tweaks with ROMs made by The Family and The Collective. I've been on it since JB was ported to our cappy and I'm seriously loving it! Can't imagine flashing anything else as my daily ROM unless it's as stable and that coming from a flash addict!
Anyway, hope the transition goes well!
Me too. We were gonna do it yesterday, but after the mayhem of my truck (took 4 hours to rotate TWO tires....), we decided that luck was not with us and decided against it lol. Hopefully I can get him to man up about it today.
Thanks for the help guys! Now to produce another convert... muahahahaha!
I would simply use the stable version of CM10.
eksasol said:
I would simply use the stable version of CM10.
Click to expand...
Click to collapse
I believe CM10 is on nightly builds atm, therefor, bugs are meant to happen. Might not be the best idea for a first step into JB
BWolf56 said:
I believe CM10 is on nightly builds atm, therefor, bugs are meant to happen. Might not be the best idea for a first step into JB
Click to expand...
Click to collapse
http://get.cm/?device=captivatemtd&type=stable
eksasol said:
http://get.cm/?device=captivatemtd&type=stable
Click to expand...
Click to collapse
Well then, I stand corrected.