Google didn't support NFC in the first round of Android Wear devices? No problem!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
lol nice work. So this adds nfc features to your phone??
Depending on the chip, you can simply stick it on back of the watch and it will work. I did that with my pebble. However, some don't work. I received some nfc stickers and they weren't strong enough.
I read on Google Plus post that someone was able to add NFC on Android Wear, the problem is that there are some interference...
Well, it makes it quick to unlock. (see https://www.youtube.com/watch?v=Zx5v63D-X80 for a video)
The way it is now, it's probably not that secure, other phone unlocking methods (e.g. pattern, pin) are worse when people around you can see what you're typing so easily. In any case I think this type of unlocking method can be made more secure if we really want to.
Ideally, future watches should support NFC communication so we can do a proper cryptographically secure handshake.
duckslivelong said:
lol nice work. So this adds nfc features to your phone??
Click to expand...
Click to collapse
It's just a nfc tag he put inside the watch. Nothing else.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A pair of security researchers have recently unveiled an interesting new keylogging method (PDF Research Paper) that makes use of a very unlikely smartphone component, your gyroscope.
Most smart phones now come equipped with gyroscopes, which can be accessed by any application at any time. [Hao Chen and Lian Cai] were able to use an Android phone’s orientation data to pin down what buttons were being pressed by the user. The attack is not perfect, as the researchers were only able to discern the correct keypress about 72% of the time, but it certainly is a good start.
This side channel attack works because it turns out that each button on a smart phone has a unique “signature”, in that the phone will consistently be tilted in a certain way with each keypress. The pair does admit that the software becomes far less accurate when working with a full qwerty keyboard due to button proximity, but a 10 digit pad and keypads found on tablets can be sniffed with relatively good results.
We don’t think this is anything you should really be worried about, but it’s an interesting attack nonetheless.
Click to expand...
Click to collapse
Source: Hackaday
this day i have a question to my self how is really smartphones 10-20 years from now??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
here is my toughts i know its not have the details but some points its pretty reasonable
how about your idea?
but i want to be scientific and reasonable
Some things:
I personally feel holding the phone and talking to be quite inconvenient and old-fashioned, so I would predict 10 years from now, the speaker & microphone would/should be replaced by something (maybe directional speakers / microphones / something more hi-fi) so that we can just talk handsfree always without worrying about interference / privacy / all the problems we currently have.
I'm not quite for predicting that touch-screen would be the dominant interface, but couldn't really think of other advanced UI methods that might crop up in the near future. I would more like moving away from the passive device with a display & touchscreen that you've to go to for accessing information towards something like google glass - something that's always there unobtrusively but provides you stuff you want always without all the lookup cycle.
Also, removing the display for something wearable and still not inconvenient (goggle/glass are not liked by everyone) would be a very good technological advance.
Here's a daydream that old school hackers out there might recognize if you've ever used CDE on Unix or VMS. This is an Android port of Jeff Butterworth's xswarm. This was mostly done as a learning project and I still have a few questions resulting from it. Though for now it's done, working, and I think I've added enough options. I'll take bug reports and pull requests but don't expect too much in the way of additional features.
Anyway, here's some shots.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--- Non-devs can skip the following questions. ---
Is there a color picker library that uses fragments and also allows hex entry? lomza/android-color-picker looks like one of the better ones, though I'd really prefer something with text input for exact values as well.
I'm also trying to come up with a way to programmatically pull in resources so I don't have to do ugly enumeration such as this (see TODO sections). The EditTextPreference dialogs do bounds checking before updating the summary field, but one thing that throws a wrench (or IllegalStateException) into things is that EditTextCheckBounds isn't attached to the Activity so you can't call getResources() within that function without jumping through a lot of hoops.
Source: https://github.com/coax75ohm/droidSwarm
In the accessories under the settings in Samsung Galaxy Core 2 it say's :
S-View Cover ( Automatic unlock) : Flip the cover to unlock the screen when secure lock is disabled. (Check or Uncheck)
Does it mean that S - View is supported in this device even if it doesn't have a proximity sensor to get S-View (Google Play)
or it is just a mistake?Because I am planning to buy an s view this month (online).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes it is a mistake. Please don't buy this mobile always getting over heat on normal usage.
tanoojk said:
Yes it is a mistake. Please don't buy this mobile always getting over heat on normal usage.
Click to expand...
Click to collapse
I don't understand because i think Samsung would not just publish a noticeable mistake. Can someone verify this.
QUOTE=RairuLyle;56608878]I don't understand because i think Samsung would not just publish a noticeable mistake. Can someone verify this.[/QUOTE]
It's a mistake made by samsung but there is workaround to set front camera as motion detection sensor for off/ on screen.
https://www.youtube.com/watch?v=VbGOGtPfMjw&feature=youtu.be
Tested.
http://android.stackexchange.com/qu...d-device-with-motion-detector-external-device
Hi guys is here anyone who can use Curve App to make NFC payments? I have registered account, but when i use it to login via app it always end with error. Curve support sucks... they cant answer me in one week.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey I use it with my Matexs and it works perfectly
I installed Curve app on Mate40 pro, but I can't pay via NFC ...
It works only online (I made few transactions), at the POS it doesn't do nothing.
In the app everything seems to be ok, Curve is set as the default application for NFC ...
The physical card hasn't arrived yet.
I have to mention that curve app should be installed from appgallery. After that, in some country works and in some doesn't work.
Right, installed from Aurora, for example, does not even open.
Hi guys i have managed to activate acc but, when i want to use it as payment i cant, cause it wanted to add to google pay. And there is a problem.
Curve installed from AppGallery has nothing related to Google Pay.
Yes i get it now now the second step is can i turn off my fingerprint authentication to pay with unlocked screen?