Database Develop

[Q] What GPS Receivers work with the KFHD

I posted this as a comment on a thread, but then noticed it was in the wrong KFHD section.. Appologies.. Can anyone help with this, the question would most likely be the same.... What GPS Receivers work with the KFHD, whos had success and who's tried and found a certain one didnt work ?
Ive got a BT338 GPS Receiver and trying to get it going on two rooted KFHD 7" both have KFHD xSettings installed, I must have spent about 6 hours reading different threads and trying things.
One on FW 7.4.3 and one on FW 7.4.1- tried them both with de.mobilej and Bluetooth GPS Provider.
The KFHD 7" on FW 7.4.3, this one connects to the Bluetooth device, however no satellites can be seen to have been detected, also Google maps and navigation both report "Searching for GPS" even though Blutooth GPS reports as active!
The KFHD 7" on FW 7.4.1 this one cannot connect to bluetooth device ??
If I launch GPSHunt, on either of them - this does not see any satellites either
All the usual stuff is turned on -
Location based services ON
Allow Mock Locations ON
Tried a few different permutations nothing seems to work for me, the frustrating part is that everything on the FW 7.4.3 seems to work okay standalone but wont just come together I cant understand why it will connect to the bluetooth receiver but not detect satellites, even though the receiver is reporting that satellites are detected (slow blinking green light).
Any help or advice appreciated
Thanks in advance

As the kindle hasn't an internal GPS, you need an app that acts as an intermediary between the two devices, an app that integrates the GPS inside the system, a "GPS Provider". All the providers that I know need to be set "Allow Mock Locations" in DEV settings to work.
From AmazonOS 7.3.1 there is a protection that hangs the program who access "Mock Locations".
But there are a few exceptions to overcome that limitation:
Fist, "Bluetooth GPS Provider"(Michael Chourdakis) is immune to that protection and injects coordinates to the system(works but jumps to a distant point and returns every now and then), is very basic and is hard to connect.A special case is "Bluetooth GPS"(from GG MobLab aka Goo goo) only installable in kinology( another protection that refuses the installation of GPS related apps), that connects perfectly to any dongle but hangs immediately when "Use Mock Location" is set inside the app...
Second, there are map based apps that own their "GPS provider". This allow them to connect to a paired GPS and work, but they don't inject coordinates to the system. I know two, Trekbuddy and Oruxmaps.
All this is theoretic, as you must test with your hardware the clues I give . There are also some utilities that transform an android phone into a GPS dongle, but my experience has been disappointing.

Thanks for the advice gflorezarroyo, I'll give Trekbuddy and Oruxmaps a try :good:

Great news gflorezarroyo, Oruxmaps works you just have go into the settings on the program and enable Bluetooth GPS, then in following screen check the box "Enable GPS from bluetooth device" then turn the GPS sensor to "ON" Thanks again :good:
This works with both the TomTom wireless GPS MkII and the BT338 GPS Receiver

I'm on 7.4.3 and use Bluetooth gps provider. I have a HOLUX M-1200 bluetooth gps. iGO works, navigon works, gmaps work.
Before the 7.4.3 update, nothing worked. After you open Bluetooth gps provider just try a few times to connect to the paired GPS device. It will fail a few times, but you will eventually get it to connect.

Thanks for the info phonexpert_alex, I also got Locus Map Free (Asamm Software, s. r. o.) to work very well on both Kindles.. Using the TomTom MII bluetooth reciever and a downloaded (for offline use) vector map of GB.. Its fully working and down to street level with the maps, postcode search etc etc, a really nice piece of mapping software, I will use it for a couple of weeks checking for stability and then buy the pro version (£5.99), It will help support the developers even if I dont use any of the added functionality, thanks again :good:

[Q] Fuelband as a Trusted Bluetooth Device?

So I am eagerly awaiting my Cyber Monday (Wednesday) Moto X and while doing so, I've been browsing through accessories I might want to enhance my Moto Xperience, and I really want to take advantage of the Trusted Bluetooth Device along with Touchless Controls.
I've been searching around, but I haven't been able to find a definitive answer, just off-to-the-side mentions of its use.. I have a Nike Fuelband SE that has BTLE. Nike doesn't support AndroidOS, so there's no dedicated app for it. I am, however, able to discover it with my current phone (Droid 4).
So basically, does anyone know if I will be able to use my Fuelband as a Trusted Bluetooth Device, or how I might go about doing that? I guess I could find some BL keychain if there was no way to use it.
Thanks ahead of time for your replies and help.

If your droid 4 can see it I can't see why the moto x won't. Once you connect to a Bluetooth device it will ask you if you want to make it a trusted device. If it doesn't the setting is under security. I can't see why it wouldn't work. Good luck.
Sent from my XT1060 using xda app-developers app

Thanks. I was concerned because it didn't actually support Android, but was hoping it could simply act as a dummy BTLE device. Got an e-mail from Fedex telling me it's arriving today so I'll test it out and come back here with what I've got

If anyone happens to be interested, the Fuelband SE isn't continuously syncing via Bluetooth to the Moto X. It pairs, and the Moto X asks if I want to make it a trusted device, but the notification tray icon never turns blue. It doesn't seem to be able to continuously sync. Too bad I was really looking forward to this.
If anyone knows a way around this, please let me know. Thanks!

iJusDefy said:
If anyone happens to be interested, the Fuelband SE isn't continuously syncing via Bluetooth to the Moto X. It pairs, and the Moto X asks if I want to make it a trusted device, but the notification tray icon never turns blue. It doesn't seem to be able to continuously sync. Too bad I was really looking forward to this.
If anyone knows a way around this, please let me know. Thanks!
Click to expand...
Click to collapse
have you done any other testing? kit kat got rid of the blue theme. the icons are either orange (no connection), white (connected) or dark (disabled).

I just tried it with a bluetooth headset and the icon turns and stays white. With the Fuelband connected, it just stays sort of grayed out.

Working!
This has been pushed back due to what I assume is a lack of interest for, but in case someone else decides to figure this out or something similar to it, I have managed to get the Fuelband SE to "sync" with the Moto X and act as a Bluetooth Trusted Device.
There's an app on the Play store called "Bluetooth Auto Connect" that you can set to sync with the Fuelband (and what I assume would be any device) and it will do so automatically. The icon stays greyed out, but turning the Fuelband's BT on and off in turn pops up that Trusted Device notification on the Moto X.
I hope this helps someone else with any type of random trusted device need.
Cheers

iJusDefy said:
This has been pushed back due to what I assume is a lack of interest for, but in case someone else decides to figure this out or something similar to it, I have managed to get the Fuelband SE to "sync" with the Moto X and act as a Bluetooth Trusted Device.
There's an app on the Play store called "Bluetooth Auto Connect" that you can set to sync with the Fuelband (and what I assume would be any device) and it will do so automatically. The icon stays greyed out, but turning the Fuelband's BT on and off in turn pops up that Trusted Device notification on the Moto X.
I hope this helps someone else with any type of random trusted device need.
Cheers
Click to expand...
Click to collapse
so what can you do with it?

640k said:
so what can you do with it?
Click to expand...
Click to collapse
You can use it as your trusted device to keep your phone unlocked while you're in proximity to it and connected via Bluetooth. Saves me those few seconds of having to enter in my password, and maintains some security.

iJusDefy said:
You can use it as your trusted device to keep your phone unlocked while you're in proximity to it and connected via Bluetooth. Saves me those few seconds of having to enter in my password, and maintains some security.
Click to expand...
Click to collapse
you're not using it for its fitness aspects?

640k said:
you're not using it for its fitness aspects?
Click to expand...
Click to collapse
Oh, I thought you were referring to what I can do with the pairing to the Moto X.
I've been using the fitness aspect of the Fuelband since March 2012. The newest one that I have now I can use to track my general activity throughout the entire day, tag specific workout sessions in order to keep track of my workout intensity over time, track hours of sleep, and set goals for myself (via # of Fuel points) every day to give me an activity level to reach for. Since there's no Android app or any sort of Android support on Nike's end, I do all my data syncing through my PC.
And now I can use it to keep my phone unlocked when it's on me

I've got a Pebble syncing fine and enabled as a trusted device but my bluetooth icon is always greyed out. I think it only turns white when there's an audio connection like with a headset or stereo.

clankfu said:
I've got a Pebble syncing fine and enabled as a trusted device but my bluetooth icon is always greyed out. I think it only turns white when there's an audio connection like with a headset or stereo.
Click to expand...
Click to collapse
Makes sense why mine is grayed out too. Pebble supports Android though, and since there's no support/app for the Fuelband on Android, I had to use the auto bluetooth connect app to force a pairing to make it a trusted device. Was close to buying a Pebble though. Saw it was on sale for $90.

iJusDefy said:
Makes sense why mine is grayed out too. Pebble supports Android though, and since there's no support/app for the Fuelband on Android, I had to use the auto bluetooth connect app to force a pairing to make it a trusted device. Was close to buying a Pebble though. Saw it was on sale for $90.
Click to expand...
Click to collapse
Yup. I got mine yesterday from Best Buy for $90. Wasn't planning on buying one but, at that price, I thought what the hell. So far I'm really digging it.

Its a shame it wasnt hacked already it would be nice to have wristband with notification...I am not into fitness or watch stuffs :angel:

Thanks for the info on the app!
By using this app to ensure a connection, how long does your Fuelband SE battery last? I suspect it has shorten considerable from when you were not using BT at all.
Also, since there are at least 2 battery sizes depending on the band size (circumference), which size is yours?

[Q] AT&T Galaxy S4 Active - Bluetooth device kills audio during phone calls

Hello everyone! I have been trying to track down a problem with my Galaxy S4 Active that has been driving me nuts for a while. I figured that making a new thread would probably be best because I did not find my particular issue listed.
Basically, what happens is that I will make a call over Bluetooth and everything will be fine. Once this call has ended, all audio related to phone calls dies. The phone still behaves as if it is making and receiving calls, but nobody can hear me and I cannot hear them. Not over Bluetooth, through the earpiece, nor over the loudspeaker. It’s all dead. I also cannot hear it ringing if I dial out, but the phone itself still rings.
I have tried turning the Bluetooth device on and off, disabling Bluetooth and turning it back on, going into Airplane mode and back out again, turning speakerphone on and off, muting and unmuting the call, and muting and unmuting the phone itself. The only thing that fixes this situation is restarting the phone.
I recall this situation first started presenting itself after updating to the ML2 firmware, but it didn’t happen all the time. It became much more apparent after updating to the NE3 firmware. At that point I spent some more time looking into it and became able to readily duplicate the issue.
I have gone so far as to reflash the NE3 firmware with Odin 3.07 to see if the issue remained. Interestingly enough, this appeared to correct the issue until I started updating and reinstalling a few apps. So now I’m trying to track down exactly what did it.
I suspect that it may be the “OK Google” hotword scanning from Google Search because I had it set to detect “From any screen” as well as “From lock screen”. Although I did not have the “Bluetooth headset” setting enabled because I wanted to take that out of the equation. Once I turned off “From any screen”, the Bluetooth appears to be working normally.
Another possibility is that I had frozen S-Voice because it got in the way of the normal voice dialer. This has been restored. I also have to mention that the voice dialer appears to be more stable after disabling “From any screen” as well.
I also can’t say for sure, but it also seems to happen more frequently when charging. Although that may just be a coincidence as I normally do charge my phone when I connect it to Bluetooth. Also I have duplicated the issue when not charging and gotten it to work fine while on the charger. So it is probably just a coincidence.
Here is what I’m working with:
AT&T Galaxy S4 Active (SGH-i537) reflashed back to I537UCUCNE3 Android 4.4.2 stock firmware.
Jabra SP700 - Main device I’m testing with. Old Bluetooth 1.1 speakerphone that clips on a visor. Supports A2DP for an FM transmitter to stream music, but I have Media disabled on it. I tested with and without this setting and it made no difference. It worked great back when I was on MF3, but started having problems since I upgraded to ML2 that are easily replicated now on NE3.
Jabra BT620s - Secondary device that I tested with that also demonstrated the same problems. Although I haven’t tested as much as the SP700. This is a pair of stereo headphones that uses Bluetooth 1.2 and A2DP for streaming music. Also worked better with older firmwares, but I haven’t used it much lately save for testing this problem.
Installed/Updated Programs:
Facebook
Facebook Messenger
Google Authenticator
Google Chrome
Google Maps
Google Play Newsstand
Google Play Services
Google Play Store
Google Search
Google Voice
Google Hangouts
Jift
SuperSU
Titanium Backup
Titanium Backup PRO
towelroot
YouTube
Other apps that I updated and then I rolled back to get things working:
AllShareCase Dongle S/W Update
Amazon Kindle
ANT Radio Service
ANT+ Plugins Service
Antivirus & Security | Lookout
Beaming Service for Samsung
Beats Music
Blurb Checkout
Gmail
Google Drive
Google Play Books
Google Play Games
Google Play Movies
Google Text-to-Speech
Google+
GROUP PLAY
HP Print Service Plugin
Lux
myAT&T
Samsung Link
Samsung Print Service Plugin
Samsung Push Service
Samsung WatchON (Video)
Samsung WatchON (On TV)
YP - Yellow Pages local search
I also tested it quite a bit right before and after rooting it and it was working fine at the time, so I don’t believe that it’s related to root.
I would like to know if anyone else has encountered similar issues or can duplicate what I’m seeing?
Thanks!

After spending some more time testing it, I can verify that it IS in fact the “OK Google” hotword scanning from Google Search 3.6.14.1337016.arm. When it is set to detect “From any screen” and well as “From lock screen”, the audio will die after the first call over Bluetooth. Once I turned off “From any screen”, the Bluetooth works normally.
Now that I've finally found it and can easily replicate it, I'm still curious if other people can replicate it or if this is something isolated to my phone and/or Bluetooth devices. Would anyone be interested in testing this with me?
I'm planning on writing up some feedback on it once I have a better idea of how big an issue it is. I think it would also help anyone else that runs into this problem. I've been fighting with this off and on for over a month because it seemed so random.
Thanks.

I am having the exact same issue with the 2 s4's that I own. I suspected it was either svoice or Ok google, I will try to turn off the from any screen setting and see if it fixes the issue on mine as well. That is a shame because I really like using the ok google feature from any screen.

I've been having the same issue, but did not realize it was ok google from any screen. I've turned it off now, let's see if it works. Thanks for the heads up.

It looks like a recent Google Search update re-enabled the "From any screen" OK Google hotword detection setting. This still is not fixed and it killed all call audio while I was trying to lead another vehicle. I didn't find out until I parked that it was turned back on.
I have sent feedback to Google on the Search app and recommend that everyone else who has had this problem do the same. If this continues to happen, I will resort to negative reviews if I must. Please help get the word out if you are having the same issue. Thanks!
EDIT:
There are apparently several other people having the same problem on other Samsung devices (particularly Galaxy S4's):
https://productforums.google.com/forum/#!msg/websearch/mEhHyCs6F5o/HVArojlzIrAJ
http://forums.androidcentral.com/sa...-sound-phone-calls-after-using-bluetooth.html

[Q] Post 5.1 Bluetooth Issues/bugs

5.1 did not fix the bluetooth issues I had...it actually added another bug.
New with 5.1:
-When playing music with Google Play Music, whenever I switch tracks, the screen turns on. Why?
Still a problem after 5.1:
-Sometimes Bluetooth plays but without sound - it takes some weird opening/closing/pausing/starting maneuvering to hopefully get it working
-Pause during notifications does not work properly - I've tried this with Google Maps and a few different podcast apps. With Google Maps Navigation on and a podcast playing...when Google Maps wants to talk, it pauses the podcast (as the setting says) but the Google Maps notification is muted. It's just silence until it is done and then the podcast resumes.
Is anyone else having these sort of issues?
Nexus 6, 5.1D, stock, rooted ,twrp, with my 2013 Cadillac ATS

Yes it is happening to others myself included. why? I have no idea. But you are certainly not alone.
Sent from my Google N6 on VZ

I just posted this in the General section ....
OTA'd the 5.1 update on 3/26/15.
Since then, contact addresses fail to appear on vehicle displays over Bluetooth.
Rebooted phone / Forgot and paired phone to vehicle, no fix.
Phone is paired to 2 vehicles with the same results.
Can anyone confirm this?

Having the same issue. If you disable ambient display, the screen will stay off when selecting tracks with Bluetooth. My issue with Bluetooth is that every few days I have to reboot the phone to get the BT to work. I can't even toggle Bluetooth. When I do, it says Bluetooth turning off, it toggles back on by itself. Tried force closing all running apps but dosent help.

Bluetooth...
jeffreii said:
5.1 did not fix the bluetooth issues I had...it actually added another bug.
New with 5.1:
-When playing music with Google Play Music, whenever I switch tracks, the screen turns on. Why?
Still a problem after 5.1:
-Sometimes Bluetooth plays but without sound - it takes some weird opening/closing/pausing/starting maneuvering to hopefully get it working
-Pause during notifications does not work properly - I've tried this with Google Maps and a few different podcast apps. With Google Maps Navigation on and a podcast playing...when Google Maps wants to talk, it pauses the podcast (as the setting says) but the Google Maps notification is muted. It's just silence until it is done and then the podcast resumes.
Is anyone else having these sort of issues?
Nexus 6, 5.1D, stock, rooted ,twrp, with my 2013 Cadillac ATS
Click to expand...
Click to collapse
When it comes to bluetooth problems, especially with cars and this phone you will find very few helpful answers. Sad but true, not many Nexus 6 people seem to use hands free automobile applications on their device. I had to buy a new head unit for my car along with all the other bullcrap to make it look nice in my car to get some of these puzzling problems to disappear. Android Auto works great if you have the supporting gear in your car and follow the instructions about how to pair phone with car and use the right USB port and wire in your Nexus. After that, everything works as expected. Unfortunately you do have to spend some cash and time to do this but it is the future and if you plan and use your phone in car more than anywhere else, it is worth the investment and will improve with time. The only good take away from all this is, so far only nexus devices running lollipop work with Android Auto supporting head units.

vvveith said:
When it comes to bluetooth problems, especially with cars and this phone you will find very few helpful answers. Sad but true, not many Nexus 6 people seem to use hands free automobile applications on their device. I had to buy a new head unit for my car along with all the other bullcrap to make it look nice in my car to get some of these puzzling problems to disappear. Android Auto works great if you have the supporting gear in your car and follow the instructions about how to pair phone with car and use the right USB port and wire in your Nexus. After that, everything works as expected. Unfortunately you do have to spend some cash and time to do this but it is the future and if you plan and use your phone in car more than anywhere else, it is worth the investment and will improve with time. The only good take away from all this is, so far only nexus devices running lollipop work with Android Auto supporting head units.
Click to expand...
Click to collapse
It wasn't perfect, but my Bluetooth was just fine pre 5.1...I can deal with the quirks and avoid spending $$ on Android Auto (for now at least)...but these major bugs need to be fixed ASAP.

Do we know if this is fixed?
Is this fixed in 5.1.1? Is there an issue logged with google? Anyone?

I have my nexus 6 rooted with 5.1.1 stock and the bluetooth doesn't work. I cannot see any device but the other devices can see it.
I have tried to fix it clearing cache and data (only bluetooth) but the problem is still there.
Do you have any idea guys?

This morning I remembered my experiments with my old gt-9100 and I have decided to do wipe cache and wipe dalvik-cache.
And now... bluetooth is alive!!!
[emoji39]

Pixel XL issues with Android Auto

I recently purchased a new VW car and have been using Android Auto on the built in display. The first time I used it it all worked perfectly, since then it hasn't. My Android Auto no longer gives me notifications when I receive texts. And if they do show up on the home screen and I click the play button to read them, it shows the four dots as if its thinking but nothing happens and I have to cancel out of it.
Additionally, I've noticed that my bluetooth smart lock doesn't seem to be working at all. Every time I connect it asks if I want to add my car to my trusted devices. Each time I say yes but it NEVER seems to save it. It will then later sometimes prompt for permission to read my messages. To this I again say yes but it doesn't seem to make the message issue go away even after I do this. I am not sure if these two issues are related (I'm hoping they are).
Can anyone tell me why the hell my smart lock can't seem to register and remember my car? And why wont android auto read my messages properly? (Pixel XL. Phone calls and navigation all are working properly)

Same issue here

You have to give Android Auto all permissions it asks for at the first start. And be sure to use a very good cable. There are many USB C cables on market which are not fully supporting USB C features and the system do expect them.

I'm in the same situation with my VW Atlas. Problem is with both my Pixel (running Android O) and my wife's Nexus 6p (running Nougat). I have given it all permissions, including some that it didn't ask for. I also have been using the little 4 inch cord that came with the 6p, so the cable or its length should not be an issue. In addition to the above, my car also forgets its bluetooth pairings if I try to connect the AA cable before the bluetooth has connected. I've been learning to do that but sometimes I forget. It's got to be an issue with the VW software.

I have come across these issues myself in a Golf Mk7 both with a Motorola Droid Turbo and now with a Google Pixel 3 XL.
In the case of getting Android Auto to read/send messages where you just get the four dots bouncing up and down and doing nothing else, that's a setting with the Google Assistant app. Go into that app on your phone (the round G icon) and drill into settings and under Voice >> Voice Match, make sure "OK Google" detection is turned on. Even though you might not be actually using it, it has to be turned on for this to work. Totally lame and non-intuitive, but that's what fixed that for me.
As for the car falling out of your Smart Lock and for repeatedly prompting you for permission to access your text messages, I have only had this issue with AA in my VW and not in other cars, so it's a VW-specific issue and something to do with the bluetooth hardware. I do not have a fix for it but the workaround is you must have BT turned on on your phone first and let it connect fully to your car OUTSIDE of AA. Make sure at that point you permit text message access (if prompted) and check your Smart Lock and add your car to it if needed. Then going forward whenever you connect to your car you MUST let BT connect fully first before you plug in and fire up AA. It's unfortunate that you can't just plug in and go w/o waiting for BT first but that's the only way I've gotten this to work without re-prompting me for SMS access permissions and Smart Lock.
Good luck!