yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] dwardo:
Thank you for the tip an nudge in the right direction !!!

Here is what worked for me :)

1. In 17.1 turned off pin code locking in settings

2. Rebooted to twrp

3. Deleted /data/system/locksettings.db file

I didn't have any of the "*.key" files and no other locksettings.* files (probably because I had deactived pin in settings before hand)

4. flashed 18.1 zip [+gapps + magisk]

5. Rebooted

6. Started enjoying 18.1 on my shamu
[Nexus 6  Original Android Development] Strephon Alkhalikoi:
Did anyone report issues attempting to use Google Camera during testing? This didn't happen on 17.1, but I'm having an issue where the app appears to not connect with the hardware, with the end result being the settings are unavailable and the viewfinder doesn't display anything. It's not a huge issue for me, as this no longer is my primary device and the LineageOS camera does work. But it would be nice. :)

I'll get you guys a logcat later if needed, but the brief look I had at it revealed an informational comment in the log regarding not being able to find a symbol in a .so file.

EDIT: Additional information. If I use the "Take a selfie" or "Take a video" long-press menus both functions work. As soon as I switch to the back camera to take a still photo the app crashes.
[Nexus 6  Original Android Development] ExpertMC:
Yes I also experience this, seems like it should be an easy fix because it works in other apps. Using shortcuts also works for selfie and video but not back camera like you said.
[Nexus 6  Original Android Development] ProBird79:
That's awesome to hear!!

wavedashdoc said it was working in a post of theirs a good while back but it was never implemented. I assume there were some bugs to work out still?
[Nexus 6  Original Android Development] maddog3030:
same here
[Nexus 6  Original Android Development] dvdram:
My knowledge about LOS internal is very limited, but I assume that this key file you're talking about contains the pin for the SIM and the lock screen, and that this file has to be kept safe when doing an OTA upgrade or a "dirty flash" without wiping the system partition first. And now big G have limited the access to that file. Am I right so far?

If that is right, disabling screen lock and SIM lock sounds promising as a workaround.

What about the data partition? As far as I know, and I might be very wrong about this, the data partition is the place where apps and user data are saved and installed. (Correct me, if this is false!)

Will wiping the system partition and leaving the data partition intact be sufficient enough to do a clean installation? Alternatively: can the data partition be restored from a backup using TWRP after the installation to get the user's data back to the same state they where before? (If I understood it correctly, that is what dwardo did in #16.)

Or are there too many changed between A10 and A11, so that there's no way of using the data partition from A10 in A11 any longer?
[Nexus 6  Original Android Development] dwardo:
So I have been playing around with 18.1since my dirty flash update from 17.1 and have encountered 3 issues :

1. Reboot (to system or recovery) shows the "rebooting" animation but doesn't reboot. I end up hard rebooting (simultaneously press pwr+volup+voldown for a few seconds) after a few minutes or waiting for reboot to happen

2. Shutdown does the same thing

3. Navigating through Settings leeds to freezes
[Nexus 6  Original Android Development] esysfound:
For what it's worth (thanks to Elektroschmock for clarifying) a dirty flash is when a very different ROM is flashed over another without any wiping. Apparently, different generation LineageOS builds are just "updates". But the discussion above has reeninforced my thoughts that:

1. The upgrade process would be helped by a more detailed explanation from the devs. Exactly what is the recommended process? I realize explaining stuff is a pain for some people, but we mortals need clearer guidance. What exactly needs to be wiped first (if anything)? What combination of any or all: SYSTEM, DATA, CACHE, DALVIK, nothing or just reset the SIM card locking, etc ?

It seems (so I thought) that just

removing the SIM lock from 17.1 Settings, Security,

deleting the related .db file til this gets sorted, then

flashing from recovery both LOS 18.1 and MindtheGapps

then a cache/Dalvik wipe, and reboot

may be all that is needed? No wiping of SYSTEM or DATA. That would save me a ton of time if most of desktop launcher prefs and app data could be left untouched. But sorry it is just not clear yet. Having this simply, clearly explained would save everyone a lot of time both on the flashing and explaining ends.

Here, the devs have said DATA needs to be wiped

Upgrade LineageOS on shamu | LineageOS Wiki

wiki.lineageos.org

So it is a bit all over the place....Some people have done it, some have not.

2. It would also help us if people who are taking the plunge explain in more detail how they flashed the new ROM (borrowing from comment above). Some have helpfully done this.

At the moment, this is all a bit more medieval than it needs to be. None of this is to take away from the devs great efforts to get an 18.1 build out. 😇
[Nexus 6  Original Android Development] Uplander:
Backup los 17 and flashed 18 & magisk, with orange fox, no gapp's.(No encryption or security phone lock used.)

No wipe (just usual art cache after install),

DMConfig and google camera issue as mentioned in previous posts.

Running smoother than I ever remember, absolutely recommend this excellent rom, many, many thanks.
[Nexus 6  Original Android Development] npjohnson:
Nah, just need time to iron it all out and include it correctly/test on 11 (he did it on 10).
[Nexus 6  Original Android Development] hbenz2008:
My samsung broke so I am using my old N6, i did change the battery about a year ago or such.

Flashed LOS 18.1, mindgapps and even restored data backup from another 11ROM that i have flashed couple months ago as test.

Anyway, so far so very good running this ROM.

All that I use works beautifully such as:

Bluetooth connection to my car, phone calls are good, broadcasting music from phone to car works.

Sygic gps works

Connection to Garming watch works and syncing

I had a VERY good Signal call over 4G , no echo no bs (didnt try whatsapp call yet) but audio notes works

Aquamail with multiple accounts works

Normal browsing and such works

I believe Android 11 manages apps better, battery is better than 10

I will report if anything . Big thanks to the Devs

I just wiped with twrp, flashed 18.1 and mindgapps.

rebooted

restored data

flashed Magisk 22

done
[Nexus 6  Original Android Development] esysfound:
You "wiped" what, exactly?
[Nexus 6  Original Android Development] hbenz2008:
what we have been wiping since long ago to flash new ROM, that is system, data NOT INCLUDING Internal storage. In another term the regular TWRP wipe
[Nexus 6  Original Android Development] Devidas_jadhav:
Great work.

ROM working fine.

I found following issue

digital wellbeing not available.

Which was available in 17.1.

Unable to install from play store. Not compatible device.

I have been using this app extensively.

Would appreciate any pointers solving this.

I suspected we have used mindthegapps instead of opengapps.
[Nexus 6  Original Android Development] hbenz2008:
+Hotspot working as intended
[Nexus 6  Original Android Development] spiral777:
Can't seem to get Viper4android working on LineageOS18/android 11...otherwise working great :)... Until the V4A fix I'm perfectly happy waiting it out on LOS 17.1
[Nexus 6  Original Android Development] esysfound:
New 7 Apr build out - has anyone who has flashed it found that this solves the reported camera problems? Not clear from the "recent changes" page.

Thx again to the devs...
[Nexus 6  Original Android Development] Elektroschmock:
No it hasn't been fixed.

Google Camera isn't available in Playstore for Shamu. I don't know which version was tested, where the apk came from and which gapps package was used.
[Nexus 6  Original Android Development] esysfound:
Google Camera actually does come up in my Playstore v 4.2.035....last updated 7 Dec 2016 (which is what I have installed and it runs fine on 17.1)

Could it be that some other version is included in MindtheGapps which might be involved in the problem?

or

Did anyone try to reinstall Google Camera (maybe there is an incompatibility with the above version and Android 11)?

There are of course other camera apps - not such a train smash, just still prefer GC.
[Nexus 6  Original Android Development] pinakini:
The google camera app we used upto a10 and still downloadble is Version 4.2.035.141213305 with hdr+
[Nexus 6  Original Android Development] Uplander:
April 7th update installed.

Version 4.2.035.141213305 google camera & DMConfig Updater issue as previously described.

Open camera & system camera work well.

No other issues detected so far,

Many thanks.
[Nexus 6  Original Android Development] Markeee:
Seems Paypal app will not install for me on my Nexus 6 with LineageOS 18.1 and Paypal Pay Here just app keeps looping when I try to login o login?

Anyone else using these apps having issues or solutions ?
[Nexus 6  Original Android Development] dvdram:
What about all the functionalities that OpenGaps Pico does not include? Are they included in MTG?

I always and intentionally use Pico, because PlayStore is the only GAPP I want on my phone. Can MTG be stripped down to this as well?

Another question: a recent version of TWRP for the N6 is not available on their site. The LOS recovery doesn't offer the options to wipe any specific partition, and I can't find instructions in the installation guide. How can the data partition be wiped instead?
[Nexus 6  Original Android Development] esysfound:
TWRP easily found by a search on the interweb-just choose your preferred mirror

Motorola Nexus 6

Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...

twrp.me

most recent is e.g. https://eu.dl.twrp.me/shamu/twrp-3.5.1_9-0-shamu.img.html
[Nexus 6  Original Android Development] Uplander:
Or try Orange Fox for shamu beta R11 if your having trouble with TWRP.

Just duckduck it.
[Nexus 6  Original Android Development] Markeee:
Deleted
[Nexus 6  Original Android Development] dvdram:
I remember when LOS 17 / A10 was released, TWRP was said to be incompatible with LOS 17 and above. Therefore I was assuming that the "_9" in the file name referred to LOS 9 somehow. Seems I was wrong. ;)

What about the differences between MindTheGapps and OpenGapps Pico, and the functionalities that those two GAPPS packages provide? I am trying to find information on the net, but to no avail so far. Can anyone tell something about this?
[Nexus 6  Original Android Development] Markeee:
MindTheGapps vs. OpenGapps​

What's the difference between those gapps packages? What's better suits to los 15.1?

https://www.reddit.com/r/LineageOS/comments/8358p0
[Nexus 6  Original Android Development] Markeee:
Clean installed 18.1 updated to 0407-nightly running super smooth and solid only issues I'm having is still getting the msg DM Config Update Keeps Stopping on reboots and Paypal mobile and Paypal Pay-Here apps don't work ?
[Nexus 6  Original Android Development] hasitCN:
Plug in the SIM card, can solve this problem
[Nexus 6  Original Android Development] Markeee:
What do you mean plug in the sim card? My sim card is in I never took it out ?

Also just noticed there's a new TWRP just out

twrp-3.5.2_9-0

https://dl.twrp.me/shamu/
[Nexus 6  Original Android Development] esysfound:
1. TWRP There was discussion in the 17.1 thread last year about if you need to recover a TWRP backup, you should do that and then flash again the ROM using the same build version. Has to do with partitions. I have not done this yet (one of the reasons I am waiting a bit to upgrade to 18.1). People who did it said it works fine. If you search the 17.1 thread for "TWRP" you can surely find this. It is possible the newest TWRPs get around this, but I am not willing to test as my phone is the daily driver. If you have a very simple installation, you can try and report back.

2. MtG vs OGs MtGs is designed to be a very minimal way to essentially get Google Play store up and running. If you go to the OpenGapps website, you can see some description of each of their options in each of the variants (hover over each). What I like about OGs is that I know it and it works (always a plus) and their file sizes seem smaller for same mix of apps (e.g. I think their Pico like 50MB smaller than MtG). Storage space an issue on my phone. Another reason I may wait just a bit to see if the full Android 11 OGs options lineup appears for the Nexus 6 chipset.
[Nexus 6  Original Android Development] Elektroschmock:
This procedure was just a workaround which isn't needed anymore.

We have 'fixed' it with this commit:

shamu: sepolicy: Fix bootloop on TWRP restore · LineageOS/android_device_moto_shamu@355c9e9

When TWRP restores a ROM backup, the root directory now has the wrong selinux context "system_file" instead of "rootfs" as it should be for Q system-as-root. Attempting to boot...

github.com

The real fix should be done on TWRPs side, but I have no information if they have done that.
[Nexus 6  Original Android Development] esysfound:
Thanks for this - great to know.
[Nexus 6  Original Android Development] dvdram:
Thank you for that explanation!

So, could MtG be said to be somewhere between OG Pico and OG Nano? It will get the PlayStore running, maybe things like TTS, but none of the higher GAPPs that are included in OG Mini and above?

About TWRP: if understand all the statements about it here correct, then this recovery is needed to wipe the system partition and to backup the data partition and restore it afterwards. But what adb? Can these steps be done using adb as well?
[Nexus 6  Original Android Development] esysfound:
Moot point re MtG because at the moment if you look on OpenGaps site, there are no Android 11 options, only A10.

On rest - of course you can do lots with ADB. Suggest you read through TWRP and ADB threads to decide what is best for you. TWRP just super simple to use.

It is still a question with this build if it is really necessary to wipe the System to upgrade. If you read through the thread, people seem to be installing with no wiping, with only System wiping, and with System and Data wiping, and who knows maybe butt wiping like I do.

I wish devs would clearly state what is and is not needed for the upgrading from 17.1 to 18.1, once and for all, as I posted above.
[Nexus 6  Original Android Development] dvdram:
Phew! I just had some very exciting moments doing the upgrade. I decided to take the conventional method using TWRP. This is how I did it:

- deactivated screen lock (but forgot to deactivate SIM pin...)

- installed TWRP using fastboot

- booted into TWRP and made a full backup onto a USB memory

- made sure that backup could be restored

- wiped system partition and cache

- installed the image and MtG, that I had copied on the same USB before

- wiped cache again

- rebooted system

System started, but when SIM pin was requested, system rebooted instantly. Bummer!

- rebooted into TWRP

- deleted the lock db

- removed SIM

- rebooted system

System came up and was running and all apps where still installed. Great! After a few moments I inserted the SIM and was asked for the pin. The SIM was unlocked and network was working! Hurray! :)

After playing with the phone for about half an hour now there's only one think I'm missing: there used to be an option to kill an app by holding down the back button for some seconds. I can't find that option any more. Has it been removed?

On the other hand, there are two apps now, that I would rather not have on my phone: Google and voice search. I assume they are part of the MtG package. I can not uninstall them. Will I be able to get rid of them by reinstalling the LOS image plus OpenGaps Pico, once those package is available? Or will installing OpenGaps break any dependencies?

One error message keeps reappearing saying "DM config update failed". Should I be worried about this? What to do about this message?
[Nexus 6  Original Android Development] runekock:
About wiping system:

Installing a rom always wipes system, however most roms have a survival mechanism (addon.d) that other things flashed can opt into. That's how gapps survives an ordinary update.

If you perform a big upgrade like this one, then it is a good idea to wipe system before to break the survival, as your gapps, magisk or whatever may not be directly compatible, and so are better reflashed manually afterwards.
[Nexus 6  Original Android Development] maddog3030:
OpenGApps - Browse /arm/test/20210130 at SourceForge.net

OpenGApps daily releases

sourceforge.net

They're still testing but there are g apps for Android 11 from open gapps
[Nexus 6  Original Android Development] esysfound:
Right but last revisions posted end January. Odd it is taking so long. Have you/anyone tried the Pico?
[Nexus 6  Original Android Development] maddog3030:
I have and running on it as well as stock with exclusions due to size....Odd? Mabey.
[Nexus 6  Original Android Development] Markeee:
And Gmail app is not working also
[Nexus 6  Original Android Development] dvdram:
Actually, on my phone that error message about "DM Config Update" only appears whenever I open one of the GAPPS that are included in the MtG package: Google and VoiceSearch. Both apps are not among those apps I do want to have on my phone, so not using them is no loss to me, and as soon as a stable version of OpenGapps Pico is officially out, I will flash my phone again to get rid of these apps.
[Nexus 6  Original Android Development] esysfound:
Took the plunge today and installed the latest 18.01 7.04 build with NO SYSTEM WIPING. Just removed all security on SIM and Screen, used TWRP to flash the ROM, then reinstalled latest TWRP and the OpenGapps PICO test build, and Magisk, then cleared Cache/Dalvik. Figured I could always do more surgery if needed. Worked/working fine. A little sluggish but after a couple of reboots, now very smooth. Getting the DM config problem, and Google Camera not working even after fresh install - both expected. But the smaller test OGapps Pico build seems to work fine. Installation of all like a 7 minute project, 99% of settings preserved (so far).

What has not worked is Maps.Me off line navigator which is annoying as I like their OpenStreet maps and find most other apps too clunky. Maps are downloaded (fresh) but app not reading them. Read somewhere some navigation apps need Location always on vs. only when app used. Have yet to figure out how to do this.

All in all, far simpler and less work than feared. Bravo devs.
[Nexus 6  Original Android Development] maddog3030:
Pico lacks a lot of let's call them common libraries that are needed for the Google apps that's why I use stock and because of the size you have to selectively "include" what libraries and core you want in the install through that config script , in the case of the camera the stock will not replace whatever existing camera are there unless you use the tagline "forceclean"

Remember to comment out or uncomment what you do or don't want using "#" at the beginning of each line.
[Nexus 6  Original Android Development] Markeee:
Formatted clean installed again 0407 - nightly MindTheGapps and latest Magisk no issues now except for DM Config Update Keeps Stopping on reboot
[Nexus 6  Original Android Development] dvdram:
Today I discovered that the MtG package even includes "Android Auto", so I gave it a try. My car's media system is equipped with several USB ports and it's capable of BT and even wifi, and there's an "Android Auto" button in its menu. But my experiments were not successful, no matter if I tried wired connection or wireless. The only thing working is BT phone calls and music streaming. But mirroring the phone's screen is not possible. So I guess the Nexus 6 is too old for this technique. Or has anyone managed to get their Nexus 6 to work with Android Auto?
[Nexus 6  Original Android Development] maddog3030:
In the developers option Bluetooth section select the 1.4 version of the map drivers and while you're there change the avrcp to 1.6 that might do the trick
[Nexus 6  Original Android Development] dvdram:
Thanks, maddog3030, but that did not change anything. I guess my car's media system and my N6 are not compatible enough for making use of Android Auto.

(According to the car's manufacture, it is said to be compatible, at least using a USB cable. I tried 4 different cables now, none of which did work. So I will have to keep operating podcast and music player on my phone's screen.)
[Nexus 6  Original Android Development] maddog3030:
Anybody else having problems with smb1 servers ?
[Nexus 6  Original Android Development] runekock:
Do you really mean SMB version 1, as in Windows XP-compatible? I hope that support for that old version has been dropped, so that a hacker cannot downgrade a connection and exploit old flaws.

Stop using SMB1

First published on TECHNET on Sep 16, 2016 Hi folks, Ned here again and today’s topic is short and sweet: Stop using SMB1.

techcommunity.microsoft.com
[Nexus 6  Original Android Development] maddog3030:
Yeah I know but lineage 17.1 and x-plore app worked fine but now on lineage 18.1 I get connection refused.....footnote the app andSMB works good so it looks like it's the x-plore app with the problem!!?
[Nexus 6  Original Android Development] dvdram:
Just in case anyone is interested: I got Android Auto working. There are two things one needs to know:

1. Android Auto needs Google Maps installed as well, which is not included in the MindTheGapps package. That's why it didn't work before. You can not use AA without GM installed, and you can not use any other routing app that is installed on your phone with AA other than GM. You even can not exclude GM from being shown by the launcher. There is no way of avoiding GM if you want to use AA. :(

2. When AA is active, playing music is only possible when you grant AA the right to access the microphone. This is a bit strange, because most commonly music is not played via a phone's microphone. At least not on any phone I know...
[Nexus 6  Original Android Development] ProBird79:
Thanks for the info.

1. So you can't have Waze as a stand alone app? I know it works with AA.

2. They probably require the microphone permissions for hands free using Google Assistant.
[Nexus 6  Original Android Development] dvdram:
It's no wonder that Waze is working with AA, because Waze belongs to Google.

Or they simply don't know how to use a speaker without opening a microphone as well... ;)
[Nexus 6  Original Android Development] ProBird79:
I understand but you said you have to have Google Maps for AA to work. Does it not work with Waze alone or are you saying you don't want any map service installed?

How else is it to recognize your speech without a microphone? How else is it suppose to work hands free? You have to have a microphone...
[Nexus 6  Original Android Development] dwardo:
Solved the first 2 with a cache wipe in twrp

3rd is more sluggishness than freezing now.
[Nexus 6  Original Android Development] Markeee:
LineageOS 18.1 Review: Android 11, coming to an old phone near you​

LineageOS 18.1 Review: Android 11, coming to an old phone near you

Instead of ditching your old phone, keep it running with LineageOS 18.1, a custom ROM based on Android 11. Here's a review of what it's like.

www.xda-developers.com
[Nexus 6  Original Android Development] esysfound:
Good find, thanks. I have had almost no problems using TWRP and find it is both a lot more powerful than the LOS recovery, but also, should one ever want to jump to another ROM, surely having TWRP would make that easier. Plus the reviewers experience with a few reboots needed with MgG etc. also suggest some caution. (Have had no problems with the OpenGapps Pico beta, apart from the Google camera and Maps.Me not working.) The review article is a useful features overview.