Customized 'hosts' destroyed randomly

Bug Reports
#1

REPRODUCIBILITY (% or how often): random
BUILD ID: 3.3.0.16 without encryption
HARDWARE (Jolla1, Tablet, XA2,…): Xperia X
UI LANGUAGE: FR
REGRESSION: (compared to previous public release: Yes, No, ?): Yes

DESCRIPTION:

From time to time, my customized ‘hosts’ file (about 10,000 entries) is replaced by its default short, minimal version.

PRECONDITIONS:

Customize ‘hosts’ with Defender (MVPS) plus custom hosts.editable

STEPS TO REPRODUCE:

  1. Customize as above
  2. Reboot several times
  3. Check ‘hosts’

EXPECTED RESULT:

Customized ‘hosts’ kept as intended

ACTUAL RESULT:

Customized ‘hosts’ destroyed and replaced with minimal version

ADDITIONAL INFORMATION:

hosts.editable and/or customized ‘hosts’ available on request.
This issue didn’t happen (yet) on my old Jolla phone.

#2

My edited (by hand) host file has been unchanged for 3 months, even after restarting.

You use defender? Defender has been acting very strange since SFOS 3.3 (??). You shouldn’t be using it with an xperia xa2. For me with the xa2, defender can no longer generate a new host file. The process runs in an endless loop. Strangely, it works like expected on my old J1.

Have a look here too :

https://together.jolla.com/question/225689/xa2-stuck-in-sony-logo-white-led-e2fsck-says-bad-magic-number/

#3

As mentioned above, my device is not an XA2 but an X (unencrypted). Defender appears to behave normally.

#4

For unencrypted devices Defender should work normal.
This boot blocker only came up for the 10 (encryption always enforced) or now XA2 devices after flashing 3.3 image or manually activating encryption.

But back to topic (how it matches now this wording on discourse ;)):
it seems I can confirm this behaviour on a XA2 unencrypted with SFOS 3.2.1.20.
It may be so lor longer times already. As I checked my hosts file, saw it in minimal and then let Defender update (which it does weekly on its own). So a reset of that file may have occured earlier unnoticed.

#5

@Objectifnul : Oh, sorry for that. I didn’t read correctly.

#6

Just found this third-party bug report by accident again.
And can tell you that this annoying thing is fixed in latest harbour-defender-II :slight_smile:

It was in there from the beginning: if there was no connectivity on scheduled (weekly) update time the host file got reset.
Now it stays as is.

1 Like