yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ascsa:
Hmm, the standard android car mode is something I do not understand .... I remember the old car mode implementation (2.3?) with a dashboard and some text-to-speech features, but to be honest, I think Google screwed it up on KitKat and "L". Some manufacturers (like samsung) and roms implemented an own (non-compatible?) version, but from my point of view this is one of the weakest points in android.

However, NFC ReTag has a native Car Mode activity (Start/Launch section) which controls the standard Android car mode (BETA, but should work without problems ;) )... so no need for Tasker for this feature.

Anyway, if you want to use Tasker, remember to enable the Tasker background service .... --> little Tasker symbol in your notification bar!

Still not working ? If the background service + allow external access is enabled, you could check if ReTag has the run Tasker Task permission .... and if this still fails, I remember some reports with issues with the task name .....remove blanks and all other weird characters (rename the task to test1 for example) and try again!.
[Samsung Galaxy Nexus] 12gage:
Thank you, I searched the thread and saw that was a solution most of that I tried except renaming and that didn't seem to help. I tried the built in car mode and it didn't work. It's there anything else I should attempt? Thanks in advance for your help
[Samsung Galaxy Nexus] ascsa:
Hmm, the Tasker task activity is pretty straight forward from ReTag point of view --> fire the task name to Tasker and that´s it.....

so if it´s not working, it´s probably because the task do not reach Tasker (due to permission, allow external access, tasker disabled...) or Tasker could not handle the task ( btw. power toggles is designed as a Tasker plugin and uses some other mechanism). Not much I could do on the ReTag side, but if you could provide a log (here or pm or email) I will have a look and try to sort this out for you.
[Samsung Galaxy Nexus] ascsa:
Update 2.12

update 2.12 just released to google play ....

Hmm, usually there is a feature update every couple of weeks for ReTag .... this one took a little bit longer, because version 2.11 is absolutely stable and I did a lot of other cool Android stuff in the meantime... some ReTag related, some NFC related and some completely unrelated ....not sure if I could / should pack everything into NFC ReTag or release some little spin-off apps ...Android L has also some new potential and a completely new design and some major redesign for ReTag is still on my to do list ....

However, I decided to release a small 2.12 update today and keep major changes for a future 3.0 Update (still a lot to do till release). The 2.12 update brings a new boot trigger, some compatibility setting for alternative TTS engines, updated libs and some small tweaks and bugfixes ...

Update 2.12 (2.12.x = fixes)

* New Boot trigger

* Compatibility setting for non-standard TTS engines

* First Android L adaptations

* Tweaks and bug fixes

BTW. did somebody realize that the Bluetooth trigger in combination with Android L and the G Watch works right out the box :cool:
[Samsung Galaxy Nexus] 12gage:
Thanks for your help, how do I check for permissions? Tasker is enabled, external access is allowed, and when I hit simulate it works. Could it be that I wrote to the tag and added the car mode activity afterwards? I have a few activities set to run and the lastly added car mode is the only thing not firing. If so is there a way to erase and rewrite the tag or do I need to get Pro for that?
[Samsung Galaxy Nexus] ascsa:
Aaaargh, how did I miss that? ....Yes, sure after writing an activity tag (write option within tag edit screen), the activities in the database are irrelevant ....only the activities on the tag were fired ... so adding activities after writing an activity tag does nothing, unless you rewrite the tag ....soo, please just rewrite the activity tag ;)

No, need for pro ... ReTag policy is to enable all features in free (but limit tag/trigger count), so you can test them without any risk or trouble.
[Samsung Galaxy Nexus] 12gage:
Thank you sir, I don't need to erase first or will just hitting "write"again take care of it?
[Samsung Galaxy Nexus] ascsa:
Yep, just hit write.
[Samsung Galaxy Nexus] 12gage:
Thanks that worked, now I do have a "New Tag" or "Retag" selection pop up every time the tag is scanned now. Even if I select retag and hit "always" instead of "one time" it still pops up, any suggestions?
[Samsung Galaxy Nexus] ascsa:
Hmm, you shouldn't get this pop up, unless you manually disabled the activity tag receiver (advanced settings), the tag isn't written correct or your firmware is buggy ( "always/default" not working is a firmware bug, too)...... However, please check the settings, rewrite the tag (btw. An activity tag in combination with Tasker doesn't make sense, so you can just write a special nfc retag tag -> more button)... still not working? - > disable the useless "tags" system app via the standard Android app info settings.
[Samsung Galaxy Nexus] khaytsus:
BTW, I had an issue after updating Tasker recently, NFC ReTag was just showing (not sure of exact text now) Tasker Permission Error.

Per suggestion from Pent (Tasker dev), I reinstalled NFC ReTag and fixed it. Not sure why that happens, he says it's an Android bug. Luckily being rooted etc, Titanium Backup made the process simple.
[Samsung Galaxy Nexus] ascsa:
Yes, Pent is right. It´s a well known Android bug. ReTag used a workaround to solve this for a long time .... Unfortunately, Android L will give you a Play Store error with this workaround enabled, so you could install either ReTag or Tasker with this workaround enabled...

Android L is a Preview, but a lot of people seems to use it as everyday rom, so I disabled the workaround with the last update and added the "Tasker permission error" message to identify easily the problem ...It´s not the final solution, but as it´s currently not possible to release a L specific update and the L Preview is still under development (there is already a official error report for this Android L issue), I think, it´s the best trade-off right now.
[Samsung Galaxy Nexus] khaytsus:
I'm on 4.4.4, not sure what happened.. Went from latest beta Tasker to the latest market version (ie: out of beta) is when it happened.

I didn't try the workaround, although I did see that message. I thought maybe that was only for "some" devices. What does the workaround do, re-issue the permissions request or something? If that's possible...
[Samsung Galaxy Nexus] ascsa:
No problem, I know exactly what happened ;) ... And no, the Tasker fallback setting and the message in ReTag has nothing to do with it ....

The (now disabled) workaround automatically fixes the Android permission issue during installation ;) ...without this workaround Tasker has to be installed before ReTag ..--> .therefore re installing ReTag (backup database first!) will fix it
[Samsung Galaxy Nexus] tigerknight:
NFC ReTag to unlock device

The Moto Skip caught my attention, and I was excited until I learned it was for Motorola only devices and I have a Note 3 (SM-N900A - Android 4.4.2). I've been looking for an alternative and this seems like a great fit, but there are still a couple issues if I understand the situation right:

NFC only enabled after unlock

root and special APK required to modify behavior

In looking through the NFC ReTag app (even the expert plugin which mentions needing root for its functions), I don't see anything about unlocking the phone - did I just miss it?

What's the best course of action for me to take from here to get my Note 3 unlocking with an NFC tag so I don't have to retype in my password every time the screen goes off? I can find root and bootloader utilities for my Note 3, no worries (mentioning that since this is a Nexus forum). Just looking for general direction input.
[Samsung Galaxy Nexus] khaytsus:
Are you using Exchange Security or something, forcing you into a password? Otherwise you might look into Delayed Lock, so at least you wouldn't have to do it immediately, you can have it lock after 5 minutes after the screen goes off or such.

But no, stock phones NFC is disabled until the phone is unlocked, presumably for security reasons.
[Samsung Galaxy Nexus] tigerknight:
I do have it set to 3 minutes of delayed lock, but when I'm busy during the day it sure seems like 'instantly' because I don't have my phone in my hands all the time and my password is moderately long.

About my other question though - assuming I could get in and root the phone successfully and get NFC to be active anytime the screen is on, does NFC ReTag have an action to unlock the device that I missed seeing?
[Samsung Galaxy Nexus] ascsa:
Nope, Retag has no native unlock feature, because from my point of view, every workaround via an app isn't stable enough to mess with this important security feature....

If you want to try it with an app, you could use Tasker and the secure settings plug in... The keyguard activity, if I remember it right.

However, if you want to do it right, use the xposed framework and the Lockscreenoffenabler module to modify your firmware ... This module also has an option to register a tag for unlocking your device...

BTW. Be aware that ReTag supports the tag lost message from this module, so if you don't want to use the tag lost feature, disable the tag lost support via ReTag settings...
[Samsung Galaxy Nexus] tigerknight:
Thanks for all the info, very much appreciated.
[Samsung Galaxy Nexus] Sves:
Any option to connect to a particular bluetooth device via nfc tag? I am close to being desperate - I have 3 bluetooth speakers in my flat so all I want is to be able to connect to them using nfc.

But, my god, this looks like an impossible thing on Android.
[Samsung Galaxy Nexus] gt1street:
Maybe you'll have a solution to my problem though it's not directly connected to the NFC ReTag app.

I have it installed and configured and working properly, but when ever i scan an empty tag (even though i have a task for it that is working) I get a selection menu on my Nexus 5 (4.4.4 Stock, with Root) that deifies the whole purpose of the automated task since i have to choose between the two options of "New Tag Collected" and "NFC ReTag FREE"

Anyway to disable the new tag thing ? (Tried the xposed module for it, but it does not work)
[Samsung Galaxy Nexus] ascsa:
It´s more a standard bluetooth issue than an android issue :eek: I did some testing a couple of month ago and even implemented this feature within one of the testing prototypes, The problem was, that is was working fine with some Bluetooth devices, working with issues with some other bluetooth devices and not working at all with a third kind of bluetooth devices .... nothing I could influence via the app ....so I decided to NOT implement it within the productive app.

However the Android bluetooth stack had some major redesigns since then, so I will eventually have a second look on that, if I find some spare time.
[Samsung Galaxy Nexus] ascsa:
Yep, easy!

- With writeable tags, just write a special NFC ReTag tag (more Button).

- With non-writeable tags just disable the absolutely useless "Tags" system app via the App manager (Android APPS Settings -> ALL)
[Samsung Galaxy Nexus] Sves:
thanks for your reply! I could make it work with Tasker + 2 modules (nfc locale plugin + Bluetooth Auto Connect). Works fine :)
[Samsung Galaxy Nexus] ascsa:
Thanks for the feedback. Nice to hear you found a solution for your device ... yep, with bluetooth auto connect you should be able to connect a specific device after switching on bluetooth ...........not sure, why you need another plugin and tasker for this, but if it´s working fine for you, feel free ;)
[Samsung Galaxy Nexus] ascsa:
Anyone with an OnePlus One and problems with ReTag?

Feedback (problem / no problem) highly appreciated!
[Samsung Galaxy Nexus] Im ZyKloN:
Just downloaded your app the other day. I'm new to the whole NFC scene so I downloaded your app for the tasker integration. I have everything set up, but it only seems to work while your app is running in the foreground. Is this normal? I couldn't find anything about this in the app description, so I'm not sure if this is a bug or intentionally designed into the free version. Any insight would be appreciated.
[Samsung Galaxy Nexus] khaytsus:
Nope, no reason to have the app in the foreground, in fact that'd take away 95% of it's usefulness ;) However, it does not work unless the phone is awake and unlocked, is that maybe the issue?
[Samsung Galaxy Nexus] ascsa:
Nope, ReTag is designed to work completely in background... In fact, ReTag doesn't even use a background service to minimize battery drain... However, seems that the nfc dispatching doesn't work on your device.... With writable tags, just write a "special ReTag tag" (more Button), with write protected tags, just disable the useless "Tags" system App.
[Samsung Galaxy Nexus] Im ZyKloN:
"Write error. Nothing done. Try again!" :(

Also, what do you mean tags system app?
[Samsung Galaxy Nexus] ascsa:
Check if your tag has enough memory and do not swipe the tag... Writing a tag takes some milliseconds. If the tag has less than 99 bytes memory, choose a write option which needs less memory.

A system app called "TAGS" ....

You didn't mention your configuration (device, software, tags) and you didn't describe what happens when in background, so I assumed some dispatching problem usually caused by this pre-installed system app called "Tags" :0)
[Samsung Galaxy Nexus] Im ZyKloN:
I bought these tags (apparently I can't post links, so it was a 12 pack from Tags for Droids off Amazon) and it says they have a writeable 137mb memory, which is far more than the fallback information I was attempting to write.

My apologies, I made an account to post on this thread and filled out my phone information in my profile, I thought it displayed that information in my signature. I'm using an HTC One M8 with stock 4.4.2 android.

I just tried to rewrite the tags and it works (I was swiping the tag instead of holding it down). Though now when I test the tags, I get a black screen pop up with the text "New Tag Collected" then "vnd android.nfc://ext/nfc_retag:tag". Does this have to do with that Tags system app that you mentioned?
[Samsung Galaxy Nexus] ascsa:
Yep, sounds like the Tags App....shouldn't be a problem if you use the default write option (instead oft the fallback option).
[Samsung Galaxy Nexus] Im ZyKloN:
Using the default write option it only opens NFC Retag and skips my tasker task.
[Samsung Galaxy Nexus] ascsa:
Hmm, weird ...do you have some empty cycles? Tasker allows external access and is enabled? No Tasker permission error?
[Samsung Galaxy Nexus] Im ZyKloN:
What are empty cycles?

External access is allowed.

No permission errors...well, technically not true. When I first tried to set up the task I got a tasker error that said something along the lines of "cannot allow external access", but I only got it once and could not duplicate the error.

The only thing I'm writing to the nfc tag is a single task that controls a boolean variable, which is the context for my Driving Profile.
[Samsung Galaxy Nexus] ascsa:
An empty cycle is a cycle without activities... A common issue is to create additional cycles and then forget about them and wonder why nothing happens.... Seems not likely in your case....

Did you install Tasker or ReTag first? ReTag first: reinstall retag!

Does the Tasker task work if you start it manually?

Also Tasker must be enabled (Tasker needs a background service to run all the time)....

Beside the above mentioned issues, I could not imagine an other issue...

Could you provide a log file if the issue persists?
[Samsung Galaxy Nexus] Im ZyKloN:
I've had tasker for a while now, and multiple other profiles running without issue. So tasker is running in the background just fine, and I installed Retag after tasker. My task runs just fine if triggered manually.

I've never had to use the system debug option, where do I get the file after I check it? I couldn't find it in my tasker folder.

---------- Post added at 09:10 AM ---------- Previous post was at 09:00 AM ----------

Hold on, I fixed it. I started fiddling with Retag settings and ended up just resetting everything, then tested my nfc chip again and everything works properly.

I guess I accidentally clicked something while looking thru the advanced settings. Might I suggest some sort of error message in this case for your app? Lol

Okay, thank you for your time. You've definitely earned a customer :)
[Samsung Galaxy Nexus] lintinlo:
nfc retag circle doesnt work

Hello dear community,

I have a small problem and do not come on. yesterday bought nfc retag because the software is really good. and have my nfc tags described, but the circle is not described. I just get the primal part of circle described or the last. So if I put my phone on the nfc tag happened the first step. I put it again on the nfc tag happens again the first step and not the second.

what am I doing wrong? it is up to the hardware?

my hardware:

OnePlus one

OS 4.4

nfc retag per

Tags:

DESFire ev1 4096byte

ntag216 888byte
[Samsung Galaxy Nexus] ascsa:
Nope, it isn´t your hardware. The one plus one has issues with some Topaz tags, but afaik Desfire and NTAG216 should work fine.:good:

However, identifying your issue is pretty simple: activity tags do not support cycles! only the current cycle is written on the tag ...--> it´s not a bug, it´s a feature ;) .... Writing activity tags only makes sense, if you want to use this tag with different devices .... and cycles usually doesn´t make sense if you use different devices ....

So the solution is also pretty simple: just write a special NFC ReTag tag (more Button) instead of the activity tags and the cycles will work without problems ....:cowboy:
[Samsung Galaxy Nexus] lintinlo:
I do not quite understand! My project is timesheet with the NFC tag. When I put my phone in the morning on the nfc tag then you want to begin recording. Evening at the end of the work I put my phone on the NFC tag and the recording is stopped.

Works in conjunction with the APP "Zeiterfassung" really good.

If I add the + New trigger _ _ -> +APP activity there then -> checkin (timestamp) -> cycle -> checkout (timestamp -> write day

Result is writing only the 2/2 step with cycle but the NFC Tag do only the second step.
[Samsung Galaxy Nexus] ascsa:
With NFC Retag you can use non-writeable tags and writeable tags ... with writeable tags you can have 2 kinds of tags written:

1.) "special ReTag tags" : no activities are written onto the tag, it just writes some dispatching info on the tag and the app internal database stores the activities and handles the cycles --> you can write them via the more Button on the first screen ("MEHR" in german) --> DEFAULT (because it has a lot of advantages over writing activities on the tag), ALWAYS use this, except your use case relies on activities on the tag.

2.) Activity tags: you write them via the Tag edit screen and they store the activities of the CURRENT cycle on the screen onto the tag ....you can´t use cycles with this kind of tags, because you would have to re-write the tags every time you scan the tags --> would likely cause some writing errors and probably this would not work at all. --> DON´T USE THIS, IF YOU NEED CYCLES! (but it´s great e.g. for sharing your WiFi credentials ;)

So bottom line: Just open the app --> choose the red "more" (mehr) Button --> choose "write special ReTag tag" (Schreibe special ReTag tag) --> Tab your "Zeiterfassungs" tag against your device and let ReTag do the magic ;)
[Samsung Galaxy Nexus] damigail:
dual sim

Hi,

I have a dual sim phone (ZP998).

I would like to switch off/on only 1 of 2 sim card with an NFC tag

Can you developpe some things for that ? :confused:

Thanks for this super application ! :good:
[Samsung Galaxy Nexus] ascsa:
Hi, very interesting use case! Unfortunately I never had an Dual Sim Device and afaik standard Android doesn´t have native dual sim support (weird! :eek: ....)........... So I don´t think, I could develop something for that ....

However, I used a "multi-sim "?!? configuration ( = 1 sim with 2 different numbers) and a different multi-sim (again'?!?) config (= several (up to 5?) Sim -cards with the same number ) in the past. Both configurations could be controlled by USSD-codes --> something like calling *123# via the standard dialer. Soooo, if you could control your dual sim via USSD codes too, you could easily use ReTag and the Call activity within the Nfc ReTag Expert Plugin ....

BTW. USSD codes are fossils from mobile stone-age but you can still trigger some nice features (like call forwarding, mailbox control, usage stats etc. (as always, depends on your carrier)) with them :cool:
[Samsung Galaxy Nexus] damigail:
Thanks for your quick answer.

Good idea... If i found something, i can inform you.
[Samsung Galaxy Nexus] damigail:
find some think

I think I found my solution to drive the dual sim. :D

But I do not know how to connect with your application. :confused:

Is it possible to simulate a press widget ?

http://xdaforums.com/android/general/review-mtk-control-dual-sim-management-t2875940
[Samsung Galaxy Nexus] ascsa:
Nope, afaik it´s not possible within android to simulate a click on a widget. You can launch an app or even launch a specific app activity (although, this only makes sense if the target activity is designed to be launched !) with ReTag, but you can not simulate a widget click .... Android has pretty good app-to-app communication capabilities, but the receiving app must provide an interface (typically a broadcast receiver) ... ReTag already provides a simple broadcast activity, so theoretically other apps could hook in, but the other app has to implement it.

Bottom line: App-to-App communication is simple, but nothing any sending app could implement without some API within the receiving app.
[Samsung Galaxy Nexus] damigail:
Thank you.

It work with tasker ! :D
[Samsung Galaxy Nexus] pesmi:
browser should popup

I have a NFC tag with a URL on it.

It is meant to be a 'business card'.

Without 'NFC retag' installed on my Phone, everything works fine. When I tap the tag, the browser opens with the url that is on the tag.

But with 'NFC retag' installes on my Phone, that app opens when I tap the tag.

So the tag is now useless.

Strange thing is that when I tap a tag with a 'trigger command' on it, there is no problem.''Trigger' handles the command and 'NFC-retag' doesn't show up.

Is there an error with the NFC-tag (with the URL on it)?

is it a matter of 'priorities' or so?
[Samsung Galaxy Nexus] ascsa:
Hmm, sounds as it works as designed ... The Android NFC dispatching is a little bit tricky and completely done by your firmware , but I guess you have the following situation:

- your Trigger tag is properly written so the dispatching works ...

- your url tag could not be properly dispatched so ReTag takes over (as designed :p)

However, you should be able to solve this pretty easy: Have a look at the ReTag settings ==>> advanced settings and disable the "NON NFC ReTag tags" and the "NFC aggressive mode" receivers ---> your url tag should work fine !:cowboy:
[Samsung Galaxy Nexus] pesmi:
Thanks! it works!

I not (yet) fully understand the settings, but this helps me very much!
[Samsung Galaxy Nexus] mydonose:
I need your Help

Hello community , I have the following problem : I have a Bluetooth coupler in the car and a Smartphone Holder with NFC tag . If I put my Galaxy S4 in the holder , then automatically starts Bluetooth , NFC is turned off and music app starts . NFC is therefore switched off so not the popup comes with each display-unlock . Now to my question : How do I have it automatically adjust the NFC turns on again at a separate Bluetooth connection and Bluetooth turns off again ? Thank you for your help .
[Samsung Galaxy Nexus] ascsa:
Hi mydonose,

just add a Bluetooth disconnect trigger (more Button --> Bluetooth trigger--> disconnected) for your Bluetooth device and add the NFC ON and Bluetooth OFF activities.:cool: