Root Bluetooth and Camera Woes

[Phastor]

I'm currently running KaosFroyo V36 on my Eris and am having a couple of issues. I'm wondering if anyone else who has had experience with this ROM had similar issues.

First off, and the most annoying, is an issue with bluetooth. Very frequently, my headset will disconnect from the phone mid-call. Sometimes it will reconnect within a few seconds. Sometimes I have to turn bluetooh off and then on again on the phone for it to reconnect. Sometimes I have to shut off the headset and turn it back on, and sometimes I have to reboot the phone for it to reconnect. This only seems to happen during calls. Sometimes it will do this several times over in a single call and I finally get tired of it and turn on speaker. I use BT Mono to route audio to my headset and it's never disconnected yet that way. At first, I thought my Jawbone was defective, but after trying another headset, I had the same results. There is a possibility that this is a hardware issue, but this started happening soon after I flashed to Froyo from stock, so I'm hoping that's the case.

My other issue is with Froyo's camera app. Every time the camera auto focuses or makes light adjustments, the picture will freeze for a second. These still frames also show up in any video recorded with the camera. Again, this only started happening after I flashed to Froyo.

 

[doogald]

First off, and the most annoying, is an issue with bluetooth. Very frequently, my headset will disconnect from the phone mid-call. Sometimes it will reconnect within a few seconds. Sometimes I have to turn bluetooh off and then on again on the phone for it to reconnect. Sometimes I have to shut off the headset and turn it back on, and sometimes I have to reboot the phone for it to reconnect. This only seems to happen during calls. Sometimes it will do this several times over in a single call and I finally get tired of it and turn on speaker. I use BT Mono to route audio to my headset and it's never disconnected yet that way. At first, I thought my Jawbone was defective, but after trying another headset, I had the same results. There is a possibility that this is a hardware issue, but this started happening soon after I flashed to Froyo from stock, so I'm hoping that's the case.

This sounds like the undead call problem. Does it happen only with BT or with other calls as well? Anyway, there is a patch that you can flash. See xda-developers - View Single Post - [SOLVED] Eris "Undead Call" Problem (AOSP/Froyo/GB) Fixed!

My other issue is with Froyo's camera app. Every time the camera auto focuses or makes light adjustments, the picture will freeze for a second. These still frames also show up in any video recorded with the camera. Again, this only started happening after I flashed to Froyo.

If using the camera is important to you, then maybe you should use a close-to-stock ROM like xtrSENSE, xtrROM. KF (IMHO) is the worst of the Eris Froyos (not only that, but V36 is a few versions old), but at this point I would recommend GSB (which is a Gingerbread ROM) over any of the Froyos, if there is some reason why you must stay away from Android 2.1

 

[Phastor]

This sounds like the undead call problem. Does it happen only with BT or with other calls as well? Anyway, there is a patch that you can flash. See xda-developers - View Single Post - [SOLVED] Eris "Undead Call" Problem (AOSP/Froyo/GB) Fixed!

The call itself doesn't drop. It's just the BT that disconnects from the phone during a call.

If using the camera is important to you, then maybe you should use a close-to-stock ROM like xtrSENSE, xtrROM. KF (IMHO) is the worst of the Eris Froyos (not only that, but V36 is a few versions old), but at this point I would recommend GSB (which is a Gingerbread ROM) over any of the Froyos, if there is some reason why you must stay away from Android 2.1

Main reason why I'm using a ROM is only for the BT enabled voice dialing, which isn't supported in 2.1. And maybe for some of the features of the BlueAnt headset whenever I get one. Otherwise I would be happy with just having a rooted phone with stock firmware.

I was hoping that GSB would be brought up here. I was thinking about giving it a try to see if I had the same issues with it. I also wanted to ask what kind of differences I would see compared to KFv36 aside from UI, such as any quirks it may have. I see mixed reviews between some saying it's clunky on the Eris, but others saying it runs smoothly.

 

[Bob Cat]

The call itself doesn't drop. It's just the BT that disconnects from the phone during a call.

Main reason why I'm using a ROM is only for the BT enabled voice dialing, which isn't supported in 2.1. And maybe for some of the features of the BlueAnt headset whenever I get one. Otherwise I would be happy with just having a rooted phone with stock firmware.

I was hoping that GSB would be brought up here. I was thinking about giving it a try to see if I had the same issues with it. I also wanted to ask what kind of differences I would see compared to KFv36 aside from UI, such as any quirks it may have. I see mixed reviews between some saying it's clunky on the Eris, but others saying it runs smoothly.

That's what rooting is all about. Try it and if you don't like it flash something else.

 

[scotty85]

The call itself doesn't drop. It's just the BT that disconnects from the phone during a call.

with the "undead call" issue the call doesn drop either,it just dissapears for a few seconds,then will reappear. youll think its disconnected but then bam! there it is(hence "undead" ) so when your headset disconnects,are you able to pick up the handset and talk to the person? or are they gone from there as well?

at any rate,id agree GSB is a better option at this point than any of the froyos. if you dont like it,try worksheds froyo rom(vanilla or themed) as he is most likely to still update and provide support. i believe all the other developers have moved on to other phones so you prolly wont find much support for the others(nonsensikal,celb,tazz,well tazz is still working on a gingerbread rom so you might try his froyo)

i think youll like gsb,tho... after running cm7 on 3 different devices i personally find it hard to use anything else

 

[doogald]

The call itself doesn't drop. It's just the BT that disconnects from the phone during a call.

Right, that's the undead call problem. The call appears to drop, then instantly reconnect. It never happened to me, but it happened to a lot of people.

Incidentally, GSB has that undead call patch (which just creates a directory folder that should be there) already set up - there is nothing to patch.

Main reason why I'm using a ROM is only for the BT enabled voice dialing, which isn't supported in 2.1. And maybe for some of the features of the BlueAnt headset whenever I get one. Otherwise I would be happy with just having a rooted phone with stock firmware.

I was hoping that GSB would be brought up here. I was thinking about giving it a try to see if I had the same issues with it. I also wanted to ask what kind of differences I would see compared to KFv36 aside from UI, such as any quirks it may have. I see mixed reviews between some saying it's clunky on the Eris, but others saying it runs smoothly.

Compared to KF, there are no quirks. KF was the quirkiest of the Eris Froyos. The only thing I don't know about is the camera, though I know that there were some camera fixes found for the CM6 based Froyo ROMs in the almost four months since the last KF came out (and yours is older than that) that I would guess are incorporated into GSB.

Besides the color of the notification/status bar, I can't of anything from a UI point of view that is terribly different about GSB. It comes with LauncherPro as the default launcher rather than ADW, but that's just a market install away from being the same, if you prefer ADW.

If you are going to install it, you do have to download a flashabale Google apps zip file package and flash it after you flash GSB but before you restart the phone. So, steps to install are:

- download and copy/move to SD the GSB and gapps zip files
- Nandroid backup
- wipe data/factory reset
- wipe Dalvik
- flash GSB
- flash gapps
- restart

So long as you have the Nandroid backup, you are just a restore away from where you are right now.

 

[Phastor]

I don't remember the calls ever dropping when I wasn't using the headset, and the headset would always sound a tone as if it disconnected from the phone. At times when it was really bad and it kept doing it over and over, it would stop after I went to speaker. However, if it is these undead calls that you speak of, that would explain why it doesn't do it when I'm feeding music to the headset using BTMono.

Thank you for the tips and suggestions. I think I'll give GSB a try.

 

[Phastor]

Well, I have GSB up and running now.

It's already making a good impression on me. It seems to be running a lot more snappy than KFv36, and the camera seems to be working fine. We'll see if it fixed my BT/Undead call issue or not after a few days.

Unfortunately it did not fix another issue I explained here some time ago.
http://androidforums.com/android-media/204242-movie-goes-screwy-3-4-way-through.html

 

[Phastor]

Here's an update.

Been running GSB for a flew weeks now and I am still having the BT disconnect problem. The call is not being dropped. The audio is just being routed to handset. Sometimes it will go back to the headset after a few seconds. Sometimes it wont come back at all. I notice that during the times that it wont go back to BT, I can turn off the headset and the phone will still think that it is cconnected until I turn off the phones BT and then back on again, after which the headset will connect again.

The most annoying thing it does though is completely freeze the phone when it disconnects. This doesn't happen too often, but once is too much for me. The only way I can reboot the phone when it does this is by pulling the battery.

I'm still hoping its the headset and not the phone. It starting to look grim though.

 

[Bob Cat]

Here's an update.

Been running GSB for a flew weeks now and I am still having the BT disconnect problem. The call is not being dropped. The audio is just being routed to handset. Sometimes it will go back to the headset after a few seconds. Sometimes it wont come back at all. I notice that during the times that it wont go back to BT, I can turn off the headset and the phone will still think that it is cconnected until I turn off the phones BT and then back on again, after which the headset will connect again.

The most annoying thing it does though is completely freeze the phone when it disconnects. This doesn't happen too often, but once is too much for me. The only way I can reboot the phone when it does this is by pulling the battery.

I'm still hoping its the headset and not the phone. It starting to look grim though.

I use BT in my truck on long trips (at least 8hrs) every other two weeks and it works fine for me. Maybe an equipment problem.

 

[jae_63]

I have been experiencing BT problems (call going to phone rather than BT speakerphone) sometimes with GSB 2.9. I didn't observe this with 2.8, and certainly not with KaosFroyo 37 which I used for five months.

I also experienced a problem after using my Zephyr BT heart monitor, where BT completely refused to turn on. This was resolved after two reboots.