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

    • Fury Gran Coupe (My First Car - What a Boat...)
    • Definite usage quirks in hunting down these sites with a rainbow sim in a s24 ultra. Fell into a hole yesterday so sent off to T-Mobile purgatory. Try my various techniques. No Dish. Get within binocular range of former Sprint colocation and can see Dish equipment. Try to manually set network and everybody but no Dish is listed.  Airplane mode, restart, turn on and off sim, still no Dish. Pull upto 200ft from site straight on with antenna.  Still no Dish. Get to manual network hunting again on phone, power off phone for two minutes. Finally see Dish in manual network selection and choose it. Great signal as expected. I still think the 15 minute rule might work but lack patience. (With Sprint years ago, while roaming on AT&T, the phone would check for Sprint about every fifteen minutes. So at highway speed you could get to about the third Sprint site before roaming would end). Using both cellmapper and signalcheck.net maps to hunt down these sites. Cellmapper response is almost immediate these days (was taking weeks many months ago).  Their idea of where a site can be is often many miles apart. Of course not the same dataset. Also different ideas as how to label a site, but sector details can match with enough data (mimo makes this hard with its many sectors). Dish was using county spacing in a flat suburban area, but is now denser in a hilly richer suburban area.  Likely density of customers makes no difference as a poorer urban area with likely more Dish customers still has country spacing of sites.
    • Mike if you need more Dish data, I have been hunting down sites in western Columbus.  So far just n70 and n71 reporting although I CA all three.
    • 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.
  • Recently Browsing

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