How to wake the INNER (unfolded) screen. (SOLVED)

[FF22]

I know an unusual question, perhaps. I thought the "transfer" from outer (folded) to inner (unfolded) was automatic. When my Pixel Fold is closed and I'm using the front screen and then UNfold it. The inner screen remains dark. I have to repeatedly tap to awaken it. If it is sleeping unfolded, again, it takes repeated taps to wake it up.

Is there a setting I might have changed or is there something I'm doing wrong? Default Pixel Launcher. Android 14 Beta something or other.

Thanks in advance.

 

[mustang7757]

It should Open automatically from the cover screen to inner screen,your on Android beta? No don't see a setting for that .

 

[bkeaver]

When I open mine, it just wakes up to the inner screen showing the content that I was being on the cover screen. There isn't a setting to make that happen, it just does it.

 

[Chex313]

It should wake. Get a hold of Google.

 

[FF22]

It should Open automatically from the cover screen to inner screen,your on Android beta? No don't see a setting for that .

On another forum (shudders at the thought!), someone mentioned that it might be a beta problem!!! No problem, I will just pound on the inner screen till it wakes up!!

 

[mustang7757]

On another forum (shudders at the thought!), someone mentioned that it might be a beta problem!!! No problem, I will just pound on the inner screen till it wakes up!!

Haha, maybe a reboot?

 

[FF22]

It should wake. Get a hold of Google.

By the neck, preferably!!!

 

[FF22]

Haha, maybe a reboot?

You are fast!

 

[mustang7757]

You are fast!

 

[Bkdodger1]

Mine is still working as intended in beta...

 

[FF22]

Mine is still working as intended in beta...

What are you doing RIGHT?

 

[Bkdodger1]

What are you doing RIGHT?

Ha I don’t think it’s me but feeling lucky I guess

 

[Bkdodger1]

Updated to beta 3 on the quarterly

QPR2 Beta 3 on Reddit today, and the new version has a build number of AP11.231215.007 on eligible devices, which are every Pixel phone, tablet, and foldable from the 5a to the 8 Pro. Like the most recent stable channel update, this version's security patch level is January 2024. As you'd expect with an update towards the end of a beta cycle, this update's release notes features a laundry list of bug fixes:

Fixed an issue where SPIR-V sequences of OpShiftLeft followed by OpShiftRight didn't produce the expected results for ARM Vulkan driver versions 43.0 and 44.0. (Issue #314048080)

Fixed issues that sometimes caused Bluetooth connections to be interrupted for some devices. (Issue #315324137, Issue #317798832)

Fixed issues that sometimes caused a device to crash or become unresponsive after restarting. (Issue #317282987, Issue #316689583, Issue #316188779)

Fixed issues that in some rare cases caused devices to reboot while in idle mode. (Issue #316903919, Issue #316557374)

Fixed an issue that caused live wallpapers to stop animating. (Issue #312869160)

Fixed an issue that prevented Google Assistant from activating in some cases. (Issue #311934282)

Fixed an issue that sometimes caused multi-finger gestures to stop working.

Fixed an issue where the device's screen didn't initially turn on when the screen was double-tapped or the power button was pressed.

Fixed an issue that sometimes caused higher than usual CPU usage during video playback.

Fixed a system issue that sometimes caused poor audio quality or higher power consumption when making calls.

Fixed an issue where the keyboard was always shown even if the "Swipe up to start search" setting was disabled in system settings.

Fixed an issue where sometimes when a user unlocked the device using their fingerprint, there was no haptic feedback.

Fixed an issue for Pixel Fold devices where sometimes after a user unlocked the device while it was folded, the inner display didn't turn on after unfolding the device.

Fixed various issues that were impacting system stability, performance, connectivity, camera, and accessibility.

 

[FF22]

I did the update a bit earlier. Today's Beta Update appears to have fixed the problem with the inner screen awakening (so far, fingers crossed).

 

[Bkdodger1]

I did the update a bit earlier. Today's Beta Update appears to have fixed the problem with the inner screen awakening (so far, fingers crossed).

Let’s hope it stays proper