• Breaking News

    Monday, January 18, 2021

    Home Unlabelled Android Moronic Monday (Jan 18 2021) - Your weekly questions thread!

    Android Moronic Monday (Jan 18 2021) - Your weekly questions thread!

    January 18, 2021

    Android Moronic Monday (Jan 18 2021) - Your weekly questions thread!

    Moronic Monday (Jan 18 2021) - Your weekly questions thread!

    Posted: 18 Jan 2021 04:00 AM PST

    Note 1. Join us at /r/MoronicMondayAndroid, a sub serving as a repository for our retired weekly threads. Just pick any thread and Ctrl-F your way to wisdom!

    Note 2. Join our IRC, and Telegram chat-rooms! Please see our wiki for instructions.

    submitted by /u/curated_android
    [link] [comments]

    Gboard's Emoji Kitchen feature creates amazing emoji combos

    Posted: 17 Jan 2021 06:05 PM PST

    This Andoid Police article showed me the amazing ways of Gboard in messaging apps: 160 awesome, ridiculous, and downright creepy Gboard emoji combos you should try out

    submitted by /u/b-e-m
    [link] [comments]

    The macro camera of the Galaxy S21 Ultra is really impressive

    Posted: 17 Jan 2021 09:28 AM PST

    How Law Enforcement Gets Around Your Smartphone's Encryption

    Posted: 18 Jan 2021 02:20 AM PST

    This recently released research paper: Data Security on Mobile Devices: Current State of the Art, Open Problems, and Proposed Solutions by Matthew Green and his team which is also covered by WIRED talks about design flaw in data encryption of android and iOS. Wired brushes off most of the technical details and the paper didn't cover android's File Based Encryption very well which I think needs some clarity on it. The paper draws the correct conclusion though and what should be improved in successor android versions.

    In android 7+, /data partition is encrypted by File Based Encryption (FBE) on first boot by default. FBE keys are generated in hardware-backed keystore. FBE keys are encrypted in keystore with the key derived from user's screen lock password. So unless you enter correct password, keystore cannot decrypt FBE keys. When you reboot your device, it is in Before First Unlock (BFU) state which means the user has yet to unlock screen first time since reboot. In this state, if someone calls you or messages you, their name won't show up unless you unlock your screen. That's because the device is waiting for your lock screen password which is to be used to decrypt FBE keys and FBE keys are encrypting your contact names.

    Once you unlock your screen first time since reboot, it goes to After First Unlock (AFU) state which means the user has unlocked the device first time since reboot. Further locking and unlocking won't revert the state unless you reboot again which throws you back on BFU.

    In AFU state, FBE keys are decrypted by the keystore and re-encrypted using a per-boot temporary key (generated & stored in keystore) and cached in /system/vold. As FBE keys are cached though encrypted, you can now use your biometric to unlock screen and kernel can request keystore to decrypt FBE keys on demand means whenever an application wants to read and write, kernel will load FBE keys in memory and they will remain in memory until next reboot. That's because running apps need them for read and write even if you lock your screen. E.g. To display contacts on lock screen, sharing live location, sync services, etc. they need those keys in memory else they won't work on locked screen.

    This opens a security hole. Users don't often reboot their devices for months so it is in AFU state. The intruder and law enforcement can extract those keys from memory to decrypt sensitive data of running applications without knowing your screen lock. This procedure requires carefully exposing the SoC without disconnecting the battery.

    iOS encrypts personal data with keys that are evicted from memory 10 seconds after locking the screen. When it is in BFU state, iPhone needs password to derive a Class key. At this time, biometric won't work. When it is in AFU state, it caches Class key in T2 chip (Secure Element). Now user can use biometric and cached Class key is used to re-derive those evicted keys again when screen is locked and unlocked.

    This keys eviction feature is what android also needs otherwise if the intruder is able to decrypt whole /data partition, it can set enable bit for OEM unlocking, it goes to bootloader mode and unlocks the bootloader to own the device.

    In most cases, FBE keys also undergo an additional key derivation step in the kernel in order to generate the subkeys actually used to do the encryption, for example per-file or per-mode keys.

    If FBE keys are compromised, so will sub-keys so this derivation step doesn't add much protection even if sub-keys are evicted in newer versions. Android should keep FBE key bundle in keystore itself and load sub-keys in memory some of which can be evicted after screen lock.

    Law enforcement can just force your fingerprint to unlock your device and can lie about that in court that it was already unlocked at the time of arrest so no kind of device security can stop them. Locks deter only honest people.

    submitted by /u/crawl_dht
    [link] [comments]

    New icons let you see which apps are rising up and falling off the Play Store charts

    Posted: 17 Jan 2021 12:58 PM PST

    How the price of samsung galaxy phones changed over the years.

    Posted: 17 Jan 2021 10:39 AM PST

    Asus ROG Phone 4/5 Alleged Live Image Spotted in Wild, Reveals 64MP Camera and Design

    Posted: 17 Jan 2021 09:38 PM PST

    Samsung Galaxy Note20 Ultra Display review: Takes top ranking from its brand sibling (Highest score)

    Posted: 17 Jan 2021 04:36 PM PST

    BlackBerry Spark Suite recognized as an Android™ Enterprise Recommended solution

    Posted: 18 Jan 2021 02:45 AM PST

    Flashback: the original Samsung Galaxy S was a best-seller that spawned an empire

    Posted: 17 Jan 2021 07:44 AM PST

    Samsung Galaxy S21 Plus | Pro-Grade Camera - WOW

    Posted: 17 Jan 2021 04:13 PM PST

    Exynos 2100 Benchmarks by Beebom

    Posted: 18 Jan 2021 12:23 AM PST

    To whomever is interested, the Youtube channel Beebom ran some benchmarks of the Exynos 2100 vs the Snapdragon 888.
    ULR: https://www.youtube.com/watch?v=W6TUuhDUjRg

    Geekbench Results:

    Exynos 2100:

    Single-Core Score: 1074
    Multi-core Score: 3335

    Snapdragon 888:

    Single-Core Score: 1139
    Multi-core Score: 3810

    Antutu Scores:

    Exynos 2100:

    CPU: 175917
    GPU: 266031
    MEM: 118303
    UX: 83077

    Snapdragon 888:

    CPU: 197454
    GPU: 319439
    MEM: 124036
    UX: 99918

    submitted by /u/Antonis_32
    [link] [comments]

    Oppo Reno Pro 5G with MediaTek flagship chip launched for Rs 35,999

    Posted: 18 Jan 2021 12:32 AM PST

    Sunday Rant/Rage (Jan 17 2021) - Your weekly complaint thread!

    Posted: 17 Jan 2021 04:00 AM PST

    Note 1. Join our IRC, and Telegram chat-rooms! Please see our wiki for instructions.

    This weekly Sunday thread is for you to let off some steam and speak out about whatever complaint you might have about:

    • Your device.

    • Your carrier.

    • Your device's manufacturer.

    • An app

    • Any other company

    Rules

    1) Please do not target any individuals or try to name/shame any individual. If you hate Google/Samsung/HTC etc. for one thing that is fine, but do not be rude to an individual app developer.

    2) If you have a suggestion to solve another user's issue, please leave a comment but be sure it's constructive! We do not want any flame-wars.

    3) Be respectful of other's opinions. Even if you feel that somebody is "wrong" you don't have to go out of your way to prove them wrong. Disagree politely, and move on.

    submitted by /u/curated_android
    [link] [comments]
    Read more
    at

    No comments:

    Post a Comment