See: Spotify/Youtube Reboot Phone (pdx203 - Community) (#8451) · Issues · e / Backlog · GitLab
Spotify and Youtube seem to reboot the phone on 2.6.3 on this device. Ticket elaborates further, but will quote it here as well. Unaware of any solutions at this time. If anyone has encountered this issue and found a solution or workaround, please let me know.
- /e/ version: 2.6.3-u-20241219455571-community-pdx203, 11/01/24 Security Update.
- Device model(s): pdx203 (Xperia 1 II)
- Developer mode enabled: yes (tried without)
- Device rooted: yes (APatch)
- Trackers blocker enabled: yes
## Summary
When audio is played through Spotify, or video through YouTube, screen flickers on and off and then the phone reboots.
## The problem
When Spotify or Youtube are installed, both will open without issues and you can browse throughout the app, however, as soon as you select a song (in Spotify) or a video (in YouTube) and it begins to play, the screen will go dark, and cycle the lock screen on and off about 12 times before the phone reboots. 90% of the time it will reboot to /e/OS, the other 10% it will reboot to recovery mode stating the phone failed to boot to the system, however rebooting from recovery when this happens, will often boot /e/OS normally. I do not recall having this issue in earlier T (13) builds, so I believe it to be exclusive to the new U (14) build.
**Steps to reproduce**
1.) Have pdx203 (may only be a bug on this device)
2.) Install Spotify, or YouTube.
3.) Open Spotify, or YouTube.
4.) Play something.
5.) Enjoy coffee while waiting for the device to reboot.
**What is the current behavior?**
Phone begins to play audio or video in the app, screen flickers on and off a dozen times (or less), phone reboots.
**What is the expected correct behavior?**
Phone should play audio or video in the app without reboot.
## Technical informations
**Relevant logs (`adb logcat`)**
Nothing in logcat after reboot.
**Relevant screenshots**
Unable to take screenshot or video of the issue (screen recorder output ends up corrupt due to interruption).
## Solutions
None known
**Workaround**
None known
**Possible fixes**
Possibly a GSF issue or call to function that MicroG does not support (unlikely as it works fine in earlier /e/OS releases), or some new DRM or feature that both apps are expecting, that is not present in /e/OS 2.6.3. Just speculating.
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services