Hey so im trying to use a maps program, that uses stored maps from my storage card, but i keep getting the permissions "do you want to allow...." and it keeps coming up, every 1 second. I was wondering how to change my registry to get rid of that prompt
Hi there,
Does anyone know how to remove the My Location from the Weather? Or at least stop it.
Cheers
You have to go into settings and location and remove use wireless to determine position checkbox. Then you can remove it.
Sent from my HTC Desire
Yesterday I installed the update from HTC on my HTC Trophy. This morning I found out that my datetime settings where changed into 6 may and 1 hour earlier.
My settings are set to automatically retrieve datetime settings, and the timezone seems to be correct.
Anyone have the same issues after installing the update? Is there a way to force the update of the datetime settings?
Had the same issue (althoug my date and time went back to 1980 ). The way I solved it was to turn off auto time detection, set it to the correct time and then turn on auto back on.
Kinda defeats the purpose of auto time detect but it got my syncing working!
I had the same problem and used the same fix
Same thing here, same fix on my hd7, my mate also had it on his mozart, no biggie really!
Thanks! I have used the same approach to get back in sync.
I was just wondering how the automatic datetime function works, and if there is a way to force the updation of it.
I think the way it works is that you have to set up an initial time and then the automatically update just updates the time when you move to a new time zone or summer time kicks in.
I thought it was supposed to function like on the PC, but the aforementioned theory fits more the bill with what is happening.
Has anyone gotten the patched/cracked Google Wallet working? After activating one card I can no longer use the application. The application force-closed and cleared all the data telling me to try again. Now I cannot add an account and when it tries it force closes, and so I acquired the output of the logcat that occurs after:
1. Opening the application.
2. Clicking my email and then "Continue".
3. After returning to Apex Launcher and after Google Wallet stops responding.
The logcat is here:
fuzo[dot]us/mehstuff/phone/logcat/walletlog01.php
I commented it a bit.
Am I getting this because of a Secure Element problem or has nobody else been able to get the wallet to work?
Enzious said:
Has anyone gotten the patched/cracked Google Wallet working? After activating one card I can no longer use the application. The application force-closed and cleared all the data telling me to try again. Now I cannot add an account and when it tries it force closes., and so I acquired the output of the logcat that occurs after:
1. Opening the application.
2. Clicking my email and then "Continue".
3. After returning to Apex Launcher after Google Wallet stops responding.
The logcat is here:
fuzo[dot]us/mehstuff/phone/logcat/walletlog01.php
I commented it a bit.
Am I getting this because of a Secure Element problem or has nobody else been able to get the wallet to work?
Click to expand...
Click to collapse
I can add cards but my cards fail to work.
Sent from my SPH-L900 using xda premium
jamice4u said:
I can add cards but my cards fail to work.
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Could I possibly trouble you to post a logcat?
Running into this same issue with my T-Mo Note. Big issue:
ControllerAppletImpl: SELECT a0000004762010 expected=0x9000: statusWord=0x6a81 (Function Not Supported) on query to MIFARE Classic Emulated that Wallet does when you attempt to add an account, so it never gets to doing the remainder of the checks. Interestingly enough, if you catch a logcat where you turn NFC on and off, you'll see that your Secure Element still shows up.
www.google.com/patents/EP2160696A1?cl=en
In the event that PPSE selection results in an error in block 308, the error is detected in block 310. In block 310, if no error is received, an ISO 14443-4 transaction may be initiated. Alternatively, if an error is received in block 310, it is determined in block 312 whether the error includes the status word (SW) 0x6A81. SW=0x6A81 indicates a special case failure (the indication is that the device is disabled) that results in immediate transaction termination without checking MIFARE® support.
If the error received in block 312 is an error other than SW=0x6A81 , the wireless reader may attempt to select at least one supported application located on the wireless smart device in block 314. For example, because PCD 100 has no prior knowledge of any applications stored on PICC 102, in block 314 PCD 100 may transmit Select application identification (AID) commands to PICC 102 for each application supported by PCD 100. PCD 100 can determine from Select AID responses which applications are supported by both PCD 100 and PICC 102.
I imagine we need some way to fix the MIFARE Classic Emulated blocks - I have tried messing around, but I'm not seeing a way to really make it work, unfortunately. I'm no Android developer, though - hopefully we'll find some way to correct this - as long as it's reporting the error state and returns that hex code, we won't be able to query the SE with Google Wallet, apparently.
NFC Tags are awesome for automating stuff. Want easy to activate sleep tracking? Just set up a tag near your bed. Want easy to activate car mode? Set up a tag somewhere in your car. But they have one big flaw: to use them, you must take your big ass phone out of your pocket.
(In above example, I activate sleep tracking, disable always-on mode and enable theater mode by just touching the tag. Always-on mode is then automagically re-enabled in the morning when sleep tracking stops.)
NfcTagRelay is simple and light tool that reads tags using your smartwatch and then relays the tag detection event to the phone, so it can be acted upon using various automation apps such as Tasker.
How it works
Every NFC tag has unique ID that can be used to identify it. That ID is broadcasted via Intent to all apps on the phone whenever tag is scanned. It is broadcasted via two different intents:
Intent 1
Action: com.matejdro.weartagrelay.RECEIVED_TAG
Extras:
tagid = <ID of the tag>
Intent 2
Action: com.matejdro.weartagrelay.TAG_<ID of the tag>
(This second one is more useful for apps that cannot filter Intents by extras such as Tasker).
Tasker example
Here is my example on how I'm receiving tags via Tasker. As mentioned above, app sends events via Intents. That is why we will be using System -> Intent Received Tasker event.
1. ID Receiving Context
First we have to figure out what is the ID of the tag that we are scanning. For that we can use com.matejdro.weartagrelay.RECEIVED_TAG which also broadcasts tag ID.
Create new context with System -> Send Intent event
Under intent action enter com.matejdro.weartagrelay.RECEIVED_TAG (See attached picture 1.)
In task that is triggered by this, copy contents of the %tagid variable to the clipboard. For convenience, you can also copy it along the rest of the second intent (see attached picture 2).
After you get the tag ID, you can delete that context or just disable it to add more tags later. It is triggered when you scan any tag so you likely won't need it.
2. TAG Context
Now that we have the ID, we can create context that will be activated whenever tag with that ID is scanned. For that we will use com.matejdro.weartagrelay.TAG_<ID> intent.
Create new context with System -> Send Intent event
Under intent action enter com.matejdro.weartagrelay.TAG_<ID>, where you replace "<ID>" with the actual ID of the tag (See attached picture 3.)
In task that is triggered by this, add whatever you want. This task will be triggered every time you scan tag with specified ID.
Installation
Install Sony SmartWatch 3 NFC Support Package. Without that, NFC will not work at all on your watch.
Install included APK to your phone
After some time (usually up to a minute), app will be automatically installed to the watch (you will get notification). After that you may also need to grant the app NFC permissions (it will ask on the watch). Make sure you do, otherwise it won't work.
Huge thanks to user ebones. Without him, this would not be possible.
Hi, all installed and appears to be working. Although I didn't get any notifications to grant NFC permissions etc. Can you also please confirm the name of the app once installed on the watch?
Thanks
I think it only asks for permission if you are running Marshmallow on the phone.
Has anyone managed to get an NFC tag (or reader for that matter) to relay to another app? I know this app does work with tasked, but it would be great if there were a way to relay to a chosen app. E.g. HID Mobile Access.
And does this app allow two way communication?
no app?
i dont get a notification about the app being installed on my smartwatch. what should i do?
Does it appear under all apps?
matejdro said:
Does it appear under all apps?
Click to expand...
Click to collapse
yes. i can uninstall it without problems too. but reinstalling didnt work
I mean on the watch.
matejdro said:
I mean on the watch.
Click to expand...
Click to collapse
no it doesnt
EDIT: after a factory reset and completely starting over it still doesnt show
EDIT 2: this does show up tho
Then you don't need to confirm permissions. It should work by itself.
matejdro said:
Then you don't need to confirm permissions. It should work by itself.
Click to expand...
Click to collapse
Thanks. Then i might have a mistake in tasker.
Verstuurd van mijn XT1072 met XDA Forums
Please help me!
I've installed NCF support package and app. Can I scan NFC Pass-card to this watch and use only watch to pass against card?
No, this is only for detecting NFC tags and perform various actions when detected.
Hi,
please, tell me your full setup (device, ROM, etc.).
After days of trying to get it to work I'm really frustrated and have no idea what to do.
My device is a Samsung Note 3 and I tried it with Kitkat 4.4 (Sweet ROM), Lollipop 5.1 (Dark Wolf), Android 7 (Resurrection) and several versions of the wear app. But nothing workes.
Smartwatch 3 Setup: TWRP, LCA43 (Android 5.1.1, built-in Wear App Version 1.3.x), NFC Support Package, Wear-SuperSU
Smartwatch 3 Working: for each new pairing with the different Smartphone OS's the watch had to be resetted and after that I installed "Wear Mini Launcher" and "NfcTagRelay" (as well as I did the steps mentioned in several descriptions e.g. enable dev & usb debugging), the NfcTagRelay installed successfully and gave the option to enable/disable NFC
Note 3: within each new OS I installed the appropiate gapps and apk's ("Wear App" v1.3.x, "Wear Mini Launcher" and "NfcTagRelay"), installation with other versions of the wear app on the phone didn't work, as expected
Note 3 Setup with Kitkat 4.4.2: Wear App works fine, connection is always enabled, Mini Launcher works great too. But that didn't work for the nfc purpose. The watch seems not to scan any tag (no vibration notification at the watch, no reaction on the phone)
Note 3 Setup with Lollipop 5.1 (Dark Wolf): Wear App does not find the watch (as far as I remember, have to test this another time, coming soon...)
Note 3 Setup with Android 7.1.1 (Ressurection Remix): after succesful pairing with the Wear App it seems to loose an active connection and on several actions in the app a message pops up that their is no connection, Smartwatch reacts on nfc scan with vibration, no reaction on the phone
greatings, think-meta