Related
I was wondering if anyone else is having issues with bluetooth on their Archos 101. I can't tell if perhaps my hardware is flaky, or if its a software issue.
Basically, bluetooth seems to work sporadically. Sometimes it pairs like it should, other times it is a fight just to get it to pair with my phone, laptop or bluetooth keyboard. Often times I have to reboot just to get it to pair and it seems to really struggle if both bluetooth AND wifi are enabled.
I'm running the stock current ROM and outside of the android market APK and some basic apps, I haven't done anything wacky or weird to it.
I guess I'm just looking for some validation and/or confirmation and/or possible fixes if any.
Sorry, i have experienced no issues with bluetooth apart from forgetting to switch it on
I have had some issues as well. Paired a set of Motorola S9 bluetooth stereo headphones. They pair and connect fine, but the audio is choppy. It will sound fine for 15-20 seconds and then it will skip, go silent, bring back audio, etc. Tried playing same audio through unit speakers and no problems. I also have an Archos 70 tablet and have no problems with the same headset. Both have been updated with the Froy 2.2. Starting to think it might be a hardware issue with the 101. Anyone have any other thoughts?
Never had it working
I always get paired but not connected. Never have been able to get it to work.
The same problem. Pair, but not connect!
I've never found problem about bluetooth (Archos 101 - firmware version 2.1.08)
Pair & connect with DELL BH200 (Bluetooth Headset) - work fine.
Pair & connect with DELL BT Travel Mouse - work fine.
i'm getting major issues on my new replacement 101. did you ever sort your issues? i'm using latest fw.
its really hit or miss (mostly miss) whether it actually see's any BT devices when it scans. yet wifi works fine 100%
I experiment something very similar with my 101, this both on standard Android and Urukdroid 0.7 or 1.0 :
- very difficult (multiple tries have to be done) to get successfull peering.
- with BT enabled phones
- with BT GPS (G-Sat BT-368i, wich is given in forums to work well on our gen8 devices)
- for the GPS (which is the BT device that interest me) : impossible to have it working directly from GoogleMap, I got some success with "Bluetooth Gps Provider" appli from Market). This device is never shown as connected from the BT Parameters.
Could it be a hardware problem, that is do I have to return the tablet to archos ?
Thanks for your experience feeling about the fiability of the BT on 101 tablet.
It generally works fine for me, but a couple days ago it got stuck, and it would not allow to send me files to other devices until I rebooted the Archos. The same day I was also using bluetooth headphones and the wifi network together, and I had audio stutter problems. It seems that wifi has a negative effect over bluetooth stability.
It works for me... though
Bluetooth is not working on my Archos 101.
When I try "scan for devices" it shows 1 or 2 devices, while my HTC HD2 shows about 5. When I click again on "scan for devices" - sometimes it is howing different device, sometime shows bloothooth adress only.
Evan my HTC can see Archos, it cannot pair with it. Archos never see my HTC.
Zalek
Same here
I can pair with my phone (htc desire hd) but cant connect.
I need my phone connected for gps.
Nobody has a solution ?
No solution ?
Thanks
BT has some issues for me too with an A43.
BT+wifi means i either can't get a proper internet connection, or BT devices disconnect.
quite annoying, because i want to be able to use my BT mouse with the internet browser.
and my jabra halo headset connects in dumb mode (no media/volume controls) most of the time.
which is annoying, because it means my headset is stuck on the volume i last used.
Hi Lara and other fellows! For me, after all sort of tries, the solution comes with full reinitialization. Plug the unit to AC outlet, backup all your data, go to settings, repair and formatting and full reini. It seems that when we update firmware the things go a little crazy with the bt side. Good luck!
Think I've sorted out bluetooth problems
I also have had real problems with the bluetooth on Archos 101 - pairing but not connecting, causing "Location & Security" to crash when I attempted to open it (in settings). I updated the firmware to 2.4.19 and then rebooted - still the same problems, so I did a full initialization and hey presto all problems seem to have vanished ! A pain because I've now got to re-download all the apps I had before but at least the tablet is working as it is supposed to.
Hope this helps others.
luiznaufel said:
Hi Lara and other fellows! For me, after all sort of tries, the solution comes with full reinitialization. Plug the unit to AC outlet, backup all your data, go to settings, repair and formatting and full reini. It seems that when we update firmware the things go a little crazy with the bt side. Good luck!
Click to expand...
Click to collapse
Hello
How can I backup all my data?
Thks
Followed your instruction however it is not work for me. I am running the last patch (2.4.19)
Thanks
luiznaufel said:
Hi Lara and other fellows! For me, after all sort of tries, the solution comes with full reinitialization. Plug the unit to AC outlet, backup all your data, go to settings, repair and formatting and full reini. It seems that when we update firmware the things go a little crazy with the bt side. Good luck!
Click to expand...
Click to collapse
It is not working for me.....
Archos 101 Bluetooth Problem - Known issue?
I'm having the same problems. I contacted Archos support and they told me to do a full reinitialization. This did not resolve the issue.
When scanning for bluetooth devices, nothing shows up until the 5th or so attempt.
The mac address of the discovered device is shown instead of the device name.
When attempting to connect it fails several times, then it pairs but says "paired but not connected."
When I finally connect the audio stutters. It's extremely choppy... useless.
If the bluetooth is left on, the 101 will eventually freeze when the screen sleeps and cannot be woken up by pressing the power button. The green light stays on when this happens. Pressing the button a few times or holding it in reboots the 101.
After reading all the posts I've come to the conclusion that Archos likely knows about this issue.
Archos, if you're reading this, for the sake of your customers, please admit this is a known issue and let us know if it's fixable and when a possible fix may be available.
I encourage everyone to open a ticket with Archos support.
If you purchased your 101 used and it's been registered by the previous owner, you can register it and the registration will be instantly transferred to you.
Create a support account at archos.com
After you create an account you can add products to your account and submit tickets for them.
Firmware: 2.4.81
Board ver: A101IT-V5
OMAP ver: ES1.2
Boot ver: Unknown / 4.04.000000
My bluetooth device: Jensen WTB210. Works fine with several other android devices.
Hi,
I'm sorry if this has been asked before. I'm having problem with my bluetooth. I'm running android version 2.3.4 on SD (HD2 Leo). I've got no problem running it on wm.
Despite setting it to discoverable, I can't detect other devices or pairing with them neither can others find me. I can't use my bluetooth headset and whenever I want to receive files from another party, I would need to switch the phone back to WM so that I can receive via bluetooth transfer
Appreciate your kind advice. thanks!
You need to make your phone to be discovered. Setinngs. Wireless. Bluetooth settings.
to receive files from other phones you need to have FTP connection enabled, in sense it's easily done. in none-sense I haven't been able to make it work manually, but some apps like "bluetooth file transfer" do it conveniently.
try that out
it would be better if you pair with the device you want to receive files from, that means set the other device to discoverable, do a search for devices, then pair with that device. it's not mandatory, but since you might be connecting with several OSs this way is 100% working.
thank you for the replies
"bluetooth file transfer" really does the job! Without it, I can't even pair with another device. My laptop is able to search for the HD2 but can never make any connection with it.
yes that's common,
enable FTP in the app settings just in case it isn't.
if you're using a sense build/rom then it won't work.. the workaround is to connect your phone to the laptop your phone can search and see the laptop's bluetooth, and you can access shared folders on it through BT file transfer app
unfortunately i'm using a sense rom i will try that method of connecting it to the laptop. thanks!
I like sense better than anything else, so I can live with that small issue
Having an issue pairing my Motoactv to the new bluetooth headset I just bought, the LG Tone+ (HBS-730). Motoactv won't even see it. Headset connects just fine to the phone, and Motoactv connects to phone and old headset (Motorola S10-HD) without a hitch. Tried removing all existing bluetooth connections on all devices. On Motorola's advice, factory reset Motoactv. Nothing seems to be helping.
Does anyone know if this is something that a dev could fix? If it's a simple "no, there's no way modding will fix that", please let me know, so I can return this headset. I really appreciate any help. I bought this thing because it can connect to 2 devices, where the S10 could not. Doesn't do much good if it won't pair, does it?
I couldn't find a better place to put this, since Motoactv doesn't have its own section. Hope that was OK.
davidam091 said:
Having an issue pairing my Motoactv to the new bluetooth headset I just bought, the LG Tone+ (HBS-730). Motoactv won't even see it. Headset connects just fine to the phone, and Motoactv connects to phone and old headset (Motorola S10-HD) without a hitch. Tried removing all existing bluetooth connections on all devices. On Motorola's advice, factory reset Motoactv. Nothing seems to be helping.
Does anyone know if this is something that a dev could fix? If it's a simple "no, there's no way modding will fix that", please let me know, so I can return this headset. I really appreciate any help. I bought this thing because it can connect to 2 devices, where the S10 could not. Doesn't do much good if it won't pair, does it?
I couldn't find a better place to put this, since Motoactv doesn't have its own section. Hope that was OK.
Click to expand...
Click to collapse
If the MotoACTV does not see the headset while the headset is in pairing mode then it won't work. It will not pair with something it cannot see. Not sure why it wouldn't see it though. The MotoACTV uses bluetooth 4.0 so the LG's bluetooth 2.0 should be seen with ease. My suggestion would be to remove all bluetooth devices from MotoACTV. Reboot the MotoACTV and try again. Also make sure that ALL other devices have their bluetooth turned as so they don't see the LG and try to pair with it. If that doesn't work then odds are it won't work at all.
I think this new version of the headset is Bluetooth 3.0. It's the Tone+ 730, not the Tone 700 original (which, apparently, has no issues pairing with the Motoactv).
davidam091 said:
I think this new version of the headset is Bluetooth 3.0. It's the Tone+ 730, not the Tone 700 original (which, apparently, has no issues pairing with the Motoactv).
Click to expand...
Click to collapse
MotoACTV is still 4.0 so it should be compatible with 3.0, good luck
pairing
Ill let you know i own one of these headsets and should be recieving my motoactv in the mail soon.
Any ideas on the issue guys? I have a Motorola h500 and an LG-HBM 235 and neither will pair with the motoactv. It drives me absolutely nuts that the Motorola headset doesn't even work with the motorola motoactv. I mean really, WTF man? I don't want a big stereo headset. SMH. If i could finally get bluetooth audio, this thing would be great. In fact, they need to make a new model with a speaker and mic then it would be the greatest!
Figured it out. Your bluetooth earpiece/headset must be A2DP compatible.
heat22 said:
Figured it out. Your bluetooth earpiece/headset must be A2DP compatible.
Click to expand...
Click to collapse
I can't post links yet, but on the LG site, it says the 730 has A2DP...
Man, this is driving me nuts. I love these headphones, and they seem awesome for running. But I'll never know at this rate...
davidam091 said:
I can't post links yet, but on the LG site, it says the 730 has A2DP...
Man, this is driving me nuts. I love these headphones, and they seem awesome for running. But I'll never know at this rate...
Click to expand...
Click to collapse
I have these headphones as well but have always had them paired to the phone. I just tried to pair them with my actv just to see if my results were any different but unfortunately, I have the same issue.
It may be possible to pair them through a third party app but I haven't tried.
Artimis said:
I have these headphones as well but have always had them paired to the phone. I just tried to pair them with my actv just to see if my results were any different but unfortunately, I have the same issue.
It may be possible to pair them through a third party app but I haven't tried.
Click to expand...
Click to collapse
Any suggestions for 3rd party apps that would do this? I'm willing to try.
Also, does anyone think that modding the ACTV with some of the work the guys here on XDA have done will have any effect? I'm reading threads dealing with similar problems with other devices (e.g. car kits) and some are saying its a bluetooth driver issue. Maybe a custom UI will include different bluetooth drivers?
I know it's annoying to hear people ask for free work, but if any of you ACTV programmers/modders think you can tackle this issue, we'd all really appreciate it. It's incredibly frustrating when you buy 2 things that should work together just fine, but for some unknown reason, just don't.
Thanks!
davidam091 said:
Any suggestions for 3rd party apps that would do this? I'm willing to try.
Also, does anyone think that modding the ACTV with some of the work the guys here on XDA have done will have any effect? I'm reading threads dealing with similar problems with other devices (e.g. car kits) and some are saying its a bluetooth driver issue. Maybe a custom UI will include different bluetooth drivers?
I know it's annoying to hear people ask for free work, but if any of you ACTV programmers/modders think you can tackle this issue, we'd all really appreciate it. It's incredibly frustrating when you buy 2 things that should work together just fine, but for some unknown reason, just don't.
Thanks!
Click to expand...
Click to collapse
Perhaps something like this could work? https://play.google.com/store/apps/details?id=com.IG.BluetoothManager
Alternatively, if your device is rooted there are .conf files under /system/etc/bluetooth/ that could potentially be modified to get this working. For example, audio.conf could be modified to remove "Disable=Headset" as well as enable HFP. These changes could possibly resolve the issue but I haven't tried tinkering with them.
Artimis said:
Perhaps something like this could work? https://play.google.com/store/apps/details?id=com.IG.BluetoothManager
Alternatively, if your device is rooted there are .conf files under /system/etc/bluetooth/ that could potentially be modified to get this working. For example, audio.conf could be modified to remove "Disable=Headset" as well as enable HFP. These changes could possibly resolve the issue but I haven't tried tinkering with them.
Click to expand...
Click to collapse
Ok, so I decided to tinker a little and the app I mentioned did not work.....neither did some of the modifications I made to to the audio.conf file.
However, I did download this app:
https://play.google.com/store/apps/details?id=es.qrr.android.btoolkit
In the app settings, I enabled experimental mode and was able to find the HBS-730 headset and pair with it. Unfortunately, I wasn't able to go any further than that. Even though it is paired, music wasn't routing to it (granted I didn't use the stock music player -- that may have worked).
I believe the actv is treating the HBS-730 like a phone, tablet, or comp rather than just a headset which is why it is not interacting directly with it. There may be another app with root privileges (like the original app I suggested) that could possibly route the audio correctly but I haven't had the time to tinker with it and don't typically need audio output from my actv anyway.
Hope this somewhat helps.
Artimis said:
Ok, so I decided to tinker a little and the app I mentioned did not work.....neither did some of the modifications I made to to the audio.conf file.
However, I did download this app:
https://play.google.com/store/apps/details?id=es.qrr.android.btoolkit
In the app settings, I enabled experimental mode and was able to find the HBS-730 headset and pair with it. Unfortunately, I wasn't able to go any further than that. Even though it is paired, music wasn't routing to it (granted I didn't use the stock music player -- that may have worked).
I believe the actv is treating the HBS-730 like a phone, tablet, or comp rather than just a headset which is why it is not interacting directly with it. There may be another app with root privileges (like the original app I suggested) that could possibly route the audio correctly but I haven't had the time to tinker with it and don't typically need audio output from my actv anyway.
Hope this somewhat helps.
Click to expand...
Click to collapse
I had similiar problems pairing my motoactv with a pair of UE 9000's. It could see the device, but would not pair through the stock menus. Tried downloading some third party bluetooth managers and was unable to get any audio. I believe it has something to do with Apt-X codec for bluetooth not being implemented in 2.3 gingberbread on the motoactv
Artimis said:
However, I did download this app:
Click to expand...
Click to collapse
Here's where I lose all credibility (and help)...
You mean download the app to my ACTV, right? So... How do I do that?
How do I download 3rd party apps to the ACTV? I haven't modded mine at all. Do I need to do anything to it?
I realize I have just exposed myself as a NOOB. Alas, I had no choice. Please continue to speak to me.
davidam091 said:
Here's where I lose all credibility (and help)...
You mean download the app to my ACTV, right? So... How do I do that?
How do I download 3rd party apps to the ACTV? I haven't modded mine at all. Do I need to do anything to it?
I realize I have just exposed myself as a NOOB. Alas, I had no choice. Please continue to speak to me.
Click to expand...
Click to collapse
No worries .
Yes, you'll need to download the app to the ACTV. It will require rooting of the device and installing a custom ROM is the best way to get everything necessary for the market to work so that you can install these apps.
There is a step-by-step tutorial in the MOTOActv rooting thread in this forum.
Any further updates?
Just curious to see how this solution worked out. I am having the same problem and am definitely a NOOB. Attempting to download an app to my Motoactv seem a bit daunting to me...
I'm working with a Nexus 7 (2013) and a Nexus 4. I've had both devices for quite awhile, the 4 for well over a year and the 7 for a year. Both are rooted and using stock ROMs, 4.4.4.
I have the two devices Bluetooth paired and sometimes connect them. For the most part, over the last year, there have been no problems doing that. Once in awhile, they won't connect, but if I reboot, they will. Now, all of a sudden, I can't get them to connect under any circumstances. They're paired. But they won't connect. They both connect to an external Bluetooth speaker and the phone connects to my car bluetooth. That happens with 100% reliability. But these devices just won't connect with each other. And I need them to for certain work related purposes.
What could have happened?
I've unpaired and repaired them a few times. I've rebooted both devices. Potentially competing Bluetooth devices (like my car and the speaker I mentioned) are turned off. The devices aren't connected to any other Bluetooth devices.
Strangely, someone I work with who's doing the same sort of thing (and whose urgency to make them work together is greater than mine) with the same exact devices as I am is having the exact same problems.
What could be going on? Please let me know if you have any ideas.
Thanks.
Same exact problem here with my Nexus 4; rooted, stock ROM, no problem paring with Bluetooth, but unable to connect. I just noticed this today when I was trying to connect to my OBD2 device. This has worked since I bought the phone a year ago. I only use one app, and not very often, so I can't pinpoint the exact time the problem started, but I am pretty sure it would be in the time-frame of the 4.4.3 or 4.4.4 update. I also tried rebooting, re-pairing the hardware with the phone, enabling and disabling Bluetooth, etc..
pjc123 said:
Same exact problem here with my Nexus 4; rooted, stock ROM, no problem paring with Bluetooth, but unable to connect. I just noticed this today when I was trying to connect to my OBD2 device. This has worked since I bought the phone a year ago. I only use one app, and not very often, so I can't pinpoint the exact time the problem started, but I am pretty sure it would be in the time-frame of the 4.4.3 or 4.4.4 update. I also tried rebooting, re-pairing the hardware with the phone, enabling and disabling Bluetooth, etc..
Click to expand...
Click to collapse
Thanks for the commentary, pjc123. At least someone said something.
I restored one of my Nexus devices to stock 4.4.3, then 4.4.4. Didn't change anything. Maybe I need to take a couple of them back to 4.4.2 or earlier and see what happens. But AFAIK, my friend who has the same problem hasn't ever even updated to those versions of the OS. And it worked fine for him, doing these Bluetooth connections on no less than a weekly basis for a year.
Google's tech support, fwiw, told me that the first thing I needed to do was to update to 4.4.4. Not that I took that as anything other than their reading off a script.
Please let me know if you ever figure anything out with this. I'll report here if I do, too.
Well, as it turns out it was my fault for not checking the Xprivacy security settings; I am brand new to that app. After wasting a good part of the day, I discovered that the Torque app for my OBD2 reader needs both "Identification (device)" and "Network(addresses)" permissions for the Bluetooth device to show up within the app so it can be connected to. Once I gave those permissions it was back to working OK again.
pjc123 said:
Well, as it turns out it was my fault for not checking the Xprivacy security settings; I am brand new to that app. After wasting a good part of the day, I discovered that the Torque app for my OBD2 reader needs both "Identification (device)" and "Network(addresses)" permissions for the Bluetooth device to show up within the app so it can be connected to. Once I gave those permissions it was back to working OK again.
Click to expand...
Click to collapse
Interesting. I temporarily turned XPrivacy off just for that purpose. The app that's failing for me wasn't being protected, anyway, but it doesn't matter. I can't even get to that point, because the devices don't connect, even though they're paired. Furthermore, only one of my devices even has XPrivacy installed. I can't get any two of my, or my friend's, Nexus devices to connect, even though they're all paired. And they all used to.
I'm waking up this thread again to see if anyone has any ideas. I just can't connect two Bluetooth devices anymore by using the list of Bluetooth devices in settings on a Nexus device. This prevents an app that's dependent on that from working.
I CAN connect two devices via Bluetooth using ES File Explorer and see the contents of the other device and make file transfers. But the Bluetooth icon remains unlit and the connection isn't made in the settings. Maybe it's a different aspect of Bluetooth. When I close the connection with ES File Explorer, the toast says that the OBEX connection has been discontinued.
Why would I be able to connect two Nexus devices regularly for a year, then not be able to anymore?
I've tried to get Google support on this. Unlike some companies who provide inept support, even laughably so, Google just blows off the notion altogether.
Some months later...
This problem remains unresolved. I've now tested this on multiple devices (about ten of them) running various different versions of Android. I just tried it today with another, a stock, factory state N4 trying to connect to a stock, factory state N7 (2012). I wiped the devices, reinstalled the OS and then tried to pair and connect as the very first act on the clean systems once I got past the initiation routine.. I even loaded a few different versions of Android from distant past (4.2) to present. I CAN NOT connect two paired Android devices using Bluetooth, even if they're successfully paired and Bluetooth is turned on for both devices. All these devices connect fine with things like external speakers and cars. I've shown this to Google employees, some of whom have tried it on their own devices. Nobody succeeds.
As mentioned earlier in the thread, this used to work every time on every set of paired devices, regardless of the Android version.
What could possibly be going on here?
I struggled with this for awhile today. Same symptom: the devices can pair, but will quickly go from "Conecting..." to "not connected". I eventually stumbled on the solution: one device must have internet tethering enabled. This setting is in the "Tethering & portable hotspot" section, not in the bluetooth settings. This will enable the two devices to connect, and it will also enable the second device to use the "Internet access" feature in the bluetooth configuration for its connection with the first device. Hope that helps!
Hey,
I own a T330NU. I bought a Bluetooth Keyboard to use with it. Everything was fine for a month, and then all of a sudden, the keyboard started being "unable to communicate" with Bluetooth. I unpaired it, tried to pair it again and it still didn't work. I NEEDED to use my keyboard, so I did a reset and restore and it worked fine after that. Until another month later, when the same thing happened. This time, a reset didn't help.
I'm able to connect the keyboard to other devices, such as my Macbook and iPhone. I'm able to connect my tablet to other Bluetooth devices, like an audio speaker and my boyfriend's T330NU. I'm also unable to connect my keyboard to my boyfriend's T330NU.
I tried rooting my tablet to see if it would help. It did not. I deleted the Bluedroid folder. That did not help. I tried turning my tablet on and off. That didn't help. I tried most of the Bluetooth keyboard apps on the Play marketplace, that did not help.
There aren't any custom ROMS for the T330NU, so I feel like I'm screwed. I NEED to be able to use a keyboard with my tablet. I'm waiting for the Stock ROM to download and MAY try that. But c'mon! I'm also going to try out an Apple Bluetooth Keyboard tomorrow, but if it doesn't work, I may pull out my hair. AGH! Any ideas?
hi,
from your post;
I'm also unable to connect my keyboard to my boyfriend's T330NU.
------------------
suggests the problem is the keyboard not the tab.
as far as i know bluetooth devices need batteries, perhaps that's the issue?
m
You were right! Weird! Battery fixed it!