MastodonTech.de

AptiviGoogle Play System Update (June 2025) rolls out for Samsung devicesGoogle Play System Update was a feature that was introduced for devices that ship with Android 10 or newer. It’s mandatory for device manufacturers that plan to release their devices with Android 10 to support Google Play System Updates. As a result, non-Google devices, such as Samsung Galaxy phones and tablets released with Android 10 (One UI 2.1), can receive such updates, too.These updates don’t require security updates from the manufacturer to work, as Project Mainline modules work independently to give you better experience with Android phones and tablets.On July 1st, a new Google Play System Update has been pushed to Samsung devices. This update upgrades your Project Mainline modules to the June 1st, 2025 version. This update weighs around 75 MB.To be able to get this version, follow these steps:<ol><li>Go to your device’s settings</li><li>Open the security settings</li><li>Find “Google Play System Update” and tap on it</li><li>If everything goes OK, you should see the below update dialog:</li></ol>Click on Download and Install, wait for it to download, then reboot your device by clicking on the blue Restart button. The next time your device boots up, the revised update gets installed, so it’s going to take about 3 minutes maximum to install all the updates.There is no progress bar, so don’t panic if it looks stuck. Your device will eventually boot up. Now, open your settings app and check your Google Play System Update. If everything is well, you should see June 1st, 2025 below the appropriate button.In case your device didn’t receive the update, wait for a few days, and it will be available shortly.Stay tuned for the July patch of 2025!<a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android/" target="_blank">#Android</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android-12/" target="_blank">#Android12</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android-12l/" target="_blank">#Android12L</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android-13/" target="_blank">#Android13</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android-14/" target="_blank">#Android14</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android-15/" target="_blank">#Android15</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android-16/" target="_blank">#Android16</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android-17/" target="_blank">#Android17</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android-b/" target="_blank">#AndroidB</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android-c/" target="_blank">#AndroidC</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android-t/" target="_blank">#AndroidT</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android-u/" target="_blank">#AndroidU</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android-update/" target="_blank">#AndroidUpdate</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android-v/" target="_blank">#AndroidV</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/december/" target="_blank">#December</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/google/" target="_blank">#google</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/google-play/" target="_blank">#googlePlay</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/google-play-system-update/" target="_blank">#GooglePlaySystemUpdate</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/mainline/" target="_blank">#mainline</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/news/" target="_blank">#news</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/operating-system/" target="_blank">#operatingSystem</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/project-mainline/" target="_blank">#ProjectMainline</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/smartphone/" target="_blank">#smartphone</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/system/" target="_blank">#system</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/system-update/" target="_blank">#systemUpdate</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/technology/" target="_blank">#Technology</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/update/" target="_blank">#update</a>

securityaffairs<a href="https://infosec.exchange/tags/Mainline" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mainline</a> <a href="https://infosec.exchange/tags/Health" class="mention hashtag" rel="nofollow noopener" target="_blank">#Health</a> Systems data breach impacted over 100,000 individuals <a href="https://securityaffairs.com/179322/data-breach/mainline-health-systems-disclosed-a-data-breach.html" rel="nofollow noopener" translate="no" target="_blank">https://securityaffairs.com/179322/data-breach/mainline-health-systems-disclosed-a-data-breach.html</a> <a href="https://infosec.exchange/tags/securityaffairs" class="mention hashtag" rel="nofollow noopener" target="_blank">#securityaffairs</a> <a href="https://infosec.exchange/tags/hacking" class="mention hashtag" rel="nofollow noopener" target="_blank">#hacking</a> <a href="https://infosec.exchange/tags/malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#malware</a>

Pyrzout :vm:Mainline Health, Select Medical Each Disclose Data Breaches Impacting 100,000 People <a href="https://www.securityweek.com/mainline-health-select-medical-each-disclose-data-breaches-impacting-100000-people/" rel="nofollow noopener" translate="no" target="_blank">https://www.securityweek.com/mainline-health-select-medical-each-disclose-data-breaches-impacting-100000-people/</a> <a href="https://social.skynetcloud.site/tags/SelectMedical" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelectMedical</a> <a href="https://social.skynetcloud.site/tags/DataBreaches" class="mention hashtag" rel="nofollow noopener" target="_blank">#DataBreaches</a> <a href="https://social.skynetcloud.site/tags/databreach" class="mention hashtag" rel="nofollow noopener" target="_blank">#databreach</a> <a href="https://social.skynetcloud.site/tags/healthcare" class="mention hashtag" rel="nofollow noopener" target="_blank">#healthcare</a> <a href="https://social.skynetcloud.site/tags/Mainline" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mainline</a>

Kevin Karhan :verified:Thanks to <a href="https://mastodon.social/@geerlingguy" class="u-url mention" rel="nofollow noopener" target="_blank">@geerlingguy</a> for <a href="https://www.youtube.com/watch?v=GKGtRrElu30&t=290" rel="nofollow noopener" target="_blank">addressing the elephant in the room.</a><a href="https://mastodon.social/@RaspberryPi" class="u-url mention" rel="nofollow noopener" target="_blank">@RaspberryPi</a> dominates the <a href="https://infosec.space/tags/SBC" class="mention hashtag" rel="nofollow noopener" target="_blank">#SBC</a> market because they know how to write <a href="https://infosec.space/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a> and build <a href="https://infosec.space/tags/drivers" class="mention hashtag" rel="nofollow noopener" target="_blank">#drivers</a> that get accepted into <a href="https://infosec.space/tags/mainline" class="mention hashtag" rel="nofollow noopener" target="_blank">#mainline</a> <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> kernel.<ul><li>The best specs and hardware is useless if it needs intimate knowledge on how to roll one's own kernel. And oftentimes one doesn't even get proper drivers and reproduceable build instructions but just some "vomited" out bootable images to <code>dd</code> onto a microSD!</li></ul>That's why my <a href="https://infosec.space/tags/BananPi" class="mention hashtag" rel="nofollow noopener" target="_blank">#BananPi</a> Zero M2 is still unused to this day: It's way too inconvenient and whilst I <a href="https://github.com/OS-1337/OS1337/blob/c4a19af5a62d7afbb80dfc416773a92074e6cc32/docu/ideas/architectures.tsv#L10" rel="nofollow noopener" target="_blank">do want to support it someday</a>, it's just not a good start when the 1st <a href="https://infosec.space/tags/RasperryPi" class="mention hashtag" rel="nofollow noopener" target="_blank">#RasperryPi</a>'s documentation to this day is still the bare minimum and vendors can't be assed to do that.<ul><li>The only reason <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#amd64</a>-based <a href="https://infosec.space/tags/SBC" class="mention hashtag" rel="nofollow noopener" target="_blank">#SBC</a>|s don't have the same issues as <a href="https://infosec.space/tags/arm64" class="mention hashtag" rel="nofollow noopener" target="_blank">#arm64</a> is because <a href="https://infosec.space/tags/BIOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#BIOS</a> & <a href="https://infosec.space/tags/UEFI" class="mention hashtag" rel="nofollow noopener" target="_blank">#UEFI</a>-boot alongside the way <a href="https://infosec.space/tags/hardware" class="mention hashtag" rel="nofollow noopener" target="_blank">#hardware</a> is initialized make it trivial to make it "go brrrr..."</li></ul>

AptiviGoogle Play System Update (May 2025) rolls out for Samsung devicesGoogle Play System Update was a feature that was introduced for devices that ship with Android 10 or newer. It’s mandatory for device manufacturers that plan to release their devices with Android 10 to support Google Play System Updates. As a result, non-Google devices, such as Samsung Galaxy phones and tablets released with Android 10 (One UI 2.1), can receive such updates, too.These updates don’t require security updates from the manufacturer to work, as Project Mainline modules work independently to give you better experience with Android phones and tablets.On June 10th, a new Google Play System Update has been pushed to Samsung devices. This update upgrades your Project Mainline modules to the May 1st, 2025 version. This update weighs around 87 MB.To be able to get this version, follow these steps:<ol><li>Go to your device’s settings</li><li>Open the security settings</li><li>Find “Google Play System Update” and tap on it</li><li>If everything goes OK, you should see the below update dialog:</li></ol>Click on Download and Install, wait for it to download, then reboot your device by clicking on the blue Restart button. The next time your device boots up, the revised update gets installed, so it’s going to take about 3 minutes maximum to install all the updates.There is no progress bar, so don’t panic if it looks stuck. Your device will eventually boot up. Now, open your settings app and check your Google Play System Update. If everything is well, you should see May 1st, 2025 below the appropriate button.In case your device didn’t receive the update, wait for a few days, and it will be available shortly.Stay tuned for the June patch of 2025!<a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android/" target="_blank">#Android</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android-12/" target="_blank">#Android12</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android-12l/" target="_blank">#Android12L</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android-13/" target="_blank">#Android13</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android-14/" target="_blank">#Android14</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android-15/" target="_blank">#Android15</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android-16/" target="_blank">#Android16</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android-t/" target="_blank">#AndroidT</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android-u/" target="_blank">#AndroidU</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android-update/" target="_blank">#AndroidUpdate</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android-v/" target="_blank">#AndroidV</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/android-w/" target="_blank">#AndroidW</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/december/" target="_blank">#December</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/google/" target="_blank">#google</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/google-play/" target="_blank">#googlePlay</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/google-play-system-update/" target="_blank">#GooglePlaySystemUpdate</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/mainline/" target="_blank">#mainline</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/news/" target="_blank">#news</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/operating-system/" target="_blank">#operatingSystem</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/project-mainline/" target="_blank">#ProjectMainline</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/smartphone/" target="_blank">#smartphone</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/system/" target="_blank">#system</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/system-update/" target="_blank">#systemUpdate</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/technology/" target="_blank">#Technology</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/update/" target="_blank">#update</a>

OlimexiMX8MaxPlus The Open Source Hardware board iMX8-SOM-4GB got OpenWRT support from Zoltan Herpai <a href="https://olimex.wordpress.com/2025/06/09/openwrt-support-for-the-open-source-hardware-imx8maxplus-board-imx8-som-4gb/" rel="nofollow noopener" translate="no" target="_blank">https://olimex.wordpress.com/2025/06/09/openwrt-support-for-the-open-source-hardware-imx8maxplus-board-imx8-som-4gb/</a> <a href="https://mastodon.social/tags/nxp" class="mention hashtag" rel="nofollow noopener" target="_blank">#nxp</a> <a href="https://mastodon.social/tags/imx8maxplus" class="mention hashtag" rel="nofollow noopener" target="_blank">#imx8maxplus</a> <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://mastodon.social/tags/mainline" class="mention hashtag" rel="nofollow noopener" target="_blank">#mainline</a> <a href="https://mastodon.social/tags/openwrt" class="mention hashtag" rel="nofollow noopener" target="_blank">#openwrt</a> <a href="https://mastodon.social/tags/oshw" class="mention hashtag" rel="nofollow noopener" target="_blank">#oshw</a>

Kevin Karhan :verified:<a href="https://gaysex.cloud/@sodiboo" class="u-url mention" rel="nofollow noopener" target="_blank">@sodiboo</a> <a href="https://possum.city/@tauon" class="u-url mention" rel="nofollow noopener" target="_blank">@tauon</a> <a href="https://transfem.social/@puppygirlhornypost2" class="u-url mention" rel="nofollow noopener" target="_blank">@puppygirlhornypost2</a> <a href="https://possum.city/@silly" class="u-url mention" rel="nofollow noopener" target="_blank">@silly</a> I don't think it's much of a "<a href="https://infosec.space/tags/freedom" class="mention hashtag" rel="nofollow noopener" target="_blank">#freedom</a>" on <a href="https://infosec.space/tags/iOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#iOS</a> but rather that the few devices and OS versions in circulation, alongside everyone from <a href="https://infosec.space/tags/jailbreaker" class="mention hashtag" rel="nofollow noopener" target="_blank">#jailbreaker</a> to <a href="https://infosec.space/tags/malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#malware</a> (espechally <a href="https://infosec.space/tags/govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#govware</a> <a href="https://infosec.space/tags/developers" class="mention hashtag" rel="nofollow noopener" target="_blank">#developers</a>) want to crack it open result in way more personnel and money behind it.<ul><li>OFC the fact that the <a href="https://infosec.space/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#Android</a> experience is worse from that POV is the lack of <a href="https://infosec.space/tags/regulation" class="mention hashtag" rel="nofollow noopener" target="_blank">#regulation</a> re: <a href="https://infosec.space/tags/repairability" class="mention hashtag" rel="nofollow noopener" target="_blank">#repairability</a> and <a href="https://infosec.space/tags/openness" class="mention hashtag" rel="nofollow noopener" target="_blank">#openness</a> that would make shit work. Most cheap <a href="https://infosec.space/tags/phones" class="mention hashtag" rel="nofollow noopener" target="_blank">#phones</a> are done with even cheaper <a href="https://infosec.space/tags/SoC" class="mention hashtag" rel="nofollow noopener" target="_blank">#SoC</a>'s by manufacturers who can't be assed (or frankly don't give a shit at all!) when it comes to <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://infosec.space/tags/mainline" class="mention hashtag" rel="nofollow noopener" target="_blank">#mainline</a> support. (I mean, you've seen the video where <a href="https://mastodon.social/@SexyCyborg" class="u-url mention" rel="nofollow noopener" target="_blank">@SexyCyborg</a> demanded a vendor to give her the sourcecode as per <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2</a> for her device?)</li></ul>Granted <a href="https://grapheneos.social/@GrapheneOS" class="u-url mention" rel="nofollow noopener" target="_blank">@GrapheneOS</a> does limit their support to devices that can comply with their <a href="https://infosec.space/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> standards.<ul><li>The issues are mostly caused by hostile app developers that specifically decided to knee-jerk their users / customers for no good reason.</li></ul>I do wish for both vendors like <a href="https://infosec.space/tags/Fairphone" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fairphone</a> to up their game and regulators like <a href="https://ec.social-network.europa.eu/@EUCommission" class="u-url mention" rel="nofollow noopener" target="_blank">@EUCommission</a> to actually push for more <a href="https://infosec.space/tags/transparency" class="mention hashtag" rel="nofollow noopener" target="_blank">#transparency</a>, <a href="https://infosec.space/tags/openness" class="mention hashtag" rel="nofollow noopener" target="_blank">#openness</a> and <a href="https://infosec.space/tags/LongTermSupport" class="mention hashtag" rel="nofollow noopener" target="_blank">#LongTermSupport</a> of <a href="https://infosec.space/tags/Smartphones" class="mention hashtag" rel="nofollow noopener" target="_blank">#Smartphones</a>, because <a href="https://infosec.space/tags/ManufacturedEwaste" class="mention hashtag" rel="nofollow noopener" target="_blank">#ManufacturedEwaste</a> like <a href="https://infosec.space/tags/SOYES" class="mention hashtag" rel="nofollow noopener" target="_blank">#SOYES</a>, <a href="https://infosec.space/tags/WiKo" class="mention hashtag" rel="nofollow noopener" target="_blank">#WiKo</a>, <a href="https://infosec.space/tags/Unihertz" class="mention hashtag" rel="nofollow noopener" target="_blank">#Unihertz</a> and others that ship <a href="https://infosec.space/tags/outdated" class="mention hashtag" rel="nofollow noopener" target="_blank">#outdated</a> <a href="https://infosec.space/tags/AndroidDevices" class="mention hashtag" rel="nofollow noopener" target="_blank">#AndroidDevices</a> and never even a single update are a major problem!<ul><li>I don't blame projects like <a href="https://fosstodon.org/@LineageOS" class="u-url mention" rel="nofollow noopener" target="_blank">@LineageOS</a> that they can't cover every device & SoC even tho they propably have the widest compatibility, I just think that there needs to be pressure that manufacturers don't just vomit stuff on the market and let customers frustratingly figure out the rest.</li></ul>I do have to give <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apple</a> credit where it is due, and that is that <a href="https://infosec.space/tags/iOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#iOS</a> does have consistency and accessibility nailed down very well. Something that they obviously are able being the "<a href="https://infosec.space/tags/BenevolentDictator" class="mention hashtag" rel="nofollow noopener" target="_blank">#BenevolentDictator</a>" of a <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleVendor</a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleProvider</a> - platform. <ul><li>Obviously since they are the <a href="https://infosec.space/tags/vendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#vendor</a> for <a href="https://infosec.space/tags/hardware" class="mention hashtag" rel="nofollow noopener" target="_blank">#hardware</a> and the sole ["legitimate" / official] <a href="https://infosec.space/tags/distributor" class="mention hashtag" rel="nofollow noopener" target="_blank">#distributor</a> for any <a href="https://infosec.space/tags/Apps" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apps</a> they do OFC cross-finance their relatively long <a href="https://infosec.space/tags/support" class="mention hashtag" rel="nofollow noopener" target="_blank">#support</a> with their 15-30% cut from <a href="https://infosec.space/tags/App" class="mention hashtag" rel="nofollow noopener" target="_blank">#App</a> <a href="https://infosec.space/tags/sales" class="mention hashtag" rel="nofollow noopener" target="_blank">#sales</a> & <a href="https://infosec.space/tags/InAppPurchase" class="mention hashtag" rel="nofollow noopener" target="_blank">#InAppPurchase</a>|s they charge, which is why <a href="https://infosec.space/tags/AndroidPhones" class="mention hashtag" rel="nofollow noopener" target="_blank">#AndroidPhones</a> suffer the "<a href="https://infosec.space/tags/3DO" class="mention hashtag" rel="nofollow noopener" target="_blank">#3DO</a> syndrome": Needing to charge more since they only get to make money once with hardware sales and not after that, so there's no incentive for them to give a shit beyond "brand value" to care. <a href="https://infosec.space/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#Google</a>, <a href="https://infosec.space/tags/Samsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#Samsing</a>, <a href="https://infosec.space/tags/Fairphone" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fairphone</a> and very few others do, but most don't as they close the books on the product once launched and sold out (angrily stares at Unihertz)...</li></ul>Maybe one day the folks at <a href="https://fosstodon.org/@frameworkcomputer" class="u-url mention" rel="nofollow noopener" target="_blank">@frameworkcomputer</a> acquire Fairphone and decide to bring the same modularity to <a href="https://infosec.space/tags/Smartphones" class="mention hashtag" rel="nofollow noopener" target="_blank">#Smartphones</a> and get something done that makes it easy to maintain long-term and that even <a href="https://infosec.space/tags/GrapheneOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#GrapheneOS</a> are willing to support.<ul><li>Until then the <a href="https://infosec.space/tags/Enshittification" class="mention hashtag" rel="nofollow noopener" target="_blank">#Enshittification</a> is ruining everything as usual...</li></ul>

Tomeu VizosoFinally found time to continue work on the Rockchip NPU. Plan to give this a strong push in the next few months:<a href="https://blog.tomeuvizoso.net/2025/05/rockchip-npu-update-5-progress-on.html" rel="nofollow noopener" translate="no" target="_blank">https://blog.tomeuvizoso.net/2025/05/rockchip-npu-update-5-progress-on.html</a><a href="https://mastodon.social/tags/rockchip" class="mention hashtag" rel="nofollow noopener" target="_blank">#rockchip</a> <a href="https://mastodon.social/tags/rk3588" class="mention hashtag" rel="nofollow noopener" target="_blank">#rk3588</a> <a href="https://mastodon.social/tags/machinelearning" class="mention hashtag" rel="nofollow noopener" target="_blank">#machinelearning</a> <a href="https://mastodon.social/tags/npu" class="mention hashtag" rel="nofollow noopener" target="_blank">#npu</a> <a href="https://mastodon.social/tags/mesa3d" class="mention hashtag" rel="nofollow noopener" target="_blank">#mesa3d</a> <a href="https://mastodon.social/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#kernel</a> <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://mastodon.social/tags/mainline" class="mention hashtag" rel="nofollow noopener" target="_blank">#mainline</a> <a href="https://mastodon.social/tags/tensorflow" class="mention hashtag" rel="nofollow noopener" target="_blank">#tensorflow</a>

Daniele Verducci 🧉Nice to see the <a class="hashtag" href="https://social.ichibi.eu/tag/esphome" rel="nofollow noopener" target="_blank">#esphome</a> test card on an <a class="hashtag" href="https://social.ichibi.eu/tag/eink" rel="nofollow noopener" target="_blank">#eink</a> display! The way the colors are mapped is not in my code, but I can see how they make sense: the left part of the R box is a scale of reds clearer of 50% red, the right part are the darker ones. So it is posterized to white and red respectively. It's interesting how the other colors are mapped to white. I imagine it makes sense, <a class="hashtag" href="https://social.ichibi.eu/tag/epaper" rel="nofollow noopener" target="_blank">#epaper</a> displays are a completely different beasts from a classic RGB display like an LCD... Now to the pull request! I'd like my code to go in <a class="hashtag" href="https://social.ichibi.eu/tag/mainline" rel="nofollow noopener" target="_blank">#mainline</a> esphome! [continues...]

Ivey Janette McClellandLower Merion.Where Black parents may eventually have to firm their own school. <a href="https://mastodon.social/tags/lowermerion" class="mention hashtag" rel="nofollow noopener" target="_blank">#lowermerion</a> <a href="https://mastodon.social/tags/mainline" class="mention hashtag" rel="nofollow noopener" target="_blank">#mainline</a> <a href="https://mastodon.social/tags/philadelphia" class="mention hashtag" rel="nofollow noopener" target="_blank">#philadelphia</a> <a href="https://mastodon.social/tags/ardmore" class="mention hashtag" rel="nofollow noopener" target="_blank">#ardmore</a> <a href="https://mastodon.social/tags/blackmastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#blackmastodon</a> <a href="https://mastodon.social/tags/montgomerycounty" class="mention hashtag" rel="nofollow noopener" target="_blank">#montgomerycounty</a> <a href="https://www.inquirer.com/education/lower-merion-school-district-racial-achievement-gap-students-20250312.html" rel="nofollow noopener" translate="no" target="_blank">https://www.inquirer.com/education/lower-merion-school-district-racial-achievement-gap-students-20250312.html</a>

Leniwcowaty :linuxmintnew:Hey there! Anyone rocking <a href="https://fosstodon.org/tags/liquorix" class="mention hashtag" rel="nofollow noopener" target="_blank">#liquorix</a> or <a href="https://fosstodon.org/tags/mainline" class="mention hashtag" rel="nofollow noopener" target="_blank">#mainline</a> kernel on <a href="https://fosstodon.org/tags/LinuxMint" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxMint</a>? Is it stable enough to use and not break anything? I want to have these fancy new AMD performance boosts from 6.13 on my main gaming PC, but I don't want my OS to glitch out or break...

Tomeu VizosoFound some time to write a short update on a recent accomplishment:<a href="https://blog.tomeuvizoso.net/2024/11/etnaviv-npu-update-21-support-for-npu.html" rel="nofollow noopener" translate="no" target="_blank">https://blog.tomeuvizoso.net/2024/11/etnaviv-npu-update-21-support-for-npu.html</a><a href="https://mastodon.social/tags/ideasonboard" class="mention hashtag" rel="nofollow noopener" target="_blank">#ideasonboard</a> <a href="https://mastodon.social/tags/etnaviv" class="mention hashtag" rel="nofollow noopener" target="_blank">#etnaviv</a> <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://mastodon.social/tags/mainline" class="mention hashtag" rel="nofollow noopener" target="_blank">#mainline</a> <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a>

casey (pattable)<a href="https://social.treehouse.systems/tags/Qualcomm" class="mention hashtag" rel="nofollow noopener" target="_blank">#Qualcomm</a> <a href="https://social.treehouse.systems/tags/Snapdragon" class="mention hashtag" rel="nofollow noopener" target="_blank">#Snapdragon</a> X elite go brrrrrgot the Lenovo Yoga Slim 7 booting. it's vvvv nice !just needs some extra modules added to the initramfs and (bluergh) firmware you have to yoink from Windows if you want battery % and GPU.<a href="https://social.treehouse.systems/tags/postmarketOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#postmarketOS</a> <a href="https://social.treehouse.systems/tags/LinuxMobile" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxMobile</a> <a href="https://social.treehouse.systems/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://social.treehouse.systems/tags/Mainline" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mainline</a>

RLAB#ASD24 Chatarra Linux: del cajón al Mainline – Val <a href="https://fediverse.tv/videos/watch/5461939b-f834-4bad-a440-745edf801617" rel="nofollow noopener" translate="no" target="_blank">https://fediverse.tv/videos/watch/5461939b-f834-4bad-a440-745edf801617</a>

Kevin Karhan :verified:<a href="https://fosstodon.org/@kernellogger" class="u-url mention" rel="nofollow noopener" target="_blank">@kernellogger</a> if <a href="https://infosec.space/tags/PREEMPT_RT" class="mention hashtag" rel="nofollow noopener" target="_blank">#PREEMPT_RT</a> becomes <a href="https://infosec.space/tags/mainline" class="mention hashtag" rel="nofollow noopener" target="_blank">#mainline</a> that would certainly be good and make <a href="https://infosec.space/tags/embedded" class="mention hashtag" rel="nofollow noopener" target="_blank">#embedded</a> device develooment easier...

Kevin Karhan :verified:<a href="https://mastodon.social/@neingeist" class="u-url mention" rel="nofollow noopener" target="_blank">@neingeist</a> <a href="https://hackers.town/@LambdaCalculus" class="u-url mention" rel="nofollow noopener" target="_blank">@LambdaCalculus</a> <a href="https://hax0rbana.social/@adam" class="u-url mention" rel="nofollow noopener" target="_blank">@adam</a> <a href="https://snug.moe/@lunareclipse" class="u-url mention" rel="nofollow noopener" target="_blank">@lunareclipse</a> <a href="https://fosstodon.org/@armbian" class="u-url mention" rel="nofollow noopener" target="_blank">@armbian</a> Still, that doesn't change the fact that in terms of <a href="https://infosec.space/@kkarhan/112610414574615319" rel="nofollow noopener" target="_blank">documentation and support</a> they ain't even in the same league as <a href="https://raspberrypi.social/@Raspberry_Pi" class="u-url mention" rel="nofollow noopener" target="_blank">@Raspberry_Pi</a> and that really is a big problem, because that's what made the <a href="https://infosec.space/tags/RaspberryPi" class="mention hashtag" rel="nofollow noopener" target="_blank">#RaspberryPi</a> so successful.<ul><li>Because there are cheaper AND more powerful options on the market but they don't get traction due to lack of good <a href="https://infosec.space/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a> and <a href="https://infosec.space/tags/mainline" class="mention hashtag" rel="nofollow noopener" target="_blank">#mainline</a> support by the <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://infosec.space/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#kernel</a>. </li></ul>Remember:<ul><li>Software makes Operating Systems &</li><li>Operating Systems make Hardware.</li></ul>That's why <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apple</a>'s <a href="https://infosec.space/tags/ARM64" class="mention hashtag" rel="nofollow noopener" target="_blank">#ARM64</a>-v8.5A - based <a href="https://infosec.space/tags/SBCs" class="mention hashtag" rel="nofollow noopener" target="_blank">#SBCs</a> are gamechangers and why <a href="https://infosec.space/tags/AMD64" class="mention hashtag" rel="nofollow noopener" target="_blank">#AMD64</a>-based <a href="https://infosec.space/tags/PCs" class="mention hashtag" rel="nofollow noopener" target="_blank">#PCs</a> ain't dead like <a href="https://infosec.space/tags/ppc64" class="mention hashtag" rel="nofollow noopener" target="_blank">#ppc64</a> and <a href="https://infosec.space/tags/SPARCv9" class="mention hashtag" rel="nofollow noopener" target="_blank">#SPARCv9</a>: <ul><li>Because at the end of the day, people don't give a damn about specs and stuff, all they care about is getting their "Compute Needs" fulfilled at a price- and painpoint they can accept...</li></ul>Which is why I use <a href="https://infosec.space/tags/refurbished" class="mention hashtag" rel="nofollow noopener" target="_blank">#refurbished</a> and <a href="https://infosec.space/tags/surplus" class="mention hashtag" rel="nofollow noopener" target="_blank">#surplus</a>'d and64-based <a href="https://infosec.space/tags/ThinClients" class="mention hashtag" rel="nofollow noopener" target="_blank">#ThinClients</a> instead of a <a href="https://infosec.space/tags/Pi5B" class="mention hashtag" rel="nofollow noopener" target="_blank">#Pi5B</a> for <a href="https://infosec.space/tags/Server" class="mention hashtag" rel="nofollow noopener" target="_blank">#Server</a> work:<ul><li>They are cheap and they run basically all the stuff I care about.</li></ul>OFC they won't replace big clusters at work but if your homelab has to run off German Energy Prices then you want a machine that barely sips power...

FrankMEin neuer Forumbeitrag: <a href="https://linux-nerds.org/topic/1555/rockpro64-mainline-kernel-6-8-0-rc3" rel="nofollow noopener" translate="no" target="_blank">https://linux-nerds.org/topic/1555/rockpro64-mainline-kernel-6-8-0-rc3</a> 1555/rockpro64-mainline-kernel-6-8-0-rc3 <a href="https://nrw.social/tags/rockpro64" class="mention hashtag" rel="nofollow noopener" target="_blank">#rockpro64</a> <a href="https://nrw.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://nrw.social/tags/mainline" class="mention hashtag" rel="nofollow noopener" target="_blank">#mainline</a>

caseptRunning <a href="https://chaos.social/tags/mainline" class="mention hashtag" rel="nofollow noopener" target="_blank">#mainline</a> on the 10 year old Samsung Gear 2 smartwatch at <a href="https://chaos.social/@spline" class="u-url mention" rel="nofollow noopener" target="_blank">@spline</a>. Still quite unstable, but Sway in a full Debian starts!

DebugPoint - Linux &Dev PortalExplore the fantastic new features of Linux Kernel 6.7! Here's a breakdown of the key highlights: <a href="https://www.debugpoint.com/linux-kernel-6-7/" rel="nofollow noopener" translate="no" target="_blank">https://www.debugpoint.com/linux-kernel-6-7/</a><a href="https://floss.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://floss.social/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#kernel</a> <a href="https://floss.social/tags/mainline" class="mention hashtag" rel="nofollow noopener" target="_blank">#mainline</a> <a href="https://floss.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#mainline