yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Netvetra:
Thanks, good work and can't wake up my screen sometimes

Thanks [MENTION=3383960]Elektroschmock[/MENTION], it's a great work.

I upgraded from the latest 14.1 nighties, updated to latest TWRP, wiped system, dalvik, cache; and kept data, flashed 15.1 nightly and opengapps micro; bootup and find all Apps all still work. Then I find when I try to wake up the mobile from sleep the screen still black, even when message, call to app notification comes in, the notification lights works, double click the power button there are vibration for camera works, just the screen still black. Later, I find sometimes it works, sometimes not.

Does anyone have any clue or any direction to start analyse this situation? Thank you!

Btw, another Nexus 6 from stock ROM, fully wiped and upgrade to LOS 15.1 works good. Only the notification LED still not working.
[Nexus 6  Original Android Development] SoTacMatt:
I had that when installing full Gapps. Started over and used built in dialer. Call history was back.
[Nexus 6  Original Android Development] djlesco:
I had the same issue. I updated twrp to the latest version and was able to install no problem after that.
[Nexus 6  Original Android Development] barbara-luise:
Flashing the system from usb drive didn't work for me. twrp gave me an "error 7".

The solution that finally worked for me was:

- In twrp: Selected Wipe and then "Format data". Then in Advanced Wipe Selected Cache, System and Data partitions to be wiped and then "Swipe to Wipe".

- Rebooted into twrp again

- Then installed the latest los 14.1 build (!)

- After that, booted up the system again until the start screen of los 14.1 appeared.

- Booted into twrp again

- TWRP DID NOT ASK ME FOR A PASSWORD THIS TIME!

- Installed los 15.1 following these instructions: https://wiki.lineageos.org/devices/shamu/install

It is worth noticing that twrp stopped asking me for a password after I installed the latest los 14.1 build. Therefore, there must be something wrong with the current los 15.1 build. Perhaps, Elektroschmock could check this out.
[Nexus 6  Original Android Development] Woodensponge:
Updated twrp and installed lineage 15.1 with no problems. Thanks for the advice
[Nexus 6  Original Android Development] Elektroschmock:
We think the problem is with TWRP.

But you only have problems when upgrading from an unencrypted data partition. That's why you should never fiddle with a build. :p
[Nexus 6  Original Android Development] tracker01:
i am having the same black screen issue when i try to wake the phone from sleep.
[Nexus 6  Original Android Development] jaxxes:
Yep, I have that same problem. I use Drupe as well and can see my call history fine there.

---------- Post added at 05:34 PM ---------- Previous post was at 05:22 PM ----------

This worked for me!
[Nexus 6  Original Android Development] WhammyDroid:
[MENTION=3383960]Elektroschmock[/MENTION], I will try this out and report back. Does this need to be reflashed after flashing a LoS weekly update?
[Nexus 6  Original Android Development] wavedashdoc:
I believe [MENTION=4450173]camcory[/MENTION] device tree includes the speakerphone fix as I do not have this issue on AOSP ROMs with his base. ?
[Nexus 6  Original Android Development] mrk2815:
Elektroschmock we appreciate all you do for keeping shamu alive. its not a big deal it will get resolved when you have the time. i don't get some people don' have patience when there is only one dedicated developer keeping a 3 or 4 year old device alive, they expect everything to come down for the old device . If you expect everything ot work then stay on stock rom or dont complain or get a new device if you can afford it.not all can do this and we appreciaet what he devs like Elektroschmock do for devices like Shamu. i am one of those who cant afford a new $600 device every two years and not all new devices have that much improvements then what we have. maybe a few other shiny features or gimmicks, but at the end of the day the nexus 6 can hold its own against anything new out there!!!!!
[Nexus 6  Original Android Development] Elektroschmock:
Thanks, but no need to flash it anymore. It's already included in the last weekly.
[Nexus 6  Original Android Development] paulmerrill:
Is there any way that hot plugging can be enabled, either permanently or via an app? I have both kernel toolbox and kernel adiutor and while they both have settings to enable hot plugging, they both don't work. The cores never go offline.

I've had hot plugging working on other ROMs for the Nexus 6 and it saves significant battery with little impact on performance. Unfortunately, those ROMs were too flaky. LineageOS is much more stable.
[Nexus 6  Original Android Development] athulele:
On the latest weekly, does anyone else have slight lag on touch screen interaction or animations?
[Nexus 6  Original Android Development] SteveYoungs:
Is anyone else experiencing incredibly long load times for widgets after a boot? Long as in multiple minutes (greater than 2 minutes). It's been like this for me since day one of official LOS 15.1 (I never used the betas). It's the same on my son's shamu (also LOS 15.1)
[Nexus 6  Original Android Development] dahawthorne:
I have a pretty cluttered home screen - Nova using tiny icons (yes, I do use many all the time and most at least sometimes... :)), with Advanced Clock Widget at the top and Power Toggles at the bottom. I've just rebooted, and Power Toggles took about 10 seconds, ACW a bit under 30 - and that's including all the background processes like starting wifi and VPN.
[Nexus 6  Original Android Development] SteveYoungs:
OK, so not everyone then. :) Thanks for replying.
[Nexus 6  Original Android Development] pinkfloyd3:
Anyway I can flash u kernel with twrp cuz I don't know how to flash with adb :rolleyes:

Sorry for my bad English
[Nexus 6  Original Android Development] Elektroschmock:
No we don't have a hotplugging driver. I tried several but didn't see much of an improvment. Perhaps I'll get bach to it someday.

I reduced the overly agressive touchboost via mpdecision of 3 seconds to a 500 ms input boost.

I didn't see much of a diffrence in performance, but an improvment in power consumption.

If you're rooted you could play a bit with the inpit boost value. I am interested if you find a value where you don't see this lag.
[Nexus 6  Original Android Development] athulele:
I'll play around with the values and let you know.

EDIT: I am noticing that the CPU isn't properly boosted on every touch. Some touches boost it to 1497MHz, while others don't change the freq. at all.
[Nexus 6  Original Android Development] nilesh0205:
Camera issue after latest patch

Hello [MENTION=3383960]Elektroschmock[/MENTION]

After installing latest patch, camera is broken?. I am not able to use any of the camera apps I have. Google camera app just crashes and other apps (Like Proshot, Open Camera, Manual Camera) inform that not able to use Camera.

Also tried using QR scanner app QR droid, but it also fails.

Thanks
[Nexus 6  Original Android Development] Dani26:
Working here! Try to factory reset, maybe it will help
[Nexus 6  Original Android Development] Elektroschmock:
I have heard of it, but I have never been able to reproduce it.
[Nexus 6  Original Android Development] runekock:
Maybe just a reboot will fix it.
[Nexus 6  Original Android Development] athulele:
[MENTION=3383960]Elektroschmock[/MENTION]

I set the input_boost_ms to 150ms and that helped a bit.

Setting the input boost freq to 1728MHz added additional smoothness. Will report if it has any profound effect on battery life
[Nexus 6  Original Android Development] Elektroschmock:
Huh? Reducing the input boost from 500 ms to 150 ms helps with smoothness?
[Nexus 6  Original Android Development] athulele:
Sorry, I think it was placebo.

Even increasing input_boost_ms to higher than 500 did not alleviate lag.

Increasing boost frequency helped a little but boosting is not being very reliable, some times the cores do not go the the boost clock at all.

I'm using this to monitor the freq

https://play.google.com/store/apps/details?id=com.waterdaaan.cpufloat
[Nexus 6  Original Android Development] Elektroschmock:
I don't think that you're able to benchmark this with apps like these.

I think most of these apps read the values at a defined interval for example every second.

If your touch boost is shorter then this interval you might not see it every time.
[Nexus 6  Original Android Development] wavedashdoc:
If you're looking for getting better performance with next to no sacrifice try these settings out. I've been tweaking and testing multiple suffer setups, here is my latest.

This can be applied to ANY AOSP or Lineage Kernel.

Here are my Values: ( I call these settings "test #21")

CPU Governor:

Interactive

Governor Options:

go_highspeed_load: 93

above_highspeed_delay: 0 1100000:40000 1400000:20000 1700000:0

timer_rate: 20000

highspeed_freq: 729600

timer_slack: 20000

target_loads: 40 300000:40 534960:30 10004880:25 1357320:50 1474800:60 1709760:68 1827240:75 2179680:82 2297160:89

min_sample_time: 60000

boost: 0

max_freq_hysteresis: 80000

CPU boost:

Input boost frequency: 0 (this lets the target loads and above highspeed dictate the needed frequencies instead of an instant scale up to 1479 or higher each touch of the screen)

Min GPU Frequency: 389

Low Mem killer:

Foreground: 29

Visible Apps: 59

Secondary Server: 89

Hidden Apps: 119MB

Content Providers: 148

Empty Apps: 178

I/0

Noop

128kb

CPU Scheduler:

Sched_wakeup_load_threshold: 110

sched_wakeup_granularity_ns: 2000000

sched_wake_to_idle: 10

sched_tunable_scaling: 0

sched_time_avg_ms: 1000

sched_shares_windows_ns: 10000000

sched_rt_runtime_us: 950000

sched_rt_period_us: 1000000

sched_rr_timeslice_ms: 30

sched_nr_migrate: 32

sched_min_granularity_ns: 2250000

sched_migration_cost_ns: 500000

sched_latency_ns: 10000000

sched_child_runs_first: 0

sched_cfs_bandwidth_slice_us: 5000

These settings are tweaked tunnables from the App L Speed ( with some adjustments I've made too). Which is also an app I highly recommend everyone check out. But if you just want to set and forget and not worry about messing anything up, this might be your route.
[Nexus 6  Original Android Development] athulele:
You're right. The app had a setting to reduce the sampling interval. I'll test some more.

I'll also check out these values and report back.
[Nexus 6  Original Android Development] nilesh0205:
rebooted 3-4 times, didn't help :(

Will try to install next weekly to check if that will solve the issue, if not then will try to do factory reset as suggested by [MENTION=3215810]Dani26[/MENTION]
[Nexus 6  Original Android Development] g3shamu:
so there's new official update and it includes the new baseband version. Do I need to flash the modem image separately once it's available? Or LineageOS includes the modem image so it'll be updated automatically once it's merged to LineageOS repo?
[Nexus 6  Original Android Development] ethanhunt123:
wondering the same thing.
[Nexus 6  Original Android Development] Dhalsim43:
Thanks, no more BT crash since update ?
[Nexus 6  Original Android Development] Elektroschmock:
Until someone grabs the download link and I can analyse the image I don't know what is included in the factory image.

If it contains a New bootoader/radio and we need it you have to flash it seperatly.
[Nexus 6  Original Android Development] ethanhunt123:
seems like it's MDM9625_104670.31.05, from what people are reporting, but that's not a new version.... not really sure

https://www.reddit.com/r/nexus6/comments/8lclr5/nexus_6_gets_system_update_today_52218/
[Nexus 6  Original Android Development] dbrickg:
You're right: that's the same radio / baseband that came out in Oct 2016
[Nexus 6  Original Android Development] g3shamu:
so the last 3 characters (2 digits and a letter) doesn't make a difference?

My N6 with LOS says 45R and the new one is 51R.
[Nexus 6  Original Android Development] dansblackcat:
This happened to me on the last build. I solved it by clearing the cache and data for the camera app. then did a restart.

(Also note that I had already uninstalled all other camera apps before clearing the data for the default camera app)
[Nexus 6  Original Android Development] dbrickg:
Yes, of course the last 3 characters make a difference. I don't know why you've still got 45R on your phone. There's probably not much difference, but 51R has been available for a long time. This site is usually pretty good about keeping copies of the latest baseband / radios:

https://xdaforums.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052

You can download the latest and flash via TWRP
[Nexus 6  Original Android Development] g3shamu:
Oh, I see. Thanks. Before I installed LineageOS, I had N6F27M on my N6. I don't know why it wasn't updated to the latest either. :confused:
[Nexus 6  Original Android Development] dbrickg:
I don't think the radio and bootloader are installed with the OS. At least I've always had to update them manually through TWRP. Or at least I *think* I've had to do that :)
[Nexus 6  Original Android Development] dansblackcat:
Same here. Strange
[Nexus 6  Original Android Development] thetallguy:
bluetooth

Hello. One of the things which have annoyed me lately is the connection to my bluetooth portable handsfree units being unreliable. They actually have been disconnecting during phone calls which can be quite annoying.

Using your test kernel for one day with one of the units and making a few calls during the day I can say that I didn't get one disconnection during a call. So it is much better. Also my smart watch still works OK. I have a bluetooth GPS receiver but I haven't tried it yet.

Thank you, please put this in the releases.
[Nexus 6  Original Android Development] paulmerrill:
That should mean different firmware.
[Nexus 6  Original Android Development] kgiri247:
I'm going to have to test this. Every call I've made through my car disconnects and re-connects and has been unusable while in live calls. Is Bluetooth battery reporting still wonky?
[Nexus 6  Original Android Development] ulibube:
Isn't 51 the Verizon-only radio?
[Nexus 6  Original Android Development] asci77:
Always On Ambient Display

Would it be technically possible to make it like that:

A black screen, which acts just like the normal phone, but just text and outlines of icons are shown in white.

I waited for that scince the nexus 6 came out.

For me this was the logical step if you dont want to buy an yota phone.

Thx asci
[Nexus 6  Original Android Development] Elektroschmock:
Possible yes, but pretty shure nobody is interessted in developing it.
[Nexus 6  Original Android Development] asci77:
darn...

because its too difficult?

or

because it makes no sense?

Battery schould last a lot longer if i browse text like that, also readability in direct sunlight schould go up...

good for reading ebooks... i read around 30 terry pratchett ebooks like that on my camera screen while travelling :)
[Nexus 6  Original Android Development] ExpectedCrayon:
Same here. Guess I need to start flashing.

---------- Post added at 02:02 PM ---------- Previous post was at 01:59 PM ----------

My guess is too much dev time for not enough benefit. To have this work in apps would be a pretty substantial change and would probably have a lot of app-specific bugs. There might be a substratum theme that achieves something similar, but again, it may not work perfectly with all apps.
[Nexus 6  Original Android Development] Elektroschmock:
Because it's difficult and would look pretty fugly.

Perhaps this comes close to what you want:

https://review.lineageos.org/#/q/status:open+topic:reader-mode
[Nexus 6  Original Android Development] g3shamu:
The thing is, non-Verizon N6s are getting the radio update with the new official OTA update.
[Nexus 6  Original Android Development] ulibube:
Which makes me wonder if the OTA went out just because some Googler hit the wrong button.
[Nexus 6  Original Android Development] dbrickg:
Yes, 51R was originally just for Verizon users. There was quite a bit of discussion about it in the 14.1 thread when the new radio came out. But note that it doesn't appear to hurt anything for non-Verizon phones to use the 51R radio:
[Nexus 6  Original Android Development] mrk2815:
not a bad idea to have a reader mode . as an option in lineage settings as i have limited vision being low vision i prefer to have dark background with light forground for easy reading.i dont get why google has to do all white bacground.its a pain for people who have vision issues. Also itsa battery drain.if we have all

dark background there is less eye strain an less battery consumption.
[Nexus 6  Original Android Development] CapnPez:
This will likely look weird, but have you tried to do the color inversion setting? It's in settings>accessibility and at the bottom. Alternatively, you can set the display to monochromatic in developer options in the hardware acceleration section and simulate color space.
[Nexus 6  Original Android Development] mrk2815:
yes i have tried the color invertion it works sometimes an it does not work other times.that is hwy i am hoping for a custom rom for android p for nexus 6 shamu as the color invetion has improved as i have played with androi p on a friends pixel and color invertion was working all the time and not a hit or miss situation. That's why i am hoping for a custom rom based of off of androi p which would help people like myself out. would appreciate hte consideration when androi p would be availabe in the andorid open source repositories.
[Nexus 6  Original Android Development] aclb5:
A few updates ago when trying to get Netflix to work I followed these steps: https://xdaforums.com/showpost.php?p=76251925&postcount=281

I deleted liboemcrypto.so. Well, I thought I just renamed it so if I needed it later I would still have it. I can't find it. Can someone upload a copy of it or let me know how I can find the file? Without it, I'm currently able to use the Netflix app and stream at low frame rates and it won't let me download videos.

Thanks!
[Nexus 6  Original Android Development] Elektroschmock:
You can't find it because we deleted it which does the same as renaming it. :p
[Nexus 6  Original Android Development] aclb5:
Ah, well, that'll do it! Thanks for your development work,I appreciate you extending the life of my phone.

Have any plans to try and make Netflix in HD and downloads work? I don't think I'm the only one, not sure about that since the latest updates though.

Thanks!
[Nexus 6  Original Android Development] Elektroschmock:
It's a known issue.

Not shure if it's fixable and it's not top priority for me.
[Nexus 6  Original Android Development] unarj:
tap-to-wake is turning my device on in my pocket now, didn't before the last update. not checking the proximity sensor?
[Nexus 6  Original Android Development] stefan_city:
Mine too, make calls in my pocket, etc.
[Nexus 6  Original Android Development] CyrusReport:
Does this issue have a name? In other words, if I look to the list of recent changes in LineageOS for the Nexus 6 for this issue to be resolved, what would it be named? Trying to switch to LineageOS 15.1 for Nexus 6 but REALLY need to Speakerphone to work properly.

Kindly, let me know. Thank you
[Nexus 6  Original Android Development] dahawthorne:
I have been using 15.1 for a week with many phone calls and I have no echo problems. You should try it to see if your N6 suffers from it - if not, you can restore the TWRP backup that you naturally took before the update... :)
[Nexus 6  Original Android Development] CyrusReport:
Regular calls were perfect the last time I installed LineageOs15.1. Speakerphone calls, and more specifically, Skype and all WiFi calls were echoing...BAD. Have you tried Skype/wifi speakerphone calls?
[Nexus 6  Original Android Development] dahawthorne:
Ah, no, sorry, I missed that it was specifically speakerphone. Next time I try it I'll let you know.
[Nexus 6  Original Android Development] nemanja066:
Terminal:

Active camera processes:

su
ps -Ao comm | grep camera

Restart camera (fix):

su
killall mm-qcamera-daemon cameraserver
[Nexus 6  Original Android Development] CyrusReport:
That would be terrific if you could confirm the echo OR NOT on Speakerphone Wifi/Skype calls with LineageOS 15.1 latest nightly build. Thank you so much
[Nexus 6  Original Android Development] Fred Simm:
I've searched, but haven't found anything. Google play auto updates is set, but not updating. Any ideas?
[Nexus 6  Original Android Development] dahawthorne:
I don't have VOIP or Skype (the new version was so appalling that I wiped it from my phone), but I've tried a normal phone-to-phone call using the loudspeaker and there was no echo on either end. If it's not the phone, perhaps there's a problem with your Skype or VOIP?
[Nexus 6  Original Android Development] CyrusReport:
OK, this is great news. I will be, LORD willing, taking the plunge again to 15.1 today! Thanks again
[Nexus 6  Original Android Development] dahawthorne:
Good luck. Remember rule number one - back up first so that you can easily recover if things go pear-shaped.
[Nexus 6  Original Android Development] Manya3084:
Love the rom, never thought I'd go back to using my Nexus 6 as a daily after replacing a cracked screen.

Anyway, just a quick one, is there any chance that the prevent accidental wake up feature could be added to this rom? I know the LG G3 lineage 15.1 rom supports it, so assume it's already built in lineage os. It uses the proximity sensor to prevent the phone from waking if it is covered.

I find with double tap to wake and also lift to check phone features on, the phone likes to open in my pocket and start calling people at random ?.
[Nexus 6  Original Android Development] duttyend:
New post from the LineageOS team and great news!

Change log 18 : https://lineageos.org/Changelog-18/
[Nexus 6  Original Android Development] CyrusReport:
You are correct. Regular Calls with Speakerphone on are perfect. Everything works great! HOWEVER, any VoIP Calls (Skype, Hangouts, Wire, etc) echo BAD. So I don't know what to say. Any info would be MUCH appreciated
[Nexus 6  Original Android Development] Dernz:
how do you update your lineage os to a newer one?
[Nexus 6  Original Android Development] Elektroschmock:
I know that this feature is built in, and I already tried to enable it, but it wasn't working.

I'm not shure if our sensor isn't fast enough or if the sensor is even enabled while the screen is off.
[Nexus 6  Original Android Development] dahawthorne:
After I discovered my N6 trying to dial Mars, judging from the number of digits on the screen :), I started to carry it screen-outwards. Not an ideal solution, since it makes the screen more vulnerable, but it works. Since it's the electrical signal from skin that causes the interaction, it's likely that this wake-up happens only when the phone is in a pocket with the screen against the skin, so I reckon that carrying the phone screen-inwards in a coat pocket is safe, but not in a trouser pocket.
[Nexus 6  Original Android Development] Manya3084:
Ah yes, I know the trick, but I'm going on holiday in a few days. The alcohol consumption may not help remembering the "put phone in pocket facing out" function in my brain.

I would have thought the feature would activate the proximity sensor once it detects the device has been asked to wake up. The implementation in lineage must be rudimentary.

Anyway, doesn't hurt to ask. Keep up the good work ?
[Nexus 6  Original Android Development] mahir555:
absolutely right .. it is a very annoying bug in all 8.1 roms.

from my experience only calls via IMO messenger are free from this .
[Nexus 6  Original Android Development] CyrusReport:
OK. Great info about IMO! Thank you
[Nexus 6  Original Android Development] ExpectedCrayon:
[MENTION=3383960]Elektroschmock[/MENTION]

It appears that the recent OTA update has been added to the Google dev site. Build number is N8I11F. Oddly, it replaced the last non-Verizon build, rather than being listed as a new build.