yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] id242:
The solution is just a few posts above yours.

https://xdaforums.com/showpost.php?p=76104778&postcount=2323

And also just a few post above that one.

https://xdaforums.com/showpost.php?p=76102387&postcount=2296
[Nexus 6  Original Android Development] johnyg07:
Bluetooth pairing worked with a fresh flash of rom. I was attempting to have the data mounted in twrp, was getting error for encrypted data mounted point, eventually have the storage unencrypted after several wipe/format/flash.

Phone working good so far.
[Nexus 6  Original Android Development] dbrickg:
I can't get netflix 4.6 to install. the installer asks if i want to install, then goes through motions like it's trying to install, then says "App not installed". I can remove the newer version that's already there or not. Doesn't seem to make any difference. I never watch netflix on my phone, but it's nice to be able to search for stuff and add it to my list via the phone rather than stupid remote control alphabet interface :) I guess I'll just use the web version of netflix to add stuff.

The netflix dvd app works just fine, by the way, but the dvd branch of netflix and the streaming branch seem to have completely divorced from each other
[Nexus 6  Original Android Development] barbara-luise:
Right now, I’m facing the same problem.

Could you please explain what you exactly did to get the storage unencrypted?

I’ve already done a factory reset and formatted the data partition in twrp. Still no luck, twrp keeps asking me for the password....
[Nexus 6  Original Android Development] ProBird79:
Is everyone's Display Mode working correctly? I'm experiencing that it won't switch from day to night when automatic is selected.
[Nexus 6  Original Android Development] Hirnlego:
You have to use your own pin. Sometimes it fails. Just try again, it should work.
[Nexus 6  Original Android Development] mugendon:
There are more people reporting this problem. For example I didn't set a screen lock on first boot, but the storage still got encrypted. So I tried the "default_password", but that didn't work after many tries. Also other people who set up a pin/password/pattern had a similar problem with unlocking in twrp (of course with their pin/password/pattern(pin)).
[Nexus 6  Original Android Development] barbara-luise:
Did you solve the problem and if so, how?
[Nexus 6  Original Android Development] mugendon:
Formated userdata to unencrypt, installed magisk this time before first boot and suddenly the encryption was not forced. Not sure if this was because of magisk, since others reported the force encrypt seemed not to happen every time. So I am now staying unencrypted (like I did on stock anyway).
[Nexus 6  Original Android Development] steelsson:
shamu после обновления на 15.1 перестал просыпаться по двойному нажатию, хотя засыпает правильно. И не только у меня.

shamu after updating on 15.1 has ceased to wake up on double pressing though falls asleep correctly. And not only me.
[Nexus 6  Original Android Development] deathpod:
Tap to wake (under the advanced menu in Settings -> Display) is off by default in Oreo. Did you enable that option?
[Nexus 6  Original Android Development] Elektroschmock:
Yes sorry it's not working right now. Currently my screen is broken and touchscreen is partly unresponsive. So I'm not able to test it propperly.

Off is the default now. You can enable it once it's fixed.

[MENTION=535343]all[/MENTION]

please use the new LineageOS 15.1 thread from now on.
[Nexus 6  Original Android Development] mugendon:
For the lazy: LineageOS 15.1 thread
[Nexus 6  Original Android Development] barbara-luise:
Did you by chance know whether twrp's failure to unlock the encrypted partition will have a negative effect on future ota updates, i. e. that such updates cannot be installed because twrp can't unlock the encrypted partition?

EDIT: Sorry, didn't see the new thread in time.
[Nexus 6  Original Android Development] mugendon:
TWRP can't access files on the internal storage if it is not unlocked, so it is likely it won't work. But this is just a guess and it could be that the updater does some tricks, which makes it still work.
[Nexus 6  Original Android Development] srnoth:
Solved on my end by fastboot flashing the latest factory image, letting it boot (and encrypt the data partition), then flashing back twrp and LOS 15.1 (doing a factory reset in twrp without actually formatting the data partition).

Can access the data partition in twrp with my PIN now (or without any prompt when I didn't have a pin set).
[Nexus 6  Original Android Development] mrk2815:
can some one give the direct link to the new lineage 15.1 XDA thread for posting for nexus 6.tried googling for it but cant find it.
[Nexus 6  Original Android Development] aankkurr:
Check 3 posts above yours.
[Nexus 6  Original Android Development] dwardo:
Been having the magisk uninstalling itdelf or disappearing since beta1... Haven't figured out what is going on...

Also noticed some app configurations also disappear as i need to reenter their login and password from time to time... Wo dering if these occurences are linked
[Nexus 6  Original Android Development] _AnAkIn_:
Having exactly the same issue with Magisk and also random reboots while being on a call.
[Nexus 6  Original Android Development] mikevb:
When Magisk "uninstalls itself", I just need to reboot to fix it. And I've only had it happen randomly while phone is in use, never as a side-effect of a random reboot.
[Nexus 6  Original Android Development] barbara-luise:
This finally fixed the Problem for me, too.: I installed the latest 14.1 build, rebooted into twrp and then followed the "official" Installation instructions ( https://wiki.lineageos.org/devices/shamu/install )

It is worth noticing that twrp stopped asking me for a password after I installed the latest los 14.1 build. Therefore, there must be something wrong with the current los 15.1 build.
[Nexus 6  Original Android Development] Fred Simm:
This is what I did about the twrp password problem. I used a mixture of ideas from the kind people here. Hooked N6 to my laptop with adb functional in developer settings. I had all the files in a folder on the laptop desktop. Booted to recovery. I did a full wipe including storage. I formatted data like many suggested. This is an important next step. Reboot recovery to verify the password is not required. I did and password request was gone. My phone storage now showed on my PC with twrp booted. I created a download folder on my phone and transferred Lineage 15,

Gapps, and magisk. Rebooted recovery one more time to verify password was gone and files were available. Installed all and rebooted system and all is well. Thanks everyone for the guidance.
[Nexus 6  Original Android Development] wrsg:
Will 14.1 get security updates or is support ended?
[Nexus 6  Original Android Development] xNotta:
Why does this rom cause Google to think my phone is a Xiaomi MI6? And how can I fix it to say Nexus 6?

The build.prop says shamu and Nexus 6.
[Nexus 6  Original Android Development] Elektroschmock:
Yes official builds haven't started yet and I haven't added shamu to the build targets yet.

Official builds coming from LineageOS will be signed with a private key. This means you have to do a clean install.

You can flash whatever funky stuff you want, but don't blame me if thing crash left and right. :p
[Nexus 6  Original Android Development] Mario_Awe:
Hello Elektroschmock,

Installed EX kernel manager a few days ago without changing any governor related settings. Just wanted to ask if it is usual/intended by your custom kernel, that two cores get disabled when dropping below ~40% of battery?

Thanks in advance
[Nexus 6  Original Android Development] LordDeath:
I don't understand this. Can you elaborate, please?
[Nexus 6  Original Android Development] RegnierD:
There is an identifier (key) built into all roms (even official ones from OEMs) that defines what kind of rom it is and can additionally can also "sign" it with that "key." This is very similar to how Google signs its roms and the key must match in order to receive an OTA. Since they will be signing the rom with a private key, it will require a fresh install in order to make sure things run smoothly. Changing the key on an already installed rom (I'm not even sure if that's possible, the zip may fail to install at all when trying to flash) is a cause for serious issues so a clean install will make sure everything runs smoothly.
[Nexus 6  Original Android Development] stw303:
Thanks RegnierD.

So after the initial clean install, future builds can be dirty flashed since they contain the same key?
[Nexus 6  Original Android Development] Elektroschmock:
AFAIK this is the default behaviour. I can try to look into this once I get my ****ty buildbox back running.

Right! Once you do a clean install you can dirty flash or use the LineageOS-updater.

But you have to wait for the first official build from our buildserver as I don't have the signing key.
[Nexus 6  Original Android Development] drmuruga:
Is there any chance of getting cmte like theme engine ? I don't like substratum.
[Nexus 6  Original Android Development] mdlf:
+ 1
[Nexus 6  Original Android Development] getbricked:
I've done a clean install of the ROM and Gapps and I've also flashed the bootloader and radio with fastboot, but i still have an ongoing issue. I don't have any cellular network. I've searched for hours on various threads and nothing I have tried has worked. I have service and ccan make text's and calls with no issue, just no data.
[Nexus 6  Original Android Development] krishnexus:
Any time-frame for the official release? I'm waiting for this since all other roms use substratum and I find that cumbersome and not as good as the old CMTE
[Nexus 6  Original Android Development] tnthd2:
You do have cellular network. Have you checked the APN settings for your carrier yet?
[Nexus 6  Original Android Development] getbricked:
Yes I've tried everything that I could find/think of.

---------- Post added at 03:41 AM ---------- Previous post was at 03:08 AM ----------

Yes, I have cellular network. It works perfectly fine on any other 7.1.1 ROM, but this one seems to be giving me issues.
[Nexus 6  Original Android Development] rvholla:
Can your unofficial version dirty flashed on earlier lineage (4/1/17) nightly?
[Nexus 6  Original Android Development] Elektroschmock:
Sorry no ETA

Yes you can do that.

New unofficial Build in my Gdrive.

Please test if the speakerphone issue is fixed for you.
[Nexus 6  Original Android Development] tnthd2:
The later builds seem to have fixed this issue even with dirty flash, but I'll try clean install for sure since I haven't done that for quite a while.
[Nexus 6  Original Android Development] Isley_:
I have a little issue with last build, I use a custom kernel and when I set the KCAL values after the screen goes off the values reset. Is there a way to disable color calibration so the values stick?
[Nexus 6  Original Android Development] tnthd2:
Who is your carrier and can you post a screenshot of your APN settings page?
[Nexus 6  Original Android Development] tnthd2:
Took me a while to test again. The Battery Saver page has been fixed, but the phone still shuts down suddenly again. Happened twice, but not at 9℅ anymore but rather randomly at 12℅ and 14℅. This includes the latest build 20170114.

I usually use the phone until the red LED turns on at 15℅ then plug in the charger. But the LED hasn't turned on lately with all the Unofficial builds, so that's why I haven't noticed the battery's gone down below 15℅. Well, the shut down lets me know anyways :D

Will try a clean reinstall to see if there's any difference. Thanks for all the builds!
[Nexus 6  Original Android Development] Popo001:
Sorry to say that but it's not a ROM issue IMO, but a hardware one :/ (happens also on stock ROM).

I have the same problem and even happens at 70%+ battery now. I googled it a lot and it seems to be a very common battery issue with the N6. I'm curently waiting for my new battery, it should solve this issue once replaced.
[Nexus 6  Original Android Development] ASHLEY117:
Latest build I can see in your Gdrive is 20170108. Should there be a more recent build?
[Nexus 6  Original Android Development] Dhalsim43:
Don't you have Magisk with safetynet fix ?
[Nexus 6  Original Android Development] steelsson:
when there will be a new update?
[Nexus 6  Original Android Development] Elektroschmock:
There will be no more builds for 14.1 as we now have builds for 15.1.
[Nexus 6  Original Android Development] 0sA:
Sad information... LOS 14.1 looksvery stable and bugfree.

15.1 is on its early stages, right? It could has some problems on the beginning of the development.

Updated (security fixes) 14.1 would be the best option for now. [emoji853]

Wysłane z mojego Nexus 6 przy użyciu Tapatalka
[Nexus 6  Original Android Development] Elektroschmock:
Sorry this was no option. Otherwise I would have chosen this way.

LineageOS only has limited build server capacity as they have to be paid with donations.

If a device receives weekly builds for 15.1 the builds for 14.1 have to be stopped.

https://www.paypal.me/LineageOS
[Nexus 6  Original Android Development] Elting:
Hm, wanted to flash the new build (with full wipe) with oreo gapps but got an error 7....

What's the problem here?
[Nexus 6  Original Android Development] gothy.gothy:
Are you on 3.2.1.0 TWRP?
[Nexus 6  Original Android Development] Elting:
That was the problem.... :angel:
[Nexus 6  Original Android Development] wrsg:
Will the 14.1 Github code also stop receiving updates? I might end up building my own 14.1 from the github source, I agree with 0sA, 14.1 is stable and reliable for me. I can't use 15.1 as I depend on this for business and many people seem to be reporting issues with Bluetooth and reboots (situation may have changed?)
[Nexus 6  Original Android Development] Elektroschmock:
Lineage 14.1 will still receive updates, as not all devices have or will make the jump to 15.1

However the shamu's device and kernel repo won't receive updates.
[Nexus 6  Original Android Development] David B.:
But what if you want to encrypt your device? As I understand it, your device is not encrypted right now.
[Nexus 6  Original Android Development] Fred Simm:
Encryption is not a priority for me. Someone else may have to answer.
[Nexus 6  Original Android Development] David B.:
It's not that it's really a priority for me. It's just that from a security perspective, it seems like a terrible idea to not have it enabled. I understand that having an unlocked bootloader is technically not secure either, but it's a lot more difficult for someone to get to your data if it's encrypted.
[Nexus 6  Original Android Development] wrsg:
I know the official builds are 15.1 now, but would it be asking too much to have a monthly build of 14.1 so that people using 14.1 for whatever reason can get security fixes?
[Nexus 6  Original Android Development] Elektroschmock:
Sorry that's not possible as we don't have enough build server capacity.

Also security fixes don't apply themself. I need to do them manually which is sometimes not easy.
[Nexus 6  Original Android Development] v8088:
In every CM and LOS firmwares on any my phones I have non-colorized icons in status bar.

But on stock firmwares on Samsung phone it's colorized.

How can I make it colorized?

Thanks in advance.
[Nexus 6  Original Android Development] yagabund:
LTE Only

Hi. How to enable the "LTE only" mode? *#*#4636#*#* does not work. When will this bug be fixed?
[Nexus 6  Original Android Development] Elektroschmock:
Never!

Lineage 14.1 is dead.
[Nexus 6  Original Android Development] yagabund:
But I'm using 15.1 20180515
[Nexus 6  Original Android Development] Elektroschmock:
Then you're posting in the wrong thread.
[Nexus 6  Original Android Development] yagabund:
Exactly. Sorry, I'll post a message in the right thread.
[Nexus 6  Original Android Development] LexX-V:
As I see there will be no more ability to download 14.1 from official server soon.

The last official build mirror - Snapshot 20180324
[Nexus 6  Original Android Development] Wasatch_Oz:
Sorry. 14.1, not 15.1. Delete.
[Nexus 6  Original Android Development] ocbones:
Hello guys hope u can help me out, i just upgraded to	lineage-15.1-20180814 from	lineage-15.1-20180807 and there is lag issues, i see under the the change logs that there has been some changes to the power settings.

power-8084: reduce interactive boost

* 1,1 GHz min freq is more than enough for interactive boost on apq8084

* default duration is unnecessarily long, reduce to 200 ms

* 1,5 GHz min freq on 2 CPUs for 1 sec is entirely sufficient for

launch action

i tried to downgrade with no luck and get stuck in the lock screen.

I understand this is done to save battery but i have no issues with battery life, and was hoping that the changes would not effect people that have settings set to performance under battery settings.

for an old phone like this every speed boost is a must for me to continue using this phone. is there any hopes of this getting fixed in the next build? would really love to keep using the latest lineage keep up the great work guys!
[Nexus 6  Original Android Development] ExpectedCrayon:
You can try changing your power profile in Settings > Battery > Battery saver and performance.
[Nexus 6  Original Android Development] runekock:
[MENTION=658816]ocbones[/MENTION]

Try Popcorn kernel and/or change settings with an app like Kernel Adiutor or EX Kernel Manager.
[Nexus 6  Original Android Development] IMAGI0:
thank you very much
[Nexus 6  Original Android Development] yoyo ma:
Verizon Nexus 6

I have problems with LOS 17.1 receiving phone call. I can make phone call and received text but not phone call. Does anyone using Nexus 6 on Verizon network have this issue?
[Nexus 6  Original Android Development] runekock:
If Verizon requires 4G for calls, you cannot use any recent rom. Some networks allow the phone to change to 3G for calling, and then it works fine - but 4G calling (VoLTE) requires a functioning IMS, and that won't work beyond Oreo (LOS 15.1).

BTW, there is another thread for LOS 17.1, this one is for 14.1.
[Nexus 6  Original Android Development] stanis64:
Hi, it is possible to implement easy data toggle so it works same as wifi and bluetooth? In the first notification panel pull down you can just turn on/off service but after the second pull down you can access the data usage. Thanks ?
[Nexus 6  Original Android Development] tnthd2:
I have 2 Nexus 6s and both work properly with CM13. Red LED always turns on at 15℅ and no shut down whatsoever. I don't recall if it even happened with CM14.1.

This issue wasn't random at first, but it was related to a documented bug incorrectly detecting battery level lower than 10℅. Looks like now instead of 10℅, it's somewhere at less than 15℅. When shutting down, it always says 2℅. But when plugged in while the phone still off, the battery reads 12℅ or 14℅. That's the only way I would know it was actually 12℅ or 14℅. Similarly, before it was always 9℅.
[Nexus 6  Original Android Development] id242:
Its battery related. The same thing happens on stock. And its not limited to the Nexus 6. When your battery has aged, its health declines.

The percentage you see in your notification bar, is generated based on design capacity. As you go through charges and discharges, your battery's health wears down over time. Each cycle makes it wear just a little bit more.

The Nexus 6 design capacity is 3,220 mAh.

If your device is prematurely shutting off at 10% or any time under 40% when you perform a processor intensive task (such as camera flash, open maps/GPS, photos index...etc), then your battery's health is most probably poor. Your device isnt getting the minimum power which is required for that single burst-task, and so it shuts down. This would explain why when you turn your device back on, the battery meter still reads in the 10% to 35% range. The also confirms why you may remember your battery lasting an entire day when your device was new, but today it last much less. Its current health may only be 2,550 mAh (about 80% of design capacity) of what it once was.
[Nexus 6  Original Android Development] EasyDeath:
I have to delete all my data or only system and cache?

I don't want to reset setting of my aps... At this rate I prefer the unofficial version, for now it's working perfectly
[Nexus 6  Original Android Development] Elektroschmock:
No one want's to lose his data. Some devs are working on a migrating solution. You'd have to flash a special build one time. After that you should be able to update without losing your data.

[MENTION=535343]all[/MENTION]

Was anyone able to test if the speakerphone issue was fixed with the last Unoffical build?
[Nexus 6  Original Android Development] cyan86:
is stable??
[Nexus 6  Original Android Development] dbrickg:
Hmm, what do you mean by "stable"? No, of course they're not stable! They're so unstable they'll make your phone explode into a million pieces! Better run away right now. Even reading any of the postings in this thread could be dangerous to your health :)
[Nexus 6  Original Android Development] tnthd2:
With 2 Nexus 6s running mostly the same CM nightlies for more than a year until the last CM14.1 build before CM closed shop, I know the difference between battery capacity problem and software bugs. Until a couple of weeks ago, there was no early shutting down or no-red-light at 15℅ problems.

I also never said the battery meter read 12-14℅ when I turned the phone back on. I said the battery read those number when the phone was still off.

In any case, I just flashed the latest Nightly (not Unofficial) 20170115 build and there's no early shut down yet. As I'm writing this on the phone, the battery reads 6℅ right now. Still no red LED though.
[Nexus 6  Original Android Development] Popo001:
Open the camera app then, and you'll be sure if there is still a problem or not.

As I said, this problem is not ROM dependent, it happens suddenly and gets worse and worse over the time.

I'll get my new battery this week and should replace my old one soon. I'll post again to tell if it fixes this problem for good.
[Nexus 6  Original Android Development] :
nightly almost ready :D

bootanimation is ready https://review.lineageos.org/#/c/156893/
[Nexus 6  Original Android Development] Elektroschmock:
It's not. :p

The bootanimation has never been a blocker for the weekly builds.

Removal of SU, smooth transistion from CM to LOS, signing and the LOSupdater are the last blockers.
[Nexus 6  Original Android Development] Xenosis:
Camera app crashes like crazy for me. About every two photos it crashes and usually at least one is either corrupted or isn't saved.
[Nexus 6  Original Android Development] rignfool:
You're using HDR and not letting the photos finish processing...
[Nexus 6  Original Android Development] liriolebron:
Wich one do you recomend? Cm14.1 or LineageOS?
[Nexus 6  Original Android Development] Elektroschmock:
CM is dead long live LineageOS. :D
[Nexus 6  Original Android Development] tnthd2:
It's the battery problem on your phone, and I know nothing about your phone to say otherwise. At this moment, my phone still has at least 4 hours of screen time and camera works fine as intended. 60℅ or more at the end of working day doesn't yet indicate a dying battery problem to me.

PS: And why did you insist my phone had the same problem as yours while you knew nothing about my phone? My previous post was written on this phone after midnight at 1am, after a whole day of normal usage plus flashing a new LOS build. Does that indicate a dead battery to you?
[Nexus 6  Original Android Development] LordDeath:
What is the current status of supporting themes? Is work on CMTE still going on? Or are they instead going to add OMS to LineageOS?
[Nexus 6  Original Android Development] Elektroschmock:
https://review.lineageos.org/#/q/topic:cm14-themes+status:open

That's the latest 'news' regarding themes.
[Nexus 6  Original Android Development] dbrickg:
just now installing the 12/17/17 unofficial lineageos ... looks good so far ... new boot animation, woo woo!

... still looking excellent this morning. hot dog!