Related
HTC Announced they are releasing a new version of the the touch cruise, what are your thoughts on this is this htc trying to recover from a bad software implementation or what, i think its unfair for them to bring out a new model to recover from it not every one can afford upgrading phones everytime a new one comes out.
You mean "Iolite"?
Here are many roms with the same specs (like footprints or M2D or Navipanel...).
So you can have a new phone without buying a new device!
Lord Meshadieme said:
HTC Announced they are releasing a new version of the the touch cruise, what are your thoughts on this is this htc trying to recover from a bad software implementation or what, i think its unfair for them to bring out a new model to recover from it not every one can afford upgrading phones everytime a new one comes out.
Click to expand...
Click to collapse
I am under the same impression too. HTC released new devices in Diamond family with distinctive names. I don't think they ran out of naming ideas . This is a clear indication (at least to me) that the original Cruise has some fundamental flaws. If it where to be firmware related a new ROM or some sort of SW upgrade could have that fixed. I am convinced that is HW related (i.e.: bad or compromised overall design; bad choice of components, etc.).
Some people here on this forum could argue that the design is similar with some other successful devices from the past. This is not completely true since we don't have full access to the internals of these designs.
Being able to load some non-official ROMs on our devices is not a real upgrade it is merely a change of user interface and a set of bugs/problems different from the original ROMs.
F
florinfr said:
I am under the same impression too. HTC released new devices in Diamond family with distinctive names. I don't think they ran out of naming ideas . This is a clear indication (at least to me) that the original Cruise has some fundamental flaws. If it where to be firmware related a new ROM or some sort of SW upgrade could have that fixed. I am convinced that is HW related (i.e.: bad or compromised overall design; bad choice of components, etc.).
Some people here on this forum could argue that the design is similar with some other successful devices from the past. This is not completely true since we don't have full access to the internals of these designs.
Being able to load some non-official ROMs on our devices is not a real upgrade it is merely a change of user interface and a set of bugs/problems different from the original ROMs.
F
Click to expand...
Click to collapse
This makes no sense. If HTC knew that the original Cruise had problems, why would they name a new device with the same name as the flawed one? When the original Cruise was released it was pretty flash from a hardware point of view - remember that was a couple of years ago now, so you really can't compare with current stuff. People seem to think that their devices will somehow manage to stay up to date with newer technology - which is impossible. For me, other than the video driver issue (which for me is really no issue at all) the Cruise works fine. If it didn't, I'd bite the bullet and simply replace it with a newer device, which by the way would probably be out of date 3 months after I buy it.
cr1960 said:
This makes no sense. If HTC knew that the original Cruise had problems, why would they name a new device with the same name as the flawed one? When the original Cruise was released it was pretty flash from a hardware point of view - remember that was a couple of years ago now, so you really can't compare with current stuff. People seem to think that their devices will somehow manage to stay up to date with newer technology - which is impossible. For me, other than the video driver issue (which for me is really no issue at all) the Cruise works fine. If it didn't, I'd bite the bullet and simply replace it with a newer device, which by the way would probably be out of date 3 months after I buy it.
Click to expand...
Click to collapse
I never implied, or thought for that matter, about my device staying up to date and competing on the same level with the newer devices.
The question was: Why not HTC Touch Cruise2 or something else? Why the newer device has exactly the same name? Oh yeah: they added the (09) description in order to avoid confusion and a heap of confused customer support.
One more thing:
On the device list on their site there is NO trace of the old Cruise but one can find the Tytn II which is an older device. One can ask himself way that is?
F
Upgrade ROM for HTC Touch Cruise 09
Nếu là các thành viên ở VN, có thể mang qua myPda 20 Trần Quốc Toản - www.myPda.com.vn,
Cheer !
Hello,
I would like to change the HTC Hero's firmware/ROM to match that of the HTC Magic's firmware/ROM. My phone is CDMA, but I'm hoping that somehow, someway it is possible to do this. My reason for wanting this is so that I can finally do mods, like Cyanogen, since the CDMA Hero isn't really that widely supported, yet.
Thanks in advance for any help,
Tyler
Any new ROM will have to be CDMA, you can't change that since it has to do with phone hardware.
I have been.trying to port over gsm roms forever and.with no luck. Theoretically its possible but I haven't the faintest idea how.
Well, then I guess I have to resort to my last and great question. Since I'm stuck with my Hero, unless I go T-Mobile, how long, do you guys suspect, that it will take for more support to role out, like there is for the Magic? I ask because I'm wanting to know rather, or not there is a lot of development happening for the Hero because I really want great functionality and mod availability. At this point, if the answer is "not a lot", I may just drop the Hero for the Magic.
Thanks again for answering my questions,
Tyler
thejedislayer said:
Well, then I guess I have to resort to my last and great question. Since I'm stuck with my Hero, unless I go T-Mobile, how long, do you guys suspect, that it will take for more support to role out, like there is for the Magic? I ask because I'm wanting to know rather, or not there is a lot of development happening for the Hero because I really want great functionality and mod availability. At this point, if the answer is "not a lot", I may just drop the Hero for the Magic.
Thanks again for answering my questions,
Tyler
Click to expand...
Click to collapse
So you're saying you're "STUCK" with a month and a half old phone, unless "more people start supporting it"? i.e. People spending their free time creating mods for the Hero, so that you can get it for free? And if people aren't going to do mods and features for free in the near future, then you're just going to get rid of your Hero and go to T-Mobile for the Magic because it has people who are dedicated to releasing software they dont get paid to spend time working on? Seems like a lot of complaining about something that is completely voluntary, nobody has to work on any mods and nobody has to support any device. If you want to drop your Hero, just do it already. Nobody wants you to keep using it, nobody is forcing you to keep using it. Just do it already, nobody cares to read threads like this.
Wow, you took what I said and totally blew it out of proportion. The reason I wanted to get Android was because I wanted to be able to do things, like root my Android device. I fully support developers in their endeavor to develop applications, mods, ROMS, etc for all Android devices on their time. I do not, however, sit here and feel that the best idea to do is to whine and cry about support for my Android device not yet being fully supported or embraced. I simply asked rather, or not heavy development was going to happen in the near future, so as to ascertain a good decision on rather I should switch. That way I could get the full and best support and benefit from my personal experience with Android. I am not a developer. I've only gotten into this, so I was simply curious as to how development was coming along for the Hero at this time, and rather it may have been a better idea to just switch. Sorry To Have Offended The Offended.
**EDIT**
And understandably, having reread what I wrote, I can understand how what I said may have come off as a little dickish; however, it was not my intention, nor was it my wanting to cause a conflict.
thejedislayer said:
Wow, you took what I said and totally blew it out of proportion. The reason I wanted to get Android was because I wanted to be able to do things, like root my Android device. I fully support developers in their endeavor to develop applications, mods, ROMS, etc for all Android devices on their time. I do not, however, sit here and feel that the best idea to do is to whine and cry about support for my Android device not yet being fully supported or embraced. I simply asked rather, or not heavy development was going to happen in the near future, so as to ascertain a good decision on rather I should switch. That way I could get the full and best support and benefit from my personal experience with Android. I am not a developer. I've only gotten into this, so I was simply curious as to how development was coming along for the Hero at this time, and rather it may have been a better idea to just switch. Sorry To Have Offended The Offended.
Click to expand...
Click to collapse
There are many threads with people making their own roms, and modifications are being made to the hero by various people. Heavy development like going to 1.6 or 2.0 will most likely not happen by any developer, but by HTC itself. Once they release a new version, people will make a new rooted ROM with all the changes. For a fairly new phone, it got rooted fairly quickly (within a month of being released or so). It hasn't even been rooted all that long yet. All of this information is available in various threads. In the end its your decision on if you can wait or not to receive updates. Bleeding edge isn't always the best choice for everybody. If you prefer bleeding edge, perhaps you did get the wrong phone because there will likely be much more activity with, say, the Droid. But as for apps, there should be tons and tons of more apps coming available for the android platform as time goes on. I just cant see why you would want to switch phones based on a really short time period of it being out, jumping ship because it hasn't been hailed and given 100% attention by tons of developers yet. Honestly, as more android phones are released, I think more people will start developing for them and the android community itself will continue to grow. There are still some 7 year old Casio devices that receive updates, if you can believe that.
In all honesty, I knew I was a little quick to jump the gun when I said rather, or not it was a good decision to move from the Hero to the Magic. Again, this is all really new to me. In my mind, my main concern was that because of the Hero's Sense UI, this would make it a lot harder for developers, like Cyanogen Mod, to keep the Hero up-to-date with the rest of the older Android devices. The Magic, seeing it being a lot more supported in just three short months since its debut, made more sense to me to possibly move to. As it had tons of development happening for it, and I simply wanted to be apart of the action.
wouldn't a 1.6 Rom work since it "supports CDMA" out of the box???
@ azfxstb
I took the liberty of looking around, and I ended up finding some links from HTC for 1.6 support. Link: http://developer.htc.com/google-io-device.html
According to the article, though, the next successive version relies on a previous version in order to update properly. In other words, in order to know I have full functionality and support, I would have to start from the beginning of the Magic's support and simply continue updating till I reach the newest update. I may be wrong, but if I'm not, then it may be something worthwhile considering, even if it's a hassle. Anyone have any thoughts about this method?
I'd say stick it out. The Sprint Hero hasn't even been out for 2 months and it is rooted and there are a couple of custom ROM's posted here. I've had my Hero for 2 weeks and have already tried numerous releases, and all have been very stable for me.
I'd love to see some of the improvements Cyanogen come over, and I'm sure they will eventually, but you have to remember how long of a time frame the Magic had to work with.
azfxstb said:
wouldn't a 1.6 Rom work since it "supports CDMA" out of the box???
Click to expand...
Click to collapse
We don't know that HTC's shoehorned CDMA support into 1.5 is compatible with the built-in CDMA support in 1.6. What that means is that there's a potential that even if we did get a 1.6 build on the phone, HTC's proprietary (i.e., not required to release source code for) software that sits between the Android framework and the linux kernel (which in turn talks to the hardware) might be speaking a different language that Android 1.6 can't understand. That's the problem with their hacked-together 1.5 build. Make note that I do not know this for certain, but it's certainly a possibility, and if that's the case, we'd have a broken phone until those HTC layers could be translated from hacked-1.5 to native-1.6.
That's why, as already stated above, those moves probably won't happen until HTC releases a 2.0 build (which means we might never see 1.6 run on this phone even after the 2.0 release, since we'll never have the HTC software that is written specifically for the 1.6 platform).
To break it down, the phone has 2 processors: ARM9 and ARM11. ARM9 runs the radio hardware, and the radio controls literally *everything* that makes this phone usable. Think of ARM9 like your computer's BIOS chip. Except in a very rare case of someone who really really wants to hack on their phone, the ARM9 will never be modified by us.
The ARM11 is the next layer, and that's what actually runs the OS, recovery images, etc. The ARM11 is able to communicate with the ARM9 using a series of two-way communication channels (shared memory) and hardware interrupts.
The linux kernel contains drivers that on one side talk to the ARM11 and other hardware in the phone, and then expose controls on the other side that allow the rest of the OS to work with those things (e.g., turn the screen on/off, register touches on the screen, play sounds, vibrate, make calls, etc).
For some things, that's enough to let Android take over and actually make use of some of those things (LCD, touchscreen, sound, ...). Still, there are other things that require intermediate controllers between the devices exposed by the kernel and Android. For example, "rild" is in charge of managing the modem as far as things like issuing commands to your carrier, getting online, telling the modem to make a call, finding out signal strength, etc. But HTC wrote their own ril that interacts with the modem -- and they aren't required (in fact, they're not allowed!) to release the source code for that, because a) it was developed using proprietary information given to them (under NDA no doubt) by Qualcomm, and/or b) it contains information that HTC themselves want to keep private, protecting their intellectual property, etc. There are several other userland libraries like that, which are NOT part of the kernel, and therefore are not required to be released as open source. Yet they are required for Android to work, as android will speak directly to those libraries, which translate the messages in order to communicate with the kernel, which communicates with the ARM11, which talks to the ARM9, which makes it happen.
The breakdown happens at the "android speaks to the libraries" step, because Android 1.5 speaks a certain language, and that's (potentially) different from the Android 1.6 language. Yes this phone is CDMA, and yes Android 1.6 has native support for CDMA... So, you say, putting Android 1.6 on the phone should "just work". But the HTC libraries that are on our phones are not designed for 1.6, they're designed for 1.5. And they're not even designed for the "standard" GSM 1.5, but for a "hacked" CDMA 1.5! If we put Android 1.6 on the phones, we could *try* to reuse the existing binary form of the HTC libraries, but if 1.5 and 1.6 talk different languages (most likely they do), the 1.5 version of the binary libraries are going to get confused and reject it. Then we're left with a 1.6 platform that can't talk to the 1.5 libraries, and we get major functionality meltdown. To be fair, it would be possible to write an additional translation layer that would convert the 1.6 messages into something that we "think" the 1.5 libraries will understand, but is it really worth the effort? (hint: it's not a small effort ) Then try doing the same with 2.0, and the potential for translation problems are even worse...
And not to mention, 2.0 also requires the 2.6.29 kernel, which (surprise, surprise), does not exist (for this phone) in the wild. We could theoretically get 1.6 running, since we already have a working 2.6.27 kernel (the phone shipped with it, and if we assume that the shipped kernel is "good enough", we can simply reuse it -- we already do that with the recovery image and even MoDaCo's rom). But as soon as we think about either modifying the kernel as it is, or god forbid, upgrading to 2.6.29, we hit a roadblock because we don't have the source code yet for the 2.6.27 kernel. Once that code is released, we could hypothetically port that support to 2.6.29. Or once HTC releases an Eclair build for this phone, it'll be guaranteed to have a ready-made 2.6.29 kernel buried inside, as well as the binary HTC libraries that are required for our phone. Until one of those two things happens (or, admittedly, someone reverse-engineers what's required... which quite frankly is not worth anyone's time considering we know that HTC *will* release both of those things eventually), Eclair is absolutely out of the question.
The short version (go ahead, admit it, you skipped to here even though I didn't put a "short version at the end" disclaimer at the top): 1.6 will absolutely require reverse-engineering the HTC libraries, just to get an already outdated (albeit still an upgrade) version of the OS on the phone -- not worth the effort. 2.0 will absolutely require reverse-engineering (both the kernel AND the binary libraries), just to get Eclair running on the phone maybe a couple weeks before HTC gives it to us on a silver platter -- And you're still likely to have a partially gimped phone at that point!
And the moral is: this **** is hard. HTC is already doing the work we need. HTC will make everything work "reasonably well". And they'll give it to us when they're done. Thus, no one *wants* to waste the effort doing it themselves. Ergo: we wait.
maejrep said:
We don't know that HTC's shoehorned CDMA support into 1.5 is compatible with the built-in CDMA support in 1.6. What that means is that there's a potential that even if we did get a 1.6 build on the phone, HTC's proprietary (i.e., not required to release source code for) software that sits between the Android framework and the linux kernel (which in turn talks to the hardware) might be speaking a different language that Android 1.6 can't understand. That's the problem with their hacked-together 1.5 build. Make note that I do not know this for certain, but it's certainly a possibility, and if that's the case, we'd have a broken phone until those HTC layers could be translated from hacked-1.5 to native-1.6.
That's why, as already stated above, those moves probably won't happen until HTC releases a 2.0 build (which means we might never see 1.6 run on this phone even after the 2.0 release, since we'll never have the HTC software that is written specifically for the 1.6 platform).
To break it down, the phone has 2 processors: ARM9 and ARM11. ARM9 runs the radio hardware, and the radio controls literally *everything* that makes this phone usable. Think of ARM9 like your computer's BIOS chip. Except in a very rare case of someone who really really wants to hack on their phone, the ARM9 will never be modified by us.
The ARM11 is the next layer, and that's what actually runs the OS, recovery images, etc. The ARM11 is able to communicate with the ARM9 using a series of two-way communication channels (shared memory) and hardware interrupts.
The linux kernel contains drivers that on one side talk to the ARM11 and other hardware in the phone, and then expose controls on the other side that allow the rest of the OS to work with those things (e.g., turn the screen on/off, register touches on the screen, play sounds, vibrate, make calls, etc).
For some things, that's enough to let Android take over and actually make use of some of those things (LCD, touchscreen, sound, ...). Still, there are other things that require intermediate controllers between the devices exposed by the kernel and Android. For example, "rild" is in charge of managing the modem as far as things like issuing commands to your carrier, getting online, telling the modem to make a call, finding out signal strength, etc. But HTC wrote their own ril that interacts with the modem -- and they aren't required (in fact, they're not allowed!) to release the source code for that, because a) it was developed using proprietary information given to them (under NDA no doubt) by Qualcomm, and/or b) it contains information that HTC themselves want to keep private, protecting their intellectual property, etc. There are several other userland libraries like that, which are NOT part of the kernel, and therefore are not required to be released as open source. Yet they are required for Android to work, as android will speak directly to those libraries, which translate the messages in order to communicate with the kernel, which communicates with the ARM11, which talks to the ARM9, which makes it happen.
The breakdown happens at the "android speaks to the libraries" step, because Android 1.5 speaks a certain language, and that's (potentially) different from the Android 1.6 language. Yes this phone is CDMA, and yes Android 1.6 has native support for CDMA... So, you say, putting Android 1.6 on the phone should "just work". But the HTC libraries that are on our phones are not designed for 1.6, they're designed for 1.5. And they're not even designed for the "standard" GSM 1.5, but for a "hacked" CDMA 1.5! If we put Android 1.6 on the phones, we could *try* to reuse the existing binary form of the HTC libraries, but if 1.5 and 1.6 talk different languages (most likely they do), the 1.5 version of the binary libraries are going to get confused and reject it. Then we're left with a 1.6 platform that can't talk to the 1.5 libraries, and we get major functionality meltdown. To be fair, it would be possible to write an additional translation layer that would convert the 1.6 messages into something that we "think" the 1.5 libraries will understand, but is it really worth the effort? (hint: it's not a small effort ) Then try doing the same with 2.0, and the potential for translation problems are even worse...
And not to mention, 2.0 also requires the 2.6.29 kernel, which (surprise, surprise), does not exist (for this phone) in the wild. We could theoretically get 1.6 running, since we already have a working 2.6.27 kernel (the phone shipped with it, and if we assume that the shipped kernel is "good enough", we can simply reuse it -- we already do that with the recovery image and even MoDaCo's rom). But as soon as we think about either modifying the kernel as it is, or god forbid, upgrading to 2.6.29, we hit a roadblock because we don't have the source code yet for the 2.6.27 kernel. Once that code is released, we could hypothetically port that support to 2.6.29. Or once HTC releases an Eclair build for this phone, it'll be guaranteed to have a ready-made 2.6.29 kernel buried inside, as well as the binary HTC libraries that are required for our phone. Until one of those two things happens (or, admittedly, someone reverse-engineers what's required... which quite frankly is not worth anyone's time considering we know that HTC *will* release both of those things eventually), Eclair is absolutely out of the question.
The short version (go ahead, admit it, you skipped to here even though I didn't put a "short version at the end" disclaimer at the top): 1.6 will absolutely require reverse-engineering the HTC libraries, just to get an already outdated (albeit still an upgrade) version of the OS on the phone -- not worth the effort. 2.0 will absolutely require reverse-engineering (both the kernel AND the binary libraries), just to get Eclair running on the phone maybe a couple weeks before HTC gives it to us on a silver platter -- And you're still likely to have a partially gimped phone at that point!
And the moral is: this **** is hard. HTC is already doing the work we need. HTC will make everything work "reasonably well". And they'll give it to us when they're done. Thus, no one *wants* to waste the effort doing it themselves. Ergo: we wait.
Click to expand...
Click to collapse
WOW...did you stay at a Holiday Inn Express last night????....J/K thanks for the in depth explanation
Like a lot of people on the forum, their HD2 has caused them a lot of headaches and problems. After waiting patiently from the Euro launch of this phone, my anticipation for this phone was at all time high, more so when I got my 2G iPhone. After I got it, lots of problems like phone slowdown, lag, freezing, SMS/Message App slowdown, lag and freezing. Weather tab freezing, Music player slowdown or skipping (.mp3 skip? What? lol). Data stop working, disconnecting or won't auto connect. Camera lag or slowdown, Email problems, delete email but they come back, or can't send emails. Sleep/Lock of death, phone won't wake up. Phone resets it's self on it's own and I can go on, lol.
I've done everything people have told me do here. I've kill all task, soft reset, hard reset 5x, taken the battery out, taken the memory card out etc. The only thing I haven't done (and will not do) is flash my ROM. The one thing I notice is, if I run "Today" instead of "Sense UI" the phone works fine, so that means Sense UI is buggy. I've contacted T-mobile and HTC, most recently HTC, I've talk to three different people and finally we are getting somewhere.
Here are the last 3 emails out of a total 11 emails I got back from HTC:
Hello Michael,
Thank you for your responses to our questions.
Thanks to your responses, I was able to work with our headquarters on this behavior with your device.
We are investigating this issue with your phone freezing. Since you notice this behavior with HTC Sense enabled, we will likely have to update the software for the HD2. I cannot provide a timeframe for an update, but I can tell you where to look for updates. T-Mobile hosts the updates for their Windows Mobile phones at www.t-mobile.com/wmupgrade.
I hope that we have addressed your question in detail.
Thank you again,
Ryan
HTC Technical Support
www.htc.com/us
Click to expand...
Click to collapse
Hello Michael,
Thank you for your response.
The freezing issue is to be helped with a ROM update as soon as possible. Our ROM updates for T-Mobile phones are hosted by T-Mobile as soon as they are available.
If you still need further response, feel free to let me know what your concern is.
Ryan
HTC Technical Support
www.htc.com/us
Click to expand...
Click to collapse
Hello Michael,
Thank you for your response.
You do not have to apologize to me. I understand how frustrating it is when your device freezes. I hope that the update will be out soon. There are many factors that go into finalizing an update between T-Mobile and HTC, so it may feel like it is taking a while. I do know that from HTC’s US headquarters that we are hard at work to address this issue.
Thank you,
Ryan
HTC Technical Support
www.htc.com/us
Click to expand...
Click to collapse
Members, please, contact HTC by using this link HTC Customer Service, fill out the quick information and send it, and PRESS THE ISSUE that your phone is having terrible problems. I have link them to this forum and they are READING the threads here but it's more apparent if you keep contacting them, get the message out so they can get an update out ASAP.
are we really having this much trouble with our phones? I mean I understand that sense ui is laggy at times.. but if I remember to kill all my running tasks, its not that bad..
I have had a big problem with 3g connectivity but im not tech in a 3g area... but I go from h to 3g to g in the same spots my g1 has 3g.. I called and told tmo..
I mean granted this isn't a rooted android device but this is a good wm phone.. nearly everything I expected...
Raadius said:
...
The only thing I haven't done (and will not do) is flash my ROM.
...
Click to expand...
Click to collapse
Why not?
There are roms that are nearly identical to stock, with just bug-fixes--which seems exactly like what you want.
That's overkill. If I had to do all of that to my phone. I would have gotten rid of it already. The only real problem I had was my phone would not stay on 3G and my wifes phone is always on it.
I'm getting a replacement though.
SaintNULL said:
Why not?
There are roms that are nearly identical to stock, with just bug-fixes--which seems exactly like what you want.
Click to expand...
Click to collapse
It voids your warranty and if you for some odd reason when you wake up some day within the next year and your phone doesn't turn on, and you send it back for a new one, and they find that you have a custom ROM on it, you'll have to pay full price for a new one. It's simply not worth it in my eyes to put on a custom ROM that voids the warranty of a 550 dollar phone to see Sense UI move a little bit smoother.
no one
No ones going to do anything if you dont complain, they'll just say that they dont have records of complaints and its not a known issue. so they cant do anything about it.
i just sent a message
The only real problems I have with tmobile is their bad coverage areas and even though they have bad coverage areas, their coverage areas are exaggerated. It says I should have web coverage in my area, but when I try to place an order for a plan they tell me that cant do it because there is no service in my area. That and I could only half hear the person on the phone because I could hear a bunch of idiots in the back ground not doing their jobs and some god awful singing. And I have to order a new sim card because they said that my sim number must have been an accidentaly reissued number because its already in use.
jas0nw0ng said:
It voids your warranty and if you for some odd reason when you wake up some day within the next year and your phone doesn't turn on, and you send it back for a new one, and they find that you have a custom ROM on it, you'll have to pay full price for a new one. It's simply not worth it in my eyes to put on a custom ROM that voids the warranty of a 550 dollar phone to see Sense UI move a little bit smoother.
Click to expand...
Click to collapse
Took the words out of my mouth.
I just sent a message, after this device might never buy a HTC phone ever again.
I don't know why anyone who's apprehensive to flashing ROMS is even here.
No offense, but this whole forum is built around flashing ROMS. It's one thing if you don't want to go that route, but getting on your high-horse and telling people its a bad idea to flash roms because it voids your warranty is a little much.
Most of the people here understand the risks involved with flashing roms, and anyone who really knows what they're doing knows that the risk is minimal, and that except for extreme cases (and stupidity), a phone can be brought back to stock if needed. Unless you flashed the wrong rom and bricked your device, the only reason you wouldn't be able to bring it back to stock is hardware malfunction due to physical damange...and in most cases, those aren't covered by warranty.
Most people here also know the benefits of flashing ROMS and modifying the UI to make it work, and aren't holding their breaths for a fix from HTC or T-Mobile. Most people here bought the HD2 expecting the stock ROM to suck, and knew that the only way to get it working at the level of their expectations is to flash a custom ROM. If waiting for a fix from HTC or T-Mobile is the route you want to go, then hit up the t-mobile forum, because honestly, the problems a lot of you are facing on the stock ROM, don't exist on custom ROMS. The chefs here will always be 5 steps ahead of T-Mobile and HTC.
It's not just about sense running smoother....its correcting innate problems in WM6.5 and sense that can make the device a pain in the ass to use. Its about making the OS and UI more accessible, capable, and above all, less prone to crashes and more stable!
mystik610 said:
I don't know why anyone who's apprehensive to flashing ROMS is even here.
No offense, but this whole forum is built around flashing ROMS. It's one thing if you don't want to go that route, but getting on your high-horse and telling people its a bad idea to flash roms because it voids your warranty is a little much.
Most of the people here understand the risks involved with flashing roms, and anyone who really knows what they're doing knows that the risk is minimal, and that except for extreme cases (and stupidity), a phone can be brought back to stock if needed. Unless you flashed the wrong rom and bricked your device, the only reason you wouldn't be able to bring it back to stock is hardware malfunction due to physical damange...and in most cases, those aren't covered by warranty.
Most people here also know the benefits of flashing ROMS and modifying the UI to make it work, and aren't holding their breaths for a fix from HTC or T-Mobile. Most people here bought the HD2 expecting the stock ROM to suck, and knew that the only way to get it working at the level of their expectations is to flash a custom ROM. If waiting for a fix from HTC or T-Mobile is the route you want to go, then hit up the t-mobile forum, because honestly, the problems a lot of you are facing on the stock ROM, don't exist on custom ROMS. The chefs here will always be 5 steps ahead of T-Mobile and HTC.
It's not just about sense running smoother....its correcting innate problems in WM6.5 and sense that can make the device a pain in the ass to use. Its about making the OS and UI more accessible, capable, and above all, less prone to crashes and more stable!
Click to expand...
Click to collapse
+1
It's almost as if the OP was attempting a very elaborate troll. The site is called "xda-developers", not "xda-lovers".
If you are looking to mod your device within the so-called "safe" limits that HTC and T-Mobile force upon you, maybe you would be better off hanging out over at freewareppc, instead of a modding forum.
#JustSaying
Snarksneeze said:
+1
It's almost as if the OP was attempting a very elaborate troll. The site is called "xda-developers", not "xda-lovers".
If you are looking to mod your device within the so-called "safe" limits that HTC and T-Mobile force upon you, maybe you would be better off hanging out over at freewareppc, instead of a modding forum.
#JustSaying
Click to expand...
Click to collapse
+2
I can tell you that I had many of those problems and after flashing a custom rom, I've fixed my HD2 almost to perfection, not only the way it looks but stability. Only problem I keep having is 3G connection problems, and by the looks of it, its not the device anymore, seems more like T-mobile's service.
I agree with both perspectives.
I flashed my phone the second day I had it. I'm new to WinMo and was a little nervous, but now I flash weekly (would be daily, but I don't want to become an addict... ) Flashing is night and day from stock and I would never go back (unless it was warranty related).
That being said, I agree with compaining to HTC and T-MO. If there are enough people complaining, then more work will be done to fix those problem, which will lead to better/more frequent updates for the chefs to work with. That way, it's win win. I love HTC devices, they are the best, but when I accidentally dial someone, and it takes me 10 seconds to get to where I can hang up because of lag on a device that technically qualifies to run Windows XP.... That seems unacceptable to me.
joe_coolish said:
I agree with both perspectives.
I flashed my phone the second day I had it. I'm new to WinMo and was a little nervous, but now I flash weekly (would be daily, but I don't want to become an addict... ) Flashing is night and day from stock and I would never go back (unless it was warranty related).
That being said, I agree with compaining to HTC and T-MO. If there are enough people complaining, then more work will be done to fix those problem, which will lead to better/more frequent updates for the chefs to work with. That way, it's win win. I love HTC devices, they are the best, but when I accidentally dial someone, and it takes me 10 seconds to get to where I can hang up because of lag on a device that technically qualifies to run Windows XP.... That seems unacceptable to me.
Click to expand...
Click to collapse
In a perfect world, a company like HTC would hear their customer's cries and devote all of their resources and attention to releasing regular updates. In the real world, HTC has released 4 phones after the HD2, and lined-up several others...they aren't interested in developing for the HD2 anymore. People have been complaining to HTC about the HD2 since it was released in Europe back in November....and they still haven't really addressed most of the concerns.
Most of the 'problems' people complain about are innate characteristics of windows mobile....You see people complaing because their phones lag or crash because they don't manage task manager, but that's an innate characteristic of a multi-tasking OS! On the other side of the fence, you have MS getting bashed for getting rid of multi-tasking in WP7...you have people bashing the iPhone for years over its lack of multi-tasking....and when they come up with a quasi-multi tasking solution, they get bashed for it not being 'true' multi-tasking!
mystik610 said:
In a perfect world, a company like HTC would hear their customer's cries and devote all of their resources and attention to releasing regular updates. In the real world, HTC has released 4 phones after the HD2, and lined-up several others...they aren't interested in developing for the HD2 anymore. People have been complaining to HTC about the HD2 since it was released in Europe back in November....and they still haven't really addressed most of the concerns.
Most of the 'problems' people complain about are innate characteristics of windows mobile....You see people complaing because their phones lag or crash because they don't manage task manager, but that's an innate characteristic of a multi-tasking OS! On the other side of the fence, you have MS getting bashed for getting rid of multi-tasking in WP7...you have people bashing the iPhone for years over its lack of multi-tasking....and when they come up with a quasi-multi tasking solution, they get bashed for it not being 'true' multi-tasking!
Click to expand...
Click to collapse
Ha! It's so true My wife has a myTouch and she complained that the battery life on it sucked and I said that all smartphones get worse battery life than the dumbphones she was use to. Well, one night she said that she understood that batterlife was worse on smartphones, but having to recharge your phone 2-3 times a day was getting rediculous along with the horrible unresponsiveness. Finally I took a look to see what was up, and I guess I must have forgotten to explain "task management" with her, as she had every application on the phone open and running at the same time! Poor phone took a pretty decent beating the first couple of weeks she had it
But back on topic, if HTC releases an update to its Sense UI for WinMo, it should benefit all users of Sense UI (WinMo) reguardless of what phone it's running on. So even if there are newer models, updates should work on older models. That's at least what happened with my Pioneer Navigation system. There were lots of complains about things not working (even a few posts like this on a forum) and that summer they released a newer model that used the same software so our models got the upgrade too. I'm not saying it was a "Windows 7 moment" but I do like to think that our nagging helped.
I'm all for complaining to companies if it means that they produce better quality products. If we just sit around and accept it, then QoS will go down. There must be some formula where the cost of developement is compared to the cost of responding to complaints. When complaints go up, the other adjusts itself accordingly to maximize profit. Lower complains, less developement until complaints go back up! That kind of thing.
Just my 2 cents. But over all, I'm quite happy with kumar's work. If I were still on stock, I'd be upset too.
This is what pisses me off about the whole issue... we ALL know what this site is about. Regardless, NO ONE should HAVE to flash a damn rom to get a phone to function like it should out of the box...especially when you have people that are spending $400+ for it. That's just plain pathetic, bs and I just couldnt go for it which was why I simply returned mine and got my money back. Flashing is cool, but not everyone comes here for new roms... some people come for software, tweaks or to figure out how to do other things.
Telling someone that they SHOULD just flash a rom and deal with it.. even though roms are nice lets just be real, almost every single one of them has SOME kind of bugs with it. That's one of the main reason I stopped doing the flash dance and chose to stick with the stock rom to begin with. But when you buy the phone and it already has bugs, YES people have the right to complain about it and want the issue resolved. That's about as dumb as buying a Mercedes with a blown header and saying.. well you should just put aftermarket headers on it anyways. Should the car just WORK when you buy it? And if it doesnt work.. you take it back and get it serviced or another car.
joe_coolish said:
Ha! It's so true My wife has a myTouch and she complained that the battery life on it sucked and I said that all smartphones get worse battery life than the dumbphones she was use to. Well, one night she said that she understood that batterlife was worse on smartphones, but having to recharge your phone 2-3 times a day was getting rediculous along with the horrible unresponsiveness. Finally I took a look to see what was up, and I guess I must have forgotten to explain "task management" with her, as she had every application on the phone open and running at the same time! Poor phone took a pretty decent beating the first couple of weeks she had it
But back on topic, if HTC releases an update to its Sense UI for WinMo, it should benefit all users of Sense UI (WinMo) reguardless of what phone it's running on. So even if there are newer models, updates should work on older models. That's at least what happened with my Pioneer Navigation system. There were lots of complains about things not working (even a few posts like this on a forum) and that summer they released a newer model that used the same software so our models got the upgrade too. I'm not saying it was a "Windows 7 moment" but I do like to think that our nagging helped.
I'm all for complaining to companies if it means that they produce better quality products. If we just sit around and accept it, then QoS will go down. There must be some formula where the cost of developement is compared to the cost of responding to complaints. When complaints go up, the other adjusts itself accordingly to maximize profit. Lower complains, less developement until complaints go back up! That kind of thing.
Just my 2 cents. But over all, I'm quite happy with kumar's work. If I were still on stock, I'd be upset too.
Click to expand...
Click to collapse
That would probably be true if HTC were releasing more windows mobile based phones and updating sense for new models, but windows mobile is at the literal end of its product life cycle, and development has come to a hault. We've already seen sense updates for Android, but most of those probably won't make it to windows mobile.
Unless it becomes a public relations nightmare for HTC, I don't see them springing to the service of HD2 users....cost is the biggest reason. They've already sold us an HD2, and they've moved onto releasing several models to replace the HD2. Continuing to develop for it will do nothing to generate more revenue for them. HTC's market-share is growing significantly by constantly pushing the hardware bar higher every few months.
I dont think these people who flash roms understand that, a phone shouldnt have so many ****in issues. It should work properly, and their is no word on whether or not T-mobile/HTC are working on an update..This completely B.S for a phone to have so many issues..I've had a dash,iphone, BB 97000 no problems..
Raadius said:
Like a lot of people on the forum, their HD2 has caused them a lot of headaches and problems. After waiting patiently from the Euro launch of this phone, my anticipation for this phone was at all time high, more so when I got my 2G iPhone. After I got it, lots of problems like phone slowdown, lag, freezing, SMS/Message App slowdown, lag and freezing. Weather tab freezing, Music player slowdown or skipping (.mp3 skip? What? lol). Data stop working, disconnecting or won't auto connect. Camera lag or slowdown, Email problems, delete email but they come back, or can't send emails. Sleep/Lock of death, phone won't wake up. Phone resets it's self on it's own and I can go on, lol.
I've done everything people have told me do here. I've kill all task, soft reset, hard reset 5x, taken the battery out, taken the memory card out etc. The only thing I haven't done (and will not do) is flash my ROM. The one thing I notice is, if I run "Today" instead of "Sense UI" the phone works fine, so that means Sense UI is buggy. I've contacted T-mobile and HTC, most recently HTC, I've talk to three different people and finally we are getting somewhere.
If your device has so much problems im sure it's a faulty one why not replace it under warranty??
Mine working perfectly out of box (i wonder where's the lagging was) i dont flash my rom, if it aint broken why fix it? i just do some tweaks that's all
Click to expand...
Click to collapse
because i dont want a refurbished phone. I seriously think i'm done with HTC and anything they add to a phone. I will never buy a phone with Sense U.I on android only ones that dont have it. Also why cant they keep us posted on an update. Its kind of B.S that they release a phone but stop making updates or wont make any because Windows Mobile is dead.. Thats like M.S not updating XP or Vista anymore because Windows 7 is out. People bought this phone a month ago so its ****in new in the U.S and their should be updates being handed out..If not HTC i hope they fail as a company and prob will in the future. Creative destruction new companies come and old ones die just like Palm.
Hello, few hours ago I received another notification about availability of new firmware upgrade. I recall that this is the 2nd time a new firmware is available since I bought the PRO 12.2 LTE. Just like the first time, I cannot tell what kind of changes the firmware made both before and after I updated the firmwares. In general, it is advisable to update whenever it is available? As you know, for some devices, updating caused more troubles.
One would hope that the manufacturer would QC their build prior to rollout so the odds of having issues should be low, but sometimes there are issues that creep up such as unforeseen incompatibilities with particular pieces of 3rd party software users may have installed on their devices. It's difficult to provide a definitive answer here in that regard.
Generally if you're not rooted and have no intention of ever rooting then the answer is yes, with the expectation that anything is possible when it comes to unforeseen incompatibilities.
If you are rooted or wish to root in the future and you're not technically inclined enough to recover from loss of root or restoring from backups then the answer is no, not until others with root have reported in on experience with retaining root or achieving root after updating. Quite often a firmware/system update will cause loss of root. In some cases root will be achieved quickly via applying prior root methods BUT this cannot be guaranteed since there is always a chance that a prior exploit used to gain root access was patched by that update.
I'm guessing root isn't something you're too concerned about but I just thought i'd mention it for the benefit of others.
Thanks. For the time being, I have no intention to root. Maybe a year later.
When it comes to updates, I have a very simple policy: If it isn't broken, don't fix it.
Due to this method of waiting for other people to pick out the errors I've managed to avoid several serious problems on Android over the years.
This applies to app updates, which more often than not introduce problems, as well.
Not to mention every update, no matter how small, brings with it the risk that you need to go through the entire process of wiping the device. I rarely have the time for that. (Which is why I'm 2 updates behind on my Note 3)
I concur with what's already said and just wanted to add my $0.02. There is an empirical finding that the best performance is achieved from the ROMs that are available about six months to a year after the release of any given device and here is the justification. The device is initially shipped with the Android version available at the time of the release. This initial version is invariably buggy because the fast design cycles of these things do not allow a comprehensive test drive by the vendor. So the consumers report the bugs, they get patched, and about 6 months later everything is wrapped into the next version of Android and pushed as an update. This second ROM release is much more stable than the first one but still lacking a few things here and there, which results in the next major ROM that will fix most everything.
By this time we are 6 months to a year into the life of the product and the market is now seeing other devices with higher processing power and better specs. The Android releases at any given point in time are tweaked towards the expected performance of the devices that are available at that time. So the next update for your now-more-than-a-year-old device will have nicer features but it is geared towards other devices that are faster and better than yours. So now you upgrade to the third release and you will find that while all the initial bugs are gone the device is laggy and the battery goes down faster than it used to. Most devices don't have a straightforward procedure to downgrade to an older version (at least for the common user) and therefore you will just write this off as your device being too old and slow and then you will be likely convinced by a salesperson to buy the next generation tablet and that is the end of that.
If you are into rooting and modding don't forget that every update makes it generally harder to root your system.
By owning a flagship android device, we always want the latest and greatest software available for this device, but there are only limited number of software engineers that work on android updates for LG flagship devices (around 300-400 engineers) depending on region, so they are not able to provide the users with all the minor android updates Google decides to release. Therefore, they turn their attention on major updates, instead of minor ones to keep their user base happy. Keep in mind that LG honors your device eligibility for upgrade to 24-27 months before dropping support and that we can't always get what we want.
My question to you is... If LG was reconstructing their plans for android updates, which one do you prefer?
1) You want all the minor android updates that Google releases to be released for your LG G3 and receive major ones later.
2) You want faster release of major android updates to the most current version.
To clarify: Choice 1 gives you more frequent small updates and Choice 2 gives you less frequent, but large updates. When your device approaches the support-end date, choice 1 will be one major update behind choice 2 because engineers working on every android updates and won't be able to release the major one in time.
This is a really hard one to call. Recently I received the 20f update from 20e on my D855. It was only a 12mb google patch but didn't change the android version the phone was on, in fact I don't know what it changed! Obviously it fixed or improved something but it would be nice to know what!
I think it is a matter of priority, if we receive a major update, for example going from 5.0 to 5.1.0, which not only has performance improvements but cosmetic and feature additions then I would like to receive this type of update as soon as possible helping my device stay at the cutting edge.
But if this update breaks something... like my wifi becoming unstable or system programmes force closing all the time, I would expect that to become the priority no matter how small the patch update may be!
So to reiterate, my first choice would be option 2 bringing in a touch of option 1 if required!
beastobadness said:
This is a really hard one to call. Recently I received the 20f update from 20e on my D855. It was only a 12mb google patch but didn't change the android version the phone was on, in fact I don't know what it changed! Obviously it fixed or improved something but it would be nice to know what!
I think it is a matter of priority, if we receive a major update, for example going from 5.0 to 5.1.0, which not only has performance improvements but cosmetic and feature additions then I would like to receive this type of update as soon as possible helping my device stay at the cutting edge.
But if this update breaks something... like my wifi becoming unstable or system programmes force closing all the time, I would expect that to become the priority no matter how small the patch update may be!
So to reiterate, my first choice would be option 2 bringing in a touch of option 1 if required!
Click to expand...
Click to collapse
I have to agree with you. I wish there was a happy medium between the two.