@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+T3s|4
+dr|z3d
+eche|off
+hagen
+hk
+lance074
+postman
+qend-irc2p
+snex
+weko
+wodencafe
Arch
BubbRubb
ContestI2PTeam
Daddy_1
Danny
DeltaOreo
FreeB
FreefallHeavens
Irc2PGuest82088
Irc2PGuest85022
Irc2PGuest85406
Irc2PGuest86602
Irc2PGuest87189
Onn4l7h
Onn4|7h
R4SAS_
Sleepy
SlippyJoe
Stormycloud
aargh
acetone_
anonymousmaybe
ardu
b3t4f4c3___
b4dab00m
bak83
cumlord
death
dr4wd3
eyedeekay_bnc
f00b4r
idontpee
mareki2p_
nnm_
not_bob_afk
ohThuku1
orignal_
poriori_
profetikla
r00tobo_BNC
rapidash
rascal
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
wew
x74a6
eyedeekay
User reports from Matrix are suggesting that the /data/data/ vs /data/user/0/ issue is happening on some devices that use the freestanding `.apk` builds and Android 11.
eyedeekay
I'm not quite sure why, it doesn't seem to be happening to any of my devices when using the `.apk` builds, including after factory reset, but logs are logs
eyedeekay
As such I'll be uploading 1.7.1 releases of the `.apk` builds tonight/this morning. It contains the same fix as the one which was required on all `.aab` builds.