No more HTC Desire by Vodafone NZ?

Forums › Android › No more HTC Desire by Vodafone NZ?

1 | 2 | 3

Dingbatt

6756 posts

Uber Geek

Lifetime subscriber

#360812 31-Jul-2010 21:06

Thanks for your comprehensive reply :)
Chances are there won't be a successor to the N1 since google have dropped selling phones themselves, which is a shame. The N1 running a skin that behaves a little like senseUI on 2.2 is probably worth looking for in my case. But then that really is (apart from some of the points you raised) what a Desire is. I survive on 1 battery so taking the back off isn't a biggie.

Edit: Corrected a typo.

“We’ve arranged a society based on science and technology, in which nobody understands anything about science technology. Carl Sagan 1996

Linuxluver

5828 posts

Uber Geek

Trusted

Subscriber

#360824 31-Jul-2010 21:37

Dingbatt: Thanks for your comprehensive reply :)
Chances are there won't be a successor to the N1 since google have dropped selling phones themselves, which is a shame. The N1 running a skin that behaves a little like senseUI on 2.2 is probably worth looking for in my case. But then that really is (apart from some of the points you raised) what a Desire is. I survive on 1 battery so taking the back off isn't a biggie.

Edit: Corrected a typo.

There are custom ROMs available with Sense UI. I tried one last week from Modaco. It also had the FM radio app and it worked with the Nexus One, which has the FM radio (receiver & transmitter) chip....but it isn't enabled in the stock Nexus One. I might have kept it on had the Bluetooth worked and the FM radio function been stable....but it's an alpha, so still somewhat experimental.

The question of a successor to the Nexus One will relate to the need for a new reference platform for the operating system's future development.

There may well be such a successor if only for political reasons. If the phone that is the basis for development is Google's phone (made by whomever) then all the phone vendors can feel somewhat relaxed about any one phone maker having the "in" for phone development. It's done by the open Handset Alliance, so they all share in that process.

But if the future reference phone succeeding the Nexus One was not "Googles".....then whose would it be? That might raise thorny competitive issues that are avoided by making the reference phone a "Google" phone.

What we don't know is how any such future phone would be made available. Perhaps only to registered developers ($25 gets you registered)? A minor hurdle to leap over to get the newest, coolest, Google Android-ness.

I hope that makes sense. I'm just speculating....letting one thought follow another. Time will tell, as always.

_____________________________________________________________________

I've been on Geekzone over 16 years..... Time flies....

drbob

12 posts

Geek

#362085 3-Aug-2010 08:30

A word of warning if buying the HTC Desire from Mobicity.

I received mine yesterday (the A8181 for use on Vodafone NZ). It worked fine at first, on the stock Android 2.1. After an hour, I accepted the 'over the air' update to Android 2.2 which the phone offered.

Since then, the phone is stuck in a reboot loop, with a 'process system is not responding' error and no wireless functions. This error has been described on other forums, mainly with 'debranded' phones. This makes me wonder whether the HTC Desire sold by Mobicity is a debranded one.

I'm sending the phone back - I would be interested if other users have had the same problem.

Dingbatt

6756 posts

Uber Geek

Lifetime subscriber

#362090 3-Aug-2010 08:49

Linuxluver:
Dingbatt: Thanks for your comprehensive reply :)
Chances are there won't be a successor to the N1 since google have dropped selling phones themselves, which is a shame. The N1 running a skin that behaves a little like senseUI on 2.2 is probably worth looking for in my case. But then that really is (apart from some of the points you raised) what a Desire is. I survive on 1 battery so taking the back off isn't a biggie.

Edit: Corrected a typo.

There are custom ROMs available with Sense UI. I tried one last week from Modaco. It also had the FM radio app and it worked with the Nexus One, which has the FM radio (receiver & transmitter) chip....but it isn't enabled in the stock Nexus One. I might have kept it on had the Bluetooth worked and the FM radio function been stable....but it's an alpha, so still somewhat experimental.

The question of a successor to the Nexus One will relate to the need for a new reference platform for the operating system's future development.

There may well be such a successor if only for political reasons. If the phone that is the basis for development is Google's phone (made by whomever) then all the phone vendors can feel somewhat relaxed about any one phone maker having the "in" for phone development. It's done by the open Handset Alliance, so they all share in that process.

But if the future reference phone succeeding the Nexus One was not "Googles".....then whose would it be? That might raise thorny competitive issues that are avoided by making the reference phone a "Google" phone.

What we don't know is how any such future phone would be made available. Perhaps only to registered developers ($25 gets you registered)? A minor hurdle to leap over to get the newest, coolest, Google Android-ness.

I hope that makes sense. I'm just speculating....letting one thought follow another. Time will tell, as always.

I guess what I was getting at was because Google retailed the N1 themselves and promoted it, sales were much higher than will be the case for any future reference phone. I assume that will mean the possibility of getting one down here will be reduced, particularly for 'casual users' as opposed to developers. Unless of course VF decide to offer it

(genesis of this thread?).

“We’ve arranged a society based on science and technology, in which nobody understands anything about science technology. Carl Sagan 1996

caldazar

459 posts

Ultimate Geek

#362133 3-Aug-2010 10:02

I'm sending the phone back - I would be interested if other users have had the same problem.

That's really crap. Is there no way to reload the ROM here?

Hope this is a rare occurrence for Android as updates shouldn't cause these issues, especially OTA updates.

drbob

12 posts

Geek

#362140 3-Aug-2010 10:11

caldazar:
I'm sending the phone back - I would be interested if other users have had the same problem.

That's really crap. Is there no way to reload the ROM here?

Hope this is a rare occurrence for Android as updates shouldn't cause these issues, especially OTA updates.

I tried downloading the update from the HTC website (as a ZIP file), renaming it 'update.zip', putting it on the SD card, and reapplying the update in the phone's recovery mode, but encountered the same problem again.

It looks like the only way to reload the ROM would be to create something called a 'gold card' (a modified SD card). This looks quite involved, and I'm not prepared to spend the time doing this (it would probably invalidate my warranty, anyway).

Awaiting word from Mobicity...

caldazar

459 posts

Ultimate Geek

#362147 3-Aug-2010 10:24

hmm, yeah just looked up the gold card instructions... doesn't look quick or simple.

I'm just new to android but surprised a restore can't be done in a simple way like the iPhone.

Quic Broadband

Move to New Zealand's best fibre broadband service (affiliate link). Free setup code: R587125ERQ6VE. Note that to use Quic Broadband you must be comfortable with configuring your own router.

drbob

12 posts

Geek

#362198 3-Aug-2010 11:23

After speaking to Mobicity, apparently this has happened to other users who recently bought the HTC Desire A8181 from them, too.

It looks like the ROM which the device shipped with is not compatible with the over-the-air Android 2.2 update. Waiting for a solution from the warranty dept...

caldazar

459 posts

Ultimate Geek

#362304 3-Aug-2010 12:53

I read up on some threads. Seems like most fixed this with the gold card - why not be adventurous and give it a try? Chances are if you send it back, that will be how Mobicity fixes it.

Elpie

1304 posts

Uber Geek

#362728 4-Aug-2010 01:58

drbob: After speaking to Mobicity, apparently this has happened to other users who recently bought the HTC Desire A8181 from them, too.

It looks like the ROM which the device shipped with is not compatible with the over-the-air Android 2.2 update. Waiting for a solution from the warranty dept...

Let us know what they say. When I saw loads of reports that HTC Desires from Mobicity were not able to be updated OTA I called and asked if there were any known issues. They told me not to do OTA updates but didn't offer any solution, just saying software updates are not covered by warranty.

That's not going to be much of an issue for me as I intend to root the phone and change my Taiwanese ROM to WWE anyway, but I'd still like to know what Mobicity do about the lack of OTA updates on non-rooted phones.

Mudwiggle

12 posts

Geek

#362777 4-Aug-2010 09:15

I have a recent a8181 desire from Mobicity and have managed to upgrade to Froyo without too many issues.
One word,of caution when buying from Mobicity, although their prices are in NZ dollars and you are invoiced in NZ dollars, the buggers charge you in Aust dollars so it attracts a transaction and conversion fee on you credit card adding about $25. This is specified in the fine print on their website.

drbob

12 posts

Geek

#363064 4-Aug-2010 15:28

Well spotted, Mudwiggle - I checked, and you're right - I was charged an extra $17 'offshore service margin' on the purchase.

Sending my phone off for repair under warranty now. I really wish I'd bought from Gadgetsonline or Aquila!

caldazar

459 posts

Ultimate Geek

#363147 4-Aug-2010 17:42

I ordered my phone from Mobicity the other day. The website prompted me when I went to make the order with a note about the order value being converted to Australian dollars, so I knew to expect it.

1 | 2 | 3