Related
Hey everyone. im from the Hero CDMA forum. i have made audio fix patches for the hero that fixed the audio loss for 2.1 roms.
I recently ended development for the audio fixes because the issue began to rise in people with stock heros. but with that aside, i will create a fix for eris users if enough of you have the problem. i believe i have seen 7-8 people with it. anyways leave a comment telling me you have the issue, when it happened, what roms cause it, and what your software builds are, and what roms dont cause the issue. thanks for the cooperation and i hope i can help
Hey Avalaunchmods!
Thanks for the help with this! I am running the Aloysius (Coincidentally a Hero port):
http://forum.xda-developers.com/showthread.php?t=663893
Audio usually cuts out for me when I am receiving a notification. It will kind of stutter/jitter and then continue to play.
one of my custom ringtones cut out on an incoming call once, but only once. so it may have only been a fluke. hadnt happened before or after.
ivans .8
alexhendershott said:
Hey Avalaunchmods!
Thanks for the help with this! I am running the Aloysius (Coincidentally a Hero port):
http://forum.xda-developers.com/showthread.php?t=663893
Audio usually cuts out for me when I am receiving a notification. It will kind of stutter/jitter and then continue to play.
Click to expand...
Click to collapse
I get the same using VanillaDroid ROM.
Thanks for the help!
I have had this problem pop up intermittently, but with increasing regularity (up to 2-3 times daily at its worst). The sound profile and volumes remain unchanged, but sometimes for no apparent reason, all audio drops. If I get a call, there is no ringer. If I get a notification, there is no audible alert. If I place/answer a call, the earpiece/speakerphone are silent, and the other party doesn't hear me. The rest of the phone's functions still work, and vibrate still works, but there is no audio from any apps or OS functions until I reboot the phone.
As for particular triggers, I haven't found any yet. I had been running ivan's 0.8t2, but have downgraded to his older 0.5.4 to see if the problem is fixed. So far it hasn't popped up, but it's only been a few days.
Thanks again for your willingness to help. I'll be sure to let you know if I see the problem resurface.
I know the fix is only possible in rooted phones, but I wanted to chime in and let you know that a lot of people on 2.1 leak v2 non-rooted are having this issue, so you can see some of the symptom reports in these threads on androidforums:
http://androidforums.com/htc-droid-...en-phone-goes-silent-multiple-times-week.html
http://androidforums.com/htc-droid-eris/57804-calling-problems.html
thenestor said:
I know the fix is only possible in rooted phones, but I wanted to chime in and let you know that a lot of people on 2.1 leak v2 non-rooted are having this issue, so you can see some of the symptom reports in these threads on androidforums:
androidforums.com/htc-droid-eris/66298-phone-useless-when-phone-goes-silent-multiple-times-week.html
androidforums.com/htc-droid-eris/57804-calling-problems.html
Click to expand...
Click to collapse
I have a non-rooted phone and I have the same issues...
If by audio problems, you mean no sound via ringtones, notification or voice over the ear piece, then I have experienced it with Ivan's 08T2. I've had it happen about three times. I did a reboot and it corrected it.
another Aloysius user here, and yep, audio problems out the wazoo. good thing I text mostly.
alright this got moved to general?
i though this would fit in development haha.
anyways ill get on a fix i believe. ill put it somewhere. not dev..
I've had audio issues, but the only thing that seems to cause it for me us getting a force close on any program that is currently playing audio, such as a music player or (worse) an alarm clock.
I've never had audio just randomly cut out on me, but it definitely all stops working after such a force close
I'm having the same audio issues. I'm currently on VanillaDroid v1.0. I experienced the issue on the eris21official-root ROM as well. It usually happens after I use the camera to snap a few pictures. If I don't use the camera, it is pretty stable. Let me know if you need any further information.
Avalaunchmods said:
alright this got moved to general?
i though this would fit in development haha.
anyways ill get on a fix i believe. ill put it somewhere. not dev..
Click to expand...
Click to collapse
Thanks ..... I don't think I have had these problems (but maybe I have and just didn't realize it) but its nice nowing there is a fix out there and people like you are out there using your time to create fixes
I i use it ..... i will "buy your time back"
Avalaunchmods said:
Hey everyone. im from the Hero CDMA forum. i have made audio fix patches for the hero that fixed the audio loss for 2.1 roms.
I recently ended development for the audio fixes because the issue began to rise in people with stock heros. but with that aside, i will create a fix for eris users if enough of you have the problem. i believe i have seen 7-8 people with it. anyways leave a comment telling me you have the issue, when it happened, what roms cause it, and what your software builds are, and what roms dont cause the issue. thanks for the cooperation and i hope i can help
Click to expand...
Click to collapse
Avalaunchmods,
Since the Droid Eris kernel code was made available from HTC, have you been able to make any further progress fixing the audio loss bug for the Eris and Hero?
Right now the only solution we know of is to replace the phone. (Those of us who have gotten warranty replacements have not had the problem resurface.)
But even if the problem is related to certain hardware, it seems like there might be a way to fix the kernel's *reaction* to the problem, so that the phone doesn't become unusable.
Having the problem too.
Happened on Evil Eris and Ivans.
Any update on this? I am having the same issue on both CyanogenEris v1.1 and ELB-Cyanogen.
i am having this issue as well, running Ivans Eris_Official 1.0 Alpha. Experienced this issue on the 0.82t also. No audio from the phone's earpiece (speakerphone wont work either) when a call comes in, or if i try to call them back. have to reset the phone and then it works. I'm running setcpu at 710 now, but i wasn't on 0.82t so probably not the culprit.
My software version stats, in case it matters -
Firmware - 2.1
Baseband - 2.42.00.04.12
Kernel - 2.6.29oc [email protected]#26
Build # - 2.36.605.1 CL1165907 release-keys
Software - 2.36.605.1
PRI - 2.11_002
PRL - 51739
Eri - 5
*double post oops*
hi..i'm havin this issue too!
I'm on a froyo rom now. I was on an xtr rom when I noticed this problem. Tried to flash a new rom to get rid of it and it's still there. I can use the phone for a few hours and then the only way i can answer calls is through speakerphone.
Model Number-FroyoEris
Android Version-2.2
Baseband-2.42.00.04.12
Kernel - 2.6.29 [email protected]#3
build number-kaosfroyo v13
HEEELLLLPPPP!!!!
Audio Problem
I've had this problem every since the 2.1 update. My wife and I both had it (we both have a Eris) on unrooted phones. I rooted to ErisLightning and still had it, switched to Tainted Vanilla, and now I'm on Lightning Bolt. My wife is on Droid Does Pink and we've had the problem with every single rom. Sometimes when we receive or make calls, the phone will go completely mute. We can't hear the other person and they can't hear us. We can't hear a ring tone if calling someone either.
I use Google Voice and I sometimes get ghost voicemails. It will save the entire length of the voicemail, but it will be completely mute. Even if I restart and re-open GV it's still mute.
For now, we're just rebooting whenever we have this problem. Seems to be the only way to get audio back.
I found out that certain combinations of ROMS and Kernels work better with my CAR Bluetooth then other combinations. For instance CM6 is not working perfect and is uncertain to reconnect to my Car system. On the other hand most Sense ROMS work better with my Car system.
So in this project I wanna track down first which components have influence on the bluetooth stack, and more important which specific parts of the kernel, software and other things are related.
This to improve the BT Car system of at least my Scenic but I have the feeling more Car systems have issues.
Please if you have info about this put it in this treath so we can make it better.
Nice initiative. My BT system in my car works flawlessly with WinMo, but as soon as I connect my nexus, my speakers begin shrieking like all hell breaks loose. Also, My Nexus the seems to lock up and I need to pull the battery for all misery to end.
LOL.
That was the first time I connected the bugger, so I wasprobably still running Eclair when I tried it.
6.1.1 works well for me, both bluetooth calling and a2dp.
Theres a little fuzziness going on when nothing is playing, like white noise, but that's pretty much my only problem. No wait, there is one more thing actually, every now and then while music is playing it'll skip more or less a second
Just to add... I have to repair and disable/enable by every time I get in the car or the sound will drop out every 15-30s on any rom that uses froyo. GB seems to help where I only need to disable / enable bt. Kenwood x-993 with parrot bt. Using latest bt firmware.
Sent from my Nexus One using XDA App
PhantomRampage said:
Theres a little fuzziness going on when nothing is playing, like white noise, but that's pretty much my only problem. No wait, there is one more thing actually, every now and then while music is playing it'll skip more or less a second
Click to expand...
Click to collapse
This happens to me too once every three or four songs, but it's such a small thing it doesn't bother me much. On the other hand, for the short while I was using MIUI, I felt it was happening much less, but I may have been imagining that
Heres my setup, and it works flawlessly every time i start the car.
Car Deck: JVC KD-R900 (Using the small bluetooth adapter that came with the unit mounted in the back USB port)
ROM: Enomthers TheOfficial Nexus1 v2.14.3
Kernel: 2.6.32.35-TheOfficial-AudioMOD-720p
Radio: 32.41.00.32U_5.08.00.04
OS Version: 2.2.1
Like i said earlier i have no problems with the audio quality or connecting to my unit. As soon as i turn my Bluetooth on it connects within about a minute.
Calling quality is good, audio quality is good and AVRCP works also (play/pause/next/prev)
If you need anymore info just let me know.
Its good to see there is some reaction on the start of this.....
My goal is to achieve and to find out which components are involved in the Bluetooth experience:
F.I. :
* Kernel modules and libs
* Application in the rom to actually making the connection
* Bluez configuration and settings
I have done some searching but found that even with the same Bluez settings there can be a difference between some roms in combination with kernel.
jscat1 said:
Just to add... I have to repair and disable/enable by every time I get in the car or the sound will drop out every 15-30s on any rom that uses froyo. GB seems to help where I only need to disable / enable bt. Kenwood x-993 with parrot bt. Using latest bt firmware.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I have the same issue on my Kenwood system.
jscat1 said:
Just to add... I have to repair and disable/enable by every time I get in the car or the sound will drop out every 15-30s on any rom that uses froyo. GB seems to help where I only need to disable / enable bt. Kenwood x-993 with parrot bt. Using latest bt firmware.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Me too, same model. I've updated the firmware on the X993 and it seemed to help.
elfblackdeath said:
I have the same issue on my Kenwood system.
Click to expand...
Click to collapse
Same here on my DDX-812. Almost everything "works", I just get the drop-out when streaming music if it's not a fresh pairing.
The bluez stack was updated with Gingerbread...I'm hoping against hope that that fixes some things.
i have to use a no-audio-boost kernel with my jabra headset, otherwise the call quality is abysmal. lots of metallic clicking and other strange effects going on.
but i have seen no differences in the overall connection stability otherwise.
hmm i have a problem with my car dock and bluetooth i think. when using the navigation the voice plays via the phones speaker not the dock speaker. is this similar to the problem in the 1st post? if so, would love a fix!
I'm on CyanogenMod Nightlies with the included Kernel and have a Kenwood DDX8024BT with built in bluetooth. It connects up perfectly when I turn the ignition on and seems fine when in call. I don't use the A2DP much but when I have I've not had any problems.
Slightly OT, the only problem I have is with reading contacts from the phone. I have two phones paired. I usually have the Nexus connected but occasionally switch to my work phone (a Tocco Lite). At some point it took the contacts from my work phone and then wouldn't redownload the Nexus contacts when it was reconnected. It's now done it at some point but there's a handful of contacts that still won't transfer no matter what I try.
On a side note, I have a Clarion CZ500 rig in my car, and the N1 is incompatible with the microphone boost firmwares they offer on their site. All I hear is crackling when I try to make or receive a call.
What's odd is that the HTC Desire works fine with those firmware. Even Blackberry Pearl.
I ordered the N1 dock on eBay. I guess I'll see if the dock can handle the firmware.
i have a n1 and im still running cm 5.0.8 with android 2.1
my phone pairs with my car without any problems and i am able to talk to people and whatnot. Now as far as music, i use a blackberry music gateway bluetooth device that i plug into my car's 3.5mm jack and then i pair that device with my phones bluetooth. It pretty much connects automatically all the time and sound quality is awsome however as someone mentioned earlier in this thread, i get the occasional 1 second skip every so often. Does anyone have any idea whats causing this and how can i fix it? It is extremely annoying!!! I paired the blackberry gateway device with my gf's mytouch and there was no such problem, which leads me to believe that the problem is in my n1 :/
My $02: I cannot use a2dp and hands free at the same time. If both are connected the the a2dp drops out all the time.
This is not an issue with my HD7.
A workaround would be awesome.
Sent from my Nexus One using XDA App
I suspect the main difference, hardware combinations aside, between Stock/CM and Sense roms is that they use different bluetooth stacks.
Differences in the bluetooth stack that have caused issue for the FM radio on stock roms, an issues for bluetooth file transfer on Sense roms as far as I know.
Like iphone fanboys would say: fragmentation
On a related note the behavior of my N1 with the Parrot handsfree has vastly improved in GB.
i have the kensington liquidaux bt adapter in the car and cm7 rc4 with stock kernel skipped constantly. rc2 was better, but still unbearable.
i am currently on intersectraven's 4/3/2011 kernel and from limited use, has not skipped on me yet.
have people tried bt music streaming with other kernels with cm7 rc4? wildmonk? pershoot? etc.. thanks.
Try CM7 Issue 3233 fix
d1mitrov said:
It pretty much connects automatically all the time and sound quality is awsome however as someone mentioned earlier in this thread, i get the occasional 1 second skip every so often. Does anyone have any idea whats causing this and how can i fix it? It is extremely annoying!!!
Click to expand...
Click to collapse
Can you try the fix in Issue #3233 on the CM7 bug tracker? http://code.google.com/p/cyanogenmo...on Model Network Owner Summary Stars Priority
scotte9999 said:
Can you try the fix in Issue #3233 on the CM7 bug tracker? http://code.google.com/p/cyanogenmo...on Model Network Owner Summary Stars Priority
Click to expand...
Click to collapse
i think thats exactly what my problem is, when the phone is connected to the car and the music gateway is connected as well i get the intermittent connection and it skips every so often but if i disconnect the phone part then the music never skips...however im not on CM7 so i dont know if that fix applies to me and i dont know how to begin changing those settings
My droid would use whatever BT headset (stereo or not) for the phone when my headphone jack was also in use (to use car stereo) for audiobook player.
I have new Fascinate and I swear it did the same until I rooted it. Regardless, it will be close to a deal breaker if I cannot find a solution to this.
Even if the headset indicator is ON, the sound still goes to the headphone jack, RIDICULOUS
In my opinion, plugging into headphone jack should only take over media type output (music, audiobook player, video) and LEAVE PHONE ON BLUETOOTH. We should at least be able to chose this behavior in a setting.
So is this a Samsung screwup? do other Samsung devices behave this.
How hard would it be for a dev to build an app to FIX this on Fascinate.
I thought I was the only one with that situation... I would love to know the answer/fix, however I have a feeling someone will be by soon to move this to the general forum...
I actually wanted the opposite. Overall, I liked how bluetooth was handled on my old chocolate and was surprised by the differences in eclair. I expected my bluetooth to be able to grab all audio, regardless of what apps were running. For instance I wanted to use my BT with a fring call. Seemed sensible!
Anyway, I went searching, and the prevailing opinion was that bluetooth was locked up until Froyo (and tightly tied to actual calls).
Does anyone know if audio is handled in a gracefully way in current AOSP or CM?
Swyped w/ XDA App. When in doubt, mumble.
soba49 said:
I actually wanted the opposite. Overall, I liked how bluetooth was handled on my old chocolate and was surprised by the differences in eclair. I expected my bluetooth to be able to grab all audio, regardless of what apps were running. For instance I wanted to use my BT with a fring call. Seemed sensible!
Anyway, I went searching, and the prevailing opinion was that bluetooth was locked up until Froyo (and tightly tied to actual calls).
Does anyone know if audio is handled in a gracefully way in current AOSP or CM?
Click to expand...
Click to collapse
I believe that my Droid 1 behaved my desired way on 2.1 and 2.2, can't remember if I used this way on 2.0...
I was assuming this was a 'problem' on Fascinate or Samsung, not android OS in general.
I thinj its a problem with fascinate. I was driving for 5 hours last week and I had bluetooth connected to my garmin and used one of those cassette thingies to play music from my fascinate. Sometimes I were able to talk without unplugging the headset.
Another reason I suspect its fascinate is cuz when I use my old blackberry headphones I have unplug and replug to use it for conversations.
Btw whats good stereo heaphones with mic that works with the fascinate?
Sent from my SCH-I500 using XDA App
I have a friend with a Vibrant and his apparently does NOT have this problem, so I am wondering if a Bluetooth file from his system might work on my phone.
There are 3 BT files in system dump:
BT OPP
BT services
BT test mode
so is one of these the file that would determine what path audio would take in any given situation? (e.g. headphone jack occupied while BT headset connected, desired paths media>headphone phone>BT)
I REALLY need to fix this before my 30 days are up or phone probably going back.
I got my hopes up when I discovered the 'secret menu', but I don't see any setting in there that seems appropriate.
I've tested with the superclean 0.7 DL30 rom and this same problem still exists
Please let me know if anyone finds a solution.
[email protected] said:
i've tested with the superclean 0.7 dl30 rom and this same problem still exists
please let me know if anyone finds a solution.
Click to expand...
Click to collapse
stupid ass samsung friggin morons!
It looks like this is a problem on other Samsung Galaxy S phones as well, see a thread and app someone made in the Epic forums.
http://forum.xda-developers.com/showthread.php?t=842571
it is just the phone app
this problem is extremely frustrating. if i have headphones plugged in the mic works just fine. the mic is only turned off when i use an AUX cable. It would be nice to be able to drive and not have to worry about unplugging the AUX cable everytime I wanted to use my phone.
I downloaded the Epic app they made over there but all it did was hard lock my phone with my first test. I dug into the code but I'm a wee bit over my head so I'll hit up the books and see if I can't work with the guy who made the Epic one to see about getting it working with our phone.
This was with the .7 superclean DL30 rom, I'd love for someone else to try one of the other DL30 roms and see if they have any better success.
I contacted the author of the app and he replied back stating he had a buddy with a fascinate test it and it worked fine and that it might be an issue with the busybox version included with the .7 superclean 2.2 rom I was running and that it relied on busybox having the pidof command. Later tonight I'll dig into this a bit more and post back hopefully a fix and instructions on hwo to ensure this is working
I got this working http://forum.xda-developers.com/showthread.php?t=842571
The Froyo version works just fine on the original DL30 leak and on rubiks .3 DL30 but does NOT work on DL30 super clean .7 or .9. In .7 I got a hard lock that I had to do a battery pull to fix and in .9 the app ran and looked like it worked, but the audio routing did not change as expected.
All credit to cicada, I did nothing more than test it
I have not tested this on any 2.1 ROMS
thande said:
I got this working http://forum.xda-developers.com/showthread.php?t=842571
The Froyo version works just fine on the original DL30 leak and on rubiks .3 DL30 but does NOT work on DL30 super clean .7 or .9. In .7 I got a hard lock that I had to do a battery pull to fix and in .9 the app ran and looked like it worked, but the audio routing did not change as expected.
All credit to cicada, I did nothing more than test it
I have not tested this on any 2.1 ROMS
Click to expand...
Click to collapse
I am on original DL30 leak and did NOT work for me... at least with Ambling Book Player. Not sure if it matters what app we are using to play media file. It shouldn't, but this whole problem should not exist. SAMSUNG morons!
Ok so i tried with my Rubiks DL30 ROM installed. The app opens up, no FCs or bricks or anything, but it doesn't work. I had my wife call me when i was driving, I picked up and she said she could hear me but I still couldn't hear her. I'm assuming that the car's mic is functioning but it still doesn't fix the issue. Is there a bluetooth adapter out there i can stick in the aux jack? Well i guess the first question should be, can the phone handle having two BT devices connected at the same time? i.e. hands-free calling and BT audio adapter
I'd say maybe try another full wipe and re-flash. I've switched over to the superclean EB01 roms, currently on 2.3 and hasn't had any issues with this working on 2.1, 2.2 or 2.3. I did have 2.2 initially not function with this tool, similar to what you reported above with it looking like it was working but not actually doing anything but a full wipe and reflash did the trick.
ok... thanks, at least you've run into that problem so i'm willing to give it another go. I'm currently on SC 2.4 so i guess i can be your guinea pig
I'm on SC 2.4 currently and had it stop working on me again. At work now but I'm going to try setting the app off and then back on, I have had to do that sometimes when flashing as the files get overwritten. This was working properly in SC 2.3
Hey man, thanks for the updates and info... you're really like the ONLY person that's giving me any hope on this. I thought the compatibility issues were busybox related? So I don't see why it wouldn't work on SC2.4
Would someone please fix this on Fascinate... ? pleeeeezzzzzz
I know there is alot of issues with bluetooth for the TB. I was able to have full A2DP streaming with my DINC in my car but the TB and EVO wont even connect at all. I have a Sony XPLOD MEX-BT3800U. I was just wondering whats going on with the hardware compatibility and if there are any possible ways to create compatibility. What exactly is not compatible? Is it the ROM, KERNAL or RADIO? Hardware or software profiles? If someone could answer how it all works from a development / engineering standpoint that would really ease my mind. Just curious if I should throw down another few hundred on a new radio for my car or if I should just wait for software fixes.
Thanks
loccoelf said:
I know there is alot of issues with bluetooth for the TB. I was able to have full A2DP streaming with my DINC in my car but the TB and EVO wont even connect at all. I have a Sony XPLOD MEX-BT3800U. I was just wondering whats going on with the hardware compatibility and if there are any possible ways to create compatibility. What exactly is not compatible? Is it the ROM, KERNAL or RADIO? Hardware or software profiles? If someone could answer how it all works from a development / engineering standpoint that would really ease my mind. Just curious if I should throw down another few hundred on a new radio for my car or if I should just wait for software fixes.
Thanks
Click to expand...
Click to collapse
Personally , I would wait for a software fix. But sometimes that might not help also. But I have some issue sometime when streaming to my radio bluetooth with a little disorder sound sometimes. Very lite.
loccoelf said:
I know there is alot of issues with bluetooth for the TB. I was able to have full A2DP streaming with my DINC in my car but the TB and EVO wont even connect at all. I have a Sony XPLOD MEX-BT3800U. I was just wondering whats going on with the hardware compatibility and if there are any possible ways to create compatibility. What exactly is not compatible? Is it the ROM, KERNAL or RADIO? Hardware or software profiles? If someone could answer how it all works from a development / engineering standpoint that would really ease my mind. Just curious if I should throw down another few hundred on a new radio for my car or if I should just wait for software fixes.
Thanks
Click to expand...
Click to collapse
I have the exact same stereo... no.problems with bamf 1.6.1 or cm7 test 4
Maybe its your stereo
Sent from my ThunderBolt using XDA Premium App
loccoelf said:
I know there is alot of issues with bluetooth for the TB. I was able to have full A2DP streaming with my DINC in my car but the TB and EVO wont even connect at all. I have a Sony XPLOD MEX-BT3800U. I was just wondering whats going on with the hardware compatibility and if there are any possible ways to create compatibility. What exactly is not compatible? Is it the ROM, KERNAL or RADIO? Hardware or software profiles? If someone could answer how it all works from a development / engineering standpoint that would really ease my mind. Just curious if I should throw down another few hundred on a new radio for my car or if I should just wait for software fixes.
Thanks
Click to expand...
Click to collapse
I had a similar problem with my factory radio on my Ford Fusion. I resolved my problem by updating firmware on the factory radio (MS Sync) and running the leaked radio update for TB and a stable Rom like Perfect Storm 1.4 and 1.11 batsaver kernel. My issues were resolved, I was having problems with pairing, when it would pair I would lose connection within 1 to 2 min and could not regain. Very fustrating. I attribute most of my issues with OC of TB I was too aggressive running what I thought stable at 1.5 Ghz.
Sent from my ADR6400L using XDA Premium App
I had some similar issues with my stock TB loosing bluetooth connectivity with my car. I would get in the car, it would connect, then a minute later disconnect. Turns out, I was able to fix it by unpairing, then reparing; and denying permission for the car to download the phonebook from my phone. Something in my contact list was causing the issue.
Weird about the phonebook
Sent from my ADR6400L using XDA Premium App
I have the Sony MEXBT2700 and it worked great with the tb at first, but then it, the tb, started acting up whenever I would turn the car off. This was one week after launch day for the tb. It would literally cut all sound off on the phone till I restarted, so I ended up calling verizon, then sent me a new phone about two weeks after launch day.
Since then it has been working perfect, sq isnt great, but its better than doing bluetooth from my Macbook pro.
If you've got a Ford with Synch
Just in case you've got a Ford vehicle with Synch, there is seemingly random problem that sounds like this and I posted some info over at Ford Syncmyride site. In a nut shell, simply pull the fuze for the system wait about a minute and then replace. If you're like me and you couldn't find the correct circuit disconnect battery cable.
Seems the system needs to do a "battery pull". Only have experience with the Ford Sync but that's my .02 and I hope it helps.
I have sync in my '08 focus and i've never had issues with any of my phones streaming music or placing/receiving calls.
TheDanimal said:
I have sync in my '08 focus and i've never had issues with any of my phones streaming music or placing/receiving calls.
Click to expand...
Click to collapse
Me neither, I have a 2010 F-150 and I have had no issues with Sync.
Sent from my ADR6400L using Tapatalk
Bluetooth with my TB to my JVC headunit has been rather problematic for me. What I did finally discover was that if I didn't allow for phonebook syncing, all is well. I am currently on Das BAMF 1.6.1 and now have perfect streaming of music and calls as long as I deny that silly phonebook.
Hope that helps.
Hate to make my first post an issue post, but I have searched all over XDA for the answer and couldnt find anything particular to my issue. I flashed CM10 to my phone and noticed my Bluetooth would turn on but would not pick up any devices in device search. I tried multiple speakers and headsets and nothing would work. I did a hard wipe and installed MeanBean thinking that it was a ROM related issue. Tried it again on MeanBean and same issue. I tried fixing permissions and Bluetooth Fix app and still nothing. Can anyone help?
(I am on the latest radio/firmware and v.06 MeanBean)
Same exact issue !
cauger24 said:
Hate to make my first post an issue post, but I have searched all over XDA for the answer and couldnt find anything particular to my issue. I flashed CM10 to my phone and noticed my Bluetooth would turn on but would not pick up any devices in device search. I tried multiple speakers and headsets and nothing would work. I did a hard wipe and installed MeanBean thinking that it was a ROM related issue. Tried it again on MeanBean and same issue. I tried fixing permissions and Bluetooth Fix app and still nothing. Can anyone help?
(I am on the latest radio/firmware and v.06 MeanBean)
Click to expand...
Click to collapse
My evo lte has been doing this for as long as i can remember also. I've been through dozens of roms and full wipes and still no bluetooth at all, not even recognizable.
Try deleting everything that is paired or was paired and then reboot. You may have Bluetooth defects if that still doesnt work. I have used on many sense roms, cm10, 10.1 varients with no problems. Hope that helps.
Sent from my EVO using xda app-developers app
Im having the same issue
I have updated my radios and noticed that i lost my Bluetooth connectivity. I was originally running meanrom ics until JB came around. Then updated my radios and moved to JB MeanBean. I did an Ruu and got it back to stock. No dice, stock rom Bluetooth still cannot find or be found. I tried my laptop ipad macbook car audio everything and nothing works. I ve never had any issues with my phone and it seems after Jelly Bean Bluetooth is non existent.
Currently I am running
Twrp 2.3.1
Arc Reactor Kernel
MeanBean3.09
Is there a way to see if the actual Bluetooth is borked or if its working properly, "if its sending a signal"?
Is it possible that something happened when upgrading that the BlueTooth became corrupted? or can it just plain old stop working, died?
At that point if it's Borked on several roms
Then it's time to take it into sprint. That's a manufacturer defect / issue and they should swap it out. Assuming you bought legit from them
Sent from my EVO using Tapatalk 2
Yes I bought it legit when it came out. I also have the insurance plan with Sprint. The only thing I'm worried about is the new hboot and unlocking/rooting the new phone .
But I guess if it means a new phone then I guess its best... To get a fresh new evo
Sent from my EVO using xda app-developers app