[ROM][UNOFFICIAL][9.0] LineageOS 16.0 [PEREGRINE]

Search This thread

Allstargaurav

Senior Member
Sep 23, 2016
479
1,851
21
Delhi
2okPze5.png


LineageOS is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), which is designed to increase performance and reliability over stock Android for your device.

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

What's working :

  • Boots
  • RIL (Calls, SMS, Data)
  • Dual-SIM
  • Wi-Fi
  • Camera
  • Video Recording
  • Video Playback
  • Audio ( Record and Playback )
  • Sensors
  • Flash
  • Led
  • Offline Charging

What's not working :
  • You tell me

Instructions :
  • Download the latest build and gapps
  • Reboot to recovery
  • Flash the latest build and gapps
  • Reboot
Downloads :
Reporting Bugs
  • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
  • If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
  • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

Code:
What is your--
Phone model:
Lineage version:
Lineage Download url:
Gapps version:
 
Did you--
wipe:
 restore with titanium backup:
reboot after having the issue:
 
Are you using--
a task killer:
a non-stock kernel:
LineageSettings/Performance settings (other than stock):
Dual SIM:
other modifications:
 
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Credits :

Donations :
You don't have to but if you want so...

XDA:DevDB Information
Pie For Peregrine, ROM for the Moto G

Contributors
Allstargaurav
Source Code: https://github.com/MotoDevelopment

ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
Based On: AOSP

Version Information
Status: Stable
Stable Release Date: 2019-04-21

Created 2018-08-28
Last Updated 2019-04-21
 

bartekm01

Senior Member
Sep 3, 2017
93
43
NOTE - I have not tested the build cuz I don't own this device.

Let me know if you find any bugs (Device Related) and read OP on how to report bugs
Lineage is still in beta stages so only report bugs if you think they are device related.
Do not ask for any feature request, they will be added in upcoming future builds
Hi
Thanks for this build. My peregrine booted without any problems. If I find any bugs I will send info.

Found one:
- device Thames - dark - is not working
- there also is no advance reboot option in developer menu
- can't enter to recovery via key combination, only via adb
- Magisk 16.71 not installed, but in TWRP installation was successful, so "su -" in terminal - permission denied -> fixed after installation Magisk Manager
- audio is not working (changing ringtone, alarm, notfication sound) - settings has stopped and no sound at all. -> also fixed after reboot audio is working fine
 
Last edited:
  • Like
Reactions: Viqta_

shellgrig

Member
Jul 31, 2014
11
3
I don't know if its a bug or nota bit i can't root ROM with magisk and after flashing latest beta 16.7 i can't connect to internet in any browser but with playstore works fine
 

Allstargaurav

Senior Member
Sep 23, 2016
479
1,851
21
Delhi
Hi
Thanks for this build. My peregrine booted without any problems. If I find any bugs I will send info.

Found one:
- device Thames - dark - is not working
- there also is no advance reboot option in developer menu
- can't enter to recovery via key combination, only via adb
- Magisk 16.71 not installed, but in TWRP installation was successful, so "su -" in terminal - permission denied -> fixed after installation Magisk Manager
- audio is not working (changing ringtone, alarm, notfication sound) - settings has stopped and no sound at all. -> also fixed after reboot audio is working fine
Literally you quoted the msg in which I said features will not be there and will be added with time
Please read before sending anything
 

sevenrock

Senior Member
Nov 27, 2012
660
1,096
Hi,
@Allstargaurav: FYI: my kernel repo now contains a lineage-16.0 branch:
https://github.com/sevenrock/android_kernel_motorola_msm8226/commits/lineage-16.0

It was forked from the oreo-m2 branch from
https://github.com/falcon-pie/android_kernel_motorola_msm8226.git
and contains 9 patches to add getrandom() to the kernel and also
46 security-related patches merged from my cm-14.1 branch:
https://github.com/sevenrock/android_kernel_motorola_msm8226/commits/cm-14.1

Your ROM boots fine on my phone, thanks!, but I am having
problems to build a working ROM myself, it loops the bootanima-
tion forever. I am suspecting some problems in the wifi area.

This is a logcat snippet from your ROM:
Code:
$ grep -i StartWifi logcat_xda 
09-01 06:04:08.879   557   557 I SystemServer: StartWifi
09-01 06:04:09.931   557   557 D SystemServerTiming: StartWifi took to complete: 1052ms
09-01 06:04:09.931   557   557 I SystemServer: StartWifiScanning
09-01 06:04:09.936   557   557 D SystemServerTiming: StartWifiScanning took to complete: 5ms
09-01 06:04:09.937   557   557 I SystemServer: StartWifiP2P
09-01 06:04:09.990   557   557 D SystemServerTiming: StartWifiP2P took to complete: 53ms
and this is from mine:
Code:
$ grep -i "No service published" logcat10 | grep SystemServiceRegistry | grep -i wifi
08-27 17:32:06.334   543   543 E SystemServiceRegistry: No service published for: wifi
08-27 17:32:06.334   543   543 E SystemServiceRegistry: android.os.ServiceManager$ServiceNotFoundException: No service published for: wifi
08-27 17:32:06.960   543   583 E SystemServiceRegistry: No service published for: wifip2p
08-27 17:32:06.960   543   583 E SystemServiceRegistry: android.os.ServiceManager$ServiceNotFoundException: No service published for: wifip2p
The complete logcat from this area look like this:
Code:
08-27 17:32:06.334   543   543 E SystemServiceRegistry: No service published for: wifi
08-27 17:32:06.334   543   543 E SystemServiceRegistry: android.os.ServiceManager$ServiceNotFoundException: No service published for: wifi
08-27 17:32:06.334   543   543 E SystemServiceRegistry: 	at android.os.ServiceManager.getServiceOrThrow(ServiceManager.java:143)
08-27 17:32:06.334   543   543 E SystemServiceRegistry: 	at android.app.SystemServiceRegistry$51.createService(SystemServiceRegistry.java:603)
08-27 17:32:06.334   543   543 E SystemServiceRegistry: 	at android.app.SystemServiceRegistry$51.createService(SystemServiceRegistry.java:600)
08-27 17:32:06.334   543   543 E SystemServiceRegistry: 	at android.app.SystemServiceRegistry$CachedServiceFetcher.getService(SystemServiceRegistry.java:1098)
08-27 17:32:06.334   543   543 E SystemServiceRegistry: 	at android.app.SystemServiceRegistry.getSystemService(SystemServiceRegistry.java:1014)
08-27 17:32:06.334   543   543 E SystemServiceRegistry: 	at android.app.ContextImpl.getSystemService(ContextImpl.java:1721)
08-27 17:32:06.334   543   543 E SystemServiceRegistry: 	at org.lineageos.platform.internal.ProfileTriggerHelper.<init>(ProfileTriggerHelper.java:77)
08-27 17:32:06.334   543   543 E SystemServiceRegistry: 	at org.lineageos.platform.internal.ProfileManagerService.initialize(ProfileManagerService.java:294)
08-27 17:32:06.334   543   543 E SystemServiceRegistry: 	at org.lineageos.platform.internal.ProfileManagerService.initialize(ProfileManagerService.java:290)
08-27 17:32:06.334   543   543 E SystemServiceRegistry: 	at org.lineageos.platform.internal.ProfileManagerService.onStart(ProfileManagerService.java:259)
08-27 17:32:06.334   543   543 E SystemServiceRegistry: 	at com.android.server.SystemServiceManager.startService(SystemServiceManager.java:126)
08-27 17:32:06.334   543   543 E SystemServiceRegistry: 	at com.android.server.SystemServiceManager.startService(SystemServiceManager.java:113)
08-27 17:32:06.334   543   543 E SystemServiceRegistry: 	at org.lineageos.platform.internal.LineageSystemServer.startServices(LineageSystemServer.java:85)
08-27 17:32:06.334   543   543 E SystemServiceRegistry: 	at org.lineageos.platform.internal.LineageSystemServer.run(LineageSystemServer.java:60)
08-27 17:32:06.334   543   543 E SystemServiceRegistry: 	at java.lang.reflect.Method.invoke(Native Method)
08-27 17:32:06.334   543   543 E SystemServiceRegistry: 	at com.android.server.SystemServer.startOtherServices(SystemServer.java:1642)
08-27 17:32:06.334   543   543 E SystemServiceRegistry: 	at com.android.server.SystemServer.run(SystemServer.java:434)
08-27 17:32:06.334   543   543 E SystemServiceRegistry: 	at com.android.server.SystemServer.main(SystemServer.java:297)
08-27 17:32:06.334   543   543 E SystemServiceRegistry: 	at java.lang.reflect.Method.invoke(Native Method)
08-27 17:32:06.334   543   543 E SystemServiceRegistry: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
08-27 17:32:06.334   543   543 E SystemServiceRegistry: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:838)
08-27 17:32:06.339   543   543 W LineageSystemServer: ***********************************************
08-27 17:32:06.340   543   543 E LineageSystemServer: BOOT FAILURE starting org.lineageos.platform.internal.ProfileManagerService
08-27 17:32:06.340   543   543 E LineageSystemServer: java.lang.RuntimeException: Failed to start service org.lineageos.platform.internal.ProfileManagerService: onStart threw an exception
08-27 17:32:06.340   543   543 E LineageSystemServer: 	at com.android.server.SystemServiceManager.startService(SystemServiceManager.java:128)
08-27 17:32:06.340   543   543 E LineageSystemServer: 	at com.android.server.SystemServiceManager.startService(SystemServiceManager.java:113)
08-27 17:32:06.340   543   543 E LineageSystemServer: 	at org.lineageos.platform.internal.LineageSystemServer.startServices(LineageSystemServer.java:85)
08-27 17:32:06.340   543   543 E LineageSystemServer: 	at org.lineageos.platform.internal.LineageSystemServer.run(LineageSystemServer.java:60)
08-27 17:32:06.340   543   543 E LineageSystemServer: 	at java.lang.reflect.Method.invoke(Native Method)
08-27 17:32:06.340   543   543 E LineageSystemServer: 	at com.android.server.SystemServer.startOtherServices(SystemServer.java:1642)
08-27 17:32:06.340   543   543 E LineageSystemServer: 	at com.android.server.SystemServer.run(SystemServer.java:434)
08-27 17:32:06.340   543   543 E LineageSystemServer: 	at com.android.server.SystemServer.main(SystemServer.java:297)
08-27 17:32:06.340   543   543 E LineageSystemServer: 	at java.lang.reflect.Method.invoke(Native Method)
08-27 17:32:06.340   543   543 E LineageSystemServer: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
08-27 17:32:06.340   543   543 E LineageSystemServer: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:838)
08-27 17:32:06.340   543   543 E LineageSystemServer: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'android.net.wifi.WifiInfo android.net.wifi.WifiManager.getConnectionInfo()' on a null object reference
08-27 17:32:06.340   543   543 E LineageSystemServer: 	at org.lineageos.platform.internal.ProfileTriggerHelper.getActiveSSID(ProfileTriggerHelper.java:188)
08-27 17:32:06.340   543   543 E LineageSystemServer: 	at org.lineageos.platform.internal.ProfileTriggerHelper.<init>(ProfileTriggerHelper.java:78)
08-27 17:32:06.340   543   543 E LineageSystemServer: 	at org.lineageos.platform.internal.ProfileManagerService.initialize(ProfileManagerService.java:294)
08-27 17:32:06.340   543   543 E LineageSystemServer: 	at org.lineageos.platform.internal.ProfileManagerService.initialize(ProfileManagerService.java:290)
08-27 17:32:06.340   543   543 E LineageSystemServer: 	at org.lineageos.platform.internal.ProfileManagerService.onStart(ProfileManagerService.java:259)
08-27 17:32:06.340   543   543 E LineageSystemServer: 	at com.android.server.SystemServiceManager.startService(SystemServiceManager.java:126)
08-27 17:32:06.340   543   543 E LineageSystemServer: 	... 10 more

The local_manifest.xml used
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>

 <!-- Motorola repos -->
 <project path="device/motorola/peregrine" name="sevenrock/android_device_motorola_peregrine" remote="github" revision="lineage-16.0" />
 <project path="device/motorola/msm8226-common" name="MotoDevelopment/android_device_motorola_msm8226-common" remote="github" revision="lineage-16.0" />
 <project path="kernel/motorola/msm8226" name="MotoDevelopment/android_kernel_motorola_msm8226" remote="github" revision="oreo-m2" />
 <project path="vendor/motorola" name="RenanQueiroz/proprietary_vendor_motorola" remote="github" revision="lineage-16.0" />

 <project path="packages/resources/devicesettings" name="LineageOS/android_packages_resources_devicesettings" revision="lineage-16.0" remote="github"/>

 <project path="hardware/qcom/power" name="LineageOS/android_hardware_qcom_power" groups="qcom,pdk" />
 <project path="hardware/qcom/wlan-caf" name="arco/android_hardware_qcom_wlan" remote="github" revision="lineage-16.0-caf" />
 <project path="device/qcom/common" name="LineageOS/android_device_qcom_common" revision="lineage-15.1" remote="github"/>
 <project path="system/qcom" name="LineageOS/android_system_qcom" groups="qcom" revision="lineage-15.1" />
 <project path="device/qcom/sepolicy" name="LineageOS/android_device_qcom_sepolicy" />

 <project path="external/connectivity" name="LineageOS/android_external_connectivity" />

</manifest>

My peregrine device tree is based on
https://github.com/MotoDevelopment/android_device_motorola_falcon/tree/lineage-16.0

I used the wlan-caf repo because it was mentioned here:
https://review.lineageos.org/#/c/LineageOS/android_hardware_libhardware_legacy/+/223521/

The bt repo mentioned there may fix the bt problems you are seeing,
I did not test it because my device does not boot :(

Do you have any idea, or better patches ;), which could solve my problem?

Regards, sevenrock
 

Allstargaurav

Senior Member
Sep 23, 2016
479
1,851
21
Delhi
Hi,

@Allstargaurav: FYI: my kernel repo now contains a lineage-16.0 branch:
https://github.com/sevenrock/android_kernel_motorola_msm8226/commits/lineage-16.0

It was forked from the oreo-m2 branch from
https://github.com/falcon-pie/android_kernel_motorola_msm8226.git
and contains 9 patches to add getrandom() to the kernel and also
46 security-related patches merged from my cm-14.1 branch:
https://github.com/sevenrock/android_kernel_motorola_msm8226/commits/cm-14.1

Your ROM boots fine on my phone, thanks!, but I am having
problems to build a working ROM myself, it loops the bootanima-
tion forever. I am suspecting some problems in the wifi area.

This is a logcat snippet from your ROM:

and this is from mine:

The complete logcat from this area look like this:


The local_manifest.xml used


My peregrine device tree is based on
https://github.com/MotoDevelopment/android_device_motorola_falcon/tree/lineage-16.0

I used the wlan-caf repo because it was mentioned here:
https://review.lineageos.org/#/c/LineageOS/android_hardware_libhardware_legacy/+/223521/

The bt repo mentioned there may fix the bt problems you are seeing,
I did not test it because my device does not boot :(

Do you have any idea, or better patches ;), which could solve my problem?

Regards, sevenrock
Use my boot image and see if the ROM boots and I don't think WiFi can make the ROM bootloop.
From where did you you pick those kernel patches?
They might be the problem, try without them.
I picked lot of open patches from los Gerrit and tracked few repo from pixel experience GitHub to make everything work
Best bet is you use hals from xpe rom cuz lineage one's are not ready (at that time no idea as of today)
 
  • Like
Reactions: sevenrock

sevenrock

Senior Member
Nov 27, 2012
660
1,096
Hi,
Use my boot image and see if the ROM boots and I don't think WiFi can make the ROM bootloop.
I did already, your image boots with working wifi, so my device is not broken ;)
From where did you you pick those kernel patches?
They might be the problem, try without them.
The bootloop already occured before I applied the additional kernel patches.
Each patch carries a link to its source and I am using them on my cm-14.1
daily driver ROM without problems.
I picked lot of open patches from los Gerrit
+1
and tracked few repo from pixel experience GitHub to make everything work
Best bet is you use hals from xpe rom cuz lineage one's are not ready (at that time no idea as of today)
Which repos did you track exactly? I am not familiar with the internals of
pixel experience so I just had a hard time finding useful repos.
 

sevenrock

Senior Member
Nov 27, 2012
660
1,096
Code:
$ grep -i "No service published" logcat10 | grep SystemServiceRegistry | grep -i wifi
08-27 17:32:06.334   543   543 E SystemServiceRegistry: No service published for: wifi
08-27 17:32:06.334   543   543 E SystemServiceRegistry: android.os.ServiceManager$ServiceNotFoundException: No service published for: wifi
08-27 17:32:06.960   543   583 E SystemServiceRegistry: No service published for: wifip2p
08-27 17:32:06.960   543   583 E SystemServiceRegistry: android.os.ServiceManager$ServiceNotFoundException: No service published for: wifip2p
Finally found the reason for the problem, all permission xmls copied by msm8226.mk
were missing in my ROM in contrast to your ROM. This commit fixes the problem:
https://github.com/sevenrock/androi...mmit/46517ee2c1c0587f21199ff049346ea480273565
 
Last edited:

sevenrock

Senior Member
Nov 27, 2012
660
1,096
Finally I was able to build and boot for the first time a self-built ROM :)
without any crashes reported and with working wifi, bluetooth, camera
(photo & video) and (1809/13) also FMRadio.

I needed to apply *a lot of* patches, for reference:

local_manifest_xt1039.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>

 <project path="device/motorola/peregrine" name="sevenrock/android_device_motorola_peregrine" remote="github" revision="lineage-16.0" />
 <project path="device/motorola/msm8226-common" name="sevenrock/android_device_motorola_msm8226-common" remote="github" revision="lineage-16.0" />
 <project path="kernel/motorola/msm8226" name="RenanQueiroz/android_kernel_motorola_msm8226" remote="github" revision="lineage-16.0" />
 <project path="vendor/motorola" name="RenanQueiroz/proprietary_vendor_motorola" remote="github" revision="lineage-16.0" />

 <project path="device/qcom/common" name="LineageOS/android_device_qcom_common" revision="lineage-15.1" remote="github"/>
 <project path="hardware/qcom/fm" name="LineageOS/android_hardware_qcom_fm" groups="qcom,qcom_fm" />
 <project path="system/qcom" name="LineageOS/android_system_qcom" groups="qcom" revision="lineage-15.1" />
 <project path="vendor/qcom/opensource/cryptfs_hw" name="LineageOS/android_vendor_qcom_opensource_cryptfs_hw" />
 <project path="packages/apps/FMRadio" name="LineageOS/android_packages_apps_FMRadio" />
 <project path="packages/overlays/Lineage" name="LineageOS/android_packages_overlays_Lineage" />
 <project path="packages/resources/devicesettings" name="LineageOS/android_packages_resources_devicesettings" revision="lineage-16.0" remote="github"/>

</manifest>
My github repos are based on
https://github.com/sevenrock/android_device_motorola_peregrine <- https://github.com/MotoDevelopment/android_device_motorola_falcon.git
https://github.com/sevenrock/android_device_motorola_msm8226-common <- https://github.com/MotoDevelopment/android_device_motorola_msm8226-common.git

Now the other patches from gerrit:
Code:
    python vendor/lineage/build/tools/repopick.py \
    223340 223341 223342 223343 223344 223345 223346 \
    225546 \
    226148 226154 226236 226343 \
    227260 227261 \
    229612 \
    230099 230382 230610 230642 230755 \
    231710 231711

    for i in \
            pie-mode-bits \
            pie-wlan-caf \
            pie-powermenu \
            pie-su \
            pie-trust-interface \
            lineagehw-hidl \
            wifi-p \
            pie-hw-fde \
            directly-show-unlock-screen \
            pie-lock-pattern \
            pie-expanded-desktop \
            pie-hide-night-display \
            revert-textrels \
            torch-colorz \
            pie-battery-styles \
            pie-qcom-legacy-sepolicy \
            pie-kernel-headers \
            pie-styles \
            ; \
        do
        python vendor/lineage/build/tools/repopick.py -t $i
    done
To fix build errors with qcom packages apply this patch:
Code:
--- los16.0/system/qcom/softap/jni/Android.mk.orig	2018-08-26 23:33:51.890102343 +0200
+++ los16.0/system/qcom/softap/jni/Android.mk	2018-08-26 23:33:42.770035526 +0200
@@ -9,6 +9,8 @@
 
 LOCAL_MODULE := libQWiFiSoftApCfg
 
+LOCAL_CFLAGS := -Werror -Wno-error=unused-parameter
+
 LOCAL_MODULE_TAGS := optional
 
 LOCAL_C_INCLUDES += $(TARGET_OUT_INTERMEDIATES)/KERNEL_OBJ/usr/include \
--- los16.0/system/qcom/softap/sdk/Android.mk.orig	2018-08-26 23:20:01.283920943 +0200
+++ los16.0/system/qcom/softap/sdk/Android.mk	2018-08-26 23:41:32.477464560 +0200
@@ -12,6 +12,8 @@
 
 LOCAL_CFLAGS += -DSDK_VERSION=\"0.0.1.0\"
 
+LOCAL_CFLAGS += -Wno-error
+
 LOCAL_USE_VNDK := true
 
 LOCAL_COPY_HEADERS_TO := sdk/softap/include
 
Last edited:

Allstargaurav

Senior Member
Sep 23, 2016
479
1,851
21
Delhi
Finally I was able to build and boot for the first time a self-built ROM :)
without any crashes reported and with working wifi, bluetooth and camera
(photo & video). I needed to apply *a lot of* patches, for reference:

local_manifest_xt1039.xml

My github repos are based on
https://github.com/sevenrock/android_device_motorola_peregrine <- https://github.com/MotoDevelopment/android_device_motorola_falcon.git
https://github.com/sevenrock/android_device_motorola_msm8226-common <- https://github.com/MotoDevelopment/android_device_motorola_msm8226-common.git
https://github.com/sevenrock/android_kernel_motorola_msm8226 <- https://github.com/falcon-pie/android_kernel_motorola_msm8226.git

Now the other patches from gerrit:

The vold patches needed to be reverted due to https://review.lineageos.org/225444
breaking my sdcard which caused a lot of follow-up errors, like broken camera.

I also removed all the "#" chars for TARGET_LD_SHIM_LIBS in
https://github.com/sevenrock/androi...n/blob/lineage-16.0/BoardConfigCommon.mk#L177
but I am not sure if this was really necessary.
Good job bro
 

ThePiGuy

Senior Member
Nov 5, 2017
1,305
1,245
Finally I was able to build and boot for the first time a self-built ROM :)
without any crashes reported and with working wifi, bluetooth and camera
(photo & video). I needed to apply *a lot of* patches, for reference:

local_manifest_xt1039.xml

My github repos are based on
https://github.com/sevenrock/android_device_motorola_peregrine <- https://github.com/MotoDevelopment/android_device_motorola_falcon.git
https://github.com/sevenrock/android_device_motorola_msm8226-common <- https://github.com/MotoDevelopment/android_device_motorola_msm8226-common.git
https://github.com/sevenrock/android_kernel_motorola_msm8226 <- https://github.com/falcon-pie/android_kernel_motorola_msm8226.git

Now the other patches from gerrit:

The vold patches needed to be reverted due to https://review.lineageos.org/225444
breaking my sdcard which caused a lot of follow-up errors, like broken camera.

I also removed all the "#" chars for TARGET_LD_SHIM_LIBS in
https://github.com/sevenrock/androi...n/blob/lineage-16.0/BoardConfigCommon.mk#L177
but I am not sure if this was really necessary.
Just came back to look at this forum - nice job on building your first ROM :)

Btw, did you have any issues with the libqsap_sdk. My LG G4 uses RIL from a Moto phone and it kicks up lots of errors because lineage removed the android_system_qcom repo from their default manifest
 
  • Like
Reactions: sevenrock

sevenrock

Senior Member
Nov 27, 2012
660
1,096
Btw, did you have any issues with the libqsap_sdk. My LG G4 uses RIL from a Moto phone and it kicks up lots of errors because lineage removed the android_system_qcom repo from their default manifest
Hi,

yes I had those problems, too. That's the reason why my local_manifest includes
Code:
 <project path="device/qcom/common" name="LineageOS/android_device_qcom_common" revision="lineage-15.1" remote="github"/>
and my to-do list includes posting to https://review.lineageos.org/227746 that we still need this repo.
 
  • Like
Reactions: bejunk and ThePiGuy

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    For those of you wishing to update to the APRIL '21 Security Patches, I've uploaded one of my unofficial builds that is based off the latest build files available with the most recent security patches added (I know there are a number of members who for one reason or another are unable to or unwilling to build it themselves).

    Note: The recent updates have been large and may require a smaller version of Open Gapps than you've been installing, the removal of some apps or, as a last resort, resizing the system partition.

    Note: Requires Full Clean Flash when installing rom for 1st time I.E., coming from 14.1 (official or unofficial), etc. - in TWRP wipe Cache, Dalvik cache, System and importantly format Data > Yes before flashing the appropriate Open Gapps (pico Jan. 17th '20, for now - the latest uploads have been presenting problems with Pie) - reboot, then in TWRP install preferred root (latest Magisk version recommended). I do not recommend the Xposed framework that's available for pie as it is closed-source).
    Very Important: Do a nandroid backup first, including your data - copy any data/media files (e.g., photos, videos etc.), on your SD card over to your PC.
    Note: Encryption is not working fully - If you need it, check out the 14.1 rom - it is fully up to date in my latest uploads there.

    If you're coming from one of the unofficial updates I uploaded previously, I recommend you do a regular clean flash (wipe Cache, Dalvik cache & System), re-install Open Gapps, reboot to recovery & install preferred root (latest Magisk recommended). I do not recommend the Xposed framework that's available for pie as it is closed-source, i.e., you really don't know what you're installing).

    Download Link for lineage-16.0-20210408-UNOFFICIAL-peregrine.zip

    I've uploaded my copy of the Jan. 17th '20 Open Gapps ARM Pico 9.0 here as it appears to be no longer available for download from the Open Gapps site: https://mega.nz/file/QShAkSqL#U20D_i2CI1VxtnblLKrSzwDNK4AAxxdGTb-KTT_iYlU

    I give full credit to the author of this thread @Allstargaurav and in particular to @sevenrock and @RenanQueiroz for their excellent work in getting this rom to this point. Those of you who have not been building this rom for themselves but using the last posted upload by the author of this thread will notice some substantial improvements and should be relatively pleased with how it performs now. After flashing let the rom settle in for a number of hours to start to see the improvements and reap the full benefit.

    I do, however, recommend you learn to build it yourselves: refer to post # 230 for the full build instructions.
    2
    This is working fine for me, even using a download straight off OpenGApps for arm/9/pico - so maybe they have fixed their site. Thanks - I am using a Peregrine a friend gave up on, because the UK network operator abandoned it on Android 4.4. It would have gone to landfill, but Lineage has allowed me to keep it going and it is now running Android 9 via your Lineage 16 build, seemingly just fine.
  • 33
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    What's working :

    • Boots
    • RIL (Calls, SMS, Data)
    • Dual-SIM
    • Wi-Fi
    • Camera
    • Video Recording
    • Video Playback
    • Audio ( Record and Playback )
    • Sensors
    • Flash
    • Led
    • Offline Charging

    What's not working :
    • You tell me

    Instructions :
    • Download the latest build and gapps
    • Reboot to recovery
    • Flash the latest build and gapps
    • Reboot
    Downloads :
    Reporting Bugs
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    Phone model:
    Lineage version:
    Lineage Download url:
    Gapps version:
     
    Did you--
    wipe:
     restore with titanium backup:
    reboot after having the issue:
     
    Are you using--
    a task killer:
    a non-stock kernel:
    LineageSettings/Performance settings (other than stock):
    Dual SIM:
    other modifications:
     
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
    Credits :

    Donations :
    You don't have to but if you want so...

    XDA:DevDB Information
    Pie For Peregrine, ROM for the Moto G

    Contributors
    Allstargaurav
    Source Code: https://github.com/MotoDevelopment

    ROM OS Version: 9.x Pie
    ROM Kernel: Linux 3.4.x
    Based On: AOSP

    Version Information
    Status: Stable
    Stable Release Date: 2019-04-21

    Created 2018-08-28
    Last Updated 2019-04-21
    15
    Lineage 16.0 April Update
    • Fixed Black Screen Issue
    • April security patch
    • Enforcing Build
    • Fixed Lineage Offline charger
    • Other Fixes and all that ****
    Just Clean flash that's all

    Would not be possible without @RenanQueiroz I did not do anything

    Download: https://www.androidfilehost.com/?fid=1395089523397953949

    Note: If you can't flash gapps look for other alternative gapps which is smaller in size.
    10
    New LineageOS 16.0 update is out!

    Changelog:
    • Fixed Whatsapp and Instagram Issue
    • Enforcing Build
    • Many ROM side changes (Most of the features from 15.1 are back, although some switches won't work)
    • Added Snap Cam
    • Zram working again
    • Many other minor improvements
    • Lot more stuff which I am lazy to list flash and find yourself

    Download: https://www.androidfilehost.com/?fid=11410963190603869829

    Special thanks to @sevenrock it would not have been possible without him
    Also thanks to @RohanHasabe8 for server
    9
    For those of you wishing to update to the MAY '20 Security Patches, I've uploaded one of my unofficial builds that is based off the latest build files available with the most recent security patches added (I know there are a number of members who for one reason or another are unable to or unwilling to build it themselves). I have been reviewing and testing these patches in LineageOS Gerrit for LineageOS 14.1 (Moto G LTE Peregrine) and LineageOS 15.1 (LG G4) when they're posted before they are merged and will be doing the same from this point on for LineageOS 16.0, before uploading for your personal use.

    Note: Requires Full Clean Flash when installing rom for 1st time I.E., coming from 14.1 (official or unofficial), etc. - in TWRP wipe Cache, Dalvik cache, System and importantly format Data > Yes before flashing the appropriate Open Gapps (pico Jan. 17th '20, for now - the latest uploads have been presenting problems with Pie) - reboot, then in TWRP install preferred root (latest Magisk version recommended). I do not recommend the Xposed framework that's available for pie as it is closed-source).
    Very Important: Do a nandroid backup first, including your data - copy any data/media files (e.g., photos, videos etc.), on your SD card over to your PC.
    Note: Encryption is not working fully - If you need it, check out the 14.1 rom - it is fully up to date in my latest uploads there.

    If you're coming from one of the unofficial updates I uploaded previously, I recommend you do a regular clean flash (wipe Cache, Dalvik cache & System), re-install Open Gapps, reboot to recovery & install preferred root (latest Magisk recommended). I do not recommend the Xposed framework that's available for pie as it is closed-source, i.e., you really don't know what you're installing).

    Download Link for lineage-16.0-20200508-UNOFFICIAL-peregrine.zip
    https://mega.nz/file/MeRQlQjK#Yw4SJBvw5pz8T1OfFoT_hmOt4gS4KbtCLOgWEKdlLQo

    I give full credit to the author of this thread @Allstargaurav and in particular to @sevenrock and @RenanQueiroz for their excellent work in getting this rom to this point. Those of you who have not been building this rom for themselves but using the last posted upload by the author of this thread will notice some substantial improvements and should be very pleased with how it performs now. After flashing let the rom settle in for a number of hours to start to see the improvements and reap the full benefit.

    I do, however, recommend you learn to build it yourselves: refer to post # 230 for the full build instructions.
    8
    How to build & update this rom yourself: Updated for Ubuntu 20.04 based systems.

    For those members wishing to build this rom for themselves and keep it updated, The following roomservice.xml file is what I've been using (forked from sevenrock's github site (https://github.com/sevenrock) - full credit to him:

    <?xml version="1.0" encoding="UTF-8"?>
    <manifest>
    <project name="sdembis/android_device_motorola_peregrine" path="device/motorola/peregrine" remote="github" revision="lineage-16.0" />
    <project name="sdembis/android_device_motorola_msm8226-common" path="device/motorola/msm8226-common" remote="github" revision="lineage-16.0" />
    <project name="sdembis/android_kernel_motorola_msm8226" path="kernel/motorola/msm8226" remote="github" revision="lineage-16.0" />
    <project name="sdembis/proprietary_vendor_motorola" path="vendor/motorola"
    remote="github" revision="lineage-16.0" />
    <project name="LineageOS/android_system_qcom" path="system/qcom" remote="github" revision="lineage-16.0" />
    <project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-16.0"/>
    </manifest>

    * Follow the directions from here for setting up the build environment: Build for peregrine
    - * Do not go any further in setting up your build environment than the paragraph including the Configure git instructions. After setting up the git configuration, ignore the rest of the instructions posted there and follow the guide posted here.

    Note: If Building on an Ubuntu 20.04 (e.g., Linux Mint 20.0) or newer based Linux versions show the content of the following:
    To get around all the errors I encountered I had to do the following:

    In the "Software Manager" confirm all the following are installed to check your installation method

    - openjdk-8-jdk
    - openjdk-8-jdk-headless
    - openjdk-8-jre
    - openjdk-8-jre-headless

    with no environment path or any other path you might have set for Java.

    Use the Switch Manager command to set Python2 as the default version (refer to this how to - https://linuxconfig.org/ubuntu-20-04-python-version-switch-manager)

    Insert (if not already included) export LC_ALL=C and export CCACHE_EXEC=/usr/bin/ccache in, save it and source it for the /.bashrc file.

    If you haven't already done so, make sure you install the additional language packs noted in the System Reports.

    That should get you going to successfully build for LineageOS on any Ubuntu 20.04 based system.

    Recommended:
    - Seriously consider installing Linux Mint - Xfce (for example), in a dual-boot set-up before setting up your build environment. Your builds will run much faster with fewer problems versus setting up your build environment in VirtualBox!
    - add an 8GB swap file (particularly important if running low ram, e.g., 4GB).

    Once you've set up the android build environment, initialize the LineageOS source repository inside a new folder labelled, for example, LineageOS_16.0 with the following command:
    repo init -u git://github.com/LineageOS/android.git -b lineage-16.0

    To add the roomservice.xml file
    above to the .repo folder (Note: if the .repo folder is not visible in your LineageOS_16.0 folder after initializing, try Ctrl H to make it visible):
    - make a new folder inside the .repo folder and label the new folder: local_manifests
    - create an empty document inside the local_manifests folder and label it roomservice.xml
    - copy the roomservice.xml file contents exactly as above and paste it into the document, making sure you save it.

    Then, in the LineageOS_16.0 folder, open a command prompt, type the following and enter it:
    repo sync --force-sync -c -j1
    (Note: j1 can be a higher number depending on the number of cores your processor has - the default is j4 but I have had the fewest problems using j1 initially if trying to build with lower ram).

    Recomended:
    - Turn on caching to speed up your builds:
    export USE_CCACHE=1 (add the line to your ~/.bashrc file using this command, for example: sudo nano ~/.bashrc to open the file, before adding the line and saving it). Then update your environment using this command: source ~/.profile
    - In the LineageOS_14.1 folder you created open a command prompt and type & enter the following:
    prebuilts/misc/linux-x86/ccache/ccache -M 50G this will permanently set your cache to 50GB and speed up your builds hugely. Only has to be done once.
    - Configure Jack by adding this as well to your ~/.bashrc file, the same way that you set up using ccache:
    export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xms8G -Xmx8G. Then update your environment using this command: source ~/.profile. Adjust the -Xms8G -Xmx8G if trying to build with lower ram (e.g., 4GB). I'm currently running 20GB ram (shortly going to 24) and use 8GB for these particular commands.
    - Note: If running very low ram (Not recommended as you will likely have problems or fail to complete the build, but if trying to build with, e.g., 4 GB), set jack.server.max-service=1 in the .jack-server folder in /home/"user-name"/.jack-server/config.properties (open the config.properties file with a text editor, make the change and save it). The default is jack.server.max-service=4.
    * If experiencing out of memory issues/stalls etc. building with jack-server/Java and you have a swap file/partition seriously consider enabling ZSWAP with lz4 compression - refer to this excellent how-to and follow it exactly: http://grimore.org/linux/zswap

    Then to build the rom, use the following commands in the LineageOS_16.0 folder, separately in order:
    . build/envsetup.sh && croot - then, when it's completed
    brunch peregrine - where the rom build actually takes place

    Your rom zip file will be found in the out > target > product > peregrine folder in your LineageOS_16.0 folder.

    Once you've completed a successful build refer to the following to learn how to update the critical security patches by thealaskalinuxuser: How to manually update your custom rom source code with security updates - as I mentioned above in my previous post, it's not that difficult a process but you do have to build the rom again and test it to make sure all is in order.

    To do another build when a new security patch is posted, run the make clobber command in the LineageOS_16.0 folder to clean out the previous build and the ccache -c command to clean-up the ccache build-up before running the repo-sync --force-sync - c -j1 command again, then check the security patch date (in /build/core/version_defaults.mk) and, only if needed and you cannot repopick the security patch topic from the LineageOS Gerrit site, add the security additions/deletions (copy and paste the additions, removing the + signs, and delete the subtractions) to the relevant files and then run the build again with the . build/envsetup.sh && croot and brunch peregrine commands.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone