yashsingh1/xdaforums huggingface dataset:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] UberFiend:
I'm on Elemental X with stock settings so I could use Magisk.

Another question; is anyone having issues with their alarm(s)?

I've been using AMDroid, Gedup, and the stock Clock off and on for years and I never had a problem with them or any of their features. Yet for the past week I'd be lucky to have even two of the three go off in the morning. [Note I've only been using them at the same time this past week to troubleshoot the issue.] I was using Gedup the past few months and a week ago today it didn't go off on a new alarm. Then I installed AMDroid again on Sunday night and it didn't go off on Monday morning. Throughout the week I'd have all three apps set to go off at two different times in the morning [five minutes between each app] and maybe one would go off, it's a dice roll which one would work. Now this morning I noticed a text I got through Pulse overnight wasn't on my screen when I got up. I know I'm not dismissing these alarms because I have the functions turned off and the apps aren't in my recent list when I wake up.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sheeezy:
Anybody got signal problems?

When I start a call it won't connect and immediatly after my reception is completly gone ?!

Got the right vendor, matching with the ROM build

Edit:

Seems like the reception was the flaw, just tried again and no problems
[Google Pixel ROMs, Kernels, Recoveries, & Other De] chrisf8657:
I'm having an issue where the Voicemail notification sound never plays, and I am never notified of a Voicemail. Does not matter if VVM is on or off, using Verizon. Regular Pixel.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Zizzy2020:
Weird crashing and issues after doing:

Fresh install of 7.1.2 (NKG47S, Aug 2017, T-Mobile, Fi carriers, and Rogers) on google pixel xl from

https://developers.google.com/android/images

Then rom flash.

Am i doing something wrong?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] piperx:
Fastboot andoid 8 to both slots with the -w intact, then flash pure-nexus to both slots
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
Android 8?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Zizzy2020:
Ya umm I can't do Android 8 with T-Mobile yet anyway. So does anyone have 1,2,3 instructions on this from fresh stock ?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
I'd install the stock image for your phone from August. Sounds like you picked the right one for you. Then flash the vendor that PN is built on. (NJH47F)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Zizzy2020:
Ok getting somewhere now...but how exactly would you install this? It's an ISO and i've gotten to used to just doing flashes...All instructions even on the first page just say DO IT....it's like uh....how?

Turns out this may be a defective phone i'm getting it RMA'd. The crashes might not even be related to this so guess i'll let you guys know in a couple of weeks...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Nick80835:
T-Mobile is supported by Oreo. :eek:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] piperx:
Ok, I was on a break at work and misread the post, thought he was on 8 and wanted to go back to pure-nexus

---------- Post added at 07:30 AM ---------- Previous post was at 07:27 AM ----------

I am on 8 and I have t-mobile, no problems
[Google Pixel ROMs, Kernels, Recoveries, & Other De] sublimnl:
Anyone know how to get rid of the Android 8.0 update notification?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Zizzy2020:
which version on the stock android devleopers downloads is it? I only see 2 oreos and from what i've been reading neither of them are designed for t-mobile.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
I'd pick the one that says TMO in the parenthetical
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Zizzy2020:
lol let's just pretend i didn't ask that then
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Nick80835:
Good choice. :eek:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] icrunchbanger:
Sign out of beta.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] sublimnl:
Thanks for the reply. Never been in beta to begin with but I'll give it a look anyway

Edit - verified my device isn't enrolled in beta
[Google Pixel ROMs, Kernels, Recoveries, & Other De] DynamicDonkey:
I had the same issue too. I flashed back to Oreo since it has built in OMS commits and Root is still super easy
[Google Pixel ROMs, Kernels, Recoveries, & Other De] smackdownn:
Stock Oreo has built in OMS? Does magisk work on it? I want to use magisk for Androidpay.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] DynamicDonkey:
I've heard there are issues with Magisk, but Substratum works flawlessly. All you gotta do is root, no custom ROM.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Golf c:
Yes it is confusing. But we're all learning alot about this phone. I wonder if we flash the rom to the inactive slot, it will end up on our original active slot?

Edit: Or is it just better to manually flash everything to both slots when the build number changes?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] FernBch:
Confusing is an understatement. But many of my questions/concerns are being answered as time passes. Now for the $64,000 question. If I do the steps outlined a few posts back two times would it be installed to both slots identically? This is my first dual-slot device so there is still much to learn.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Chronzy:
Seems like flash-all to both slots initially would solve all problems. After that it wouldn't matter. Unless you're going to flash kernels or other mods then I guess you need to know which specific slot.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Golf c:
Haha, good question? I'm just trying to work out the easiest way to accomplish this as we go forward. You know we will get it eventually.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] sn0warmy:
Anyone try Elemental X 1.03 (January Update) kernel with this ROM yet? Curious if there are any issues before I go down the rabbit hole of testing myself.

EDIT: Elemental X 1.03 works flawlessly with this ROM.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] dantexaiver:
Any chance of a built in updater to get Rom updates?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] FernBch:
I am to the point where I'm willing to bet if it was flashed to slot A, then boot into slot A it would flash to slot B.

I have seen the fastboot commands scattered across the forum but is there a place where one could easily find them all in one place?

My last device in particular allowed me the opportunity to learn various ADB commands but I'm not versed with fastboot.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Golf c:
Yeah, I still don't understand why a custom rom is switching slots? Just makes it more confusing. Must have something to do with Google's OTA slot switching? I haven't found a concise Fastboot command document. The problem is they change commands alot.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] FernBch:
You could be right there. From what I have read the "dual-slot" concept is most beneficial to the seamless update process.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] McMarius11:
Hello Devs and Guys, i would love to have one feature (bug fix) The Fingerprint does not work when screen is turned off using a software screen off.

Everytime i lock my device via a software method (action launcher 3 shortcuts) i can't use the fingerprint sensor again :/

it would be awesome if you BeansTown106 could implement shortcuts in PureNexus Settings to lock the device for example hold the back button for 3 seconds to lock the device.

so far the rom is working very well <3
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aholeinthewor1d:
I think beanstown said he thinks it's something in twrp that causes it to flash to the inactive slot.

Also can you clarify what you mean a few posts back about the bootloader, radio, etc.

If you do flashall.bat let's say with NMF26U doesn't that flash EVERYTHING to both slots? Essentially making it completely 100% stock??

Also curious if you could help me figure out the status of what's on my other slot based off of what I did..

-Phone shipped with 7.1 (forget the build)

-Unlocked bootloader

-Took NFM260 OTA

-Took NMF26U OTA

-fasboot boot twrp.IMG

-I was in slot A

-flashed PureNexus so it flashed to slot B

-rebooted phone to log into Snapchat

-rebooted to twrp

-flashed V vendor image

-flashed SU

-rebooted

So if I'm understanding pure nexus is now on slot b. When I rebooted to twrp it switched to slot b so when I flashed The V vendor image it was getting flashed to slot b where PN is

So where do I stand with slot A? What's on it now? Is it possible to boot into A right now or will it not boot?

Thanks
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
Yes, that's what it's all about.

Also, I posted the list of all fastboot syntax this week. I'll look for it.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] k.s.deviate:
As far as I can tell pure nexus was flashed over the O image that was on slot b. So your radio, bootloader etc will be what from that image.

Basically the device was on the a slot when you got it. You took an OTA which applied to the b slot, then you took another OTA which applied to the a slot. Then you flashed pure nexus which applied to the b slot. And so on..

I always (because I'm OCD) flash the full image (flash all) then boot and flash twrp, switch slots, boot back into bootloader and then flash the same factory image again. Then repeat the twrp process and flash my custom ROM. This way I know for certain both partitions have the up to date stuff. This is faster for me than flashing each image to each partion manually.

Again, this is just what I do.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aholeinthewor1d:
So flashall doesn't flash everything to both slots? I thought that was the point of it
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Golf c:
If I understand you, it sounds like your in slot b. Boot into bootloader and it will tell you the active slot, bootloader version and radio (baseband) version. Slot A should be from your last OTA U,

slot B pure nexus,

vendor V,

bootloader O,

pure nexus boot image

radio O

I haven't had the balls to boot inactive slot. Im getting there though. Lol

Fastboot flash-all flashes in your active slot(doesn't switch like OTA and Roms)

Active slot=

System

Boot

Bootloader

Vendor

Radio

Inactive slot=

System_other

I still don't know what system_other is. Hence my apprehension to boot into inactive slot. Hope I understood your post?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Golf c:
That would be handy thanks. Speaking of thanks, I'm all out for the day.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aholeinthewor1d:
Awesome thanks for the reply. So basically flashing a ROM only flashes the boot IMG.. You then still have which ever bootloader, radio, and vender you had previously right?

I already have the V vendor so I'm guessing there's no point in flashing the V bootloader and radios right?

So what do I need to do in order do make sure my A slot is safe. Just make sure its active and flashall? Then I can boot into it right? Err.. Or would that mess up my slot B with PN on it?? Since it would be flashing system_other to it?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] k.s.deviate:
I think system_other is the same system as the image your flashing, and flashes it to the inactive slot so that you have "something" workable there. Imagine messing things up so bad that nothing boots.. but only the active slot gets the updated bootloader, radio etc.

---------- Post added at 01:33 AM ---------- Previous post was at 01:30 AM ----------

So in "theory" flash all "should" flash everything to both slots... But I'm not sure it does. I could be wrong tho, I am far from an expert
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Golf c:
The only thing your missing is the new bootloader, radio hasn't changed. Vendor always changes. Radio and bootloader version can be verified on bootloader screen. Slot A is from your first OTA, you might want to manually update vendor, radio, boot and bootloader in slot A so you can start crack flashing. Haha!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] dantexaiver:
Weird I'm running PN but Google play services just informed me to update to 8.0 and I can't get rid of the notifications
[Google Pixel ROMs, Kernels, Recoveries, & Other De] machoman1337:
Same here! I just blocked the notification for now but that'll interfere with other updates...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] newbie4ever:
can we except the ota while on this rom? or will it mess stuff up?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
No you cannot accept the OTA on a custom ROM. Or even stock with a custom recovery for that matter.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sheeezy:
Yes I also would be interested in how to get rid of the notification without blocking everything from Google play services
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Jesse402:
Could someone explain why I'm not getting an Oreo update notification on the newest version of this ROM? Not that I'd update, it just seems like y'all are all getting it.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
I find myself asking the same thing since I have never seen an update notification running this ROM on this device since it was first released
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Jesse402:
Even weirder, in dev options I have "Automatic system updates" switched ON, but I'm positive that my OS has never done anything of the sort on my several months on PN.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] dantexaiver:
Funny you say that because before I reported this yesterday first thing I did was make sure that feature was off and it was indeed off but now I'm stuck with this notification even after clearing play service cache
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Jesse402:
Scratch everything I said! I've just gotten my own copy of the notification to upgrade. Turned off the setting now just to be safe. Who knows what the determining factors are in getting it.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] thrgk:
Do I flash the vendor image before the rom to update the radio and stuff or before ? I was on Oreo 8 when I rooted and unlock so I think I'm good ?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
Radio and stuff are not in the vendor.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] thrgk:
When I boot it complains of a wrong vendor image and that I need 470D one. Can I just flashed that I. TWRP?

Also can I disable the Android 8 notification pop up also ? Thanks
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Jesse402:
You can flash the correct vendor image in TWRP at any time to make that popup go away.

Your second question has been asked already very recently. Can't disable it without disabling all GP Services notifications or disabling actual GP Services.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] thrgk:
Ok thanks. Btw are there zips for latest radio firmware and bootloader I can flash or should I be ok? I don't have problems but just curious
[Google Pixel ROMs, Kernels, Recoveries, & Other De] egaal:
Hey there!

I'm on the latest PN version but only getting 4 to 5 hours SOT.

Could someone tell me the best settings or share a link to a helpful guide to improve my battery life?

I'm using the Elemental X kernel with stock settings.

Thanks in Advance!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] cambunch:
I get about 3 hours SOT, care to share your settings? :D
[Google Pixel ROMs, Kernels, Recoveries, & Other De] dantexaiver:
I know etas are not allowed to be asked for but this nag to update to official 8.0 is annoying and hope I won't have to put up with it for a few months with out being about to stop it
[Google Pixel ROMs, Kernels, Recoveries, & Other De] scryan:
Not nessisasary even looked for an ETA... I have been on an old version for a while and came here to update and noticed we are a few month old at this point... Checked Bean's post history and it seems his last post was when he uploaded the last version in July?

I know he is more active on G+, so checked there, and other then him reposting an ad for Android file host the other day, he hasn't made any post in a month and a half?

Seems like work and life is taking most his time lately? Am I missing something?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] icrunchbanger:
Chill out ;)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Lazer_Lemon:
I install the rom with the vendor image but it still tells me I have the wrong one. Help plz
[Google Pixel ROMs, Kernels, Recoveries, & Other De] tiboric:
To bad, any one want to pick up where he left? ;)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] cntryby429:
You probably flashed the vendor image without rebooting after flashing the rom. Go back and flash the vendor image now that the newly flashed slot is active.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] daver68:
Out of curiosity for what Paranoid Android is like these days (I miss the old PA), I gave it a spin for a day or two. However, I just couldn't handle the lack of features it has compared to PN. PN might be "stock" in appearance, but I just can't get away from it. Such a great ROM, even if the current build is 1.5 months old.

I'm not complaining about release times here, but I do wish there was a way in Android to just patch the current ROM with the security fixes, much like you can with a desktop Linux flavour, or even Windows and macOS. I'm not a huge fan of having to essentially flash a "full" ROM to receive security updates. But I guess with custom ROMs, it requires devs to customize and release those separately for each variant, and that's just time nobody has...

Either I'm missing something, or you are...

In case I'm being daft and not understanding you, that screenshot shows he's been making commits to what appears to be an Oreo build... so he might have just skipped the previous Sept release altogether in favour of a newer and (subjectively) better Oreo build. And those commits were made "yesterday" as of yesterday, so they are very new.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] clothednblack:
I think that was sarcasm, because of the wink, but who knows lol
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Ezrem:
So I think I just discovered a bug. I have Settings -> Pure Nexus -> Lock Screen -> Scramble Layout enabled. This works fine when unlocking using the touchscreen, I just choose the proper numbers. However, today I connected a bluetooth keyboard. When I wake the phone and type in my PIN, it refuses to unlock. I know my PIN, it is easy to type, I tried it several times. So, I decided to try typing the remapped numbers. For example, if my PIN was 123456, and the lock screen 10-key layout is:

298

136

705

4

I would actually have to type 415096 on the keyboard to unlock my phone.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] tiboric:
Like any one moaning here has ever make a significant contribution to the Dev community.... It was definitely sarcasm.

Arnt we all fed up of entitled people complaining they have to wait for so long for the next release, all the time the Dev is either engrossed in the project, banging there head against a wall because one small change has prevented the build from compiling. Or ........ their own lives.

Sorry ranting. Been a long day .

Oreo ok but I the OST is greatly reduced. May beans it will be enhanced in a custom ROM
[Google Pixel ROMs, Kernels, Recoveries, & Other De] hummel95:
Hi,

do you think it is possible to add Galileo (European GPS) support?

According to internet sources Snapdragon 821 is capable of using Galileo.

Cheers.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] clothednblack:
It happens on every thread and it's sad to see it. This is why a lot of people have moved away from xda to G+, op has much more say as to who stays and who gets the boot for asking for handouts.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] blk_jack:
As a dev I don't really find people asking for updates that big of a deal. I usually give a bit of a heads up in a thread and fellow users inform anyone who hasn't seen it when they ask.

It's really not a big deal, annoying sure, but ultimately it shows people are interested in your project.

As for the self moderation bit, OPs can (and should) moderate comments they don't want showing up in the thread. It might be RDs only but they've been able to self moderate for like at least 6 months now.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] r29:
Hey Guys,

Is there a way to block system update for android o ?? android os data seems to be trying to download and install it. Not sure how that is possible =/
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shinesthru:
Just read the last several pages. There's no fix.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Caleb83:
I've been having connectivity issues with my google pixel, lately.

I've had the phone since October 2016, and I've never had a problem, I always stayed on LTE. I went on vacation at the end of August, and connectivity was still good on vacation, but ever since I got back, I keep losing signal, and the phone keeps switching to 3g despite the fact that I know I have strong LTE service where I am.

I've made several attempts to search for an answer, and I haven't found anything concrete yet. I've tried reinserting my SIM card, clearing network data, and then clearing caches and finally I did a factory reset. I was on the February 15 build of Pure Nexus, so I tried reinstalling that version first, and then I tried upgrading to the latest version with a clean wipe. I've also tried flashing the latest radios, and the problem persists. I'm not sure whether the problem is with this rom or with android in general, or with the pixel in general.

I had a similar issue with my HTC one M8, and I had to reset the entire phone to stock and then reinstall everything again. That's going to be my last-ditch option here, but I'm turning to the wise folks at xda for any suggestions you're able to provide. Thank you
[Google Pixel ROMs, Kernels, Recoveries, & Other De] cntryby429:
Have you done a "network settings reset"? That's what fixed a similar frustrating problem on my old m8. I thought I had done just about everything.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Caleb83:
I did, that's what I meant by "clearing network data." Sorry I wasn't more clear on that, but thanks anyways for trying to help. I do appreciate the effort.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] chili81:
I'm not seeing a description of what the net result of this problem will be. When it finally forces the update (which my last 7.1.xx update did before I went to PN), will it brick or just fail or maybe corrupt things and require a reflash to stock?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] DynamicDonkey:
It should just fail. Android can't flash the update over a custom ROM or root. I may be completely wrong though
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Colday96:
Why is there no linesge os for pixel devices ?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] sd_shadow:
why are you asking in this thread?

please try to stay on topic

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

and there is a Lineage rom, try search
[Google Pixel ROMs, Kernels, Recoveries, & Other De] chili81:
I'm having the same issue. Did you ever figure anything out?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] chrisf8657:
I turned the Premium Visual Voicemail off, then back on in the Verizon account portal on the web. The first time I did it, I was getting the sound again but no transcribed messages. Took turning it on and off a few times to fix it.