[VTS] Fastbootd related VTS modules are failing. [331856213]

Infeasible

Bug

[AOSP] assigned

Status Update

No update yet.

Description

ja...@gmail.com

created issue #1

Mar 29, 2024 05:17AM

Android version: 13

VTS tool version: 13_r1

Modules Failing :-

FastbootGetvarUserspaceTest

FastbootVerifyUserspaceTest

Issue description:

My device is Android 13 launch device(with AOSP r24 tag), based on x86_64 architecture. Above mentioned vts modules are failing on my device. My device doesn't have adb over usb support, so i am running vts through adb over ethernet. My device have recovery and fastbootd(fastbootd over tcp) support, so i am running the above mentioned 2 vts fastbootd related modules with adb over ethernet. When i am running these modules, device is entering into fastbootd mode and stuck in it. Modules are failing with Could not find device <IP ADDRESS> in fastbootd error.

Questions i have :-

1.Are these failures of FastbootGetvarUserspaceTest & FastbootVerifyUserspaceTest vts modules are expected, if Android device doesn't support adb over usb or fastbootd over usb?

2.Are these modules pass with fastbootd over tcp support is present?

Experiment i did:- From host machine i ran below commands,

adb connect <IP ADDRESS of device>

adb reboot fastboot [device went to fastbootd mode now]

./fastboot -s tcp:<IP ADDRESS of device> getvar all [got o/p]

With the fastboot executable/tool, i can able to communicate with the device which is in fastbootd mode over tcp, but VTS modules are failing.

Comments

vi...@google.com <vi...@google.com> #2Mar 29, 2024 05:26PM

Assigned to vi...@google.com.

Information redacted by Android Beta Feedback.

vi...@google.com <vi...@google.com> #3Apr 7, 2024 06:52AM

Why hasn't this more stars? I have this in Beta right now and it's so annoying!

ja...@gmail.com <ja...@gmail.com> #4Apr 8, 2024 08:53AM

Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

vi...@google.com <vi...@google.com> #5Apr 9, 2024 04:28PM

The issue is not reproducible on our internal development build (which is ahead of the public release). Please test it on the final public release and let us know if you are still having issues.

ja...@gmail.com <ja...@gmail.com> #6Apr 10, 2024 10:26AM

comment#2

Can you still reproduce the issue? I haven't tried it yet. I don't have my phone currently. I'll try again tomorrow. But in the meantime, please do try yourself to replicate the issue on Beta 2 :=)

ja...@gmail.com <ja...@gmail.com> #7Apr 15, 2024 11:20AM

I cannot reproduce anymore on S2B2.211203.006

ja...@gmail.com <ja...@gmail.com> #8Apr 17, 2024 06:07AM

comment#7

Awesome, so it's probably fixed! :)

Google, you can close this now, I think :=)

vi...@google.com <vi...@google.com> #9Apr 20, 2024 11:30AM

Currently the test requires USB. If you'd like to submit a fix for the test to AOSP, we can review it.

ja...@gmail.com <ja...@gmail.com> #10Apr 24, 2024 07:03AM

ok, thanks for the information.

vi...@google.com <vi...@google.com> #11May 5, 2024 04:58AM

Status: Won't Fix (Infeasible)

We believe with reference to the above comment, your query has been answered, hence closing the bug. Please feel free to re-open the issue in the future if desired.