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
This isn't supposed to be some sort of complaint or anything, but was just wondering if anyone had any suggestions/ideas why my K33428US LiquidAUX Bluetooth Car Kit stopped working with ANY 2.1 ROM (FRESH & Damage)
it worked great with 1.5 but honestly I am not rolling back now, will just have to use the headphone jack for now.
At first I thought it was an issue with AD2P in general but then i started to see posts where people had success with it, so now i am disappointed.
Glod said:
This isn't supposed to be some sort of complaint or anything, but was just wondering if anyone had any suggestions/ideas why my K33428US LiquidAUX Bluetooth Car Kit stopped working with ANY 2.1 ROM (FRESH & Damage)
it worked great with 1.5 but honestly I am not rolling back now, will just have to use the headphone jack for now.
At first I thought it was an issue with AD2P in general but then i started to see posts where people had success with it, so now i am disappointed.
Click to expand...
Click to collapse
I have the same kit and i can connect just fine...but with 2.1 I have to manually connect it everytime but going into settings.
Just wondering if it's possible to pull out everything related to bluetooth and A2DP (Stereo Bluetooth Audio) from 1.5 and insert it into damages 2.1 ROM.
I have tried every 2.1 ROM and I can't seem to get reliable bluetooth audio through my headphones, it skips and cuts out. It is very frustrating.
I have tried several headset to no avail, it always work flawless in 1.5.
I just got done running a logcat as well, and everytime it would skip or cutout nothing showed in the logcat, it was very strange!
Thanks
Roman
Roman G said:
Just wondering if it's possible to pull out everything related to bluetooth and A2DP (Stereo Bluetooth Audio) from 1.5 and insert it into damages 2.1 ROM.
I have tried every 2.1 ROM and I can't seem to get reliable bluetooth audio through my headphones, it skips and cuts out. It is very frustrating.
I have tried several headset to no avail, it always work flawless in 1.5.
I just got done running a logcat as well, and everytime it would skip or cutout nothing showed in the logcat, it was very strange!
Thanks
Roman
Click to expand...
Click to collapse
These ROMs still are not official builds from Sprint and HTC. They are leaked beta versions.
I am sure until Sprint officially releases their update that some of these things will be buggy.
Everything else in his newest ROM is flawless.
DJAscendance said:
These ROMs still are not official builds from Sprint and HTC. They are leaked beta versions.
I am sure until Sprint officially releases their update that some of these things will be buggy.
Everything else in his newest ROM is flawless.
Click to expand...
Click to collapse
Oh I realize that, I was just wondering how hard it is to do that and if it could be done!
Some of the other Roms I have tried have been complete dumps and none of them have worked either!
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.
Okay Ive been looking for about an hour now and have given up on the search for this. But I'm trying to get my cardock to play music through the 3.5mm jack on the back of the dock when its plugged in. I've found a bunch of useful posts that fix it in Froyo but I can find any fix to work on Gingerbread. Specifically I'm running latest CM7 and using the regular CM kernel. If there is another kernel I can download to fix the problem or anything please let me know.
Thanks!
are you in the right forum? (Samsung Vibrant).
I don't know of a car dock, and there's no port for it. The USB port is on the top.
I have the desktop dock and I couldn't get the sound to route through the external speakers either. There is a setting in CM7 but it doesn't seem to work. I also had an app that would re-route sound for the car and desktop dock that works great on 2.2 and 2.2.1 but it would not run in CM7.
To my knowledge, and this is running with Froyo, the only way to get the audio to come out of the car dock 3.5 mm jack is to use the Samsung Car Dock application. I May be wrong, but this is what I have discovered so far, which sucks as I really prefer the Google Car Home app.
cyberpyr8: What is that redirect app?