My NFC reader app (as well as several downloaded from Play) no longer detects credit cards on devices running Android 13 (Pixel 4a & Pixel 6a). No problems on devices running Android 12 (eg, Pixel 3a). My app recognizes ndef, isodep, mifare,nfc[abv].
On Android 13, only NDEF tags trigger discovery.
Is anyone else experiencing this?
Related
I'm trying to see why our DJI-enabled app isn't working correctly with the Mavic Air 2 on iOS or Android. Here I'm debugging with iOS but I've seen the same failures when briefly testing on our Android app.
When calling setMode:completion: on the single camera belonging to the Mavic Air 2, I consistently get "Current product does not support this feature.(code:-1013)"
isMediaDownloadModeSupported returns true for the camera, and yet I can't set the camera mode to media download mode at all (or any other mode).
I've found that setFlatMode:completion: seems to work ok to set photo and video modes as a sort of alternative, however this is only for photo/video modes, and won't help me with downloading media from the SD card. (right?)
Any help out there?
From my DJI Developer Support ticket for the same issue:
For the Mavic Air 2 drone, should use the setFlatMode to switch the photo, video mode, and use the enterPlayback, exitPlayback to enter/ exit the download mode.
Can i know is it possible to communicate with Beacon without having any Mobile app on device?
Thanks in advance
Both Android and iOS devices need some kind of app installed to interact with your beacons. Some phones have such apps pre-installed, but the options are limited. The two such apps with the widest distribution are:
Google Chrome App (Android/iOS)
Google's Chrome app will interact with beacons supporting Eddystone-URL (also known as physical web), which transmit a URL that can be displayed within Chrome when the app detects it.
This works on both Android and iOS devices with Chrome installed. For newer Android phones, this is a relatively high percentage of devices. For iOS, it is a very small percentage, as the app is not installed by default. This makes it of very limited use on iOS.
The other real drawback to relying on Chrome for beacon detection is the hoops users have to jump through to opt-in, and the way the beacon notifications are buried. Until users opt-in, they will see no notifications on beacon detections. Once they do, they will see a very generic notification "Physical web beacons are nearby", and only once the user taps on that are the specifics about the web page associated with the beacon transmitted URL displayed.
Passbook (iOS)
Apple's passbook app will bring up a passbook entry (usually used for tickets, coupons, etc.) associated with a set of iBeacon identifiers if the user comes within range of the beacon. In order to use this, however, the user must first download the passbook entry to his or her iPhone. Only once this is downloaded and opened will the app respond to associated beacons.
EDIT April 2020: For a time prior to December 2018 Google supported app-less notifications based on beacon detection using their Google Nearby product. This was discontinued in December 2018 due to predictable abuse and spam that it generated. While you may find some outdated documentation online about this ability, understand that this feature no longer works. As of this writing, my understanding is that this answer is still correct.
You should checkout Eddystones from Google. They can push you URLs even without app.
If you want to interact with beacons and do custom stuff (notifications, http requests, etc) you will need an app.
I am using eddystone beacons to transmit my business url. How can I make the url notification received to alert thru sound on the users device? Any idea?
Understand that Eddystone-URL beacon advertisements don't automatically do anything on a user's phone unless they have an app installed to detect them.
Chrome for iOS and Android (installed on many newer Android devices, but very few iOS devices) will automatically detect Eddystone-URL advertisements and display a notification from Chrome if the user has opted-in. However, no sound is played. Bottom line: on a phone without a custom app, detecting an Eddystone-URL will not cause a sound to play.
If you build a custom app and get it installed on users' devices, you can certainly make it play a sound on Android devices when the beacon is detected. On iOS devices, you could also display a local notification on the device that will play a sound, but only if the user has the volume turned up on the device, does not have do not disturb on, and has opted-in to receiving notifications from the app.
I want to make a game .
There are 20 iPhones or more.
When one iPhone is nearly another.they both know that. (Distance is less than 1or 2 meters)
Is it possible?
sorry for my English
Yes, this is possible, but only if phones have your app in the foreground.
Apps can send an iBeacon transmission, but only if they are in the foreground. Apps listening for an iBeacon transmission can do so both in the background and foreground, allowing other apps that are up to ~40 meters away to know about the presence of the transmitting apps.
When I started working on our company's Windows Phone app project there was no full HD resolution for WP. But now there is and I'm supposed to disable the app for full HD devices in the WP Store. How do I exactly do that?
The main reason for this is that the app has a thick black ribbon on top of the screen when used with a full HD device.
I have noticed that when you update or upload .xap file, the Store recognizes the requirements of the app. The Store says the app works on all screens. How do I set the requirements so that the app is disabled HD resolution screens?
The app is made to support WP versions 7.1 through 8. I eyed the Internet for help but it seems that because the app is WP 7 compatible I can't describe the resolutions in the WMAppManifest where the Store would easily to find it. Or can I?
It would be so great if I could do this some easy way instead of going through the whole app to make it work "better" on HD screens.
There is no way how you can prevent users with certain display resolutions from installing your app. A similar question was asked here, it was about installation prevention of apps for specific device types. What you can do is to do the check in code.
You could check the device's display resolution when starting the application. If the size exceeds your limit, you could inform the user about that and exit the application.
How can I get a screen resolution of Device (Windows Phone)
However, I don't know how this would affect the app certification.
Windows Phone 7.1 only supports 800 x 480 resolution and Windows Phone 8 supports multiple resolution.
The scaling used for Windows Phone 7x apps on Windows Phone 8 means that one 720p and 1080p devices, you will get a black band. There is nothing you can do.
You could recompile the app as Windows Phone 8 app and have both WP7x and WP8 xaps available and this will ensure that the space is consumed correctly and the black band isn't shown.