Created attachment 589184 [details] logcat Tested on Windows and Linux emulators. The content is always black. We do seem to be using direct textures in the emulator, but I notice that the AndroidGraphicBuffer realloc test fails. Not sure if it's related.
love to see this fixed at some point.
(In reply to Doug Turner (:dougt) from comment #1) > love to see this fixed at some point. Actually it should be fixed now wuth the whitelist in place.
Created attachment 591986 [details] logcat 2 I was getting the black screen when Mfinkle reported this bug, and after comment 2 I rebuild Fennec. Now, I got a crash during startup, and I don't think it's due to my patch. There is the logcat. I don't know if there is crash signature, because I can't access to the about:crashes. I'll try to install GA to check it.
I am not seeing a crash on startup nor black screen with the linux emulator. used NDK 5 and 4.0.3 emulator. Theo have you checked recently?
No, not since my last comment. It's a good news if it's fixed, I'll try. Thanks!
Windows emulator still shows "empty" content
Created attachment 611713 [details] Logcat 3 And sadly I still have a crash at startup... 4.0.3, on Linux, like you nhirata, but my Linux is a VM, does it count? Maybe a bad VM configuration?
quite possibly. I had startup crashes with NDK6. I reverted back to NDK 5c and it works just fine now. (I had to change some things in my mozconfig as well) Can you show us your mozconfig? Here's my mozconfig : mk_add_options MOZ_OBJDIR=objdir-droid # Add the correct paths here: ac_add_options --with-android-ndk="/home/mozilla/android-ndk-r5c" ac_add_options --with-android-sdk="/home/mozilla/android-sdk-linux/platforms/and roid-14" ac_add_options --with-android-tools="/home/mozilla/android-sdk-linux/tools" ac_add_options --with-android-toolchain="/home/mozilla/android-ndk-r5c/toolchain s/arm-linux-androideabi-4.4.3/prebuilt/linux-x86" ac_add_options --with-android-platform="/home/mozilla/android-ndk-r5c/platforms/ android-5/arch-arm" # android options ac_add_options --enable-application=mobile/android ac_add_options --target=arm-linux-androideabi ac_add_options --with-endian=little #ac_add_options --enable-debug-symbols ac_add_options --with-system-zlib export JAVA_HOME=/usr/lib/jvm/java-6-sun/jre/bin/ ac_add_options --enable-warnings-as-errors
Hum, I tried with a regular try-server build, who works on a phone.(In reply to Naoki Hirata :nhirata from comment #8) > quite possibly. I had startup crashes with NDK6. I reverted back to NDK 5c > and it works just fine now. (I had to change some things in my mozconfig as > well) Can you show us your mozconfig? > Hum, in fact, I tried with a regular try-server build, which works on a phone. Here is the build: http://email@example.com/try-android/ (And the changes https://tbpl.mozilla.org/?tree=Try&rev=af7a388cd3a7) I guess if it's not working with an official build, it will not work with my own build, but I can try it too.
I tried with your build, and it worked fine as well for me. If you are on a computer with the en0 interface not active, you will have to set that to down. Test with the default browser. If it crashes or if the VM restarts on you, chances are it's not the fennec build, but the VM settings. Here are the following settings I have for my VM: Android 4.0.3 - API Level 15 (ARM (armeabi-v7a) SD card size 8 GiB Skin Build-in WVGA800 SD Card Support yes Abstracted LCD density 240 Cache partition size 66 MB Cache partition support yes Keyboard support yes Max VM application heap 512 Ideal size data partition 0 GPU emulation yes Touch-screen support yes
fyi, the screenshots are from the Mac OS Android VM. I also got it working on the Mac as well.