LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
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 Wiki.
Important Info
DON'T USE TWRP 3.0.2-0 OR OLDER WITH LINEAGEOS. IT DOES NOT WORK CORRECTLY. USE VERSION 3.2.1.0 HERE
Current lineage 15.1 shamu nightlies are based on the N6F27M October 2017 update from google.
So you should be using the radio and bootloader img from that update.
If you already have those you don't need to flash them again.
They can be extracted from the factory image on google's site here.
Or you can use the ones linked below that I already extracted:
radio-shamu-d4.01-9625-05.45+fsg-9625-02.117.img
bootloader-shamu-moto-apq8084-72.04.img
IMPORTANT NOTE FOR VERIZON USERS: Google released a separate October 2017 security update (NGI77B) just for verizon users that has a different radio. So you'll want to flash it. I repeat, THIS RADIO IS JUST FOR VERIZON USERS.
radio-shamu-d4.01-9625-05.51+fsg-9625-02.118.img
You can use fastboot to flash the bootloader and radio.
More information and installation instructions can be found on the LineageOS wiki here.
Download Links
LineageOS OFFICIAL: https://download.lineageos.org/shamu
As you will see it is no longer available and there will be no new OFFICIAL builds as shamu has been promoted to LineageOS 18.1.
Seems an archive of the official 15.1 builds is here. To check official signature you can follow this guide
LineageOS UNOFFICIAL: lineage-15.1-20220301-UNOFFICIAL-shamu.zip
Includes the now (no longer official from now on as per comments here) non official February 2022 security bulletins.
Here is its md5sum.
Google apps: MindTheGapps or OpenGAPPS <= nano
HEADS UP:
When you initially install LineageOS, be sure you flash the gapps package with your ROM. If you boot your ROM, then go back and try to flash gapps after, you're gonna have a bad time.
If you are migrating from an OFFICIAL build to the UNOFFICIAL build you have 2 options:
Wipe data and do a clean install of UNOFFICIAL build
Dirty flash thanks to an intermediate MIGRATION build
First flash the MIGRATION build (lineage-15.1-20200501-MIGRATION-shamu.zip md5sum), boot to it and then flash the UNOFFICIAL build and boot to it.
SU addon zip: Addon Install zip / Addon Removal zip
NOTE: LineageOS does not come with root, so this is now provided for those that want it.
The install zip is a one time flash, like gapps.
Meaning, it persists when updating to a new LineageOS nightly.
Changelog
Builddate: 2018.07.17
Changes:
[new] Full featured, binderized power HAL with support for following power profiles:
- Power save => Maximum of 2 cores online, max. freq limited to 1,036 GHz
- Bias power => Up to 4 cores online, max. freq limited to 1,036 GHz
- Balanced => Up to 4 cores online, no freq limits
- Bias performance => Up to 4 cores online, min freq limited to 1,19 GHz
- Performance => 4 cores online always at 2,6 GHz
[new] Core hotplugging through new mpdecision
Known Issues:
[bug] Trusted voice is not working and probably never will
[bug] TWRP is not able do decrypt your data if you encrypted it with lineage-15.1
[bug] Not every app is compatible with the expanded desctop feature. If you have ranndom problems to turn on your device
disable expanded desktop for the app
Older Changelogs:
Builddate: 2018.06.19
Changes:
[new] Full RGB brightness support
Builddate: 2018.06.12
Changes:
[new] LineageOS's Trust
[new] Spectre V1 patches
[new] june security fixes
[fix unconfirmed] Camera app 'missing' on some devices
Builddate: 2018.05.28
Changes:
[new] Option to check proximity sensor before device is woken up with dt2w
[new] Stereo recording in all available formats
[fix] DRM is now L1
[fix] SU hiding is now working properly
Builddate: 2018.05.21
Changes:
[new] New BT power management driver with less wakelocks
Builddate: 2018.04.30
Changes:
[new] Stereo recording
[new] Ability to edit apn regardless of carrier
Builddate: 2018.04.23
Changes:
[fixed] DRM now working on L3
Builddate: 2018.04.16
Changes:
[fixed] Netflix not working: DRM issue
[fixed] Camcorder audio too low
[new] Get rid of forceencryption
[new] BCL not turning of core 2 and 3 at ~40 % battery anymore
We're limiting the max frequency instead
Builddate: 2018.04.12
Changes:
[fixed] Double touch to wake
[fixed] Power HAL loading
[fixed] Vendor image mismatch notification popping up every boot
[new] Optimized boot latemounting of data and cache
Known Issues:
[bug] Netflix not working: DRM issue
[bug] Camcorder audio too low
[bug] Trusted voice is not working and probably never will
Builddate: 2018.04.02
Known Issues:
[bug] Vendor image mismatch notification popping up every boot. Just ignore it
[bug] touch to wake is not working
[bug] Trusted voice is not working and probably never will
XDA:DevDB Information
LineageOS, ROM for the Nexus 6
Contributors
Elektroschmock, Elektroschmock, dwardo
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2018-04-04
Last Updated 2020-11-14
Thank you for your support...
I am getting this message on every reboot https://ibb.co/gUBVux
I have downloaded N6F27M from google but there is no vendor.img in the zip file
aqatramiz said:
Thank you for your support...
I am getting this message on every reboot https://ibb.co/gUBVux
I have downloaded N6F27M from google but there is no vendor.img in the zip file
Click to expand...
Click to collapse
It's nothing you should worry about...just ignore it.
It will be fixed with the next nightly.
You might want to add the info about "vendor image" + "counterfeit april fools joke" + "double tap 2 wake not working yet" + into the op under known issues or something. I see those questions posted over and over again in the old thread and other communities
People should use TWRP 3.2.1.0 with LOS 15.1
https://dl.twrp.me/shamu/
First of all, thank you very much. I'm using my Nexus 6 only as a secondary device but I'm happy to upgrade it to LineageOS 15.1 now
Does it support FBE or direct boot? I'm already running LOS 14.1 and not quite sure if encryption changes upon a data wipe
While on a phone call adding another call, then merging the two results in dropping both lines.
Install:
Wiped, lineage-15.1-20180402-nightly-shamu-signed.zip, opengapps super, magisk.
Logcat: https://drive.google.com/file/d/1XQbvCKna63HG1rPdNP3VoBXwznAxEaib/view?usp=drivesdk
never mind
mugendon said:
Yap, just what the op says in red letters
Click to expand...
Click to collapse
What I meant is advice people from beginning ro use 3.2.1.0 because there are in between version too.
Is the SU addon zip coming anytime soon?
You can get 'double tap to wake' working if you enable it via something like EX Kernel Manager.
Sent from my Nexus 6 using XDA Labs
---------- Post added at 01:44 PM ---------- Previous post was at 01:38 PM ----------
rodritoledo94 said:
Is the SU addon zip coming anytime soon?
Click to expand...
Click to collapse
https://forum.xda-developers.com/ne...om-cm14-1-nexus-6-shamu-t3514362/post76101587
Also, Magisk works great on this ROM.
Sent from my Nexus 6 using XDA Labs
someone is experiencing a problem with huge battery drain via Google Play Services?
i have clean install with full wipe (installed factory image -> twrp -> full wipe -> LOS 15.1 + OpenGapps)
and 2nd problem is strange "beep" after incoming/outgoing phone call
Running perfectly (using opengapps nano and magisk 16.1).
- Had one reboot 48hrs ago and nothing since.
- Some lag in a couple spots, but may still be settling in.
- Netflix, you have to roll back to v4.6.
- Battery drain is identical to 14.1 for me (edit: Meaning no bad drain at all...it's ideal)
- Had some minor signal issue with cell calls in spots that are normally good, but that could be weather/sunspots/aliens.
- Had no issue removing the LOScoins alert.
rodritoledo94 said:
Is the SU addon zip coming anytime soon?
Click to expand...
Click to collapse
It's better to use Magisk on Android 8+.
Lagarde said:
Running perfectly (using opengapps nano and magisk 16.1).
- Had one reboot 48hrs ago and nothing since.
- Some lag in a couple spots, but may still be settling in.
- Netflix, you have to roll back to v4.6.
- Battery drain is identical to 14.1 for me
- Had some minor signal issue with cell calls in spots that are normally good, but that could be weather/sunspots/aliens.
- Had no issue removing the LOScoins alert.
Click to expand...
Click to collapse
Using micro, everything is working great.
...
Another report for all good. I upgraded from the latest 14.1 nightly: Updated TWRP; Wiped system, dalvik, cache; flashed 15.1 nightly and then mind_the_gapps; boot once, then reboot to TWRP and flash Magisk. Apps all still work; all good! Thanks for the great build!
Been using this for 2 days now. A couple of issues:
Biggest issue is Netflix issue. Also heard YouTube TV isn't working, but I haven't had the opportunity to test it.
Stutters when unlocking. Also when switching between apps using the multitask button (or whatever it's called).
I haven't run into any other problems (outside the ones listed in OP).
ExpectedCrayon said:
Been using this for 2 days now. A couple of issues:
Biggest issue is Netflix issue. Also heard YouTube TV isn't working, but I haven't had the opportunity to test it.
Stutters when unlocking. Also when switching between apps using the multitask button (or whatever it's called).
I haven't run into any other problems (outside the ones listed in OP).
Click to expand...
Click to collapse
This is because DRM Widevine L1 or L3 hasn't been implemented yet. Other Oreo Roms have however. Netflix and YouTube check for this now.
Any suggested kernel for the Lineage 15.1?
My phone started stuttering (As per CPU-z it looked like two cores were offline when the battery was low) and I thought of trying PureZ Kernel 5.2, but with that my phone got stuck at the boot logo for hours. Reinstalled Lineage 15.1 to fix that and wanted to check with others before trying a new Kernel.
wavedashdoc said:
This is because DRM Widevine L1 or L3 hasn't been implemented yet. Other Oreo Roms have however. Netflix and YouTube check for this now.
Click to expand...
Click to collapse
Do you know if there are plans to implement it?
---------- Post added at 05:43 PM ---------- Previous post was at 05:41 PM ----------
manish_bhaumik said:
Any suggested kernel for the Lineage 15.1?
My phone started stuttering (As per CPU-z it looked like two cores were offline when the battery was low) and I thought of trying PureZ Kernel 5.2, but with that my phone got stuck at the boot logo for hours. Reinstalled Lineage 15.1 to fix that and wanted to check with others before trying a new Kernel.
Click to expand...
Click to collapse
I'm waiting for Franco Kernel. There isn't an Oreo version yet, but the dev said he intends to make a version for Lineage 15.1 Shamu on his Google + a few days ago.
Related
Hello together,
Last week I bought two devices: Apollo (w/o LTE) + Thor (incl. LTE)
Today I installed on the Apollo device CM 14.1, but the issue is,
Issue 1: the screen does not rotate. Only apps are switching the rotation.
Issue 2 (minor): WiFi connection lost after sleep
What I did today:
- Rooted the original installation (14.3.0.2_user_302075320) with KingRoot
- Unlocked and installed TWPR based on http://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982 ( I followed all steps except of the aboot_vuln.mbn, as the firmware was below 14.3.2.3.2)
- Full wipe, Flashed CM 14.1 (first official nightly) incl. pico OpenGapps
- Noticed the problem
- Upgraded the bootloader to 14.3.2.3.2 based on http://forum.xda-developers.com/kin...p-flashable-3-2-3-bootloader-upgrade-t3025504
- Problem still there
- Flashed CM 11 from http://forum.xda-developers.com/kin...-cm-11-safestrap-20150628-unofficial-t3145547
- Problem gone (as already on original FireOS)
Any help is welcome, so that I can use CM 14.1 as others do not seem to have this problem. If you need further information (logs, retries with our custom roms, ...), I am happy to provide/do it.
Zathor said:
Hello together,
Last week I bought two devices: Apollo (w/o LTE) + Thor (incl. LTE)
Today I installed on the Apollo device CM 14.1, but the issue is,
Issue 1: the screen does not rotate. Only apps are switching the rotation.
Issue 2 (minor): WiFi connection lost after sleep
What I did today:
- Rooted the original installation (14.3.0.2_user_302075320) with KingRoot
- Unlocked and installed TWPR based on http://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982 ( I followed all steps except of the aboot_vuln.mbn, as the firmware was below 14.3.2.3.2)
- Full wipe, Flashed CM 14.1 (first official nightly) incl. pico OpenGapps
- Noticed the problem
- Upgraded the bootloader to 14.3.2.3.2 based on http://forum.xda-developers.com/kin...p-flashable-3-2-3-bootloader-upgrade-t3025504
- Problem still there
- Flashed CM 11 from http://forum.xda-developers.com/kin...-cm-11-safestrap-20150628-unofficial-t3145547
- Problem gone (as already on original FireOS)
Any help is welcome, so that I can use CM 14.1 as others do not seem to have this problem. If you need further information (logs, retries with our custom roms, ...), I am happy to provide/do it.
Click to expand...
Click to collapse
Known issue on Apollo CM 14.1 builds; developer is actively pursuing. See CM 14.1 thread for current status and possible work around (Nova launcher).
BTW - kudos on your efforts to date. Shows familiarity with the material and a willingness to read/research/self-help. Refreshing!
Davey126 said:
Known issue on Apollo CM 14.1 builds; developer is actively pursuing. See CM 14.1 thread for current status and possible work around (Nova launcher).
BTW - kudos on your efforts to date. Shows familiarity with the material and a willingness to read/research/self-help. Refreshing!
Click to expand...
Click to collapse
Thank you very much for your kind reply.
I tried the Nova launcher approach, but it does not work sadly. ggow suggested for the LTE device to install the complete firmware 14.3.2.3.2 - maybe this helps here also, as others do not seem to have the problem. How would I do that in the current state of the device? And how should I do that with the untampered Thor device (13.3.2.4_user_324002120) - let it update to 4.5.5.2 and as root seems to work unlock the bootloader from there?
Zathor said:
Thank you very much for your kind reply.
I tried the Nova launcher approach, but it does not work sadly. ggow suggested for the LTE device to install the complete firmware 14.3.2.3.2 - maybe this helps here also, as others do not seem to have the problem. How would I do that in the current state of the device? And how should I do that with the untampered Thor device (13.3.2.4_user_324002120) - let it update to 4.5.5.2 and as root seems to work unlock the bootloader from there?
Click to expand...
Click to collapse
- hold on bootloader update as there was a recent report of an unfavorable outcome (bricked device); need to see how that plays out
- for 13.3.2.4 root with TowelRoot and then proceed with bootloader unlock; keep device off network (WiFi off) except when rooting to prevent an OTA update; no need to update FireOS for bootloader unlock - root is sufficient
Ok, I will wait with the bootloader update for Thor, for Apollo I have already done it sucessfully yesterday (see first post).
I tried a few additional custom roms:
- cm-11-SAFESTRAP-20161016-UNOFFICIAL-apollo: OK
- cm-12.1-20160922-UNOFFICIAL-apollo: OK
- cm-13.0-20161108-NIGHTLY-apollo: OK
- cm-14.1-20161218-NIGHTLY-apollo: NOT OK
So the screen stuck in one orientation seems to be a CM 14.1 problem only.
To be honest I do not know why, but the problem is solved. After dirty flashing (without wipe) from cm-13.0-20161108-NIGHTLY-apollo to cm-14.1-20161218-NIGHTLY-apollo the automatic screen rotation does work now. Even after a full wipe and a clean installation of CM 14.1 (which I always did before), it does work now.
This is a port of OMNIRom 7.1.1 for the Samsung Galaxy Tab A 7.0 (2016) LTE SM-T285. OMNIRom aims to be a community based project and is a lot "lighter" than CyanogenMod/LineageOS.
5.1.1 is the best that you can get from samsung right now and it is not known if they plan to do any upgrades. I have absolutely no idea why samsung chose to stay with the outdated 5.1.1 mid 2016 when we already got 7.1 coming out. This custom rom is probably the best you can get if you want an upgrade from Lollipop. Performance on the latest build is also better, you be the judge.
Though this is stable enough that I use it currently as my daily driver, make sure you read the pending issues below and decide if this is acceptable to you before you flash this rom. This rom probably won't get much use out of some people until bluetooth is fixed.
Based off on OMNIRom 7.1.1 N4F260 sources which is based on Marshmallow.
For more information on OMNIRom and its features see their site here.
Device Tree:
=========
https://github.com/jedld/device_samsung_gtexslte.git
https://github.com/jedld/vendor_samsung_gtexslte.git
https://github.com/jedld/kernel_samsung_gtexslte.git
Omnirom Notes:
=============
- omnirom doesn't have ffmpeg libraries unlike the CM based roms, but no worries since I ported over CMs libraries here.
Works:
- Wifi/LTE/SMS (Some users report data intermittently not connecting, though toggling airplane mode on/off can fix it)
- Audio
- Graphics
- Bluetooth
- Wifi Hotspot
- MTP
Does not work:
- Calls (needs testing)
- Camera
- GPS (no fix)
- probably more (need testers)
Download
========
Remember flashing an unofficial ROM on your samsung device will probably void your warranty. Don't expect samsung to support you if you have any issues.
As always flash this at your own risk. Make sure you have a copy of the stock ROM so that you have something to fall back to, which is highly the case when using an experimental rom.
See DevDB download section for older releases. Or click below for the latest release:
https://forum.xda-developers.com/devdb/project/dl/?id=23245
Note that this rom is pure stock and does not come with the Play Store or any Gapps, I suggest you download a micro gapps package separately and install it via recovery.
There have been reports that recent versions of open gapps don't work properly, it is advised to use older versions instead (e.g. open_gapps-arm-6.0-nano-20161109.zip)
Installation Instructions
==================
Perform a backup of all of your important files. This ROM is experimental and I will not be responsible for your loss of data.
Download the zip file and extract the tar.
Use Odin/Heimdall to flash the tar file to your device. If you are coming from stock oranother rom make sure you wipe first using TWRP. Coming from a previous version of OMNIRom for SM-T285 may not require a wipe, however please perform a wipe if you encounter problems.
Root and customization
===================
This ROM is a purely based on source and is not rooted out of the box. However you can easily root it by using TWRP to install the latest version of SuperSU.
If you want to customize this ROM and repackage it you may use this guide as a reference.
XDA:DevDB Information
Omnirom 7.1.1 Galaxy Tab A 7 LTE SM-T285, ROM for the Samsung Galaxy Tab A series
Contributors
jedld
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: Omnirom
Version Information
Status: Testing
Created 2017-02-18
Last Updated 2017-02-20
Possible Hope?
Im Not A Developper But I'm The Closest Thing There Is To It. Il Be Running Some Tests To See If It Might Be Compatable With The Sm-t280 Model. Any Boot.Img I Should Install First?
thanks Jedid-did you have a link here for the ROM as I cannot see it (says status is testing so perhaps a placeholder?) as always great work!
mac231us said:
thanks Jedid-did you have a link here for the ROM as I cannot see it (says status is testing so perhaps a placeholder?) as always great work!
Click to expand...
Click to collapse
should be available now
Tinker101 said:
Im Not A Developper But I'm The Closest Thing There Is To It. Il Be Running Some Tests To See If It Might Be Compatable With The Sm-t280 Model. Any Boot.Img I Should Install First?
Click to expand...
Click to collapse
It will be a long shot, there are hardware differences, but nothing stopping you from trying it. Do note that the T280 has a padded boot.img see here, which means you need to get the boot.img from this rom and add an additional header in front of it before you flash it with heimdall or odin.
jedld said:
should be available now
Click to expand...
Click to collapse
thanks Jedid
will look in a couple of days when I the Tab back (gave it to a friend)
EDIT
tried the ROM today...calling is a problem (for me) tried multiple times of reboot and allowed rom to settle before making calls (4g and data in out activity was showing-could go to internet)
The call does not connect and sits in dialing mode forever...if you try to hang up it then sits in hanging up mode and will not terminate
(shows a call in progress as if it is still on)...sms works
With all credit to you and all due respect...I stopped there-
think your very FIRST Lineage 14.1 was the best in all the Nougat ROMs
(the next one had issues with the drives seen but not accessible even though the MTP thing was purported to have been solved in that one)-i.e no real files just drives with overall sizes shown and then the lockscreen issue made it unusable (the PIN and notification method was risky as swiping the notification accidentally would lead to an inaccessible phone or maybe demand a reboot)
Works for me
I don't use the Sim functionality at all, so can't comment on that. I had to try a few variations of GApps to get a working Google Play service, and finally managed with the Dynamic GApps 20170215 Minimal build. Once I got that going, everything worked well. I'm using this as my daily ROM on the tablet now, so will report any further issues I have. Just wanted to say a big thank you! This ROM is very fast and smooth.
home button to wake up device
hi, i just use this rom and its really fast..
just want to ask how to make home physical button to wake up device beside the power button ?
Original Link worked but the file i got
"omni-6.0-20161209-UNOFFICIAL-SMT285-BETA-3.tar"
did not flash, rejected by Odin.
The new one you have linked works
"omni-7.0-20170219-UNOFFICIAL-SMT285.tar"
Quick scan results:
Mem use 462mb of 1.4gb
Space use 2.71 of 7.28gb
Apps installed 17
Very Similar to Lineage "LINEAGE-OMS-14.1-20171209-UNOFFICIAL-SMT285.tar".
In fact almost exact other than a couple of megabytes and an app.
This is BEFORE SU And APP Remover has gone in to shred some files
Stock rom: Terrible
Mem use 5 TB of 1.4gb
Space use Smoke coming out of 7.28gb
Apps installed Still counting I was sure it would finish last week.
Stock rom: Terrible
Mem use 874mb of 1.4gb
Space use 3.7gb of 7.28gb
Apps installed 64
Vol Down Button
Home
Power
[DOWNLOAD SCREEN]
Vol Up to confirm
{Go to PC Odin}
Load AP Custom Rom (TWRP Required)
Press Start...
file explorer cannot read files in internal and external sd card, is it just me, or anyone else?
Download
thank
Can anyone send me other link this ones showing not found.
Link not found
thatha said:
Link not found
Click to expand...
Click to collapse
index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)
index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)
aol.zanoza.lv
Here is the link.
Reload 4 times if not loading.
This ROM is Going to be Primary Based on LineageOS 15.0 source or ROM compiled with Base as LineagesOS 15.0
I am going to regularly compile it and going to share it with community over here
Features of This ROM Based on LineagesOs 15.0
Customizable Theme Engine (Blend with Substratum)
Picture in Picture Mode of Android Oreo
Notification Dots
New user interface in Settings
Split Screen
Improved battery life
Notification Snoozing
Android Oreo Navbar
New UI in Status Bar and Quick Tiles
New Emojis based on Android Oreo
And much more.
Download
For Nexus 6 Android file Host
Gapps For Oreo
Opengapps You can get that from Oppengapps.org
Gaapps For 8.1 Till Open gapps start official Build
The Build is from @Nezorflame And Gapps downlod from
Do NOT expect daily builds. I'll build when I'm free.
Do NOT use this unofficial build and ask for support at the official threads.
Do NOT be rude.
Respect all users
If you see a NOOB question and you don't feel like replying, DON'T, just ignore that post. If you do reply, good for you.....and be nice in your reply.
1st Time Installing
You Need To have Rooted and Custom Recovery Installed Phone To Use This ROM
If you are New Just Go To This Thread and Download Wug's Nexus Tool Kit And Follow Instructions.
Once Custom Recovery Installed. TWRP 3.1.x recommended
Download the zip
Download Gapps
WIPE DATA/FACTORY RESET
Install Modem/Firmware Update
Install the update zip from recovery
Install Gapps
flash Magisk14.1 or 14.0 .zip
Reboot
Already Using the Previous Version of Same ROM
Download the zip
Install latest zip from recovery
wipe Cache
Reflash Gapps
Flash Magisk
Reboot
Credits:
LineagesOs team
CRdroid Team
ScottHeart BTi
He][razor
Vortex 1969
neobuddy89
XDA Developers community
The users and all developer of XDA who has helped me direct or indirect way
Google for Android.
If I miss someone Here please point it out to me.
Source
https://github.com/LineageOS/
https://github.com/crdroidandroid
XDA:DevDB Information
SourceBuilt ROM for Nexus 6, ROM for the Nexus 6
Contributors
chineel, chineel
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: LineageOs
Version Information
Status: Beta
Created 2017-10-28
Last Updated 2017-10-28
Hi everyone The ROM Upload is still On
I have two build Ready One is LineagesOs unofficial and second One CrDroid4.0 which is also based on LineageOs 15.0
Both Got Uploaded
first is Crdroid
crDroidAndroid-8.0-20171028-shamu-v4.0.zip
Second One is LineagesOs-15.0
lineage-15.0-20171028-UNOFFICIAL-shamu.zip
Both Rom are unofficial nothing official about it.
For best error free opration you need to have it Clean Installed
means
Factory reset
wipe
System, Cache,
Flash ROM
Flash Gapps
Flash Magisk / Super Su for rooting
Wait for a while
let it get settled
Enjoy the New Oreo 8.0
11/07 Build Onwards forced encryption is removed so your data by default is not encrypted anymore.
For all those having trouble booting should follow below steps.
get ADB fastboot installer from here
Take back up of everything including DCIM and TWRP or TITANIUM or SMS contact backup or any other.
reboot to bootloader.
open command prompt.
fastboot format userdata (This will format everything on internal storage and will recreate data partition)
wait till success message.
reboot to recovery
wipe system cache data (if you like to but not needed this time)
flash ROM
Flash Gapps of your choice.
wipe dalvick and cache
Reboot
wait for a while
let your phone settle for some time.
reboot to recovery again
flash magisk
reboot
Enjoy your phone unencrypted and fresh as new. Connect to pc copy back your data
restore back whatever you want to restore enjoy.
3rd one
i may Need this one also
Great work! Had any issues with random reboots?
rebel1699 said:
Great work! Had any issues with random reboots?
Click to expand...
Click to collapse
No No reboot since yesterday on my phone
chineel said:
No No reboot since yesterday on my phone
Click to expand...
Click to collapse
Good deal. Will install in the morning and test it out. Again, great work to help keep shamu alive
Hey man thanks for the efforts, a little OT question tho, i saw you got a crDroid build on AFH, are you the new maintainer? edit: Oops, just read the 2nd post ^^ .
gr3ud said:
Hey man thanks for the efforts, a little OT question tho, i saw you got a crDroid build on AFH, are you the new maintainer? edit: Oops, just read the 2nd post ^^ .
Click to expand...
Click to collapse
I am going to request for that if I can continue compiling this ROM but till then Unofficial only
Downloading now. Pretty excited since I'm currently running crdroid.
Do you keep a changelog you're willing to share?
Schiben said:
Do you keep a changelog you're willing to share?
Click to expand...
Click to collapse
For CRdroid already in ROM About section attached here also
Lineageos changelog https://www.lineageoslog.com/15.0
Thank you very much for your great work ? I like this rom
I will try LOS version tonight. Any known bluetooth or Mobile data issues so far ?
Thanks for the effort and appreciate the continued update for Nexus 6.
Hi, I appreciate the effort. Mind telling us the differences between ROMs though? Does the CR one have more features than the stock based Lin one? Still going to test them both but was just wondering, thanks.
mobile data is ON by default, and even when you're connected with Wifi, it still uses your data. Blew thru my 200meg Free T-mobile trying to finish an install. Also, found that NFC is turned off. Might be a driver issue.
Battery life is OK. Sound is bad on my device. Playing some youtube videos, and the sound goes from very loud, to I can barely hear it, plus the only speaker working, is the top, the bottom one cuts in and out. (at least in youtube)
not a bug report, or any disrespect to the dev. but, its just what I've had happen while using this rom.
newsguy99 said:
mobile data is ON by default, and even when you're connected with Wifi, it still uses your data. Blew thru my 200meg Free T-mobile trying to finish an install. Also, found that NFC is turned off. Might be a driver issue.
Battery life is OK. Sound is bad on my device. Playing some youtube videos, and the sound goes from very loud, to I can barely hear it, plus the only speaker working, is the top, the bottom one cuts in and out. (at least in youtube)
not a bug report, or any disrespect to the dev. but, its just what I've had happen while using this rom.
Click to expand...
Click to collapse
Mobile data can be stopped from developer options and untick mobile data always on
steps
1 Open about Phone
2 Go to build number
3 Tap continuous till you got message you are now developer.
4 Tape on Back button
5 You will be seeing Developer options now
6 scroll down till you see mobile data always on toggle it off
Bluetooth issue was found for me when connected to my head unit in my truck. It connects, blurps sound out for half a second and then nothing the songs/videos(videos also go down to like 2 fps while paired) are still playing during but no audio. It's late I just got home will try to capture a log tomorrow. Other than that this rom is butter smooth, thanks for your hard work keeping our old whale swimming. Plz remove if it needs to be I won't be butthurt about it.
Xd great work!
Hi to everyone here... Finally a MoKee ROM is relased for Xiaomi Mi 9 SE (grus) devices!
Developer: subdragonzj
This thread will be unofficial for testing of a AOSP-MoKee ROM builded from the source...
(and ROM based on MoKee with some mods builded by myself)
Stay tuned
I have to say that I was pleasantly surprised by this ROM. It doesn't have the existential issues of PE, so it has all those little useful features out of the box (instant face unlock, double tap to sleep on the lockscreen, etc.). It's not XenonHD based, so no freezing incoming calls. Performance is good (closer to xiaomi.eu). Fingerprint scanner is reasonably fast (I say reasonably because xiaomi.eu is always two steps ahead, in this department). And battery life is also optimized to best levels.
I had issues completing Google setup and with wifi, but I have to be honest: I installed the ROM on top of the latest xiaomi.eu (without sound issues, by the way). Now I have 10.3.4 eea vendor. Let's see how it performs on everyday tasks.
PS - Also, I didn't like the ads on MoKee Center, but Adway takes care of that, of course. I have several paid apps from Play Store, so if the ROM is really good, I have no problems with donation for some extra features.
Can you tell us which steps you made to install mokee properly?
Cheers
Gesendet von meinem MI 9 SE mit Tapatalk
Install Vendor 10.3.3 Global or 10.3.4 EEA via fastboot
Reboot to recovery and install ROM
Do a factory reset (or format Data)
Reboot to system and do initial setup
Reboot to recovery and install Pico GAPPS + faceunlock.zip
Reboot to recovery and install Magisk
Reboot to system and finish setup.
This works for me.
Ultrawide camera is having same problems that XenonHD had (https://forum.xda-developers.com/mi...xenonhd-9-0-experimental-15-08-t3957888/page5). Can you fix this? Probably Okita kernel will fix it, but I would like to keep this kernel for now, seems very optimized for battery.
elpaablo said:
Ultrawide camera is having same problems that XenonHD had (https://forum.xda-developers.com/mi...xenonhd-9-0-experimental-15-08-t3957888/page5). Can you fix this? Probably Okita kernel will fix it, but I would like to keep this kernel for now, seems very optimized for battery.
Click to expand...
Click to collapse
Ultra-wide camera is broken due to missing some nodes at the kernel dtsi on Xiaomi side (their kernel source is too much broken stuff, even for MIUI itself, which is funny).
And because MoKee dev uses Xiaomi kernel source with little modification, so it's pretty much expected.
And because MoKee dev uses Xiaomi kernel source with little modification, so it's pretty much expected.[/QUOTE]
does it support camera 2 API full
I'm using this ROM for now because it's more optimized than PE. Apart from color profiles that don't stick in any AOSP ROM and a dark theme with white notifications, everything else (except camera, as posted above) is working fine. Fingerprint scanner is reliable (although still a little slow), face unlock is instant and the only issue that needs to be solved asap is ultra wide lens not working. A custom kernel can deal with that, but the stock kernel performs better with this ROM. So, I think I'll wait for a fix or other ROM development.
Anyone getting this on any of your AOSP ROMs?
Been using for 3 days now, and by far it gives the ideal battery performance. Tried crDroid and although there were some improvements, couldn't last a day with barely 20% and high idle drain.
Will be staying with this ROM as everything that I expect from this device is provided for. Personally, no battery means no phone for me, so that's my baseline. Thanks to the other developers for their hard work and free time!
elpaablo said:
Anyone getting this on any of your AOSP ROMs?
Click to expand...
Click to collapse
For now, custom AOSP ROM have 177k-184k antutu score, and it's normal.
you can't expect it to be as close as miui (which can go between 185k-195k).
besides, antutu doesn't represent the true performance since anyone can hack it just like huawei before.
btw, this is from some unreleased custom rom that I use right now, no kernel mod, no nothing. typical custom aosp's score
Yes, but generally it gives you the right idea. The ROM is very fluid. I've installed all my stuff and it remains fluid. In fact, I think the latest nightly update has improved user experience.
Then comes maintenance and that's what worries me the most. We see ROMs (XenonHD and PE) that freeze on incoming calls. This is not just a little bug, it's a massive bug. It basically disables your phone. And it's not been solved yet? crDroid developer seems to think that SIM management is not important in a dual SIM phone. Instead, he tries to make fingerprint scanner work 0.1 seconds faster. Yes, camera is not fully working on MoKee and I really hope that this issue is solved, but at least I can receive calls and enable my data SIM card only when I use it, which saves a lot of battery.
---------- Post added at 05:57 AM ---------- Previous post was at 05:36 AM ----------
I installed latest xiaomi.eu version last week and it's way ahead in every aspect, except 2: MIUI (sucks) and SIM management. AOSP ROMs (except crDroid) handle SIM management in a much better (easier) way.
elpaablo said:
Install Vendor 10.3.3 Global or 10.3.4 EEA via fastboot
Reboot to recovery and install ROM
Do a factory reset (or format Data)
Reboot to system and do initial setup
Reboot to recovery and install Pico GAPPS + faceunlock.zip
Reboot to recovery and install Magisk
Reboot to system and finish setup.
This works for me.
Click to expand...
Click to collapse
Sorry for picking this up again, i´d like to give mokee a try.
which faceunlock.zip did you use?
https://forum.xda-developers.com/android/software-hacking/mod-fix-gapps-unlock-t3863509 The one from this thread?
Thank you, Cheers.
Sooo now i´m stuck on fastboot.
Tried flashing vbmeta using fastboot with "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img", but it just says "fastboot.exe: unknown option -- disable-verity"
Any ideas?
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
It's the exact phrase I copy/paste.
Maybe you added a space somewhere?
If you're using power shell type cmd first.
Face unlock: https://androidfilehost.com/?fid=11410963190603910002
i used copy/paste too.. i´ve attached a screenshot.
That´s really annyoing atm..
Type cmd or just use cmd instead of PowerShell.
Yes you should always use cmd in administrator mode in the same folder than vbmeta.img
well... can u tell me what i´m doing wrong here again?
Sorry for the circumstances guys..
Cheers
Humpfrey said:
well... can u tell me what i´m doing wrong here again?
Sorry for the circumstances guys..
Cheers
Click to expand...
Click to collapse
Can you tell us where is located fastboot and vbmeta.img on your pc?
For instance, i have all my files in c:\Android
So I launch the cmd directly in that folder.
Started by DL https://androidfilehost.com/?fid=962187416754459552
Copied on C drive and renamed into Android
Then I copy my files on it, and right click/launch as admin on "cmd-here".
About:
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (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.
Introduction:
This is an unofficial WIP LineageOS thread for the Motorola G7 Power, codename ocean.
We support all the T-Mobile, International, and Project Fi variants, as their bootloaders are unlockable, while we can't support the Verizon and AT&T variants, as their bootloaders are permanently locked.
Changelog:
20200516 (download from Drive) (download from AFH):
Using audio configuration from @Grim truth , which is confirmed to be working
20200514 (build pulled)[/URL]:
Using @Rondeau79's audio stack, which is currently incompatible
20200511 (download):
Builds are now signed. Please wipe data if you're coming from the previous build.
The May security patch has been merged in.
Audio issues have now been eliminated.
Hotspot now works.
Issues:
VoLTE not working prior to May 6 build
[*]Hotspot issues
[*]Garbled call audio on some devices
Headset issues and no audio from local files on May 11 build
ROM:
My Google Drive folder
Android File Host
Make sure to only download the latest build.
Stock Firmware:
Official Firmware
Recovery:
Use whatever recovery you want, but I'm linking OrangeFox (courtesy of @electimon) here
Copy Partitions (To setup slot_b):
copypartitions.zip
(courtesy of @filipepferraz)
GApps:
https://opengapps.org
Pixel GApps (optimized for ocean, Open GApps can have issues)
Preparation for A/B Roms:
Download a custom recovery and the stock firmware for your variant from the links above.
Remove your Google account under Settings > Accounts then factory reset your device, as FRP is enforced.
Unlock your bootloader on Motorola's official site.
Flash your factory firmware image on slot_a.
Hold power + Volume down untill you reach bootloader (fastboot mode).
In your extracted firmware folder, open a terminal or command prompt and flash your firmware files with these commands.
NOTE: This last step installs vendor.img to slot_b as well.
ROM - Installation:
LineageOS 17.1 requires some extra steps to install properly. These instructions are brought to you by @Bernie_nix.
Boot phone into bootloader
From a PC, use one of these command to boot custom recovery (TWRP/oFox). In Linux, use the following command:
Code:
sudo fastboot boot recovery.img
In Windows or macOS, use the following:
Code:
fastboot boot recovery.img
Replace 'recovery.img' with the filename for your recovery image.
If you are coming from stock, install the copy partitions zip after your phone boots into recovery.
In TWRP/oFox go to Wipe - Dalvik/Art Cache, Data, Internal Storage and System.
In TWRP go to the Reboot menu > Switch slots OR in oFox go to the Reboot menu > Switch Slots (press the grey one)
Wipe - Dalvik/Art Cache, Data, Internal Storage and System again.
Reboot into bootloader.
Boot TWRP/oFox with the fastboot command in step 2 above.
Install LineageOS.
Reboot.
It will bootloop 2x, then take you to factory data reset screen. Select Yes. It will reboot into LineageOS. At this point, if you don't want to install anything else, you're done.
Once Lineage boots, if you want to set up GApps, Magisk or another recovery, reboot into recovery mode, install TWRP/oFox, GApps, and/or Magisk.
Reboot into the bootloader and input this.
Code:
fastboot -w
Reboot. You're done.
Updating (AKA 'dirty flash') {do not follow these steps when going from unsigned to signed builds}:
Download the updated ROM.
Reboot to recovery
Install ROM.zip + the recovery, if you're using something other than Lineage Recovery.
Reboot into recovery
Flash gapps + Magisk (if you want)
Reboot into system.
Notes:
Any time your internal storage aka "userdata" is from a stock install you must use 'fastboot -w' to erase it before using any ROM, otherwise it won't boot.
Contributing:
If you have any patches you want to make to the device-specific code, do it at my GitHub, which will be linked at the bottom. I've conveniently pinned all the repositories.
If you want to contribute to LineageOS itself, go to the LineageOS GitHub at https://github.com/LineageOS .
XDA:DevDB Information
LineageOS 17.1, ROM for the Moto G7 Power
Contributors
yagyaxt1068, electimon, erfanoabdi, The people who contributed to LineageOS and the device sources
Source Code: https://github.com/yagyaxt1068
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: No Longer Updated
Current Beta Version: 20200516
Beta Release Date: 2020-05-16
Created 2020-05-09
Last Updated 2020-07-05
Nice! I'm looking through the git repos now. What's all this with switching between LineageOS and RevengeOS? Never heard of RevengeOS before.
Edit: Is it possible to keep the stock software installed in slot A, and install this in slot B?
Greek2me said:
Nice! I'm looking through the git repos now. What's all this with switching between LineageOS and RevengeOS? Never heard of RevengeOS before.
Edit: Is it possible to keep the stock software installed in slot A, and install this in slot B?
Click to expand...
Click to collapse
I based my device tree off of @Electimon's Revenge OS device tree.
And, it is possible to keep stock installed in slot A, but slot A would be useless without a data wipe in fastboot.
I'll give it a try sometime soon. Is there anything you need help with? I'm new to Android work, but I can take a stab at it.
edit: Installed, and it's working well for the most part! I'm going to record issues here as I come across them:
moto gestures missing Actually, they are included. There are two menus: one called "Gestures" and one called "Moto Gestures". They're both under the "System" category in settings.
notification LED constantly on battery was fully charged...
Android Setup crashes after agreeing to TOS
Bug Confirmation
Greek2me said:
I'll give it a try sometime soon. Is there anything you need help with? I'm new to Android work, but I can take a stab at it.
edit: Installed, and it's working well for the most part! I'm going to record issues here as I come across them:
moto gestures missing
notification LED constantly on battery was fully charged...
Android Setup crashes after agreeing to TOS
Click to expand...
Click to collapse
I can confirm that Android Setup is crashing. This occurs with both Pico/Nano Gapps. Also, I'm not sure if this is just the nature of Lineage, but after adding a google account, the only sync toggle option is listed as "People details." I am attempting to sync my contacts from my google account but this doesn't seem to be available. This would be under settings > accounts > google > contacts. There are also some frame rate issues, particularly when switching between applications or home screens. There does not seem to be any frame rate issues within the apps themselves, however.
I just want to add that everything I need seems to be working well. I've placed several calls and the quality was as expected. This will probably be my daily driver - nice work!
Bug report....
Installed nicely in Xfinity (Comcast) Phone.
Bug report - Local music files do not play from speaker or plugin headphones. Doesn't matter if stock player or other. (But works with Bluetooth device).
However speaker and plugin headphones work from browser and apps like Spotify.
nomadman1 said:
Installed nicely in Xfinity (Comcast) Phone.
Bug report - Local music files do not play from speaker or plugin headphones. Doesn't matter if stock player or other. (But works with Bluetooth device).
However speaker and plugin headphones work from browser and apps like Spotify.
Click to expand...
Click to collapse
Try updating to the latest build. If the problem persists, let me know.
Hello all! Considering upgrading to the G7 Power and replacing my aging LG V20 and throwing LOS on it. One single question: Does your LOS support WiFi Calling, and do other ROMs? This is the single factor forcing me off my beloved old tank, I moved to the middle of nowhere and I don't have any signal, and my only option is VoLTE and WiFI Calling, neither of which is supported in LOS on the V20.
Thanks so much for your work!
vectorvitale said:
Hello all! Considering upgrading to the G7 Power and replacing my aging LG V20 and throwing LOS on it. One single question: Does your LOS support WiFi Calling, and do other ROMs? This is the single factor forcing me off my beloved old tank, I moved to the middle of nowhere and I don't have any signal, and my only option is VoLTE and WiFI Calling, neither of which is supported in LOS on the V20.
Thanks so much for your work!
Click to expand...
Click to collapse
Most ROMs (including this one) support WiFi calling. I've tested it myself.
Sent from my moto g(7) power using Tapatalk
I'm not sure if this is just me, but wired headphones/mic don't seem to work while on a call. The audio still comes through the phone speakers.
Please note that I'm still on the May 6th build.
Greek2me said:
I'm not sure if this is just me, but wired headphones/mic don't seem to work while on a call. The audio still comes through the phone speakers.
Please note that I'm still on the May 6th build.
Click to expand...
Click to collapse
It's an issue on the May 11 build as well.
Sent from my moto g(7) power using Tapatalk
Glad you can confirm. Location services also seem to be nonfunctional at the moment.
I installed the latest build (May 14th) on my device and all audio output is now broken (including calls). I have a XT1955-2.
edit: I flashed the May 11th build over the top and audio is working again.
My Moto_G7_XT1955-5_ ocean is mute completely with May 14th build.
bluetooth speakers work.
fastness said:
My Moto_G7_XT1955-5_ ocean is mute completely with May 14th build.
bluetooth speakers work.
Click to expand...
Click to collapse
That was part of a test to see if there were audio issues. It will be reverted eventually.
Greek2me said:
Glad you can confirm. Location services also seem to be nonfunctional at the moment.
Click to expand...
Click to collapse
I'm on the May 11 build and my GPS locks faster than it ever has and it's very accurate on my device. I'd even go so far as to say its faster than stock. I haven't used maps ever on my 1955-5 except on rare occasions when testing a rom but when I saw your location is off post I flipped on location tile opened Google maps and probably 2 seconds after that the dot showed just outside my bedroom window at my house. Going to run a few tests now and see what the outcome is just for kicks but seems good on my end on the May 11th build.
Yes, location is working now on the May 11th build.
I'm not sure if this is the fault of the OS, but my SMS messages are being received late and in batches. It seems that I sometimes don't receive SMS messages until I unlock the phone and open the Messages app. Is anyone else experiencing that?
Greek2me said:
Yes, location is working now on the May 11th build.
I'm not sure if this is the fault of the OS, but my SMS messages are being received late and in batches. It seems that I sometimes don't receive SMS messages until I unlock the phone and open the Messages app. Is anyone else experiencing that?
Click to expand...
Click to collapse
I get that now and I'm not rooted yet
The night light / blue light filter doesn't seem to work in the May 11th build.