yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] vincenzov:
recovery lineage

Hi everyone, I have seen that the file recovery for each lineage version comes with a recovery version.

It doesn't update itself .... I need to update it or not? If yes, do I have to unlock the fastboot every time? (recovery)

Sorry i am italian and i use google translator...
[Nexus 6  Original Android Development] Eazy:
I don't know if this is considered a bug or not...

First I thought I just didn't hear when people called me. So I checked the volume and raised it. Even though I heard the ringtone (the same I always use) when raising the volume (volume was in the middle to begin with) the phone was silence when I got a phone call. When I checked what ringtone I had, it did just show a number instead of the name of the ringtone. I changed the ringtone to something else, and that did the trick. It took a long time to figure this out...

My guess is, when you do the first setup of the phone and choose to restore from google cloud, it will pick the same ringtone you had before even if it is not included in the rom. Strangest thing is I could hear the same old ringtone I always use when changing the ringtone volume. The ringtone I always use is Themos, a standard ringtone from Android Nougat.

Is it in the rom or google this problem is in?

I upgraded to LOS 17.1 from LOS 16 with a clean install (full wipe before I installed LOS 17.1).
[Nexus 6  Original Android Development] maddog3030:
I don't and haven't for maybe 3 updates

if you do an update through the ROMs update utility the recovery does not get updated.

Need to check the changelog to see if any part of the log pertains to the recovery.

last change the recovery (if I remember right) was just moving some menu items around the sub menus.

---------- Post added at 06:10 PM ---------- Previous post was at 06:01 PM ----------

No it's been that way since forever since the original T-Mobile MyTouch when it loses track of the ringtone for whatever reason,

You can recreate it by changing the name on the ringtone.
[Nexus 6  Original Android Development] Dhalsim43:
Pixel launcher was working well with 20200410 build but is no more working with 20200412 build
[Nexus 6  Original Android Development] Newfe:
When i put screen lock to anything it works. If i put it to no lock i get this.

format clean install still does it . Don't know if you can fix this or it is just this phone. Did not do it on version 16.

Thanks for version 17 Works good. other then this problem.\

https://drive.google.com/file/d/1GMdwt8GYOdlzZEzzKgxnKfxSqRCdLdR4/view?usp=sharing

also i see the pixel xl has to same problem.

https://xdaforums.com/showpost.php?p=82261591&postcount=650
[Nexus 6  Original Android Development] SteveYoungs:
I'm very happy to report that Google Pay is working fine.
[Nexus 6  Original Android Development] pinakini:
Hi, how to have more fonts than the available two?
[Nexus 6  Original Android Development] dvdram:
[MENTION=279717]eelco_akker[/MENTION]: I upgraded two days ago following your advise and it worked out perfectly. Thanks for these hints! :)

Until now, I haven't encountered any big problems or bugs. I was pleasantly surprised by the speed of the first boot after flashing. It was nothing compared to former upgrades: it didn't seem to take any longer than flashing just another nightly of the same version. And all my apps kept working! :)

Some thoughts and notices so far:

The dark mode is very nice and handy, and I am looking forward to the day that every (third party) app will support it. (Especially Firefox is a menace in the dark and using an add on like Dark Reader slows down the fox massively.)

One suggestion for dark mode though: it could also be triggered by the light sensor, not just by time of day.

I like the possibility that trusted hardware, like your BT headphone, can now be set to retard the screen lock, but not to automatically unlock the screen. That was a real security lack in former version!

(Talking about BT: I really miss the the possibility for system sounds to be played on the phone's speaker instead of hearing them on my BT headphone while I listen to music, trying to relax...)

Being able to customize the LED colour per app is a real nice thing!

System profiles: I noticed that sometimes when I activate my "at home" profile (wifi activated, screen lock deactivated) the back button and the home button don't work. To make them work again, I have to switch to another profile.

I have not yet found the settings for fading out nav bar and/or status bar. Is this option gone completely in Android 10 or is it just not yet there?

Over all it's a great work and the system works very smoothly. Thanks a lot for the effort!
[Nexus 6  Original Android Development] Sam Nakamura:
Just to confirm and let you know... this doesn't happen on a full wipe, so clean flashing 10 should solve your issue with network!
[Nexus 6  Original Android Development] nhatminh87:
Anyone know how to backup lineage 17; i used TWRP cant restore backup; stop at boot logo
[Nexus 6  Original Android Development] wrsg:
Just to make it clearer what the problem with the Calendar app is, this is how it's looking in 17.1. The top-right usually has the 3-button dropdown menu, which isn't showing here.

Also [MENTION=3383960]Elektroschmock[/MENTION] to give a little more info on the WhatsApp video calling problem, it starts freezing up after around 30 mins of a video call.

I said earlier this happens with group video calls, but now it's also happening on a normal video call to a single other person. It was working fine on LOS 16.0. I also noticed it tends to happen after around 30-40 mins of a video call.
[Nexus 6  Original Android Development] xuxu1:
Yeah, also tried to restore full twrp backup without success. Then I installed current lineageos 17.1 + gapps + magisk and restored only data and its working fine.
[Nexus 6  Original Android Development] McMannes:
Hello, how you solve NFC pay? İt doesnt work on my phone?
[Nexus 6  Original Android Development] xuxu1:
[MENTION=4895778]McMannes[/MENTION] Activate magiskhide in magisk settings. Press hide magiskmanager in magisk settings. And then add Google pay to magiskhide.
[Nexus 6  Original Android Development] alfacrux:
The LineageOS 17.1 Calendar app is now more likely a calendar viewer not a full-functional calendar application. Alternative is to stay on LOS 16.0 or use another calendar application with event creation/editing capability...
[Nexus 6  Original Android Development] wrsg:
I doubt that very much. It's completely absurd to downgrade an essential part of the system and not inform people in advance.
[Nexus 6  Original Android Development] alfacrux:
Read youself:

https://www.reddit.com/r/LineageOS/comments/fygkxn/calendar_lineageos_17/fn2vcfu?utm_source=share&utm_medium=web2x
[Nexus 6  Original Android Development] wrsg:
Thanks for the link. That is really disappointing. I think I'm going to put 16.0 back.
[Nexus 6  Original Android Development] zapjb:
And how. Calendar is pretty essential for most.
[Nexus 6  Original Android Development] Eazy:
Why don't you just install a calendar app from Google Play?
[Nexus 6  Original Android Development] wrsg:
I know I could, but it's also the WhatsApp video calls freezing up after 30 mins.
[Nexus 6  Original Android Development] githyanki:
I wonder how people expect things to get fixed if they won't submit a log of the issue?
[Nexus 6  Original Android Development] wrsg:
Yes, that's true. I'll be on the call later so I'll grab a logcat then.
[Nexus 6  Original Android Development] alfacrux:
Actually - that's probably the intention of Google when stripping down the AOSP calendar app. But if you install gapps, then the logical way is to install Google calendar anyway. If you like to keep your system as FOSS as possible, then a good calendar app is ETAR Calendar from F-droid repository. The stripped down original LineageOS calendar app could be disabled in settings if needed...
[Nexus 6  Original Android Development] wrsg:
I guess this would be a good time to mention that when running Bromite (a chromium-fork browser) 81.0.4044.97, the GPS/location icon in the top bar keeps switching on and off. I'll also be grabbing a logcat of this, but I'll do the Whatsapp video call one first as that one is bit more disruptive than this.
[Nexus 6  Original Android Development] Elektroschmock:
Missing camera app

If someone is experiencing the missing camera icon problem , but other cameras are still working- can you please check something for me?

- go to setting / Apps and notifications

- tap 'See all ?? apps'

- select 'Disabled apps' from the dropdown menu

- if camera is on that list enable it

Please tell me if that worked for you
[Nexus 6  Original Android Development] skbhere:
I have the missing camera app issue. I just checked the camera app isn't disabled, and you can't disable it as well since the option is greyed out. I tried force stopping and rebooting but nothing seems to work. I'm on the April 12th nightly build currently and had these issues in the previous nightlies as well.
[Nexus 6  Original Android Development] ivanperezcaro:
The camera app is there, but I can't enable it.
[Nexus 6  Original Android Development] wrsg:
Could someone please recommend a logcat app that works well with Android 10? I'm using Logcat Reader (the first result on the Play Store), but it's really slow to save a log. Its actually still saving after like 10 mins. The one I usually use (the one with the cat logo) said it doesn't fully support Android 10.
[Nexus 6  Original Android Development] Strephon Alkhalikoi:
I use Logcat Extreme without problems.
[Nexus 6  Original Android Development] maddog3030:
The camera does work if you use any app that can generate a shortcut on the desktop.
[Nexus 6  Original Android Development] joeweeks:
I am no power user but do have a spare N6 to try different solutions. with the 04/14 release installed I have no camera icon. I dl the google camera from the play store and it worked fine. Today updated to the 04/15 release and the downloaded camera would not work. Uninstalled it. In setting APPS it show the original app but cannot get it to run. Happy to help where I can. Like I said this is a spare N6 it is ATT branded but unlocked however I have no SIM to test with.
[Nexus 6  Original Android Development] JaimeZX:
With fingers crossed, I dirty-flashed 17.1 + GAPPS over 16.0 in TWRP. Trebuchet kept crashing. Flashed the 17.1 nightly again in TWRP, and all seems fine!

Bonus - Footj camera works now! (It conflicted with 16.0 on my phone; if it was even installed then no camera apps would work period.)

So. That upgrade was much easier than I anticipated.
[Nexus 6  Original Android Development] dansblackcat:
Upgraded from 16 to 17.1. Is it right that I now see LTE where I used to see 4G?
[Nexus 6  Original Android Development] maddog3030:
1) install the Google camera.

2) power down the phone.

3) wait a good minute before turning it back on.

4) after you turn it back on before the phone finishes booting as soon as you can get lock screen open launch the camera.

This has worked for me a hundred percent of the time.

maybe I've been lucky and got the sequence down correctly every time but it does fix it.

given time it might break it again but I repeat the process and it gets it back up and running.

best guess here is there's a memory leak that happens post boot that's affecting the camera registers but if you can launch the app before this event occurs the camera does work.
[Nexus 6  Original Android Development] SteveYoungs:
All cameras (Google, AOSP, Open Camera) are working fine for me. They always have.
[Nexus 6  Original Android Development] alfacrux:
I have always had problems with camera. Usually it survived the nightlies updates but sometimes needed a reboot or two to get it to work.

Now I did a clean flash of lineage-17.1-20200414-nightly-shamu-signed.zip with the same dated LOS recovery. (No gapps always.) Camera worked OK.

Did an OTA update to 17.1-20200415 -> camera icon exists but camera app crashes. Did an OTA update to 17.1-20200416 -> no change, camera app crashes.

Tried a clean flash of lineage-17.1-20200416-nightly-shamu-signed.zip -> no camera icon. Now also clean flash of lineage-17.1-20200414-nightly-shamu-signed.zip did not help - still no camera icon.

Reverted to LineageOS 16 by clean flash - camera icon is present and camera is working :)
[Nexus 6  Original Android Development] pinakini:
I am facing the problem of illegible text in aosp keyboard & aosp messages app and some non stock apps (Sony music etc.) When dark mode is enabled.
[Nexus 6  Original Android Development] mahir555:
When the phone is off the charger it works great , but as soon as the charger plugged in i experience a massive lag in all actions , phone became a pain to use especially ehile using 2 apps simultaneously such as a voip call and Twitter . Also phone temp rises quickly.

Am using the original charger.

Does anyone experience this ?
[Nexus 6  Original Android Development] hamed_a12:
Echo, Camera and flashlight issues

Hello this Rom is great but I have two problems with it

1 echo issue in calls like WhatsApp and Skype

They hear their voices.

I had this problem from 16 version of Lineage os

2 my camera and flashlight stopped

Sometimes they stop working

This one appeared from 17.1

I have tried to restart, shot down, update Rom, wipe cash partition...

I did not find the problem and the solution but sometimes camera is ok mostly not.

I don't want to change this advantageous OS so I need to solve these issues. Thanks
[Nexus 6  Original Android Development] mahir555:
This is a general problem with different ways for temporary fixation.

For me i use an app called " kill camera " from the store . It needs root. I kill the camera process then re-lunch it , works perfectly.
[Nexus 6  Original Android Development] lazloe:
Currently also having issue with camera crashing instantly. I was able to get a logcat of the process, but am not entirely sure if it has the best collection of data needed. These are the logs of only the apps themselves. I logged the stock app and the Google app. They are, fortunately, short, and attached.
[Nexus 6  Original Android Development] Elektroschmock:
Okay thank you everybody for the reports and workarounds for the non-working camera.

Right now I don't need more reports. I am able to reproduce it on one of my shamus.

I'm tracking the bug down since a week, but the whole camera system is quite complicated as you can see here:

https://source.android.com/devices/camera

If your camera is crashing could you please set the power profile to 'high performance', reboot ans report if it fixes the camera/flash?

(Note this won't bring back the missing icon)

At least on my device it fixes the issue. I already have a patch that disables mpdecision and only starts it when the boot is complete.

This way no cores get hotplugged during boot. But I am not shure if it works on all devices.
[Nexus 6  Original Android Development] Babouchnikov:
Thank you for your work, this is already awesome.

It didn't work for me...
[Nexus 6  Original Android Development] pinakini:
Any body spoke on call while connected in car Bluetooth? I am receiving calls but the call is not heared on both ways after connecting. I didn't have this problem on los 16.

---------- Post added at 10:39 AM ---------- Previous post was at 10:35 AM ----------

No. It did not work. But soft reboot is instantaneous.

Many big thanks
[Nexus 6  Original Android Development] Smeagol1375:
I have had the camera issues like others. I tried a bunch of suggestions from this forum with no success. I tried other camera apps from the play store. What worked for me was, if you have root access (I flashed Magisk Manager) then you can completely uninstall the Stock Camera app (I used Titanium). Then any other camera and flashlight app seems to work.
[Nexus 6  Original Android Development] Uplander:
Same situation by using magisk debloat module to "uninstall" stock camera then normal installation of google camera app . All functions working including flashlight, no issues at all so far.

Excellent rom many thanks to the developer.
[Nexus 6  Original Android Development] Smeagol1375:
Agreed, the ROM is very solid. It has been a while since I have ROMed a device, this is awesome!!
[Nexus 6  Original Android Development] Sam Nakamura:
Not had a single issue with Camera even once, having stock and Google camera running, I however cranked up performance in battery settings from the day I clean flashed lineageOS 17.1, if this makes a difference...

Just wanted to give a short feedback regarding lineageOS recovery which I finally flashed via TWRP using the img option and it so far works beautifully and keeps patching the kernel with Magisk when applying a OTA via lineageOS updater, so addon.d support works - it also seems possible to flash zips when they're unsigned but I haven't tried yet and cannot say to which extent, like I don't know if flashing Magisk from recovery would work or flashing Magisk modules - I however felt quite some lag in the recovery UI when using touch controls, not a deal breaker at all but lag is noticable!

Anyway... Very satisfying the Q experience on Shamu - definitely much love from my side!!! :highfive:
[Nexus 6  Original Android Development] Luny Lennon:
I installed old Google Camera and work fine
[Nexus 6  Original Android Development] zapjb:
Do you mean you flashed Lineage OS Recovery from TWRP & it replaced TWRP & left only Lineage OS Recovery?

And that flashing Magisk from Lineage OS Recovery is unknown if it works?

Was the lag in the recovery UI from Lineage OS Recovery or TWRP?

Thank you.
[Nexus 6  Original Android Development] maddog3030:
Disableling MPdecision fixed the camera problem for me.
[Nexus 6  Original Android Development] xdajacob:
Almost everything is working but the camera is broken.
[Nexus 6  Original Android Development] wavedashdoc:
Not helpful. Already known.

Please post logs to continue to support issue tracking.
[Nexus 6  Original Android Development] lazloe:
I have just updated to the April 17 nightly and it appears, thus far, that my camera is working again.

:fingers-crossed:
[Nexus 6  Original Android Development] Sam Nakamura:
Exactly, I replaced TWRP with lineageOS recovery as suggested by the lineageOS team by using TWRP's 'flash Image function' and re-booted back to recovery which then was of course lineageOS recovery...

Magisk is at least kept when updating lineageOS, if a fist flash Magisk would work I don't know, maybe the inconvenience could be on first installment needing a PC, we'll see..

The lag is in lineageOS recovery's UI but actually nothing to worry, it's only noticable!

---------- Post added at 08:42 AM ---------- Previous post was at 08:36 AM ----------

And not universally true either, it works very well for me, documented a trip in the nature with daughter yesterday, did 200 pics in 90 minutes and had zero issues, using Google camera... Never had the issues even once!

Edit: stock cam works as well for me
[Nexus 6  Original Android Development] skbhere:
Amoled dark mode

Is there a way to turn black(amoled) dark mode on? Like if you turn dark mode on in los 17.1, the settings app is in grey theme(even like the volume expander is grey), which I do not prefer. I loved the los 16 option to just turn it all black. How can that be achieved? Any chance it'll be added in future builds?
[Nexus 6  Original Android Development] Eazy:
I don't know if this is a thing with Android 10 or with LOS 17.1. I use Timely. The Alarm clock function works OK, but the Timer does not. If I set the timer and the phone turns of screen, when the time ends there is no sound and the screen does not turn on. I tried other timers on Google play and some of them have alarms sounds, but none of them turn the screen on. Is that a permission problem perhaps? I have given all permissions to the app I could find it needed.

(Yes I could use the built in timer and alarm clock, but i like Timely very much.)

Edit:

Looks like the Timely alarm clock function does not turn on the screen either...

Could I perhaps solve this by moving Timely to system, and how could I do this safely?

I know there are apps on Google play to do this but I'm unsure if they work with Android 10.

Edit2:

Moved Timely to system, but did not help :/ Have mailed developer of Timely, but don't imagine they will answer...

the reason seems to be this. OK Google!
[Nexus 6  Original Android Development] dvdram:
There seems to be a small problem concerning system profiles: I set up a profile "@home", in which wifi is turned on and screen lock is deactivated. The standard profile, in which the screen is locked after half a minute, is set to activate when my phone disconnects from my home wifi. That setting works perfectly when I leave my flat, but I noticed that my phone switches to standard profile, even it's in constant line of sight to the wifi router and not being moved at all.

I did not notice this behaviour in LOS 16. Is this some new intended feature?
[Nexus 6  Original Android Development] pinakini:
I could not get the bluetooth calling going with whatever I did within my ignorable knowledge. So went back to LOS 16.0. Hope to catch up soon. Thanks.
[Nexus 6  Original Android Development] Sam Nakamura:
Just tested calling via Bluetooth headphones out of curiosity and because I had them on already and it works beautifully, could hear the person who I called and I was heard as well - in such cases where you think you experience a obvious flaw it's absolutely helpful to get logs while testing and experiencing the issue, either a logcat or the standard Android debugging bridge on your PC can be used...

Usually reports without logs will get ignored totally as they offer nothing to really investigate on!
[Nexus 6  Original Android Development] TotalChen:
I tried every pieces of advice mentioned in shamu-related posts to solve the camera problem, but made no difference, including applying latest commit in the gerrit building an unofficial rom to test about holding back mpdecision.

Something I can reproduce is rebooting from TWRP, boot menu, even bootloader, will mostly trigger the problem, when the system is up, draw the QS menu, can see the flash torch icon is grey, never get enabled again. That indicates the camera surely FC and won't work.

LONG PRESS power button for about 10s to cold reboot the phone, after system up, the flash torch icon keep grey for one second or two and then turn into enabled, then the camera get available, EVERY TIME, NOTHING ELSE I have to do.

Anyone who has the phone can try, however, I can't find any useful information in logcat and kmsg. Hope this will help.
[Nexus 6  Original Android Development] zapjb:
https://xdaforums.com/nexus-6/development/aosip-8-1-official-t3801408/page80

Post# 800

P.S. I've read some people are having troubles with their camera. I'm using Camera NX_com.google.android.GoogleCameraNX1 & it works well for me. I have the APK it's 25MB. If somebody in charge will let me know how to make this available I'd be glad to do so.
[Nexus 6  Original Android Development] TotalChen:
I'm using 32bit Google Camera 4.2.035, facing the same situation no matter which 3rd party camera apps. When flash torch is unavailable, the camera is neither.
[Nexus 6  Original Android Development] zapjb:
I am using a different ROM AOSiP 8.1. All I know I was having many problems with the camera app. Then I used the specific apk I mentioned & all is well.
[Nexus 6  Original Android Development] Elektroschmock:
This bug has nothing to do with the camera app used.

It's the timing of the camera hal, the cameraserver and the camerea deamon. If the don't come up with the right timing. No camera app can use the camera hardware or the torch.

If this happens on the first boot Snap (Lineage's camera app) removes it's icon from the launcher.

It will never come back at any following boot even if the services come up right.

Thats why many users think its app dependant.