Google Pixel October Factory and OTA Images are available to download with 4 functional updates and no security fixes.
OTA: https://dl.google.com/dl/android/aosp/sailfish-ota-ppr2.181005.003-db23e6d5.zip
Factory: https://dl.google.com/dl/android/aosp/sailfish-ppr2.181005.003-factory-727c51f5.zip
Boot image on my Google Drive: https://drive.google.com/file/d/1Krybqgb8BJcTI-67Pi2t9IQflOwW6YZo/view?usp=drivesdk
Changes:
Code:
- Improved performance for certain protected media formats (Pixel 2, Pixel 2 XL)
- Improved stability when using Android Auto (Pixel 2, Pixel 2 XL)
- Improved fast-charging behavior for Pixel devices (Pixel, Pixel XL)
- Modified Call Screening behavior when using Maps Navigation (All Pixels)
October security bulletin: https://source.android.com/security/bulletin/pixel/2018-10-01
So who's ready to fast charge on Pie?
Can someone explain what's the procedure to upgrade from a stock rooted ROM without loosing data? Will the package wipe data or keep it?
danial.aw said:
Can someone explain what's the procedure to upgrade from a stock rooted ROM without loosing data? Will the package wipe data or keep it?
Click to expand...
Click to collapse
If you install the OTA, you will not lose data. If you install the factory image, the installer will wipe everything by default. If you want to keep data, you have to edit the appropriate flash-all script to remove the "-w" switch, then save the script before running it.
Since you're already running stock rooted ROM, I suggest installing the OTA update through the following steps:
Boot to TWRP, go to Advanced -> ADB Sideload
Connect to computer
Follow the instructions at https://developers.google.com/android/ota
Be aware that you will lose TWRP and Magisk, and you'll have to reinstall them. You can reinstall Magisk from within the Magisk Manager app, or you can flash the .zip from TWRP.
Fast charge always worked for me on Pie, I don't get the hype.
still didn't get OTA( anyone on Verizon got it?
a1exus said:
still didn't get OTA( anyone on Verizon got it?
Click to expand...
Click to collapse
Get it and install it manually here:
https://developers.google.com/android/ota#sailfish
Hi, i got this problem that said "fingerprint hardware not available" randomly on my lockscreen when i tried to unlock my phone.
Is this possible to solve by flashing the Factory Images?
kntlbngsd said:
Hi, i got this problem that said "fingerprint hardware not available" randomly on my lockscreen when i tried to unlock my phone.
Is this possible to solve by flashing the Factory Images?
Click to expand...
Click to collapse
there is only one way to find out)
---------- Post added at 02:04 PM ---------- Previous post was at 02:03 PM ----------
post-mortem said:
Get it and install it manually here:
https://developers.google.com/android/ota#sailfish
Click to expand...
Click to collapse
already did) thanks!
a1exus said:
still didn't get OTA( anyone on Verizon got it?
Click to expand...
Click to collapse
Are you enrolled in the Android Beta Program? Once I disenrolled I got the update.
z3pp3lin said:
Are you enrolled in the Android Beta Program? Once I disenrolled I got the update.
Click to expand...
Click to collapse
This also worked for me. I unenrolled and got it immediately.
wfraser207 said:
This also worked for me. I unenrolled and got it immediately.
Click to expand...
Click to collapse
Did the OTA wipe your phone? I was in the Beta program and am still waiting for the monthly security patch with the official version. When I select "Opt Out" on the Beta website it warns me that my data will be wiped...
cucumbers said:
Did the OTA wipe your phone? I was in the Beta program and am still waiting for the monthly security patch with the official version. When I select "Opt Out" on the Beta website it warns me that my data will be wiped...
Click to expand...
Click to collapse
Just install it manually, following Google's instructions. You won't lose data.
If you install the full factory image, you will lose data, by default. If you edit the script to remove the "-w" switch, then even that will not remove data.
Both of the above options require a computer.
post-mortem said:
Just install it manually, following Google's instructions. You won't lose data.
If you install the full factory image, you will lose data, by default. If you edit the script to remove the "-w" switch, then even that will not remove data.
Both of the above options require a computer.
Click to expand...
Click to collapse
Thanks. But I took the plunge, opted out of the Beta and did an OTA update anyway.
Turns out that if you had been in the Beta and got the final update to the official Android P build, you can opt out of Beta and start getting the OTAs again without your data getting wiped. You only get your data wiped if you are still on a Beta build when you leave. I should have remembered all of this, I did the exact same thing with the Android 8 Beta...
kentexcitebot said:
Google Pixel October Factory and OTA Images are available to download with 4 functional updates and no security fixes.
OTA: https://dl.google.com/dl/android/aosp/sailfish-ota-ppr2.181005.003-db23e6d5.zip
Factory: https://dl.google.com/dl/android/aosp/sailfish-ppr2.181005.003-factory-727c51f5.zip
Boot image on my Google Drive: https://drive.google.com/file/d/1Krybqgb8BJcTI-67Pi2t9IQflOwW6YZo/view?usp=drivesdk
Changes:
October security bulletin: https://source.android.com/security/bulletin/pixel/2018-10-01
So who's ready to fast charge on Pie?
Click to expand...
Click to collapse
How to get root and magisk on October update?
Currently on oreo custom ROM rooted with magisk, what's best way to upgrade, can I do so without losing root or will I need to re-root, and will I lose data? Or is it best to save data elsewhere and start completely fresh?
acidspider said:
Currently on oreo custom ROM rooted with magisk, what's best way to upgrade, can I do so without losing root or will I need to re-root, and will I lose data? Or is it best to save data elsewhere and start completely fresh?
Click to expand...
Click to collapse
Update to what? If there is a newer version of your custom ROM, follow the instructions in the relevant thread. If you want to upgrade to a different custom ROM or stock ROM, you'll have to reroot, unless the custom ROM is prerooted. You will likely need to backup and restore all user data.
So I realized that I'm still on the August update. I double checked to make sure I'm no longer enrolled in the beta program and still no updates pop. Am I able to flash the OTA in twrp?
SkinnyT said:
So I realized that I'm still on the August update. I double checked to make sure I'm no longer enrolled in the beta program and still no updates pop. Am I able to flash the OTA in twrp?
Click to expand...
Click to collapse
OTA flashing in TWRP has been hit and miss over the past couple of years (some TWRP/OS versions have worked while others haven't). I honestly don't know the current status, but since you are obviously BL unlocked it is easier to just install the factory image with the flash-all . Delete the -w from the batch file to keep your data of course. Either way, you will need to root again and install TWRP if you want to replace the factory recovery. The only difference is that the factory image will not swap you into the other A/B partition automatically.
SkinnyT said:
So I realized that I'm still on the August update. I double checked to make sure I'm no longer enrolled in the beta program and still no updates pop. Am I able to flash the OTA in twrp?
Click to expand...
Click to collapse
Yes, you can flash the OTA manually. Follow the instructions here. Make sure you are using the latest version of TWRP.
Works fine in twrp.
Sent from my Pixel XL using Tapatalk
Related
I'm still on 4.2.1 on my nexus 4 (been a little slow with the updates...they always fail on me so I have to manually flash). My question is, can I download and flash the latest version (4.4.4) or is it best to update my way up (4.2.2, then 4.3, then 4.4, so on and so forth)?
If you have a flashable zip of 4.4.4 you can update to that. Otherwise I'd update to 4.4 and then incremental.
Make sure everything is up to date, recovery, boot img ect. ect. I had an issue with twrp and had to update it, problem was that the twrp updates would fail. Long story short, had to go the adb route and update my recovery...all went well after that.
Sent by flying midget
matrix0886 said:
I'm still on 4.2.1 on my nexus 4 (been a little slow with the updates...they always fail on me so I have to manually flash). My question is, can I download and flash the latest version (4.4.4) or is it best to update my way up (4.2.2, then 4.3, then 4.4, so on and so forth)?
Click to expand...
Click to collapse
My version was 4.4.2 and I flashed manually to 4.4.4. Only one app needed reinstall. (Hex editor)
See my reply http://forum.xda-developers.com/nexus-4/help/help-ota-t2802250
If you don't mind losing all of your data, then you can simply download the latest factory image from here and install it via one of the toolkits or using fastboot. https://developers.google.com/android/nexus/images
If you're rooted, then you need to update to the latest TWRP, flash the latest radio and bootloader and then install any 4.4.4 ROM and Gapps. A factory reset is recommended however.
TheDarkLord1997 said:
If you're rooted, then you need to update to the latest TWRP, flash the latest radio and bootloader and then install any 4.4.4 ROM and Gapps. A factory reset is recommended however.
Click to expand...
Click to collapse
When on a Nexus 4 the LTE is activated (hack) then flashing the latest radio is not a good idea.
After flashing LTE is gone.
Maybe my reply to another post is helpfull http://forum.xda-developers.com/nexus-4/help/help-ota-t2802250
TheDarkLord1997 said:
If you don't mind losing all of your data, then you can simply download the latest factory image from here and install it via one of the toolkits or using fastboot. https://developers.google.com/android/nexus/images
If you're rooted, then you need to update to the latest TWRP, flash the latest radio and bootloader and then install any 4.4.4 ROM and Gapps. A factory reset is recommended however.
Click to expand...
Click to collapse
Actually, if you download the factory image from google and extract it, you can change the flash-all.bat file so that it doesn't wipe your data.
Right click the file and select "edit" and delete the "-w" between "nutfastboot" and "update" towards the end and it prevents your data from being wiped. From there, you put your device into bootloader mode, then on your computer just right click the folder that you extracted while pressing shift and select "open command window here." Type in "flashboot devices" to make sure the phone is seen by the system, then type "flash-all.bat" and boom, good to go. Just flashed a factory image without wiping the data.
Upgraded right to 4.4.4. Did have to root again and reinstall TWRP, but the Nexus Root Toolkit makes that easy, lol. My only thing is that everything seems to take a bit longer. Transitions are smooth, but there's a lag from when I select something, to when it opens. For example, I use widget locker. When unlocking, it used to immediately unlock. Now it takes about 2 or 3 seconds, but that may just be the app itself. Probably would have been best to flash a little at a time (4.3, then 4.4, then 4.4.4) but oh well. Maybe when I get back from vacation next week, lol.
Also, wasn't concerned about losing LTE because I never really needed it to begin with. I only ever use data when i'm on my lunch at work and it's mostly playing something like Ruzzle or reading news articles. Plus, LTE pretty much cut my battery down to half of what it normally is. I'll be getting a new phone when the next Nexus is released anyway so i'm not too concerned about lack of LTE on my current phone. We got, what, 4 months before the next one is due?
Where was this ages ago?
matrix0886 said:
Right click the file and select "edit" and delete the "-w" between "nutfastboot" and "update" towards the end and it prevents your data from being wiped.
Click to expand...
Click to collapse
Wow! Very thankful for such a simple "hack" :highfive:
I must have missed your argument for and against incrementally updating @matrix0886
knightowl439 said:
Wow! Very thankful for such a simple "hack" :highfive:
I must have missed your argument for and against incrementally updating @matrix0886
Click to expand...
Click to collapse
Except, make sure you take the userdata.img out of the zip too or that'll wipe your device.
Edit, this already has the hacks http://forum.xda-developers.com/showthread.php?p=53533289
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Except, make sure you take the userdata.img out of the zip too or that'll wipe your device.
Click to expand...
Click to collapse
Are you sure, because I didn't take it out. All I did was delete "-w" from the batch file and that was it. Although, I do think I remember something about that as a secondary "just in case you're really worried about it" option.
Happy to be Guinea Pig
I had problems with my launcher @matrix0886 when I just deleted the "-w"
I'll give what @jd1639 said a shot too
Sorry for the late reply. I don't use the stock launcher (I use widget locker for my lockscreen and Apex for my home launcher) so I obviously haven't noticed any problems, lol. But how did the other option go for you @knightowl439?
I just upgraded my Nexus 7 from the factory image. I edited the "-w" out of the update image in flash-all.sh , and expected not to lose my data. In fact I did lose my data. No tragedy, on boot it reinstalled the apps from google play automatically, but I did have to do a bunch of tedious reconfigures for many apps.
Now I'm up to doing the same for my N4, which has a lot more things to configure. Can I avoid losing my data?
My N4 (and the N7) were rooted with various optimizations, which is why I;m using the factory image and not an OTA.
kmandel said:
I just upgraded my Nexus 7 from the factory image. I edited the "-w" out of the update image in flash-all.sh , and expected not to lose my data. In fact I did lose my data. No tragedy, on boot it reinstalled the apps from google play automatically, but I did have to do a bunch of tedious reconfigures for many apps.
Now I'm up to doing the same for my N4, which has a lot more things to configure. Can I avoid losing my data?
My N4 (and the N7) were rooted with various optimizations, which is why I;m using the factory image and not an OTA.
Click to expand...
Click to collapse
I reccomend the CM12 unofficial build located http://forum.xda-developers.com/nex...cyanogenmod-12-unofficial-build-mako-t2936332
No issues to speak of, other than the ASOP keyboard crashes (just install google keyboard on the play store), and you have the disable all the junk ASOP apps. Other than that, it is fast and rock solid stable. I had an issue with the flashable stock rom, and couldn't get it working right.
mattgrantlackey said:
I reccomend the CM12 unofficial build located http://forum.xda-developers.com/nex...cyanogenmod-12-unofficial-build-mako-t2936332
Click to expand...
Click to collapse
Thanks, and I may move to it later. For now I'm looking for advise on getting to the lollipop factory image without erasing my data.
kmandel said:
Thanks, and I may move to it later. For now I'm looking for advise on getting to the lollipop factory image without erasing my data.
Click to expand...
Click to collapse
If you've modified or deleted any system files the ota will not work. You could try flashing the factory image manually. Flash each image except userdata.img. userdata.img will wipe your device as you found out on the n7
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
If you've modified or deleted any system files the ota will not work. You could try flashing the factory image manually. Flash each image except userdata.img.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Well, you could flash stock recovery and just DL the OTA the normal way. Kindof ass backwards but it will work. The "flashable stock ROMs" on here have issues.
mattgrantlackey said:
Well, you could flash stock recovery and just DL the OTA the normal way. Kindof ass backwards but it will work. The "flashable stock ROMs" on here have issues.
Click to expand...
Click to collapse
I doubt it'll work. Sounds like he has modified system files. The ota will fail
Sent from my Nexus 9 using XDA Free mobile app
rather them removing -w, running all img files manually is always best option. My cent though.
Don't run Userdata.img and you should have all your data intact.
kmandel said:
I just upgraded my Nexus 7 from the factory image. I edited the "-w" out of the update image in flash-all.sh , and expected not to lose my data. In fact I did lose my data..
Click to expand...
Click to collapse
The only time I ever heard that removing the -w did not work was when someone thought they removed it, but they only made the change in memory in Notepad++, and never saved the change out to the file. I have used this method successfully with every single update on my Nexus 4 since the phone was released. The OTA never works for me either and I use the factory image because I am rooted with TWRP, however I do remove any other changes (like disabling LTE and uninstalling Xposed) before flashing the factory image. If indeed this really is an issue with Lollipop, then that is a very disturbing mistake that that Google made.
It is a moot point for me anyway, as I wait a few weeks after any new release, or for the next .1 release to be issued, so that all the major bugs are fixed and all affected apps have been upgraded and patched; that way things just go smoothly and I don't have to rip my hair out. In the meantime I keep an eye on these forums for what works and what does not work.
Same as above i have updated through flashing factory img since 4.3 with -w removed and it has never removed/deleted any of my stuff..
OK, I went ahead and did the N4 update via flash-all.sh with the "-w" removed, and it worked with no problem and preserved all data.
I guess the problem I had with my N7 was a glitch in my update. My first attempt hung after a couple of steps, seemingly because the USB connection was through a USB HUB. I moved the connection to a direct USB port and started the flash-all from the beginning. Perhaps that explains why it lost my data, and re-installed the apps google knew about.
At any rate, taking out the '-w" works as expected on the N4 5.0 factory image update.
Hi all,
it's been a while since i started following you and 'till now i haven't had any issue at all.. over the last few days i started experimenting with my N4.
As of now i keep in unlocked, rooted with stock kernel and.. no custom recovery. Bad thing is i've done some crap steps, other than not having a recovery:
1 after unlocking/rooting, i uninstalled some pre-build apps (korean/pying/imeikeyboard/exchange..)
2 everything seemed fine
3 today i tried sideloading 5.1.1 and, of course, it gave me error "couldn't find 'koreanblabla'"
4 i deleted those apps from the ota
5 it passes the apps check but failed upon signature verification - no surprise, i was expecting this.
Now, how do i have that - modified - ota signature ok?
Wipe is not an option, i'd rather buy a new phone lol
Installing those app neither, i'd wanna stick with "my way" : F
I've found these.
jhshi.me/2013/12/02/how-to-create-and-sign-ota-package
source.android.com/devices/tech/ota/sign_builds.html
BTW, along with overclock.net - and reddit lol -, that's one of the best communty driven portal.
Thanks.
urielejh said:
Hi all,
it's been a while since i started following you and 'till now i haven't had any issue at all.. over the last few days i started experimenting with my N4.
As of now i keep in unlocked, rooted with stock kernel and.. no custom recovery. Bad thing is i've done some crap steps, other than not having a recovery:
1 after unlocking/rooting, i uninstalled some pre-build apps (korean/pying/imeikeyboard/exchange..)
2 everything seemed fine
3 today i tried sideloading 5.1.1 and, of course, it gave me error "couldn't find 'koreanblabla'"
4 i deleted those apps from the ota
5 it passes the apps check but failed upon signature verification - no surprise, i was expecting this.
Now, how do i have that - modified - ota signature ok?
Wipe is not an option, i'd rather buy a new phone lol
Installing those app neither, i'd wanna stick with "my way" : F
I've found these.
jhshi.me/2013/12/02/how-to-create-and-sign-ota-package
source.android.com/devices/tech/ota/sign_builds.html
BTW, along with overclock.net - and reddit lol -, that's one of the best communty driven portal.
Thanks.
Click to expand...
Click to collapse
Due to the way 5.0+ does signature checks, if you are even just rooted with stock recovery and no other changes, you have to unroot and revert to stock to install the OTA. It now checks the whole partition and will error if even a byte is out of place. You can either do that, or just flash the images directly, which I find to be the easiest.
Why you don't use factory image and edit flash-all.bat. Remove -w switch and flash. You will lose root and recovery but all apps and data remains.
viktorlj said:
Why you don't use factory image and edit flash-all.bat. Remove -w switch and flash. You will lose root and recovery but all apps and data remains.
Click to expand...
Click to collapse
whatwaitwhat?!
what will that do? is that similar to windows' refresh?
Yes, it will install complete system without wipe. But you must edit flashall.bat and remove -w switch.
what if i reinstall those uninstalled apps? will the integrity check be ok?
If you decide to use factory image there is no integrity check.
mmm
urielejh said:
what if i reinstall those uninstalled apps? will the integrity check be ok?
Click to expand...
Click to collapse
No, because you had to be rooted to remove them in the first place. You have to be unrooted to use the OTA, it has nothing to do with those apps. If you replace, you will just get an error at a different part of the OTA sideload process.
Use the images, as another poster said, you can remove -w from flashall to prevent the wipe (I prefer to always wipe to ensure a clean install however. I don't have anything which I don't backup or can't reinstall quickly)
ok, guys, think i'm done.
using Nexus Root Toolkit i've flashed 5.1.1 update without wiping.
Thanks. pity that i didn't make it the hard way lol
Hi all,
I got the update message(I'm on the RU firmware) but I'm also rooted and twrpd so my question is the following...Will the update process complete without me reverting to stock or will I have to before I go to 6.0?
Cheers
I don't recive the notification but I also wonder
I didn't have the patience to let the OTA download at a crawl while the servers are getting hammered, so I don't know, but I'm guessing it would fail. What I did do was download the full update from the MM thread, and "Install" it with TWRP (wiped cache etc after install). I haven't re-rooted yet, but it's running fine.
Sent from my YD201 using Tapatalk
hippy dave said:
I didn't have the patience to let the OTA download at a crawl while the servers are getting hammered, so I don't know, but I'm guessing it would fail. What I did do was download the full update from the MM thread, and "Install" it with TWRP (wiped cache etc after install). I haven't re-rooted yet, but it's running fine.
Click to expand...
Click to collapse
Did you wiped anything before installing it with the TWRP?
wilver said:
Did you wiped anything before installing it with the TWRP?
Click to expand...
Click to collapse
No, I used the button TWRP shows after install to wipe cache, but I kept my data. It's working fine for me so far but I can't promise it's not better to wipe it.
Sent from my YD201 using Tapatalk
Just check to see if they fixed the download speed problem and it looks like they've pulled the update out!
My download of the update cut out and now I can't see it either.
I stay with the Android 5 for the momment, the differences is worth it?
Well I did what hippy dave did and it seems to be working.
Something I wish could be customized is the bottom buttons on the EPD. The home button on the black theme is way too big :/
Done same as Dave, also installed superus and xposed, all fine =) other doubt I have, sometimes the back screen seens harder to unblock, anyone know why it happens or how to fix it? It have anything to do with the light in the place I am?
Nikolay1243D said:
Hi all,
I got the update message(I'm on the RU firmware) but I'm also rooted and twrpd so my question is the following...Will the update process complete without me reverting to stock or will I have to before I go to 6.0?
Cheers
Click to expand...
Click to collapse
From my fresh experience: install full version from torrent (http://4pda.ru/forum/dl/post/9988519/yotaphone2-user-full-RU1.1.47.zip.torrent) through TWRP, wipe cache, install SuperSU. And after that steps - reboot. All datas and apps on it's places.
https://www.google.com/android/beta
Factory Image direct link: http://storage.googleapis.com/andro.../walleye-ppp2.180412.013-factory-6406b348.zip
Opted in but I'm thinking like other developer previews, I probably should have not taken most current ota to may before. Oh well.. will wait until dp3 lol
...
My phone is rooted, I just received the update to install should I do it or do it manually?
xSunny said:
My phone is rooted, I just received the update to install should I do it or do it manually?
Click to expand...
Click to collapse
Do the OTA because a manual install won't receive future OTA updates.
---------- Post added at 07:37 PM ---------- Previous post was at 07:37 PM ----------
bmwh0r3 said:
Opted in but I'm thinking like other developer previews, I probably should have not taken most current ota to may before. Oh well.. will wait until dp3 lol
Click to expand...
Click to collapse
It should be fine since its the OTA update and not one you have to sideload
TechOut said:
It should be fine since its the OTA update and not one you have to sideload
Click to expand...
Click to collapse
It installed ota over Mays 8.1 update.
installed with custom recovery and magisk root and custom kernel. after reboot all work but lost magisk and xposed.
Where to find sideload ota.zip?
Just finished install and so far so good running very smooth no issues yet!
snowrelyt said:
[]
Factory Image direct link: []
Click to expand...
Click to collapse
Does everyone get this error when trying to download?
"Anonymous caller does not have storage.objects.get access to (I'm not allowed to post links yet )"
I upgraded via OTA (completely stock phone, so beware), but my phone no longer boots (system UI keeps restarting until eventually the phone reboots saying that my data may be corrupt and advising a factory reset), so I want to try flashing the factory image without wiping data, see if it helps.
dextart said:
Does everyone get this error when trying to download?
"Anonymous caller does not have storage.objects.get access to (I'm not allowed to post links yet )"
I upgraded via OTA (completely stock phone, so beware), but my phone no longer boots (system UI keeps restarting until eventually the phone reboots saying that my data may be corrupt and advising a factory reset), so I want to try flashing the factory image without wiping data, see if it helps.
Click to expand...
Click to collapse
Yes, it seems everyone is getting this error. It should be fixed soon.
Stock Verizon Pixel 2 XL here, signed up for Beta and checked for update, got the OTA. Installed just like any other update, works great.
snowrelyt said:
Yes, it seems everyone is getting this error. It should be fixed soon.
Click to expand...
Click to collapse
No not everyone is having this error mine isntalled rebooted and worked like a normal update
Can I update OTA when having TWRP and Magisk?
Mayex said:
Can I update OTA when having TWRP and Magisk?
Click to expand...
Click to collapse
Wouldn't an OTA require the factory bootloader
TechOut said:
No not everyone is having this error mine isntalled rebooted and worked like a normal update
Click to expand...
Click to collapse
I was talking about the error you get when you try to download the factory image.
Anyways, it looks like it's working now.
snowrelyt said:
I was talking about the error you get when you try to download the factory image.
Anyways, it looks like it's working now.
Click to expand...
Click to collapse
Yep, it does. Unfortunately for me, I managed to get myself into this mess with a locked bootloader and now only a full DP2 OTA .zip can maybe save me. Any chance anyone here has one?
Is Google Pay working on Android P DP2? This is what kept me from running DP1.
tibere86 said:
Is Google Pay working on Android P DP2? This is what kept me from running DP1.
Click to expand...
Click to collapse
The App starts up just fine and I was able to set it up without issues but I haven't tried using it for a payment yet
There is a magnifier when moving the text cursor. Finally....
Build is completely smooth and have May security patch. (I was expecting to have an older security patch like in previous betas).
I think is much smoother than Oreo...but let's see in a few days. Animations are nice.
The speed to switch between the last 2 apps is incredibly decreased with the new Home button gesture. But at least is not slow.
Sent from my Pixel 2