yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Medlir:
If you're on Verizon and having frequent reboots into TWRP, at least in my case, it was due to com.android.phone/Phone Services crashing constantly due to the missing IMS functionality, which was triggering RescueParty ( https://source.android.com/devices/tech/debug/rescue-party ) to kick in, and at level 5, RescueParty reboots the phone into recovery to prompt you to do a factory reset.

From this XDA article on RescueParty ( https://www.xda-developers.com/no-android-oreo-rescue-party-not-bootloop-fix/ ) I ended up doing a quick "setprop persist.sys.disable_rescue 1" and not a single reboot into TWRP since. That said, com.android.phone is still crashing constantly in the background so phone service and mobile data come and go. Sometimes up for several hours, sometimes crashing multiple times in 5 minutes, but the phone itself stays on and Phone Services seem to come back on their own after a bit every time.

On the plus side, it sounds like npjohnson may have a solution for the crashing involving ripping out all the IMS stuff entirely, which may make it fully functional again when/if that gets merged... at least until the end of the year when Verizon shuts off CDMA and VoLTE becomes required. -_-
[Nexus 6  Original Android Development] Sanabil:
Oh ok. Np man.
[Nexus 6  Original Android Development] JaimeZX:
This is me, except I went straight from stock ROM to 14.1. I encrypted using the option in 14.1. Flash to 15.1 after upgrading TWRP was successful. Had to Format Data and sideload 16.0.
[Nexus 6  Original Android Development] torecdude:
The camera shipped working for me after reboot, but it does not appear in the app drawer. I am able to get to it by double pressing the power button
[Nexus 6  Original Android Development] Fred Simm:
I always try to get info from the experienced people dealing with my exact situation. If you don't want to help then don't. I don't appreciate the sarcasm.
[Nexus 6  Original Android Development] dahawthorne:
Not for the first time I agree with dbrickg. Your original query was "Ok, dumb question. How do you side load files? Never done it." which to my mind doesn't qualify as "my exact situation".

Nevertheless, it's so simple that Google would be the perfect answer, but despite your attitude I'll try to help.

From memory, in TWRP 3.2.3, Advanced, Sideload. You'll see a black screen saying "Awaiting sideload" or similar.

On your computer, with the file you want to flash in the same directory as your adb.exe, type "adb sideload file.zip".

That's it.

Edit: I forgot to say that after typing the sideload command you should press <enter>.
[Nexus 6  Original Android Development] Fred Simm:
Ok thanks. I was confused. There's an option in twrp for sideload. You're saying this requires a pc. Can I assume we can't just dirty flash 16 over 15? What I meant by exact situation was the installation of lineage 16.
[Nexus 6  Original Android Development] dahawthorne:
I haven't read the entire thread, since I'm just a lurker keeping an eye on Elektroschmock's excellent work with a view to trying it one day if ever I become unhappy with the ROM I'm using now. May be a while...

You'll have to read the thread - there is a reason for sideloading which I haven't tried to understand, though obviously I shall when/if the time comes. It's to do with encryption and TWRP's inability to read encrypted partitions.

It's not a long thread.

Edit: to answer your specific question, the general wisdom is that you don't dirty flash major updates. You might get lucky, but more likely you'll get random reboots, force closures, etc. Best start with a data wipe & format and a clean install.
[Nexus 6  Original Android Development] Fred Simm:
Thanks again, you fixed a lot of confusion. Now I have to decide if I want to upgrade. I dirty flashed a few days ago and pixel launcher kept crashing. 15 is so smooth right now. I may wait for the rom to get more stable.
[Nexus 6  Original Android Development] dahawthorne:
I don't want to seem argumentative, but did you understand what I wrote? You dirty flashed, got crashes, and you propose waiting until the new ROM is "more stable"? You don't think maybe the dirty flash might be the problem?
[Nexus 6  Original Android Development] mezerr:
Pixel Launcher crashes on a clean flash also FYI.
[Nexus 6  Original Android Development] ermintrude:
The reason that it is necessary to sideload (i.e. transfer files from a connected PC while in recovery mode) is that upgrading doesn't work if your phone was encrypted (which can happen even if you never asked for it, thanks to Google updates.) The only way to decrypt is to *format* /system (not just wipe it) which will wipe *everything* on your phone, including any downloaded files you wanted to flash. Therefore, you will need to sideload those files from your PC to get them back on your phone for the update.
[Nexus 6  Original Android Development] IMAGI0:
the best rom for shamu, thanks! very smooth and great battery life ;)
[Nexus 6  Original Android Development] Sanabil:
Yes by now everyone knows for me its also crashing, i did however flashed it via twrp , it works but have following cons

1 - It lags like hell.

2 - You have to update it again when lineage is updated.

Hopefully it will get fixed at some point.

---------- Post added at 07:54 AM ---------- Previous post was at 07:53 AM ----------

https://xdaforums.com/nexus-6/orig-development/rom-lineageos-16-0-nexus-6-shamu-t3906045/page13

Here you will find the zip.
[Nexus 6  Original Android Development] mahir555:
Can't we use an otg cable to connect a usb stick containing the required files and access it via twrp to flash them?
[Nexus 6  Original Android Development] githyanki:
Yes. It is not the way recommend only because not many people have the OTG cable.

If you have it, it is very easy that way.
[Nexus 6  Original Android Development] dwardo:
Well it turns out shamu is pickier than bacon when it comes to otg cable quality. OTG works on both with a "newer" otg cable.
[Nexus 6  Original Android Development] Najeeb3344:
Substratum Themes

Anyone try substratum on lineage os 16
[Nexus 6  Original Android Development] SteveYoungs:
Yep, works great. Just make sure any theme you want to use fully supports Android Pie.

I don't know if this is a mandatory requirement but it installs a Magisk module if you have Magisk installed.

Have fun.
[Nexus 6  Original Android Development] b8842dc0:
A few questions:

1. Is this problem affecting ALL Verizon users?

2. Is it also impacting people using Verizon MVNOs?

Thanks!
[Nexus 6  Original Android Development] Sanabil:
During my use i can see micro stuttering and sometimes lag in general during UI navigation or app switching even if performance profile is selected.

Could this be linked to a poor battery?
[Nexus 6  Original Android Development] SteveYoungs:
Beware! LOS 20160311 made my /data partition unmountable by either the system or TWRP. (it gave the "password correct, data corrupt" thing, even though I'm unencrypted).

SOLUTION: Copy previous version from pc via usb while in TWRP; flash; boot to system; reboot to TWRP; reflash and boot system; profit.

The 2nd flash is to pick up any addon.d stuff that would have been missed (gapps etc)
[Nexus 6  Original Android Development] githyanki:
Just found this out also when I was going to try another ROM. This is the reason I had avoided LOS for the longest time as they force encrypted. This version was supposed to not do that, but looks like they implemented this "feature" without notification.
[Nexus 6  Original Android Development] pr0ndigy:
WTF are you talking about?

Force encrypt?

Uh.... NO!

I've wiped and installed LOS 15 and 16 several times, and not once has it "forced encrypted" my phone.
[Nexus 6  Original Android Development] SteveYoungs:
No, I think this was caused by a seemingly innocent change to the fstab.shamu file. That change has since been reverted and the commit message said it was because recovery couldn't deal with it. Fingers crossed that tomorrow's build should be fine.
[Nexus 6  Original Android Development] xKillerXSmileZx:
I don't think the random reboot into TWRP issue is just a Verizon thing. It happened to me twice so far and I have only ever used T-Mobile on my Nexus 6. Once on the March 9th nightly (not sure what caused it, it just seemed totally random) and a second time on the March 11th nightly. This second time it happened, I had toggled on Airplane Mode from the lock screen and then toggled it again. I noticed it said I didn't have a SIM card inserted so I toggled Airplane Mode a few more times and then it was shutting down and booted into TWRP. It also seemed to restore my settings in TWRP to default for some reason. Other than this, I haven't had a problem so far. It's been pretty smooth and the battery life is about the same as when I was using LineageOS 15.1 based ROMs.

For some additional info, I had done a completely clean flash (my previous ROM was already unencrypted), flashed the gapps in the OP, and the latest Magisk. My radio is the 05.45R version and latest bootloader version (72.04).

Also, I was definitely able to reproduce this again just now by turning on Airplane Mode again like normal. It again said I didn't have a SIM card inserted, and after toggling Airplane Mode a few times and waiting for a few seconds, it powered off and rebooted into TWRP, again resetting the TWRP settings to default (I usually disable vibration and it also asked me to swipe to allow modifications again). My TWRP version is 3.2.3-0.

Edit: Never mind, the TWRP settings seem to change to default every time regardless of if it occurred because of the reboot into TWRP problem, or if I'm simply booting into TWRP on demand. I tried attaching the logcat.txt and radio.txt but they both exceeded the file size limit so I put them on here if you don't mind: logcat.txt ; radio.txt
[Nexus 6  Original Android Development] pinakini:
Google Pay India. Could not link/restore my bank account. It returns error `Could not send SMS. Insert the same sim etc.'.. But the messaging works in other apps perfectly. Could this have caused by decryption? On 15.1 G-Pay worked flawlessly. Shall I encrypt again? If encrypted, will I encounter problems in installing future updates of LOS 16.0?
[Nexus 6  Original Android Development] Elektroschmock:
Yeah it is not only Verizon it's everything that uses the IMS.apk.

We're trying to remove all IMS related stuff with:

https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/239600

but it's not yet tested.

You might just delete your ims.apk and see if that fixes your crashes/reboots.
[Nexus 6  Original Android Development] duhec:
Anyone knows why the build hasn't begun yet? :confused:

I'm stuck with the broken 11/3 build and waiting. Usually at this time the build is already done. See attachment.
[Nexus 6  Original Android Development] xKillerXSmileZx:
Thank you for this suggestion. I used Titanium Backup so I could attempt to backup and safely uninstall it. For me the package name is org.codeaurora.ims. I tried uninstalling it and rebooting but it kept persisting on reboot each time (would not actually be uninstalled) so this time I just "froze" it which disables it since I have TB Pro, and this has worked. It does not reboot into recovery anymore after toggling Airplane Mode on & off and does not say the SIM isn't found (when that happened it would reboot into recovery after about 40 seconds). Seems all good for now!
[Nexus 6  Original Android Development] duhec:
Never mind. I found it here.
[Nexus 6  Original Android Development] BootloopedMillennials:
The 3/11 build did some weird stuff. It installed and booted fine. But now that I downloaded the 3/12 build and boot into TWRP to install it I cant access my data partition. I can reboot into the OS, the 3/11 build, and it shows the phone is NOT encrypted. So there is no reason TWRP shouldnt be able to read the data partition. Pretty sure if I sideload the 3/12 build now, Ill get the data partition corrupted error everyone else faced. Weird, my N6 hasnt been encrypted in a long, long time.
[Nexus 6  Original Android Development] Elektroschmock:
It's the quota support I merged and reverted later. Our TWRP doesn't support it and needs an update. I didn't notice it, as I have an encrypted data partition which TWRP can't mount.

Sorry about that.
[Nexus 6  Original Android Development] usuppue:
how i can format system with twrp?
[Nexus 6  Original Android Development] mezerr:
So.. is everyone just using the Trebuchet launcher with LOS16?
[Nexus 6  Original Android Development] Najeeb3344:
[MENTION=3383960]Elektroschmock[/MENTION]

I faced an issue ,I plugged in my headphones then using TikTok app then screen goes black!

It was hard shutdown the battery was 60% when after my mobile boot battery remains same.

Whats the problem it is?
[Nexus 6  Original Android Development] Sanabil:
Yes i am using it, i face lags some times swiping to side and sometimes opening or switching apps it stutters. Also google feed on left lags alot.

Does it happen to you too?
[Nexus 6  Original Android Development] BootloopedMillennials:
I was able to sideload the 3/12 update and it booted up fine. Am I going to have to do a clean install to fix it when the reversion is merged?
[Nexus 6  Original Android Development] mezerr:
I didn't use Trebuchet for long.. I reverted to 15.1 after 5-10 minutes cause of a couple issues, one of them being lag. 15.1 is so butter right now.
[Nexus 6  Original Android Development] Sanabil:
I might also consider going back to 15.1
[Nexus 6  Original Android Development] githyanki:
Same issue here. 3/12 build works for me, but still cannot access data partition from TWRP. Don't know if there is a fix for that or will have to format data to have access again.

Thanks for all of your hard work electroschmock, this is the price we pay for living on the bleeding edge. :laugh:

Update: a second reboot when I noticed I didn't have magisk installed and TWRP can now read data. So either wait longer after installing 3/12 build, or reboot a few times. :good:
[Nexus 6  Original Android Development] TheLach03:
Could you please advise how you got back to 15.1? I created a backup in TWRP (boot/system/data) before upgrading to LOS 16 can't find any clear instructions on how to go back. Cheers!

EDIT: Should have mentioned I'm aware of the docs on the lineage page where it advises the method is as if installing for the first time. I'm looking to revert my phone using the TWRP backup if possible!
[Nexus 6  Original Android Development] SteveYoungs:
20190312 installed and runs smooth as silk.
[Nexus 6  Original Android Development] duhec:
Confirm. :good:

The only thing that still isn't working is when someone is calling me (the phone is ringing) or I'm in the middle of a call, the BT headset does not connect to the phone. Only when I finish the call I have to turn off the headset, then turn it back on and then it connects. Alternatively I can disable BT, then reenable it and then it connects but it's not really a solution.
[Nexus 6  Original Android Development] Sanabil:
Installing latest nightly removed my root and restored the OS to default settings with all stock apps reappearing. Should i again manually install magisk?
[Nexus 6  Original Android Development] def1003:
thank you for your work everything is running smoothly thanks!
[Nexus 6  Original Android Development] dahawthorne:
Overwriting System removes root. Magisk runs an addon.d script which automatically reinstalls Magisk root, so if that hasn't happened then yes, you'll have to manually install it.
[Nexus 6  Original Android Development] Sanabil:
I asked because previously i just updated and my root never reverted. I just had to root once i.e installing fresh OS via twrp.
[Nexus 6  Original Android Development] SteveYoungs:
It sounds to me like you did a clean install instead of dirty (you manually wiped system etc before you flashed the update). addon.d scripts won't survive a clean install and it's those scripts that take care of reinstalling Magisk and gapps. So that could account for missing Magisk and stock apps (gapps replaces a lot of stock apps).
[Nexus 6  Original Android Development] Muggins:
Not true. As has been mentioned above, TWRP was unable to read data partition, so Magisk script couldn't run.

I had to use OTG ability of TWRP to reinstall Magisk.zip manually. In any event several reboots later all seems to be fine.
[Nexus 6  Original Android Development] Sanabil:
Nopes, i used automatic Lineage updater it takes the process to twrp and does it's stuff and then reboot with my apps settings and root enabled.
[Nexus 6  Original Android Development] mezerr:
Just boot into TWRP and select restore. Select your recent backup, and restore it. .. easy peasy.
[Nexus 6  Original Android Development] pinakini:
CAMERA : my observation.

Camera used to survive updates. Since 12/3/2019 update it requires an additional reboot.
[Nexus 6  Original Android Development] TAGTRAUM:
I've experienced a magisk disappearance too, but after installing ROM, rebooted to TWRP it was unable to mount any partitions, yet another reboot normalized everything, all partitions mounted, magisk installed, settings survived
[Nexus 6  Original Android Development] Elektroschmock:
The JIT complier can't optimize everything in 5 Minutes thats why its a bit laggy at first. Additionally cpus are usally thermally limited after the first install because it is running at high freqs for a long time during install.
[Nexus 6  Original Android Development] Sanabil:
Oh so this was the reason, no wonder now it doesn't lag as intially. Thanks for an educated answer. :good:
[Nexus 6  Original Android Development] Elektroschmock:
Let me get my crystal ball and I'll fix all your problems.

Get me a log of the crash and I can have a look at it.
[Nexus 6  Original Android Development] teamoushy:
Thank you [MENTION=3383960]Elektroschmock[/MENTION] for the wonderful work
[Nexus 6  Original Android Development] Sanabil:
Crystal ball ?
[Nexus 6  Original Android Development] papajonpizza:
I love Lineage, and so happy I'm able to run the latest and greatest version of Android, but yea, I got hit with that 3/11/2019 sudden-encryption-TWRP-can't-decrypt OS bug update

I tried to sideload 3/09 through OTG cable, but couldn't get a stable connection, it's mainly the on the Nexus 6 USB port side that hasn't been that reliable. Anyway, mounted the system partition and ADB transferred 3/09 to it and tried to install it, failed with some errors, so now, no choice but to format data.

All is not lost, I do have a TWRP backup that's 2 weeks old, Lineage 15, and dirty-flashed Lineage 16 3/13 and Mindgapps and Magisk 18, so not so bad. I'm back in business, but cost me about 3 hours as I had to reset my Galaxy Watch Active to get it re-connected. Good thing I did a backup of that before I started all of these.

Lessons learned. A 5-minute TWRP backup ADB pulled to laptop will save you 3 hours (or more) of "fun" stuff. I got a backup today again and ready for 3/14 Lineage 16 nightly update :)
[Nexus 6  Original Android Development] TAGTRAUM:
I'm usually use crystal skull (vodka, google it) and then all the problems passed by ?
[Nexus 6  Original Android Development] x-raf:
Hi i'm on LineageOS 16 + OpenGapps + Magisk 18.1. Clean install, I've some problems with Google Pay.

SafetyNet check: all green, I can hide Google Pay but I can't add my cards. It's saying that my phone is rooted or modified.

Any advice?
[Nexus 6  Original Android Development] pinakini:
Updated to 14/3/2019. Both the cameras not working despite reboots, cache/data clearance & reinstallation.

I do not know if it only occurred to me.

Reverted to 10/3/2019- cameras are back again.

these are not complaints, but the experiences posted with an intention to appraise the rom development.
[Nexus 6  Original Android Development] runekock:
Not related to the rom.

There is a separate thread about getting Google pay to work with Magisk:

https://xdaforums.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703/
[Nexus 6  Original Android Development] mezerr:
Anyone else have issues with Google Assistant working? OK Google doesnt trigger the assistant, and can't see to train voice. Just curious if it's something bunked with my install or if it's just not configured yet in this rom. Thx
[Nexus 6  Original Android Development] SteveYoungs:
Working fine for me using either "OK Google" or "Hey Google".
[Nexus 6  Original Android Development] nilesh0205:
Anyone having issues with hotspot? It automatically turns off after 30 minutes or so. Not sure if any settings there which does this. How to resolve this?

Also I also having issues with Google assistant with okay google or hey Google.

Thanks
[Nexus 6  Original Android Development] Sanabil:
Can someone confirm this issue? or am i the only one. This issue was also present in 15.1 .

Sometimes the aimbient clock does not work as i pick up the phone and with this if i receive call the screen never recovers from being black unless i press power button to revive it.

It gets fix when i reboot.

Can someone confirm?

Thanks
[Nexus 6  Original Android Development] SteveYoungs:
Yes, there is a setting for turning off hotspot automatically (see screenshot). It's on by default.

Google Assistant is working perfectly for me.
[Nexus 6  Original Android Development] kevinga:
Set Google Dialer app as your default phone app. If you go to settings, then type the word default apps in the search bar then select default apps. I also had the same problem with Google assistant. For some reason there was not a default app setup for assistant. All works now.
[Nexus 6  Original Android Development] mezerr:
Yes I got mine working now. For whatever reason, it wouldn't train with OK Google or Hey Google. Tried it again in a quieter place and all good.

Do you have the old assistant or new one? (When you say OK Google, does the assistant show at the TOP or BOTTOM?).

Edit: Got the new Google Assistant now. Changed my language to English (United States), and added below to BUILD.PROP:

ro.product.model=Pixel XL

ro.opa.eligible_device=true
[Nexus 6  Original Android Development] SteveYoungs:
Wow, the only thing that I did was to set the default assist app in settings. But systematically going through all the settings is the first thing I do with a brand new ROM so this happened long before I used GA for the first time. I didn't need to train the voice because it was still set from LOS 15.1 which was still set from 14.1. I certainly didn't change my default language (English, Australian), nor did I alter build.prop in any way. Those tweaks haven't been necessary for some years now.

GA should work "out of the box" for most users.
[Nexus 6  Original Android Development] mezerr:
Ya, it was working out of the box.. it was just the older version. In order to get the newer version, I had to make the three changes, and then got a notification saying "New Assistant Available". No idea.. This was on a clean flash.
[Nexus 6  Original Android Development] SteveYoungs:
With the exception of the very first time I triggered GA in LOS 16 I've got the current version.

Moving from 15.1 to 16 I did a partial clean flash (didn't wipe data¹) but dirty all the way ever since. :)

[1] I did end up backing up, formatting, and restoring data though because of the encryption issues.
[Nexus 6  Original Android Development] nilesh0205:
Thank you, it worked, now banging my head on wall, why I didnt clicked on the advanced link :p
[Nexus 6  Original Android Development] amaruk27:
This worked for me too, and saved me from having to revert to 15.1. Thank you!!! I didn't even have to toggle airplane mode, as soon as I froze IMS my cell service came back immediately.
[Nexus 6  Original Android Development] mezerr:
I will say... my install is butter right now. Clean flash of LOS 16, March 15. Magisk Canary (google pay issues), Gapps Mini, Nova Launcher.

BUTTER
[Nexus 6  Original Android Development] wrsg:
If we want to encrypt the phone on 16.0 and also have root enabled, are we stuck until we get a new TWRP?

Because the current 3.2.3 twrp won't decrypt.