Is the debugging bug report on the power menu constantly running and logging errors to files until it reboots? If so, is there something that would indicate that this is running?
No, it’s collected as long as the progress bar runs and then stops.
ok-that is probably why it won’t capture spontaneous reboots!
I’m installing Android Studio as a flatpak to keep it sandboxed. So we’re using a Google app to debug a non-Google phone? 
First of all, Android is Google, there is no non-Google Android phone, there is only non-Google-Services phone.
Android Studio is the most reasonable way to work on Android phones in the context of the Android Framework.
Use adb on the terminal. Check that the cable doesn’t lose the connection or else let the phone stationary somewhere.
After connecting the phone allow the debugging on Brax3 so that,
adb devices
shows Brax3#ID device and not unauthorized
If you want to save to a file
adb logcat > logfile
both terminal output and file saving
adb logcat | tee logfile
documentation for adb commands here, adb logcat - ADB Shell
a tool I found randomly and logs everything, you can run manually the commands mentioned in the README.md description instead of using the tool, GitHub - abhinavsaurabh/ADBLogCaptureTool: A modern, user-friendly Python-based GUI application for capturing logs from Android devices using ADB (Android Debug Bridge). This tool simplifies the process of collecting critical logs for debugging and diagnostics, making it suitable for developers, testers, and engineers.A GUI-based Python tool for capturing Android logs (dmesg, xlog, logcat).
We’ve also created this article (work in progress) on android debugging: Android Debugging Crash Course - Open Source Community Guide
The HAL debugging should be useful for the issues with the modem, some users can’t get the APNs loaded and others have issues with the phone audio and WiFi calling which are resolved randomly by playing with the settings or by using another phone app.
I was thinking de-Googled phone but typed non-Google phone. That Google flatpak is taking up too much space on my old computer and couldn’t unzip the configuration files because it kept running out of space. I just added 32 GB to my computer so it should work now.
While doing that I was listening to an offline podcast on AntennaPod and my phone crashed 4 times. That seems a good way to reproduce this!
Do you mean that your app crashes and you need to start it again, or your phone crashes and reboots?
the phone restarted 4 times when just listening to an audio podcast.
Got you. I just had the app crash 2 times on me in 4 minutes, but phone didn’t reboot. Will try to reproduce.
I was able to use adb logcat to make a file of the errors in my phone. I saw the file incrementing in size as time went by so maybe it was logging live errors. I got the system to reboot by playing the offline podcast on AntennaPod again. The file is a 5.8 MB text file and too large to post here. What should I do with this?
I will DM you.
1 Like
I show you the tee command that you can have both screen output and save to file.
You may have to run many more tests, plamen will inform you.
The system continually generates messages, the reboot errors will be in the end of the file but there may be errors earlier forecasting an upcoming crash like that you run out of memory.
The messages are labeled
i : info
d : debug
w : warning
e : error
Using the right tool or editor those have different colors, errors should be red.
1 Like
I will mess around with this tee command later.
I did figure out a way to prevent spontaneous phone reboots. Keep your phone connected to a Bluetooth speaker when using VLC or AntennaPod.
This would help with another LogCat to see what makes the difference. It could be a hardware problem concerning your device only and instead of crashing the app it crashes the phone.
Ok-I plan on doing that today. Plamen has access to the first logcat file so hopefully he can figure things out as well!
I am now running tee on my BraX3 with adb to generate another log file. This is the command I am using and it displays lots of information on my computer screen that is happening on my phone in the background!
adb logcat | tee BraX3_tee_diagnosis.log
I can not get my phone to crash today-that new log file with tee is over 7.0 MB now! 
My phone finally crashed again while making a log file on adb using tee. It is 8.9 MB!
EDIT:
The last warning was about Windscribe VPN!
plamen will tell you, in case the problem is the VPN remove the app an configure it through
Settings > Network & internet > VPN
I never use any VPN’s app, I always configure the native Linux/Android system
2 Likes