• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][OFFICIAL] LineageOS 17.1 for Nexus 6 (shamu)

Search This thread

Markeee

Senior Member
Sep 29, 2012
1,227
259
South Florida
Wonder if it will affect my Xfinity mobile which supposedly runs off the Verizon's network ?

Is there anyway to check your phone on Xfinity or Verizon see if your phone will be affected ?
May be forced to put the Nexus 6 to rest and get a new phone ?
That would suck


Not necessarily true.....



Try the IMEI check at T-Mobile's website
My Nexus 6 will still operate on T-Mobile's Network after the deadline
 
Last edited:

ProBird79

Senior Member
Jan 13, 2008
224
74
Not necessarily true.....



Try the IMEI check at T-Mobile's website
My Nexus 6 will still operate on T-Mobile's Network after the deadline
That was released by T-Mobile after I posted. Thanks for the added information. It's only a matter of time until VoLTE is needed and when that time comes the N6 will need to be on LOS15.1.
 

Markeee

Senior Member
Sep 29, 2012
1,227
259
South Florida
I could use some help here I was installing testing some of the Android 11 roms and now when I try and restore my twrp nandroid Lineages 17.1 backup it won't allow me to boot to system its just stuck in android oem recovery bootloader luckily I can get back to twrp but it just won't boot back to system ?
 
Last edited:

maddog3030

Senior Member
May 5, 2014
123
48
Nexus 6
I could use some help here I was installing testing some of the Android 11 roms and now when I try and restore my twrp nandroid Lineages 17.1 backup it won't allow me to boot to system its just stuck in android oem recovery bootloader luckily I can get back to twrp but it just won't boot back to system ?
ADB it and re-flash TWRP...
I could use some help here I was installing testing some of the Android 11 roms and now when I try and restore my twrp nandroid Lineages 17.1 backup it won't allow me to boot to system its just stuck in android oem recovery bootloader luckily I can get back to twrp but it just won't boot back to system ?

ADB it and re-flash recovery partition with TWRP, might have to fix (reformat) your other partitions
 

esysfound

Senior Member
Oct 21, 2017
231
194
Anybody find a chance log?....my backup grew to 8.6 GB!!!!
Am watching this as I reported a significant change in Dec., and this was using TWRP 3.4. As always lots of variables so you need to try isolate what is going on.

In Settings menu, Storage you can see more details-look especially at "Other Apps". My System installed seems to have stabilized at 7 GB. The growth seems elsewhere - Map Navigation Apps (the Maps themselves) can take up a lot of space. So do some Email clients like Type and Blue can expand massively (even with no email stored - Lord knows what they are harvesting or due to overly snappy graphics but at one point it was over 1 GB !?). Use stock email app. Google and Play Services also doing their part. Worth going through Apps and tweaking/clearing out, e.g. Whatsapp Stickers etc. Most likely some of these "power" apps changed recently and account for the growth. YMMV.

My TWRP backup was below 8GB for most of year, but it jumped significantly in Nov-Dec (at one point almost 16GB) . Now around 10.5 GB after a lot of cleaning and App removal - (Minions stickers are sadly gone). In my case, most of it is stored navigation maps from Here and opensource Map Me, and Google background stuff that is not easily removed or moved out of the system partition. Some are not fans of CCleaner App and it does have annoying ads, but is an easy way to clean out lots of junk, especially app caches, on a regular basis. Just keep an eye on all, but most likely App growth is the culprit.
 
Last edited:
  • Like
Reactions: maddog3030

jvifdz

Member
Apr 26, 2016
15
0
Hi guys in the last 2 builds i see the notification led is always on (screen of) when i recive a notification, how can i put It on only like 2 seconds?
 

frankybabyd

New member
Jan 12, 2021
3
0
I'm new to all this and did my first install of a custom Rom on my Nexus 6. I chose the latest Lineage 17.1. For me the main reason was because i just found it way too laggy with the stock 7.1 and figured I'd give it a try. I have to say it's amazingly smooth now. However I've noticed one pretty important issue, that I've seen others mention as well and one other I noticed today.

1. I have the problem people mention with the camera crapping out after using it for a few minutes. This happens all the time for me. Nothing except rebooting gets it back working. I had the Dec 30 version and now the Jan 6 version and always have the issue. I made a logcat once I was in the state that the camera doesn't work. I've attached the logcat file here. Is there a bug entered for this already? Otherwise I don't mind entering it. I'm sure many, many people must have this problem, from what I'm seeing in this thread.

2. When using the speakerphone, people on other end hear themselves. I didn't have this problem with the stock 7.1. I 'm guessing there needs to be some sort of code with the microphone that it doesn't transmit what's playing out, that isn't there. I think though that this issue was not there in the Dec 30 version and is there now in the Jan 6 version (it's just my feeling because i don't think people I was talking to complained about hearing themselves when I had the Dec 30 version

Also I don't necessarily need to be on the latest. I just want a working phone, that isn't laggy. I also have a Nexus 5 which i installed Lineage 14.1 and that seems pretty amazing. Are there any people that have the camera problem, that didn't have it in Lineage 15 or 16 ? I don't mind using an older version if the camera and speakerphone work.

One quick question: Using the recovery that came the Dec 28 Lineage 17.1, can i flash Lineage 16.0 ROM and where can I get it? A quick search on google turned up short as they all point to https://download.lineageos.org/shamu which has 17.1...

I ended up creating a bug for this here so perhaps others that have issue too can add comments https://gitlab.com/LineageOS/issues/android/-/issues/2946

Thank you all!
 

Attachments

  • logcat.log
    1,017.4 KB · Views: 1
Last edited:

alfacrux

Member
Jan 10, 2019
32
15
Tallinn
1. I have the problem people mention with the camera crapping out after using it for a few minutes. This happens all the time for me. Nothing except rebooting gets it back working. I had the Dec 30 version and now the Jan 6 version and always have the issue. I made a logcat once I was in the state that the camera doesn't work. I've attached the logcat file here. Is there a bug entered for this already? Otherwise I don't mind entering it. I'm sure many, many people must have this problem, from what I'm seeing in this thread.
Can't confirm it here - camera works as expected. However - just plain LineageOS here, no gapps.
As of earlier (15.1 or 16.0) versions of LineageOS - check the first posts in corresponding threads in https://forum.xda-developers.com/f/nexus-6-original-android-development.3711/ about unofficial builds.
 

frankybabyd

New member
Jan 12, 2021
3
0
Can't confirm it here - camera works as expected. However - just plain LineageOS here, no gapps.
As of earlier (15.1 or 16.0) versions of LineageOS - check the first posts in corresponding threads in https://forum.xda-developers.com/f/nexus-6-original-android-development.3711/ about unofficial builds.
Ok thanks for the link. Don't you need gapps though if you want the Google Playstore? You don't need any apps from the Google playstore? I know you can install apk's but isn't the Playstore sort of a needed basic thing? I guess I can try without Gapps installed to see if I can repro.

Can anyone else that has the camera problem confirm whether they have or don't have Gapps ?

Thanks!
 
Last edited:

frankybabyd

New member
Jan 12, 2021
3
0
I been using Opened Camera its a Camera app still crashes once in a while but works most of the time
I have that one installed too and when it's crapped out, they all don't work. I'm pretty sure if you do any video calling you'll get the problem within a few minutes. I can't go more than 10-15 minutes without it crapping out... Very annoying for an otherwise amazing experience on my Nexus 6.

I'd also like to say that I am not rooted and don't want to be as would like bank apps to work normally. I think I read that I can have Magisk to be rooted, but fake to be not rooted, but that all seems complicated when i don't want to be rooted.

I'm mentioning being rooted, because i think someone said there is an app to Kill Camera, but quickly looking in Playstore, the app I found says you need to be rooted.

Is there an app or something i can do to get camera working without having to reboot?

Thanks
 

Top Liked Posts

  • There are no posts matching your filters.
  • 42
    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.

    Recovery
    The LineageOS 17.1 reovery is recommended
    If you still want to use TWRP never install the TWRP app as system app. Otherwise your device won't boot

    Current lineage 17.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.
    Before you flash a bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one and don't need to flash it 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: https://download.lineageos.org/shamu
    Google apps: Opengapps Use an ARM (not ARM64) package for Android 10

    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.

    Changelog

    Builddate: 2020.06.17
    Changes:
    [new] June security updates
    [new] LineageOS clock

    Builddate: 2020.05.29
    Changes:
    [new] May security updates
    [fix] ULL audio fixes
    [new] Add back serif fonts
    [fix] Screen turning itself on when no lockscreen is set
    [new] Etar calendar

    Builddate: 2020.04.12
    Changes:
    [new] April security updates ROM & kernel

    Builddate: 2020.04.08
    Changes:
    [new] Initial LineagOS 17.1 release

    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-16.0
    [bug] IMS is not working - if you need it you have to stay on lineage-15.1

    XDA:DevDB Information
    LineageOS, ROM for the Nexus 6

    Contributors
    Elektroschmock, elektroschmock, npjohnson
    Source Code: http://github.com/lineagos

    ROM OS Version: Android 10
    ROM Kernel: Linux 3.10.x

    Version Information
    Status: Nightly

    Created 2020-04-08
    Last Updated 2020-04-08
    19
    Is there any chance to have lineage-18.1 on shamu?

    Well code is ready since 'forever' as you can see on the other Android 11 ROMs for shamu which are using Lineage's code. I just don't see a reason to use you users as guinea pigs for testing as long as there are bugs I am able to reproduce. If nothing goes south shamu will be in the first batch of devices receiving Lineage 18.1
    12
    Hi-no the times are sort of real world screen on and off over a typical, normal day.
    I will play with the Ex Kernel Manager but normally using the conservative setting if anything lengthens battery life. (I think it just throttles back clock speed vs tinkering with all the multiple different frequencies. I believe it was designed originally to manage the Elemental kernel, but it is just overhead software really, and can be used with any. See here: https://play.google.com/store/apps/details?id=flar2.exkernelmanager&hl=en

    But it does raise a useful question - what kernel is used with 17.1 and do you have a better solution to manage that vs. just stock tweaks? Thanks

    Okay sorry I think I was unclear in my writing. I know what Ex Kernelmanager and Ex-Kernel is. I'm just don't know exactly what those profiles intend to do and on which sysfs interfaces the manager relies.
    When Exkernel was a thing shamu was still supported by google hence all kernel were mostly the same. Only some stock tweaks like you call them where the difference. With android 8 the different kernels began to drift apart, and most where given up for various reasons. Since android 9 there is only one kernel left for shamu It's the lineage kernel. You might find other kernels, but on the inside they are the lineage kernel with a different name tag applied.

    Answer your questions what this kernel is, is kind of hard, but I try.
    Base Google's 3.10.40 kernel for shamu
    Updated to 3.10.108
    Security patches up to April 2020
    Full RGB LED support. (hint hint I'm proud of this)
    Binder backport from 3.18
    interactive governor updated to 3.18
    various fixes for a lot of subsystems

    What this kernel does not and will never support
    Overvolting
    Undervolting
    Over clocking
    CPU Governors with long and funny names and ****ty function
    faking of bootloader status

    Okay now back to your other questions.
    LineageOS does have has power profiles for you too choose from. You can choose between longer battery life and higher performance. I don't know the exact setting for each profile, but I can look them up for you if you are interested.

    I recommend using these and advise against the use of any kernel manager. Those where never meant to be used on this kernel and can wreck all powersavings. Only use them if you know shamu better then me. ;)
    12
    So it was a coincident? :)

    Curious: did you find the reason for the camera crashes and is it explainable to noobs?

    The app crashed because camera HAL was reporting no camera devices.
    For the HAL to work properly there are two services needed. 1. cameraserver and 2. qcamerasvr.
    Cameraserver needs qcamerasvr running to work.

    So we started qcamerasvr and then cameraserver in the init. At least this was the plan.
    But init is not synchronus which means it can reschedule the starting of those services which could lead to switched starting order.

    See:
    https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/273010
    https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/273406
    11
    just reflashed today build.did aclean install from cr droid to lineage 17.1. So far so good. Will we get the june 2020 security patches in the next set of nightlies. .

    I need some more days, as I didn't have the time yet to update the kernel.