Firefox android constantly closes as soon as it's opened
This has been going on since FF34. It takes several tries before it actually stays open long enough for anyone to do anything. Before anyone asks, no there are no crash reports I can send since it's technically a crash. The app just shuts itself down almost as soon as I open it. I have a Nook HD+ so I'm guessing no one here is going to bother to fix it so that it'll be more stable since Barnes&Noble is no longer selling HD's.
כל התגובות (7)
Hi Chesshur, Thank you for your questions, I understand that the Nook HD has Firefox for Android, however it is crashing.
There is a new version of Firefox 37 out today. I do not know if this device is compatible.
it still occurs on FF37. Firefox does not count it as a crash since it's not listed in the about:crashes tab, it just closes. It does this 99% of the time whenever I try to go on to Youtube or Tumblr. I'm not sure which version the Nook HD+ uses, but I do know that it's some version of Ice Cream Sandwich.
The youtube app should be available from the Google play store on that device. However for Tumblr http://app4smart.com/en/phone/barnes-.../557-tumblr.html might also help.
In Firefox for Android in the mean time I am happy to troubleshoot further if these are not helpful alternatives.
I already have the Youtube app, but it no longer has the ability to download videos. I use the addon "Youtube Center" to download videos with FF. As for the Tumblr app, I tried it a while ago and I found it to be poorly designed. However, the crashing actually may be device related and not caused by FF. I noticed that the Nook has a very nasty habit of syncing itself constantly and that may be what is causing the crash since there is no way to stop the Nook from syncing since it tries to sync even with WIFI turned completely off.
Hi Chesshur, I asked the mobile team for some help on how to further investigate what might be happening. Would collecting a logcat log be something that could be done on the Nook HD+?
For example enabling the developer tools and launching the app while connected to a usb to a desktop installation of Firefox? Take a look at the instructions and please post back if it is.
In order to investigate any errors it is possible to connect the device via remote debugging:
- Connect the device to the computer via usb.
- In android settings go to About device and double tap on build id 7 times
- Go back and now see the developer menu
- Open the Web Console on the Desktop computer the mobile device is connected to. Click on the gear icon in the menu and on the far right column (3rd at the bottom) make sure "enable remote debugging" is enabled
- Open up Firefox on the android go to settings > developer tools and check remote debugging
- From Desktop go to Tools > Connect
- Open Tools > Console
- Click on gear and on the far right click on "Remote debugging for this session only"
- [adb sdk install required] in a terminal window
adb devices
make sure a device is listed.
- On desktop in the window that openned up when you opened up connect click on connect
- Immediately after run this in the terminal:
adb forward tcp:6000 localfilesystem:/data/data/org.mozilla.firefox/firefox-debugger-socket
- On the device hit enable on the connection
- should be connected on the connect and click on the remote tabs.
- the logs will start to show up in the console.
- If you need adb log cat logs run in the terminal before you start to test:
adb logcat > text.txt
- Open up the Web Console on the desktop to view any errors when the application first launches.
note: gcp contact in #mobile
השתנתה ב־
Two follow up questions that are easy:
- Does is happen only for the main user or for all users?
- Does it happen if you install it, not on/from the sdcard?
I can't give you a logcat file since I don't have ADB installed on the laptop I'm using also Nook's setup is different from most android devices so your instructions won't work here. As for your question about whether it happens if from SD or device, Nook does not allow apps to be installed to SD cards so it happens on the device itself.