I wiped and installed via TWRP and have no problems. Not sure why LR would make a difference (unless it manages partitions differently)?Sounds like you wiped via TWRP instead of via Lineage Recovery when you installed maybe?
I wiped and installed via TWRP and have no problems. Not sure why LR would make a difference (unless it manages partitions differently)?Sounds like you wiped via TWRP instead of via Lineage Recovery when you installed maybe?
I suspect that a wipe in Lineage recovery is actually the same as format data in TWRP.I wiped and installed via TWRP and have no problems. Not sure why LR would make a difference (unless it manages partitions differently)?
It is not often - we reserve space on partitions on FDE devices for encryption - TWRP doesn't sometimes.I suspect that a wipe in Lineage recovery is actually the same as format data in TWRP.
?So is the complete lack of wide vine support ever going to be fixed?
Does Netflix or the like work?Nope it doesn't. Drm info shows no widevine support. Unless I'm reading it wrong. There's no widevine tab at all.
I'll look into this. Thanks.
Nope. We have kernel 3.10 without BPF support, so we can't ever properly run anything over 18.1 officially.Just a short thanks to the Devs for keeping all humming - big update this week.
There is an LineageOS 19/ A12 build out for Nexus 6 Shamu but I dunno, reports suggest it is not as stable as what we have here. See https://xdaforums.com/t/rom-unofficial-lineageos-19-1-for-nexus-6.4443649/page-1
Has there been any thought about an LineageOS 20 / A13 ROM?
Replacement battery came in last saturday... Swapped it in ASAP and after 3 charge cycles accubattery says its state of health is 97% vs. the theoretical 3220mAh !On another note my shamu's 2nd battery has died after 4 years (getting the Sudden Shutdown at 54% ).
So I just ordered a new battery cause I can't let my shamu go !
Just to partially answer my question:Hello,
I successfully followed the install guide and have Lineage 18.1 and MindTheGApps on my trusted Nexus 6.
However, the device is not Play Protect certified now and therefore Disney Plus or Netflix are not working.
With the known GFS ID I tried to register on google's site, but during registration my ID is not accepted (the box turns red).
What can I do in order to use these above mentioned apps?
Thanks in advance!
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
That paper doesn't understand how any of this works, and the fact it paints /e/ in a good light really makes me question it's integrity. Plus, the chart that shows the "reporting" we do to google - none of it is correct. We do none of that - unless you install gapps - which is an aftermarket user choice.Interesting Privacy article out 6 Oct, lots on the interweb today. Android in general, and also LineageOS discussed. There is the usual tradeoff between data needed for functionality and innovation vs just revenue. The point is it could be more transparent, and give users some choices.
Full article: https://www.scss.tcd.ie/Doug.Leith/Android_privacy_report.pdf
Nope! Builds are rolling right now!I can't believe my eyes!! Thanks!!!
EDIT: Wait... is this an april fools joke? -__-
No I'm just crazy busy, it's on my to-do list albeit low atmAwesome to see the continued development!!
I assume the IMS development has been dropped? https://github.com/wavedashdoc/android_device_moto_shamu
Thank you for the tip an nudge in the right direction !!!Maybe deleting the .key files like explained here could be a workaround.
Google removed the support for our legacy hardware based hashing of passwords/pins/patterns, ..
Our wiki unfortunatly doesn't state that a wipe is needed. I'll be adding that.
Like said above maybe deleting the .key files is a workaround, but we can't make it the default install method for obvious reasons.