yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] runekock:
As to the reviewers problems with gapps, there is a likely explanation in a comment from @duckyduck!

"After flashing lineage rom recovery changes slot to another slot like if a then to b or b to a.

U need to reboot to recovery again after flashing rom and then flash gapps."

If that is the case, then it doesn't matter on Shamu, which doesn't have A/B partitions.
[Nexus 6  Original Android Development] pdm2007:
Nexus 6/shamu LineageOS 18.1 20210414 PlayMarket is uncertified

Google Nexus 6 (shamu) LineageOS 18.1: lineage-18.1-20210414-nightly-shamu-signed Build date: Wed Apr 14 04:38:09 UTC 2021

I installed the latest lineage-18.1-20210414-nightly-shamu-signed and lineage-18.1-20210414-recovery-shamu using these instructions:

Upgrade LineageOS on shamu | LineageOS Wiki

wiki.lineageos.org

I tried to use different bootloaders - but it didn`t help:

| lineage-18.1-20210407-recovery-shamu |

| lineage-18.1-20210401-recovery-shamu |

| lineage-17.1-20210331-recovery-shamu |

Current play market`s version is 24.9.17-21 [0] [PR] 367727371

While updating through recovery - I used MindTheGapps-11.0.0-arm-20210412_124103

I read the article from Lineage os: https://lineageos.org/Google-Play-Certification/

But the solution after registration of the device's GSF ID - didn't work :(

Has someone experienced that? And maybe there is a fix?
[Nexus 6  Original Android Development] alfacrux:
Overall 18.1 is working great (no gapps here). The only thing was, that sometimes after the reboot the camera app was missing. Usually then a reboot (or shutdown/start) brought it back.

However - after update to lineage-18.1-20210421-nightly the camera app is just missing and no reboot or shutdown/start brings it back... Anybody else with this problem?

Edit: Inserted SIM (was testing PinePhone) and the camera app was back. Could the presence of SIM be related to camera initialization process?
[Nexus 6  Original Android Development] Elektroschmock:
No, there is a small chance to hit a race condition where some dependant services don't come up with the right timing.

I tried to mitigate the chance to hit that race condition with these commits:

shamu: Don't go breaking my HAL · LineageOS/android_device_moto_shamu@a2d14bb

Ooh-hoo, nobody knows it When it was down I was your clown Ooh-hoo, nobody knows it, nobody knows Right from the start * On some devices camera HAL doesn't come up reliable. Camereraserver n...

github.com

shamu: Don't go breaking my HAL part 2 · LineageOS/android_device_moto_shamu@ad93b52

* Starting services in a specific order doesn't make much sense as 'start' isn't synchronus Reference: https://android.googlesource.com/platform/system/core/+/master/init/READ...

github.com

Everthing that has an influence on the boot timing can trigger or mitigate the race condition.

Things like: Power profile, number of installed apps, device temperature, cpu binning, ...
[Nexus 6  Original Android Development] esysfound:
So all these excellent screen shots don't show anything about certification (which is found in a Google Play settings menu).

But what exactly is your problem that makes you think you require Google Play Protect certification?

My phone is un-certified. Actually I am personally also un-certified. And yet, we both work fine.....
[Nexus 6  Original Android Development] npjohnson:
Fixed the DMconfig issue, next build should be fine. - Google Camera idk, you'd need to use the old APK, and even then not sure it will work on Android 11.

Lineage Recovery can too... click "Wipe" and pick either cache, data, or system. It uses format for all of them.

Fixed the DMconfig issue, next build should be fine. PayPay is due to SafetyNet likely, which we don't (and won't) pass.

Fixed the DMconfig issue, next build should be fine. - Good to hear you could upgrade like that but I wouldn't recommend this to others, as I'm not sure it covers all cases.

Good advice!

Refleash your gapps, or wipe your data, something isn't right, this works fine.

Fixed the DMconfig issue, next build should be fine.

don't use SBM1 - bad idea, unsupported, insecure. Burn it with fire.
[Nexus 6  Original Android Development] maddog3030:
Unfortunately I have some old equipment that are not smb2 so I'm stuck with it for the meantime I did find a workaround so I'm good thanks
[Nexus 6  Original Android Development] McMannes:
i cant load any apps, it always say insufficient storage in play store. How i can solve this problem
[Nexus 6  Original Android Development] dvdram:
Sorry for the long delay! I did not consider Waze, because I do not think of Waze and GM as two different apps. They are both made by Google, and a.f.a.i.k. they both work online only. Osmand, on the other hand, stores its maps on the phone and thus doesn't require any online connection while driving, and that is my preference.

Yes, you're right about that, but try to look at it like this: the microphone is needed when I speak, the speaker is needed when I am listening. So, why does the microphone need to be accessed, when I only want to listen to music? That does not make much sense, does i?

Yes, that issue is solved. Thanks for that! :)
[Nexus 6  Original Android Development] dvdram:
I found a small bug:

In the screen saver's options there's one setting to dim the clock's brightness in dark envirenments.

settings > display > screen saver > clock > settings > night mode

That setting is not being kept: deselecting "dimming in dark environment", does not make any difference, and when entering the menu again, that option is marked again.
[Nexus 6  Original Android Development] alfacrux:
It seems that there has been no new builds since that post... :D
[Nexus 6  Original Android Development] Elektroschmock:
It's already included in lineage-18.1-20210421-nightly-shamu-signed
[Nexus 6  Original Android Development] esysfound:
Time for a phone clean out. Look in Settings Storage and see how much free space you still have - will give you an idea of how much to chop. Delete some junk photos, old apps, music files after 1990 (just kidding). Might use CC Cleaner app (carefully)-it will clear out lots of junk but be slow and careful what you allow (and watch permissions). Then in Settings, Apps, PlayStore - clear cache and storage (carefully so you are sure you can recover all settings). Then try again. Avoid any solutions involving dynamite, vacuum cleaners, hydrochlorozine, or bleach.
[Nexus 6  Original Android Development] michele72:
Hi, I have the same problem, in the past (including on another device on A11, Poco F1) I was always able to get it working. Here is what I attempted and that in the past at the end worked:

Installed Viper 2.7.2.1 Magisk module, rebooted, granted SU permission.

V4A prompted for the installation of the driver, granted, rebooted and V4A asks again. So the problem is that the installation of the driver in the system fails.

Attempted to install Busybox in various ways (Meefik in play store, both via the app and via the Recovery zip method, and Stericson via play store, which usually works because it allows tro try system/xbin and system/bin, but this as well failed) . I am pretty sure that V4A uses Busybox in some way to install the driver so since Busybox fails to install, V4A fails to install the driver too.

OR, Busybox is no longer required for the installation of V4A, BUT.... the fact that there is no way to install Busybox in the system has the same root cause of the failed installation of V4A driver too! So I investigated this more

It turns out that there is no way to mount the system as RW in this version of LOS? I tried everything and it just doesn't mount as RW, so I am not wondering why both Busybox and V4A fails to install.

Maybe can this be tackled in some way by the DEVs? This was definitely working in the previous version 17.1
[Nexus 6  Original Android Development] muppetmania:
Does anyone have Netflix working? I use a DRM Checker and it shows that this ROM (or maybe it's because of the MindTheGApps package?) doesn't have Widevine at all. So Netflix won't work - I don't even get a sign in screen, just an error. I assume this is because it can't initalise the Widevine DRM.

I did a full wipe before installing!
[Nexus 6  Original Android Development] dvdram:
How does HFR mode work? No matter which resolution I choose, I am told that

I guess there are other Options to be set as well.
[Nexus 6  Original Android Development] psychoela:
Try again with latest magisk canary
[Nexus 6  Original Android Development] michele72:
Wow many thanks for this! It actually worked on CRDROID 7.5 (which is based on LOS) which has the same exact problem. And this worked! So, for everybody on LOS18.1 (Android 11) and derived roms, you can get Magisk Canary from here: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk . After getting the apk file and installing it, also rename the same file changing the extension to .zip. Restart to recovery and flash. Reboot. After that install Viper 2.7.2.1 from Magisk repository, don't reboot yet, just execute Viper and it will prompt to install driver. Reboot. Viper will work on music apps, however if you want to make it work for Youtube or other apps, go to the preferences and enable the Legacy mode. Works amazingly well!!!
[Nexus 6  Original Android Development] Markeee:
Just want to say I've used pretty much every Nexus 6 rom going back well over 5 yrs and this has got to be one of the if not the very best rom to date
[Nexus 6  Original Android Development] aja100:
Great ROM, every thing works fine.
[Nexus 6  Original Android Development] aja100:
Install big games from play store like Asphalt 9, Call of duty mobile and Dead trigger 2, PUBG mobile they start download and at end give error. Other small games no problem.

Can be fixed?
[Nexus 6  Original Android Development] esysfound:
I never thought of this before, but you could be right. The Singularity is near....
[Nexus 6  Original Android Development] alvi.bagolini:
Hi everyone, I'm on CRDroid because of face unlock, was wondering if anybody tried magisk module face unlock on this lineage.

cheers
[Nexus 6  Original Android Development] ExpertMC:
Has anyone had a chance to look into this? Lineage camera doesn't take as good pictures as the stock one
[Nexus 6  Original Android Development] npjohnson:
I'll take a look. Can you file a bug report according to wiki guide with logcat?
[Nexus 6  Original Android Development] npjohnson:
That's pretty much a known thing. We lack the Google processing. Use an old Google Camera if you want that. Or a newer GCam port.
[Nexus 6  Original Android Development] ahmedkordofani:
Does anyone else have back camera problems? Camera won't focus, blurry all the time. If any one has solved this problem please let me know. Love this ROM it's the best! :)
[Nexus 6  Original Android Development] Uplander:
Having carrier stability issue possibly due to apns config fix for giffgaff merged early April (14.04.21). Carrier issue (giffgaff ) also on official crDroid thread (7.5 update, April) posts #922 & #923.
[Nexus 6  Original Android Development] dahawthorne:
To add a bit more info to Uplander's comment above, I have a Nexus 5 and a Nexus 6, both running crDroid 7.6. I understand that crDroid is based on LOS sources.

I didn't know about the Giffgaff commit until Uplander mentioned it, but the timeline makes it look as if this was the cause of the instability.

My Nexus 6 has a Giffgaff SIM. (Giffgaff is a virtual UK network running on the larger O2 network). On crDroid 7.4 (March) mobile data was stable. 7.5 and 7.6 (April/May) have a mobile data signal which blinks in and out second by second. The same happens with LOS 18.1 10th May.

My Nexus 5 has an O2 SIM. The mobile data is stable on crDroid 7.6.

To me this indicates that the problem is with the Giffgaff component.
[Nexus 6  Original Android Development] BDroidz:
Running into the same issue as well even with Magisk 23.0 installed and SafetyNet checks passing. "DRM Info" doesn't show Widevine at all.

Symptoms:

1. Netflix encounters error on load.

2. Disney+ encounters error on playback start.

3. Udemy videos appear to play but have no image or audio.

4. Udemy videos within Chrome attempt to play multiple times but ultimately report a video error.

No issue with YouTube or other videos on the web so does appear to be DRM related.
[Nexus 6  Original Android Development] Elektroschmock:
Perhaps you could reopen this issue:

Update (fix) giffgaff APNs (#3070) · Issues · LineageOS / issues / android · GitLab

Expected Behavior giffgaff APN details should be up-to-date and correct. Current Behavior

gitlab.com
[Nexus 6  Original Android Development] dvdram:
I encountered a small problem concerning smart lock: when adding a trusted device to keep the phone unlocked, the list of BT devices does not show the name of the devices any more, if you renamed them, like "my car" or "kitchen radio". If you run two identical devices it's hard to tell them apart in that list. LOS 17 used the personalized names there.
[Nexus 6  Original Android Development] Uplander:
For anyone having issues with giffgaff (UK carrier) instability see posts #926 & #927 on official crDroid Android 11 v7.6 Shamu thread for possible workaround.
[Nexus 6  Original Android Development] McMannes:
Thank you very much for this nice rom. The volume is a little low, I wonder if there is a way to raise this. however the proximity sensor does not work sometimes
[Nexus 6  Original Android Development] npjohnson:
I don't. Can you toss a log up according to the bug report page on wiki.lineageos.org?

Give me the right APN and I'll push a fix.

Give me the right APN and I'll push a fix.

I'll look into it! Probably easy to fix.

Give me the right APN and I'll push a fix.

volume matches stock, proximity sensor die after some years, possible it's getting flakey, make sure it doesn't happen on stock too.
[Nexus 6  Original Android Development] aja100:
Download apk Netflix 4.16.0 build 15122 It work fine.
[Nexus 6  Original Android Development] aja100:
Android auto work fine on my car on wired connection. No problem.
[Nexus 6  Original Android Development] Detro_:
Hi, is there any way to remove this bottom bar?

Spoiler content hidden.
[Nexus 6  Original Android Development] BDroidz:
Given that the current version is "7.103.0 build 9 35464", going back to v4 seems non-ideal. Other video sources besides Netflix have issue as well. Was v4 recommended in another discussion somewhere?
[Nexus 6  Original Android Development] alvi.bagolini:
about google camera: not sure if this was already known but old 3.2.045 version of gcam works great with Android 11 CrDorid! may work also with Lineage..

cheers

PS: you need to disable energy saving on the camera app otherwise you will get black camera screen bug.
[Nexus 6  Original Android Development] cyrildtm:
Hello! I would like to report a problem with bluetooth.

I have several bluetooth headsets, as new as manufactured last year and as old as more than ten years. Before LOS 18.1, I used 16.1 to make phone calls with all of them and my Nexus 6 with no problems.

With LOS 18.1, soon as I upgraded the system, I was unable to hear the other party from my BT headset. The other one could hear me clearly. I tested with two phones myself so this is accurate.

With BT headset connected, in the in-call phone UI, I could select the talking device. If I switch from BT to speaker, no sound. If I switch from BT or speaker to "phone", sound appears. If I switch from "phone" to speaker, sound persists. If I switch from "phone" or speaker to BT, there is occasionally a fraction of second when I can hear something from the BT headset, but immediately the sound is cut off.

When there is no sound in my BT headset, I can hear the digital background noise -- pretty loud in my older devices -- as I have been hearing for the past decade, so I know the headset is working. Also, when I hang up, there is a "hang up" sound played through the headset. It's like it's working all the time but just refuses to give me voice call sound.

There is this fix all over Google:

I tried. The default configuration in my build.prop is "voicecall=true". All the above happened. When I changed it to "voicecall=false", it was the opposite. I could hear from BT headset and speaker, but not "phone". When I changed back to "voicecall=true", things went back again. This fix is not ideal, since I don't always carry a bluetooth device with me, and I do want to use the built-in earpiece for phone calls.

Other attempts I have tried --

Safe mode: Yes, I do hear sound over BT headset. But clearly I don't want to use a heavily modded phone for its "basic" purposes.

AudioFX: I cleared the "AudioFX" and "Bluetooth" apps storage. No help. I used Titanium Backup and froze "AudioFX" then no sound at all (understandable).

Disconnect BT devices and re-connect: I tried the simple, of course.

The only thing I did not try is clearing Wi-Fi and Bluetooth configuration. I have dozens of passwords and I don't want the hassle. To me for now it does not appear to be this part's issue, though.

Other build.prop attributes I tried --

persist.audio.fluence.voicecomm (false-->true)

ro.audio.flinger_standbytime_ms (300-->3000)

ro.qc.sdk.audio.fluencetype (fluence-->none)

The phone that used to work with BT voice had LOS 16.1 (last nightly ever; I do not like the "new[ly removed] features" from Android 10 as my daily driver so I passed). By the time 18.1 was out, I dropped my first Nexus 6 and I didn't feel repairing the screen anymore. The second Nexus 6 was on 17.1 but I never made phone calls until then, and I decided to upgraded it to 18.1 with a dirty flash (again, I don't want the hassle, I have 100+ apps). Been using every nightly since 18.1 official came out.

Many thanks to the developers and maintainers who keep this device working. It's still better in many ways than more recent flagship phones. I appreciate your work.
[Nexus 6  Original Android Development] pinakini:
The GCamGo_GreatnessNS2 works very well. Takes a lot better photos.

I found it on https://www.celsoazevedo.com/files/android/google-camera/f/changelog1447/
[Nexus 6  Original Android Development] esysfound:
"Better photos" than what? Based on what criteria? I have been using Open Camera and it has been fine, good interface, enough options, sharp photos, colors seem true. That it works is also a plus.....

@devs - thanks as always for the update (June) keeping the beast going.
[Nexus 6  Original Android Development] pinakini:
Sharper than the stock in good light.
[Nexus 6  Original Android Development] alfacrux:
Does some of the gcam ports work also in "nogapps" pure LineageOS 18.1?
[Nexus 6  Original Android Development] fahrer17:
First of all thank you very much for keeping the good ole N6 alive :) (y)

Sorry if this was asked before but I couldn't find an answer:

I want to update from 17.1. to 18.1. In the official instructions it is said to "wipe data partition" before updating. Using Lineage recovery the only wipe I find is "Factory Reset" but this means loosing all my files and stuff, right?

Is there a way to move on to 18.1 without a factory reset?
[Nexus 6  Original Android Development] dwardo:
Yep Molotov won't play anything either...
[Nexus 6  Original Android Development] alvi.bagolini:
update: one should NEVER kill the Gcam app. reboots are ok. If you kill it and re run it you get black screen and need to uninstall-reinstall. Yet I'm on CR-Droid android 11 so things may be different in Lineage.
[Nexus 6  Original Android Development] esysfound:
I have never used the Lineage Recovery - have stuck with TWRP (latest) because it is easier to use and I trust it. So take all this as context. I upgraded from 17.1 to 18.1 with a simple, dirty flash, and then clearing cache / Dalvik. Have had no problems. I have some apps that have gotten lost when wiping Data (it is the fault of the apps and where they store things) and it is time consuming to reinstall and reconfigure. So I fought this and it has worked fine. Part of the reason is that 18 is not such a huge change from 17. A System wipe is theoretically safer/better - if you look in the earlier pages of this thread you will see there are different approaches (I tried to get a consensus on this in those comments, and failed, so I just plunged ahead). I can only say what worked for me, using latest TWRP (3.5.2). It was quite painless. Have had 0 problems.

What you must do before anything is a full backup, and store this off phone. Once you do this, you can try what ever method suits, and if necessary roll it back and try an alternative if that does not work. That was my plan - try the simplest way first, knowing if there was a problem, I could recover all. I know how all this behaves in TWRP, less so with LOS recovery as I have never used it for real-I tried it and removed it as it seemed less powerful and / or I did not want to do the necessary learning. (You should not have both on your phone so you have to choose) and make sure the recovery image is stored in Recovery, not the Boot partition. Either way, just make sure you have a full backup first and you really cannot go wrong.
[Nexus 6  Original Android Development] runekock:
@fahrer17

Dirty flash is known to fail if you have any kind of lock screen security (e.g. pin or pattern). If you remove that beforehand, dirty flash might work.

Edit: Even with screen lock removed, dirty flash didn't immediately work for me. I had to delete the .key files that @Elektroschmock mentioned:

https://xdaforums.com/t/official-lineageos-18-1-for-the-nexus-6.4255327/post-84768101
[Nexus 6  Original Android Development] esysfound:
Indeed - good point, and I did remove this first, forgot to mention.
[Nexus 6  Original Android Development] npjohnson:
This was a platform wide issue due to a few really old typos :(

It is fixed in the newest builds. Sorry for the inconvenience!
[Nexus 6  Original Android Development] Chriz87:
Hi

I've been enjoying lineageos 18 in my shamu.

But since the last updates my phone has been reaching up to 55°c while charging, that's really hot, the max temp I was getting in lineage 17 was 45°c. I'm using nikgapps btw.

Anyone else is experiencing it?
[Nexus 6  Original Android Development] Elektroschmock:
We haven't changed anything charging related. Batteries close to their end of life show this behaviour.
[Nexus 6  Original Android Development] cyrildtm:
Thank you for the update! I tried the latest, 20210609, but it's got worse. With BT headset connected, when I started a call, it was silent on my side (caller) as before. When I switched to "phone", it became silent which was different than before. Then I tried "speaker" and then back to "phone" and it was giving sound again. Without any BT connected, when I started a phone call, it was all fine.

Was the related fix "Remove USE_XML_AUDIO_POLICY_CONF"? I saw that being applied across the board. I might be wrong. Is there anything else I need to do on my side?
[Nexus 6  Original Android Development] npjohnson:
that change changes nothing. The flag has been dead for about a year now lol.

But weird, so BT calls don't work?
[Nexus 6  Original Android Development] Chriz87:
Ooohh, thank you. Time to replace it then.