Closed zlyfer closed 5 months ago
in attached log, I see no actual issue please try taking a log while the system is not reponding adb logcat
in attached log, I see no actual issue please try taking a log while the system is not reponding adb logcat
Thank you so much for your work on going through the log! I apologize for the inconvenience and that the issue isn't actually in there.
Usually it happens at least once a day so I will monitor it today and as soon as it happens provide a (hopefully) better log.
do make sure you are on proper firmware also
do make sure you are on proper firmware also
Firmware? How can I check that?
you can not "check" actually if you remember you used 13.1.0.593(EX01) from install page, should be fine if you don't remember doing it, go to download page (https://crdroid.net/lemonade/10), click on firmware button and download it put phone in fastboot mode run firmware flash tool sideload crdroid zip again reboot to recovery sideload gapps zip again
Oh yea I definitely used the 593.
@gwolf2u The bug happened again and I connected my phone to my computer. I started logcat and tried to "wake" the device. I edited the issue and updated the log. Does this look more like something that describes the bug?
not able to reproduce here suggest clean flash as maybe some setting issue
Issue type
User interface
Device
Oneplus 9 (lemonade)
crDroid version
crDroid 10
Exact version / Build date
10.4/2024-04-28 10.4/2024-05-12 10.5/2024-05-12
Bug description
While inactive (phone screen off, laying on desk) it sometimes doesn't turn on anymore. No touchscreen nor any button inputs can wake the screen.
Steps to reproduce
It seems to be random. However I feel like it never happened so far when I used the phone recently. It always happened after I didn't use the phone for more than 10 minutes or so.
Step 1: Get latest build for crDroid 10 for the OnePlus 9. Step 2: Use the phone normally and then let it be inactive for a longer period of time.
Relevant log (logcat/build log)
Screenshots or videos
No response
Solution
Restarting the phone using
adb reboot
or holding down the power and volume up buttons.Additional context
Sorry for the long log. I tried to trim it as much as possible - with my knowledge. If there is any tips on how to get a better log, feel free to tell me and I try my best to provide it. EDIT: I can confirm that the bug still happens with the recent update and therefore added the version/build date to this issue.
Acknowledgements