Search results

If this flag is set, on a device capable of HW decryption, can the build end up still not supporting decryption? Can decryption be supported, practically, without this flag? Any software-only implementations?

If it's just a superset, you may say it can only be better. But I will concede that if the superset is not as rigorously tested it may have bugs that weren't in the baseline.

TARGET_HW_DISK_ENCRYPTION in BoardConfig.mk means it supports decryption, right?

I see. That wasn't clear until your last, more detailed, reply. Thank you. I thought this is the main thread for OF because all the activity is here, and there's no dedicated OF discussion for the device.

When it starts, this is what I get when it tries to mount:

Doesn't OrangeFox aim to support decryption of /data partitions? Else, why does OrangeFox ask for decryption password when starting up?

Decryption support on Redmi 5.

Does this TWRP patch make sense: https://forum.xda-developers.com/redmi-5/development/official-official-twrp-xiaomi-redmi-5-t3727158/post77607048#post77607048

How does KEEPVERITY work? I thought dm-verity means that a boot partition modified by Magisk will be detected.

... duplicate message ...

If you're saying dm-verity checks also the recovery partition, I think I may have misinterpreted something from the TWRP site about dm-verity: I took "system modifications" to mean the system partition and maybe boot partition, and the fact that you don't have to mount those in TWRP, an action...

Is OrangeFox a better idea than TWRP for this device?

What are the use cases for this tool? Are there cases where it's needed also when using Magisk? When is fstab modification important?

I thought dm-verity only checks the system and boot partitions.

Here's one password manager that's supposed to support TOTP: https://play.google.com/store/apps/details?id=keepass2android.keepass2android It's probably more complex to use than stuff like MS/Google Authenticator. A short search on the web suggests even Google Authenticator doesn't have a...

But as far as I understand, (when there's no A/B) recoveries just modify the recovery partition, which isn't protected by dm-verity. So if you install just a recovery, it doesn't matter? If I got it right, with A/B the recovery has become part of the boot partition. If dm-verity protects that...

Don't recoveries store all their data in the recovery partition, which is not verified? Or is the assumption that installation will include stuff like Magisk, which modifies the boot partition? Is the situation different with A/B partitions?

I've never used the Microsoft app but I think it uses a standard method similar to Google Authenticator and others: https://en.wikipedia.org/wiki/Time-based_One-time_Password_algorithm You might be able, somehow, to export the secret key and other parameters (these could be common defaults)...

Thanks for confirming!

In many threads you can only view the first page. Pages 2 and on lead to a 403 error. It's been like that for a while now. I'm thinking maybe it's about the HTTP referer header, but it happens randomly and I'm not sure what the point would be to disallow navigation to plain pages. Any idea...

Thanks for the info. It's not a Surface, but yes, a similar x86 Windows tablet with keyboard attachment. I believe also all-in-one computers have multi-touch, and probably touchscreen laptops. And yes, I mean notifying the guest Android of orientation changes from the host OS.

Does LeapDroid support touch input and orientation change notifications from Windows?

What's the difference between 20A, 20B, 20C, and so on? Are these different regions, or newer revisions of version 20? Any harm in trying a different version than what the phone came with?

I have a G2 that wants a decryption password on startup. It's rooted, and with stock recovery. I reflashed with the LG tool, and did a "wipe data/factory reset" in recovery mode. The password problem remains. I noticed that recovery mode complains "failed to mount /cache (Unknown error 150)"...

It definitely shows apps on Samsungs with v4, but I can't say I looked in depth on too many v2 devices. Are you sure? It'd seem half-pointless. At least some screenshots on the web show apps on Android v2 (but I guess it could be a customized version):

Thanks. I've actually had a look before on this one, but it can't be used to manually set the date/time. Only automatically after getting the info from the internet.

Can anyone suggest a simple app, for rooted, to set the date and time? Something similar to the the option you normally find in the Settings.

I'm on a rooted v2.3.4 phone. The stock battery usage graph screen doesn't show any apps, only core Android elements like Phone Idle, WiFi, Display, etc. It's not because apps didn't use enough CPU time. Any idea how to fix it?

Automatic time setting is usually a toggle you can turn off.

A temporary fix is to root the phone (e.g., UnlockRoot for a more automated process), then use an app that can set the system time. I'm not aware of one, actually, but a time sync app might do in a pinch, like ClockSync.

I have a Samsung i9070 with v4.1 on which I want to reenable the new user popup tips (those with a "don't show again" checkbox) that show when you first use a fresh phone/OS, and introduce the user to various gestures and UI ideas. I don't want to do a complete reset, just to get these popups...