Jump to content

(At Least Some) EVO 4G LTE BlueTooth Connectivity Issues Possibly Solved???


unccjester

Recommended Posts

Hokay so... for weeks, I've been having trouble connecting my EVO to my 2011 Sonata. It would just hang and eventually come up with a wonky error message in a white box, saying it had run out of RAM and wanted me to convert memory, which ended up not working - but my wife's EVO *WOULD* connect. After doing some "helplessdesk" troubleshooting steps, I finally came to the assumption that my Bluetooth unit had died inside the phone, since 4 other people COULD connect to my car for BT & streaming via Pandora *kanyeshrug*. :wacko:

 

The tech guy at the Sprint store had trouble staying connected to a BT headset in the store as well, so he ordered me a new EVO for $35 (no TEP, but we're all still under the 1 year HTC warranty). I get the new unit today, pair it up and what happens? It starts to connect, but as soon as it gets to d/l my address book, what happens??? It HANGS AGAIN!!!!! :td: Once again, the wife's EVO pairs up fine. Ugh! *facepalm*

 

I go through all the BT options on the phone and can't really find any that would affect it. I start narrowing it down to something with the address book vs. possible limitations with vehicle BT / address book simplicity / limitations.

 

Suddenly, it dawns on me - my wife has no interest in (Google) linking her contacts, but I sure do, so I "unlink" all my contacts, go back out to the car, unpair and delete the phone out of my Sonata, and pair it back up... SUCCESS!!!! Pandora plays beautifully now, my address book has once again started downloading, and it pairs up to other BT devices as well!

 

If you are having ANY sort of BT issues with this phone and have Google Linked contacts, break the link on ALL of them and try what you were attempting before. I really hope this works for everyone out there since nobody's come up with a solution yet. Please let me know either way! :tu:

Edited by unccjester
  • Like 1
Link to comment
Share on other sites

So the BT connection locked up again yesterday morning. On the drive to work, I thought about what else was different that was so minor, it felt like I was reaching like a country song. :lol:

 

When I got to work, the only thing I could think of was that my phone's name was partially in lower case, so I renamed it with all uppercase letters and things seem to be fine for the drive home and back into work this morning with the exception of a quick drop here and there. That'd be pretty lame if the problem lied within my car's incompatibility with lowercase letters, but w/e at this point. If that's it, that'd be something else. At any rate, I figure those with BT problems are willing to try anything at this point, so there's one more thing to try.

Link to comment
Share on other sites

  • 5 weeks later...

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

    • Good catch! I meant 115932/119932. Edited my original post I've noticed the same thing lately and have just assumed that they're skipping it now because they're finally able to deploy mmWave small cells.
    • At some point over the weekend, T-Mobile bumped the Omaha metro from 100+40 to 100+90 of n41! That's a pretty large increase from what we had just a few weeks ago when we were sitting at 80+40Mhz. Out of curiosity, tested a site on my way to work and pulled 1.4Gpbs. That's the fastest I've ever gotten on T-Mobile! For those that know Omaha, this was on Dodge street in Midtown so not exactly a quiet area!
    • Did you mean a different site? eNB ID 112039 has been around for years. Streetview even has it with C-band back in 2022 - https://www.google.com/maps/@40.7303042,-73.9610924,3a,24.1y,18.03h,109.66t/data=!3m8!1e1!3m6!1s2ossx06yU56AYOzREdcK-g!2e0!5s20220201T000000!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3D2ossx06yU56AYOzREdcK-g%26cb_client%3Dmaps_sv.share%26w%3D900%26h%3D600%26yaw%3D18.027734930682684%26pitch%3D-19.664180274382204%26thumbfov%3D90!7i16384!8i8192?coh=205410&entry=ttu Meanwhile, Verizon's eNB 84484 in Fort Greene has been updated to include C-band and CBRS, but not mmWave. I've seen this a few times now on updated Verizon sites where it's just the CBRS antenna on its own, not in a shroud and without mmWave. Odd.
  • Recently Browsing

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