yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ascsa:
Thanks for your feedback! The good thing is, that the plugin seems stable .... -->it was a pain in the §$$ to get it stable and secure ...

Hmm, tested it and I can confirm that the "show homescreen" activity kills (sort of) the plugin activities ....aargh, not sure if I could change that behavior but I will have a look ...!

Usually I recommend this "show homescreen" activity to simulate the android close app behavior (--> back to your original question ;)) .... but in this case it´s annoying ... I think you could add some wait activity before the homescreen activity to let the plugin do it´s magic ... but I doubt it would be reliable .....and that´s one of the problems with all close app / kill app activities ....as android is not designed to let a user (or a 3rd party app) really close an app, this usually doesn´t work reliable ...so I think just delete the show homescreen activity and let´s find a solution for your " kill app " problem ....

both, music player and navigation apps are designed to run in the background ....so anyway, the "show homescreen" activity would not kill them ... the good news is that a lot (but unfortunately not all music player apps) will close automatically if you use the toggle play (or play and stop) parameter ....so no need to kill it manually ...didn´t find a similar trick for the navigation activity (you could try car mode off to show the homescreen ;)) ... but I think I must have a look at this "kill app" feature more in detail ....another issue I recognized is that the navigation activity starts very fast ... and if you want to combine this with the gps activity it´s too fast ....some disadvantages, if you design an app that runs the activities parallel and as fast as possible ...so a lot work for the next update ;)

EDIT: and that also answers your question, regarding the re-arrangement of the activities ... they are all fired within a couple of milliseconds ....after that, androids multitasking kicks in and runs them more or less in parallel ... and depending on your system load, pending background intents , the specific activities etc. you can´t control which activity will finish first ....so a re-arrangement is in most of the cases useless ...sure in some cases the wait activity will do the trick, but it´s also not always reliable ....Bottom line: Sure I could add such a feature (and probably will add it eventually) but due to the minor effect of this feature, it´s not high priority ...
[Samsung Galaxy Nexus] ascsa:
Yep, I also prefer the ID method ;) ...

But as your problem seems like some dispatching issue, I recommend to use the " write special NFC ReTag tag " option (more button!) if some dispatching issues occur again ... this only writes a dispatching message on your tags (activities still saved in database!) and you don´t have to rely on the standard android background dispatching process any more ... very helpfull, if you have several NFC apps installed --> makes your NFC Retag tags bulletproof ;)
[Samsung Galaxy Nexus] ascsa:
Hmmm, didn´t want to wait until the next major update with this gps / navigation issue ... so just released a small fix for it ...--> 2.4.1. GPS should now turn on before the navigation app starts ...

...closing an app is still something for a major update ....

BTW: I´m on a trip till the end of next week, with only limited access to internet and development resources (theoretically I will be able to do some emergency fixes ...but I don´t think this will be necessary ...:eek:) ... so please expect that the support will be a little bit slower / limited the next couple of days ...
[Samsung Galaxy Nexus] klau1:
Lockable NFC Launcher

I'm trying to use a NFC Task Launcher to control [App Protector Pro] so that specific Apps can be unlocked via NFC.

Basically the following method:

NFC Task Launcher -> Tasker Task -> App Protector Pro Plugin -> Disable App Protector Pro

But the problem is, the task to unlock App Protector Pro can also be called from directly within the NFC Launcher GUI. This defeats the purpose of App Protector Pro since anyone can go into the NFC Task Launcher to unlock App Protector Pro.

at least a PIN lock is needed to plug this security hole.

Could NFC ReTag implement something that locks it's own GUI access?
[Samsung Galaxy Nexus] ascsa:
Re: [APP][2.3.3+][NFC] NFC ReTAG --&gt; re-use write protected NFC tags

Hi klau1,

I'm not sure if I understood you right, but implementing a security related app / function / whatever via a Tasker task makes no sense for me.

The Tasker api is open and easy to implement, everybody could build a small app to bypass this "security" feature... You could even use a url to launch a Tasker tasks....

So perhaps you should re-design your app / concept, rather than to ask everybody to change their apps.....

Bottom line: your concept is easy to bypass and please be aware that the bad guys won't play nice.... So redesign your app and make it secure and don't rely on others to keep your app secure.

EDIT: Didn't want to sound rude and as mentioned I'm not sure if I understood you right.... Re-reading your post twice and still don't know if you were a user requesting a lockscreen feature... Or the dev of this app/concept complaining that his concept isn't secure...
[Samsung Galaxy Nexus] klau1:
True, I agree. I have thought about that possibility. But it's not my app to change.

The app in question is Face Unlock Pro.. (App Protector Pro is better in that it CAN'T be disabled without a password in Tasker)

It has a plug-in for Tasker, that allows Tasker to disable it.

Since it's there anyways, I have two choices, delete the app, or use it.

Since bought it, I might as well take advantage of it by using it.

But yes, anyone could launch a tasker task that calls for the Face Unlock plug-in to be disabled.
[Samsung Galaxy Nexus] ascsa:
Re: [APP][2.3.3+][NFC] NFC ReTAG --&gt; re-use write protected NFC tags

Edited my last post.... But you was faster to post an answer... ;)
[Samsung Galaxy Nexus] klau1:
As a user, I'm trying to figure out a way using NFC to enable and disable a App based locking app, called Face Unlock Pro. (also App Protector Pro)

Face Unlock Pro has a plug-in for Tasker that allows it to be disabled by the Plug-in.

But while Tasker UI can be locked from casual users, NFC Launchers have no GUI lock.

This means, any casual user can go into the NFC Launcher to unlock the Face Unlock Pro App via the Face Unlock Pro Plug-in.

So I was wondering if it was possible to add a GUI Lock as protection against casual snoopers.

(against serious hackers, all hope is lost with pretty much any concept anyways, unless you're willing to encrypt the entire device and take performance hits.)
[Samsung Galaxy Nexus] ascsa:
Re: [APP][2.3.3+][NFC] NFC ReTAG --&gt; re-use write protected NFC tags

Aaaah okay, think I got it.... You want some pin protection for accessing the app....->definitely not top priority, but anyway I will put it on my longterm development list and check it again eventually.
[Samsung Galaxy Nexus] klau1:
Thanks for the quick reply.

It would be great if that could be implemented instead of having to wait for NFCSecure to implement a App Locking component.

I think some form of App Locking is pretty important, since one day, you might be lending your phone for a friend to call for a second, and the next second, he/she could be snooping around your phone behind your back just out of curiosity.
[Samsung Galaxy Nexus] omidlolo:
Hi

I want backup my student id card and copy its data on Sony smart tags

But how?

My id card was not formatted, according NFC apps error

---------- Post added at 10:02 PM ---------- Previous post was at 10:00 PM ----------

How can i run shortcut with this?
[Samsung Galaxy Nexus] ascsa:
AW: [APP][2.3.3+][NFC] NFC ReTAG --&gt; re-use write protected NFC tags

I'm not aware of any possibility to copy your student id or any other security badge...

Open nfc retag - >tap your tag - >add a name for your tag - >add activities... That's it!... Pretty simple and straight forward from my point of view :)
[Samsung Galaxy Nexus] omidlolo:
ok, but for ex. i need run profile scheduler+ shortcut and i can't do this
[Samsung Galaxy Nexus] ascsa:
Re: [APP][2.3.3+][NFC] NFC ReTAG --&gt; re-use write protected NFC tags

Ok, don't know profile scheduler and don't know if it provides an api, but have you tried the "start activity" option (Lab)?
[Samsung Galaxy Nexus] ItsSamShaw:
AW: [APP][2.3.3+][NFC] NFC ReTAG --&gt; re-use write protected NFC tags

Is there any possibility to get the pro version without using Google Wallet? I don't have a credit card or could pay via provider neither.
[Samsung Galaxy Nexus] ascsa:
AW: [APP][2.3.3+][NFC] NFC ReTAG --&gt; re-use write protected NFC tags

No, the PRO version is only available via google playstore.
[Samsung Galaxy Nexus] klau1:
Re: [APP][2.3.3+][NFC] NFC ReTAG --&gt; re-use write protected NFC tags

Could you try a prepaid credit card?
[Samsung Galaxy Nexus] ItsSamShaw:
AW: [APP][2.3.3+][NFC] NFC ReTAG --&gt; re-use write protected NFC tags

I've never heard about that in germany.
[Samsung Galaxy Nexus] ascsa:
Hmm, your right, prepaid credit cards are not popular in Germany, but however there are a lot of possibilities to buy a prepaid credit card in Germany, too ...you could buy them even on some gas stations ...

Have a look (german):

http://www.mywirecard.com/visa.html

or

http://www.visa.de/de/kartenprodukte/visa_prepaid_karte.aspx

Btw. afaik a lot of german carriers also provide carrier based payments by now, so perhaps you could check this again.

However, let´s hope Google will add some additional payment methods soon ;)
[Samsung Galaxy Nexus] asblikk:
Timestamp to Google Calendar

Hi

Is there any possibility to have this App to write timestamps to Google Calendar? The App write to "My Calendar", which i cannot sync with Google Calendar. I want to read mine timestamps on my laptop and that's why i want to sync with Google Calendar.

I think this App is a very good and i will buy it for my business if i can solve this problem.

Excuse my bad english... :rolleyes:

Best regard

AB

My Phone is SG III, Android 4.1.2
[Samsung Galaxy Nexus] ascsa:
Hmm, wasn´t aware that there is a Google calendar sync issue ....I did some tests with a galaxy s3 a couple of minutes ago and yes your right, seems not to work .... not sure if this is a samsung issue or something else ...however I will have a look, and check if I could fix this ...
[Samsung Galaxy Nexus] ascsa:
Livehacker: Hacker Challenge: share your best hotel room hack.

And the winner is ....

http://lifehacker.com/5991176/hacker-challenge-winner-automate-your-hotel-room-with-nfc-tags

Congrats!
[Samsung Galaxy Nexus] evetillard:
Making NFC ReTAG a default NFC App?

The app works great, but I have several applications that can read any tag on my phone, so I systematically need to choose the application when I scan a recycled tag. I haven't foun a way to make NFC ReTAG the default NFC app for tags that are not explicitly associated to other applications.

Is there a way to define such a default app?

Using a Nexus S, 4.1.2 .

Thanks by advance,

Eric
[Samsung Galaxy Nexus] ascsa:
Hi Eric,

I love the nexus devices and pure android, but this is one of the few things which is better implemented on some roms from device manufacturers. ... The dispatching of the tags is completely done by the firmware... and on pure android there is no way to define a "default nfc app" (if these apps have defined similar filters)... :eek:

Some manufacturers (afaik at least Samsung and LG...) added this "default nfc app" option to their roms --> :good:

However, there are some tricks to achieve the same on a nexus s device on stock rom:

- Most simple solution: Write a special NFC ReTag tag( --> more button!) .....but you mentioned recycled tags, so I don´t think you could write to these tags ... right ?

- Every good nfc app should have an option to disable background dispatching ....so have a look at your other nfc apps settings and try to disable background dispatching within these apps ...-->usually they will work as expected when in foreground and will disappear in the background dispatching chooser ....

- If these apps have no settings to disable background dispatching, I´m sorry, the only thing you could do is to freeze or uninstall these apps or live with the chooser or get some writable tags....Sorry, nothing I could do within NFC ReTag ...:eek:
[Samsung Galaxy Nexus] asblikk:
Hi.

Have you look at that "problem" with timestamp on google calendar?

--

Regards

AB
[Samsung Galaxy Nexus] ascsa:
Yep, already solved and tested within my current prototype ... works perfect now ...so it will be definitive included within the next update ...

I have some additional things on my list for the next update ... but I´m not sure if I could implement them all this time, or if I just should release a smaller update with the timestamp update and some minor improvements ...

Usually my philosophy is to fix critical bugs asap (minor/bugfix releases) and include several new features every few weeks (major releases)... personally I don´t like apps, updating every few days, with just some tiny improvements and a lot of new issues ....

I will have a look at one or two additional things until Monday or Tuesday, and then I will decide the final scope for the next update:

small update --> probably end of next week :D || bigger update--> additional one or two weeks ... :eek:
[Samsung Galaxy Nexus] ars0n:
Any way or program out there that can mock or mimic an NFC tag and or use the phone to read the tag. Save it to the phone, then use the phone as that card. etc..?
[Samsung Galaxy Nexus] ascsa:
Hmm, probably the wrong thread, but one of the most frequently asked questions regarding NFC ....and already answered on xda a lot of times...

However, to make it short:

- from a technical/ theoretical point of view: yes, should be possible

- from a practical point of view: NO, it´s not possible (unless you have the right device + special firmware + special app ....and you only want to emulate a poorly secured, non-encrypted tag):eek:
[Samsung Galaxy Nexus] :
t
[Samsung Galaxy Nexus] ascsa:
Hi royjr96,

yep, I´m working on a lot of similar requirements/ projects, but haven´t found an optimal solution (within my standard NFC ReTag app) yet. Usually the problem is, that NFC ReTag is not designed for such purposes, especially when you think about a large number of tags, and the need to configure each tag ... that´s simply not convenient ...from a technical point of view it´s not a big problem to solve this, by adding an additional "pass through" mode to NFC ReTag , but I suspect that a lot of users will have problems with this mode, because it´s a complete different app behavior ....so I haven´t add such a mode yet and I´m not sure, if I should add such a mode ever....Currently, I use a small custom made app within these projects.

However, if I understand you right, you search a solution within NFC ReTag. ...There are also a lot of different ways to solve this, but your clipboard approach is something I never thought about ;) ... I´m sure it would work, but I think this could be done perhaps a little bit more elegant ...

for example:

- if I remember it right, i could simply pass the UID to tasker ... so no need to use the clipboard ..

- Or i could add an UID Parameter( something on my todo list for a long time) to NFC Retag, so you could use something like"your.url.index.php?id=[%UID]"

- Another possibility would be, to provide a simple NFC ReTag broadcast api...

Anyway, I think I will add one or two of the possibilities above in one of the next updates and keep the clipboard approach in my mind (and on my toDo list) ... the clipboard thing should not be a problem to implement, but as mentioned, never thought about it before, and therefore never tried to implement it ....
[Samsung Galaxy Nexus] ars0n:
Ah thank you for the reply!
[Samsung Galaxy Nexus] ascsa:
Update 2.5

OK, update released ...Main app 2.5 and plugin 1.2

Update 2.5 (2.5.x = fixes)

* Support for placeholders (e.g. [%UID], [%DAT])

* Tasker Task advanced (pass variables to tasker)

* ReTag Broadcast (for 3rd party apps)

* Improved Timestamp activity (Define Calendar ID and Title prefix via settings)

* Language support for German

* Minor improvements, tweaks and bugfixes

Looks like a small update, but the placeholder support and the advanced Tasker tasks and last but not least the ReTag Broadcast gives you lots of new and unique possibilities ...
[Samsung Galaxy Nexus] asblikk:
Google Calendar...

Hi.

It works with Google Calendar now. Nice, very nice. You got youreself a customer....:highfive:

--

Best Regards

AB
[Samsung Galaxy Nexus] ascsa:
Yep, I like it a lot, too ..

And in combination with the runtime parameters it´s a powerful feature ...For example, you could use it as some simple multi-user time-punch machine ... all you need is an additional shared "timestamp calendar" and two activity tags(one for in and one for out)... add the [%UID] parameter for identifying the tags (-->or in/out) and the [%AID] parameter for identifying the users ... you could even do it, with a little bit more configuration effort with one tag and the cycle ID ....or use your own webserver to build your own solution ... the possibilities are endless ....:victory:
[Samsung Galaxy Nexus] albsat:
Is there a way to disable the tag effect?

I want that nfc retag open Bluetooth near the tag and after remove to switch it off?. Is it possible?
[Samsung Galaxy Nexus] m.klinge:
A while back in this thread I posted a way to simulate that using tasker, you should be able to find it. Ascsa hasn't chosen to implement the solution in nfc re-tag yet :(

However the short answer would be no as the phone only detects when a tag I'd present, not when it's not present anymore (that's how nfc works) :)

//M

Sendt fra min LT25i med Tapatalk2
[Samsung Galaxy Nexus] ascsa:
Yep, we discussed it here a while back .... and m.klinge did a great job with Tasker ... there is also an additional thread in the NFC Hacking section of the xda - developers forum ...involving a modified NFC.APK and a hacked app.... overall an interesting approach, because it manipulates the firmware to send a "tag lost" trigger, but I don´t support hacking apps without the permission of the developer (not sure they have one) and it changes the NFC behavior in a way, I´m not sure, if some side-effects will show up....

My problem is, that the standard nfc stack simply isn´t designed that way and there is no simpel and reliable way to change that, except Google would change the api ....Sure I experiment a lot with these features on my testing devices and within some of my app prototypes, and sure here on XDA are a lot of users who could understand this hacking ... but NFC ReTag is available in Google Play and I´m happy when the normal user understands the android and nfc basics ....

So bottom line: No, there is no way to do this on standard android ... but as always on android, you could hack the firmware.... Currently, I do not plan to implement such an hack in NFC ReTag in the near future ....but never say never ;) ... and let´s hope that the next android update improves the nfc api a bit ...

BTW. : You could simply use the toggle function or the ReTag cycles to achieve a on/ off toggling by swyping the tag ....
[Samsung Galaxy Nexus] m.klinge:
Dude make an advanced section that includes my "tasker" solution - heck you can even add my email address as support :)

//M

Sendt fra min LT25i med Tapatalk2
[Samsung Galaxy Nexus] ascsa:
;)

If I remember it right your Tasker solution had some disadvantages ... e.g. as it uses only the screen lock for triggering .... I called it the Tag lost light solution.... the moded NFC.apk solves the triggering problem ... so if I would implement something like that, I would prefer the moded NFC.apk ...with the disadvantage, that you need a rooted device and a moded NFC.apk for the specific device ...

However, NFC ReTag has already a advanced section (the expert plugin and the labs section) ...I spend a lot of time evaluating , experimenting and testing new features... and a lot of these features only exist as prototypes, because it´s simply not possible to find a reliable implementation (or I´m to stupid to make it right) or they don´t work as expected.... it´s quite hard to make the decision, NOT to release a feature after hours and hours of developing and testing, but that´s my way to develop a stable app. Even the labs activities are fully tested on several devices, with several android version and configurations without any known problem ... I know this development approach seems not popular anymore with a lot of apps, programs, games, even devices etc. focusing on eye-candy and half working functions, but I spend a lot of years on business critical multi-million $ software projects, and that´s my norm. :eek:

To make it short: Sorry, currently I don´t think that I could implement such a feature in a reliable way. I will keep this request in mind (as the last couple of month) and I will spend some additional time experimenting, but to be honest, I have some much cooler and more mature features in the prototype stage than this.
[Samsung Galaxy Nexus] m.klinge:
Well I don't share your idea that it's unreliable, unstable or otherwise "not working" - I guess that's why I can't see the hurt in implementing it. From my point of view about 95% if the use cases where you would actually need something triggering when the tag is gone its perfectly fine to use the display on as a trigger. I also fail to see how that is complicated to communicate and understand :)

Back then you said that would rather just tap the tag again or press a widget, well if that was (and is) the use case why don't you just make a widget to toggle the action?

I'm not going to argue about how you develop your apps, in fact I think you do it the correct way. However to be honest personally I don't really care what else you implement as all you have ever implemented I've already done with tasker if I needed it. And yes I might be special I'm that sense :)

//M

Sendt fra min LT25i med Tapatalk2
[Samsung Galaxy Nexus] ascsa:
Hmm I don´t know, why we are arguing again. I still don´t think I could implement a proper "tag lost" solution within NFC ReTag and you already has done your solution with Tasker.

So what´s the problem?
[Samsung Galaxy Nexus] m.klinge:
One reason would be I'm not the only one asking for this feature. Another would be that it's messy to do in tasker with multiple tags. Yet another would be that your app would be the first top implement it :)

Please don't take this as an attack, as I've stated before you have made a really great app that works perfectly fine, I just can't get my head around as to why you don't want to implement a perfectly working solution that would not require root or any other hack :)

//M

Sendt fra min LT25i med Tapatalk2