yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] manish_bhaumik:
Nitrogen OS which I am using doesn't have weekly updates hence I am not aware if the resolution setting gets saved between updates. Even if it doesn't persist, it's easy to change it again. Thankfully the setting stays between reboots.

It does appear that adb is able to change resolution without root. If trying form the phone itself, there doesn't appear be be a non-root method.
[Nexus 6  Original Android Development] tinfox:
I'm on T-Mobile. The Google phone app from the market voicemail section is empty. It used to work on 7.1.1 pure Nexus.
[Nexus 6  Original Android Development] manish_bhaumik:
Doesn't work for me too. I use TMobiles voicemail app.
[Nexus 6  Original Android Development] tinfox:
That's what I'm using as well. I was hoping there was a magic code.
[Nexus 6  Original Android Development] Elektroschmock:
I don't think this is something we want to have.

I also don't see any abnormal jitter or jank. You can always set your animations to 0.5x in developer settings.
[Nexus 6  Original Android Development] dahawthorne:
I agree with Elektroschmock. I bought my N6 because of its fantastic resolution, and I see no point in deliberately downgrading the major feature of the phone. If I wanted just HD then I'd have bought a cheaper phone. Also I checked this out a long time ago and the general consensus was that it had little benefit to battery life, and brought potential risks from altering the native resolution. I'm guessing that any perceived increase in speed is due to the placebo effect.
[Nexus 6  Original Android Development] wavedashdoc:
Lol I have you ever played a PC game? Lowering the resolution allows the GPU and CPU to render less pixels, which in turn provides better performance (better fps) and less impact on them both. I understand there is minimal battery improvement since the screen is still on and the pixels are still lit up. But while the Nexus 6 does well at 2k resolution setting to 1080p via terminal emulator or ADB does improve fluidity ever so slightly and does run the phone a little cooler under more demanding application loads. After all the 805 was one of the first to support quad HD.

This is android, we have options to adjust the dang clock position in custom ROMs, I think anything related to performance improvement even in the slightest should be a consideration. Sorry for the rant.
[Nexus 6  Original Android Development] ExpectedCrayon:
I actually got it to work, but I'm not sure how. Also on TMobile. Might have been a setting. I remember having trouble getting it to work after 15.1 (it worked fine in 14.1), but eventually I got it working again. Sorry I can't be of more help, but at least I can tell you it is possible.
[Nexus 6  Original Android Development] ExoticDylan1:
When updating the nightly builds on lineage os 15 would you recommend dirty or clean flash. I have lineage and gapps 8.1.0 but no root?
[Nexus 6  Original Android Development] tinfox:
I uninstalled the Google phone from the market and enabled the original dialer, went to settings, then voicemail and enabled visual voicemail. Reinstalling the Google dialer will then show your current voicemails, but won't get any new ones.
[Nexus 6  Original Android Development] manish_bhaumik:
[MENTION=3383960]Elektroschmock[/MENTION], please reconsider the resolution settings. It is extremely helpful in making the performance better and surely users would appreciate that on an ageing device. The few apps on the store didn't work out for me.
[Nexus 6  Original Android Development] flakinarist:
This was working for me, too.

Thanks!
[Nexus 6  Original Android Development] mithic:
Hi, a friend bought a used N6 as second phone and as it was in stock rom (7.1.1 N6F27M) and he would like to pass on LOS 15.1.

I told him that have to install one by one all the editions of 15.1 (are 10 if i'm not mistaken) till the latest (that's what I' ve done on mine) but he install directly the latest.(that of June).He hasn't the patiency....

Till now for him everything looks good as he said me. The phone works pretty good...

I'm asking if he missed something (by non installing the first 9 by 10 till now editions of 15.1 LOS) or can go ahead with this way??

Thanks.
[Nexus 6  Original Android Development] dahawthorne:
I was on a different ROM (not stock) and I wiped system, Dalvik, cache, data before installing my first weekly LineageOS 15.1 a few weeks ago. Everything worked fine, and I've dirty-flashed several weeklies since then. The important step is the wipe when making a major change - e.g. from one ROM to another or to a new version such as 14 to 15. You're gaining nothing by updating every weekly from day one.
[Nexus 6  Original Android Development] mithic:
Thanks for reply.

Yes he did all necessary wipes (System,Dalvik,Cache,Data) and N6 works fine...(5-6 hours ago he finished the configuration).I told him that (to install one by one all the releases of 15.1 los) because some previous posts we have had a discussion about TWRP and it's capability to install the downloaded updates... (see post #996)

Any way..we will see next week what TWRP do on this N6.
[Nexus 6  Original Android Development] giannis_mathiou:
They are mentioning as, as I also have, problem to auto update through LineageOS updater without doing anything manually. You can normally download the update through LineageOS update the latest zip reboot to TWRP and manually dirt flash latest ROM, not a single problem with that.
[Nexus 6  Original Android Development] flakinarist:
I dirty flashed over the modified settings and they stayed modified.

(Btw. I did it via adb without root)

As others mentioned: the boot animation is offset and some widgets behave a bit different in size.

Let's see what the feeling and battery says... ;)

Oh... What are the defaults?

1.440 x 2.560

493 or 506 dpi? (On text size small / size smaller)
[Nexus 6  Original Android Development] Manya3084:
I would say this would be a feature that the Los team would need to work on together, not just the power of one man.

I think the new power management tweaks that he is working on will make a better user experience when they are ready to be released. ?
[Nexus 6  Original Android Development] alesfot73:
Hi all.

I have a problem when the N6 is in stand-by.

A random don't restart!

Many thanks
[Nexus 6  Original Android Development] adm1jtg:
You mean randomly won't wake up?

Could be expanded desktop being turned on for Google app causing it search on earlier posts, they're is an adb fix
[Nexus 6  Original Android Development] paulmerrill:
A quick request, I've a little time so decided to see if I can download and compile lineageOS for the Nexus 6 myself. I have followed various directions from the web and all seems to have worked but I'm getting a compile fail very early on. My question is, can someone provide a good/proven set of instructions to download and compile LineageOS 15.1 for the Nexus 6? I'm using Linux Peppermint V 8. I've used these instructions: https://wiki.lineageos.org/devices/shamu/build

but the compile error I get is

[1062/1062] including ./vendor/qcom/opensource/rcs-service/Android.mk ...

ninja: error: 'vendor/motorola/shamu/proprietary/bin/ATFWD-daemon', needed by '/home/pmerrill/android/lineage/out/target/product/shamu/system/bin/ATFWD-daemon', missing and no known rule to make it

17:34:57 ninja failed with: exit status 1

Ideas?
[Nexus 6  Original Android Development] deniz3801:
Hello Guys,

the rom works really good. Good Job.

But when I type this command "*#*#4636#*#*" in the Dialer App and click on Phone Information the App crashs.
[Nexus 6  Original Android Development] MartinN6:
it´s a known issue - happens to ALL oreo-ROM for Shamu
[Nexus 6  Original Android Development] kern3l:
Hi [MENTION=3383960]Elektroschmock[/MENTION]

Regarding the recent commit "shamu: Set bluetooth.enable_timeout_ms to 12 seconds" https://review.lineageos.org/217172

I see that bluetooth.enable_timeout_ms was set to 120000 (2 mins) instead of 12000. Am I missing something ?
[Nexus 6  Original Android Development] Elektroschmock:
Oops thank you!

I'll change that, but it doesn't matter. It only defines how long we wait for libbt to initialize.

What matters is that it's longer then the default 3 seconds.
[Nexus 6  Original Android Development] Fred Simm:
Does los 15 have built in burn in protection? It used to be a display option.
[Nexus 6  Original Android Development] dwardo:
Do you have the Muppets repo for proprietary shamu stuff in your .repo/local_manifest/roomservice.xml (I don't recall that being in the lineage instructions when I also stumbled on such errors...)

See screenshot attached... I'm setup to compile for both sbamu and bacon and roomservice.xml is all that i had to modify (if i remember correctly) in addition to the lineage instructions.
[Nexus 6  Original Android Development] Elektroschmock:
We don't talk about the muppets as it's a legal grey zone.

But if you follow the instructions you don't need to add this repository as the files are extracted from the device.
[Nexus 6  Original Android Development] dwardo:
Well I guess file extraction did not work properly for me (or I did it wrong even with the instructions...) both on shamu and bacon...
[Nexus 6  Original Android Development] orgert:
hello everyone , i just updated to 06/11 build, and noticed Trust , and to my surprise it shows that my phone is decrypted , when i fact i think its encrypted , i checked at security/encryption and there it shows that it is (as i never did anything ) .

also the problem of not being able to update through updater ( [MENTION=2363245]Chace[/MENTION]/ recovery/block.map) is still there, saw some other users here have it, any idea or work around this ? :fingers-crossed:
[Nexus 6  Original Android Development] dbrickg:
likewise: just updated to today's nightly. and likewise, i saw something pop up about "Trust". but after i cleared the notifications, i can't find "Trust" anywhere. what is it? and, also likewise, my phone is still encrypted.

but other than that, none of which matters to me in the least, everything seems to be running well.

cheers!
[Nexus 6  Original Android Development] velishka:
You can find Trust under security settings
[Nexus 6  Original Android Development] FedericoUY:
So nightly 0611 is working ok?
[Nexus 6  Original Android Development] dbrickg:
yes :)
[Nexus 6  Original Android Development] dahawthorne:
First impressions of the 11th build are very good. I just want to comment on the new "Trust". Is this a Lineage item, or is it something new from Google? I got the "Learn more about Trust" notification, and the icon stayed in my notification bar until I eventually pressed it. As commented above, the Trust dialogue is in Settings/Security & Privacy/Trust.

It claims "Root access: Disabled" and "Encryption: Disabled" - neither is true. Fortunately... :)

Edit: Duh... always read the OP... :)

Builddate: 2018.06.12

Changes:

[new] LineageOS's Trust

[new] Spectre V1 patches

[new] june security fixes
[Nexus 6  Original Android Development] paulmerrill:
Ok, so followed the official instructions and on my Peppermint Linux 8 machine and I appear to have built a shamu unofficial ROM! It created the zip file, so on the weekend I will give it a shot. It's pure Lineage OS 15.1, so hopefully it will be near the same as the last release. Boy did it take a long time to compile, hours and hours on my old Linux box but it got there in the end.

Now, my next step is to play around with the kernel, I want to make some tweaks, perhaps introduce a couple of known good governors do another compile and see what I can make happen. Ah to code again after a long long time! I am assuming the kernel code is located under lineage/kernel/moto/shamu. Under there is a whole list of directories and files and lots of Kbuild and Kconfig files.

What I'm looking for is someone to point me to a good guide/tutorial on the web about building and adjusting the kernel. Something that's relatively recent. I've found tutorials dating back to 2012 but that's not so relevant. Can anyone provide some guidance to get me started?

Thanks!
[Nexus 6  Original Android Development] mikevb:
Been having issues with updates auto-installing. Clean flashed the first official 15.1 build and since then, 1 update managed to auto-install, all the others have failed. I read in posts from the end of April that this had to do with an 8.1 ROM encrypting storage, but mine is unencrypted...
[Nexus 6  Original Android Development] ExpectedCrayon:
6-11 build running well here as well! I also have the weird thing where Trust shows the phone as decrypted, yet the security settings show it encrypted. I never decrypted the phone.
[Nexus 6  Original Android Development] Elektroschmock:
Info about Trust:

https://lineageos.org/Trust-me/
[Nexus 6  Original Android Development] athulele:
Probably because this commit was merged after the ROM was built.

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

https://www.cmxlog.com/15.1/shamu/
[Nexus 6  Original Android Development] kern3l:
The changelog seen for a build in cmxlog or download.lineageos.org is not always accurate (read complete), because the changelog is generated based on when the build was queued and not when the build actually started. To know the last commits (for device and kernel) that were included in the build, you need to look at the build logs. For example for the 6/11 build: https://jenkins.lineageos.org/job/android/13087/consoleText

Based on this, the commit https://review.lineageos.org/#/c/217241 was included in the 6/11 build.
[Nexus 6  Original Android Development] giannis_mathiou:
Once you've build the ROM from source, according to this, if it's not against the rules would you mind to share the recovery please?
[Nexus 6  Original Android Development] velishka:
I randomly started losing mobile data when I get off the Wi-Fi. Is it me, rom or T-mobile?

Only restarts helps. I am in NYC.
[Nexus 6  Original Android Development] ExpectedCrayon:
I've had this problem even when I was on stock. Also TMo, NYC. I found that airplane mode for a minute usually fixes it (a quick toggle isn't enough, I have to wait). I've given up on finding a better solution.
[Nexus 6  Original Android Development] paulmerrill:
Me three. I've rebooted to fix but I will try airplane mode approach next time. It happens randomly for me but not very often, perhaps once a week or once every two weeks.
[Nexus 6  Original Android Development] duhec:
I've come back to Oreo to try the 06/11 to see if it's ready to be used everyday and I can confirm the BT drain in the battery stats although no drain is actually occurring. I went to Google settings, deactivated Instant tethering, the default thing to do, to eliminate the "drain" but it's still showing massive BT usage. Then there is still no option to lower the vibrator intensity, but the thing I wanted to ask you is about the notification light.

I noticed that when for instance you are charging the phone and the light is eighter solid red, blue or green, depending on the battery percentage, when you receive a WhatsApp message the light turns white-blue normally but after a small amount of time, if you continue charging, the battery notification light overrides the WhatsApp notification light.

This shouldn't be that way and it's the last bug that is keeping me away from Oreo for now. Is there a setting to make it more important than the battery light?

Other than the abovementioned things the ROM is nice and smooth. :cool:
[Nexus 6  Original Android Development] Lagarde:
6/11 update results. Your mileage may vary. ( [MENTION=3383960]Elektroschmock[/MENTION] )

Good stuff:

- Much smoother than previous version.

- Phone isn't getting nearly as hot.

- A few random reboots I'd gotten with the last version don't occur on this one.

Not so good:

- A lot higher BT drain. Not unreasonable or runaway drain, but still higher. Strangely, it's IDLE drain only. If I'm playing music on BT, drain is low. If I pause the music and leave BT connected, the drain is 2-3 times higher than with music playing. This, of course, makes no sense.

- One incident of LTE suddenly getting the X for no data. Toggled airplane mode and it came right back, but still odd.

Overall, I'd say it's a big improvement, though battery life took a hit.

Thanks again Elektro!
[Nexus 6  Original Android Development] Elektroschmock:
How do you measure drain?

The battery statistics aren't a viable tools to measure it.

I think I know what you mean.

If your device is sleeping and connected to a BT device it is woken up every 12 seconds. There is nothing we can do about it. It's just the way BT works.

Because the system is sleeping most of the time the relative energy 'consumed' by BT is high.

When your device is awake and doing something the relative energy 'consumed' by BT is low.
[Nexus 6  Original Android Development] Lagarde:
Yeah, I don't trust the tools for statistics. I rely solely on "what % did it drop in an hour of playing/idle". That does describe it perfectly as far as the idle usage.
[Nexus 6  Original Android Development] Manya3084:
I have my pebble connected via Bluetooth daily and I haven't had any abnormal battery drain
[Nexus 6  Original Android Development] Lagarde:
As noted, your mileage may vary. Different devices, apps, and luck really play into things. The Pebble may use a better version of BT than my headset, car, or watch...all of which cause bad drain right now for me. Glad it's not impacting everyone, but it's definitely an issue on mine.
[Nexus 6  Original Android Development] Treatcon:
Let me just say... Awesome!! Just jumped from 14 to 15. No issues for the past 6 hours so far. Started with full charge, now at 85%. Love the work, and will support everything you do Team LOS!! Thank you!!!
[Nexus 6  Original Android Development] wisnu666:
already installed the newest nightly. runs very smooth and fluent also the cores can be hotplugged via kernel adiutor :) just wonder where's is the toggle of performance mode? i saw the log that the power profiles is alresdy added. thanks ins advance :)
[Nexus 6  Original Android Development] Elektroschmock:
It isn't added yet, as it depends on binaries which are not available for our device.
[Nexus 6  Original Android Development] paulmerrill:
Recovery Image

I will, I'll just have to do on the weekend, a little rushed at the moment.
[Nexus 6  Original Android Development] runekock:
Maybe if you quantify it some more, Elektro could know whether it is unreasonably high. E.g.: was idle for 3 hours, lost xx% battery.

Do you have any special apps that communicate with your Bluetooth devices?
[Nexus 6  Original Android Development] Elektroschmock:
Thank you for this bugreport. I never noticed it, as I have the charging LED turned off.

I'm already looking at the code and found some oddities.

When I ported the light code to oreo it was based on this commit

https://github.com/LineageOS/android_device_moto_shamu/commit/1a5d059439134aab6d95c595ba4205839ce1fdba

Which gives the impression that each of our LEDs has 20 brightness levels. In reality each LED can either be on or off.

So this leaves us only these 'colors':

red green blue

0 0 0 off

0 0 1 blue

0 1 0 green

0 1 1 cyan

1 0 0 red

1 0 1 violet-blueish

1 1 0 yellow-greenish

1 1 1 whitish
[Nexus 6  Original Android Development] runekock:
From what I read, there is a fourth led "charging" which is also green. But I'm not sure that that is in anyway useful.

More interestingly, [MENTION=6124077]doitright[/MENTION] seems to have had variable light (but still no blink) working back in 2016:

https://xdaforums.com/nexus-6/devs-only/enabling-charging-notification-led-t2960135/post69413948

https://xdaforums.com/nexus-6/devs-only/enabling-charging-notification-led-t2960135/post69425649
[Nexus 6  Original Android Development] Lagarde:
No special apps at all. Tested with just car audio or headset, same results. No other devices connected. Screen off for all testing. Multiple tests, including after reboots.

- Music playing (Pandora) with bluetooth connected: 10-12%/hr

- No apps open, but bluetooth connected: 15-17%/hr

- No bluetooth connected: 6%/hr
[Nexus 6  Original Android Development] R1skNt:
I can't adjust the vibration it's on 81%, tried to change with kernel auditor but no luck
[Nexus 6  Original Android Development] Elektroschmock:
This is way too much, I am seeing 1%/hr with BT connected to a smartwatch, connected to wi-fi and idling on my desk.

Something seems to be really wrong with your setup or your device.
[Nexus 6  Original Android Development] Lagarde:
Interesting. I've had similar drain across every version of 15. Clean installs on most (not all). Slapping BBS on it now to see if I can track what's drawing all the power. Built-in battery stats (yuck) are showing all of the drain as Bluetooth.

Current:

Bluetooth 27%

Apps 1%

System 1%

Mobile network standby 1%

(everything else 0%)
[Nexus 6  Original Android Development] Elektroschmock:
Ah I remember that I had it working back then, but we didn't want to change too much in kernel as we still got Google updates at that time.

I made some changes in kernel and rewrote the light hal.

Now we have brightness control which means we can mix colors. :highfive:

Additionally you're now able to reduce brighness in DND

Notification has a higher priority as the battery light too.

I need to do some more testing as I don't want to break the build on monday.
[MENTION=5040396]Miccia[/MENTION] [MENTION=5848265]npjohnson[/MENTION]
[Nexus 6  Original Android Development] duhec:
The colors are working fine, it's just the priority of notifications I wasn't sure if it was broken or it was meant to be this way.

But as far as I know our notification light consists of two LEDs. So you're saying we have the available colors for the upper and the lower one separately like in the picture below?

(picture borrowed from the internet)

Because in Whatsapp I have the default setting set to white and the upper led is indeed white, while the lower is blue.

So you're saying this is fixed already and will be included in the next build? You really are great, you know that? ;)
[Nexus 6  Original Android Development] Elektroschmock:
Yes the priority is fixed already.

Shamu has 4 LEDs one green LED meant as charging LED

A red, green, blue LED in one case meant as notification LED

We are not using the charging LED, because I couldn't come up with a valid use case.

Previously colors were only working partly, as we only had the combinations I described above. Now we are able to controll the brightness of each of the 3 LED in 256 steps which gives us a better choice of mixed colors.. It still doesn't look perfect, because the LED is strangely placed under the speaker grille in a way it blocks mixing a bit.
[Nexus 6  Original Android Development] wisnu666:
Review about Battery's Performance

i want to tell ya all about the battery performance on this newest nightly build LoS 15.1

i admit that the battery performance is really awesome. at the past time, i used Pure Nexus ROM 7.1.2 and elemental X kernel but the performance is not as good as this LoS. as these pictures that i attached here, you can see that my shamu can stanby (idle state) arround 19h 48 minutes with screen on time nearly reached 5 hours (to be exactly is 4h 56 minutes). i used my phone for youtube, facebook browsing via browser, chat with hangout, and whatsapp. since it can be hotplugged, i turned off the last two cores (core 3 and 4) when the task isn't heavy and turned on the all cores when the task is quite heavy. the performance of the ROM is also very good. fluent and smooth. finally can enjoy this oreo rom with a good battery performance. great job [MENTION=5303006]electros[/MENTION]chmock :D

also if you have with bluetooth which is always taking some percentage of the battery, make sure your location scaning with bluetooth is turned off. see in the attached picture below :)

note : btw i used a new battery so it can reach until 1% :)
[Nexus 6  Original Android Development] ThePhenomenalOne1:
anyway to enable aptx in our shamu?