yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] alryder:
I understand that a dirty flash is not recommended but I seem to see a lot of people doing it so..... after dirty flashing the ROM do you need to flash GAPPS and Magisk again? Previous ROM's I have been on have scripts that back up and restore GAPPS and reinstall Magisk, does Nitrogen have the same scripts?
[Nexus 6 Android Development] hbenz2008:
No, just flash the Rom. Done.
[Nexus 6 Android Development] alryder:
Perfect, that worked great! Thank you!!
[Nexus 6 Android Development] fueled:
Nitin
[Nexus 6 Android Development] nitin.chobhe:
I don't know now. You'll have to wait patiently.

Nitin
[Nexus 6 Android Development] magnamentis:
it's all about terms:

- a dev usually prefers users to clean flash because it's much less prone to issues and easier to troubleshoot and/or find out real bugs

- dirty flash in fact is the norm and only should issues arise would one clean flash before complaining while mentions of issues are always ok

. in the right tone and with a reasonable amount of information and logs if possible.

- exception is if a clean flash is "MANDATORY" that's would be clearly stated in the update post and compared to that, recommended is more

- to cover one's back, same like the initial post about loosing warranty and that the dev is not responsible.

in short, clean install is safer but for some setups like i.e. mine a real lot of work to get all the details right/same again

while dirty install is in most cases no issues and at times can be avoided for months or even throughout entire API life-cycles.

so clean dirty first but be ready to do a cleany if something's not right

ON THE REBOOT FRONT:

no reboots observed on the themeless setup which would be a dealbraker because i'll never stay white LOL

since i made a backup and a restart in the process i have to wait some longer to see whether RRs happen over several 24h intervalls.
[Nexus 6 Android Development] fueled:
the logcat is running and recording for 9hours now, is it taking too much resources ? like cpu , memory and battery ?
[Nexus 6 Android Development] agentqx2:
I am on google fi and did a full wipe.

The carriers are not provisioning wifi calling to the phone so the wifi calling option does not show at all.

I have tried the google fi dial code to fix with no luck.

Also when it switches to sprint I get a completely different phone number, and the wrong number shows up on peoples caller ID.
[Nexus 6 Android Development] keiyrno:
Did VoLte worked on this build sir?
[Nexus 6 Android Development] rfactor117:
Awesome, someone with the correct... absolute perfect answer.

Thank you. ? ? ?
[Nexus 6 Android Development] hbenz2008:
Keeping it simple works
[Nexus 6 Android Development] ECrispy:
How do we fix this?? I had wifi calling on Nitrogen Oreo. I recently switched to another Oreo rom since I had constant wakelock and battery drain (see my other post). Now my battery life is back but I dont see wifi calling anymore :crying:
[Nexus 6 Android Development] agentqx2:
As far as I understand carriers have the last word on if you're allowed to use wifi calling on their network. For example if you dial *#*#4636#*#* it will bring you to a Testing menu then you can look at Phone information. In the phone information area you can see if your carrier has enabled Wifi Calling Provisioned for you. If this is disabled then android wont even display the Wifi calling toggle/setting. So I assume Google Fi(sprint/tmobile) just dont allow PIE wifi calling yet. On Nitrogen Oreo my permanent fix for keeping wifi calling working was to uninstall the latest Carrier Services update from google play and disable it from updating, then my wifi calling worked fine, every time I updated Carrier Services my wifi calling would be called something else and it would break.
[Nexus 6 Android Development] ECrispy:
I didnt know about this secret code - thanks !!

I just tried it, I'm on Oreo 8.1, in 'phone info' it shows 'wifi provisioning' disabled! I'm on Fi and its using Sprint right now.

So I need to disable 'carrier services' updates? I don't understand why Fi would disable Wifi calling on Oreo?
[Nexus 6 Android Development] dynacopas:
I find no issues. Sundays build works great. Good battery life etc. Any issues I have had. Were because of app installs. I uninstall a few recent apps and restart. Most of the time the issue disappears. Clean installs are the way to go. Thanks to Nitin awesome work. No random reboots no loss of mobile data or network after reboot either.
[Nexus 6 Android Development] nitin.chobhe:
Volte doesn't work on any pie ROM for Shamu.

Nitin
[Nexus 6 Android Development] Markeee:
Ok Nitin I did test Carbon clean installed it skipped setup and problems no loss of mobile network issues for me at all I rebooted 10x and working every-time ?

Don't get me wrong I'm not complaining just trying to help

So far i don't know why but this issue for me is only happening with this rom and none of the other 9.0 roms and it only started in the past 3 releases of Nitrogen previously it worked fine
[Nexus 6 Android Development] nitin.chobhe:
:D That's really strange... The OP of Carbon ROM says it doesn't work for him and it works for you... Leave it.

I think we'll have to live with this for users who still face this issue... As mentioned in last post, it has been fixed for most of the users (who posted on last 2-3 pages) and also for one of the guys from the testing team (only he was facing this issue and he's also on Verizon).

Nitin
[Nexus 6 Android Development] alryder:
FYI: I experienced two random reboots about an hour ago that were five minutes apart. I dirty flashed the 11/12 release so I don't expect support and I'm just throwing this out there for information. The weird thing about the reboots is that they didn't seem like full reboots, I didn't catch the phone in the boot animation either time, they just seemed to be UI reloads. They didn't even reset my uptime widget. Is that even a possibility that they weren't full reboots?
[Nexus 6 Android Development] Dhalsim43:
For me it occurs on idle state and I notice it when I take the phone and get message like "enter pin code after the phone restarted"
[Nexus 6 Android Development] alryder:
My phone was idle too and I only noticed the reboot because I had the phone sitting right in front of me when it happened. I haven't had a reboot when I have been actively using the phone.
[Nexus 6 Android Development] Dhalsim43:
I mean when the screen is off
[Nexus 6 Android Development] alryder:
Me too, the screen was off and it coming on was what caught my attention and made me notice it had rebooted.
[Nexus 6 Android Development] hameedf:
Me too, I had that yesterday, it's not full reboot, I get black screen for few seconds and then it goes to lock screen
[Nexus 6 Android Development] alryder:
Yes, exactly. The only reason I knew for sure that there had been some type of reboot was because my phone momentarily showed "No Service" on the lock screen and when I went to use the phone it told me an unlock was required after a reboot.
[Nexus 6 Android Development] agentqx2:
So after more testing, I found that when you install the Google Fi application it overrides the carrier provisioning.

For example im on Android Pie, if I have Google Fi installed my wifi provisioning is disabled and when I remove google fi app/reboot my wifi provisioning is turn on and the wifi calling option is turned on and available in android which leads me to believe the Fi app is not PIE ready. So I would assume on Oreo you have Google Fi installed which turns off the carrier provisioning and does its own thing, i was just saying the latest carrier services update from the play store broke wifi calling for me on Oreo. Back to Android Pie even after removing Google Fi app and getting wifi calling option back, when I try to place a wifi call in a dead zone like at work, the phone says not cell service please connect to wifi to make a wifi call even though im on wifi. So still no dice for wifi calling working on PIE. It either thinks im not connected to wifi even though i am or im in airplane mode.
[Nexus 6 Android Development] milocj:
In my shamu works perfectly

Enviado desde mi Nexus 6 mediante Tapatalk
[Nexus 6 Android Development] alryder:
The link for your screenshot does not work for me.
[Nexus 6 Android Development] milocj:
VoLTE

Enviado desde mi Nexus 6 mediante Tapatalk
[Nexus 6 Android Development] NLBeev:
My guess is that you did not restore the data partition after flashing the new release.
[Nexus 6 Android Development] alryder:
LOL, another member posted that it wasn't necessary to do so. He said to just flash the update and go so that's what I did. I haven't had the same issue yet since then so I'm going to leave it be for now and if it becomes a bigger problem I'll just do a clean flash. Thanks for the feedback! :)
[Nexus 6 Android Development] NLBeev:
When you've a backup, you could give it a try to restore the data in twrp. (before a clean flash).
[Nexus 6 Android Development] alryder:
Thanks. I do have a backup but it is a direct to PC backup so it is just a backup.ab file.The last time I restored one of those using "adb restore --twrp" I wasn't given a chance to select what partitions were restored, it just restored the entire backup.
[Nexus 6 Android Development] magnamentis:
really not related, you once had one good idea with the themes, i'm still testing that and it looks spot on, no reboots

the other issues is with voltage, both workarounds, not themes = zero reboots till now and higher voltages on idle frequencies reduced them to 50%

hence there could be two or more or a combo of reasons.

i flashed totally dirty and others too, no problems at all, even more responsive as far as i can tell and nor reboots, i download a logcat

several times a day and look for errors and fatals and fails and nothing, no reboots.

i keep it going for another few days to be sure but your mention of the themes was a good throw as i told you, hence let's see.

BTW if it really is the theme, a very reliable theme, updated every 2-3 days, swift black is the name, and that theme never caused any issues on any other device or rom, there must be a reason why it reboots on that theme here, too early to tell with certainty but looks very much like it.

since this rom is over all the best PIE rom for this device, especially since the cell-signal issue is resolved for most of us, it would be a pity to let go of it for such a reason but i can't have it white, no way.

gonna try pixel dust soon once the initial glitches are ironed out, it has more theming options built in.
[Nexus 6 Android Development] dahawthorne:
Not a deal-breaker - my notification LED has stopped in the new version. Dirty flash over the previous version, so not complaining, just asking if other people have working notification lights...? I tried Lightflow Pro, but that also didn't work. Thanks.
[Nexus 6 Android Development] magnamentis:
all working here as always, including lightflow, not changes at all and flashed as dirty as possible, hence not related to that either.

if you use lightflow you should backup your settings in tools and restore them, like this you will always be sure that your setup is identical

and look for the culprit elsewhere.

only thing i can guess is that it could be kernel related because i'm using franco kernel but i'm not saying this, just mentioning the only thing

that is special here, (not default) to be fair.
[Nexus 6 Android Development] dahawthorne:
Ha... I'm also on Franco 76, so I guess that it's just related to my earlier comment about the impossibility of catering for every combination of ROM/kernel/app set... :)

No worries. Maybe it'll sort itself out one day.
[Nexus 6 Android Development] magnamentis:
as i said, i'm on the same combo rom/kernel/app like you and have no issues, hence it will most probably not sort itself, don't give,

make a nandroid and clean install, to see whether it works, if yes, it's worth to set up new, if not consider a hardware failure eventually, just guessing but of course there is a reason, just have to find it ;)
[Nexus 6 Android Development] alryder:
Mine did too with a dirty flash and running the stock kernel. I didn't try Lightflow as it's not a huge deal to me that it's not working. There was one other report a few pages back and I think that was with a clean flash so I decided not to go that route. My LED does flash once during boot so it's not a hardware problem.
[Nexus 6 Android Development] ekring67:
LED Notification option nowhere to be found

I know there has been a little bit of discussion about the LED notification light but for the love of sweet tea in Georgia I cannot find it in my phone. I have been rooting and installing custom roms for about 10 years and clean flashed this ROM after being on the former Nitrogen rom which would give me notification led for notifications. I have seen other people post screenshots of their phones that has the option for the led notification shown along with the notification dot, etc but on my phone it just is nowhere to be found.....not in apps and notifications, not in personalization, nowhere. I even flashed the LED notification I found in this thread and that still didn't solve anything. The led works only when I am charging. I have tried some third party apps and still nothing seems to work. I am just wondering if I am missing something somewhere. build is nitrogen_shamu-9-PQ1A.181105.017.A1 and yes I have Nexus 6.

I have RTFF and some people say it works fine and some have difficulty like myself. I flashed this about 2 days ago and so far everything else works excellent, including camera and the flashlight.

What am I missing?
[Nexus 6 Android Development] ekring67:
lol....I literally JUST posted the same issue. I did a clean flash though.
[Nexus 6 Android Development] Jason928591:
Sign in issue

I tried to flash the latest version of this rom with magisk, and open gapps "stock" and get stuck with trying to login to my gmail account once it boots. The error is the "Google Account Verification" (“This device was reset, to continue to sign in with a google account that was previously synced on this device”) and wont go past that. The thing is, If I reinstall my Oreo rom, I have no issues with signing in. Does anyone else know if this is a known bug?
[Nexus 6 Android Development] githyanki:
Did you change your password recently? Cannot setup a "new" phone shortly after changing password.
[Nexus 6 Android Development] alryder:
This is the first I have heard of this so it is not a known bug, at least with the last two versions. Did you follow the instructions in the OP? -

Go to your recovery

Wipe each partition except internal storage manually (in stead of factory reset)

Flash ROM and Gapps zip

Flash Magisk 17.x if you want root (If you care about safetynet, flash this Safetynet fix)

Reboot - 1st boot takes around 3-4 minutes.

I clean installed that way with the 11/11 version and I had no issues signing in to my Google account.
[Nexus 6 Android Development] Jason928591:
This was a new Email account but didn't change the password at all.
[Nexus 6 Android Development] alryder:
If you don't remove your Google account from your phone before wiping it you need to set it up with the same account that was on it before you wiped it. You can't use a different account.
[Nexus 6 Android Development] Jason928591:
I usually wipe everything then do the adb push command to send over the files to install. I'm gonna give it a try again though.

---------- Post added at 04:15 AM ---------- Previous post was at 04:13 AM ----------

If I remember right, I had been using my new email when I had the Oreo rom installed. I'm gonna try that though, and reflash it and see how it goes.

---------- Post added at 05:02 AM ---------- Previous post was at 04:15 AM ----------

I removed my gmail account prior to flashing this rom and still get the "please sign in with one of the owner's account for this device" error message. I only had this one email account setup as the other one is deleted, and no longer setup on this phone. I did that and followed the directions on the main page. Idk...I guess it was worth a shot either way. Thanks for the help anyways.
[Nexus 6 Android Development] alryder:
That is really strange, hopefully someone will come along with a solution.
[Nexus 6 Android Development] fueled:
yea that was my report of notification led not working for notifications , although it is working for charging the phone , low battery indication and at boot very first screen where it says "Google" it blinks once.

i have clean flashed and tried dirty over it too, it just wont work.
[Nexus 6 Android Development] hbilaiya:
I think, it's our duty towards the devs to report anything which is breaking. This can't be termed as nitpicking. Being a developer myself, improving the project is an ever going process..the more bugs reported, better is the chance of improving it for the masses! :cowboy:
[Nexus 6 Android Development] sucharithan:
Yea Shamu! Auto-Correct! :cyclops:
[Nexus 6 Android Development] GypsyJames:
Help help help!!

Installed per instructions, given error code of "64" for incompatible device for gapps

phone restarted, cycled past nitrogen screen to "To start android, enter your password"

What password??? not the one had previously!!

need this phone to work or I am totally screwed!!

HELP!!
[Nexus 6 Android Development] nitin.chobhe:
You didn't read the OP. It seems your phone was encrypted. All your data is lost now unless you have it copied somewhere else.

You'll have to format your phone.

Nitin
[Nexus 6 Android Development] AmirHRC:
why you didn't read the op . to run any android pie for shamu you must be unecrypted
[Nexus 6 Android Development] dahawthorne:
Nitin, just a thought. Given that people appear too eager to start flashing without properly reading the instructions to the end (duh) might it help newcomers to Pie to have the "you must decrypt" notice above the installation instructions? In 24-point red flashing letters... :)
[Nexus 6 Android Development] NLBeev:
My previous post was about issues of any kind after dirty flashing.

Wiping and restoring the data partition might solve issues...or not...
[Nexus 6 Android Development] GypsyJames:
How do i do that? phone was not encrypted, didnt have any type of password....

have back up of important things
[Nexus 6 Android Development] nitin.chobhe:
lol... I liked the idea ;)

See the video in second or third post.

Nitin
[Nexus 6 Android Development] magnamentis:
this phone is encrypted from day one, if you didn't decrypt it once and it's getting re-encrypted if you flash any rom that doesn't prevent it from being encrypted, has nothing to do with using a password/PIN or not, you have to manually and actively decrypt this phone, rest was said already by other users.
[Nexus 6 Android Development] :
Verizon Reboot data loss & No sim detected - No Service FIX

I had this same problem of losing the data connection with the last two versions of this ROM. I finally found some time to play around with this and here is what worked for me: Settings-Network & Internet-Mobile Network-Advanced - Change Preferred network type to LTE/GSM/UMTS. Access Point Names - I have only one which is Verizon VZWINTERNET. Finally, I set the CDMA roaming mode to Automatic.

These have stuck on reboot and I do not lose data any more. As a bonus, my voicemail number (Google Voice) does not default back to *86 any more like it did on Oreo.

I hope this helps everyone who is struggling with and has experienced this issue. Now I really like Pie and especially this ROM.
[Nexus 6 Android Development] nitin.chobhe:
Thanks!

[MENTION=4872948]Markeee[/MENTION] can you try this and share the results?

Nitin
[Nexus 6 Android Development] Markeee:
I had this same problem of losing the data connection with the last two versions of this ROM. I finally found some time to play around with this and here is what worked for me: Settings-Network & Internet-Mobile Network-Advanced - Change Preferred network type to LTE/GSM/UMTS. Access Point Names - I have only one which is Verizon VZWINTERNET. Finally, I set the CDMA roaming mode to Automatic.

These have stuck on reboot and I do not lose data any more. As a bonus, my voicemail number (Google Voice) does not default back to *86 any more like it did on Oreo.

I hope this helps everyone who is struggling with and has experienced this issue. Now I really like Pie and especially this ROM

No it don't work for me I've tried it before but after i read the post I tried it again it didn't work for me
[Nexus 6 Android Development] nitin.chobhe:
Looks like yours is special problem :confused:

Nitin
[Nexus 6 Android Development] Markeee:
Yeah most likely coz my service provider is Xfinity mobile owned by Comcast but they run off of the Verizon network

So even my apn is different then normal Verizon ones mine is not VZWINTERNET as the guy said above mine is COMCAST.RSLR.VZWENTP
[Nexus 6 Android Development] hbenz2008:
Sorry if I throw this here. Please I need a digitizer if any1 has a broken N6.

Thanks [MENTION=5044214]nitin.chobhe[/MENTION] for a wonderful Rom.

No reboot, no bs.
[Nexus 6 Android Development] :
Amended fix for Verizon data problems

Actually, preferred network type should be LTE CDMA. Otherwise you will not be able to make phone calls.
[Nexus 6 Android Development] rfactor117:
Any one on Verizon or Piggybacks on the Verizon network must have there mobile network set to "LTE / CDMA".

And now without VOLTE it is imperative to have there mobile network set to "LTE / CDMA".
[Nexus 6 Android Development] rfactor117:
SS
[Nexus 6 Android Development] krazzyvishal:
Am the only one facing this glitch? It happens most of the time on waking the device. Happened on previous build, and also happens on the current one.

If you can't understand, it's a screenshot of the lockscreen. The clock and everything disappears, and the status bar appears like that.
[Nexus 6 Android Development] rfactor117:
You mean the double vision?

If so that is because you used a SS of that hot ? looking car ? as your lock screen wallpaper.
[Nexus 6 Android Development] magnamentis:
first thing that comes to my mind is theming ?

since i'm already at it, i did not observe any more reboots (not so random as mentioned earlier) since 3 days now.

if nothing changes for the next 2-3 days and i as well searched to logs for fatal errors in case i missed the reboot visually, i declare the reboots i had as theme related.

that unfortunately does not make it much better since i'm not willing to live with a white interface, especially lockscreen notifications at night and in the morning spoil my else quite stable mood LOL

of course there is a reason in the code but i do not expect or ask for a fix because it's very demanding and time consuming, hence i shall try pixel dust rom that has themes built in.

i tried to start setting up pixel dust with aroma gapps but my twrp says the zip was corrupted and i had not time to make a second attempt.

my question is whether anyone ever had issues with aroma gapps to flash them, if there is something i have to consider in this context.

thing is that i never flashed aroma gapps, only nano since years but due to the rom setup, the dev's recommendation as well as a few great

new features in google phone, contacts and messenger app, i want to try. i know it's OT but i was curious whether there is something special

to aroma gapps or if it will be ok to re-download and try again

cheers [MENTION=9350973]All[/MENTION] and a nice sunday for where it's not already over ;)
[Nexus 6 Android Development] hau_ruck:
Hi after flashing the latest update i got these curved corners around the screen and its cutting the clock and battery icon off anyone knows how can i disable it?
[Nexus 6 Android Development] Knightxda:
NitrogenOS and Stock Gapps (11/16/2018 version), Google Camera did not work for me. However, Open Camera did work. Later, I installed NitrogenOS, and Micro Gapps. Then, I installed Google Camera (4.2.xxxxxx) from play store. Google Camera as well as Open Camera work flawless. Thank you.
[Nexus 6 Android Development] hameedf:
Anyone have issue with partial screenshot?