So I updated without going back in and seeing that Verizon is not working on 9.0.10. I'm stuck signal-less. My question is, can I flash 9.0.7-8( can't remember Wich one came before, I got the international phone, no mclearan.) Also in the process of downloading the open beta. Can I flash these without doing a data wipe?
Same problem here!! Wtf!
Yeah I'll stick with 9.0.7 before they fix this in 9.0.11. why even rush into updating your phone when it's working fine beforehand
YEAH NO GUYS. DONT GO BACK. BOOTLOOP.
However, the open beta gave me service back.
zakkyzombie said:
YEAH NO GUYS. DONT GO BACK. BOOTLOOP.
However, the open beta gave me service back.
Click to expand...
Click to collapse
Yah debating if I should load beta or wait for fix. I need phone for office calls tomorrow.
Artnig said:
Yeah I'll stick with 9.0.7 before they fix this in 9.0.11. why even rush into updating your phone when it's working fine beforehand
Click to expand...
Click to collapse
See I tell myself that, but then I see a update and I'm like "hmm...wonder what's new" and there I go doing it. That's how I missed a jailbreak when I did have a iPhone. S8 on Verizon before this and root and shid wasn't a thing, so I updated freely. Now I have to be careful ??
coolguy said:
Yah debating if I should load beta or wait for fix. I need phone for office calls tomorrow.
Click to expand...
Click to collapse
I'd stay till it's stable. I've seen some reports of the beta not fixing it.
zakkyzombie said:
I'd stay till it's stable. I've seen some reports of the beta not fixing it.
Click to expand...
Click to collapse
Loaded beta. Fixed the issue.
Beta fixes issue for me so far, but kinda sucks they missed that I got notification for update so did it and noticed that right away lol
I took the 9.0.10 update on Verizon without issue. No signal loss or anything. Wonder what could be the issue with those losing signal???
Hopefully not major issue but u were lucky one lol I've seen few already with same issue as me but hopefully if it is prob they will fix next update
Glad I saw this thread, I was driving myself crazy trying to figure out why my signal wasn't working
Yeah, going Open Beta didn't fix my signal loss issue. I really don't want to jump through the hoops to do a factory reset and set my phone back up, though, so I'll just run off my TMO work SIM and wait for a fix.
Wipe the cache.
I updated with the full OTA flashed to both slots.
No issues on Verizon.
I'm glad I read the warnings. Thank guys who brave enough to try.
Sent from my OnePlus 6T using Tapatalk
chrisliphart said:
Yeah, going Open Beta didn't fix my signal loss issue. I really don't want to jump through the hoops to do a factory reset and set my phone back up, though, so I'll just run off my TMO work SIM and wait for a fix.
Click to expand...
Click to collapse
Hmm doing beta update fixed mine.
I'm on TMobile with McLaren edition, no issues on 9.0.10
chrisliphart said:
Yeah, going Open Beta didn't fix my signal loss issue. I really don't want to jump through the hoops to do a factory reset and set my phone back up, though, so I'll just run off my TMO work SIM and wait for a fix.
Click to expand...
Click to collapse
You try to flash on both slots?
well, for everyone's reference, i tried to update twrp to official 3.x.x-0 and then updated to the newest oos 9.0.10 on both slots. and i flashed magisk on each. somehow i missed the memo about it borking my vzw service. that being said, i tried to restore my backup of oos 9.0.7 and next thing i knew, i was stuck booting with the red "device is corrupted" message which then booted into twrp with my files locked encrypted. not wanting to lose my data, i decided to fastboot boot twrp 3.x.x-0 (newest, official). this allowed me to see my files again, so i am now copying internal to my *computer. my next step will be to use msm download tool to flash back to oos 9.0.5. wish me luck.
edit- fastboot booting the twrp let me back everything up to my pc. then i used msm tool to flash 9.0.5 successfully. did update to 9.0.7 and now am copying data back. took quite some time, but until i see fixes for vzw, i wont be doing that update. lol.
The main point, though, is signal/service are both back to normal. Victory is mine! lol.
First I've heard of flashing both slots.
zakkyzombie said:
You try to flash on both slots?
Click to expand...
Click to collapse
I updated to 9.0.10 and now my connection drops. This is the first I've heard of flashing both slots. Can you direct me to a guide for this?
Related
Running an Australian N9005.
I was running Temaseks unofficial CM11 build just fine. Got bored and wanted to go back to a more Samsung styled phone.
Decided to flash X-Note. As I'd used it before CM11. It worked fine then.
Attempted to flash X-Note but it wouldn't boot, stuck at initial screen with the Kernel warnings at the top of the screen. Was told it was because I hadn't got the new 4.4 bootloader.
I was told to follow the instructions here: http://forum.xda-developers.com/showpost.php?p=46223545&postcount=2
Which I did.
Using these download links and instructions: http://forum.xda-developers.com/showthread.php?p=49931269
That fixed the boot issue. I suppose I'm not on the 4.4 bootloader.
However when I booted up the stock Polish ROM, the initial Samsung Setup Wizard would crash at the end of the setup and force me back to the start of the setup. Tried ignoring it and just flashing the custom recovery and then XNote. Same issue, the setup wizard in XNote crashes as well.
Someone then told me I should try repartitioning the device using a PIT. I don't know what that is, but it was suggested.
Using this ROM: https://mega.co.nz/#!QVwlVDgJ!QyAxmDMcsIA-56cX_28Ua2aPZLcJATVvdM07LOs0V10
And this PIT: http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Completes successfully.
Same issue............... That being a third separate ROM (official? at that)....
Samsung Setup Wizard crashes...
I even tried flashing XNote and removing the setup wizard just to get past it. That fixes it for about 10 minutes or so. After about 10 minutes of use the phone freezes and I have to hold the power button to force it to restart. If I leave the phone off, it still freezes, as soon as I try to unlock it it freezes and need to force restart.
I really don't know what to do now... Any help guys? I'm trying my best here...
Please, if you need any more information, please ask.
Might not help, but have you wiped your phone clean using custom recovery ( data,cache, dalvik, internal sd ) before flashing xnote or factory reset on recovery when on stock?
Do you have reactivation lock enabled?
Sent from my fingers to your face using my Samsung Galaxy Note 3!
hey_joe said:
Might not help, but have you wiped your phone clean using custom recovery ( data,cache, dalvik, internal sd ) before flashing xnote or factory reset on recovery when on stock?
Click to expand...
Click to collapse
Yes.
nicholaschum said:
Do you have reactivation lock enabled?
Click to expand...
Click to collapse
No.
This has puzzled me, not sure why it's still acting up especially after re-partitioning and flatlining everything.
radicalisto said:
This has puzzled me, not sure why it's still acting up especially after re-partitioning and flatlining everything.
Click to expand...
Click to collapse
Yes indeed. I'm very confused...
So... I don't want to get ahead of myself, but my phone seems to have sorted itself out...
I decided to just send it back to the carrier to get it replaced. So I decided to just flash the official Firmware again. (I accidentally left repartition ticked)
Once it started I thought... Oh ****... But I was sending it back anyway so who cares. (the carrier said they will just swap it for me if they can see it not working)
So I let it finish and turn it on to see what happens, run through the setup to make sure it still crashes at the same spot so I can show them... and it doesn't crash... wtf?
So I flash the custom recovery and XNote... And it seems to be working now. Now freezing, no nothing... I... I don't know...
Crazy, least it appears somewhat sorted lol
radicalisto said:
Crazy, least it appears somewhat sorted lol
Click to expand...
Click to collapse
So far, yeah... I think I got the runt of the litter or something... Haha
Reynbow said:
So far, yeah... I think I got the runt of the litter or something... Haha
Click to expand...
Click to collapse
Just out of curiosity, as I see you have an AU model, did you buy it from Kogan? -- Reason I ask is that they used HK firmware on some models and HK models have issues flashing normal firmware (similar to the issue you had)
radicalisto said:
Just out of curiosity, as I see you have an AU model, did you buy it from Kogan? -- Reason I ask is that they used HK firmware on some models and HK models have issues flashing normal firmware (similar to the issue you had)
Click to expand...
Click to collapse
Not from Kogan, no. From Optus. Pretty standard.
Hello,
As many of you know, lollipop has been released for verizon very recently. I just unrooted my phone fully by using tot method to go back to stock. When I try to install the second update for lollipop, when my phone reboots after installing, it is stuck at the lg logo screen. I have tried factory reset and have used tot method to go back to stock and retry installing lollipop 3 times now. Any help on why the update isn't working would be appreciated, thank you
So it is doing the update to the previous version before Lollipop? Then the Lollipop update itself fails? That is odd, which model is it?
Silentwidow said:
So it is doing the update to the previous version before Lollipop? Then the Lollipop update itself fails? That is odd, which model is it?
Click to expand...
Click to collapse
I have model number vs980 4g. I have a couple pictures which may help. Any advice would be greatly appreciated i really want this update
The same thing happened to me. Had to tot back to stock and Im on 27a not sure if I want to try again
ThatKidDrew said:
The same thing happened to me. Had to tot back to stock and Im on 27a not sure if I want to try again
Click to expand...
Click to collapse
Ive tried 4 times now. I have to keep using tot to go to 11a and update from there. I get the first part of 5.0 (28a) successfully, but the second part always ends up sitting at the lg logo screen. Last thing i know i could try is a factory reset before the second update.
When was the last time your phone was rooted, and were there any problems you had before you went back to stock? Because for me i tried to update and i was unrooted but still had twrp. My phone was stuck going into recovery mode and i had to input that command in the terminal so i could go into download mode.
sk8ergun234 said:
Ive tried 4 times now. I have to keep using tot to go to 11a and update from there. I get the first part of 5.0 (28a) successfully, but the second part always ends up sitting at the lg logo screen. Last thing i know i could try is a factory reset before the second update.
Click to expand...
Click to collapse
I'm on my second try right now waiting for the first part to install. I can try factory resetting before the second part
ThatKidDrew said:
I'm on my second try right now waiting for the first part to install. I can try factory resetting before the second part
Click to expand...
Click to collapse
Ya try that and tell me how it goes please! if that doesnt work i also saw talk of using verizon upgrade assistant
sk8ergun234 said:
Ya try that and tell me how it goes please! if that doesnt work i also saw talk of using verizon upgrade assistant
Click to expand...
Click to collapse
I actually went ahead and started the second part without wiping. My dad updated his G2 to lollipop without any issues and he hasn't wiped the phone since it came out. I think it might be a heat issue so I let it sit in the freezer for a little before I started it the second part of the update. If this doesn't work I'm either gonna try and use the upgrade assistant or go to 27A and then root and flash the 39a firmware through twrp. If you try wiping in between updates let me know how it goes!
ThatKidDrew said:
I actually went ahead and started the second part without wiping. My dad updated his G2 to lollipop without any issues and he hasn't wiped the phone since it came out. I think it might be a heat issue so I let it sit in the freezer for a little before I started it the second part of the update. If this doesn't work I'm either gonna try and use the upgrade assistant or go to 27A and then root and flash the 39a firmware through twrp. If you try wiping in between updates let me know how it goes!
Click to expand...
Click to collapse
What makes you think its a heat issue?
ThatKidDrew said:
I actually went ahead and started the second part without wiping. My dad updated his G2 to lollipop without any issues and he hasn't wiped the phone since it came out. I think it might be a heat issue so I let it sit in the freezer for a little before I started it the second part of the update. If this doesn't work I'm either gonna try and use the upgrade assistant or go to 27A and then root and flash the 39a firmware through twrp. If you try wiping in between updates let me know how it goes!
Click to expand...
Click to collapse
http://lg-phone-firmware.com/mobile/index.php?id_mod=36
You can find the firmware file there, that might help you
sk8ergun234 said:
What makes you think its a heat issue?
Click to expand...
Click to collapse
Just a theory, maybe the phone doesnt want to boot completely because it's too hot. Either way freezing it for a little didnt work so Im gonna have to tot back to 11a and restart and try the upgrade assistant
ThatKidDrew said:
Just a theory, maybe the phone doesnt want to boot completely because it's too hot. Either way freezing it for a little didnt work so Im gonna have to tot back to 11a and restart and try the upgrade assistant
Click to expand...
Click to collapse
Yeah I just tried again without wiping since my phone's temperature seemed fine and it didn't work either lol. Now I have to wait until tomorrow to use the upgrade assistant. Tell me if that works though please
sk8ergun234 said:
Yeah I just tried again without wiping since my phone's temperature seemed fine and it didn't work either lol. Now I have to wait until tomorrow to use the upgrade assistant. Tell me if that works though please
Click to expand...
Click to collapse
I decided to stop updating after the 24A update and Im going to root and install twrp with autorec from here. Then i'm gonna follow this http://forum.xda-developers.com/verizon-g2/development/vs98039a-stock-fw-t3051560 to get to lollipop so I can keep root, recovery, and install custom ROMs
ThatKidDrew said:
I decided to stop updating after the 24A update and Im going to root and install twrp with autorec from here. Then i'm gonna follow this http://forum.xda-developers.com/verizon-g2/development/vs98039a-stock-fw-t3051560 to get to lollipop so I can keep root, recovery, and install custom ROMs
Click to expand...
Click to collapse
alright, im going to try the verizon upgrade assistant tomorrow and post how that goes
sk8ergun234 said:
alright, im going to try the verizon upgrade assistant tomorrow and post how that goes
Click to expand...
Click to collapse
Using the assistant does work for anyone wondering
ThatKidDrew said:
I decided to stop updating after the 24A update and Im going to root and install twrp with autorec from here. Then i'm gonna follow this http://forum.xda-developers.com/verizon-g2/development/vs98039a-stock-fw-t3051560 to get to lollipop so I can keep root, recovery, and install custom ROMs
Click to expand...
Click to collapse
sk8ergun234 said:
alright, im going to try the verizon upgrade assistant tomorrow and post how that goes
Click to expand...
Click to collapse
There are multiple (39a kdz with instructions how to attain root and a recovery, flashable stock 39a zip, and a debloated stock 39a ROM) ways to get on Lollipop but it will help you both to look in the Verizon section.
Sent from my XDABBEB VS982.5 v1.1 with ART using XDA Free mobile app
My phone reboots on DP5 whenever the device locks and it's not charging. It happens in safe mode too, and after factory resets. Any advice?
Thanks!
Tiduszk said:
My phone reboots on DP5 whenever the device locks and it's not charging. It happens in safe mode too, and after factory resets. Any advice?
Thanks!
Click to expand...
Click to collapse
It may be far fetched but check and make sure your case is not putting pressure on Power button.
Witek_M said:
It may be far fetched but check and make sure your case is not putting pressure on Power button.
Click to expand...
Click to collapse
Using a live case, complete cutouts for the buttons. Thanks for offering any help though!
Tiduszk said:
Using a live case, complete cutouts for the buttons. Thanks for offering any help though!
Click to expand...
Click to collapse
I am running N preview since March as daily driver. Just looked at up time. Last reboot was after DP5 update. Try flashing official factory image and see if that cures the problem.
Witek_M said:
I am running N preview since March as daily driver. Just looked at up time. Last reboot was after DP5 update. Try flashing official factory image and see if that cures the problem.
Click to expand...
Click to collapse
Is a dirty flash okay, or should I clean flash?
Witek_M said:
I am running N preview since March as daily driver. Just looked at up time. Last reboot was after DP5 update. Try flashing official factory image and see if that cures the problem.
Click to expand...
Click to collapse
Also, will I still get OTAs if I flash it?
Tiduszk said:
Also, will I still get OTAs if I flash it?
Click to expand...
Click to collapse
Clean flash only. Of your device is enrolled on preview program you will receive OTA when it becomes available.
Witek_M said:
Clean flash only. Of your device is enrolled on preview program you will receive OTA when it becomes available.
Click to expand...
Click to collapse
Okay. Thank you! I'll report back with results
Witek_M said:
Clean flash only. Of your device is enrolled on preview program you will receive OTA when it becomes available.
Click to expand...
Click to collapse
Two new developments. The reboots survived two clean flashes (the first time didn't boot for some reason), and the real cause of the reboots is nothing to do with Google play movies; the phone reboots wherever it locks while connected to a carrier network. I however did find a temporary fix for this, just putting my phone into airplane mode whenever I'm not using it, but that is not sustainable for obvious reasons.
Tiduszk said:
Two new developments. The reboots survived two clean flashes (the first time didn't boot for some reason), and the real cause of the reboots is nothing to do with Google play movies; the phone reboots wherever it locks while connected to a carrier network. I however did find a temporary fix for this, just putting my phone into airplane mode whenever I'm not using it, but that is not sustainable for obvious reasons.
Click to expand...
Click to collapse
Try changing or reflashing the radio?
DJBhardwaj said:
Try changing or reflashing the radio?
Click to expand...
Click to collapse
I'll give it a try, where can I get my hands on it?
Tiduszk said:
I'll give it a try, where can I get my hands on it?
Click to expand...
Click to collapse
Radio flash-able image files are present inside every factory image. What radio version are you currently operating on?
DJBhardwaj said:
Try changing or reflashing the radio?
Click to expand...
Click to collapse
I just reflashed "radio-angler-angler-03.72.img"
I'll reply again with whether or not it worked.
Tiduszk said:
I just reflashed "radio-angler-angler-03.72.img"
I'll reply again with whether or not it worked.
Click to expand...
Click to collapse
Good luck. If it doesn't, try radio version 3.61 from the latest MM factory image (MTC20F).
DJBhardwaj said:
Radio flash-able image files are present inside every factory image. What radio version are you currently operating on?
Click to expand...
Click to collapse
It did not fix it. Thanks for your help though.
DJBhardwaj said:
Good luck. If it doesn't, try radio version 3.61 from the latest MM factory image (MTC20F).
Click to expand...
Click to collapse
Is the marshmallow radio compatible with DP5?
Tiduszk said:
Is the marshmallow radio compatible with DP5?
Click to expand...
Click to collapse
Theoretically, it shouldn't harm at all. Kindly wait for someone with more experience on this. Until then, post your query at this thread: http://forum.xda-developers.com/nexus-6p/general/android-n-doesnt-t3332989
DJBhardwaj said:
Theoretically, it shouldn't harm at all. Kindly wait for someone with more experience on this. Until then, post your query at this thread: http://forum.xda-developers.com/nexus-6p/general/android-n-doesnt-t3332989
Click to expand...
Click to collapse
Well, I'll try it tomorrow. The worst that could happen is that I need to do a clean flash again.
Tiduszk said:
Well, I'll try it tomorrow. The worst that could happen is that I need to do a clean flash again.
Click to expand...
Click to collapse
DJBhardwaj said:
Theoretically, it shouldn't harm at all. Kindly wait for someone with more experience on this. Until then, post your query at this thread: http://forum.xda-developers.com/nexus-6p/general/android-n-doesnt-t3332989
Click to expand...
Click to collapse
Unfortunately it did not help, the issue persisted. I then tried to flash all the way back to stock marshmallow, and that didn't work. With Nougat released today, I flashed to it and my phone still reboots. I was able to further isolate the cause though; the phone reboots when it has a mobile data connection regardless of carrier (I tried Sprint, T-Mobile, AT&T, and China Unicom).
I think my only option left is to RMA it again.
Anyone having this working? It appears something doesn't work right as the screen is a big single screen (not the dual lens type thing of VR apps.) Some have suggested build.prop changes but they were met with mixed success it seems.
Anyone got this going and what did you do?
cincibluer6 said:
Anyone having this working? It appears something doesn't work right as the screen is a big single screen (not the dual lens type thing of VR apps.) Some have suggested build.prop changes but they were met with mixed success it seems.
Anyone got this going and what did you do?
Click to expand...
Click to collapse
I got this and decided to go back to stock because I been eagerly waiting for Plex VR. Going back to stock was a very long 2 day process I never want to go through again but was well worth it. Plus stock isn't really all that bad.
Well, there is no way I'll go back to stock. Not only an arduous project going back but I do enjoy LOS far, far more than stock.
Thanks mate
mllora81 said:
I got this and decided to go back to stock because I been eagerly waiting for Plex VR. Going back to stock was a very long 2 day process I never want to go through again but was well worth it. Plus stock isn't really all that bad.
Click to expand...
Click to collapse
cincibluer6 said:
Well, there is no way I'll go back to stock. Not only an arduous project going back but I do enjoy LOS far, far more than stock.
Thanks mate
Click to expand...
Click to collapse
Arduous? Getting a TWRP flashable zip and flashing it through TWRP is not a 2 day process. There are TWRP flashable zips for the G (raystef66's B09) and for the U (DrakenFX's stuff).
Choose an username... said:
Arduous? Getting a TWRP flashable zip and flashing it through TWRP is not a 2 day process. There are TWRP flashable zips for the G (raystef66's B09) and for the U (DrakenFX's stuff).
Click to expand...
Click to collapse
I tried DrakenFX's flashable zip. After a day my phone went into nonstop bootloops.
mllora81 said:
I tried DrakenFX's flashable zip. After a day my phone went into nonstop bootloops.
Click to expand...
Click to collapse
And everyone will have that same thing happen to them? If that happens I would either a) reflash, or b) install the stock recovery and flash the official zip.
Choose an username... said:
And everyone will have that same thing happen to them? If that happens I would either a) reflash, or b) install the stock recovery and flash the official zip.
Click to expand...
Click to collapse
I used the Axon 7 toolkit and couldn't get back to stock because XiaoMiFlash kept giving an error. Had to use MiPhone instead and then was able to flash stock files.
mllora81 said:
I used the Axon 7 toolkit and couldn't get back to stock because XiaoMiFlash kept giving an error. Had to use MiPhone instead and then was able to flash stock files.
Click to expand...
Click to collapse
MiFlash (and therefore axon7toolkit) is the last place you should go to. Imagine that the connection breaks somehow. Power surge, the USB cable getting disconnected, anything...
Going back to stock is as easy as flashing it via TWRP or flashing the stock recovery img and installing an official zip.
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