yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] NewDayRising:
IIRC, I did a complete wipe after verifying the correct radio and bootloader were installed, rebooted to TWRP, then flashed the 14.1 LOS + GApps (check for recommended version) + Magisk, encrypted and verified encryption after setup, then repeated the process with a dirty flash of 15.1 and GApps.

I may be missing a step, since it was a while back, and you may or may not want Magisk, that's your call. As for LOS 16, nothing is official. And I haven't searched the forums in a bit, but there might be a version of TWRP in the works to sort the encryption issue, but I may have read that somewhere else.

If I'm missing something, or someone else has anything to add, feel free. As for as LOS and long-term support, that's never guaranteed, but I've been happy with it. Edit: And yes, TWRP still works after the above process.
[Nexus 6  Original Android Development] duhec:
Electroschmock, I have a question.

In another topic you wrote:

And now I see you have a link to the unofficial builds in the signature. I searched if you posted an explanation anywhere and I didn't find it.

So are these builds from you? Are they working, can we test them? What's the background of all this?

Thank you for your answer.

edit: Apologies. When I clicked on the link, the files in Google Drive say "unofficial" that's why the above question. Now I saw it says official preview builds in the signature. :cool:
[Nexus 6  Original Android Development] ChrisDos:
Thank you for your reply. I think I'll be going through those steps and I found my new rom.
[Nexus 6  Original Android Development] NewDayRising:
I may have spoken too soon. Looks like there's a post in r/Android about an official LOS 16 about to drop, with Shamu being a day one device, according to one of the maintainers. Here.
[Nexus 6  Original Android Development] mezerr:
That maintainer also says "We still have a lot to go. Wouldn't bet on this month even tbh. Those wiki changes have been up for a while, don't know why they're getting attention now."
[Nexus 6  Original Android Development] NewDayRising:
Fair enough. I'm still happy with possibility of Shamu being a day one drop whenever it happens.
[Nexus 6  Original Android Development] Sam Nakamura:
That's a big achievement from our handsome shamu/lineageOS maintainer! Much love!!! Well done!

Happy to join the N6 party just yet - found it for a great price in mint condition and couldn't resist...

After having used the N4, N5, N7 I'm absolutely conformable with the N6, it's still working great when being rooted & rom'ed, what a huge thing it is, one got to love it... :laugh:
[Nexus 6  Original Android Development] Elektroschmock:
Yeah I was imprecise. What I meant is: We don't want unofficial builds from others, as it doesn't help anyone tackle possible bugs.

Yes the builds I linked are from me. They are compiled from LineageOS's sources but with our SU included as it's not yet available as seperate download.

Every build not done on our servers is unofficial and is not signed with our private key.

My builds are the official preview builds they are meant for people who can't wait.

For me they are working, but IMS is broken for most pre-Pie devices and it might not be fixable as we don't have the sources.

If you (your provider) depends on IMS features Pie on shamu might not be something for you.
[Nexus 6  Original Android Development] gettes:
I have searched the thread and there are only 3 references to IMS without explanation. Would someone please provide a pointer or 1-2 sentence explanation of IMS? And if someone knows if Google fi depends on it, please indicate so?

Once again, [MENTION=3383960]Elektroschmock[/MENTION] THANK YOU so much for all you do!
[Nexus 6  Original Android Development] magnamentis:
google is your friend, remember the next time ;)

https://www.google.com/search?sourc....1j1......0....2j1..gws-wiz.....0.GR2wy5rjIEE
[Nexus 6  Original Android Development] runekock:
This gives some idea of why it is difficult to get IMS working in pie: https://source.android.com/devices/tech/connect/ims

According to Google, the IMS is provided by the vendor or carrier. This seems to me a strange choice. Wouldn't it be more appropriate for Google to include a reference implementation in AOSP?

When I read about the IMS functions, none strike me as hardware dependent, so no need to do it individually for each phone.

And while I guess that some functions could be carrier dependent, that would mean that you would lose major functionally if you change carrier - unless there is a way to change IMS at the same time, and I haven't heard about that.
[Nexus 6  Original Android Development] MaxPower742:
I think I might be experiencing this. Can you elaborate on how this is done? Googling suggests you need a custom kernel in order to change that value, is there one that works well with this ROM? By "adjust" do you mean turn it up, down, make it more / less aggressive?
[Nexus 6  Original Android Development] mezerr:
If your phone is rooted, download the Kernel Adiutor app. That app can control the stock Lineage kernel. There is a section there called Low Memory Killer. At the bottom, select "Aggressive". Background apps and processes will be terminated earlier so you have more free ram remaining.

Usually, the saying "Free Ram is Wasted Ram" is true.. but with the N6, if the free ram gets below a certain value, chug city for whatever reason...
[Nexus 6  Original Android Development] magnamentis:
the device has only 3GB of RAM and apps nowadays get/got bigger and bigger and ram usage increased.

one can do the following in addition to what you wrote (that is totally correct):

- decrypt the phone if not done already

- set readahead buffer size to <2000

- disable fsync

- set logger buffer size to >1, better 4M

- disable unnecessary (not wanted or not needed) logging at all, many logs are stored on RAM and written to storage in intervals (not all but some)

i'm not speaking against or por one of the above workarounds, only referring to sluggish behaviour and even for those who cannot get totall rid of it, by following above steps it takes a real lot longer to reach to point
[Nexus 6  Original Android Development] Elektroschmock:
Not cool to propose something like that, knowing that many users have really old batteries.
[Nexus 6  Original Android Development] magnamentis:
you are right but i wrote that i do not say all those steps are recommended hence it's not a recommendation but a working way to make the device snappier.

but as i say, you are right its kind of risky on the other hand what's much to loose, strored data on sdcard are safe and the part in the ram would ask for a reflash in the worst case.

as you stated it happened to me with dying battery that i had to re-flash the rom to get it back up running and to redo a few settings but that took 10 minutes.

my devcie is extremely quick now with fsync enabled hence i let it but if i have to choose between days weeks and months of snappiness against a 10 minutes troubleshooting round i'd still chooose to disable fsync.

in short, i did not recommend it but it's personal choice which makes it worthwhile for users to know about the possibility and choose on their own.

thanks for mentioning it howerver and giving me the opportunity to elaborate further

;)
[Nexus 6  Original Android Development] MaxPower742:
Never even realized mine was encrypted. A quick google search suggests I'll need to perform a full wipe from TWRP, making sure to format userdata, and start fresh, or do you think there's an easier way?

Are these configured with KA-Mod Reborn / Kernel Adiutor?
[Nexus 6  Original Android Development] Elektroschmock:
Are these configured with KA-Mod Reborn / Kernel Adiutor?[/QUOTE]

Readahead is already at 128 K so no need to even lower it.

Increasing logbuffer doesn't help in any way unless you want to debug something. Log is a ringbuffer so increasing it only maximizes the amount of entries it can hold before they get overwritten.
[Nexus 6  Original Android Development] magnamentis:
i use EXKM by flar2 most of the time, works fine while availability of the features depend on ROM and Kernel.

as i pointed out in my last post those workarounds are general, not always recommended and not available for each rom/kernel combo, it are just the ways to make a sluggish device quicker and decryption had a big impact for me while on newer devices the impact in negligible.

for many PIE roms one would have to decrypt anyway while there is no way to avoid going from scratch, at least as far as i'm aware of.once decrypted you'd need a rom or kernel that keeps it hat way, if you flash i.e. this rom and/or stock images you will end up encrypted.

since this does not really belong into this thread and has a lot to do with other kernels and combos i'd say we have to take this to PM should you have further questions.
[Nexus 6  Original Android Development] Bigb12:
Any of you guys having issues with root? I use magisk and I no longer get a prompt and when new apps need root access. The ones that I granted access to have root access though and don't have any issues.

I tried using the lineageos suaddon that is in the OP and that didn't help either. I have never had this issue before. I used root checker to make sure and it says that I don't have root access, but I clearly do.
[Nexus 6  Original Android Development] girkev:
Installed by Twrp?

If so, install the Magic Maher APK.. And the rest follows
[Nexus 6  Original Android Development] Bigb12:
Yes, I installed the magisk 18.1 zip in twrp. I have the lastest magisk manager apk installed as well. Still can't figure out what the issue is.
[Nexus 6  Original Android Development] mezerr:
I have the exact same issue when Magisk 18.1 is installed. Install 18.0 instead and it'll work normal again. I've tried for days to get 18.1 working. Something is borked with it.
[Nexus 6  Original Android Development] Bigb12:
Anyone with input is appreciated. The issue that I am having is whenever I update from a nightly, my phone lags like hell. Takes a solid 5 secs to open apps that used to open in a second. I have tried using the built in updater, and downloading the zip and doing it manually. Any tips that you guys have would be appreciated.
[Nexus 6  Original Android Development] dbrickg:
Bigb12: I thought I remembered seeing something about a 5 second lag, and managed to find the post that I've included below. It looks like rebooting the phone is a solution, at least a temporary one.
[Nexus 6  Original Android Development] Bigb12:
Thanks for finding that post. I tried finding something but I failed. I did try doing that multiple times, and it didn't fix it for me, and I waited it out for a few hours to see if it would work itself out but it never does. I usually get frustrated and restore my backup.

I have tried wiping dalvic/cache in twrp and rebooting and that didn't help either. Idk...I figure I will wait a week or so and try again and maybe it will work itself out. If not I guess I will do a clean install or something.
[Nexus 6  Original Android Development] GammelBS:
I have the same lag after an update from time to time. When it happens I wipe system, dalvik and cache followed by reinstall rom, gapps and magisk. After next bootup lag is gone.
[Nexus 6  Original Android Development] wrsg:
Anyone know if there's anything to be gained from messing around with the Bluetooth default settings in Developer Options in LOS 15.1?

I basically want to get a clearer audio quality when I have a Bluetooth headset connected, if that's possible. Otherwise I will just stick with the defaults.
[Nexus 6  Original Android Development] runekock:
In my experience, most of them are actually read-only. Things like codec seem to be auto-selected no matter what I choose. But it is still useful to be able read them.

If your headset supports AptX, you can flash an add-on for that. LOS doesn't include it for copyright reasons.
[Nexus 6  Original Android Development] Najeeb3344:
Is there lineage os 16 is releasing today?
[Nexus 6  Original Android Development] dahawthorne:
I'm curious - is it your eyes or your memory that are bad...?

https://xdaforums.com/showpost.php?p=78902960&postcount=2272
[Nexus 6  Original Android Development] wrsg:
hahaha, it's understandable given that the Android news sites are starting to pick up on the commit about what devices are moving to 16
[Nexus 6  Original Android Development] Elektroschmock:
I wouldn't trust the device list untill it has been merged.

I might remove shamu, as I encounterd a camera bug on unencrypted devices.
[Nexus 6  Original Android Development] def1003:
regardless of when it comes me so excited thank you for your work elecktroschmock
[Nexus 6  Original Android Development] Feimitsu:
What are the default settings on "Battery Optimization" settings screen for Nexus 6 with LOS? Anybody could post a screenshot from a cleanly installed ROM?
[Nexus 6  Original Android Development] dbrickg:
I don't know what you mean by Battery Optimization settings. If I go to Settings / Battery and click on the 3 dots in the upper right and select Battery optimization, it just gives me a list of which apps are optimized and which are not.
[Nexus 6  Original Android Development] Feimitsu:
Yes, i would like to know what apps are not optimized by default on this ROM
[Nexus 6  Original Android Development] dbrickg:
Ah, well, at least on my phone, all of them are optimized, except a small handful:

Carrier Provisioning Service

Carrier Services

Cell Broadcasts

Download Manager

Google Play services

Shell

All of them say "Battery optimization not available"

---------- Post added at 04:38 PM ---------- Previous post was at 03:55 PM ----------

There's a tantalizingly long list of changes to be included in the next build:

https://download.lineageos.org/shamu/changes/

but the most recent build is from a couple of days ago :(
[Nexus 6  Original Android Development] Elektroschmock:
In preparation for 16.0 we already dropped 14.1 builds and downgraded 15.1 to weekly builds. https://github.com/LineageOS/hudson/commit/b8cf20218fd7676d7904152531e0f1cacead740f

But good news: Once 16.0 comes for shamu I'll maintain 15.1 and 16.0 in parallel for you. (At least for a while)
[Nexus 6  Original Android Development] runekock:
A great day for shamu, but sad for all those devices stuck on nougat. Like watching half the village die of old age at the same time.
[Nexus 6  Original Android Development] Elektroschmock:
We just don't have the resources to do automated builds for 14.1 as the servers and stuff cost money.

But the source code can still be updated for older devices. Some guys are even merging CVE fixes for CM11 into our codebase.

And to be honest running your own builds should be doable by everybody.
[Nexus 6  Original Android Development] pinakini:
Can I automatically update to stable LOS 16 when it is officially released from preview build?

---------- Post added at 07:33 AM ---------- Previous post was at 07:03 AM ----------

does sideloading will also format the internal storage?
[Nexus 6  Original Android Development] Elektroschmock:
No as I stated before you can't automatically upgrade from a preview build as the signing keys differ.

I might do a transistion build which resets all keys but I have never done that so I don't know if it really works.

Sideloading is just a way to flash something. If you're sidloading a user partition your internal data is overwritten.

But as we don't include a user partition your internal data is safe.
[Nexus 6  Original Android Development] Goram:
Hi,

my Nexus crashes when I enter the sim pin if it´s ~50 Power, I have to plug it in to not crash there. Is this a known issue?
[Nexus 6  Original Android Development] Elektroschmock:
No
[Nexus 6  Original Android Development] Goram:
I changed my device and got the same error there, but used a backup from the old device. maybe that was not wise?
[Nexus 6  Original Android Development] dwardo:
Sounds like a dead battery. My old one would do that at 30%.
[Nexus 6  Original Android Development] Goram:
That´s what I thought and changed the device, but got the same error a few mins ago
[Nexus 6  Original Android Development] wrsg:
Do you plan to release any more preview builds before official is out? I notice your last one was from over 2 weeks ago..
[Nexus 6  Original Android Development] dahawthorne:
I don't have the reference to hand, but I remember reading a long time ago that it's unwise to use one device's backup on a different device; at best you'll have problems, at worst it won't work at all. Better to clean-install from scratch.
[Nexus 6  Original Android Development] Elektroschmock:
Ooops yeah I was debugging something and totaly forgot to upload something new. I'll do a build and upload it. Should be up in half an hour or so.

Edit: Uploading now...
[Nexus 6  Original Android Development] magnamentis:
your battery is most probably dying, thus far it's a known behaviour but not rom related
[Nexus 6  Original Android Development] veesix:
Same thing happened to me, at ~40%. You definitely need a new battery.
[Nexus 6  Original Android Development] duhec:
Sooo anyone tried the new LOS 16 preview builds? :o

I know I should try myself but I'm finding myself out of time lately as I usually do clean flashes and everything takes time to configure and I need a working phone every day.
[Nexus 6  Original Android Development] mrk2815:
Elektroschmock

does incription work with your preview builds. will there bea new twrp to support the incription issues with twrp recovery and lineage 16 builds.should we wait for new twrp build to address incritpion issues before flash lineage 16 when its officially available for the nexus 6.
[Nexus 6  Original Android Development] pinakini:
Sorry to bother. I am getting `error' or `failed to sideload xxxx.zip' on the console. And

In recovery sideload failed. I was trying to flash LOS 16 preview by our beloved developer.

Any guidance please?
[Nexus 6  Original Android Development] Elektroschmock:
1. If you mean encryption/decryption - yes it works. Otherwise I wouldn't have posted anything. We're not one of the ROMs which force their users to format everything. ;)

2. TWRP already 'supports' our issue with encryption. I guess you want a version which solves the issue. But I am not maintaining TWRP as I can't cut anymore from my daily 4.5 h sleep.

3. I am not recommending anything, but I guess the wait will be forever then.

Does 'adb devices' show your device?

Did you start sideload in recovery?
[Nexus 6  Original Android Development] pinakini:
Does 'adb devices' show your device?

Did you start sideload in recovery?[/QUOTE]

1. Yes the device is shown in adb devices.

2. Sideload was started in recovery with perennially showing "starting adb Sideload"
[Nexus 6  Original Android Development] dahawthorne:
Just so we're clear on what you're doing, are you following these steps after seeing your device in "adb devices"?

First, are you using TWRP 3.2.3? If not, flash (or boot) 3.2.3.

In TWRP, press Advanced, then ADB Sideload and swipe. You should now have "Starting ADB sideload feature...".

On your laptop, run adb sideload xxx.zip.

Is this what you're doing?
[Nexus 6  Original Android Development] npjohnson:
I'll also personally be regularly verifying 15.1 on my proto-shamu, as IMS (VoLTE/VoWi-Fi/Carrier Video Calling) just won't ever work on 16.0.
[Nexus 6  Original Android Development] L.F.B.:
So, LOS 16 is official!

Weres the oficial link? Its not on LOS download page...
[Nexus 6  Original Android Development] SubwayJrd:
https://lineageos.org/Changelog-22/

Stated that builds will start 1 March 2019. Might be available tomorrow reading that.
[Nexus 6  Original Android Development] raka:
https://builds.lineageos.org/

It's building now! ?
[Nexus 6  Original Android Development] veesix:
Wait, are there more devices than what initially announced, or am I reading it wrong?

edit: Yes, I was wrong, nevermind
[Nexus 6  Original Android Development] pinakini:
Yes, please. All the things mentioned by you are done sequentially. Yet failed. On TWRP 3.2.3.
[Nexus 6  Original Android Development] dahawthorne:
The only things I can think of are encryption or corrupted zip download. Since there's a new 16 build coming today you could try downloading, checking the MD5 integrity, and sideloading it. If it still doesn't work, try a factory reset, format data to remove encryption, and try sideloading again.
[Nexus 6  Original Android Development] Elektroschmock:
The build is already done. :)
[Nexus 6  Original Android Development] roerch:
Hi,

very willing to try the new 16.0 build. Just which su addon to use? On lineage extras website, they still list only the 15.1 su versions. Would that be ok to use them or better wait until 16.0 su is released?

Thanks a lot for all the work.
[Nexus 6  Original Android Development] Elektroschmock:
Wait for the 16.0 release of SU.
[Nexus 6  Original Android Development] Yahoo1:
But Lineage Wiki page says:

5. Now tap Format Data and continue with the formatting process. This will remove encryption as well as delete all files stored on the internal storage.

So format is needed or not?

Thank you very much, [MENTION=3383960]Elektroschmock[/MENTION]. It is great that we have official Lineage for our beloved Shamus :) Keep up the great work :)
[Nexus 6  Original Android Development] Elektroschmock:
This is just for first time installation if you are coming from stock or a different ROM.

If you're updating from 15.1 no wipe is needed.

Please move any further 16.0 talk to the new 16.0 thread I started.
[Nexus 6  Original Android Development] amroj:
Would you care to give a link to the new thread? :confused:
[Nexus 6  Original Android Development] rivernov:
I flashed all and I can't boot. It asks always for my password and I flashed it again without gaaps but no luck.

Edit : nvm I did it bad thinking I had the latest twrp
[Nexus 6  Original Android Development] BootloopedMillennials:
Time for a new thread. And much thanks for the hard work you put in. :good:

Edit- Nevermind new thread is already up.
[Nexus 6  Original Android Development] y300owner:
I have couple of issues and have no idea for a fix

My phone keeps on disconnecting v during a call and screen is always turned during it
[Nexus 6  Original Android Development] nyceyes:
Hello Friends:

A helpful comment and and question.

I upgraded my Nexus-6 from LineageOS 15.1 to 16.1 (via the latest TWRP), and it upgraded flawlessly and is working flawlessly.

:fingers-crossed:

My question:

Ever since I got my Nexus-6 (in 2014), I could never get VoIP Apps to ring only. They always ring and vibrate, even though I disabled vibration everywhere in Android and in the VoIP apps themselves (if they offered the option). This is true from Android v6.x, v7. x, v8. x and now v9.x.

This is currently happening with Google Voice, but was true of other apps, too.

Has anyone experienced this? For me there appears no way to stop vibration with VoIP apps.

Thank you.
[Nexus 6  Original Android Development] Sugarkryptonite:
Does anyone else have the need to hit the screen multiple times on the icon of your choice from the share menu of an app? It's almost like it doesn't respond. Sometimes when I tap perfectly on an icon (WhatsApp for example), the share menu will start to minimize, almost as though it senses that I was flicking it down.

I'm at my wits end about it and it drives me insane.
[Nexus 6  Original Android Development] dwardo:
Yes does it to me too and it does it also, albeit less, in 16.0... one of the behaviors that eventualy lead me to switch phone after 4 years...
[Nexus 6  Original Android Development] Sugarkryptonite:
Thanks! Glad I'm not alone. Trust me I'm really thinking about it...I actually thought about going back to Nougat because of it.