I'd like to enable Google Smartlock for passwords on my Google Pixel C, but when I was running Android N, under Settings/Security it shows my device as encrypted with no option to turn it off. So, I reloaded MM, N still has a lot of bugs I don't feel like messing with on an everyday tablet, but even under MM my device is encrypted with no option to disable it. Smartlock for passwords will not run on an encrypted device, but Google has decided to make encryption part of the OS. Is the only way around this is to unlock the bootloader and flash another ROM?
Rolldog said:
I'd like to enable Google Smartlock for passwords on my Google Pixel C, but when I was running Android N, under Settings/Security it shows my device as encrypted with no option to turn it off. So, I reloaded MM, N still has a lot of bugs I don't feel like messing with on an everyday tablet, but even under MM my device is encrypted with no option to disable it. Smartlock for passwords will not run on an encrypted device, but Google has decided to make encryption part of the OS. Is the only way around this is to unlock the bootloader and flash another ROM?
Click to expand...
Click to collapse
I never encrypt my devices so I couldn't speak about smart lock only working on encrypted devices. I know Marshmallow and up it's required for OEMs to encrypt (85% sure on that - I think it was supposed to start with Lollipop but OEMs weren't required to do so). Not that I don't believe you though, but that just seems weird for Google to "force" encryption but then allow another of their features, Smart Lock, to only work with unencrypted devices?
To answer your question - if you're running stock MM or N on a Google device, by default your data will be encrypted. The only way to decrypt would be to unlock the bootloader, format the data partition and flash a kernel that doesn't force encryption. You don't have to use another ROM per se, you just need a kernel that will keep you decrypted on your first boot.
I've no issue with smartlock on Pixel C, stock N5 and unencryted N9. I've only use trusted location - without GPS I wonder if you are having a problem with your location. Have you got "location" correctly set?
Ok, on your Pixel C, go into settings/Google, then scroll all the way to the bottom where it says Smartlock for Passwords, press it, and tell me what it says. When I do, it says, "This account uses custom passphrase encryption, which is unsupported at this time."
However, if I go to settings/security, I can enable Smart Lock, but just underneath where it says Smart Lock, it says:
Encryption
Encrypt Tablet
Encrypted
I never chose to encrypt anything, but, I guess Google uses encryption by default. Smart Lock can still be used, but Smartlock for Passwords can not.
Rolldog said:
Ok, on your Pixel C, go into settings/Google, then scroll all the way to the bottom where it says Smartlock for Passwords, press it, and tell me what it says. When I do, it says, "This account uses custom passphrase encryption, which is unsupported at this time."
However, if I go to settings/security, I can enable Smart Lock, but just underneath where it says Smart Lock, it says:
Encryption
Encrypt Tablet
Encrypted
I never chose to encrypt anything, but, I guess Google uses encryption by default. Smart Lock can still be used, but Smartlock for Passwords can not.
Click to expand...
Click to collapse
Sorry misunderstood. I think the answer is that using your own passphrase disables Smartlock on Android see: https://support.google.com/chrome/answer/1181035?p=settings_encryption&rd=1
"Some Google features will not be available after you set a sync passphrase
Google Now won’t show suggestions based on sites you browse in Chrome.
You won't be able to view your saved passwords on https://passwords.google.com or use Smart Lock for Passwords on Android.
Your history won't sync across devices. Web sites or URLs that you type in the address bar in Chrome will still sync."
Setting for Google/custom passphrase in chrome browser at chrome://settings/syncSetup
The strange thing is I don't use a custom passphrase, all of my information does sync between all of my devices, and I get Google Now cards based off my search history. However, last night, when I logged into an app, Smartlock for Passwords popped up and asked me if I wanted to save this password, so I guess it's working now. It still shows my tablet as encrypted, so I imagine it's just a bug.
Ok so I'm a little bit of a security freak, I care about how my data are secure on my device and make sure that not a single bit of Google's code is left and tracking me (I debloat roms myself).......... The biggest issue is Encryption
I have both OP3 and 3T
Pre OS setup
OP3:
- OB 28 firmware
- Blu.Spark TWRP 8.61
OP3T
- OB 19 Firmware
- Blu.Spark TWRP 8.61
The issue I faced is that once I set an encryption password I either cannot change it, or a garbage password will be set and I won't be able to boot to my phone again unless I "fastboot format userdata"
- Type 1 issue, Set encryption password but can't change later: happens in all RR and LOS based roms (I even read somewhere that this bug was reported but due to it not being a popular feature the issue was cancelled", they suggested that in order to change it I have to make a complete back up, decrypt, restore back up, and encrypt again with a new password.... And this is a no go for me.
- Type 2 issue, Set encryption password and a rubbish password will be set: this happened to me in a few AOSP based roms (CardinalOS for example), so if I set a pattern for example, the encryption password will not be the same pattern I set, thus I'll be locked out of my phone unless I format userdata
I tried the cryptfs command
"vdc cryptfs changepw password '<old encryption password>' <new password>"
But nothing changes
Not all AOSP roms have this issue tho, PureFusion ROM (which is AOSP based) is fine, and all OOS based roms are fine too
Is there any fix for such issue? I'd love to use another rom,
possibly RR (Currently using FreedomOS), but the encryption issue is bothering me
According to latest part of your post, the "buggy" cryptfs concerns only some custom roms.
How would you solve that issue? It's depending by rom developer, the only attempt you could try is a bug report.
But there's a good risk to be ignored, because many people are not so obsessed by security, developers won't to find time for very rare issues.
DaKing1512 said:
Ok so I'm a little bit of a security freak, I care about how my data are secure on my device and make sure that not a single bit of Google's code is left and tracking me (I debloat roms myself).......... The biggest issue is Encryption
I have both OP3 and 3T
Pre OS setup
OP3:
- OB 28 firmware
- Blu.Spark TWRP 8.61
OP3T
- OB 19 Firmware
- Blu.Spark TWRP 8.61
The issue I faced is that once I set an encryption password I either cannot change it, or a garbage password will be set and I won't be able to boot to my phone again unless I "fastboot format userdata"
- Type 1 issue, Set encryption password but can't change later: happens in all RR and LOS based roms (I even read somewhere that this bug was reported but due to it not being a popular feature the issue was cancelled", they suggested that in order to change it I have to make a complete back up, decrypt, restore back up, and encrypt again with a new password.... And this is a no go for me.
- Type 2 issue, Set encryption password and a rubbish password will be set: this happened to me in a few AOSP based roms (CardinalOS for example), so if I set a pattern for example, the encryption password will not be the same pattern I set, thus I'll be locked out of my phone unless I format userdata
I tried the cryptfs command
"vdc cryptfs changepw password '<old encryption password>' <new password>"
But nothing changes
Not all AOSP roms have this issue tho, PureFusion ROM (which is AOSP based) is fine, and all OOS based roms are fine too
Is there any fix for such issue? I'd love to use another rom,
possibly RR (Currently using FreedomOS), but the encryption issue is bothering me
Click to expand...
Click to collapse
If you really are concerned with security then stay on stock and lock your bootloader. Anything else weakens the security of a device.
But really really. Mobile security is a myth. It is a fear mongering tool used by people to keep you in line. If someone wants your info they will get it and they dont need your device.
this might happen with you , happened with me (✖╭╮✖)
I have encrypted my data on the M9 (see settings->storage->encryption) . Every time you reboot the phone, a prompt for the password (in my case a pattern) appears before the phone proceeds and decrypts your data. A failed attempt after 50(?) tries resets the phone to factory. Currently, the encryption option in settings is checked and not modifiable but rebooting never produces a decryption password query?
This is a SPRINT phone Android Ver.: 7.0 Security Patch level: Feb 1. 2017
Don't quote me on this but I think it applies to turning the phone off and back on. Once the phone knows the key it's pointless to keep asking every time you unlock the device because if you know the pattern then it is obviously you..
If anyone can help that would be awesome - this is the first time i have encountered this problem on an android device.
one of the first things i do is remove encryption on my android phones because
1. i like the option
and 2. i notice a considerable amount of difference.
now starting from Pie we have metadata encryption with file encryption
removing metadata encryption causes 0 problems.
however when i remove file encryption i run into a problem
i am un-able to setup a fingerprint (the option isnt even there anymore)
also when i set up a PIN, i am unable to change it (it says incorrect pin)
when i use the pin to unlock the phone, it says "wrong pin" but it works in unlocking the phone.
i didnt experience this on my oneplus 5/6 or samsung / huawei devices having them decrypted.
does anyone know how we can get fingerprint / pin working without encryption?
i notice the phone is more responsive and snappy without encryption
Hello,
I accidentally replaced my encryption password with the default encryption. Does anyone know if I can set my own one again?
I tried out "Macrodroid" with the goal to automatically enable and disable airplane mode and while trying out different things (bound to fingerprint gestures) it asked me for accessibility access which I allowed but then it (the accessibility settings page) asked for my password and said it was needed since accessibility is also related to encryption state or so. But I didn't enter my password and clicked on cancel, I don't know the app that well so I didn't want to give it access over my encryption.
My theory is now that it replaced my encryption password with the default one then because it didn't ask me again for my encryption password when I de- and reactivated accessibility.
I uninstalled the app then and use "Auto Airplane mode" now. I checked with "Sd-maid" for any leftovers and then rebooted and it didn't ask me for my password, I just straight booted into system. (Device is still encrypted but with standard password.)
Booted into twrp and it was able to surpass encryption, went straight to main twrp menu.
Is there any option to manually set the encryption password?
I think if I flash "disable-force-encrypt" again (like I did while installing my phone) I would have to format data, too in order to remove encryption and re-set it in system settings, or not?
My last option before totally reinstalling the ROM would be to restore a nandroid backup from after I installed it the first time.
Greetings,
7080