cross-posted from: https://lemmy.ml/post/9939705
Pixel 4a (5G) and Pixel 5 are end-of-life and shouldn't be used anymore due to lack of security patches for firmware and drivers. We provide extended support for harm reduction.
Tags:
- 2023123000-redfin (Pixel 4a (5G), Pixel 5)
- 2023123000 (Pixel 5a, Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold, emulator, generic, other targets
Changes since the 2023121200 release:
- Keyboard: add new implementation of multi-locale spell checking support to fix crashes and other issues
- Sandboxed Google Play compatibility layer: add Android Auto support with the compatibility layer eliminating the need for most of the permissions and a permission menu with 4 toggles for granting the minimal special access required for wired Android Auto, wireless Android Auto, audio routing and phone calls
- Settings: remove confusing mention of Android Auto from Connected devices screen
- exempt non-app system processes from Sensors permission enforcement (fixes some issues including gpsd crashes)
- fix Bluetooth auto-turn-off race condition to avoid crashes
- work around upstream race condition bug in biometric service
- disable support for pre-approving PackageInstaller sessions due to incompatibility with Network permission toggle
- fix several upstream bugs in handling crash reports mainly to improve our user-facing crash reporting system
- use GrapheneOS Widevine provisioning proxy by default
- add settings for changing Widevine provisioning server
- add configuration for setupdesign and setupcompat libraries to improve system UI theme
- kernel (Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold, Generic 5.10): update to latest GKI LTS branch revision including update to 5.10.204
- kernel (Pixel 8, Pixel 8 Pro, Generic 5.15): update to latest GKI LTS branch revision including update to 5.15.142
- kernel (Generic 6.1): initial port of GrapheneOS changes for use with emulator builds
- force disable network ADB in early boot to improve verified boot security (no user-facing change since it's currently disabled by default later in the boot process, but not robustly)
- Vanadium: update to version 120.0.6099.115.0
- Vanadium: update to version 120.0.6099.144.0
- AppCompatConfig: update to version 2
- GmsCompatConfig: update to version 88
- GmsCompatConfig: update to version 89
- GmsCompatConfig: update to version 90
- Auditor: update to version 78
Yet no automatic call recording.
There is an open issue on GitHub regarding adding automatic call recording, but it is a low priority enhancement. GrapheneOS' default dialer already supports call recording.
If you would like to keep track of this issue, you can do so by checking out on the official GrapheneOS Issue tracker: https://github.com/GrapheneOS/os-issue-tracker/issues/2083
Yepp, I saw that issue last month or something like that :) Thank you for the link anyway.
I use the call recorder whenever I feel like it's important (for an example, when calling a company). But sometimes the phone (Pixel 6a) does not register my push on the record button. So most of the times, I have to press it 2-4 times before the phone goes like "aha, you actually pressed the button" -.- Super annoying! Automatic call record will prevent this issue :)
Would you please be able to post this on the issue tracker, if not already there?
I don't want to create a new account only for that. I want to preserve my privacy :) If they had their source code on Codeberg, I would already posted that issue.
May you please specify the GrapheneOS build number that is found in the Device Settings > About > Build Number, along with the device model you are using?
You can copy paste the build number by pressing and holding it.
Would you be able to provide logs captured during call when this issue happens?
UQ1A.240105.002.2024010400, Pixel 6a
Sorry, but I don't know how to get the logs and where to find the logs.
Open Settings > Press About Phone > press Build Number until a toast notification says "You are now a developer". You may be prompted to type in your lock screen password before the toast message is shown.
Once you have done the above. Go back to the main screen of the settings menu > Press System > Developer Options > Bug Report. Follow the on screen instructions to choose the best style of bug report to create. Once you have made your selection, precede to call and press call record again to capture any possible logs.
Please remember, once you have captured your log to head back to developer options and disable them by pressing the toggle located on the far top right of the screen.
Sorry for the delayed reply, but this issue got fixed maybe 2 months ago :)
Awesome👍