Iskanje po podpori

Izogibajte se prevarantski tehnični podpori. Nikoli vam ne bomo naročili, da pokličete telefonsko številko ali nam pošljete osebne podatke. Sumljivo dejavnost prijavite z gumbom »Prijavi zlorabo«.

Več o tem

firefox Beta quits on my android. no crash - just quits - is there a fix for this yet?

  • 11 odgovorov
  • 3 imajo to težavo
  • 6 ogledov
  • Zadnji odgovor od kptnfmrs

more options

This thread is apparently abandoned by the support people. https://support.mozilla.org/en-US/questions/1026282#answer-643651

so I'm starting it again with some details from the other thread...

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

on 10/16/14 started quitting on any website. no crash notice. App just quits. uninstalled on 10/17/14 and reinstalled with no add-ons from Google Play Store No change - Firefox runs as long as it is not connected to the web. Shows history - bookmark - etc. Soon as it connects on the internet it quits. Connecting via wireless network. I have uninstalled it so I can use the internet


I got this suggestion but was unable to duplicate all the steps...

Ok so I tried this finally and got it to work: this might be long but a shortened version:

   . Connect the device to the computer via usb.
   2. In android settings go to About device and double tap on build id 7 times
   3. Go back and now see the developer menu
   4. Open and enable remote debugging
   5. Open up Firefox on the android go to settings > devloper tools and check remote debugging
   6. From Desktop go to Tools > Connect
   7. Open Tools > Console
   8. Click on gear and on the far right click on "Remote debugging for this session only"
   9. [adb sdk install required] in a terminal window 

adb devices

make sure a device is listed.

   10. On desktop in the window that openned up when you opened up connect click on connect
   11. Immediately after run this in the terminal: 

adb forward tcp:6000 localfilesystem:/data/data/org.mozilla.firefox/firefox-debugger-socket

   12. On the device hit enable on the connection
   13. should be connected on the connect and click on the remote tabs.
   14 the logs will start to show up in the console.
   15. If you need adb log cat logs run in the terminal before you start to test: 

adb logcat > text.txt

   do you thing, and attach it to a bug. 


Here was my response:

I'm getting lost on #6 What "Tools" are you talking about?

I am using a laptop btw. Windows 8.1

Thanks

This is where it stopped... some fool got on that thread and was being obnoxious - so I hope we can start fresh here.

This thread is apparently abandoned by the support people. https://support.mozilla.org/en-US/questions/1026282#answer-643651 so I'm starting it again with some details from the other thread... 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 on 10/16/14 started quitting on any website. no crash notice. App just quits. uninstalled on 10/17/14 and reinstalled with no add-ons from Google Play Store No change - Firefox runs as long as it is not connected to the web. Shows history - bookmark - etc. Soon as it connects on the internet it quits. Connecting via wireless network. I have uninstalled it so I can use the internet I got this suggestion but was unable to duplicate all the steps... Ok so I tried this finally and got it to work: this might be long but a shortened version: . Connect the device to the computer via usb. 2. In android settings go to About device and double tap on build id 7 times 3. Go back and now see the developer menu 4. Open and enable remote debugging 5. Open up Firefox on the android go to settings > devloper tools and check remote debugging 6. From Desktop go to Tools > Connect 7. Open Tools > Console 8. Click on gear and on the far right click on "Remote debugging for this session only" 9. [adb sdk install required] in a terminal window adb devices make sure a device is listed. 10. On desktop in the window that openned up when you opened up connect click on connect 11. Immediately after run this in the terminal: adb forward tcp:6000 localfilesystem:/data/data/org.mozilla.firefox/firefox-debugger-socket 12. On the device hit enable on the connection 13. should be connected on the connect and click on the remote tabs. 14 the logs will start to show up in the console. 15. If you need adb log cat logs run in the terminal before you start to test: adb logcat > text.txt do you thing, and attach it to a bug. Here was my response: I'm getting lost on #6 What "Tools" are you talking about? I am using a laptop btw. Windows 8.1 Thanks This is where it stopped... some fool got on that thread and was being obnoxious - so I hope we can start fresh here.

Vsi odgovori (11)

more options

Hi, The "Tools" are in the old drop down menu, which are not shown by default in the new Firefox Design. To show this menu: Firefox Menu > Customize On the bottom left there will be Show/Hide Toolbars. The Menu will be listed here.

more options
more options

I have firefox 33.1.1. The Menu appears now. When I select Tools drop down there is no "connect" in it. Here is what shows: Downloads Add-ons Set Up Sync... Ghostery > Web Developer > Page Info Options Download Helper > Adblock Plus >

Now what?

Spremenil kptnfmrs

more options

May I request that you check to see if this still happens if you install this version of Firefox Nightly? You may need to enable installs from sources other than the play store: https://nightly.mozilla.org/

more options

As for the no connect, this needs to be enabled from the Web Developer Console. Click on the gear on the top right and scroll to the bottom on the right "enable remote debugging" should be checked.

more options

I am running Nightly, now. So far so good. Is this an alternative to Firefox? or the next generation of Firefox? ... or ???

more options

Nightly is one of the four main development channels of Firefox.

Release, Beta, Aurora and the most unstable being Nightly. Nightly gets checkins almost everyday so therefore a update each of those days.

more options

The latest release, and the Firefox Beta don't work in my Android but Nightly does work. I don't know if or why it makes a difference, but the release and the beta were downloaded from Google Play. I downloaded Nightly from Mozilla per "guigs2" instructions. I'm wondering if Firefox Release or Beta would work if I downloaded it from Mozilla. I can try it if I'm given a link. That would be very interesting if it didn't work because it was downloaded from Google, wouldn't it?

more options

Okay, then. Nightly is glitchy on my S4 and no further solutions have been offered. I'll be sticking with the stock Android browser or trying Opera or something.

more options

The other thread that the report for this was reported seems to have been resolved when they updated android to kitkat.

more options

https://support.mozilla.org/en-US/questions/1026282#answer-643651

This thread is not resolved. The last entry was on 11/14 where it was suggested that I download Nightly from Mozilla.

Nightly does not quit spontaneously like Firefox does, but it doesn't work quite right on one of the sites I go to a lot.

I don't know anything about an upgrade to Kit Kat.

Thanks