Database Users

Android 5.1 dropping right now*

*But it doesnt say what devices are getting it. And nothing on my 6 yet.
http://officialandroid.blogspot.com/2015/03/android-51-unwrapping-new-lollipop.html

stevessvt said:
*But it doesnt say what devices are getting it. And nothing on my 6 yet.
http://officialandroid.blogspot.com/2015/03/android-51-unwrapping-new-lollipop.html
Click to expand...
Click to collapse
here is another one
http://www.androidcentral.com/android-51-updates-nexus-5-could-begin-today-t-mo-docs-suggest

wonder when well see some updated roms

it can take up to 3 weeks to get an update once google starts. within 3 weeks is what google promises.

Newest nexus device = last device to get the update it needs and has needed since it's botched release. Gj googs

Guess it's time to turn back on the webpage update add on for the factory image pages. I mostly just want to try a new modem.
---------- Post added at 05:01 PM ---------- Previous post was at 04:58 PM ----------
dhufford81 said:
Newest nexus device = last device to get the update it needs and has needed since it's botched release. Gj googs
Click to expand...
Click to collapse
People say this, but I don't really have any problems. Everything works. I just want to see if I can get some better reception in a few spots, but really it's very minor.

brizey said:
Guess it's time to turn back on the webpage update add on for the factory image pages. I mostly just want to try a new modem.
---------- Post added at 05:01 PM ---------- Previous post was at 04:58 PM ----------
People say this, but I don't really have any problems. Everything works. I just want to see if I can get some better reception in a few spots, but really it's very minor.
Click to expand...
Click to collapse
Yeah I really don't have to many issues either I was just being snide. I do think it burns too much battery while sitting idle with screen off though. I shouldn't be losing 5 to 10 percent battery overnight. Mind you my overnights are 6 to 7 hours usually.

brizey said:
Guess it's time to turn back on the webpage update add on for the factory image pages. I mostly just want to try a new modem.
---------- Post added at 05:01 PM ---------- Previous post was at 04:58 PM ----------
People say this, but I don't really have any problems. Everything works. I just want to see if I can get some better reception in a few spots, but really it's very minor.
Click to expand...
Click to collapse
Main issue I want fixed is the sound issues then all will be fine for me.

Everyone calm down, it's not in aosp yet

and all i want is just a stock deodex rom =/

so what is new besides the HD voice and device protection ?

italia0101 said:
Everyone calm down, it's not in aosp yet
Click to expand...
Click to collapse
Finally, someone with common sense (and you beat me to it).
ROM's won't appear until it's in AOSP and Dev's re-compile.
for those devices it goes out to, we might see the OTA available if someone captures and upload it to their favorite BB
And then this could lend credence to VZ's hitting stores with 5.1 a week from Thursday (But I still think those would be a 5.0 variant with a open and update to 5.1 myself ...)

prestige2 said:
so what is new besides the HD voice and device protection ?
Click to expand...
Click to collapse
Still think were waiting on an official change log from google. Here's some 5.1 changes that have been posted: http://www.androidpolice.com/tags/android-5-1-feature-spotlight/
Sent from my Nexus 6

I hope google fixed the increasing tone (or allowed to disable it)

Looks like factory images dropped for the N5 and N10, but nothing yet for Shamu

The 2012 Nexus 7 also got some love.

wrinklefree said:
Looks like factory images dropped for the N5 and N10, but nothing yet for Shamu
Click to expand...
Click to collapse
shamu takes more time for some reason, its usually later than the rest

It is being pushed to aosp now: https://android.googlesource.com/device/moto/shamu/+/lollipop-mr1-release
http://www.androidpolice.com/2015/0...d-5-1-lollipop-source-code-to-aosp-right-now/

The system images are live for the nexus 4&5. But not the nexus 6 as per usual.
Why is the 6 slower to update? Is it done chronologically?

5.1 Could Begin Today
http://www.androidcentral.com/android-51-updates-nexus-5-could-begin-today-t-mo-docs-suggest

Got an update today.

Not sure if this is old news or not, but this came through today. (Attached)

Me too...just few hours ago
Enviado desde mi SM-T810 mediante Tapatalk

Any comments on the update?

Anyone know if this OJ1 update is compatible with OH7 root method (coming from OG2 5.0.2)?
TIA
---------- Post added at 10:21 PM ---------- Previous post was at 09:36 PM ----------
^^^ Hmmm.... It's still just an update to stay within 5.0.2 where I am. To OJ4.

Mine is 223.99 MB

Didn't take a screenshot but mine was 1.2 GB?!
I don't know if that was because Smart Switch included the backed-up data I'd just processed?
---------- Post added at 10:47 PM ---------- Previous post was at 10:45 PM ----------
I guess that's it till sometime next year then...

Nope, still stuck on 5.0.2 here

I usually play Sims Free Play. I noticed that the UI has become tiny after the update. It's very difficult to play this game after this last update. The game doesn't have any option to increase UI's font. Also, increasing font size on tab s2 display settings does not have any effect on the game ui size.

stateit said:
Anyone know if this OJ1 update is compatible with OH7 root method (coming from OG2 5.0.2)?
TIA
---------- Post added at 10:21 PM ---------- Previous post was at 09:36 PM ----------
Click to expand...
Click to collapse
I was on OH7 unrooted and took the 0J1 update and then used the CF autoroot OH7 method to root. Works fine.

Very bad update.
I've got mine 5 days ago, 240 smth MB's.
T-715 started to freeze if it is ON+connected to charger. Only way to restart or turn it of is to keep pressed PWR+Vol DOWN buttons
Also it is overheating without any reason, and it is restarting randomly at least 1-2 times/day.
It is not rooted, all software is legal/bought via Google Play.
Only way to charge device is to turn it off and than connect it to charger.
Battery life because of overheating - 80+C is reduced to less than 1 day.
Build num: LRX22G.T715XXU1AOI5
Kernel: 3.10.9-5795450
Android: 5.0.2

neo0001 said:
Very bad update.
I've got mine 5 days ago, 240 smth MB's.
T-715 started to freeze if it is ON+connected to charger. Only way to restart or turn it of is to keep pressed PWR+Vol DOWN buttons
Also it is overheating without any reason, and it is restarting randomly at least 1-2 times/day.
It is not rooted, all software is legal/bought via Google Play.
Only way to charge device is to turn it off and than connect it to charger.
Battery life because of overheating - 80+C is reduced to less than 1 day.
Build num: LRX22G.T715XXU1AOI5
Kernel: 3.10.9-5795450
Android: 5.0.2
Click to expand...
Click to collapse
It looks like you're on the older build which this build fixes (overheating etc.) Suggest you keep checking manually for updates.

Got mine. 53 mb. . No issues. T810
Sent from my SM-T810 using Tapatalk

zapote21 said:
Got mine. 53 mb. . No issues. T810
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
Were you able to root it?
Sent from my Nexus 6

kookahdoo said:
Were you able to root it?
Sent from my Nexus 6
Click to expand...
Click to collapse
See post #10. I did it twice with no issues.
Sent from my SM-T810 using XDA Free mobile app

Just got my second update for the S2 T715 4G version, the latest one is 140MB.
update: apparently it's still android 5.0.2.

I just got my S2 (T-917T from T-mobile with 5.1.1 AOG8) yesterday and not long after I got home an update popped up. I held off at the time in case it complicated gaining root, but after doing so today I just got the notification again. The build is AOJ3 and... it looks potentially sketchy. Attached is a shot of the update screen, the second point is worrisome (?) "After updating you will not be able to downgrade to the old software because of updates to the security policy." Weak... I've never downgraded firmware, but there are occasionally legit reasons to do so.
Is anyone running this build? Any problems?

jazzmachine said:
I just got my S2 (T-917T from T-mobile with 5.1.1 AOG8) yesterday and not long after I got home an update popped up. I held off at the time in case it complicated gaining root, but after doing so today I just got the notification again. The build is AOJ3 and... it looks potentially sketchy. Attached is a shot of the update screen, the second point is worrisome (?) "After updating you will not be able to downgrade to the old software because of updates to the security policy." Weak... I've never downgraded firmware, but there are occasionally legit reasons to do so.
Is anyone running this build? Any problems?
Click to expand...
Click to collapse
Its normal, since samsung installed knox on their phones and tab, downgrade is not possible, through the normal way, or procedures.
---------- Post added at 02:42 AM ---------- Previous post was at 02:39 AM ----------
Just update my os, bu still on 5.0.2, a few changes, faster, better battery life and icons has changed shapes, much rounder, could be more, need to check this out for further changes.

kms108 said:
Its normal, since samsung installed knox on their phones and tab, downgrade is not possible, through the normal way, or procedures.
---------- Post added at 02:42 AM ---------- Previous post was at 02:39 AM ----------
Just update my os, bu still on 5.0.2, a few changes, faster, better battery life and icons has changed shapes, much rounder, could be more, need to check this out for further changes.
Click to expand...
Click to collapse
It has samsung themes?

kms108 said:
Its normal, since samsung installed knox on their phones and tab, downgrade is not possible, through the normal way, or procedures.
---------- Post added at 02:42 AM ---------- Previous post was at 02:39 AM ----------
Just update my os, bu still on 5.0.2, a few changes, faster, better battery life and icons has changed shapes, much rounder, could be more, need to check this out for further changes.
Click to expand...
Click to collapse
Just seems a bit... hypocritical on Samsung and/or the carrier's parts. It's atypical, but sometimes a new build is just a total dud. But it's not unheard of for an "upgrade" to cause things like increased battery usage, excess heat, performance issues, app compatibility, sporadic boot loops. "New" security policy: no flashing back to the build that you were enjoying 2 weeks ago. A new build that addresses these issues will be out "soon".
I'm just really curious about the rational of insisting that you remain on a build that makes you hate your $$$ phone and also what the other mentioned "security policy" changes are baked into the new build because if they further (attempt to) restrict how I'm allowed to use the device that I own... I don't particularly care for that! Also, who knows how long one'll be stranded on a crappy build. It seems that Samsung should be spending their time ensuring that, at least, all of their flagship devices are receiving regular/timely updates rather than adding new policies that are particularly disadvantageous for power users who tend to buy those devices.
/r :silly:

kms108 said:
Its normal, since samsung installed knox on their phones and tab, downgrade is not possible, through the normal way, or procedures.
---------- Post added at 02:42 AM ---------- Previous post was at 02:39 AM ----------
Just update my os, bu still on 5.0.2, a few changes, faster, better battery life and icons has changed shapes, much rounder, could be more, need to check this out for further changes.
Click to expand...
Click to collapse
Its NOT normal. It has always been possible to downgrade regardless of KNOX with an unlocked bootloader.
So called security updates that state that you will not be able to downgrade are bad, and usually mean one thing a bootloader update. Bootloader updates like this often lead to locked bootloaders, its happened before on Samsung devices. Locked bootloader means, no root, no custom recovery and no roms.
I'd stay away from this update until more is known about it. It may be possible to update without the bootloader.

Where's our Nougat update ZTE??

Update 6/21/2017: OTA update to Android 7.1.1 is out, and I received the OTA and installed it around 10 pm CST. Working great so far!! I like to think that my writing this post here on XDA finally caught the attention of ZTE, so they decided to get the update out ASAP lol. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Getting a Nougat update for the Axon 7 mini seems to be too much of a challenge for ZTE. As most of you know, ZTE has been running a closed Beta test of Android Nougat for our device. Three months is a pretty long Beta test, and it seems to me that ZTE may be experiencing some problems. I am not part of the Beta, I was in the hospital and didn't find out about it until sign ups were over. Is there anyone who's running the Beta right now that could give us an update? Feel free to PM me, and I can pass any updated info along to those of us not in the Beta, as I don't want anyone who does pass the info along to get in trouble for violating an NDA. Thanks!
Sent from my ZTE B2017G using Tapatalk

I messaged ZTE on twitter about a week ago asking if they plan on releasing nougat or if not to unlock the bootloader if they planned on no longer supporting the device and this is the reply I got.
The Axon 7 Mini is still supported, and we've confirmed than an update will be released soon. We appreciate your continued patience. At this time, we are unable to provide assistance to unlock the bootloader of this device.
---------- Post added at 10:21 AM ---------- Previous post was at 10:18 AM ----------
Now my definition of soon may be different from theirs but I got this message last Tuesday I hope this helps in some way.

lllWHALEYlll said:
I messaged ZTE on twitter about a week ago asking if they plan on releasing nougat or if not to unlock the bootloader if they planned on no longer supporting the device and this is the reply I got.
The Axon 7 Mini is still supported, and we've confirmed than an update will be released soon. We appreciate your continued patience. At this time, we are unable to provide assistance to unlock the bootloader of this device.
---------- Post added at 10:21 AM ---------- Previous post was at 10:18 AM ----------
Now my definition of soon may be different from theirs but I got this message last Tuesday I hope this helps in some way.
Click to expand...
Click to collapse
Thanks for the info, hopefully the update will be here soon!
I have received information about the beta via a couple of PM's from active beta testers. Looks like they are currently testing 7.1.1 with the June security patch. The software is said to be running good, but has a couple unspecified bugs that need to be corrected. All sources indicate that the update should be releasing very soon, but no confirmed release date yet. I wi6add further information as I receive it.
Sent from my ZTE B2017G using Tapatalk

Hi, I'm in the beta test and wrote you a pm ?

CreepaY said:
Hi, I'm in the beta test and wrote you a pm ?
Click to expand...
Click to collapse
Hi, can u write beta-firmware version?
I'm not betatester, but i got 7.1.1 OTA.

maestromony said:
Hi, can u write beta-firmware version?
I'm not betatester, but i got 7.1.1 OTA.
Click to expand...
Click to collapse
It's also android 7.1.1. build number is B2017GV1.2.0B09
Maybe beta test is over ?

CreepaY said:
It's also android 7.1.1. build number is B2017GV1.2.0B09
Click to expand...
Click to collapse
Same version. Interesting...

Android Headlines is reporting the roll-out of 7.1.1 is starting... anyone seeing it, still showing "Your software is up to date" here in US?
https://www.androidheadlines.com/20...gins-getting-android-7-1-1-nougat-update.html

maestromony said:
Same version. Interesting...
Click to expand...
Click to collapse
That's just weird. According to the beta testers, that build was sent to them shortly after the beta began, and still has some software bugs. I would have thought that ZTE would at least have one more update to the firmware prior to launch.
I guess we'll see if ZTE just ignored the bugs to get the update out. Apparently the OTA is supposed to be available, but I'm not seeing it yet (Missouri). Anyone here in the US been able to update yet?
Sent from my ZTE B2017G using Tapatalk

I am downloading the 7.1.1 update now! I have the Axon 7 Mini on T-Mobile in the US. I will post more info as soon as it finishes. Very excited to see it says it adds T-Mo Wi-Fi calling support.

I got the update last night but this morning after turning on the T-Mobile wi-fi calling it messed up my cellular radio. Keeps turning on/off. Connects then disconnects. Anyone else having this problem?
Looks like I may have to reset the phone. ?

eddie873 said:
I got the update last night but this morning after turning on the T-Mobile wi-fi calling it messed up my cellular radio. Keeps turning on/off. Connects then disconnects. Anyone else having this problem?
Looks like I may have to reset the phone. ?
Click to expand...
Click to collapse
Can u share with us some screenshots of the nougat experience on the mini?

So far the update is great! before the update if I enabled VoLTE I was unable to receive texts. The update fixed that. Wi-Fi calling works great. Here are some screenshots of the updated Settings menu.

r3xx3r said:
So far the update is great! before the update if I enabled VoLTE I was unable to receive texts. The update fixed that. Wi-Fi calling works great. Here are some screenshots of the updated Settings menu.
Click to expand...
Click to collapse
Is it possible to set a custom dpi?

So I reset my phone and that didn't fix my problem. I messed around with all the WiFi & WiFi calling settings and cellular data settings with none of them fixing my problem. I then turned on the developers options and for some reason that fixed my cellular from turning on and off.
That fixed my issue if anyone has the same problem.

ayoub.hariri.20 said:
Is it possible to set a custom dpi?
Click to expand...
Click to collapse
not exactly. They have 2 options in the Display settings, 1 for Font size with Small, Default, Large, and Largest options, and another for Display size with Small, Default, and Large options. Those screenshots were taken with both set to Small

r3xx3r said:
not exactly. They have 2 options in the Display settings, 1 for Font size with Small, Default, Large, and Largest options, and another for Display size with Small, Default, and Large options. Those screenshots were taken with both set to Small
Click to expand...
Click to collapse
Okay thanks man

My son's got it this morning finally... Update took a while, probably close to 40 minutes start to finish, including the "Android is upgrading" portion after full boot. That must be an N thing, it rebuild cache on the fly or something. So far so good, no issues or problems yet.
We don't have T-Mobile here, use H2O (an AT&T MVNO) and so far no issues with radios or connection.
TBH, the more I play with this device the more I like it... the UI isn't too bad, one thing that gets me is the modified "Home" menu and you can't easily switch launchers without uninstalling one, but that is for another thread if I ever decide to pursue it.

r3xx3r said:
not exactly. They have 2 options in the Display settings, 1 for Font size with Small, Default, Large, and Largest options, and another for Display size with Small, Default, and Large options. Those screenshots were taken with both set to Small
Click to expand...
Click to collapse
Actually, it's in the Developer Settings. I saw it under "smallest width," if I'm not mistaken.
---------- Post added at 04:13 AM ---------- Previous post was at 04:04 AM ----------
So, after I installed the update, I had connection problems. Everything had trouble using data. I reset and it's fine. And I must say, I'm impressed. It feels smoother and faster than before. I'm happy they finally released it.

https://www.xda-developers.com/android-7-1-1-is-now-rolling-out-to-the-zte-axon-7-mini/
I checked for an update tonight after reading this article and am now downloading what I presume is 7.1.1.

Oreo OTA downloading now

Pixel XL from play store.

Not in beta?
---------- Post added at 07:24 PM ---------- Previous post was at 07:22 PM ----------
Actually, four taps and I got the update too. I'm not in the beta.

I got the notification earlier. Pixel XL on Sprint and Pure Nexus

scottjal said:
Not in beta?
---------- Post added at 07:24 PM ---------- Previous post was at 07:22 PM ----------
Actually, four taps and I got the update too. I'm not in the beta.
Click to expand...
Click to collapse
Nope, not it beta.

no OTA's here

Just got it, play store Pixel XL with Verizon service. Update was pretty quick. Seems smooth and apps seem to load faster and work faster once they are open.
Sent from my Pixel XL using Tapatalk

I just updated my wife's Verizon Pixel, I "checked for updates" and it instantly came up.

ahent said:
Just got it, play store Pixel XL with Verizon service. Update was pretty quick. Seems smooth and apps seem to load faster and work faster once they are open.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Same here pixel XL from play store on Verizon and ota just popped up. Downloading now
Sent from my Pixel XL using Tapatalk

It's boot time (not the first one during update) is astoundingly fast.
Sent from my Pixel XL using Tapatalk

I just flashed back from factory image Oreo to N yesterday, due to Beta OTA Oreo causing me a few issues...
Now the real OTA is here and I don't want to upgrade to it.... :/

Okmed said:
Pixel XL from play store.
Click to expand...
Click to collapse
pwnsicle said:
I got the notification earlier. Pixel XL on Sprint and Pure Nexus
Click to expand...
Click to collapse
ahent said:
Just got it, play store Pixel XL with Verizon service. Update was pretty quick. Seems smooth and apps seem to load faster and work faster once they are open.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
airmaxx23 said:
I just updated my wife's Verizon Pixel, I "checked for updates" and it instantly came up.
Click to expand...
Click to collapse
Guys - please post the following:
Final build number:
Bought from:
Disk size:
Carrier SIM:
Approx. update file size and count (did you install two OTAs and reboot twice?):
The reason is that there are multiple 'final' build numbers out there for those going from DP4 => Oreo

Opr6.170623.012
Google play store
128gb
Verizon
Approx. 945mb (can't remember exactly)
Sent from my BTV-W09 using Tapatalk

OPR6.170623.011
Google Play store
128gb
Sprint
951.2 MB
Unmodified stock device. No beta. No bootloader unlock.(or does the G store version come unlocked bootloader already??)

I'm moving this thread to general discussion section as this is not related to any Q&A.

makapav said:
Guys - please post the following:
Final build number:
Bought from:
Disk size:
Carrier SIM:
Approx. update file size and count (did you install two OTAs and reboot twice?):
The reason is that there are multiple 'final' build numbers out there for those going from DP4 => Oreo
Click to expand...
Click to collapse
Build number: OPR6.170623.012
Bought from Alpabet (formally Google)
Memory: 128mb
PIXEL XL
SIM: Verizon
I think it 850mb or so. One OTA, one reboot
Hope that helps.

After using it for about 24 hours I can't say that I have noticed a big increase or decrease in battery life. I know most people say give it a day or 2 for the update to "settle in". I also have had 0 problems with apps so far.
Sent from my Pixel XL using Tapatalk

[FIXED - May 2018] Multi-touch issues in Android 8.1.0

Issue has been fixed in builds:
Android 8.1.0 (OPM2.171019.029.B1, May 2018)
Android P Developer Preview 2 (PPP2.180412.013, May 2018)
Last builds affected:
Android 8.1.0 (OPM2.171019.029, Apr 2018)
Android P Developer Preview 1 (PPP1.180208.014, March 2018)
When two or more fingers are placed on the screen for an extended period of time the touch input from the second finger will become erratic at times, jumping to different parts of the display while you are moving it. I play first person shooter games commonly and this issues is extremely annoying when trying to aim.
If anyone has time to test I highly encourage you to let Google know of the problem by going to:
Settings > System > About Phone > Send feedback about this device
Also you can star the issue I already created in the Android issue tracker. Links are below for anybody able to test. Thanks for reading.
Issue tracker (please star):
https://issuetracker.google.com/issues/70344455
Video (most noticeable after 35 second mark):
https://drive.google.com/file/d/0B1tb_AIZ5QUwTWxKN0FaRTdHcWs/view?usp=drive_web
Game video (11 second mark, after 33 second mark):
https://drive.google.com/file/d/1sZvnaKJLwMWxokmSPOci4lPOwJTv9j4q/view?usp=drive_web
Google Photos pinch to zoom video (after 14 seconds):
https://www.youtube.com/watch?v=2Vv584tvVyg
Multi-touch tester app used:
https://play.google.com/store/apps/details?id=com.spencerstudios.screentest
Reverting to 8.0.0 will "fix" the issue, the issue is NOT present in 8.0.0.

Issue still exists in the public 8.1.0 release OPM1.171019.011.
https://issuetracker.google.com/issues/70344455

still exists as of january patch
---------- Post added at 03:30 PM ---------- Previous post was at 03:29 PM ----------
if you're experiencing this go STAR the issue linked on the google tracker

2x4 said:
still exists as of january patch
---------- Post added at 03:30 PM ---------- Previous post was at 03:29 PM ----------
if you're experiencing this go STAR the issue linked on the google tracker
Click to expand...
Click to collapse
Use issue # 70344455 from post #2. The one from DP has been deferred.
I put up a new video today demonstrating using one of Google's own apps vs a game.
https://issuetracker.google.com/issues/70344455#comment72

Has anybody tested to see if the issue is present using any of the custom kernels on XDA? I am just trying to determine where the problem originated.

yes, i am using this one:
https://issuetracker.google.com/issues/70344455

I have also sent feedback via settings and posted in the issue tracker. I would love to know of there are Pixel 2 XL owners that do not have this issue. If that is the case I will be submitting an RMA. Tomorrow I will be contacting support and asking for a definitive answer as to when and if we can expect a fix. This is the single most frustrating issue I have with the device. I love everything else about this phone but this is driving me nuts
---------- Post added at 08:15 AM ---------- Previous post was at 08:13 AM ----------
I watched the videos attached and to my surprise and unfortunate relief I noticed you are having this issue with SGL. That and Afterpulse are unbearable to play.

Just remove your case

Happens to me all the time while zooming in on photos!

Ksehwail said:
I have also sent feedback via settings and posted in the issue tracker. I would love to know of there are Pixel 2 XL owners that do not have this issue. If that is the case I will be submitting an RMA. Tomorrow I will be contacting support and asking for a definitive answer as to when and if we can expect a fix. This is the single most frustrating issue I have with the device. I love everything else about this phone but this is driving me nuts
---------- Post added at 08:15 AM ---------- Previous post was at 08:13 AM ----------
I watched the videos attached and to my surprise and unfortunate relief I noticed you are having this issue with SGL. That and Afterpulse are unbearable to play.
Click to expand...
Click to collapse
Any luck contacting support? I don't think RMA will help, as it is a software issue. SGL is frustrating as hell, I end up not completing any missions I start.
wmcdrugs said:
Just remove your case
Click to expand...
Click to collapse
What?

quakeaz said:
What?
Click to expand...
Click to collapse
Are you using case? Try to reproduce your problem without it.

wmcdrugs said:
Just remove your case
Click to expand...
Click to collapse
Hahaha really?!? I've tried with a case without case, with a screen protector without... Funny guy very very funny. So am I to assume you don't have this issue

Ksehwail said:
Hahaha really?!? I've tried with a case without case, with a screen protector without... Funny guy very very funny. So am I to assume you don't have this issue
Click to expand...
Click to collapse
Not joking, there was a similar situation at another forum, really.

wmcdrugs said:
Not joking, there was a similar situation at another forum, really.
Click to expand...
Click to collapse
Do you have a link? It doesn't sound like the same kind of problem to me, but I am curious.

wmcdrugs said:
Not joking, there was a similar situation at another forum, really.
Click to expand...
Click to collapse
Well my apologies I thought you were trying to be a wise guy. Again this was one of the first possible solutions I thought of as I've had that work with previous devices. Sometimes the grounding when making contact with the actual device without a case does work. However, I've tried all possible fixes and none have worked.

quakeaz said:
Do you have a link? It doesn't sound like the same kind of problem to me, but I am curious.
Click to expand...
Click to collapse
Sure, but be ready for translating russian. http://4pda.ru/forum/index.php?showtopic=847032&view=findpost&p=69149836
Before this post some discussion and attempts of other people to reproduce that.

wmcdrugs said:
Sure, but be ready for translating russian. http://4pda.ru/forum/index.php?showtopic=847032&view=findpost&p=69149836
Before this post some discussion and attempts of other people to reproduce that.
Click to expand...
Click to collapse
Thanks. Well, I tried it, no luck. It is most definitely software. Downgrading to 8.0.0 fixed it for me. I'm back on 8.1.0 now though, I shouldn't have to run older software and an outdated security patch just to "fix" a problem that Google should fix properly. Part of the appeal of the Pixel is being up to date.

I read somewhere that the Feb update is supposed to address some of the touch and swipe issues. Try again then.
Sent from my Pixel 2 using Tapatalk

JasonJoel said:
I read somewhere that the Feb update is supposed to address some of the touch and swipe issues. Try again then.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Where did you read that? Google has been pretty silent on the issue.

Is is any better for Feb OTA update?