yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Elektroschmock:
It needs some time untill the build is mirrored to all servers.
[Nexus 6  Original Android Development] werindam:
can we able to change bluetooth driver somehow? it's possible to choose in dev options but when i change it to LDAC or anything else its returns to SBC..

and anything about audio bluetooth what i change it returns to default
[Nexus 6  Original Android Development] Elektroschmock:
I guess you mean the codec and not the driver.

To be able to change it you need to have a BT device connected which supports the codec you want to switch to.

We don't ship some Codecs linke AptX for legal reasons. Those won't work out of the box.
[Nexus 6  Original Android Development] werindam:
i just realized something weird.

when BT is (i guess) in low energy mode when not playing anything and then when i receive notification or start play music in my phone then volume panel appears.. maybe it's intended action?

and yes..

I can change codec(yep not driver) but when i goes back and then again in dev options it shows default - can't change

//edit nevermind.. my speaker doesn't support other codecs, only SBC. Sorry
[Nexus 6  Original Android Development] Elektroschmock:
Changelog 23 has been published

A new changelog has been published.

Perhaps you haven't discovered some of the new features yet.

https://lineageos.org/Changelog-23/
[Nexus 6  Original Android Development] githyanki:
The last update to the kernel seems to be a lot better on my battery!

Thanks!
[Nexus 6  Original Android Development] pinakini:
Call recording is enabled for India. I could not find a button or something for recording or I have to use an additional app for that?

Please ignore my ignorance.
[Nexus 6  Original Android Development] Elektroschmock:
It needs to be enabled per device.

I never found the time and passion to do that for shamu.

Right now I don't have SIM in my device, but maybe I'll look into implementing it next month.
[Nexus 6  Original Android Development] mrk2815:
what can we change with the stock lineage kernel if we have a kernel manager app on our device.
[Nexus 6  Original Android Development] githyanki:
Most kernel managers can detect which settings they can change and will only show appropriate options. For more details, check with the appropriate thread for the manager you are using.
[Nexus 6  Original Android Development] TAGTRAUM:
No mobile network after last nightly update, all radio related options in settings greyed out (WiFi and BT works), dirty or clean flash, w/ and w/o erasing baseband cache and flashing radio, same result, 22 June build for example after flashing have mobile network as usual right after loading
[Nexus 6  Original Android Development] Belahzur:
Hey there [MENTION=3383960]Elektroschmock[/MENTION]

Would like to work with you to resolve the camera bug that is still plaguing LOS 16 build July 8th, attached is a logcat running during trying to open the Camera app, build number 190705.003 a8ea17839

Hope that helps
[Nexus 6  Original Android Development] Elektroschmock:
Like posted before, the settings you can change are autodetected. But very little oft them make sense to change. Like fiddling with hotplugging will break the power hal.
[Nexus 6  Original Android Development] Majorcrafter:
Good to know I'm not the only one having a camera issue. Any way to get it working while they find a fix?
[Nexus 6  Original Android Development] Elektroschmock:
Unfortunately a log i not enough. I got a lot of them, but I wasn't able to reproduce the problem.

I need more info like when did the bug occur, how did you install it. How many apps do you have installed.

Perhaps if having more info I can see a pattern why only ~ 1 % of the users are affected.
[Nexus 6  Original Android Development] Belahzur:
Hi there Elektro.

Right now this Nexus 6 has 7 apps (Non-Google related) from Play Store, but the bug with the camera is still there, even on a fresh wipe and install with nothing but Nano Gapps installed, and the Google Camera installed from Play Store (Camera not included with Nano)
[Nexus 6  Original Android Development] Sanabil:
Try stock gapps,
[Nexus 6  Original Android Development] dvdram:
Please forgive me, but I am a bit disappointed now. Many users are eagerly waiting for Bluetooth to be fixed, so that system signals and alarms are not routed to BT devices any more, but instead someone comes up with a rainbow mode, whatever this is good for.

Seriously? :(
[Nexus 6  Original Android Development] dahawthorne:
And I reply to you in return - seriously?

I'm an end user like you, and I wouldn't dare to criticise devs who maintain our 5-year-old devices on the cutting edge of software. They do this as volunteers, hobbyists, and they don't need self-entitled people complaining about which path they choose to follow.

Take some time to think about your attitude.
[Nexus 6  Original Android Development] p-hil:
I've been having this issue since the 16.0 release. I'm sure it affects more than 1%, maybe they're just not reporting the issue.

So to help, we need to include:

logcat

time the bug occured

install method

number of apps installed

Would anything else help with this?
[Nexus 6  Original Android Development] jacomail95:
Is there any hope left for a workaround to enable correctly the WiFi Direct on Pie? I use my device often for screen mirroring and WiFi repeater, and I don't really want to downgrade to Oreo. I don't want to impose, really, I'd just like to know why Pie is different from previous Android versions when it comes about that feature. Thanks for the ROM, and I am grateful for all the work behind it, have a nice day devs
[Nexus 6  Original Android Development] Elektroschmock:
Rainbow mode is a very important feature! Life without rainbows is possible, but doesn't make sense. :p

I am the only one working on shamu so if a developer decides he want's to implement a feature it doesn't mean anything for shamu

Not the time - more like when did the bug occur e.g on first install, update at random times.

One more thing which could trigger it is thermal limiting.

It might be, that if you did a backup first and then install the ROM that your device gets that hot that the cores enter thermal frequency limiting.

With PIE there were many changes to which we had to adapt to.

I guess those two changes are connected with the issue you are seeing.

https://github.com/LineageOS/androi...25774ef#diff-c23f7ab876ac167e05468ef79f046cb7

https://github.com/LineageOS/androi...591196a#diff-c23f7ab876ac167e05468ef79f046cb7

Unfortunately I haven't had time and won't have time the next 3-4 weeks as I'll be looking after ~100 kids at a summer camp

Maybe [MENTION=5848265]npjohnson[/MENTION] can give it a try in the meantime?
[Nexus 6  Original Android Development] npjohnson:
You mean Wi-Fi display? Pie removed this feature (Miricast, or otherwise). We did re-add QCOM's implementation, but it uses CAF blobs I don't think will work on a non CAF device. Feel free to try (look at other devices who did it on Gerrit) and contribute yourself if you want to! I have no device to test it and don't really care to.

If you mean Wi-Fi direct, it's broken on many legacy devices, file a ticket on Gitlab please. I'll try to get to it.

It's a race condition, just re-format data and chances are you won't hit it again.

No clue, tried it, works fine.

Try clean flashing, or removing your mods.

Yeah, so, the Camera issue is a race-condition logs won't show, and that is only hit (in my testing) ~1/15-20 times you clean flash -- so basically, just format /data once more and statistically, you won't hit it again.

---------- Post added at 07:01 AM ---------- Previous post was at 06:54 AM ----------

Might look at it. Many legacy device (klte, etc.) have this issue too, so we aren't alone.

I don't forgive you, honestly. That comment just pisses me off.

I didn't even write that feature, and YoDevil just picked it from a branch from long ago -- it's the people who worked on that 1. Don't even have shamu & 2. Don't owe you anything.

And heres the thing -- I might be able to fix this, if anyone who hits a bug would actually *report* said bug the actual way. I have gone through and explained, worked on, fixed, or otherwise for all shamu tickets https://gitlab.com/LineageOS/issues/android/issues?label_name[]=device:shamu&state=closed, leaving only 2 open, as they're not shamu specific, and are platform bugs I don't know how to solve.

So in short, don't act like that, as it kills any motivation we have, and also, file a ticket with logs if you have an actual issue.
[Nexus 6  Original Android Development] dvdram:
If my comment sounded rude to you or if it insulted you: I am really sorry for that!

It was not meant to be an insult, it was meant to be a criticism. I apreaciate the work that you and every one else working on LOS are doing. But I can't understand the priority that has been chosen there: how many people have complained about missing rainbow colors, how many have said they can't use their phone any longer without it? And on the other hand: if you search the web about that bluetooth bug, you'll find lots and lots of people complaining about missing important system notifications, because they are routed to a paired bluetooth device, no matter if that device is in use or not. In Android O and LOS 15 and below it was possible to get system sounds out of the phone's speaker, while only phone calls and music was routed via BT. That is a very important feature, which is really missing.

I know that this BT bug is not shamu specific, it hits other models as well. And I also don't hold you or any one else working on LOS responsible for it. If it sounded like that: once again, I am sorry! I guess Google messed up the kernel or the BT driver, and sadly, LOS inherited that bug.

But try to look at it from an end user's point of view: there is something very important that needs to be fixed, that you really, really miss, that makes you miss important notifications after upgrading to LOS 16, and then you see a change log entry about something like rainbow colours. What would you think in such a position? Even if the two issues have nothing in common, wouldn't it irritate you a bit?
[Nexus 6  Original Android Development] dahawthorne:
Keep digging...
[Nexus 6  Original Android Development] dbrickg:
A hundred kids! That's a LOT of kids! Hope you have a great time! Cheers!
[Nexus 6  Original Android Development] npjohnson:
No one complained about rainbows begin missing -- but again, literally a tiny, nominal amount of work and time was spent on something some of us enjoy for nostalgias sake (very old CM joke).

You didn't even cover the most important thing here -- No one has filed a bugreport! If no one is going to go to the work to help me understand it on the tracker we use, there's no way it's getting fixed.

And if that honestly pisses you off, maybe Lineage/OSS software just aren't for you. not everyone is going to drop what they're doing to work on a bug on a random device many of them don't even have.
[Nexus 6  Original Android Development] jacomail95:
I absolutely have no idea of how it happened, but now WiFi Direct works, at least for my need of using the phone as WiFi repeater. I can't change name and password, but hey, now I don't have to downgrade to Oreo. Again, thanks for maintaining this ROM, devs
[Nexus 6  Original Android Development] dvdram:
I would have thought that there was more than one bug report, because when you search the web about bluetooth and missing notifications, there are tons of complains from users who miss calls from their boss or important messages. Even here, at xda, there can be found lots of comments about this strange BT behaviour on Pie.

After doing some research, I now learned that this behaviour is intended by Google: when a BT A2DP sink is connected, every sound is sent there. And in my opinion, that has been a very stupid idea by Google, because it turns out that people miss important messages and even calls from their boss, because the BT sink is muted or not able to play the notification sound.

I appreciate all the work, that LOS developers do, and I really believe them to be smarter than those person(s) at Google, who came up with this idea for BT. That's why I am asking this: as far as I know, Android is Open Source, and anyone (capable of programming) can modify it to their needs. Is a law that LOS has to inherit and life with this stupid idea from Google? Would it be possible for LOS to undo this decision?

If it is possible for LOS to undo this strange BT behaviour, or at least to give the user a choice where to send system notifications, I would like to ask you to do so, very humble and politely! I am convinced, that this would not just please existing LOS users, I think it will also make much more people want to use LOS instead of their stock ROM, when they get choices that Google don't offer.
[Nexus 6  Original Android Development] githyanki:
I agree with you. Now, file a bug report and label it as enhancement request . If you don't, then you are not really doing anything more than talking, just like all the info you found on the web about this issue.
[Nexus 6  Original Android Development] dvdram:
Could you explain to me, where and how I do that? At this page it says, feature requests should not be reported. So, where do I make this request?
[Nexus 6  Original Android Development] githyanki:
Good question. Never made a feature request so not sure. Hopefully one of the developers can tell you how to do that. I don't think you should call it a bug (although it may seem like one), it would probably get deleted.
[Nexus 6  Original Android Development] dahawthorne:
[MENTION=5926898]dvdram[/MENTION]

It's probably best that you follow the path you've suggested (see link below) and quit wasting electronic paper and everyone's time.

https://xdaforums.com/nexus-6/help/downgrade-los-16-to-los-15-1-t3949385
[Nexus 6  Original Android Development] jdranzer:
You have a misconception about how an oper source project works, specifically with LOS.

LOS developers make their best effort to bring us an updated OS to our legacy phones. Yes, they bring enhancements and new features that stock Android don't have. And wether their time and other factors allows them, they kindly accept requests to implement new features, which doesn't imply they are forced to deliver. From this perspective, your request is disrespectful to their work.

I suggest you to read the FAQ in the LOS website.

***
[Nexus 6  Original Android Development] dbrickg:
you forgot to say "respectfully" :)
[Nexus 6  Original Android Development] dvdram:
I think you completely misunderstood what I said. I never doubted the effort and commitment LOS developers put into this big project. Quite the opposite: I appreciate it and I am very thankful for their work. They have done so many enhancements to Android, they made so many things in a better way than Google ever did, so I don't understand why you call it disrespectful to ask them if they can do another enhancement or undo a dumb decision that Google made.

Can you tell my why you see disrespect in such a request?
[Nexus 6  Original Android Development] Elektroschmock:
We're getting a bit offtopic here. I guess nobody felt offended.

The thing is just that we don't accept change / feature requests. Usually developers work on stuff the want or need.

Perhaps no dev is bothered by the change in behaviour you described.

Maybe you want to look into fixing/changing it yourself. It might be an easy change if you find out which code is involved.
[Nexus 6  Original Android Development] beta1204:
Hi,

I have been using version 16.0 since the beginning. Great work, well done!

I am looking for a solution to switch the smartphone to airplane mode after X minutes.

I listen to the radio in the evening with a timer and I would like to switch the smartphone to plane mode automatically.

Do you have any ideas?

Thanks !
[Nexus 6  Original Android Development] Dhalsim43:
You can use Tasker or Trigger app
[Nexus 6  Original Android Development] beta1204:
Ok, thanks !

I had already looked at the "Tasker" application but it requires root access. The problem is that my bank's application doesn't accept a root phone.

Do you know a solution to hide root access to an application ? I had tried "magisk" on another ROM but it didn't work.

Do you know if "magisk" works correctly to hide applications on LineageOS 16.0? If not another solution ?

For root access currently I have installed "addonsu-16.0-arm-signed.zip" add-on (root access is therefore not permanently enabled).

Thanks,
[Nexus 6  Original Android Development] spastico:
I had gave up and went back to 15. Gave 16 another try last week, and now all is good.
[Nexus 6  Original Android Development] spiral777:
Att shamu Los16 apn?

Hello :) is anyone else using Los16 Shamu on ATT? 15.1 Worked fine but once I updated to 16 I no longer have have cell service ?. Can anyone suggest proper apn/network settings?

Thank you!

Edit : fastboot flashed the radio and bootloader from OP and now everything works perfectly lol
[Nexus 6  Original Android Development] runekock:
For lineage root, you can try hiding with iSu, https://xdaforums.com/android/apps-games/isu-simple-app-to-deactivate-activate-t3478348/

Magisk should work fine on its own, but remove lineage addonsu first.

Of course, there is still the possibility that your banking app can detect something despite being hidden. But that's a problem for the iSu/Magisk threads.
[Nexus 6  Original Android Development] stonedsun:
Lost IMEI after flashing bootloader and radio

So I flashed the LOS 16 according to their instructions, then I flashed radio and a bootloader from this thread.

Now it's a wifi tablet: OS shows that IMEI is unknown. Bootloader barcodes shows the zeroes IMEI.

I guess I'm going to try now the factory defaults restore from Google images....
[Nexus 6  Original Android Development] Elektroschmock:
Which ROM did you have installed prior installing LineageOS 16.0?

When coming from stock 7.1.1 there is no need to flash bootloader or radio image.

Make shure you really followed our instructions in the wiki and didn't miss any step.

Also make shure those steps were successfull by verifying the console output.

Also make shure you have the right radio image for your provider as there are 3 different ones.
[Nexus 6  Original Android Development] beta1204:
Thank you very much! It works !

I will now try Tasker or Trigger app
[Nexus 6  Original Android Development] chefp:
The IMEI and SIM card were also not functioning on 2 of my Nexus 6's after upgrading to LineageOS 16. One was running LineageOS 14, the other was running stock 6.0.

For both phones, I installed the bootloader, radio and LineageOS 16 as described in the OP. Both resulted in non-operational SIM cards and no IMEI. I found a solution after many hours of experimentation. Stock 7.1.1 must be installed first, and NOT the bootloader / radio when upgrading to Lineage 16.

I started a thread so as to not pollute this one. I replied with the solution after discovering this.

https://xdaforums.com/nexus-6/help/nexus-6-lineageos-16-sim-detected-t3950577
[Nexus 6  Original Android Development] spiral777:
Viper4android

What version of viper4android is everyone using on this rom?
[Nexus 6  Original Android Development] Sanabil:
This version works flawlessly! And has a pretty neat UI.

https://xdaforums.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651/page255
[Nexus 6  Original Android Development] Sanabil:
My Ui and app switching experience is laggy mainly using launcher. Is it because of new renderer? Anyone else experiencing it? Apps them self operate normally.

I am using trebuchet launcher. Could my battery be the issue it is old now.
[Nexus 6  Original Android Development] spiral777:
This is perfect! Thank you so much! :)

The UI is beautiful! Thank you you made my day :)
[Nexus 6  Original Android Development] JaimeZX:
Well... back to not working. I have tried clearing Cache/Davlik three times now, and waiting at least two hours after booting before otherwise touching the phone, and still no working camera. Any further suggestions?
[Nexus 6  Original Android Development] dbrickg:
Make sure your battery is well charged. If mine gets below about 65%, the camera doesn't work ... or, worse, it crashes the whole phone
[Nexus 6  Original Android Development] mrk2815:
had issue had to go back to stock.i want to reinstall lineage 16.do i need to decript before i install lineage or is that not an issue anymore.
[Nexus 6  Original Android Development] githyanki:
Yes, need to decrypt.
[Nexus 6  Original Android Development] mrk2815:
thanks will do so when i have some time.
[Nexus 6  Original Android Development] BootloopedMillennials:
That means the battery is in bad health. Things like the camera have a high draw which causes the battery voltage to drop too low, hence restarting.
[Nexus 6  Original Android Development] mrk2815:
OK. what the best twrp for flashing lineage 16.0. Iis is it 3.2.3 or 3.3.0. justwondering.
[Nexus 6  Original Android Development] dahawthorne:
Why not use the newest? 3.3.1.

https://dl.twrp.me/shamu/
[Nexus 6  Original Android Development] JaimeZX:
Yeah, new battery installed in January. Definitely not the problem.

I've tried the wiping Davlik+Cache+wait minutes-to-hours several more times now, plus installed the latest (31 July) update. Still no camera. Kind of a bummer since I was on a work trip last week and, not having brought a separate camera, I had no way to get pics along the way. :/

Still open to suggestions.

//BREAK BREAK//

For a couple of years I have been using the Proximity Sensor Calibration app to fix the problem of the screen protector making the phone think it's always up to my ear... in the last few weeks though, (since the ~4 July update?) the fix only lasts a few hours as opposed to, well, permanent. Not sure if whatever setting the app is writing to the system is then being over-written with defaults or whatever.

Sounds like I need to figure out how to post logs.
[Nexus 6  Original Android Development] dansblackcat:
This has happened to me several times in the past and I was able to get it working by:

Uninstalling any third party camera apps, leaving only the default LOS camera app.

Clearing Cache and Storage for the LOS camera app.

Restarting the phone.
[Nexus 6  Original Android Development] BootloopedMillennials:
Have you tried Google Camera? I've had no issues with it. Except once in awhile it'll launch but black screen in the viewfinder. Exiting and launching it again, it works. I've disabled the stock LOS camera.

The Google Camera app might be old but it still takes the best pictures on the Nexus 6 because of HDR+.
[Nexus 6  Original Android Development] JaimeZX:
Thanks! I was game to try it. No luck. Stock camera app just crashes out.
[Nexus 6  Original Android Development] p-hil:
I've installed Open Camera from F-Droid and it works, even with stock camera not working.
[Nexus 6  Original Android Development] dvdram:
The camera crash after booting happened to me as well. Then, accidentally, I discovered that the camera would not crash, if I started any GPS app *before* starting the camera app. Is it possible, that the camera crashes because it can't retrieve the positioning data?
[Nexus 6  Original Android Development] dbrickg:
Wow! If that's true, it seems like a really positive find! Can anyone else verify that?
[Nexus 6  Original Android Development] dahawthorne:
It sounds unlikely, maybe coincidental, but in any case that could be discounted simply by switching off the "save location" function.
[Nexus 6  Original Android Development] dvdram:
I can reproduce that behaviour any time, and it doesn't make any difference, if "save location" is activated or not:

- reboot into recovery,

- wipe Cache,

- reboot

- start camera -> crash

- reboot into recovery,

- wipe Cache,

- reboot

- start GPS-Test

- wait a few seconds until position is found

- start camera -> no crash!