Question about NoDo - HD2 Windows Phone 7 Q&A, Help & Troubleshooting an

Hi,
when is the release of the NoDo-ROM for the HD2-WP7 ?
Will it takes much longer ?

Unless I slept through it, I don't think NoDo has been officially released for 'proper' WP7 devices, so I wouldn't look for it any time soon.
That said, a leaked build has been in the hands of XDA-ers for a few weeks now and at least one developer has been working to make it work on the HD2 - there is a thread about it in the ROMs forum.It's far from easy though, so again, don't expect anything too soon.
Very happy to be proved wrong though...!

actually it has been released for all windows phone 7 devices as of today so developers can now use the official roms to cook something up?

It's being rolled out in phases, begining today. Hasn't hit most devices from what I've read/heard.

I can obviously claim the credit for shaming MS into finally releasing NoDo then...
I still wouldn't expect anything for the HD2 too quickly, there seem to be a few technical challenges to overcome.
Having been proved wrong once today already I'll happily be proved wrong again though.

Related

Finally: Android 2.2 introduced on Google I/O

Look it up:
http://www.youtube.com/watch?v=yAZYSVr2Bhc&feature=player_embedded
http://developer.android.com/index.html
We should focus on developping the 2.2 ROM when the source will be ready and leave 2.1 behind!!!
the sdk is out. Does anyone know when the source is going to be available to start compiling
ohh yeeah !
Hope Android 2.2 come fast on our tattoo.
As a former Windows Mobile fan I made the switch to Android because it looked like the way forward due to the amount of interest it had generated.
I wouldnt hold my breath for Android 2.1 never mind 2.2. HTC are too concerned with making money from releasing new handsets to worry about upgrading old ones. I have never known an OS to be so quickly discarded for a new version, with no update for older ones. At least Windows Mobile has pretty contant update (some were quite buggy, but at least they were there).
Hats off to the dev's who are trying to get it working on their own. I fear they are going to be our only hope with an upgrade.
I've never wanted to be proved wrong as much...................
I read on the German news that HTC will update all their Smartphones they released in 2010 (Droid Incredible, Desire, etc.)!!!! Since our Tattoo is 2009 we can forget getting any support from them. We have to support our devs to get decent results in ROM development...:/
It's true, the chance that the Tattoo will get a Froyo update is practically unexistent. It isn't even confirmed for all 2010 phones.
Source: engadget.com/2010/05/21/htc-most-phones-launched-in-2010-will-get-android-2-2/
I'm still hoping that HTC will release a 2.1 update for the Tattoo somewhere in June. If they don't do it in June, they never will.

[Q] Question

I've been installing Froyo Roms coutesy of FusionRom and Froydvillain makers for a while now on my Hero. It's now time for an upgrade...
I know that Android 3.0 is coming "soon" and will supposedly be released this year - maybe with next couple of months but info is very thin on the ground.
Wondering if anyone knows if Android 3.0 devices will be released this year or is it just the Software that will be released and announced?
I'm holding out upgrading my phone and waiting for Android 3.0 but the most compelling option out at the moment is the Samsung Galaxy S. Anyone think Android 3.0 will be available on the Galaxy S or is it worth waiting until later this year to see what new hotness gets released?
I know there's not much info out there about Android 3.0 but I'm essentially asking if it's worth waiting or not?
Could be waiting for 4 months or more, can you handle that? Having said that Google are well known for just up and releasing stuff without much build up so it could be sooner than expected... personally I don't think it will be til early 2011 for 3.0 phones to be released.
btdag said:
Could be waiting for 4 months or more, can you handle that? Having said that Google are well known for just up and releasing stuff without much build up so it could be sooner than expected... personally I don't think it will be til early 2011 for 3.0 phones to be released.
Click to expand...
Click to collapse
Really? Early 2011? Damn.... I was convinced that 3.0 would be out *with* phones by the end of this year?! I can't really handle 4 months or more because my Hero is so damn slow and unstable. I love and appreciate the custom ROMs for it from the good folks at XDA but I need mo speed!
Thanks for the reply.... Only question now is finding out if the Galaxy S will get the custom ROM love that my Hero got or if I should wait for a HTC of similar (or better) spec.... I think I'm going to go for the Galaxy S because I could be waiting forever otherwise and my phone is basically a pain in the ass. I'll have a look at what's going on in the Galaxy S dev forum....
Bear in mind anything on this subject is speculation. I don't have any insider knowledge, its just my guesstimate.
btdag said:
Bear in mind anything on this subject is speculation. I don't have any insider knowledge, its just my guesstimate.
Click to expand...
Click to collapse
I appreciate that. Thing is.... What happens with Android releases usually? What's the pattern? Did 2.0 come out as software after an announcement and then a good while later the phones trickeld out? How long between the announcement and the release of SDK/dev tools etc and the the actual availablitlity of phones? I know very little is know about 3.0 - but does anyone know if it's confirmed that the *software* will be revealed/released by the end of this year or something else?
Is there a better place to ask this?
Cheers
I have heard speculation Android 3 will be for the tablets.
So if you want it, hold off on buying anything. Remember, dont buy because of what they promise. HTC promised 2.0 and 2.1 for AGES before releasing it. Custom ROMs were possible as there were leaks, but without leaks, you're essentially stuffed.
pulser_g2 said:
I have heard speculation Android 3 will be for the tablets.
So if you want it, hold off on buying anything. Remember, dont buy because of what they promise. HTC promised 2.0 and 2.1 for AGES before releasing it. Custom ROMs were possible as there were leaks, but without leaks, you're essentially stuffed.
Click to expand...
Click to collapse
I never knew that leaks make custom Roms possible...There are already custom Roms on XDA for the Galaxy S as far as I can tell. Forgive my ignorance but is it the case that Custom ROMs can only be developed from leaked official ROMs (for drivers etc)? Or can custom ROMs be developed simply from android sources? i.e. Because the Galaxy S is one of only a few android handsets from Samsung am I right in thinking that it's therefore much more difficult to, say, port Froyo to the Samsung Galaxy S unless there is an official version out there somewhere from Samgung themselves?
I LOVED messing about with new ROMs on my Hero and am currently rocking ForydVillain which is great - but the cracks in the Hero are starting to show - it's slow. In terms of ROM development - are HTC devices much more likely to get custom ROMs than Samsung phones? I don't know of any upcoming HTC handsets that rival the Samsung Galaxy S......yet!
It's such a pain because there are so many variables with Android, Handsets etc.... :-s
alsheron said:
I never knew that leaks make custom Roms possible...There are already custom Roms on XDA for the Galaxy S as far as I can tell. Forgive my ignorance but is it the case that Custom ROMs can only be developed from leaked official ROMs (for drivers etc)? Or can custom ROMs be developed simply from android sources? i.e. Because the Galaxy S is one of only a few android handsets from Samsung am I right in thinking that it's therefore much more difficult to, say, port Froyo to the Samsung Galaxy S unless there is an official version out there somewhere from Samgung themselves?
I LOVED messing about with new ROMs on my Hero and am currently rocking ForydVillain which is great - but the cracks in the Hero are starting to show - it's slow. In terms of ROM development - are HTC devices much more likely to get custom ROMs than Samsung phones? I don't know of any upcoming HTC handsets that rival the Samsung Galaxy S......yet!
It's such a pain because there are so many variables with Android, Handsets etc.... :-s
Click to expand...
Click to collapse
Hold on, you've got confused here, as I wasn't pretty clear about what I was saying. You don't need a leak to make a ROM, but a leak lets you do it before official release. What I'm saying is that there's no guarantee that HTC or samsung or motorola or whoever will release Android 3 in any expedient time. HTC took forever to bring us 2.1, and the only way we managed to get it running BEFORE official release (which was June), was to use custom ROMs based on a leak.
Without that leak, we would likely have been much further back in making ROMs, and might not have managed till the release.
You can dev from a final release just fine, but leaks are needed to do so before the ROM release.
As for building from sources, you can do so, if there's a vendor overlay available. This is how FroydVillain is built.
XDA specialised in HTC devices since 2002/2003, but is now introducing stuff like Samsung devices. I don't know how many "real" devs are on the Samsung, but I think you'll have less custom ROMs, at least initially, until a development community builds up.
pulser_g2 said:
Hold on, you've got confused here, as I wasn't pretty clear about what I was saying. You don't need a leak to make a ROM, but a leak lets you do it before official release. What I'm saying is that there's no guarantee that HTC or samsung or motorola or whoever will release Android 3 in any expedient time. HTC took forever to bring us 2.1, and the only way we managed to get it running BEFORE official release (which was June), was to use custom ROMs based on a leak.
Without that leak, we would likely have been much further back in making ROMs, and might not have managed till the release.
You can dev from a final release just fine, but leaks are needed to do so before the ROM release.
As for building from sources, you can do so, if there's a vendor overlay available. This is how FroydVillain is built.
XDA specialised in HTC devices since 2002/2003, but is now introducing stuff like Samsung devices. I don't know how many "real" devs are on the Samsung, but I think you'll have less custom ROMs, at least initially, until a development community builds up.
Click to expand...
Click to collapse
Thanks for all the info - appreciate the detail and effort and maybe I need to get out more but I find it all fascinating
By the way - Somehow I've been thinking all day - utterly convinced - that 2011 is a whole year (12 months) from now instead of just a few months from now. I even called Orange to find out when I could cancel my contract. These years are flying by.... Maybe I'm getting old... Consequently - maybe I'll hold out a few more months for 3.0...
FroydVillain is as good as it gets on the Hero at the mo and it can only get better(!)

So I talked to T-Mo Rep

Today, I kept getting random messages from random numbers, so I called in to block, the rep also had a vibrant. So she was like "So... how do you like the vibrant?"
I'm all like "It's sexy"
But it took her so long to solve my problems, so I asked about random stuff like "Do you know when Froyo is coming out?"
She was a pretty "SMART TECH" you don't see those much on help lines now do you?
She replies: Let me check on that for you
and then she came back on and said "it won't be anytime soon, because if it is anytime soon, the tech supports usually knows weeks or months beforehand, but right now, it says 'to be determined'"
SO, do you guys it'll take as long as the rep said?
Unfortunately, this still fell into the same "He Said She Said" category, until we get an official statement, it's all moot. She may be smart but she is still a rep and I doubt she will have access to OTA information. She most likely turned around and asked her best friend/co-worker who is a tech, and he replied that he didn't know anything, and she passes that onto you.
I think she's right. We already know that froyo would come by the end of the year according to the galaxy s twitter. I expect it to come around December 29. Am I so pessimistic?
ori2 said:
I think she's right. We already know that froyo would come by the end of the year according to the galaxy s twitter. I expect it to come around December 29. Am I so pessimistic?
Click to expand...
Click to collapse
No, I believe you are pretty optimistic. End of December...well..
same here. I read the same thing in a tech online magazine.. they actually said 2011 but no precise date..
Im running the unofficial TMO froyo posted in this forum though and I like it
Cheers
Personally, I think Samsung should just give up and hand over the kernel source, maybe keep some respect.
The Unoffical Official T-MO Froyo ROM is in the Development section. If that is actually the real thing (and I completely believe it is) I don't see what the delay is for them to just release it.
Even when it does come out, I know for myself that I will keep a custom ROM. Why have stock when you can rock!
I think the point for all of us that are running one of the leaked 2.2 roms is that an official release will have more of the bugs ironed out and it will help with some of the compatibility issues. I for one have tried all flavors and each has a quirk or two. The good thing is that when 2.2 finally drops officially the devs will have almost perfected their roms and it will be easier to implement any changes made by Tmobile.
Sent from my SGH-T959 using XDA App
I agree with the previous post. I think Samsung leaked the ROM so that the devs here could get their hands on it and make fixes that they then can implement into the official ROM.
So it wouldn't be so embarrasing on Samsung's part? x) Something big like a software update isn't too "easily" leaked. So I do sort of have to agree too.

Gingerbread on Verizon ???? LOOK HERE

For those of you wondering what phones will and will not get Gingerbread, or the tards (or just diehard wishful thinkers) that think Verizon will just skip right over FroYo and go to Gingerbread, this is an official quote from Verizon:
"Google's just-announced Gingerbread software is generating buzz in the media.
Initially, it is not available on the Verizon Wireless lineup of Android phones.
BUT ... we're working with Google as they release source code for device manufacturers to begin integration. We are also assessing which devices will get Gingerbread within the coming months.
Stay tuned - more information will be available soon."
So that means, they won't even begin ASSESSING what phones receive the updates for MONTHS. Not days, not weeks, MONTHS. So those hoping to see Gingerbread anytime soon, well, sorry to burst your bubble, but its not happening. Those thinking FroYo was delayed to bake its bug fixes into Ginger, well, they'd have to delay it for months. Lets hope this is not the case....
Don't ask where I got the quote from....'tis not your concern
No
Sent from my SCH-I500 using XDA App
It could also mean be interpreted as they are assessing the devices now to have the update(s) rolled out in the coming months. Either way, I say end of March would be the soonest any device would see an official update, likely going to be over half-way through the year with LTE devices being released before most have Gingerbread though.
imnuts said:
It could also mean be interpreted as they are assessing the devices now to have the update(s) rolled out in the coming months. Either way, I say end of March would be the soonest any device would see an official update, likely going to be over half-way through the year with LTE devices being released before most have Gingerbread though.
Click to expand...
Click to collapse
Assess how ???? There is no source code to work with, the OEM's have not released Gingerbread builds as Googlele hasn't dropped any into AOSP yet (correct me if I'm wrong), so how would you like Samsung or Motorola to like working on builds when they don't have the source code ???? And even if they did, they won't bother working on the next build UNTIL a carrier requests for them to. They don't just start devoting resources to developing a build that may never be released....
This is unfortunately just again, hopeful wishing and you trying to justify accordingly. I don't know why I bother
I promise you, you won't see any Verizon devices with official Gingerbread builds until April/May at the earliest. They decide what phones are going to have it, then they turn it and a bug fix list over to the OEM, and they will wait for builds. Then, they get builds and start testing, which can take another few months.
At least you're not still hoping they'll skip over FroYo and straight to this....
Who really cares about gingerbread anyway. I'm very satisfied with DJ05 update, roms/kernals/themes. I can now wait patiently for froyo and... not even concern myself with when/where gingerbread will be released.
I never said they were skipping Froyo
I'm just saying there are two ways you could read their statement. A better way to word it in the manner that you are stating it would be something like "In the coming months, we will be assessing which devices will get Gingerbread".
To me, the way it is worded means more that they put their devices that are out in a line and pick which they will update and which they won't, then put a timeline on when they'd like to see the updates start coming.
To say that OEMs don't have code for Gingerbread right now, especially Samsung, seems a little naive really. We may not have source code, but I can't imagine Google not sharing it with OEM partners so that they can start working with it.
Truthfully, I couldn't care less when the update arrives as I'll probably wait to see what the developers can do with it before updating. But this doesn't say anything about when any device will receive the update and what devices won't get it. It just says that we have a few months before we are likely to see it in any official form, and I don't think anyone was expecting it any sooner, especially from Big Red.
imnuts said:
I never said they were skipping Froyo
I'm just saying there are two ways you could read their statement. A better way to word it in the manner that you are stating it would be something like "In the coming months, we will be assessing which devices will get Gingerbread".
To me, the way it is worded means more that they put their devices that are out in a line and pick which they will update and which they won't, then put a timeline on when they'd like to see the updates start coming.
To say that OEMs don't have code for Gingerbread right now, especially Samsung, seems a little naive really. We may not have source code, but I can't imagine Google not sharing it with OEM partners so that they can start working with it.
Truthfully, I couldn't care less when the update arrives as I'll probably wait to see what the developers can do with it before updating. But this doesn't say anything about when any device will receive the update and what devices won't get it. It just says that we have a few months before we are likely to see it in any official form, and I don't think anyone was expecting it any sooner, especially from Big Red.
Click to expand...
Click to collapse
Samsung has code obviously, without it, they couldn't have built the Nexus S. And I doubt Google builds the "Nexus" software because of all the little nuances of the code interacting with drivers and so forth (RIL ring a bell????), but I could be wrong, I don't work for either Google or Samsung.
I doubt the other OEM's have any builds running yet, as evidenced by the very first reference to builds, where they say that they are working with OEM's AS GOOGLE releases source code for them to integrate into their phones, but people can take it for what they wish.
I just put the quote out there verbatim. Do with it what you will.
mexiken said:
Assess how ???? There is no source code to work with, the OEM's have not released Gingerbread builds as Googlele hasn't dropped any into AOSP yet (correct me if I'm wrong), so how would you like Samsung or Motorola to like working on builds when they don't have the source code ???? And even if they did, they won't bother working on the next build UNTIL a carrier requests for them to. They don't just start devoting resources to developing a build that may never be released....
This is unfortunately just again, hopeful wishing and you trying to justify accordingly. I don't know why I bother
I promise you, you won't see any Verizon devices with official Gingerbread builds until April/May at the earliest. They decide what phones are going to have it, then they turn it and a bug fix list over to the OEM, and they will wait for builds. Then, they get builds and start testing, which can take another few months.
At least you're not still hoping they'll skip over FroYo and straight to this....
Click to expand...
Click to collapse
Actually I don't know how many times this has been said. Google releases their OS source not so long after their press release. It is the OEMs who have to release their kernel for us to develop anything. We've had 2.3 code for awhile now but we don't have kernel. They just released Nexus One kernel like yesterday so they'll get it pretty soon. People, Google's OS code and OEM kernel are two different things. We always had code source pretty fast at hand.
The fact that I'm super-skeptical of these unsourced-but-supposedly-from-Verizon quotes aside, I think imnuts has a point here.
imnuts said:
It could also mean be interpreted as they are assessing the devices now to have the update(s) rolled out in the coming months.
Click to expand...
Click to collapse
According to the rules of grammar, he's right. The order matters: since the clause "will get gingerbread within the coming months" comes after "which devices," not "we are assessing," it refers to the former. Had the quote been "We are also assessing within the coming months which devices will get Gingerbread," then it would be the other way around.
But that aside, even more importantly, saying a process will happen "within the coming months" doesn't mean that the process won't start for months. It means something is likely to be ongoing and could be done within one month, six months, or anything in between (or longer). Ultimately, that's the kind of wording people use when they want to remain intentionally vague, and we really can't read a timeline one way or the other from it. Especially when it comes to mobile carriers and software updates.
mexiken said:
There is no source code to work with, the OEM's have not released Gingerbread builds as Googlele hasn't dropped any into AOSP yet (correct me if I'm wrong), so how would you like Samsung or Motorola to like working on builds when they don't have the source code ????
Click to expand...
Click to collapse
Well, for starters, Samsung obviously has had the 2.3 source code for quite some time considering they have a Gingerbread phone coming out tomorrow. We also know Motorola has the 3.0 code seeing as how they're working on at least one already-functional Honeycomb device. The only one we can say definitely doesn't have 2.3 is LG, because they said so (though they also said 2.3 required a 1ghz processor in the same breath, which turned out to be a complete lie, so it's hard to trust them). But clearly, AOSP gets the code just a tad later than at least some OEMs do.

Update Signs?

First off let me say I Do Not intend for this to be another whine thread....
Just wanted to reach out and see if anyone has had any signs of an update. I recall from one of the previous now closed threads started one user mentioned the 5th as being a possible date. Though seemingly arbitrary date the 5th is here.
People chime in if you get the notification!
Nothing for me yet.
It probably won't come out until the new Google phones do. I know it's difficult for flashaholics, but be patient.
Now I'm waiting for the September security update for Marshmallow, maybe it will be late too. They seem to be in a huge work.
This thread is the best sign.
daimerion said:
First off let me say I Do Not intend for this to be another whine thread....
Just wanted to reach out and see if anyone has had any signs of an update. I recall from one of the previous now closed threads started one user mentioned the 5th as being a possible date. Though seemingly arbitrary date the 5th is here.
People chime in if you get the notification!
Click to expand...
Click to collapse
That's what intended mine to be, but it went south so fast! Lol no sign for me yet, I'm hoping maybe by tonight. It's REALLY behind said release date. Staying optimistic!
This is the only sign from Google I have seen.
Absolutely notting here. Not even the sept security update.
There will be a September in 2017,too
If I'm remembering the same post, a user speculated that the update would be tied to the September monthly security update. That seemed like pure speculation. I hope the updates are posted soon but I don't think today will be the day, since it is already the afternoon and a business holiday. Hope I'm wrong!
Hope it's soon.
theman22 said:
If I'm remembering the same post, a user speculated that the update would be tied to the September monthly security update. That seemed like pure speculation. I hope the updates are posted soon but I don't think today will be the day, since it is already the afternoon and a business holiday. Hope I'm wrong!
Click to expand...
Click to collapse
Maybe tomorrow then, I forgot it was a holiday. What gets me is how they got everyone all riled up that it was gonna be in August, and it's gonna be out at the same time haha
Yeah Im ready for the official build too, this NPD90G preview wants me to want more, or at least some minor fixes.
No updates.............there will be speculations.
No speculations.....probably updates.
From what I've heard Qualcomm needs to do some driver upgrades for full Android N Support. If that is the case, it would explain why Google hasn't released the update yet, they simply can't until Qualcomm delivers. I can imagine Qualcomm has their hands full at the moment with all the smartphone companies out their requesting driver updates to support Android N as well.
I don't have any references for this, as I read it in a post somewhere but don't remember where. Don't take my word for it. But of course it would be interesting if someone could confirm or deny this.
I don't expect the update any time soon, but at least the latest beta runs very smoothly on my device. Can't complain at the moment.
Thats what has confused me DP5 runs well so id have thought it was near release quality but I guess not with the update taking so long. As far as qualcomm surely google should be the highest priority for drivers/updates given that they build the entire base that all other android phones base off? So an N driver for a specific SoC should work for all devices using that SoC?
I'm pretty satisfied with the Uber N ROM as is.
What @onemandivision said is correct, driver updates are critical. It's not just the kernel and the android base.
I'm a little confused by the delay though since it is already clear that phones on chips older than snapdragon 800/801 won't get nougat (ie 65-70% of all android phones according to some surveys), so there should be very few drivers to update/fine tune? Am I wrong?
Sent from my Nexus 6 using XDA-Developers mobile app
september update , my s7 edge still has the july update , samsung are dam slow pushing updates , my nexus 6 has the latest dev update but hope oneday soon the real 7.0 comes out.
New Marshmallow Image up... (MOB31E)

Categories

Resources