yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Elektroschmock:
I can still see the N6F27M build. :confused:

Not shure what this new T-mobile build is, but it doesn't contain any new binaries. I ran my extraction script an nothing was updated.
[Nexus 6  Original Android Development] Elektroschmock:
Even if this wasn't my top priority I had some time today and fixed it. :)

Should be in the new build on monday.
[Nexus 6  Original Android Development] gothy.gothy:
Recommended Gapps for 15.1 are OpenGapps or MindTheGapps?

Very unclear subject when reading this thread

Thank you
[Nexus 6  Original Android Development] moso11:
I used OpenGapps. No issues so far.
[Nexus 6  Original Android Development] dbrickg:
Yes the original recommendation was MindTheGapps, but only because OpenGapps didn't have a version that worked with 15.1
[Nexus 6  Original Android Development] adm1jtg:
Appears like the only change was the radio file which changed from 545 to 551, oddly enough based on other forum postings this NEW 551 is NOT the same as the Verizon only 551.
[Nexus 6  Original Android Development] SteveYoungs:
The sensor can be enabled with the screen off. Whenever I want to pick up my phone without having "lift to wake" kick in I'll do so with my thumb covering the sensor... Works every time. :) However, DTTW is a different story, proximity will prevent it occasionally, but often won't (it actually doesn't work more than it does). This is not a LOS thing or even an Oreo thing, it has always been like this.

And with Automate (https://play.google.com/store/apps/details?id=com.llamalab.automate) I logged what the sensor was doing with the screen off... It is working, but did notice that sometimes it was slow in that it would occasionally miss state changes.

Bottom line, the proximity sensor does work with the screen off, but not reliably enough to prevent bum dialing when DTTW is set.
[Nexus 6  Original Android Development] dbrickg:
Quite awhile ago I got so fed up with the phone thinking it knew when I wanted it to wake; I turned off all the auto-wake crap, and set it to wake *only* when I press the power button. Likewise with the auto-sleep: I set it to stay awake for the maximum time (30 minutes, I think) and just press the power button again when I want to make it go to sleep.
[Nexus 6  Original Android Development] SteveYoungs:
Oh I hear you! Many times I've thought and felt the same. :)
[Nexus 6  Original Android Development] Manya3084:
That's very interesting. Maybe a work around could be, if you enable the feature, DTTW becomes greyed out. It's either one or the other.
[Nexus 6  Original Android Development] BoozYooNit:
Wasn't there a problem with OpenGapps and emergency calling? It's not spelled out on the opening post, but I've read that MindThe Gapps is recommended because OpenGapps is not fully compatible with 15.1.
[Nexus 6  Original Android Development] dbrickg:
Hmm, I don't know. If you want somebody to help you with this, you'll need to cite some sources. What "problem with emergency calling"? And where did you read that OpenGapps is not fully compatible with 15.1? What incompatibilities are there? You'll have to let us know in a bit more detail if you want anybody to help you research the problem. Or, better yet, you could try doing some research yourself. Try the experiment and see if it works.
[Nexus 6  Original Android Development] BoozYooNit:
It's not a problem for me, and I don't need any help doing research. I was simply asking a question based on comments i've read on the linneage os subreddit as well as this XDA story from March:

https://www.xda-developers.com/gapps-package-recommended-rom-developer/
[Nexus 6  Original Android Development] dahawthorne:
I think the problem that you're referring to is a report that a person was unable to dial 999 (or 911?) to call an ambulance. The solution was to specifically set Phone as the default telephone app in Settings/Apps & Notifications/Advanced/Default apps.

I strongly recommend that everyone check this setting before you actually need an ambulance. And tell your friends...
[Nexus 6  Original Android Development] nilesh0205:
Thank you, that worked. :)
[Nexus 6  Original Android Development] aclb5:
Hell yeah! Thank you. :good:
[Nexus 6  Original Android Development] Elektroschmock:
Good news! I managed to fix our proximity check on wake.

The main problem was that our touchscreen driver was sending a KEY_POWER instead of KEY_WAKEUP event. That is the equivalent of a power key press.

Of course the proximity sensor shouldn't block a power key press. :D

I fixed it with this commit:

https://review.lineageos.org/#/c/LineageOS/android_kernel_moto_shamu/+/216440/

and enabled the feature with this commit:

https://review.lineageos.org/#/c/LineageOS/android_device_moto_shamu/+/216439/

I need some testing, but I hope I can get it in for today's build.
[Nexus 6  Original Android Development] duttyend:
Awesome! You're the best :cool:
[Nexus 6  Original Android Development] Manya3084:
Great news! I'll report back with either a ?, or a sample of an arse typed mms. ??
[Nexus 6  Original Android Development] MiroALG:
why icant find latest update on lineage os site
[Nexus 6  Original Android Development] CyrusReport:
JUST now posted...grab it
[Nexus 6  Original Android Development] MiroALG:
thank you ?
[Nexus 6  Original Android Development] girkev:
OTA download Null, zilch.

Someone else ??)
[Nexus 6  Original Android Development] SteveYoungs:
Didn't make today's build. Ah well, something to look forward to for next week.
[Nexus 6  Original Android Development] runekock:
I read that back in the Nougat days. But this issue seems to tell a different story:

https://github.com/opengapps/opengapps/issues/618

The issue seems to say that Android is hard coded to use the aosp dialer for emergency calls, so the gapps mustn't remove that. Maybe that's the Oreo way? [MENTION=7145576]BoozYooNit[/MENTION]

---------- Post added at 07:56 AM ---------- Previous post was at 07:47 AM ----------

I think the echo occurs if the bottom speaker is active, because it is right next to the mike. But I have no idea how to fix that.
[Nexus 6  Original Android Development] nemanja066:
Where's the reading mode tile, i don't see...[emoji847]
[Nexus 6  Original Android Development] ExpectedCrayon:
Flashed the 5-28 version. Running smoothly, DRM is reporting L1 and a Netflix appears to be working! Haven't tested downloads, but it seems to be streaming HD.

Thanks [MENTION=3383960]Elektroschmock[/MENTION]!
[Nexus 6  Original Android Development] Elektroschmock:
...soon! :D
[Nexus 6  Original Android Development] smoothxda:
Awesome! Cant wait to try that out.
[Nexus 6  Original Android Development] CyrusReport:
Brilliant!
[Nexus 6  Original Android Development] duttyend:
Wunderbar :D
[Nexus 6  Original Android Development] paulmerrill:
Does this mean the cores will be hot plugged, so will turn off when not needed?
[Nexus 6  Original Android Development] Elektroschmock:
Exactly!

There will be 5 power profiles:

1. Power Save=> Maximum of 2 cores online

2. Bias Power => 3 cores hotpluggable

3. Balanced => 3 cores hotpluggable

4. Bias Performance => 3 cores hotpluggable

5. High Performance => All 4 cores always enabled
[Nexus 6  Original Android Development] paulmerrill:
Excellent, hot plugging the cores has a big impact on battery life with little impact on performance in my opinion on the Nexus 6. I'm looking forward to it.
[Nexus 6  Original Android Development] smoothxda:
So option 2, 3, and 4 will be the same "3 cores hotpluggable" setting?
[Nexus 6  Original Android Development] Manya3084:
You sure? The option is showing in the display-adavanced settings. It's working quite well ?
[Nexus 6  Original Android Development] SteveYoungs:
Well, bugger me! I hadn't noticed that "Prevent accidental wakeup" in the settings. And you're right, it does work well.

Mystifying that the ChangeLog says the 2 commits that fix and enable this came in _after _ the 20180528 release? That, plus the fact that stupid me hadn't found the setting, is why I posted what I did. ? Sometimes I really like being proven wrong... This is one of those times. :)
[Nexus 6  Original Android Development] dbrickg:
Likewise! :) In fact, where "this" equals "just about always".
[Nexus 6  Original Android Development] SoTacMatt:
[MENTION=8568276]Electroshmock[/MENTION]

The Nexus 6 is no longer my daily phone. I wiped it. If you want any tests done, I am happy and willing to help.

Great job on what you have done! I really enjoyed using your roms!
[Nexus 6  Original Android Development] Elektroschmock:
Thank you for your kind words. :o

If you want to test it here is a build with the new power hal.

You need a clean install, as it is not signed with LineageOS's keys.

https://drive.google.com/open?id=1Wrvr_WcTUDEtAi17rxL55eadzdGJudvj

Let me think what you think of the performance and battery life. It's always hard to judge, as you can't benchmark it properly.
[Nexus 6  Original Android Development] Elektroschmock:
Of course there are other differences between those three profiles, but that would be too much to write. ;)
[Nexus 6  Original Android Development] CyrusReport:
Truly this is great work. Thank you!
[Nexus 6  Original Android Development] orgert:
anyone else having this same issue ? im curently updating manualy, cuz every time i try updating in ota , i get this error , tried to read after the post above but didnt find any solution
[Nexus 6  Original Android Development] BoozYooNit:
Yep, I got the same error trying to install the download. and also had to install manually in TWRP.
[Nexus 6  Original Android Development] Malvarose:
Anyone else know it takes a while for the screen to turn on sometimes? Is there a way around this? I can double tap the power button to open the camera, and that seems to help.
[Nexus 6  Original Android Development] SteveYoungs:
Yes, my son gets it, but I don't. I've heard that if you start from the last 14.1 and install every 15.1 in succession without skipping any you won't get it. (I skipped the first couple of 15.1 releases on my son's phone)
[Nexus 6  Original Android Development] kern3l:
Well that's weird, mine's on 14.1 and I sometimes experience this issue.
[Nexus 6  Original Android Development] paulmerrill:
I've never got auto update working. It does the download, boots into twrp 3.2.1 but never installs. I end up doing update manually as well. 14.1 use to work fine.
[Nexus 6  Original Android Development] wisnu666:
just curious whether in high performance, the core will be clocked down or not when the battery is under 40%? this would be an awesome feature to be implemented :D
[Nexus 6  Original Android Development] digitalcircuit:
Screen wake issues with Expanded Desktop + Google app

Do you have Expanded Desktop enabled and Google app installed?

There appears to be a bug where the Google app conflicts with Expanded Desktop mode whenever the screen is off. You can work around this by disabling immersive/Expanded Desktop mode for the Google app, as per a post earlier in this thread by makerick811.

If you only hide the navigation bar:

adb shell settings put global policy_control immersive.navigation=apps,-com.google.android.googlequicksearchbox

If you hide both navigation and status bar:

adb shell settings put global policy_control immersive.full=apps,-com.google.android.googlequicksearchbox

NOTE: I have not personally tested this as I reverted back to the last LOS 14.1 build. However, running this on LOS 14.1 fixed an issue with the Google app causing massive battery drain whenever the lockscreen was active, spamming the logs with WindowManager: Layout repeat skipped after too many iterations.

Other people on Reddit appear to have this issue, too, where I originally wrote the above. This seems to be a platform issue, not specific to the Nexus 6, possibly beyond the scope of what Elektroschmock maintains?
[Nexus 6  Original Android Development] paulmerrill:
No, this is what AICP did and the phone became unusable once it hit 40%. What they did was disabled 2 cores and the phone lag was awful. Perhaps adjust the top speed but I'd check it first with Kernel toolkit to see if the use is ok, then perhaps set it up in the kernel.
[Nexus 6  Original Android Development] flakinarist:
I freshly installed the 0528 build with MindTheGapps.

Unfortunatelly I am not able to find the camera app inside the app drawer...

But I can start it from the lock screen.

Is there anything I can do to get it into the drawer?

Thanks!

---------- Post added at 02:58 PM ---------- Previous post was at 02:17 PM ----------

Another question:

On my Nexus9 after installing LOS 14.1 (no gapps) I noticed:

- email app has exchange and push mail

On my Nexus6p and Nexus 6 after installing LOS 15.1 (MindTheGapps) I noticed:

- email app has no exchange and no push mail

Is it possible to have at least push mail inside the email app?

(Could have something to do with gapps?)

Thanks!
[Nexus 6  Original Android Development] ReedN:
I find that when I intend to turn off the phone with the power button it often goes to the camera. Is there any way to disable the camera shortcut via multiple presses of the power key?

Great ROM, thanks for all your work!
[Nexus 6  Original Android Development] CapnPez:
Go to settings > System > Gestures > Jump to camera and disable.
[Nexus 6  Original Android Development] wisnu666:
omg, i cant wait this Lineage OS 15.1 with this tweakkkkk!
[Nexus 6  Original Android Development] acex1:
I've read that tweaking the mixer_paths.xml file under the /system/etc folder can improve speaker/headphone volume. My problem is that there is no such file under this folder. Is it somewhere else? I am on 15.1 rom.
[Nexus 6  Original Android Development] Elektroschmock:
Perhaps you shouln't 'tweak' anything if you're not able to find the file. :p
[Nexus 6  Original Android Development] MartinN6:
/system/vendor/etc/

..but you are right, Elektroschmock :)
[Nexus 6  Original Android Development] hixutu:
What are the plans of fixing the broken updater? Worked fine in LineageOS 14.1. Broken since 15.1
[Nexus 6  Original Android Development] h4wk3y:
Please, does anybody have an experience with installing APTX support files into that Lineage? Is it working OK? Thank you!
[Nexus 6  Original Android Development] gandeepan:
Getting the best battery backup out of this device,

More than 3-4.30 hrs of screen on time

With more than 1.45hrs of calling.

...latest 28 may build..

Nice ROM,

Have disabled ambient display, enable double tap to wake which is little buggy at times(does not wake at first double tap to be accurate, )

Waiting for the battery core limiter update in the post which I think might give stable 5hrs + screen time.
[Nexus 6  Original Android Development] dahawthorne:
Less-than-perfect double-tap-to-wake is not the fault of this excellent ROM. When the N6 first came out 3.5 years ago the story was that Google pulled the implementation because the hardware didn't allow a 100% success rate. Me, I'm happy to quad-tap until it wakes up... ?

And since I'm here, thanks to Elektroschmock for this ROM, the first Oreo ROM that I've tried that does 100% of what I want and has been rock-solid since I first installed it. Really great job.
[Nexus 6  Original Android Development] SteveYoungs:
You'll have to expand on what you mean by "broken" because everything in the updater works perfectly for me (and I'm sure for others, too).
[Nexus 6  Original Android Development] paulmerrill:
Not for me, downloads, reboots into recovery but doesn't flash, TWRP 3.2.1. Any ideas how to fix?
[Nexus 6  Original Android Development] wavedashdoc:
[MENTION=3383960]Elektroschmock[/MENTION] here is a log file from right before the phone rebooted using YouTube TV with current 5.28.18 release.
[Nexus 6  Original Android Development] SteveYoungs:
If you have skipped any release from the final 14.1 to current 15.1 you could try...

1. Clean flash the last 14.1 release + current Opengapps for 7.1.

"Clean flash" == Wipe dalvik, cache, system, data (don't touch internal)

2. Get that to boot. Don't bother yet with setting everything up and making your phone all pretty, just get it booting.

3. Partial clean flash the FIRST 15.1 release + current Opengapps for 8.1.

"Partial clean flash" == Wipe system (don't touch data or internal). You could also wipe dalvik and cache if you want, but probably not necessary.

4. See 2

5. Dirty flash the 2nd, and then each and every 15.1 release in succession (don't skip any).

"Dirty flash" == Don't wipe anything, just flash the sucker.

6. Tidy up, make it all nice and pretty (finish up installing, setting up apps, homescreens etc)

7. Profit.

YMMV, at your own risk, don't blame me if it doesn't work, etc, etc, etc.

I went through these steps on my device just last week (for another reason (PEBKAC)) and there was one release where TWRP tripped up on, but it came good again on the very next one. Sorry, can't remember which.
[Nexus 6  Original Android Development] paulmerrill:
I did not come from 14.1, I cleaned flashed 15.1 and while it downloads and reboots to recovery properly, it just doesn't flash the download. I need to do it manually.
[Nexus 6  Original Android Development] SteveYoungs:
In that case try what I suggested. :)
[Nexus 6  Original Android Development] paulmerrill:
Steve, yes I understand now but don't want to reflash, resetup is just a pain. I'll stay with manual. Eventually I'll go to another ROM at some point and hopefully the problem will fix itself.
[Nexus 6  Original Android Development] shsmani:
Bluetooth battery consumption

Pretty awesome! Good to see BT at 0%, was the BT ON or OFF during your usage cycle? I have a problem where if I leave BT on, it consumes too much battery and drains it to a point where the overall adv of lineage OS is lost. Please advise if you are running into BT draining issues.
[Nexus 6  Original Android Development] k1l:
since the latest BT changes i have massive Battery drain from BT. I am using a android watch with permanent BT connection.
[Nexus 6  Original Android Development] ikramii:
Anyone know how to reduce lag in nexus 6?
[Nexus 6  Original Android Development] paulmerrill:
You need to adjust governor settings. I've done successfully with Kernel Toolkit. You must install on a rooted phone for it to work. However, remember, no lag has an impact on battery life. It's a balancing act. I find that the stock LineageOS setting are not too bad. I've changed the I/O scheduler to ROW and readahead to 512kb.
[Nexus 6  Original Android Development] Elektroschmock:
How do you know that?

Is your battery really draining faster or is BT just on the top of your battery consumption list?

If it's the latter just ignore it.
[Nexus 6  Original Android Development] k1l:
YEs it was in the stats like 150% and the next item was like 5%. I had the n6 connected with audio sink to play some musik the whole day. and after some hours the battery was alreardy gone. i dont have stats, but it should last somewhat longer. and i was running inside and outside the BT range and the watch had some issues to connect properly even when i was in range.

i just flashed a new own daily build and so far it seems like this didnt occur so far. so i dont have any logcat now. so far the BT is most times at 0% at that list.
[Nexus 6  Original Android Development] Sziklián:
Is there any kernel, which supports this ROM and has Kcal settings?
[Nexus 6  Original Android Development] FedericoUY:
I've been on this rom for some days now. But after flashing to 0528 nightly i've been having phone power off when starting apps. Is this a known issue?
[Nexus 6  Original Android Development] athulele:
You don't need KCAL if you're trying to do color calibration. You can use the LiveDisplay menu or KA to edit the settings, LiveDisplay will also give you more granularity over colors.
[Nexus 6  Original Android Development] Sziklián:
LiveDisplay does not support saturation, and Kernel Auditor just does not start for me, it stucks at "Checking information...", while I have root access.

Update: Kernel Auditor finally started to work but no saturation settings available here, because Kcal support needed to appear.
[Nexus 6  Original Android Development] acex1:
You are right! I don't want to tweak anything, but, even if the ring volume is maxed in sound settings, the ringing on the phone is too low. This is what I am trying to fix.

Maybe you can help me.

Thank you!
[Nexus 6  Original Android Development] DarkSearinox92:
Hi guys, i've installed LineageOS on my Nexus 6. I've just power on the device and I have a problem: I can not find the camera app. If I go into the menu all the app, I find it present and asks me if I want to finish it for example, but in the dash, there is not. To reach the camera, I have to activate it from the lock screen. I have read that another user has the same problem but no one has answered on this ...

However, the first time the camera doesn't work... I had to restart the phone and the app started.

I wait your notice! :)
[Nexus 6  Original Android Development] giannis_mathiou:
I managed to get camera application only via clean flash of latest Lineage OS, after that flashing MindTheGapps and prior to first boot dirty flash Lineage OS .zip file once again.
[Nexus 6  Original Android Development] gettes:
Not for me. OS works beautifully.
[Nexus 6  Original Android Development] digitalcircuit:
I also had issues with Netflix HD and YouTube paid video content (the free movies from past promos) causing a lockup and reboot - Netflix triggered once it tried going to 720p or above, YouTube triggered it immediately.

Strangely enough, I had issues after restoring my 14.1 backup, too, but only for one reboot. If there's more testing I could do, I'd be happy to help. I'll just be slow, as this is my daily driver and backup/flash/restore takes time :)
[Nexus 6  Original Android Development] Manya3084:
Yeah, I don't think it was a slam dunk with the HD support for Netflix on the latest build. My phone hard locks when the video starts to play in HD.

Anyone else experiencing the same issue?

I haven't had an issue in youtube, although I was hoping 1440P would show up as an option.

Anyway, everything else has been working well. Looking forward to the power management tweaks :D
[Nexus 6  Original Android Development] wisnu666:
Power management tweakkk :d
[Nexus 6  Original Android Development] kraehetest:
If I want to start play a Netflix Video the phone make a soft reboot.
[Nexus 6  Original Android Development] ExpectedCrayon:
For me it seems to depend on the show. Some shows are working for me fine, but others cause a reboot.
[Nexus 6  Original Android Development] wavedashdoc:
Yeah not sure why YouTube no longer shows 1440p as an option. And I have YouTube Red (Premium). This has been the case for all ROMs, not just lineage. Started happening in April, before that there was no issue. I think it might be server side on Google's end.
[Nexus 6  Original Android Development] digitalcircuit:
There's some changes for DRM queued in Gerrit; hopefully this'll fix the issue?

Gerrit: "shamu: Include DRM service"

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

Gerrit: "shamu: sepolicy: Fix DRM HAL related denials"

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

I don't yet have permission to post outside links...
[Nexus 6  Original Android Development] ExpectedCrayon:
Dope. Linking here for those who want to see.

shamu: Include DRM service

shamu: sepolicy: Fix DRM HAL related denials