Database Info

[Q] WP7 Bluetooth Functionality

I would really love to use a WP7 as my main phone. However I have 2 deal-making requirements:
1) Bluetooth DUN profile
I have a Mercedes Comand Online in my car which requires Bluetooth DUN capability, From what I've seen, even the Mango update won't address this? I assume there can't be any 3rd party apps available due to lack of APIs?
Even the Blackberry supports this functionality.
2) Wifi Tethering
For me, it is staggering how the WP7 doesn't support this and I haven't read anywhere in the Mango updates that WP7 will support wireless tethering. Again, is there any possibility that this will be possible?
Android and IOS allow these functionalities via jailbroken or unlocked software. For me, if WP7 is serious about making headway into the market, Microsoft need to cater for gaps in the market.

2) Wifi Tethering
Actually this will be available in Mango but as a hidden feature , Soon we will know how to enable it.
The first one is up to MS to make as nothing can be done to change any core functionality of this OS

Thanks, Wifi tethering sounds promising. Particularly if you can use it in stealth to stop carriers from charging you extra for tethering.
You can do this on IOS with Mi-wi or PDAnet.
As for the bluetooth issue, I just hope Microsoft get their act together but it doesn't sound like it will happen anytime soon! Do you know if Bluetooth PAN is / will be supported?

2) Wifi Tethering
Click to expand...
Click to collapse
Yes, it's included into MANGO update.
But it need proper drivers with internal support;
HTC WP7F doesn't have such drivers for now.
It seems they built in such kind of support inside driver in HTC WP7S (Omega, Entitle) but there also used new BCM4330 seems. So it's not very backward compatible with BCM4329.
1) Bluetooth DUN profile
Click to expand...
Click to collapse
There also some drivers was added in MANGO, but they are unused seems for now.

Worth noting that Bluetooth access is probably possible using native DLLs. The APIs are still there, and if you have a WinCE dev kit you can code against them.
Currently we can't use homebrew native DLLs in Mango, but Heathclif74 says he's got a way to fix that. This would mean you could run any code you wanted to, even in Mango.

I think you should add this app into settings (I'm going to do it myself later, but maybe it would be nice feature for everyone? )
Sent from my 7 Mozart using XDA Windows Phone 7 App

Wrong thread. Damn. It was intended for your multitask toggle app, GoodDayToDie
Sent from my 7 Mozart using XDA Windows Phone 7 App

Google Wallet

So the Galaxy Nexus guys got Wallet working on their phone with just an .Apk. I installed the .apk and it installed but FCed every time I tried to run it with NFC enabled. I was hoping someone more talented than me would be able to make it work for us.
http://forum.xda-developers.com/showthread.php?t=1365360
[APP] Google Wallet (Flash: 1.1-R41v8, APK: 1.1-R41v8) [18/12/2011]

I'm running the taste of ics from and tried side loading the apk today. All I got was a black screen.

i installed the apk and when the app started up i got an error saying my version of android was not supported (2.3.5) and then a second error saying that my device is not supported. Im thinking that maybe if i installed a 2.3.6 rom and then modified my build.prop to fake my device as a sprint nexus s, maybe that would trick the app into working? The rom will need to have nfc enable of course too. Anyone know of a good 2.3.6 rom with nfc?

I'm running TPCv2 with DaG.3 kernel and didn't get any errors when installing it. The app came up and said NFC needed to be enabled and when I did that it FCed. But otherwise it didn't FC or error.

EvilEvo said:
I'm running TPCv2 with DaG.3 kernel and didn't get any errors when installing it. The app came up and said NFC needed to be enabled and when I did that it FCed. But otherwise it didn't FC or error.
Click to expand...
Click to collapse
Same here. Installed fine and asked to enable NFC in settings. Once enabled though, Wallet forced closed. Running Quikwiz 1.0.3

I'm curious if changing build.prop to what the galaxy nexus is would fix the issue.

I would be eternally grateful if a dev were able to get this working for us.
I got the same result. Launched at first to tell me NFC needed to be enabled, but after I enabled it, I got force closes. Running QuickWiz 1.0.3

Its sounds like we are missing some important libraries that are required for wallet to talk to the NFC hardware. I noticed that the process for the nexus includes adding another JAR and APK which look like they add additional NFC functionality. Has anyone tried going thru the install process listed on this thread?
http://forum.xda-developers.com/showthread.php?t=1365360

sclarke27 said:
Its sounds like we are missing some important libraries that are required for wallet to talk to the NFC hardware. I noticed that the process for the nexus includes adding another JAR and APK which look like they add additional NFC functionality. Has anyone tried going thru the install process listed on this thread?
http://forum.xda-developers.com/showthread.php?t=1365360
Click to expand...
Click to collapse
Instructions in that thread basically just say install the .apk. I just tried it again with the same result. With NFC enabled, it FCs when trying to load. When NFC is NOT enabled, it starts up and initializes and then says NFC needs to be turned on. When I do that, it FCs.

right, i was talking specifically about the section below that where it talks about installing NFC extras via a command line.
Has anyone looked in their logs to see if they can find a stack trace after a FC happens? It may give a hint as to what we are missing. I dont get the same errors on my phone so my logs aren't useful.

http://forum.xda-developers.com/showthread.php?t=1282890
XK72 said:
I've seen a couple posts regarding getting Google Wallet to work (and hopefully I'm not being redundant with this post). I've had Google Wallet working on my own 2.3.5 source ROM for quite some time now and I figured I'd share what got it working for me. As a matter of disclosure, I do have the 4G, but I haven't seen anything in the code that would give reason for why this wouldn't work.
While I'm able to build a ROM, I for some reason, don't know how to put together a flashable update. Maybe somebody with a little more know-how can piece this together and try it out, or at least tell me I'm wrong.
Files needed from the GWK74 ROM:
system/etc/permissions/com.google.android.nfc_extras.xml
(I just added the permission entry to the existing com.android.nfc_extras.xml file instead to keep the clutter down).
system/framework/com.android.nfc_extras.jar
The version in the GWK74 ROM contains code that has yet to be released, since korg is down and all. The extra file has something to do with NFC emulation, but I've only glanced at it, so I really couldn't tell you what it does.
system/app/Wallet.apk
Obviously.
Here's the catch: The Wallet app requires permissions from Nfc.apk (NFCEE_ADMIN). By default, the Nfc.apk is signed with the "platform" key, but as long as these two files are signed with the same key, it will grant it the proper permissions to Wallet.apk no matter what key that may happen to be. Considering that Nfc.apk also requests other permissions from "platform" as well, certificate consistency would be advisable.
Hope this works out or at the very least, gets the ball rolling.
Click to expand...
Click to collapse

I suspect that the reason the ADK does not work on the Skyrocket is because the phones have different NFC chip. According to this post, the Galaxy Nexus has the NXP PN65N which contains an NFC controller as well as an embedded secure element (SmartMX) supporting both JavaCard as well as Mifare technology. The Galaxy S II (of which the Skyrocket is a variant) comes with the PN544 which does not have the embedded secure element. This could explain why NFC can be enabled on the Skyrocket (with a custom ROM) but it would FC the Wallet app. The SE (Secure Element) is needed to securely store transaction info and perform all the card emulation functions. Without it, the GW won't work. The app probably just check to see if a SE is available or not, and finding none, simply FC. Now it is possible to use the SIM as a SE but that would require a different SW.
It appears that folks were able to enable GW on the Nexus S, but I think it also sports the PN65N chip with SE. Can somebody confirm it?

wyt168 said:
I suspect that the reason the ADK does not work on the Skyrocket is because the phones have different NFC chips.
Click to expand...
Click to collapse
I think I have found some support for my speculation. In a thread on Android Developer Google Group, Michael Roland explained the 3 different modes of NFC. In particular, the role of SE in the card emulation mode, supports my view expressed earlier, I've lifted the relevant paragraphs here:
So the card-emulation mode allows the emulation of a contactless smart
card (and not an NFC tag, although the smart card could *possibly* be
used as NFC tag). As applications like credit cards typically have high
security requirements, card emulation is not handled by the NFC device
itself (i.e. the application processor of an NFC-enabled mobile phone).
Instead, the NFC device has a dedicated hardware component (the
so-called Secure Element) that handles all the card emulation. (*)
(*) This is not entirely true, as some NFC controllers (like the
PN544) would theoretically allow the emulation of ISO/IEC
14443-4 contactless smart cards from the application processor.
Yet, I don't know of any NFC phone that makes this functionality
available to the user and I rather doubt that this will become
available on the Nexus S.
The Secure Element (SE) is typically a smart card itself. But instead of
a normal contact/contactless smart card interface it has a connection to
the NFC controller, which connects it to the NFC antenna.
The Nexus S has an integrated SE (a SmartMX combined into the same
package as the PN544 NFC controller). This SmartMX emulates a ISO/IEC
14443 (Type A) smart card and a MIFARE Classic card.
In addition to this integrated SE it is possible to use a special UICC
(also known as SIM card) that supports the Single Wire Protocol (which
is an interface designed for the communication between the NFC controller
and a UICC) as the SE.
Click to expand...
Click to collapse

DELETE

Looks like Google Wallet was just released for AT&T Nexus devices, hopefully Skyrocket isn't too far behind. Officially or otherwise androidcentral . com/google-wallet-now-available-nexus-s-and-galaxy-nexus-att

LoSt180 said:
Looks like Google Wallet was just released for AT&T Nexus devices, hopefully Skyrocket isn't too far behind. Officially or otherwise androidcentral . com/google-wallet-now-available-nexus-s-and-galaxy-nexus-att
Click to expand...
Click to collapse
I tried the newest version from the market and got a secure element error. I don't think we're going to get wallet support any time soon because our devices don't have a secure element.

Would it be possible to edit the build.prop to appear as a Nexus S or Galaxy Nexus GSM now to all it to work? It installed fine on my phone but now says my hardware isn't supported.

EvilEvo said:
Would it be possible to edit the build.prop to appear as a Nexus S or Galaxy Nexus GSM now to all it to work? It installed fine on my phone but now says my hardware isn't supported.
Click to expand...
Click to collapse
No because our phones lack a secure element. Physically lack. So no edits to the app will work until Google decides to update this specifically for phones without a secure element.
Sent from my SAMSUNG-SGH-I727 using Tapatalk

I bought some of the nfc tags from sparkfun and the task launcher app and tasker so I could use the tags to run tasker tasks. you know, swipe when you get home, to work, into the car.
When I swipe one I get a force close on the nfc service.:-(
I tried skyicecream and buoyancy roms. fixed permissions. super clean install of rom. Thoughts?

mcmasterp said:
I bought some of the nfc tags from sparkfun and the task launcher app and tasker so I could use the tags to run tasker tasks. you know, swipe when you get home, to work, into the car.
When I swipe one I get a force close on the nfc service.:-(
I tried skyicecream and buoyancy roms. fixed permissions. super clean install of rom. Thoughts?
Click to expand...
Click to collapse
the Alien ROM supports NFC to a certain extent

Developers and non-developers united to get better bluetooth experience at Android

The user ukdutypaid request me and
LNEt - I don't found the profile yet
Robbie P
qazzi76
sergiocabraljr
With some words:
So can anybody tell me either a) why is BT HID so 'rubbish' on Android, ie why is it so rare that anybody seems to have got it to work e.g "Look. It's a massive problem, nobody really knows how to do it. Count yourself lucky that you've got found a GB build where it does work at all. Put the problem down and walk away"; or b) what a solution might be?
I've tried rooting round in builds, until I'm blue in the face but unless the *.so file either has a BT and or an HID in the file name, then I'm in the dark.
qazzi76 ; GregórioAxiaMagno and sergiocabraljr have found various solutions for GB builds I think and I know Samsung seems to have solved the problem. (I've seen videos of the Galaxy Nexus and it worked with no problems on an SII a friend of mine has).
Could it simply be a case of isolating and extracting the magic HID file and putting it into any/all custom roms, or it's a case (for some just to make it harder reason) that the BT files have to be recompiled for each and every build; as GregórioAxiaMagno has kindly pointed out with some of his work.
The holy grail I suppose is a set of files that can be uploaded to any build by apt, that resolve the lack of BT keyboard with every/any build.
Click to expand...
Click to collapse
:good:
The point here is, as always I say, the bluetooth stack on Android is a issue like call recording. And with this cenario, I think we can join people to help on this thread to post information about mods, replacements, hacking, apps and more. Until we find the optimal solution for the largest number of phones what we can. :fingers-crossed:
All is valid: kernels, modules, CWM, apps, tips, :angel: pray... any way of help.
I will ask for you people to post solutions here, and along of the time I will quote it in the second post of this thread.
Also, I want discuss with you about an optimal solution.
So keep this thread clean and focused only about bluetooth.
No, I and nobody thinks what the bluetooth is the world conquest, I want only use the totally potential of this "old" tecnology.
I know we have other tecnologies like OTG, but this thread must be only about how to deal with bluetooth in our daily use and experiences.
Lets start! :highfive: I have your help?
Please, press thanks instead to manifest your support with posts.

Current solutions
[app][beta][2.1+] myblucon v1.0 & mybluime v1.0 - bluetooth kit to hid devices
so you buy a bluetooth mouse but your ginger won't connect it?
Or you have an bluetooth keyboard and can't write at your ice cream?
Solution for:
* ST15a/i - GB/ICS
* Others
Click to expand...
Click to collapse
Bluetooth Keyboard problem resolved
Infamous "paired but not connected."
Solution for:
* Galaxy Note GT-N7000
Click to expand...
Click to collapse
[APP]Bluetooth Keyboard Easy Connect
A service which connects your bluetooth keyboard device.
Android 2.3 has support for HID devices but is not able to connect bluetooth keyboard devices correctly (yet).
This service automates the connection to your keyboard.
Solution for:
* Many Androids
Click to expand...
Click to collapse
Solving Bluetooth connecting problems
My Desire's bluetooth allways worked like a charme untill rooting REDUX 1,2
Connecting to any previously known device, or any new once for that matter, did not work.
Some grey hairs, upgrading to Redux 2.0 and many tries later I concluded some data must be corrupted somewhere.
Deleting the content, not the files, just the content of the following files did the trick, much to my relief.
Solution for:
* HTC - Redux
Click to expand...
Click to collapse
HID Bluetooth Device FIX for 2.3.5 and 2.3.6!!
Like many of you I was extremely excited to learn that android now supports HID devices and immediately rushed out to purchase a HID-BT Keyboard. Getting home, I fired up the phone and keyboard, entered the 6 digit code to pair them and saw the device connecting and disconnecting in an infinite loop. I was crushed and disappointed.
What went wrong? As stated above this is merely a workaround. But the problem lies somewhere between the kernel and broadcom chipset. This fix will reset your bluetooth pairings. It has been tested on my Samsung Galaxy SII I727 but it should work with any other device.
Solution for:
* Many Androids
Click to expand...
Click to collapse

resv 2

:good::good::good:

Congratz... keep going

Looking here:
/data/misc/bluetoothd/<A BLUETOOTH ADDRES>
I was thinking one of this files have a value to set for make an device manually connectable. Like disabling/enabling auto connect. So the market apps to HID devies will work better.
What do you think?

I was messing into the system and looking at this path
system\etc\bluetooth
Inside, we can found some confs, so I was editing and guessing about input.conf.
So I made some mods and I will test today, but if anyone know something more about or want to test, please a hand will be cool xP.
Regards.
EDIT: yeah nothing changes... haha

[Q] Have you used any Bluetooth 4.0 (aka Bluetooth Smart) supported devices?

Specifically for the HTC One S, i'm curious how our phones work with it. If you have, please let me know if you are using stock, CM, or any other ROMs. I'm looking to get maybe the pebble (not out yet) or fitbit. Thanks!

I'd like to know this too. Are there any ROMs out yet that enable Bluetooth 4.0 one the HTC One S?

It works from 4.0.3 version with open broadcom ble api which was here recently http_s://code.google.com/p/broadcom-ble but now it's deleted.
It needs a little patch to the library (does not work without). I have done some little tests last year but then put it out.
New rewritten api is here http_s://code.google.com/r/naranjomanuel-opensource-broadcom-ble/ but not tested.
Now I'm making an app to test things. I can connect to TI Keyfob with Keyfob demo firmware and read battery level and tx level and even get notifications when level changes. Have to add some quirks to make it work
And there is a proprietary HTC BLE SDK which you get after NDA. Not sure if it support this phone, but it's based on broadcom api.
As of 4.1.1 version phone can "see" discoverable ble devices in bluetooth settings, but can't do anything from there.
I'm actually looking for other phones with ble supported, chinese maybe. But I guess we should wait for 4.3 to spread around.

MaximusHD. But i dunno really if this works, since i can barely see any difference at all when i was on sense 4+/4.1.1 when it comes to speed on sharing files via bluetooth..

i am on Magio ROM 1.0.4. i want to pair my Heart Rate Monitor. I can see the device, but when i want to pair it, the message is, that the PIN is wrong. Shame...

Does Bluetooth 4.0 depend on the Android version (4.3 or higher) or on the kernel version? From Linux I know that drivers can be included in ther kernel or as separate modules.
Is there any custom ROM with 4.3+ AND Sense?
Edit: My co-worker has CM 11 installed and his Runtastic BT 4.0 HRM belt works fine.

anyone know that fitbit work and sync with one s (maximus hd rom)?

[Q] Google Wallet Tap and Pay?

Does tap and pay work for this phone with CM11? Is there anything special I need to do to make it work?
I've installed google wallet successfully, enabled tap and pay in settings, but I've tried tapping at several stores and nothing seems to happen, both from the lock screen and after unlocking and opening the wallet app (not sure if that's necessary, but tried it anyway).
I did some searches and read stuff about hacked versions of google wallet and other workarounds (like forum.xda-developers.com/showthread.php?t=2280943 ) but it seems these apply to older android versions only.

I don't think Google Wallet was ever officially supported on the Q. Like you said, some people hacked it up and I think a few made it work... but not many. Doesn't seem to be worth the effort.

arrrghhh said:
I don't think Google Wallet was ever officially supported on the Q. Like you said, some people hacked it up and I think a few made it work... but not many. Doesn't seem to be worth the effort.
Click to expand...
Click to collapse
Someone with a similar username to you is one of the few that made it work last year (from that other thread):
Aaargh! said:
I made an in store purchase today and it worked perfect. Pretty cool technology
Click to expand...
Click to collapse
However that thread seems to be for CM10.1/Jellybean not CM11/Kitkat so was hoping for something more recent before I start just trying things I don't fully understand.

After much more reading and questiong etc I think I figured this out and thought I'd post the details incase anyone else is interested:
#1 - Google stopped supporting tap&pay for anything earlier than KitKat summer 2014. So the older versions/hacks won't work anymore even if running older android version, etc.
#2 - There are several NFC chips, our phone uses NXP PN544 - same as Droid Razr any many other brands. There are no open source drivers for this chip, so AOSP, which CM is based on, doesn't have these drivers. Other NFC chips, like Broadcom BCM20793, do have open source drivers and they are included in AOSP, so phones with those do work for tap & pay with CM11. It also seems there is a newer NXP chip in some new phones, PN547, which may possibly work with recent AOSP 4.4.3 but I didn't keep reading about those details.
#3 - People have been trying to get NXP to release open source drivers for PN544 to AOSP, as well as trying to reverse engineer closed-source drivers from factory roms that support it natively, as well as looking at possible compatibility with PN547 drivers, but no success in any case yet. The following thread tracks that effort: http://forum.xda-developers.com/showthread.php?t=2573842
Conclusion - No way to make it work with our phone at this time. Perhaps in the future if NXP releases open source drivers or someone brilliant hacks something out.