Closed
Bug 1099439
Opened 10 years ago
Closed 9 years ago
Crashes on Startup Samsung Galaxy S4
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: guigs, Unassigned)
Details
Reference: https://support.mozilla.org/en-US/questions/1026855 and https://support.mozilla.org/questions/1030671 continued: https://support.mozilla.org/en-US/questions/1030671 Quick summary: Started: 10/16/14 started quitting on any website. no crash notice. App just quits. Reinstalled: Via wireless Shows history - bookmark - etc. Soon as it connects on the internet it quits. Started in version 33. 1st: Galaxy S4 Model ISGH-M919 Android 4.2.2 Baseband M919UVUAMDL Kernel 3.4.0-453951 se.infra@SEP-133 #1 Fri Apr 26 16:55.54 KST 2013 Build JDQ39.M919UVUAMDL-iwireless1.2 SELinux status permissive Second: Graphics Adapter Description Model: SGH-M919, Product: jfltetmo, Manufacturer: samsung, Hardware: qcom, OpenGL: Qualcomm -- Adreno (TM) 320 -- OpenGL ES 2.0 V@14.0 AU@ (CL@3544079) Device ID Adreno (TM) 320 Driver Version OpenGL ES 2.0 V@14.0 AU@ (CL@3544079) GPU Accelerated Windows 1/1 OpenGL (OMTC) Vendor ID Qualcomm WebGL Renderer Qualcomm -- Adreno (TM) 320 In the threads I also asked to attempt an logcat, since there are no crash reports.
Reporter | ||
Updated•10 years ago
|
OS: All → Android
Hardware: All → ARM
Version: Firefox 35 → Firefox 33
Comment 1•10 years ago
|
||
If possible, could we get people to try using Nightly and see if the problem still exists?
Comment 2•10 years ago
|
||
I installed Nightly 10 minutes ago. So far, it hasn't crashed. I'll let you know tomorrow if the problem still exists.
Comment 3•10 years ago
|
||
Also, again I noticed these reports are form 4.2.2. If the devices update to 4.4 is the problem gone?
I borrowed Nick Alexander's Galaxy S4, running Android 4.3, and I was unable to reproduce a crash.
Comment 5•10 years ago
|
||
Apologies for the delay in replying. A) Nightly seemed to work just fine. b) I upgraded the phone to KitKat, and Firefox seems to be ok on that version.
Comment 6•10 years ago
|
||
Thanks for the help.
Marking resolved based on comment 5. Thanks for your help, Rebecca.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Updated•10 years ago
|
Status: RESOLVED → UNCONFIRMED
Ever confirmed: false
Resolution: WORKSFORME → ---
Comment 8•10 years ago
|
||
Much like the GFX issues on desktop we can't get all users to update. We should investigate downgrading a phone to 4.2 to attempt to resolve this issue.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•10 years ago
|
Flags: needinfo?(kbrosnan)
Comment 9•10 years ago
|
||
I have this issue. I'm on 4.2.2 and refuse to update my phone as I don't wish to break root and re-root. I had to use an alternate download store to revert back to 32.x (which still works fine).
Comment 10•9 years ago
|
||
Can you attach to this bug a text logcat from your device capturing your attempt to launch the browser?
Flags: needinfo?(the.moonkeeper)
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago → 9 years ago
Resolution: --- → WORKSFORME
Updated•9 years ago
|
Flags: needinfo?(kbrosnan)
Assignee | ||
Updated•3 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
•