“nfc”

I’ve only had these for like a year now, and the battery life on them was never really that good. And it has only been getting worse with time. Also, you would think that transparency mode could save batteyr-life but really transparency mode seems to make the battery life even worse than with noise cancellation. I would rather just turn off both transparency mode and noise cancellation without the sound being 10x worse. Where the heck are the controls for AirPod settings? Why isn’t there a section in the settings app for AirPod settings? Why isn’t there a Low Power Mode for AirPods? These are all things that either other Bluetooth wireless headphones have, or Apple has implemented on its’ other devices. Does Apple think they can just totally slack on competitive development for AirPods because they usually sound great; if now the best compared to other Bluetooth pod types? Because I will switch to a better brand soon with more features, better battery, better settings app, etc. -like Bose. I have a pair of Bo

We're trying to communicate with Tangem cards (https://tangem.com) that contains ISO7816 Tag via NFC.We open session:readerSession = NFCTagReaderSession(pollingOption: [.iso14443], delegate: self, queue: nil)readerSession?.begin()Bring our card to iPhone NFC Reader and connect to a tagsession.connect(to: tags.first!)and start sending APDU commands one by one.But after about 20 seconds CoreNFC session sends us the error:Error Domain=NFCErrorCode=100 Tag connection lostUserInfo={NSLocalizedDescription=Tag connection lost}or, if there was no active command at that moment:Error Domain=NFCErrorCode=201 Session timeoutUserInfo={NSLocalizedDescription=Session timeout}We have to send plenty of commands within one session. It is needed to secure Tangem clients from malefactors that can read data without user's knowledge and approval. Session with the card can last more than 30 seconds. And we can't invalidate session and start another one, because after it we have to start sending commands from the very begin

Hi All, We are using a ST25DV NFC tag and Fast Transfer Mode. Our iOS app sends a custom command that sends some data as an input and expects a response from the tag that includes a payload of ~4000 bytes. We have successfully sent this command to the tag using the NFC Tap App on Android and received the full data response. However, on iOS (15.3.1-iPhone 12 Pro) as we loop through and get the response (256 bytes at a time), at random point during the reading of the response we get the following error: [CoreNFC] 00000002 80050360 -[NFCTagReaderSession transceive:tagUpdate:error:]:824 Error Domain=NFCError Code=102 Tag response error / no response UserInfo={NSLocalizedDescription=Tag response error / no response, NSUnderlyingError=0x283c3cde0 {Error Domain=nfcd Code=29 Tag Error UserInfo={NSLocalizedDescription=Tag Error, NSUnderlyingError=0x283c3c1b0 {Error Domain=com.apple.nfstack Code=20 No response from tag UserInfo={NSLocalizedDescription=No response from tag}}}}} We are not using .addres

I created a demo to test core NFC and failed to write the iso15693 tag. Byte bytes[8]={0x12,0x21,0x04,0x74,0x65,0x73,0x74,0x00};t NSData *data = [[NSData alloc] initWithBytes:bytes length:8]; [iso15693Tag writeSingleBlockWithRequestFlags:RequestFlagSelect blockNumber:0x04 dataBlock:data completionHandler:^(NSError * _Nullable error) { t if (error) {t tt NSLog(@Failed to write tag!); tt} else { tt NSLog(@write succeeded!); tt } t }]; I couldn't execute successfully and got the error message： Error Domain=NFCError Code=100 Tag connection lost UserInfo={NSLocalizedDescription=Tag connection lost} I would like to ask if core NFC supports writing iso15693tag？ I think I need a successful example of how to create a correct blockdata. I hope someone can help me. Thank you very much！

Description:We are using the `read NFC tag in background` functionality but we are also reading the tags in foreground mode.If we do the Tag scan with NFC, having the app opened (in foreground), we also receive the notification about the scan result comming from the background read functionality. In result, we are experiencing the Tag read completion twice at once being in foreground mode: from foreground read and the background listener.Step-by-step instructions:1. Setup the `NFC background read` listener and the `NFC foreground read` functionality2. Open the app3. Run the NFC session4. Move the iPhone towards the Tag to read itResults we see:The Tag is being read but we are also receiving the notification from the `background NFC reader` at the same time.Results we expect:If the user is in the foreground mode, the app is opened, and he reads the tag, we expect not to receive the notification from the background NFC listener. The notification fro