{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Introduction
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.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
What's working
It boots!
Display, touch
Audio
USB
Wi-Fi
Bluetooth
RIL (IMS / VoLTE untested)
Camera (buggy)
NFC
Fingerprint scanner - Oreo modem firmware required
GPS
OTG
FM Radio
Treble - GSIs don't boot
Bugs
Camera (might be buggy; recording breaks after some time but should work right after a reboot)
SELinux permissive
GSIs don't boot
Installation instructions
Make sure you have: Oreo modem firmware and a 64-bit TWRP with treble and system-as-root support installed. Official TWRP by JarlPenguin recommended.
Download the ROM to the device's storage
Wipe: system, data, dalvik-cache, cache, and vendor in TWRP
Install the zip in TWRP
Install GApps if you fancy, OpenGapps recommended
If installing Magisk, reboot to recovery again first - otherwise it will fail at (un)mounting /system. This is a bug either in the Magisk installer script or TWRP.
Changelog
Newest build - 2020-08-24:
Code:
* ROM sources updated
* Updated camera HAL from deen Q
** fixes HAL3 one photo bug
* Reverted rear camera libraries
** fixes green tint when using the flash
** fixes image being too dark
* Reverted QMI blobs
** should fix GPS
* Reverted netmgr
** should make mobile data work with the reverted QMI blobs
Older builds:
Code:
2020-08-16:
* Removed compass HAL
* Corrected a file path for NFC removal
* Compass permissions are now removed from XT1792 and XT1795 - might fix ro.hw.ecompass being incorrectly set
* Updated media configs from aljeter Pie
* Vendor blob updates:
** libril*, libqmi*, libmdm*, netmgrd: from deen Pie - should fix mobile data
** libmot_gpu_mapper.so: from aljeter Pie
** libchromatix_s5k3p3* and libmmcamera_s5k3p3.so: from deen Pie - fixes all kinds of camera glitches in low light conditions
** some remaining camera blobs from our stock Oreo
2020-08-14:
* Vendor blobs updated:
** Reverted netmgrd and libdiag to deen Pie
** mm-qcamera-daemon from montana stock Oreo
2020-08-13:
* Updated netmgrd blobs
* Updated thermal-engine blobs
2020-08-12:
* Initial release
Downloads
Latest build:
lineage-17.1-20200824-UNOFFICIAL-montana.zip [MediaFire]
Old builds:
lineage-17.1-20200816-UNOFFICIAL-montana.zip
lineage-17.1-20200814-UNOFFICIAL-montana.zip
lineage-17.1-20200813-UNOFFICIAL-montana.zip
lineage-17.1-20200812-UNOFFICIAL-montana.zip
Sources
(branch lineage-17.1 in all the repos)
Device tree
Kernel source
Vendor blobs
Credits
Everyone who contributed to LineageOS 17.1 for the Moto G5 - the G5S device and vendor repositories are based on sources from that project.
Kernel source is based on the moto-msm8937 repository.
Code:
* The LineageOS team
* JarlPenguin
* wiktorek140
* KalilDev
Contributors to LineageOS 17.1 for the Moto G5:
* CodeZero
* m_vaisakh
* wzedlare
* vache
* kubersharma
* TeamMex
* nonesovile96
* FelipeRizzon
* ADHILR
XDA:DevDB Information
LineageOS 17.1, ROM for the Moto G5S
Contributors
AsD Monio, The LineageOS team, JarlPenguin, wiktorek140, KalilDev, CodeZero, m_vaisakh, wzedlare, vache, kubersharma, TeamMex, nonesovile96, FelipeRizzon, ADHILR
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: stock Oreo modem firmware
Version Information
Status: Stable
Created 2020-08-12
Last Updated 2020-08-12
THIS IS AWESOME!
Seriously, you're doing gods work in this community. I'll flash it right now!
---------- Post added at 06:30 AM ---------- Previous post was at 05:37 AM ----------
OK, just flashed it and so far it is very fast! For some reason tho, the SIM card IS detected but I have "no service"... Tomorrow I'll try to remove and insert the SIM again to see if the problem solves, but I honestly don't think it will. I flashed this coming from ViperOS 6.6, and the signal was perfectly fine there. Anyways, this is a huge project and thanks again for keeping it up with the ROMs
does not load after installing xt1799-2
Mutcholoko said:
THIS IS AWESOME!
Seriously, you're doing gods work in this community. I'll flash it right now!
---------- Post added at 06:30 AM ---------- Previous post was at 05:37 AM ----------
OK, just flashed it and so far it is very fast! For some reason tho, the SIM card IS detected but I have "no service"... Tomorrow I'll try to remove and insert the SIM again to see if the problem solves, but I honestly don't think it will. I flashed this coming from ViperOS 6.6, and the signal was perfectly fine there. Anyways, this is a huge project and thanks again for keeping it up with the ROMs
Click to expand...
Click to collapse
Thanks As for the RIL, I noticed that on the first boot it says no service for a little while, I get signal shortly after the "finishing update" notification disappears. Aside from that, it works fine on my XT1794, so I can't reproduce the bug. Please flash this zip and send me a radio logcat (adb logcat -b radio). The zip will set a prop on boot (persist.vendor.radio.adb_log_on) to make libril output to the logcat. Also please start the logcat while booting because I need to know what's going on when the RIL is starting.
omonra2004 said:
does not load after installing xt1799-2
Click to expand...
Click to collapse
Sorry, but XT1799-2 is unsupported. It is like an entirely different device (montana_retcn, this ROM if for montana) and would require making a separate device tree, kernel etc. and a separate build just for it.
AsD Monio said:
Thanks As for the RIL, I noticed that on the first boot it says no service for a little while, I get signal shortly after the "finishing update" notification disappears. Aside from that, it works fine on my XT1794, so I can't reproduce the bug. Please flash this zip and send me a radio logcat (adb logcat -b radio). The zip will set a prop on boot (persist.vendor.radio.adb_log_on) to make libril output to the logcat. Also please start the logcat while booting because I need to know what's going on when the RIL is starting.
Sorry, but XT1799-2 is unsupported. It is like an entirely different device (montana_retcn, this ROM if for montana) and would require making a separate device tree, kernel etc. and a separate build just for it.
Click to expand...
Click to collapse
It is a pity that the device that you can still buy a new one is not engaged in anyone. I put the previous build LineageOS some even worked in addition to the front camera and NFC.
Nice work, I am going to test it, from our more known main Dev Jarl, I did find out this isn't treble tho
Maybe you should "Collab" in the future?
AsD Monio said:
Thanks As for the RIL, I noticed that on the first boot it says no service for a little while, I get signal shortly after the "finishing update" notification disappears. Aside from that, it works fine on my XT1794, so I can't reproduce the bug. Please flash this zip and send me a radio logcat (adb logcat -b radio). The zip will set a prop on boot (persist.vendor.radio.adb_log_on) to make libril output to the logcat. Also please start the logcat while booting because I need to know what's going on when the RIL is starting.
Sorry, but XT1799-2 is unsupported. It is like an entirely different device (montana_retcn, this ROM if for montana) and would require making a separate device tree, kernel etc. and a separate build just for it.
Click to expand...
Click to collapse
I'm using montana XT1792 and I can confirm that RIL is working, but I can't have mobile data access.
GivFNZ said:
I'm using montana XT1792 and I can confirm that RIL is working, but I can't have mobile data access.
Click to expand...
Click to collapse
Oh hey giv
Some random said:
Oh hey giv
Click to expand...
Click to collapse
Oh hey Rush
Lmfao
Some random said:
Nice work, I am going to test it, from our more known main Dev Jarl, I did find out this isn't treble tho
Maybe you should "Collab" in the future?
Click to expand...
Click to collapse
It definitely is treble, the ROM contains a vendor partition image (check the attached screenshot). It might not be fully working, we may need to tweak the VNDK or some other things in order to boot GSIs, probably move a bunch of vendor blobs around as well. And I'm pretty sure the new (well, it existed before but we didn't use it in Pie and earlier) /product partition will be an issue, since we don't have one and just put everything it's supposed to contain in /system. I have a (dumb?) idea though - use /cache, AFAIK it's only used for storing OTA packages on stock.
GivFNZ said:
I'm using montana XT1792 and I can confirm that RIL is working, but I can't have mobile data access.
Click to expand...
Click to collapse
I forgot to test that, it is (or was) broken on my device too. I fixed it right now, so I'll try to get a new build uploaded soon.
GivFNZ said:
I'm using montana XT1792 and I can confirm that RIL is working, but I can't have mobile data access.
Click to expand...
Click to collapse
Do you have "no service"?
Also, I just checked and my IMEI is 0, but that was probably my fault. But it also doesn't make sense tho, I was on ViperOS 6.6 which is Android 9 and then flashed this right after. Shouldn't be considered as a downgrade.... I'll try to flash stock and then flash this again.
---------- Post added at 02:16 PM ---------- Previous post was at 02:14 PM ----------
AsD Monio said:
It definitely is treble, the ROM contains a vendor partition image (check the attached screenshot). It might not be fully working, we may need to tweak the VNDK or some other things in order to boot GSIs, probably move a bunch of vendor blobs around as well. And I'm pretty sure the new (well, it existed before but we didn't use it in Pie and earlier) /product partition will be an issue, since we don't have one and just put everything it's supposed to contain in /system. I have a (dumb?) idea though - use /cache, AFAIK it's only used for storing OTA packages on stock.
I forgot to test that, it is (or was) broken on my device too. I fixed it right now, so I'll try to get a new build uploaded soon.
Click to expand...
Click to collapse
I have Montana too and I can't get data access too. Waiting for the build
Mutcholoko said:
Do you have "no service"?
Also, I just checked and my IMEI is 0, but that was probably my fault. But it also doesn't make sense tho, I was on ViperOS 6.6 which is Android 9 and then flashed this right after. Shouldn't be considered as a downgrade.... I'll try to flash stock and then flash this again.
Click to expand...
Click to collapse
The "no service" thing, is "normal" for now, new build later
About full custom ROMs
Make sure, that IF you dirty flash, to flash from Lineage 16
If you want to switch to this, do a [Bold]Clean Install[Bold/]
---------- Post added at 02:18 PM ---------- Previous post was at 02:17 PM ----------
AsD Monio said:
Introduction
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.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
What's working
The ROM has not been tested for very long, bugs may occur.
It boots!
Display, touch
Audio
USB
Wi-Fi
Bluetooth
RIL (IMS / VoLTE untested)
Camera
NFC
Fingerprint scanner - Oreo modem firmware required
GPS
OTG
Treble - GSIs untested
Everything else?
Bugs
SELinux permissive
Installation instructions
Make sure you have: Oreo modem firmware and a 64-bit TWRP with treble and system-as-root support installed. Official TWRP by JarlPenguin recommended.
Download the ROM to the device's storage
Wipe: system, data, dalvik-cache, cache, and vendor in TWRP
Install the zip in TWRP
Install GApps if you fancy, OpenGapps recommended
If installing Magisk, reboot to recovery again first - otherwise it will fail at (un)mounting /system. This is a bug either in the Magisk installer script or TWRP.
Changelog
Downloads
lineage-17.1-20200812-UNOFFICIAL-montana.zip [MediaFire]
Sources
(branch lineage-17.1 in all the repos)
Device tree
Kernel source
Vendor blobs
Credits
Everyone who contributed to LineageOS 17.1 for the Moto G5 - the G5S device and vendor repositories are based on sources from that project.
Kernel source is based on the moto-msm8937 repository.
XDA:DevDB Information
LineageOS 17.1, ROM for the Moto G5S
Contributors
AsD Monio, The LineageOS team, JarlPenguin, wiktorek140, KalilDev, CodeZero, m_vaisakh, wzedlare, vache, kubersharma, TeamMex, nonesovile96, FelipeRizzon, ADHILR
Source Code:https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: stock Oreo modem firmware
Version Information
Status: Stable
Created 2020-08-12
Last Updated 2020-08-12
Click to expand...
Click to collapse
What is the theme/mod you used for that altered dark mode by the way?
---------- Post added at 02:28 PM ---------- Previous post was at 02:18 PM ----------
@Asd Monio
Currently video recording is broken on any tested app. Including the stock camera
---------- Post added at 03:06 PM ---------- Previous post was at 02:28 PM ----------
@AsDMonio
Did you ever have Google Play Problems btw?
(Some apps wouldn't display)
If so, how did you fix it?
New build is uploading now, should be up in an hour or so.
Mutcholoko said:
Do you have "no service"?
Also, I just checked and my IMEI is 0, but that was probably my fault. But it also doesn't make sense tho, I was on ViperOS 6.6 which is Android 9 and then flashed this right after. Shouldn't be considered as a downgrade.... I'll try to flash stock and then flash this again.
---------- Post added at 02:16 PM ---------- Previous post was at 02:14 PM ----------
I have Montana too and I can't get data access too. Waiting for the build
Click to expand...
Click to collapse
If the IMEI does not show up (0 is probably default) then I think the mobile data fix won't help you. What exact device model do you have (XT179x)? I had to try a few different sets of RIL blobs (libril and libqmi) to get it working on mine, so maybe yours needs a different one. Also, you can try to wipe the modemst1 and modemst2 partitions (make a backup just in case). I did that on my device somewhere along the way.
Some random said:
What is the theme/mod you used for that altered dark mode by the way?
Click to expand...
Click to collapse
Swift Dark Substratum theme
Some random said:
Currently video recording is broken on any tested app. Including the stock camera
Click to expand...
Click to collapse
It turns out the updated libqmi (or libril) I used to fix the RIL also broke thermal-engine, which in turn broke recording. I tested the camera when the RIL was still fully broken, so I had no idea. Will be fixed in the new build.
Some random said:
Did you ever have Google Play Problems btw?
(Some apps wouldn't display)
If so, how did you fix it?
Click to expand...
Click to collapse
Nope, no Google Play problems here, and I never used that build. For this ROM, I used CodeZero's cedric device and vendor trees as base and those never had that problem.
AsD Monio said:
If the IMEI does not show up (0 is probably default) then I think the mobile data fix won't help you. What exact device model do you have (XT179x)? I had to try a few different sets of RIL blobs (libril and libqmi) to get it working on mine, so maybe yours needs a different one. Also, you can try to wipe the modemst1 and modemst2 partitions (make a backup just in case). I did that on my device somewhere along the way.
Click to expand...
Click to collapse
I have a XT1792, aka montana. I'll wait for your new build and see if it works. I'm guessing the problem ain't the rom itself, because now I flashed stock via Fastboot and my IMEI is non-existent there too... Anyways, thanks for your kindness
New build is up
lineage-17.1-20200813-UNOFFICIAL-montana.zip
Changelog:
Code:
* Updated netmgrd blobs
* Updated thermal-engine blobs
* ^ fixes camera
Mutcholoko said:
I have a XT1792, aka montana. I'll wait for your new build and see if it works. I'm guessing the problem ain't the rom itself, because now I flashed stock via Fastboot and my IMEI is non-existent there too... Anyways, thanks for your kindness
Click to expand...
Click to collapse
If there's no IMEI even on stock, then I'm like 90% sure there is something wrong either with the modem data in your /persist partition, or the modem cache (modemst1 and modemst2). Check that you have dhob.bin, dhob.bin.bak and shob.bin in /persist/rfs/msm/mpss. If not, then we can't do anything, but you may still be able to run the modem on whichever ROM works with the modem cache you currently have. If you do have those files, check the permissions, especially owner user and group. On my device it looks like this in adb shell:
Code:
montana:/ # ls -l /persist/rfs/msm/mpss/
total 96
drwx------ 2 vendor_rfs vendor_rfs 4096 2017-08-09 05:56 datablock
-rw------- 1 vendor_rfs vendor_rfs 16384 2017-08-09 05:56 dhob.bin
-rw------- 1 vendor_rfs vendor_rfs 16384 2017-08-09 05:56 dhob.bin.bak
drwxrwx--x 2 vendor_rfs vendor_rfs 4096 1970-11-06 01:44 mot_rfs
-rw------- 1 vendor_rfs vendor_rfs 5 2020-08-13 18:31 server_check.txt
-rw------- 1 vendor_rfs vendor_rfs 43695 2017-09-01 09:38 shob.bin
montana:/ # id vendor_rfs
uid=2903(vendor_rfs) gid=2903(vendor_rfs) groups=2903(vendor_rfs), context=u:r:magisk:s0
montana:/ #
^ So if it doesn't say vendor_rfs vendor_rfs for those files you should run: chown 2903:2903 /persist/rfs/msm/mpss/{d,s}hob.bin*
If you have the files and setting permissions doesn't help on stock (Oreo, because Nougat had different user and group IDs), try wiping the modem cache in TWRP (adb shell or terminal):
Code:
# to backup to internal storage:
dd if=/dev/block/bootdevice/by-name/modemst1 of=/data/media/0/modemst1.img
dd if=/dev/block/bootdevice/by-name/modemst2 of=/data/media/0/modemst2.img
# to backup to external microSD:
dd if=/dev/block/bootdevice/by-name/modemst1 of=/external_sd/modemst1.img
dd if=/dev/block/bootdevice/by-name/modemst2 of=/external_sd/modemst2.img
# to wipe:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
AsD Monio said:
New build is up
lineage-17.1-20200813-UNOFFICIAL-montana.zip
Changelog:
If there's no IMEI even on stock, then I'm like 90% sure there is something wrong either with the modem data in your /persist partition, or the modem cache (modemst1 and modemst2). Check that you have dhob.bin, dhob.bin.bak and shob.bin in /persist/rfs/msm/mpss. If not, then we can't do anything, but you may still be able to run the modem on whichever ROM works with the modem cache you currently have. If you do have those files, check the permissions, especially owner user and group. On my device it looks like this in adb shell:
^ So if it doesn't say vendor_rfs vendor_rfs for those files you should run: chown 2903:2903 /persist/rfs/msm/mpss/{d,s}hob.bin*
If you have the files and setting permissions doesn't help on stock (Oreo, because Nougat had different user and group IDs), try wiping the modem cache in TWRP (adb shell or terminal):
Click to expand...
Click to collapse
deleted
Reason:
Turns out my carrier is an asshole and locked me out for not having filled up using a 5$ card :|
@Some random Actually, you're right, mobile data is broken for me as well again. It must be this thermal-engine messing with the new netmgrd (once again, I tested mobile data before fixing the camera with the broken thermal-engine). I've updated the posts, I'm going to find a version that works and update again soon.
AsD Monio said:
@Some random Actually, you're right, mobile data is broken for me as well again. It must be this thermal-engine messing with the new netmgrd (once again, I tested mobile data before fixing the camera with the broken thermal-engine). I've updated the posts, I'm going to find a version that works and update again soon.
Click to expand...
Click to collapse
Wait, but it works for my friend (Giv)
Tf
Wait do you have XT1794 too? (RetEU, Europe Model)
AsD Monio said:
New build is up
lineage-17.1-20200813-UNOFFICIAL-montana.zip
Changelog:
Code:
* Updated netmgrd blobs
* Updated thermal-engine blobs
* ^ fixes camera
If there's no IMEI even on stock, then I'm like 90% sure there is something wrong either with the modem data in your /persist partition, or the modem cache (modemst1 and modemst2). Check that you have dhob.bin, dhob.bin.bak and shob.bin in /persist/rfs/msm/mpss. If not, then we can't do anything, but you may still be able to run the modem on whichever ROM works with the modem cache you currently have. If you do have those files, check the permissions, especially owner user and group. On my device it looks like this in adb shell:
Code:
montana:/ # ls -l /persist/rfs/msm/mpss/
total 96
drwx------ 2 vendor_rfs vendor_rfs 4096 2017-08-09 05:56 datablock
-rw------- 1 vendor_rfs vendor_rfs 16384 2017-08-09 05:56 dhob.bin
-rw------- 1 vendor_rfs vendor_rfs 16384 2017-08-09 05:56 dhob.bin.bak
drwxrwx--x 2 vendor_rfs vendor_rfs 4096 1970-11-06 01:44 mot_rfs
-rw------- 1 vendor_rfs vendor_rfs 5 2020-08-13 18:31 server_check.txt
-rw------- 1 vendor_rfs vendor_rfs 43695 2017-09-01 09:38 shob.bin
montana:/ # id vendor_rfs
uid=2903(vendor_rfs) gid=2903(vendor_rfs) groups=2903(vendor_rfs), context=u:r:magisk:s0
montana:/ #
^ So if it doesn't say vendor_rfs vendor_rfs for those files you should run: chown 2903:2903 /persist/rfs/msm/mpss/{d,s}hob.bin*
If you have the files and setting permissions doesn't help on stock (Oreo, because Nougat had different user and group IDs), try wiping the modem cache in TWRP (adb shell or terminal):
Code:
# to backup to internal storage:
dd if=/dev/block/bootdevice/by-name/modemst1 of=/data/media/0/modemst1.img
dd if=/dev/block/bootdevice/by-name/modemst2 of=/data/media/0/modemst2.img
# to backup to external microSD:
dd if=/dev/block/bootdevice/by-name/modemst1 of=/external_sd/modemst1.img
dd if=/dev/block/bootdevice/by-name/modemst2 of=/external_sd/modemst2.img
# to wipe:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
Click to expand...
Click to collapse
Camera crashes when I set to video mode. I didn't have problems with RIL anymore.
Related
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.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
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. You will need to provide your own Google Applications package (gapps). 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 our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for official LineageOS 14.1 builds for Huawei G620s/Honor 4/4x(msm8916). The following will not be supported here:
Custom kernels
Mods
Xposed
Supported device:
C8817D
C8817E
G620S-UL00
G620S-L01/L02/L03
G621-TL00
Che1_CL10
Che1_CL20
Che1_L04
Baseband requirement:
If you can't hang up, install this baseband via TWRP and it should be solved.
We don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Known bugs:
No NFC support Done by Blefish
For some users, you may meet some stability issues(related to your EMUI base)
Installation:
First time flashing LineageOS 14.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery, e.g., my TWRP: https://forum.xda-developers.com/honor-4x/development/recovery-twrp-3-0-0-0-touch-recovery-t3309504
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package, install the SU addon package(https://download.lineageos.org/extras, choose arm)
Reboot
Source code:
https://github.com/lineageos
Credits:
LineageOS Team & Contributors
Code Aurora Forum
Blefish (This won't happen without his remarkable work!)
......
Download:
Che1-CL10: https://download.lineageos.org/che10
Others: https://download.lineageos.org/cherry
XDA:DevDB Information
LineageOS, ROM for the Honor 4x
Contributors
dianlujitao, blefish
Source Code: https://github.com/lineageos
ROM OS Version: 7.x Nougat
Version Information
Status: Nightly
Created 2017-01-30
Last Updated 2017-03-21
@dianlujitao @Blefish
great job !! thank you very much !!:good:
edit : The installation fails if you mark the signature verification in TWRP.
Is Volte/IMS feature enabled?
custon3 said:
@dianlujitao @Blefish
great job !! thank you very much !!:good:
edit : The installation fails if you mark the signature verification in TWRP.
Click to expand...
Click to collapse
That option has to be unmarked, that error occurs in all roms. :good:
I've flashed the su binary attached here. But I can't get root privileges. What to do ?
GLokin666 said:
That option has to be unmarked, that error occurs in all roms. :good:
Click to expand...
Click to collapse
In Roms CM 12.1/13.0 and Mokee 60.1/71.1 verifies the signature without failures.
---------- Post added at 06:03 PM ---------- Previous post was at 05:52 PM ----------
gvrgvr said:
I've flashed the su binary attached here. But I can't get root privileges. What to do ?
Click to expand...
Click to collapse
Enables administrative access in the development menu
There is a very big problem when the wi fi signal is low, then reset the phone and it happens very often.
The rest is very good.
Great. A build is finally here. I had been having problems recently with the cm13 and was waiting for a lineage os. But didn't think it'd be this soon.
But before I switch, I just want to confirm, is it stable? Or do you suggest I should wait for a more stable version?
If anyone has tried please comment your views about this rom.
Thank you in advance!
gvrgvr said:
I've flashed the su binary attached here. But I can't get root privileges. What to do ?
Click to expand...
Click to collapse
Interesting! Flashing su binaries enabled the option, to enable/disable root privileges under developer settings. I see the root privileges.
---------- Post added at 10:14 PM ---------- Previous post was at 10:12 PM ----------
I couldn't see the VoLTE feature anywhere... May I know by when we can see the VoLTE enabled in the ROM ?
https://download.lineageos.org/extras
Embeddednut said:
Interesting! Flashing su binaries enabled the option, to enable/disable root privileges under developer settings. I see the root privileges.
---------- Post added at 10:14 PM ---------- Previous post was at 10:12 PM ----------
I couldn't see the VoLTE feature anywhere... May I know by when we can see the VoLTE enabled in the ROM ?
Click to expand...
Click to collapse
I think you misunderstood what I said. I was able to enable the root after flashing the su binaries.
But one think I would like to know is as how can we know if Volte is enabled into the ROM without even flashing it. Any suggestions are welcome.
Flashed the su from link.
Saw the root privileges in dev options.
Enabled it.
Opened es file explorer pro. Enabled root explorer.
Asked for root permissions. Gave the permissions.
It says "test failed. It won't work in this device"
What to do ???
What if I flash supersu 2.79 instead of su included in lineage os page ??
dianlujitao said:
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.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
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. You will need to provide your own Google Applications package (gapps). 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 our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for official LineageOS 14.1 builds for OnePlus 3. The following will not be supported here:
Custom kernels
Mods
Xposed
Supported device:
C8817D
C8817E
G620S-UL00
G620S-L01/L02/L03
G621-TL00
Che1_CL10
Che1_CL20
Che1_L04
Baseband requirement:
If you can't hang up, install this baseband via TWRP and it should be solved.
We don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Known bugs:
No NFC support
For some users, you may meet some stability issues(related to your EMUI base)
Installation:
First time flashing LineageOS 14.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery, e.g., my TWRP: https://forum.xda-developers.com/honor-4x/development/recovery-twrp-3-0-0-0-touch-recovery-t3309504
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package, install the SU addon package(https://download.lineageos.org/extras, choose arm)
Reboot
Source code:
https://github.com/lineageos
Credits:
LineageOS Team & Contributors
Code Aurora Forum
Blefish (This won't happen without his remarkable work!)
......
Download:
Che1-CL10: https://download.lineageos.org/che10
Others: https://download.lineageos.org/cherry
XDA:DevDB Information
LineageOS, ROM for the Honor 4x
Contributors
dianlujitao, blefish
Source Code: https://github.com/lineageos
ROM OS Version: 7.x Nougat
Version Information
Status: Nightly
Created 2017-01-30
Last Updated 2017-01-30
Click to expand...
Click to collapse
What about the camera? does it have the pro mode to manually adjust focal length, exposure, etc?
data is not working
shubham412302 said:
data is not working
Click to expand...
Click to collapse
Check the configuration of your APN ,to me they work correctly in both 3G and 4G.
Great job！But it often randomly auto reboots..
Can we have VoLTE patch for Honor 4X just like we have for Redmi note 3.
Please see the details of this patch at below link https://forum.xda-developers.com/re...t/volte-patches-nougat-based-cm-roms-t3509257
fix random reboot (wifi and data) after enable/disable airplane mode @Blefish @dianlujitao https://github.com/mparus/android_k...mmit/ef53d6fb757f10f338ebcdcbec14af04e89412c3
Jenkins again failed in build !! two failures of three build !!
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.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
BUG REPORTS / KNOWN ISSUES
https://jira.lineageos.org
- IR: not supported
- Fingerprint: Fingerprint will crash/reboot on first boot. After this glitch should be fine.
GOT QUESTIONS?
http://wiki.lineageos.org/zl1_info.html
3rd PARTY ADDONS/MODS
While we have no issues with people using supersu/magisk/xposed/custom kernels/etc, we can't provide support for users who have them installed.
HOW TO INSTALL LINEAGEOS
- Make sure your phone is running 19S bootloader or higher
- Download the LineageOS zip(s). (see Downloads)
- Copy the LineageOS zip to internal sdcard.
- Unlock bootloader and install TWRP. (see Downloads)
- Boot into TWRP.
- Perform a backup of your current ROM. (Optional)
- IMPORTANT: Do a Factory Reset. (Wipe data & cache)
- Flash LineageOS.
- Optional: Install the Google Apps addon package. (see Downloads)
- Reboot
Click to expand...
Click to collapse
HOW TO INSTALL TWRP
- Enable developer options
- Allow oem unlock
- Power off
- Hold Volume down + Power for Fastboot mode
- fastboot oem unlock-go
- fastboot flash recovery twrp.img
- fastboot boot twrp.img
Click to expand...
Click to collapse
DOWNLOADS
LineageOS:
https://download.lineageos.org/zl1
Google Apps:
http://opengapps.org/ (recommended: ARM64, 7.1, nano)
SU-Addon:
https://download.lineageos.org/extras
TWRP-Recovery:
https://dl.twrp.me/zl1/
SOURCECODE
Device tree: https://github.com/LineageOS/android_device_leeco_zl1
Kernel: https://github.com/LineageOS/android_kernel_leeco_msm8996
HOW TO CONTRIBUTE
Use our code review system to send patches: https://review.lineageos.org
XDA:DevDB Information
LineageOS 14.1 Weekly Bulids (X710/X727, zl1, pro3), ROM for the LeEco Le Pro3
Contributors
jrior001, codeworkx
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Beta
Beta Release Date: 2017-03-18
Created 2017-03-19
Last Updated 2018-02-25
All, please keep in mind moving between official & unnoficial builds of any version requires a full wipe/clean flash
Omg a god. 7.1.1 with camera for the beast
Seems to be amazing:cyclops:
Gonna try it today,
Thanks
Amazing work guys! Rom runs amazing!
How is the camera app? It was pretty bad for me on the 13 LOS.
Anyone else have the crash when setting up the fingerprint in the initial setup?
thesingh603 said:
Anyone else have the crash when setting up the fingerprint in the initial setup?
Click to expand...
Click to collapse
For many ROMs, that's a scheduled reboot that's needed for configuring the fingerprint sensor. Its normal.
---------- Post added at 03:38 AM ---------- Previous post was at 03:31 AM ----------
Also, wouldn't the 7.1 GAPPS be needed, not 6.0?
thesingh603 said:
Anyone else have the crash when setting up the fingerprint in the initial setup?
Click to expand...
Click to collapse
Yes, will update op. Likely will crash once and be fine. Forgot that still happens on clean install.
Sent from my LEX727 using Tapatalk
Some confusion with this thread.
Topic says Official but file says Unofficial.
Gapps recommendation says to use 6.0.
xiton said:
Some confusion with this thread.
Topic says Official but file says Unofficial.
Gapps recommendation says to use 6.0.
Click to expand...
Click to collapse
Cleaned up.
I tried to install 7.1 Arm 64 gapps Pico launcher is crashing on boot constantly.
---------- Post added at 03:38 AM ---------- Previous post was at 03:31 AM ----------
[/COLOR]Also, wouldn't the 7.1 GAPPS be needed, not 6.0?[/QUOTE]
That's what I thinking. Does it work with 7.1 gapps?
Installed with aroma. No issues yet. Will report standby drain tomorrow
benjmiester said:
---------- Post added at 03:38 AM ---------- Previous post was at 03:31 AM ----------
[/COLOR]Also, wouldn't the 7.1 GAPPS be needed, not 6.0?
Click to expand...
Click to collapse
That's what I thinking. Does it work with 7.1 gapps?[/QUOTE]
Clean flash... I have been running since this morning and 0 issues
Its Gapps 7.1 arm64..I used pico
Wooohoo. Cant wait to try. Congrats guys, and a big thank you.
goood morning, i know this version is quite new. But is it suitable for daily use? Or much bugs?
Should i use instead LineageOS 13.0 instead of this one for some time ?
Keep up the good work you both!!
I used gapps 7.1 and it's working fine.
andiak said:
goood morning, i know this version is quite new. But is it suitable for daily use? Or much bugs?
Should i use instead LineageOS 13.0 instead of this one for some time ?
Click to expand...
Click to collapse
No bugs at all
Wonderful rom
Code:
** Disclaimer
I am not responsible if flashing this ROM bricks your
phone or causes thermonuclear war and ends the
world as we know it. You have been warned.
ROM Information
ROM Target Device: Samsung Galaxy J5 SM-J5008 | SM-J500H | SM-J500F/G/M/Y | SM-J500FN
ROM Status: Stable
ROM OS: LineageOS 14.1
Project GitHub Repositories: https://github.com/Galaxy-MSM8916
Project Gerrit Review site: https://review.msm8916.com/
Telegram Channel (for ROM build/completion notifications): https://telegram.me/Samsung_MSM89XX
Telegram Group (for Q&A): https://telegram.me/joinchat/AJrZvz_pGY7Pvfis9kzMwA
Bug reports: https://bugs.msm8916.com/
Click to expand...
Click to collapse
Device Names
Verify your device codename before downloading any firmwares or recovery images!
Code:
[B]SM-J500F/G/M/Y[/B] - [COLOR="DarkSlateBlue"][B]j5lte[/B][/COLOR]
[B]SM-J5008[/B] - [COLOR="DarkSlateBlue"][B]j5ltechn[/B][/COLOR]
[B]SM-J500FN[/B] - [COLOR="DarkSlateBlue"][B]j5nlte[/B][/COLOR]
[B]SM-J500H[/B] - [COLOR="DarkSlateBlue"][B]j53gxx[/B][/COLOR]
Click to expand...
Click to collapse
Download
All builds: https://download.msm8916.com/
Jenkins Builds: https://jenkins.msm8916.com/job/LineageOS_Builds/job/Samsung_Galaxy_J5/
TWRP Builds: https://jenkins.msm8916.com/job/TWRP_Builds/
GApps: http://opengapps.org/?arch=arm&variant=micro&api=7.1
RSS: https://jenkins.msm8916.com/job/LineageOS_Builds/job/Samsung_Galaxy_J5/rssLatest
Click to expand...
Click to collapse
Instructions
Installation via recovery (TWRP/LineageOS Recovery)
* Download a recent .zip file from the links above for your device.
* Reboot into recovery mode [Press Power+Volume Up+Home].
* Wipe your data and cache partition (equivalent to doing a Factory Reset)
if you are coming from a stock ROM.
* Either: Plug in your phone into your computer, copy the zip file to a location on your Internal or External Storage on a device, click Install on TWRP on your phone and locate the zip file in the phone, or:
* Plug in your phone into your computer, and open Advanced->ADB Sideload on TWRP on your phone and swipe the slider to enter sideload mode.
Then open a command prompt/terminal on your computer in the folder you put the file by Shift-Clicking (Shift+Right Click) and selecting "Open Command Prompt/Terminal Here" (you will need to have adb installed) and type:
adb sideload name_of_zip.zip
to sideload the file. Replace name_of_zip.zip with the name of the file. If you are running Linux you may need to type adb kill-server and use sudo adb sideload if you get an `Insufficient Permissions` error.
* Download and flash GApps in the same way.
Click to expand...
Click to collapse
How to provide logcats
Under Windows:
Code:
[B]* Install samsung device drivers and then
the adb utils from here:[/B]
[url]https://forum.xda-developers.com/showthread.php?t=2588979[/url]
[b]* Then enable developer mode, connect your phone to usb,
and from [B]cmd[/B] paste this command:[/b]
[I]adb logcat > %userprofile%/Desktop/logcat.txt[/I]
[b]then try to reproduce the bug.[/b]
[b]* The logcat file will be on your desktop.[/b]
Under Linux:
Code:
[b]* Install the adb utils from your distribution's
package manager and execute the command:[/b]
[I]adb logcat > ~/logcat.txt[/I]
[b]then try to reproduce the bug.[/b]
[b]* The logcat file will be on your home directory.[/b]
* Create a bug report at https://bugs.msm8916.com/ and paste the logcat there.
* If you cant connect the device through adb on windows because the drivers, connect the device over wifi, enable adb over network on the quick setting tiles, and type:
Code:
adb connect [ip address here]
And then the adb logcat command for windows.
Click to expand...
Click to collapse
Features
Code:
[B]
* Supports both MM/LL bootloaders.
* OMS/Substratum theming support.
* The usual LineageOS features.
* All builds support over-the-air updates.
[/B]
FAQ
Q: Are you taking device requests?
A: If and only if the device is using an msm8916 chip, and you're willing to buy me/donate the device for testing, sure.
Q: But I don't have that kind of money! What else?
A: Alternatively, if you're skilled with Linux and adb, and have an unsupported device, if you're willing to work with me as a tester, that works as well.
Q: Are you accepting feature requests?
A: Unless you're willing to implement it yourself, no.
Q: Can you make XXX ROM as well as LOS?
A: Unless more people donate, no. I simply don't have the time to maintain more than LOS nor money to hold that many ROMs on my already (tiny) struggling server.
Q: Can I throw money at you?
A: Most certainly. Donations are always welcome.
Click to expand...
Click to collapse
You want to help?
We need hardware power to get the builds done.
If you want to help us go faster, send a PM to @kentone or
@vince2678. Your computer will act as a client for our jenkins server.
In a perfect world, that would be all, but unfortunately no. We need money to keep the server running and keep bringing these ROMs.
As always, logcat any problem you find.
Click to expand...
Click to collapse
PLEASE, don't PM @vince2678, as he's busy right now, and your questions can be not answered. PM @kentone instead, write here on the post, or on the telegram group, your questions will be responded as soon as we can Understand that we have family, studies and jobs aside of this project. Thanks for your understanding
XDA:DevDB Information
[UNOFFICIAL][OMS][ROM] LineageOS 14.1 for Galaxy J5 [SM-J5008/H/F/FN/G/M/Y], ROM for the Samsung Galaxy J5
Contributors
vince2678, minz1
Source Code: https://github.com/Galaxy-MSM8916
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: >= 5.0.x Lollipop
Based On: LineageOS
Version Information
Status: Stable
Created 2017-04-12
Last Updated 2018-08-10
Changelog
For more detailed changelog information, see the changelog on the download or jenkins servers for each specific build.
Code:
[B][U]11/09/2017[/U][/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Rear camera focus and flash should be working in the latest builds. [/B]
Code:
[B][U]29/08/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Added KeyDisabler. For devices with touch keys controlled separately
from the touch screen, this means that the virtual Nav Bar
can be enabled in the Settings. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Shifted to using a kernel driver for disabling touch devices
when the screen is off instead of a user service for that. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Updated kernel to the latest upstream AOSP and
CAF tags. There should be a noticeable performance boost. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Shifted to using OSS GPS code instead of prebuilt libs.
Location applications should be getting and reporting
satellite fix information properly. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Disabled cpusets support, which was slowing
down the system performance. [/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] The auto time zone feature should now be working
proper, (that is, without resetting the time zone
to 0000 UTC).[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Data should be working fully on all devices. [/B]
Code:
[B][U]22/08/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B]Updated xda post to include F/FN devices [/B]
Code:
[B][U]08/06/2017[/U][/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Video recording should now be working [/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] The "message not sent" bug in text messaging
app(s) should be gone. [/B]
Code:
[B][U]01/06/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and prima (wifi)
driver to the latest caf branch LA.BR.1.2.9_rb1.18[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] The reboots caused by errors in the
prima kernel driver should be gone.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] F2FS should work completely now.
Updated F2FS code from upstream kernel sources and enabled
security extended attribute support (for SElinux) to fix
android support.[/B]
Code:
[B][U]15/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Wifi driver is now built-into the kernel again.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B][B] The sleep issue should be fixed in the latest build.
This was due to the failure to set a critical kernel
variable at boot because the kernel init system was
not interpreting a boot command line variable correctly.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B][B] Touch screen should be disabled properly during
calls and when the screen is off.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B][B] Rotation sensor should be working properly in
the latest build.[/B]
* [B][[COLOR="Red"]FEATURE[/COLOR]][/B][B] OMS/Substratum support is now built into the
ROM.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] F2FS is enabled in-kernel, so F2FS filesystem
mounting and formatting should be working fully.[/B]
Code:
[B][U]05/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Wifi driver is being built as a module for now,
transitioning to a new kernel somehow broke the ability
to build it into the kernel binary.[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Transitioned to a new kernel based on T560NU and
J500H MM kernel sources (J500HXXU2BPJ9 and T560NUUES1BPL1). [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and wifi driver to LA.BR.1.2.9_rb1.16[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Builds now use sdcardfs from Google. This should
result in faster file operations on the sdcard overall
compared to using FUSE as an overlay.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] In-call audio should now work fully without having to
toggle the loudspeaker. [/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Brightness adjustment should be functional. [/B]
Code:
[B][U]15/07/2017[/U][/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] RIL should be fully functional. The
RIL service was not starting at boot for the second SIM. [/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Fixed support for all bootloaders.
The culprit was a hardcoded string in the bootloader
passed to the kernel, which is not recognised if the
bootloader is older than the display driver and vice-versa. [/B]
Code:
[B][U]12/07/2017[/U][/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Build first image [/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Created DevDB project [/B]
Known Issues
Code:
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
* [B][[COLOR="Red"]BUG[/COLOR]][/B] [B] USB OTG does not work [/B]
Code:
[COLOR="RoyalBlue"][B]J5008/FN[/B][/COLOR]
* [B][[COLOR="Red"]BUG[/COLOR]][/B] [B] NFC does not work [/B]
Finally a Nougat rom. Thumbs up to you man :good:
(Heck, still waiting for my thanks limit to end)
Great to see Nougat for J500H.
You are saving this device.
I'm gonna bring this up for other H users to see
Hey I own j500f but can you make a volte fix for j500h so that it can be sorted on our devices as well??
YuZaGa said:
Hey I own j500f but can you make a volte fix for j500h so that it can be sorted on our devices as well??
Click to expand...
Click to collapse
VoLTE is only for 4g(LTE) devices!
when i try to install through twrp it shows an error which goes something like this:
E3004: This package is for device: gprimelte.......this device is j5lte
updater process ended with ERROR:7
I am currently using TWRP Aroma Installer
Aadars said:
when i try to install through twrp it shows an error which goes something like this:
E3004: This package is for device: gprimelte.......this device is j5lte
updater process ended with ERROR:7
I am currently using TWRP Aroma Installer
Click to expand...
Click to collapse
This is only for H. You have another variant
Aadars said:
when i try to install through twrp it shows an error which goes something like this:
E3004: This package is for device: gprimelte.......this device is j5lte
updater process ended with ERROR:7
I am currently using TWRP Aroma Installer
Click to expand...
Click to collapse
You have a J500F and you are trying to install a Grand Prime rom? ok
Aadars said:
when i try to install through twrp it shows an error which goes something like this:
E3004: This package is for device: gprimelte.......this device is j5lte
updater process ended with ERROR:7
I am currently using TWRP Aroma Installer
Click to expand...
Click to collapse
Installing the wrong device ROM...
vince2678 said:
Installing the wrong device ROM...
Click to expand...
Click to collapse
Oh i got it ....had problem with aroma installer 3.0.2.1
Now i had succesfully installed it..hurray:angel
---------- Post added at 05:13 PM ---------- Previous post was at 05:07 PM ----------[/SIZ
---------- Post added at 05:15 PM ---------- Previous post was at 05:13 PM ----------
Just tried it and it is really awesome couple of bugs though but hope they will be shortly fixed
one of the bug is that the tile doesnt get managed if we drag it....other bugs are already mentioned by dev
Really thankful for dev for making it available for j500H
@vince2678 , typo in changelog date (it's still 2016)
There's a problem with the updater-script, if you're coming from a ported rom it'll detect different variant.
I've deleted the part that checks if the device is 3gxx. Voila.
kim said:
There's a problem with the updater-script, if you're coming from a ported rom it'll detect different variant.
I've deleted the part that checks if the device is 3gxx. Voila.
Click to expand...
Click to collapse
That's not a problem with the updater script. That's a problem with the rom you're running not being compatible with the rom you're trying to install, and happens when there's a mismatch of device strings.
vince2678 said:
That's not a problem with the updater script. That's a problem with the rom you're running not being compatible with the rom you're trying to install, and happens when there's a mismatch of device strings.
Click to expand...
Click to collapse
Okay it's not a problem in updater-script, but it detects j5lte in my j53g, maybe it's because of my current rom. But Thanks this Rom works with blazing fast performance ?
any news??
thank u bro i hope u to keep developing this rom until it be stable
3la2Hus said:
any news??
Click to expand...
Click to collapse
Look at the changelogs
UPDATE: As of today this fixes already went into LineageOS official, but keeping the thread for future reference and extra info...
PROBLEM
Some users report that their US996 and LS997 variants are only able to utilize 2 cameras in LineageOS or AOSP based ROMs.
The problem happens regardless of camera being used.
This is not the 'dark screen' capture on the Snap Camera happening on LineageOS, the problem is the 3rd camera not being active at all.
On further investigation this phones use a similar (spec wise) but different camera sensor and actuators for the 3rd camera.
DESCRIPTION
As of today (Sep-12-2017) The current LineageOS and AOSP builds that use LGE 8996 common repository are still missing some information for some variants of our beloved US996 and LS997 phones. Seems like these variants use a different camera sensor on some called the s5k2p7.
So I have decided to share my personal patches for users who might have problems with only being able to utilize 2 cameras (users whose only cameras that work are wide angle and selfie, and not the normal rear camera). I hope this is temporary and that we can get the fixes upsteam sometime soon but I am sure I can make some V20 users happy with this.
The other added benefit of using this is that this Kernel is based on CM's August version and will not have the touch-screen bug that has been recently seen and experienced on LineageOS recent automated builds.
The way it works is that in order for LineageOS or any AOSP ROM to see and activate this camera it needs a proper library and binary blobs for qcamera server. I have extracted these new'ish updated binary blobs from the US996 firmware and after doing so and flashing them on top of your ROM you should now be able to see the 3rd camera on these phones. However after patching the above it is still lacking proper Kernel support so that focusing works and hence will need to flash a re-compiled Kernel on top of your ROM to make it work.
INSTRUCTIONS
Be in recovery, if you are looking for this post you most likely already have AOSP and are facing these issues
Please just try the builds from this post #20 and flash it as @x86cpu has incorporated those fixes in this UNOFFICIAL builds
Flash the optional "flashable-snap.zip" if your Snap camera starts up black by default. This will make some users happy, this is not related to the sensor fix but it is just using an older Snap version that does proper auto shutter speed.
Reboot
KERNEL CHANGES
The changes lie in the following files that can be obtained and extracted from LG's LS997 Kernel sources:
Code:
drivers/media/platform/msm/camera_v2/sensor/actuator/msm_actuator.c
drivers/media/platform/msm/camera_v2/sensor/ois/msm_ois.c
drivers/media/platform/msm/camera_v2/sensor/ois/Makefile
drivers/media/platform/msm/camera_v2/sensor/ois/lgit_s5k2p7_rohm_ois.h
drivers/media/platform/msm/camera_v2/sensor/ois/lgit_s5k2p7_rohm_ois.c
DOWNLOADS
flashable-lge-v20-s5k2p7-eeprom-camera-libs.zip [NOT NEEDED ANYMORE, THIS IS JUST A PLACEHOLDER, READ THE INSTRUCTIONS]
flashable-snap.zip
Please just try the builds from this post #20
<< If you like my work here is my hat, please donate! >>
CHANGELOG
v1.0
Added support for US996 (Tested Kernel and libraries on two phones, all working well).
Added support for LS997 (Kernel Untested, I hope to get feedback soon).
Binary blobs based on US996 latest version of 10h.
I'll be testing it out soon as I get home. I love aosp and if all 3 cameras work it will be awesome.
Sent from my LG-LS997 using XDA-Developers Legacy app
---------- Post added at 04:48 PM ---------- Previous post was at 04:07 PM ----------
I keep getting error 1 when installing the kernel.
Sent from my LG-LS997 using XDA-Developers Legacy app
philiptibbs said:
I'll be testing it out soon as I get home. I love aosp and if all 3 cameras work it will be awesome.
Sent from my LG-LS997 using XDA-Developers Legacy app
---------- Post added at 04:48 PM ---------- Previous post was at 04:07 PM ----------
I keep getting error 1 when installing the kernel.
Sent from my LG-LS997 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks for testing for the LS997, I was explicitly waiting this to happen ... since I hadn't tested this myself on LS997. Can you check the zip and open anykernel.sh:
Change
Code:
do.devicecheck=1
to
Code:
do.devicecheck=0
Save the *.zip and reflash?
Since I used an equivalent zip I created for US996, I had used the following:
Code:
device.name1=omni_us997
device.name2=ls997
device.name3=LG-LS997
But seems like none of those names match the LS997 device, do you know what name it uses so that I can fix it properly?
Elsa is what TWRP has it for and ls997 .
Sent from my LG-LS997 using XDA-Developers Legacy app
---------- Post added at 05:44 PM ---------- Previous post was at 05:43 PM ----------
I will try in a little bit going to dinner.
Sent from my LG-LS997 using XDA-Developers Legacy app
I still get error 1 after changing the do.devicecheck=0 file ? I tried it on TWRP 3.0.2.1 and 3.1.1.0
Omar-Avelar said:
PROBLEM
Some users report that their US996 and LS997 variants are only able to utilize 2 cameras in LineageOS or AOSP based ROMs.
The problem happens regardless of camera being used.
This is not the 'dark screen' capture on the Snap Camera happening on LineageOS, the problem is the 3rd camera not being active at all.
On further investigation this phones use a similar (spec wise) but different camera sensor and actuators for the 3rd camera.
DESCRIPTION
As of today (Sep-12-2017) The current LineageOS and AOSP builds that use LGE 8996 common repository are still missing some information for some variants of our beloved US996 and LS997 phones. Seems like these variants use a different camera sensor on some called the s5k2p7.
So I have decided to share my personal patches for users who might have problems with only being able to utilize 2 cameras (users whose only cameras that work are wide angle and selfie, and not the normal rear camera). I hope this is temporary and that we can get the fixes upsteam sometime soon but I am sure I can make some V20 users happy with this.
The other added benefit of using this is that this Kernel is based on CM's August version and will not have the touch-screen bug that has been recently seen and experienced on LineageOS recent automated builds.
The way it works is that in order for LineageOS or any AOSP ROM to see and activate this camera it needs a proper library and binary blobs for qcamera server. I have extracted these new'ish updated binary blobs from the US996 firmware and after doing so and flashing them on top of your ROM you should now be able to see the 3rd camera on these phones. However after patching the above it is still lacking proper Kernel support so that focusing works and hence will need to flash a re-compiled Kernel on top of your ROM to make it work.
INSTRUCTIONS
Be in recovery, if you are looking for this post you most likely already have AOSP and are facing these issues
Flash your favorite AOSP based ROM (I recommend lineage-14.1-20170728-nightly-us996-signed.zip for US996 if you want Bluetooth working).
Flash "flashable-lge-v20-s5k2p7-eeprom-camera-libs.zip".
Flash "flashable-*-gamma-kernel-1.0.zip".
Flash the optional "flashable-snap.zip" if your Snap camera starts up black by default. This will make some users happy, this is not related to the sensor fix but it is just using an older Snap version that does proper auto shutter speed.
Reboot
KERNEL CHANGES
The changes lie in the following files that can be obtained and extracted from LG's LS997 Kernel sources:
Code:
drivers/media/platform/msm/camera_v2/sensor/actuator/msm_actuator.c
drivers/media/platform/msm/camera_v2/sensor/ois/msm_ois.c
drivers/media/platform/msm/camera_v2/sensor/ois/Makefile
drivers/media/platform/msm/camera_v2/sensor/ois/lgit_s5k2p7_rohm_ois.h
drivers/media/platform/msm/camera_v2/sensor/ois/lgit_s5k2p7_rohm_ois.c
DOWNLOADS
flashable-lge-v20-s5k2p7-eeprom-camera-libs.zip
flashable-ls997-gamma-kernel-1.0.zip
flashable-us996-gamma-kernel-1.0.zip
flashable-snap.zip
<< If you like my work here is my hat, please donate! >>
Click to expand...
Click to collapse
Do you have the exact source (against the LOS kernel) you changed? And what blobs had to be updated. I did try this adding into the LOS kernel on my us996 and blobs. Except it didn't work, nothing could open the camera any more. Kernel compiles, but not sure if I got an mis-config there or missing some blobs. https://review.lineageos.org/189552
Hey @x86cpu, thanks... So I had to do it con branch cm-14.1_20170811.
I didnt get to try it with the latest upstream, and for the blobs it is all contained un that zip (libs, and *.xml). Sorry that I cannot be more verbose as I am away from my computer.
Btw, updating the prebuilts on an already flashed system requires you to update the SELinux policies to match again:
Code:
chown root:shell /system/bin/mm-qcamera-*;
chmod 0755 /system/bin/mm-qcamera-*;
chcon -t system_file /system/bin/mm-qcamera-app;
chcon -t mm-qcamerad_exec /system/bin/mm-qcamera-daemon;
set_perm_recursive 0 0 0755 0644 /system/vendor/lib;
set_perm_recursive 0 0 0755 0644 /system/vendor/lib64;
set_perm_recursive 0 0 0755 0644 /system/etc/camera;
chmod 0644 /system/media/*.bin;
restorecon -r /system/vendor/lib;
restorecon -r /system/vendor/lib64;
restorecon -r /system/etc/camera;
restorecon -r /system/media;
Omar-Avelar said:
Hey @x86cpu, thanks... So I had to do it con branch cm-14.1_20170811.
I didnt get to try it with the latest upstream, and for the blobs it is all contained un that zip (libs, and *.xml). Sorry that I cannot be more verbose as I am away from my computer.
Btw, updating the prebuilts on an already flashed system requires you to update the SELinux policies to match again:
Code:
chown root:shell /system/bin/mm-qcamera-*;
chmod 0755 /system/bin/mm-qcamera-*;
chcon -t system_file /system/bin/mm-qcamera-app;
chcon -t mm-qcamerad_exec /system/bin/mm-qcamera-daemon;
set_perm_recursive 0 0 0755 0644 /system/vendor/lib;
set_perm_recursive 0 0 0755 0644 /system/vendor/lib64;
set_perm_recursive 0 0 0755 0644 /system/etc/camera;
chmod 0644 /system/media/*.bin;
restorecon -r /system/vendor/lib;
restorecon -r /system/vendor/lib64;
restorecon -r /system/etc/camera;
restorecon -r /system/media;
Click to expand...
Click to collapse
Yeah, I built the entire ROM. Kernel changes went it, but for LOS to use it it'll need to have the other g5 (lucye) changes in there too. kernel is the same source for both sets. The touchscreen kernel bug should be fixed shortly. Trying to get this into LOS might be next. My us996 though doesn't have that sensor, so I can only test that my builds do not break my camera (which they do currently).
What would happen if i would flash the camera libs on a h990ds which has the same s5k2p7 sensor?
jody2k said:
What would happen if i would flash the camera libs on a h990ds which has the same s5k2p7 sensor?
Click to expand...
Click to collapse
You would get the 3rd camera 'working' and showing in the apps. But without focus (OIS). Once @x86cpu gets the Kernel changes upstream then we could get the DS Kernel built and hopefully get this working soon for your device.
x86cpu said:
Yeah, I built the entire ROM. Kernel changes went it, but for LOS to use it it'll need to have the other g5 (lucye) changes in there too. kernel is the same source for both sets. The touchscreen kernel bug should be fixed shortly. Trying to get this into LOS might be next. My us996 though doesn't have that sensor, so I can only test that my builds do not break my camera (which they do currently).
Click to expand...
Click to collapse
I see, yeah... seems like it still needs more dissecting to cherry-pick and keep the support for the G5/G6's intact... :highfive: thanks for being proactive on getting these upstream as I haven't had much extra time
Omar-Avelar said:
I see, yeah... seems like it still needs more dissecting to cherry-pick and keep the support for the G5/G6's intact... :highfive: thanks for being proactive on getting these upstream as I haven't had much extra time
Click to expand...
Click to collapse
I think I got it. Those kernel changes are correct. The blobs I had were messed up. I'm hoping to have a build (UNOFFICAL) shortly that will have the latest LOS, kernel no touchscreen fixed, blueborne patches in too. Only for us996, but it is a start. I'll validate it works for me and does not break my camera at least. I won't be able to tell if it works for the s5k2p7 sensor as mine does not appear to have it.
Omar-Avelar said:
You would get the 3rd camera 'working' and showing in the apps. But without focus (OIS). Once @x86cpu gets the Kernel changes upstream then we could get the DS Kernel built and hopefully get this working soon for your device.
Click to expand...
Click to collapse
My friend we have working focus already thx to jahlex
https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296/page71
But the kernel is bit basic for moment, no kcal colors tweaking and no gouvernors or schedulers etc but we cant complain
I'm currently using kernel with lot of features (from leicxan) but focus is not working thats why i asked about the libs maybe i could get focus to work on that kernel with flashing libs
x86cpu said:
I think I got it. Those kernel changes are correct. The blobs I had were messed up. I'm hoping to have a build (UNOFFICAL) shortly that will have the latest LOS, kernel no touchscreen fixed, blueborne patches in too. Only for us996, but it is a start. I'll validate it works for me and does not break my camera at least. I won't be able to tell if it works for the s5k2p7 sensor as mine does not appear to have it.
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B51rjK5Hd_P5NmpwY1o4VmlyaUk
us996 test one to ensure what I did is sane. My us996 works still. In the s5k2p7_sensor_test folder.
jody2k said:
My friend we have working focus already thx to jahlex
https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296/page71
But the kernel is bit basic for moment, no kcal colors tweaking and no gouvernors or schedulers etc but we cant complain
I'm currently using kernel with lot of features (from leicxan) but focus is not working thats why i asked about the libs maybe i could get focus to work on that kernel with flashing libs
Click to expand...
Click to collapse
Seems like you only need to flash the libs and propeitary files (flashable-lge-v20-s5k2p7-eeprom-camera-libs.zip) without my Kernel then and it should work. I wasn't aware of that Kernel
x86cpu said:
https://drive.google.com/open?id=0B51rjK5Hd_P5NmpwY1o4VmlyaUk
us996 test one to ensure what I did is sane. My us996 works still. In the s5k2p7_sensor_test folder.
Click to expand...
Click to collapse
Awesome! Can anyone with the US996 with the s5k2p7 sensor try this build? I gave that phone to my sister and cannot test it myself either... this would bring confidence on the fixes all together and getting this upstream in a not too distant future
Omar-Avelar said:
Seems like you only need to flash the libs and propeitary files (flashable-lge-v20-s5k2p7-eeprom-camera-libs.zip) without my Kernel then and it should work. I wasn't aware of that Kernel
Awesome! Can anyone with the US996 with the s5k2p7 sensor try this build? I gave that phone to my sister and cannot test it myself either... this would bring confidence on the fixes all together and getting this upstream in a not too distant future
Click to expand...
Click to collapse
Not sure what you mean with properitary files ? My knowledge is pretty low of tweaking files
Oh oxejar whats gama kernel
---------- Post added at 09:58 PM ---------- Previous post was at 09:51 PM ----------
Omar whats gama kernel
Omar-Avelar said:
Seems like you only need to flash the libs and propeitary files (flashable-lge-v20-s5k2p7-eeprom-camera-libs.zip) without my Kernel then and it should work. I wasn't aware of that Kernel
Awesome! Can anyone with the US996 with the s5k2p7 sensor try this build? I gave that phone to my sister and cannot test it myself either... this would bring confidence on the fixes all together and getting this upstream in a not too distant future
Click to expand...
Click to collapse
I'm hoping to have an UNOFFICIAL build for this today (us996/ls997/h918/vs985). This would have the necessary blobs/configs that you had in your .zip file as well as the update into the kernel at the latest LOS release. I want to test first with my us996 just to ensure that I do not break my own camera. I do not have the s5k2p7 sensor, so I cannot test if that part works, but it should not prevent my camera from working either.
Omar-Avelar said:
Seems like you only need to flash the libs and propeitary files (flashable-lge-v20-s5k2p7-eeprom-camera-libs.zip) without my Kernel then and it should work. I wasn't aware of that Kernel
Awesome! Can anyone with the US996 with the s5k2p7 sensor try this build? I gave that phone to my sister and cannot test it myself either... this would bring confidence on the fixes all together and getting this upstream in a not too distant future
Click to expand...
Click to collapse
Are you able to test: https://drive.google.com/drive/folders/0B51rjK5Hd_P5NmpwY1o4VmlyaUk The ls997 for 09202017 has the necessary files/kernel fixes to make this sensor work....or at least I think it does. Just need confirmation things might work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About LineageOS
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.
Warning!!!
BackUp EFS and persist partition before installing. If you lose IMEI , use this backup to retrieve it in future.
What's working :
Boots
RIL (Calls, SMS, Data)
Fingerprint
Wi-Fi
Bluetooth
Camera
Camcorder
Video Playback
FM Radio
Audio
Sensors
Flash
LED
GPS
Volte
Encryption
Usb tethering
What's not working :
Nothing
Flashing and updating
LineageOS clean install :
- Mandatory to flash 64bit recovery
- (Optional) Wipe the data & cache & system(Backup to make sure not to loose data)
- Flash the LineageOS ROM zip from the Recovery
- (Optional) Flash the GApps to have the Google Applications
- (Optional) Every additional zip you want to flash
- Reboot
LineageOS update / upgrade :
- Mandatory to flash 64bit recovery
- (Information) Don't wipe anything unless you want to
- Nothing to wipe when switching
- (FUTURE RELEASES) Might need clean, informations will be updated
- Flash the latest LineageOS ROM zip from the Recovery
- (Optional) Flash the GApps on first install / upgrade. Not required later, but do update sometimes
- (Optional) Every additional zip you want to flash
- Reboot
Downloads Links
LineageOS 16.x arm64(Unlocked Bootloader) :
Development : https://www.androidfilehost.com/?w=files&flid=287970
Google Applications (optional) :
Opengapps : Link (Use packages for ARM64, Android 9.0)
Information : Flash the GApps before the first boot. If not, a clean flash is recommended.
Recovery Mandatory to flash for 64bits ROM :
Download TWRP 3.2.1-0 : https://www.androidfilehost.com/?fid=11410963190603887243
About the builds
Device tree : https://github.com/Sohamlad7/android_device_motorola_cedric/commits/lineage-16.0
Kernel sources : https://github.com/Sohamlad7/android_kernel_motorola_msm8937/commits/lineage-16.0
Vendor blobs : https://github.com/Sohamlad7/android_vendor_motorola_cedric/commits/lineage-16.0
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel, third party apps or you installed Xposed
DO NOT Report bugs if you've modifies system files
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)
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.)
Code:
adb logcat > logcat.txt
Code:
adb shell dmesg > dmesg.txt
If it is a random reboot, grab kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Code:
adb shell cat /sys/fs/pstore/console-ramoops
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Bug report should be done in following format provided in code below
Code:
What is your
LineageOS version:
LineageOS Download url:
Gapps version:
Did you
wipe:
restored with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Q&A - FAQ
LineageOS 16.0 arm64 Cedric Regular Questions and Answers : Q&A Thread
Credits :
- The LineageOS Team
- Thanks to ROM that have been built on Legacy Server and also thanks to all the legacyserver member friends
- Special Thanks to @wzedlare and @vache without them it wouldn't have been possible for us to get Nougat and Oreo
- Thanks to @infixremix , @m_vaisakh and @AyamDobhal for helping
- Thanks to @DavidKirsch , @robt77, @ADHILR, @Jefe1177, @Robson1000 and everyone else from cedric testing group for testing rom
- Let me know if i missed anyone
XDA:DevDB Information
LineageOS 16.0, ROM for the Moto G5
Contributors
CodeZero, m_vaisakh
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: Stable
Created 2019-01-01
Last Updated 2019-05-22
ATTENTION :-
Just a heads up, that we are moving to Stock Oreo's firmware, so it's better that you update to it for the upcoming Pie Roms.
I have moved to Stock Oreo Firmware base so you will have to flash Stock Oreo first and then move to lineage or else Fingerprint will not work
TWRP Flashable Stock Oreo rom
Thanks to @NZedPred https://forum.xda-developers.com/g5/development/twrp-flashable-soak-test-oreo-t3827913
Changelog
12/09/2019
Patched CVE-2019-1988 vulnerability
[*]Removed cpuset foreground boost
[*]Switched to common basic USB HAL
[*]Moved to common data-ipa-cfg-mgr
[*]Enabled USB enumeration in power-off charging mode
[*]Added permission entries for location component
[*]Enabled multiple haptic intensity support
[*]Migrated to audio V4
[*]Added Mapper 2.1 to VNDK SP list
[*]Included all new changes from LineageOS
09/07/2019
Added perfboostsconfig.xml from stock
[*]Fixed inverted fp gesture issue
[*]Removed persist.camera.is_type (which partially fixed green tint camera issue in low light)
[*]Added drop_unicast_in_l2_multicast commits
[*]Included all new changes from LineageOS
22/05/2019
Switched back to Camera2
[*]Kernel source upstreamed to linux stable release 3.18.140
[*]Enabled metadata for FDE
[*]USB Tethering fixed thanks to @wiktorek140
[*]Encryption fixed
[*]Added QCOM's WFD
[*]Synced some config files with stock
[*]Addressed some vendor_init denials
[*]Copied missing vendor.display.config
05/04/2019
Volte fixed
[*]SElinux Enforced
[*]Kernel source upstreamed to linux stable release 3.18.138
[*]Migrated livedisplay to livedisplay 2.0
[*]Updated GPS blobs from deen PPK29.68-16-8
[*]Updated keystore and gatekeeper HALs
[*]Updated DRM blobs from ocean
[*]Added QTI wifi hals
[*]Added missing camera blobs
[*]Updated SDM blobs from LA.UM.7.5.r1-03700-8x96.0
01/01/2019 - Initial Release
Note :-
We can now run 64bits ROM on our phone.
But actually we have to run app_process (system server) as 32bits, mainly cause of sensors non working actually with a 64bits system server.
More to come next, vendor tree is still missing many 64bits blobs, and some of our proprietary services still run in 32bits mode too.
As we have found out , Flashing stock whilst having anything 64bit even the recovery for some reason the efs (IMEI) gets wiped .
I do not recommend you revert to stock on any 64bit rom.
Current local manifest of the ROM build
Code:
<!-- https://github.com/Sohamlad7/android_development_manifest/blob/local_manifests/lineage-16.0.xml -->
Great work bro. All the hardwork finally we get a nice pie rom. Thank you very much soham
---------- Post added at 10:21 AM ---------- Previous post was at 10:12 AM ----------
CodeZero said:
About LineageOS
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.
Warning!!!
BackUp EFS and persist partition before installing. If you lose IMEI , use this backup to retrieve it in future.
What's working :
Boots
RIL (Calls, SMS, Data)
Fingerprint
IR Blaster
Wi-Fi
Bluetooth
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
LED
GPS
What's not working :
Volte
Usb tethering
SELinux is permissive
Flashing and updating
LineageOS clean install :
- Mandatory to flash 64bit recovery
- (Optional) Wipe the data & cache & system(Backup to make sure not to loose data)
- Flash the LineageOS ROM zip from the Recovery
- (Optional) Flash the GApps to have the Google Applications
- (Optional) Every additional zip you want to flash
- Reboot
LineageOS update / upgrade :
- Mandatory to flash 64bit recovery
- (Information) Don't wipe anything unless you want to
- Nothing to wipe when switching
- (FUTURE RELEASES) Might need clean, informations will be updated
- Flash the latest LineageOS ROM zip from the Recovery
- (Optional) Flash the GApps on first install / upgrade. Not required later, but do update sometimes
- (Optional) Every additional zip you want to flash
- Reboot
Downloads Links
LineageOS 16.x arm64(Unlocked Bootloader) :
Development : https://www.androidfilehost.com/?w=files&flid=287970
Google Applications (optional) :
Opengapps : Link (Use packages for ARM64, Android 9.0)
Information : Flash the GApps before the first boot. If not, a clean flash is recommended.
Recovery Mandatory to flash for 64bits ROM :
Download TWRP 3.2.1-0 : https://www.androidfilehost.com/?fid=11410963190603887243
About the builds
Device tree : https://github.com/Sohamlad7/android_device_motorola_cedric/commits/lineage-16.0
Kernel sources : https://github.com/Sohamlad7/android_kernel_motorola_msm8937/commits/lineage-16.0
Vendor blobs : https://github.com/Sohamlad7/android_vendor_motorola_cedric/commits/lineage-16.0
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel, third party apps or you installed Xposed
DO NOT Report bugs if you've modifies system files
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)
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 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
Bug report should be done in following format provided in code below
Q&A - FAQ
LineageOS 16.0 arm64 Cedric Regular Questions and Answers : Q&A Thread
Credits :
- The LineageOS Team
- Thanks to ROM that have been built on Legacy Server and also thanks to all the legacyserver member friends
- Special Thanks to @wzedlare and @vache without them it wouldn't have been possible for us to get Nougat and Oreo
- Thanks to @infixremix , @m_vaisakh and @AyamDobhal for helping
- Thanks to @DavidKirsch , @robt77, @ADHILR, @Jefe1177, @Robson1000 and everyone else from cedric testing group for testing rom
- Let me know if i missed anyone
XDA:DevDB Information
LineageOS 16.0, ROM for the Moto G5
Contributors
CodeZero
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: Beta
Created 2019-01-01
Last Updated 2019-01-01
Click to expand...
Click to collapse
FIX VoLTE for Pie
1. Copy lines from the file to/vendor/build.prop
2. Reboot
3. install ims apk after every reboot
Eu não sou responsável por qualquer coisa que aconteça ao seu telefone. Faça por sua conta e risco.
Funciona apenas em roms de pie
Am I able to install it from stock Oreo ROM? I haven't unlocked it.
FIX VoLTE for Pie
1. Copy lines from the file to/vendor/build.prop
2. Reboot
3. install ims apk after every reboot
I am not responsible for anything that happens to your phone. Do it at your own risk.
Only works on pie roms
https://www.mediafire.com/file/ruoxo93m5szymh5/1_4936412157622353977.apk/file
https://www.mediafire.com/file/2dtky4f3ad3y5y2/1_4936412157622353976.prop/file
giri45 said:
Am I able to install it from stock Oreo ROM? I haven't unlocked it.
Click to expand...
Click to collapse
Yes,
First follow this guide to unlock your bootloader.
Then install the above mentioned TWRP using ADB & FASTBOOT.
After that follow the instructions in the thread.
Good luck!
thanks for the New year gift just waiting for the volte fix
Thanks for your work @CodeZero, nice build, everything is working fine for me.
DavidKirsch said:
Thanks for your work @CodeZero, nice build, everything is working fine for me.
Click to expand...
Click to collapse
Is front hdr in gcam 6.1 working?
Hi there,
first thank you for this fine release. I am interested in installing this rom but have a few questions which could also be interesting for other users.
1. I am currently using LineageOS 15.1, can I flash this rom directly after a clean wipe or do I need to flash the stock firmware first? I have read that flashing stock firmware could be dangerous regarding loosing the IMEI.
2. I have installed TWRP 3.2.1 and was trying to do a backup of EFS and persist partions. Only the EFS partition is selectable for backup, persist seems to be missing.
3. Is the stock camera working fine or is there a long delay when starting like in other 15.1 roms?
AyamDobhal said:
Yes,
First follow this guide to unlock your bootloader.
Then install the above mentioned TWRP using ADB & FASTBOOT.
After that follow the instructions in the thread.
Good luck!
Click to expand...
Click to collapse
Thanks a lot?
CodeZero said:
ATTENTION :-
Just a heads up, that we are moving to Stock Oreo's firmware, so it's better that you update to it for the upcoming Pie Roms.
Click to expand...
Click to collapse
So wasn't a waste of time trying out the crappy Stock Oreo after all. Thanks
Any tested fm radio?
kutlay1653 said:
Any tested fm radio?
Click to expand...
Click to collapse
Yes, it's working.
Thanks a lot for your work! It seems like finally I'm gonna install a custom ROM in cedric :laugh: I have a Oreo stock untouched device, any heads up as how to not loose IMEI or mess up with something else?
Also, is the camera totally working? Thanks a lot again!
J.
jpm92 said:
Thanks a lot for your work! It seems like finally I'm gonna install a custom ROM in cedric :laugh: I have a Oreo stock untouched device, any heads up as how to not loose IMEI or mess up with something else?
Also, is the camera totally working? Thanks a lot again!
J.
Click to expand...
Click to collapse
It's recommended to backup fully working EFS/persist before messing with 64bit TWRP/ROMs.
For the unknown reason, reverting to stock (using fastboot) with anything 64bit at least once installed (even TWRP) wipes the IMEI.
Idk about the camera, but I'd like to ask the same as I'm also interested in trying LOS based on Pie.
SafetyCheck is certified? No lags and stuttering?
jpm92 said:
Also, is the camera totally working? Thanks a lot again!
Click to expand...
Click to collapse
At first I thought the camera was working fine. There is no big startup delay when starting the camera app (just the normal second). Flashlight, front camera and video recording also worked for me.
But when I am trying to take a picture from within a messenger app my phone crashes or something. The same thing happens If a take more than one picture. The camera app seems to crash and the whole phone becomes unusable. I only can see a black screen or my lock screen.
How do you back up EFS?