I upgraded from 1.0.6 to 1.0.7 and found that my bluetooth was no longer syncing with the car. I Odined back to DI18 and found that bluetooth was fine..I deleted the pairing from the car and the phone...installed DK28 and reinstalled Nebula 1.0.7 and still have the same problem. I am not sure why the bluetooth thing stopped working. The car syncs with the rest of the bluetooth enabled devices I have.... Nebula 1.0.6 was working fine...
I don't know anything about nebula rom. The.best thing you can do is post this on The roms thread and people familiar with the rom could help you. Sorry I couldn't help you anymore.
Sent from my Evo Killer!!!
I had a similiar problem. My bluetooth devices would show up as a mac address instead of the model name and would not connect. I couldn't find an answer for this and odin'd back to DK28 and put ACS signed ROM on and Bluetooth is fine so not sure if it was one of the files removed from Samsung or Sprint in 1.0.7 but decided not to try it until someone else has the same problem. But yours sounds a little different then my problem. I read somewhere that your Bluetooth device might need a hard reset since you are only having trouble with one. Find out how to that for that device. Each is different.
Thanks for the help guys....i was not able to post in the dev section earlier but was able to now. Posted it there.
Sent from my SPH-D700 using XDA App
Related
Hey all, so I recently switched from a 1.47-based back snack to the newest froyo-based baked-snack and/or fresh and since then my wireless tether has gone the way of the dodo. Wireless tether seems to be launching and broadcasting but is not allowing connections from PC/MAC laptops (tried both). I've additionally tried the most recent FRESH ROM as well as the stock netarchy build and in all cases I can't get any connections from other computers (I don't even get the request or notification of an attempt to connect in wireless tether) As far as I can tell I don't have a MAC address issue of any sort.
Any ideas?
Wifi and 3G seem to be functioning fully, as well as everything else I've tested.
NOT Q/A
npgeorgeuw said:
Hey all, so I recently switched from a 1.47-based back snack to the newest froyo-based baked-snack and/or fresh and since then my wireless tether has gone the way of the dodo. Wireless tether seems to be launching and broadcasting but is not allowing connections from PC/MAC laptops (tried both). I've additionally tried the most recent FRESH ROM as well as the stock netarchy build and in all cases I can't get any connections from other computers (I don't even get the request or notification of an attempt to connect in wireless tether) As far as I can tell I don't have a MAC address issue of any sort.
Any ideas?
Wifi and 3G seem to be functioning fully, as well as everything else I've tested.
Click to expand...
Click to collapse
THIS IS DEV SECTION! Not Q/A... Please go to General Section
Fail.
Sent from my PC36100 using XDA App
Seems to me a developer's section would be the appropriate place to post if I am having a recurring permanent problem post-installation of a developer's ROM.
-Just checking to see if anyone else might have seen this same problem, post ROM.
No need to be male genitalia.
I have tether working on calkulin evio rom. Test different versions,v visit the developers page. Pre 2 seems to be working best imo.
Sent from my HTC Evo using Tapatalk.
Haven't heard of this issue. You said you're running the netchary kernel on fresh right? What version of wireless tether are you running?
Thanks gmaine. I've tried both the Pre 2 that came with the backed snack rom and whatever version came with Fresh, and both had the same problem. Uninstalling and reinstalling whatever the current version is in the marketplace as well didn't work. It feels more and more like a hardware issue, though nothing else is funky at the moment.
Am currently running the netarchy update froyo kernel and have tried new and old version of wireless tether.
Try uninstalling the current tether app and using this one.
I'm running fresh 3.1.0.1 and using pre 7 of wireless tether and having no problems. Try uninstalling what you have now and install pre 7 from here http://code.google.com/p/android-wifi-tether/downloads/list?can=2&q=Evo
am installing, etc, now.
npgeorgeuw said:
Seems to me a developer's section would be the appropriate place to post if I am having a recurring permanent problem post-installation of a developer's ROM.
-Just checking to see if anyone else might have seen this same problem, post ROM.
Click to expand...
Click to collapse
The you should probably post in that specific ROM's thread.
for the netarchy kernel many are using Pre6. Some ROM's require the new Pre7.
Pre7 works on the Stock netarchy build for me and is mentioned several times in that thread.
gmanvbva said:
The you should probably post in that specific ROM's thread.
for the netarchy kernel many are using Pre6. Some ROM's require the new Pre7
Click to expand...
Click to collapse
Totally agree with you on that one, but didn't get my answer after a few days and tens of pages of posts later.--So of course, that was the first route I went. (Everyone seemed to busy arguing about PRI downgrades, but I digress.)
Anyways, the .apk that was just linked works, although I'm really not seeing the difference between it and the marketplace wireless tether and reinstallation. Either way, things are working now, thanks for those of you with constuctive advice!
I just wanted to share some info here in case anyone else was having this problem. I installed a Kenwood KIV-700 with the KCA-BT300 bluetooth addon. It connected and paired with the phone just fine, however, I noticed that I could not get contacts to sync, tried deleting and reconnecting the phone from head unit several times. Then it occurred to me that it could be my ROM (was using CM6 RC1 at the time). I flashed to AVA-FROYO6, thinking that maybe since it is closer to the stock ROM, that the phonebook would sync. It worked and now I am completely syncing with the unit. To be fair, I have not updated CM beyond RC1, as I was happy with it, so didn't feel the need to update to 2 yet, so maybe this worked in the later version.
My guess is that Kenwood works off of stock ROMS and this could be the reason that CM6 did not work completely with it. Anyway, hope this helps someone.
Cool I've got that BT add on sitting in the garage awaiting my install.
Thanks.
dougdascenzo said:
I just wanted to share some info here in case anyone else was having this problem. I installed a Kenwood KIV-700 with the KCA-BT300 bluetooth addon. It connected and paired with the phone just fine, however, I noticed that I could not get contacts to sync, tried deleting and reconnecting the phone from head unit several times. Then it occurred to me that it could be my ROM (was using CM6 RC1 at the time). I flashed to AVA-FROYO6, thinking that maybe since it is closer to the stock ROM, that the phonebook would sync. It worked and now I am completely syncing with the unit. To be fair, I have not updated CM beyond RC1, as I was happy with it, so didn't feel the need to update to 2 yet, so maybe this worked in the later version.
My guess is that Kenwood works off of stock ROMS and this could be the reason that CM6 did not work completely with it. Anyway, hope this helps someone.
Click to expand...
Click to collapse
Well back to the drawing board. Eventually I got the same Hf-68 error again with Ava's ROM. Then I went to CM6 (release version this time) with King's first CM6 kernel and it worked for the entire time I ran that (about 3-4 weeks). Then i started having some unrelated issues so I decided to try Virus's new sense ROM based off of 3.28 leak release (RC2) with King CFS7 and low and behold I get the error again every time during the point when it is downloading the phonebook.
I am going to try Virus's senseless when he finishes uploading it and try that. I wonder if it has anything to do with the sense contacts...
So frustrating when you buy an expensive piece of equipment and it works so inconsistently.
i installed eb13 froyo and rooted my phone with cwm3.0.0.5 , then flashed viper rom trinity 2.0 with the eb13 genocide 1.2 ghz..everything seems to be very good and fast, but so far i have noticed that the blue tooth is not connecting. does anyone have any answers to why bluetooth is not connecting?
so i toggled around with my settings and now my bluetooth is working allowing me to answer phone calls and talk on the phone but the only thing that my bluetooth doesnt do is allow me to give voice commands when i tap on the button on my blue tooth!!! any advice anyone?
How did you get the headset to take calls?
Bluetooth Issues - Summary of Testing Results
This is a problem that goes away if I simply go back to a DK28 based ROM (which I have no plans of doing), but appears with any flavor of the EB13 update available.
On a day when I didn't have a lot to do, I decided to do some testing to see if I could find the magic combination of EB13 loading (upgrade.apk, ODIN .tar/.pit load, Samsung SWUpgrade and the DEODEXed [stock-ish] ROMS available) to get my bluetooth working like it does on DK28. I have upgraded to EB13 stock, EB13 deodex, deodex w/EXT4 (no member ROMS yet) along with stock/Genocide/Daemon's kernels ... essentially every mix of install, ROM and Kernel available. Add to that, I also cleared data on the OPP application --- I tried to cover every base I could. That being said, I have narrowed down my list of issues with bluetooth on EB13 to:
Paired devices are not saved. I have a Jawbone ICON and I have to add it everytime my phone is rebooted.
(Only add once on DK28)
Unable to Pair and Connect on first attempt. It always takes at least 2 and most of the time 3 presses of Pair and Connect to get the Jawbone paired and connected.
(Paired and connected on first attempt on DK28)
When my Jawbone pairs up, if you watch the notification bar closely, my wifi will also do a quick off/on right after the notification shows "Paired" on the Jawbone. Before you ask - yes, I ran tests with the various radio's on and off just to see if that was the cause. Nope.
(Never saw this on DK28, but then again was not watching for it either)
Like others have said, I can voice dial using the Voice Dialer application on the phone, but I cannot voice dial by pressing and holding the voice dial activation button on the Jawbone (the start/stop/quick disconnect happens on the application).
(Press button, state name, call on DK28)
It did not matter what combination of the above I used, the result was always the above. I'll gladly assist in troubleshooting this issue, so if anyone out there knows what to look for in the logfiles, I'll gladly run a pair/connect sequence and capture the adb logcat output for review.
Thanks in advance ... None of these are showstoppers, in fact I love EB13 and also appreciate all the hard work done by the devs and contributors in these forums (plus I guess I need 10 posts now to add anything relevant to a dev thread ).
- Dan
If you use Titanium Backup and have backups from before the update, please read this:
I was having the same problem with bluetooth on EB13. Just before ODINing back to DI18, I decided to try this:
1. In Titanium Backup>Backup/Restore, find these three items backed up from a previous kernel: Bluetooth Pairings, BluetoothTest 1.0, BrcmBluetoothServices 1.0. --Touch and restore each one of these.
2. Go to Home>Menu>Settings>Wireless and Network>Bluetooth Settings (turn on bluetooth): If your device is listed as paired, unpair it. Pair it again as a new device.
This worked for me, except voice-dial through my Jawbone is force-closing (but I honestly don't know if it ever worked right anyway). At the very least, it is now pairing and connecting fine and staying connected for calls and music.
P.S.
I suppose if you don't already have a backup of these items you could ODIN back, get Titanium Backup, backup all apps and system data, then update to EB13 all over again and restore the bluetooth data.
If you flash the acs frozen rom bt voice dialing works and the rom is very fast and very smooth. The best rom I've seen yet.
I've been having problems with Bluetooth on MidnightROM 4.2. The Bluetooth is extremely flaky -- sometimes pairs, sometimes doesn't -- doesn't stayed paired.
I haven't struggled with it too much because I never used Bluetooth much, but I would like to know if there's a fix.
jbadboy2007 said:
If you flash the acs frozen rom bt voice dialing works and the rom is very fast and very smooth. The best rom I've seen yet.
Click to expand...
Click to collapse
ACS has these same issues. It is a EB issue and I find I am having the same problems.
It seems like since I have been using gingerbread 2.3.4 I am having some major bluetooth issues. My devices seem to disconnect at random both my headset and car system. I will check my phone setting in bluetooth and it is not showing any devices even paired, or even there at all. I have to reboot the phone and then they may or may not show up. Another issue is contacts taking forever to show up in my car pioneer system. They show up sometimes and sometimes they don't. When they don't I look in the settings and sure enough even though my phone is connected to the car there are no devices showing in the settings. Another thing that happens is even though I have gotten out of the car and shut it off, my phone will stay connected to the pioneer system. It does this on our truck's system as well so it is not the pioneer. The truck is a Ford f150 and uses sync. When I was on 2.2 SF 1.2 I had zero BT problems, in fact I am back on it and my contacts show up on my car instantly now.
My question is this, is this a know problem, is anyone else having BT issues. I searched but could find nothing on this.
Thanks.
I have had zero bluetooth issues on the Gingerbread leaks but only use a cheap Samsung earpiece, no fancy car docks or anything. Have you tried different leaks and installed the EG22 modem?
I have a Moto Finiti Bluetooth and another cheaper one. They have seemed to be working perfect for me
Sent from my SPH-D700 using XDA Premium App
This is the one I have used
[Odin]Stock EG22 Deodexed with CWM 3.1.0.1/Root/Busybox 1.18.4
I have also added in the hotspot mod, I also recently flashed the theme but the issues were happening before I did this. I may try starting over clean. What is are you using?
redram38 said:
This is the one I have used
[Odin]Stock EG22 Deodexed with CWM 3.1.0.1/Root/Busybox 1.18.4
I have also added in the hotspot mod, I also recently flashed the theme but the issues were happening before I did this. I may try starting over clean. What is are you using?
Click to expand...
Click to collapse
Wow, good question. I believe it was Go Green and Scrambled Eggs
Sent from my SPH-D700 using XDA Premium App
redram38 said:
This is the one I have used
[Odin]Stock EG22 Deodexed with CWM 3.1.0.1/Root/Busybox 1.18.4
I have also added in the hotspot mod, I also recently flashed the theme but the issues were happening before I did this. I may try starting over clean. What is are you using?
Click to expand...
Click to collapse
If you Odin'd that in then you probably also have the EG22 modem as your baseband. I am on Bonsai B14 EG22 based ROM.
Yes try it from scratch and check it each step of the way to find out where the issues develop.
I have the same problem periodically with my Audi. I'm on SRF 1.2 Genocide kernel, EC05 modem.
elevans said:
I have the same problem periodically with my Audi. I'm on SRF 1.2 Genocide kernel, EC05 modem.
Click to expand...
Click to collapse
Any ideas of what could be causing this problem or how to resolve it?
Since I went back to SF 1.2 I am not having near the issues I did. My contacts show up within seconds now.
I am using NexusMod ICS Zero - [4-19-12] Modified for T989 - 2nd Release
I try to flash with SuperWipe, without superwipe, Darkside Superwipe, M&S Kernel clenser, with format everything, with clear everything.
Don't know what else I should try.
how come when I come back to my restore (which is easydoes ICS ROM) the bluetooth works fine (I have to re-pair in my car after restore, because I clear the bluetooth system in my car evertime I pair the new rom)?
For me bluetooth didn't work for any of the new UCLD2 ROMS.
The bluetooth worked on the earlier ICS leaks.
Here is the LogCat for the crash
LogCat Link
Thanks,
here is the logcat for the fresh install and fresh test with the car bluetooth.
Can someone tell me what direction I should look at?
just flash your stock rom/ or just radio
there is no ICS Stock Rom available for flashing.
and I did flash the LB7 radio
I tried Gingerbread stock works fine....
then install NexusMod and same issue.
UCLD2 broke bluetooth for me also (Skyrocket). Works fine on the first ICS leak though (UCLC something).
It pairs to my JVC car stereo.
But buzzes/crashes when trying to stream.
Bluetooth will turn on/off over and over.
I still not able to find any fix or way around.
Please update this thread if you find one.
Sent from my SAMSUNG-SGH-T989
Eddie
What is the version of your cmw?
I am on 5.0.2.7
Not cmw touch. Dunno maybe its working with cmw touch only.
Sent from my SAMSUNG-SGH-T989
I read it on skyrocket forum the Dev said on nexusmod thread that you have to be on cmw touch.
I update my cmw to touch and then reinstall the ROM and that didn't help either.
That's weird. Have no clue why Bluetooth is not working...
Anyways back to the first leak for now...
Sent from my SAMSUNG-SGH-T989
As I stated in the NexusMOD thread, bluetooth integration to my car is broken as well. Haven't tried v3.3 yet nor have I tried the make nandroid -restore from nandroid trick mentioned in the T989 NexusMOD thread... Am still hopeful that a new leak will come out with a different BT stack which fixes this
-greenboy- said:
I still not able to find any fix or way around.
Please update this thread if you find one.
Sent from my SAMSUNG-SGH-T989
Click to expand...
Click to collapse
I noticed "bluetooth" kept showing up on my CTS stereo like it was connecting. Under bluetooth click menu button and set visible timeout (mine was set to 2 minutes). I set mine to unlimited, since then it stopped showing up on my stereo.
wave_sailor said:
I noticed "bluetooth" kept showing up on my CTS stereo like it was connecting. Under bluetooth click menu button and set visible timeout (mine was set to 2 minutes). I set mine to unlimited, since then it stopped showing up on my stereo.
Click to expand...
Click to collapse
Thanks for the feedback.
I re-install the ROM with 3.8 update and tried your method but that still not stop crashing the BT and transferred the call to the handset and disconnect from the car BT.
I guess I have to wait for the new leak with the hope that it will not have this issue.