Fairphone 2 (FP2)

flohack

@Fla I was thinking about Telegram private message but here is ok also ^^ You need to find /usr/share/powerd/device_configs/config-default.xml - there are values inside how the brightness is being scaled. You probably need to change the curve points there. Give me a reply if you know what to do ^^

flohack

Sorry its probably /usr/share/repowerd/device-configs/config-FP2.xml

Fla

I don't have any config-FP2.xml file there, maybe @peat_psuwit didn't add one in this new port at the moment?

Here are the files I have: config-default.xml config-flo.xml config-grouper.xml config-hammerhead.xml config-maguro.xml config-mako.xml config-manta.xml.

In config-default.xml, the minimum brightness is set to 10, and config_automatic_brightness_available is set to false. Can I change those value? The filesystem is said to be read only...

Luksus

@Fla you can mount the root fs writable sudo mount -o remount,rw / and then edit the config-default.xml file and save it under config-FP2.xml.

After that you need to reboot (perhaps a unity8 restart is sufficient).

I successfully set the minimal brightness to 1 and the display gets much darker.
For the auto brightnessyou need to write some kind of config table, perhaps you could copy it out of another config file....

flohack

@Fla does not sound if the file hjas been overriden properly, @peat_psuwit did you enable the repowerd confi already to be copied? auto brightness must be true otherwise

Fla

@Luksus it works, thank you very much!

hoogs

Hello everybody!

I've been using this port as a daily driver for a couple of weeks, after switching from a Nexus 5 with stable, and everything has honestly been working great so far!

I even got my bluetooth headset to work, so I've been thinking of testing Spotify out in Anbox. Has anybody here experimented with getting Anbox to work on this port? Do I have to use a patched kernel, for example?

Fla

@hoogs I used Anbox with the 5.1 port which has the patched kernel, but I never did it with that port so I can't tell. However if your goal is to use spotify, then open.spotify.com should be enough, isn't it? I could even be packaged as a webapp. There is also CloudMusic in the OpenStore but I never used it.

rom4nb

Dear community,

I own a FP2 but a year ago I sadly gave up to use ubuntu Touch as a daily driver because I had too many Unity8/Lomiri crashes in daily use and then messages I was typing disappeared, crashes during browsing happened etc.

I considered give it a new try after OTA-12 with finally the new Mir/Lomiri update coming to stable - maybe it works more reliable then for me.

I have been out of Ubuntu Touch for quite some time and wonder now whether you would recommend to use the "normal" image distributed by Ubports installer (I suppose it still includes Halium 5.1?) or this new Halium 7.1? What is faster, what is more stable? I learnt now that flash on new camera module will never work with Halium 5.1 but at Halium 7.1 there is finally a chance at least ... Anbox (which I have never used in my "Ubuntu Touch times", but for DB Navigator it would really be worth a try because for me, who has no car and who uses a lot public transport, mobile tickets make life so much easier ...) does not work with Halium 7.1 as far as I understand the above comments? But I'm not sure whether Anbox is still good enough at all to use it "seriously" on a daily driver apart from development work and testing.

In recent Q&A, there was also talked about Halium 9, but there is no discussion for our FP2 to push it to Halium 9? (LineageOS has had Android 9 for quite some time for the FP2 I think ...)
Is it a decision of Uports to change the "default" Halium in the Ubports images images or is it an separated decision of Halium project?

Thank you for your counsel, rom4nb

flohack

@rom4nb said in Fairphone 2 (FP2):

udes Halium 5.1?) or this new Halium 7.1? What is faster, what is more stable? I learnt now that flash on new camera module will never work with Halium 5.1 but at

When its ready, definitely change to the Halium 7.1 based build. The same goes for N5 and OPO, as soon as the builds are there, we will switch them over in the installer, so we kinda force everyone to use it. Its so much better in all aspects

rom4nb

@Flohack
Hi Flohack. Thank you for the answer. What is still missing for the Halium 7.1 to become "default" for FP2, OPO and N5? Should I better wait some longer time longer for OTA 13, until Halium 7.1 is ready or is it still not foreseeable when this will happen?

flohack

@rom4nb we dont know when it will happen, but we will announce it some time ahead, and you will not able to miss it

Luksus

Just another issue documentation:

When the phone is fully charged, but still connected to the power-chord and WiFi is enabled (connected to a 5Ghz WiFi), it reboots itself frequent.
Sometimes every 10 minutes.

And another one:

When I want to switch between cellular data and WiFi, I mostly need to turn off the one that I don't want to use, otherwise I get no internet connection.
Example: I am on cellular, turn on WiFi, the indicator indicates that it uses WiFi, but it has no internet connection, I turn off cellular data -> WiFi works.

Fla

@rom4nb hi! I used the halium 5.1 port until last march and it is pretty stable. The only advantage to use the 7.1 port at the moment is a better camera (quicker to launch and with flash). So if taking pictures isn't something you do a lot, I would advise you to install the 5.1 port using the installer. And yes, it is way more stable now than one year ago, you should definitely give it another try.

About Anbox, the kernel supporting it is now included in the build for the FP2 so you should be able to try it easily, but no, it should not be considered a stable solution. Especially, Android applications run that way are very slow and can't access hardware like bluetooth.

Welcome back to the Ubuntu Touch world, it's a nice place and is improving daily, you won't regret your return

Fla

@Luksus hm, I never encountered those bug, I probably never was in the case to reproduce the first one but I definitely was in the situation of the second one and didn't remember such problems. I guess that now that OTA-12 is officially released, @peat_psuwit will work again on that port?

At the moment I still use the image you provided me with so it is almost two months old. Did you build another image on your phone? Would that difference explain why you have those bugs and not me?

Emphrath

@Fla "about Anbox, the kernel supporting it is now included in the build for the FP2 so you should be able to try it easily" Is it really ? that would mean i just have to download the installer and no image to flash ? Last time i did that it broke my system beyond repair.

Luksus

@Fla hm perhaps the issues are unique to my phone, wifi module and/or battery.

No, I did not built another image yet. But this is also not necessary, when there are no changes in halium for FP2.
So you just can take the "old" halium and system build and flash it together with the latest ubports build.

Fla

@Emphrath it is yes, since february in devel I guess. And now in stable with OTA-12.

Fla

So you just can take the "old" halium and system build and flash it together with the latest ubports build.

@Luksus sorry I'm not sure I get what you mean, you mean that I can go back to last devel code with the installer and keep my Halium 7.1 base now that I flashed it? All the layers of Ubuntu Touch aren't clear to me, if you have some documentation to read it would be great.

Luksus

@Fla When you flashed your phone with the Halium 7.1 version, you took the images I provided to you and you also needed to download the current rootfs (dev) build from the CI-Server.
So you just can download the new rootfs build and flash your phone again with that command:

path/to/halium-install -p ut path/to/rootfs.tar.gz path/to/system.img

(Perhaps there is a way to flash the rootfs only? Hm, perhaps it is possible to flash the phone with the ubports-installer without flashing the boot-partition and the system-image, I don't know.)

After doing that, you need to make changes, which you did to the rootfs, again. For Example the droid-cam patch.