Bug 486594 - "Disks & Devices" reports AOSP device in initial charge reporting state has accessible storage, but it doesn't.
Summary: "Disks & Devices" reports AOSP device in initial charge reporting state has a...
Status: REPORTED
Alias: None
Product: frameworks-solid
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 6.1.0
Platform: Fedora RPMs Linux
: NOR minor
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL: https://discuss.kde.org/t/how-to-acce...
Keywords:
Depends on: 486931
Blocks:
  Show dependency treegraph
 
Reported: 2024-05-04 22:41 UTC by Roke Julian Lockhart Beedell
Modified: 2024-05-12 20:48 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
4wy78uwh: performance-


Attachments
The dialog. (31.30 KB, image/png)
2024-05-04 22:41 UTC, Roke Julian Lockhart Beedell
Details
Example of the recognised device. (50.60 KB, image/png)
2024-05-04 23:04 UTC, Roke Julian Lockhart Beedell
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Roke Julian Lockhart Beedell 2024-05-04 22:41:58 UTC
Created attachment 169197 [details]
The dialog.

SUMMARY
The "Disks & Devices" plasmoid reports that an AOSP device in its initial charge-reporting state has accessible storage, but it doesn't.

STEPS TO REPRODUCE
1.  Shutdown the device (using `adb shell reboot -p` per https://android.stackexchange.com/revisions/47994/2#:~:text=Try-,adb%20shell%20reboot%20-p,-to%20shutdown%20the).
2.  Boot into the state whereby it solely displays its charge (as https://android.stackexchange.com/revisions/257032/1#:~:text=Most%20importantly%2C%20I'd,device%20commences%20charging describes).
3.  Attempt to access the device's storage via the plasmoid.

OBSERVED RESULT
An error dialogue window appears.

EXPECTED RESULT
The plasmoid shouldn't present the device has possessing accessible storage.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.8-300.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor
Memory: 30.5 GiB of RAM
Graphics Processor: AMD Radeon RX 5700
Manufacturer: ASRock
Product Name: X670E Taichi

ADDITIONAL INFORMATION
https://discuss.kde.org/t/where-to-report-bug-for-disks-devices-plasmoid/15057/1?u=rokejulianlockhart#:~:text=i%20ask%20because%20i%20want%20to%20report%20aosp%20devices%20being%20identified%20as%20accessible%20after%20booting%20from%20an%20unpowered%20state%20(when%20their%20bootloader%20displays%20charging%20information%2C%20but%20the%20os%20is%20not%20initialized).
Comment 1 Roke Julian Lockhart Beedell 2024-05-04 23:04:56 UTC
Created attachment 169199 [details]
Example of the recognised device.
Comment 2 Roke Julian Lockhart Beedell 2024-05-04 23:09:32 UTC
(In reply to Roke Julian Lockhart Beedell from comment #0)
The fact that I've enabled https://developer.android.com/studio/debug/dev-options#Enable-debugging might be relevant.