I'm trying to set up a tasker profile that would work around when my laptop is on with bluetooth, my phone would connect and run the appropriate Tasker profile. I can pair the phone but it just sits at "Paired but not connected". Is this even possible or do I need an app like Bluetooth File Transfer to generate the constant connection.
Inc2 w/ CM9 AOKP build 22 (happened with MIUI 11.25 & 12.9 as well)
Macbook Pro most recent model
I have had the same problem with CM builds. I have found that sense roms for this phone has much better BT connectivity. I use Locale alot, and it just seems to work better with sense roms. I have not tried any apps to help though.
420fan said:
I have had the same problem with CM builds. I have found that sense roms for this phone has much better BT connectivity. I use Locale alot, and it just seems to work better with sense roms. I have not tried any apps to help though.
Click to expand...
Click to collapse
Thanks, i had a feeling Sense base would work better.
Related
Hi All
I'm trying to track down a rom which has Bluetooth DUN installed. CyanogenMod 5.0.8 test 7 has it installed but the rom is a wee bit buggy. Any recommends?
TiA
I.
Bumpty Bump
I'm just wondering, why do you need BT DUN when you have wifi tethering?
I need bluetooth DUN so my TomTom GPS can talk to my phone
Try to search "pda net" in Market. Is it what you want ?
Hi
Nope been there, tried that
It does not have full DUN, i.e. it won't talk to TomTom. Sent them a email asking for help.
IrishBiker said:
I need bluetooth DUN so my TomTom GPS can talk to my phone
Click to expand...
Click to collapse
does tomtom work on android ???
Yes, install CyanogenMod 5.0.8 test 7 and Tomtom will work with traffic updates (which is what I want DUN for). This early test is just a wee bit buggy for day 2 day use.
Its an issue that has been long outstanding:
https://code.google.com/p/android/issues/detail?id=1416&colspec=ID Type Status Owner Summary Stars
There is even a module which could be compliled, which is in 5.0.8 test 7:
http://github.com/wertarbyte/android_vendor_cyanogen/blob/omni-tether/prebuilt/common/bin/tether
pmub bump
I agree, it would be nice to have this
Might have a play see if its possible somehow. Busy schedule though, but I'll say if I have any success...
because CM5 supports it, maybe CM6 supports it, too. And if CM6 supports it, then maybe OpenDesire and DeFrost which are mods of CM6, too.
I've tried both cm6 and frost. Both from what I can see neither has it installed. Anyone else confirm?
Sent from my HTC Desire using XDA App
*UPDATE*
I've now tried both (thanks to Rom Manager) and neither have BT DUN.
Bumpty Bump
Things that go BUMP in the night
.PMUB|BUMP.
Any luck in finding anything?
So it seems Bluetooth DUN is not very popular these days (probably because most are using WiFi which is faster, in terms of speed and battery drain).
But I really need it for my new Mercedes C-class which has 'Comand Online' with internet connectivity based on BT DUN. Currently only most Nokia and Blackberry models are supported because they have native Bluetooth DUN.
Programs like PdaNet won't work because they need a client running on the device and I obviously cannot install anything on the Comand Online (no it's not a typo ) system of the Mercedes.
Any suggestions for a decent BT DUN program or Android ROM/kernel? A proper BT DUN implementation should obviously be done in the kernel. I read reports that Moto Droid X devices had success in similar scenario's and CM5 was supposed to have it in it's kernel... :-(
Anyone?
Bump...anyone?
This would be great but i think its a goooooole thing...
The only way i think thiswill happen is with a custom rom.
hey there,
I have successfully connected my bt keyboard to a galaxy s running froyo, and to an Iphone 3gs. it worked flawlessly with both.
It doesn't work with my defy running cm7, didn't work with the betas and it doesn't work with rc0 or rc1. I can't downgrade my phone to froyo to test it
I can use it with Blueinput and bluekeyboard jp, but with either of them the connection is very flaky, and it disconnects after 5 seconds to 5 minutes. I can't figure why.
I'd love to try copying a couple of files from a system that I know it's working on to my phone, but alas - I don't know where to start digging. can you tell me which files are responsible for bt connectivity? the hid profile file and such?
Thanks a lot for your help
Shawn
Does anyone know how to enable the bluetooth SPP profile for any of the Sense 3.5 ROMs? What I would like to do is tether my GPS location to my Win7_64bit laptop. Verizon's latest OTA has it enabled and my laptop configures the modem/COM port just fine, but when I try to connect to any of the newer Sense 3.5 ROMs my laptop doesn't detect the SPP feature from my phone and doesn't create a COM port, but creates the other audio features.
Could it be as easy as copying the bluetooth.apk from the Verizon OTA and installing it in one of the 3.5 ROMs?
make a backup and try and let us know
Snag ShareGPS from the market, it will turn your phone into a bluetooth GPS transceiver.
Weselers said:
make a backup and try and let us know
Click to expand...
Click to collapse
I tried that, phone kept restarting when I went into Bluetooth settings. Understandable.
Nova5 said:
Snag ShareGPS from the market, it will turn your phone into a bluetooth GPS transceiver.
Click to expand...
Click to collapse
Thank you for the suggestion! Funny though that I tried this about a day before you replied! I'm such a noob So it seems that the OTA with its DUN, I think, tells my laptop that there's a COM port, and is constantly running, which now makes complete sense. I think it was when I was trying ShareGPS, and actually had it running when I added my phone as a bluetooth device, that I noticed the Serial Port (SPP) within the services of my phone properties on my laptop. The other times I didn't have any GPS tether app running when I added my phone, or any app that creates a bluetooth serial port for that matter, so the SPP service was not listed...brilliant Great learning experience though! In the end I prefer GPS over BT though...guess I'm a sucker for tons of info
I have been running SkyNote 8.2 for a while now and have really liked Sean's ROM. I flashed Liquid last week (also a great ROM) and noticed something that I found confusing. With the TW Bluetooth (including the stock ROM), my 2009 car didn't really react well to the Bluetooth in my Note II. The connection between the car and phone would constantly connect and then drop off, connect again then drop off. Once I was on the phone (call), after initialing disconnecting me, the connection would stay but once I hung up it would go back to the on off cycle. My contacts would not sync either and yes I did grant access to the contacts. I just assumed it was because the phone has a newer Bluetooth profile (4) than my car (3). But after flashing Liquid my Bluetooth connection was fine, never dropped off and my contacts were all visible. I don't know much about the inner workings of Bluetooth, is the difference a TW thing?
Just looking for some insight from folks smarter than me.
Bump.... I would also like to know
AOSP only has Bluetooth 3.0 right now, so that's probably why you get more information. I have a FitBit and it only works with TouchWiz since it uses Bluetooth 4.0.
This is a fairly well known issue, but I haven't see a good summary anywhere, so I'll try here.
The problem isn't so much TW vs AOSP, it is Jellybean versions 4.1.x vs 4.2.x. Touchwiz is 4.1.2 and most maintained AOSP ROMs are 4.2.x.
Google, though their ultimate wisdom, decided to effectively castrate 4.2 by switching the Bluetooth stack.
From Android.com
New Bluetooth stack
Android 4.2 introduces a new Bluetooth stack optimized for use with Android devices. The new Bluetooth stack developed in collaboration between Google and Broadcom replaces the stack based on BlueZ and provides improved compatibility and reliability.
Click to expand...
Click to collapse
So...
Jellybean versions 4.1.x use the opensource BlueZ stack
Jellybean versions 4.2.x use the quasi-opensource Broadcom/Google stack called Bluedroid,
4.2.x has documented issues with audio streaming which are attributed to A2DP, or the Advanced Audio Distribution Profile. Google has proposed a fix, but the community consensus is that the issue remains.
Another problem with 4.2.x is that it doesn't support AVRCP 1.3 like 4.1.x did. This means that track metadata is not available to devices on 4.2. This is bad for me since I like to see track information when I connect the phone to my BMW M3.
I'm sure there are some workarounds on this problem, but I am not aware of a single, silver-bullet solution to make BT work flawlessly on 4.2.x Roms.
In summary, if you want to use Bluetooth in any meaningful way, stick with 4.1.x builds until Google gets their **** together. This is a fairly large miss on their part and they have been slow to address it.
Anyone know of any updates to this? There are so many 4.2.x ROMs out there that i love, but without a good BT A2DP connection, i just cant use that as the regular ROM.
ZoinksS2k said:
In summary, if you want to use Bluetooth in any meaningful way, stick with 4.1.x builds until Google gets their **** together. This is a fairly large miss on their part and they have been slow to address it.
Click to expand...
Click to collapse
Hi. I'm loving Android 4.2.2. I've noticed one parity difference though when it comes to auto connecting to my car's bluetooth dongle (It's a belkin aftermarket one). I've tried LiquidSmooth, rootbox nightlies, DeviantXone, etc. I've probably tried 7-8 different brands of ROMs. I've noticed though that on 4.2.2, bluetooth auto connect isn't alike on all of them. For some of them, bluetooth always auto connects with my Belkin receiver in the car. On the other ones, maybe sometimes.
I'm wondering if this perhaps has to do with deep sleep because I've noticed that (perhaps not coincidentally) on the ROMs where it always auto connects just fine, battery life tends to be a lot weaker. For a given ROM, I've tried changing the kernel from Ktoonsez, Lean, etc...no difference. For me, it's the ROM that makes the difference, not the kernel.
I've looked in /system/etc/bluetooth and perused through the .conf files. I could have sworn there used to be an auto sync related parameter but can't seem to find it. I don't know if maybe it's some parameter in a conf file somewhere. It would make sense that attempting to always auto connect with nearby devices would result in more of a battery drain.
Any ideas? Is it a setting or something ROM specific? Can it be changed by the end user of a ROM? I am trying to avoid bluetooth auto connect apps on the market since I also don't want a kernel wakelock being used for a service that never sleeps. That may really hinder battery. Thanks!
davidisflash said:
Hi. I'm loving Android 4.2.2. I've noticed one parity difference though when it comes to auto connecting to my car's bluetooth dongle (It's a belkin aftermarket one). I've tried LiquidSmooth, rootbox nightlies, DeviantXone, etc. I've probably tried 7-8 different brands of ROMs. I've noticed though that on 4.2.2, bluetooth auto connect isn't alike on all of them. For some of them, bluetooth always auto connects with my Belkin receiver in the car. On the other ones, maybe sometimes.
I'm wondering if this perhaps has to do with deep sleep because I've noticed that (perhaps not coincidentally) on the ROMs where it always auto connects just fine, battery life tends to be a lot weaker. For a given ROM, I've tried changing the kernel from Ktoonsez, Lean, etc...no difference. For me, it's the ROM that makes the difference, not the kernel.
I've looked in /system/etc/bluetooth and perused through the .conf files. I could have sworn there used to be an auto sync related parameter but can't seem to find it. I don't know if maybe it's some parameter in a conf file somewhere. It would make sense that attempting to always auto connect with nearby devices would result in more of a battery drain.
Any ideas? Is it a setting or something ROM specific? Can it be changed by the end user of a ROM? I am trying to avoid bluetooth auto connect apps on the market since I also don't want a kernel wakelock being used for a service that never sleeps. That may really hinder battery. Thanks!
Click to expand...
Click to collapse
The audio.conf is no longer there in 4.2.2. I've read something about the BT stack being re-engineered. Someone on xda has released some replacement libraries for BT and I suspect compiling a new library might be the only way to make changes similar to the previoud audio.conf file changes. This really sucks and there are not too many people who know enough about this sort of thing. Also, the android documentation for bluetooth is not helpful.
As for me, I am trying to get by BT audio working well again. Right now audio is skipping pretty bad streaming to my Kenwood (Parot) Bluetooth headunit. I know what settings I need for audio.conf to make this work, but have no idea what to tweak in Android 4.2.2.
HELP PLEASE
gg48gg said:
The audio.conf is no longer there in 4.2.2. I've read something about the BT stack being re-engineered. Someone on xda has released some replacement libraries for BT and I suspect compiling a new library might be the only way to make changes similar to the previoud audio.conf file changes. This really sucks and there are not too many people who know enough about this sort of thing. Also, the android documentation for bluetooth is not helpful.
As for me, I am trying to get by BT audio working well again. Right now audio is skipping pretty bad streaming to my Kenwood (Parot) Bluetooth headunit. I know what settings I need for audio.conf to make this work, but have no idea what to tweak in Android 4.2.2.
HELP PLEASE
Click to expand...
Click to collapse
+1 I have the same problems with my head unit. I'm hoping someone can fix this