Forwarded from Codeaurora Releases
New CodeLinaro OSS release detected!
Tag:
Manifests: Vendor - dummy (AUDIO_IOT.LA.11.0.R2) - dummy (GRAPHICS.LA.16.1.R2) - dummy (VIDEO.LA.5.1.R1) - dummy (LA.QISI.16.0.R1)
Chipsets:
Build ID: BQ2A.250705.001
Date: 2025-08-22T11:17:33.000+00:00
Tag:
LA.VENDOR.16.2.1.r1-03700-LAHAINA.0 Manifests: Vendor - dummy (AUDIO_IOT.LA.11.0.R2) - dummy (GRAPHICS.LA.16.1.R2) - dummy (VIDEO.LA.5.1.R1) - dummy (LA.QISI.16.0.R1)
Chipsets:
blair, canoe, common, kalama, lahaina612, sepolicy_vndr, sun, taro, vendor-common, wlanBuild ID: BQ2A.250705.001
Date: 2025-08-22T11:17:33.000+00:00
😐3
It's an IoT tag, don't expect your lahaina smartphones or tablets on stock to get a new vendor. Unless it's Fairphone or industrial device.
😐5
If you don't swipe on your keyboard yet (especially if it's Gboard and you often use English), you should absolutely start to, it's like riding a bike, except that not enough people will shame you for missing this skill.
(I just read that there are people who WANT the Xiaomi behavior of back gesture working over the keyboard which obviously breaks swiping, smh)
Alternatively, if you still refuse to swipe, I'll excuse you if your daily phone screen time doesn't exceed an hour. Otherwise, please learn it, for your own wellbeing. Disable typing personalisation and form a basic memory on which words you can expect to be easily swipable and ones you expect to need typing manually. From there, single handed typing will become actually pleasant and accurate.
(I just read that there are people who WANT the Xiaomi behavior of back gesture working over the keyboard which obviously breaks swiping, smh)
Alternatively, if you still refuse to swipe, I'll excuse you if your daily phone screen time doesn't exceed an hour. Otherwise, please learn it, for your own wellbeing. Disable typing personalisation and form a basic memory on which words you can expect to be easily swipable and ones you expect to need typing manually. From there, single handed typing will become actually pleasant and accurate.
❤12
Google is asking non-GP developers to identify themselves so that Google gets a better opportunity to show how extremely compliant they are by skipping the Play Protect nag screens on such third party verified developers
AND/OR
they're looking for a chance to be a bigger nuisance for apps distributed by third parties which refuse to identify themselves.
Either way, you already disabled Play Protect long ago, right? The chance that disabling Play Protect won't suffice is rather slim. Going so far as to require Google stamp on every sideloaded app no matter the way of installation would be absolutely great news to move privacy conscious people away from GMS Android, hence a bulletproof restriction is very unlikely. We don't even know if European Union and other countries are completely fine with existing Apple policy where they're always in your way of permanent installation of an "unauthorized" app. Google must balance their greed.
AND/OR
they're looking for a chance to be a bigger nuisance for apps distributed by third parties which refuse to identify themselves.
Either way, you already disabled Play Protect long ago, right? The chance that disabling Play Protect won't suffice is rather slim. Going so far as to require Google stamp on every sideloaded app no matter the way of installation would be absolutely great news to move privacy conscious people away from GMS Android, hence a bulletproof restriction is very unlikely. We don't even know if European Union and other countries are completely fine with existing Apple policy where they're always in your way of permanent installation of an "unauthorized" app. Google must balance their greed.
😐5
Google is asking non-GP developers to identify themselves so that Google gets a better opportunity to show how extremely compliant they are by skipping the Play Protect nag screens on such third party verified developers
AND/OR
they're looking for a chance to be a bigger nuisance for apps distributed by third parties which refuse to identify themselves.
Either way, you already disabled Play Protect long ago, right? The chance that disabling Play Protect won't suffice is rather slim. Going so far as to require Google stamp on every sideloaded app no matter the way of installation would be absolutely great news to move privacy conscious people away from GMS Android, hence a bulletproof restriction is very unlikely. We don't even know if European Union and other countries are completely fine with existing Apple policy where they're always in your way of permanent installation of an "unauthorized" app. Google must balance their greed.
AND/OR
they're looking for a chance to be a bigger nuisance for apps distributed by third parties which refuse to identify themselves.
Either way, you already disabled Play Protect long ago, right? The chance that disabling Play Protect won't suffice is rather slim. Going so far as to require Google stamp on every sideloaded app no matter the way of installation would be absolutely great news to move privacy conscious people away from GMS Android, hence a bulletproof restriction is very unlikely. We don't even know if European Union and other countries are completely fine with existing Apple policy where they're always in your way of permanent installation of an "unauthorized" app. Google must balance their greed.
😐13
(turns out adding same or two (?) captions for both images hides them completely)
🤯6❤1😐1
Tadi Channel
Google is asking non-GP developers to identify themselves so that Google gets a better opportunity to show how extremely compliant they are by skipping the Play Protect nag screens on such third party verified developers AND/OR they're looking for a chance…
🔥26😐2
Hacker News
Word documents will be saved to the cloud automatically on Windows going forward Article, Comments
Telegram
Tadi Channel
https://tuta.com/blog/how-to-disable-gemini-on-android
Don't login into your OS vendor's account. The capabilities and incentives of screwing you are way too high. "There was a contract which you accepted" is less of a working defense when a given contract…
Don't login into your OS vendor's account. The capabilities and incentives of screwing you are way too high. "There was a contract which you accepted" is less of a working defense when a given contract…
😐3
Tadi Channel
A friend said this phone is in large circulation among bot farms, so this LOS stats result can actually be legit.
I initially thought it's about Samsung, but it couldn't be. It's the non-2022 Oppo A57. Now it makes sense.
👍3😐1
https://fdn.gsmarena.com/imgroot/reviews/25/google-pixel-10-pro-xl/camera/gsmarena_024.jpg
Next step for AI-assisted zoom: make the fake license plates realistic by looking up the current location of user.
Next step for AI-assisted zoom: make the fake license plates realistic by looking up the current location of user.
😁15🔥2😐2
Tadi Channel
https://fdn.gsmarena.com/imgroot/reviews/25/google-pixel-10-pro-xl/camera/gsmarena_024.jpg Next step for AI-assisted zoom: make the fake license plates realistic by looking up the current location of user.
https://fdn.gsmarena.com/imgroot/reviews/25/google-pixel-10-pro-xl/camera/gsmarena_022.jpg
Currently it even struggles with buildings, something well known for straight shapes. Wouldn't be surprised if they're feeding a jpeg to the algo instead of raw, since the jpeg samples already exhibit worm-like shapes that shouldn't be there.
Currently it even struggles with buildings, something well known for straight shapes. Wouldn't be surprised if they're feeding a jpeg to the algo instead of raw, since the jpeg samples already exhibit worm-like shapes that shouldn't be there.
😁6😐1
https://www.feistyduck.com/newsletter/issue_128_google_debuts_device_bound_session_credentials_against_session_hijacking
Google came out with a mostly cool idea that can eventually turn into a nuisance and impossibility of backing up your logged in sessions (in worst case scenario, as web seems much less vulnerable to monopoly than embedded hardware). From the look of it, currently a TPM whitelist isn't a part of the standard and I've seen none of such plans.
Keep in mind: TrustZone, TPMs and hardware authentication devices are a genuinely cool thing that can save your ass. But whitelists of what third party entities consider as accepted are never right and will prevent you from making improvements or tradeoffs you deem acceptable. We shouldn't need vulnerabilities for capabilities.
Watch DBSC with caution.
Google came out with a mostly cool idea that can eventually turn into a nuisance and impossibility of backing up your logged in sessions (in worst case scenario, as web seems much less vulnerable to monopoly than embedded hardware). From the look of it, currently a TPM whitelist isn't a part of the standard and I've seen none of such plans.
Keep in mind: TrustZone, TPMs and hardware authentication devices are a genuinely cool thing that can save your ass. But whitelists of what third party entities consider as accepted are never right and will prevent you from making improvements or tradeoffs you deem acceptable. We shouldn't need vulnerabilities for capabilities.
Watch DBSC with caution.
😐3👏1