![Firefox untuk Android logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-37-28-a0d9f0_1.png)
Firefox crashes directly after start on LG P970 with ICS
Since two or three updates Firefox crashes always 1 or 2 seconds after starting the app.
I've tested it also with the beta 20.0b7 apk... it's always the same... start the app - 1 or 2 seconds later I'm back on the home screen.
I have the LG P970 Optimus Black phone with ICS 4.0.4
Is a fix for this problem on this phone in sight? Cause I really like the firefox browser and really dislike to use some of the other browsers in the store...
Semua Balasan (20)
When do the crash start? Right on startup? Mid way through?
some seconds after the startup... if I start the app I see some seconds the firefox frontpage and then the app close without any error or something like that and then I'm back on the android homescreen.
The problem started with Firefox 19. I have just checked with Firefox 20 and it is still happens. The workaround for me was to manually install this build: https://ftp.mozilla.org/pub/mozilla.org/mobile/releases/18.0.2/android/ So sad, since 19 is much faster and 20 has new features.
The crash only happens in LG's ICS 4.0.4. I have an Cyanogen 10 installed on this same device. There Firefox 19 worked fine.
- (
Thanks for the answer! I hope someone at mozilla can fix this 'cause I'm sure LG won't fix it -.-'
Could you try clearing data? Could you try uninstall - reboot - install ?
yeah... dosn't help! everything newer then 18.0.2 crashes on startup...
Would you provide a crash id? Type about:crashes in the address bar. There should be some crash ids listed.
kbrosnan: I think Firefox crashes once tapped on to be opened therefore not giving enough time to type in about:crashes.
Right! not enough time to type anything in the address bar ;)
but I found the cause of the crash with logcat. The problem is that Fennec/Firefox requires READ_PHONE_STATE permission...
04-06 22:50:52.317: W/System.err(24209): Caused by: java.lang.SecurityException: Requires READ_PHONE_STATE: Neither user 10147 nor current process has android.permission.READ_PHONE_STATE.
I tried to build Fennec from source with this permission added in the AndroidManifest.xml and it works... no more crashes.
But the big question now is why does Fennec need permission to read the phone state only on LGs 4.0.4 for this device?
Hi Kauraiko:
This sounds like a bug. I suggest filing a bug at bugzilla.mozilla.org if you haven't already.
Cheers!
...Roland
Diperbarui oleh Roland Tanglao pada
READ_PHONE_STATE is not set by Mozilla. Are you using a Mozilla binary? The only place in the Mozilla source READ_PHONE_STATE is used is a tool called SUTAgent. This is not distributed with Firefox. It is only used for testing.
https://mxr.mozilla.org/mozilla-central/source/build/mobile/sutagent/android/AndroidManifest.xml#38
Right, READ_PHONE_STATE is not set by Mozilla and that is the problem on LG's ICS build for LG P970... the offiziell Firefox build from the Play store crashes on startup after this exception: 04-06 22:50:52.317: W/System.err(24209): Caused by: java.lang.SecurityException: Requires READ_PHONE_STATE: Neither user 10147 nor current process has android.permission.READ_PHONE_STATE.
as you can see it need the permission for READ_PHONE_STATE but android doesn't grant it 'cause it's not set by Mozilla in the AndroidManifest.xml...
I build my own apk from the offizial source code (mercurial repo) and added this permission to the AndroidManifest.xml the result is that this build runs without crashes on my phone.
and btw I think the problem is LGs Android build and not on Mozilla's side...
Ah OK I understand now. I think we are tracking this as part of https://bugzilla.mozilla.org/show_bug.cgi?id=856445
Sorry for my bad english ;)
yeah looks right even if they think the problem is something else.
I have this problem too on my LG p970 ICS 4.0.4 using version 21 stable and 22 beta. It's almost 2 months now since a user found a solution and until now Mozilla team can't fix it.
zubacho54: We are working on this issue and reading the bug, we are close to a patch for it.
It's good to know that this issue has been fixed according to the changelog. Too bad, I can't even try it because my optimus black has just died 3 weeks ago. But, thanks anyway to Mozilla team.
Diperbarui oleh zubacho54 pada
Aww!! That's is just too sad to hear :(
hi zubacho54
yup fixed in firefox 22 for android which was released today.
sorry to hear about your phone!
...Roland
It works now with Firefox 22. Tested with LG's Android 4.0.4. Now going back to Cyanogen 10.1 nightly build. :)