[ROM][(Un)OFFICIAL] LineageOS 15.1 for Nexus 6 (shamu)

[learlyman]

That's your weapon of choice:

https://play.google.com/store/apps/details?id=com.digibites.accubattery

...

Thanks very much for that! I've installed it and it's giving me great information.

The charging weirdness continues though. It stopped charging through USB until I turned it off - I let it charge while off, and then turned it on with the USB still connected, and it kept charging and it now also has the LED under the top speaker grille lighting up blue while charging which it didn't before - no idea where that is coming from now.

I charged it to 100% and then let it drain back down to 70%, put it on the wireless charger, and it's now wireless charging with the charge current (according to AccuBattery) fluctuating between 100mA and 800mA.

 

[Sam Nakamura]

Thanks very much for that! I've installed it and it's giving me great information.

The charging weirdness continues though. It stopped charging through USB until I turned it off - I let it charge while off, and then turned it on with the USB still connected, and it kept charging and it now also has the LED under the top speaker grille lighting up blue while charging which it didn't before - no idea where that is coming from now.

I charged it to 100% and then let it drain back down to 70%, put it on the wireless charger, and it's now wireless charging with the charge current (according to AccuBattery) fluctuating between 100mA and 800mA.

What does it say about the remaining battery capacity (at the 'health' tab)? Charging madness usually comes from a pretty worn-out battery, if it's remaining capacity is below 70% you're on the right track, mine was virtually useless when it hit 55% and made al kinds of nonsense when charging and also switched off after 20 minutes of use, with big chunks of charging percentage missing once I was able to restart the device...

Sent from my Pixel 2 XL using XDA Labs

 

[learlyman]

What does it say about the remaining battery capacity (at the 'health' tab)? Charging madness usually comes from a pretty worn-out battery, if it's remaining capacity is below 70% you're on the right track, mine was virtually useless when it hit 55% and made al kinds of nonsense when charging and also switched off after 20 minutes of use, with big chunks of charging percentage missing once I was able to restart the device...

Still working on letting it go through a few charge cycles. The first charge (via USB) it showed 55%, for the wireless charge session it showed 90%. I think the truth should be somewhere in between, especially since I'm not seeing any wonkiness yet like phone turning off at 50% charge, or with high current draw (tested by watching 720p youtube videos).

 

[learlyman]

So something very weird is going on.

If I boot the phone without USB plugged in, it will not charge via either USB or Qi charger. It detects the connection (battery indicator shows lightning bolt) but will not actually charge. The Indicator LED won't turn on, but will turn on red when low on battery.

If I turn the phone off, plug it into USB, let it charge while "off", and turn the phone on while it is still connected, it will charge via both USB and Qi, until I turn it off again. In Lineage, The LED under the top speaker grille will light up blue while charging.

I turned the phone off, unplugged it, and booted into bootloader. There placing it on the Qi charger shows "Battery OK (Charging)", LED not on - as there is no battery charge percentage, I can't determine if it is actually charging.
Booting from Bootloader into TWRP, there is no charging.

I turned the phone off, plugged USB in, booted it, (so charging worked), and then did an advanced reboot into recovery. TWRP shows charging. I unplugged USB and placed the phone on the Qi charger, and charging works here as well.

So, these observations lead me to believe that charging (whether USB or Qi) is only working if the phone is charging before booting it.

Is it possible that some hardware component necessary for charging (a charge controller, one could say) has to be initialized in order to allow charging, and this only happens properly when the phone is booted into "offline charging" mode, and it then stays initialized until the phone is turned off - but when the phone is turned on while "fully" off, Lineage fails to initialize this?

Do I need to reflash or am I jumping to conclusions?

 

[githyanki]

So something very weird is going on.

If I boot the phone without USB plugged in, it will not charge via either USB or Qi charger. It detects the connection (battery indicator shows lightning bolt) but will not actually charge. The Indicator LED won't turn on, but will turn on red when low on battery.

If I turn the phone off, plug it into USB, let it charge while "off", and turn the phone on while it is still connected, it will charge via both USB and Qi, until I turn it off again. In Lineage, The LED under the top speaker grille will light up blue while charging.

I turned the phone off, unplugged it, and booted into bootloader. There placing it on the Qi charger shows "Battery OK (Charging)", LED not on - as there is no battery charge percentage, I can't determine if it is actually charging.
Booting from Bootloader into TWRP, there is no charging.

I turned the phone off, plugged USB in, booted it, (so charging worked), and then did an advanced reboot into recovery. TWRP shows charging. I unplugged USB and placed the phone on the Qi charger, and charging works here as well.

So, these observations lead me to believe that charging (whether USB or Qi) is only working if the phone is charging before booting it.

Is it possible that some hardware component necessary for charging (a charge controller, one could say) has to be initialized in order to allow charging, and this only happens properly when the phone is booted into "offline charging" mode, and it then stays initialized until the phone is turned off - but when the phone is turned on while "fully" off, Lineage fails to initialize this?

Do I need to reflash or am I jumping to conclusions?

Check the charging port for lint or something.
Use a toothpick to clean in there.

 

[dbrickg]

looks like lineage os is no longer supporting 15.1! so sad!

https://www.lineageoslog.com/15.1/shamu

"The selected device is not currently supported in LineageOS 15.1 .... RIP Oreo"

 

[Elektroschmock]

looks like lineage os is no longer supporting 15.1! so sad!

https://www.lineageoslog.com/15.1/shamu

"The selected device is not currently supported in LineageOS 15.1 .... RIP Oreo"

I gave you a heads up some weeks ago.
15.1 is still supported, but there won't be automated builds anymore. You can still build it yourself - the guide is pretty straightforward.
Sorry that I can't do more for users still relying on 15.1 builds, but I am running aut of time and discspace.

 

[ktmom]

@Elektroschmock you have gone above and beyond for our beloved Shamu. Thank you for all of your efforts these last few years!

 

[dbrickg]

I gave you a heads up some weeks ago.
15.1 is still supported, but there won't be automated builds anymore. You can still build it yourself - the guide is pretty straightforward.
Sorry that I can't do more for users still relying on 15.1 builds, but I am running aut of time and discspace.

Yes, I understood. Thanks. And thank you for all your efforts keeping it afloat. Nevertheless, it's always a bit of a shock when something you love goes away, even though you *knew* it was going to

 

[mrk2815]

i figuredt that over time it would be best to be current as possible with whatever developer would support nexus 6 through whatever rom. at least we do have a lineage 16. those jus move on to lineage 16. til we havea stable lineage 17.1 for our device. our device will be 6 years now and still receiving support is a blessing to us. most developers afte a certain amount of time move on to the next thing or device.

 

[thetallguy]

I gave you a heads up some weeks ago.
15.1 is still supported, but there won't be automated builds anymore. You can still build it yourself - the guide is pretty straightforward.
Sorry that I can't do more for users still relying on 15.1 builds, but I am running aut of time and discspace.

Yes we were warned and yes I am OK with it. I have been staying on 15.1 for two reasons. The first is obvious, the Voice over LTE. But actually down here in the South Pacific I have never had the ability to use VoLTE anyway. The three providers here never implemented VoLTE until they started installing 5G recently. I suppose 5G makes it compulsory. The provider of my prepaid SIM recently announced they have improved sound quality. But in the fine print they say it is limited to about 4 models which they currently sell in their shop, conservative buggers. I still can't use it. Rant over.
The other is that Google limited the rate of WiFi access point scanning in Androind 9, making apps like WiFi Analyzer less useful. I like to find out what is nearby before picking a channel on my own AP and keep an eye on changes in the neighbourhood.
Many thanks for keeping our Nexus 6s viable. Mine has outlasted my friend's Nexus 6P which has had all of the battery/charging and bootloop issues known in that model. Mine also has the original battery still going OK. I will upgrade to LineageOS 16.0.

 

[woodcarver]

Huge thanks for all the hard work! Can anyone tell me if 16 is as smooth as 15.1 now? I had lag and dropped frames in animations/swipes back in December or so.

 

[ProBird79]

/shamu-lineage-15.1-builds/lineage-15.1-20200501-UNOFFICIAL-shamu.zip
/shamu-lineage-15.1-builds/lineage-15.1-20200501-UNOFFICIAL-shamu.zip.md5sum

Thanks for building 15.1!! Would you mind posting your 15.1 builds here in the 15.1 thread or start a new thread? Do you plan to give continuous updates?

 

[dwardo]

Thanks for building 15.1!! Would you mind posting your 15.1 builds here in the 15.1 thread or start a new thread? Do you plan to give continuous updates?

I can indeed post them here from now on... I guess I can rebuild whenever @Elektroschmock informs he's pushed something worth it or someone sees there have been security updates to 15.1 that are worth a recompile.

 

[ProBird79]

I can indeed post them here from now on... I guess I can rebuild whenever @Elektroschmock informs he's pushed something worth it or someone sees there have been security updates to 15.1 that are worth a recompile.

I tried a clean flash using Open GApps stock and get a black screen with the back arrow during setup (after the choice of setting up as new or restore from the cloud). I can't proceed further.

 

[razorloves]

I tried a clean flash using Open GApps stock and get a black screen with the back arrow during setup (after the choice of setting up as new or restore from the cloud). I can't proceed further.

That's a known opengapps issue.
The Chrome apk in arm opengapps has been broken since march 17. (their zip building script is stripping the certificate from the Chrome apk, which results in android rejecting it so it fails to install)
That black screen happens in setupwizard when webview is missing, and webview is provided by the Chrome apk in stock opengapps.
Just use an older opengapps build (before 17 march) and it will work fine.
https://sourceforge.net/projects/opengapps/files/arm/20200311/

UPDATE: It's fixed now so you can use current builds.
https://gitlab.opengapps.org/opengapps/arm/-/merge_requests/3

 

[0sA]

There will be any further unofficiall updates or we have to move to LOS 16 or 17?

Wysłane z mojego Nexus 6 przy użyciu Tapatalka

 

[ProBird79]

There will be any further unofficiall updates or we have to move to LOS 16 or 17?

Wysłane z mojego Nexus 6 przy użyciu Tapatalka

That will depend on @dwardo or anyone else that knows how to compile a ROM. I hope they continue support as I won't be able to use LOS16 and beyond since I need IMS.

 

[dwardo]

Waiting for the latest security updates to make it to 15.1 then I'll make a new unofficial build

 

[dwardo]

I just updated the Top Post and provided links to download the lastest UNOFFICIAL build (from today) with june 2020 security bulletins included.

Don't forget to also read the instructions about migration from OFFICIAL to UNOFFICIAL