Porting LineageOS to FP2

sky · August 4, 2017, 5:06pm

Just thought that perhaps libril-qc*.so could be changed in the new blobs.

z3ntu · August 4, 2017, 6:29pm

Would be great to get a list of changed blobs for all releases. @anon36364121 please?

Heiner · August 5, 2017, 8:16am

Does this change make a difference in power consumption while the screen is switched on? My impression is,that it is higher with Lineage than with the open FPOS.

sky · August 5, 2017, 11:10am

I see a lot of changed binarys and xmls comparing the blobs from 17.03 and 17.07 with a diff. How could we use the new blobs with the LAOS builds? I have no glue what to do but be willing to help.

chrmhoffmann · August 5, 2017, 12:47pm

The blobs are not taken from the fp open but from the stock fp OS. Not sure if that truly matters. I could check if there’s a new version out there, too.

Chris

chrmhoffmann · August 5, 2017, 11:17pm

New blobs are up. And some CVE fixes in the kernel. I will try to get all CVEs done, but that is very slow process.

Chris

maba007 · August 7, 2017, 1:45pm

@chrmhoffmann: Is that the requirement, so that a device with LineageOS appears in the deviceliste?

snevas · August 7, 2017, 2:57pm

New testbuild with the new blobs available @ https://fp2.joutubes.nl/builds/full/

Gonna test it now.

lklaus · August 7, 2017, 7:20pm

unfortunately, the new blobs don’t solve the proximity sensor drain

sky · August 8, 2017, 5:46am

SIM2 SMS bug also still persist

maba007 · August 8, 2017, 6:53am

Tested testbuild.zip (14.1-20170807-UNOFFICIAL-FP2):

Not able to Disable/Enable SIM slots

The .sha512 files should not contain a path. Currently it is not possible to check the .zip files with a single linux command.

snevas · August 8, 2017, 7:17am

Gonna fix the sha512 files and will update the porting post with all the found bugs. Thanks for the work.

Also started a new testbuild with the new security patches:
https://source.android.com/security/bulletin/2017-08-01

@chrmhoffmann is there anything you can do about the 3 bugs mentioned above, or are they broken upstream?

Lazalatin · August 8, 2017, 8:35am

So should the recent testbuild from 07.08.2017 contain the binary blobs 17.07.6? (As they can be downloaded here )
If so, why is the build.prop of the actual testbuild referring to fp2-gms-17.04.8 in its fingerprint?
Am I getting something wrong? Is the version number in the fingerprint not related to the binary blobs delivered with the image?

snevas · August 8, 2017, 9:05am

The buildserver uses this repo for the blobs:
https://github.com/FairBlobs/proprietary_vendor_fairphone-fork
which contains the 17.07.6.1 blobs

So I think the version number does not match the actual blobs used.

aral-matrix · August 8, 2017, 5:31pm

Bugreport:
SIM slot 1: Main Sim w/ PIN
SIM slot 2: prepaid Sim with default 0000 PIN

Turn on phone, upon entering the correct SIM1 PIN: “SIM PIN Operation failed”

Compare:
SIM slot 1: prepaid Sim with default 0000 PIN
SIM slot 2: Main Sim w/ PIN

Turn on phone, SIM1 PIN request skipped(*), upon entering the correct SIM2 PIN: both SIMs are activated correctly, all network services can be used

(*) There is a setting activated on the Sim card (as I just learned) that it is not locked

lklaus · August 8, 2017, 6:21pm

Is this FP2 specific or general LOS?

08-08 20:12:30.647 14273 14273 W sh : type=1400 audit(0.0:304): avc: denied { read } for name="/" dev=“rootfs” ino=1 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:rootfs:s0 tclass=dir permissive=0

I see this also when working with a terminal emulator. Not being root gives a a permission denied (termux) or “empty directory” (file manager)

“of course”

z3ntu · August 8, 2017, 7:46pm

I’d call this wanted behavior because why should a non-root user be allowed to see that folder?

WolleTD · August 8, 2017, 8:04pm

I recently built and installed LineageOS on my FP2, works decent so far. Thanks to all contributors.

I just realized a feature I loved on the Fairphone OS that seems missing in Lineage: Mounting the SD card as USB Mass Storage to a computer.

I’m not an Android dev, but some digging around makes it look like 1) nobody believes this is possible, while 2) it’s perfectly possible and low-level implementation just waits for a userspace button.

lklaus · August 8, 2017, 8:05pm

Well, why not? This is root, the start of everything, and what secret do you expect there? Besides, on every SELinux enabled system, / is readable by everyone. I can’t think of any reason not to be able to read /. Except you would propose security by obscurity. But even then, the contents of root are no secret on Android. You may argue for /system, and the likes, but /? Also /data is only readable as root, as seen by the permissions. So, if /data is rwxrwx–x, which reflects this, / is rwxr-xr-x, as on every Unix system, and forbidden by policy? I wouldn’t call this consistent…

sky · August 9, 2017, 9:31am

It’s more about signed builds and release keys

BUILD_FINGERPRINT=Fairphone/FP2/FP2:6.0.1/FP2-gms-17.04.8/FP2-gms-17.04.8:user/release-keys

github.com

LineageOS/android_device_fairphone_FP2/blob/cm-14.1/lineage.mk

# Copyright (C) 2017 The LineageOS Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#      http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

# Inherit from those products. Most specific first.
$(call inherit-product, $(SRC_TARGET_DIR)/product/full_base_telephony.mk)

# Inherit from FP2 device
$(call inherit-product, device/fairphone/FP2/FP2.mk)

This file has been truncated. show original