A few answers

1. anbox is very experimental still so personally I would expect more than 50% of all apps to not work (anything that uses Google services like the maps api will not work); and probably less than 10% of apps to work without major issues (for me, of around 12 apps I tried only spotify works without me noticing problems)
2. as far as I know there is no icon for anbox (it's just software that runs in the background)
3. I guess these are system apps (on a normal android they are not listed by default in the settings apps)
4. after you enabled anbox with anbox-tool it is supposed to start automatically on boot, but if I remember correctly I also had situations were some commands didn't work; only after starting an android app those were possible so I guess there is still some difference between something like "ready" and "running" or so (or maybe it's just a bug due to the experimental nature of anbox on UT)
5. Android apps rely on a back button, so running android apps on a system that doesn't have those just can't be operated fully; there may or not be workarounds like stopping the app and starting it again

There is also a 3h recording of a live porting session you might want to check out
https://www.youtube.com/watch?v=nShXVDXM50A

@dtarrant said in Let's be honest, Ubuntu Touch is bad:

In support of Android, many folk cite the availability of a plethora of apps. How many do you really need? Aren't many of them simply "shovelware"?

Of course I can give only examples relevant to me

Some apps that come to my mind

• I pay 10 EUR per month for Spotify Premium and I mostly listen to it while on my way (to work, friends, etc.); haven't found a way to do that on UT natively (Spotify is one of the few apps that works in anbox, though, but with horrible battery life)
• I pay money to use car/bike/scooter sharing apps and none of them offer a way to book a vehicle on their mobile website
• my Office 365 apps at work only work with certain trusted apps installed

These are kind of show stoppers for me.

So personally I can very well understand where ollehell comes from. For me UT is unusable as a daily driver. And probably will be forever, I don't know. Still I like and support the idea that people have a choice. And I met some in person who are happy using UT. So I contribute a little (working on docs, the installer and providing a manual installation alternative), but admittedly with focus on the Fairphone 2 which ultimately is what drives me.

@domubpkm said in Volla phone might be (or not) a new UT phone in 2020:

But what could encourage us to go more to this phone than another and invest in this campaign?

Well, it would add one more new device to the list of supported devices that are not old and can be bought regularly. Which would increase the number of available new UT phones to choose from by 100% or 50% (depends on when Pinephone and Librem 5 are available).

That's strange...

The curly braces enclose optional parts, i.e. /{,var/}run/aethercast/dhclient*.leases lrw, means /var/run/aethercast/dhclient*.leases lrw, and /run/aethercast/dhclient*.leases lrw,

The curly braces ({}) make this rule apply to the path both with and without the content enclosed by the braces.
https://www.novell.com/documentation/apparmor/apparmor201_sp10_admin/data/bx5bmkc.html

P.S.: because I'm usually on the dev channel and update rather frequently, I wrote a script to re-apply the change after each update: https://gist.github.com/Ingo-FP-Angel/905c5655511435b0ded2eb354dab538b

In the doc it says adb uninstall [APP_ID] to uninstall an Android App but it doesn't explain what [APP_ID] is.
http://docs.ubports.com/en/latest/userguide/dailyuse/anbox.html#how-to-uninstall-apps

[APP_ID] is not the name of the APK so that won't work. There are different ways to find out this ID, e.g. for Whatsapp: if you look at the app in the play store with your browser, the ID is part of the URL
https://play.google.com/store/apps/details?id=com.whatsapp

com.whatsapp in this case is the [APP_ID] , therefore it would be

adb uninstall com.whatsapp

@Flohack said in Do I need to root my Fairphone 2 to install Ubuntu Touch?:

you need to unlock the bootloader if it is still locked

The FP2 bootloader is always unlocked AFAIK. Sure, it does no harm to unlock it, but it isn't necessary.

I've done it recently. Let's assume you want to install Spotify and the APK is called "com.spotify.music.apk".

Then, on your PC in a terminal in the same folder where the APK is located

adb root
adb push com.spotify.music.apk /home/phablet/anbox-data/data
adb shell
sudo lxc-console -ndefault -P /home/phablet/anbox-data/containers -t0
cd data
pm install com.spotify.music.apk

Then, on the phone, refresh the app scope and it should be there.

Ah yeah, I just remembered it wrong, it was too long ago I tried out UT

Edit: the first post mentions to edit /etc/ubuntu-touch-session.d but it should be /etc/ubuntu-touch-session.d/android.conf

It actually did contain the line with "handset", so I just added the other two. I assume it needs a reboot for it to take effect?
Edit: yeah, after the changes and a reboot the pull down menu looks fine

Yet another edit: of the things marked as "not tested" I tried SMS in/out and they are working

When long-pressing the power button to see the shutdown menu, the entry "restart" only restarts unity8 (I had assumed it'd do a full reboot; which is possible via sudo reboot over ssh).

And in order to try out mobile data I temporarily disabled WiFi. After enabling it again, the phone did not reconnect, even if my WiFi was still in the list of known networks and also seemed to have stored the correct PSK. Only forgetting it and connecting again with PSK worked.

About my findings which files are flashed etc.: that other thread strictly will just work for the FP2!
The installer queries some files depending on the selected device and will do more/less/other things for other devices. One carefully needs to look at the configs before trying anything too bold

@prog-amateur said in Is our phone phoning home to Google?:

Another question, do you know what is the 10.15.19.82 address ? I have tried to reach it in a browser to find the owner without success.

I don't have a UT phone at the moment, but the very same IP address exists in the list of known hosts I have connected to via ssh. That info plus 10.xx.xx.xx being a private network address (see https://en.wikipedia.org/wiki/Private_network) makes me think it is the default (kind of internal) address of a UT phone.

And now that I typed it... that IP is mentioned in the GSI porting notes at https://github.com/ubports/porting-notes/wiki/Generic-system-image-(GSI)

The download URL in the first post is definitely outdated.

Edit: taking the archive from https://github.com/WeAreFairphone/modem_zip_generator/releases/tag/19.11.2 contains the corresponding images. The naming is slightly different as the image files are called like the partion they're supposed to be flashed to.

Found something about the core module: https://forum.fairphone.com/t/speaker-module-from-fp3/64728

At the moment the Fairphone Forum is down for maintenance, though.

@Luksus said in Fairphone 3 (FP3):

@Ingo I can't find any information about core-module differences

I'm not aware of any written information about it, either. They ran two Q&A live video sessions (IIRC on youtube and facebook). It must be somewhere in those streams.

About downgrading: the new modules are not supported with Android 9. Several people learned that the hard way when they installed the /e/ version for FP3 based on Android 9 on their FP3+.

@Luksus said in Fairphone 3 (FP3):

It's just an updated camera module in it, no?

It's also a new audio module. And IIRC from the live event Q&A session of the FP3+ launch there's probably also "some" change in the core module (because they said upgrading the audio module wouldn't have an effect on the FP3).

But then, the hardware related changes should be in the vendor partition. So if I understood the concept of GSI correctly, the GSI system is supposed to work.

Ah yeah, I just remembered it wrong, it was too long ago I tried out UT

Edit: the first post mentions to edit /etc/ubuntu-touch-session.d but it should be /etc/ubuntu-touch-session.d/android.conf

It actually did contain the line with "handset", so I just added the other two. I assume it needs a reboot for it to take effect?
Edit: yeah, after the changes and a reboot the pull down menu looks fine

Yet another edit: of the things marked as "not tested" I tried SMS in/out and they are working

When long-pressing the power button to see the shutdown menu, the entry "restart" only restarts unity8 (I had assumed it'd do a full reboot; which is possible via sudo reboot over ssh).

And in order to try out mobile data I temporarily disabled WiFi. After enabling it again, the phone did not reconnect, even if my WiFi was still in the list of known networks and also seemed to have stored the correct PSK. Only forgetting it and connecting again with PSK worked.

@Luksus said in Fairphone 3 (FP3):

Make the system writable

How do I do that? I tried sudo mount -o rw / which gave
mount: unknown filesystem type 'rootfs'

I wasn't asked to set up a screen lock password after initial start and now the phone asks for it to unlock after suspend. Tried 0000 and leaving the password blank, but that didn't work.
What is the default password?

Edit: ok, now I guessed it: "phablet"

Edit2: didn't test much so far, but swiping down the notifications etc. from the top only works on the right two-thirds of the screen (and the left third of the screen still shows the active app).

Edit3: seems like bluetooth isn't working (doesn't see any device; BT on/off from settings aps and quick settings pull down menu are not in sync) and with developer options enabled I don't see the phone with adb devices (ssh phablet@10.15.19.82 works)

That sounds great! I might be able to try it out this weekend

It's definitely not necessary to root the FP2 before flashing UT.
And the bootloader of the FP2 is unlocked by default, so no need to unlock it.

What's definitely needed is to enable USB debugging.