Related
hey guys, I'm about to trade my htc desire for a nexus one and have read up on a few problems, and I wanted to find out first hand from you guys wether they're actually problems, or wether they are a load.
Which leads me to my questions.
Does your nexus one have any of the following problems:
1. trackball gets stuck sometimes
2. the on/off/standby switch has stopped working (or you have had to send it back to be repaired)
3. the touchscreen randomly stops working
4. 3G connectivity issue
5. Wifi problems
6. Proximity sensor sensitivity issue
7. earpiece: insufficient volume
and lastly -
Is there any reason why you would not recommend me selling my desire and buying a nexus?
Thanks,
Brandon
It would be easier to have them numbered
1. Trackball - never heard of it.
2. Power button - never had anything on mine, but there's a good reason to believe there was a faulty batch out there - some had to exchange theirs.
3. Touchscreen - The issue is that it starts "missing" the presses, registering way below. Pressing the power button twice (entering and exiting standby) "cures" it. A real issue, happens very rarely.
4. 3G - opinions are split on it, reported only by vocal minority and only in areas barely covered by 3G, and only long time ago. Personally, never saw anything that could be considered as "issue". Actually, rather good reception and good data rates over bad connections.
5. WiFi - again, depends on what "issue" is. It's not completely flawless, for example, fails connecting to encrypted network w/ Cisco 521G. Haven't had any problems on mine, though.
6. Proximity sensor - never heard of it.
7. Volume - never heard of it.
To the last question - why would you want to do that? You have a device with very similar specs that runs very similar firmware. Froyo is already out for Desire, AFAIK, and that exchange would only bring you the trackball notifications and the future updates (Gingerbread). Is that the reason for you to switch?
P.S. All or almost all of the issues listed above would be similar for both phones, since they're almost identical.
Jack_R1 said:
To the last question - why would you want to do that? You have a device with very similar specs that runs very similar firmware. Froyo is already out for Desire, AFAIK, and that exchange would only bring you the trackball notifications and the future updates (Gingerbread). Is that the reason for you to switch?
P.S. All or almost all of the issues listed above would be similar for both phones, since they're almost identical.
Click to expand...
Click to collapse
Thanks for the reply!
The problem is that the there are only about 4 chefs cooking for the desire (and about 5 others uploading their own version of the 4 roms). And the battery life on the new froyo ROMs are terrible. I used up the whole battery in about 6 hours with 3g not enabled, and brightness at the minimum.
and there seems to be much more support for the nexus. (XDA support that is)
+ there are much more cases available for the nexus, I think it looks better, and I really love the idea of the trackball and how it can change colors
P.S I forgot to ask how are the capacative buttens?
Some have said they don't exactly work (you have to press them a few times before it works)
I remember reading somewhere that you have to press them a bit above the buttons and they work fine. Is this true? or are some devices just randomly screwed?
Thanks,
Brandon
No to all.
Atleast I didn't notice
Any reason not to just keep the Desire? The n1 is great but the Desire is nearly identically and slightly better in some ways.
brandon1108 said:
hey guys, I'm about to trade my htc desire for a nexus one and have read up on a few problems, and I wanted to find out first hand from you guys wether they're actually problems, or wether they are a load.
Which leads me to my questions.
Does your nexus one have any of the following problems:
1. trackball gets stuck sometimes- Never had this problem......
2. the on/off/standby switch has stopped working (or you have had to send it back to be repaired)- Um, not for me.... But I have heard this happening to people.
3. the touchscreen randomly stops working - NEVER ever has this happened
4. 3G connectivity issue - I only use wifi since it's everywhere. More efficiant and faster!
5. Wifi problems - None for me.
6. Proximity sensor sensitivity issue - Nope
7. earpiece: insufficient volume - Nope, I find it too loud sometimes. But, I do have sensative hearing.
and lastly -
Is there any reason why you would not recommend me selling my desire and buying a nexus? No reasons honestly. They are both pretty similar except for support and design as well as a few other diffs. The only thing I like about the desire is it's hardware keys and chin
Thanks,
Brandon
Click to expand...
Click to collapse
brandon1108 said:
Thanks for the reply!
The problem is that the there are only about 4 chefs cooking for the desire (and about 5 others uploading their own version of the 4 roms). And the battery life on the new froyo ROMs are terrible. I used up the whole battery in about 6 hours with 3g not enabled, and brightness at the minimum.
and there seems to be much more support for the nexus. (XDA support that is)
+ there are much more cases available for the nexus, I think it looks better, and I really love the idea of the trackball and how it can change colors
P.S I forgot to ask how are the capacative buttens?
Some have said they don't exactly work (you have to press them a few times before it works)
I remember reading somewhere that you have to press them a bit above the buttons and they work fine. Is this true? or are some devices just randomly screwed?
Thanks,
Brandon
Click to expand...
Click to collapse
Ugh, I do have issues with the capacitive buttons. Like I said above, I envy hardware keys. It's not that they don't work, they just arent calibrated. You need to touch way above where they are for them to register. If you press the button where its placed exactly they don't work.
NOTE: I should let you know about all the cool things the Menu button does (second button with the lines) I just found out about the Menu button on my Nexus Lol!
I would do that trade and not have any issues at all. The nexus is The most active device right now and will be thru this year at least. Those problems you listed are not a big deal, the power button only fails for some people. Use track ball wake and you have nothing to worry about. Everything else is not really a problem.
brandon1108 said:
P.S I forgot to ask how are the capacative buttens?
Some have said they don't exactly work (you have to press them a few times before it works)
I remember reading somewhere that you have to press them a bit above the buttons and they work fine. Is this true? or are some devices just randomly screwed?
Thanks,
Brandon
Click to expand...
Click to collapse
They're all screwed equally All the capacitive buttons register too high, so you have to press higher to hit them. At least they're consistent.
not a single mention of white notification burn-in. seems common.
brandon1108 said:
Does your nexus one have any of the following problems:
1. trackball gets stuck sometimes
3. the touchscreen randomly stops working
7. earpiece: insufficient volume
Thanks,
Brandon
Click to expand...
Click to collapse
yup.
1. get stuck on going "down". kind of annoying but a spazz around with it fixes it.
2 yup, cant get it to unlock sometimes.
3, sort of. wouldnt mind it louder and of better quality. More depth.
mtl171 said:
not a single mention of white notification burn-in. seems common.
Click to expand...
Click to collapse
:O I remember someone talking about it in the desire forum - If I use a black notification bar I should be fine right?
Brandon,
Does your nexus one have any of the following problems:
1. trackball gets stuck sometimes No
2. the on/off/standby switch has stopped working (or you have had to send it back to be repaired) Yes & Yes gettting repaired by HTC as we speak.
3. the touchscreen randomly stops working No - used to occasionally before Froyo but not anymore
4. 3G connectivity issue No
5. Wifi problems No
6. Proximity sensor sensitivity issue No
7. earpiece: insufficient volume No
8. how are the capacative buttons? Fine, If you swipe them downwards in the opposite direction but the same manner as you would, to select the notification bar. If you tap them with the pad of your finger instead of the point it also a non issue. OTOH tapping with the point of your finger you just need to tap slightly below.
PurpleSmurfLlama
I disagree and do not think the majority of power button failures are due to poor maintenance. Is your poor maintenance theory just a hunch perhaps? I keep my phone nice and clean, no obvious crap beneath the button. In another thread someone who had a failing power button dismantled his phone an reported the power button presses a switch that is connected via a ribbon cable to a circuit board. No amount of cleaning these fixed it for him. Furthermore people who have had their "power buttons" repaired have reported that all these these items appear to have been replaced when they get their repaired phone back from HTC. Same phone comes back with new IMEI because the circuit board has been changed as part of the fix. To me this suggests that on the faulty units the issue goes deeper than just the button and a users maintenance of it. I am just hoping that the FIX is permanent.
I've had my Nexus One for a few months now and I can't say I've had any of those problems, well my WiFi sometimes just disconnects, but I think that's just to do with the distance between my room and the router. As for button and trackball problems there's been none, even after a horrifying ordeal where a friend spilt beer on my N1 then instantly after in the panic I dropped it in the sand :/
The swap in my opinion can only be based purely on aesthetics, IMO the N1 is nicer, not being biased, the Desire is beautiful, I just think the N1 is more sleek. Hope this helps even a little.
Sent from my Nexus One using XDA App
brandon1108 said:
:O I remember someone talking about it in the desire forum - If I use a black notification bar I should be fine right?
Click to expand...
Click to collapse
Yes exactly, just use black color and you'll be fine. That white is such a horrible color anyway.
brandon1108 said:
Does your nexus one have any of the following problems:
1. trackball gets stuck sometimes
2. the on/off/standby switch has stopped working (or you have had to send it back to be repaired)
3. the touchscreen randomly stops working
4. 3G connectivity issue
5. Wifi problems
6. Proximity sensor sensitivity issue
7. earpiece: insufficient volume
Click to expand...
Click to collapse
How about a poll?
1. no
2. switch is "soft" on the replacement I just received (was fine on original phone and 1st replacement)
3. no
4. YES! RECEPTION IS A BIG PROBLEM! AS IS 3G CONNECTIVITY (3 bars and websites won't load WTF?)!
5. no
6. no
7. yes
maybe add:
8. PINK screen - YES. Just keep asking HTC for replacements, screw them for their poor quality control.
9. camera color tint (blue for me) - YES. Ok for me ... but I made go another replacement binge if I find anything at fault with this phone.
10. I also experience bad call quality - got fixed by the replacement.
1. Trackball - NO problems here.
2. Power button - NO problems here.
3. Touchscreen Unresponsive - Roughly once or twice a month. I put it to standby and back, and it's fixed. I've noticed that only certain ROMs do this. I never had the problem on FRF50 or FRF83, but I have once in a while on FRF91.
4. 3G Connectivity - NO issues.
5. Wifi - NO issues.
6. Proximity sensor - NO issues.
7. Earpiece volume - NO issue, but I have always had one of Pershoot's kernels installed, which includes an "audio fix."
I would have no hesitation recommending a nexus. Though, if you're a gamer, I'd say get a Galaxy S phone because of the better GPU.
#3 is the only one that consistently pisses me off.. all the other ones are software and can and are fixed with different roms.
Hi,
I have my sgs about 2 months and I'm very happy with it. The only problem I have is, that sometimes there are strange displayinterferences.
It looks like there are moving waves from top to down.
Does anybody have this troubles too and has a solution for it?
Or is it an hardware error? The problem is that the error isn't reproducable.
Maybe somebody can help me, please!
Thanks in advance
spyro
I think I have also noticed that once or twice. I believe it can be seen when you have the android drop down menu (notifications etc) open and you start or stop WiFi. It must be some kind of interferance with wifi hardware. Normal wifi operation does not cause it, only the startup of the WiFI which lasts one second or so.
Yeah, i think this could be true. I also see it often, when I open die Notification bar. But I also have the same interferences, when I am working in apps. Maybe also the 3G connection could be the reason? Does anybody else have this problem.
Is this a problem, which I have to life with or could this be an error of the hardware(warranty)?
http://forum.xda-developers.com/showthread.php?t=753402
I have the same problem. Never on wifi tho.
Which firmware are you using?
Hi,
my firmware is I9000AUJF1(A1 branded from Austria). I don't know if the problem in your posted thread is the same. The interferences I mean only exist one or two seconds. There are horizontal dark lines which moves from top to the bottom. After some time everything is OK again. It looks like anything interfers the display(wifi, 3g?).
The problem of warranty is, that I'm not able to show the problem, because it's not reproducable.
Screen flickering under WiFi data transfer
I noticed this problem a couple of days ago.
Whenever there is some data transfer going on over WiFi, wherever I am browsing or some service syncs up the screen starts flickering and I have what I can describe as faint scan lines crossing the screen vertically like there is some sort of interference.
These are mostly noticeable on white and light grey backgrounds.
I have gone trough 2 firmware updates currently being on stock JPK rooted.
I have searched around on google and found on some forum one guy that was saying the cause is an interference between the WiFi module and the screen refresh rate.
Has anybody encountered this problem or these symptoms ?
Is there somebody around more knowledgeable in this issues that can confirm that this is a hardware problem ?
wow! , you might have a defective phone then.
I use WiFi very often, Wireless N at aprox 87 Mbps
that should be high enough to reproduce the problem you experienced, if i had a faulty screen
the description of the scan line reminds me of interference when you are in close proximity with another LCD or CRT screen causing the distortion field
OMG, I get this too. Usually happens on boot or when I'm browsing a data heavy website or using Android market. Are our phone defective? Does anyone else have this problem? I wonder how common it is.
does the scan line comes from bottom up
or goes from top to bottom?
very slowly or fast?
if you are pluged in and charging, also are you in a 120v or 240v?
AllGamer said:
does the scan line comes from bottom up
or goes from top to bottom?
very slowly or fast?
if you are pluged in and charging, also are you in a 120v or 240v?
Click to expand...
Click to collapse
They tend to be random and I'm on battery power atm. Also they're quite fast but don't last very long. They'll start then stop then start etc ..
Hi,
just for your information. I've sent my phone to samsung on friday. Maybe they find the error. I report, if there are new information.
Yep i have the same problem. Can t find the source though....
Sent from my GT-I9000 using Tapatalk
The lines appear from top and travel the screen fast.
Imagine a TV who for a second has problem with reception.
I am on 240 V.
Also the issue is much more noticeable when not plugged in.
If I have the phone plugged in its barely noticeable.
I will try to call the service and ask about this issue. I have a strong feeling that this is a hardware issue. But Besides the screen being defective I also think about the battery. Maybe when in high load (WiFi) it's voltage varies and affects the screen.
It seems if I uncheck Power saving mode in Settings>Display and also uncheck Automatic brightness things improve a bit.
segun_aduba said:
The lines appear from top and travel the screen fast.
Imagine a TV who for a second has problem with reception.
I am on 240 V.
Also the issue is much more noticeable when not plugged in.
If I have the phone plugged in its barely noticeable.
I will try to call the service and ask about this issue. I have a strong feeling that this is a hardware issue. But Besides the screen being defective I also think about the battery. Maybe when in high load (WiFi) it's voltage varies and affects the screen.
Click to expand...
Click to collapse
Another issue to worry about .. God starting to think about selling this phone and getting something else. Stuck in a 2 year contract though
some one already reported this on another topic
it does seems that some version of the phone are prone to WiFi interferance
we still haven't found out what causes it exactly
for example i can not replicate the issue on my phone when using WiFi
found it
http://forum.xda-developers.com/showthread.php?t=793944
Cant reproduce it.
Not that I'm unhappy with it...
If this is a hardware issue Samsung should replace my phone. I am waiting though a little bit before calling the service to make sure that it is a hardware problem.
If I find that it can easily be fixed with a software fix, it's not worth the hassle of trying to replace it.
can anyone in North America confirm this issue?
i got a huntch it might be an Europe only issue related to the high voltage of the electric interferance nearby, like lights, tv, radio, wifi, etc.
I have had continuous issues with the Droid 3. One of my biggest issues is that the GPS seems completely unstable. I have tried turning on/off GPS options, etc...
Weather I try to use Google Maps or another application such as Endomondo, it cant maintain a lock. It seems to be able to locate me within 12 - 30 feet and then within a mile!!!
Using an application like Endomondo (running, cycling, etc), is completely useless. It can't track my location at all and when it does lock on, it only holds for a few seconds and then gone again.
I took the phone in to Verizon with a complaint about the GPs and screen issues (http://forum.xda-developers.com/showthread.php?t=1239980) and the rep said both were normal for this phone...
Has anyone figured out a way to resolve this problem?
I, too, have the same issue with GPS. I use SportyPal Pro, and cannot use my Droid 3 when running/walking. I can go for a 5 mile run, and SportyPal will show I had ran 6 miles. I can run north to south in a straight line, and when finished, SportyPal will show that I went east and west as much as 400-500 feet off of that straight line and because of that can add anywhere from .1 miles to .5 miles to that 1 mile run.
It is so unreliable that I will use my older decommisioned Droid2 to run with. It works perfectly with the same software.
If anybody has any suggestions, I'm all ears.
bishop0114 said:
I have had continuous issues with the Droid 3. One of my biggest issues is that the GPS seems completely unstable. I have tried turning on/off GPS options, etc...
Weather I try to use Google Maps or another application such as Endomondo, it cant maintain a lock. It seems to be able to locate me within 12 - 30 feet and then within a mile!!!
Using an application like Endomondo (running, cycling, etc), is completely useless. It can't track my location at all and when it does lock on, it only holds for a few seconds and then gone again.
I took the phone in to Verizon with a complaint about the GPs and screen issues (http://forum.xda-developers.com/showthread.php?t=1239980) and the rep said both were normal for this phone...
Has anyone figured out a way to resolve this problem?
Click to expand...
Click to collapse
Sadly, I have the same issues.
Well with only 3 people chiming in, maybe it is bad hardware?
bishop0114 said:
Well with only 3 people chiming in, maybe it is bad hardware?
Click to expand...
Click to collapse
God, I hope not. I have enough problems with this phone as it is.
No problems with GPS for me
Sent from my DROID3 using xda premium
kshen1 said:
No problems with GPS for me
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
Are you using it for navigation only? Or a similar application for running/walking?
The reason I ask is because I do not notice a problem during navigation. It works great for that without any problems. Until I get to downtown Chicago. I almost expect problems there. Even with my Droid2.
i've only had issues with my gps in areas with lte. when im at college im in a city with lte support and my gps doesn't work (my friend who has an X also has issues with his gps when in areas with lte). when im home where there isnt lte support my gps works fine.
No it's not hardware mine works flawlessly and almost instantly fixes position, tho i have modded the gps.conf found in the etc folder. Details for tweaking this for your region can be found here:
http://forum.xda-developers.com/showpost.php?p=13537801&postcount=1
Many thanx to 75markus for this.
Since we don't have a recovery yet to flash a zip you will need to edit the gps.conf file manually.
Oceanic region can be found in my sig below apart of my camera mod.
-smc
The problem I was having with the GPS from Day 1 is that I would occasionally notice that it would not start up at all when openning a GPS-dependant app (such as Maps or Weatherbug, etc). Whenever that happened, I would have to restart the phone, and then the GPS would be able to initialize again... at least, for a while.
Eventually, I was digging around in the setting and found the "VZW location services" option under "Location & security settings". I unchecked that option and, ever since, I've had no problem with the GPS. It seems that th VZW-based location services were causing the problem. Of course, since then, I've rooted and frozen all of the VZW bloat, so I might be able to turn that option back on with no ill effect. Still, it was as simple enough fix.
My issue might not sound exactly the same as yours, but you could give this a try and see if it helps.
-SR-
I'm not having any GPS issues on my phone. Perhaps it's based on the area your in?
I know it's satellite but.. just a guess.
WarER4X said:
The problem I was having with the GPS from Day 1 is that I would occasionally notice that it would not start up at all when openning a GPS-dependant app (such as Maps or Weatherbug, etc). Whenever that happened, I would have to restart the phone, and then the GPS would be able to initialize again... at least, for a while.
Eventually, I was digging around in the setting and found the "VZW location services" option under "Location & security settings". I unchecked that option and, ever since, I've had no problem with the GPS. It seems that th VZW-based location services were causing the problem. Of course, since then, I've rooted and frozen all of the VZW bloat, so I might be able to turn that option back on with no ill effect. Still, it was as simple enough fix.
My issue might not sound exactly the same as yours, but you could give this a try and see if it helps.
-SR-
Click to expand...
Click to collapse
I have been experiencing the exact same problem and temporary solution (restarting) since day 1, on both my first and second droid 3's. Difference is, I've had VZW location services unchecked since around the time I first got the phones, and I am still experiencing the problem... even as recently as last night. I just double-checked the setting, and indeed, VZW location services is stil unchecked.
Once I have lock I usually have no problem continuously using GPS. Last night, I tracked a two and a half hour walk using the My Tracks app, including a 45 minute stop for dinner indoors. For the first 10 minutes, it couldnt find a signal, so I restarted. It got a lock almost instantly following the restart and never lost it after that. I had the app running for the whole excursion. As expected, it got a little confused while I was inside, but automatically picked the signal right back up when I got back outside and tracked my entire walk back home.
a_lazy_dude said:
I have been experiencing the exact same problem and temporary solution (restarting) since day 1, on both my first and second droid 3's. Difference is, I've had VZW location services unchecked since around the time I first got the phones, and I am still experiencing the problem... even as recently as last night. I just double-checked the setting, and indeed, VZW location services is stil unchecked.
Once I have lock I usually have no problem continuously using GPS. Last night, I tracked a two and a half hour walk using the My Tracks app, including a 45 minute stop for dinner indoors. For the first 10 minutes, it couldnt find a signal, so I restarted. It got a lock almost instantly following the restart and never lost it after that. I had the app running for the whole excursion. As expected, it got a little confused while I was inside, but automatically picked the signal right back up when I got back outside and tracked my entire walk back home.
Click to expand...
Click to collapse
When you look at your walk on the map, is it true to where you actually walked? If I do that same walk on my phone, it will show me deviating off course as much as a 1/2 block and then back. I can tolerate that deviation once and maybe twice during my runs/walks. However, mine does it the majority of the time, adding bogus mileage to my walks/runs. In an hour's time, it will deviate approximately 20-30 times.
eallison978 said:
When you look at your walk on the map, is it true to where you actually walked? If I do that same walk on my phone, it will show me deviating off course as much as a 1/2 block and then back. I can tolerate that deviation once and maybe twice during my runs/walks. However, mine does it the majority of the time, adding bogus mileage to my walks/runs. In an hour's time, it will deviate approximately 20-30 times.
Click to expand...
Click to collapse
Just took a closer look at the track it recorded. I definitely do see these kinds of deviations, but they seem to only be in areas where I think it'd be reasonable to expect them. I live in a suburb, so I don't have any tall building to mess with the GPS reception, instead, I have somewhat steep hillsides. It seems I get a fair amount of deviation in the (significantly) hilly areas (it looks like I was walking down people's driveways, then across their front yards, when in reality I was just walking more or less straight down the sidewalk), but in the flat areas the line has almost no significant deviations, just some minor noise. Next time, at the risk of my fiance calling me a geek, I'll take my Droid 1 along for the trip, and see how the two records compare.
a_lazy_dude said:
Just took a closer look at the track it recorded. I definitely do see these kinds of deviations, but they seem to only be in areas where I think it'd be reasonable to expect them. I live in a suburb, so I don't have any tall building to mess with the GPS reception, instead, I have somewhat steep hillsides. It seems I get a fair amount of deviation in the (significantly) hilly areas (it looks like I was walking down people's driveways, then across their front yards, when in reality I was just walking more or less straight down the sidewalk), but in the flat areas the line has almost no significant deviations, just some minor noise. Next time, at the risk of my fiance calling me a geek, I'll take my Droid 1 along for the trip, and see how the two records compare.
Click to expand...
Click to collapse
I've attached screenshots from two runs. D2 is this morning's run with my Droid 2. It's flawless. D3 is the last run I did with my Droid 3. Looking at it you can understand my disgust with it. Ignore the big missing section from both shots. I wouldn't want anyone knowing the exact location of where I live. Someone might come steal my Droid 3.
eallison978 said:
I've attached screenshots from two runs. D2 is this morning's run with my Droid 2. It's flawless. D3 is the last run I did with my Droid 3. Looking at it you can understand my disgust with it. Ignore the big missing section from both shots. I wouldn't want anyone knowing the exact location of where I live. Someone might come steal my Droid 3.
Click to expand...
Click to collapse
WOW... That is awful but a great example of the concern with this phone. You are actually doing much better than me. Mine is only able to triangulate down to about 20 feet and then it bounces between 20 and 300 feet!!!
I am going to call VZW today and see about a replacement phone but I doubt it will resolve the problem.
I just called VZW and once again, they said the accuracy was normal... They said none of their phones can lock on with the accuracy I described and if it has, I have been lucky. He said their phones are only accurate within 500 feet!
I explained to him that with that accuracy, it would be totally useless to use as a navigation device...
He looked through their documentation and said he has no record of other people having issues with the GPS... He also said he has no record of the blue tint when taking pictures.....
Oh well. I hope the replacement fixes it...
bishop0114 said:
WOW... That is awful but a great example of the concern with this phone. You are actually doing much better than me. Mine is only able to triangulate down to about 20 feet and then it bounces between 20 and 300 feet!!!
I am going to call VZW today and see about a replacement phone but I doubt it will resolve the problem.
Click to expand...
Click to collapse
With that kind of change in accuracy, it seems like it isn't using the GPS as all, but just the cell towers. Is the GPS logo showing in the notification bar when that is happening? If it's there, is it blinking or solid?
-SR-
bishop0114 said:
I just called VZW and once again, they said the accuracy was normal... They said none of their phones can lock on with the accuracy I described and if it has, I have been lucky. He said their phones are only accurate within 500 feet!
I explained to him that with that accuracy, it would be totally useless to use as a navigation device...
He looked through their documentation and said he has no record of other people having issues with the GPS... He also said he has no record of the blue tint when taking pictures.....
Oh well. I hope the replacement fixes it...
Click to expand...
Click to collapse
My humble opinion of VZW representatives...they're all full of BS. They're going to tell you what they need to tell you to get your out of the store or off of the phone if you're not buying anything. A representative's main concern is sales. Sell him another phone, renew his contract, add a line, add a feature.
This issue may be better addressed to Motorola directly. I may make that phone call today.
I just got off the phone with Motorola tech support. Same story as VZW gives. There are NO known issues with the Droid 3. I asked about the GPS, the bluish pics the cam takes and battery life. The only thing the tech would say is the phone "needs to be evaluated"
Greetings XDA users! As you can see, this is my first post on this forum. I have registered here in order to get some answers from other users of the HTC One concerning some problems that I have experienced. I have been using the device since more than a week now, and these are the issues I've come across so far, so please let me know which ones of these you are experiencing as well:
1. YouTube audio / video out of sync
I noticed this the first time I used YouTube on my HTC One. Lip sync simply looked horrible while watching some videos. To test if you have this issue as well, you should try something like this video where it can clearly be seen in action: Link (Since I cannot post links due to below 10 post count, simply search YouTube for "BBC HD audio sync test")
2. Simple games lag / do not play smoothly
The first game I tried on my HTC One was Doodle Jump. It's a very simple game, and before purchasing the One, I have read about other recent HTC smartphones having problems with such simple games because some HTC devices don't know how to properly use their GPU/CPU in situations where games don't have high demands. If this is still the case with the HTC One, and not just some issue with my own, it is simply unacceptable. After all, a new flagship smartphone should not have any issues when playing the most simple of games that any old android smartphone can do perfectly.
Note: I have already tried to cure both of these problems by doing it with / without power savings enabled. I have also tried with / without Beats, Bluetooth, NFC and so on. Nothing helps.
Please let me know if you are experiencing these two issues on your HTC One as well.
Other issues and annoyances I have noticed, that come to mind right now:
3. Blinkfeed share bar at the bottom of the screen is very annoying, and apparently can't be removed at all. It's doubly annoying because sometimes you can hit this bar when trying to use the back button.
4. 3-dot-menu bar at the bottom of the screen in some apps. There even used to be a built-in feature in the setting menu to get rid of this, but HTC seems to have removed this in the final software versions, for questionable reasons.
5. Video camera settings such as 60-FPS-HD or slow motion keep resetting themselves each time the screen gets locked and go back to "Normal".
6. Audio issues (cracks / pops) when using YouTube (maybe other apps as well). This happens especially often with Beats turned on, but I have also heard it happening with Beats off.
7. Odd volume jump that happens around 80% volume when increasing volume while streaming music via Bluetooth. (Volume actually goes down instead of up, and the next step after this sounds much louder than just 2 "clicks" more.)
8. Wifi reception gets a lot worse when covering the upper side of the device with my hand. And by covering I mean holding it normally in landscape orientation, I'm not intentionally trying to smother the signal. This is quite noticeable in areas where the signal is not that strong to begin with, as I've experienced multiple times that I've choked my wifi signal by simply holding it that way to watch some YouTube videos. The wifi bar can jump from 2-3 bars to just the dot by doing this.
I am rather disappointed to see this thread buried on page 3 already without any replies at all. All I asked for is a simple yes-or-no answer if your device also exhibits un-synchronous YouTube playback and/or unsmooth Doodle Jump gameplay.
So I guess this either means that I am the only one experiencing these problems and should promptly return my phone to get a properly working One, or it means people here simply do not notice these problems or accept to overlook them.
(By the way, the Bluetooth volume oddity seems to have been a randomly caused bug, as it was working fine again this afternoon)
I'm having the same issue with YouTube. It's basically unusable, the sound and lip sync gets progressively worse. Tried wiping the app data, re-installing YouTube, disabling Beats. Still no luck, this is the only beef I have with an otherwise excellent bit of tech. I tried the test videos and it looked spot on.
If I watch the same videos on my Asus Infinity there is no problem, so it's definitely the phone. I'm pretty much out of ideas.
YouTube audio / video out of sync
is indeed very horrible.....
ive never experienced anything like that, are you guys running stock rom?
For me, it's everything BUT YouTube. Games, apps, anything, there's about a 1/4 second delay between the on-screen action and when I hear the accompanying sound. Audio sync is one of my pet peeves, so this drives me absolutely crazy. I can only assume there's some kind of processing going on with the audio that's causing it, but damned if I can figure out what it is. The only audio switch I've seen to turn stuff on and off is Beats, and that has no effect on the latency.
I'm running stock ROM. Friend of mine with a ROMd unit says his doesn't do it.
I'm also having issues with the YouTube...
Sent from my LG-P768 using xda app-developers app
So is there no solution? I'm have the same problem...
Sent from my HTCONE using Tapatalk 4
Is anyone else having an issue with the always on display? Not a big deal but occasionally the AOD goes off and the tap to wake function doesn't work. Unlocking/locking the phone fixes it but it reoccurs again randomly through the day.
andrewd71 said:
Is anyone else having an issue with the always on display? Not a big deal but occasionally the AOD goes off and the tap to wake function doesn't work. Unlocking/locking the phone fixes it but it reoccurs again randomly through the day.
Click to expand...
Click to collapse
I was having the same issue when I had the edge notification app installed that makes the screen light up around the camera when you get a notification.
Uninstalled and no issues since
Tap to wake not working for me
Not sure if this is connected but in addition to the always on display/tap to wake issue when I'm in a phone call the screen will stay off even when I move the phone from my ear to hang up, see the keypad etc. Again I have to use the power button to wake the screen. A problem with the proximity sensor perhaps?
andrewd71 said:
Not sure if this is connected but in addition to the always on display/tap to wake issue when I'm in a phone call the screen will stay off even when I move the phone from my ear to hang up, see the keypad etc. Again I have to use the power button to wake the screen. A problem with the proximity sensor perhaps?
Click to expand...
Click to collapse
Do you have any notification or edge lighting apps installed?
Mdizzle1 said:
Do you have any notification or edge lighting apps installed?
Click to expand...
Click to collapse
No, I've not installed any apps like that.
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
czm said:
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
Click to expand...
Click to collapse
This is an odd one - are you using a case? I just had a case through the post this morning and now using the phone with the case the issues have stopped! I'll keep checking through the day but as of now all is good.
andrewd71 said:
This is an odd one - are you using a case? I just had a case through the post this morning and now using the phone with the case the issues have stopped! I'll keep checking through the day but as of now all is good.
Click to expand...
Click to collapse
Not using a case. It's sporadic. Tap to wake works fine for a while and then stops. The issue during calls is constant. Not major issues just niggles.
Not noticed any bugs with ambient display, but it has used 20 percent battery in 21hrs.
Seems a bit high to me, have just turned it off, not worth a 5th of my battery.
czm said:
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
Click to expand...
Click to collapse
Yeah I'm having both issues happen RANDOMLY as well. I'm HOPING Google will put out a fix for these two issues very soon.
Tried working with Google's Tech Support Team via chat earlier on the AOD issue. Tried a few things like clearing the cache of the launcher & restarting in Safe Mode then back to Normal Mode, and it seems to be doing it less but then it just did it again for a short time like an hour ago.
Using a case, no edge stuff, and also using Nova Launcher (though it happened in Pixel Launcher as well).
If anyone finds a fix for this, I would appreciate it too!
RockStar2005 said:
Yeah I'm having both issues happen RANDOMLY as well. I'm HOPING Google will put out a fix for these two issues very soon.
Tried working with Google's Tech Support Team via chat earlier on the AOD issue. Tried a few things like clearing the cache of the launcher & restarting in Safe Mode then back to Normal Mode, and it seems to be doing it less but then it just did it again for a short time like an hour ago.
Using a case, no edge stuff, and also using Nova Launcher (though it happened in Pixel Launcher as well).
If anyone finds a fix for this, I would appreciate it too!
Click to expand...
Click to collapse
Mine is fine for a while them randomly the tap-to-wake won't respond. I had also hoped that the OTA would have addressed, but maybe it is affecting far fewer users than other bugs.
czm said:
Mine is fine for a while them randomly the tap-to-wake won't respond. I had also hoped that the OTA would have addressed, but maybe it is affecting far fewer users than other bugs.
Click to expand...
Click to collapse
Yeah. Seems like more and more people are noticing and like me reporting these various issues to Google. So hopefully the next batch will include fixes for all this stuff.
I have same two problem with AOD, touch to wake up and screen off/on when calling.
DOMIN_ said:
I have same two problem with AOD, touch to wake up and screen off/on when calling.
Click to expand...
Click to collapse
I recommend you guys report these issues to Google so to increase the odds of them coming up with an OTA sooner than later. You can call them or chat with them via this link (as I did). Just scroll down to the bottom and choose your contact preference.
RockStar2005 said:
I recommend you guys report these issues to Google so to increase the odds of them coming up with an OTA sooner than later. You can call them or chat with them via this link (as I did). Just scroll down to the bottom and choose your contact preference.
Click to expand...
Click to collapse
On the pixel support forum they also recommend you report it via settings>about phone>send feedback about device. I think this way it also easily picks up the log files.
I believe the answer to all of your questions lies in a faulty proximity sensor. I was driving myself nuts with all of these issues exactly, and no app was the culprit because I factory reset and still had the issue. I'm going to post a link to a Reddit thread that I found that confirmed my suspicions. on Wednesday of this week I went back to Verizon and traded the phone in and now I have received a phone that works 100% as expected.
Reddit thread.
Good luck all, hope this helps.
czm said:
On the pixel support forum they also recommend you report it via settings>about phone>send feedback about device. I think this way it also easily picks up the log files.
Click to expand...
Click to collapse
Yeah I got an e-mail from the support guy to do that as well after he'd ask that I send a bug report. Just did it regarding AOD not staying on all the time and also.............I noticed that Hold for Me doesn't ALWAYS come up when calling businesses. Two examples include T-Mobile Customer Service & a local major hospital in Chicago. In most cases though, it does. Just an FYI. Not sure if this is something that they will fix, but I think it should come up all the time, or AT LEAST when you're calling an established business of ANY kind.
---------- Post added at 05:30 PM ---------- Previous post was at 05:26 PM ----------
Morpherios said:
I believe the answer to all of your questions lies in a faulty proximity sensor. I was driving myself nuts with all of these issues exactly, and no app was the culprit because I factory reset and still had the issue. I'm going to post a link to a Reddit thread that I found that confirmed my suspicions. on Wednesday of this week I went back to Verizon and traded the phone in and now I have received a phone that works 100% as expected.
Reddit thread.
Good luck all, hope this helps.
Click to expand...
Click to collapse
Very interesting!
I REALLY don't want to send mine back because I've spent so much time setting it up already (and my sister's too lol). I did some changes in the settings so I'll just cross my fingers and hope it works right.
Is there a way to recalibrate the proximity sensor?
RockStar2005 said:
Yeah I got an e-mail from the support guy to do that as well after he'd ask that I send a bug report. Just did it regarding AOD not staying on all the time and also.............I noticed that Hold for Me doesn't ALWAYS come up when calling businesses. Two examples include T-Mobile Customer Service & a local major hospital in Chicago. In most cases though, it does. Just an FYI. Not sure if this is something that they will fix, but I think it should come up all the time, or AT LEAST when you're calling an established business of ANY kind.
---------- Post added at 05:30 PM ---------- Previous post was at 05:26 PM ----------
Very interesting!
I REALLY don't want to send mine back because I've spent so much time setting it up already (and my sister's too lol). I did some changes in the settings so I'll just cross my fingers and hope it works right.
Is there a way to recalibrate the proximity sensor?
Click to expand...
Click to collapse
I don't believe it's a calibration issue. The way mine worked (or didn't as the case may be) was sporadic and seemed to almost be as if the sensor or module was loose? Inside the housing. Quite literally, jostling it around would make it work sometimes. Furthermore, if you download the app in that reddit thread, the proximity sensor tester Link Here, you can sort of gauge yourself if it's actually occurring. With mine, sometimes it would work by swiping my hand over the sensor, the color would change. Other times, the color stayed the same, and as the video showed ,I could put pressure on where the sensor was and change the color. But if it wasn't working, jostling the phone around would sometimes make it work and the color would change.
Additionally in the advanced test in that app, it is supposed to tell you how far away from the sensor an object is. On my (nonworking) phone, that number for distance would be pegged at 0 regardless of how far away my hand was. However if I put pressure on the sensor, it would jump to like 5 cm.
See if your phone is doing these things. If so, I would recommend you get it replaced, as it likely will not work properly otherwise. Verizon deemed this a hardware issue when I swapped phones. Also note that I factory reset twice, and one of those times I imported literally nothing when setting it up. So it wasn't a settings or app issue. I do believe there's a rash of faulty proximity sensors going on here.
Morpherios said:
I don't believe it's a calibration issue. The way mine worked (or didn't as the case may be) was sporadic and seemed to almost be as if the sensor or module was loose? Inside the housing. Quite literally, jostling it around would make it work sometimes. Furthermore, if you download the app in that reddit thread, the proximity sensor tester Link Here, you can sort of gauge yourself if it's actually occurring. With mine, sometimes it would work by swiping my hand over the sensor, the color would change. Other times, the color stayed the same, and as the video showed ,I could put pressure on where the sensor was and change the color. But if it wasn't working, jostling the phone around would sometimes make it work and the color would change.
Additionally in the advanced test in that app, it is supposed to tell you how far away from the sensor an object is. On my (nonworking) phone, that number for distance would be pegged at 0 regardless of how far away my hand was. However if I put pressure on the sensor, it would jump to like 5 cm.
See if your phone is doing these things. If so, I would recommend you get it replaced, as it likely will not work properly otherwise. Verizon deemed this a hardware issue when I swapped phones. Also note that I factory reset twice, and one of those times I imported literally nothing when setting it up. So it wasn't a settings or app issue. I do believe there's a rash of faulty proximity sensors going on here.
Click to expand...
Click to collapse
Hey Morpherios,
Ok.............downloaded that app and tried it out several times. It passed some of the time, but then I'd try it again a few minutes later and it would fail on both tests. Ughh!!
You think even though it passed a few times I still need to replace it?