• Login
    • Search
    • [[global:header.recent]]
    • [[global:header.tags]]
    • [[global:header.popular]]
    • [[global:header.groups]]
    • [[global:header.search]]
    1. Home
    2. MadDave123
    M
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 3
    • Best 0
    • Controversial 0
    • Groups 0

    MadDave123

    @MadDave123

    0
    Reputation
    947
    Profile views
    3
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    MadDave123 Unfollow Follow

    Latest posts made by MadDave123

    • RE: Bug(s): App activation / Google sign-in / Power cycle bypass

      Thanks very much for the response. That helps ease some of my concerns.

      posted in NFC Ring Apps
      M
      MadDave123
    • Bug(s): App activation / Google sign-in / Power cycle bypass

      Hi,

      Note: I've been through the relevant sections of this forum, the public bug database and FaceBook page. I can find no similar issues to what I've decribed below.

      [u:tt198m0x][b:tt198m0x]Summary/details:[/b:tt198m0x][/u:tt198m0x]
      I'm a Kickstarter backer (don't have a ring yet), using a Nexus 4 running Android 4.4.2

      I was having a play with my NFC Ring Unlock app earlier and activated the security features. Initially nothing happened (which I expected), but about 8 hours later, after I returned home from work, I tried to unlock my phone and the NFC screen had kicked in.

      Since I don't have a ring yet I tried to bypass the app by signing into my Google account. However, I use 2-step authorisation for my Google account, so when I entered my details it rejected them. It seems there was no way for the app to prompt for a 2-step verification code: these are normally requested after the phone navigates to a Google sign in page via a web browser (I don't think the Google sign in API or whatever is used allows for 2-step auth). Note that I did notice an authentication message at the top of my phone screen cycle a few times before it gave up.

      Now the only thing left for me to try was a power cycle. I turned the phone off and on again and entered my unlock PIN as soon as I was able. This did bypass the NFC Unlock app and allowed me to deactivate it.

      [u:tt198m0x][b:tt198m0x]Bugs/questions/suggestions:[/b:tt198m0x][/u:tt198m0x]

      1. Why did it take so long for the app to start working? I was using my phone intermittently throughout the day and nothing changed (I could unlock my phone with my PIN without issue).

      2. Should the app kick in without any kind of Ring/Tag registered against it? This seems like it could lock potential early users out of their devices (as it almost did me).

      3. Shouldn't there be a way for Google 2-step authorisation to work within the app? Is this a bug, a limitation of the app or a big oversight?

      4. Should power cycling a device bypass the NFC Ring Unlock app?

      Thanks,
      MadDave123

      posted in NFC Ring Apps
      M
      MadDave123
    • Nexus 4

      Has anyone tested the rings (standard & alpha) with the Nexus 4? Either the test rings or the production ones.

      There seems to have been a lot of confusion about whether the Aphpa ring was actually needed for the Nexus 4, since John accidentally mentioned the N4 instead of the N5 in one of the updates. Some people (myself included) had previously contacted support asking to change to an Alpha ring based on teh info in that update, but now it'd be good to know if it's safe to switch back to the standard ring.

      posted in Which ring will work with my phone?
      M
      MadDave123