IssueTracker

Project: platform/frameworks/support
Branch: androidx-main

commit e465976de8f05f0d1db49b4e2887c9f3cd4beab5
Author: Jeremy Woods <jbwoods@google.com>
Date:   Wed Mar 17 17:07:42 2021

    Add OnBackPressedDispatcher observer before NavController observer
   
    If you add a OnBackPressed callback with the NavBackStackEntry as the
    lifecycle owner, if the Activity Lifecycle is STOPPED and STARTED again, the navController callback and NavBackStackEntry callback are readded to the Activity Lifecycle in the wrong order. This means that the new callback will not properly intercept onBackPressed() calls from the system, they will instead be intercepted by NavController.
   
    If an OnBackPressedDispatcher is set, we should remove and readd the
    NavController observer after we add the callback to the dispatcher.
   
    RelNote: "OnBackPressedCallbacks added to a dispatcher with the
    NavBackStackEntry as the LifecycleOwner now properly intercept back
    after the Activity Lifecycle is STOPPED, then STARTED"
    Test: NavControllerTest
    Bug: 182284739
   
    Change-Id: I6acf78848546160eaea7ed700ef8875664a125d0

M       navigation/navigation-runtime/src/androidTest/java/androidx/navigation/NavControllerTest.kt
M       navigation/navigation-runtime/src/main/java/androidx/navigation/NavController.kt

https://android-review.googlesource.com/1643646

Project: platform/frameworks/support
Branch: androidx-main

commit f231e0f384f9fd2e7a078bfcbeb7768c82c617b1
Author: Jeremy Woods <jbwoods@google.com>
Date:   Wed Mar 17 17:40:05 2021

    Add BackHandler callback with a LifecycleOwner
   
    We need to ensure that the callback from BackHandler remains in the
    proper position in the event of Lifecycle changes.
   
    RelNote: "The BackHandler will now properly intercept back presses in
    the event that the Activity is STOPPED, then STARTED again, and other
    callbacks were added with a LifecycleOwner."
    Test: BackHandlerTest
    Bug: 182284739
   
    Change-Id: I71de6184ba73f56b34de9dcddaf138d98c46417f

M       activity/activity-compose/build.gradle
M       activity/activity-compose/src/androidTest/java/androidx/activity/compose/BackHandlerTest.kt
M       activity/activity-compose/src/main/java/androidx/activity/compose/BackHandler.kt

https://android-review.googlesource.com/1644062

Project: platform/frameworks/support
Branch: androidx-main

commit d1d6f89ba90be8e7fba193570b427f52ec98f57a
Author: Jeremy Woods <jbwoods@google.com>
Date:   Wed Mar 31 09:40:42 2021

    Make nav compose depend on Navigation 2.3.5
   
    Upgrading to the latest Navigation version to take advantage of fixed
    bugs, (particularly around OnBackPressedDispatcher and lifecycles
    b/182284739).
   
    RelNote: "Navigation-compose now depends on Navigation version `2.3.5`"
    Test: ./gradlew bOS
    Change-Id: I7e63b32c93deaee60b1d5e132d3fa255c3ba85e2

M       navigation/navigation-compose/build.gradle

https://android-review.googlesource.com/1660640

does not work for me on '2.4.2'

        val navController: NavHostController = rememberNavController()
        HomeNavHost(navController = navController)

        BackHandler(true) {
            // code doesnt get called here
        }

I got similar issue, after I run launcher (exp: select document), BackHandler no longer triggers

    BackHandler{
        action.onBack()
    }

to solve BackHandler no longer triggers after i run launcher, i am using this

@Composable
fun BaseBackHandler(onBackHandler: () -> Unit = {}) {
    var refreshBackHandler by rememberSaveable { mutableStateOf(false) }
    OnLifecycleEvent { _, event ->
        when (event) {
            Lifecycle.Event.ON_PAUSE -> {
                refreshBackHandler = false
            }
            Lifecycle.Event.ON_RESUME -> {
                refreshBackHandler = true
            }
            else -> {}
        }
    }
    if (refreshBackHandler) {
        BackHandler {
            onBackHandler()
        }
    }
}

Is there a way to re-open this issue? Still experiencing this on latest version of the navigation library.

Only way to use face unlock is making factory reset

Same issue, that I believe won't be fixed. Verizon, I hate you!

Beta 2 did not fix this unfortunately.

I am still unable to downgrade on a Sprint Pixel 4 on Beta 2. Still fails and fails into fastboot 3X and reverts to Android 11 beta 2.

The issue has been fixed and it will be available in a future build.

I have the Same Problem

Як повернути ся на Андроїд 10?

Same issue here, I can't downgrade to Android 10, i'm stuck with the 11 and the battery in draining very fast on idle with the android beta 2 update. What should I do?

It looks like they marked this as fixed, and it will be in an upcoming release - but will we be notified of when that release goes out? I have given up trying to install the update that is on my phone right now since it keeps screwing up my phone.

I am on Verizon and I am in the same situation. The bootloader unlock toggle cannot be enabled. The battery percent is at 50%, it doesn't give me any usage info. The phone will die immediately after unplugging it from the charger, after charging all night. Every few days after it completely dies, it will turn back on and show the battery percent for a day and then the same thing happens again. I was told by Pixel support that a warranty claim cannot be filed unless I am running a stable, public version of Android 10. I was also told that some Android 10 users are having this issue unrelated to the Android 11 Beta testing. I would appreciate some help in at least getting my phone back to Android 10, or push out an update to fix this issue.

I put out Android 11 beta but OTA downgraded is unable to Android 10

Same! Opt out, install 10, after erasing and reboot it still has me in beta.
Hopefully the fix noted above fixes this.
I'm in the UK with an unlocked device, so I don't think it's a Verizon or sprint issue? We don't use them here

Its isn't a verizon issue, it's the same for us! When you downgrade to Android 10 face id doesn't work anymore and you are stocked with Android 11.

- Build Number: google/bonito/bonito:11/RPB2.200611.009/6625208:user/release-keys


Didn't open some app


Filed by Android Beta Feedback. Version (Bundled): 2.10-betterbug.external_20200514_RC01
To learn more about our feedback process, please visit https://developer.android.com/preview/feedback#feedback-app.

- Build Number: google/coral/coral:11/RPB2.200611.009/6625208:user/release-keys


Android 10 not available even after 24h of Android beta 11 opting out

Filed by Android Beta Feedback. Version (Bundled): 2.10-betterbug.external_20200514_RC01
To learn more about our feedback process, please visit https://developer.android.com/preview/feedback#feedback-app.

Same issue, cannot downgrade to Android 10 after opt out of beta. I download the stable release, go through the install then in restart it puts me into the boot menu and when I'm able to get it to boot it starts the 11 beta. Has happened 3x. Please fix, I am having problems with apps in the beta. Thanks.

After many failed attempts to opt out of beta 11, phone is working very unstable. Many apps do not work, like the camera, flashlight, and sporadic emails. I need to perform a hard not, and then will get flooded with the missed emails.
Other things that are affected flickering screen, can't swipe up when running certain apps. And keep getting notified to install Android 10, because it is trying to opt out, and fails.

Would you be able to revert the opt out state and or back in, I am not able to.
I am not sure that the phone will get the fixed for the beta 11 issue in the state of its in.
Thanks

I am experiencing the same issue.  I received a refurbished 4xl since my old 4xl charging port was no longer working.  I updated to Android 11 and everything was fine until yesterday when my earpiece speaker malfunctions.  Cant hear anyone on call and distorts playing music.  I contacted support for an exchange and was told they cant help me until i revert back to android 10.  
I'm unable to do so like you all.  It puts me in bootloader screen and then after several attempts reboots android 11 which has been wiped.

This has rendered my personal Pixel 4 XL unusable. As i have "Opted-Out" of the Android 11 Beta, my device is now stuck in a recursive wipe/reboot/bootloader/boot Android 11 instead of reverting to Android 10 as it should do. It's been as such for days now and my Pixel 4 XL is simply a very expensive paper weight now. Please can you advise on how to downgrade to Android 10 asap so that I can have a phone again?

Thanks,
Ben

- Build Number: google/coral/coral:11/RPB2.200611.009/6625208:user/release-keys


Due to app compatible with beta2. I'm unable to go back to android 10. Wipes data then returns to beta 2

Filed by Android Beta Feedback. Version (Bundled): 2.10-betterbug.external_20200514_RC01
To learn more about our feedback process, please visit https://developer.android.com/preview/feedback#feedback-app.

I also have this issue. July 19

Same issue here.

same issue, downloads the android 10, resets the device to MS and lands back on ANdroid 11 beta. Battery on the other side got improved by a lot. Will we be notified here on the release gone out into the world?

just noticed the toggle IN PROD on the bug, so will watch for that :)

- Build Number: google/coral/coral:11/RPB2.200611.009/6625208:user/release-keys


I'm having the same problem. Got some apps that will not work with android beta.

Filed by Android Beta Feedback. Version (Bundled): 2.10-betterbug.external_20200514_RC01
To learn more about our feedback process, please visit https://developer.android.com/preview/feedback#feedback-app.

Information redacted by Android Beta Feedback.

- Build Number: google/coral/coral:11/RPB2.200611.009/6625208:user/release-keys


Unable to downgrade

Filed by Android Beta Feedback. Version (Bundled): 2.10-betterbug.external_20200514_RC01
To learn more about our feedback process, please visit https://developer.android.com/preview/feedback#feedback-app.

Has anyone been able to confirm that we can downgrade to 10 now that 2.5 is out? Did it work for anyone? Call me a coward, but...

I couldn't because when I wanted to get out of the program, they sent me the downgrade version 10, I downloaded the update and indicated that I needed to do a factory restoration, but when I started it and I entered it was again version 11 beta, so I never could, I tried to follow these steps but nothing happened either ( https://andro4all.com/guias/android/desinstalar-android-11-volver-android-10 )

I can confirm that this issue is resolved. Updated pixel 4 to beta 2.5 and then opted out. The phone downgraded to Android 10. Yay!

I successfully downgraded to Android 10 by following the steps. Thx.

can confirm also, downgrade to android 10 was successful on Beta 2.5 on Pixel 4

Nice

On Wed, Jul 22, 2020, 2:52 PM <buganizer-system@google.com> wrote:

I've successfully downgraded now.

I (like others here) am currently in a situation where my device is un-enrolled from the Android 11 Beta and the downgrade to Android 10 fails. I can't upgrade to Beta 2.5 as when my device boots with a fresh copy of Android 11, it immediately informs me that I am un-enrolled, downloads Android 10, reboots (and wipes the device) to the bootloader then nothing happens before it reboots to a fresh copy of Android 11 again.
If i try to re-opt in to the Android 11 beta here: https://www.google.com/android/beta#devices , I receive an error "We can't enrol your device at the moment. Please try again later.".
I've tried Factory Reset (Through bootloader Recovery Mode) but it still boots to Android 11 and the: "boot, download Android 10 update, reboot (& wipe)" recursive loop persists.

I contacted Google support who told me that they won't support me with the Google issue affecting the Google Android 11 beta on my Google Pixel 4 XL device... so at the moment, I am paying for a device that I can't use all because I participated in the Android beta.

We were advised on enrolment that we can unenroll back to Android 10. Here’s the statement:
“You will not be able to unenrol and revert back to a lower public release version of Android without first wiping all locally saved data on your device.”
Source: https://www.google.com/android/beta#devices
I am happy to wipe all locally saved data (as my device has done this multiple times due to this issue). So Is this a false statement?

How can we revert to Android 10 or re-enrol to the Android 11 beta to download beta 2.5 to fix this issue and have a working Pixel 4 XL again?

Many thanks

To confirm, I have tried installing Android 10 twice this morning and the same issue persists. This issue is not fixed for my device.

Have you tried re-enrolling from a computer?
I had a similar issue but once Android 11 bottles back up I was able to
re-enroll which allowed me to get the beta 2.5

On Thu, Jul 23, 2020, 06:05 <buganizer-system@google.com> wrote:

Thank you, I had previously tried this and received an error of "We can't enrol your device at the moment. Please try again later." in my browser.
I've tried again this morning and it's worked! I Upgraded my device to the latest Android 11 Beta, opted out, Installed Android 10 through System Update on my device and it's all fixed!

Thank you for your help and for fixing this Google! :)

- Build Number: google/flame/flame:11/RPB2.200611.012/6677315:user/release-keys


Face unlock not work anymore


Filed by Android Beta Feedback. Version (Bundled): 2.10-betterbug.external_20200514_RC01
To learn more about our feedback process, please visit https://developer.android.com/preview/feedback#feedback-app.

- Build Number: google/coral/coral:11/RPB2.200611.012/6677315:user/release-keys


My phone is having problems when I try 2 open up an incoming call from the drop-down boxes on it does not pick up from the boxes for example the green box to pick up the call it doesn't do anything it goes to voicemail

Filed by Android Beta Feedback. Version (Bundled): 2.10-betterbug.external_20200514_RC01
To learn more about our feedback process, please visit https://developer.android.com/preview/feedback#feedback-app.

- Build Number: google/coral/coral:11/RPB2.200611.012/6677315:user/release-keys


Same problem here

Filed by Android Beta Feedback. Version (Bundled): 2.10-betterbug.external_20200514_RC01
To learn more about our feedback process, please visit https://developer.android.com/preview/feedback#feedback-app.

Why did Google automatically blok the oem after trying to factory reset the option on development option OEM UNLOCKING become available 'turn gray to white giving you access to oem (however) when I try to fastboot oem unlock it is still lock and when I goes back to dev option it turn back to gray so after 6 time factory reset Google manager told me that I got sell a returning phone so they cannot do anything to unlock it so my question is WHY ? I tried with Samsung work perfectly I tried with Motorola work perfect (event the most recent phone can manually be unlock) exception on Google pixel what everywhere I look we all have the same issue after flashing OTA and you know what m my pixel 2 factory reset 2 time on is own when my battery die at 0% and you LOCK my OEM for good when I did not lock inor tried to unlock it before

i'm a bit worried to try downgrading my pixel 3 after reading this... i don't live in the USA and if i fall into some issue this means the only support i can get is over the phone...

anyone can share their experience with such a configuration? i suppose it still works for most people, but i'm also curious to know for those that had a failure, if at least the device continues to work fine or what needs to be done to fix it.