This patch implements nsSplashScreen for android and sends the progress events over the android java bridge.
What patches do I need to apply this one?
Summary: Android splash screen does not dismiss what accelerated layers is enabled → Android splash screen does not dismiss when accelerated layers is enabled
I have it applied over the patch on bug 594553
OS: Linux → Android
Hardware: x86_64 → ARM
Comment on attachment 473971 [details] [diff] [review] patch I don't see a splashscreen with this patch.
Comment on attachment 473971 [details] [diff] [review] patch do you have --enable-splashscreen in your mozconfig?
(In reply to comment #5) > Comment on attachment 473971 [details] [diff] [review] > patch > > do you have --enable-splashscreen in your mozconfig? Turned it on and it crashed. Cleaned the embedding/android directory and then it started working. Will have to look into that at some point.
Probably need to add a dependency on autoconf.mk for our preprocessed files
Comment on attachment 473971 [details] [diff] [review] patch This does feel faster. It seems to feel faster regardless of whether we update the progress bar or not. Wonder what's going on.
--enable-splashscreen/--disable-splashscreen don't seem to reliably enable/disable the progress meter. With both, non-GL fennec starts fine, but also with both, I never see anything drawn with GL. This is on a galaxy s.
(Note: I deleted $objdir/embedding/android in between changing --*-splashscreen.)
With --disable-splashscreen removed from my mozconfig, I don't get the splash screen; SW layers draw just fine; GL layers don't ever draw to screen.
This doesn't need to block b2 anymore since GL compositing has been pushed back to b3.
tracking-fennec: 2.0b2+ → 2.0b3+
There's a r+'d patch for this in bug 6050632; will land that soon.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 605063
You need to log in before you can comment on or make changes to this bug.