2
GrapheneOS version 2025100300 released: (grapheneos.social)
submitted 1 year ago by to c/privacy@fedia.io
9 comments fedilink hide all child comments
 

GrapheneOS version 2025100300 released:grapheneos.org/releases#202510See the linked release notes for a summary of the improvements over the previous release.Forum discussion thread:discuss.grapheneos.org/d/27029#GrapheneOS #privacy #security

you are viewing a single comment's thread
view the rest of the comments
[โ€“] 1 point 1 year ago (4 children)

@GrapheneOS yep, it's working again after a reboot. Thanks for the tip

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [โ€“] [S] 1 point 1 year ago (3 children)

    @topcaser Possibly a glitch with the hardware-level sensor hub which implements this. Not really clear. It might have just gotten into a weird state. A reboot generally fixes those rare issues. Some hardware isn't fully reset on reboot and turning off completely + turning on again can work around those glitches. These issues are rare but they do happen and we have a lot of users so we regularly encounter people running into rare issues like this where we haven't heard of it ever before.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [โ€“] 1 point 1 year ago (2 children)

    @GrapheneOS Could you describe once how your regression suite looks like? You are releasing so much versions that I am wondering how you can do this. Most of the time there is working everything and of there are problems in there, they are related with upstream bugs. To be honest, from this observation I set the update channel to beta, knowing that you will deliver. Bit this is only gut feeling. To keep up that low bug rate you need probably a highly automated test suite?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [โ€“] [S] 1 point 1 year ago (1 child)

    @topcaser Android has a set of huge automated test suites. Bear in mind most of the code comes from the Android Open Source Project and we try to keep our changes as uninvasive as possible. We heavily rely on user testing regardless because the automated tests do not catch most of the kinds of issues we end up encountering. The main CTS is very large so in practice we only run a small subset of it and then add additional parts to test the changes we've made when that's relevant.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [โ€“] [S] 1 point 1 year ago

    @topcaser Nearly all regressions are upstream regressions since that's most of the code and we're very careful with our changes. Most of the regressions specific to GrapheneOS have to do with porting to new Android releases, so it's the upstream code changes causing issues either due to needing changes to our device support code or the features we add / changes we make. We have a lot of our own code but it's not changing much beyond porting to new releases. We slowly add new stuff.

  • permalink
  • fedilink
  • source
  • parent