yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ascsa:
Yep, but the number of request over the last couple of month is limited

You could add some tag identifier .... I would face the same problems and some others in NFC ReTag.

NFC ReTag was first to implement a lot of things: e.g. The first NFC app

- using the id for starting activities and working with write protected tags

- having a TextToSpeech activity

- with an unlimited number of tag cycles

- with beaming tags

etc. etc.

Btw.: the last update implemented advanced Tasker tasks with support for runtime variables ...afaik the first and still only NFC app that could do that ...

No, I don´t take it as an attack :D and please don´t get me wrong, but I´m a little bit stubborn and if I don´t see the need for a feature and could not make it 100% work how I think it should work, I don´t see why I should implement it ..

btw.: You mentioned, it should not be a problem to explain such a feature to end users ... However, I once thought that it should not be a problem to explain to end users that nfc is deactivated when screen is off and that´s a firmware restriction no app could influence, or that´s crystal clear that an app that has an call feature needs a call permission or that some features simply need root or that you could not swype your device over your (or your neighbors) company access badge or credit card and then use your device instead ....but that´s exactly the kind of questions, request and comments I receive several times a day ...
[Samsung Galaxy Nexus] m.klinge:
What would it take from me to get you to make a stand-alone app that does nothing more than what I explained (along with being able to execute tasker tasks)?

I guarantee you it will be a hit :)

Btw being first at implementing something is a very poor reason to stop implementing new "firsts" later on :P

//M

Sendt fra min LT25i med Tapatalk2
[Samsung Galaxy Nexus] ascsa:
LOL tenacious as ever ;) ... simply convince me .... However, you don´t have to convince me that a "tag lost" feature would be nice and some people would like it..

BUT your solution is based on the display on/off event and it´s basically this:

Display ON -> wait 5 sec and then check if tag (the last tag?!) was scanned within the last 5 seconds, if NOT start the "tag lost" activities of this tag ....

Therefore NO instant detection of the lost tag (for me a show stopper), no detection if the screen stays on, issues when scanning a second tag without having unlocked the screen before (e.g. grap the device from your nightstand without unlooking it and put it in your carholder and unlock it there ) , No support for modded NFC.apk with NFC ON during screen off and tons of possibilities for other false positives.

So, you have to convince me that THIS solution, is what user want ...and that it´s worth all the time (that I don´t have) I would have to put in ...only to get (best case) a "tag lost light" solution.

To be honest, if I had to implement a solution right now, I would spend the time to implement the solution with the modded NFC.apk.
[Samsung Galaxy Nexus] bingunginter:
I can make it turn on bluetooth when nfc is detected, but can it do this : when nfc is detected if bluetooth already on, force connect to device ?
[Samsung Galaxy Nexus] ascsa:
We experimented with this feature a couple of month ago. It worked with some Bluetooth devices, but it didn´t work with other Bluetooth devices. We tested it with several headsets, car navigation systems, PC Bluetooth adapters etc. To make it short: the Bluetooth "standard" is a mess and the Android Bluetooth API is also sometimes a little bit strange. We couldn´t find a reliable solution, therefore we didn´t implement it ... but it´s still on our ToDo list.
[Samsung Galaxy Nexus] abarash:
Hi Ascsa,

I love your app and have been using it for a while (much more lately!). There's one thing I'm struggling with, though: is it possible to re-order the activities within a cycle? If there's a way, I can't find it.

Thanks again!
[Samsung Galaxy Nexus] MaxWantsIt:
Standard Procedure

Hi,

I'd like to set up a standard procedure to set my (Galaxy S3) phone to a default state before setting the specifics of a particular tag.

e.g.

Car

SetDefaultState (volume normal, comms off, etc)

Bluetooth On

Home

SetDefaultState

WiFi On

Is it possible to define a standard procedure that can be called at any time?

I've browsed and searched but can't find an answer.

TIA,

Max

Edit: I've bought Tasker, which can call std procedures, but I'd like to do away with Tasker and buy NFC ReTag

Edit #2: NFC ReTag has templates which could be used as a std procedure, however they will do only half the job because they are not dynamic i.e. if the standard procedure changes then the changes will need to be included in the template and all existing tag procedures will need to be re-created with the new version of the template.
[Samsung Galaxy Nexus] ascsa:
Nope, there is currently no way (except you could always change an activity to another activity and use templates as workaround).

Basically two reasons:

First, it´s incredible difficult on android to find an easy, manageable and reliable way to easily change the order within the current design. We did some testing and even implemented some background stuff to support such a feature, but this usually leads to some awkward solution (move up or down buttons etc. ) and due to reason two we didn´t implemented it (yet?).

Two: NFC ReTag is designed to be as fast and as reliable as possible. Due to this goal , we use an approach we called the fire and forget approach ....every activity is started (except the wait activity) within milliseconds and then the standard android multitasking kicks in ...most times NFC ReTag is already closed, when activity 2 or 3 isn´t even finished ... And we can´t control the standard android multitasking process ... if you have long running activities it usually doesn´t make a difference if you start it as first activity or as last activity (depends on your current workload, other background processes and services etc.) ...Sure, we made some exceptions, for some activities and combinations (e.G. Turn on GPS + start Navigation) and you could always try to control it a little bit via the wait activity, but as mentioned in a lot of cases it wouldn´t make a difference in which order you start your activities ....
[Samsung Galaxy Nexus] abarash:
That makes a ton of sense - thank you for the detailed explanation!
[Samsung Galaxy Nexus] ascsa:
Interesting idea!

I use some "default mode" tag for a long time, but as I understand you right, you would like to use this default mode within other tags ... sure you could use tasker or a template as workaround to do this ...but I have 1 or 2 ideas to improve this ... just let me think and play around a little bit.. perhaps I could implement something like this ....
[Samsung Galaxy Nexus] MaxWantsIt:
Yep, you got it, I want to be able to run a standard procedure from within other tags.

My example was to set up a "default mode" procedure and call that from a tag. However, the concept could be generalised to allow any number of procedures to be created that could be called from any number of tags, providing this is possible within your excellent app.

I will be patient and look fwd to the results of your playing around!

Cheers
[Samsung Galaxy Nexus] MaxWantsIt:
Loving NFC ReTag but a cuppla issues

Me again,

I'm really loving NFC ReTag because it's so easy to use, intuitive and works (mostly!)

I've set up a couple of test tags and love the ability to add cycles. My car set up goes like this:

First cycle:

Turn off all comms

Set sound to Normal

Turn on Bluetooth

Second cycle:

Turn off Bluetooth

So I get in the car and tap the tag for Bluetooth. Tap the tag on the way out to turn Bluetooth off

My meeting tag is similar. One tag tap for Vibrate going in, and a second tag tap on the way out for Normal plus turn on comms to auto check mail etc

It's brilliant but I'm happy to hear suggestions for improvements.

However, there appears to be an issue when turning off WiFi Hotspot because WiFi gets turned on, even though it's specifically turned off in the preceding step. Is this a bug?

Secondly, I set up a template with WiFi Hotspot Off. When I discovered the problem above, I removed the WiFi Hotspot from the template and saved it. When I opened the template for editing it wasn't there, but when I used the template in a new tag then it was there! I deleted it from the tag, but why is it appearing in the first place?

And finally, is it possible to tap the tag and have it activated when the phone (Galaxy S3) is off - not locked, just off? The phone has no security so at the moment I must turn on the phone to use the tag then turn the phone off.

TIA
[Samsung Galaxy Nexus] ascsa:
It´s not a bug, it´s a feature ;) ... turning on WiFi Hotspot automatically turns off Wlan (android standard) .. so I decided to add an auto turn on Wlan when turning off Hotspot ...to solve this, simply move your Wlan off activity to the second step (turn off hotspot + turn off Wlan)... should work without problems.

Hmm sounds like some updating/ refreshing problem, but I couldn´t reproduce this on my international Galaxy S3 so far...could you reproduce it ? and if yes, could you give me a step by step description?.

Yep, it´s possible, but nothing you could do with an app. NFC dispatching is completely done by your firmware (rom).... so you would need a rooted device and an adapted nfc.apk . For more info, please have a look here: http://xdaforums.com/showthread.php?t=1709586

Btw. there are other threads for different Gs3 and firmware versions, and different features ("nfc on when screen off" and "nfc on when screen locked") so be careful, backup and only try the apk specially tailored for your device/ software combination.
[Samsung Galaxy Nexus] MaxWantsIt:
All solved

OK, thx for all that.

Sadly I don't know how to multi-quote on XDA. There's a button for it but clicking it does nothing so your stuff will be italics.

It´s not a bug, it´s a feature ... turning on WiFi Hotspot automatically turns off Wlan (android standard) .. so I decided to add an auto turn on Wlan when turning off Hotspot ...to solve this, simply move your Wlan off activity to the second step (turn off hotspot + turn off Wlan)... should work without problems.

That makes sense and is easy.

Hmm sounds like some updating/ refreshing problem, but I couldn´t reproduce this on my international Galaxy S3 so far...

Mine is a stock S3 from Vodafone Australia

could you reproduce it ?

Just did it again now. I created a 5 line template, called it Default and used a Fake Tag.

I inserted it into a new tag fine, but I had the WiFi Hotspot problem so I deleted the Hotspot line - it was in the middle.

The Default template shows up in my list of tags...............aaaaaaaaaarrrrrrrrrrrrrrrrrrggggggggggggggggghhhhhhhhhhhhhhhh..............there's the problem. I have a template called Default and I have a Tag called Default. The template has 5 lines and the tag version has 4. Ba Na Na Naaaaaa. Solved. Sorry to muck you around.

Yep, it´s possible, but nothing you could do with an app. NFC dispatching is completely done by your firmware (rom).... so you would need a rooted device and an adapted nfc.apk

OK. I've rooted my tablet but don't want to do it to my phone so will live with switching the phone on.

Thx again.
[Samsung Galaxy Nexus] akira018:
Hi,

May I know how to set "Switch on Bluetooth Tethering" by tapping a NFC tag. I can;t find this setting in the apps

Thanks
[Samsung Galaxy Nexus] ascsa:
That´s because it is not implemented.

The Standard Android Bluetooth API is a little bit weird, and we didn´t find a reliable solution ... so we never released such an feature.....A new and updated Standard Android Bluetooth stack was announced some time ago ... we will check if this new Bluetooth stack solves all (or at least some!) of the issues ....In the meantime, you could try the WiFi Hotspot activity for tethering.
[Samsung Galaxy Nexus] kantjer:
Hi buddy I just tried import these task in Tasker but I'm getting "bad data format" error in Tasker.

Can you upload them again in a Tasker 4.x compatible format. I really would like to try them.
[Samsung Galaxy Nexus] artesea:
I've been using NFC-ReTag since I got my GS3 last year. It allowed me to use my work door pass and Tasker to launch my Work Profile.

Since then I've purchased some blank NFC tags and placed them in places like my car, to launch my Car Profile.

However since updating to the leaked 4.2.2 ROM for the GS3 everytime I scan a blank tag I get this

Choose an action

- New tag collected

- NFC ReTag FREE (2.5)

with no "Use once / Always"

I'm assuming it one of three things,

a new app on the phone which needs removing/freezing,

a new policy which doesn't allow NFC tags to trigger the phone without user intervention

a problem with using blank tags

Has anyone come across this before, and got any suggestions. I could programme the blank tags, but I like the idea that it's not fixed to doing just one job and could mean different things from my phone to say my wifes.
[Samsung Galaxy Nexus] kantjer:
Use the "write special NFC ReTAG tag" under more. That will solve your problem.
[Samsung Galaxy Nexus] artesea:
Cheers, hoped it would be something simple.
[Samsung Galaxy Nexus] SCRASHER:
Hi,

is there a way to deactivate the NFC Notification Sound?

Thanks
[Samsung Galaxy Nexus] ascsa:
The sound is made by your firmware/ rom ... nothing any app could change... ...on a rooted device, you could have a look at your NFC.apk (/system/app/) and change the standard sound files (/res/raw/start.ogg and /res/raw/end.ogg) to something silent ...don´t forget to backup your nfc.apk first ..
[Samsung Galaxy Nexus] BeeGee_Tokyo:
GooglePlay says "Not compatible with my device"

I have a Motorola Razr M with NFC, but it is from Softbank Japan and named 201M. Android OS 4.1.2 Original Softbank ROM (device cannot be rooted).

NFC is definitly working as I use it daily in the convinience store and on the Tokyo railways and subways.

Any possibility to get the application on my phone. Any download link other than GooglePlay?
[Samsung Galaxy Nexus] ascsa:
Sorry no, Google Play store is currently mandatory....
[Samsung Galaxy Nexus] ascsa:
Update 2.5.1

Update 2.5.1 just released ...

Update 2.5.1

* Small fixes and design improvements

* New experimental template activity
[Samsung Galaxy Nexus] kaippally:
Sending RFID to web server with tag id.

I would like to read tags and send the tag id to a webserver like the following

nfc.domain.com:1234/?id=abc&lat=12.34567&lon=12.34567

Is this possible.

Thanks.
[Samsung Galaxy Nexus] ascsa:
I think I already answered this on g+ but for all others being curious:

yep sure, use the "website" activity and the placeholder [%UID].. Parameter should look like this :

nfc.domain.com:1234/?id=[%UID]
[Samsung Galaxy Nexus] pwlsrs:
You made a great apps but is any possibility to add activity which will be turned off working apps? When I left car I want to stop navigation apps like gmaps or sygic.

Second things, GPS cant't starts on my xperia t before I accept info about transfer data to google.
[Samsung Galaxy Nexus] ascsa:
Good question!

Android is not designed to let users close apps ...Usually apps will be paused and stay in memory until the firmware needs the resources... and then the firmware closes these apps automatically.....However, some types of apps (navigation, music player etc.) are designed to work in the background, and it´s quite difficult to close these apps automatically ....there is an API but this API is not very reliable (even with some workarounds and root ) ....so we decided NOT to implement such an unreliable feature as a native activity.

Normal apps (without some background services) could be send to pause via a simple workaround : use the "show homescreen" option.

The music player is also usually no problem, because you could use the play/pause toggle and a lot of players will close automatically

For closing navigation apps (etc.) you could create and try a Tasker (3rd party app) task with the Tasker kill app feature, but as mentioned it´s not always reliable.

Not sure, what you exactly mean, but since android 2.3.7 + (as i remember it right ) you need root to toogle GPS automatically. NFC ReTag provides an expert plugin which should be able to toogle GPS without any user interaction (if you have root!) ...

Btw. the standard android GPS implementation is quite good by now... it automatically disables GPS when not needed, and from my point of view it´s not necessary to toogle GPS because of battery drain issues ( ...however, privacy issues could be a different matter ...) ... so personally, I never disable GPS on all my android devices ....
[Samsung Galaxy Nexus] artesea:
Except for the Facebook app which insists on doing a full GPS lookup every time you open the app, just so they can speed up the checkins if you do post a status update.
[Samsung Galaxy Nexus] ascsa:
yep, some apps are annoying ....I would love some standard android GPS black/white lists feature ...
[Samsung Galaxy Nexus] tkellytpa:
Free to Pro Problem Note 2... Andr 4.1.2

First love your app. For some reason after buying pro the app doesn't think I hv it. It is like stuck in free version. The pro button takes me to google.. which allows me to open. Of course I am already in it. I hv tried the following;

1. uninstall both

2. Which caused a cancel purchase. Rebooted phone. Re-purchased and made a point not to import

3. Cleared the data in the app manager.

Respectively,

Tom Kelly
[Samsung Galaxy Nexus] ascsa:
Hi Tom, sometimes the Google servers are a little bit slow and the server authentication needs some time (nothing we or you could do, except to be patient) ... Beside that, I would recommend to go pro (buy via Google), import the tags from the free version and then uninstall the free version (not mandatory, but minimizes possible confusions) .... Don't forget to rewrite your tags with the pro version (special nfc retag tags & activity tags, if you have created such) because these will still point to the free version...

If you have further questions/ problems, please don't hesitate to contact me via this forum, PM or email ;)
[Samsung Galaxy Nexus] ascsa:
airplane mode broken in JB 4.3

FYI: Android JB 4.3 broke (AGAIN!...after 4.2 needed root) the airplane mode "API" ....not sure if I could hack around this ....The good thing is, that the app doesn´t crash, so I decided to have a second (3rd/ 4th...) look at it, before I will update the app (and probably block the airplane mode for 4.3) ...

btw.: Didn´t found other 4.3 issues yet ....So, if you found other 4.3 issues, please report it here or send me a PM or an email via the playstore ...
[Samsung Galaxy Nexus] ascsa:
Fixed Airplane mode issues with JellyBean 4.3

Wooohooo! I think, I fixed the Airplane mode issues in JB 4.3 !! Hacked around the 4.3 restrictions and published an update for the NFC ReTag Expert plugin (Version 1.2.1 !!!) a couple of minutes ago ... all you have to do (beside being rooted!) is download and install the Expert plugin from playstore and the airplaine mode should work ... Afaik, Nfc Retag is the first and currently the one and only app who solved the airplane mode issues in JB4.3 .... enjoy and please report back !
[Samsung Galaxy Nexus] tremblayseb:
Is there a Windows Phone similar app?

Hi

is there a similar application for windows Phone?
[Samsung Galaxy Nexus] ascsa:
NO!

;) OK, the long version:

We frequently look into other operating systems. The windows phone os simply doesn´t support settings and functions triggered by 3rd party apps as it is possible within android. It´s, in fact, very difficult even with android and it´s getting harder and harder with every android version, So, as long as the windows phone os doesn´t provide some additional APIs, only very simple standard NFC activities (email, vCard, text etc.) are possible.
[Samsung Galaxy Nexus] Lark123:
I am trying to use ReTag in conjunction with my own Tasker generated app. I am trying to use your simple broadcast intent but it fails because I believe Tasker doesn't like the String Extras to be in upper case, i.e. RETAG_UID etc. If I manually send the same intent from a test task using retag_uid instead then everything works as expected. Is it possible to configure ReTag to use lower case, or does anyone have any insight into how I could configure Tasker?
[Samsung Galaxy Nexus] ascsa:
Hi Lark, I answered your email, before I saw your post.....

For all others being curious, here is my answer ;) :

"Yes, I remember some issues with the upper case variables in Tasker. Because of this, the NFC ReTag Tasker task ADVANCED activity (lab) uses lower case for the Tasker variables ....I'm not familiar with the tasker app factory, so I wonder, if you just could use the tasker task advanced activity instead of the simple broadcast intent?....However, currently there is no lower case option available within ReTag ...but as a workaround I probably could add an additional string extra with lower case or something like that (not top priority, but perhaps I could include this within the next update)."
[Samsung Galaxy Nexus] ascsa:
Update 2.5.2

Update 2.5.2 just releases .... contains some small fixes and Jelly Bean 4.3 adaptations .....

AND I included (quick and dirty ;)) a compatibility setting for the lower case variables mentioned above --> have a look at the advanced settings ;)
[Samsung Galaxy Nexus] Lark123:
Thanks for this. Tested and working well. I'm as grateful as I'm impressed :D
[Samsung Galaxy Nexus] ascsa:
No problem :good: ...

The 2.5.2 update was already scheduled for yesterday, so after I did the last small fixes, I decided to add a few lines of uncritical code, did some additional testing and here we go ....probably a lot easier than changing Taskers variables handling or hacking around the Tasker app factory limitations ...and also make the ReTag Broadcast a little bit more flexible. I have some additional ideas on my ToDo list, for the ReTag Broadcast, but that´s something for one of the next major updates ;)
[Samsung Galaxy Nexus] 320flyboy320:
I've been able to get NFC ReTAG to do the following (for when I leave the house);

Airplane Mode (Plugin + root) OFF

WLan OFF

Bluetooth ON

But when I do the reverse (like when I come home);

Airplane Mode (Plugin + root) ON

WLan ON

It turns on airplane mode, very briefly turns on WLan, but then immediately turns it off again, like airplane mode is taking over again. I then tried adding a delay of 3 seconds between turning airplane mode on and turning WLan on, but it didn't seem to follow the correct order. It waited 3 seconds, then seemed to turn on WLan briefly, and turn on airplane mode. It almost looks like the order of the actions isn't being respected. Strange thing is if I tap the tag again, it will then turn on WLan...

At any rate, I just can't seem to get it to turn on airplane mode (to save battery over night as i have a weak signal), and just have wifi on.
[Samsung Galaxy Nexus] kantjer:
This has nothing to do with this app. Airplane mode turns off all transmission including WiFi so you can never have WiFi on in airplane mode.
[Samsung Galaxy Nexus] 320flyboy320:
Well it was working fine for me in 4.2.2, but now I've updated to 4.3, NFC ReTAG can no longer do it. I can do this by using Power Toggles, all I do is select airplane mode, and then select wifi, and it turns on airplane mode, and turns on WiFI...works just fine. Also, NFC Task Launcher was able to do this prior to 4.3 as well.

So yes you can have airplane mode on and wifi on at the same time.