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.
Related
I just read this and so I'm hoping we get Froyo soon too. Hopefully we will.
http://phandroid.com/2010/06/22/htc...-desire-and-legend-within-the-next-two-weeks/
Would be awesome if true but why in the world isn't the Evo mentioned
Vandam500 said:
Would be awesome if true but why in the world isn't the Evo mentioned
Click to expand...
Click to collapse
I don't know but I hope we get it.maybe that's why google is updating all their apps. Google maps is also getting a update.
Sent from my Sprint Evo
We should definitely be getting it on the EVO... the only question is how soon???
http://www.youtube.com/watch?v=IY3U2GXhz44
Correct me if I'm wrong but the Desire and Legend do not have Sense UI, which means it's a straightforward port.
If you've played with any of the 2.1 ROMs with JIT you would know that JIT does not work with Sense. Froyo - JIT = FAIL. Thus a froyo port for sense devices could be a little further away than you would hope.
Just wait for the evo kernel source to be released and we will have a complete badass froyo rom for evo, minus the sense (which I've learned to live without already.)
itmustbejj said:
Correct me if I'm wrong but the Desire and Legend do not have Sense UI, which means it's a straightforward port.
If you've played with any of the 2.1 ROMs with JIT you would know that JIT does not work with Sense. Froyo - JIT = FAIL. Thus a froyo port for sense devices could be a little further away than you would hope.
Just wait for the evo kernel source to be released and we will have a complete badass froyo rom for evo, minus the sense (which I've learned to live without already.)
Click to expand...
Click to collapse
Correction....the Desire and Legend do have the SenseUI. The Nexus is stock, Vanilla Android.
itmustbejj said:
Correct me if I'm wrong but the Desire and Legend do not have Sense UI, which means it's a straightforward port.
If you've played with any of the 2.1 ROMs with JIT you would know that JIT does not work with Sense. Froyo - JIT = FAIL. Thus a froyo port for sense devices could be a little further away than you would hope.
Just wait for the evo kernel source to be released and we will have a complete badass froyo rom for evo, minus the sense (which I've learned to live without already.)
Click to expand...
Click to collapse
Both Desire and Legend are running on Sense UI. The Only HTC (Android) device that I know that doesn't run on Sense is The Nexus One.
The key is the Desire and Legend aren't locked to carriers, and don't have to go through the US carrier dance whenever they want to release an update.
If you read the article and then jump to the Adobe announcement..."explicitly mentioned several devices that will be getting Android 2.2 sometime down the line to take advantage of Flash Mobile 10.1 (it will be heading out of beta and into a final release the moment Froyo is available). The Google Nexus One, HTC Desire, HTC EVO 4G, Motorola Droid/Milestone, and the HTC Droid Incredible are all of the obvious candidates they mentioned,"
My hunch is that we will see 2.2 drop with some fixes for things seen in the first release of the EVO (30 fps, screen capacitance, etc.). If that's true, we will see 2.2 sooner rather than later.
pixelpop said:
If you read the article and then jump to the Adobe announcement..."explicitly mentioned several devices that will be getting Android 2.2 sometime down the line to take advantage of Flash Mobile 10.1 (it will be heading out of beta and into a final release the moment Froyo is available). The Google Nexus One, HTC Desire, HTC EVO 4G, Motorola Droid/Milestone, and the HTC Droid Incredible are all of the obvious candidates they mentioned,"
My hunch is that we will see 2.2 drop with some fixes for things seen in the first release of the EVO (30 fps, screen capacitance, etc.). If that's true, we will see 2.2 sooner rather than later.
Click to expand...
Click to collapse
That would be a very beautiful thing if you are right. They would be killing multiple birds with one stone then. Almost seems to logical for htc and sprint though so i doubt this will be the case
Things needed for a fully working Froyo Build on the EVO
1 2.6.32 kernel source with drivers for the EVO. (Not Available)
2 Evo Vendor Files needed for Froyo source (Not Available)
3 Froyo Source
pixelpop said:
If you read the article and then jump to the Adobe announcement..."explicitly mentioned several devices that will be getting Android 2.2 sometime down the line to take advantage of Flash Mobile 10.1 (it will be heading out of beta and into a final release the moment Froyo is available). The Google Nexus One, HTC Desire, HTC EVO 4G, Motorola Droid/Milestone, and the HTC Droid Incredible are all of the obvious candidates they mentioned,"
My hunch is that we will see 2.2 drop with some fixes for things seen in the first release of the EVO (30 fps, screen capacitance, etc.). If that's true, we will see 2.2 sooner rather than later.
Click to expand...
Click to collapse
HTC has said that the 30fps issue is hardware related and will not be fixed, so if it somehow gets magically fixed the same time they push Froyo I will be ecstatic.
asrebel said:
HTC has said that the 30fps issue is hardware related and will not be fixed, so if it somehow gets magically fixed the same time they push Froyo I will be ecstatic.
Click to expand...
Click to collapse
If the LCD is running off of the MDDI interface, there is no way to fix it. MDDI 1.1 has a 30hz limitation. End of story.
Doesn't it stand to reason that HTC must at least wait for google to finish Froyo before HTC can release it? Perhaps HTC is able to begin designing their Sense UI while awaiting a final build of Froyo, but I doubt they'd release 2.2 for their devices based upon a beta-build of Froyo.
I certainly hope that we see an official HTC Froyo release asap, though once it's available I will wait to see what the XDA community is able to do to preserve root, and eagerly await some optimized ROMs based on an official release of Froyo.
In the meantime, I love my Evo and am enjoying it thoroughly. I just wish we'd get some 4G down here in the big-easy.
Battery issues aside, I picked up one of the chinese battery/charger bundles on ebay for $11 shipped. I don't mind carrying 2 spare (albeit, probably lower mAH) batteries for extended weekend excursions.
Vandam500 said:
Both Desire and Legend are running on Sense UI. The Only HTC (Android) device that I know that doesn't run on Sense is The Nexus One.
Click to expand...
Click to collapse
G1/Dream
MyTouch 3G/Sapphire/Magic/Ion/etc...
There are more than just the N1.
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.
Great advancements have been made with the HD2 over the course of the last 6/7 months none more so than us being able to have NAND Android on our phone and much credit and respect due to everyone involved.
I've noticed though over the last few months that Gingerbread with Sense seems to be all the rage, unfortunately I don't believe any great major progress has been made recently, I'm looking through and have flashed various gingersense builds but its the same problems with them all camcorder,graphic glitches, Wi-Fi trouble,etc etc seem to common reoccurring problems,I've no doubt in time that these issues will be resolved but it seems some people who are content to have a build that might only be say 80% complete on their phone just because it is gingersense as opposed to a build that is 100% stable and thats a bit baffling really, as I said no doubt these issues will in time be resolved but until then personally speaking ill just stick with my stable froyo build until I get my Samsung Galaxy S2.
Sent from my HTC HD2 using XDA App
.....and the point of this was?
MagikWorx said:
.....and the point of this was?
Click to expand...
Click to collapse
bit of a smart ass aren't you
The point being that im wondering why no real advancement has been made with gingersense builds, for months now the same issues are still there,im sure in time they will be resolved but to date they haven't been.
Cuz the source code was not released.
gingersense is the most godawful ****ing word I have ever heard. I hate hearing that word, even in my own head.
gingersense.............
!~!!!!!!!
I can do without sense roms personally, but I feel you, fully functional sense builds would be a dream, truly.
Kailkti said:
Cuz the source code was not released.
Click to expand...
Click to collapse
I wasn't aware of this, i knew that Google didn't release the source code for Honeycomb.
kypeth said:
gingersense is the most godawful ****ing word I have ever heard. I hate hearing that word, even in my own head.
gingersense.............
!~!!!!!!!
I can do without sense roms personally, but I feel you, fully functional sense builds would be a dream, truly.
Click to expand...
Click to collapse
BTW i didn't coin the phrase "gingersense" ive no idea who did i just read it on here.
Well google did release gingerbread's source code, but they don't handle the releasing of source code for phones'. The manufacturer's do.
MagikWorx said:
.....and the point of this was?
Click to expand...
Click to collapse
I agree. You never stated that you had a question in the OP. Just that you're staying with froyo with sense. Cool story, bro.
Sent from my HTC HD2 using XDA App
I have gingercyanomod (did i just make up a word too???) and i tell you pal, ginger is worth it in some perhaps little aspects! (nothing compared to cyanogen mods which i love above all)
all is working ok for me on Android 2.3.4 ...ok, i could do with native usb tethering (theres an app for that!) and true hd camera drivers but these are little things i can live without.
Better that than having to use windows mobile right?
As for sense builds etc, i dont see the point unless you are lucky enough to have bought the TMOUS HD2... every single sense build i tried on my EU HD2, regardless of overclocking, just runs laggy and annoyingly freezes all the time... sure i can have data and sync off and it will run smoother, but thats crap innit?
Using NAND Typhoon for HD2 3.3.2v MAGLDR (clk still has a few bugs imo)
I was looking around to see if the source code for gingersense had been released and I went to http://developer.HTC.com and the first thing on there is HTC Desire HD - GB MR - 2.6.35 kernel source code and when I downloaded it the file is called ace-2.6.35-gb-MR.tar. now I have no idea but isn't that what they need? Or is it there something else?
Sent from my HTC HD2 using XDA App
Well what the devs have right now is the sensation's build, atleast I think so. Haven't been in that forum in some time.
The devs are waiting for the Desire GB kernel source to be released...then well see some major leaps forward.
Oh and I'm happy with GINGERSENSE because minor graphic glitches don't bother me and I don't use camcorder. WiFi has no issues either for me.
The devs are waiting for the Desire GB kernel source to be released...then well see some major leaps forward.
Click to expand...
Click to collapse
well that is good to hear anyway.
Oh and I'm happy with GINGERSENSE because minor graphic glitches don't bother me and I don't use camcorder. WiFi has no issues either for me
Click to expand...
Click to collapse
each to their own my friend but a working camcorder is absolutely essential for me and every gingersense build ive tried has had some sort of issue with Wi-Fi so ill just keep the stable build i have.
GB 2.3.3/4 with CM7 runs so smoothly, couldnt change to a sense rom and lose all the smoothness
if ur waiting for anything
its htc to release the source code for their ginger sense and or a group of devs to write up some new drivers for the hd2 case alot of the driver arent compatible with the hd2
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)