yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] wrsg:
I have a bug related to the voice call audio failing on the 1st attempt receiving/making a call after a long sleep period (the 2nd time you receive/attempt works fine).

This is a problem because any time someone calls me after the phone has been in standby/sleep for hours, it always fails. It's similar to the bug that happened recently where no audio was going through.

Can you help me solve this please? [MENTION=3383960]Elektroschmock[/MENTION]
[Nexus 6  Original Android Development] Elektroschmock:
Are you able to catch a log?
[Nexus 6  Original Android Development] bipe@88av.net:
I have an issue at fresh install. I got a new nexus 6 and first i flashed the last nexus 6 factory image from google by running flash-all.sh to get latest baseband and bootloader (the one from dez 2018).

Then i installed latest twrp from the twrp website with fastboot.

In twrp i wiped all and copied the LineageOS 16 nightly file. Then i installed it like always. But at first boot i got asked to enter a encryption passwort. The phone was completely wiped before. That did not made any sense.

Then i installed older nightly (few days older). There i had the same issue.

Then i installed LineageOS 15.1 without any issues. It worked perfectly fine. Afterwards i boot again into twrp, wiped, installed lineageOS 16. I got asked again at first boot for a never set encryption password.

Have someone any ideas about that?

EDIT:

I have installed LineageOS 15.1 once and then enabled the encryption to 0000. Then i disabled the encryption again. Wiped everything and installed LineageOS 16. The phone asked me for encryption password (why? i wiped the phone before). I then entered 0000. The phone accepted 0000 and told me that the phone have to be wiped because my data were broken. I accepted that. Then the prone reboot into twrp, wipe something, boot again. Sadly i got again the requirement to enter the 0000 pin. Then the same error with broken data and the question if i want to wipe.

How can i get out of this situation? I cant get a working LineageOS 16 on the phone.
[Nexus 6  Original Android Development] githyanki:
Wiping is not enough, you need to format data. That option is under advanced wipe.
[Nexus 6  Original Android Development] bipe@88av.net:
Thanks! I have overseen this button. I always wiped every single partition (system, data, cache,... ) but never tried the button "format data" next to it.

I used latest TWRP 3.3.1 and everything works now like it should.
[Nexus 6  Original Android Development] nilesh0205:
Hi all / [MENTION=3383960]Elektroschmock[/MENTION] ,

I had changed battery of my Shamu 2 months back, and I was continuously getting around 3 hours of SOT in a day till last Thurseday and used to shut down around 2-3% when reached. Suddenly from Friday Phone started shutting down around 40% and wont restart back.

And from Yesterday it got worse, it will shut down anytime when reached below 80% (in just 1 hour it reaches 80 % and that too when its on aeroplane mode most of the time). but it restarts and keeps rebooting every few minutes, making phone nearly unusable. and between restarts battery % sometimes drops and sometimes magically goes up but unable to use much.

And then completely shutdown around 20% now.

Now total screen on time I am getting is not much than 20 odd minuted. What might have causing these issues? I have not updated to any latest nightly after I think 10th September. Is this battery problem (Its New :( ) or something else entirely? How do I find out? How do I get logs if someone can look at them?

BTW I tried to wipe Dalvic / ART Cache from recovery and Cache it didn't help. Also I tried the boot logger logs method which was discussed on other topics as well which didn't helped as well.

Thanks in advance for your help
[Nexus 6  Original Android Development] Elektroschmock:
Are you shure this is a quality battery? 3 h SOT is pretty bad.

If your problem persists after a clean install I'd guess your battery is faulty.
[Nexus 6  Original Android Development] nilesh0205:
Thank you Elektroschmock for replying.

The battery looked exactly the same as original battery. also at the start the SOT was around 4 hours. I will try clean install and let you know

Thanks,

Nilesh
[Nexus 6  Original Android Development] Elektroschmock:
I prefer batteries not claiming beeing an original.

Usually manufacturers of those fake OEM batteries cram the cheapest stuff into them, because the can only compete through the price.
[Nexus 6  Original Android Development] Eazy:
Trying to install this I get a bootloop Have not read up how to install and installed it as i always do, buy flashing from twrp. As I'm already is decrypted so did not format data but I did wipe all other partitions. Can this only be installed through ADB or what did I do wrong?
[Nexus 6  Original Android Development] githyanki:
May be gapps, they have has some issues the last few days. Last good build is from the 9th I think, check the gapps thread.

https://xdaforums.com/android/software/pa-gapps-continuation-t3098071/page626
[Nexus 6  Original Android Development] Eazy:
It was Gapps. Had an older version (Open Gapps nano) already downloaded on the phone. The ROM seems to be working fine.

I only miss one feature that I have had on all ROM's I've been using. Date in the status bar. Is there any way to get that on this ROM? I know there is different apps on Google Play that shows the date with an icon, but that is not what I'm after. I would like to have it likes this "Clock Date" (13:31 12 October). This is availible on most ROMS. there is no add on or something I can flash?
[Nexus 6  Original Android Development] nl1010:
Hey! Nice ROMs, these Lineage OS 16.0 and 15.1, thanks for all hard work!

But, can we expect a Lineage OS 17.0 development for the Nexus 6?

That will be really great!
[Nexus 6  Original Android Development] Elektroschmock:
I am already working on LineageOS 17.0, but that doesn't necessarily mean that I am ever going to ship it.
[Nexus 6  Original Android Development] Eazy:
Does the Audiofx EQ work when using bluetooth? It is working on speakers but not when I use bluetooth in my car.
[Nexus 6  Original Android Development] Sanabil:
Pixel 4 just launched, and i am using lineage on n6. Great work keeping it alive. Let's see if n6 can make it to 2020.:good::)
[Nexus 6  Original Android Development] dbrickg:
At least!!! I'm hoping to see it continue till 2030 ... and beyond! :)
[Nexus 6  Original Android Development] Sanabil:
:good::laugh:
[Nexus 6  Original Android Development] kanecreek:
Deleted
[Nexus 6  Original Android Development] AmirHRC:
We have one of the best contributors on lineage os [MENTION=3383960]Elektroschmock[/MENTION] (Kim Le) thanks sir for making this device awesome

I tried many lineage os custom rom on deferent phones like oneplus 3t but i found that shamu run faster that because of your work sir so thank you for making new life to this device and looking forward to your lineage os 17 for shamu ??
[Nexus 6  Original Android Development] McMannes:
Hello friends, i have twrp, and telephone all wiped. it is just have loading files. but i cant load radio-shamu-d4.01-9625-05.45+fsg-9625-02.117.img, i cant use fastboot commands, and twrp install says "size of image is larger than target device". how can i solve
[Nexus 6  Original Android Development] dahawthorne:
As a first step I suggest that you get your Nexus working again by using TWRP to sideload the full Google factory image:

https://developers.google.com/android/ota#shamu

That includes the radio, and from there you can wipe and install a new ROM.

Or you could extract the radio image from the full image and flash it in TWRP:

https://developers.google.com/android/images
[Nexus 6  Original Android Development] McMannes:
i load the factory image. after loading twrp, it looks password problem. and i formatted data but problem is goes on. now no password problem but the phone didnot open on lineages os
[Nexus 6  Original Android Development] dahawthorne:
Did you try loading the OTA? It was the method I used for many months to install a fresh copy of Android. It's very simple if you have TWRP (use the latest 3.3.1 from https://twrp.me/motorola/motorolanexus6.html), Advanced/Sideload, then follow the instructions at the top of the Google OTA page. It's simple and fast and you should have a working phone which you can then upgrade to a new ROM.
[Nexus 6  Original Android Development] McMannes:
i dont understand what is the problem? i load this rom many many times. i always do wipe everything on twrp. after copy rom files. and install it, but this time i'm dealing with nonsense problems.

and there is no problem stock 7.1.1 and lineage 15.1 but lineage 16 is problem
[Nexus 6  Original Android Development] dbrickg:
I'm not sure, but I think you need to "format /system", too, in order to switch from 15.1 to 16.0. See the quote above

PS: but now that I search through this thread, I can't find the instructions to format /system. I thought for sure I'd seen that somewhere, but now I'm not seeing it at all. And I can't find it in twrp anywhere either. I guess I was misremembering something. Sorry about that
[Nexus 6  Original Android Development] runekock:
I agree that wiping system (which does format - only wipe data doesn't) is a good idea when changing roms.

Gapps and some other add-ons include survival scripts that run unless system gets wiped. And you don't want the wrong gapps to survive.
[Nexus 6  Original Android Development] dahawthorne:
Are you sure? When I flash the Gapps packages part of their output script shows "Removing previous Gapps".
[Nexus 6  Original Android Development] runekock:
Indeed. The old gapps survives flashing the new rom, but should be removed file-by-file by the new gapps. Still, I don't trust that to work perfectly between versions.
[Nexus 6  Original Android Development] dahawthorne:
Sabes que tienes que escribir en ingles, verdad? Puedes utilizar Google para traducir.

You know you have to write in English, right? You can use Google Translate.
[Nexus 6  Original Android Development] dwardo:
Elektroschmock, you wouldn't happen to have the various WeatherPovider apks compiled for 16.0 ?
[Nexus 6  Original Android Development] BootloopedMillennials:
Not seeing that issue, clicking wallpapers brings up Complete Action using Wallpapers or No Wallpaper. Maybe check permissions of Trebuchet.
[Nexus 6  Original Android Development] dvdram:
I am not sure about that: on my N6 I see two contradicting settings:

1. Settings -> Security -> Trust -> Encoding: deactivated

2. Settings -> Security -> Encoding & Login: Smartphone encoded

(Sorry, if those are not the correct options, but my phone is set to German and I translated it back to English by guess and by gosh.)

So, one options tells me that the phone is encrypted, the other option tells me that it is not encrypted. Strange...

There are two PINS in use: one for the SIM card, and one for the screen lock. Both pins are requested when LOS 15.1 starts, but none of them is required by TWRP to browse, rename or delete any file on the internal storage or data partition. So I guess that means that the phone is not encrypted, doesn't it?

But still, after installing LOS 16, following the instructions very closely, I got the same error: password is correct, but data seems corrupted. The strangest thing there: no matter what I enter, it always says that the password is correct, even if I just enter rubbish.

How can LOS verify the entered password to be correct, if I just enter some random characters?? :confused:

My personal data and options are NOT stored on Google, for obvious reasons. So, how can I install LOS 16 without having to reset the phone and loosing my data?
[Nexus 6  Original Android Development] tong6998:
This worked extremely well for me, skipped Magisk for not needing it, and used open gapps stock.

Only issue I have is that when the phone hits 60% battery, it powers off, and does that every even % number after that (50, 40,.....) But only on the even numbers. (Ending in 0).

********EDIT: DID NOT WORK, this "dirty flash" caused tons of reboots into recovery ****** check later in thread.
[Nexus 6  Original Android Development] SubwayJrd:
From all the other posts in this thread (and the 15.1 thread) your battery appears to be dying.
[Nexus 6  Original Android Development] tong6998:
Wouldn't disagree, however, it never once did that in 15.1 which makes me question it.... if it keeps happening, I'm going back to 15.1, but weird thing is that it only happens on when the percentage goes to *0%, wouldn't it shut down if the battery was bad at any % amount?
[Nexus 6  Original Android Development] dvdram:
No, it still does not work. :( LOS still asks for a password, even after I deleted the lock screen PIN before flashing LOS 16 and even when I remove the SIM card. So there is definitely no reason at all why LOS should ask for a password, and even more, there are even less reasons why it should declare any random characters to be the correct password!
[Nexus 6  Original Android Development] tong6998:
Mine was unencrypted with a simple pattern lock screen. Kept all my apps and settings and all, just updated them.
[Nexus 6  Original Android Development] githyanki:
If your encrypted and did not set a password, it uses a default password.

Backup using Titanium backup.

You can copy data to and from your computer in TWRP before and after doing the format, so copy everything of phone, format, reboot and put it back.

Install 16 and setup. Restore apps and data from Titanium. Do not do any system apps.
[Nexus 6  Original Android Development] dvdram:
That sounds like a very, very silly idea in the first place. Why should LOS use a password, that does not need to be entered and thus be veryfied? Anyone who owns more than two brain cells and who is able to turn on the device by pushing the power button will also be able to access the data.

And still the question remains, why LOS verifies any characters entered to be the correct password. That should not happen.
[Nexus 6  Original Android Development] TamCore:
If you don't set a password by yourself, Android (not LineageOS) uses "default_password" as the default password. Also, it should be noted, how the encryption works under the hood. Even though the password is "default_password", that's just the password that's used to unlock the master key, which then is used for encryption. So, if would just wipe the sectors holding the master key of your data, even knowledge of the default password, won't help you at all. Hope that wasn't too confusing :D

---

Coming from official LineageOS 15.1, wiped /system and flashed 16.0 + OpenGapps. Ended up being asked for the password. As I have nothing set myself, tried "default_password", but that didn't work either. Ended up restoring my TWRP backup. Setting up everything from scratch, fiddling around with "adb backup" or TitaniumBackup is not an option for me - no time for that.
[Nexus 6  Original Android Development] dvdram:
Somehow LOS 16 must be able to access the data after the installation, because when it asks for the password it also displays the owner's information that have been entered in LOS 15.1 settings.

It seems there is something very strange going on, not working as it is supposed to work. I think it's better to wait for LOS 16.1 to use, hopefully this issue is cleaned by then. And it also would be a very great relieve if LOS 16.x could be installed as a normal update, using "system settings -> LOS -> update".
[Nexus 6  Original Android Development] BootloopedMillennials:
You were asked for a password unencrypted or did you encrypt on 15.1 and not setup a password?
[Nexus 6  Original Android Development] TamCore:
My LineageOS 15.1 setup is encrypted using "default_password", the way Android does it by default. So, I didn't put in a passphrase myself and I didn't fiddle with any of those disable-forceencryption-hacks either. So in my case, LineageOS 16.0 seemed to be unable to decrypt my data, using the default password which is hardcoded in the source code.
[Nexus 6  Original Android Development] tong6998:
No offense or nothing, but there's like a few posts here stating that it does NOT work with encrypted... So why do it if others are stating that and are having problems???
[Nexus 6  Original Android Development] TamCore:
Might be, because I already did it yesterday, shortly after 16.0 was announced. I would bet, at that time, there weren't many complaints about problems in this thread ;)
[Nexus 6  Original Android Development] JaimeZX:
And you did Format /Data in TWRP before flashing LOS & GAPPS?
[Nexus 6  Original Android Development] ProBird79:
Wow, LOS 16 is a nice surprise! I saw someone else ask this question but nobody responded. What is IMS and how do we know if we need it or not?
[Nexus 6  Original Android Development] magnamentis:
Este foro es solo en inglés, por lo tanto, tendrías que cambiar al inglés para usarlo y beneficiar.

this forum is english only hence you'd have to switch to english to make use of it
[Nexus 6  Original Android Development] dbrickg:
Aha! Thanks for that clarification!
[Nexus 6  Original Android Development] def1003:
Elektroschmock i cannot thank you enough for your work you sir are a legend
[Nexus 6  Original Android Development] mezerr:
Is there an issue with TWRP flashing Lineage these days? Not sure if I missed something.

1) Clean latest LOS16 with TWRP 3.3.1, and stuck on boot animation for 5 minutes, then reboots to TWRP

2) Flashed Lineage Recovery, and then clean flashed latest LOS16, and it worked fine.

3) Just for testing, flashed TWRP 3.2.1 (as the instructions say), and clean flashed latest LOS16, and stuck on boot animation for 5 minutes, then reboots to TWRP

4) Back to Lineage Recovery, and working fine.

I usually Clean flash once a month, and never had troubles with TWRP until recently.
[Nexus 6  Original Android Development] jdranzer:
It seems to be a issue in recent TWRP images that might fall into bootloop if you select to install TWRP as a system app. Try again avoiding that TWRP app installation.
[Nexus 6  Original Android Development] Elektroschmock:
Yes we are enforcing apps' privileged permissions and if you add a system app it won't boot
[Nexus 6  Original Android Development] mezerr:
Gotcha. That's exactly what it is. Thanks all!
[Nexus 6  Original Android Development] McMannes:
There was no such problem before, we were able to load without any problems, I tried a lot last week, I even wrote here, but I did not get a correct answer, so that is the problem, I think this should be added to the first post. because I spent hours in vain
[Nexus 6  Original Android Development] ChargedPikachu:
Yeah is strange and it took me 1 hour to figure it out :D i wasnt able to understand why it fails since am new to the the custom rom and specialy the lineageos family .Today there is an update that am downloading as we speak my question is this, the flashlight is not working if the update doesn't fix it has anyone come across this prob? and if he/she can tell me how to resolve it will be awesome .Also if someone has the .so file or whatever is needed to active the high frame rate recording (60fps) or slow mo (120fps) kindly share it with me

Update:After the last update the flash light works fine ! now if someone guides me to this crisp hfr will be awesome...
[Nexus 6  Original Android Development] Elektroschmock:
It's not a bug. Enforcing priviledged permissions is working as intended. I wasn't aware that anyone installs the TWRP app as system app. But honestly the install tutorial never said that you should do that.

Anyway I added an info to the first post.
[Nexus 6  Original Android Development] Nixx7:
Any chance of lineage OS 17 for Nexus 6 ?

Just want to know is there any development going on ?
[Nexus 6  Original Android Development] githyanki:
Lineage official takes a lot longer to update to new versions. You will find a lot of android 10 ROM's son enough, then some unofficial lineage 17 builds, and eventually official lineage 17.

In other words, look in the threads for other ROMs for progress.

Bliss and havoc have had a few comments from their developers.
[Nexus 6  Original Android Development] dbrickg:
Nixx7: see electroschmock's post from 3 weeks ago above
[Nexus 6  Original Android Development] Nixx7:
Thanks buddy. Really appreciate the developers!
[Nexus 6  Original Android Development] Elektroschmock:
Yes I am porting android 10 to shamu. But as stated before there could be some problems which could block an official release.

Right now everything works so far except:

* de- /encryption

* seamless upgrade from 16.0

I wouldn't that say that we take longer - it's just that we have higher standards. ;)

I don't know how Bliss or Havoc people could know anything about shamu's current development status, as they only take the code I have already pushed to LineageOS's gerrit.

AFAIK there is no development from their side - so here would be the best place to ask.
[Nexus 6  Original Android Development] Sanabil:
Noice ?. Can't thank you enough ❤️
[Nexus 6  Original Android Development] Ta3miyyasandwich:
Goes without saying but thanks for breathing life into this device, at the expense of your personal time, and for those exacting standards for rom development. Plus we all know the moment you release it early is the moment people start complaining left and right about bugs :eek:
[Nexus 6  Original Android Development] wavedashdoc:
It's these kind of comments that deter developers from working, in their free time, to support a 5 year old device.

If you'd like to contribute, Android is open source and the code is there for manipulating ? I once was a user, but I took a year to learn how to work with GitHub, WSL and Linux to build a ROM with the help and support of some great devs in my free time and theirs.

XDA by developers for developers. Just saying.
[Nexus 6  Original Android Development] dahawthorne:
Was that aimed at [MENTION=1631192]githyanki[/MENTION] or at the person to whom he was replying? I read githyanki's comment as a positive, trying to direct the OP to other ROM threads where he may see some Android 10 news. I certainly didn't read it as a criticism of delays with LineageOS.

Quality takes time. I should set that as my sig... :)
[Nexus 6  Original Android Development] githyanki:
Thanks David! I certainly think Elektroschmock has seen much worse comments than what you seem to be reading into mine, but to clarify:

Other ROM's will be putting out alpha or beta quality builds soon enough. The Developers of those roms are putting out some updates of their status as such already. I did not know that they were not contributing back to Lineage, and am disappointed to hear that from Elektroschmock. Official Lineage has several criteria that needs to be met before they will allow a ROM to be "Officially" maintained, and even Elektroschmock is not sure if/when that will happen. So, as I stated, you will see other ROM's put out some android 10 builds, then when Elektroschmock may put out a Unofficial LOS 17, and hopefully we end up with a Official LOS 17 build.

I was pleased to see a update from Elektroschmock about LOS 17 progress, I was not expecting to see anything like that from him till closer to a possible "Ship" date.

I would like to claim English is not my first language for any misunderstanding, but sadly it is just my weak grasp of English that leads to my poor communication skills. If you still find something wrong with my opinion (and this is all just my opinion) please PM me to discuss.
[Nexus 6  Original Android Development] hasitCN:
Don‘t give up，thanks
[Nexus 6  Original Android Development] wrsg:
[MENTION=3383960]Elektroschmock[/MENTION] If you do release 17.0, would it only be after an official announcement from the LOS organization, or would you do so regardless?
[Nexus 6  Original Android Development] Elektroschmock:
I didn't even think about that, because right now it's not even shure that there will be LineageOS 17.0 for shamu.

But I guess I don't distribute anything other then official builds.