yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Elektroschmock:
Sorry, I didn't ignore your question, but I first had to check.

It's kind of hard to imagine how a blind person would do it if you can see.

If you have Lineage recovery installed and are able to boot into recovery do the following steps:

Press the Volume Down button 1 time

Press the power button two times

You are now in the adb apply update mode.

There you can install all the zip files you want. I guess you script does the rebooting to system itself.

If you need further help just ask.
[Nexus 6  Original Android Development] s_dino:
[MENTION=3383960]Elektroschmock[/MENTION]

Thanks for your hard work!

I have two questions, if lineage recovery wipe the internal storage every time when I wipe the data or system? and when I flash the boot animation it seems not work. May you give some suggestion? Thank you!
[Nexus 6  Original Android Development] Elektroschmock:
The recovery doesn't do anything on it's own. If you want to wipe any partition you need to select the corrosponding entry in the recovery.

I don't know about which bootanimation you are talking about. Do you mean the bootloader?

Before you flash bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one.
[Nexus 6  Original Android Development] s_dino:
In TWRP I can select only wipe data/cache/system, the internal storage can be retained. The lineage recovery haven't the "wipe internal storage" option, so how can I wipe the data/system and keep the internal storage at the same time? Do I need to update the recovery version when I update the system daily build?

I mean I want use the google original boot animation to replace the lineage boot animation, but not success.
[Nexus 6  Original Android Development] runekock:
I noticed this: "disable audio rotation tracking"

https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/272403

Is that the end of stereo sound in landscape? (Of course if that is necessary to fix the loss of sound in calls, it is totally worth it, just curious).
[Nexus 6  Original Android Development] Elektroschmock:
You still have those options:

Go to "Factory Reset"

There you can choose which partition you want to wipe.

- Wipe data/factory reset

- Wipe cache

- Wipe system

I guess you want the "wipe system" option

Sorry we don't support modifying our builds for obvius reasons. If you want to do that you are on your own. Sorry.

It's just a test. Non of us was able to trigger the loss of audio. Youl'll still have stereo but it won't switch channels if you turn your device.
[Nexus 6  Original Android Development] wrsg:
No, stock camera is also crashing.
[Nexus 6  Original Android Development] Elektroschmock:
Well looks like I can't fix it for everybody. I'm out of options as qcamerasvr is a proprietary binary I can't change.

I can only trigger the bug if my device is in thermal limiting mode or if I use a semidead battery and BCL kicks in.

Idk why some Shamus behave so differently, maybe I should just pull the plug on night lies.
[Nexus 6  Original Android Development] pinakini:
Yes it works on balanced - my always on profile, since 0422.
[Nexus 6  Original Android Development] wrsg:
Please don't. If there's a workaround (like the Kill Camera thing), I don't mind using it. I didn't know about the binary problem.
[Nexus 6  Original Android Development] mahir555:
I had this camera bug since long time ago with different Android versions and every time i just use kill camera app and it worked fine . I think with clean flash this option will definitely work.

This rom is amazing please reconsider what you are planning to do.
[Nexus 6  Original Android Development] wrsg:
which one do you use?
[Nexus 6  Original Android Development] mahir555:
https://play.google.com/store/apps/details?id=info.aario.killcamera
[Nexus 6  Original Android Development] esysfound:
Is there anyway to change the System font? I have tried everything - iFont, Fonster, several others (all with Root), have copied over what I want into system/fonts and nothing is working. Everything else is working quite well. Thanks
[Nexus 6  Original Android Development] wrsg:
the app KillCamera works perfectly.
[Nexus 6  Original Android Development] maddog3030:
Not all Nexus 6 has are built the same, I'm not talkin about us and international (xt1103, xt1100).

Often times they'll switch internal components somewhere along the assembly ( different chip subsets) and for the big picture at usually doesn't matter because manufacturers will make allowances in the drivers for the difference is in those chips.

developers have no way of knowing unless they disassemble the drivers as well as take apart electronics to try to figure out what the differences are so they can maintain the drivers for the new operating systems... drivers are usually proprietary, they're not required to release the source code.

So therein lies the problem so we do the best we can....

And for a six-year-old device this is fantastic!.
[Nexus 6  Original Android Development] JaimeZX:
[MENTION=3383960]Elektroschmock[/MENTION]... this continues to work great. I've only had the camera quit on me once in the last week, fixed with cache/Davlik wipe. Otherwise I'm very pleased.

Easy question - alarm clock! On Monday my alarm didn't go off. At 6AM (alarm time) it just immediately went to "Missed alarm" without sounding. Weird. I tested the alarm that afternoon at like, 5:30PM and it was fine.

Tuesday - my alarm didn't go off. Same "missed alarm" without sounding. I dug into Do Not Disturb settings... Alarm should break through, but it didn't.

I changed Do Not Disturb "off" time to 5:59AM so that the 6AM alarm would work.

Today at 6AM the alarm sounded!! But I couldn't turn it off... there wasn't the usual [ ZZZzzz ----- ( ) ------- X ] on the screen.... I had to enter my unlock code and then pull down from the top to access the active alarm and then hit "dismiss."

POSSIBLY RELATED?

When my phone rings, I don't usually get the caller ID on the screen; screen remains blank, I have to unlock the phone and then pull down from the top to hit "Answer."

Is there something going on that isn't allowing Alarm and Phone through the lockscreen?
[Nexus 6  Original Android Development] pinakini:
Please don't. I had camera problem since LOS Pie. It may be specific to my device along with few other problems. I always have a work around like an extra reboot or clearing cache etc., it doesn't bother me. I always enjoyed being on latest version of android on my age old phone, purely because of the selfless service of you in specific and other developers in general.
[Nexus 6  Original Android Development] dvdram:
Thanks! Being a Linux user, I perfectly understand this kind of trouble that depending services can cause. :(

The first time I noticed this problem was back in LOS 15. And it's not just the home button that doesn't work, the menu button (or app list button) is also effected. The only button that still works is the back button.

But I have found a good work around for this in LOS 17.1 now: just switch to 2 button mode and use gestures to call the app list, and in 2 button mode the home home button always works.

I absolutely agree with this! This camera issue may be as annoying as it is, but the overall performance of your piece of work is just great!

I want to use my N6 as long as it's physically intact. It offers every thing I need on a phone and being able to run the latest Android just makes me feel glad I decided to buy it. And I am sure other users will think similar about this.
[Nexus 6  Original Android Development] chefp:
Great work [MENTION=3383960]Elektroschmock[/MENTION] !

I first went to the Lineage upgrade page for shamu before finding this thread. That didn't mention specifically to use the ARM build of GApps. I tried the ARM64 version first, which predictably failed (Lineage OS stuck on splash screen). Thought I was screwed and would have to factory reset, but before doing that installed the ARM GApps over it, cleared cache, and it worked. Boot took a while, and initially it was stuck on the lock screen which was probably because it was finishing the upgrade post-boot.

The camera app crashed at first. Rooted with Magisk and installed Kill Camera. Now Google Camera and Camera ZOOM both work fine. Mine is running the 0423 nightly.
[Nexus 6  Original Android Development] TotalChen:
Can anyone confirm if long pressing power button for 10s can totally replace the "Rooted with Magisk and installed KillCamera"? If this easiest way works for everyone, camera fc won't bother us at all.
[Nexus 6  Original Android Development] boneheadjim:
I am a noob at flashing roms but my experience was I could not get camera to work no matter how many times I rebooted. After holding power button down for ten seconds the camera worked! This method worked on my phone with Lineage 17 and CR Droid both of them do not have root. (I this doesn't post twice, having internet problems)
[Nexus 6  Original Android Development] xuxu1:
I have 17.1 since release and I never had camera problems. But I had them once at lineageos 16.

I like your Rom, its very fast and I noticed no Bugs. Great work [MENTION=3383960]Elektroschmock[/MENTION]
[Nexus 6  Original Android Development] Elektroschmock:
Were you able to see a difference in the log? Usually the bug happens around 25 s into the boot process.

It's hard for me to replicate, because my shamus ar not affected by this bug
[Nexus 6  Original Android Development] TotalChen:
Hope these logs could help.
[Nexus 6  Original Android Development] mrk2815:
have been running lineage 17.1 sinc day 1 and have not had any camera issues. as soon as i knew how to do the flash process being blind .then i went through it and i got up and running. Have not had any issue with lineage 17.1 android q.its a rock solid build.keep up the great work. That's coming from a blind person running lineage custom roms on their Android devices.
[Nexus 6  Original Android Development] tupac13:
[MENTION=3383960]Elektroschmock[/MENTION] hello sir can you help me ?

i was trying to build my own lineage os 17.1 rom for my shamu using all you're trees but iget this :

[ 0% 472/52995] build out/target/product/shamu/obj/ETC/vendor_mac_permissions.xml_intermediates/vendor_mac_permissions.xml

FAILED: out/target/product/shamu/obj/ETC/vendor_mac_permissions.xml_intermediates/vendor_mac_permissions.xml

/bin/bash -c "out/host/linux-x86/bin/insertkeys.py -t userdebug -c . out/target/product/shamu/obj/ETC/vendor_mac_permissions.xml_int

ermediates/vendor_keys.tmp -o out/target/product/shamu/obj/ETC/vendor_mac_permissions.xml_intermediates/vendor_mac_permissions.xml

system/sepolicy/reqd_mask/mac_permissions.xml"

/bin/bash: out/host/linux-x86/bin/insertkeys.py: No such file or directory
[Nexus 6  Original Android Development] Elektroschmock:
If it fails that early it's a strong indication, that you didn't stick to the build guide. Please double check, that you meet all prerequisites.
[Nexus 6  Original Android Development] esysfound:
Have been tweaking 17.1 for a few days - finally got all set where I want, Titanium successfully brought over a fair bit of (though not all) previously installed apps, Nova Launcher working fine and I have the system font I want (finally having mastered Magisk and the great Font Changer module). No camera problems. Nightlies updating fine and semi automated, even using TWRP. Very happy also with the footprint - much smaller than my prior Android 9 build.

Highly recommend this to all to keep the fine Nexus 6 alive and kicking (ass). [MENTION=3383960]Elektroschmock[/MENTION] - fantastic job and many thanks. :highfive:
[Nexus 6  Original Android Development] H@P:
Wiped/formatted everything using TWRP 3.3.1.0, flashed 2020-04-24 nightly, latest OpenGapps nano, latest magisk. Camera app not present after first boot. Installed Google camera app, rebooted, and camera has worked ever since (still no "default" camera app, if there's supposed to be one, but Google Camera app works).

Auto-flashed 2020-04-26 nightly. TWRP seemed to handle it perfectly.

Have only seen a few issues:

1) slight flickering/rendering glitches on Gboard. Sometimes doesn't render a bordered key edge (if you need a pic I'll see what I can do)

2) Bluetooth... only on a phone call, only receiving. They can hear me, I can't hear them. Headset worked fine before all of this (stock/rooted 7.1.1, N8I11F, Oct 2017, T-Mobile). Music plays fine. Using Bluetooth for a Duo or Signal audio call works fine. Tried both the preinstalled Phone app, and Google Phone app from Play Store; same issue. After monkeying with it, trying random things, it started working... but after reboot it stopped working again, and I can't get it working now no matter what I do. If you need logs, tell me what to grab, and I'll see what I can do.

3) not really broken, and probably nothing you need to worry about, but vibrate strength is *strong*. Tried using Kernel Adiutor to set it lower, and the first buzz is what I set, every subsequent buzz is back to *strong*. EDIT: This post indicates LineageOS kernel doesn't support tweaking this setting: https://www.reddit.com/r/nexus6/comments/8jee50/lineageos_and_vibration_setting_in_kernel_auditor/

Should have put this at the beginning of this post, but this build is *amazing*. Can't find a good enough phone to replace this beast, and this breathes new life into it. Thank you so much for your efforts.
[Nexus 6  Original Android Development] Sanabil:
Im late to the party, for many days was thinking that why hasn't anyone posted on lineage 16 thread.now i know.?
[Nexus 6  Original Android Development] VerucaSalt:
Flashed latest nightly successfully and in the status bar I have a microphone icon (looks like voice search perhaps) constantly flashing.

Any ideas how to get rid of that?
[Nexus 6  Original Android Development] gettes:
Turn off Google Assistant voice or disable the mic icon in settings > system > status bar
[Nexus 6  Original Android Development] pinakini:
I am facing this Bluetooth call problem in los 17.1.
[Nexus 6  Original Android Development] esysfound:
Battery Performance

I'm getting higher battery drain since using this ROM. ES addressed this in the Colt OS thread- where someone else reported this, saying it should not be an issue. Have checked all settings, running apps, throttled CPU to more conservative setting, etc. Battery settings suggest all apps using power normally. Have not done a really thorough look at this as difficult to compare apples with apples on different days - use of phone varies. Screen brightness is normally 35-40%. My gut tells me this maybe a WiFi seeking issue so I will turn off when not needed. But on Android 9 with light use, I could go all day and still have 50% left. Now it seems like maybe 3 hours.

Anyone else experiencing this?
[Nexus 6  Original Android Development] dvdram:
Two things I noticed within the last couple of days, good and bad news alike:

1. The good news:

The random profile switching (see here) did not happen any more since Monday.

2. The bad news:

Yesterday my N6 just turned itself off after I ended a phone call on Bluetooth. I pressed the power button to hang up, and 2 seconds later my BT device told it was not connected any more. The Nexus' display was black, it did not reboot by itself, it was simply turned off. Just like that! I could restart it by pressing power for 3 seconds, and everything was back to normal.

That was the second time this happened to me. The first time it happened was last week, and I thought I had pressed power button for too long when hanging up. This time I hardly touched the power button and surely I did not press it any longer than half a second to end the call.
[Nexus 6  Original Android Development] pinakini:
I here with attach a system activity log caught through LogCatE regarding my two main problems of Bluetooth calling and messages crash.

1. I can not hear the other side while a Bluetooth device is connected to my phone (I tried car, Bluetooth speaker) during a call. They can hear me. The Bluetooth speaker just sits there.

2. When my call is not answered or I disconnect it, The message prompt is crashing when I try to message the called.

Both were perfect on my device in 16.0.

I am very much illiterate in this android thing, but an ardent fan of custom ROMs, customization & N6. I do not know this will help or not. I request you all to excuse me.
[Nexus 6  Original Android Development] githyanki:
What percentage was the phone at? Classic first signs of a battery issue. Watch if it is happening around a certain battery level and see if gets worse below that level. Used to happen more often if you used the camera due to it's higher demands on the system.

Mine started around 20% and got worse until the phone was unusable below 40%. Replacing the battery fixed it right up.
[Nexus 6  Original Android Development] dlbarron:
Yes, I've noticed my battery performance isn't as good as before upgrading. I haven't had time to dig into it either.
[Nexus 6  Original Android Development] Sanabil:
I wiped every thing then used nexus tool kit on pc to flash Lineage recovery , now i am unable to install the downloaded Lineage OS and GAPPS like i use to with TWRP. I cant get my pc to show the device folder so i can copy to phone. Any help would be appreciated.
[Nexus 6  Original Android Development] FexusPexus:
Sensors not working after 17.1

Hi all,

Hoping anyone can point me in the right direction. Sensors on phone like accelerometer, gyroscope are not working after update. I've verified with Sensor Test and get "no data from sensor". Any advice on troubleshooting is appreciated.
[Nexus 6  Original Android Development] Sanabil:
I am kinda stuck i can still use TWRP but i want to try Lineage recovery as it is recommended. I installed Lineage recovery with an error saying at bottom

"E: failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated:no su ch file directory"

I guess its not reading the internal memory i cant get pc to show its memory so that i can copy lineage OS and gapps.
[Nexus 6  Original Android Development] maddog3030:
You have to turn on ADB by hand and that recovery there's an option for it and one of the sub menus.

that recovery is quite different than twrp you have to pay close attention especially in the sub menus.

When you're flashing it from fastboot flash it twice maybe three times in a row.

and double-check the CRC on that file before you try flashing it you could have a corrupted file (sha256)

3a2241a52d301ce3f6d617c3f34559b67dfac91275bc2d841ba035d414c16c0c lineage-17.1-20200429-recovery-shamu.img
[Nexus 6  Original Android Development] zapjb:
nvm please delete ty
[Nexus 6  Original Android Development] Sanabil:
Ok thanks
[Nexus 6  Original Android Development] mrk2815:
yes i was not sure rom or battery related.i flashed cr droid 10,.i have been using that fora day now and cant reproduce why that rom will not battery drain an why lineage rom will. so guess for time being will be on cr droid till the is a resolution for lineage 17.1. Don't know how i can help.on cr droid , under battery i have set it to efficiency instead of balanced. Under dark mode, there is an option in dark mode on cr droid to have dark gray, or oled d bblack and that is also set.so i dont know if these settings may cause difference in battery or performance. But for time being that rom is holding a good day on teh battery that the nexus 6 wwas replaced.it was done by a friend of mine a while back.
[Nexus 6  Original Android Development] Sanabil:
Ok i used Nexus tool kit to wipe partition and flash lineage recovery image 3 times , now i dont see the error but how can i use Lineage recovery to copy my files from my pc to my phones storage and then use lineage recovery to flash it in my phone? Or do i have to flash everything from PC? Is there a guide on this? im kinda confused. TWRP shows folders and when connected to PC i can transfer files in phone but on Lineage recovery when connected to PC i cant get access to my memory.
[Nexus 6  Original Android Development] maddog3030:
https://wiki.lineageos.org/devices/shamu/

All instructions are in the above link
[Nexus 6  Original Android Development] Sanabil:
Ok i got the instructions thanks a lot

---------- Post added at 01:21 AM ---------- Previous post was at 12:39 AM ----------

Is there a disadvantage for using TWRP? And what is the main advantage of Lineage Recovery over TWRP?
[Nexus 6  Original Android Development] maddog3030:
Truth be told I use TWRP myself over lineage recovery.

Twrp hasn't been developed in a while and will not deal with the a/b devices.

Twrp also has a lot more functionality but as of this moment there is no detriment to using it that I can see.

Lineage recovery functions with the update menu of the lineage os and can I update the OS from the update menu.

and plans are to allowed to update the recovery as well from the same menu.
[Nexus 6  Original Android Development] Sanabil:
Is it me or Google feed and using gesture navigation there is lag? My battery has about 70% life remaining.
[Nexus 6  Original Android Development] Gysper:
Might need a bit more clarification. Is your lag referring to animation speed or when you swipe and it doesn't respond?

This is probably a limitation of the N6 and its aging processor although if you go to the settings and select battery, you can change the performance mode to something higher than balance which may make it smoother.
[Nexus 6  Original Android Development] Sanabil:
Yes the lag the frames drop, and I also agree n6 age is contributing to this drop in performance but on lineage 15.1 same animations and feed were considerably smoother.

maybe the newer apps and OS framework is more demanding and requires a more recent processor and GPU etc.
[Nexus 6  Original Android Development] dvdram:
Thanks for this hint! I will keep an eye on that!

The first time it happened the battery was about 70%, and the second time it was about 40%.

When your battery started to dy, were you still able to use your phone until 5% battery or less from time to time? For example, yesterday I was able to use my Nexus until the battery icon went red (5%). No crashes, no glitches until then. On normal days I don't need to stress the battery that much, but yesterday was an exception. When I finally got to plug it in to charge, the battery was down to 3%, but still the display was alive and I still could receive text messages.

Can a dying battery still behave like that? I have experienced bad phone batteries before, but they always just reached very low percentage very quickly. I never experienced a phone switching of just like that at ~50%.

---------- Post added at 09:27 AM ---------- Previous post was at 09:23 AM ----------

The reason why I still use TWRP is the possibility to back up the entire system as an image without having to root the main operating system. As soon as LOS recovery will offer that function, I will use it.
[Nexus 6  Original Android Development] Elektroschmock:
Should be considerable improved in one of the next nightlies. But the Google feed isn't a very good test case for smoothness, as it has to reload data every time you scroll.

A better Test case is the recents animation.
[Nexus 6  Original Android Development] githyanki:
Yes, the powering off seemed to be random for awhile until it became frequent enough. I could use the phone till the battery was completely dead for awhile until the crashing became too frequent at lower percentages.

However if it shut off at 70%, that may not have been the problem. Only time will tell.
[Nexus 6  Original Android Development] Sanabil:
It's kind of a miracle to see Nexus 6 running Android 10. Seriously can't say enough thanks to Elektroschmock for doing this.:good: