[ROM][OFFICIAL][Peregrine][7.X] LineageOS 14.1

Search This thread

Kayant

Senior Member
Jul 14, 2011
1,861
4,150
http%3A%2F%2Fi.imgur.com%2F2okPze5.png


LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), 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)
  • Wifi
  • Bluetooth
  • Camera ( Videos And Photos )
  • Video Playback
  • Audio ( Record and Playback )
  • Sensors
  • Flash
  • Led

Instructions :
  • Ensure your on latest twrp
  • Download the latest build and gapps if you want
  • Reboot to recovery
  • Flash the latest build and gapps(optional)
  • Reboot

Downloads :
Builds : https://download.lineageos.org/peregrine
Google Apps: http://opengapps.org

Reporting Bugs
Grab a logcat and here 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.

Credits
  • @LuK1337 : For being the boss :p :D
    For donating his server for our device builds and continued to support moto msm8226 devices
  • @luca020400 : As he is co-maintainer
  • Gabriele M for continued support
  • @Somcom3X : Help during development
  • @kaustubh88 and @crpalmer : Kernel Tree and Patches
  • Motorola : For providing the Kernel Source Code
  • CM Team


Donations :

If you have some spare bucks and want to say thanks in another way donate to these awesome people -
LuK1337: http://xdaforums.com/donatetome.php?u=5075128
luca020400: http://xdaforums.com/donatetome.php?u=5778309



XDA:DevDB Information
LineageOS, ROM for the Moto G

Contributors
Kayant, LuK1337, luca020400, skaveelicious, Somcom3X, crpalmer, Intervigil
Source Code: https://github.com/LineageOS

ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: LineageOS

Version Information
Status: Beta

Created 2016-09-26
Last Updated 2017-01-30
 
Last edited:

Kayant

Senior Member
Jul 14, 2011
1,861
4,150
Migration from cm-14.1

Regarding installation, we recommend that users wipe when switching to LineageOS, and reinstall their gapps. However, we recognize that this can be time consuming, so we are offering an EXPERIMENTAL (read as, if it fails, you’ll have to wipe anyways) solution.

Alongside the ‘weekly’ release for your supported device, we’ll provide an EXPERIMENTAL data migration build.
This build will allow you to ‘upgrade’ from CM to the signed LineageOS weekly
This build may wipe permissions (you’ll have to re-allow app permissions), but should retain all user data
This build will be watermarked with an ugly banner to ensure that you don’t permanently run this EXPERIMENTAL release, and upgrade to a normal weekly after.
The process for this installation will be as follows:
Install EXPERIMENTAL migration build on top of cm-13.0 or cm-14.1 build (don’t try to install LineageOS 13.0 on top of CM 14.1, that will not work).
Reboot
Install LineageOS weekly build
Reboot
Re-setup your application permissions
Given the EXPERIMENTAL nature of this process, we are going to remove this option in two months time.

See more here - http://lineageos.org/Update-and-Build-Prep/
 
Last edited:
  • Like
Reactions: FabTheZen and 239

Lurker-Observer

Senior Member
May 6, 2015
74
18
Hi guys!

I just wanted to tell my "way" of encrypting the device from 0.

- Flash TWRP, flash Cyanogenmod (and GApps) and other zips if you would like to.
- Reboot your Android to Bootloader.
- Flash CM Recovery (any Nightly or Stable version)
- Boot your Android to Recovery JUST AFTER THE FLASH (so you don't do twice the next step)
- In CM Recovery use the Factory Data Reset.
- Wait then reboot to system.
- Encrypt your phone.
- Reboot to Bootloader then flash TWRP (or your Recovery of choise, if you would like to) and done.

This will obviously delete the data.

The phone doesn't ask for passcode/pattern?
Change/re-enter your passcode/pattern then choose the ask for passcode on reboot.

Hope this helps, encryption is a must for security and awesome if your device gets stolen, I hope I'm helping, thanks for the new thread!
 
Last edited:

LuK1337

Recognized Developer
Jan 18, 2013
8,940
18,141
Samsung Galaxy S III I9300
Moto G 2014
Hi guys!

I just wanted to tell my "way" of encrypting the device from 0.

- Flash TWRP, flash Cyanogenmod (and GApps) and other zips if you would like to.
- Reboot your Android to Bootloader.
- Flash CM Recovery (any Nightly or Stable version)
- Boot your Android to Recovery JUST AFTER THE FLASH (so you don't do twice the next step)
- In CM Recovery use the Factory Data Reset.
- Wait then reboot to system.
- Encrypt your phone.
- Reboot to Bootloader then flash TWRP (or your Recovery of choise, if you would like to) and done.

This will obviously delete the data.

The phone doesn't ask for passcode/pattern?
Change/re-enter your passcode/pattern then choose the ask for passcode on reboot.

Hope this helps, encryption is a must for security and awesome if your device gets stolen, I hope I'm helping, thanks for the new thread!

Want an easier way to do it?
1. Flash CM, gapps, whatever.
2. `fastboot -w`
3. Encrypt your device
4 Profit?
 

Kayant

Senior Member
Jul 14, 2011
1,861
4,150
In terms of installing CM without wiping data I just tried to install it coming from a CM13 install and it seemed to go fine minus Phone still crashing but everything else seems ok.

Now before I installed it I wiped Settings Storage, Call Log backup, Phone and Messaging Storage just to be safe but I still ended up with Phone app Fc. In order to fix that I deleted the Phone app via a file manager(root/system/priv-app/Dialer) then rebooted and finally rebooted again into recovery and reinstall the rom which fixed the phone app crashing. Alternatively you could just delete or freeze the phone app and download same one from the Play store
or an alternative Dialer app.
Now we're talking! Thanks a lot @Kayant
It's unbelievable to have such an stable ROM this early!
Hey I just made the thread and posts some links. @luca020400 @LuK1337 Gabriele M are the ones doing the real work :D
 
Last edited:

pjconoso

Member
Jul 27, 2015
21
11
Build 28-09-2016 has a recurring crash on exchange services even if you select mute.

EDIT: Reverted back to 27-09-2016, and it keeps on happening now. Both flash attempts were dirty though. Will try a clean install.
EDIT: The exchange error only happened once on build 27-09 after I reverted so I stuck to it. So far so good.
 
Last edited:

sebaalbo98

Member
Mar 19, 2015
47
28
25
Copiapo
You can not change the value night mode, returns to the default value ... And some are heard something cut to the top..

.....edit.....
Today in version 29, mail and Exchange services force close when starting
 
Last edited:

pjconoso

Member
Jul 27, 2015
21
11
You can not change the value night mode, returns to the default value ... And some are heard something cut to the top..

.....edit.....
Today in version 29, mail and Exchange services force close when starting

Strange, I had that problem on the 28th but it went away when I went back to 27th. No issues with 29 so far.
 

Lurker-Observer

Senior Member
May 6, 2015
74
18
The ROM's been awesome, it looks like I have the same issue with YouTube App (minimizing the video inside the App turns to black)
I can't use the flashlight, I've been trying the fix someone said in the other thread, but nothing.
Also I don't know if it only happens to me, but downloading a thing using Chrome (I know it uses Download Manager) tends to cancel the downloads in background, it's not a internet issue.

Keep the good work!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 71
    http%3A%2F%2Fi.imgur.com%2F2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), 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)
    • Wifi
    • Bluetooth
    • Camera ( Videos And Photos )
    • Video Playback
    • Audio ( Record and Playback )
    • Sensors
    • Flash
    • Led

    Instructions :
    • Ensure your on latest twrp
    • Download the latest build and gapps if you want
    • Reboot to recovery
    • Flash the latest build and gapps(optional)
    • Reboot

    Downloads :
    Builds : https://download.lineageos.org/peregrine
    Google Apps: http://opengapps.org

    Reporting Bugs
    Grab a logcat and here 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.

    Credits
    • @LuK1337 : For being the boss :p :D
      For donating his server for our device builds and continued to support moto msm8226 devices
    • @luca020400 : As he is co-maintainer
    • Gabriele M for continued support
    • @Somcom3X : Help during development
    • @kaustubh88 and @crpalmer : Kernel Tree and Patches
    • Motorola : For providing the Kernel Source Code
    • CM Team


    Donations :

    If you have some spare bucks and want to say thanks in another way donate to these awesome people -
    LuK1337: http://xdaforums.com/donatetome.php?u=5075128
    luca020400: http://xdaforums.com/donatetome.php?u=5778309



    XDA:DevDB Information
    LineageOS, ROM for the Moto G

    Contributors
    Kayant, LuK1337, luca020400, skaveelicious, Somcom3X, crpalmer, Intervigil
    Source Code: https://github.com/LineageOS

    ROM OS Version: 7.x Nougat
    ROM Kernel: Linux 3.4.x
    Based On: LineageOS

    Version Information
    Status: Beta

    Created 2016-09-26
    Last Updated 2017-01-30
    13
    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:

    <?xml version="1.0" encoding="UTF-8"?>
    <manifest>
    <project name="LineageOS/android_device_motorola_peregrine" path="device/motorola/peregrine" remote="github" revision="cm-14.1" />
    <project name="LineageOS/android_device_motorola_msm8226-common" path="device/motorola/msm8226-common" remote="github" revision="cm-14.1" />
    <project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-14.1" />
    <project name="LineageOS/android_kernel_motorola_msm8226" path="kernel/motorola/msm8226" remote="github" revision="cm-14.1" />
    <project name="TheMuppets/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="cm-14.1" />
    <project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="cm-14.1"/>
    </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 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 or higher versions (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


    Note: If Building on an Ubuntu 22.04 or higher versions (e.g., Linux Mint 21.1) or newer based Linux versions show the content of the following:
    You will most likely run into YYLLOC definition errors in the kernel build process during the build. In order to avoid this, the working solution is to install gcc-9 & g++-9. Refer to the following article to install the needed versions and use the Switch Manager to set the default version of GCC to 9: https://linuxconfig.org/how-to-swit...-versions-on-ubuntu-22-04-lts-jammy-jellyfish


    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_14.1 with the following command:
    repo init -u git://github.com/LineageOS/android.git -b cm-14.1

    To add the roomservice.xml file
    above to the .repo folder (Note: if the .repo folder is not visible in your LineageOS_14.1 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_14.1 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).

    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 -Xms4G -Xmx4G" Then update your environment using this command: source ~/.profile
    - Note: If running very low ram (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).
    * 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_14.1 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_14.1 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_14.1 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, if needed, 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.
    13
    Just so you are aware the next nightly should provide a upgrade path for people from previous CM versions(i.e CM13 to 14.1) without the need to wipe data. Will test it tomorrow to confirm it.

    Also to note of course you will need to flash a 7.1 Gapps if you use Gapps.

    Thanks to those commits - https://review.cyanogenmod.org/#/q/topic:db-upgrade
    13
    Tip: If you want to be able to flash latest CM14.1 updates you need to update your twrp.
    ~ https://dl.twrp.me/peregrine
    13
    For those of you wishing to update to the APRIL '20 Security Patches, I've uploaded one of my unofficial builds that is based off the official build files with the latest security patches added (refer to post # 1243 for further elucidation). I review and test these patches in LineageOS Gerrit when they're posted, before uploading for your personal use.

    Note: Requires Full Clean Flash when installing rom for 1st time from an official build or encrypting for first time - in TWRP wipe Cache, Dalvik cache, System and importantly format Data > Yes before flashing the appropriate Open Gapps - reboot, encrypt if desired, then in TWRP install preferred root (latest Magisk version recommended) and Xposed, if desired as well. 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.

    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, preferred root & Xposed (if required).

    Re: Encryption issues - use twrp-3.1.0-0-peregrine or twrp-3.1.1-0-peregrine. I've tested them and they work. Note: Refer to post # 1274 by @pigeons9 (and remember to hit the Thanks button at the bottom of his post if it helps) for a possible solution to solving encryption issues with newer TWRP versions.

    Download Link for lineage-14.1-20200407-UNOFFICIAL-peregrine.zip:
    Link: https://mega.nz/file/0P52nYIa#_xbF1Bwvq8ILi5oLDtPmg200TqInfW1_howzKHlt1nA

    I do, however, continue to recommend you learn to build it yourselves: refer to post # 1210 for the full build instructions.