I updated to the latest AT&T ROM (via Kies) after the update I can no longer get a GPS lock (picked up one lock after 2 hours). After reading several posts it would appear folks were / are having the same issue on the L5 ROM.
Would it be reasonable to exchange the (warranty) phone for another one or do you think I will get the same issue on the next one?
- GPS worked fine while on Gingerbread
Thanks
I'm too having same problems. Turning phone off then on seems to help some. Sigh
Sent from my GT-P7510 using Tapatalk 2
XDA is no longer worth my time.
So I'm asking to confirm whether this is a bug or a problem with my phones hardware. Any time I'm on WiFi for an extended period of time and then turn it off my mobile network won't connect. The only way to fix it is with a reboot and then it connects immediately. My wifes phone is completely stock and she doesn't have this issue. I'm rooted with s-off.
Sent from my EVO using Tapatalk 2
btbamzao said:
So I'm asking to confirm whether this is a bug or a problem with my phones hardware. Any time I'm on WiFi for an extended period of time and then turn it off my mobile network won't connect. The only way to fix it is with a reboot and then it connects immediately. My wifes phone is completely stock and she doesn't have this issue. I'm rooted with s-off.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
i fought with that problem ever since i've had the phone, installed the update released yesterday and it's fixed.
http://community.sprint.com/baw/com...e/blog/2012/07/11/htc-4g-lte-software-updates
since your wife's phone is stock she probably has benefited from that, you'll have to un-root/return to stock to apply the update or wait until someone here concocts a way for you to apply this update, or at least the radio update that it contains.
dangle79 said:
i fought with that problem ever since i've had the phone, installed the update released yesterday and it's fixed.
http://community.sprint.com/baw/com...e/blog/2012/07/11/htc-4g-lte-software-updates
since your wife's phone is stock she probably has benefited from that, you'll have to un-root/return to stock to apply the update or wait until someone here concocts a way for you to apply this update, or at least the radio update that it contains.
Click to expand...
Click to collapse
I flashed the radios yesterday and still had the issue. Flashed a stock Rom this morning based on the new ota so we will see what happens. The weird thing is my wife didn't have the issue before the ota. Thanks for the reply.
Sent from my EVO using Tapatalk 2
btbamzao said:
I flashed the radios yesterday and still had the issue. Flashed a stock Rom this morning based on the new ota so we will see what happens. The weird thing is my wife didn't have the issue before the ota. Thanks for the reply.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
yeah, it seems just from reading around that some did and some didn't. i almost wonder if it wasn't related to some glitch when applying the previous update. i know that when i first powered on my phone to activate it i briefly saw some message about failing to apply an update or something.
i think the radio update may have only been half of it; seems that some of HTC's performance and power management stuff may have been to blame as well.
i can tell you that it's been several hours over 24 since i did the update and haven't had to reboot the phone once to regain 3G. before i could shut down wifi at any random time through the day and mobile network would sit there churning on "turning on..." now i can turn it off and on at will and it connects pretty much instantly.
Just something the phone does not a bug and
Hit the thanks button
e3d4eva said:
Just something the phone does not a bug and
Hit the thanks button
Click to expand...
Click to collapse
After flashing full firmware package my problem is fixed.
Sent from my EVO using Tapatalk 2
Glad its working now, I'm rooted with Fresh 1.0 since it came out. Only update is PRL. I have always switched instantly to 3G coming off of WiFi. Never had that issue so must be something software related on your cell, I guess confirmed by your update.
Sent from my htc_jewel using xda app-developers app
Just returned from taking care of my bill at a corporate sprint store in Detroit Michigan area, and brought up concerns about issues since jb was released. Before I was able to tell my personal issues since the update the couple techs that were at the front door greeting/mingling with customers, told me they have been notified that a patch is being worked on for the Bluetooth, navigation, proximity sensor, wifi and various glitches others have been reporting. This was all said before I even mentioned those issues that myself and others on this forum have brought up. They've even been instructed to stop doing replacement handsets for people with the issues. So to me it sounds like the issues have been noticed/verified finally and HTC/sprint may be releasing something soon. Sounds legit considering the tech's themselves named off the issues and seemed to know a bit about the problems without me saying anything. Figured I'd pass on this tidbit of info and hopefully it becomes a reality.
Update 01/11 called HTC and they have a bulletin that's been sent out that proximity sensor was specifically being worked on (news for stock users at least)..the nav issue the guy said wasn't a for sure thing because it might be a google dropping the ball thing/capatability issue
Sent from my EVO using xda app-developers app
onefasttreopro said:
Just returned from taking care of my bill at a corporate sprint store in Detroit Michigan area, and brought up concerns about issues since jb was released. Before I was able to tell my personal issues since the update the couple techs that were at the front door greeting/mingling with customers, told me they have been notified that a patch is being worked on for the Bluetooth, navigation, proximity sensor, wifi and various glitches others have been reporting. This was all said before I even mentioned those issues that myself and others on this forum have brought up. They've even been instructed to stop doing replacement handsets for people with the issues. So to me it sounds like the issues have been noticed/verified finally and HTC/sprint may be releasing something soon. Sounds legit considering the tech's themselves named off the issues and seemed to know a bit about the problems without me saying anything. Figured I'd pass on this tidbit of info and hopefully it becomes a reality.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I would guess for the new year. Htc always does a delta patch a few weeks later
Sent from my EVO LTE using xda-developers app
Hopefully this is true. Only issue I'm having is the proximity sensor, so I've been pretty lucky but another update would be nice.
Sent from my EVO using xda app-developers app
Kanes_Inferno said:
Hopefully this is true. Only issue I'm having is the proximity sensor, so I've been pretty lucky but another update would be nice.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Out of curiousity, I know I started another thread on the following topic, but did you just recently get your phone? Like maybe in the last 3 months or so? Trying to find a pattern to the issues and handset batch.
Sent from my EVO using xda app-developers app
i got mine on launch day june 2.. i have proximity sensor problems thats it so far.. i dont use bluetooth or have LTE so dont kno bout that?
onefasttreopro said:
Out of curiousity, I know I started another thread on the following topic, but did you just recently get your phone? Like maybe in the last 3 months or so? Trying to find a pattern to the issues and handset batch.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I got in August, I believe.
I'm on my second phone so if that helps any phone seems to work much better
Sent from my EVO using xda app-developers app
I have to flash back to an ics rom then back to jelly bean while wiping as little as possible just to get mhl-hdmi adapter to work. And sometimes at that. Most of the time I have to reset the phone 3 times, unplug, plug in cable to phone. It just blows balls! I am about to just go back to ics and stay there. Jelly bean or at least this iteration of it sucks. Not to mention the worse battery life? Why are we excited about jb anyway? It looks good and sounds nice, but it is just like its abbreviation (jb) jailbait!
Does anyone else agree with me or are you all on the google strain of bud? Here's my list of issues over ics: Battery hog! Mhl-hdmi previously mentioned, New usb connection manager screwed my car audio. Have to update busybox everytime I reset just so root explorer displays remaining space in sd card.
I will quit my rant now though I guess. No one at sprint or htc or most the people here even give a rats **** about these issues because i obviously must be a noob who cant wipe and flash a rom properly or my phone has issues so I must be retarded or something. Tired of those attitudes on xda. But thats another topic. Good day to u all!
I updated to JB and I don't have any of the issues you are talking about. After hearing some of your experiences I think I will wait until a patch comes out to update my wife's phone.
I like JB on this phone. Google now is a welcome feature. Initially I experienced shorter battery life, but after adjusting the settings in Google Now I would say my battery life went back to normal or possibly even better than before.
The one thing I don't like about JB is the in scrolling background, but all the pluses more than make up for it.
Sent from my EVO using xda app-developers app
@ antonicia
I just tried mhl/hdmi output for the first time since upgrading and it worked after 1 reboot for the phone and tv.
I'm running choclate beans from the mikmik and am using the most popular cable on Amazon for $9
Sent from my EVO using xda premium
@ttown
What settings in Google Now did you adjust to get better battery performance?
Sent from my EVO using xda premium
mito8485 said:
@ttown
What settings in Google Now did you adjust to get better battery performance?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Dude. Nice avatar! KZ FTW!
Google Now doesn't seem to drain my battery at all. I'm wondering if the people that it's draining are in weak signal areas?
Sent from my EVO using xda app-developers app
mito8485 said:
@ttown
What settings in Google Now did you adjust to get better battery performance?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I turned off any cards that would frequently update.
Ex. Traffic, weather and nearby places
I can't say for sure that these consume extra battery, but ever since adjusting the settings my battery has been performing well.
It's currently at 50% after 12h 36m off the charger with medium use.
I wish they would just fix this dam Proximity Sensor. I hate my calls hanging up when it touches my face and how it wont show the screen when I wish to hang up.
The CM10 proximity fix woked for me.
[MOD] [CM10] Proximity Sensor Fix
I tested using Proximity Sensor Finder before and after. Before nothing happened, after it went from 9 to 0 when covered.
I've seen all those issues the MeanBean Thread.
All 4.1 JB Devices Broke Bluetooth Voice Dial. As far I know only 4.2 fixes it.
I'd be really impressed if Sprint released 4.2 let alone any update.
I posted a [MOD] in the development section to get Cyberon to be the Default when you click the bluetooth button and it works great, better than it ever has and no longer relies on the Network. And I'm nolonger forced to keep my contacts in gmail. I prefer keep them only in my work's ExchangeMail account.
Nav has worked for me so far but I have not used it too heavily.
As far as Bluetooth Reliability during a Call JB is MUCH better. ICS would drop bluetooth headset as I passed WIFI HotSpots.
WIFI has been an issue on this device since day 1. JB release doesn't seem much better or worse, but it does seem different, but usable for me. I've had it get stuck once and would not let go of WIFI as I drove away, which jams the whole phone up until you shut WIFI off.
The Proximity Sensor seems to be a calibration issue. My guess is the OTA update might have accindentally wiped each devices calibration or something. You can recalibrate it. The default cal works for people. I have not had the issue or it's not a big enough issue for me to care.
Well I can verify after getting a couple refurbs because of the jb updates/roms having nav crashes (first refurb to replace my new launch date phone being a launch date activated one with nav crashes and faulty strip in touchscreen), I finally have one that the navigation works flawlessly on so far with several jb Roms I tried....the refurb date on this phone was in December with no usage/data etc....and I was the first to activate the phone (maybe damaged casing on phone etc and never was sold)...so the pattern of newer built elte's seems to be a pattern...at least for me...it was a battle to get a working phone but paid off in the end...
Sent from my EVO using xda app-developers app
The other day I wanted to try out the ART run-time in the development section under settings. I let it do the conversion of the apps (20min wait) but noticed after it was done, the phone was not responsive and seemed to be having issues. I jumped on xda and found alot of people were having the same issues as I was, so I reverted back Dalvik run-time. It had to do the app conversion back, which to go alot quicker this time around. I then rebooted and it found more apps to convert back to Dalvik. Ever since doing this, I haven't a single skip..beep or honk when using the spotify in my car like I have been since I got this phone. I'm running the latest stock firmware and I'm rooted.
I fixed my BT issues maybe this will fix yours.
i never had bt issues until i took the new update. now i get the skips in the car that i did not have before.
Sent from my VS985 4G using Tapatalk
It sounds like wiping your dalvik cache is what cured the bluetooth problems you were having.
Sent from my VS985 4G using Tapatalk
Hello, about a month ago my GPS suddenly decided to be garbage and it can't find enough GPS signal unless I'm in COMPLETELY open sky and even then it's slow. So I thought I was just unlucky and I still have warranty, so I'm going to use it, but today this reddit post appeared about the Galaxy S8 https://www.reddit.com/r/Android/comments/in2qbi/many_samsung_galaxy_s8_and_note_8_users_are/
and a LOT of people there are complaining about the same issue I have, so I'm sitting here wondering if having the sd 835 chipset is the cause and somehow Google released some kind of update that ****ed up GPS for us.
To the people still running completely stock android, have you noticed recent problems in GPS signal?
Have you tried clearing and updating your AGPS data? Use an app like this one to do it.
https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2
Sent from my LG-US998 using Tapatalk
kenbo111 said:
Have you tried clearing and updating your AGPS data? Use an app like this one to do it.
https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2
Sent from my LG-US998 using Tapatalk
Click to expand...
Click to collapse
Yep, nothing helps, pretty sure the GPS antenna has issues.