Related
Another phone looks to be coming in April, (via BGR). Hopefully we also get 2.4 as soon as this launches, and that we don't have to wait...
http://www.bgr.com/2011/02/07/android-2-4-reportedly-lands-in-april-viewsonic-among-first-to-launch/
uhhhhhhh... interesting to see ViewSonic coming to the battleground
they used to be famous for their Displays and Monitors... i wonder if they plan to release their own screens to fight against Samsung & Sony
AllGamer said:
uhhhhhhh... interesting to see ViewSonic coming to the battleground
they used to be famous for their Displays and Monitors... i wonder if they plan to release their own screens to fight against Samsung & Sony
Click to expand...
Click to collapse
Should be interesting. Also, I had not heard of a ViewSonic phone before this article, and I am not sure if I am liking its design.
Nonetheless, based on what you said, it's good to see others come along and hopefully compete with Samsung, especially since so many people do not like or want a Samsung phone - other than to have Samsung's beautiful phone screen.
Bmerz said:
Should be interesting. Also, I had not heard of a ViewSonic phone before this article, and I am not sure if I am liking its design.
Nonetheless, based on what you said, it's good to see others come along and hopefully compete with Samsung, especially since so many people do not like or want a Samsung phone - other than to have Samsung's beautiful phone screen.
Click to expand...
Click to collapse
that's exactly my problem
I love their screens, but not so much their bugged phones
AllGamer said:
that's exactly my problem
I love their screens, but not so much their bugged phones
Click to expand...
Click to collapse
Ditto. There are a few other interesting forays into the smartphone market this year like vizio. Ill add a link when I get back to my computer
Sent from my Darkginger CM7 Google Nexus S!
Would the nexus s get the update before its released on another phone?
Sent from my SGH-T959 using XDA App
If they don't update us before or at the same time the phone releases, this will be my last android device.
Sent from my Nexus S using XDA App
meetagrawal said:
If they don't update us before or at the same time the phone releases, this will be my last android device.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
it doesn't work that way you see...
we on SNS got 2.3 before any body else
including the old HTC N1 which are still stuck on 2.2 officially
unofficial ROM cooks of course released 2.3
so chances are we'll see the same with 2.4 or 3.0
benifactor said:
Would the nexus s get the update before its released on another phone?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I've seen two(2) videos showing 2.4 in the NS.
One of them showed 2.4 build GRI06B.
I'm not sweating...
Look in the I9023 thread.
Worst case: more fragmentation with I9020 2.3 and I9023 with 2.4...both being NS. haha
AllGamer said:
it doesn't work that way you see...
we on SNS got 2.3 before any body else
including the old HTC N1 which are still stuck on 2.2 officially
unofficial ROM cooks of course released 2.3
so chances are we'll see the same with 2.4 or 3.0
Click to expand...
Click to collapse
Well, the way they're treating N1 owners right now is rubbing me the wrong way, but I'm willing to give them benefit of the doubt. In fact, they could be just waiting till 2.4 is ready to give it to both Nexus 1 and Nexus S. We buy the Nexus phones partly because we are supposed to be given updates on a first priority basis. If Google decides to hold back 2.4 from us for another phone, they will have lost an Android supporter in me.
AllGamer said:
uhhhhhhh... interesting to see ViewSonic coming to the battleground
they used to be famous for their Displays and Monitors... i wonder if they plan to release their own screens to fight against Samsung & Sony
Click to expand...
Click to collapse
They already have an Android Device the "g Tablet". Although from what I have read the reviews say the screen sucks (poor viewing angle), surprises me since that is what they do. On another note the g Tablet has Android 2.2 and nVidia Tegra 2
...viewsonic.com/gtablet/
meetagrawal said:
Well, the way they're treating N1 owners right now is rubbing me the wrong way, but I'm willing to give them benefit of the doubt. In fact, they could be just waiting till 2.4 is ready to give it to both Nexus 1 and Nexus S. We buy the Nexus phones partly because we are supposed to be given updates on a first priority basis. If Google decides to hold back 2.4 from us for another phone, they will have lost an Android supporter in me.
Click to expand...
Click to collapse
I'd bet my meager reputation that we get it before.
Sent from my Darkginger CM7 Google Nexus S!
I'd be shocked if we didn't get the 2.4 update, at the time of its launch. Especially since 2.4 doesn't seem to be Ice Cream, but rather a touch of Honey glazed over Gingerbread.
While I am kind of new to Android (and smart phones in general), I cannot see Google keeping this update from us NS users. Although, I am a little surprised that the N1 hasn't seen Gingerbread yet (OTA from Google that is).
Just curious, how many updates did the N1 get from the time of its launch, and what Android version did it start with (Eclair or Froyo?).
I'm really surprised the N1 hasn't seen GB officially yet. I would be curious to see 2.4
Bmerz said:
I'd be shocked if we didn't get the 2.4 update, at the time of its launch. Especially since 2.4 doesn't seem to be Ice Cream, but rather a touch of Honey glazed over Gingerbread.
While I am kind of new to Android (and smart phones in general), I cannot see Google keeping this update from us NS users. Although, I am a little surprised that the N1 hasn't seen Gingerbread yet (OTA from Google that is).
Just curious, how many updates did the N1 get from the time of its launch, and what Android version did it start with (Eclair or Froyo?).
Click to expand...
Click to collapse
N1 came with eclair and then got froyo 2 months later I believe.
Sent from my Darkginger CM7 Google Nexus S!
Not liking the Viewsonic design. I thought it was an external HDD.
I hope that the Nexus S gets its update, well if not at the same time as the release of the Viewsonic phone, at least a week or two after.
Bmerz said:
I'd be shocked if we didn't get the 2.4 update, at the time of its launch. Especially since 2.4 doesn't seem to be Ice Cream, but rather a touch of Honey glazed over Gingerbread.
While I am kind of new to Android (and smart phones in general), I cannot see Google keeping this update from us NS users. Although, I am a little surprised that the N1 hasn't seen Gingerbread yet (OTA from Google that is).
Just curious, how many updates did the N1 get from the time of its launch, and what Android version did it start with (Eclair or Froyo?).
Click to expand...
Click to collapse
the phone started with Eclair and it was approximately 6 months until OTA Froyo.
kenvan19 said:
N1 came with eclair and then got froyo 2 months later I believe.
Sent from my Darkginger CM7 Google Nexus S!
Click to expand...
Click to collapse
More like 6 months later for the official OTA.
Sent from my Nexus S using XDA App
krohnjw said:
More like 6 months later for the official OTA.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
When did the first phone with Froyo launch? Or was N1 the 1st to get it?
terra_droid said:
Not liking the Viewsonic design. I thought it was an external HDD.
I hope that the Nexus S gets its update, well if not at the same time as the release of the Viewsonic phone, at least a week or two after.
Click to expand...
Click to collapse
that's exactly what i though as well when i first saw the picture. LOL
http://www.pocket-lint.com/news/38311/android-2-4-april-release-date
in a move that shows there is some kind of cover-up of the mistake of the lack of Android 2.3 devices on the market (aside from the Nexus S) 2.4 will still be called Gingerbread, as the only new feature it adds will be this ability to support dual-core apps on a single-core device.
Click to expand...
Click to collapse
Makes complete sense. Dev's are already using the honeycomb SDK to produce apps made for dual core devices. Google cares more about having the maximum number of apps to be available to as many people as possible rather than having a handful of consumers having the absolute latest edition (and I have to agree with them).
How many stock vanilla android devices are there? Just us and the NS (pretty sure no one gets OTA's the day of except us two). Getting an OS out there for everyone is more important then keeping a relatively small group happy with the latest official build. Besides, the N1 is meant for ROM's. Google want's us to play with them, which is why I own the phone. If you've been waiting for gingerbread, just flash a freaking ROM and be happy.
Gingerbread isn't even that great anyway.
AFAIK Gingerbread suffers different problems:
1. security
2. resets
IMHO google devs are working on them before pushing 2.3 on the nexus one too, making it vulnerable and unstable.
elegos said:
AFAIK Gingerbread suffers different problems:
1. security
2. resets
IMHO google devs are working on them before pushing 2.3 on the nexus one too, making it vulnerable and unstable.
Click to expand...
Click to collapse
Yhea i did read about the resets in NS, i'm using GB on N1 but it never resets on it's own.
commodoor said:
Yhea i did read about the resets in NS, i'm using GB on N1 but it never resets on it's own.
Click to expand...
Click to collapse
The resets may be an issue with the Nexus S hardware, and not with the OS. The Samsung Galaxy S phones have quite a few "issues", just ask any owner of a Captivate. I switched from the Captivate to a Nexus One, it is a much better phone.
commodoor said:
Yhea i did read about the resets in NS, i'm using GB on N1 but it never resets on it's own.
Click to expand...
Click to collapse
I'm on CM7 and getting occasional random resets.
Google announced 27. January that OTA for Nexus S coming in 1-2 weeks, I don´t know why, but maybe we´ll see both Nexus One and Nexus S OTA.
I wish people would stop saying "just flash a GB ROM and be done with it", there's more to it than that. The N1 is sort of a reference design for alot of phones out there. A working N1 GB ROM means solid drivers, solid battery life, solid performance, etc.
I also have an HD2, it's running GB but the battery life (and BT stack in particular) is pretty poor. Devs say they won't be able to improve much until there are more GB ROMs they can pick parts from. First on that list is the N1.
There are more than just us Nexus One users tapping their fingers waiting for Google on this.
elegos said:
AFAIK Gingerbread suffers different problems:
1. security
2. resets
IMHO google devs are working on them before pushing 2.3 on the nexus one too, making it vulnerable and unstable.
Click to expand...
Click to collapse
The "reset" issue is specific to the NS hardware. Samsung screwed the pooch on that one. There are plenty of people here running GB roms with out issue.
But I do believe the security flaws recently discovered to have a significant impact on GB's delayed release.
GldRush98 said:
The "reset" issue is specific to the NS hardware. Samsung screwed the pooch on that one. There are plenty of people here running GB roms with out issue.
But I do believe the security flaws recently discovered to have a significant impact on GB's delayed release.
Click to expand...
Click to collapse
I've had plenty of resets on my N1 with CM7
James Bell said:
I wish people would stop saying "just flash a GB ROM and be done with it", there's more to it than that. The N1 is sort of a reference design for alot of phones out there. A working N1 GB ROM means solid drivers, solid battery life, solid performance, etc.
I also have an HD2, it's running GB but the battery life (and BT stack in particular) is pretty poor. Devs say they won't be able to improve much until there are more GB ROMs they can pick parts from. First on that list is the N1.
There are more than just us Nexus One users tapping their fingers waiting for Google on this.
Click to expand...
Click to collapse
My N1 is running a GB ROM with solid battery life, and performance. I don't know about drivers but everything works perfectly and as it should. Almost like I am running an official build of GB. The reboot issue only seemed to occur on CM7.. oddly. And it wasn't frequent enough for me to care.
I thought the HD2 always had pathetic battery life when it came to Android. Mine's did, until I remembered to install SetCPU. It last all day, which is just what I need.
I mean the AOSP was released for gingerbread, so we can get some pretty stable ROM's. No it isn't as good as an official update, but if I wanted to wait for official updates, I would have bought a desire.
Now I'm not sure about this, but I think most ROM's that are cooked are built using the ASOP rather than modified stock ROM's. It isn't worth waiting and complaining for a 100% optimized OTA ROM when there are tons of temporary solutions.
XSafire said:
I mean the AOSP was released for gingerbread, so we can get some pretty stable ROM's. No it isn't as good as an official update, but if I wanted to wait for official updates, I would have bought a desire.
Now I'm not sure about this, but I think most ROM's that are cooked are built using the ASOP rather than modified stock ROM's. It isn't worth waiting and complaining for a 100% optimized OTA ROM when there are tons of temporary solutions.
Click to expand...
Click to collapse
dont get ya. do you think desire owners arent using AOSP ginger?
XSafire said:
I mean the AOSP was released for gingerbread, so we can get some pretty stable ROM's. No it isn't as good as an official update, but if I wanted to wait for official updates, I would have bought a desire.
Now I'm not sure about this, but I think most ROM's that are cooked are built using the ASOP rather than modified stock ROM's. It isn't worth waiting and complaining for a 100% optimized OTA ROM when there are tons of temporary solutions.
Click to expand...
Click to collapse
I bought the N1 because it was great hardware and, most importantly, because it was carrier free. The ability to root and flash the phone is nice in case I ever feel the need to admin yet another Linux machine, but that was certainly not everyones reason for getting the phone.
madman_cro said:
dont get ya. do you think desire owners arent using AOSP ginger?
Click to expand...
Click to collapse
I simply meant that we receive updates as soon as they are available, and are the first ones to get it. Desire has to wait for HTC to update sense and drivers and all that stuff until they release an OTA.
pfmiller said:
I bought the N1 because it was great hardware and, most importantly, because it was carrier free. The ability to root and flash the phone is nice in case I ever feel the need to admin yet another Linux machine, but that was certainly not everyones reason for getting the phone.
Click to expand...
Click to collapse
Touche, although there aren't many people on these forums with the same intentions. I was simply speaking to the masses.
I don't know why release is taking so long...
My N1 resets randomly on CM7.... but luckily I don't have the wonks!
Google will release it when its ready!
has anyone heard any more speculation on what phones are gonna get gingerbread?
gingerbread is being skipped and is going to be 2.4 instead of 2.3. Still named gingerbread though. This is what I heard a few weeks back. It makes sense because the Nexus S is full of problems and it's mostly on the software side. Gingerbread is nothing but a themed froyo.
There are a lot less core differences between 2.2 and 2.3 than there were between 2.1 and 2.2. I would think the manufacturers would have an easier time upgrading them and the crapware on it.
Jjday7 said:
gingerbread is being skipped and is going to be 2.4 instead of 2.3. Still named gingerbread though. This is what I heard a few weeks back. It makes sense because the Nexus S is full of problems and it's mostly on the software side. Gingerbread is nothing but a themed froyo.
Click to expand...
Click to collapse
Incorrect. There are other phones getting Android 2.3 besides the Nexus S; the Sony Ericsson Xperia Play is, for example. Gingerbread has made quite a few changes to the underlying code & add many nice APIs for app developers to it.
teharchitekt said:
Incorrect. There are other phones getting Android 2.3 besides the Nexus S; the Sony Ericsson Xperia Play is, for example. Gingerbread has made quite a few changes to the underlying code & add many nice APIs for app developers to it.
Click to expand...
Click to collapse
True, but, don't know if you noticed that the Nexus One has yet to get an OTA Gingerbread OTA. There's a reason for that. The random rebooting issue could be to blame - but Google for Froyo (such a huge, huge change from 2.1 Eclair) pushed it out to Nexus One users like 2 weeks after announcing it. Huge. Quick.
Gingerbread will probably not come to existing devices. 2.4 (whether it is Ice Cream Sandwich or Gingerbread - who knows/cares) will probably be pushed out first. Don't expect any incremental updates to any existing device yet.
The reason the Xperia Play has 2.3 is because it's out in the AOSP and Sony Ericsson is just choosing to deploy the 2.3 code instead of 2.2. They have the right timeframe and want their device to appeal to the hardcore geeks.
Anyhow, no Gingerbread - especially not for the EVO 4G Shift anytime soon.
I'm hoping for updates to the Shift, i just got it, but i hate knowing there is a newer version somewhere lol
I hate knowing that I got gingerbread working on a 4 year old Windows Mobile phone (HTC Touch/Vogue) and yet it's not officially available for the Evo Shift. I may go AOSP in the future.
Sent from PG06100 (Evo Shift 4G) & XDA App
NuAngel said:
I hate knowing that I got gingerbread working on a 4 year old Windows Mobile phone (HTC Touch/Vogue) and yet it's not officially available for the Evo Shift. I may go AOSP in the future.
Sent from PG06100 (Evo Shift 4G) & XDA App
Click to expand...
Click to collapse
AOSP is where it's at.
Sent from my PG06100
Edit: man I'm drunk. That took forever to type.
Noob question: What exactly is aosp and are there any pros as far as roms go?
Sent from my Evo Shift.
Aosp is android open source project, check out the cyanogen/evervolv roms and that's what aosp is
Waht is AOSP
bobtsunam said:
Noob question: What exactly is aosp and are there any pros as far as roms go?
Sent from my Evo Shift.
Click to expand...
Click to collapse
AOSP is default open source Android. Every manufacturer puts on their own overlay for HTC it is Sense and Motorola is Moto Blur. When you put an AOSP ROM on your phone it will be default android which is normally more efficient and more bare bones. For instance when you might not have all the functionality that you had with your stock setup. Personally I like how in Sense when I have my Google contacts set up in groups Sense se that and carries those groups over to my phone. When I put the evervolve or CM7 on my phone to test it out I lost that.
I don't know all the things that are different with an AOSP ROM but here are the things I have seen:
Contacts
Messaging app
Home Screen
Now I know there are more programs that are operate in the background that are included (just run titanium backup and look at all the ones that start with HTC) but I don't know what they do for the most part.
Also AOSP stands for Android Open Source Project.
I think I'll wait for a stable sense ROM to try gingerbread. I'm pretty sure I tried a bare bones ROM when I rooted my cliq and didn't like it. Definitely like having everything sync'd like contacts and such. Has anyone come up with something spectacular for a modded or themed stock ROM? Guess I could just go look...
Thanks everyone for the help. Really appreciate it.
Sent from my Evo Shift.
While the T959 is a well built phone with great specs, I felt like it was incomplete until 2.2 ROMs came out in November. Then, when 2.3 and the Nexus S were announced, that feeling returned.. now with Cyanogenmod7 working so well, I am in love with my Vibrant once again.
Even without any further version updates (2.4, 3.0 if possible) the phone has been improved dramatically by the work of Team Whiskey, Supercurio, Eugene, and the Cyanogenmod Team.
What keeps the Vibrant apart from all the HTC and Motorola phones when it comes to Cyanogenmod - is it a driver issue? Is it because of the Hummingbird processor?
Now that CM7 is finally working well on the Vibrant, does this mean that future Cyanogenmod versions will work on the Vibrant? Have they finally "cracked the shell" so to speak?
I am curious also as to what makes CyanogenMod different to work on for our phones vs the other ones you named.
CM is actually worse for Motorola devices as they have a locked bootloader...
On the other hand, HTC is very good about releasing source for their devices when compared to Samsung, who rarely releases source code if at all (driver source). Plus, CM started on HTCs, and with every device using similar Qualcomm hardware, i can imagine it is easier to port to newer Qualcomm-equipped HTC devices. That said, it appears that HTC is beginning to implement software to prevent rooting on newer phones like the G2, so we may see more people moving towards the more open Samsung devices.
Finally, this is explained to me. Thanks!
Why do drivers need to be recompiled for each version of Android? Do they need to be recompiled for similar releases such as 2.0 and 2.1 or 2.3 and 2.4?
I'm not exactly an expert when it comes to the Linux architecture, so take the following with a grain of salt.
Anyways, I believe it has to do with the kernel, which should contain the device drivers. Now, kernels must indeed be recompiled for every android system update; this is why a 2.1 or 2.2 kernel will not work with the newer 2.3.x roms. The problem for us is that once Samsung stops releasing kernels/roms for the SGS series, devs will no longer have a base to build off of. Hopefully devs can make use of updates/drivers from the Nexus S to keep the SGS series up to date with CM.
qtilt ......... nicely explained
oka1 said:
qtilt ......... nicely explained
Click to expand...
Click to collapse
I agree!
The main difference between CM/MIUI and the rest of the roms you see here on XDA is that CM/MIUI are built directly off of a Vanilla Froyo/Gingerbread. No extra flavorings or seasonings such as TouchWiz, HTC Sense, MotoBlur, Droid UI, etc. The use of, or misuse of, causes phones to run slower and do more work (unnecessarily) while it computes extra calculations of the UI. [EDIT]When developers BASE a rom off of a leak or pre-existing firmware it does not make it Vanilla just by removing TWiz or Sense or the rest of bloatware. Vanilla is generally the most simple a firmware can be, with no added extra-pazzaz[/EDIT]
There hasn't been a solid update to MIUI for our phone in a month, but CM has nightly builds and HOPEFULLY it has "cracked the shell," so to speak. Even if Samsung STOPS upgrading our firmware (which has already happened IMO), CyanogenMod makes their own code and develops independently without the use of previous stockpiles of code...which is why it's difficult at first to come up with their own driver source (because Samsung refuses to release ALL the sources needed). Hopefully our Vibrant is covered for the next 2.4 or 3.0 (3.1) update.
Samsung needs to continue to make money. They wouldn't if they let each phone update to the newest andros os. Not just samsung, any hardware company.
Sent from my vibrant using cyanogenmod7.
boltdidit said:
Samsung needs to continue to make money. They wouldn't if they let each phone update to the newest android os. Not just Samsung, any hardware company.
Click to expand...
Click to collapse
I disagree with this because, If Samsung released the code and people updated their phones as they liked and put different operating systems, roms as they liked. customer satisfaction would skyrocket. People would be more likely to buy new phones only from Samsung because they wanted the newest available hardware, read this as faster more flexible with more options.
but alas Samsung as with most of the manufacturers suffer from penny wise and dollar stupid syndrome and they end up being fairly low on the customer satisfaction scale another words they suck
rbcamping said:
I disagree with this because, If Samsung released the code and people updated their phones as they liked and put different operating systems, roms as they liked. customer satisfaction would skyrocket. People would be more likely to buy new phones only from Samsung because they wanted the newest available hardware, read this as faster more flexible with more options.
but alas Samsung as with most of the manufacturers suffer from penny wise and dollar stupid syndrome and they end up being fairly low on the customer satisfaction scale another words they suck
Click to expand...
Click to collapse
As a hardware company customer satisfaction is one thing and making them buy more of their products is another. If your 4,5-years old phone can still upgrade to the newest OS why would you buy a new one? So there is a balance for them to keep, their want to make their customer happy with their product but not too happy so their stay with old product forever.
That's very much why samsung was hesitated about 2.3 upgrade for the galaxy line.
The future of the device has more to do with whether or not the developers stick with the device. With the SGS being an international phone there is a better chance of this happening, and samsung has started getting better with releasing their source. As mentioned earlier HTC is making devices harder to root, for example the HTC desire CDMA with 2.2 is impossible to root and the G2 was an annoyance.
Also samsung has released multiple phones that are very close to the Vibrant such as the Nexus S and the Vibrant 4g. The Nexus S will be updated for awhile and source will be released for it, so its something though not much. The Vibrant 4g will also hopefully be updated and that will hopefully be an easy port. Also 2.4 is very similar to 2.3 so that will hopefully be an easy update for the developers.
Basically as long as we have the awesome devs that we have and we dont flame everyone that the devs get tired of working with the phone then we will have a device that will be updated and beautiful.
I want a stock style gingerbread, and I hope a touchwiz themed CM7 coming out.
vvsnail said:
I want a stock style gingerbread, and I hope a touchwiz themed CM7 coming out.
Click to expand...
Click to collapse
I believe Krylon is working on Stock, as for a Twiz themed CM7 I ask why?
bearsfan85 said:
I believe Krylon is working on Stock, as for a Twiz themed CM7 I ask why?
Click to expand...
Click to collapse
Ha, this is whats to come. CM7 hasn't arrived yet and now they want it with twiz. The ridding of twiz is part of what makes it great.
Sent from my SGH-T959
joe.kerwin said:
Ha, this is whats to come. CM7 hasn't arrived yet and now they want it with twiz. The ridding of twiz is part of what makes it great.
Sent from my SGH-T959
Click to expand...
Click to collapse
+1 agree 100%
bearsfan85 said:
The future of the device has more to do with whether or not the developers stick with the device. With the SGS being an international phone there is a better chance of this happening, and samsung has started getting better with releasing their source.
...
Basically as long as we have the awesome devs that we have and we dont flame everyone that the devs get tired of working with the phone then we will have a device that will be updated and beautiful.
Click to expand...
Click to collapse
Amen. Well stated.
Android 4.0 source being released now! Can't wait for some roms!
http://www.droid-life.com/2011/11/1...same-android-4-0-1-build-as-the-galaxy-nexus/
WOOP WOOP. cm9 here we go!!!
Just beat me to it
So excited!
http://androidandme.com/2011/11/new...idandme+(Android+and+Me)&utm_content=FaceBook
cant wait, ahihihi
It's up now.
http://groups.google.com/group/android-building/msg/40cbd4ea69e035d5
That's just GREAT!
I cannot wait to see ICS on my sexy N!
So why CM9 and not CM8?
Swyped from my Nexus One
SiNJiN76 said:
So why CM9 and not CM8?
Swyped from my Nexus One
Click to expand...
Click to collapse
Because there never was a CM for honeycomb, so to simplify things they skipped CM8 as they skipped Honeycomb.
Ahhh...completely forgot about Honeycomb. Thanks!
Swyped from my Nexus One
How amazing and refreshing is this:
The branches that you care about:
-android-4.0.1_r1 is the release branch, ITL41D, that is expected to
ship on Galaxy Nexus. That's the one you want to be using to port to
devices.
Click to expand...
Click to collapse
I know a lot of you are exciting about CM, but will there also be a vanilla Google ROM of ICS for the N1?
kostiak said:
I know a lot of you are exciting about CM, but will there also be a vanilla Google ROM of ICS for the N1?
Click to expand...
Click to collapse
Not from Google themselves. They've stopped support for the N1 so best bet will have to be somebody here making a ROM for the N1.
kostiak said:
I know a lot of you are exciting about CM, but will there also be a vanilla Google ROM of ICS for the N1?
Click to expand...
Click to collapse
As someone who stays as far away from CM, I am hoping for a very very vanilla AOSP 4.0 for N1. I almost wish that google would built it but just not OTA it, and let developers figure out the space issue..
There is no need to worry about small system partition size.
BlackRose is the answer.
We'll get ICS
dla5244 said:
There is no need to worry about small system partition size.
BlackRose is the answer.
We'll get ICS
Click to expand...
Click to collapse
I wonder where the drivers could be obtained
I guess GB drivers does not work on ICS
It's going to be a little more complicated to bring to devices because the device is now considered "obsolete" like the G1 and the Ion. Hopefully someone other than Cyanogen can make us a good AOSP rom.
Nexus S, a.k.a. "crespo", and Nexus S 4G, a.k.a. "crespo4g", are supported with gingerbread, but can't currently be used with newer versions of the Android Open-Source Project.
Nexus One a.k.a. "passion" is obsolete, was experimental in gingerbread and unsupported, and can't be used with newer versions of the Android Open-Source Project.
Android Developer Phones (ADP1 and ADP2, a.k.a. "dream" and "sapphire") are obsolete, were experimental and unsupported in froyo, and can't be used with newer versions of the Android Open-Source Project.
Click to expand...
Click to collapse
DownloaderZ said:
As someone who stays as far away from CM, I am hoping for a very very vanilla AOSP 4.0 for N1. I almost wish that google would built it but just not OTA it, and let developers figure out the space issue..
Click to expand...
Click to collapse
Why do you stay far away from CM?
Some people just want no customizations even as little as they might be.
But if CM manages to get a rom working on the N1 someone can take that as a base to build a vanilla rom.
So I'm pretty sure this will come!
nergrum said:
Why do you stay far away from CM?
Click to expand...
Click to collapse
Well although I am running CM7.1 right now I really can see the reason for this. I ran an unrooted version of Vanilla GB since about February and only decided to adjust recently to get ready for ICS after it was announced we wouldn't officially get it. I know Vanilla has less features but it somehow just feels of a higher quality at times. Bit of a less is more type of thing.
Has everybody seen the Cyanogen Twitter feed? Two months for stable builds of CM9 and work on CM7 7.1.2 continues in the meantime.
(Nothing specific mentioned about the N1 though)