[Motorola Moto G32] rootfuchs:
Hello everybody!

First things first: Thank you @Dhina17 for all the work you've already put into it! It's always a great thing if people work on stuff during their spare time and share it with others. I really appreciate that! :)

Seeing the device being officially supported by LineageOS I've bought a Motorola G32 (XT2235-2). Before installing LOS the system was updated to the latest stock (Android 13, RETEU, Nov. 2023 I think).

I also ran into a problem after installing LOS which I think is an issue with the UI and closely related to the problem described by @Leonidas23. After the first installation of LOS the symptoms were exactly the same but after the second install (and all following installs) the symptoms got different. To localize the problem I've kept the system as basic as possible: No SD card, no SIM, no WiFI, no Gapps, no screenlock method, no customizations. Just a basic install closely following the instructions on the LineageOS Wiki, keeping the default settings and skipping everything I could skip during the LineageOS setup assistant after the first boot. The only thing I've changed is setting the display inactivity timeout to 10 minutes to further analyze the problem and to see what's going on.

The problem is as follows:

The system boots up normally (static Moto splashscreen, bootloader warning, static Moto splashscreen again, LineageOS bootsplash)

The UI comes available*

Leaving the device untouched, after exactly 105 seconds** the LineageOS bootsplash appears again. No full reboot I suppose as there's no Moto splashscreen and no bootloader warning.

The UI comes up partially*** and that's the end of the procedure

* Things that don't work: Keyboard doesn't pop up, no volume control when pushing any of the volume buttons, no power off/reboot menu when pushing the power button.

** Watchdog related maybe?

*** The UI only shows a bar at the bottom (for pulling up the menu which doesn't work) and the clock and battery info at the top. Black background. No reaction when tapping on anything. The only thing that pops up is the Power off/Reboot menu after a delay of a couple of seconds when pressing the power button.

Builds I've tried (with the specific boot/vendor_boot/dtbo images that come with it):

lineage-20.0-20240113-nightly-devon-signed (currently installed)

lineage-20.0-20231223-nightly-devon-signed

lineage-20.0-20240104-microG-devon

Somehow I wasn't able to enable ADB via the somewhat usable UI when reaching step #2 ("adb: no devices/emulators found") but I've managed to enable it at boot by modifying the build.props via non-persistent TWRP so if you need a (horribly large) logcat including the timestamps after reaching each of the problems stages I'd be happy to provide it to you.

Other things I've tried without making any difference after making ADB accessible:

- Installing another launcher and setting it as default ("Posidon Launcher", F-Droid)

- Installing another keyboard and setting it as default ("Simple Keyboard", F-Droid)

- Installing via TWRP with the LineageOS zip copied to the local storage

In case you want to take a look into it and need further debug information I'd also happily provide them to you asap. If you prefer an official bug report I can try creating one. I never did that for LOS but I'll try my best to meet the basic requirements.

Unfortunately I'm completely out of ideas. Does anyone in this thread have an idea on how to fix this or any clue where the problem might be located? The phone isn't usable at all in that state so hopefully this can be fixed somehow. I really don't wanna go back to stock because, well... stock sucks :)

@Leonidas23: Thank you for posting your issue. There's nothing I could find on the web that was even remotely related to the problem I'm dealing with and I just didn't want to believe I'm the only one having this kind of trouble. Your post gave me hope that my phones hardware isn't broken.