Serious ROM leak documented on video!! May Cause fatal sms issue.
BUG FIXED: If you guys are still suffering from this issue upgrade to the Maintenance Release, it fixes it for the most part, except for the occasional failure to connect. No ROM leak though.
It appears a leak is being caused when rebooting (or turning off bluetooth) the phone when the phone is in a "connecting" status with bluetooth device. Basically the phone stays in a "connecting" status when it fails to connect, even though the notification in the notification bar says it is connected and your bluetooth device says it is connected. In actuality it is not and all calls and audio will be routed to your phone not bluetooth device. If you restart or turn off bluetooth while your phone with a "connecting" status active I have found when you reboot it will eat away at your ROM memory(not RAM). You may not ever notice the bluetooth connection failure if you don't get a call while when it should be active. The "connecting" status does not clear unless you unless it manages to connect after a while which is rare (either does it within a few seconds or not at all) . I made a video of this behavior because not a lot of people have been experiencing or at least catching on to it with their usage patterns.
Edit: It appears that the leak actually occurs even if you turn bluetooth off while the phone is in connecting status so a reset is not necessary for the leak to occur. This basically renders bluetooth use unusable as there is no way I can think of to avoid a leak if it gets stuck with the "connecting" status.
FYI: I just exchanged my Hero for a new one and the intermittent sms issue persists. The phone has been out of the box for 20 minutes, and Bluetooth has not even been turned on - not ever.
Thanks for posting, although not sure I entirely understand what your argument is with regard to bluetooth. My phone completely lost the ability to get texts or voicemail and I never turned on bluetooth once in the entirety of owning the device. I certainly didn't try to connect to anything with bluetooth.
Thanks for posting, although not sure I entirely understand what your argument is with regard to bluetooth. My phone completely lost the ability to get texts or voicemail and I never turned on bluetooth once in the entirety of owning the device. I certainly didn't try to connect to anything with bluetooth.
Did you get a low on storage memory warning? The fatal sms/voicemail issue appears to be tied into the phone not having enough storage memory. This is one of the paths that leads to that at least it did with my first hero and it is doing it with this one as well. I suppose it can also be cause by the user filling up the ROM with too many apps.
The intermittent/delayed sms issue is caused by something else, I have not experienced it.
Last edited by elguapo76; October 27th, 2009 at 01:49 PM.
Yeah...I personally didn't have any ROM issues. I always had atleast 90MB free and there was no intermittentness to my lack of SMS or Voicemail. There are obviously multiple issues here.
I haven't had problems with SMS or voicemail (that I'm aware of), but am having a ROM memory issue, and I do use bluetooth pretty extensively and have had the same "connecting..." issue with both Motorola SD9-HD and Plantronics Voyager 855.
A few days ago I gave up on Bluetooth working altogether because it was such a pain and just bought a pair of noise isolating corded ear buds. And today I factory rest my device to reclaim memory.
Last edited by Gambit; October 27th, 2009 at 02:02 PM.
Also, this should be a candidate to be added to the Confirmed Issues sticky in my opinion. The Bluetooth/ROM leak is an issue within itself whether or not it contriburtes to the SMS failure.
I'm trying to wait til there's some sort of confirmation from Sprint or HTC that they're aware of the issue before I add it to the big sticky. If I went adding every issue that someone confirms independently, I'd have no free time.
I just performed a hard rest on my device. I did not load any applications or services. It still performs the same behavior if it gets stuck "connecting". On my device it connects 9 out of 10 times but those few times that it fails to actually connect it causes this issue. I suppose if you have a device that connects all the time you will not see it but if it ever gets stuck "connecting" check your memory.
Last edited by elguapo76; October 27th, 2009 at 03:09 PM.
i saw this connecting issue on a BT 8010 headset.it would still try to connect even though the headset was connected to my other phone.
what i did was turn off BT. this released the phone from trying to connect, but later once i turned on BT the hero would still try to connect to the 8010.
so i unpaired the hero form the 8010 and of course no more issues.
i use the hero with my BT in the car. it connects and disconnects fine. no errors or issues.
i do not use the stock sms app to SEND messages, but i do receive messages (and that blasted 9103). i use GV for all messages...
no ROM leak.
also perhaps knowing what BT profile the headest one is trying to use may be helpful. if its an older BT stack that may be the issues.. so i can see a lot of variables herelll
The bluetooth has to get stuck on "connecting" status for the leak to occur. If it does not it will not leak. Each time it happens and you turn bluetooth off or reset your Hero the ROM loses 5-15mb.
The memory can be restored with a factory reset, correct? From what I recall, I thought Sprint said you may have to take the phone back to them when this happens... as if the memory was somehow lost forever.
Knowing that a factory reset may not work is quite disconcerting... so does that mean whatever has a hold on the memory will continue to do so after a complete restore? In other words, did the factory reset report more memory than before but still not receive SMS messages, or was the memory still being allocated?
I can confirm this issue on my device. I have a LiquidAUX BT receiver for my car and I have had connection issues with my Hero since day 1. Most of the time it connects but other it just hangs. Then i started to receive low disc space warning most likely due to the reasons described above.
If this is not resolved along with the sleep issue, or 2.0 is not deployed before my 30 days Im returning the device and going to the droid.
Quote:
Originally Posted by kinetic
Knowing that a factory reset may not work is quite disconcerting... so does that mean whatever has a hold on the memory will continue to do so after a complete restore? In other words, did the factory reset report more memory than before but still not receive SMS messages, or was the memory still being allocated?
A hard reset did return my memory to above 130Mb. I have not received any text yet, but i am pissed I had to do a hard rest to get it back
Last edited by WhiteWidow; October 30th, 2009 at 11:33 AM.
A factory reset restores your storage memory every time but if you get to low on storage memory before you factory reset our phone the problem is you stop receiving sms/voicemail. If that is the case it's looking like there is no recovering that functionality short of exchanging the phone.
Last edited by elguapo76; October 30th, 2009 at 12:13 PM.
This is very strange behavior. Butttt can that issue be exploited to open a back door into the root since this is obviously writing to the ROM if it actually persisting after a hard reset?
A factory reset restores your storage memory every time but if you get to low on storage memory before you factory reset our phone the problem is you stop receiving sms/voicemail. If that is the case it's looking like there is no recovering that functionality short of exchanging the phone.
Crap just tested SMS and i cant receive only send. Now to exchange it.
This is very strange behavior. Butttt can that issue be exploited to open a back door into the root since this is obviously writing to the ROM if it actually persisting after a hard reset?
It could be possible, or it could be the phone just misreporting available storage memory.
I believe the reason the sms/voicemail issue occurs is because the system intentionally puts up a remote flag to not send any sms/voicemail while low on memory. The problem lies that when you free up memory even if you hard reset the phone it doesn't take down the flag it down unless you change to a phone that communicates the flag already down. That's just my understanding so I could be totally wrong!
thank you. i totally understand the "issue". i had the same "connecting" status on the phone and no leaks were seen then ...and now... i appreciate your concern in making sure i understood...
Quote:
Originally Posted by elguapo76
@marctronixx
The bluetooth has to get stuck on "connecting" status for the leak to occur. If it does not it will not leak. Each time it happens and you turn bluetooth off or reset your Hero the ROM loses 5-15mb.
thank you. i totally understand the "issue". i had the same "connecting" status on the phone and no leaks were seen then ...and now... i appreciate your concern in making sure i understood...
Yup that sucks but at least they are working on it. Don't mind waiting a couple of weeks for it. Hopefully we will get a few more fixes in that maintenance release.
Device(s): HTC Evo 4G (Sprint) - Rooted - CM 7.1.x Nightly 150
Carrier: Not Provided
Thanks: 11
Thanked 1 Time in 1 Post
I just discovered I was suffering from this. I did a reset and restored my applications and messages, but left Bluetooth turned off. Seems to be working just fine now. Sure hope this gets patched quick-like. Like above, missing my headset.
__________________
Current: EVO 4G Supersonic CM7 Nightly | Archos 70it 2.1.8
First ROM: Fresh 1.1 (Hero)
Use Dropbox
Im getting this on my HTC hero too, I've heard that using "sms to mail" app is a way round this issue for now.. but if there are any fixes please let us know!
If you guys are still suffering from this issue upgrade to the Maintenance Release, it fixes it for the most part, except for the occasional failure to connect. No ROM leak though.
Serious ROM leak documented on video!! May Cause fatal sms issue.
