Closed
Bug 1326559
Opened 9 years ago
Closed 8 years ago
"mach install" on Android x86 AVD causes a reboot
Categories
(Firefox for Android Graveyard :: Testing, defect, P1)
Firefox for Android Graveyard
Testing
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: glasserc, Assigned: gbrown)
Details
(Whiteboard: [mach])
Attachments
(1 file)
|
34.69 KB,
text/plain
|
Details |
I was able to get the android emulator started by removing `-enable-kvm` from `android_devices.py` and using `./mach android-emulator --version x86`. However, when I tried to do `./mach install`, the Android emulator rebooted (making it difficult to install or test my build). I'm not really an expert in this area, but from what I can see, the `emulator.log` output doesn't look unusual. The output of `adb logcat` during this process shows a SEGV of `PackageManager`. I have attached this log in case it is of any use.
Updated•9 years ago
|
Whiteboard: [mach]
| Assignee | ||
Updated•9 years ago
|
Assignee: nobody → gbrown
Priority: -- → P1
| Assignee | ||
Comment 1•9 years ago
|
||
This works for me: I can 'mach android-emulator --version x86' and then 'mach install' (after building and packaging for x86) and then I can start Firefox on the emulator - no sign of trouble.
I tested on Ubuntu 16.04, with adb 1.0.36.
Assignee: gbrown → nobody
| Reporter | ||
Comment 2•9 years ago
|
||
I was able to reproduce it again on an artifact build of current tip (a9a67c9d3659fcd3dc4f5e5cdf1f889fd918e360). Fedora 25, adb 1.0.36. Sometimes instead of rebooting, I get "Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]" instead.
One thing that I might have done that perhaps makes my situation unique was that I ran "tools/android update sdk" at some point because I saw some message that something was out of date. It spent a lot of time downloading and updating stuff but I didn't really understand what it was doing. Is it maybe possible that I'm running a mixed-version environment or have the wrong SDK version or something? I noticed I wasn't running the right version of the Android build tools (I had 23.0.1 whereas https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Simple_Firefox_for_Android_build says I need 23.0.3), so I updated to 25.0.2, but I can't tell if those are the ones being used or not.
| Assignee | ||
Updated•8 years ago
|
Assignee: nobody → gbrown
| Assignee | ||
Comment 3•8 years ago
|
||
I still have not managed to reproduce this.
I just ran, on Ubuntu 16.04 with adb "version 1.0.39 Revision 3db08f2c6889-android":
./mach build && ./mach package && ./mach android-emulator --version x86 --force-update && ./mach install
and had no problem.
:glasserc -- Do you still have trouble today? If not, can we close this?
| Reporter | ||
Comment 4•8 years ago
|
||
I haven't done anything with Fennec/Android for months, so I guess we can close it.
| Assignee | ||
Comment 5•8 years ago
|
||
Thanks Ethan.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Updated•5 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•