You can download the manifest_*.xml file from any build from the date that
you want, then use repo sync -m /tmp/manifest_*.xml to sync the revisions
from that manifest.
On Fri, Jun 28, 2019 at 7:56 AM Alex wrote:
> Hi folks,
>
> I did not find any related post to my question so I decided to
Hello,
For a very dirty workaround, you may find armtranslator (used in vbox86,
genymotion and in a bunch of noname x86 hdmi sticks) capable of running
some ARM apps with decent performance. Running the whole system (even
trimmed down to Go-style system) would result in penalties ranging in
5-30x,
How did you download it? Based on the banner, that's at least partially
master, not 9.0. A mismatched source tree could explain that error (or it
happened to be broken when you synced, and you should try syncing again if
you do want master).
- Dan
On Fri, Jun 28, 2019, 7:56 AM 岳羽
Hello all,
I tried to post this message on the Android Emulator group, but as there is
not activity since 2017, I have the weird feeling I will not get anything
there ^^. So here is my problem...
Regarding some needs on a project (scaling + third parties only available
in arm64), I must run
Hi Alessio
I was missing the steps of binary blob for pixel 3, after installing the
blob into root of aosp, it works as a charm !
On Thursday, June 27, 2019 at 4:50:21 PM UTC+8, Alessio Balsini wrote:
>
> Hi Jw,
>
> There are some missing pieces in your procedure, e.g., you didn't
> mention
Here is all the commands:
1. source build/envsetup.sh
2. lunch 21 (aosp_x86-eng)
3. rm -rf out && make -j4 2>&1 | tee b.log
than, always show the error log.
On Thursday, June 27, 2019 at 4:54:10 PM UTC+8, Alessio Balsini wrote:
>
> Can you please post all the exact commands you ran?
>
> Cheers,
