Can't send emulator bug report if emulator is stuck in boot loop without display [64707210]

Fixed

Bug

Migrated-Tools-emulator

[AOSP] win10

Status Update

No update yet.

Description

ni...@gmail.com

created issue #1

Aug 15, 2017 12:45PM

Build: 2.3.3, AI-162.4069837, 20170606,

AI-162.4069837, JRE 1.8.0_112-release-b06x64 JetBrains s.r.o, OS Windows 10(amd64) v10.0 , screens 2560x1440

Steps to reproduce:
1. Start an emulator that is known to cause a boot loop such that no screen capture is available (eg on a bad driver)
2. Open 'Bug report' menu from emulator extended controls.
3. It will keep trying to capture a screen shot and data even if these options are unchecked. It is possible to bypass screen shot issue by clicking the power button, but data collection never ends even if it is unchecked.

IMPORTANT: Please read

https://developer.android.com/studio/report-bugs.html carefully and supply all required information.

Comments

uc...@google.com <uc...@google.com> #2Aug 15, 2017 07:36PM

We use build flavours heavily with a lot of common code. The refactoring support in AS is really good but it continually catches us out when it doesn't work across all flavours in a project. It's a big gap for serious product development.

ni...@gmail.com <ni...@gmail.com> #3Aug 16, 2017 08:07AM

We at my company need this same feature. We have a lot of white labels and need refactor the same class across flavours. :(

ni...@gmail.com <ni...@gmail.com> #4Aug 16, 2017 08:08AM

I need this feature too...

hu...@google.com <hu...@google.com> Aug 16, 2017 10:29PM

Assigned to wd...@google.com.

wd...@google.com <wd...@google.com> Aug 17, 2017 12:25AM

Accepted by wd...@google.com.

ap...@google.com <ap...@google.com> #5Aug 29, 2017 10:21PM

+1, I need this very badly

wd...@google.com <wd...@google.com> Oct 9, 2017 09:45PM

Marked as fixed.