I believe that this also affects other HTC models, but I'm puzzled by it:
If I go to the communications menu and switch off the phone receiver, the GPS also seems to stop receiving. Enabling Bluetooth seems to bring it back to life, but enabling WiFi doesn't.
I don't always want to have the phone receiver working when I'm travelling using GPS, so it's rather annoying.
Does anyone know the reason why this happens ?
Are there perhaps some common parts of the Qualcomm chip that are shared by the GPS and phone and/or bluetooth ?
- Steve
Hi guys,
Yesterday I was thinking about how to enable the NFC sgs2 not have this technology, so I thought that using bluetooth or wifi direct you might also enable nfc
Android is not a developer so I need someone who can create a program that "hijack"the signals that are transmitted via the nfc nfc chip to an external device via bluetooth or wifi direct, then I did this I will create a hardware device composed of the NFC chip and a receiver / transmitter bluetooth or wifi direct to hide behind the battery, you will be able to receive the signal and then sending it to the NFC chip.
Does anyone know how to help me?, I am completely new in the Android paronama.
Think you need an extra chip for that, not as "simple" as hijacking a signal.
^
From what I understand, I think he is suggesting an "external"/standalone NFC device that will communicate with the phones via Bluetooth or Wifi.
@OP
I suggest you look for NFC capable android-arduino (open source dev boards for android phones).
Like this(I think this is exactly what you want to do as that board all needs is a BT module and an android program to interface with the board.):
Arduino to Android IO on the cheap (aka Poor Man's NFC)
http://jdesbonnet.blogspot.com/2011/05/arduino-to-android-io-on-cheap-aka-poor.html
I think the only advantage of NFC technology is security.
It was intentionally design to attenuate in a very short distance for security sake.
If NFC signal can be transferred to another wireless signal,then why we use NFC in the first place.
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!
Hi
I have an issue with my Samsung Galaxy S4 GTi-9505 with Cyanogenmod 12.1 where having Wifi and Bluetooth enabled causes one another to stop working.
I believe this was a known issue but the net is strewn with out-of-date information and forum posts and I just cannot seem to find out whether or not there was ever a solution.
The actual problem is if I have both Wifi and Bluetooth enabled, connected to Wifi but no bluetooth device the Wifi will drop after a few minutes and will switch from 'Authenticating...' to 'Saved' over and over. Switching off the Bluetooth will allow the Wifi to stay connected. Switching off the Wifi and turning it back on will allow the Wifi to stay connected for a few minutes. If I am streaming music to my car's head unit via Bluetooth with Wifi enabled I'll get broken stuttery audio with occasional Bluetooth crashes.
Specs and stuff:
Samsung Galaxy S4 GT-i9505
Cyanogenmod: 12.1-20151106-Nightly
Modem/Baseband: XXUHOF2
Physical environment: Wifi 54G access point
Maybe relevant: open plan office with other random Bluetooth devices kicking around.
Any help would be much appreciated. Thanks.
Hello. I bought from AliExpress android headunit for audi a6. In main manu it have "phone" and there I am able to connect phone for calls and music play. I wanted to connect obd2 bluetooth adapter to this android unit but cannot enable bluetooth at all. It has system settings, under that there is android settings. And those are classic tablet settings for Android. There is Bluetooth option, but when I try to enable it, it refuses. Like factory disabled that.
Is there any way to acrivate that Bluetooth like on normal phone or tablet android?
Activate Developer options, check your settings there. Network reset. Clear system cache.
blackhawk said:
Activate Developer options, check your settings there. Network reset. Clear system cache.
Click to expand...
Click to collapse
I will try that. Do You think that it has Bluetooth like any other tablet, just restricted by software? Seller told me that doesn't support obd2, only for phone connection.
Cannot turn it on. Video attached
Found bluetooth config and switches to BT transfer. (Was BT phone). Now it works
I have the same issue. Can you tell me exactly how you fixed it. How did you get to Bluetooth config. I may have gotten to it, but I see bt phone or bt audio emission. I'm also trying to connect a bluetooth ObdEleven
JovanSRB said:
Found bluetooth config and switches to BT transfer. (Was BT phone). Now it works
Click to expand...
Click to collapse
How did you get to bluetooth config?
JovanSRB said:
Found bluetooth config and switches to BT transfer. (Was BT phone). Now it works
Click to expand...
Click to collapse
Would be cool to know this?
Hello. It was long time ago, I forgot how exactly I came to settings. But, goal is to switch from BT phone to BT transfer. Now I can connect OBD bluetooth adapter. I must check it again and I will write here. I am sorry for late answe, i have little time in this period, so I can't pay attention enough.
JovanSRB said:
Hello. It was long time ago, I forgot how exactly I came to settings. But, goal is to switch from BT phone to BT transfer. Now I can connect OBD bluetooth adapter. I must check it again and I will write here. I am sorry for late answe, i have little time in this period, so I can't pay attention enough.
Click to expand...
Click to collapse
Did you find it?