GrapheneOS version 2023120701 released:
https://grapheneos.org/releases#2023120701
See the linked release notes for a summary of the improvements over the previous release.
GrapheneOS version 2023120701 released:
https://grapheneos.org/releases#2023120701
See the linked release notes for a summary of the improvements over the previous release.
Repair mode is going to come to graphene os or its not a part of aosp code?
Nice. This update fixed the fingerprint reader on my Pixel 6a. It was completely disabled on the Dec 4th release for some reason.
GrapheneOS
This new version brings the following error message on my Pixel 8 Pro:
type: crash
osVersion: google/husky/husky:14/UQ1A.231205.015/2023120701:user/release-keys
uid: 1000 (u:r:surfaceflinger:s0)
cmdline: /system/bin/surfaceflinger
processUptime: 28s
signal: 11 (SIGSEGV), code 9 (SEGV_MTESERR), faultAddr d00d9fe4b427749
threadName: surfaceflinger
MTE: enabled
backtrace:
/system/bin/surfaceflinger (android::SurfaceFlinger::commit(android::PhysicalDisplayId, android::ftl::SmallMap<android::PhysicalDisplayId, android::scheduler::FrameTarget const*, 3ul, std::__1::equal_to<android::PhysicalDisplayId> > const&)+800, pc 20ef60)
/system/bin/surfaceflinger (android::scheduler::Scheduler::onFrameSignal(android::ICompositor&, android::VsyncId, android::TimePoint)+364, pc 1ee39c)
/system/lib64/libutils.so (android::Looper::pollInner(int)+376, pc 18b08)
/system/lib64/libutils.so (android::Looper::pollOnce(int, int*, int*, void**)+124, pc 1892c)
/system/bin/surfaceflinger (android::impl::MessageQueue::waitMessage()+92, pc 1deefc)
/system/bin/surfaceflinger (android::scheduler::Scheduler::run()+28, pc 1ee21c)
/system/bin/surfaceflinger (main+1792, pc 25b920)
/apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+104, pc 5ad08)
GrapheneOS
… and the same crash also on my Pixel 7 Pro:
type: crash
osVersion: google/cheetah/cheetah:14/UQ1A.231205.015/2023120701:user/release-keys
uid: 1000 (u:r:surfaceflinger:s0)
cmdline: /system/bin/surfaceflinger
processUptime: 10s
abortMessage: hardened_malloc: fatal allocator error: detected write after free
signal: 6 (SIGABRT), code -1 (SI_QUEUE)
threadName: binder:598_2
backtrace:
/apex/com.android.runtime/lib64/bionic/libc.so (abort+164, pc 62e64)
/apex/com.android.runtime/lib64/bionic/libc.so (fatal_error+24, pc 4d3a0)
/apex/com.android.runtime/lib64/bionic/libc.so (allocate+1912, pc 4a3d8)
/apex/com.android.runtime/lib64/bionic/libc.so (malloc+36, pc 45d54)
/system/lib64/libc++.so (operator new(unsigned long)+24, pc 51028)
/system/bin/surfaceflinger (android::surfaceflinger::frontend::TransactionHandler::queueTransaction(android::TransactionState&&)+56, pc 1a0018)
/system/bin/surfaceflinger (android::SurfaceFlinger::setTransactionState(android::gui::FrameTimelineInfo const&, android::Vector<android::ComposerState>&, android::Vector<android::DisplayState> const&, unsigned int, android::sp<android::IBinder> const&, android::InputWindowCommands, long, bool, std::__1::vector<android::client_cache_t, std::__1::allocator<android::client_cache_t> > const&, bool, std::__1::vector<android::ListenerCallbacks, std::__1::allocator<android::ListenerCallbacks> > const&, unsigned long, std::__1::vector<unsigned long, std::__1::allocator<unsigned long> > const&)+3604, pc 21e1b4)
/system/lib64/libgui.so (android::BnSurfaceComposer::onTransact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+2836, pc cfbc4)
/system/bin/surfaceflinger (android::SurfaceFlinger::onTransact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+408, pc 225518)
/system/lib64/libbinder.so (android::BBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+304, pc 74b00)
/system/lib64/libbinder.so (android::IPCThreadState::executeCommand(int)+1016, pc 5ed78)
/system/lib64/libbinder.so (android::IPCThreadState::getAndExecuteCommand()+160, pc 5e8c0)
/system/lib64/libbinder.so (android::IPCThreadState::joinThreadPool(bool)+112, pc 5f210)
/system/lib64/libbinder.so (android::PoolThread::threadLoop()+24, pc 69078)
/system/lib64/libutils.so (android::Thread::_threadLoop(void*)+284, pc 1430c)
/apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204, pc cf9ec)
/apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64, pc 64730)
… after activating in Settings menu “Notify about system process crashes” like on my P8P and booting it again.
BTW: What does “surfaceflinger” mean?
I did also the test on my P7P,
arfter reboot I got instantly this:
osVersion: google/cheetah/cheetah:14/UQ1A.231205.015/2023120701:user/release-keys
uid: 1000 (u:r:surfaceflinger:s0)
cmdline: /system/bin/surfaceflinger
processUptime: 13s
abortMessage: hardened_malloc: fatal allocator error: detected write after free
signal: 6 (SIGABRT), code -1 (SI_QUEUE)
threadName: binder:588_2
backtrace:
/apex/com.android.runtime/lib64/bionic/libc.so (abort+164, pc 62e64)
/apex/com.android.runtime/lib64/bionic/libc.so (fatal_error+24, pc 4d3a0)
/apex/com.android.runtime/lib64/bionic/libc.so (allocate+1912, pc 4a3d8)
/apex/com.android.runtime/lib64/bionic/libc.so (malloc+36, pc 45d54)
/system/lib64/libc++.so (operator new(unsigned long)+24, pc 51028)
/system/bin/surfaceflinger (android::surfaceflinger::frontend::TransactionHandler::queueTransaction(android::TransactionState&&)+56, pc 1a0018)
/system/bin/surfaceflinger (android::SurfaceFlinger::setTransactionState(android::gui::FrameTimelineInfo const&, android::Vector<android::ComposerState>&, android::Vector<android::DisplayState> const&, unsigned int, android::sp<android::IBinder> const&, android::InputWindowCommands, long, bool, std::__1::vector<android::client_cache_t, std::__1::allocator<android::client_cache_t> > const&, bool, std::__1::vector<android::ListenerCallbacks, std::__1::allocator<android::ListenerCallbacks> > const&, unsigned long, std::__1::vector<unsigned long, std::__1::allocator<unsigned long> > const&)+3604, pc 21e1b4)
/system/lib64/libgui.so (android::BnSurfaceComposer::onTransact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+2836, pc cfbc4)
/system/bin/surfaceflinger (android::SurfaceFlinger::onTransact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+408, pc 225518)
/system/lib64/libbinder.so (android::BBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+304, pc 74b00)
/system/lib64/libbinder.so (android::IPCThreadState::executeCommand(int)+1016, pc 5ed78)
/system/lib64/libbinder.so (android::IPCThreadState::getAndExecuteCommand()+160, pc 5e8c0)
/system/lib64/libbinder.so (android::IPCThreadState::joinThreadPool(bool)+112, pc 5f210)
/system/lib64/libbinder.so (android::PoolThread::threadLoop()+24, pc 69078)
/system/lib64/libutils.so (android::Thread::_threadLoop(void*)+284, pc 1430c)
/apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204, pc cf9ec)
/apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64, pc 64730)
`````
The permission manager still crashes regularly.
type: ANR
osVersion: google/panther/panther:14/UQ1A.231205.015/2023120701:user/release-keys
package: com.android.permissioncontroller:330000000
process: com.android.permissioncontroller
activity: com.android.permissioncontroller/.permission.ui.ManagePermissionsActivity
cause: ANR Input dispatching timed out (2118782 com.android.permissioncontroller/com.android.permissioncontroller.permission.ui.ManagePermissionsActivity (server) is not responding. Waited 5003ms for FocusEvent(hasFocus=true)).
info: ANR in com.android.permissioncontroller (com.android.permissioncontroller/.permission.ui.ManagePermissionsActivity)
PID: 30439
Reason: Input dispatching timed out (2118782 com.android.permissioncontroller/com.android.permissioncontroller.permission.ui.ManagePermissionsActivity (server) is not responding. Waited 5003ms for FocusEvent(hasFocus=true)).
Parent: com.android.permissioncontroller/.permission.ui.ManagePermissionsActivity
ErrorId: 6bed3096-3ed3-4d24-b9ea-d4d948651fea
Frozen: false
Load: 3.73 / 3.3 / 3.0
----- Output from /proc/pressure/memory -----
some avg10=0.00 avg60=0.00 avg300=0.00 total=92372152
full avg10=0.00 avg60=0.00 avg300=0.00 total=58763659
----- End output from /proc/pressure/memory -----
----- Output from /proc/pressure/cpu -----
some avg10=13.77 avg60=12.58 avg300=12.64 total=2054382408
----- End output from /proc/pressure/cpu -----
----- Output from /proc/pressure/io -----
some avg10=0.00 avg60=0.00 avg300=0.00 total=102942947
full avg10=0.00 avg60=0.00 avg300=0.00 total=70344217
----- End output from /proc/pressure/io -----
CPU usage from 131822ms to 0ms ago (2023-12-08 21:34:20.765 to 2023-12-08 21:36:32.587):
35% 25208/com.github.libretube: 23% user + 11% kernel / faults: 32559 minor 2642 major
32% 725/surfaceflinger: 23% user + 9.1% kernel / faults: 6994 minor 175 major
25% 1553/system_server: 15% user + 10% kernel / faults: 81183 minor 5300 major
21% 29152/org.thoughtcrime.securesms: 17% user + 4.7% kernel / faults: 56849 minor 623 major
15% 1097/samsung.hardware.media.c2@1.0-service: 8.7% user + 6.6% kernel / faults: 2350 minor
11% 3118/com.android.systemui: 9.2% user + 2.5% kernel / faults: 43529 minor 716 major
8.5% 1268/media.swcodec: 7% user + 1.4% kernel / faults: 4626 minor 313 major
7.8% 732/android.hardware.composer.hwc3-service.pixel: 4.8% user + 3% kernel / faults: 105 minor 61 major
5.1% 1108/audioserver: 5.1% user + 0% kernel / faults: 1089 minor 91 major
4.3% 11531/com.google.android.inputmethod.latin: 3.5% user + 0.8% kernel / faults: 18443 minor 692 major
28% TOTAL: 16% user + 9.6% kernel + 0% iowait + 1.5% irq + 0.5% softirq
CPU usage from 32ms to 419ms later (2023-12-08 21:36:32.619 to 2023-12-08 21:36:33.005):
165% 1553/system_server: 76% user + 89% kernel / faults: 9774 minor 174 major
76% 1767/Signal Catcher: 44% user + 31% kernel
31% 30751/AnrAuxiliaryTas: 9.5% user + 22% kernel
12% 10905/binder:1553_19: 6.3% user + 6.3% kernel
9.5% 1790/binder:1553_2: 3.1% user + 6.3% kernel
9.5% 10990/binder:1553_20: 6.3% user + 3.1% kernel
3.1% 1768/perfetto_hprof_: 0% user + 3.1% kernel
3.1% 3058/AudioService: 3.1% user + 0% kernel
3.1% 14099/AudioTrack: 0% user + 3.1% kernel
63% 30439/com.android.permissioncontroller: 27% user + 36% kernel / faults: 35 minor
27% 30515/RenderThread: 18% user + 9% kernel
22% 30439/ssioncontroller: 0% user + 22% kernel
4.5% 30521/mali-event-hand: 0% user + 4.5% kernel
4.5% 30746/binder:30439_5: 4.5% user + 0% kernel
28% 725/surfaceflinger: 19% user + 8.5% kernel
17% 725/surfaceflinger: 11% user + 5.6% kernel
2.8% 767/binder:725_2: 2.8% user + 0% kernel
8.5% 732/android.hardware.composer.hwc3-service.pixel: 8.5% user + 0% kernel
8.5% 4867/binder:732_8: 8.5% user + 0% kernel
2.6% 49/rcuog/4: 0% user + 2.6% kernel
2.6% 50/rcuop/4: 0% user + 2.6% kernel
2.6% 71/rcuop/7: 0% user + 2.6% kernel
2.7% 334/decon0_kthread: 0% user + 2.7% kernel
2.8% 803/csf_sync_update: 0% user + 2.8% kernel
2.9% 962/loop34: 0% user + 2.9% kernel
3% 1097/samsung.hardware.media.c2@1.0-service: 3% user + 0% kernel
6% 29359/HwBinder:1097_3: 3% user + 3% kernel
3.8% 25208/com.github.libretube: 3.8% user + 0% kernel / faults: 24 minor
3.8% 25208/ithub.libretube: 3.8% user + 0% kernel
3.8% 26985/HwBinder:25208_: 3.8% user + 0% kernel
4.4% 30038/kworker/5:1-memlat_wq: 0% user + 4.4% kernel
38% TOTAL: 19% user + 17% kernel + 0.3% iowait + 1.3% irq + 0.6% softirq
See https://discuss.grapheneos.org/d/8238-permission-manager-app-crash
I'm getting a lock screen bug after switching profiles .
Pin input and finger print option are open at same time finger print will go away but pin numbers stay open.
There's an issue that may be related to your crashes: https://github.com/GrapheneOS/os-issue-tracker/issues/2792
It's marked upstream.
other8026 There's an issue that may be related to your crashes: https://github.com/GrapheneOS/os-issue-tracker/issues/2792
It's marked upstream.
I find that this project is repeatedly pointing a finger at and complaining about AOSP or Google software defects, despite GrapheneOS being purposefully based on AOSP.
Does it matter? It's not as if users can run GrapheneOS on iOS. AOSP is the integral core of GrapheneOS. When it's defective, it still ruins usability or kills the phone completely or creates a security and privacy problem.
How many times a week do they push updates? I flashed the 1207 build yesterday through the Web interface and just now I got another update. And every time they push an update (which is multiple times a month), it drains a big chunk of my battery and makes the device hot.
SoulKeeper My device was lagging significantly the last update after updating, so I fully understand what you mean, however its good that the team keeps updating GrapheneOS so that things are stable and secure. I'd rather have more updates and be fully up to date security wise than waiting months for an update.
ve3jlg yeah, I hear you, but since AOSP is the base for many different OSes running Android, does it make sense for all of them to constantly fix upstream issues in their downstream project? I don't know how this specific crash affects those who have it happen on their phones. I'm guessing it's just a crash once then everything continues working as usual kind of thing.
I've seen many upstream issues fixed in GrapheneOS, especially those that are very bad. Like the most recent update from December 8th is to fix an upstream issue.
After the last update and a reboot I've the impression, that the battery drain in idle-state has improved on my Pixel 6a.