Sad to see the Updater app still creates a storage/emulated/0/updater on top of the already existing /storage/emulated/0/ (the absolute path being /storage/emulated/0/storage/emulated/0/updater/)
Updated without problem.
Did see a glitch in the lockscreen when drawing my pattern: the screen was split in multiple squares that were all flickering randomly as I was moving my finger. Did it twice and then went back to normal
After a very quick scan of the updater source code, I didn’t find any reference to that path… But I can see the same behavior on my device…
So now I have tried deleting the folder and as soon as I have opened the Updater app, the folder was recreated.
Also a funny thing is, that the are creating storage/emulated/0/updater/ AND updater/ in the internal storage
Debugging the updater is hard because it’s install as a system app that not even TitaniumBackup can uninstall apparently
Okay, I finally uninstalled the updater with (in the phone shell): mv /system/priv-app/FairphoneUpdater/FairphoneUpdater.apk /system/priv-app/FairphoneUpdater/FairphoneUpdater.apk.bak; sync; reboot
I think I found something… The line final File externalStoragePublicDirectory = Environment.getExternalStoragePublicDirectory(Environment.getExternalStorageDirectory() + resources.getString(R.string.updaterFolder)); gets the path /storage/emulated/0/storage/emulated/0/updater…
I think the programmer didn’t quite understand the method getExternalStoragePublicDirectory (see here for documentation about that method), basically you give it a constant pre-defined like Environment.DIRECTORY_PICTURES and not your own string…
So apparently I fixed it (at least that folder doesn’t get created but I am not 100% the OTA is still working…^^) (btw why am I fixing bugs for Fairphone in my freetime? )
I thought the problem would be something similar, but didn’t have the spare time (nor I was in the mood, honestly) to dive into the Java (ugh) code myself. Thank you so much!
Hope they fix it in the next release, now that they have your contribution,
PD: you could had change the package signature in build.gradle to avoid the need of uninstalling the original one,
At some point during the EFCT16 I also ran into this. I wrote a post on authorising from within TWRP - though this will likely only work if the phone isn’t encrypted. It could be that if your device is encrypted that the file with the authorisation signatures isn’t readable when in TWRP, causing no authorisations to be available. Sorry if seems a stupid explanation - I’m not that aware of how this whole Android thing is designed to work.
Just changing the package id didn’t work, the app just crashed on startup… And my custom built Updater (also without changes) also doesn’t work because it fails with some error message, that /cache/fp_update_.zip is not found. Maybe that happens because the app is installed as a normal user app instead of a system-privileged app (dunno how to actually properly develop system-privileged apps on Android…)
Hi there everybody,
maybe I found a bug today concerning Truephone.
Since 3 days I am running FOS 16.09.0 installed by the Fairphone updater without any special configuration, rooted. But I got Truephone installed since months. With previous FOS-versions I used truephone and the build-in phone app simultaneously as I still did until today. Today I reused the “left desktop” with “letzter Kontakt” and “am häufigsten kontaktiert” since a long time. I can’t call any of the contacts there with both sim. When trying to call after choosing one of my two sim it says “Anruf nicht verbunden”. Same result when using “Kontakte”.
Anybody else with the same problem?
Do I have to uninstall truephone?
When the choose SIM dialogue comes up, try waiting a little longer before choosing a SIM card. Five seconds should do it, though I recall someone mentioning they had to wait a little longer. See also the topic over here or Fairphone support’s software issue report.
)