Hacker News new | ask | show | jobs
by leloctai 964 days ago
Which is a horrible design on Android. Firefox on my (admittedly relatively old) phone take 20s to load the first page when browser start with uBlock enabled. On desktop this is fine as it only happen once a day. But on the phone it happen a lot since apps getting killed is a normal thing.
6 comments

I have the same issue with UBlock Origin since my phone is quite aggressive when killing apps. While it is indeed annoying, I don't think it's a bad design.

Maybe it's lacking a setting to toggle this (Suspend all network until lists are loaded doesn't control this behavior), but I wouldn't want to load pages full of ads on mobile simply because the app got killed.

The real issue for me is my phone killing applications when it has both battery and memory available.

Chrome desktop since v110 has started killing background tabs and reloading them upon use. [1]

Lately, I've noticed Chrome being really aggressive about this.

[1]: https://arstechnica.com/gadgets/2023/02/chrome-110-will-auto...

I'm on the regular stable Chrome build and was explicitly asked on several devices over the last few months if I wanted to enable memory saver or not, it wasn't automatic for me at least.
My 4 year old S10E does not exhibit this behavior at all (Firefox with uBlock).
S10e was the peak of mobile design.
Any phone without an IR Blaster can not be the peak of mobile design. Note 4 master mobile.
I feel the same about my s7 edge I keep as a spare, although currently using the s21 ultra and no complaints
S22, I had to find a way to exclude Firefox from memory management altogether, because the auto-killing behavior was getting ridiculous. Unfortunately, there is still no way to prevent Firefox itself from unloading tabs.

I know I'm in the minority, but I consider both of these behaviors to be a very bad and extremely frustrating idea.

Preach! I'm holding onto it for dear life, perfect form factor, no BS.
I could've done without the useless Samsung button that doesn't do anything but whine for a Samsung account before you can change the behavior of the button. So I used adb to disable the button entirely, to prevent the whiny Samsung page from accidentally being pressed on the button raised off the left side of the s10e.
Why was it that?
Small form factor, powerful enough to keep working fine today (as long as not gaming), has DeX, has audio jack, physical fingerprint reader sideways, and samsung support (no glitches for important apps)

But it has some pretty big downsides, the battery is small, and it is rather bad at this point of life. The audiojack has been oversized by constant use and barely holds now the headphone, stuck in Android 12.

And my 7 years old oneplus 3T neither
Do you mind sharing your ubo settings?
Just the default one plus french list in regional settings. To be fair though, I had a tablet from the same time but it was way cheaper than this phone, specifically having way less ram and firefox was not really usable.
Do you mind sharing your ubo settings?
Whatever the defaults are after installation, I didn't adjust the settings at all.
I don't get this behaviour on Firefox in Android at all.
Do you mind sharing your ubo settings?
I didn't change anything - just the default settings. Phone is a pixel 6a.
IIRC there's a setting for that in UBo (look for pre-fetching)
I could be wrong, but I’m pretty sure that’s a different thing altogether.

Edit:

Yeah, disabling prefetch:

> This will ensure no TCP connection is opened at all for blocked requests: It's for your own protection privacy-wise.

uBlock holds itself (ideally) to a higher standard than not executing js or hiding an element, it tries to prevent the network connections from even taking place. This is for browser prefetching that happens on many pages even after the environment and extensions are fully loaded, in many different contexts, to speed up requests by having the binary payload of the response already available in cache before it is needed.

I'm already allowing prefetching
i'm pretty sure there's an setting/option to disable battery optimization for firefox
In fact there are multiple switches you have to turn, however I've made sure to check all of them.