Related
after the 1.6 update i can no longer use my headphones. i was able to use them with toggle headset widget before. anyone know how i can fix this?
anyone have a solution, i cant listen to music
Me too
I'm having this exact problem. It was odd; when i first installed 1.6 the headphones flicked on and off for all of 5 minutes and then stopped working fully. I have the standard usb to 3.5 converter that came with the phone, and it seems to work in another device.
I tried a couple of fixes that had been suggested to people having a similar problem when they had upgraded to cupcake but neither of these worked.
Halp would be appreciated
What radio version you guys have?
First thing i read on your reply was about cutting throuats and spreading cheese which totally threw me...
Anyway, am using CyanogenMod 4.1.999, and if i'm right in thinking radio and baseband are the same thing..... 62.50s.20.17H_2.22.19.261
I just updated to the latest mod 4.1.9999 and still it won't recognise the headset. It is the original one that came with my G1.
Have searched fairly extensively and can't find anything.
Any pointers or suggestions would be very useful.
theres an app called sound route switcher, its updated and i heard it works, but i dont have a credit card, wish someone would update headset toggle widget
I'm currently running DamageControl 1.0 but have also tried AOSP 2.1 and DarchLegend 4.1 and cannot get my phone to pair the 'calls' part to my Pioneer car stereo. The music part pairs fine but not the phone. It worked perfectly on every version of 1.5 I ran.
Is there a way to push some 1.5 bluetooth files to a 2.1 rom?
I searched XDA and it appears that some folks with Eris phone using the latest leak are also experiencing this same thing, one guy specifically stated he had a Pioneer deck as well - coincidence? Could it be Pioneer?
Reading the rom specific threads it appears that most folks have working bluetooth so it may be my situation, hence the question, can I push some 1.5 files to 2.1 to get the phone to pair? If so, any help as to which ones?
ItsDon said:
I'm currently running DamageControl 1.0 but have also tried AOSP 2.1 and DarchLegend 4.1 and cannot get my phone to pair the 'calls' part to my Pioneer car stereo. The music part pairs fine but not the phone. It worked perfectly on every version of 1.5 I ran.
Is there a way to push some 1.5 bluetooth files to a 2.1 rom?
I searched XDA and it appears that some folks with Eris phone using the latest leak are also experiencing this same thing, one guy specifically stated he had a Pioneer deck as well - coincidence? Could it be Pioneer?
Reading the rom specific threads it appears that most folks have working bluetooth so it may be my situation, hence the question, can I push some 1.5 files to 2.1 to get the phone to pair? If so, any help as to which ones?
Click to expand...
Click to collapse
I am also running into this with all 2.1. I have a premier(pioneer) deck. Any luck finding a solution?
CharlyDigital said:
I am also running into this with all 2.1. I have a premier(pioneer) deck. Any luck finding a solution?
Click to expand...
Click to collapse
Nope. I tried everything possible but nothing got the phone and radio to pair. I just can't go back to 1.5 so I've resorted to using a BT earpiece until the official 2.1 is released. Hopefully it will have an updated Bluetooth.
If you come across something I'd love to be kept in the loop.
Truely sorry i cant be much help...but you might consider posting your question in damages thread, or pm him.
Cheers
I love the DCv2.05 ROM! However, every since I flashed it my Bluetooth will no longer work in my C300 Mercedes. The stock ROM does work perfectly.
The phone will pair with the car and connect; but it will disconnect itself several seconds later. It does this over and over and over. The phone says it is paired but not connected.
Any help?
Having the same problem with my Pioneer head unit. Same rom, same connect-disconnect for the phone, but the bluetooth audio function works fine. I can listen to music from the phone, but not make or receive calls...
A2DP has issues in Fresh 2.0d as well. I can pair and connect with my car stereo, but the bluetooth "hiccups" 2-10 times per minute.
danknee said:
A2DP has issues in Fresh 2.0d as well. I can pair and connect with my car stereo, but the bluetooth "hiccups" 2-10 times per minute.
Click to expand...
Click to collapse
As a datapoint I've been running this ROM for a week now and my Mazda3 has no problems connecting to my phone, both music, and voice.
I spent 20 minutes on the phone through the sound system on my way home from work.
smw6180 said:
As a datapoint I've been running this ROM for a week now and my Mazda3 has no problems connecting to my phone, both music, and voice.
I spent 20 minutes on the phone through the sound system on my way home from work.
Click to expand...
Click to collapse
Are you running any mods or just a straight copy of fresh? Maybe I will reflash today and see if my BT issue continues.
danknee said:
A2DP has issues in Fresh 2.0d as well. I can pair and connect with my car stereo, but the bluetooth "hiccups" 2-10 times per minute.
Click to expand...
Click to collapse
I have no idea what A2DP is.
danknee said:
Are you running any mods or just a straight copy of fresh? Maybe I will reflash today and see if my BT issue continues.
Click to expand...
Click to collapse
Straight copy of Fresh, with PlagaDeBuuf's theme.
I installed the lockscreen from Flipz' site earlier but my TWS problem came back so I removed it, and nandroided back to a copy I'd made this morning just before flashing, so it's essentially the same ROM I've been running for a week.
danieledwards1 said:
I have no idea what A2DP is.
Click to expand...
Click to collapse
A2DP = stereo bluetooth
This is an issue with all 2.1 ROMs. Pioneer is known for having the issue where it will pair up but only play media. I have not run into one 2.1 ROM which will work. I have seen some, non pioneer, which report that it works though. Let's just hope the official will have this ironed out or I will be keeping 1.5 around just for this reason. Darch has been working on this in his Legend ROM.
I'm having the opposite effect. The 2.1 leak has had the best Bluetooth implementation I've ever had. Works great on my Ford SYNC and Motorola S9-HDs.
working great in my grand cherokee
repair your bluetooth
I had the same problem in my Infiniti... I thought it was the rom because if I restored my previous rom it worked fine, but when I pair it with the new one it didn't work.
To fix it I had to delete the pair from the car's bluetooth and the phone and repaired them and it worked fine. This worked for both Damage and Flipz's rom. It was odd this was still a problem going from damage to flipz. So when I switched, I deleted the pairing and repaired them.
Hope that helps
I haven't been able to get any of these ROMs to connect to the cassette deck in my 1999 Saturn SL
thematrixkid17 said:
I haven't been able to get any of these ROMs to connect to the cassette deck in my 1999 Saturn SL
Click to expand...
Click to collapse
Did you try to sync the magnetic track? Maybe you need to flip over to the B side and try again?
diordnahero said:
working great in my grand cherokee
Click to expand...
Click to collapse
I too have the Uconnect in my Grand Cherokee, but can't get it to work. The phone pairs, but won't actually connect. What ROM are you running?
danknee said:
Did you try to sync the magnetic track? Maybe you need to flip over to the B side and try again?
Click to expand...
Click to collapse
I think my PRI is bad.... http://bit.ly/bi0Mzt
Pioneer Not connecting
I have a Pioneer Head Unit Premier - ONLY BT Audio - NO Handsfree working. w-damage and fresh latest.. Will try it with my Kenwood and let ya all know.
I haven't had any issues in my 2010 Mustang w/Sync.
atoy74 said:
I'm having the opposite effect. The 2.1 leak has had the best Bluetooth implementation I've ever had. Works great on my Ford SYNC and Motorola S9-HDs.
Click to expand...
Click to collapse
wow this is crazy . i have 2 s9-HDs and 2 heros wih dmage 2.1 rom and eithr of them work correctly ...i just dont get it ..how can some have issues and others dont ...i am going to try Fresh and see it is better ...
the headsets are great but they cut off every couple seconds and come back ...wonder if the Hero just doesnt have the power to do this ??? or maybe higher bitrate mp3s ? most of my MP3s are 128bit ...
rgildoss said:
wow this is crazy . i have 2 s9-HDs and 2 heros wih dmage 2.1 rom and eithr of them work correctly ...i just dont get it ..how can some have issues and others dont ...i am going to try Fresh and see it is better ...
the headsets are great but they cut off every couple seconds and come back ...wonder if the Hero just doesnt have the power to do this ??? or maybe higher bitrate mp3s ? most of my MP3s are 128bit ...
Click to expand...
Click to collapse
It's not the headphones or the Hero, it's 2.1!
I am having the exact same problems as you and finally went back to 1.5 and it's flawless!
Like I have said before it's seems to be 50/50 across the board, some work and some don't!
So I've had this issue since the first Eris leaked ROMs. Basically, any 2.1 ROMs I've tried, INCLUDING what I'm running now, DC 2.07.2
When I turn on bluetooth, and then try to pair my headset, I get a popup saying:
Code:
To pair with "Motoroal H270",
confirm that it is showing the
passkey: 001328.
{Pair} {Don't pair}
The numbers that show up for the passkey are always different, but always 6 digits. I'm assuming the phone is not registering the correct profile for my headset.
Of course, it never pairs.
In 1.5 ROMs I simply entered 0000 as the passkey, but I do not get that option.
I've searched, but with limited keywords to search for... let's just say the hundreds of posts are a little difficult to filter through.
Is that an older Motorola Bluetooth?
I've paired the Motorola H720 with the leaked Eris. Smooth like butter. All I did was enter "0000." Worked fine. Try another bluetooth device, possibly one of more recent vintage. (Don't know how old a model your 270? is.)
I have not had any problems with my Clarion car stereo or my plantronics headset. In my car, in fact, the 2.1's have worked better than stock, since my car stereo picks up the phone and streams the audio automatically every time I get into the car without having to delete and re-pair (as I had to do with stock).
Pete
I have had no luck pairing my phone and any of my cars with any ROM based on 2.1. It pairs, but will not stay connected. Phone says "paired but not connected"; car says "paired, connected; then disconnected"; then endless loops of connected/disconnected. Sucks!
The sad thing is it seems most of these amazing ROM cookers do not use BlueTooth so it is not something they worry about. I bet this is what is holding up releasing the official Sprint update.
I too have tried searching through endless posts about bluetooth and 2.1. All I can come up with is there are some libraries missing from the 2.1 BlueZ; or something to that effect.
I love Damage's 2.0.7.2 ROM! But I have to go back to stock since driving and talking on the phone without a handsfree device is now illegal here in El Paso, TX.
I don't have a car or stereo bluetooth device to pair against. Just tried pairing my bluetooth with the new 2.0.2v2? Alysious ROM. Took 2 sec and nearly totally automatic. Amazing.
My issue with all 2.1 roms is that I can pair, dial and audio stream all day. I just cant talk as no sound or mic. I reflash back to 1.5 and all works well. BT in the car is now useless. sigh
2.1 paired fine, but its a crappy connection on 2.1, on 1.5 i had a better connection
finally used my BT last night with my phone ...worked like a champ! everything was clear to me....i don't have no sound probs and haven't used any of the fixes...
I pair with my bluetooth headset most of the time without problem. I do occasionally have to turn on and off my headset and the bluetooth on the phone to get it to reconnect. Thankfully, it only happens occasionally.....
Maybe I'm just one of the lucky ones (this time) but I have been streaming audio from my hero to the car stereo while while using google navigtion, which politely talks over the music, and have not had any problems. I'll get an occasional skip in the music (probably during downloads of map data), but nothing worth complaining about.
Pete
poor_red_neck said:
So I've had this issue since the first Eris leaked ROMs. Basically, any 2.1 ROMs I've tried, INCLUDING what I'm running now, DC 2.07.2
When I turn on bluetooth, and then try to pair my headset, I get a popup saying:
Code:
To pair with "Motoroal H270",
confirm that it is showing the
passkey: 001328.
{Pair} {Don't pair}
The numbers that show up for the passkey are always different, but always 6 digits. I'm assuming the phone is not registering the correct profile for my headset.
Of course, it never pairs.
In 1.5 ROMs I simply entered 0000 as the passkey, but I do not get that option.
I've searched, but with limited keywords to search for... let's just say the hundreds of posts are a little difficult to filter through.
Click to expand...
Click to collapse
Guys, sorry to revive an old post but I am having this exact same issue as the OP. If anyone has found a fix, please post. Thanks.
Looking at FroYo they have updated some Bluez stuff (what makes out BT work) maybe it will be better when we get that.
Hopefully...
So I flashed to a froyo ROM over the weekend and have found someone posted a fix for the gps issues, but I'm having BT issues as well. Has anyone else experienced this: I can pair certain BT accessories but not others, and even when paired the devices cannot connect without multiple connection requests.
My specific issue is that I have motorola rockr bt earbuds, and a Jabra car kit, and they both pair with the phone (after a few trys) but neither will automatically connect to the phone once they're turned on. With the earbuds I have to manually try to connect 6 or 7 times in a row before they'll connect, and even then they may only connect with the phone audio only. This wasn't an issue with the stock ROM so I'm assuming its the bt radio library for Froyo thats the problem?
I'm not new to development, but I'm kinda new to development on Android. I've been trying to learn more about the radios and how they're configured within the OS but I haven't found a lot of good documentation on it. I'd be happy to work this out for myself and post any improved radio to the forum but it would be helpful if someone could send me a link to some learning material? If someone has an improved Epic Froyo BT radio to flash that would be helpful as well
yes bluetooth issues as well, but different in that only when i turn bluetooth on it foreclose's. the bluetooth is otherwise not affeceted. only on the initial start up.
I've been having issues as well, but also mine a different. If I walk away from my phone and it get disconnected I manually need to re-establish the connect. Also sometimes the A2DP stops working requiring a reboot. And I've NEVER been able to get Bluetooth voice dialing to work on Froyo for the Epic. I had 2.2 running on my Hero before I switched phones and it worked great.
I am in no way a developer, but I do prowl this site everyday, so unfortunately I can't help with fixing it. More power to you and I hope you (or somebody) gets it worked out!
Delta1Fox said:
I've been having issues as well, but also mine a different. If I walk away from my phone and it get disconnected I manually need to re-establish the connect. Also sometimes the A2DP stops working requiring a reboot. And I've NEVER been able to get Bluetooth voice dialing to work on Froyo for the Epic. I had 2.2 running on my Hero before I switched phones and it worked great.
I am in no way a developer, but I do prowl this site everyday, so unfortunately I can't help with fixing it. More power to you and I hope you (or somebody) gets it worked out!
Click to expand...
Click to collapse
I had the Hero before the Epic as well and but I never tried 2.2 on it. I had BT issues with the Hero, but I didn't bother too much with it.
I had the same BT issues with the stock ROM when walking away, having to reconnect after coming back. Voice dialing never worked with BT either. I was hoping for an improvement with the upgrade, but I'd settle for what it was before. I'll start tinkering but I'm not sure what I'm doing with the radios....I'm a developer, but not an Android developer.
revjtanton said:
I had the Hero before the Epic as well and but I never tried 2.2 on it. I had BT issues with the Hero, but I didn't bother too much with it.
I had the same BT issues with the stock ROM when walking away, having to reconnect after coming back. Voice dialing never worked with BT either. I was hoping for an improvement with the upgrade, but I'd settle for what it was before. I'll start tinkering but I'm not sure what I'm doing with the radios....I'm a developer, but not an Android developer.
Click to expand...
Click to collapse
I noticed that too with the stock 2.1. However, Bluetooth voice dialing is a feature built into 2.2. I've read that some people having it work great, but other's like myself, are not having it work at all. Oh well. I'll live for now. Hopefully if it isn't fixed beforehand then it'll be fixed with the "official" release. LOL.
now that you mention it, i had this problem too doing some bluetooth file transfers between my buddy and I's phones last night. it struggled to connect multiple times but after the first successful transfer it seemed to stop having problems for a little. I'm moving back to 2.1 until we get some non-beta custom roms for froyo because i use bluetooth and gps everyday. just out of curiosity though, for those who are having problems, which rom and modem are you using?
I put the DI18 modern on there and that has seemed to fix the gps more or less. I think I'm going to go back as well. Maybe I didn't flush data enough times but layar can't find the camera, neither can the bar code scanner...it's close, but Froyo just isn't ready for the Epic yet.
Sent from my SPH-D700 using XDA App
Still having Bluetooth problems with official Froyo release on Epic 4G
I was also having glitchy issues with BT oo my Epic running the leaked build of Froyo. I ended up flashing back to 2.1. The problem I was having was when I turned on my Motorola Finity, it worked fine.. for one call...) Then it wouldn't work again unless I turned the headset off and back on again. To make matters worse, after using BT one time, All sounds including ringers and media, came out of the earpiece instead of the actual ringer/speaker on the back of the phone.. Strange, huh? I had to reboot the phone to make it normal agian. Now to my surprise, after installing the newly released official Froyo build, I am having the same problem. Is anyone else having an issue like this with the official software? I am going to try the headset on another Epic at work, maybe its just a compatibility issue with my particular headset, but its very strange...
I am using the new official Froyo release from Samsung/Sprint. having the same buggy issues I had with the old leaked version.
donkeysauce said:
I was also having glitchy issues with BT oo my Epic running the leaked build of Froyo. I ended up flashing back to 2.1. The problem I was having was when I turned on my Motorola Finity, it worked fine.. for one call...) Then it wouldn't work again unless I turned the headset off and back on again. To make matters worse, after using BT one time, All sounds including ringers and media, came out of the earpiece instead of the actual ringer/speaker on the back of the phone.. Strange, huh? I had to reboot the phone to make it normal agian. Now to my surprise, after installing the newly released official Froyo build, I am having the same problem. Is anyone else having an issue like this with the official software? I am going to try the headset on another Epic at work, maybe its just a compatibility issue with my particular headset, but its very strange...
Click to expand...
Click to collapse
I can confirm these issues still exist in the official release.
I'm having the same problem, but when I use bluetooth in my car, it insists on transmitting sounds to my car's bluetooth, even when I repeatedly uncheck Use for media audio. I don't have an option in my car to disable A2DP. My only complaint with Eclair, other than speed (I'm using Bonsai4All, and previously, Syndicate) was that I was running out of space for software (was using EpicExperience). Sometimes, bluetooth won't connect at all, necessitating a phone reboot, or going into airplane moe and then back out. So I'm gathering that this is across the board, regardless of Froyo build? Syndicate didn't work at all with my car.