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)
Related
Does anyone has a clue about when Froyo will be available for Aria?
I'm not holding my breath for update from AT&T!
saint168 said:
I'm not holding my breath for update from AT&T!
Click to expand...
Click to collapse
I am hoping we'll be able to port the Legend Rom with a great deal of success once it is available. I will be looking into an unbranded 2.1 Legend ROM port for the Aria next.
eh it was just released... wouldn't expect to hear about a 2.2 release for at least a few months probably more.
Froyo hasn't even been officially released yet. after that, HTC will need to port SenseUi for it. HTC did say all 2.1 devices released this year should expect a 2.2 update.
Probably not until AT&T figures out how to remove tethering from it.
ryusen said:
Froyo hasn't even been officially released yet. after that, HTC will need to port SenseUi for it. HTC did say all 2.1 devices released this year should expect a 2.2 update.
Click to expand...
Click to collapse
As saint168 said, I wouldn't hold your breath. What will happen is HTC will say "we expect a Froyo update for the Aria by Christmas!" and then the day before Christmas they will say "We expect a Froyo update for the Aria by the end of February!" and then we won't see an update except in Taiwan in June.
I am going by the official Eclair update for the GSM Hero of course.
attn1 brought up a factor, as most likely we will be seeing mostly stable 2.2 Roms within the next six months or so for the Aria that will probably make the frustrations of any promised official update increase.
Shad0wguy said:
Probably not until AT&T figures out how to remove tethering from it.
Click to expand...
Click to collapse
Or perhaps not remove it outright, but to figure out how to make it billable to the tune of extra $20 per month on top of "DataPro" data plan, as they've done it with iPhone 4/iOS4.
Android 2.2 Froyo will definitely for Aria but i don't count on AT&T. I want a clean Froyo and not At&T B.S. in there
jaex said:
Android 2.2 Froyo will definitely for Aria but i don't count on AT&T. I want a clean Froyo and not At&T B.S. in there
Click to expand...
Click to collapse
cyanogen has said he's porting to the MT3GS, which is nearly identical to the Aria. That WILL be ported to the Aria.
AOSP Froyo 2.2 - cyanogen style. Everyone and their all their brothers will be taking a crack at that port - including me.
attn1 said:
cyanogen has said he's porting to the MT3GS, which is nearly identical to the Aria. That WILL be ported to the Aria.
AOSP Froyo 2.2 - cyanogen style. Everyone and their all their brothers will be taking a crack at that port - including me.
Click to expand...
Click to collapse
Will this be a dump of the official update for the MT3GS or is there a port that's being used. Also, if this is a pre-existing port then what kind of features should we expect to not work by the time it hits Aria (like camera, 3D acceleration, gps, and sound)?
By the way ... my Aria is now in my state so hopefully will be playing with it in an hour or two.
sentinel79 said:
Will this be a dump of the official update for the MT3GS or is there a port that's being used. Also, if this is a pre-existing port then what kind of features should we expect to not work by the time it hits Aria (like camera, 3D acceleration, gps, and sound)?
By the way ... my Aria is now in my state so hopefully will be playing with it in an hour or two.
Click to expand...
Click to collapse
The MT3GS and Aria are very closely related. HTC does not do AOSP roms - they add their proprietary HTC sense stuff. If you want that, it will take some time for HTC to release a stable version for either the MT3GS or the Aria.
AOSP means Android Open Source Project based - and that means no HTC Sense UI. The Nexus One runs pure AOSP, which personally, I prefer. cyanogenmods are all AOSP based, but are generally better in terms of features and performance.
cyanogenmod 6.x will be based on Android 2.2 AOSP code, and is being built and in limited testing now. It will be released for a half dozen phones almost simultaneously - and soon. Once something is working for the MT3GS, it will be a very short time before it is ported to the Aria.
attn1 said:
The MT3GS and Aria are very closely related. HTC does not do AOSP roms - they add their proprietary HTC sense stuff. If you want that, it will take some time for HTC to release a stable version for either the MT3GS or the Aria.
AOSP means Android Open Source Project based - and that means no HTC Sense UI. The Nexus One runs pure AOSP, which personally, I prefer. cyanogenmods are all AOSP based, but are generally better in terms of features and performance.
cyanogenmod 6.x will be based on Android 2.2 AOSP code, and is being built and in limited testing now. It will be released for a half dozen phones almost simultaneously - and soon. Once something is working for the MT3GS, it will be a very short time before it is ported to the Aria.
Click to expand...
Click to collapse
Man this is like night and day coming from the Xandroid community (new android features seem to take months to develop).
I too prefer AOSP which I used on the Xandroid builds (tested on my Pure) and I had Launcher Pro installed which I think is LEAGUES better than Sense.
I'm extremely excited to learn more about flashing android roms. Don't know anything about it yet but I saw Aria's already been rooted.
I do appreciate the WVGA of the Pure but this Aria really isn't THAT different in quality (seems more colorful though). Gotta get a screen protector from AT&T ... will have to wade through crowds of iPhone sheep no doubt.
attn1 said:
AOSP means Android Open Source Project based - and that means no HTC Sense UI. The Nexus One runs pure AOSP, which personally, I prefer. cyanogenmods are all AOSP based, but are generally better in terms of features and performance.
cyanogenmod 6.x will be based on Android 2.2 AOSP code, and is being built and in limited testing now. It will be released for a half dozen phones almost simultaneously - and soon. Once something is working for the MT3GS, it will be a very short time before it is ported to the Aria.
Click to expand...
Click to collapse
When you say ported, does that mean I can rewrite my phone replacing Sense? Because I don't just want to have Froyo AND Sense and just have sense disabled and hiding in the background.
hocplyr98 said:
When you say ported, does that mean I can rewrite my phone replacing Sense? Because I don't just want to have Froyo AND Sense and just have sense disabled and hiding in the background.
Click to expand...
Click to collapse
I think you're confusing Android 2.2 (FroYo) with HTC's user interface (Sense).
cyanogenmod is based on pure AOSP code - no Sense UI.
I just completed a port of a MyTouch3G rom to the Aria. Wifi doesn't work, and my touch keys don't work. I am sure those are simple fixes. Eugene probably has answers to some of those issues, but it stands to reason that when CM 6 is released for the MTS3G, we can begin work on a port for the Liberty (Aria).
Froyo runs... it's just a matter of someone who knows what they're doing fixing all of the drivers and a few other things.
big file here
CM6 is coming soon I think!
"release later this weekend" ... running out of time but this is exciting.
http://androidspin.com/2010/06/25/sneak-peek-at-cyanogenmod-cm6-test-build-on-g1-and-nexus/
So what does the release of CM6 mean for us?
attn1 said:
The MT3GS and Aria are very closely related. HTC does not do AOSP roms - they add their proprietary HTC sense stuff. If you want that, it will take some time for HTC to release a stable version for either the MT3GS or the Aria.
AOSP means Android Open Source Project based - and that means no HTC Sense UI. The Nexus One runs pure AOSP, which personally, I prefer. cyanogenmods are all AOSP based, but are generally better in terms of features and performance.
cyanogenmod 6.x will be based on Android 2.2 AOSP code, and is being built and in limited testing now. It will be released for a half dozen phones almost simultaneously - and soon. Once something is working for the MT3GS, it will be a very short time before it is ported to the Aria.
Click to expand...
Click to collapse
jznomoney- Read that
Sorry. Wrong thread.
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.
Well, even though Samsung and Google have delayed their event, Ice Cream Sandwich is around the corner and the funny thing is that still nothing has been confirmed of its features.
Looking forward to it on your Desire Z?
It'll be nice, but I'm sure not much of a change for day to day use for me. I'm more excited about getting it on my Nook Color.
You should put desire z and g2. But I just want it to be released already. Have you seen the new ics video on the supposed nexus prime?
Sent from my HTC G2 using XDA app
98% sure it won't be released for our phones.
rmcsc said:
98% sure it won't be released for our phones.
Click to expand...
Click to collapse
Definitely won't be released officially, but that's why we have CyanogenMod and other CM-derived ROMs
I still hope they think of us Desire owners.....
Sent from my HTC Vision using XDA App
Isn't there an update supposed to be coming for the DZ? Maybe we'll get the ICS with Sense 3.5...
I think they will . But have you guys downloaded the new ics music app just search for it on the forums. Looks similar to the honeycomb one just a few tweeks here and there
Sent from my HTC G2 using XDA app
rmcsc said:
98% sure it won't be released for our phones.
Click to expand...
Click to collapse
I smell Darwin Award....
We all know it wont be released for our phones.
I bought a Viewsonic gTablet and this was the same talk going on - No Honeycomb. Mods started to ban people whining about when HC would be ported to the gTab. I gave up hope and literally a month later, there was an alpha ROM and now there are 3-4 good HC ROMs out there. And I think Google didn't release the source code for it. So, I am sure we will get IS on our Zs!
rmcsc said:
98% sure it won't be released for our phones.
Click to expand...
Click to collapse
Well obviously... But most people on XDA aren't waiting for official OTA updates lol. Go go CM8!!
ashwinmudigonda said:
I bought a Viewsonic gTablet and this was the same talk going on - No Honeycomb. Mods started to ban people whining about when HC would be ported to the gTab. I gave up hope and literally a month later, there was an alpha ROM and now there are 3-4 good HC ROMs out there. And I think Google didn't release the source code for it. So, I am sure we will get IS on our Zs!
Click to expand...
Click to collapse
Well the issue there was no source code and probably a smaller community. It will be much easier when ICS source drops lol.
Im more excited about all the cool roms the devs are going to make based off ICS!
im sure cyanogenmod 8 will be he BOMB!
According to Koush on G+ it will be CM9. Makes sense because Honeycomb wasn't open source
C.Flat said:
According to Koush on G+ it will be CM9. Makes sense because Honeycomb wasn't open source
Click to expand...
Click to collapse
Makes sense I guess, but I would think since CM8 never existed they'd just do CM8 for ICS.
Yea that would be awesome regardless of the naming scheme. I have yet to flash CM7 but for ICS I would do it in a heartbeat lol.
C.Flat said:
According to Koush on G+ it will be CM9. Makes sense because Honeycomb wasn't open source
Click to expand...
Click to collapse
Actually doesnt make sense but let the CM team do what they want....
In related news to CM, CM 7.1 final was released today
I would like to point out that there is absolutely no evidence to suggest that there will not be a 4.0 upgrade available for HTC VISION. Need I remind you all that there was an official upgrade to Android 2.2 for HTC SAPPHIRE/MAGIC32B made almost exactly ONE YEAR AGO? Yes, approximately the exact same time that HTC VISION was initially made available.
Also remember that the 32B was a 192 MB RAM device where only 97 MB was actually available to Linux. This significant upgrade from Android 1.6 to 2.2 required some MEMORY REDISTRIBUTION via new SPL to increase the available RAM to 112 MB. HTC VISION is not starved for RAM as the 32B was. HTC VISION has plenty of space left within the system partition (in fact on mine, there are 262 MB of free space on /system of over 400 total -- clearly intended to leave space for upgrades). Unlike the 32B, the specifications of Vision are far more than adequate, and even with a device as limited as 32B, they made the upgrade.
---------- Post added at 02:33 PM ---------- Previous post was at 02:19 PM ----------
riahc3 said:
Actually doesnt make sense but let the CM team do what they want....
In related news to CM, CM 7.1 final was released today
Click to expand...
Click to collapse
CM "team", as well as all the other rom cookers out there (yes, they are cookers, Android is written by Google, CM just cooks it and adds in a few goodies.) do a TERRIBLE job of versioning.
I once suggested a much more sensible approach to versioning, which is used by many other downstream open source projects... but they threw a tantrum.
Versioning of Android ROMs should be as follows;
UPSTREAMNAME-UPSTREAMVERSION-DOWNSTREAMREVISION.DOWNSTREAMNAMEVERSION.ARCHITECTURE
Obviously ARCHITECTURE doesn't apply directly, but this could be replaced with DEVICE.
So.... CM7.1 for VISION should be versioned as
android-2.3.7-0.CM7.1.vision
With this, if they make a minor update (that they would normally call CM7.1.1), it would increment the DOWNSTREAMREVISION, so the new version would be android-2.3.7-1.CM7.1.vision.
I.e., the point here would be to keep the priority on the upstream version rather than downstream, because "android-2.3.7" is FAR more important than "CM7.1". Quite frankly, the "CM" version means ABSOLUTELY NOTHING.
Haven't heard anything amazing about ICS so far wish I had though. Any solid awesome rumors about improvements or features?
killj0y said:
Haven't heard anything amazing about ICS so far wish I had though. Any solid awesome rumors about improvements or features?
Click to expand...
Click to collapse
Not really.
dhkr234 said:
I would like to point out that there is absolutely no evidence to suggest that there will not be a 4.0 upgrade available for HTC VISION. Need I remind you all that there was an official upgrade to Android 2.2 for HTC SAPPHIRE/MAGIC32B made almost exactly ONE YEAR AGO? Yes, approximately the exact same time that HTC VISION was initially made available.
Click to expand...
Click to collapse
That was a long time ago. Now, forget it. They already gave up one update. They wont give us another.
Besides HTC is problably planning a new version of Sense for Ice Cream Sandwich.
killj0y said:
Haven't heard anything amazing about ICS so far wish I had though. Any solid awesome rumors about improvements or features?
Click to expand...
Click to collapse
Nothing. There is nothing confirmed for Ice Cream Sandwich at all. Google has had it tightly wrapped up.
The only thing we do know that it is Android 4.0
Besides that:
Facial recognition features, new APIs to reduce development fragmentation, a unification of phone and tablet UIs and its APIs.
Nothing else is confirmed with sources beside it.
Hey,
I'm sure you've seen Beezy's (on AndroidCentral) and DrewGaren's work on a stable ICS port for the Nexus S. Beezy's original ROM for the Nexus S 4G originally comes from a leak-of-sorts of ICS Build 13 (that's the one that was on that Nexus S off eBay a month ago that was all over the Net, Build 14/15 is the final version that's hitting with the Galaxy Nexus), and DrewGaren worked on making it all compatible with the Nexus S 3G and pulling in more newer UI features from the SDK. It seems to be VERY stable as well.
Here's the link to DrewGaren's site: http://drewgaren.com/DrewGaren.com/ICS/ICS.html
And there's also a thread on the Nexus S version: http://forum.xda-developers.com/showthread.php?t=1313337
Current version is Beta 4, Beta 5 should be out this weekend, and he claims it's stable enough to be a daily ROM... He's also working on a SDK port for the Nexus S and the Nexus One.
So, the question is, are any of the HD2 devs willing to port this? If it's that stable, it will be a brilliant thing to use on our HD2s until source hits just after Nov 17 (that's when the G-Nex is out in the UK at least, according to Amazon.co.uk) I'm actually impressed how they got a stable (-ish) port out for the Nexus S!
it's here already.. not that perfect but at least you can feel them already before the official release..
http://forum.xda-developers.com/showpost.php?p=18745118&postcount=80
JeremyGuan said:
it's here already.. not that perfect but at least you can feel them already before the official release..
http://forum.xda-developers.com/showpost.php?p=18745118&postcount=80
Click to expand...
Click to collapse
Thanks, so is that basically a port of the We Scream For Ice Cream ROM, because I can't really work out from the posts on that thread if it is...
antovolk said:
Thanks, so is that basically a port of the We Scream For Ice Cream ROM, because I can't really work out from the posts on that thread if it is...
Click to expand...
Click to collapse
Nope, this is a port of the Android SDK.
Nigeldg said:
Nope, this is a port of the Android SDK.
Click to expand...
Click to collapse
Saw that, thanks! I'm just hoping that they can use this ROM to work off for a stable HD2 port...
I'm sure it's coming we just have to be patient.
antovolk said:
Hey,
I'm sure you've seen Beezy's (on AndroidCentral) and DrewGaren's work on a stable ICS port for the Nexus S. Beezy's original ROM for the Nexus S 4G originally comes from a leak-of-sorts of ICS Build 13 (that's the one that was on that Nexus S off eBay a month ago that was all over the Net, Build 14/15 is the final version that's hitting with the Galaxy Nexus), and DrewGaren worked on making it all compatible with the Nexus S 3G and pulling in more newer UI features from the SDK. It seems to be VERY stable as well.
Here's the link to DrewGaren's site: http://drewgaren.com/DrewGaren.com/ICS/ICS.html
And there's also a thread on the Nexus S version: http://forum.xda-developers.com/showthread.php?t=1313337
Current version is Beta 4, Beta 5 should be out this weekend, and he claims it's stable enough to be a daily ROM... He's also working on a SDK port for the Nexus S and the Nexus One.
So, the question is, are any of the HD2 devs willing to port this? If it's that stable, it will be a brilliant thing to use on our HD2s until source hits just after Nov 17 (that's when the G-Nex is out in the UK at least, according to Amazon.co.uk) I'm actually impressed how they got a stable (-ish) port out for the Nexus S!
Click to expand...
Click to collapse
Tytung is like the Master when it comes to the Nexus for the HD2. So if the Nexus has a stable enough rom to be use every day I'm sure the HD2 will have it. It will complete the collection. Froyo, Gingerbread and Ice Cream Sandwich.
HD2 never had Donut/Cupcake?
daedric said:
HD2 never had Donut/Cupcake?
Click to expand...
Click to collapse
Why are you going back in time?
Sent from my HD2 using XDA App
venky80 said:
Why are you going back in time?
Sent from my HD2 using XDA App
Click to expand...
Click to collapse
I'm not... just asking
Actually... i'm curious if the HD2 ever had anything bellow 2.2...
if nexus 1 cant run ICW, i doubt we can.. hoping to get a try of ICW before deciding if i should get the galaxy nexus as my next phone after hd2..
fi3ry_icy said:
if nexus 1 cant run ICW, i doubt we can.. hoping to get a try of ICW before deciding if i should get the galaxy nexus as my next phone after hd2..
Click to expand...
Click to collapse
I'm going to disagree with you here, I think you're over looking one big thing. The HD2 wasn't suppose to run Android period, now it does. And... We have a lot of different versions now, like Sense 3.5. If memory serves me, our awesome phone wasn't suppose to run that cause it's for dual core phones, but it does and now we have a graphic's fix for it that smooths everything out. It's just a matter of time and how determined people/devs are.
If someone feels the need to correct me, please do so.
fi3ry_icy said:
if nexus 1 cant run ICW, i doubt we can.. hoping to get a try of ICW before deciding if i should get the galaxy nexus as my next phone after hd2..
Click to expand...
Click to collapse
dermann said:
I'm going to disagree with you here, I think you're over looking one big thing. The HD2 wasn't suppose to run Android period, now it does. And... We have a lot of different versions now, like Sense 3.5. If memory serves me, our awesome phone wasn't suppose to run that cause it's for dual core phones, but it does and now we have a graphic's fix for it that smooths everything out. It's just a matter of time and how determined people/devs are.
If someone feels the need to correct me, please do so.
Click to expand...
Click to collapse
He said IF. And those suspitions come from a google-employee-wannabe that has been spreading FUD long before.
The nexus is more than capable of running ICS, what MIGHT happen, is Google not releasing it officially.
As to the HD2... and the Diamond, and the Fuse, and the Blackcomb... and the Rhodium... and the Vogue... and the Kaiser... and the Polaris... None of them was meant to run Android.
I can't speak for all those devices, i only have a HD2 and a Kaiser... and both of them have a amazing support. On the Kaiser at we're only missing a better power manegement, and camera auto focus. The rest, works as it should.
Kaiser came with WM6.0... it got 6.1 officially..... it got 6.5 unofficially... it got Android unoficially... Ubuntu...
If we're all going to "Don't think about it... the [insert device name here] was not meant to run [insert os here]", XDA would not exist.
Besides... the "it's not possible" or the "it's not going to work" idea... is really really Apple'ish. And they got android on the 3g or 3gs IIRC
daedric said:
He said IF. And those suspitions come from a google-employee-wannabe that has been spreading FUD long before.
The nexus is more than capable of running ICS, what MIGHT happen, is Google not releasing it officially.
As to the HD2... and the Diamond, and the Fuse, and the Blackcomb... and the Rhodium... and the Vogue... and the Kaiser... and the Polaris... None of them was meant to run Android.
I can't speak for all those devices, i only have a HD2 and a Kaiser... and both of them have a amazing support. On the Kaiser at we're only missing a better power manegement, and camera auto focus. The rest, works as it should.
Kaiser came with WM6.0... it got 6.1 officially..... it got 6.5 unofficially... it got Android unoficially... Ubuntu...
If we're all going to "Don't think about it... the [insert device name here] was not meant to run [insert os here]", XDA would not exist.
Besides... the "it's not possible" or the "it's not going to work" idea... is really really Apple'ish. And they got android on the 3g or 3gs IIRC
Click to expand...
Click to collapse
This was the point I was trying to make, but you have done it far better than me.
Sent from my Android HD2 using XDA Premium App
Alright guys...lets face it. Our HD2 will definitely run ICS and even Jelly Bean...its just a matter of how fast and stable it will be compared to the amzingly stable and speedy 2.3 builds we have now. Also, its also a matter of time till CM9 hits ICS...Hope Google releases the AOSP code soon!...
uhm..? click me!
*roll eyes*
fi3ry_icy said:
if nexus 1 cant run ICW, i doubt we can.. hoping to get a try of ICW before deciding if i should get the galaxy nexus as my next phone after hd2..
Click to expand...
Click to collapse
Who said Nexus 1 can't run ICS? I'm sure it can. All I've heard is that it will not get an official update to ICS. Screw the official update. This is XDA and everything is possible.
Alot of sources are now saying the source code for ics is being released on the 17th, So not long to wait now!
tsddave said:
Alot of sources are now saying the source code for ics is being released on the 17th, So not long to wait now!
Click to expand...
Click to collapse
Looks like the sources were off a couple of days
Now the waiting to see who, if anyone, is going to work on a ICS rom - and if it will be better then what we have now!
hi all the awesome developers
do you think anyone will manage to get a working SDK port on our device?
and a question: if HTC wont release a kernel for JB for our device, we will get stuck without camera or we could use the ICS kernel?
thanks, and good luck at porting
DubelBoom said:
hi all the awesome developers
do you think anyone will manage to get a working SDK port on our device?
and a question: if HTC wont release a kernel for JB for our device, we will get stuck without camera or we could use the ICS kernel?
thanks, and good luck at porting
Click to expand...
Click to collapse
I'm betting that AOSP ROMs should be able to be ported with just an ICS kernel, much of 4.1 is UI improvements rather than deep changes like 4.0.
DubelBoom said:
hi all the awesome developers
do you think anyone will manage to get a working SDK port on our device?
and a question: if HTC wont release a kernel for JB for our device, we will get stuck without camera or we could use the ICS kernel?
thanks, and good luck at porting
Click to expand...
Click to collapse
Most likely not. There are many under the hood changes that will not work without the proper source but to be honest. Why in such a rush, The ICS source is still a few months away
zelendel said:
Most likely not. There are many under the hood changes that will not work without the proper source but to be honest. Why in such a rush, The ICS source is still a few months away
Click to expand...
Click to collapse
4.0 and 4.1 is totally different from 2.3 to 4.0 so you're completely wrong here.
The answer is. It is possible but someone needs to do it and most developers have moved on.
gkillerx said:
4.0 and 4.1 is totally different from 2.3 to 4.0 so you're completely wrong here.
The answer is. It is possible but someone needs to do it and most developers have moved on.
Click to expand...
Click to collapse
We will see. The notification bar alone will require massive work. Not to mention the changes they added to the kernel to support the tegra closed source drivers. So we will see what happens when the nexus gets the update.
Not to mention few will use the sdk to make a rom
Sent for a corner cell in Arkhum
so, there is a fully working rom for the galaxy nexus.
how will be our hero and port it?
http://forum.xda-developers.com/showthread.php?t=1738197
aaand everyone gave up on ics cuz they saw the next item. did we get all the apple users to buy android phones or something?
btw porting from nexus is not gonna happen. jb is quite a ways off from dhd if at all. starting to push the limits of this old phone. and personally id rather have a perfect working ics coming soon than start up with another flakey and nothing really working alpha again.
Darunion said:
aaand everyone gave up on ics cuz they saw the next item. did we get all the apple users to buy android phones or something?
btw porting from nexus is not gonna happen. jb is quite a ways off from dhd if at all. starting to push the limits of this old phone. and personally id rather have a perfect working ics coming soon than start up with another flakey and nothing really working alpha again.
Click to expand...
Click to collapse
we will have an official fully working ICS in a few weeks, and I think the AOSP ICS roms are good enough for daily use, so its just the right time to start working on JB!
It says here ........http://www.androidauthority.com/galaxy-s3-jelly-bean-update-details-samsung-ram-98158/ ......that JB will be rolled out to 3 year old devices, some by July, and one of these is the Nexus S. So if the Nexus S will be capable of running JB we might even be lucky enough to see an official release for our DHD's by the end of the year maybe!!?? Atleast should get a decent port!! Looks more promising to see some Jelly Bean goodness than I first thought anyway!!
spikey001 said:
It says here ........http://www.androidauthority.com/galaxy-s3-jelly-bean-update-details-samsung-ram-98158/.......that JB will be rolled out to 3 year old devices, some by July, and one of these is the Nexus S. So if the Nexus S will be capable of running JB we might even be lucky enough to see an official release for our DHD's by the end of the year maybe!!?? Atleast should get a decent port!! Looks more promising to see some Jelly Bean goodness than I first thought anyway!!
Click to expand...
Click to collapse
remember. ICS was released mid october, and we still dont have official yet :/
True, but ICS was a major change to Gingerbread whereas JB is supposed to be an incremental upgrade, so maybe if we do get it officially it will be a bit quicker getting to us than ICS!!?? Can always hope
LC said he is waiting for source, and then he will build a rom.
he also said JB is a small update to the source, so it wont be a problem to build a working rom. (or at least this is how I read it XD)
Our DHDs are due an official ICS rom in the coming weeks. Once this happens, surely it won't take long to get the camera fully working in ICS and JB update should merely be incremental. I'm not a dev though, so could be wrong.
I did the jellybean sdk port for iconia a500 and I happen to have a desire hd in my pocket maybe I'll mess with it
randomblame said:
I did the jellybean sdk port for iconia a500 and I happen to have a desire hd in my pocket maybe I'll mess with it
Click to expand...
Click to collapse
You would be loved by the entire Desire HD community please DO!!!!! ))
it's booting
got past the gralloc issues and it showed the bootanimation and now the android is upgrading screen. May not look quite right I'm using software rendering
randomblame said:
it's booting
got past the gralloc issues and it showed the bootanimation and now the android is upgrading screen. May not look quite right I'm using software rendering
Click to expand...
Click to collapse
LOL, already?
it's not hard...
still got a few issues preventing boot to homescreen tracking them down.
randomblame said:
it's not hard...
still got a few issues preventing boot to homescreen tracking them down.
Click to expand...
Click to collapse
How is the speed compared to AOSP ICS?
Sent from the Going Merry
Wow, your good
If you debug, do you any good sign for the camera?