yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ascsa:
Hi Jamolah,

no you don´t do something wrong. Ringer mode silent should disable vibrate and ringer volume....and it works fine on all my testing devices (no note 2 ;-( ...but GS3 with stock 4.1.1 should have the same touch wiz version ....)

Have you added a additional "set ringer volume" activity? (--> this is not necessary, and android standard, automatically activates vibrate, even if you set ringer volume to 0....)
[Samsung Galaxy Nexus] Jamolah:
Yes my ringer volume is set to 0. See attached screen shot
[Samsung Galaxy Nexus] Avalonnw:
Too complicated :(

Tasker has key input plugin even, but Tasker is a bit too much for my feeble mind, I afraid :)
[Samsung Galaxy Nexus] ascsa:
Then please delete the ringer volume 0 activity ...as mentioned ringer mode silent automatically set the volume to 0 and when you manually set it to 0, vibrate gets activated again ... a little bit odd, but that´s android :eek:
[Samsung Galaxy Nexus] Jamolah:
Thanks, that worked.
[Samsung Galaxy Nexus] Jamolah:
When I tap an NFC tag it brings up the List of activities. And I have the Don't Show pop-ups checked.

Is there a way to disable the list of activities from showing up.
[Samsung Galaxy Nexus] ascsa:
Hmm, strange ...the mute pop-up setting does exaclty this .... Are you sure it is checked ?

Perhaps uncheck it and then check it again ....
[Samsung Galaxy Nexus] Jamolah:
Ya I figured that too. I tried checking and then unchecking and same behavior. When I touch the nfc tag it brings me to nfc app screen.

I did try to check then uncheck that didn't work. I'm using a note 2 on stock Rogers ROM
[Samsung Galaxy Nexus] ascsa:
App screen? not the activity pop-up? -->Hmm, sounds like the app is not closed properly... Could you please try to close NFC ReTag via the BACK (NOT HOME! ) button and check if the problem persists ?
[Samsung Galaxy Nexus] Jamolah:
Ya so that worked. Thanks
[Samsung Galaxy Nexus] ascsa:
You are welcome! ... and thanks for your continuous feedback!

I will have a look at this BACK/ HOME behavior and perhaps I could change it for the next update .....
[Samsung Galaxy Nexus] shaggy-h:
I just discovered this app today. It's great - simple and effective, love it! I'm currently just using it to launch the "Oyster Master" app when I touch my Oyster card (London public transport card) to my Galaxy Nexus (running JB 4.2.1). One immediate problem is that (as discussed in this thread already) there's no "default" option on Android for background intents. Because I have another app "NFC TagInfo" installed that also catches these intents, I'm always forced to make a choice between launching ReTag and TagInfo. The workaround of using a writeable tag doesn't help me here, since I want to use the Oyster card itself as the trigger, not some other writeable NFC tag. Fortunately TagInfo lets me disable it from launching when a tag is detected. This is OK since I can always manually launch TagInfo if I want to scan another NFC tag, however I can think of a new ReTag feature that would enable a better solution...

Would you consider adding a "Default" tag to your application? Once configured, this special tag would trigger whenever an unrecognised tag was scanned (rather than show the current "Tag Detected!" dialog). This would allow me to launch Oyster Master when I scan my Oyster card, but if I scanned any other NFC tag then I could use ReTag to launch NFC TagInfo instead. Obviously with a "Default" tag in place any further new NFC tags would need to be set up in ReTag by launching the app manually, which I don't think is too much of a problem?

What do you think?
[Samsung Galaxy Nexus] ascsa:
Hi shaggy-h, thanks for the feedback!

Unfortunately the tag dispatch process depends completely on your firmware ....every app can define filters, but if two apps define the same filters, the firmware will show you the app chooser ....standard android even hasn´t the option to choose a default app in this case,but e.g. samsung added such a feature within their latest firmware versions ...however, not much an app can do (if you use write protected tags ), since this is done completely by the firmware before any app is started ...(--> except that any good app, will allow you to disable the background dispatching) .....

I think, I understand your request ... currently nfc retag has two "launch modes" : "Edit-mode" and "Auto-mode" and you would like me to add an additional mode --> do something else with a new tag (e.g. launch TagInfo --> be aware that this would only launch the app, you would have to scan the tag again..) ... from a technical point of view, this could be done ... in fact, I have some cool ideas for additional launch modes already on my list, but I´m not sure if the "normal" user could handle these additional launch modes (--> not all are xda-developers :crying: ... and currently a lot of users are already overwhelmed by the new nfc technology ...) ...

However, this would be some mid-term development and I will have to find a manageable solution for this ... So I will keep your request in mind and put it on my mid-term ToDo list ....
[Samsung Galaxy Nexus] shaggy-h:
Hmm, it's not clear to me whether we're talking about the same thing or not! :) Let me try to clarify what I meant... I don't consider this to require a new launch mode. Here's how I would see it working:

Currently you have an "Add test tag" button. Suppose you added a new button called "Add default tag". This would work in exactly the same way, except instead of generating a tag ID like "FakeID xxxxxxx" it would create a tag with a special ID called "Default". The user could then assign activities to that "Default" tag in the same way they can currently be assigned to a real or fake tag. With me so far?

OK... As things stand currently, when a tag is scanned the Android OS triggers your "Auto-mode" code. Presumably your code checks the ID of the tag that was just scanned against its database and tries to find a matching ID so it can run the activities assigned to it. If it doesn't find a matching tag, your code instead displays the "New tag" dialog and allows the user to create a new entry for that tag. My suggestion is to add some logic to see if there is a "Default" tag configured in your database and if so run that. If there is no "Default" tag then just fall through to the existing behaviour of showing the dialog. Does that make sense? Of course user interface and implementation details might be different depending on your preferences and how things really work under the hood, but I hope it is now clear the sort of thing I'm looking for.

I don't quite understand what you're getting at when you say "be aware that this would only launch the app, you would have to scan the tag again". Does that mean I'd have to move the phone away from the tag then back again once NFC TagInfo was launched by ReTag, so NFC TagInfo could then read the tag for a second time? If so, that would indeed be a bit awkward :(
[Samsung Galaxy Nexus] ascsa:
No problem ;), i´m sure we do ...

yep, it´s not required, but it´s much more comfortable (enable/ disable via settings, without to have create and delete the "default" tag) and will better fit into the current app.

understood ... not sure, if I would implement it this way ... perhaps saving this "default" tag as a template would be better ... but that is only a minor implementation detail ;)

as mentioned i would prefere an additional launch mode, to keep it manageable and not to confuse the majority of users ...but the logic is quite similiar ...

yep, exactly! ... you would have to tap the tag again with the taginfo app open ....Remember, the tag dispatching is done by the firmware and the background dispatching of Taginfo is disabled (else you wouldn´t launch retag ...) ... without some major hacking (not sure, if it is possible at all) TagInfo wouldn´t get the tag content ....so for your specific use case a lot of work, without the desired result ....but however,I like the general concept ...
[Samsung Galaxy Nexus] shaggy-h:
Yep it sounds like we do, thanks for clarifying :)

Ah I see, ick... I thought there might be an easy way to start the relevant TagInfo activity by just passing the NFC intent through to it but I guess not. Thanks again for the clarification and the great app!
[Samsung Galaxy Nexus] Jamolah:
Is there a way I can choose a different keyboard depending on which tag?!
[Samsung Galaxy Nexus] ascsa:
I'm not aware of a possibility... But to be honest, I never thought about that...
[Samsung Galaxy Nexus] Jamolah:
I never thought about it either until I got a note 2. Samsung has one handed operation feature which shrinks the keyboard. But when I'm at work I want to use swiftkey flow keyboard (which doesn't have one handed keyboard operation)
[Samsung Galaxy Nexus] ascsa:
Update NFC ReTag 2.2

Update 2.2 released within google playstore a couple of minutes ago ....

* Beam your tag cycles to other devices

* Import beamed tag cycles

* Minor improvements

* Fixes
[Samsung Galaxy Nexus] ascsa:
Hmm, seems that the sony LT26i (xperia s) has some problems with the update ... trying to fix it between some x-mas party ;)

EDIT: OK, uploaded an update (2.2.2 ! )....did some minor corrections to make it bulletproof ....bug report show sony devices only ... mainly LT26i ... not sure if it is a specific sony bug ....couldn´t test on a xperia s so far, so all feedback (especially from sony users !) is welcome !
[Samsung Galaxy Nexus] HinHammer:
Set timer to 15 minutes

Hi,

Thanks for a great app, it's great.

I miss one thing, i would like to set a timer for 15 minutes, during my nap, or half an hour during email reading, on my Xperia V.

I tried the "set alarm in x min" activity which gives me this functionality, but it also gives me one alarm entry each new alarm time filling up the alarm list.

It looks liket there was a functionality like this in v1.5 but it disappered? Any possiblities to add it again so I can have a power nap and be sure not to oversleep?

Cheers
[Samsung Galaxy Nexus] ascsa:
Hi HinHammer,

the mentioned v1.5 timer functionality is exaclty the "set alarm in x min" activity and yes it´s annoying to fill up the alarm list.

Background: Android had no standard timer functionality till version 4.2 ...and from my point of view, the overall alarm API is very poor. ...so nearly all manufacturers added an own version, a lot of 3rd party apps were written and everybody implemented it a little bit different ....after experiementing with some different approaches (including writing my own little alarm/ timer app and trying to handle as much as possible different implementations ) I decided to use the standard api, because everything else, wasn´t userfriendly, reliable etc. either... and live with the disadvantages .... but you´re right, version 1.5 is nearly 6 month ago, so I should have a second look at the alarm and timer feature .... perhaps i could find a better solution now ...as soon as I find some sparetime, I will have a second look at this.
[Samsung Galaxy Nexus] ascsa:
Still error reports ...mainly from some Sony Xperia S LT26i ....couldn´t reproduce the error and no additional feedback from users --> so please write an e-mail, pm or use this thread, if you have issues (or if it´s working fine on your sony device!) ....I suspect a bug within a rom ...but without some additional feedback, it´s impossible to track this down ....:cowboy:
[Samsung Galaxy Nexus] m.klinge:
Hi :)

Working flawlessly in my Xperia s with custom rom :)

//M

Sendt fra min LT26i med Tapatalk2
[Samsung Galaxy Nexus] ascsa:
Thanks for the feedback ... supports my suspicion that this is rom related and that only a minor number of users is affected ... anyone with additional feedback (rom, android version would be nice ;)) ?
[Samsung Galaxy Nexus] admin@xda:
Crash on Alcatel OT 922

There is a budget phone with NFC - Alcatel OT 922. Android 2.3.

NFC Retag crashes after pressing 'Add Tag' button. Phone is brand new out of the box with no pending updates for its Android. Have sent crash information to Google (?) or developer (?) in crash dialog.

Believe it is important to fix it on this particular model as it is breakthrough of NFC to cheap android phones. Plan to use it with my kid to auto SMS when coming to school/home. Also considering reverse application - when phone is fixed in the classroom and coming/going kids are touching it with nfc tags to send SMS to their parents. Nfc tag from tube ticket cost zero.

May participate in troubleshooting-debugging if needed.
[Samsung Galaxy Nexus] ascsa:
Hi admin,

thanks, that´s the kind of feedback I was missing.

Received yesterday an e-mail from an other user also pointing to Android 2.3 (obviously a lot of LT26i users still use GB) ....So the hardest part was to find a testing device with Android 2.3 running ;) ... finally I downgraded a nexus s and then had to flash some NFC fixes to it, because downgrading to 2.3 breaks the nfc functions on the nexus s :eek: ...could reproduce the error and I think I fixed it -> Update 2.2.3 was uploaded to the playstore a couple of hours ago ...-> Feedback welcome !

BTW.: It´s getting harder and harder to support Android 2.3, but as long as there is a manageable solution I will try to support it....

The funny thing is, that the beam feature now also works (sort of) on a nexus s running Gingerbread ;) ...-> afaik android beam was official announced for ICS ....Ok, I know that GB contains some early beam API, but I hadn`t expect it to work ... and I´m not sure, if the flashed NFC fix has something to do with ...Try it out, if you want .... works like on ICS, except the screen will not shrink!--> so go to the Edit Tag screen and tap your devices together (ICS/JB: screen on + no lockscreen; GB: screen on) ...you will hear a NFC sound and then touch the screen --> beams your current tag cycle to an other device with NFC ReTag installed ;))

OK, now the bad news:

The SMS feature is NOT (native) supported by NFC ReTag ...experiemented a lot with this feature and had a working prototyp a couple of month ago, but decided to NOT implement it, because of some very poor API implementation (--> e.g. SMS will not be listed in send messages ) and some "evil" permissions you need for that :eek:

I´m thinking about something like an additional plugin/ module for these "evil" and root functions ... but that´s something for a future release ...

However, you could always try Tasker (+ Secure Settings plugin) in conjunction with NFC ReTag for this.
[Samsung Galaxy Nexus] admin@xda:
You a great and should be named admin instead of me.

Seriously - astonished with such level of support :)

2.3.3 works flowless. Now trying to find a solution how to enable nfc with screen off / locked but this is another story. Found several threads on xda already.
[Samsung Galaxy Nexus] nyarnon:
Re: [APP][2.3.3+][NFC] NFC ReTAG --&gt; re-use write protected NFC tags

REQUEST:

A switch for GSM WCDMA would be helpful.

Send from my N7100

Kernel: Perseus 31.2

Rom: Android Revolution HD 8.0

Rescue: TWRP 2.3.3.2
[Samsung Galaxy Nexus] ascsa:
yep, and I would like to implement it ... unfortunatelly the last time I checked this, I didn´t found a manageable & reliable solution ...However, i will put it on my todo list and check it again ...
[Samsung Galaxy Nexus] ascsa:
Update 2.3

Update 2.3 released ...

* Add new SSID (great for sharing/ beaming WiFi SSID and password)

* Say current time

* Launch App Activities

* Bluetooth discoverability

* Set default ringtone

* Set default notification tone

* Set default alarm tone

* Improved media control

* Minor improvements and fixes

Added also a "labs" category, for new (and sometimes beta) features, to accelerate the update cycles ....:eek:
[Samsung Galaxy Nexus] ItsSamShaw:
AW: [APP][2.3.3+][NFC] NFC ReTAG --&gt; re-use write protected NFC tags

Its an awesome app. I really like it. Good job!

Is its possible that I can open a special file if i slide over a tag? That would be great.

That would make my job easier.

Just a idea for you

Thanks a lot

Sent from my GT-I9300
[Samsung Galaxy Nexus] ascsa:
Hi ItsSamShaw,

I´m currently a little bit busy getting the next update finished (95% done, testing and tweaking the last 5% ...). This update will introduce an additional "NFC ReTag Expert Plugin" which will give me the possibility to add root functions and security related permission without having to add "evil" permissions and root functions to the main app ....:cool: ....means keeping the main app secure for users with security concerns and without root (anyone on XDA ?) and providing advanced functions for root users and users who understand that you need a CALL_PHONE permission for an app that has a "Call" activity ...:eek:

So after the update, I should be able to add functions, which I refused to add in the past because of their security implications, to the plugin, without messing with the main app ...- -> everything should be possible ;)...

Open a file on your device should not be a problem ... never tried or thought about it, but this should be easily manageable ....however, the devil is in the detail....I will put it on my todo list, and have a look ...
[Samsung Galaxy Nexus] ascsa:
Update 2.4

Update 2.4 just released.....

--> Update 2.4 (2.4.x = fixes)

* Add support for new NFC ReTag Expert Plug-in ( --> Download FREE Plug-In)

* Toggle GPS (via plug-in and root)

* Airplane mode (support for JB 4.2 via plug-in and root)

* Stay On while charging (support for JB 4.2 via plug-in and root)

* Moved Call activity and CALL_PHONE permission from main app to plug-in

* Moved Timestamp activity and WRITE_CALENDAR permission from main app to plug-in

* Minor improvements and fixes
[Samsung Galaxy Nexus] matejdro:
Is there a way to disable "NEW Tag detected!" Message?

EDIT: Also, is there a way to disable toasts that pop up when saved tag is detected?

I still want it to act automatically, but silently fail if tag is not in the database.
[Samsung Galaxy Nexus] ascsa:
Hmm, sorry not sure if I got your use-case ....And I´m not sure if your problem is the pop-up or if you want to dispatch the tag to another nfc app ...that´s something completely different.

However, let me explain it a little bit:

That´s the easy part: Yes, sure..Have a look at --> Settings--> Mute pop-ups ( that´s the activity pop-up, which shows you the list of started activities ...or do you mean something else?)

Now, the "new Tag detected pop-up" issue: Currently there is no way to disable this pop-up, if the tag is dispatched by the android firmware to NFC RetTag and the tag is not in the database ... as mentioned, I´m not sure if disabling the pop-up is really that what you want, because I don´t get the use-case ... why would you like to dispatch the tag to NFC ReTag and then let it fail --> HINT: no other app will be able to use this tag, no chooser will be shown etc. ...(btw. you could add the tag to the database and don´t assign an activitiy --> info toast or assign the "do nothing" activity and nothing will happen).

So I assume your issue is more likely a dispatching issue rather than this pop -up ...Right?

There are a some ways to influence the android dispatching process, if you have writable tags, and it´s a lot harder / impossible with write protected tags ....so please could you explain your use-case (and configuration) a little bit more in detail, and perhaps we could find a solution for this ...
[Samsung Galaxy Nexus] kadolf:
Hi ascsa,

NFC ReTag is a great app. One nice addition would be an Activity in Expert Plugin allowing you to "kill"/close an running app. That's the only feature I miss in your app so far. One example where this would come in handy: I use a tag in my car to start the app playing my music and navigation software. It would be great if I can just scan another tag (or use the cycle feature) to close these apps when arrived.

Also, is there a possibility to re-arrange the activities in one tag profile?

EDIT:

Just noticed that root plugin doesn't work on my Nexus 4. Expert plug-in is detected in settings, the app states that the plugin is installed and has root access.

Nevertheless neither Call nor Flightmode activity works. Root works flawlessly in other apps.
[Samsung Galaxy Nexus] ascsa:
Ok, let´s discuss the additional features later ... the issues with the plugin/ root access have priority.

Could you please use the "Check again" button in the Settings .... and give me the message ?

And is it possible for you to grap a log file while running Airplane mode and call ?

... don´t think it´s root related --> because call doesn´t need root... However, something seems wrong with the permissions handling ...

EDIT: very strange .... because it seems that it worked before, else the app wouldn´t state that the plugin is installed and has root access. Did you do something else ? Backup and re-install, sideload, fix permissions etc. ??
[Samsung Galaxy Nexus] kadolf:
I just did a few tests. Problem only occured, if I used a "Show Homescreen" activity within the same tag.

It seems like "Show Homescreen" gets executed earlier than the plugin-activities and "kills" connectivity between the app and its plugin.

As you can see in the logfile (I used "SIMULATE", didn't use a real NFC tag for logging) the intent to start expert plugin is still seen - but afterwards nothing happens:

02-21 14:02:17.156 I/ActivityManager(535): START u0 {flg=0x10104000 cmp=com.widgapp.NFC_ReTAG_FREE/.NFC_ReTAG bnds=[322,876][662,1176]} from pid 776

02-21 14:02:17.376 D/NfcDispatcher(946): Set Foreground Dispatch

02-21 14:02:17.476 I/ActivityManager(535): Displayed com.widgapp.NFC_ReTAG_FREE/.NFC_ReTAG: +209ms

02-21 14:02:18.537 I/ActivityManager(535): START u0 {cmp=com.widgapp.NFC_ReTAG_FREE/.ShowDB} from pid 11691

02-21 14:02:18.547 D/NfcDispatcher(946): Set Foreground Dispatch

02-21 14:02:18.757 I/ActivityManager(535): Displayed com.widgapp.NFC_ReTAG_FREE/.ShowDB: +210ms

02-21 14:02:21.270 I/ActivityManager(535): START u0 {cmp=com.widgapp.NFC_ReTAG_FREE/.NFC_ReTAG} from pid 11691

02-21 14:02:21.320 D/NfcDispatcher(946): Set Foreground Dispatch

02-21 14:02:21.320 I/ActivityManager(535): START u0 {flg=0x4000000 cmp=com.widgapp.NFC_ReTAG_FREE/.automode (has extras)} from pid 11691

02-21 14:02:21.330 D/NfcDispatcher(946): Set Foreground Dispatch

02-21 14:02:21.390 D/safa (11691): activity: Airplane mode (PlugIn + Root)parameter: 2

02-21 14:02:21.400 D/safa (11691): activity: Show homescreenparameter:

02-21 14:02:21.400 I/ActivityManager(535): START u0 {cmp=com.widgapp.NFC_ReTAG_FREE/.ConnectPlugin (has extras)} from pid 11691

02-21 14:02:21.400 I/ActivityManager(535): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10000000 cmp=com.android.launcher/com.android.launcher2.Launcher} from pid 11691

02-21 14:02:25.765 W/KeyguardViewMediator(535): verifyUnlock called when not externally disabled
[Samsung Galaxy Nexus] matejdro:
It was conflicting with Sleep as Android app, which was in foreground (showed message despite app should take over NFC). Then I added new blank profile to ReTag, but that created long toast with each swipe. Fixed that by adding "Do nothing" action.

Anyway, removed everything and it appears that it kinda fixed itself now!

Thanks for the app, it really helps. I actually have writable tags, but reading ID method is much faster since phone don't have to read whole tag.