Your irregular reminder that Alpine Linux DOES NOT have any Telegram channels and any community use of the Alpine marks in a way which indicates an official relationship with or endorsement by the project is forbidden by our Code of Conduct.
Unfortunately, it is hard to get Telegram to do anything about this. We have been trying for years.
Yesterday evening I geeked on @postmarketOS and installed u-boot and a brand new version of postmarketOS on an "old" 2011 android 4.0 tablet. So happy to see this device with new up to date software π€©π
New product names coming right up:
GitHub β> CopilotHub
LinkedIn β> Copilot Unemployed
Xbox β> XCopilot
Teams β> CopilotSkype
Azure β> CopilotCloud
OneDrive β> CopilotDeleteurfiles
Edge β> CopilotExplorer
VSCode β> CopilotCursor
Bing β> Copilot4cucks
Defender β> CopilotNoViruses
Intune β> CopilotMalware
Windows β> CopilOS
Authenticator β> CopiletMeIn
the METR study is gonna go round again because Fortune *just* posted a fresh writeup of it yesterday, based on their own article from July
every time you see an AI guy dismiss it as insufficient, ask them where the better studies are. (there aren't any.)
Mailing list? Nah that's boomer shit, instead we use Blorboβ’ for communication and bug reporting, it's this cool new solution ICE set up in collaboration with Palantir. Yeah you can search it and keep backup logs you just need a blood sacrifice. You gotta understand we need a Project Communityβ’. Yeah that guy yelling slurs is my friend just deal with it or smth idk
Users of the π±FAIRPHONE 4οΈβ£ who avoided or did not get the ill-fated and retracted 15.15.2 update (see earlier toot above) should gradually get a new π² UPDATE 15.14.4
Going by the description in the forum and the version number, it might come without any of the changes that 15.15.2 was supposed to bring, but with the very most recent Android security patches (5 January 2026) β‘οΈ https://forum.fairphone.com/t/software-update-fp4-srel-15-14-4-20251229152255/128916?u=wearefairphone /u
Thanks to @newbyte's efforts and @agx's reviewing, everything relevant from the "postmarketOS tweaks" app has been integrated into Phosh Mobile Settings so that we were able to sunset the legacy app in postmarketOS edge and have one less settings app in total! π
As a bonus, Phosh Mobile Settings now has a generic conf-tweaks interface that can be used to add other custom settings with config files as well!
Details in the edge post:
https://postmarketos.org/edge/2026/01/04/postmarketos-tweaks-replaced/
#postmarketos #linuxmobile #phosh
https://social.phosh.mobi/users/phosh/statuses/01KE52S074EH28WZR7K13EW0XTSo for anyone playing at home, the Rockchip RV1126+ is a yet-undocumented variant of the Rockchip RV1126 that identifies itself as 0x112d rather than 0x1126.
The only mentions found about it are in the git log of rkbin, where they quote the git log of their OP-TEE fork, where they first βadd rv112d supportβ, and then βadd rv1126+ supportβ. The quick diff of the OP-TEE binary before and after those two updates shows that indeed, 0x112d is RV1126+.
The "fun" thing is that their other binaries that may care about how a chip identifies have not been made aware of the 0x112d variant.
For example, the usbplug binary (which is how rockusb is implemented by the vendor) is resetting out quite quickly out (which could mislead an unobservant developer in thinking it didn't even try to run).
This might help others:
Boot1 Release Time: Mar 29 2023 15:54:09, version: 1.24 NO FTL
Boot from dev = 10
chip_id:2d115652
hamming_distance:112d 1126 3
hamming_distance:112d 1109 2
chip_id:5256112d00,-1
ChipType = 22
Not sure what the best format to share a binary patch is, but here's the diff of the xxd output before and after. Hint, see the -r flag to xxd.
--- bin/rv11/rv1126_usbplug_v1.24.bin.xxd 2026-01-01 12:42:25.758834328 -0500
+++ rv1126_usbplug_v1.24.rv112d.patched.xxd 2026-01-01 12:42:06.817577746 -0500
@@ -90 +90 @@
-00000590: 9df8 1010 04f0 03fc 002c 14da b048 fff7 .........,...H..
+00000590: 9df8 1010 04f0 03fc 15e0 14da b048 fff7 .............H..
Β―\_(γ)_/Β―
RT: https://ap.samueldr.com/objects/65289274-1465-4d8c-9625-f3bae8de10e0
Dear @c3voc Once again: Thanx for your excellent work @ #39c3! π
And some constructive feedback on #Audio: I saw a user complaining about the Intros of recorded talks being too loud.
Did some measurements. (Perceived) Integrated Loudness compared:
βΆοΈ 1h Talk without Intro/Outro:
-24.1 dB LUFS
βΆοΈ 15sec Intro-Part:
-12.3 dB LUFS
Intro = nearly 12dBs louder than actual talk β that's a lot!!
For a more pleasant experience I'd recommend aiming for similar LUFS levels i.e. β€6dB difference.
π
Microslop Slopdows 11