soft restart?

hnn8

I opned Mull (firefox fork) and after trying to connect to my social media account, there was the full screen grapheneOS logo, like it is displayed when the phone is restarted. But the Verified boot key hash wasnt shown as the (very fast) "reboot" happned. I was back at my Owner profile and had to put in my password, what I did, but then I decided to do a full reboot.
What did happned? Im on the Beta channel.

other8026

hnn8 it does sound like a soft reboot, but there's no way for us to know what caused it without logs or more information. Probably nothing to worry about if it happens just once.

router99

hnn8 I have had this happen intermittently for a few months or so, too. I think it was always with Mull.

hnn8

After a soft restart, credential encrypted storage remains unlocked.

https://source.android.com/docs/core/runtime/soft-restart

I had to put my password in, fingerprint wouldnt work. But I didnt had to enter my SIM-PIN.

hnn8

ah, okay, unlocked it and a notification says "system_server has crashed"

hnn8

Here is the log I got from the notification:
type: crash

osVersion: google/panther/panther:14/AP2A.240905.003/2024100800:user/release-keys
uid: 1000 (u:r:system_server:s0)
cmdline: system_server
processUptime: 258737s

abortMessage: Splitting motion events requires a down time to be set for the target on connection 16c8aea StatusBar (server) for MotionEvent

signal: 6 (SIGABRT), code -1 (SI_QUEUE)
threadName: InputDispatcher

backtrace:
    /apex/com.android.runtime/lib64/bionic/libc.so (abort+164, pc 64a24)
    /apex/com.android.art/lib64/libart.so (art::Runtime::Abort(char const*)+596, pc 905b24)
    /apex/com.android.art/lib64/libbase.so (android::base::SetAborter(std::__1::function<void (char const*)>&&)::$_0::__invoke(char const*)+80, pc 17ca0)
    /system/lib64/libbase.so (android::base::LogMessage::~LogMessage()+352, pc 171a0)
    /system/lib64/libinputflinger.so (android::inputdispatcher::InputDispatcher::prepareDispatchCycleLocked(long, std::__1::shared_ptr<android::inputdispatcher::Connection> const&, std::__1::shared_ptr<android::inputdispatcher::EventEntry const>, android::inputdispatcher::InputTarget const&)+2160, pc 1284e0)
    /system/lib64/libinputflinger.so (android::inputdispatcher::InputDispatcher::dispatchEventLocked(long, std::__1::shared_ptr<android::inputdispatcher::EventEntry const>, std::__1::vector<android::inputdispatcher::InputTarget, std::__1::allocator<android::inputdispatcher::InputTarget> > const&)+232, pc 122958)
    /system/lib64/libinputflinger.so (android::inputdispatcher::InputDispatcher::dispatchMotionLocked(long, std::__1::shared_ptr<android::inputdispatcher::MotionEntry const>, android::inputdispatcher::InputDispatcher::DropReason*, long&)+896, pc 11f920)
    /system/lib64/libinputflinger.so (android::inputdispatcher::InputDispatcher::dispatchOnceInnerLocked(long&)+1108, pc 11c3e4)
    /system/lib64/libinputflinger.so (android::inputdispatcher::InputDispatcher::dispatchOnce()+84, pc 11bee4)
    /system/lib64/libinputflinger_base.so (android::(anonymous namespace)::InputThreadImpl::threadLoop()+24, pc b338)
    /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+244, pc 115d4)
    /system/lib64/libandroid_runtime.so (android::AndroidRuntime::javaThreadShell(void*)+140, pc ed45c)
    /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204, pc 767ac)
    /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64, pc 67d50)

other8026

hnn8 Does it keep happening, or has it happened only the one time?

I found multiple issues in the OS issue tracker. Developers have said that it's an upstream issue. If it keeps happening, it may be worth looking into further.

Here are a few of the issues so you can take a look:

hnn8

Didnt happned to me anymore but Im not a heavy user of Mull but used it for some hours per day since then.