GrapheneOS / os-issue-tracker

Issue tracker for GrapheneOS Android Open Source Project hardening work. Standalone projects like Auditor, AttestationServer and hardened_malloc have their own dedicated trackers.
https://grapheneos.org/
353 stars 19 forks source link

Several problems with the screen on the Pixel Fold #4111

Open jamesponddotco opened 5 days ago

jamesponddotco commented 5 days ago

Having several issues with the screens in the first generation Pixel Fold.

With the update prior to the one released today, my Pixel Fold would take several minutes to switch from the outter screen to the internal screen when opening it up, and the same goes the other way around.

With the update released today, the screen I use to boot the device stays active no matter what, and it never switches to the other screen... I basically have to reboot the device with the phone closed if I want to use it closed, and with the phone open if I want to use it open.

Doesn't seem to be a hardware issue since the problem changed with the update. I can provide any logs necessary if told where to look for them, haha.

I'm on the beta channel, by the way.

thestinger commented 5 days ago

Not able to replicate an issue. Make sure developer options are off.

jamesponddotco commented 5 days ago

No developer options enabled; I'll try to reinstall tonight to see if that helps.

As an aside, I looked at the system log and I see something that may be related?

hwc-display: [SecondaryDisplay] resetColorMappingInfoForClientComp:: resetColorMappingInfo() idx=2 error(-22)
hwc-display: Fail to open file data/vendor/log/hwc/SecondaryDisplay_hwc_error_log0.txt, error: Permission denied

The permission denied for the log file gets repeated a couple of times.

thestinger commented 5 days ago

You could factory reset instead of reinstalling but it shouldn't be necessary to do that. It's strange, can't replicate any issue here and didn't get any other reports of it.

jamesponddotco commented 5 days ago

Is there any way for me to access data/vendor/log/hwc/SecondaryDisplay_hwc_error_log0.txt? I assume these logs would shed some light on the issue.

thestinger commented 5 days ago

Not sure how to do that. It might be included in a bug report zip captured via developer options.

jamesponddotco commented 5 days ago

Just tried that, but while it does include the data directory, it doesn't include the vendor one inside. Run find and grep to see if I could find anything, but nope, all I get is:

10-09 21:18:10.700  1000   571   571 E hwc-display: [SecondaryDisplay] resetColorMappingInfoForClientComp:: resetColorMappingInfo() idx=0 error(-22)
10-09 21:18:10.700  1000   571   571 E hwc-display: Fail to open file /data/vendor/log/hwc/SecondaryDisplay_hwc_error_log0.txt, error: Permission denied
10-09 21:18:10.700  1000   571   571 E hwc-display: Fail to open file /data/log/SecondaryDisplay_hwc_error_log0.txt, error: No such file or directory
10-09 21:18:10.700  1000   571   571 E hwc-display: Unable to open log file for SecondaryDisplay_hwc_error_log0.txt
10-09 21:18:10.700  1000   571   571 E hwc-display: [SecondaryDisplay] resetColorMappingInfoForClientComp:: resetColorMappingInfo() idx=1 error(-22)
10-09 21:18:10.700  1000   571   571 E hwc-display: Fail to open file /data/vendor/log/hwc/SecondaryDisplay_hwc_error_log0.txt, error: Permission denied
10-09 21:18:10.700  1000   571   571 E hwc-display: Fail to open file /data/log/SecondaryDisplay_hwc_error_log0.txt, error: No such file or directory
10-09 21:18:10.700  1000   571   571 E hwc-display: Unable to open log file for SecondaryDisplay_hwc_error_log0.txt
10-09 21:18:10.700  1000   571   571 E hwc-display: [SecondaryDisplay] resetColorMappingInfoForClientComp:: resetColorMappingInfo() idx=2 error(-22)
10-09 21:18:10.701  1000   571   571 E hwc-display: Fail to open file /data/vendor/log/hwc/SecondaryDisplay_hwc_error_log0.txt, error: Permission denied
10-09 21:18:10.701  1000   571   571 E hwc-display: Fail to open file /data/log/SecondaryDisplay_hwc_error_log0.txt, error: No such file or directory
10-09 21:18:10.701  1000   571   571 E hwc-display: Unable to open log file for SecondaryDisplay_hwc_error_log0.txt
10-09 21:18:10.701  1000   571   571 E hwc-display: [SecondaryDisplay] resetColorMappingInfoForClientComp:: resetColorMappingInfo() idx=3 error(-22)
10-09 21:18:10.701  1000   571   571 E hwc-display: Fail to open file /data/vendor/log/hwc/SecondaryDisplay_hwc_error_log0.txt, error: Permission denied
10-09 21:18:10.701  1000   571   571 E hwc-display: Fail to open file /data/log/SecondaryDisplay_hwc_error_log0.txt, error: No such file or directory
10-09 21:18:10.701  1000   571   571 E hwc-display: Unable to open log file for SecondaryDisplay_hwc_error_log0.txt

I do get these permission audit messages right after, but I'm not sure if they're related:

10-09 21:18:10.697  1000   571   571 W binder:571_4: type=1400 audit(0.0:15955): avc:  denied  { search } for  name="log" dev="dm-56" ino=265 scontext=u:r:hal_graphics_composer_default:s0 tcontext=u:object_r:vendor_log_file:s0 tclass=dir permissive=0
10-09 21:18:10.697  1000   571   571 W binder:571_4: type=1400 audit(0.0:15956): avc:  denied  { search } for  name="log" dev="dm-56" ino=265 scontext=u:r:hal_graphics_composer_default:s0 tcontext=u:object_r:vendor_log_file:s0 tclass=dir permissive=0

Guess I'll just wait for an update and hope it fixes the issue ¯_(ツ)_/¯

jamesponddotco commented 5 days ago

It just occurred to me that this could still be a hardware issue. The sensor or whatever that says if the device is open or closed could be busted.