yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Mr. Spontaneous:
Thanks for your reply. To give you an idea of what I'd like here's what I'm doing:

I bought Touchatags, which are a write-protected NFC Type 2 tag which has a URL as browser content (according to the NXP Tagwriter). When you scan them, they send you to a URL which serves as a launching point for an action. I'd like to get in my car and tap my device to the dash to activate car mode (GPS, Nav, etc.).

The service idea sounds workable - if you could catch all NFC scans, run them against a list of known ids and then forward them onto the system if they're unrecognized, that seems like it would fulfill my needs while letting you be able to offload the default actions to the OS as needed. I don't know if this is feasible, but if it is, consider this a feature request.

Thanks! :)

I don't use tasker, but I might have to look in that direction.
[Samsung Galaxy Nexus] the7thson:
THIS is amazing. You need to create a new thread with this info and have it stickied imo, so many people would benefit from this.
[Samsung Galaxy Nexus] m.klinge:
Ahh fantastic :D

However I'm still unable to get it to work (The way i want) :(

When the screen is on and the tag is removed it works very well. However if I scan the tag, turn off the screen, remove the tag finally turn on the screen NFC ReTag still acts as if the tag is present :(

Ideally the "Tag lost" should be broadcastet when the screen is back on (Unless use NFC while screen is off option is used) :)

Perhaps I'm - yet again - overlooking something? Otherwise I would stick with my Tasker solution for now, as one of my uses would be in the car where I more often that not removes the phone while the screen is off :)

//M
[Samsung Galaxy Nexus] ascsa:
Nope, in this case NFC ReTag is closed and does nothing, not even draining battery ;)... because there is no trigger ....remember NFC dispatching is done by your firmware, even the xposed mod hooks into some low-level nfc method ...so, without a trigger, no action ....you would need an other trigger :D.

So here you could use the perfect combination with your Tasker solution--> get the screen on event, wait a few seconds, check if a tag was scanned and then fire your tasker task .... but as mentioned, I wouldn´t like the screen on trigger because it´s not instantly.

or just use the nfc always on option ....
[Samsung Galaxy Nexus] m.klinge:
Well that's actually exactly what I've made with Tasker, granted IF the tag is lost while the screen is on my current setup won't catch it until the screen has been turned off - so yea I could take use of the "Tag lost" to make it even better - in reality I'm not really sure if it's worth the hassle :)

I'm all in for automating my normal usage, not pressing extra buttons or swiping tags to do stuff, it needs to fit my current use pattern and make my day more efficient :)

In essence we'll never have a working solution without using the NFC scan always on if we don't accept something else as a trigger. Now I do know NFC always on is a possibility, but on the other hand I tend to believe there's a reason (Battery consumption) it hasn't been implemented in the first place. That being said I havn't done any testing to see just how much it will affect my battery life when the device is not resting on a tag...

Besides my concern about battery consumption the feature is currently not working on my LG G2 :)

//M
[Samsung Galaxy Nexus] ascsa:
Update 2.7

HUGE update 2.7 is out in the wild now ;)

Main features: New Wifi and Battery triggers ... new activities ... an improved trigger handling .. and many other tweaks .....you will love it :D

It´s a Staged Rollout within the Google Playstore, due to the complexity of this update, so perhaps you have to wait a little bit longer until it´s available for you ...

Feedback highly welcome!

Update 2.7 (2.7.x = fixes)

* NEW Wifi and Battery triggers

* NEW Activities: Close app, Toggle NFC Setting, Location Access, URI

* Log table for activities

* Improved receiver handling

* Many additional improvements, tweaks and bugfixes

EDIT: OK forget the staged rollout approach ....with a free and a pro version available, a parallel staged rollout makes no sense --> so complete update is out now ... btw. don´t import database from Free v.2.7 to pro v.2.6 ...it will definitively crash :silly:
[Samsung Galaxy Nexus] Szczepanik:
Thanks. Nice mention in

http://www.gottabemobile.com/2013/1...of-pvc-tags-automate-android-phone-functions/

Cheers

Tom

My Note 2 to you
[Samsung Galaxy Nexus] ascsa:
Yep, thanks for the link.

And that´s still v2.6 .... any feedback on 2.7 ?

( I love it, but I´m a little bit biased :highfive:)
[Samsung Galaxy Nexus] klau1:
Can an actual Tasker Plugin like the Locale NFC PLUGIN be implemented into this ReTag app?

For security reasons, allowing external access to Tasker for ReTag is a security vulnerability.

Some Tasker tasks are created to open locks and other security functions.

I would rather not have to enable the option to allow every program into the world to have access to my sensitive Tasker tasks.

---------- Post added at 07:15 PM ---------- Previous post was at 06:56 PM ----------

Another question I have is, how does one disable the toast messages that pop up when a tag is scanned.

I know the toast messages are from ReTag because they stop appearing once the App is frozen.

The search function is down again.
[Samsung Galaxy Nexus] ascsa:
Hmm according to your signature, you are rooted .....so enable the external access option in tasker should not be your primary security concern ... ;)

However , you can easily make your tasks secure by adding some kind of password ....only allow tasker to handle tasks if this password is set correct ..... then add the password to the ReTag Advanced Tasker task activity as your custom variable and check it on receive .... also add the password to your existing profiles/tasks.. .and don´t forget to clear the password after each run..... and you should be fine. Sounds complicated, but should be relatively bulletproof ...

And sorry no, it is currently not planned to support other locale / tasker plugins ....

Which toast messages? NFC ReTag only toasts a new tag detected and on some activities to give you additional information ...and you can´t disable them ...

OR do you mean the standard android app chooser that occurs if more than one app can handle the nfc intent? (has nothing to do with nfc retag, but yes this would disappear if you freeze all nfc apps but one) --> sure you can solve this either by deactivating the nfc retag background receivers (or the background receivers of the other nfc app ... every good app should have such an option) or writing a tag that contains the specific filter information, which app to choose (e.g. special nfc retag tag ).
[Samsung Galaxy Nexus] klau1:
Thanks for the tips, I'll try them out when I get the chance

About the toast msg, no I don't mean the chooser, it's the small messages that disappear after a second. Seems to display the tag info

Do you understand what I'm referring now?
[Samsung Galaxy Nexus] ascsa:
Hmm, to be honest, no ... could you give an example ?
[Samsung Galaxy Nexus] klau1:
Well I would give you a screen shot, but toast messages disappear before any screen shot can be taken.

But it says something like this:

NO ACTIVITYName: [Go] UID: [xxxxxxxxxx_LOST] Cycle:[1]
[Samsung Galaxy Nexus] ascsa:
No need for an screenshot, I know exactly what it is ;) ....

This toast pops up when you have a tag cycle defined without any activities ... should inform the user that he has forgotten to add activities ... simply add the "do nothing" activity to mute this pop up ....or delete the tag cycle

But in your case I assume you have the xposed tag_lost module (xx_LOST) activated, and a tag (GO) defined to get rid of the new tag_lost detected message for a tag you don´t want the tag lost feature . ;) right ?

sure you can mute this by adding the do nothing activity, but the better solution is to activate the "don´t add tag lost tags" (Settings/Advanced settings/Activate tag lost support) via the settings ... this only recognizes "lost_tags" already saved ... so if i´m right, you could delete this tag and simply activate the option ;)
[Samsung Galaxy Nexus] klau1:
Great response! In that case, I plan to add an activity to the tag_lost later so your hard work is not gone to waste ;)

Used to have an activity setup for taking the phone off the car dock in the tag lost forked version of AnyTag on the S3 before I got the note 3.

But for now, I will add a do nothing activity to hide the toast message. :)
[Samsung Galaxy Nexus] klau1:
I'm trying to follow your advice above to secure tasker tasks.

My understanding, correct me if I'm wrong...

1. Create a password variable

2. For each task, implement a variable check to see if variable matches password, if matches then run then clear variable, else do nothing

How would this work for automated contexts within Tasker?

For example,

if there's a time context that triggers a task [Unencrypt] which unencrypts a file at 12:00

If I were to set the password variable to the correct password within tasker via a task [Set Correct Password], and have the above [Unencrypt] task Check for the variable before running, external access will allow other apps to do the same.

So how can password protected tasks for tasker contexts be automated?
[Samsung Galaxy Nexus] ascsa:
Hmm, it´s getting a little bit complicated ... but I think the most easy solution would be, to let your context based tasks check the context ...have a look at the %PACTIVE variable ;) ...
[Samsung Galaxy Nexus] klau1:
Nice! Thanks for the tip!

BTW, NFC Lockscreen Enabler team just recently implemented system intents that can be recieved directly by Tasker.

Looks like there are now two solutions, I'll check out which one works best for this case.

Keep up the great work!
[Samsung Galaxy Nexus] ascsa:
Yep, they send a broadcast (two different broadcasts, depending on version?*confused*). ... From my point of view, broadcasts are not the best solution to handle nfc events ...

And btw. sending a broadcast is something you could also do with ReTag .. ... There is even a compatability setting for lower case variables for Tasker.... But I had in mind, that you would also need the external access enabled...(probably wrong!)

However, check it out and report back if you want ;)
[Samsung Galaxy Nexus] Tinnman:
ok first of all I am a complete noob in this so please bear with me. :o

I would like to us a tag in my car to turn on bluetooth, play music, start play music app and keep the screen on all the time. Then when I remove the phone I would like the music to stop and bluetooth turned off.

Is this possible?

Issues I have now are:

My phone (nexus 4) needs to be unlucked to activate a tag

I will not start the music

When I remove the tag there is no change. (am I right in assuming NFC only gives an order and then does nothing untill you remove the phone and tag it again?)
[Samsung Galaxy Nexus] Szczepanik:
Phone has to be unlocked to activate NFC. You do not want someone else activating actions on your locked phone do you?

You can have 2 activuties fir a tag. First tap on tag will turn things on. Second tap on tag can turn things off.

Cheers

Tom

My Note 2 to you
[Samsung Galaxy Nexus] ascsa:
Yep, Szczepanik is right, that´s the standard android behavior since android ICS 4.0 ....I don´t like it, but afaik google implemented it due to some google wallet security issues ....from my point of view it´s not necessary ...and with retag you are absolutely safe if you disable the activity tag and beam receiver because the activities are stored in an app internal database (exception: activity tags and beam ;))... ...Even with the activity tags enabled, what´s the worst case? sending someone to a website, disable bluetooth, make a call and let the text2speech activity say the f*** word ...?

However, on a rooted device, you can change this "must be unlocked for nfc" behavior via a moded nfc.apk or a xposed module. Usually you can decide between "nfc always on" and "nfc on when screen is on" (that´s the old Gingerbread behavior, and personally I prefer it that way, because from my point of view it´s the right mix of security and usability ). The same xposed module (link in post #1) and some moded nfc.apk´s support the "tag lost" feature .... You can catch these "tag_lost" messages via NFC ReTag (enable it via settings) ...personally I prefer the double swipe approach Szczepanik mentioned (either with some toggle options or via cycle), but ReTag supports your requirement, anyway.

Start the music is sometimes a little tricky but once you have found the right configuration, it´s absolutely bulletproof ....the trick is to use the "Start/Launch" / "Music Player" / "Toogle Play" activity .... this activity will act like a headset button, so make sure your Music Player will recognize Headset commands (btw. Google Play Music doesn´t support headset commands ;-( ... also make sure, that you don´t have several player apps installed, that want to catch the headset command ....that usually causes a mess and no app will respond ......don´t launch and close music player apps via the start app activity ... this will usually not work.

Had some problems with the music player activity on one of my testing devices a while ago ....uninstalled all music players, except the one I usually use and since then it works perfect again ...i think it was caused by some old xbmc version, but this is only a poor guess.

EDIT: Hmm forget the part "Google Play Music doesn´t support headset commands".... just played a little bit with a N5 without any 3rd party music player app installed and it works without problems .... ;)
[Samsung Galaxy Nexus] ascsa:
Update 2.8

Update 2.8 just released.... Mainly a new Bluetooth trigger ;) a new setCycle activity (usefull if you use multiple triggers with the same template )....and Android 4.4 adaptations ....

btw. anyone with android 4.4 issues ? Feedback welcome!

Update 2.8 (2.8.x = fixes)

* NEW Bluetooth trigger

* Set Cycle activity

* Android 4.4 support

* Android 4.4 Location activity

* Bug fixes
[Samsung Galaxy Nexus] Szczepanik:
2.7

Thanks for the 2.7 and 2.8 updates. Continues to work well on my Samsung Galaxy Note 2, I could not see any difference in Wi-Fi trigger. This brings me to suggesting a few enhancements. I do not have Tasker (yet) and appreciate that these ideas would widen the usage of NFC Re-tag in that direction.

1) Widgets that would allow one to simulate a tag. If you were not near a tag, the appropriately named widget would perform the same action touching the tag or the same as launching NFC Re-tag > My Tags > [tag name] > Simulate.

2) Ability to re-order actions when editing a tag e.g. insert new action at second step and move step three to after step four etc.

3) Connect to particular bluetooth device - similar to existing one for Wi-Fi. I have tag in car that turns on bluetooth but I want to connect to car bluetooth and not my PC BT.

4) Wait for Wi-Fi connection. I currently use a delay after turning on Wi-Fi but would prefer to be sure that Wi-Fi was connected before launching apps such as mall that I want too synchronise over Wi-Fi.

Thanks again for this app. I use it every day, first thing on waking and last thing before sleeping.

Cheers

Tom
[Samsung Galaxy Nexus] ascsa:
Many thanks for the feedback ! Answers below ;)

already on my near term to-do list ;)

discussed here several times.;)...bottom line: in most cases the order is irrelevant due to the android multitasking and the way retag fires the activities ...however if we find a nice way for reordering the activities we will implement it ...in fact, we implemented already some basic internal stuff to support this ;)

usually you should automatically connect to your car bt when in range ... at least, if the car has some decent bluetooth stack ... btw. the whole bt compatibility thing is a mess from my point of view .... however, I have some nice ideas regarding additional bluetooth features, and connecting a particular device should be one of the easier activities...;)

Not sure I got this one ....the wifi trigger actually recognizes the wifi-connection ....perhaps the sync between your access point takes some additional time ? ... However, the pause activity got some tweaks in 2.8 , too .... so your approach should work better on 2.8 ....

EDIT: Ah ok, think I got it ... you turn turn wifi on via a tag, right ? then I would simply add an wifi trigger that starts the apps ...

Thanks, feedback and suggestions always welcome !
[Samsung Galaxy Nexus] ascsa:
Update 2.8.1

Update 2.8.1 with russian translation by 4pda community is uploaded to Google PLAY ....
[Samsung Galaxy Nexus] sap323:
Hi !

I have some noob doubts.

1st of all:

I have installed in my Nexus 7 (4.4):

NFC Retag PRO

Tasker

Secure Settings

Xposed (with module NFC Lockscreenoff enables 1.9.5)

Please, explain like im 5.

I want to when my tablet is on my tag, a movie opens (i already did that with a simple task in tasker), but what thing should i do, that when the tag i lost (my tablet isnt on my tag anymore) the movie close (go to homescreen)

I dont understand if i need another cycle or not, and what activity (and how) should i use to close the movie when the tag is removed.

Did i explain myself ?

Thnxs for all !
[Samsung Galaxy Nexus] ascsa:
Hmm ok, not sure if I could explain it to a 5 year old noob, but I will try ...;)

First of all, I wouldn´t use the "tag lost" feature, because every time you grab your tablet, you will close the video ... not very convenient from my point of view ....so I would recommend a second cycle instead --> first swipe start the video, second swipe stop the video ... but that´s up to you.

The difference between "tag lost" and a double swipe is only the trigger, activities should be the same ....

Means, Xposed (with module NFC Lockscreenoff and tag lost message enabled ) should give you a "tag found" message (id 12345678_LOST ) every time you move your device away from the tag --> HINT: check if "Tag lost support" is enabled in ReTag settings AND uncheck "Don´t add tag lost tags" )

So basically, with tag lost you have TWO tags in ReTag ---> first with ID 12345678 and second with ID 12345678_LOST ....so you add the start video activity to the first tag and the Close video activity to the second tag.

If you use 2 swipes, you only have ONE tag in ReTag (ID 12345678 HINT: disable tag lost, if you doesn´t need it for other scenarios ...) --> Here you need 2 CYCLES --> first cycle: start the video, second cycle close video ... as mentioned, the same activities as int the tag lost scenario.

Activities:

1.) Start video: Ok, you said you have done this with tasker ...not bad for a 5 year old noob ;) .... .to be honest, I wouldn´t know how to start a video with tasker without searching a bit, so I use the native ReTag Activity "RUN URI" (Category: Start/ Launch) with a parameter like "file:/storage/emulated/0/YOUR_VIDEO_FOLDER/YOUR_VIDEO.mp4"

2.) Closing video could be a little bit tricky .....Android usually doesn´t support things like that ... but you´re rooted, so it shouldn´t be a problem (with a little help from the ReTag Expert Plugin ;)). Try the "Close app" activity (Category: Lab) and choose your media player as parameter ....

(HINT: The "Close app" activity depends on your preferred method to play a video... on my testing device, I use BubbleUPnP together with the standard Video Player, so I have 2 "Close app" activities: 1. close GALERIE (=standard video player) and 2. close BubbleUPnP ... works without problems for me ;) )
[Samsung Galaxy Nexus] sap323:
Wow ! Perfect ! Thank you so much !

I have to use the "tag lost" because is for some especific use. I cant use the double swipe...

Yes, i dont why before i didnt get the "tag found" lost. But now i got it, and it works just fine !

But where do i add that id ? ID 12345678_LOST ?

Yes, with tasker you could make to "open file"

And also with tasker, you could make "go homescreen"

Thanks !
[Samsung Galaxy Nexus] ascsa:
Hmm, don´t get me wrong, with retag you can use both features ("tag lost" and "double swipe/cycles") for different scenarios at the same time without any problems (heck, you can combine both if you want ;)) ...so, as mentioned, it´s up to you ....

it´s an example ID...just to illustrate that you will have 2 tags in retag .... 1. the normal scan tag and 2. the tag with _LOST in the ID ... you can add both tags via the standard retag add tag function ... no need to add the id manually ...

Not sure, if the "go homescreen" function is exactly what you need because I could imagine that some media players will not stop, but play in background ...However, Retag has also a "show homescreen" activity (Category: Misc) ...so again, it´s up to you...choose the setup which fit´s your needs ;)
[Samsung Galaxy Nexus] ascsa:
Update 2.8.2

Update 2.8.2 is out in the wild now ;)

Contains small design changes and bug fixes ...
[Samsung Galaxy Nexus] Fed0r_off:
question

hello!

GPS is not included if it is in one cycle with the launch navigation. What to do? delay does not help ...

Sony Xperia Z1, 14.1.G.2.257 + root, NFC ReTag Expert Plugin is installed.
[Samsung Galaxy Nexus] ascsa:
Hmm, the GPS activity is optimized to work with the Google maps navigation (=navigation activity) ...and should work without problems ;) . Do you use the "navigation" activity or do you try to open a different navigation application via the "start app" activity?
[Samsung Galaxy Nexus] Fed0r_off:
i try to open different navigation application via the "start app".

i use: Yandex Navigator and Navitel Navigator (i can not insert links).

google maps working bad in Russia.
[Samsung Galaxy Nexus] ascsa:
Hmm, ok I think I know what the problem is ....the "start app" activity (and also "start activity" activity) is too fast ;) for the plugin on some devices .

I did already some fine tuning for the "navigation" activity and I must do something similar for the "start app" activity ... Shouldn´t be a problem ....Will include it in the next update ...

Not sure if I could release a bugfix update within the next couple of days (also depends on the current Kitkat 4.4.2 release and the implications ...) and x-mas is coming ;) ...worst case, i will release a new major update in January ...

Thanks for reporting the issue!
[Samsung Galaxy Nexus] MrWilliams2:
I just popped in to say thanks for an awesome app!
[Samsung Galaxy Nexus] ascsa:
You´re welcome!

If you have any issues or questions, post here, write me a pm or just send an email ;)
[Samsung Galaxy Nexus] dav010:
I want to thank you for this incredibly useful app.

It could be nice to add the support for the lock screen security: for example I'd like to remove pin or sequence when I'm at home (and connected to my wifi).

Do you think it would be possible?

Thank you very much and happy holidays. :good:

Marco.
[Samsung Galaxy Nexus] ascsa:
Hmm, good question .... you could try Tasker and the Secure Settings plugin (-> Keyguard ) for this .... should work.....on some devices .... sort of .....

The problem is, that android doesn´t support lock screen security settings via an official api and all the workarounds and hacks are not 100% reliable from my point of view... although ReTag uses a lot of hidden apis, hacks, experimental functions and workarounds, we haven´t found a secure and stable solution for this (yet) ....and because of lock screen security is some essential security feature, we will not release a buggy and insecure native activity for this, until we are 100% satisfied....

However, you could always try ReTag with the Tasker/Secure Settings solution and check if it´s stable on your device/rom ....
[Samsung Galaxy Nexus] kkennedy22:
Motorola skip & skip dots

Is there any reason I shouldn't be able to get this working with the Motorola skip and skip dots that came with my moto X? They are definitely NFC tags. To try to make it work I have to disable the Motorola skip setup app, otherwise it intercepts all communications with those tags. But even with that disabled NFC still works since I can use Android Beam etc. But when I hold the phone to those tags in NFC retag, nothing happens. Any help/advice would be appreciated.