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.
There are some very old threads about this - but this is now, pretty certainly, a general stock android 4.3/4 problem with "older" car hands-free systems. My kit is a Galaxy Note with OmniROM right up to date. My car is an Opel/Vauxhall Zaphira with a Navi 900 onboard computer. However there are threads on many android forums complaining of the same symptoms for "pure" stock 4.3/4 devices (e.g. the Nexus range, including the Samsung Galaxy Nexus) and a variety of cars, and all describing the same workaround (and a few lamenting that Google haven't been very responsive in addressing the problem). The symptoms and workaround are:
The car recognizes and "partially" pairs with the phone
However, the contacts list and call lists are empty and the phone cannot be controlled from the car, neither for incoming calls nor for outgoing calls (dialing from the car interface always gives a failed message, while trying to receive or hangup from the interface just plain fails).
Calls using the phone work, and show up on the car interface, always as "Unknown" (not surprisingly - it doesn't have the contacts list)
HOWEVER if, after this "partial" pairing up, I make a 30-45 second call using just the phone itself, then, after the call has terminated, contacts and call lists are properly available through the car interface and the phone can be fully controlled from that interface (and, of course, the FIRST time this happens, I get the notification on the phone telling me the car wants this information, which, of course, I confirm)
A workaround like that can be scripted with something like "Tasker" and using, say, my voice mail number (with my provider here in France, plain fake number calls don't stay online long enough for the above to work).
But does ANYONE have any idea where to start looking for the root cause and possible solutions, or have any theories on those points?
EDIT:
Just to be clear - the workaround "make a call from the phone" trick has to be done every time the phone and car reconnect, not just the first time.
Had this happen in my ford the other day and it's sync system.
The fix for me was a not so visible notification upon establishing the Bluetooth pairing in the notification tray asking if I wanted to allow for my phonebook to be downloaded. Clicked yes and everything set up as normal.
Mgd_toronto said:
Had this happen in my ford the other day and it's sync system.
The fix for me was a not so visible notification upon establishing the Bluetooth pairing in the notification tray asking if I wanted to allow for my phonebook to be downloaded. Clicked yes and everything set up as normal.
Click to expand...
Click to collapse
I got that notification AFTER I had done the "make a call from the phone" trick, not before.
I should also point out that the "make a call from the phone" trick has to be done every time I want to reconnect to the phone to the car (while the notification only appeared the first time I did the trick - because subsequently the phone and the car "trust" each other).
Aside from maybe unpairing and trying to set it up again which I am certain something you've probably already tried; have you checked the cars firmware?
Could also try resetting your Vauxhall's system as well in case there is a gremlin in there causing a hang up with the sync.
Again with Fords sync I have had to do it a few times over the years when the systems been misbehaving with the Bluetooth and it fixed it.
Mgd_toronto said:
Aside from maybe unpairing and trying to set it up again which I am certain something you've probably already tried; have you checked the cars firmware?
Could also try resetting your Vauxhall's system as well in case there is a gremlin in there causing a hang up with the sync.
Again with Fords sync I have had to do it a few times over the years when the systems been misbehaving with the Bluetooth and it fixed it.
Click to expand...
Click to collapse
Indeed I did the resets. And yes, possibly, an upgrade of firmware MIGHT fix it, but these problems don't occur with Android 4.1.n (or, I, believe 4.2.n).
I've logged a bug with the OminROM developers, but would like some pointers so I myself can start looking at solutions and fixes.
Hmm... Unfortunately I don't know who to assign that JIRA bug to.
Problem is - none of us own vehicle headunits that we can reproduce/test this problem on. I used to have a Sony MEX-BT2500 (technically I still do...) but since I sold my old convertible it just sits and collects dust.
I would agree that this will be a difficult one to find. It reminds me of working with 802.11b/g with it's dozens of "pre-draft" variants that just didn't interoperate properly.
If you wanted to dig into this yourself, the first place I'd look is https://github.com/omnirom/android_external_bluetooth_bluedroid and its upstream and parallel variants. That is the code that generally handles the upper-level Bluetooth management functions.
Edit -- Also worth looking at https://source.android.com/devices/bluetooth.html if you want an overview of how Android implements Bluetooth.
The comments on commits there might also be worth reading through. For example
https://github.com/omnirom/android_...mmit/73ce8ab2ddd30cab6499d0062c46b3a16f9130a9
Fact is however, that the use of SDP features value for peer_features
is new since Android 4.2 and breaks existing good behavior on a BMW
2005/E46 car kit (navi professional). This kit never asks for AT+CHLD
and never via AT commands suggests it supports 3WAY (although it seems
to have the flag set via SDP).
Not the same issue, but there might be clues of that nature in the commit messages.
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!
I'm wondering if anyone has issues with and solutions for bluetooth connectivity problems. Specifically, constant dropouts and stuttering.
Background of problem
I recently purchased my phone, which was already on Android 10 (Build QP1A.190711.122). From the start, bluetooth has been unbearable: if I move the phone in any way, or I move the connected bluetooth device (headphones, earbuds, speakers, etc.) it stutters and cuts out momentarily. Sometimes the stuttering continues incessantly. In short, my bluetooth is useless for listening to audio, making phone calls, etc. I basically have to be next to be perfectly still and right next to the phone, and even then it may act up.
Failed troubleshooting efforts
I installed the September update, rooted the phone and tried various options many times, including:
*Hard resetting the phone
*Flashing and re-flashing the stock rom several times (even after full wipes)
*Wiping the cache in recovery
*Clearing the bluetooth cache
*Playing with the bluetooth options in Developer Options
*Unpairing and re-pairing various bluetooth devices
I'm lost and wondering if the gyroscope is messing with bluetooth connectivity in someway. I have no idea whatsoever.
Thoughts and comments appreciated.
@droctii
I have not had an issue like this, sounds like a low power/weak signal issue or interference or conflicting devices
Which sounds like this
https://forum.xda-developers.com/essential-phone/help/awful-bluetooth-connection-t3713280
users report 2 or 3 fixes scanning through thread
Same here. bluetooth connectivity has rather worsened since android 10.
however the recent ota updates on android 9 have been a hit or miss since march 2019. Before that, bt was working perfectly fine.
Coming back to android 10, as an example, the link with my bose soundwear with minor exceptions had been really strong bt -wise but since the update I get even with it random disconnects, and infrequent stutter/cuts etc. The same for my sony wh1000x m3, it behaves a little better but only using sbc codec, so i stick to that. However, older devices such as my car's bt, tv soundbar or even google mini when phone's just next to it are unusable with this phone. Also, the more crowded an environment (interference-wise) more likely to experiment issues.
For comparison, all other older phones I have still work fine within same parameters
I haven't taken my PH-1 to A10 yet, but my pixel 3XL had been struggling with Bluetooth. Today is the first time it's been useable, but I made a bunch of random changes in developer options. I haven't worked out which had helped. FWIW, I'm attaching a screen shot of the settings I'm using.
ktmom said:
I haven't taken my PH-1 to A10 yet, but my pixel 3XL had been struggling with Bluetooth. Today is the first time it's been useable, but I made a bunch of random changes in developer options. I haven't worked out which had helped. FWIW, I'm attaching a screen shot of the settings I'm using.
Click to expand...
Click to collapse
A lot of Bluetooth devices don't implement the protocols properly, especially on the cheaper side. You disabled A2DP so that probably helped.
You should be able to enable A2DP but use the highest version of AVRCP available, yours seems rather low. Should work fine.
Verlog5454 said:
A lot of Bluetooth devices don't implement the protocols properly, especially on the cheaper side. You disabled A2DP so that probably helped.
You should be able to enable A2DP but use the highest version of AVRCP available, yours seems rather low. Should work fine.
Click to expand...
Click to collapse
What makes you think A2DP is disabled? The hardware handoff is disabled. Not the same thing. And that is the solution to my stuttering and disconnect issues. Toggling that makes the problems come and go.
Same problem on my car with 1+7pro and android10, music is discontinued, or freezed, stuttered...
But for me line with disable bt ad2p hardware offload is greyed and swith is to left
salva52 said:
Same problem on my car with 1+7pro and android10, music is discontinued, or freezed, stuttered...
But for me line with disable bt ad2p hardware offload is greyed and swith is to left
Click to expand...
Click to collapse
You would be better served looking/posting in your own device forum. This is the Essential PH-1 and your software is very different.
I have had such problems with various devices and while disabling A2DP offload always solved the problem, so did playing around with the AVRCP versions.
My essential phone has been sitting on my desk for the last 3 months due to these insolvable bluetooth issues. Neither AVRCP nor A2DP solved the issues, the bluetooth is stuttering constantly when I move my phone around and not in direct sight of my receiver(s).
I tried 3 different wireless earbuds and they all suffer from random stutters or disconnects if I'm actively walking with my phone. The closer the phone is to my upper body, the better the signal is (most of the time). If I connect my phone to any Bluetooth device at home or in the car where the phone isn't moving, the connection is perfect. I've tried the different methods mentioned in this thread and nothing fixes it. I've given up and just hoping my next phone doesn't suffer from the same thing.
Hello to everyone.
From when i bought it the op8pro has some problem with the bluetooth. Is like if the device can connect to one device only. I have a fossil 5 gen, one fiesta mk8 with android auto and the bluetooth headset but is like if the bluetooth has some problem to connect to two or one devices. For example every time my car doesnt connect to the phone automatically and today when i was to the gym my headset doesnt connect automatically too. My previous note 10 pro was able to connect without any problem... Someone has some problem with the bluetooth? Thanks
I have another problem. Every time that i enter in my car the device is connect to android auto but if i want to play an audio from whatsapp i have to tap a lot of time on the play botton.!!!???why
I see this same issue, I'd say 80-90% of the time (the other 10-20%, it "just works", which is truly odd, given the protocol).
For example, I use some bone-conducting open-air headphones, while cycling (long time road cyclist), and sometimes I want to connect my Garmin Edge 1030, to download a route, when I'm out.
Good luck, even upon returning, I'm often sitting in the garage, trying 20+ times (after shutting my headphones off, even), to try and download my ride-data, for the day. Sometimes it requires rebooting both devices, flushing the Bluetooth app-cache, and the Garmin app-cache, and then it'll work, that's perhaps 40% of the time.
For another 40%, it will NOT connect, what-so-ever, across multiple reboots and app-cache flushes, period (I tend to give up at around the 20+ attempt mark, depending).
The last 20%, it works, perfectly, as you'd expect, and as my OP7 Pro did, I can't recall a single BT connectivity issue, with it, either solo (Garmin) or with headphones concurrently.
I've filed bugs with OP (along with NUMEROUS other radio bugs, like the fact you can't connect to a 5G-mobile signal, if you're connected to a WiFi signal, on the INO2025 model, bug filed, trace-logs submitted, including pointing out log-lines where the radio(s) fail).
Unfortunately, with the Bluetooth issues, it will not repro, if I use the OP debug-mode, which is how they want to receive logs (and how I've submitted many bugs, previously), so I'm at a loss, short of finding a hardware Bluetooth debug module (I used to work on h/w and s/w boundary driver stuff, so I've used a h/w BT debugger before, but not for some years, and have no access to one, currently).
OP seems to just ignore the bugs, at that point, when I can't provide the logs, they pretty much abandon the bug-thread, so I'm not sure how they're going to get some of these resolved (I've noted that the debug-mode seems to introduce some latency, or similar, that prevents repro, no response to that, what-so-ever).
I have reset the radio-stack, a couple of times, and did one full factory-reset (shortly after getting the phone, about 1 month back now), with no real change in results, for reference.
I feel like I'm back in the late-90's, when Bluetooth was super-flaky. on most devices, in the 1.x and 2.x days.
Not exactly a "flagship phone experience", or even a decent budget phone Bluetooth experience, for this day and age...
I'm open to ideas on how to debug further, I'm really more of a storage and display guy, and memory-management, in terms of the bulk of my dev/debug skills, communication protocols were something I did on the fringe, of sorts, when they overlapped, or similar.