So I am making a project for my android class at school.
The project is about helping handicaped people communicating with a nurse if they can't speak. The solution I've come up with is an app where 24 pictures is combined with 24 sound files which the user then can use to communicate. For example, by taking a picture with a helper and then the nurse records the word on a tablet then when next time the user needs to get an apple he/she just presses the apple on the app and it says apple.
What would optimize this app would be that instead of each user of the app having a tablet, the nurse only has one. Then when entering the house of a user he/she can by scanning a NFC chip, get the pictures and sound files into the app belonging to that person.
So here's the question. Can this be done by combining a NFC chip with some sort of SD card solution or will this have to be done by the chip returning for example an URL with some sort of user parameter getting the pictures and soundfiles by using an internet connection?
So is there some storage thing you can put together with an nfc chip that could make this posible?
Related
My coursework requirement is to build an Android application that lists all available mobile devices within close proximity. None of the devices have access to the internet.
To make things easier, the assumption is that all devices have my application installed.
When user first installs my app, they must define a user name and upload a profile picture.
When they launch my app, it should display the following profile info about other devices nearby:
User Name Profile picture
Now, I know this is an open ended question, but I'm totally stumped and need some guidance.
Specifically, I find these points challenging:
How to establish communication between devices/my app without internet?
How to retrieve other devices' profile picture without having to store everything locally on the device
I did some research and found Wi-Fi Peer to Peer, but not sure if this will be suitable for my use case as I don't have internet access. Bluetooth is another option but I think devices would have to be paired first before exchanging data.
You can starting Wifi hotspot with name like "YourAppName".
And create simple brodcasting this data inside this network.
So:
user opens your app and registering;
your application, checks if there is WIFI "YourAppName".
if NO, your app start hot spot "YourAppName".
if YES, your app promt user to connect to this network.
If connection successfully established, you will need to think how to transmit the list of data to your app, and represent it to user
Hope that this steps will helps you! Good luck
I have a dual-sim Android phone and during the morning I use one of the SIM cards for the data connection, and during the evening I use the other one. It's a pita to manually switch from one card to the other twice every day, so I thought I could create a simple app that does the switching at a given time.
I've been reading and looks like starting at version 5.1 of Android's API, theres a SubscriptionManager class which offers info about current subscriptions (data, voice, sms, etc), but as far as I've seen there're a lot of get methods but no setters anywhere.
Does the Android API offer a way of setting the SIM card used in the data connection? I guess it does, because otherwise it wouldn't be possible to change it from the settings panel.
We are developing an android application where user can swipe his/her magnetic card.
We need to parse the information, however there will be two scenarios to capture and handle the card input (we have connected the USB magnetic card reader):
When focus is on Credit Card# textbox and user swipes his/her card we need to parse the information, need to show the card number only in the current focus field and Card Holder Name in another textbox/label.
If our application is running or even if it is not running and user swipes his/her card, we need to capture this information take the user to a particular activity in our application and need to pre-populate the captured information.
Please let us know how to do this in both scenarios.
The MSR100 is a fairly cheap USB HID device. You can get more information, including some setup info here:
http://www.posunitech.com/products_detail/&productId=73.html
I'm fairly certain you can use it like a standard keyboard on android by using a USB OTG cable. Not all devices can use it, but it will essentially let you use many USB devices on Android. With it, you can put your cursor in an EditText field and swipe to get the raw swipe data. From there you could write a listener on the EditText field to pull back the stripe, parse it, and put the data where you want.
If you want better security and less liability, I would go with an encrypted swiper that has EMV/Smart Card capability. IDTech has their UniPay models that do these and are compatible with PC, iOS, & Android.
http://www.idtechproducts.com/products/mobile-readers/176.html
I have been reading information on NFC but could not find exact process or sequence of steps that happens when an NFC mobile phone comes in contact with an NFC tag?
In more detail i got to know how the antenna, coil etc generate the magnetic field and how data is transferred, but i want to know
whether any handshaking happens in the first stage?
Or What data is transferred between 2 NFC enabled phones before the actual sharing of a photo or any information happens.
Thanks in advance.
For explanation purposes, lets say the actual hardware communication of magnetic field generation, etc. etc. is the hardware layer of communication.
On the android OS layer, there is something called NfcManager ( a service ) that runs in the background when you enable "Nfc" settings. This service is responsible for converting the raw byte data that is received from the below layers, which could be the kernel or the hardware layer, depending on how you look at it.
Once the service picks it up, this link should give you a basic idea as to how it is pushed into the application!
As far as 2 NFC phones go, this is not an extremely informed opinion, but im guessing from sheer experience. In the case of a data that needs to be sent below a certain quantity, there is no "pairing" that happens. It identifies the other 2nd NFC device and simply sends out data. In the case of photos or anything larger, i would assume it pairs it using Bluetooth and sends out the data.
I'm building a Kiosk, using a MacMini and an Elotouch display. It would load a CoreAnimation based App. that plays multimedia content following user touch-based choices.
I'm in a early stage of the project. I can change the architecture/technology if needed.
I need that my Kiosk could also distribute mp3 content to Smartphones close to it, wirelessly.
For now I would like to support iOS and Android phones. I don't have any control on the smartphone side. The Kiosk is coin-operated (with time based session expiration) and connected to the web through a wifi network, managed by me.
Can you tell me a common, safe and simple way to accomplish this?
I thought to WebDav but I would like to explore alternatives, the simpler for the user-side the better.
If you have one-time/session-based URLs, displaying a QR code on your kiosk screen would be one way to get the download URL to the device (and invalidated after successful download/session expiration); this would require a QR code reader which neither iOS nor Android have built in, though, but many users have one.
Additionally, display the same URL that's encoded in the QR code using URL shortener service like bit.ly, goo.gl, etc. for the user to type in.
This way there's no set up for the user, no funny business with pushing data to the user (privacy/security concerns) and every smartphone does have a web browser.
The best way to accomplish this is by using OBEX Push and bluetooth.
There are plenty of command-line tools to list all bluetooth devices nearby, and to do a file transfer to one of them.
The user would just need to activate bluetooth discovery on his cell phone, search for the phone on the kiosk, and select his phone.
Another alternative is mail. WebDAV is a bad idea, because the user will have to type in the address (cumbersome!).
A lot of photo kiosks are already using OBEX Push to receive photos from phones.
The easiest is to provide different types of usb cables: micro-usb, mini-usb... Almost all cell phones can be attached as a USB disk nowadays.
Summary:
* OBEX Push
* USB connect
* Mail