Related
...does anyone know if and when 02 are going to release a new ROM for the Exec?
I've had mine running now for a while with the Blackberry Connect software and it's not what you call stable. The service stops for no reason, or hangs or simply wont connect, I have to reset frequently.
I used an 02 Mini-S for a while and that was rock solid... shame the Exec isn't.
Thats the million dollar question.
Various posts about this with no answer.
I emailed O2 a week or 2 ago asking the very same thing. I did get an answer which basically said they don't know with no plans. O2 Cust service said they usually know a few months in advance but haven't heard anything.
How long is a peice of string????
mrbrightside1977 said:
Thats the million dollar question.
Various posts about this with no answer.
I emailed O2 a week or 2 ago asking the very same thing. I did get an answer which basically said they don't know with no plans. O2 Cust service said they usually know a few months in advance but haven't heard anything.
How long is a peice of string????
Click to expand...
Click to collapse
...our company got them just as they'd released the Blackberry Connect update, got that hot off the press straight from 02.
It's not such a bad piece of kit, the only wobbles I have are with the BB functionality and the phone... but then again as I said previously, the Mini-S was faultless...
davidUK said:
...our company got them just as they'd released the Blackberry Connect update, got that hot off the press straight from 02.
It's not such a bad piece of kit, the only wobbles I have are with the BB functionality and the phone... but then again as I said previously, the Mini-S was faultless...
Click to expand...
Click to collapse
Guess your company should of pressured O2 into confirm/agreeing upgrade commitment contract etc...
Sorry, I wished O2 were better ie they release some great phones/PDA devices but still think of them as 12 month contract phones. Don't see the big picture.
Company I work for (one of the big banks in the UK) where trialing the XDA EXEC but couldn't really get what they wanted from O2.
Shame as all IT guys love the machine - just software was a bit pants.
mrbrightside1977 said:
Guess your company should of pressured O2 into confirm/agreeing upgrade commitment contract etc...
Sorry, I wished O2 were better ie they release some great phones/PDA devices but still think of them as 12 month contract phones. Don't see the big picture.
Company I work for (one of the big banks in the UK) where trialing the XDA EXEC but couldn't really get what they wanted from O2.
Shame as all IT guys love the machine - just software was a bit pants.
Click to expand...
Click to collapse
...feel enclined to agree... it would have been useful to be able to browse the web on them, but they tell us as we're on a Blackberry tariff Internet access is unavailable... tried several technical work arounds to no avail.
Odd really, previously we had some T-Mobile MDAIII's with Blackberry functionality and we could browse the web with them quite well.
We were hoping for some kind of Terminal Services remote control of our services over a VPN of some description with the Exec..but the lack of Internet access on them put a stop to that.
I don't think, this is a problem specifically with the O2 company. I beleive the entire HTC Universal device provider whether O2, IMate, TMobile, QTEK, etc... HAS NO PLANS OF RELEASING ANY ROM UPDATE FROM NOW ON. Why? To them, our device is a thing of the past. They are concentrating more on their current NEW or UPCOMING devices.
cktlcmd said:
I don't think, this is a problem specifically with the O2 company. I beleive the entire HTC Universal device provider whether O2, IMate, TMobile, QTEK, etc... HAS NO PLANS OF RELEASING ANY ROM UPDATE FROM NOW ON. Why? To them, our device is a thing of the past. They are concentrating more on their current NEW or UPCOMING devices.
Click to expand...
Click to collapse
...I'll not be too impressed if thats the case. I think the latest 02 device is the Orbit, looks ok, only seen it on the website though.
davidUK said:
...feel enclined to agree... it would have been useful to be able to browse the web on them, but they tell us as we're on a Blackberry tariff Internet access is unavailable... tried several technical work arounds to no avail.
Odd really, previously we had some T-Mobile MDAIII's with Blackberry functionality and we could browse the web with them quite well.
We were hoping for some kind of Terminal Services remote control of our services over a VPN of some description with the Exec..but the lack of Internet access on them put a stop to that.
Click to expand...
Click to collapse
We decided to scrap the BlackBerries in favour of Mini S and Execs. That effectively brings in Exchange Push E-mail synchronisation, Phone Service and Internet access as well... not to say you can install GPS Sat Nav on them and other good things.
Granted, I had to understand how to make a Certificate Based Authentication to comply to the Corporate Policy, and having strong password is a real pain in the proverbial -- but still it beats all devices.
My only grudge against Exec is not so much free RAM; as a result Navigon MN|5 requires a reboot beforehand if you're going somewhere far - to prevent nasty surprises during the trip (esp. considering the goddam strong password which you can't enter with your finger...)
cktlcmd said:
I don't think, this is a problem specifically with the O2 company. I beleive the entire HTC Universal device provider whether O2, IMate, TMobile, QTEK, etc... HAS NO PLANS OF RELEASING ANY ROM UPDATE FROM NOW ON. Why? To them, our device is a thing of the past. They are concentrating more on their current NEW or UPCOMING devices.
Click to expand...
Click to collapse
... Which is really SHAME, because there are so far NO "New" or "Upcoming" Phone Edition devices with VGA screen... Universal is one of a kind. Granted there are VGA devices with GPS - but no phone; or nice phones with GPS - but only QVGA or even 240*240 screen.
We've paid shedload of money and... once again guys, tough, go buy another one. ARRRRGHHH!!!!
Or shall we?
Screw this.
I guess during the Christmas holidays I'll just go and try one of the ROMs that can be found here - got nothing to lose and all to gain, and a good experience of flashing ROMs on previous XDA II Himalaya.
If these hold Push E-mail updates, screw the O2 updates altogether.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HTC-USA OFFICIAL TECH SUPPORT IS CLUELESS ABOUT THEIR OWN PRODUCTS.
Today is Thursday August 5th, 2010. I have not yet gotten the Froyo update. How do I get it. This is my scenario:
I am in USA, I have an unbranded, unlocked UK Desire (purchased the day they first went on sale in UK). My cell operator is T-Mobile USA. No, I don't have 3G and don't care. (T-Mobile USA wont offer good phones so I choose to buy good phones and give up 3g, since I use WIFI 80% of time anyway).
My firmware version still says: 2.1-update1
I have manually tried "Check Now" several times for the past 5 days to see if the update was ready for OTA download. NO. It always says "Your software is up to date."
(1) Has ANYONE from USA gotten the update on a UK Desire Phone?
(2) Does anyone know the rollout procedure? This is an unlocked phone that was bought without tied to a carrier. What kind of detection does HTC have regarding REGION of where you are located in determining when you are "next" to get the update?
thank you.
/quicksite
Currently it's only Europe that has the update. I'd say flash your phone with the Europe ROM but that would probably cause issues as T-Mo US uses a different radio frequency so you'd get no 3G.
steve228uk said:
Currently it's only Europe that has the update. I'd say flash your phone with the Europe ROM but that would probably cause issues as T-Mo US uses a different radio frequency so you'd get no 3G.
Click to expand...
Click to collapse
Let me clarify:
1) I bought an unlocked Desire from the UK the day they first were shipped, the very first people at XDA developers who got a phone.
2) I chose this phone because I wanted it, even knowing T-Mobile USA sucks for not offering the phones I want -- the Hero last year, no. The Desire this year, no. Thus, I pay for European models and do without the 3G because I want the phones
3) It is also not true re just Europe. The Sprint EVO, which is the Desire for USA, on Sprint network, has the update.
4) I just spoke to HTC-USA support. They are about as incompetent as anyone to whom i have ever spoken. THEY sound like the "iPhone 4 buyer" in the infamous YouTube video comparing the Evo vs iPhone4... which is to say, they are blithering idiots.
a. I ask them when I will get my update. They said: it was already available 2 weeks ago for unlocked phones.
b. I asked where? They said: from http://developer.android.com
c. I went there while on the call and saw only a SDK download and asked, are you sure? He said, NO, no not that. You want the generic 2.2 download, because since you are not on a branded carrier phone, there is nothing that you need from the carrier.
d. I said "there is nothing here, can you find the link?"
e. After he searched he said, I cant find any link. he said "i can find a link on 3rd party sites but we cannot endorse them."
f. I said: I bought an HTC phone. How do I get an HTC approved 2.2 update?
g. he said, unfortunately, since you are in USA with T-mobile, and they don't carry this phone, you cannot get the update OTA. The signal won't reach you from the UK cell towers.
h. I said: Then how are the people in UK getting it?
i. He said: Their local cell towers are pushing it out?
j. Then if I can't get it OTA, where do I get it?
k. He says: Unfortunately I cannot find anything about it on any HTC website in Europe or North America. We do not host the downloads.
l. So how do I get it?
m. I'm afraid I don't know.
n. ME: I am calling HTC Support north america and you don't know how i am to get this update?? Should I call HTC Support UK since it is a UK purchased phone? (I was serious, not smartass)
o. No, they won't be able to help you since we have no files on UK site either.
p. This is pathetic. Will you please check with a supervisor and tell me who i should contact, or where i should leave a support trouble ticket to be able to be told where to download the update?
---
on hold
---
back
---
q. I'm sorry I told you wrong. You SHOULD be getting your update OTA.
r. How is that possible when you told me 10 minutes ago that I could not get it because it was being pushed from European cell towers and the signal could not be reached here? How NOW am i supposed to get it OTA?
s. I was mistaken. You had a WINDOW OF OPPORTUNITY about 2 weeks ago and it must not have worked, so you have to hold on maybe another week or so until they come around again to your cluster.
t. what?
u. They release the OTAs in clusters, and yours has expired and so you will have to wait til it comes around again.
v. I have no faith at all in what you are telling me. Suddenly it's supposed to appear in my Software Updates -- and yet I missed the fact that it occurred already? How is that possible? I have manually checked it every day for past 2 weeks?
I then asked about IF i were to go to a THIRD PARTY SITE to download the 2.2 update, is it PHONE SPECIFIC? because that is what I kept reading HTC saying, that it takes time to port it over and test it per phone.
He said: No, it was ready 2 weeks ago, it didn't take long to test at all.
I asked: Are you sure? Isn't this supposed to have an update to Sense?
No. There's no update to Sense that I know of.
Are you sure? I thought there was? And that this was why it was taking so long. That HTC had to get Android 2.2 to work properly and have Sense work on top of it.
Not that I know of.
I asked: So, this update will enable 720p recording, and apps2sd?
He (HTC TECH SUPPORT): Well 720p is dependent on whether or not your phone is capable of it.
Me: What? I am calling HTC. Don't you even know your own phone? The DESIRE has been stated as being capable of it, as having a far greater sensor than necessary but the OS update is what will enable this feature. How can you not know that?
He: Well to be honest, I have not had a lot of time to play with the phones.
Me: I am astounded. I am a customer and I know your product line and you don't even have a clue. You have been zero help on this call. I am going to post about this whole experience on XDA developers (I am sure he didn't know what that was, anyway). I said "Are you sure you don't want to amend anything you've said?"
He: I'm sorry I got the OTA info wrong initially.
Me. Thank you, I have to go.
He: is there anything else I can help you with today?
me: Are you kidding me? No.
He: Well keep in mind you can get updates to support issues at our twitter channel 24/7.
Me: Oh please, no. is this the twitter/HTC channel?
He: Yes.
Me: You have got to be kidding me. Do you have any idea what gets posted on that channel?
He: Support news.
Me: NO! It posts about "See our latest TV ad for the Aria on Jimmy Kimmel Show tonight" ... It is crappy marketing, it has nothing to do with support. How could you have possibly made an already terrible call filled with horrible misinformation any worse? and yet you did by citing HTC's pathetic TWITTER channel which has nothing but marketing contests. Something is terribly wrong with your company's communications. I have been buying your phones for over 5 years, HTC invented the genre -- and with no disrespect intended, you have managed to malign the whole brand reputation in one phone call. Please, get your act together.
======================
So -- here I am an hour later -- and now I know that I am ABLE to get the update -- my phone being an unlocked UK phone. So please, is there anyone who can explain how. This is ridiculous.
thank you.
This may be a long shot (but might work)
Assuming you are connecting over wifi to do this then how does the phone know it is in the USA and not the EU? My guess is because when you first put a SIM in the phone, it tells it.
So take the SIM out of the phone and try again (over WiFi of course). If that does not work, see if you can manually set the operator to a UK one (such as Vodafone).
The OTA update comes over the air (duh). But when you are connected over wifi you are bypassing the carriers network and connecting direct to the HTC servers (wherever they are). So the argument about you not being on am EU network does not make sense.
Try the above and see how you go and if it does not work, sorry.
Not sure that will work, it doesn't even work for me in the UK...
My official response from HTC was similar to the phonecall repeated here, they said it is being released in batches not all together and I just have to wait until my batch comes round, potentially up to 2 weeks according to support.
My phone is also a very early one (bought on 2nd day they were in store after my pre-order from CPW wasn't fulfilled because they were somehow out of stock, despite having them in stock in my local shop!) I guess they're not releasing the update in serial number order!
P.
How long have you been trying though? I know that the EVO has had the update but what I was saying is the Desire hasn't anywhere but Europe i.e. Canada, Asia, and the USA.
You should be able to get the OTA if it's a SIM free phone with a WWE ROM but there are posts on the forum stating the the update may have been removed due to some issues.
Keep hitting that check button or just flash manually with the released ROM zip.
Sent from my HTC Desire using XDA App
.
HTC SUPPORT WEBSITE IN UK: Search results for: HTC Desire > Android 2.2
@MARK said:
This may be a long shot (but might work) ... Assuming you are connecting over wifi
Click to expand...
Click to collapse
It's a great idea, thank you for that suggestion! hadn't even thought of it, i will try it -- despite messages afterwards saying wont even work in UK.
But what I want to know is: WTF is happening to HTC?
Really, this is becoming more and more disturbing.
The people at XDA are the people that PUT THEM ON THE MAP as their earliest buyers -- we are the early adopters of touchscreen smartphones -- longe before an iphone existed as a glimmer in Steve Jobs' eye. True, he had the Newton years ago, and hats off, as always, to Apple's exceptional product design vision. But it wasn't a phone, and it was long ago abandoned.
HTC and Windows Mobile made this whole new multi-billion dollar industry possible -- that now enables Verizon to profit from introducing and seling the DROID, that enabled steve jobs to launch the iPhone and, in all fairness, to finally get the UI right -- and take advantage of touchscreens -- vs Windows Mobile engineering's retarded tiny stylus driven tap inside 5-pixel wide box to hit that preference selection.
Then HTC ceded that business to Apple for several years as they barnstormed the industry, became the darling of engadget and gizmodo and could do no wrong. WHAT KEPT WINDOWS MOBILE COMPETITIVE were two things: HTC -- and their various UI overlays -- like touchflo -- now advanced to SenseUI -- and XDA-developers -- who pioneered so many advances that made a stylus-based OS start to work like a finger-navigable OS.
MY POINT? We, the early adopters, don't just get bragging rights. That's juveile. WE BOUGHT PHONES -- over and over and over. I have bought 5 HTC smartphones. SO I am getting a little sick and tired of being treated like **** by them. They paid multiple hundreds of millions for the whole new BRANDING campaign internationally -- to jetison the faceless image of no-name chinese manufacturer -- to a brand name of high quality phones they have always been known for.
But with that corporate makeover on the outside, what the hell has happened on the inside? WE, those of us who bought the Desire en masse in pre-orders -- were screwed over by HTC time and time again in April and May of this year as they have taken their eye off the prize -- of rewarding customer loyalty -- and now they just shoot for NEW CUSTOMER RELATIONSHIPS... They diverted OUR stock of shipments to RE-STOCK T-mobile UK, and other carrier sticks - so the carriers could CHA-CHING selling not just phones but service plans and data plans -- and HTC kissed their asses, while dismissing us as expendable.
It was only after we mounted a huge backlash that they did an about face and fixed that issue, but only after showing their hand, and really annoying alot of loyal customers -- these are not cheap phones -- and we don't buy the low-end crap. we buy the high end phones.
And so same thing now. WHO GETS THE UPDATES -- frikkin SPRINT in the USA with the EVO.... The CMDA phone which has no legacy tie at al to the GSM phones HTC built their reputation on. They are once again spitting in the faces of their loyal REPEAT CUSTOMER base -- because they feel they can DO so -- and what are we going to do -- STOP BUYING?
That's when hubris sets in, and it's very arrogant, and very calculated. They run the risk/benefit analyses of "what's the downside of pissing off the unlocked phone buyers" vs the UPSIDE of making our NEWEST PARTNERS -- Sprint in the USA -- and VERIZON in the USA -- happy?
I know how this game is played. I live in the heart of silicon valley. I live in the neighborhood with many google developers including the guy who product designed the G1 -- the first android phone -- and developed its UI. I onlty say this because I know the marketing business very well. SO well that it makes me very angry when I get PLAYED by smartass people who think they can pull the wool over customer eyes.
They only CAN because custimers let them. It ticked me off that XDA-devs sat on their thumbs and refused to use their enormous CLOUT when HTC was F*ing over all of the DESIRE pre-order purchasers in April and May.
I frnakly do not understand the sheep argument.. of why it is that people sit back and take it --- and sooner or later someone will post here -- dude- chill - it's just a phone, or - dude-chill -- Im sure there is nothing going on like you say. and so on.
Yeah? okay, fine. I will twiddle my thuimbs and keep looking for that update while some as*h*le who only discovered touchscreens last month and bought their EVO from Sprint quickly gets their 2.2 update served to them on a silver platter. This is nuts.
Oh. Sorry. I just riffed off of a THANK YOU post to someone who posted to help me Trust me, i greatly appreciate it, and will try it. This steam is of course not venting at you. It is at the situation and how preposterous it is.
@MARK said:
This may be a long shot (but might work)
Assuming you are connecting over wifi to do this then how does the phone know it is in the USA and not the EU? My guess is because when you first put a SIM in the phone, it tells it.
So take the SIM out of the phone and try again (over WiFi of course). If that does not work, see if you can manually set the operator to a UK one (such as Vodafone).
The OTA update comes over the air (duh). But when you are connected over wifi you are bypassing the carriers network and connecting direct to the HTC servers (wherever they are). So the argument about you not being on am EU network does not make sense.
Try the above and see how you go and if it does not work, sorry.
Click to expand...
Click to collapse
steve228uk said:
You should be able to get the OTA if it's a SIM free phone with a WWE ROM but there are posts on the forum stating the the update may have been removed due to some issues.
Click to expand...
Click to collapse
Thank you. When you first posted I had not yet spoken to HTC... So i didn't yet understand what you meant.. sorry bout that. What does "WWE ROM" mean?
Whose site would it have been hosted on -- before there were issues?
This is what I am trying to understand. The HTC guy initially told me: You can get it from the Android site -- then use HTC Sync to downlaod it to computer and then install onto phone that way...
Then it was not available at Android.com
Then you were saying perhaps it was available from T-Mobile UK's site -- in downloadable form? Is that correct?
(NOT DIRECTED AT YOU) Why is this such a frikkin' mystery? Isn't the whole concept supposed to be: Android phones are updatable firmware phones, thus, improved features sets and functionality always as the code is improving... And phone manufacturers like HTC manufacture phones that are compliant with Google's Android OS. So why is this such rocket science?
I have an HTC phone. It's been cleared for takeoff. Android 2.2 exists for this phone. What is their problem?
Hi,
I live in Canada but managed to get a zune HD over a year ago. I also setup a USA addressed live ID and purchase zune pass cards in the US(buddy in US does it for me)...
If I get a WP7 is this going to work with the USA live id or will it see I'm matched with a Canadian cell phone provider and disallow the zune pass to work?
Thanks.
LIP
I've seen posts where others are using US based ID's and CC's to access the Marketplace from non WP7 countries. So my guess is you'll be OK.
somebody has to be the guinea pig...
If I could get a dell venue pro up here in Canada...or even get the samsung unit from somewhere other than Rogers(Robbers) I would be all over it...I'll get this phone anyway...I think in the long term it will be one of the better platforms, if not the best.
I haven't had any problems yet.
nrfitchett4 said:
somebody has to be the guinea pig...
Click to expand...
Click to collapse
My US Zune Pass ran out 2 months ago, but I still have my old laptop setup to work with it. So added my UK Omnia7 and linked to the US ID, without any problems.
I could sync MP3's, Videos even Zune Pass sub'd music to the phone. All played fine except the sub'd music, that wanted to check my usage rights.
And the phone it worked fine too, sync'd with my US hotmail account while still using my UK sim card.
So the zune pass (subscription music) doesn't seem to work for you ZaForD?
Anyone outside of USA (anyone who resides where zune pass does not officially work) have a zune pass working on their wp7 phone?
NEW IN THIS THREAD?
PLEASE READ THE FOLLOWING BEFORE REPLYING
PLEASE NOTE THAT THE PROBLEM HAS BEEN FIXED WITH AN OVER-THE-AIR UPDATE BY GOOGLE. IF YOU SUFFER FROM THIS PROBLEM THEN YOU SHOULD WAIT FOR THE UPDATE TO ARRIVE ON YOUR DEVICE.
Full details:
What the problem is
The device has an issue of volume acting strangely. Most often the volume mutes very quickly. Sometimes the volume starts 'jumping' between muted and loud very quickly.
This volume issue happens often during phone calls, using internet or receiving SMS text messages.
Some users are also reporting that when calling, they can hear 'radio interference' sounds.
The device is often unresponsive while the problem happens. Power button not working for the brief time has been reported.
How it happens
The problem happens while the device uses GSM 900 network, that is when the device is in 2G.
Your phone is on 2G when it uses E (Edge) and G (GPRS) connections, both data and mobile. If data is used, a small letter near signal indicator points out what you are connected to.
The problem happens while another device that is on GSM 900 is nearby and is transmitting in 2G network. This happens even if Nexus itself is not using any networks at the time (such as when radios are off and the device is in Airplane mode).
The problem is more evident when user is in low-signal area and more 2G information is transmitted.
The problem also happens in bootloader and is not the fault of Android 4.0 itself.
Please remember that the problem does not happen for all 2G networks, some 2G networks (especially outside Europe) do not use GSM 900.
How many users are affected
Every Samsung Galaxy Nexus handset seems to be affected by this problem. Majority of users however are not encountering the problem due to not using GSM 900 2G networks.
2G networks working on GSM 900 are majority of Europe, Africa, Australia, Middle East and large part of Asia.
In UK, the GSM 900 is used by O2, Vodafone, giffgaff, Tesco Mobile.
What Samsung and Google are saying
No official statements from Samsung other than asking people to send details of the problems on their customer support e-mail ([email protected]).
Samsung did post a quote on their Samsung UK Facebook wall that says 'We are aware of the volume issue and have developed a fix. We will update devices as soon as possible.' This quote is said to be originating from Google according to Samsung, Clove, androidpolice.com and The Verge.
Google employee has confirmed in an Android developer chatroom that Google is developing or has developed a software fix for the problem.
Another Google employee, Dan Morrill, shared a post by Lee Johnson on his wall and said that he is very accurate in his estimation about how software can fix this hardware flaw.
Google has replied to a customer support thread that there is a fix and it will be rolled out in the coming week. It is possible that the 'coming week' refers to week starting 5th of December.
What sellers are saying
Handtec and Clove conducted additional testing on the devices and both found the volume bug to exist on their devices.
Handtec stopped the shipments after the problem became widely known. Samsung Distribution also stopped shipments for sellers few days later, delaying shipments of the device for a week.
Clove stated that according to what they heard from Google, that a software fix is being worked upon. Clove stated that according to their sources the problem is in software and not hardware. Clove has not gotten this information from Google or Samsung directly however and refers to their inside research about information found online and their own sources.
While it was originally believed that the shipment delays are because of Samsung flashing the devices with updated software that will fix the bug, the new devices shipped on 29.11 also carry the bug according to Clove. It seems Samsung held the shipments to give Google additional testing time with the fix and held back possible refunds and replacement handsets would have gotten had the shipments not been held back.
Is it hardware or software problem?
All the tests conducted by many users so far indicate that the problem is in hardware and that the device receives signals from 2G that it should not receive due to not being protected from radio interference. This is also shown while the device runs in bootloader.
Many engineers here and in other forums and social networks say that a cheap hardware shielding would fix the problem easily, however Samsung and Google intend to fix the problem with possibly as valid means through software.
If the software fix manages to patch the problem, then it really does not matter if the problem was in software or hardware, as long as the device works properly and there are no after-effects, since some users fear that the software fix of a hardware might cause additional battery drain or unresponsiveness problems. But this is merely an opinion, we will know more once the patch is out.
The flaw is confirmed to be a hardware flaw by engineers, as well as a Google employee (referred to above). But both state that it is common for this type of hardware flaw to be patched with software and it is likely that many devices you already own have such patches in place without you knowing it.
What you can do
Wait for the update to arrive on your Galaxy Nexus. Google is slowly rolling out a fix to all handsets right now. Make sure you have internet or data connection for the update and have your phone in a charger just in case while updating.
Have it on mine
bought from Phones4u in the Trafford centre, Manchester
This looks really bad. While I am sure many people who don't have this problem won't even bother to vote in this thread, the fact that there's just one vote for someone who does not have a problem, is a surprise. I expected 50%-50% at worst.
Bought mine from O2 store in Liverpool. Problem continues even after factory reset.
Phones4u market street manchester.
I also posted the problem on Samsung UK Facebook page, those of you who have a problem should post there too so they are made aware of the problem. This might help get to the bottom of things quicker.
https://www.facebook.com/SamsungUK
Anyone reported to Google support forum?
dont have the device yet so would be hard for me to respond when google asks for logs etc. That would be the best thing to do though.
According to this video, it seriously looks like a hardware issue, so letting us know where you got the phone would be even more helpful.
Duddyroar said:
https://www.youtube.com/watch?v=B6xlZFcgPlo&feature=youtube_gdata_player
Click to expand...
Click to collapse
kristovaher said:
According to this video, it seriously looks like a hardware issue, so letting us know where you got the phone would be even more helpful.
Click to expand...
Click to collapse
Thanks for the video.... Looks like I gotta be grateful I can't get the Galaxy Nexus yet. If its sw, i expect an update soon... But something tells me, its a hw issue in a certain batch.
gogol said:
Anyone reported to Google support forum?
Click to expand...
Click to collapse
Anyone know where the Google support forum is?
I haven't noticed any problem with my phone but I have locale installed so I'm not sure if that is masking the problem.
to those trying to replicate, try turning off wifi, then disabling 3G (settings - wireless & networks - more - mobile networks - use only 2G networks). When it connects, get some data going (load a large website for example), or make a call, see if that sets it off.
it may not work 100% of the time (if it's really radio interference, there are a lot of variables) but it seems to be related.
I do have this issue. Got mine at the launch event at the Oxford Street Phones 4U.
Anyway in the other thread it looks like people are narrowing down the problem to something related to 3G or Wi-Fi signal. I think that might be the case since it had only happened to me while I am outside and not connected to Wi-Fi. (I use JuiceDefender to automatically disable Wi-Fi if it doesn't find any known spots)
I got mine from Oxford St. too. Same problem here.
Sent from my Galaxy Nexus using XDA App
had this problem yesterday with my vodafone sim.
been using it with my o2 sim today and not had the issue occur.
doubt the network would be an issue but thought i'ld just throw it in there.
yep, I have the problem too. I got mine from Phones 4 u On the lauch day in Oxford Circus. Hope this is not HW related!
I seem to have this problem intermittently. Thought it was just me doing something wrong.
Got mine from O2 over the phone.
I'm assuming it can be fixed with a software patch.
Im also having this issue. Purchased from phones4u today 19th nov 2011.
Dosnt happen all the time though. It did happen when i had my old desire next to it and was loading spotify on my desire....
What software version does everyone have? Hopefully the next (assuming 4.0.2) will fix it.
I haven't seen this topic show up on this forum and I had a couple of questions so...... im very interested to know what you guys think of AT&T's upcoming NFC program ISIS? Also does anyone know when we can expect it to be available?
AFAIK its launched in two area atm like a pilot program i believe on of the areas is texas the other then name escapes me.
DJSYNTHVIRUS said:
AFAIK its launched in two area atm like a pilot program i believe on of the areas is texas the other then name escapes me.
Click to expand...
Click to collapse
I didn't know that thanks! Im hoping it will be useful.
I just find it stupid that AT&T is dumping Google Wallet in favor of a system that isn't even ready yet.
Way to give us NFC without it really being useful. (I mean, there's Android Beam, which is cool, but not really useful...)
Xodium said:
I just find it stupid that AT&T is dumping Google Wallet in favor of a system that isn't even ready yet.
Way to give us NFC without it really being useful. (I mean, there's Android Beam, which is cool, but not really useful...)
Click to expand...
Click to collapse
Classic AT&T fail...
It really isn't a fail on AT&T's part. Google Wallet isn't doing that fantastic, especially with how few companies are accepting it. Yea, ISIS isn't ready to go yet, however I live in SLC, one of the main areas that ISIS will be launching at in the summer, and at least 1 in 3 stores has already signed on and started preparing for the switch, UTA (the transit system out here) has also signed on and are making adjustments. Once ISIS is out, it will have a much stronger chance of doing well right out of the gate compared to Google Wallet.
Yes, it required a delay for AT&T users before we get to use NFC for payments, however choosing to back a program that now has a strong backing from companies as well as banks/credit card providers, ISIS really was a good decision.
Sure they could have put their eggs in both baskets, but that probably wouldn't have worked out too well, after all, one of the two would have tried to force them into one corner or the other.
It is not just AT&T. The whole ISIS initiative is a joint venture between AT&T, T-mobile, and Verizon. That is why when the Google Wallet first launched it could only be used on the Samsung Galaxy Nexus from Sprint.
orionl said:
It really isn't a fail on AT&T's part. Google Wallet isn't doing that fantastic, especially with how few companies are accepting it. Yea, ISIS isn't ready to go yet, however I live in SLC, one of the main areas that ISIS will be launching at in the summer, and at least 1 in 3 stores has already signed on and started preparing for the switch, UTA (the transit system out here) has also signed on and are making adjustments. Once ISIS is out, it will have a much stronger chance of doing well right out of the gate compared to Google Wallet.
Yes, it required a delay for AT&T users before we get to use NFC for payments, however choosing to back a program that now has a strong backing from companies as well as banks/credit card providers, ISIS really was a good decision.
Sure they could have put their eggs in both baskets, but that probably wouldn't have worked out too well, after all, one of the two would have tried to force them into one corner or the other.
Click to expand...
Click to collapse
Yes, this is also true. People are blaming just their networks, but Google is at fault here too. They have been very slow in everything that relates to Google Wallet. Getting retailer support isn't actually a problem for Wallet, since it uses PayPass which is already quite popular. But getting more support for phones, especially internationally, is very important, and Google have failed badly at this.
LoveNFC said:
Yes, this is also true. People are blaming just their networks, but Google is at fault here too. They have been very slow in everything that relates to Google Wallet. Getting retailer support isn't actually a problem for Wallet, since it uses PayPass which is already quite popular. But getting more support for phones, especially internationally, is very important, and Google have failed badly at this.
Click to expand...
Click to collapse
Not to mention the fact that Google didn't really pursue adding more carriers early on. First they wanted extensive testing to insure it was ready for a large scale launch. Unfortunately by the time they were ready to bring in everyone else, T-Mobile, Verizon and AT&T had decided not to wait but instead to help start up something new. Honestly, I'm excited because ISIS looks very promising.
Blaming AT&T, or for that matter any carrier other than Sprint, or not waiting on Google to let them in on G-Wallet is kinda pointless, after all no business wants to wait, they want to get in on the action and try to beat the competition.
Google is just piggy back ridding off of PayPass. I'm positive Google Wallet will be accepted by every NFC payment system.
Sent from my Nexus S using Tapatalk 2
DannyB513 said:
It is not just AT&T. The whole ISIS initiative is a joint venture between AT&T, T-mobile, and Verizon. That is why when the Google Wallet first launched it could only be used on the Samsung Galaxy Nexus from Sprint.
Click to expand...
Click to collapse
A slight correction - Google Wallet launched on the Nexus S 4G on Sprint in ~September 2011 via an OTA.
There are a few things to understand about the release and development of an application like this.
1) To release an application you have to have it available to devices.
- AT&T, Verizon, and TMobile have basically stopped the release of this app by preventing it from being installed on over 80% of the phones in the US.
2) Wallet is just as good as any other app out there, and could be better with a large company like Google behind it.
- Knowing that they would not be able to install on the majority of phones, development probably got put on the back burner.
3) AT&T, Verizon and TMobile in may ways have jointly killed the Wallet project since Google decided not to go to court to fight for the app to be released on their networks.
4) The Wallet application CAN run on any network, it is just software.
5) In no way is Google responsible for the success or lack of it with Wallet. In this case, they tried to release it with the intention of having it on all Nexus phones and the carriers stopped it.
crimsonconcepts said:
5) In no way is Google responsible for the success or lack of it with Wallet. In this case, they tried to release it with the intention of having it on all Nexus phones and the carriers stopped it.
Click to expand...
Click to collapse
Google are not obliged to block Wallet from showing up in the Play Store for certain networks. Like you said, Wallet will work on any network.
Apple would have no trouble installing their own Wallet solution, regardless of the networks' reluctance. It's because Google are '*****es' to the networks - they do whatever the networks tell them to. That's why their own 'pure' Google devices like the Verizon Nexus have bloat and branding on them. That's never been the case with Apple. Apple puts their foot down, and the networks have no choice but to comply with Apple. It's not the same for Google. They're pushovers.
Google could of course release Wallet in the European markets, where they already have money handling licences for the web version of Google Wallet and where consumers aren't so heavily reliant on networks when purchasing phones. But they haven't done this.
So, yes, the eventual failure of Google Wallet will be down to Google.