this post was submitted on 03 Sep 2025
37 points (100.0% liked)

Android

31751 readers
504 users here now

DROID DOES

Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules


1. All posts must be relevant to Android devices/operating system.


2. Posts cannot be illegal or NSFW material.


3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.


4. Non-whitelisted bots will be banned.


5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.


6. Memes are not allowed to be posts, but are allowed in the comments.


7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.


8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.


Community Resources:


We are Android girls*,

In our Lemmy.world.

The back is plastic,

It's fantastic.

*Well, not just girls: people of all gender identities are welcomed here.


Our Partner Communities:

!android@lemmy.ml


founded 2 years ago
MODERATORS
 

Has anyone experienced this? Using my mom's comcast wifi when I navigate to a new site the navigation takes a very long time, like a full minute. Once it eventually completes, I can click around inside the site at normal speed. This only happens with Firefox (I tried installing the Duckduckgo browser and it doesn't have the problem). It only happens on the comcast wifi (switching to mobile internet makes it go away). Using my laptop on the same wifi network has no problem. The issue on Android only started with the last update on F-droid. The only extension installed is ublock origin.

I can make some useless guesses at what might be happening (DNS queries getting hung somehow) but haven't made any attempt to check them with network sniffing.

Has anyone else experienced this?

you are viewing a single comment's thread
view the rest of the comments
[–] LiveLM@lemmy.zip 4 points 4 days ago* (last edited 4 days ago)

On the latest F-droid blog post they listed this as a known issue:

Fennec F-Droid was updated to 142.0.0 and got a lot of publicity, and not for how great it works, unfortunately. It appears the slow spell hit it too as there’s an issue using extensions that use webRequest listeners, like uBlock Origin, Privacy Badger, Ghostery, TamperMonkey and more, that delay the connections to websites on start. For now we recommend to try a couple of things. While disabling these extensions fixes it, we know that the Internet is unusable without ad blocking.

  • First trick is to disable the extension, wait, hear me out, just toggle it OFF then ON back again. (Small note here: while there are many ads related extensions out there, maybe it’s time to look at their usage a bit more and decide to keep only one. We’ve seen users installing them all thinking this will cover all angles, while the truth is they are messing with each others rules and you might end up more exposed than less.)
  • Second, the issue is seen when swiping the app away (where the app status is decided by Android, Schrödinger’s app paradox), but some users reported success if instead of swiping it you actually close it. The Close button appears in the main menu if you enable “Delete browsing data on quit” in Settings. eg. “Cached images and Files” is the least annoying option to select, careful not to select any of the others. So, when you want to close the app, just use the button and on the next start it should load pages normally.
  • Third, our own @linsui pointed that, we can just close the screen. [...] When you open the app, if you see it stand there doing nothing, lock the device and then unlock it. We don’t understand why this works for some, but surely it has to do with libraries and drivers and magic numbers.

As a reminder, there’s a reason why our fork of Firefox is named Fennec, it’s not about some code name anymore, but about the fact that our version is a work on top of Mozilla’s code. We need to extract all the bad (read non-FOSS, read privacy invading) code and give you a clean app that serves you and not some faceless corporation. Are we breaking some eggs to do this omelette? We sure are. And we do our best to serve it fast and tasty. Yet sometimes egg shells might end up in the final product.--