Fairphone 2 (FP2)

[Fla]

Okay so I found a proof (if needed) that I'm indeed running with the new Halium 7.1 base: the famous bug of toggling data after flight mode is gone! And that is great.

However, I found some regressions:

• The auto-brightness option isn't available anymore. Is the proximity sensor available?
• The phone can't be updated anymore (no release channel available). I guess that is expected as far as this build isn't available on the official servers?

I will continue to test and wrote my findings here.

[Fla]

Continuing my report, I installed GStream-droid (see that topic) and indeed, the camera app is now quicker to boot and the flashlight is working when taking a picture! Not alone though but that means it can be done and that is awesome.

It looks like there is an orientation problem however, the pictures aren't in the good orientation. I don't know if that's because of halium or GStream-droid.

[Fla]

It looks like the automatic connection to the pc isn't working anymore: it isn't seen as an USB stick as it was when I plug it.

[Luksus]

@Fla That's the already known MPT issue: https://forums.ubports.com/post/28068
You can connect over ssh though, with ssh phablet@10.15.19.82, when connected by usb-cable.

[Emphrath]

@Fla Concerning the camera rotation, it's a problem that was encountered by the first batch of Fairphone OpenOS (android) - and as far as I know people had to turn to the Opencamera app to "reverse" the problem. Actually I don't think it's been fixed. To me it seems that AOSP drivers for the camera can't to the job. On another hand, the flash worked and camera app was way faster so here you go: that patch gets you the good and bad stuff you have with Fairphone OpenOS; maybe check open camera app and see what makes it work

[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!