Related
Just tried a few latest windows 6.1 roms and found out that my bluetooth headset (I tried a few) is not asking for passcode anymore (it used to ask to enter "0000"). On one hand - it's a cool feature saving you time and efforts to pair your devices. On the other hand- it's quite dangerous. Just imagine somebody near you (while you're having lunch) is playing with bluetooth on the laptop and connects to your phone without you knowing it. Potentially, he can download all your info from the phone. No good!
I was thinking that it maybe something wrong with my bluetooth or the ROM on the phone. But after I did a quick search here, it appears that Windows 6.1 has this neat feature of "automatic cycling of the standard passcodes" during pairing process. Is there any fix to this security breach? Or maybe I'm not getting it quite right?
well i still havent paired my headset with my pdacorner v23 NonRBSN rom but if you go to comm manager, hit settings, the click on bluetooth. On the tab Security there should be a box that says authentication passkey required. i dont know if thats bluetooth or infrared....but im sure its bluetooth.
Hope that works.
With all the wm 6.1's I've used it appears to only work with BT headsets... GPS and other BT devices need a key....
Cheers...
If that's so - it's good. I'll experiment with bluetooth dongle on my PC.
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
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!
Joying JY-VOS01N4GS w/ an SC-9853i 1.8GHz Octa-core, installed in a 1991 Toyota MR2 with a Honda K24A2 turbo engine swapped into it, controlled by an ECU called a Hondata KPro V4.
https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.com/ulk/itm/143309152617
I can install and run Hondata or RealDash apps on the stereo without issue, but I can't get it to connect to the ECU itself so I'm looking for suggestions. I've got a $20 no name tablet or a 7+ yrs old Samsung Note 3....all connect to the KPro without issue. Hondata, RealDash and Torque apps all connect without issue on the tablet or phone. New $350+ stereo...keeps giving me failed to connect error.
I'm open to rooting if needed, installing a different Bluetooth app, I have the pin to access developer options, etc....I just need it to connect and work.
m5james said:
Joying JY-VOS01N4GS w/ an SC-9853i 1.8GHz Octa-core, installed in a 1991 Toyota MR2 with a Honda K24A2 turbo engine swapped into it, controlled by an ECU called a Hondata KPro V4.
https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.com/ulk/itm/143309152617
I can install and run Hondata or RealDash apps on the stereo without issue, but I can't get it to connect to the ECU itself so I'm looking for suggestions. I've got a $20 no name tablet or a 7+ yrs old Samsung Note 3....all connect to the KPro without issue. Hondata, RealDash and Torque apps all connect without issue on the tablet or phone. New $350+ stereo...keeps giving me failed to connect error.
I'm open to rooting if needed, installing a different Bluetooth app, I have the pin to access developer options, etc....I just need it to connect and work.
Click to expand...
Click to collapse
It will not pair. Joying (actually FYT/SYU) crippled the bluetooth on their units. You can only pair with phones and a few OBD and TPMS BT devices.
For the rest: nothing.
And that is done onto the lowest compiled level including the MCU. Other drivers/apps/kernels/whatever will not work.
I've been writing Joying and they offered to sell me their OBDII dongle at a discount. I explained to them shortly before writing this post that the car doesn't have an OBDII port since it's a 91, lightly explained the engine sway, but I haven't heard anything yet. Why would they go through all that effort...just to force us to buy their $15 OBDII dongle?
What about universal Bluetooth dongle plugged into one of the USB cords? Or maybe even USB to USB? The ECU has a USB port that I use when I connect to my laptop to run KPro Manager (a Windows PC based program) and the RealDash app on Android does give me the option of Bluetooth, USB or serial input. I'm currently monitoring from this tablet which is completely illegible while driving, needs to be manually powered on/off and then reconnected to Bluetooth...not being able to see the gauges on a much larger screen and automatically reconnect when I start the car crushes EVERY reason why I bought this stereo. There's gotta be a way.
Wrote a long reply, stupid token expired...I'm gonna try this.
https://www.hondata.com/forum/viewtopic.php?t=18829
Bluetooth dongle didn't work, but I can't confirm if it's a dongle issue since I can connect to it but then the Hondata app says "Ignition not on" when it is. Nevertheless today I played around with the GF's cwr who has a Joying JY-HOS02P4 screen in hers, it's only 3 months old, and it'll connect to my Hondata just fine! Would it be as simple as taking the Bluetooth APK from her car and installing it on mine?
Bump for help...there's gotta be a way :/
Bumping again, hoping maybe someone can help.
Following - need this for ECUTEK bluetooth adapter in my GTR, otherwise the screen is worthless...
m5james said:
Bumping again, hoping maybe someone can help.
Click to expand...
Click to collapse
Like mentioned a couple of posts above. Joying crippled Bluetooth and there is simply no "normal" bluetooth stack.
You cannot alter the current BT app as it won't be signed correctly anymore and it will not even be visible anymore.
You cannot add another BT app as that will not have the correct signing either.
Your question is not new. This BT "not being able to pair" is already an issue since 2016. You would be the first to find a solution.
The only thing you can try is what I described in this post, based on info from ojuniour.
Having said that: you should also search the rest of the forum and not only stick to your own question. Otherwise you might already have tried what I described. It might work, it might not.
Surfer, thank you so much for the reply. I've read in depth and was fearful of that, but will try what is in the thread you linked. If you'd be so kind, couple questions that you may have answers to:
- I have a sofia 9853 with android 8.1 (upgrading to 9.0), does that make things better worse or same for the bluetooth situation?
- I've seen some talk on much older threads of using Comfast® CF-WU725B as an external/usb bluetooth solution? Did this (or an alternative dongle) ever or does it still work?
- I've also seen talk of used xposed modules to add bluetooth devices to the whitelist - is there any truth to this?
Surfer, thanks in advance, this is for a tesla screen in a GTR. By removing the stock screen we lose a ton of critical info that can only be gotten back through ecutek, which currently only has a bluetooth solution for android.
M5James - sorry for hijacking your thread, but hopefully this helps you as well
xadamadax said:
Surfer, thank you so much for the reply. I've read in depth and was fearful of that, but will try what is in the thread you linked. If you'd be so kind, couple questions that you may have answers to:
- I have a sofia 9853 with android 8.1 (upgrading to 9.0), does that make things better worse or same for the bluetooth situation?
- I've seen some talk on much older threads of using Comfast® CF-WU725B as an external/usb bluetooth solution? Did this (or an alternative dongle) ever or does it still work?
- I've also seen talk of used xposed modules to add bluetooth devices to the whitelist - is there any truth to this?
Click to expand...
Click to collapse
1. There is no Sofia 9853. There is a Intel Sofia AND an Intel SC9853i. Those are 2 different CPUs needing different ROMs.
2. No idea. Like mentioned: an external BT dongle has not worked till now, but I have never heard of that Confast one.
3. Xposed is not supported on the 9853i. Not on Android 8.1 and neither on 9.0
@surfer63, thank you again, your thread here (https://forum.xda-developers.com/an...qa-tips-info-roll-joying-fyt-sc9853i-t3979377) helped me tremendously
@m5james, on a whim i plugged in ecutek to usb via the usb mini port, and shockingly there is support for it. Maybe try the same with Hondata if there is an sort of interface on it.
surfer63 said:
Like mentioned a couple of posts above. Joying crippled Bluetooth and there is simply no "normal" bluetooth stack.
You cannot alter the current BT app as it won't be signed correctly anymore and it will not even be visible anymore.
You cannot add another BT app as that will not have the correct signing either.
Your question is not new. This BT "not being able to pair" is already an issue since 2016. You would be the first to find a solution.
The only thing you can try is what I described in this post, based on info from ojuniour.
Having said that: you should also search the rest of the forum and not only stick to your own question. Otherwise you might already have tried what I described. It might work, it might not.
Click to expand...
Click to collapse
Fair enough...honestly like 10 +/-yrs ago I was WAY more into custom ROMs, baking, etc etc but nowadays I feel like it's over my head again. The only reason why I asked about using other BT versions from other Joying devices is because the GF's similarily aged stereo was able to connect, but I understand the signing thing since our two stereos don't share the same OS and CPU.
xadamadax said:
M5James - sorry for hijacking your thread, but hopefully this helps you as well
Click to expand...
Click to collapse
You're fine, the more exposure the merrier...I'm not as good at this stuff as I used to be so I'm just hoping someone smarter than me can help
xadamadax said:
@surfer63, thank you again, your thread here (https://forum.xda-developers.com/an...qa-tips-info-roll-joying-fyt-sc9853i-t3979377) helped me tremendously
@m5james, on a whim i plugged in ecutek to usb via the usb mini port, and shockingly there is support for it. Maybe try the same with Hondata if there is an sort of interface on it.
Click to expand...
Click to collapse
Do you have a pic of how you physically hooked it up? I haven't touched much on this subject since my original post and honestly don't recall the connections at the moment but I do recall mine having a square port (I don't know it's official name) that allows me to connect via USB to a laptop. I think I even tried connecting directly to the stereo that way but no luck.
Hondata runs on the screen easily in both portrait and landscape mode but I prefer RealDash, which at doesn't like portrait mode...I'm hoping it's something I can adjust to fit myself since RealDash allows for customisable gauges.
@m5james that is a micro usb port you have, try connecting it to a usb port on the head unit (same way you would a laptop) and open your hondata app - with any luck you'll be in business. If one port doesn't work, try the other - good luck
If you guys want to use the bluetooth pairing with basically about anything then buy the "Stop" brand. Unit actually confess with 2 BT models. One for music and phone call, the other one is located in the android bluetooth setting that would enable you to pair with anything.
ojuniour said:
If you guys want to use the bluetooth pairing with basically about anything then buy the "Stop" brand. Unit actually confess with 2 BT models. One for music and phone call, the other one is located in the android bluetooth setting that would enable you to pair with anything.
Click to expand...
Click to collapse
I looked on eBay for "stop android DIN" and nothing comes up.
m5james said:
I looked on eBay for "stop android DIN" and nothing comes up.
Click to expand...
Click to collapse
lol my bad I mean Atoto.. Damn auto correction.
here is an example of one connecting to ecuTek obd bluetooth:
https://www.ft86club.com/forums/showthread.php?t=141515
xadamadax said:
@m5james that is a micro usb port you have, try connecting it to a usb port on the head unit (same way you would a laptop) and open your hondata app - with any luck you'll be in business. If one port doesn't work, try the other - good luck
Click to expand...
Click to collapse
Wait wait wait. Wait a minute.... Are you saying you are able to get the ecuTek OBD bluetooth to work in wired mode[ to the head unit] without connecting to it wirelessly through bluetooth?
And you are using the ecuTek App?