Hey there!
I posted this answer within another thread, but thought it would help more people if I set it up here. I will be modifying the original post here to point back to this post so that I'm not spamming.
Anyway, if anyone is having the same issues with bluetooth because of the kernel issue in 7.0, I discovered a workaround until they patch it out. It's about as elegant as a bear in a tutu, but it works. Also, take into account that I used this method on a SM-J700T with a port of this ROM by mr.duck254 and FullOfHell. Their fine work is linked here: https://forum.xda-developers.com/galaxy-j7/j700t-development/rom-synexos-v1-0-port-duck254-fullofhell-t3756157
First you need to install these two apps (I'm not reputable enough to post outside links yet so I'll do my best to narrow your search):
"Bluetooth Pair" by Waylon Huang
"Bluetooth Auto Connect" by UniqTec Inc.
Fire up Bluetooth Pair and turn on your bluetooth antenna with button in the lower right.
Do a refresh in the settings menu if your device doesn't pop up.
When your device does pop up, tap the "PAIR" button.
In my experience, the "Connect" button within Bluetooth Pair did work for my devices. This is when you switch to Bluetooth Auto Connect.
Open Bluetooth Auto Connect and tap "Devices".
Make sure the device you want to connect has a check mark next to it and use the handle on the right to drag it to the top of the list.
Tap the device to and place a check mark next to the role(s) it performs.
Go back one screen and tap "Connect". If your device is on and paired you should now be connected.
Hope this helps. Good luck. :fingers-crossed:
Thanks man!!! Confirming that this works.
Only thing I did differently was that I unpaired everything so I could actually pair new devices through settings again but I'm guessing that the issue will come up again. Anyway thanks again man.
ziggyjustice said:
Hey there!
I posted this answer within another thread, but thought it would help more people if I set it up here. I will be modifying the original post here to point back to this post so that I'm not spamming.
Anyway, if anyone is having the same issues with bluetooth because of the kernel issue in 7.0, I discovered a workaround until they patch it out. It's about as elegant as a bear in a tutu, but it works. Also, take into account that I used this method on a SM-J700T with a port of this ROM by mr.duck254 and FullOfHell. Their fine work is linked here: https://forum.xda-developers.com/galaxy-j7/j700t-development/rom-synexos-v1-0-port-duck254-fullofhell-t3756157
First you need to install these two apps (I'm not reputable enough to post outside links yet so I'll do my best to narrow your search):
"Bluetooth Pair" by Waylon Huang
"Bluetooth Auto Connect" by UniqTec Inc.
Fire up Bluetooth Pair and turn on your bluetooth antenna with button in the lower right.
Do a refresh in the settings menu if your device doesn't pop up.
When your device does pop up, tap the "PAIR" button.
In my experience, the "Connect" button within Bluetooth Pair did work for my devices. This is when you switch to Bluetooth Auto Connect.
Open Bluetooth Auto Connect and tap "Devices".
Make sure the device you want to connect has a check mark next to it and use the handle on the right to drag it to the top of the list.
Tap the device to and place a check mark next to the role(s) it performs.
Go back one screen and tap "Connect". If your device is on and paired you should now be connected.
Hope this helps. Good luck. :fingers-crossed:
Click to expand...
Click to collapse
Related
Hi folks,
I upgraded my Hermes with Schap's Windows Mobile 6 ROM. Works fine so far. But when I try to use my Bluetooth GPS it acts strange.
I paired the Bluetooth device and set up a COM-port for the applications. The first time it works. The next time, when I switch on Bluetooth and start for example TomTom, the Hermes tells me there is a new Bluetooth device that wants to connect. I checked and found out the GPS is still in the list of known Bluetooth devices and the COM-port is set. But the assistant is still bugging until I add the "new" device. After that of course my "old" device is gone.
How can I avoid this? Anyone experiencing the same problem?
I have the same issue, really annoying so would love to know the answer
Tafkas.Net said:
Hi folks,
I upgraded my Hermes with Schap's Windows Mobile 6 ROM. Works fine so far. But when I try to use my Bluetooth GPS it acts strange.
I paired the Bluetooth device and set up a COM-port for the applications. The first time it works. The next time, when I switch on Bluetooth and start for example TomTom, the Hermes tells me there is a new Bluetooth device that wants to connect. I checked and found out the GPS is still in the list of known Bluetooth devices and the COM-port is set. But the assistant is still bugging until I add the "new" device. After that of course my "old" device is gone.
How can I avoid this? Anyone experiencing the same problem?
Click to expand...
Click to collapse
On your Hermes:
Have you tried to checked off: "Make this device visible to other devices"?
Under: Start\Settings\Connections\Bluetooth\Mode (2nd tab on the bottom)
Option #1 (Hermes)
~If, "Make this device visible to other devices is not enabled, delete the pairing for your GPS.
~Check off "Make this device visible to other devices"
~Pair your GPS again (ensure that "Make this device visible to other devices" is still enabled)
Option #2 (GPS)
Don't know what kind of settings for bluetooth you may have on your GPS. I found for my car stereo, that I needed to leave it, in the "waiting/open for connection mode.
Now when I turn the car on it automatically connects the phone and stereo off my Hermes.
What I'm basically saying here is there may be a setting to leave your GPS automatically open for bluetooth connections?
I think option #1 may do the trick....
Hope this helps! Good Luck!
jac said:
On your Hermes:
Have you tried to checked off: "Make this device visible to other devices"?
Under: Start\Settings\Connections\Bluetooth\Mode (2nd tab on the bottom)
Option #1 (Hermes)
~If, "Make this device visible to other devices is not enabled, delete the pairing for your GPS.
~Check off "Make this device visible to other devices"
~Pair your GPS again (ensure that "Make this device visible to other devices" is still enabled)
Option #2 (GPS)
Don't know what kind of settings for bluetooth you may have on your GPS. I found for my car stereo, that I needed to leave it, in the "waiting/open for connection mode.
Now when I turn the car on it automatically connects the phone and stereo off my Hermes.
What I'm basically saying here is there may be a setting to leave your GPS automatically open for bluetooth connections?
I think option #1 may do the trick....
Hope this helps! Good Luck!
Click to expand...
Click to collapse
Mine is set to NOT be visable to others & my bluetooth GPS device just ha a on/off button.
paul8811 said:
Mine is set to NOT be visible to others & my bluetooth GPS device just ha a on/off button.
Click to expand...
Click to collapse
If your concerned about Security you can always change the Pairing codes.
and or turn off bluetooth when not needed.
I'm unaware of any cases where one can connect unless there paired, so in most cases access needs to be allowed on both ends, usually needing pairing codes. Even if it is one way, an approval code will still be needed.
What I found is this, if you want automatic connecting with one way pairing codes i.e. (Car Stereo to PDA or GPS to PDA) You'll need to allow "make device visible" checked off. The usual cause is a memory storing issue with the GPS or Car Stereo. I know that on high end Stereo's and GPS's they have on board memory which will save connection settings, where you'd put pairing codes on both ends and it will save the settings, thus negating the need to leave visible.
Don't know if I answered your question?
Hope I was able to shed some light on the subject....
Good Luck!
I'm having a problem where my phone's (XPERIA X1i) A2DP connection doesn't properly reconnect to my car's receiver most of the time. I've found that if I go into the Bluetooth settings, uncheck "Wireless Stereo" on the appropriate device, save, then recheck it, and save again, everything works well. Obviously, this is a lot of trouble, so I'd like to automate it.
I've found where the enable bits are in the registry, but I can't tell how to do the equivalent of the "save" button in the settings. I'm happy to write my own program to do this if someone can point me to the right API call. Thanks!
- Scott
PS: Although I've found A2DPToggle to be a help elsewhere, it doesn't solve my problem of reconnecting the device.
A7 working as GPS using Coplilot live with Holux GPSslim240 bluetooth reciever and app (Bluetooth GPS Provider) every thing works.
nice! do you use a dashboard mount? if so, which one?
sjpn said:
nice! do you use a dashboard mount? if so, which one?
Click to expand...
Click to collapse
No just got It working I would like to find one that it will fit in.
Think this USB GPS would work? http://www.priceplunge.com/
$20 for GPS and software is pretty nice...
Will not without drivers. Already tried.
rspray said:
Think this USB GPS would work? http://www.priceplunge.com/
$20 for GPS and software is pretty nice...
Click to expand...
Click to collapse
You will need a blutooth one. I got mine off ebay
ninetoes49 said:
A7 working as GPS using Coplilot live with Holux GPSslim240 bluetooth reciever and app (Bluetooth GPS Provider) every thing works.
Click to expand...
Click to collapse
How did you get it to connect. Mine doesnt even give the option. it just finds it and sits after recognizing.
immortalsoule said:
How did you get it to connect. Mine doesnt even give the option. it just finds it and sits after recognizing.
Click to expand...
Click to collapse
Heres how I do it. Im running dexter 1.3 mod. You have to install the bluetooth fix. Put you a7 in discovery mode and you gps into discovery mode . Scan for your gps once found pair it with the a7. It should come up and say paired but not connected and thats normal.
Download bluetooth pgs provider from the market and run it. It will ask you to choose your gps. Tap on your gps when you see it. after that you should see a bar that says start tap on that. Now you should see stats at the bottom of the screen from your gps. Now you can run your gps program and it should work mine does. I use copilot live. I also use it on my phone. After I install it on the a7 I had to copy my copilot directory from my phone to the a7 to make it work. There are other bluetooth programs on the market that do the same as bluetooth provider If that doesnt work you could try some of the others
hope that helps
ninetoes49 said:
Heres how I do it. Im running dexter 1.3 mod. You have to install the bluetooth fix. Put you a7 in discovery mode and you gps into discovery mode . Scan for your gps once found pair it with the a7. It should come up and say paired but not connected and thats normal.
Download bluetooth pgs provider from the market and run it. ...
hope that helps
Click to expand...
Click to collapse
I am hitting a dead end. I have tried both Dex's 1.3 mod with the bluetooth fix as well as the 1.4 mod with the same results. In either case, when I go to the market, the Blue GPS app as well as many others don't show up in searches when I try to get them (for example, when I search for meowsbox I only see 3 apps including the "Bluetooth GPS License" but not the GPS app itself). I can see them in my PC browser but not via the market App and in my browser they say they are not compatible with my device. I was able to download Blue GPS manually from source_forge by accepting non-certified apps but that didn't work either (connection errors).
For reference, I see the following in "About Device":
Model Number: A7-040; Firmware Version: 2.2; Kernel version: 2.6.32.9 [email protected] #1; Serial number 2496430001227; Build Number: Dexter's ElocityA7 Mod v1.41; EC version: 0.14;
Also, when I hit the market, I see the following:
Maker:Compal; Model:A7-040; Carrier:T-Mobile;
Any ideas?
nodozen said:
I was able to download Blue GPS manually from source_forge by accepting non-certified apps but that didn't work either (connection errors).
Click to expand...
Click to collapse
this is the only way, and it works.. i have used a bT gps with it..
remember as mentioned to enable "mock location" in settings -> development
Can't find the Bluetooth fix for Dextermod 1.3 does anyone have a copy?
I purchased a GSat Bluetooth GPS receiver and want to use it but all of a sudden I can't enable bluetooth. I'm running 1.3 without any patches and I used to at least have the ability to turn on the bluetooth and pair up a headset. Now, in settings, I can't even get bluetooth enabled (I have WiFi just fine). I was looking for the bluetooth patch that was created for Dexter's 1.3 mod, but can't find it. Does anyone know where I can locate that patch?
I know that I could update to 1.4 (plus patches) but I've been spooked by some of the problems reported, and everything else is working well.
Update: OK, I found it at Post#690 on the Android Dev/Elocitymod thread. I hope it works!
if i recall the right file from examining dexters rom, he replaced either the settings or contacts apk that originally had bluetooth settings option from elocity w one that does not have those bluetooth settings, at least in the 1.41 rom. so upgrading will not help.
Sent from my X10i using Tapatalk
i didnt however inspect the settings fc update. =P
Sent from my X10i using Tapatalk
Bestialbub, if you have any advice for me I would really appreciate it. Your wife is so lucky to have you to help her... my husband is wonderful but l'm the techie of the family!!!
i might have the answer for that one;
1
download and install "anycut" from the market. its a utility application for making convenient shortcuts to important activities and menus in programs.
2
open anycut from your applications menu.
3
choose "new shortcut"
4
choose "activity"
5
scroll down to where i hope you see "Bluetooth settings"
you should now have a shortcut on the desktop labeled "Bluetooth settings". see if that gets you to what you need. it didn't work on my cm6 froyo rom for my x10 phone, and i don't have a tablet in my hands at the moment. i just got a force close error. i should think if the bluetooth app (it is an apk) is working right, it should open that menu, even though you may not find it elsewhere. sorry if it doesn't work.
EDIT; otherwise, if that doesn't work, using the same solution you may find one of the many "Settings" listings further down the activities list could be a bluetooth menu entry as well. they don't list the subnames sometimes for multiple activities/menu's in 1 program. you may also find some of these activities/shortcuts causes your tablet to reboot.
bestialbub said:
if i recall the right file from examining dexters rom, he replaced either the settings or contacts apk that originally had bluetooth settings option from elocity w one that does not have those bluetooth settings, at least in the 1.41 rom. so upgrading will not help.
Click to expand...
Click to collapse
1. i did not remove bluetooth ... why would i do such thing..
2. previous roms had firmware bluetooth problems not "settings" in android.. different story.. different problem..
when its said "bluetooth fix", it means bluetooth boot.img fix, not anything else.. i would not recommend ideas, when you can actually just open and check yourself... and you're not using so why start advising on the firmware you havent seen.. your advise can be easily misunderstood, and you cannot see the problem, as you start directing in wrong direction, which lead to total confusion, which i see now.... why use shortcuts when settings offer a "bluetooth" option like all android would...
@dexter_nlb; i never falsely represent my suggestions as definitive solutions; just possibilities as workaround for a device i didn't have in my hands at the moment.
and for the record, *i* tried both suggested solutions, and yes, i verified the bluetooth settings shortcut i suggested (which could be a convenience for some to have direct access to from the homescreen) worked, as well as yours. i made the silly assumption someone would have checked the settings menu before asking.
@okantomi; under Wireless in the Settings menu in the newest elocity firmware, i cant say for elocitymod version youre running.
sorry dex couldn't CLEARLY answer this before chewing me out. @dexter_nlb; did you try my suggestion before snapping?
i wasn't making things up about your contacts.apk either;
Code:
<uses-permission android:name="android.permission.BLUETOOTH" />
<uses-permission android:name="android.permission.BLUETOOTH_ADMIN" />
permissions not listed in the contacts.apk you provided that are listed in the factory apk. suggestive that the contacts.apk provided in elocitymod could be lacking some bluetooth functionality OR accessibility to such settings, at the least in the contacts.apk; a system application in your rom.
i'm pretty sure users are permitted to answer questions on xda without your permission, even if they do relate to your rom. wouldn't they be posting directly to your rom thread if they thought you were the only one with all the answers?
and i'm not suggesting you would intentionally remove functionality in your rom; but your rom is a work in progress, just like all roms. i'm sure with room for improvement, and those improvements are generally made with feedback and insight from other users.
good luck with your rom developmemt if this is how you respond when other users try to help each other online, out of your thread nonetheless, on a forum thats says "xda", not "dexter's". you should be taking these opportunities to learn from other people that are willing to help you, instead of assuming you have all the answers. i only quote what other users have been freely pm'ing and emailing me in private, after you've clearly given this impression to other users, and not for the first time.
EDIT: @dexter_nlb; i will have my own a7 by next week. you can rest a little sounder knowing i won't be suggesting untested solutions in the near future. sorry for the scare.
bluetooth access is if the framework require that in combination with a headset that has speech support or similar, but direct related its not.
Contacts and Bluetooth works independently.. and some rights failing during bootup can be ignored, and yes, contacts and calendar is "motorola" design for mobiles, so bluetooth makes less sense here, and the access is not important.
people using BT gps units mostly fail with it, as they think they should have it in "connected" state when they use the bluegps4droid app, but no, just have it paired is ok.. and mock locations enabled in this case under development, but all info possible to find when looking for bluegps4droid..
my previous problem with bt, was firmware flashing in previous releases not happening for all ppl. 1.41 do not have the problem.
the "problems" reported on 1.41 is sdcard related, that did not exist on 1.3 or previous as it were not at all found in android, but only as mount in filesystem. now its fully supported but with some tweaks to work with.
I installed Dexter's Bluetooth Fix for version 1.3 and it worked...I got my bluetooth back. Now I'm trying to get my GPS receiver to connect again -it did so for a while last night and won't connect again since I rebooted. However, I'm sure that's an issue with the hardware I'm using and will keep working on it.
Thanks to everyone who is working on making this tablet work better. I have learned a lot from all of the discussions and explanations. It is very appreciated.
I had an old "Palm" branded Garmin bluetooth GPS receiver laying around; so, I decided to give this a try with my A7. Pairs with bluetooth fine. Connects with Bluegps4droid. GPS stats seems to report the correct lattitude and longitude, but Google navigation does not work at all. I own copilot; so, maybe I'll try that later.
Every time my car connects via Bluetooth I get a window and notification sound on my Note3 that asks me if I want to make my device discoverable or something along those lines. My car successfully connects but I have to click cancel on this window every time. Does anyone know how to disable this?
Thanks
docprego said:
Every time my car connects via Bluetooth I get a window and notification sound on my Note3 that asks me if I want to make my device discoverable or something along those lines. My car successfully connects but I have to click cancel on this window every time. Does anyone know how to disable this?
Thanks
Click to expand...
Click to collapse
The pop up refers to whether or not you wish to share your contacts and other files from the device with your audio systems capabilities. There is a radio dialog you can click on so it will accept your initial answer and no longer prompt.
Hope this helps!
Thank you, however this pop up has nothing to do with sharing contacts. It lists my phone on top with a check box to make it discoverable. And it shows my connected car audio system below. If I tap the lower entry it will ask me if I want to disconnect from my car. If I tap the other one it puts my phone into discoverable mode for 2 minutes. The problem is the phone is already connected.
Sent from my SM-N900T using Tapatalk
docprego said:
Thank you, however this pop up has nothing to do with sharing contacts. It lists my phone on top with a check box to make it discoverable. And it shows my connected car audio system below. If I tap the lower entry it will ask me if I want to disconnect from my car. If I tap the other one it puts my phone into discoverable mode for 2 minutes. The problem is the phone is already connected.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Strange... The only thing I could suggest would be to look at your BT settings on the device. Maybe some type of menu item has been selected thus causing this popup to occur. The only other method is to delete the paired device from your vehicle's BT system and add it again in case some type of glitch happened during the discovery and pairing process.
Hope this helps!
cellrama said:
Strange... The only thing I could suggest would be to look at your BT settings on the device. Maybe some type of menu item has been selected thus causing this popup to occur. The only other method is to delete the paired device from your vehicle's BT system and add it again in case some type of glitch happened during the discovery and pairing process.
Hope this helps!
Click to expand...
Click to collapse
Here's a screenshot of the window:
I get the same thing. Subscribed.
Sent from my SM-N900T using Tapatalk
Any Updates?
Sent from my SM-N900T
I get this too, but it's with my Motorola headset, not a car device. I just hit cancel. Sure would be nice if it would stop doing that.
Same here with my car's bt. I just hit "home" every time...
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Well, I too get this window when I connect to my bt speakers at work and furthermore I'm not sure why I have to always physically connect. on my nexus as soon as I turned on bluetooth it would automatically connect.
I am coming from a long history of HTC use and so I apologise if this question has an obvious answer.
Previously, if I wanted to connect to my bluetooth in the car (previously paired with), I would just hit the bluetooth button in quick settings to turn it on and that was it, just like connecting to wifi.
If I do this on my S7E, I then get another screen popping up that tells me my device is visible to others and lists previously paired devices for me to select from, and then I have push the back button to leave that screen?
Is there a simpler way as I used to do on my HTC?
cheers
C.
PS - I am sure this will be the first of a number of questions as I get used to TouchWiz and Marshmallow......Sorry.....
crazyC said:
Previously, if I wanted to connect to my bluetooth in the car (previously paired with), I would just hit the bluetooth button in quick settings to turn it on and that was it, just like connecting to wifi.
Click to expand...
Click to collapse
Have you ever *paired* your new phone with your car?
I've only had two cars with BT in them, but in both cases the car and phone had to be paired before they would work together.
Once that was done then it would work as you expect.
Specifics of getting your *car* into pairing mode I can't help with, but once you do that you should be able to select it while scanning from the phone (as you've seen already the phone will list devices it finds) and you can finish walking through the pairing.
C0derbear said:
Have you ever *paired* your new phone with your car?
I've only had two cars with BT in them, but in both cases the car and phone had to be paired before they would work together.
Once that was done then it would work as you expect.
Specifics of getting your *car* into pairing mode I can't help with, but once you do that you should be able to select it while scanning from the phone (as you've seen already the phone will list devices it finds) and you can finish walking through the pairing.
Click to expand...
Click to collapse
Oh yes, it was paired with the bluetooth fine (its actually a visor BT device, not the car itself), and when I turn on the BT it shows up on the list of previously paired devices)
Don't have to make it a trusted device for it to auto-pair?
Why turn Bluetooth off at all?
Just leave it on.
Regards,
Dave
Sent from my Nexus 6P using Tapatalk
neezy13 said:
Don't have to make it a trusted device for it to auto-pair?
Click to expand...
Click to collapse
Nope, just had to be paired.
Trusted Device brings in the Smart Lock stuff, which enables the option of having your phone NOT authenticate you (pattern/pin/finger/passwd) when connected.
For example, I have my car bluetooth set as a trusted device so that when I'm driving I don't get any identity challenge to use the phone (like for navigation), the screen will just come on as requested.
Smart lock is blocked by my exchange administrator as I get my work emails on my phone.
I turn the Bluetooth on the phone off because I don't turn the one in the car off and it's just outside the house and will stay connected.
Sent from my S7 Edge