Jump to content

New update for Evo 4G LTE


Jaggrey

Recommended Posts

I tried from navigation directly and it still crashes. I think Google might have to release an update to the maps app as this as been reported on the s3 as well after JB update....

It's weird because on my wife's S3 the Google Nav works fine, post update. But I did see that some Verizon S3 users were having the same problem as us.

I didn't connect in a fringe 4G area where I usually connect, twice. Hope its not a trend.

I've noticed this also, but I'm waiting to give it more time to see what happens.
Link to comment
Share on other sites

It's weird because on my wife's S3 the Google Nav works fine, post update. But I did see that some Verizon S3 users were having the same problem as us.

I've noticed this also, but I'm waiting to give it more time to see what happens.

 

Mine has been connecting to LTE just fine.

Link to comment
Share on other sites

My LTE has always sucked. I haven't had a chance to test post update.

 

The only problem I've ever had with navigation is when network throughput sucks.

 

Prox sensor problems? huh? I've never had a problem there.

Link to comment
Share on other sites

Its not a hardware issue and a factory reset does not fix it. There is a thread over on android central if you want more details. In summary, everything worked fine with ICS and now it doesn't.

 

I went and read the thread. If it doesn't affect every phone, and some (but not all) people running custom ROMs like CM 10 have the same problem, and wiping the phone and reinstalling to a baseline, factory-fresh state where it is known to work on other Evo LTEs doesn't fix the problem, it has to be a hardware problem with specific phones by definition. Just because new software exposes the underlying hardware problem doesn't mean it's not actually a hardware problem.

Link to comment
Share on other sites

One more thing I just found, you can now update your voice mail app by going to settings. It changed the theme a little bit, but now you can have white or black background if you decire.

 

 

I had to manually download a new Voicemail app before I could do it.

Link to comment
Share on other sites

Just tried the suggested maps work around by putting Nav in 2D mode and no kidding it actually worked for me. I have tried every other 'fix' with no luck until now. Your mileage may vary but tap the compass to try toggling modes.

 

Sent from my EVO using Tapatalk 2

 

 

Link to comment
Share on other sites

I think this update is a step backwards in terms of LTE connectivity. In areas where I used to automatically connect to LTE I no longer do, i have to use the Airplane mode toggle again. This really sucks, is there a way to roll back to the previous update?

Link to comment
Share on other sites

I think this update is a step backwards in terms of LTE connectivity. In areas where I used to automatically connect to LTE I no longer do, i have to use the Airplane mode toggle again. This really sucks, is there a way to roll back to the previous update?

If you are S-OFF you can.
Link to comment
Share on other sites

After several days I see a slight difference (if any) in getting onto LTE. I did prefer how it hopped onto one more quickly before this last update. I have noticed that my battery life has been significantly better, like back to how it was before the Jellybean update. If maybe it was scanning too often before and that affected battery life, I think how it is now is a nice balance.

Edited by Jaggrey
Link to comment
Share on other sites

I went and read the thread. If it doesn't affect every phone, and some (but not all) people running custom ROMs like CM 10 have the same problem, and wiping the phone and reinstalling to a baseline, factory-fresh state where it is known to work on other Evo LTEs doesn't fix the problem, it has to be a hardware problem with specific phones by definition. Just because new software exposes the underlying hardware problem doesn't mean it's not actually a hardware problem.

 

I don't think so. You are operating under the assumption that each evo uses the exact same components.

 

My bone stock EVO 4G LTE can't run nav, it crashes. I tried a factory refresh RUU and it didn't fix. I know 4 people with evo, 2 people have problems since the update, two people don't. All are stock, non-rooted. All worked perfect prior to JB update.

 

My guess is that HTC uses different component vendors for some part that has a bad driver and makes nav crash - dunno though. If I run non-JB, no nav crash.

 

Sounds like a software issue to me :-/

Link to comment
Share on other sites

I don't think so. You are operating under the assumption that each evo uses the exact same components.

 

My bone stock EVO 4G LTE can't run nav, it crashes. I tried a factory refresh RUU and it didn't fix. I know 4 people with evo, 2 people have problems since the update, two people don't. All are stock, non-rooted. All worked perfect prior to JB update.

 

My guess is that HTC uses different component vendors for some part that has a bad driver and makes nav crash - dunno though. If I run non-JB, no nav crash.

 

Sounds like a software issue to me :-/

 

Still very strange that navigation is crashing for you. I ran nav back and forth to KC this weekend, starting it from the app drawer, and starting it from Google maps, and couldn't cause it to crash. Worked perfectly.

Link to comment
Share on other sites

Still very strange that navigation is crashing for you. I ran nav back and forth to KC this weekend, starting it from the app drawer, and starting it from Google maps, and couldn't cause it to crash. Worked perfectly.

 

It crashes for me as well. It will work for a few minutes then the screen will freeze, while still giving turn by turn information by voice, then the whole thing will just lock up. I can use any other navigation app just fine though.

Link to comment
Share on other sites

It crashes for me as well. It will work for a few minutes then the screen will freeze, while still giving turn by turn information by voice, then the whole thing will just lock up. I can use any other navigation app just fine though.

 

It froze up on my GS3 last night, but my EVO didn't have any problems.... :scratch:

 

I was actually getting really frustrated with my GS3. The screen kept freezing, it was still running, but frozen. I don't use the voice, it annoys me lol. If I hit the home button and then came back into the program it would work for a bit, but then it would freeze again.

Link to comment
Share on other sites

I don't think so. You are operating under the assumption that each evo uses the exact same components.

 

My bone stock EVO 4G LTE can't run nav, it crashes. I tried a factory refresh RUU and it didn't fix. I know 4 people with evo, 2 people have problems since the update, two people don't. All are stock, non-rooted. All worked perfect prior to JB update.

 

My guess is that HTC uses different component vendors for some part that has a bad driver and makes nav crash - dunno though. If I run non-JB, no nav crash.

 

Sounds like a software issue to me :-/

Interesting theory. Maybe you should check the build dates of your friends phones and start to test that theory. Just to start you off. I have a held up at customs on release day EVO and I have had none of the issues that you detail.
Link to comment
Share on other sites

Proximity sensor issue has been fised, but now my LTE connections are slower to connect and the USB debug autoconnect issue is still here. I'm still having issues with auto spacing in internet searches. very strange, didn't do that before the JB update. I did a hard reset a while ago just fyi, so i'm lost on this.

Link to comment
Share on other sites

i noticed the LTE connection difference as well. i looked into the LTE scan timer and BSR Max timers and noticed they had changed after the maintenence release. i cant remember the values it set when JB was released, but i "think" they were higher with this maintenance release. i set mine back to 1 and 1, and have the same quick connect and long hold time as i did with the original JB release. my wife's takes longer to connect and disconnects easier. i have not changed her settings yet.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...