yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Elektroschmock:
I don't get your question. Stuck on what?

What does it have to do with beein rooted.

Don't have too high hopes anyone is updating TWRP anytime soon.
[Nexus 6  Original Android Development] wrsg:
I'm encrypted on LOS 16.0 and have TWRP 3.2.3. When I try to access the phone system/storage from inside TWRP to flash Magisk (it didn't persist through the last update for some reason) it basically won't decrypt the storage.
[Nexus 6  Original Android Development] Elektroschmock:
Yes, that is a well known behaviour. TWRP can't decrypt the data partition and unless someone more capable then me updates TWRP it will never be able to do that.

You can always flash your magisk through adb sideload.

That's why I don't get why and on what you are stuck.
[Nexus 6  Original Android Development] Najeeb3344:
[MENTION=3383960]Elektroschmock[/MENTION]

Please fix sudden shutdown problem on lineage os 16 it is 3rd time for me within one week
[Nexus 6  Original Android Development] Elektroschmock:
I can't fix dead batteries through software. There is nothing I can do without crippling the performance of users who still have good batteries or who've spent the 20 bucks for a replacement battery.
[Nexus 6  Original Android Development] Najeeb3344:
But no battery drops it remain same at 40% and reboots fine with the same battery

---------- Post added at 03:47 PM ---------- Previous post was at 03:43 PM ----------

This problem not occur with previous version 15.1
[Nexus 6  Original Android Development] Elektroschmock:
A dead battery doesn't always lead to percentage drops. It just can't handle the current peak which leads to a brownout.

But If you are 100 % shure that it's not your battery - do a proper bug report.

I have stated in post #2 that I'm not willing to look into 'bugs' If the user doesn't contribute in any way.

Without bug report I'm blind, as I can't reproduce any shutdowns.
[Nexus 6  Original Android Development] Najeeb3344:
How I take bug report of sudden shutdown:rolleyes:
[Nexus 6  Original Android Development] dahawthorne:
There are some users, usually juniors, whose attitude makes it clear that they're not really interested in your expert help, just in seeing their name on a post.
[Nexus 6  Original Android Development] pinakini:
Thanks. The 17th March update fixed cameras (what I think.)

---------- Post added at 05:15 PM ---------- Previous post was at 05:11 PM ----------

Can I encrypt & continue to update through Updater?
[Nexus 6  Original Android Development] Dhalsim43:
Yes but if you have anything else to flash (magisk, boot animation...) you will have to use usb otg because twrp won't be able to decrypt data partition
[Nexus 6  Original Android Development] FaultOverload:
What kind of diagnostics can I run to get you the battery data that might help figure this out? I replaced my battery about a year ago with a XT1100 EZ30 3200mAh US that I bought off ebay and experienced the random reboots to my bootloader that others are complaining about. When running 15.1 I get amazing battery life and have no random reboots.
[Nexus 6  Original Android Development] Elektroschmock:
Sudden shutdowns and crashes are something totally different.

We fixed a bug related to IMS which could cause crashes for some users.

It's fixed with lineage-16.0-20190318-nightly-shamu-signed.zip
[Nexus 6  Original Android Development] BootloopedMillennials:
When your phone gets down to 40 percent. Open the camera app and take a picture (should cause a voltage spike like [MENTION=3383960]Elektroschmock[/MENTION] mentioned). Does it suddenly shutdown?
[Nexus 6  Original Android Development] Newfe:
i get battery drain on version 16 anyone else have that problem?. I went back to 15 now the problem is gone.
[Nexus 6  Original Android Development] pinakini:
Actually my battery life got better on Los 16.0. I am now having an extra 30 mts. SOT. I have the same setup as was on Los 15.1. Though my 90% battery shuts down at 10%. [this reason may not be correct]. I flashed openGapps micro.
[Nexus 6  Original Android Development] FaultOverload:
Oh neat, many thanks for you and all the other devs that work hard to fix these kinds of issues. I'll try it out again when I get some time to run the upgrade.
[Nexus 6  Original Android Development] Sanabil:
I am noticing delay in app load times.. especially when they are not in memory, is this me only?
[Nexus 6  Original Android Development] duhec:
Isn't this normal for a 4+ year old device?

It's especially true when I run Google Maps app. I could solve a rubicks cube in the meantime.
[Nexus 6  Original Android Development] Sanabil:
Maybe newer apps are more optimized for newer gen processors and chipsets. But delay was not there first its now that i am noticing it.
[Nexus 6  Original Android Development] mezerr:
YUP!

I just OTA'd the March 18th update, from a clean flashed March 15th, and I started getting the same thing. Facebook stayed on the blue screen for 25 seconds before it opened, and same thing with Instagram. I restarted, cleared cached, but didn't help. Left the phone over night and this morning is better.

I just tried to capture a log but can't reproduce issue.
[Nexus 6  Original Android Development] Elektroschmock:
Thats why we have different power profiles. You could chose a faster, more energy hungry one.

But shamu's memory is slow so it can't compete with a newer device.

But imho shamu is still usable as a DD.
[Nexus 6  Original Android Development] mezerr:
I've been on QUICK since day one, and only started experiencing app opening delays for the first 4-5 hours after OTA'ing March 18th. It's since gone away and everything is speedy again.

This is just a FYI, I'm not actually looking for help. If it continues, I'll post a log.
[Nexus 6  Original Android Development] Sanabil:
I am already on Quick profile, i recently have noticed it Facebook and Gmail in particular takes considerably long time to start up. Maybe after updating it may get fixed as i did not noticed it earlier.
[Nexus 6  Original Android Development] Elektroschmock:
Why should cleaning cache help? It doesn't do any magic.

I don't know how long after updating you did your tests, but after an update the system is doing a lot od stuff in the background.
[Nexus 6  Original Android Development] mezerr:
Blah Blah

Opening apps was delayed for roughly 10-15 hours after updating. I was close to reverting back to my twrp backup. However I left the phone overnight, and this morning was better.
[Nexus 6  Original Android Development] dahawthorne:
What...?
[Nexus 6  Original Android Development] dbrickg:
"blah blah" is the correct answer to the zen master's question: "what is the sound of one moray eel clapping?" :)
[Nexus 6  Original Android Development] mrg666:
Thank you for the ROM. It is running excellent for me since two weeks. Can't complain about anything.
[Nexus 6  Original Android Development] duhec:
I usually customize my opengapps installation with .gapps-config file and this is the first time I had to use the +WebViewStock # Don't remove Stock WebView entry otherwise stock webview would be deleted, Chrome wouldn't install and you therefore remain with no webview installed and then you cannot even sign in to Google because the screen goes blank.

Now I see Chrome still isn't installing. I guess there is something wrong with OpenGapps.. :rolleyes:
[Nexus 6  Original Android Development] Elektroschmock:
Nothing wrong with OpenGapps. System just isn't big enough for the gapps package you chose. The size of the system image varies from build to build so it isn't wise to fill the system partition to the max imum with gapps

I changed shamu to full-dexpreopt lately to have shorter boot times. That increased the image size by 22 Mb
[Nexus 6  Original Android Development] Sanabil:
So does that mean that installing gapps stock or full package will decrease performance ? Like i installed stock gapps, maybe that's the reason for slow app loading?

---------- Post added at 06:59 AM ---------- Previous post was at 06:23 AM ----------

Hallelujah!! After updating Lineage OS , app speed is restored. Thanks bro ? now apps loading instantly
[Nexus 6  Original Android Development] duhec:
I'd have never guessed that. I learn something everyday. Thanks. :)
[Nexus 6  Original Android Development] duhec:
Update: Hm, I don't think system partition size is the problem. Is just that when installing Chrome through opengapps, stock webview get deleted and Chrome (+chrome webview) not installed. But why is it doing that I don't understand? :confused:

I attached the opengapps logs but it doesn't say anything special except there is plenty of space on system partition and chrome successfully installed.

Update again: seems like the included Chrome version 73 is giving problems. I will now try the opengapps from march 15th which still has the Chrome v72.

Update: Yes. Chrome version 73 is the problem because opengapps from 15/3 installed Chrome v72 and webview with no problem and I can now sign in to Google.
[Nexus 6  Original Android Development] dbrickg:
FYI: I'm still on 15.1, and the Chrome version on it is 73.0.3683.75, and it doesn't seem to be causing any problems.
[Nexus 6  Original Android Development] duhec:
If you update within the rom already installed then I think there is no problem, only when you clean flash and try to install Chrome with opengapps. Judging by the Opengapps thread on XDA I'm not alone. But as I said, I downloaded an earlier version and things work fine. Now I'm really loving Pie. I'm not going back to Nougat anymore. :D

[MENTION=3383960]Elektroschmock[/MENTION] some time ago in Oreo I remember Whatsapp notification LED lighted up when you received content from people but instead of being permanent until you swiped the notification away, the LED light would go off after a number of seconds. Now same thing is happening with Messaging app from Google in Pie. Can you do something about it? Because in Oreo I remember you fixed something. :cowboy:
[Nexus 6  Original Android Development] Elektroschmock:
Sorry I kind of bricked my DD so I need my shamu right now. I can't work on it for a while.
[Nexus 6  Original Android Development] duhec:
Oh. That's unfortunate. We will wait then.

In the meantime I found the post where you explained it was something about the priority of the notification.
[Nexus 6  Original Android Development] Elektroschmock:
That was something different. Charging LED overwrote the notifiation LED back then.

Perhaps your 'bug' can be fixed in the settings of the missbehaving app.
[Nexus 6  Original Android Development] duhec:
The missbehaving app is Messages from Google which replaced Lineage SMS app with OpenGapps by default and the settings are pretty straightforward as seen in the picture.

[IMG="Google Messages"]http://shrani.si/f/0/lp/3AOQA9Mj/googlemessages.png[/IMG]

And it's not that it doesn't work, it just turns the LED light off after ~10 seconds. :)

I'm trying different settings but it doesn't stick. If someone can point me in the right direction.. :rolleyes:
[Nexus 6  Original Android Development] Elektroschmock:
Perhaps disable 'blinking', as shamu's LED can't blink.
[Nexus 6  Original Android Development] dbrickg:
Hmm, so, after you go back to the old version of Chrome, can you go into the google play store and update your apps to get the more recent version? Not that it probably matters much. Just wondering.
[Nexus 6  Original Android Development] duhec:
I wish it was that easy. "Blink light" just means "activate the LED". If I disable it, then there is no LED. If it is activated then it blinks. Once. Very useful. :rolleyes:

Ok so you're saying it is not about the priority, for example that the battery LED overrides the messages notification LED?

It's been about 10 hours now since I clean flashed and of course I was curious just as you are and went to Play Store several times to check if there is an update available and there is none. I have version 72.0.3626.121 from March 1st and it doesn't offer me any new version. Interesting.
[Nexus 6  Original Android Development] dbrickg:
well, darn! i was hoping there was some kind of simple something or other ....
[Nexus 6  Original Android Development] yhwh111:
Hi everyone, loving this room so far no issues. I have a question, is anyone got face unlocked on this room, and which gapps are you using of yes? Thx.
[Nexus 6  Original Android Development] dahawthorne:
https://play.google.com/store/apps/details?id=com.chrome.beta&hl=en_GB

Current Version 73.0.3683.75

I'm using Kiwi, not Chrome, but have you checked your Chrome on Google Play for "Become a beta tester"?
[Nexus 6  Original Android Development] duhec:
I'm always hoping for some kind of simple something.

What dbrick said - it doesn't matter much. Besides I will flash and clean flash Lineage many times in the future because... well I can't help myself and I will have the time to experiment more.

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

Question for all of you using the stock SMS app that comes with Lineage: when you receive a text message, does you LED stays on until you swipe the notification away/read the message or does it stay on just for a couple of seconds?
[Nexus 6  Original Android Development] anhsbio:
Sorry to hear about your DD. Hope it gets sorted soon. Out of curiosity, what DD do you use?
[Nexus 6  Original Android Development] wavedashdoc:
Actually, I believe there's a work around in AOSiP that introduced blinking LED. But I don't use it.
[Nexus 6  Original Android Development] Elektroschmock:
It's more a hack then a workaround. This implementation uses softwaretimers and doesn't work properly.

It should be doable to do the blinking in HW, but I'm not shure if I want to dump countless hours into it.
[Nexus 6  Original Android Development] wavedashdoc:
[MENTION=3383960]Elektroschmock[/MENTION] are you seeing noticeable improvements with these commits?

I'm trying to squeeze as much performance and proficiency as I can with 8.1. also trying to implement some commits from the previously popular Android 5.1 and 6.0 Vindicator Kernel.

Just trying to keep the whale alive as long as possible. Like you said, still plenty usable in 2019. SD805 was a head of it's time.
[Nexus 6  Original Android Development] Elektroschmock:
Hard to say, as memory leaks only hurt after a longer uptime. But as I usually flash my shamus every day I can't really judge it.

But fixing memory leaks is always good. :)
[Nexus 6  Original Android Development] Hammerfest:
if ya ever did, id love ya for it

always bugged the **** out of me that it cant blink, to the point where its an on/off operation so the logic should be simple catch blink commands then in the background simply toggle on, then wait, then off, SADLY i know its no-where near that easy :X
[Nexus 6  Original Android Development] Sanabil:
I appreciate your and Electroschmock efforts.
[Nexus 6  Original Android Development] k1l:
Anyone with Kamera crashing issues?

I am running my own (vanilla) builds and since i flashed todays build the camera cant start. my oldest builds are only 3 days old, so i cant go any further back to check since when its an issue.
[Nexus 6  Original Android Development] Hammerfest:
cam is kinda crazy on LOS, as I reported back in the 15.1 thread it happened to me there as well, but after a few reboots or full power down then power on, bam, back to working
[Nexus 6  Original Android Development] k1l:
ok, it works now again.

i did reboot, didnt help.

i did flash the 3 days old build, then todays build. didnt help.

i did power down, didnt help.

opening kamera several times again, still crashin. now out of the blue it works again. dont ask me why. kamera was very stable the last months for me.
[Nexus 6  Original Android Development] JaimeZX:
Happens to me... every ~10 days? Have to reboot the phone and then it's fine. My issue with the phone existed in 15.1 too - takes dang forever to take the picture. Impossible to get pictures of the kiddos, they move four times between the "look" I wanted and when it actually takes the photo. :/

Thanks for all your hard work on this, sincerely.

Question - how challenging would it be to add "LED" to the app permissions? I'm guessing a lot... the dang LED on Shamu is like a spotlight at night. I have to flip the phone upside down or it lights up the whole room. I do shadow puppets on the ceiling for my wife. She doesn't find that funny. :p

I guess a "disable LED during XYZ hours" like with the automatic display brightness would be cool... lol
[Nexus 6  Original Android Development] githyanki:
Yes, set up an automatic do not disturb profile. You can disable visual notifications with that.
[Nexus 6  Original Android Development] Elektroschmock:
It's already there. Additionally you can lower the brightness globaly during DnD.
[Nexus 6  Original Android Development] ocbones:
I love the ROM but my only major issue is the brightness even on the lowest setting it's to bright and it's killing my battery life and hurting my eyes when watching YouTube at night, didn't have this issue on 15.1 saw few pages back that this was done on purpose. Thanks in advance.
[Nexus 6  Original Android Development] Elektroschmock:
I have two shamus. One running 15.1 the other 16.0. I don't see much of a difference regarding minium brightness.

The one 16.0 is even a bit less bright, but I guess thats due to the fact that ist 2 years older then the other one.
[Nexus 6  Original Android Development] ocbones:
could this change to the level per slider setting have caused the the lowest brightness to start at 35%? am i the only one to notice this? or maybe i need to do another flash.
[Nexus 6  Original Android Development] ocbones:
I was able to fix this by setting the RGB to 50% in color calibration under live display/advance display settings ✌️
[Nexus 6  Original Android Development] wrsg:
Wow, the commit list for the next build is huge
[Nexus 6  Original Android Development] Elektroschmock:
No new features just a lot of backported fixes from 3.16 and 3.18.
[Nexus 6  Original Android Development] Lawstorant:
[MENTION=3383960]Elektroschmock[/MENTION] Actually, on 15.1 the brightness is way lower with 0% setting and automatic brightness turned on. Just cover the light sensor.

Did something change regarding audio in 16.0 in our shamu? 15.1 has noticeably louder output on headphone jack.
[Nexus 6  Original Android Development] JaimeZX:
So either I did something wrong, or it didn't work. The LED was still on last night. At first I thought it might be dimmer, but it was still plenty bright to do shadow puppets on the ceiling!
[Nexus 6  Original Android Development] Elektroschmock:
Did you set it like this?
[Nexus 6  Original Android Development] JaimeZX:
No! I didn't know that screen existed, the only DnD I found was in "Sound," but after you posted that screenshot I "searched" and found it. Thank you! I'll try 25%.
[Nexus 6  Original Android Development] L.F.B.:
The traffic monitor... Is it working? Its in the middle of ststus bar and Its seems not working... Anyone can reproduce?
[Nexus 6  Original Android Development] ReedN:
Back in ~April of 2018 I discovered that LOS 14.1/15.1 lacked an OEM file specifying default applications which caused creation of profiles for Android 'Work Profiles' or AfW (Android for Work) to fail.

This Android capability is used by many employers to create a protected profile in which employees can securely receive work emails and such.

To work properly the 'ManagedProvisioning' module needs to have a proper set of vendor required apps specified in the 'vendor_required_apps_managed_profile.xml' file. This is the task of the OEM so that they can specify which apps will replace stock apps. When I first encountered the problem the stock AOSP code was blank. There is a set of minimum defaults needed as specified in Android documentation: https://source.android.com/devices/tech/admin/implement#required_apps (They give an example from a Nexus phone).

With the default set apps correctly specified Google's open source test code 'Test DPC' should be able to complete successfully.

https://github.com/googlesamples/android-testdpc/

(Also available on Google Play: Example code distributed by Google to help developers implement)

The change submission I created here (https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/212726) created the appropriate defaults file for LOS 14/15.

Does anyone know if this change was carried over from LOS 14/15 to the new LOS 16?
[Nexus 6  Original Android Development] everdium:
OK, I understand. Then it is strange that LineageOS asks for the PIN, if its not encrypted.

But if I do encrypt it with LOS 16, I can not use TWRP to decrypt ? That means that I will not be able to use TWRP to flash a ZIP when that ZIP is present on the data partition.

By the way, the phone is very fast, unencrypted.
[Nexus 6  Original Android Development] BootloopedMillennials:
I formatted system in TWRP and not via fastboot format commands. It worked. shrug

It works. I tried it with clock on the left.
[Nexus 6  Original Android Development] wrsg:
So did anyone manage to sideload 16.0 successfully on an encrypted 15.1? Or is that not possible because of TWRP?
[Nexus 6  Original Android Development] Dhalsim43:
This information needs to be updated in OP
[Nexus 6  Original Android Development] everdium:
The LineageOS 16 camera app does not work (force close). The same happens with Google Camera.

I checked permissions, looks fine. Any ideas ?
[Nexus 6  Original Android Development] Elektroschmock:
Usually fixed by a reboot
[Nexus 6  Original Android Development] McMannes:
i have twrp 3.2.3.0. Can i use it. Or should i only use twrp 3.2.1.0
[Nexus 6  Original Android Development] cou94114:
Google Fi uses IMS?

I'm on Google Fi with my Nexus 6 running LineageOS 15.1. The first post states that IMS is not working on the new 16.0 build. I think Fi uses IMS, right? If this is correct, I need to stay on 15.1.
[Nexus 6  Original Android Development] Sam Nakamura:
Thank you for your work on Shamu! I'm totally impressed, just wow! :good::highfive::victory:

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

Flashed lineageOS 16 via latest TWRP few hours ago, together with Open GApps Nano for Android 9 / ARM, Magisk 18.1 and all good, I was coming from lineageOS 15.1 (decrypted) and wiped /system, /cache & /dalvik/ART cache before flashing the row of 3 (ROM, GApps, Magisk).

Only small hiccups with force closing APPs, a re-install of the trouble making applications however fixed it, so far everything is just fine and working, I don't think logs for such none issues are helpful and that's rather a GApps problem anyway, actually not even a problem... Let's forget about it!

Just posting because I'm happy about this update and wanted to share my experiences! That's just awesome!
[Nexus 6  Original Android Development] Lawstorant:
I only experience Pixel Launcher FC's (OpenGapps stock). I'll try to reflash them though and report back.
[Nexus 6  Original Android Development] agibby5:
I had 15.1 installed. It says it was encrypted. I couldn't figure out how to decrypt it. Anyway, I proceeded with a backup using

adb backup --twrp

from my laptop. I did an upgrade through TWRP from the sdcard. Everything went well, but when it booted, it asked for my decryption password. I don't have one. The only option was to restart the phone or try to enter a password. I guessed at a password, but it was wrong and it forced me to factory reset. Ok. I figured, I'll restore my 15.1 backup to keep my data partition with

adb restore backup.ab

Nope. that wouldn't boot and caused issues with my partitions. So I wiped everything and fixed system in TWRP, formatted data. Flashed 16.0 again fresh. Everything is working after logging in with my gmail account. It's currently downloading a Google Cloud backup. We'll see what that brings back. I would have much prefered to keep my data partition, but I guess that's out. Sounds like my backup is not good enough to restore. I wish I could. I may have had videos of my son. My pics are synced to Amazon Prime, but not videos. Doh.