Fairphone 2 (FP2)

Fla

@Emphrath hm I think it's a different problem, isn't it? What I'm experiencing is, the pictures are fine in the phone, it's once displayed on the pc that they are rotated.

Emphrath

@Fla OK yeah it's sth else

Fla

Continuing my experience as a daily driver, I found two other regressions:

The minimal brightness cannot be set as low as it can be on the halium 5 port. As someone who's always using the lowest level of brightness, this impact both my eyes and the power consumption
When recording a video, the automatic lock of the screen isn't disabled anymore. So after 1 min of video, the screen switches off and the video is cut.

Fla

It also looks like battery is dying more quickly when data connection is on with that port.

Fla

Another regression: when you plug the phone and it is switched off, the battery indicator on the screen is missing. There is only a very small text with the battery percentage.

flohack

@Fla yes thats an easy fix, it needs the custom charger animation feature activated. I might make a PR for that ^^

Fla

@peat_psuwit I don't know if you're still working on that port but the regression which annoys me the most is inability to set the brightness as low as it is possible with the 5.1 port. Like everyone else I'm now spending all my time inside and my eyes are more tired every day, so I would really to be able to set the brightness of the screen to a lower level.

flohack

@Fla there is a config file where you can try out the best values and then send it to us to integrate. Ping me tomorrow on Telegram ,I can show you how to do

Fla

@Flohack maybe you can post the How-to here? Or in which channel do you want to be pinged?

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?