yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] savaytse66:
I wanted to also chime in that I am not able to receive inbound calls on the most current 10/5 update, like a few posters above. I am on Verizon. I wish I could provide more technical information, but I'm unable to right now. I can probably get a logcat later this evening, but I wanted to at least chime in that I am also having the problem.

Interestingly, I tried dirty flashing 9/14 over the 10/5 since I was not having any issues on that ROM, and while it would boot to my lockscreen, I could not get past "Phone Is Starting" message.
[Nexus 6 Android Development] hbenz2008:
Try and flash boot.Img from 9/14

No idea about the Verizon thing
[Nexus 6 Android Development] Wizkid:
Nitin, do you thing this IMS registration not successful might be causing no incoming calls on LTE? Just noticing....
[Nexus 6 Android Development] wavedashdoc:
No. I go the IMS to register. The same error appears in the log each time we attempt to turn on VoLTE.
[Nexus 6 Android Development] wavedashdoc:
Here's from the latest Androidx.

Note: calls will still drop to 1xrt on Verizon. So this also didn't work to fix dropped data on calls either.
[Nexus 6 Android Development] Golf c:
Obviously all you guys have the wrong carrier. I never have issues with any of this. Verizon blows.
[Nexus 6 Android Development] sryu120:
Maybe you can fix this problem with this latest modem.

https://xdaforums.com/nexus-6/general/ref-nexus-6-modem-collection-t2969380
[Nexus 6 Android Development] Markeee:
I flashed 9/14 boot.Img after a clean install of 10/5 and it seemed to fix the No Sim - No Service issues but created more mess other issues like dialer and phone not working and no in coming or out going calls

I'm flashed back to 9/14 for now with absolutely no issues

Just hope this No Sim - No Service glitch don't continues on in future builds that would suck big time
[Nexus 6 Android Development] fueled:
The overall device became very fast .

Thnx.

Ps. I didnt do any changes to the voltage parameters, had no guts to do that. :o
[Nexus 6 Android Development] watoan:
Tried 1005 release, seems Cast is not working, enabled wireless display, but it shows no nearby devices found and I have another phone which running Android 8 is showing the device.

For other functions, so far working well, just the mobile network lost at 1st time reboot, but went to 4636 enabled then no more issue.

Thanks.
[Nexus 6 Android Development] wavedashdoc:
Yes wireless display is broken for anything but chromecast display casting.
[Nexus 6 Android Development] Axel85:
For me it's working in every way. I have 3 Chromecast in 3 different network + an Android box with official Google cast support . It's working using Google home , and with the option integrated in the os. Clean flashed last nitrogen release + last popcorn kernel
[Nexus 6 Android Development] magnamentis:
wrong quote and everyone should update firmware including modem etc. from time to time while the newest is quite old already ;)

fully agree, i've been on latest since first day after release and have no issues with current rom version.
[Nexus 6 Android Development] LunaticSerenade:
[MENTION=3777325]wavedashdoc[/MENTION] is your build of AndroidX receiving calls?

Also, since you seem to be pretty close to the development, do you know if anyone is finding success with VoLTE? Just curious.

Nitin, due to not being able to receive calls, I had to go back to the 9/14 build. I will say the 10/05 build was super smooth, and the data connection was significantly more stable (1 - 2 dropouts total, vs the maybe 5 I've experienced on the 9/14 build)
[Nexus 6 Android Development] wavedashdoc:
So there a two pieces to the puzzle.

If you are coming from an 8.1 ROM that had VoLTE turned on, and then flash a Pie ROM, for Verizon, calls won't work. You may be able to make calls, but you won't receive them. So what I had to do to fix this was reflash one of the radios available. After flashing the radio, in the hidden menu I was switched from LTE to 1xrt (CDMA) and in coming calls worked again. So this in theory should work for Nitrogen too. One tell tale sign of this is your carrier should only show 'Verizon' on Pie, if it says 'Verizon Wireless' then calls will fail.

As far as VoLTE. As I've said in this thread only a few days ago, after going through thousands of lines of code and fixing all of the old paths from 8.1 and prior to point to where Pie is looking, I was able to get the IMS registered but VoLTE still failed (and the same errors in the log we're generated). This took about a full day to do and after trying a few different tests I gave up. I think at this point it's beyond updating the paths. It doesn't help that Google has failed to provide good documentation to support the new IMS implementation. (Which might be on purpose)

A side note, Camcory is not going to be as active going forward as his personal life is taking precedent. He and I have tried numerous attempts to get VoLTE working but i think we're both burnt out at the moment. I've spent too much time for too little pay off, and I'm nowhere near any of the devs here as far as experience and skill. I'm just an enthusiast who was taught how to build and start developing.

I welcome anyone to try their hand at fixing VoLTE. I posted the error log in my Thread if anyone's interested in finding the root cause.
[Nexus 6 Android Development] LunaticSerenade:
Thanks for the response. I will give that a try this weekend and see if it works.

I appreciate your efforts on getting it working. I'm not a dev by any means, but I understand burnout, so no worries. RE: Camcory, real life always comes first. Hopefully it's nothing serious, and if it is, hopefully it gets corrected painlessly.

Thanks again for all you do!
[Nexus 6 Android Development] savaytse66:
After reading this, I tried flashing the Baseband cache eraser zip from here: https://xdaforums.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052, and low and behold, I can receive calls again on Verizon. My intent was to reflash the modem, but before doing so, I flashed this zip.

I'm not savvy enough to know why this worked, or if it will work for anyone else. But I am happy to be receiving calls.
[Nexus 6 Android Development] wavedashdoc:
Yeah that works too.
[Nexus 6 Android Development] maksimreder:
What does it do?
[Nexus 6 Android Development] CJ74753:
Bluetooth issues

Would just like to start off saying thank you for all of your hard work, dedication and putting up with everything. I'm having these bluetooth issues.

1. Connecting my headset everytime requires me to actually turn the phones screen on otherwise the headset will just time out. Simply pressing the power button and bringing up the screen causes it to connect.

2. If I have my headset on and my phone rings the audio sound may ring very quietly 1 or 2 times, but all notifications are impacted. I won't know I received a text message or email unless I have my ear piece in.

Are these known issues or is no one else having them and I simply need to reflash everything?
[Nexus 6 Android Development] ExpertMC:
Hello I have found a reproducible bug. When you have a PIN lock longer than four with quick unlock enabled, it slows down and lags after typing in the fifth and sixth digit. This does not happen with a 4 digit PIN.
[Nexus 6 Android Development] mbush78:
Anyone got a link to the previous build, from last month?
[Nexus 6 Android Development] deadcatsrule:
Here's all of them. https://androidfilehost.com/?w=files&flid=121669&sort_by=date&sort_dir=DESC
[Nexus 6 Android Development] mbush78:
Thank you
[Nexus 6 Android Development] watoan:
Thanks for the info, the case sounds like the official 7.1.1 N6F27M stock, its only support chromecast but not for other miracast directly casting devices like LG TV, but NitrogenOS Oreo fixed the problem and I was using that for screen casting, hopefully Miracast somehow can be working with NitrogenOS Pie.

Please advise if there is any workaround for this, Thanks.
[Nexus 6 Android Development] wavedashdoc:
There is currently no work around. Pie changed a lot of things and it will take time to resolve no crucial implementations if fixed at all. If you want these features I suggest going back to Oreo ROM for now. I believe all 8.1 ROMs that I had listed on the 8.1 ROM repo have this enabled.
[Nexus 6 Android Development] ryanallaire:
Haven't been here for a while but I see you produced a pie rom, thanks a lot [MENTION=5044214]nitin.chobhe[/MENTION]!!!!
[Nexus 6 Android Development] sanumaj:
Report after a week of use. For me it's perfect and bug free. ATT, followed the steps on Post 2 video. Have to say this the happiest I've been with this phone. Nitin, thank you!
[Nexus 6 Android Development] Aimless Rambler:
I second this! Made the old N6 work better than my pixel.
[Nexus 6 Android Development] samer4arsenal:
Coming from Lineage 15.1. This room in fantastic.

From two days until now it sounds very good. But there is a problem with MiXPlorer. When I am selecting a folder or a file and tap the information icon the app freezing. I tried different versions of the app and it is the same. So is it a ROM bug?
[Nexus 6 Android Development] Dhalsim43:
Probably this app doesn't support Android 9.0
[Nexus 6 Android Development] Sonvolt99:
Looking at app on Google play it's not been updated since June 2017, so doesn't support pie
[Nexus 6 Android Development] mikevb:
Try disabling "Allow Root" under "More Settings" in the Settings menu. I noticed it took around 5 seconds when requesting root the first time, and it might just time out and do nothing if you're not rooted (don't know whether you are).

The app is from XDA, the version on the play store is very sketchy and possibly malicious. It uses the XDA author's logo/branding to make it seem legit, but it has a different icon in the launcher and is named "Easy File Manager" or something like that.
[Nexus 6 Android Development] rafa90elo:
Debes tener esas 3 opciones activadas en las opciones de personalización.
[Nexus 6 Android Development] samer4arsenal:
You are right [MENTION=7987518]mikevb[/MENTION], I didn't install magisk manager and enabled root for Mixplorer. And now when I enabled the information tab it worked perfectly.
[Nexus 6 Android Development] maksimreder:
Any new development on the signal issue that's plagued Verizon?

Sounds like no issue with GSM, (ATT, TMOBILE)
[Nexus 6 Android Development] rfactor117:
I'm on Verizon... There is NO "plagued" connection issues on Verizon.

I've been roaming in Canada on GSM... No issues to report.

I've been from North Dakota to Nevada... There are no issues to report.
[Nexus 6 Android Development] Markeee:
I'm still having the same Verizon issue hoping the next build will fix it
[Nexus 6 Android Development] maksimreder:
That's great to hear that its a no issue for you, but does not eliminate the issue altogether. I'm not the only one with this, others having reported the same.

I have no problem on Lineage Oreo 15.1 and is what I'm currently running.

I can live with the signal not showing up after reboot, I can manually enable the radio power, but what I can't get by is when the device is showing LTE signal and full service I cannot receive phone calls,

The phone that you trust is unable to meet the basic function of a phone, is a glorified music player.

I tried the few suggestions offered a few pages back, calls would work there after then out of no where, I can't be reached.

Velocity Beta 3 seems to have fixed it, but won't share his success, as its a closed source.
[Nexus 6 Android Development] Markeee:
I clean installed and tested all six 9.0 roms in the below link last week all have there own particular issues but none not just Velocity have the Verizon issue where I loose mobile service after reboot ?

For me this issue is specific to the Nitrogen 10-5 build only last months 9-15 build works fine ?

https://xdaforums.com/nexus-6/gener...ssion-tips-t3829957/post77885448#post77885448
[Nexus 6 Android Development] :
Verizon Signal Loss

First off, thank you very much for the time and effort that you put into this ROM. It looks and works well.

I am also having the signal loss upon reboot problem with Verizon in the US. I had no problems installing the Pie ROM properly with everything working. However, any time I rebooted, data disappeared. A simple dirty flash fixed the problem, but when I reboot again data goes away once more. I went back to a Nitrogen 8.1 ROM because of this. Even with 8.1, I will occasionally lose data when I move away from the wi-fi connection I use at home or work. A simple reboot fixes this issue so it is tolerable.

I am not sure why a small number of people who have bothered to post messages are having this problem. Here is some information that hopefully will help: I bought my Nexus 6 directly from Motorola. I have only had it on the Verizon network. I have used a wide variety of ROMs. I always clean flash. I am using the latest radio, bootloader and TWRP versions. I used to root with SuperSU, but switched to Magisk about a year or so ago. I clean flashed Nitrogen Pie after decrypting and rooted with the latest stable Magisk (17.1). Again, I had no functionality issues with any aspect of the ROM until I rebooted. That's when data disappears and will not come back without dirty flashing.

I hope this possibly helps someone or the next build lacks this problem for those of us that have experienced it.
[Nexus 6 Android Development] NLBeev:
What do you mean with 'data' ?
[Nexus 6 Android Development] :
I mean cellular network signal, 4G, LTE, mobile data. I sincerely apologize if that was unclear.
[Nexus 6 Android Development] Aimless Rambler:
"I will occasionally lose data when I move away from the wi-fi connection I use at home or work"

The above statement makes it appear that you are having wifi connection problems ... not mobile data. If it is in fact mobile data you are referring to (not wifi connection), have you tried toggling the wifi connection (off) and then checking your mobile data connection? Also check your options in Settings >> Network >> Mobile Network >> Advanced >> Access Point Names and check against your suggested APN settings for Verizon (Google it). I know there is a Google setting (somewhere) which when utilized uses both wifi and mobile data in order to hand-off data more effectively (developer options?) but I'd check your APN first.
[Nexus 6 Android Development] CJ74753:
Has anyone experienced any bluetooth issues like I have?

1. Connecting my headset everytime requires me to actually turn the phones screen on otherwise the headset will just time out. Simply pressing the power button and bringing up the screen causes it to connect.

2. If I have my headset on and my phone rings the audio sound may ring very quietly 1 or 2 times, but all notifications are impacted. I won't know I received a text message or email unless I have my ear piece in.

Are these known issues or is no one else having them and I simply need to reflash everything?
[Nexus 6 Android Development] Dixon Butz:
I too had the no signal after booting on Sprint. Missed a couple of texts after the phone spontaneously rebooted and had no signal.

Went back to an 8.1 ROM. Everything is so much faster.
[Nexus 6 Android Development] nitin.chobhe:
Those who are having data issues, can you get me log with following command?:

adb logcat -b radio -v time -d > logcat_radio.log

Nitin
[Nexus 6 Android Development] Fred Simm:
Not sure why I'm not getting vibration for notification. Maybe I've missed a setting. Any ideas?
[Nexus 6 Android Development] Markeee:
Ok I grabbed you 2 log files one when mobile service is enabled and one after reboot when its disabled

Hope that helps
[Nexus 6 Android Development] Fred Simm:
I was on a trip and turned on battery saver. Vibration doesn't work with battery saver on.
[Nexus 6 Android Development] Markeee:
I don't know anything about coding roms or understanding log files but I think you did say you used vendor from dirty unicorns I've clean installed and tested all six 9.0 roms out as of last week and none had this issue only Nitrogens latest 10-5 build has it

I didn't test dirty unicorn I couldn't find any pie build of it out yet but if you point me to the build you grabbed the vendor from I'll test it and see if the same issue popes up :)
[Nexus 6 Android Development] dylix:
I've also been getting random reboots since switching to Pie, what logs can I provide and how?
[Nexus 6 Android Development] nitin.chobhe:
"I've also"??? There are no reboots on the builds that are released.

Check your setup. One way to confirm is, clean flash just the ROM (and nothing else) and reproduce the reboot. If you can, then get the log and share here.

Nitin
[Nexus 6 Android Development] piperthedj:
First of all, Nitin, I can't thank you or your Dev's enough. You continue to bring new life to the N6 and help me maintain my device. Bravo.

I have a Google Voice number and a standard cell number that ring to the same device. I have the Google Voice number set to Ring to the Google app not the default phone app.

On occasion both the Google Voice number and the cell number goes straight to voicemail. I haven't been able to find a pattern to this Behavior yet. Anybody else experiencing this Behavior?

As always Hail to the Dev's

Piper ~ goodny
[Nexus 6 Android Development] magnamentis:
i use bluetooth several hours on/of on motorbike with real wireless in-ears and have not the slightest issues, works absolutely flawlessly on connect as well as on disconnect, even music autostarts as expected like on wired headsets.

could be device related, perhaps you take some logs to document the issue so that someone can look into it to see what happens.

---------- Post added at 08:21 PM ---------- Previous post was at 08:17 PM ----------

check your battery, most RRs are aging battery in combination with N6 typcial voltage vulnerability problems related.

it's not easy to find good battery replacements, be prepared to try out a few and make sure your show allows you to come back and try another, i needed 4 till i got a decent one, 2 of them didn't even charge ;)
[Nexus 6 Android Development] rfactor117:
Because when Battery Saver is enabled "vibration uses battery" Battery Saver is trying to save battery usage.
[Nexus 6 Android Development] Fred Simm:
I was posting that I had found the answer myself. It's quite obvious that's what was happening. I forgot that my battery saver was on for the trip.
[Nexus 6 Android Development] piperthedj:
How did you get your real wireless ear buds to connect to N6?

Cheers
[Nexus 6 Android Development] golpemortal:
Hey guys I just flashed the phone twice with just the rom and I cannot receive calls, I dial just fine but I cannot receive calls and I ran out of options and seeking help from you guys.
[Nexus 6 Android Development] NLBeev:
Check - call forwarding - do not disturb - blocked callers.

Toggle airplane mode and wifi few times.Try another sim.
[Nexus 6 Android Development] githyanki:
Make sure the dialer is set to the default app for phone calls..
[Nexus 6 Android Development] youssefkr:
I don't know if I'm lucky or anything but I had ZERO issues since installing this build (and the build before it). Everything is butter smooth, battery life is great, standby time is also great, no random reboots, no signal drops....

Thanks again nitin :good::good:
[Nexus 6 Android Development] nitin.chobhe:
Thanks!

Just to re-iterate - there are no Random Reboots - there is just 1 user who reported it and I asked him to do some check. We have 2500+ downloads now and no reports of Random Reboots....

Signal drops is only in sparse cases of Verizon supported operators.

Nitin
[Nexus 6 Android Development] raidyne:
[MENTION=5372360]magnamentis[/MENTION]

I'm experiencing the lag, too.

could you post the settings? thanks alot!

Why not revert back to kernel of build 14.09. if it was snappier?
[Nexus 6 Android Development] Johnabis:
I am having this exact problem. I can receive calls only if I select 3g for preferred network type. If it's on LTE then I won't receive calls. I am on tmobile.
[Nexus 6 Android Development] nitin.chobhe:
Anyone else facing this issue? [MENTION=4980030]rfactor117[/MENTION]? [MENTION=5143811]eocobby721[/MENTION]?

Nitin
[Nexus 6 Android Development] montoya.brandon:
Yes I have nitin the exact same thing happens to mine
[Nexus 6 Android Development] NLBeev:
Here in NL no issue with calling.

But the Do Not Disturb options needs to be turned off.
[Nexus 6 Android Development] rfactor117:
I also have a GV number and a standard cell number that ring to the same device. I have the GV number set to Ring to the Google Hangouts not the default phone app.

There is no correlation between cellular calls or GV calls, if you are not receiving cellular calls its most likely a intermittent tower issue, if you are not receiving GV calls its a wifi or data issue.

I have also had sparse missed calls on GV but I just call the them back.

---------- Post added at 04:22 PM ---------- Previous post was at 03:48 PM ----------

I have tested inbound and outbound phone calls on the GSM network and on Verizon network over and over.

Then I removed the sim and swapped with a different sim and performed same test.

Cellular connection, data and phone calls works perfect just like there supposed to.

Nitrogen OS 1005 works flawlessly, As good as my Verizon Pixel 2 XL, No issues to report.

I will however suggest to select to try "Global" as your preferred network type.
[Nexus 6 Android Development] shiftymccool:
I've been holding back because it wasn't a big deal before but I'm getting several random reboots every day. I've looked into getting logs but by the time it reboots there's no logs to get. I'm just adding my voice to the other reboots reports so the notion of "nobody's reporting this" can be dismissed.

I'm on the 9/5 build. Let me know if there is any way to give you more information/logs.

Also, since October 1, there have been reports of reboots by mirekyiv, dylix, RedFodex, and Dixon Butz. Mine makes 5 reports.
[Nexus 6 Android Development] rfactor117:
I have 4 shamu's on Nitrogen OS 1005 with no reboots.

However I have one shamu still on Nitrogen OS 0817 with a poor battery health of approx (55 Percent) it will shutdown if the battery demand is to great.

We have experienced this before, shamu is old, batteries get weak and yet we demand better performance.

What is your battery health?

SS is from my DD orriginal battery.
[Nexus 6 Android Development] shiftymccool:
I replaced my battery a few months ago and, according to AccuBattery, my battery health (when I had about a month of usage with it) was 95%. I had many other battery-related issues that were resolved after the replacement.
[Nexus 6 Android Development] Fred Simm:
For some with the calling or receiving calls issue, I am on a Cricket/ATT gsm sim and since nougat I'm forced to use only one baseband/radio on Shamu. I use MDM9625_104670.31.05.45R. If I don't my phone will not drop to 3g when people call. And a lot of times it won't drop to 3g when I try to call someone. It took hours of experimenting to find the magic baseband for my phone. Sometimes latest is not best.
[Nexus 6 Android Development] rfactor117:
???

Do you substratum installed?

Could it be a installed apk?
[Nexus 6 Android Development] nitin.chobhe:
The first thing that you should do is - Update to the latest release and then report the things.

Also I asked to do this check to [MENTION=3663331]dylix[/MENTION] and waiting for his reply.

Nitin
[Nexus 6 Android Development] rfactor117:
That is really really good info for users... I myself am on 51r and it switches as it should.

Thank you.

---------- Post added at 05:32 PM ---------- Previous post was at 05:28 PM ----------

Sorry ? did not see you are on a old build bud, why are you reporting issues from a month ago.

Lots of changes have happened since then.