@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.

@peat_psuwit said in Fairphone 2 (FP2):

The biggest issue currently is that the phone tends to reboot itself when trying to power it off. The issue has been traced to be related to the Android container

That happened on stock ROM as well. IIRC it was fixed at some point. Until then, the workaround was to enable the torch before shutting down (no kidding!).

That question came up in the FP2 UBports Telegram group the other day. Someone is working on it and will post here in the forum at some point.

I did try myself some time ago but couldn't manage. There still might be useful information at https://forum.fairphone.com/t/ubuntu-touch-gsi-for-the-fairphone-3/61569?u=ingo

I remember that someone was working on support for the FP3 but all information was in the Halium Telegram group.
Does anyone know if things are still going on (I left Telegram for good and don't intend to return)?

@Luna said in Trying to use the UBports Installer on a Debian system with an OnePlus One: Failed to start adb server:

In effect, you have to install adb and fastboot

Is that true? The installer comes with bundled adb and fastboot (can be seen in the output).

Edit: of course it can be helpful to have access to those tools outside the installer, too.

I'm not familiar enough with snap to help (it does say "operation not permitted").
But alternatively, you could try to use the deb or AppImage packages instead.
Personally I always found the AppImage most convenient (I'm on opensuse linux).

I don't have a Nexus myself, but the Wifi problem with anbox is known: https://forums.ubports.com/topic/3324/nexus-5-wifi-problems-with-anbox/7

Maybe you can post to that topic, too, so it gets more attention.

@C0n57an71n said in Is this chart ok?:

Ja, but how come so little attention in supporting UT financially is given?

Without having checked what kind of topics actually are in the Marketing category, but how come you draw this conclusion from just the chart? I don't see any financial aspects in those numbers. I'd expect the Marketing category to have discussions about spreading the word about UT and to get more people to install/use it. (I could be wrong, though, as I can't remember reading something there; I typically just look at the unread topics and their titles, not necessary which category they were posted in).

It's the number of posts per category, right?

Wouldn't say I see something unusual. For forums like this I'd assume the biggest part is about people trying to get help, so no wonder the Support catagory has the most postings.

It will not work with TWRP as recovery, the installation process requires the UT recovery.

@Kyrylo Quite some time ago I did some reverse engineering of the installer for my FP2: https://forum.fairphone.com/t/state-of-the-ubports-installer-or-command-line/47035/23

But that was by observing a successful run on my computer and then looking at the logs.
I don't remember too well but looking at the JSON configs the installer downloads (and partly at the source code) I'm pretty sure that the individual steps are likely a little different depending on the device. Meaning that if you follow my steps for the FP2 with a different device I wouldn't guarantee it will work.

Edit: I almost forgot: there was a larger rewrite of the installer later, so I guess the steps are probably still the same but config files format and resource URLs probably have changed in the last ~1.5 years.