Closed Bug 503109 Opened 15 years ago Closed 15 years ago

do our first run work during installation

Categories

(Firefox for Android Graveyard :: General, defect)

All
Windows Mobile 6 Professional
defect
Not set
normal

Tracking

(fennec1.0b1-wm+)

RESOLVED FIXED
Tracking Status
fennec 1.0b1-wm+ ---

People

(Reporter: blassey, Assigned: alexp)

References

Details

(Keywords: mobile)

While our start up time on windows mobile in general isn't great, its extra awful for the firstrun because of the profile creation.  We should do that during the cab installation.
tracking-fennec: --- → 1.0-wm+
Assignee: nobody → alex.mozilla
Status: NEW → ASSIGNED
Bug 502933 contains a fix for this one as a part of the new installer.
When browserd lands, we may want to just launch that. CC'ing crowder
The new installer implemented for bug 502933 runs "fennec.exe -silent", and it just works!

Have to make sure though if it will work with an unsigned EXE on the devices with active SECPOLICY_UNSIGNEDPROMPT security policy.
Depends on: 502933
tracking-fennec: 1.0-wm+ → 1.0b1-wm+
Summary: do our first run work during cab installation → do our first run work during installation
If fast-start daemon is enabled, the first run should be with "-faststart-hidden" argument, which leaves Fennec running in the background.
Depends on: 529678
Installer now runs Fennec (or FennecFastStart, if it exists) at the end of the installation process.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Depends on: 533581
No longer depends on: 533581
I receive a "SilentFirstRun failed Last Error = 30123" on both the HTC Touch Pro and Omnia 2 over trunk and 1.9.2. Is this something that was known when the patch landed?
Component: Windows Mobile → General
QA Contact: mobile-windows → general
Hardware: ARM → All
You need to log in before you can comment on or make changes to this bug.