منتدى دعم ”فَيَرفُكس لأندرويد“

Hello,

Firefox 120 is freezing my Android 11 phone when I start typing on the search bar (weirdly it start to happens when a space is inserted). It freezes so hard that pretty much it takes 30-min to 1 hour for the phone to restart or the battery to drain.

Reverting to 119.1.1 solves the problem immediately.

My guess would be that maybe the search bar or the suggestion related code introduced something weird, as I do have a lot of bookmarks. Nevertheless, it's definitely a new issue (been using Firefox mobile since first day around 2010) and introduced in 120.0.

Since the phone is hard freezing, I can't even connect in ADB and try to see any message hinting at what's wrong. If there's a crash trace maybe some info could be dug there.

Thanks in advance for the help!

Firefox on my android phone times out on any webpage whenever I am not connected to a Wi-Fi. All webpages and IP addresses timeout with no response. Same issue occurs on Firefox Beta app and Firefox Nightly. All other applications work as expected with full internet access on mobile data. The same pages/addresses respond as expected on Chrome and the built-in browser.

Simply put, all Firefox apps have no internet connectivity on mobile data.

Solutions I've attempted with no success or change: Re-install Firefox. Logging out of Firefox Sync. Clear Firefox data and cache. Disabling tracking protection. Disabling HTTPS-only mode. No proxy settings are enabled. Confirmed Firefox application has mobile data network privileges. Disabling, re-enabling mobile data network privs. Installing Firefox Beta and Firefox Nightly; same issue.

Another possibly related issue: Firefox does not follow routes from a Cisco AnyConnect VPN on my phone. Opening pages/IP addresses routed through the VPN are rejected or timeout as if the VPN is not active at all. The same pages/addresses respond as expected on Chrome and the built-in browser. This occurs over Wi-Fi as well, of course nothing works on mobile data as described above.

Device: Oneplus 8T (KB2003) OS: OxygenOS 13.1 (Android 13) Firefox version: 117.0.1

After updating Firefox for Android, my phone started rebooting after downloading any file. This makes it very difficult to use the browser and I had to use Chrome temporarily. The Crashes tab in About Firefox is empty. I tried to collect a logcat and uploaded it to Google Drive (maybe this will help somehow.): https://drive.google.com/file/d/1kmdS5rTH3r0u09KLxeUDeY5U8r5xiEK1/view?usp=sharing. I hope this information is helpful in solving the problem.

Firefox crashes Android system and System UI processes after every image download.

It happens after every image download finishes.

Firefox version in screenshots.

I have no idea what is happening... But after restarting, clearing my cache, making sure I have data and it is working for other apps... Still no results.

No matter what, whether I try to type in a URL, click on a link in the google app, or refresh a page I already have open, the app doesn't even attempt to load a page or throw up an error. Just a blank background, no loading bar, no error messages, and no redirects...

FF for Android Version 112.2.0 Build #2015946691

Keep seeing a bug where tabs that were kept open but are not active, upon reopening do a full reload, and then take a long time to load often failing to load at all after a timeout.

video recording

I'm using Android 13 and Firefox is updated to the latest update. When I Google something and select an image, Firefox freezes and I either have to reload the page and the image will load or I have to close & reopen the app and switch to the Images tab. This is on the main Google search page. Images selected in the Google Images tab work as expected.

I have the problem that Firefox does not correctly recognize when I want to scroll up on a web page. This often causes me to accidentally refresh the page. Usually this should only happen when I'm already at the top of the website and then swipe down again and not in the middle of the website. I have even tried Firefox Nightly and Klar, but the issue occurs with every browser. Is there perhaps some trick or hidden setting that causes the browser to scroll reasonably again instead of constantly refreshing the website?

I'm having an issue with Firefox on Android. On certain websites (e.g., Yahoo News, Calscape.org, Google search results--with Goggle Search Fixer add-on enabled), I can scroll down the page without issue, but scrolling slowly back up toward the top of the page with downward drags of my finger is only responsive half of the time. That is, I can only scroll back up with every-other downward swipe/drag of my finger. This odd behavior does not happen with other mobile browsers (I'm on Android 13 and using a Galaxy A53 5G). Any suggestions?

Hi,

I am a regular user of the Android version but currently when I get my search results it freezes and when it doesn't none of the links are clickable. Other browsers have no issues, anything I can do?

Hello!

The problem is I'm getting the "Unexpected response from server" message when trying to open any web page. Could you try to solve this without me updating the android version? My phone is not new and quick in the terms of performance so I do not update the OC. Please find the error examples, broeser version and my phone's system info attached in a form of screenshots.

Thank you Regards, Denis

I search for "desktop" and it returns "Web pages" "page" along with desktop. None of the 81 results answer the query, "what is the desktop site?" in settings. Why? Why return random words? Why don't Boolean operators work? Please tell me the trick to searching, it's becoming a daily routine.

Android Firefox v114.1.0 (Build #2015955411), 4bddc25255+ Samsung Galaxy S9+ Android v10

Hello,

Firefox was upgraded on my Android phone to the version above yesterday, and all existing tabs or any new websites are now blank (see second image attached). No page will load, no open tabs have any content / cant reload them etc. Clearing cache for the app, hasnt worked either.

Just hoping there is a fix rather than blowing everything away and then finding out there is still an issue.