D

doffactory

These devices aren't properly standards compliant and have security vulnerabilities. That's why they keep having issues with Android security updates. Android is trying to fix Bluetooth security issues but unfortunately that can cause issues with devices which were depending on security holes to function. They're trying to preserve support for these problematic devices but sometimes there's no way to do it and they get dropped or partially broken. It's not something specific to GrapheneOS. It's unfortunate that these devices aren't higher quality and that they tend to lack firmware updates to provide them with security patches and bug fixes. They're quite critical to people and yet not handled at all seriously by the companies making them.

doffactory I also wanted to warn those users who depend on these important services/devices to be careful with the upcoming updates

AOSP 15 based on QPR2 stable isn't scheduled to be released until several months into the future. GrapheneOS isn't known for shipping production releases based on beta versions of AOSP (not even sure if those exist?). I don't think it's ever actually happened. While making people aware of potential bugs in an upcoming release of an AOSP stable version might be beneficial in some cases, it does not seem clear in this case that a warning is justified.

doffactory QPR2v1 discussion of GrapheneOS on Android 14: https://discuss.grapheneos.org/d/11383-request-for-testing-and-feedback-with-bluetooth-on-android-14-qpr2-grapheneos

While the release that is being talked about in that thread also includes the term "QPR2", I am not seeing how a shared term in an old release would automatically mean that a future release would carry similar, already fixed, bugs.

doffactory And original article: https://www.androidpolice.com/android-15-qpr2-beta-2/

That article is saying that Bluetooth bugs, including what sounds like the bug your are reporting, will be fixed in an upcoming beta version.

This doesn't seem to be affecting GrapheneOS at all, so reporting it in the chat room intended for GrapheneOS alpha and beta testing doesn't seem necessary.

Please note that I do not speak for the GrapheneOS project.

doffactory
Since this is regarding the Beta, it would be more appropriate to address this on the Matrix Testing channel, or perhaps Discord, than here.

doffactory This was caused by the update to Android 14 QPR2, not a GrapheneOS-specific change. Please provide the feedback requested in https://discuss.grapheneos.org/d/11383-request-for-testing-and-feedback-with-bluetooth-on-android-14-qpr2-grapheneos.

Looks like GrapheneOS isn't impacted. Thanks devs!

https://grapheneos.social/@GrapheneOS/111309676504712576

I simply disable automatic reboot after an update and instead manually reboot when convenient, usually first thing in the morning. But I leave data enabled so it can download/install during the night.

doffactory Thanks.

doffactory I had this happen a while back after an update . had to delete the scheduled and make a new one to fix it .

i have 5 profiles and everyday i have to switch on then many times, every time i have to swipe down the screen, press the icon from the current user then choose the profile i want on that moment to login.
i think graphene developers could add the SWITCH PROFILE OPTION on power button. so if power button pressed (two times or three times) it would show up a menu with all the profiles to choose.

Osmand from fdroid works great in germany/austia/czech republic.
Recently I tried Organic Maps because it looks way better and searching adresses is a lot smoother.

https://github.com/Sangwan5688/BlackHole

Feature packed music app, support multiple platforms and playlist import from spotify, yt music etc..

doffactory This morning I woke up to the error message

What error message?

doffactory I removed the device and re-added it

If the Attestation website says Pinned OS: GrapheneOS (unmodified official release) then you're okay.

Looks like you have a Pixel 7. You can also verify the boot key hash is the same as what's listed on the website here: https://grapheneos.org/install/web#verified-boot-key-hash. You can verify it's correct on your phone right as it's booting up or on the attestation website.

On the attestation website, it should say: Pinned verified boot key hash: [The key listed on the GrapheneOS website, except in uppercase. For this hash, upper/lower case doesn't matter.]

GrapheneOS version 2022122700 released: https://grapheneos.org/releases#2022122700.

See the linked release notes for a summary of the improvements over the previous release.

doffactory That looks perfect thanks!

I agree that its an annoying limitation.

hi,
will it be possible to set the number row to be shown all the time? I don't wanna install a different keyboard, the grapheneOS one is nice but the lack of the persistent number row is an issue, for me at least (: