FORUMS
Remove All Ads from XDA

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

1,853 posts
Thanks Meter: 4,139
 
By Kayant, Senior Member on 26th September 2016, 11:12 AM
Post Reply Email Thread
Announcement from Kayant: LineageOS? Lineage!!!


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
    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://forum.xda-developers.com/dona....php?u=5075128
luca020400: http://forum.xda-developers.com/dona....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
The Following 59 Users Say Thank You to Kayant For This Useful Post: [ View ] Gift Kayant Ad-Free
 
 
26th September 2016, 11:12 AM |#2  
OP Senior Member
Thanks Meter: 4,139
 
More
Migration from cm-14.1
Quote:

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/
The Following 2 Users Say Thank You to Kayant For This Useful Post: [ View ] Gift Kayant Ad-Free
26th September 2016, 01:03 PM |#3  
aha360's Avatar
Senior Member
Thanks Meter: 223
 
More
...and in case anyone wants to install Google Camera for Android Nougat as a System app that will survive dirty flashes, here's a flashable ZIP that will do just that:

https://1drv.ms/u/s!Agj5mSliZ57FhkYpkeioCOfZIY_b
The Following 5 Users Say Thank You to aha360 For This Useful Post: [ View ] Gift aha360 Ad-Free
26th September 2016, 01:32 PM |#4  
LuK1337's Avatar
Recognized Developer
Flag Zamość
Thanks Meter: 8,966
 
Donate to Me
More
Replace the banner with that one, Kayant.
http://i.imgur.com/ZaPMuiW.png
The Following 6 Users Say Thank You to LuK1337 For This Useful Post: [ View ]
26th September 2016, 04:03 PM |#5  
Junior Member
Flag Cadiz
Thanks Meter: 3
 
More
How's it going?
26th September 2016, 04:13 PM |#6  
Member
Thanks Meter: 18
 
More
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!
26th September 2016, 04:38 PM |#7  
LuK1337's Avatar
Recognized Developer
Flag Zamość
Thanks Meter: 8,966
 
Donate to Me
More
Quote:
Originally Posted by Lurker-Observer

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?
The Following 3 Users Say Thank You to LuK1337 For This Useful Post: [ View ]
26th September 2016, 04:49 PM |#8  
Senior Member
Thanks Meter: 64
 
More
Is there any way to see the changelog between versions?
26th September 2016, 06:18 PM |#9  
Member
Flag Copiapo
Thanks Meter: 28
 
Donate to Me
More
Nice post
26th September 2016, 08:03 PM |#10  
Member
Flag Governador Valadares
Thanks Meter: 7
 
More
adb is not working here... I cant get the device to authorize my computer. Is there some workaround or fix?
26th September 2016, 08:14 PM |#11  
LuK1337's Avatar
Recognized Developer
Flag Zamość
Thanks Meter: 8,966
 
Donate to Me
More
Quote:
Originally Posted by Eddie_53

adb is not working here... I cant get the device to authorize my computer. Is there some workaround or fix?

Wait for tomorrow's build.
The Following 7 Users Say Thank You to LuK1337 For This Useful Post: [ View ]
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes