home.social

#mainline — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #mainline, aggregated by home.social.

  1. New PSA for the sdm845-device users on @postmarketOS running edge:
    if you devices sensor suddenly stopped working since an update, check if also the -sensors device firmware package is installed, e.g. firmware-xiaomi-beryllium-sensors

    #mainline #mobilelinux #postmarketOS

  2. PSA for the sdm845-users in @postmarketOS running edge: linux-postmarketos-qcom-sdm845 was just updated to version 7.1!

    #mainline #mobilelinux #postmarketOS

  3. PSA for the sdm845-users in @postmarketOS running edge: linux-postmarketos-qcom-sdm845 was just updated to version 7.1!

    #mainline #mobilelinux #postmarketOS

  4. PSA for the sdm845-users in @postmarketOS running edge: linux-postmarketos-qcom-sdm845 was just updated to version 7.1!

    #mainline #mobilelinux #postmarketOS

  5. PSA for the sdm845-users in @postmarketOS running edge: linux-postmarketos-qcom-sdm845 was just updated to version 7.1!

    #mainline #mobilelinux #postmarketOS

  6. PSA for the sdm845-users in @postmarketOS running edge: linux-postmarketos-qcom-sdm845 was just updated to version 7.1!

    #mainline #mobilelinux #postmarketOS

  7. sooo i tried using the new b4 review TUI for my last U-Boot PR and it was a bit of a disaster. I understand the process being a bit clunky to begin with but the whole process of actually setting up a branch was really involved. It failed to update a bunch of series on pathwork, and the b4 ty emails it generated had completely wrong commit SHAs

    I get that the intention is primarily patch review but even for that it feels less like a tool i can utilise to automate the process and more like an imposed workflow that offers little flexibility

    the thing that really pissed me off in the end though was realising that b4 review was VIBE CODED, kinda explains everything... This tool had so much potential but i struggle to see now how it will deliver when AI is involved in building it

    #kernel #maintainer #b4 #mainline #patchwork #foss

  8. sooo i tried using the new b4 review TUI for my last U-Boot PR and it was a bit of a disaster. I understand the process being a bit clunky to begin with but the whole process of actually setting up a branch was really involved. It failed to update a bunch of series on pathwork, and the b4 ty emails it generated had completely wrong commit SHAs

    I get that the intention is primarily patch review but even for that it feels less like a tool i can utilise to automate the process and more like an imposed workflow that offers little flexibility

    the thing that really pissed me off in the end though was realising that b4 review was VIBE CODED, kinda explains everything... This tool had so much potential but i struggle to see now how it will deliver when AI is involved in building it

    #kernel #maintainer #b4 #mainline #patchwork #foss

  9. sooo i tried using the new b4 review TUI for my last U-Boot PR and it was a bit of a disaster. I understand the process being a bit clunky to begin with but the whole process of actually setting up a branch was really involved. It failed to update a bunch of series on pathwork, and the b4 ty emails it generated had completely wrong commit SHAs

    I get that the intention is primarily patch review but even for that it feels less like a tool i can utilise to automate the process and more like an imposed workflow that offers little flexibility

    the thing that really pissed me off in the end though was realising that b4 review was VIBE CODED, kinda explains everything... This tool had so much potential but i struggle to see now how it will deliver when AI is involved in building it

    #kernel #maintainer #b4 #mainline #patchwork #foss

  10. sooo i tried using the new b4 review TUI for my last U-Boot PR and it was a bit of a disaster. I understand the process being a bit clunky to begin with but the whole process of actually setting up a branch was really involved. It failed to update a bunch of series on pathwork, and the b4 ty emails it generated had completely wrong commit SHAs

    I get that the intention is primarily patch review but even for that it feels less like a tool i can utilise to automate the process and more like an imposed workflow that offers little flexibility

    the thing that really pissed me off in the end though was realising that b4 review was VIBE CODED, kinda explains everything... This tool had so much potential but i struggle to see now how it will deliver when AI is involved in building it

    #kernel #maintainer #b4 #mainline #patchwork #foss

  11. sooo i tried using the new b4 review TUI for my last U-Boot PR and it was a bit of a disaster. I understand the process being a bit clunky to begin with but the whole process of actually setting up a branch was really involved. It failed to update a bunch of series on pathwork, and the b4 ty emails it generated had completely wrong commit SHAs

    I get that the intention is primarily patch review but even for that it feels less like a tool i can utilise to automate the process and more like an imposed workflow that offers little flexibility

    the thing that really pissed me off in the end though was realising that b4 review was VIBE CODED, kinda explains everything... This tool had so much potential but i struggle to see now how it will deliver when AI is involved in building it

    #kernel #maintainer #b4 #mainline #patchwork #foss

  12. I'm a bit desperate T_T

    I'm working on getting #mainline #Linux to work on my Galaxy A71 ( #A715F ) and currently stuck getting the I2C to work where my touchscreen is connected to. The driver's using #qcom #gpi dma to communicate but I'm getting timeouts.

    Does anyone (that reaches this) knows what the issue might be or how to best investigate what the cause is?

    #sm7150

  13. I'm a bit desperate T_T

    I'm working on getting #mainline #Linux to work on my Galaxy A71 ( #A715F ) and currently stuck getting the I2C to work where my touchscreen is connected to. The driver's using #qcom #gpi dma to communicate but I'm getting timeouts.

    Does anyone (that reaches this) knows what the issue might be or how to best investigate what the cause is?

    #sm7150

  14. I'm a bit desperate T_T

    I'm working on getting #mainline #Linux to work on my Galaxy A71 ( #A715F ) and currently stuck getting the I2C to work where my touchscreen is connected to. The driver's using #qcom #gpi dma to communicate but I'm getting timeouts.

    Does anyone (that reaches this) knows what the issue might be or how to best investigate what the cause is?

    #sm7150

  15. I'm a bit desperate T_T

    I'm working on getting #mainline #Linux to work on my Galaxy A71 ( #A715F ) and currently stuck getting the I2C to work where my touchscreen is connected to. The driver's using #qcom #gpi dma to communicate but I'm getting timeouts.

    Does anyone (that reaches this) knows what the issue might be or how to best investigate what the cause is?

    #sm7150

  16. I'm a bit desperate T_T

    I'm working on getting #mainline #Linux to work on my Galaxy A71 ( #A715F ) and currently stuck getting the I2C to work where my touchscreen is connected to. The driver's using #qcom #gpi dma to communicate but I'm getting timeouts.

    Does anyone (that reaches this) knows what the issue might be or how to best investigate what the cause is?

    #sm7150

  17. I am thrilled to be back at FOSDEM. It is a fantastic opportunity to meet with the open source community and connect with fellow developers at such a great conference!

    Please join me this Saturday in the FOSS on Mobile devroom. I will be presenting the technical evolution of the Snapdragon 8 Gen 3, demonstrating how we achieved full mainline support—from power management to the Adreno GPU—running on actual product hardware.

    I look forward to seeing you there.
    Saturday, 18:30 | Room UB4.132

    #FOSDEM #Linux #UBoot #OpenSource #Snapdragon #Mainline

  18. I am thrilled to be back at FOSDEM. It is a fantastic opportunity to meet with the open source community and connect with fellow developers at such a great conference!

    Please join me this Saturday in the FOSS on Mobile devroom. I will be presenting the technical evolution of the Snapdragon 8 Gen 3, demonstrating how we achieved full mainline support—from power management to the Adreno GPU—running on actual product hardware.

    I look forward to seeing you there.
    Saturday, 18:30 | Room UB4.132

    #FOSDEM #Linux #UBoot #OpenSource #Snapdragon #Mainline

  19. I am thrilled to be back at FOSDEM. It is a fantastic opportunity to meet with the open source community and connect with fellow developers at such a great conference!

    Please join me this Saturday in the FOSS on Mobile devroom. I will be presenting the technical evolution of the Snapdragon 8 Gen 3, demonstrating how we achieved full mainline support—from power management to the Adreno GPU—running on actual product hardware.

    I look forward to seeing you there.
    Saturday, 18:30 | Room UB4.132

    #FOSDEM #Linux #UBoot #OpenSource #Snapdragon #Mainline

  20. I am thrilled to be back at FOSDEM. It is a fantastic opportunity to meet with the open source community and connect with fellow developers at such a great conference!

    Please join me this Saturday in the FOSS on Mobile devroom. I will be presenting the technical evolution of the Snapdragon 8 Gen 3, demonstrating how we achieved full mainline support—from power management to the Adreno GPU—running on actual product hardware.

    I look forward to seeing you there.
    Saturday, 18:30 | Room UB4.132

    #FOSDEM #Linux #UBoot #OpenSource #Snapdragon #Mainline

  21. I am thrilled to be back at FOSDEM. It is a fantastic opportunity to meet with the open source community and connect with fellow developers at such a great conference!

    Please join me this Saturday in the FOSS on Mobile devroom. I will be presenting the technical evolution of the Snapdragon 8 Gen 3, demonstrating how we achieved full mainline support—from power management to the Adreno GPU—running on actual product hardware.

    I look forward to seeing you there.
    Saturday, 18:30 | Room UB4.132

    #FOSDEM #Linux #UBoot #OpenSource #Snapdragon #Mainline

  22. Finally managed to get proper serial access to u-boot on my Samsung A5 (a5y17lte) using github.com/dsankouski/u-boot/t

    I did have to break open my last a5y17lte and add lines to the internal serial port to check as it was very hard to get it working blind.

    I've actually not done anything particularly special just reused other people's work but getting my head around it was a challenge. I'll publish an image file for others if they wanted to try it out (I appreciate the a5y17lte hacking club membership currently stands at 1).

    #postmarketos
    #mainline
    #linux
    #uboot

  23. Finally managed to get proper serial access to u-boot on my Samsung A5 (a5y17lte) using github.com/dsankouski/u-boot/t

    I did have to break open my last a5y17lte and add lines to the internal serial port to check as it was very hard to get it working blind.

    I've actually not done anything particularly special just reused other people's work but getting my head around it was a challenge. I'll publish an image file for others if they wanted to try it out (I appreciate the a5y17lte hacking club membership currently stands at 1).

    #postmarketos
    #mainline
    #linux
    #uboot

  24. Finally managed to get proper serial access to u-boot on my Samsung A5 (a5y17lte) using github.com/dsankouski/u-boot/t

    I did have to break open my last a5y17lte and add lines to the internal serial port to check as it was very hard to get it working blind.

    I've actually not done anything particularly special just reused other people's work but getting my head around it was a challenge. I'll publish an image file for others if they wanted to try it out (I appreciate the a5y17lte hacking club membership currently stands at 1).

    #postmarketos
    #mainline
    #linux
    #uboot

  25. Finally managed to get proper serial access to u-boot on my Samsung A5 (a5y17lte) using github.com/dsankouski/u-boot/t

    I did have to break open my last a5y17lte and add lines to the internal serial port to check as it was very hard to get it working blind.

    I've actually not done anything particularly special just reused other people's work but getting my head around it was a challenge. I'll publish an image file for others if they wanted to try it out (I appreciate the a5y17lte hacking club membership currently stands at 1).

    #postmarketos
    #mainline
    #linux
    #uboot

  26. Finally managed to get proper serial access to u-boot on my Samsung A5 (a5y17lte) using github.com/dsankouski/u-boot/t

    I did have to break open my last a5y17lte and add lines to the internal serial port to check as it was very hard to get it working blind.

    I've actually not done anything particularly special just reused other people's work but getting my head around it was a challenge. I'll publish an image file for others if they wanted to try it out (I appreciate the a5y17lte hacking club membership currently stands at 1).




  27. Day 2 of #dailydriving sdm845-next

    Key changes:
    -
    🔄 Kernel rebased to next-20251217
    -
    🎉 Haptic now works (mailing list patches replaced with patches from sdm845-mainline tree)

    #linuxonmobile #mainline #testing

  28. Day 2 of #dailydriving sdm845-next

    Key changes:
    -
    🔄 Kernel rebased to next-20251217
    -
    🎉 Haptic now works (mailing list patches replaced with patches from sdm845-mainline tree)

    #linuxonmobile #mainline #testing

  29. Day 2 of #dailydriving sdm845-next

    Key changes:
    -
    🔄 Kernel rebased to next-20251217
    -
    🎉 Haptic now works (mailing list patches replaced with patches from sdm845-mainline tree)

    #linuxonmobile #mainline #testing

  30. Day 2 of #dailydriving sdm845-next

    Key changes:
    -
    🔄 Kernel rebased to next-20251217
    -
    🎉 Haptic now works (mailing list patches replaced with patches from sdm845-mainline tree)

    #linuxonmobile #mainline #testing

  31. Day 2 of #dailydriving sdm845-next

    Key changes:
    -
    🔄 Kernel rebased to next-20251217
    -
    🎉 Haptic now works (mailing list patches replaced with patches from sdm845-mainline tree)

    #linuxonmobile #mainline #testing

  32. Google Play System Update (October 2025) rolls out for Samsung devices

    Google 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 October 28th, a new Google Play System Update has been pushed to Samsung devices. This update upgrades your Project Mainline modules to the October 1st, 2025 version. This update weighs around 49 MB.

    To be able to get this version, follow these steps:

    1. Go to your device’s settings
    2. Open the security settings
    3. Find “Google Play System Update” and tap on it
    4. If everything goes OK, you should see the below update dialog:

    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 October 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 November patch of 2025!

    Google play icons created by Pixel perfect – Flaticon

    #Android #Android12 #Android12L #Android13 #Android14 #Android15 #Android16 #Android17 #AndroidB #AndroidC #AndroidT #AndroidU #AndroidUpdate #AndroidV #December #google #googlePlay #GooglePlaySystemUpdate #mainline #news #operatingSystem #ProjectMainline #smartphone #system #systemUpdate #Technology #update