yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] cyrildtm:
They don't. All I can hear from the earpiece is background digital noise (my other better BT devices don't even have anything for me to hear).

When I search online about this issue, I can see a few people were having the same issues. Most suggested "fixes" were rebooting, resetting, and reconnecting BT. I didn't start reporting this issue here until I exhausted everything I could do on my side, except a full factory wipe. Sadly as my network is migrating to VOLTE, I will have to abandon Nexus 6 in a couple of months, and I already have another phone set up ready so I don't feel wiping by daily driver and reinstalling everything from ground up.

For the past year I have been using 16.1 on my other Nexus 6 which is broken by now. Calling with BT worked on that one.

I was hoping there was a magic switch to turn off the new noise reduction / noise cancelling implementation in newer Android versions, so things can fall back to the way in LOS 16.1. I might be wrong but I believe it's somehow related, since according to my initial investigation, messing around with "fluence" did bring some changes, just not the good ones. Oh yeah BTW the noise cancelling effect is much worse in this version than before; I can hear it.
[Nexus 6  Original Android Development] Elektroschmock:
You might try to disable voice match
[Nexus 6  Original Android Development] cyrildtm:
Thank you, Elektroschmock! That worked. I only turned off Voice Match in Google Assistant, not "Okay Google" in Google Maps during navigation. And phone voice is working with and without navigation in foreground and background.

This is a good enough solution for me, since "Okay google" is not that responsive when the phone is idle anyway (because N6 does not have an always-active voice processing circuit, so far as I understand.

Let me collect my memory about what I have done. When I booted my phone into safe mode, no user apps were enabled, and the phone voice was working. I didn't bother to disable-enable each of my 100+ apps one at a time, but I did try with a dozen that had "Phone" permission granted, * including Google Assistant *. Disabling Google Assistant did not make it, though. Following Elektroschmock's instruction, disabling voice match while leaving google assistant installed worked.

It's interesting to see how Google has evolved along the years when they claimed they tried to improve device compatibility.
[Nexus 6  Original Android Development] McMannes:
How can I install netflix, is there any solution?
[Nexus 6  Original Android Development] TravMan_63:
Hello,

Thank you for the work put into this ROM.

I had not visited the forums nor installed a new ROM for a couple of years (was running Nitrogen - Pie) - I had to 'relearn' ...

(I started 1st custom ROM back with JBSourcery on a Galaxy Nexus)...

Nitrogen on the Nexus 6 had too many frequent need to reboot for camera/flashlight, or the phone just randomly indicating 'No SIM ' and doing 'something like' a GUI reboot. (removing and re-seating the SIM did nothing) as well as 2 years running and becoming really laggy...

I initially flashed Arrow with their recommended Gapps - and had several applications I couldn't run (noteably acar could not import data) issues with syncing google apps.

(sorry for the long intro)

Installed Lineage 2021.06.29 and 'all the troubles' were gone. The setup went very smoothly.

I am running build# RQ3A.210605.005 7074f5a3f4

Acar imported data just fine (about 10 years worth!)

Response is much better.

No Sim issues like I had with Nitrogen/no 'GUI restarts'

3 similar issues (Arrow and Lineage) - Google Camera shows black screen (using pre installed camera and open camera work fine - reboots and all no issues with that or flashlight)

I notice application 'droid Info' - doesn't read thermal or CPU

One other similar issue - which I thought had completed / not an issue - is SprintDM - the configuring network never finishes.... (it's been running 6 hrs at this moment)

and - I just discovered (attempting to send MMS - which failed)- I do not have cellular data (I am on Sprint/T-Mobile)

Calls and SMS work fine -

--

Is there a known fix for the SprintDM issue?

--
[Nexus 6  Original Android Development] runekock:
Google Camera: you'll need to go back to version 3. Version 4 doesn't run on Lineage 18.

Data: check APN. Also, flash latest baseband if you have an old one - the latest is MDM9625_104670.31.05.51R
[Nexus 6  Original Android Development] TravMan_63:
Thank you for the quick reply

I found this thread , which lead to this 1GB download (wow)

from Q9Nap

also this older thread from 2012

APN - referring to - settings - network & internet - Mobile network - Advanced - Access Point Names

This is set to Sprint LTE internet - I believe this is correct.

My current Baseband version = MDM9625_104662.2205.34R

About phone>Android version

---

I would think the baseband file would be relatively small - do you have a source?

Then would this (baseband file) simply be flashed via TWRP?
[Nexus 6  Original Android Development] runekock:
APN: you'll need to check the settings within the Sprint entry. Sprint should list the needed settings somewhere on their website.

Baseband: sometimes people have made TWRP-flashable files, but if you can't find one, then download the complete stock rom from https://developers.google.com/android/images and fastboot flash just the radio image (you can see the command in the flash-all batch file). Or - if you don't mind losing the files on your phone - flash the complete stock rom, which will also update other partitions such as the bootloader.
[Nexus 6  Original Android Development] TravMan_63:
Thank you again.

Report: (concerning data for Sprint (US) ) and Sprint DM

Quick summary:

I have this working at the moment. Fix - toggle airplane mode.

This may or may not stick (keep active) with reboots - mixed results.

Sometimes need to toggle more than 1x, and wait a few moments in between toggle states.

The above has worked for the last 4+ reboots and testing.

Toggling wifi on off does not work reliably - use airplane mode toggle.

Have verified MMS sending while on WIFI working OK

-------------------

Long notes:

Something new: unable to save APN

Here are the settings needed per T-Mobile / Sprint:

Note that MMS Protocol is not listed on the phone.

https://www.t-mobile.com/support/de.../byod-t-mobile-data-and-apn-settings#subhead2

Attempting to save gives no error, and no listing in the APN list.

Other methods that did work - but not every time:

Create a new APN - even though not saved, worked.

Create a new APN - only putting in the name (I used test) - then back out.

Toggle Global <> LTE (note 2nd phone same carrier/Pixel) is on global (The Nexus - is on LTE)

Also note could not view APN information on the Pixel (it is stock non modified)

Selected the available radio button APN's - then Sprint LTE - worked

(again all these would not perform as reliably as the airplane toggle).

To rule out the phone currently having issues: phone had no radio issues on the Nitrogen Pie (9) Rom just earlier this week (and ran that ROM > 1 year)

Arrow ROM (also 11( also had issues - I believe the radio did work intermittently.

---

Thank you very much for your assistance, greatly appreciated.

Good news (2 of the reasons to flash a new ROM - the camera and flash light are working 100% (there is a small delay at boot up), and no ' random partial GUI reboots' like I experienced with Pie.
[Nexus 6  Original Android Development] Rootmaster906:
Can we just flash this in twrp?
[Nexus 6  Original Android Development] npjohnson:
Probably. But you should follow the wiki guide, it's guaranteed to work.
[Nexus 6  Original Android Development] Rootmaster906:
Thanks. But I don't like using lineage recovery. Not many options within that recovery
[Nexus 6  Original Android Development] npjohnson:
Seed vault backup in the OS + Lineage Recovery ftw.

If you use TWRP and have problems flashing tho, probably won't be able to help much
[Nexus 6  Original Android Development] McMannes:
Thanks my friend, it works
[Nexus 6  Original Android Development] aja100:
Open GApps for android 11 is now available.

Maybe works on LOS 18.1?
[Nexus 6  Original Android Development] fahrer17:
Tank you and sorry for my very late reply :(

Unfortunately I didn't receive any notification when you answered my question.

As I was pretty impatient to update my N6 I formated everything and installed TWRP+CrDroid (I guess, not sure atm).

It is not my daily phone any more and I didn't have much time to play around so it ran out of battery and is lying around.

But as soon as possible I'd like to give LOS18 a try.
[Nexus 6  Original Android Development] e.venasquez21:
Can I flash this on Nexus's 6 latest TWRP instead of installing Lineage OS Recovery?
[Nexus 6  Original Android Development] Elektroschmock:
This was asked and answered 8 posts above.

It might work, but we just don't know it.

TWRP for Shamu is maintained by nobody and is probably outdated.
[Nexus 6  Original Android Development] runekock:
I flashed with TWRP, and it worked fine. Then a few hours later, my phone fatally bricked itself.

I don't think we can conclude anything from that.
[Nexus 6  Original Android Development] xdaggg:
My Nexus 6 is on the latest nightly and has this issue as well. Any chance of a fix? And thank you for keeping this device updated!
[Nexus 6  Original Android Development] npjohnson:
Fixed by https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/313599 - next build should be fine.
[Nexus 6  Original Android Development] Elektroschmock:
Echo in Hangouts an other apps using webrtc should be fixed with lineage-18.1-20210721-nightly-shamu-signed
[Nexus 6  Original Android Development] alfacrux:
lineage-18.1-20210721-nightly-shamu-signed upgrade results no camera application...

Edit: some reboots and camera is back

:)
[Nexus 6  Original Android Development] Elektroschmock:
This is a well known bug since 15.1 which we unfortunately can't fix.
[Nexus 6  Original Android Development] xdaggg:
Flashed latest nightly and still having problems with Netflix. Netflix shows error code "502.-1006" immediately when launching, disabling DRM/liboemcrypto lets it load a little further but then reports error code "501.-109" instead. Did you or anyone else manage to get it working successfully? Thanks
[Nexus 6  Original Android Development] cyrildtm:
Same.

DRM info app reports the same as before, no Widevine.
[Nexus 6  Original Android Development] npjohnson:
Looking into it.
[Nexus 6  Original Android Development] indians810:
I was wondering if Stadia is working for anyone on the latest build. I launch any game and it just immediately crashes back to the home screen. Maybe it has to do with the DRM issue? I changed the graphics driver under developer options and it still did the same thing.
[Nexus 6  Original Android Development] woodsticks:
Thank you Devs and everyone who contributed to this ROM and for keeping Shamu going. I Dig It! Works Butter Smooth for me.

Coming from LOS 17.1 and keeping it simple, I used lineage recovery 18.1-20210804, then using a microSD & adapter flashing 18.1 20210804 and MtG. No issues, it's not over heating. Right On!
[Nexus 6  Original Android Development] mithic:
Hi, thanks everyone for this awesome rom!!I am on latest 18.1-20210811, but what i'm going to describe it happens also in previous editions.

ONLY when i am on a "normal" call (using 2g,3g or lte) and am trying to navigate on internet through wifi or mobile connection my phone shutdown!!

ps: (my battery is new,1 year ago was changed).
[Nexus 6  Original Android Development] Markeee:
Getting alot of instability random shutdowns and reboots also with this rom
[Nexus 6  Original Android Development] 96carboard:
This doesn't make sense, because its just the application launcher icon that disappears, the camera itself still works if launched through another application, like gallery.
[Nexus 6  Original Android Development] 96carboard:
How old is your battery? Mine was doing weird crap like that if the battery was under 75%, and basically wouldn't work at all if the battery was under 50%. Changed the battery and its rock solid after 6 hours screen on and 48 hours since last charge. I also changed with an OEM LG EZ30, which are cheap anyway, $11 CAD: https://www.esourceparts.ca/motorola-google-nexus-6-xt1100-xt1103-ez30-replacement-battery.html

I wouldn't waste energy trying to go with an off-brand battery. Why pay 4x as much for a knockoff that doesn't even *pretend* to be better spec? The only thing you need to be cautious about in replacing the battery, is peeling the charger coil off the old battery. Its the only thing under the back cover that's actually glued, everything else is really nicely screwed together. I wish phones were still made like this, its a true beauty.
[Nexus 6  Original Android Development] 96carboard:
OEM or knockoff?
[Nexus 6  Original Android Development] 96carboard:
@npjohnson : Nice work on this. Normally I build my own everything from AOSP, but time is tight for me this year, so thank you very much for this. Its nice enough that I've switched back to N6 from P2XL (screen is just not wide enough at 68mm vs 74mm). It might be short lived for me though, the P6Pro (71mm) might be adequate with a bit of layout trickery in the OSK. Nevertheless, never thought I'd be switching back to this phone :)
[Nexus 6  Original Android Development] mithic:
OEM.
[Nexus 6  Original Android Development] Markeee:
Yeah I guess I really need to go ahead and replace the battery mine is super old and having the same symptoms as you mentioned . I think I'll pay someone to do it for me this time I tried changing the battery on my Pixel C Tab a few months ago and i destroyed the thing accidently slashed a cable trying to separate the screen from it. One thing that kind worries me about buying the original OEM Nexus 6 batteries is they all seem to be from super old stock they don't make the battery anymore and from what i read Li ion batteries have a unused shelf life ?

​
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] npjohnson:
Google Pixel 3a

- Your warranty is now void.
- You have been warned.
- Use at your own risk.

Introduction:

This is the Official Lineage OS 18.1 thread for the Google Pixel 3a .

Downloads:

Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.

sargo

If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

Known Bugs:

None.

Find any? Report them according to this guide.

Notes:

The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.

Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!

Kernel Source: https://github.com/LineageOS/android_kernel_google_msm-4.9
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] SilentDenizen:
nice, I'm about to try it

edit: works great, I love it. thanks for sharing this post.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Mokura3rd:
Followed update instructions, everything appears to be working fine so far. I was even able to sideload MindTheGapps after using OpenGapps back on 17.1! I'll be reinstalling my modules that rely on version detection for functionality, but I think it's going to be smooth sailing. Easiest major version update I've done for something in a long time.

EDIT: Never mind, Magisk is having issues detecting itself, meaning I'll probably have to factory reset - but that's no issue, I can move all my data to backups first.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] VP24:
I had problems with NFC on 17.1 (simply did not turn on). Any known issues on 18.1?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Mokura3rd:
I'll give the April 6 build a try soon - I had some weird issues with Magisk and reverted to the final 17.1 build. Magisk had an update as well so hopefully things don't go sideways this time.

Side question - does the old flashable su module still work, or is that more for legacy devices?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] batp:
My Tello T-Mobile sim won't work with LTE data on these builds.

It shows nothing in APN and won't let me add one.

"access point name settings are not available for this user lineage"

I put in my tracfone sim and it works.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Mokura3rd:
After a fresh install:

So far so good on the new build with Magisk. Crossing my fingers Android Auto works, but so far everything else seems to be okay, Google Fi included.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] FA21:
As far as I can see so far, the update from 17.1 to 18.1 went almost without problems. KeyPassDX had to be reinstalled once, but now works again.

I had uninstalled the Magisk modules before. Magisk itself could not be uninstalled. But it was no problem. After sideloading the latest 18.1 nightly, reboot to system, reboot to recovery, sideload Magisk 22.0 zip, everything runs as usual. Thank you.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Mokura3rd:
Android Auto worked flawlessly. I also installed the ElementalX kernel and KTweak with no issues. LOS runs like a dream again, thank you!
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] MoistPicklez:
Unfortunately I get no mobile data after installing gapps. I'm using Telus as my carrier in Canada. This happens on quite a few different ROMs that I've tried. I will be willing to do some testing if there's hope that this can get resolved @npjohnson
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] ceebeeme72:
I have never gotten any of the Lineage recoveries to work with my Pixel 3a. TWRP works using the guide, but I thought since it doesn't support Android 10, that LineageOS 18.x cannot be flashed with TWRP. For those that are using 18, how did you end up installing it?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] blksith0:
This is probably our best Android-11 ROM option at the moment, correct?

I'll likely upgrade, since DU is still on 10, but:

Does Lineage have our phone's Active-Edge support?

Does it allow dragging across the top nav-bar for brightness adjustment?

I wish I could have the stability of LOS with the customizability of Bliss.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] KingJ50:
Having issues with this rom and MagiskHide. Once Hide is enabled the system becomes unstable and no new apps will open. Eventually the system just locks up completely. I tried factory resetting as well. Eventually downgraded but figured I'd try again seeing as a few updates have happened. Still having the same issue. If I disable Hide and reboot than the system works great. Has anyone else had this issue or is it even known? I have not been able to find anything about this on Google or XDA.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Mokura3rd:
View attachment 5278101

Does "update recovery" relate to the boot image? In other words, if the switch is off, will Magisk be retained? Either way, I should probably bring my update/Magisk instructions here.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Mokura3rd:
1. Flash latest A11 factory image, let it boot to the welcome screen.

2. Enter bootloader, flash recovery. (EDIT: fastboot flash boot [recovery zip file])

3. Enter recovery, factory reset.

4. Navigate to update w/ADB, sideload LOS zip.

5. (Optional) Use recovery menu to reboot to recovery again, to sideload MindTheGapps.

6. Reboot to system.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] CelerClicks:
Just upgraded from 17.1 and Everything works great! (Including the NFC)
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] ceebeeme72:
Thanks for that, but I already tried something similar. After flashing the A11 factory image, when I start the bootloader and try to flash the recovery, I get the error message " FAILED (remote: 'Not allowed to flash (recovery)')"
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Mokura3rd:
Did you try "fastboot flash boot [LOS recovery file.zip]"? Emphasis mine. I should have been more clear in my instructions, sorry.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] ceebeeme72:
No, the LineageOS recoveries that I have been using are all *.img.

I found a work around finally. I followed the first few initial instructions:

fastboot flash boot boot.img

fastboot flash dtbo dtbo.img

fastboot flash vbmeta vbmeta.img

And then I was able to successfully flash the lineage recovery by using "fastboot flash boot [LOS recovery file.img]"

Now my problem in the same as why I switched from the LG G5 to the Pixel 3a, VoLTE and Wifi Calling don't work.

Oh, well. Thanks for the help.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] npjohnson:
File a bug ticket as the wiki describes pls, can help more there.

No clue why that would be - they work for everyone else...

Good to hear!

You shouldn't be flashing 'recovery' - read the wiki pls, you may mess up your device.

Don't do any of this.

Flash stock Android 11, then as per the wiki guide, fastboot flash boot lineage-recovery.img, and then boot to recovery immeadiately.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] ceebeeme72:
Yeah, I tried that. Multiple times. When I found out that I could reset my Pixel 3a with the Android Recovery Tool, even if it was bootlooped, then I started experimenting. The process I used worked. The one you outlined did not.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] npjohnson:
You:

1. Started on Android 11

2. Rebooted to bootloader

3. `fastboot flash boot lineage-recovery.img`

4. Use keys to select and boot to recovery

5. Sideload LineageOS

6. Click "Advanced", "Reboot Recovery"

7. Sideload MindTheGapps?

I ran through these exactly so some wires must be getting crossed here.

Also, Android Recovery Tool is not needed at all, ever. You can factory reset a bootlooped device from recovery at any time. If you mess up recovery, you can reflash it.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] ceebeeme72:
Really? I wonder why it exists then? I used it, and it did what I wanted it to do, and it was super easy.

And I had major problems flashing a recovery in the first place. Any recovery. So your advice to fix a boot loop by re flashing a recovery just wasn't possible. I tried it. Multiple times. Which is why I used the Android Recovery Tool.

And the list of steps you posted did not work for me. I got an error every time on step #3. As I said earlier.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] npjohnson:
What was your error on step 3?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] reini_from_nl:
I am using this rom and all is working really good. But the volume on calls is very low. Does anyone know something about this problem?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] npjohnson:
we use the same configuration from stock, so unsure why you'd experience that.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Anghirrim:
Hi,

First, thanks for this rom, this is nice to see a good support for the Pixel 3a.

I just recently bought mine and plan to unlock the bootloader and flash LOS 18.1.

I have one question regarding camera quality. The main reason I bought the 3a is for it's super good photo/picture quality.

On LOS 18.1, will it be as good as on stock, or should I expect some loss?

Thanks,
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] pojr:
I was waiting for this update. Didn't feel like downgrading from Android 11 to 10.

I have a dummy question for you guys. When using lineage, if there's an OTA update is it simpler than updating stock Android on an unlocked bootloader? I just like the idea of hitting "update" and actually being able to update without having to do anything additional.

Just curious, thank you.