[APP] BT Tag Writer - Samsung Galaxy Nexus

BT Tag Writer is application that offers you way to add NFC pairing to your old Bluetooth speakers. NFC pairing allows you to pair, connect and disconnect the device just by tapping the NFC tag with your phone. This application is still under development and this thread can be used to request changes and new features for this application.
Market: https://market.android.com/details?id=fi.siika.bttagwriter
Video: http://www.youtube.com/watch?v=IbuLGsXIvKI
--- original first post ---
Hello everybody.
I have been now writing application for Android devices with NFC capabilities. It basically offers wizard interface for writing new NFC connectivity tags for your Bluetooth speaker(s)/headset(s)/etc. And software that will take care of the actual pairing/connecting, when you tap the tag with your phone. NFC pairing is something Nokia does with N9 and it's Bluetooth speakers, but it looks like Android still doesn't handle this well out-of-the-box. Also I still haven't found easy to use connectivity tag writers for any devices.
Sort demo of application in it's current state: Check youtube video kzoG5VM6VcU (can't have this as a proper link, as I only have less than 8 posts to this forum, sorry)
Before I release this software to market, I would like have some people testing it with their speakers and devices. I really hate alpha level software in market. If you have Galaxy Nexus, some sort of Bluetooth speaker(s)/headset(s) and hopefully some writable NFC tags, and you would like to help me to get this software tested: Please tell it here. I still have some small things to resolve before this is ready for closed testing. If you like to help me to get this tested please also tell what sort of Bluetooth device you have and what NFC tags you have available.
I will most likely release this software as free (gratis) and probably in open source (don't know the license yet). So I am not planning stealing your time and then making money out of it. Only thing I can offer to you is to add your name to application's thanks list.
Also if you know software that already does all this, please tell. If my software does not bring anything new, I have to redesign it little bit.
Thanks.

I'd like to test your app.
Got the same NFC-Chip like you (mi(d)fire or something like that I've bought for my old Nexus S) and a Nokia BH-504 Bluetooth Headset and for sure a Galaxy Nexus and a Galaxy S, too
Just tell me how I can help testing...

i would test as well buddy!

s60mike said:
I'd like to test your app.
Got the same NFC-Chip like you (mi(d)fire or something like that I've bought for my old Nexus S) and a Nokia BH-504 Bluetooth Headset and for sure a Galaxy Nexus and a Galaxy S, too
Just tell me how I can help testing...
Click to expand...
Click to collapse
For now this is ICS software, do you happen to have some unofficial 4.0 image in those? I kinda would like to make this 4.0 only software, as all NFC devices most likely will get that update.
S suxeN said:
i would test as well buddy!
Click to expand...
Click to collapse
Your phone is Nexus S? What sort of Bluetooth devices you have, and NFC tags...

I'd love to test this. I've been using NFC Task Launcher to do something similar but it doesn't currently support connecting to a specific device. I'm running ICS on a GSM Galaxy Nexus and have several A2DP speakers I could test with.

Northernmost said:
I'd love to test this. I've been using NFC Task Launcher to do something similar but it doesn't currently support connecting to a specific device. I'm running ICS on a GSM Galaxy Nexus and have several A2DP speakers I could test with.
Click to expand...
Click to collapse
I will fix few annoying things and then will put link to debug apk-file here (maybe Wednesday). I will try to see if I can make it run in 2.3.5+ too. Anyhow software will be limited to Mifare Ultralight tags (original and C versions). I have to buy other type tags to see what I can do with those, but that's later. Common Ndef writer classes does not work at all with Android or then I'm doing something wrong.
Android also really limits clean ways to do intents for more complex tags. So these tags software now writes are not proper connectivity handover tags. Just the core part of those is used and stored as single NDEF mime item and then this app is marked to handle those NDEF messages/records. Positive side with that is of course that information fits to smaller tags. Also PIN code storing will be probably done little hacky way to the first version.

alump said:
For now this is ICS software, do you happen to have some unofficial 4.0 image in those? I kinda would like to make this 4.0 only software, as all NFC devices most likely will get that update.
Your phone is Nexus S? What sort of Bluetooth devices you have, and NFC tags...
Click to expand...
Click to collapse
Like said above. Both devices got ICS and NFC and I've got Midfire NFC Tags...

s60mike said:
Like said above. Both devices got ICS and NFC and I've got Midfire NFC Tags...
Click to expand...
Click to collapse
So many different Mifare tags out there. Mifare Classics will not work (for now).
Anyway, pushed software to market after all. In few hours you should be able to find it from there. Offer still stays, if you can try it out and report issues here it would help. I had to drop headset support for now as it didn't work as well as I hoped.

Great! Will try it out today. Here's the market link https://market.android.com/details?id=fi.siika.bttagwriter
Sent from my Galaxy Nexus using Tapatalk

alump said:
Mifare Classics will not work (for now).
Click to expand...
Click to collapse
Missed that bit. I really must learn to read All the Mifare tags I have are Classic ones.
A couple of initial thoughts after myfirst use of the app...
1) Back when I was on 2.3.7 there was a Bluetooth A2DP widget I used (can't remember the exact name now) that, when you created the widget, would display a list of already paired devices that supported the A2DP profile. Once you'd picked one the widget would attempt to connect to it automatically.
I'd like to see your app do something similar rather than having to go through a pairing process with a device I've already paired with. It's a small thing to do I know, but I'd imagine most users will have already paired with their speakers before ever finding your app. I don't know if you can enumerate paired devices supporting the A2DP profile in ICS though.
2) When your app was scanning for BT devices it would find my speakers but would only display the BT address. It didn't display the BT device name after waiting for several seconds. This may be a BT stack problem though.
3) It looks very nice!

Northernmost said:
Missed that bit. I really must learn to read All the Mifare tags I have are Classic ones.
A couple of initial thoughts after myfirst use of the app...
1) ....I'd like to see your app do something similar rather than having to go through a pairing process with a device I've already paired with...
2) When your app was scanning for BT devices it would find my speakers but would only display the BT address. It didn't display the BT device name after waiting for several seconds. This may be a BT stack problem though.
Click to expand...
Click to collapse
1. Yes my app does not trust the already known devices list. Have to see if I can get that too. Anyway my application does not pair devices that have been paired already. It simply is stupid to not offer those. I have to check if I can used paired devices list too. I have to add some indicator to list what devices are then old known and what are just found with discovery.
2. I have seen "no name" issue only once. But yes, that's "stack problem"... I hope
Anyway I think I have to try to add Mifare Classic support first.

alump said:
1. Yes my app does not trust the already known devices list. Have to see if I can get that too. Anyway my application does not pair devices that have been paired already. It simply is stupid to not offer those. I have to check if I can used paired devices list too. I have to add some indicator to list what devices are then old known and what are just found with discovery.
Click to expand...
Click to collapse
Sorry for spam, but finally this will be mine 8th post
Request to list already paired devices is now added to Market version (0.3). So no need to turn already paired devices to pairing mode when writing tags.
Support for other than ultralight Mifare tags might take some time. Thanks to keys etc those tags are not ideal for this use. I think I will try to add headset support first.

Just to confirm that 0.3 is listing my paired A2DP devices

alump said:
Your phone is Nexus S? What sort of Bluetooth devices you have, and NFC tags...
Click to expand...
Click to collapse
Nexus S, running Brainmasters ICS 4.0.3
Bluetooth devices:
2 headsets
another Xperia ArcS
NFC Tag:
dont have a tag yet, but could get some. Dunno what kind they are!

S suxeN said:
NFC Tag:
dont have a tag yet, but could get some. Dunno what kind they are!
Click to expand...
Click to collapse
My unofficial NFC tag type list (from memory, might have mistakes)
Mifare Ultralight C is my recommendation. If you plan to use this for this, or for example: storing your contact information, storing some url, storing application starter information etc.... Simple, cheap and easy to use alternative.
Mifare Ultralight (non C) is too small for almost anything. You can use it anyhow with my software (limited features) and you can fit sort URL to it.
Mifare 1K, Classic, etc... these are for more secure needs. Or if you really want to store a lot more information to the tag. For non secure usage (e.g. my app) the secure features are just annoying extra that makes things more complex. Key based security so if you mess up with key, then you can't read or replace that data anymore. Also kinda "proprietary alternative".
Felicas are Sony's alternative for all these. Probably not easy to find outside Japan. Topaz is good alternative for Ultralights, but I don't know how well Android supports those currently (haven't tested). And if Broascom/Innovision still makes these? Not too easy to find anyway. And then there are many more... it's a total mess and maybe the main reason why it's so hard for NFC to break big time.
But for the most of use cases: I assume Mifare Ultralight C is the best alternative.
NFC Tag store examples:
TagAge - I'm using this, but mainly because I live in Finland.
NFCDog - is one UK alternative.
And many more, Google search is your friend. And this message has't been paid by either of these stores

alump said:
My unofficial NFC tag type list (from memory, might have mistakes)
Mifare Ultralight C is my recommendation. If you plan to use this for this, or for example: storing your contact information, storing some url, storing application starter information etc.... Simple, cheap and easy to use alternative.
Mifare Ultralight (non C) is too small for almost anything. You can use it anyhow with my software (limited features) and you can fit sort URL to it.
Mifare 1K, Classic, etc... these are for more secure needs. Or if you really want to store a lot more information to the tag. For non secure usage (e.g. my app) the secure features are just annoying extra that makes things more complex. Key based security so if you mess up with key, then you can't read or replace that data anymore. Also kinda "proprietary alternative".
Felicas are Sony's alternative for all these. Probably not easy to find outside Japan. Topaz is good alternative for Ultralights, but I don't know how well Android supports those currently (haven't tested). And if Broascom/Innovision still makes these? Not too easy to find anyway. And then there are many more... it's a total mess and maybe the main reason why it's so hard for NFC to break big time.
But for the most of use cases: I assume Mifare Ultralight C is the best alternative.
NFC Tag store examples:
TagAge - I'm using this, but mainly because I live in Finland.
NFCDog - is one UK alternative.
And many more, Google search is your friend. And this message has't been paid by either of these stores
Click to expand...
Click to collapse
Okay, ima gonna order some and report back to u

music auto start
is there a way to make it so that my music app doesn't auto play my most recently played track when the BT connection is made ... id like for it to simply open the app

Related

[APP] 6/12 NFC Task Launcher 3.6.1

I am consolidating threads. Maintaining several threads was getting to be too much. Please move to the new thread here with any new questions or comments: http://forum.xda-developers.com/showthread.php?p=34417369
Market Link: https://market.android.com/details?id=com.jwsoft.nfcactionlauncher
Application Site: http://www.jwksoftware.com/
Screenshots: http://www.jwksoftware.com/screenshots
Where to get Tags?
http://www.jwksoftware.com/nfc-tags
Features:
NFC Task Launcher uses the NFC Hardware and RFID/NFC Tags to allow you to create tags several types of tags, including a custom "Task" tag that will automatically execute tasks when read. See Site for full feature list.
If you do use and enjoy the app it is up in the Market as a paid app. Any purchases / ratings are appreciated as I have put quite a few hours into this expanding it to fill requests for functionality.
Change log:
6/12 Version 3.6
- GPS (Root needed)
- Mobile Data (Root needed)
- Display Timeout
- Fixed Airplane mode bugs
- Precision timer
- New languages
- Cloud backup and restore
5/9 Version 3.4
- UI updates
- Added German, Spanish and Korean
- Removed Italian as it is out of date
- All tags now save to "Your Tags". Recent shows the 5 most recently used
- Changed Tag limiting to uniquely track switch tags
4/19 Version 3.3
3.3
- Added Google Places support in Latitude
- Added Navigate to address support
- Added Auto-rotation
- Added write lock option when writing
- Added size to vCards
- Added setting to pause after launching an app (for launching multiple apps or launching and then interacting)
- Added notification when tags save when hitting finish
- Updated Tasker integration (should fix issues with HTC One X)
- Enhanced debugging to make bug reports easier
- Fixed condition where tasks would stop executing when wifi changed
- Fixed reported crashes and typo
Full: http://www.jwksoftware.com/change-log
If you'd like to see some functionality added feel free to make a request.
The APK linked below is free of the license check of the Market version and is fully functional for 7 days.
http://goo.gl/xBBOU
For anyone who decides to purchase the app after using the APK attached to the thread - un-install the free version first otherwise the market installation may fail.
Here's a few videos I made for a current demo:
Tag Demos
Car Dock Demo
Awesome. I'm gonna have to research this. Off topic but how much do those tags cost?
My mind is racing with ideas.... oh no
player911 said:
Awesome. I'm gonna have to research this. Off topic but how much do those tags cost?
My mind is racing with ideas.... oh no
Click to expand...
Click to collapse
They are pretty reasonable. If you check out the site I compiled a list of shops that I've tested. Usually $1.15 - 1.50 a piece for Ultralight C or Classic 1K tags.
Question for you guys with the nfc tags what have you done with them I like the idea of swiping my phone over a credit card scanner but what can be created with your own tags
Sent from my SCH-I510 using xda premium
Can't wait to try this. Already ordered the starter pack from tagstand. Looks like an amazing app. Will definitely buy as soon as I get my phone = ]. Thanks for the hard work.
@krohnjw
Can these tags be pre-defined and written into the software?
Was just thinking, you could be onto a winner here.
Set your program to know whats tags are, so say put a tag for a store. When someone scans it with your app, it auto checks them in at whatever app they have installed
Evostance said:
@krohnjw
Can these tags be pre-defined and written into the software?
Was just thinking, you could be onto a winner here.
Set your program to know whats tags are, so say put a tag for a store. When someone scans it with your app, it auto checks them in at whatever app they have installed
Click to expand...
Click to collapse
The instruction set is encoded on the tag. Any user with the app that scans the tag will see the same actions performed. It makes no calls back to any server or outside service.
Sent from my Nexus S using xda premium
Ah ok, makes sense. How do you code the tag though?
Sent from my iPad 2 using Tapatalk
Evostance said:
Ah ok, makes sense. How do you code the tag though?
Sent from my iPad 2 using Tapatalk
Click to expand...
Click to collapse
It's fairly simple. I designed a basic syntax describing the actions to be taken and wrote a complementary parser for when the tags are read.
That's simply amazing. I knew the NFC would be a nice toy, but not that nice!
Does anyone know where to get some cheap tags in germany. Cheapest I found so far was ebay, but still around 2,50 EUR per tag (incl. shipping).
Atreus said:
That's simply amazing. I knew the NFC would be a nice toy, but not that nice!
Does anyone know where to get some cheap tags in germany. Cheapest I found so far was ebay, but still around 2,50 EUR per tag (incl. shipping).
Click to expand...
Click to collapse
Did you check http://www.tagage.net/tagage-shop/ ?
I purchased these nfc tags which the seller has confirmed that they are in working order and bought the application. However, the app says that the nfc type is not supported. What's up with that?
drdino said:
I purchased these nfc tags which the seller has confirmed that they are in working order and bought the application. However, the app says that the nfc type is not supported. What's up with that?
Click to expand...
Click to collapse
See the edited first post. Something in 4.0 changed and Mifare Ultralight, Ultralight C and Classic 1K tags are no longer reporting as NdefFormatable - so the functionality to format them TO NDEF is broken.
Essentially the NdefFormatable class verifies that the tag lists the tech before it will operate on them. As they no longer list that tech it refuses to do anything with them.
This affects all NFC Apps I've tried in the Market so far. If the tags are already formatted NDEF then they work without issue.
I've got a bug report open to see if I can get a response on this as well as a post on the dev group as it's not a listed change in the API changes anywhere from 3.0 up.
If you don't want to wait it out and want a refund let me know and I'll process it.
Its allright, seems like a decent app so I still want to explore the possibilities.
drdino said:
Its allright, seems like a decent app so I still want to explore the possibilities.
Click to expand...
Click to collapse
There are shops that sell the tags pre formatted with NDEF - those will work. Anything that comes blank though currently will not.
As a curiosity I sent an email to NXP as well to see if they have any more information. I'd like to get this sorted sooner rather than later so hang in there
Can this app be set to do something when moved away from an NFC tag?
So say you put it in car dock and a tag turns on BT. But when removed its turns off BT
Sent from my Galaxy Nexus using Tapatalk
Evostance said:
Can this app be set to do something when moved away from an NFC tag?
So say you put it in car dock and a tag turns on BT. But when removed its turns off BT
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
No, there's no intent raised when the tag is moved out of range, only when it is detected.
It is reported in the logcat, but to do that you'd need to constantly be reading the logs and scanning for that (which would involve a read logs permission).
For all Europeans: I contacted tagage and their tags are not pre-formatted by default, but if you send them an email, they'll format your tags first.
Atreus said:
For all Europeans: I contacted tagage and their tags are not pre-formatted by default, but if you send them an email, they'll format your tags first.
Click to expand...
Click to collapse
Most vendors don't pre-format their tags - so get in touch with them before/when your order for now to be sure.
Hopefully this is something that I can get an answer on, but I don't currently see a good workaround.
krohnjw said:
No, there's no intent raised when the tag is moved out of range, only when it is detected.
It is reported in the logcat, but to do that you'd need to constantly be reading the logs and scanning for that (which would involve a read logs permission).
Click to expand...
Click to collapse
Can you put implement it as an option on each tag? That way we could enable it for a car tag only and not another tag etc.
If that makes sense?
Sent from my Galaxy Nexus using Tapatalk

Any NFC apps on here at all?

I know Google Wallet isn't on here yet but aren't there supposed to be some basic NFC apps to read tags? Am I confused?
Sent from my Galaxy Nexus using xda premium
There are some.
This one has been used by people on the Nexus S, and is the official app for NXP semi, who make heaps of NFC tags.
Unfortunately, that app (as well as several others) refuse to write tags with my Galaxy Nexus. They can read them fine, but they can't write them.
I think we just need to wait for software devs to add support for the galaxy nexus.
Niksko said:
There are some.
This one has been used by people on the Nexus S, and is the official app for NXP semi, who make heaps of NFC tags.
Unfortunately, that app (as well as several others) refuse to write tags with my Galaxy Nexus. They can read them fine, but they can't write them.
I think we just need to wait for software devs to add support for the galaxy nexus.
Click to expand...
Click to collapse
Have you tried using NFC Task Launcher? It works on the Nexus S running ICS so you might give it a try if you haven't already.
Sent from my Nexus S using xda premium
Niksko said:
Unfortunately, that app (as well as several others) refuse to write tags with my Galaxy Nexus. They can read them fine, but they can't write them.
I think we just need to wait for software devs to add support for the galaxy nexus.
Click to expand...
Click to collapse
It's a bit more than that. Right now the class utilized to format tags to NDEF that aren't previously NDEF (read ANY blank tag you receive) can't be used with ICS.
This is because these tags no longer report the tech NdefFormatable. Without this tech reporting the class refuses to operate on them (returns a null object when you try to get an instance on which to operate from the incoming tag) - rendering all current apps unable to format them to NDEF.
There's NO notes on this in any API changes (3.0, 3.1, 3.2, 4.0) and no other API able to be used to accomplish this task that I can find. It's not yet known if this is an intentional change or not. I've got an issue raised in the issue tracker to try to get some more information.
If you purchase pre-formated tags they work fine as they are already formatted for NDEF. Tags that are truly "blank" are dead in the water right now on ICS.
Wait GoogleWallet doesn't work on the GN?
krohnjw said:
It's a bit more than that. Right now the class utilized to format tags to NDEF that aren't previously NDEF (read ANY blank tag you receive) can't be used with ICS.
This is because these tags no longer report the tech NdefFormatable. Without this tech reporting the class refuses to operate on them (returns a null object when you try to get an instance on which to operate from the incoming tag) - rendering all current apps unable to format them to NDEF.
There's NO notes on this in any API changes (3.0, 3.1, 3.2, 4.0) and no other API able to be used to accomplish this task that I can find. It's not yet known if this is an intentional change or not. I've got an issue raised in the issue tracker to try to get some more information.
If you purchase pre-formated tags they work fine as they are already formatted for NDEF. Tags that are truly "blank" are dead in the water right now on ICS.
Click to expand...
Click to collapse
This is really interesting information. This is what I'm experiencing, as my tags were previously blank.
Thanks for the info, and hopefully somebody makes an API that will allow us to write to these uninitialized tags.
Niksko said:
This is really interesting information. This is what I'm experiencing, as my tags were previously blank.
Thanks for the info, and hopefully somebody makes an API that will allow us to write to these uninitialized tags.
Click to expand...
Click to collapse
I spent the last hour or so trying to get around this to no avail. I can successfully "spoof" the tag tech by grabbing it via reflection and altering it at runtime so I can get an instance of the class - it throws an IO exception when connecting though So I'm still stuck there - I'll see if I can devise a work around this week. I am not super optimistic though.

Card Emulation in general

Hi there,
right now I am researching for a possibility to emulate a smartcard with a smartphone. As we all know, the standard os and api won't let us do this. What I want to achieve is create a way to use the smartphone for physical access without the need to change the existing infrastructure. o achieve that, the smart phones gets a localy and time limited informationtoken it should present to the reader. In other words, I actually dont realy need access to the secure element, as any data would be temporary.
Right now I am a bit confused about this. Is there a way to use card emulation, without the need of a secure element? I have searched for different ways to acchieve this, but on many ends, I can't seem to find a definitv answer.
For example I stumbled on OpenNFC. They praise that they can acchieve card emulation. Yet, they don't provide any examples on this and fail to actualy deliver some sort of information on the requirements of this. As I understand it, it seems like this method only works when the smartphone uses Inside Secures Chips MicroRead or SecuRead. Anyone knows more about this?
I'm realy open to ideas on this one, as it seems theres little to no documentation or examples to go on.
I'd realy be happy to read about what you guys found out on this issue as of yet.
I've been looking into it too. This is what I have found:
EddieLeeDefcon20.pdf
nfcproxy
(Google them, I can't post links)
So, yeah, it can be done, but you have to modify android to be able to.
I ended up to OpenNFC too, but no sample code!
I have a good background on Mifare Classic 1K and 4K programming using RFM130 under linux and win.
Sent from my HTC One X using Tapatalk 2
Ok, so after browsing the mailinglist like a maniac I found this answer from one of OpenNFCs developers:
Hello,
The OpenNFC stack porting on Android complies to the Google API, as far as the applications are concerned.
Since these API do not allow an APK to do card emulation, it is not possible to use this mode on the Nexus,
nor on any Android phone, with or without OpenNFC.
However, OpenNFC provides card emulation feature for other porting (Win32, linux), depending on the hardware capabilities.
Kind regards,
Stephane
Click to expand...
Click to collapse
Source is on their mailing list on sourceforge, cant post link....
So seems we can forget this one... Only option would be using the Cyanogenmod patch that is used by NFCProxy.
When this message has been posted? I think things has changed (not sure)
Anyway, I posted a message yesterday to have more informations about their projects on Android
The Message is from March 29th, 2012.
Again as I said, if that has changed, they really have to work on their communication to the outside. There seems to be noone but the devs that can say anything about this. And that means quite a lot.
When there is no API for something, we can use native code and directly communicate to NFC hardware. Agree?
Sent from my HTC One X using Tapatalk 2
Well, the way I understand it is, that we could take a build of android and tinker with it to get it to work. We would have to change the NFC softwarestack and its interaction with the rest of the system in order to make software emulation possible. That is quite some pile of nontrivial work to do if you ask me.
Sorry for doing a new reply instead of editing the old one, but I think this is interesting enoug to not get overread.
I got an answer from the OpenNFC Developerteam regarding my question. Part of my question was also if it was possible to emulate for example a Mifare Tag through their NFC Stack. Here is the answer:
Hello XXXXX,
The Open NFC stack is designed to be largely hardware-independent, with a small adaptation module (NAL) for each hardware chipset. However, currently we only provide the NAL module for the MicroRead / Securead chipsets; therefore out of the box we are only compatible with these chipsets.
It is possible to emulate ISO 14443-4A and -4B cards and Type 4 tags from the Open NFC stack; for emulation of MiFare Tag, you’d indeed need to use a Secure Element.
Best regards,
Sebastien.
Click to expand...
Click to collapse
Hope this clears some questions regarding OpenNFC.

Write NFC tags that do not require other users to have the app used to write the tag.

I have a done a bit of looking but all I've come up with is mainly 'use trigger' or something like it. But my question is: Is there a way with Trigger to write a tag that anyone can read? Or is there another NFC tag writer app that I should use?
The thing I want to do is make a tag for friends to tap when they call over that will connect them to my wifi network, but if they have to go and download trigger first then no one is going to use my tag.
Sorry if this is a re-posted question, I looked and didn't see it anywhere here and when I put the title in there was no recommended threads that had what I was asking.
I've tried different apps, and it looks like connect to wireless is not one of the default actions that is included in Android. I've only found connect to bluetooth.
Hi, you can use NFC Tools for that.
All records on "write" tab is compatible with other NFC device.
daniel_loft said:
I've tried different apps, and it looks like connect to wireless is not one of the default actions that is included in Android. I've only found connect to bluetooth.
Click to expand...
Click to collapse
I am new to NFC and I am a little confused about what NFC can do. I have the nfc-tool App and I can read many NFC tags that I have.
But for an Android phone with NFC support, without installing any 3rd party App, what can it do? Is NFC enabled by default? Are there native NFC apps that can trigger action, open URL, etc?
Also, since each NFC tag already has a unique identifier, it seems to me writing data to NFC tag isn't all that useful when only 1 phone is using it. As you could have just programmed the command to the phone. The same applies to multiple phones if you can program the phones through some other means. Am I missing something here?
As I was saying, looks like what you want is only possible in Android L.
Have a nice day!
nookin said:
I am new to NFC and I am a little confused about what NFC can do. I have the nfc-tool App and I can read many NFC tags that I have.
But for an Android phone with NFC support, without installing any 3rd party App, what can it do? Is NFC enabled by default? Are there native NFC apps that can trigger action, open URL, etc?
Click to expand...
Click to collapse
Android has native build-in support for some simple standard NFC activities, like reading a messages/contact, open URL/URI, launch application etc. .For more sophisticated activities you will always need an app to parse the tag content and handle the activities.
Also, since each NFC tag already has a unique identifier, it seems to me writing data to NFC tag isn't all that useful when only 1 phone is using it. As you could have just programmed the command to the phone. The same applies to multiple phones if you can program the phones through some other means. Am I missing something here?
Click to expand...
Click to collapse
yep, fully agree. Have a look at NFC ReTag
ascsa said:
Android has native build-in support for some simple standard NFC activities, like reading a messages/contact, open URL/URI, launch application etc.
Click to expand...
Click to collapse
I'm a newbie here. I have a phone running 4.2.2. How do I make it read an NFC tag and take action without installing additional app? Just tap?
So I finally found an official NFC tag in mall. When I place my phone on it, it asks me to choose between stock Browser and Chrome. I guess if I have already chosen a default, it will just open a webpage. Now I wonder if there are security concerns. What if the URL is malicious? What if it downloaded a lot of data when the user is roaming?
I wonder what other functions an NFC tag can trigger without installing additional Apps? If I buy writable NFC tags, like the Samsung TecTiles, can it be programmed just like the mall NFC tag?

USB Accelerometer on Joying radio

Hi,
Sorry, I had already posted this on another section but I think this one is more appropriate and can't delete other post.
I have a Joying JY-NL124 android car radio, which does not have an accelerometer. I bought the Yocto 3d V2 http://www.yoctopuce.com/EN/products/usb-position-sensors/yocto-3d-v2 to see if I could get it to work with torque and other android apps for the track but although android sees the device the apps do not. I am not a programmer, but is there a way to get the apps to recognize an external accelerometer like some do for an external GPS?
Very interesting. I would like to know as well. It might also be usefull in navigation to get a faster direction orientation.
I was reading up on this again and this bit means someone with the know how would probably need to code something
The main advantage of this solution is that you don't need to install a driver to communicate with a Yoctopuce module, as the HID layer is always present. You only need to add our library, that we provide in source form, to your driving software for it to be able to directly talk to Yoctopuce modules.
Click to expand...
Click to collapse
Have you tried contacting them directly and asking if they can do this for you?
sinnedone said:
I was reading up on this again and this bit means someone with the know how would probably need to code something
Have you tried contacting them directly and asking if they can do this for you?
Click to expand...
Click to collapse
Uff, sorry for the late reply. Life has a way of getting in the way of interesting projects. I'm about to restart this project since I'm using the car a lot on the track. It's weird that the units don't come witha compass, gyroscope, accelerometer, etc, considering they are meant to be used in moving vehicles.
Definitely post up if you figure it out.
It would be nice to get it to work with Android as a whole. If that's the case you might need to talk to one of the ROM developers to see if it's something they can do ROM wise or even a custom kernel.(the kernel bit might be a little harder)
Did anybody get this right. It would be cool if these usb accelerometer could work in the apps
flash_xx said:
Hi,
Sorry, I had already posted this on another section but I think this one is more appropriate and can't delete other post.
I have a Joying JY-NL124 android car radio, which does not have an accelerometer. I bought the Yocto 3d V2 http://www.yoctopuce.com/EN/products/usb-position-sensors/yocto-3d-v2 to see if I could get it to work with torque and other android apps for the track but although android sees the device the apps do not. I am not a programmer, but is there a way to get the apps to recognize an external accelerometer like some do for an external GPS?
Click to expand...
Click to collapse
I'm very interested to understand whether this is possible as I am thinking about a similar setup. You tried the three Bluetooth tips in the roll up thread?
https://forum.xda-developers.com/an...roll-joying-2gb-sofia-mtcb-mtcd-tips-t3555249
"Bluetooth Tethering & BT Settings", "Difficult to pair BT devices" and "Modified stock bluetooth app to allow connection to all devices"
Have you tried external GPS for higher refresh rates or is the Head Unit gps refresh good enough for the track?
Bob
MX5DrIver said:
I'm very interested to understand whether this is possible as I am thinking about a similar setup. You tried the three Bluetooth tips in the roll up thread?
https://forum.xda-developers.com/an...roll-joying-2gb-sofia-mtcb-mtcd-tips-t3555249
"Bluetooth Tethering & BT Settings", "Difficult to pair BT devices" and "Modified stock bluetooth app to allow connection to all devices"
Have you tried external GPS for higher refresh rates or is the Head Unit gps refresh good enough for the track?
Bob
Click to expand...
Click to collapse
Sorry....USB not Bluetooth... Also discouraging. I was hoping USB would be an alternative to BT for track add-ons...
I too have an Android head unit and do track days, and have the exact same interest as you. I use Harry's Lap Timer. I have the Pumpkin AE0273B head unit. It too lacks the compass and accelerometer. I too found this to be a very unfortunate omission.
I have developed apps actually so I do know Android program to some degree (although I am sortof a hack, not a pro). I have apps on the Play Store (since I can't post links just search Play Store for developer JimRoal). I saw the Yocto stuff. When I get some time I will look into this some more.
Any update on this? Would also like to add a compass / accelerometer to my joying.
Also interested. But on a newer 10.0 unit. Something I am going to look into.
nFiniti said:
Also interested. But on a newer 10.0 unit. Something I am going to look into.
Click to expand...
Click to collapse
Sad that over 4 years after I first posted this we still don't have a unit with these features. I finally gave up and bought an AIM Solo 2 DL.
I'm looking for a newer radio though, since mine is older than this thread
Still waiting as well.
Looking forward for solution, we have also WIMOTION sensors in the market with sample android apk but I'm not a developser so, put things together is hard for me !
I think the hard job is try to mock the sensors in Android AS IF external accelerometer was factory embeeded (allowing apps to recognize it)
Nothing new about this project / idea ???
?? dead ???
mariodantas said:
?? dead ???
Click to expand...
Click to collapse
Once you've figured out how to modify the kernel, you should be good to go!
Another option could be sensor to serial over USB, via a compatible adapter, write an app and there you go. Of course it won't be standard Android though.
Drivers are here
https://elixir.bootlin.com/linux/v4.14.133/source/drivers/iio/imu/st_lsm6dsx
The problem is adding them to kernel !
You dont need to add them to the kernel. You will need to implement an Android HAL that can read the values of these sensors. Its not a trivial task but also not very hard if you have access to the source code

Categories

Resources