Related
As I read the forum, I discover that :
- flash is not supported (but probably will be)
- UMS is not supported
I'm very disappointed and plan to buy later and/or another device.
The lack of UMS prevent me from using a smart sync software like Syncback SE. And the google search "mtp sync software" does not give much results.
Thanks for your comments.
Thank you for making another thread instead of using the other 10 threads discussing the same complaints.
fredjm31 said:
As I read the forum, I discover that :
- flash is not supported (but probably will be)
- UMS is not supported
I'm very disappointed and plan to buy later and/or another device.
The lack of UMS prevent me from using a smart sync software like Syncback SE. And the google search "mtp sync software" does not give much results.
Thanks for your comments.
Click to expand...
Click to collapse
Well the Gnex is the last android phone to get Flash so whats the point in you buying a future new phone? They wont be support, this one will be so it solves part of it for you.
Can someone explain this ums problem in simple terms please ? I transferred files from pc to gn quite happily yesterday via usb .....
MTP is seen in Windows Explorer because Windows Explorer has an extension to process this protocol and show the device "as is" if it was UMS. But in fact, it's not. So, given that most Windows Application use the standard Windows API (OpenFile and so on) to manage files, they won't see the files.
at least the gnex has a possibility of getting flash.. other future phones may not
They will. Other future OS versions will (not "may") not get a new version of Flash, but I doubt that Adobe will refuse to change 2 lines of code to make it compatible with Android 5.0, for instance.
JohnSteveDoe said:
but I doubt that Adobe will refuse to change 2 lines of code to make it compatible with Android 5.0, for instance.
Click to expand...
Click to collapse
They have already stated they wont.
They said they are stopping development on it. Doesn't mean they will stop supporting it.
Need to read between the lines. Adobe isn't just going to walk away from their biggest stronghold on the web. Flash is all but dead but Adobe knows it can't compete against HTML5, so why keep developing a product that you know has a short life?
They confirmed already that Flash Support will come for Android 4.0 (ICS) by end of this year. But this will be the last Android Version who gets it.
http://androidcommunity.com/adobe-says-flash-for-ics-will-be-last-supported-os-20111121/
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
Hello,
I am developing an App, which should provide some NFC functionality. This app will run on an Android device with Android 4.2, with an NFC-Reader attached via USB. (Link - ACR 1252U Usb NFC Reader) The NFC-Reader comes with an Android-Library, that gives me access to it. (Link - ACS Android library).
The goal is, that every Android User can hold his phone to this reader, and then gets a small file on his device. That is the functionality, that the app should do. Just send a little file to the smartphone.
The connection to the reader works fine. I also can use the libraries classes to provide some basic functionality like information whether an NFC Card is attached or not, or getting the Cards ATR.
But unfortunately thats about it...
For the desired functionality I need "P2P-mode" or "Card Emulation-Mode". But I could not find any example on how to do this with this library. Is this library even capable of these functionalities?
Has anybody ever used this library for something like this?
Is it somehow possible to use the Android-Builtin NFC-functions together with the USB Reader?
Has anybody any tips for me?
Thank you in advance.
Hi,
I'm in the same point as You, I'm too use Android 4.2, I'm to use ACR1252U, and I'm stuck at same functionality problem yesterday/friday
belfegore said:
Hi,
I'm in the same point as You, I'm too use Android 4.2, I'm to use ACR1252U, and I'm stuck at same functionality problem yesterday/friday
Click to expand...
Click to collapse
Well, if you find something out, please report it here. I will do the same!
I'm not sure exactly what you are are trying to do. But you could use and nfc tag to programmed to a url to download a file. When the tag is brought within range of the nfc enabled phone the tag will send the url activating a web browser and download the file.
H3xxEdit said:
I'm not sure exactly what you are are trying to do. But you could use and nfc tag to programmed to a url to download a file. When the tag is brought within range of the nfc enabled phone the tag will send the url activating a web browser and download the file.
Click to expand...
Click to collapse
I'm trying to read/write data to nfc tag-card. But I'm have a problem with implement sending any command to my nfc adapter - ACR1252. Found interesting project created by Guru of NFC in Android @skjolber github.com/skjolber/ndef-tools-for-android but tries of implement additional adapter outgrows me or I'm doing it wrong
H3xxEdit said:
I'm not sure exactly what you are are trying to do. But you could use and nfc tag to programmed to a url to download a file. When the tag is brought within range of the nfc enabled phone the tag will send the url activating a web browser and download the file.
Click to expand...
Click to collapse
Hi,
that is exactly what I have done so far. I put the reader in card-emulation mode, and stored a URL on it.
The browser of the phone than successfully opens, when approaching the (emulated) tag.
Do you know if there is a possibility, that the image-link (e.g. "https://www.google.de/images/branding/googlelogo/2x/googlelogo_color_272x92dp.png"), that is stored on the tag, gets opened in the image-viewer-app ("Gallery"), instead of the browser?
Maikell84 said:
Hi,
that is exactly what I have done so far. I put the reader in card-emulation mode, and stored a URL on it.
The browser of the phone than successfully opens, when approaching the (emulated) tag.
Do you know if there is a possibility, that the image-link that is stored on the tag, gets opened in the image-viewer-app ("Gallery"), instead of the browser?
Click to expand...
Click to collapse
I think you might have a conflict there, I have been only working with the tags for a few months, but your passing in a URL, the default handler will process that as a browser based request and thus open up in the browser. If you have an application, other than the browser that can open pictures from a URL you may be able to do that
I went around the problem:
- On the Tag I am storing a link to an HTML-Site.
- This HTML shows the picture, and prompts the user, if he wants to download that image (via JavaScript)
- If he confirms, the image is saved in his gallery, like I wanted.
Still the basic question remains:
Can I send this image to the user without the detour over the internet? Meaning just sending him the image via peer-to-peer?
Maikell84 said:
I went around the problem:
- On the Tag I am storing a link to an HTML-Site.
- This HTML shows the picture, and prompts the user, if he wants to download that image (via JavaScript)
- If he confirms, the image is saved in his gallery, like I wanted.
Still the basic question remains:
Can I send this image to the user without the detour over the internet? Meaning just sending him the image via peer-to-peer?
Click to expand...
Click to collapse
Unless you were to chain alot of PC's up over a long distance in which could be used they would be acting as hosting servers for the files, then no. Also, if you are asking if that NFC could potentially transmit the file to other phones without the use of a connection, then technically, yes it is possible, yet the plausibility of the idea sufficing is low. NFC has a very limited connection span, and in order to transmit files over a long distance using NFC would require that everyone would act as a hosting server, and that if a user would request for the file download, then the rest of the phones would act as the sender, sending chunks of the file.
Nice idea
Sent from my HUAWEI MT7-TL10 using XDA-Developers mobile app
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
Hello, can anyone tell me the file location of the smart tag of the Samsung Galaxy A52s 5G? Thank you
for your time.
You mean, the NFC module? Top half of the phone, about the height where the cameras are.
robogo1982 said:
You mean, the NFC module? Top half of the phone, about the height where the cameras are.
Click to expand...
Click to collapse
It is about the smart tag. I am looking for files and DB locations regarding the smart tag on the phone.
thomas_jonson said:
It is about the smart tag. I am looking for files and DB locations regarding the smart tag on the phone.
Click to expand...
Click to collapse
Do you mean that there is a RFID-tag inside the phone? Smart Tag is as I understand it commercial term used in marketing and has no precise technical definition.
gerhard_wa said:
Do you mean that there is a RFID-tag inside the phone? Smart Tag is as I understand it commercial term used in marketing and has no precise technical definition.
Click to expand...
Click to collapse
I am new to all the terms and learning. Maybe it is RFID that you are writing about here. But I should specify more. Recently I bought a Samsung phone and I got a smart thing and that is Samsung smart tag (Bluetooth device) for anti loss. This device works like airtag(for iPhone) device. So, my plan is to work with those DB files that smart tag stores on the android device using user activity through its own application. I tried to collect but I am not successful. I am confused about the location of the data, do I have to unlock the phone or have to root the phone? Could you please help me with that? Thank you.
Ok, I see you are talking about the Samsung Smart Things system. I suppose the things you are asking about will be covered in the manual for the respective hardware devices and in the Samsung Smart Things app.
gerhard_wa said:
Ok, I see you are talking about the Samsung Smart Things system. I suppose the things you are asking about will be covered in the manual for the respective hardware devices and in the Samsung Smart Things app.
Click to expand...
Click to collapse
No, on the manual, not such inormation about the installed app's file location.
thomas_jonson said:
No, on the manual, not such inormation about the installed app's file location.
Click to expand...
Click to collapse
Just to understand what you are doing, why do you need to know the inner works of the Smart Things app? What are you going to use the files for? If it is for backup purpose, all relevant database files and other configuration will be included in a Samsung Smart Switch backup. Perhaps someone else can help you!
gerhard_wa said:
Just to understand what you are doing, why do you need to know the inner works of the Smart Things app? What are you going to use the files for? If it is for backup purpose, all relevant database files and other configuration will be included in a Samsung Smart Switch backup. Perhaps someone else can help you!
Click to expand...
Click to collapse
It's about a project purpose.
robogo1982 said:
You mean, the NFC module? Top half of the phone, about the height where the cameras are.
Click to expand...
Click to collapse
Maybe it is RFID that you are writing about here. But I should specify more. Recently I bought a Samsung phone and I got a smart thing and that is Samsung smart tag (Bluetooth device) for anti loss. This device works like an air tag(for iPhone) device. So, my plan is to work with those DB files that the smart tag stores on the android device using user activity through its own application. I tried to collect but I am not successful. I am confused about the location of the data, do I have to unlock the phone or have to root the phone? Could you please help me with that? Thank you.