So should I use bluetooth, or not?

[Dylan]

So I've read the threads about the ROM leak causing the SMS problems, and so far I've not paired my Hero up with the bluetooth dialer in my car. The problem is, I really like using the bluetooth dialer in my car to accept and place calls - tapping on the touchscreen while driving is going to get me killed.

So is it safe to pair the phone with the car bluetooth, or is that type of connection what is going to cause the phone to stop receiving SMS?

Thanks for any advice

 

[BSki]

I have paired mine to my car and have not had any problems receiving messages.

I am not sure what this reported bluetooth problem is as I have not seen it.

 

[Bill-E-BoB]

That type of connection will cause the problem. If your contacts & everything exist somewhere that can be recovered, like gmail or exchange, then I say go ahead & use it though. Its a phone, not worth wreckin' your car over. Just check your storage memory several times a day, and when it gets low do a hard reset to get your memory back. You'll have to reinstall all your apps & resync your contacts but it'll buy you some time. When you reset the phone, it'll be back to 140MB system memory. As long as you never let it get below 50MB, it trigger the SMS problem.

Or, if you can put up with it for another couple weeks, supposedly HTC is preparing an OTA to fix the problem, then we can all use bluetooth like normal. Me personally, I just don't talk in the car for now unless I can get the speakerphone dialed & connected while at a stoplight. Driving comes first.

 

[BSki]

So somehow the bluetooth is eating internal phone memory that a soft reset wont free up?

Where and what is it writing?

If I am asking questions already answered post a link if you have it. I will also search for it.

 

[Bill-E-BoB]

There are various threads about it in pretty much any hero related forum I've seen online so far, here's the one I found out about it in:

Anyone getting "Low on Space" message? - SprintUsers.com

The long & short of it, somehow during the attempts to connect to bluetooth (specifically A2DP profiles I believe) it gets wonky somehow and starts saving about 6MB of hidden cache files to the internal storage that cannot be removed or recovered unless you root the phone. So what ends up happening is your internal memory dips down below safe operating levels (40-50MB from what people are saying) and the Hero tries to save itself by turning off its ability to receive SMS or visual voicemail. The kicker is that when you get more memory back (doing a hard reset recovers the memory) it doesn't remove that system flag that turned off your text messages...so there is no way to recover SMS & visual voicemail once this flag gets tripped, & then you have to replace the phone.

I talked to HTC support about it & they recently opened a Known Issue ticket addressing both the bluetooth issue and the texting issue it creates...and they unofficially guessed that they'll have the update pushed to us all through an OTA within the next week or 2.

 

[marctronixx]

i have the hero paired up to my vehicle. i have a bone stock phone non rooted with GV installed, and i have zero bluetooth issues and zero ROM leaking.memory eating issues. i use exchange but do not use the built in sms app- i use GV for all sms....

 

[Bill-E-BoB]

i have the hero paired up to my vehicle. i have a bone stock phone non rooted with GV installed, and i have zero bluetooth issues and zero ROM leaking.memory eating issues. i use exchange but do not use the built in sms app- i use GV for all sms....

Hmm, interesting. what device are you pairing to? Voice only, or stereo? How much storage memory do you have? (Home>Menu>Settings>SD card & phone storage> Internal Phone Storage Available Space) How long has bluetooth been working for you? Are we talking about a few days & you haven't noticed a problem, or since you bought the phone on 10/11 and nothing has failed?

My pet theory is that it only affects users who try to use A2DP bluetooth...but I'm in no way qualified to actually have any expertise on the matter. That being said, nobody's been able to disprove it yet.

 

[joehp1]

I have been paired via bluetooth on my 2008 BMW 335 for over 3 weeks. Still have 71 MB storage. Imports ALL my contact phone numbers with no problem. (Had Palm phones prior to this and it never imported all the contacts.)

 

[BSki]

I have been paired via bluetooth on my 2008 BMW 335 for over 3 weeks. Still have 71 MB storage. Imports ALL my contact phone numbers with no problem. (Had Palm phones prior to this and it never imported all the contacts.)

Interesting. My Acura MDX paired with my LG Dare and imported the phonebook without a problem.

I have my Hero paired, but it will not import the phone book

Oh, I have had it paired for a about a week and have 90mb free. I will keep an eye on the memory.

 

[marctronixx]

since launch day i have had my phone paired to a 2008 nissan armada LE. i then swapped it out for the "with google" branded hero and did the same thing. so its been that way since. i also have my phone paired to a blueant M1 BT stereo speaker with subwoofer (A2DP) and also my jabra bt8010 headset. (A2DP)

i have 15,185 TOTAL space and 14,842 MB available space.

Hmm, interesting. what device are you pairing to? Voice only, or stereo? How much storage memory do you have? (Home>Menu>Settings>SD card & phone storage> Internal Phone Storage Available Space) How long has bluetooth been working for you? Are we talking about a few days & you haven't noticed a problem, or since you bought the phone on 10/11 and nothing has failed?

My pet theory is that it only affects users who try to use A2DP bluetooth...but I'm in no way qualified to actually have any expertise on the matter. That being said, nobody's been able to disprove it yet.

 

[PGR]

It's important to note that the problem doesn't happen by default if you use Bluetooth. To trigger the problem, the phone apparently has to go into sleep mode while Bluetooth is still "Connecting" during a failed or incomplete connection attempt. If that doesn't happen you won't experience the memory leak.

Or so the story goes. I've had perfect luck with my BlueAnt earpiece, but I haven't even tried my Hero with the Blaupunkt stereo in my car because it does have occasional connection issues.

Pete

 

[marctronixx]

i have my bt8010 paired to both my PRO2 and the hero. a couple of times when i turn the bt8010 on, i may want to use either the hero or the PRO2. so a couple times i had it sniffing out the hero but then i would change the bt8010 to lock onto the PRO2. so the hero did get stuck in "connecting" mode.. i would simply do the soft reset button procedure to reset the device and then it would stop trying to connect to the bt8010. i have not see any ill affects when i have had to do this.

now the above procedure may not qualify for the memory leak other may have experienced , but i have soft reset the device while it was "connecting".

 

[redram38]

Here is something I discovered today and it may or may not mean anything, BUT, I was having all kinds of problems with BT connecting and losing Memory at first. I had a Jabra SP700 and Jabra BT530. I had both paired and used the SP700 when in the car and the BT530 other times. As others, connecting would be hit and miss. I have since taken the SP700 out of the equation. I gave it to my wife to use with her Moment and I only have the BT530 paired now. Since I have done this I have not had one single connection problem. So I wonder if the issue is having more than one device paired to the Hero is what it causing the issue. Now if that is the case Sprint needs to fix this becasue many like myself want to be able to use hands free in the car and not have BT sticking in their ear. Hope they get this fixed with this first update.

 

[marctronixx]

as i posted just above your post, i have THREE BT devices paired to the hero, my SUV's BT handsfree, a blueant M1 stereo speaker/subwoofer (A2DP) and a blueant bt 8010 (also A2DP). no memory leaks or low memory errors...

So I wonder if the issue is having more than one device paired to the Hero is what it causing the issue.