Hi, first of all, thanks for the great work and showing that an alternative OS works on the FP2.
On the weekend I installed your lineageos version on my FP2 expecting some troubles, but against my expectations I didnāt run into much troubles.
The installation process was straight forward and worked very well.
Iām very happy now, to have a nearly actual android based system on my FP2, what is providing more flexiblity according to managing app restrictions and providing more time using my FP2 until it needs to be connected to a charger again.
Two things are NOT working for me until now:
Using apps like ControlDNLA or DroidUPNP (or naim app to manage a naim device like muso) to control a UPNP device does not work. From my point of view there is no UPNP support implemented/activated at all?!
When charging my FP2 there is no LED indication at all. Possibly I didnāt find the necessary configuration yet. (The LED works pretty well e.g. as notification for a new email or an alarm.)
Something broke my cameraā¦ I last used it on Saturday where it workedā¦ (btw reboot doesnāt help)
05-30 08:23:25.131 303 3047 D QCamera2HWI: [KPI Perf] int qcamera::QCamera2HardwareInterface::openCamera(hw_device_t**): E PROFILE_OPEN_CAMERA camera id 0
05-30 08:23:25.131 303 3047 E mm-camera-intf: mm_camera_open: dev name = /dev/video1, cam_idx = 1
05-30 08:23:25.132 307 307 E mm-camera: server_process_bind_hal_ds:112: Error in bind socket_fd=11 Address already in use
05-30 08:23:25.132 307 307 E mm-camera: main: New session [1] creation failed with error
05-30 08:23:25.132 303 3047 E mm-camera-intf: mm_camera_open: opened, break out while loop
05-30 08:23:25.132 303 3047 E mm-camera-intf: mm_camera_open: cannot open control fd of '/dev/video1' (Bad address)
05-30 08:23:25.132 303 3047 E mm-camera-intf: camera_open: mm_camera_open err = -1
05-30 08:23:25.132 303 3047 E QCamera2HWI: camera_open failed.
05-30 08:23:25.135 303 3047 E CameraFlashlight: Could not open camera 0: -19
05-30 08:23:25.135 303 3047 E CameraClient: initialize: Camera 0: unable to initialize device: No such device (-19)
05-30 08:23:25.135 303 3047 E CameraService: connectHelper: Could not initialize client from HAL module.
05-30 08:23:25.137 3266 3266 E CarrierConfigLoader: Cannot save config with null packageName or iccid.
05-30 08:23:25.147 303 3047 E CameraService: initializeShimMetadata: Error initializing shim metadata: Status(-8): '10: connectHelper:946: Failed to initialize camera "0": No such device (-19)'
05-30 08:23:25.161 303 2388 E CameraService: getCameraPriorityFromProcState: Received invalid process state -1 from ActivityManagerService!
05-30 08:23:25.215 303 2388 D QCamera2HWI: [KPI Perf] int qcamera::QCamera2HardwareInterface::openCamera(hw_device_t**): E PROFILE_OPEN_CAMERA camera id 0
05-30 08:23:25.215 303 2388 E mm-camera-intf: mm_camera_open: dev name = /dev/video1, cam_idx = 1
05-30 08:23:25.215 307 307 E mm-camera: server_process_bind_hal_ds:112: Error in bind socket_fd=11 Address already in use
05-30 08:23:25.215 307 307 E mm-camera: main: New session [1] creation failed with error
05-30 08:23:25.216 303 2388 E mm-camera-intf: mm_camera_open: opened, break out while loop
05-30 08:23:25.216 303 2388 E mm-camera-intf: mm_camera_open: cannot open control fd of '/dev/video1' (Bad address)
05-30 08:23:25.216 303 2388 E mm-camera-intf: camera_open: mm_camera_open err = -1
05-30 08:23:25.216 303 2388 E QCamera2HWI: camera_open failed.
05-30 08:23:25.216 303 2388 E CameraFlashlight: Could not open camera 0: -19
05-30 08:23:25.216 303 2388 E CameraClient: initialize: Camera 0: unable to initialize device: No such device (-19)
05-30 08:23:25.216 303 2388 E CameraService: connectHelper: Could not initialize client from HAL module.
05-30 08:23:25.222 303 2388 E CameraService: initializeShimMetadata: Error initializing shim metadata: Status(-8): '10: connectHelper:946: Failed to initialize camera "0": No such device (-19)'
05-30 08:23:25.222 5310 5310 E CAM_Util: exception trying to get camera characteristics
05-30 08:23:25.279 303 5422 E CameraService: connectLegacy: Camera HAL module version 100 too old for connectLegacy!
05-30 08:23:25.360 303 5423 D QCamera2HWI: [KPI Perf] int qcamera::QCamera2HardwareInterface::openCamera(hw_device_t**): E PROFILE_OPEN_CAMERA camera id 0
05-30 08:23:25.360 303 5423 E mm-camera-intf: mm_camera_open: dev name = /dev/video1, cam_idx = 1
05-30 08:23:25.361 307 307 E mm-camera: server_process_bind_hal_ds:112: Error in bind socket_fd=11 Address already in use
05-30 08:23:25.361 307 307 E mm-camera: main: New session [1] creation failed with error
05-30 08:23:25.361 303 5423 E mm-camera-intf: mm_camera_open: opened, break out while loop
05-30 08:23:25.361 303 5423 E mm-camera-intf: mm_camera_open: cannot open control fd of '/dev/video1' (Bad address)
05-30 08:23:25.361 303 5423 E mm-camera-intf: camera_open: mm_camera_open err = -1
05-30 08:23:25.361 303 5423 E QCamera2HWI: camera_open failed.
05-30 08:23:25.364 303 5423 E CameraFlashlight: Could not open camera 0: -19
05-30 08:23:25.364 303 5423 E CameraClient: initialize: Camera 0: unable to initialize device: No such device (-19)
05-30 08:23:25.364 303 5423 E CameraService: connectHelper: Could not initialize client from HAL module.
05-30 08:23:25.376 5310 6349 E CameraHolder: fail to connect Camera:-1, aborting.
05-30 08:23:25.376 5310 6349 E CAM_PhotoModule: Failed to open camera:0
Uh, I donāt like the duplication of device trees. Iāll see later today if I merge both repos ācontent is on different branches, after all. Or we can ditch the old one, it never worked, after allā¦
Wow, this is really amazing! Thanks @chrmhoffmann!
I tried it several times and it seems that Dual-SIM is now working reliably in combination with the flight mode. For me this Lineage Port is now near to perfect, I didnāt find major bugs, and an other cool thing: Random reboots are completely gone. I had ~ 2 reboot per week before.
@roboe: @snevas and I decided to keep the repos for now because we feared that something would be lost if we delete it. If you say that no important work is gone forever if we delete it, you can remove the repos.
@chrmhoffmann Is there any chance that the whole community (you and everyone else) can work on one codebase together (rather than having to pull all commits you make into the WeAreFairphone repos)? We have a working build server set up (by @snevas) at the WeAreFairphone GH organization, which is triggered at every commit. No need to upload to AndroidFileHost then.
Just for info. The buildserver triggers from hooks when there are changes in the āWeAreFairphone/android_device_fairphone_FP2ā-repo and has the following manifest:
Dear everybody,
first I want to say thank you and especially @chrmhoffmann for working hard on making FP2 and LineageOS compatible!
I am considering to get a fairphone atm and essentially for me the decision depends on a free OS working.
But there is one thing that is quite important to me: encryption. Are you currently considering to work on it? (Do you have any idea on what the problem is?) Or is it rather low priority so it probably wonāt be fixed soon?
Until LineageOS supports encryption and depending on your definition of a āfree OSā you could probably check out Fairphone Open OS.
Itās the Open Source sibling of the ānormalā Fairphone OS, does not have Google services initially (if you want, you could install Open GApps or microG), and supports encryption.
there is already a free OS working: FP Open OS which is same as FP OS without Google and with Root (currently still based on Android 5.1 but Android 6 variant is coming very soon).
.
