Fixed
Status Update
Comments
ag...@google.com <ag...@google.com> #2
If it were not for NFC unlock I would not use any kind of display lock at all.
Face unlock does not work properly, as well as trusted places.
Bluetooth would not make any sense, since I would have to unlock my phone to switch on bluetooth to have my phone unlocked by bluetooth (wtf ?).
On body detection is useless, too: whenever I carry my phone around in my pocket with the screen unlocked, all kinds of strange things happen when the screen gets activated by some app or another.
As for fingerprint, my phone does not have one. Even if my next phone had a fingerprint reader, it would be of no use when located in the back and the phone is sitting in any kind of holder or cradle.
Face unlock does not work properly, as well as trusted places.
Bluetooth would not make any sense, since I would have to unlock my phone to switch on bluetooth to have my phone unlocked by bluetooth (wtf ?).
On body detection is useless, too: whenever I carry my phone around in my pocket with the screen unlocked, all kinds of strange things happen when the screen gets activated by some app or another.
As for fingerprint, my phone does not have one. Even if my next phone had a fingerprint reader, it would be of no use when located in the back and the phone is sitting in any kind of holder or cradle.
hu...@google.com <hu...@google.com>
wd...@google.com <wd...@google.com> #3
We have passed this to the development team and will update this issue with more information as it becomes available.
wd...@google.com <wd...@google.com> #4
@3 Please do consider re-adding this feature.
There are actually people who think it's an awesome thing to have. Even medical cases, such as this one:
https://issuetracker.google.com/issues/65425413#comment37
There are actually people who think it's an awesome thing to have. Even medical cases, such as this one:
ja...@google.com <ja...@google.com> #5
Bring back NFC unlock. Or add NFC U2F unlock with something like Yubikey.
wd...@google.com <wd...@google.com> #6
Another thing I would like to see is custom Smart Unlock providers. This way a company like Yubikey could add support for NFC U2F dongles.
wd...@google.com <wd...@google.com>
wn...@google.com <wn...@google.com> #7
It was really useful to me, I had a nfc tag near my mouse pad. It was safer and much more precise compared to gps location!
Description
3.1 canary 8
Emulator Version (Emulator--> Extended Controls--> Emulator Version): 27.1.9-4592662
HAXM / KVM Version:
Android SDK Tools:
Host Operating System: glinux
CPU Manufacturer: [Intel / AMD / Other]
Steps to Reproduce Bug:
1. Create an x86 /w google apis kitkat image, 2gb internal storage
2. Start the emulator
3. run: adb shell df
4. Stop the emulator
5. Edit emulator settings through the studio UI: advanced -> set "Internal Storage" to 4000 mb
6. Save & start emulator
7. run: adb shell df
Expected Behavior:
Step 7 should have more space available than step 3
Observed Behavior:
They show the same df output.
In the .avd directory, I see:
-rw-r----- 1 agrieve primarygroup 2.0G Mar 16 10:45 userdata-qemu.img.qcow2
-rw-r----- 1 agrieve primarygroup 2.0G Feb 21 11:38 userdata.img
-rw------- 1 agrieve primarygroup 5.9G Mar 16 10:38 userdata-qemu.img
Note: at one point I tried setting 6000MB, so probably why there's a 6gb file (although I've since set it to 4000 again).
Seems like that is too many files? Wrong one being used?
config.ini makes no mention of "userdata"