Access USB OTG in Android 11 [246857526]

Fixed

Bug

[AOSP] assigned

adexe s nau

Status Update

No update yet.

Description

km...@gmail.com

created issue #1

Sep 15, 2022 07:27AM

According to the documentation https://developer.android.com/training/data-storage/manage-all-files#operations-allowed-manage-external-storage, MANAGE_EXTERNAL_STORAGE permission grant access to root directory of the USB (OTG) drive.

val sm = application.getSystemService(Context.STORAGE_SERVICE) as StorageManager
val sv = sm.storageVolumes

sv.forEach{
    it.directory.exists()
}

The above code returns 'true' for primary_storage and SDCARD. For USB drive, cannot access with MANAGE_EXTERNAL_STORAGE permission.

Comments

ra...@google.com <ra...@google.com> Sep 15, 2022 07:34AM

Assigned to vi...@google.com.

vi...@google.com <vi...@google.com> #2Sep 15, 2022 11:05AM

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

commit 16278c75a09262bfc2b1e230730f79ec5a4d4918
Author: Andrey Kulikov <andreykulikov@google.com>
Date: Tue May 25 18:25:16 2021

Do not reset initial scroll position in LazyColumn/Row when items are loaded asynchronously

If the initial scroll position(or restored scroll position) is not 0 this value will be immediately overridden by 0 if there were no items yet provided for LazyColumn/Row.
It is easily reproducible with Paging where we start loading asynchronously and there is always a first frame when we don't have any items.

Fixes: 177245496
Test: new tests for LazyColumn and LazyRow
Change-Id: I95e374fb06dc480aab7b56b8b3cacb92ca1188a9

M compose/foundation/foundation/src/androidAndroidTest/kotlin/androidx/compose/foundation/lazy/LazyColumnTest.kt
M compose/foundation/foundation/src/androidAndroidTest/kotlin/androidx/compose/foundation/lazy/LazyRowTest.kt
M compose/foundation/foundation/src/commonMain/kotlin/androidx/compose/foundation/lazy/LazyListState.kt

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

km...@gmail.com <km...@gmail.com> #3Sep 15, 2022 01:19PM

I think this issue still exists. The fix could break easily when you add a header item to LazyColumn.

vi...@google.com <vi...@google.com> #4Sep 19, 2022 07:07AM

Yes, we basically just changed the default behavior for the empty case for now. Please track this bug b/179397301 for the following work in this space.

km...@gmail.com <km...@gmail.com> #5Sep 21, 2022 07:48AM

Also, the itemCount always started from 0 when navigated back. I can't identify whether it is really empty or just a temporary state. Especially if I need to show an empty UI, it will flash shortly then display the paging data.

My workaround currently is to keep `LazyPagingItems` object in `ViewModel`, so that `itemCount` and other state will be the same when navigated back.

vi...@google.com <vi...@google.com> #6Sep 21, 2022 08:45AM

yes, it is expected as the paging is starting loading asynchronously and there is always at least one frame when there is no items yet

km...@gmail.com <km...@gmail.com> #7Sep 21, 2022 09:21AM

But we need a mechanism to display an empty UI when there is really no data. Blink screen is definitely not good for UX.

km...@gmail.com <km...@gmail.com> #8Sep 27, 2022 05:02PM

As it is not really related to the initial issue described in this bug don't you mind filing a separate bug here

https://issuetracker.google.com/issues/new?component=413106&template=1096385
so we can discuss this separately.
Thanks!

vi...@google.com <vi...@google.com> #9Sep 28, 2022 09:33AM

Marked as fixed.

Where can I find the new bug? this issue affect me as well.

km...@gmail.com <km...@gmail.com> #10Sep 30, 2022 02:51AM

>My workaround currently is to keep `LazyPagingItems` object in `ViewModel`, so that `itemCount` and other state will be the same when navigated back.

Can you provide an example? In my case stored `LazyPagingItems` object does not want to load data

upd: No longer needed. In my case the issue with LazyVerticalGrid. For myself I found solution - I made copy of LazyPagingItems to make counstructor public and create LazyPagingItems inside ViewModel, so reloading does not occur when navigating backwards