IssueTracker

https://ads.google.com/status/publisher/incidents/ZDDr9AsgkrNxd7zHjU4c?hl=en

ro...@gmail.com <ro...@gmail.com> #5Sep 4, 2019 07:09PM

Same here. Seems like a remote issue as nothing changed from our part.
I'd say that it's possibly because the static string key saved on the shared prefs is used somewhere else, even in a different library perhaps, as an Integer. Couldn't fully recover the string name though because of the compiled code. Haven't delve much in though

st...@gmail.com <st...@gmail.com> #6Sep 4, 2019 07:20PM

Ok I gave up and delve deeper.
It's a bit hard to understand where's the problem is as the code is obfuscated but it should be one of these:
"gad_has_consent_for_cookies"
"IABTCF_gdprApplies"
"IABTCF_TCString"
"IABTCF_PurposeConsents"

I don't know who exactly causes this crash but I know that the "getString" function crash when one of them returns an integer instead of string.

The getString function crashes somewhere here:

public final void onSharedPreferenceChanged(SharedPreferences sharedPreferences, String str) {
char c;
int i;
zzbbc zzbbcVar = zzbbk.zzay;
C6158t c6158t = C6158t.f15178d;
if (((Boolean) c6158t.f15181c.zzb(zzbbcVar)).booleanValue()) {
if (zzbwv.zza(str, "gad_has_consent_for_cookies")) {
if (!((Boolean) c6158t.f15181c.zzb(zzbbk.zzaw)).booleanValue()) {
return;
}
int i2 = sharedPreferences.getInt("gad_has_consent_for_cookies", -1);
C6482j0 c6482j0 = (C6482j0) this.zzc;
c6482j0.m973p();
synchronized (c6482j0.f16228a) {
i = c6482j0.f16242o;
}
if (i2 != i) {
((C6482j0) this.zzc).m982g(true);
}
((C6482j0) this.zzc).m984e(i2);
return;
} else if (zzbwv.zza(str, "IABTCF_gdprApplies") || zzbwv.zza(str, "IABTCF_TCString") || zzbwv.zza(str, "IABTCF_PurposeConsents")) {
String string = sharedPreferences.getString(str, "-1");
if (string != null && !string.equals(((C6482j0) this.zzc).m965x(str))) {
((C6482j0) this.zzc).m982g(true);
}
((C6482j0) this.zzc).m983f(str, string);
return;
} else {
return;
}
}
String string2 = sharedPreferences.getString("IABTCF_PurposeConsents", "-1");
int i3 = sharedPreferences.getInt("gad_has_consent_for_cookies", -1);
String valueOf = String.valueOf(str);
int hashCode = valueOf.hashCode();
if (hashCode != -2004976699) {
if (hashCode == -527267622 && valueOf.equals("gad_has_consent_for_cookies")) {
c = 1;
}
c = 65535;
} else {
if (valueOf.equals("IABTCF_PurposeConsents")) {
c = 0;
}
c = 65535;
}
if (c != 0) {
if (c != 1) {
return;
}
if (((Boolean) c6158t.f15181c.zzb(zzbbk.zzaw)).booleanValue() && i3 != -1 && this.zzf != i3) {
this.zzf = i3;
zzb(string2, i3);
}
} else if (!string2.equals("-1") && !this.zze.equals(string2)) {
this.zze = string2;
zzb(string2, i3);
}
}

where the str argument is one of the static strings I mentioned. Notice that Google does lots of type/null checks before communicating with the SharedPreferences so this seems like something that the developers tried to avoid

df...@gmail.com <df...@gmail.com> #7Sep 4, 2019 08:22PM

I'd say that it's related to the new GDPR dialog as the results/consents are fetched remotely.
Again, I could be wrong. My assumptions are heavily relayed on lots of obfuscated code

ic...@gmail.com <ic...@gmail.com> #8Sep 4, 2019 10:53PM

On an old build of com.google.android.gms.policy_ads_fdr_dynamite (211512000057.367949677.367949677 July 15, 2021), there are 2 potential culprits:

    public final void onSharedPreferenceChanged(SharedPreferences sharedPreferences, String str) {
        Context context;
        if ("IABTCF_PurposeConsents".equals(str)) {
            String string = sharedPreferences.getString("IABTCF_PurposeConsents", "");

    public final void onSharedPreferenceChanged(SharedPreferences sharedPreferences, String str) {
        char c;
        if ("consent_string".equals(str)) {
            String string = sharedPreferences.getString("consent_string", "");

I have a strong feeling that IABTCF_PurposeConsents is the one we are crashing on.

From the documentation:

Binary String: The '0' or '1' at position n – where n's indexing begins at 0 – indicates the consent status for purpose ID n+1; false and true respectively. eg. '1' at index 0 is consent true for purpose ID 1

Something in the chain might have replaced this value thinking it was an Integer 🙈.

wa...@gmail.com <wa...@gmail.com> #9Sep 4, 2019 11:34PM

Yeah that's not bad. So.. basically.. as a quick fix:
```
val prefs = PreferenceManager.getDefaultSharedPreferences(this)
try {
prefs.getString("consent_string", "")
} catch (e: ClassCastException) {
prefs.edit().putString("consent_string", "").apply()
}
MobileAds.initialize(this) {}
```

eu...@gmail.com <eu...@gmail.com> #10Sep 4, 2019 11:48PM

deleted

ro...@gmail.com <ro...@gmail.com> #11Sep 5, 2019 12:02AM

deleted

fg...@gmail.com <fg...@gmail.com> #12Sep 5, 2019 04:43AM

Sorry. This is the complete solution we have until now:

val prefs = PreferenceManager.getDefaultSharedPreferences(this)
try {
    prefs.getString("consent_string", "")
} catch (e: ClassCastException) {
    prefs.edit().putString("consent_string", "").apply()
}

try {
    prefs.getString("IABTCF_PurposeConsents", "")
} catch (e: ClassCastException) {
    prefs.edit().putString("IABTCF_PurposeConsents", "").apply()
}
MobileAds.initialize(this) {}

ni...@gmail.com <ni...@gmail.com> #13Sep 5, 2019 05:25AM

I advice against using this solution though. I don't think you're suppose to touch the consent finals. This message only meant to help point to the right solution

ba...@gmail.com <ba...@gmail.com> #14Sep 5, 2019 05:35AM

Is there an ETA from the Google AdMob team for the fix? I'm also experiencing this (22,830 crash events affecting 973 users)

co...@gmail.com <co...@gmail.com> #15Sep 5, 2019 07:07AM

Same issue here, lots of spike in Crashlytics

vi...@google.com <vi...@google.com> #16Sep 5, 2019 07:45AM

Assigned to vi...@google.com.

I guess the team has to undo the recent remote changes on Admob server side ASAP

li...@gmail.com <li...@gmail.com> #17Sep 5, 2019 08:01AM

Any Google update on this? Some config change on AdMob servers?

(don't think we should be altering GDPR strings as stated above...)

ba...@gmail.com <ba...@gmail.com> #18Sep 5, 2019 08:16AM

Is there anyone on Crashlytics who is seeing a decrease in crashes? (I'm not)

lf...@gmail.com <lf...@gmail.com> #19Sep 5, 2019 02:29PM

I'm not sure that this is GDPR-related. I've asked my users where they are, and two said North America, one said England. Also I'm not seeing a drop in crashes despite it being 1am in England.

ch...@gmail.com <ch...@gmail.com> #20Sep 5, 2019 02:38PM

Is there anyone on Crashlytics who is seeing a decrease in crashes? (I'm not)

Crashes stopped between 01:04-01:14 GMT but they appeared again after that interval for me.

ja...@gmail.com <ja...@gmail.com> #21Sep 5, 2019 05:49PM

I see a decrease in crashes after reach the peak around 5h ago. Many european users

bg...@gmail.com <bg...@gmail.com> #22Sep 5, 2019 05:56PM

Isn't this being monitored by admob people? Are a lot of apps and developers suffering right now and there's no issue resolution or progress sharing?

ni...@gmail.com <ni...@gmail.com> #23Sep 5, 2019 07:21PM

I'm not sure it is decreasing. This issue is still occurring.
I just released a new version with try-catch.

ni...@gmail.com <ni...@gmail.com> #24Sep 5, 2019 07:48PM

It looks like Google is working on the fix now:

df...@gmail.com <df...@gmail.com> #25Sep 5, 2019 08:40PM

The number of crashes appear to be decreasing now. Pretty poor form on somebody's part - a widespread issue like this can cause significant app publisher reputation damage & loss of user installed base. Users don't know that it's affecting all apps - they just see it causing issues in the apps they're using. Considering the higher & higher standards we're being held to this is a real kick in the teeth.

ni...@gmail.com <ni...@gmail.com> #26Sep 5, 2019 08:44PM

Still being affected by this. Of course we would not be in this situation if your engineers spent their working hours writing robust code instead of posting disrespectful garbage on memegen mocking other companies and their products.

da...@gmail.com <da...@gmail.com> #27Sep 5, 2019 09:27PM

Google Mobile Ads SDK is almost fixed as they explain in their recent status. We also check our company app(using european region vpn) and consent is working fine but ads are not loading right now.

https://ads.google.com/status/publisher/incidents/ZDDr9AsgkrNxd7zHjU4c?hl=en

ge...@gmail.com <ge...@gmail.com> #28Sep 5, 2019 11:00PM

It's surprise that any Google engineer didnt post a single reply here yet.
the status page doesnt include any technical details.
I just hope that they fixed the issue in a robust way.

wk...@gmail.com <wk...@gmail.com> #29Sep 5, 2019 11:57PM

Can I prevent a crash from occurring with try-catch?
Google said it was resolved, but many crashes are still being reported.

az...@gmail.com <az...@gmail.com> #30Sep 6, 2019 12:41AM

Any news on this subject : we are still seeing a lot of crashes related to this issue

lo...@gmail.com <lo...@gmail.com> #31Sep 6, 2019 12:56AM

We still getting this crash, has anyone found any solution?

ym...@gmail.com <ym...@gmail.com> #32Sep 6, 2019 01:20AM

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Related API or developer doc.

Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:

https://developer.android.com/studio/debug/bug-report#bugreportdevice

Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Note: Please upload the bug report to google drive and share the folder to android-bugreport@google.com, then share the link here.

de...@gmail.com <de...@gmail.com> #33Sep 6, 2019 04:18AM

https://ads.google.com/status/publisher/incidents/ZDDr9AsgkrNxd7zHjU4c?hl=en

da...@gmail.com <da...@gmail.com> #34Sep 6, 2019 04:37AM

The number of crashes has been decreased but It's still happening.

ba...@gmail.com <ba...@gmail.com> #35Sep 6, 2019 04:44AM

deleted

da...@gmail.com <da...@gmail.com> #36Sep 6, 2019 05:41AM

We still getting this crash, has anyone found any solution?

ba...@gmail.com <ba...@gmail.com> #37Sep 6, 2019 05:51AM

Rats, I added try/catch around the MobileAds.initialize() call, released it, but the crash is still happening! It's in a callback as a result of shared preferences changing:

Fatal Exception: java.lang.ClassCastException
java.lang.Integer cannot be cast to java.lang.String
android.app.SharedPreferencesImpl.getString (SharedPreferencesImpl.java:306)
com.google.android.gms.ads.internal.scionintegration.a.onSharedPreferenceChanged (:com.google.android.gms.policy_ads_fdr_dynamite@240304709@240304704034.602821767.602821767:73)
android.app.SharedPreferencesImpl$EditorImpl.notifyListeners (SharedPreferencesImpl.java:693)
android.app.SharedPreferencesImpl$EditorImpl.lambda$notifyListeners$0$android-app-SharedPreferencesImpl$EditorImpl (SharedPreferencesImpl.java:699)
android.app.SharedPreferencesImpl$EditorImpl$$ExternalSyntheticLambda0.run (Unknown Source:4)
android.os.Handler.handleCallback (Handler.java:942)
android.os.Handler.dispatchMessage (Handler.java:99)
android.os.Looper.loopOnce (Looper.java:226)
android.os.Looper.loop (Looper.java:313)
android.app.ActivityThread.main (ActivityThread.java:8762)

Any ideas how to defend against that?

ba...@gmail.com <ba...@gmail.com> #38Sep 6, 2019 08:29AM

It appears fixed for me, I've gone from a peak of over 50k crashes to just 1.2k in the last hour, it's slowly improving.

bugreport-blueline-QP1A.190711.020-2019-09-06-10-23-39.zip

2.9 MB

See: https://ads.google.com/status/publisher/incidents/ZDDr9AsgkrNxd7zHjU4c

ac...@gmail.com <ac...@gmail.com> #39Sep 6, 2019 11:19AM

It looks like it's not fully fixed yet, the number of crashes no longer decreases.

Referring to the posts above, the problem is that the saved type of iab consent strings of the initially affected users was somewhat corrupted.
Google needs to restore these corrupted iab consent strings to their original state,
but I'm worried that they may have omitted this part.

ku...@gmail.com <ku...@gmail.com> #40Sep 6, 2019 11:36AM

java.lang.ClassCastException: java.lang.Integer cannot be cast to java.lang.String
at android.app.SharedPreferencesImpl.getString(SharedPreferencesImpl.java:302)
at com.google.android.gms.ads.internal.scionintegration.a.onSharedPreferenceChanged(:com.google.android.gms.policy_ads_fdr_dynamite@240304709@240304704034.602821767.602821767:73)
at com.google.android.gms.ads.internal.scionintegration.m.a(:com.google.android.gms.policy_ads_fdr_dynamite@240304709@240304704034.602821767.602821767:106)
at com.google.android.gms.ads.nonagon.a.s(:com.google.android.gms.policy_ads_fdr_dynamite@240304709@240304704034.602821767.602821767:439)
at com.google.android.gms.ads.nonagon.a.b(:com.google.android.gms.policy_ads_fdr_dynamite@240304709@240304704034.602821767.602821767:5)
at com.google.android.gms.ads.ChimeraMobileAdsSettingManagerCreatorImpl.getMobileAdsSettingManager(:com.google.android.gms.policy_ads_fdr_dynamite@240304709@240304704034.602821767.602821767:52)
at

com.google.android.gms.ads.internal.client.bx.bR(:com.google.android.gms.policy_ads_fdr_dynamite@240304709@240304704034.602821767.602821767:40)
at m.ajn.onTransact(:com.google.android.gms.policy_ads_fdr_dynamite@240304709@240304704034.602821767.602821767:21)
at android.os.Binder.transact(Binder.java:1169)
at ocm.gL(:com.google.android.gms@240812038@24.08.12 (190400-608507424):8)
at com.google.android.gms.ads.internal.client.ay.getMobileAdsSettingManager(:com.google.android.gms@240812038@24.08.12 (190400-608507424):12)
at com.google.android.gms.ads.MobileAdsSettingManagerCreatorImpl.getMobileAdsSettingManager(:com.google.android.gms@240812038@24.08.12 (190400-608507424):42)
at com.google.android.gms.ads.internal.client.az.fL(:com.google.android.gms@240812038@24.08.12 (190400-608507424):40)
at ocn.onTransact(:com.google.android.gms@240812038@24.08.12 (190400-608507424):101)
at android.os.Binder.transact(Binder.java:1169)
at com.google.android.gms.internal.ads.zzato.zzbg(SourceFile:8)
at com.google.android.gms.ads.internal.client.zzcp.zze(SourceFile:15)
at com.google.android.gms.ads.internal.client.zzeq.zza(SourceFile:15)
at com.google.android.gms.ads.internal.client.zzaq.zzc(SourceFile:109)
at com.google.android.gms.ads.internal.client.zzax.zzf(SourceFile:1)
at com.google.android.gms.ads.internal.client.zzax.zzd(SourceFile:93)
at com.google.android.gms.ads.internal.client.zzej.zzA(SourceFile:15)
at com.google.android.gms.ads.internal.client.zzej.zzn(SourceFile:49)
at com.google.android.gms.ads.MobileAds.initialize(SourceFile:3)
at com.viber.voip.ViberApplication.lambda$doInitApplication$16(SourceFile:889)
at com.viber.voip.ViberApplication.x(SourceFile:1)
at com.viber.voip.y1.init(SourceFile:1)
at u20.f.initInstance(SourceFile:3)
at u20.d.b(SourceFile:16)
at u20.d.run(SourceFile:1)
at d00.j1.run(SourceFile:1)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:487)
at java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:307)
at d00.i1.run(SourceFile:1)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
at java.lang.Thread.run(Thread.java:1012)

ed...@gmail.com <ed...@gmail.com> #41Sep 6, 2019 12:16PM

Please provide the requested information mentioned in comment #32 to proceed further.

ed...@gmail.com <ed...@gmail.com> #42Sep 6, 2019 12:22PM

comment #41 this issue has been resolved by the AdMob team as stated above.......

belkin_pixel_3_fast_wireless_charger_1.jpg

56 KB

Screenshot_20190905-132512.png

3.6 MB

https://del.dog/jikesoroyu.cc

pc...@gmail.com <pc...@gmail.com> #43Sep 6, 2019 12:44PM

Thanks for the information. We are closing this issue as this forum is for reporting Android issues only. For Google Mobile Ads issues, please visit the Google Mobile Ads SDK Technical Forum.

tr...@gmail.com <tr...@gmail.com> #44Sep 6, 2019 01:13PM

I have adaptive brightness, auto rotate and lift to wake but no active edge. All working before upgrade to 10.
Pixel 2, build QP1A.190711.019

br...@gmail.com <br...@gmail.com> #45Sep 6, 2019 01:32PM

Lift to wake, double-tap, and adaptive brightness are not working on my Pixel 2 after updating to Android 10, Build QP1A.190711.019.

fr...@dataligent.com <fr...@dataligent.com> #46Sep 6, 2019 02:15PM

Smart cover not working for me after upgrading to Android 10.

pa...@gmail.com <pa...@gmail.com> #47Sep 6, 2019 02:22PM

No issues here. Pixel 3XL. Updated via OTA from 9 running August security patch to 10. All sensors work as expected.

mb...@gmail.com <mb...@gmail.com> #48Sep 6, 2019 02:36PM

Upgrade to 10 now have to wait 2 minutes for outgoing calls. Rrrrrrrrrrr

ma...@gmail.com <ma...@gmail.com> #49Sep 6, 2019 02:36PM

No issues here

Pixel 2XL,
Stock Android 9 on latest SP
Never tampered with the phone
Downloaded update via update button
Installed, rebooted all sensors working as expected

al...@gmail.com <al...@gmail.com> #50Sep 6, 2019 02:47PM

I also have this sensor issue when everything was fine on pie. Here is logcat

2019-09-06-09-44-36.txt

31 KB

sh...@gmail.com <sh...@gmail.com> #51Sep 6, 2019 02:59PM

I had tons of issues with Q build QP1A.190711.020

But sideloaded Q build QP1A.190711.019 and no issues with sensors/bootloop/etc so far. Someone else give this a shot maybe?

pe...@gmail.com <pe...@gmail.com> #52Sep 6, 2019 03:02PM

Since I updated to Android 10 my Verizon text messaging app will not do pop Up's over the lock screen anymore? And everything in settings are the same it should work??
My out going calls lag for over 1-2 minutes 😡😡

al...@gmail.com <al...@gmail.com> #53Sep 6, 2019 03:09PM

You dimwits need to stop posting unrelated issues in this sensor thread. You issue is probably user error if you're that stupid anyways

ro...@gmail.com <ro...@gmail.com> #54Sep 6, 2019 03:22PM

I created a bug report after rotating my phone and tried to use Active Edge (squeezed the Phone).
I also recorded my screen and rotated my phone in landscape with the camera active, so you can see the rotation is not working.

The two files are attachted.

Hopefully it helps.

bugreport-crosshatch-QP1A.190711.020-2019-09-06-17-05-36.zip

5.3 MB

video.mp4

66 MB

so...@xara-capoeira.com <so...@xara-capoeira.com> #55Sep 6, 2019 03:28PM

Ditto - same issue. Phone is unusable if you connect in a call, or Zoom, etc due to blank screen.
Hard reset is the only way to get the phone back.

mi...@gmail.com <mi...@gmail.com> #56Sep 6, 2019 03:48PM

Since the 10 update placing a call takes up to 20 seconds to start ringing????

bt...@aol.com <bt...@aol.com> #57Sep 6, 2019 04:10PM

I have the same problem when making a call, it takes a while to connect. Receiving calls isnt a problem.

ni...@gmail.com <ni...@gmail.com> #58Sep 6, 2019 04:47PM

Hint: this might have something to do with the persist partition. There is no way to get persist.img for crosshatch since it is not part of the factory image. Any idea where I can find that?

mi...@gmail.com <mi...@gmail.com> #59Sep 6, 2019 06:37PM

Haven't had any issue on my pixel 3a. All sensors still work. Updated through settings rather than updating manually.

co...@googlemail.com <co...@googlemail.com> #60Sep 6, 2019 06:53PM

i have pixel 2 was fine on pye updated to android 10 and now *#06# to show imei is not working anymore used to work fine before update i can see imei in settings about and i get no bar codes when it displays anymore use this for security at work so *#06# was helpful

mi...@gmail.com <mi...@gmail.com> #61Sep 6, 2019 07:07PM

My Pixel1 can hardly make a phone call after update.and it doesn't receive call all that well now either 1 out of 5 call make it to ringer. And my son's diabetic blood app has stopped work completely.

be...@gmail.com <be...@gmail.com> #62Sep 6, 2019 07:11PM

Double tap to wake, lift to wake, and ambient lighting not working on my Pixel 3a since downloading 10 (QP1A.190711.019) OTA. All were working in Pie.

mb...@gmail.com <mb...@gmail.com> #63Sep 6, 2019 07:27PM

Talked to the Google pixel folks, if you have the Verizon App. Need to uninstall the app and your outgoing calls will work again. Worked for me.

la...@gmail.com <la...@gmail.com> #64Sep 6, 2019 09:10PM

so i have a pixel 3a xl coming in monday, will the upgrade start as soon as i get the phone going or can i keep the upgrade from installing?

pe...@gmail.com <pe...@gmail.com> #65Sep 6, 2019 10:13PM

Double tap to wake isn't working on my pixel XL

ma...@gmail.com <ma...@gmail.com> #66Sep 6, 2019 10:45PM

WiFi says that it is connected but no internet. Anyone else?

jm...@gmail.com <jm...@gmail.com> #67Sep 6, 2019 11:04PM

My Pixel 2 is having a number of issues since the update to 10. Similar problems around the screen rotation, screenshots and lock as others...but the camera is the big one, keeps 'sticking/freezing'' doesn't work at all sometimes. Their was an app update for it post the 10 update, not sure if it is that or the system update causing it, but it no longer reports the error either. I have rolled back the app update, seems to be working better...??

ti...@gmail.com <ti...@gmail.com> #68Sep 6, 2019 11:29PM

Pixel 3A XL user here, I'm unaffected by most of these. Only thing I've noticed is that when I take screenshots or save photos (taking photos is fine), they don't end up in my temp gallery within messaging apps. I have to send the screenshot or saved picture by going to it and manually sharing. Otherwise everything else is working great.

10 (QP1A.190711.020)

rc...@gmail.com <rc...@gmail.com> #69Sep 6, 2019 11:48PM

I have the build ending in .019 and have no problems on a Pixel 2.

gr...@gmail.com <gr...@gmail.com> #70Sep 7, 2019 12:14AM

I updated to Android 10, now my phone won't work properly, no service. I have the pixel 3a xL unlocked with visible SIM card.No data text or call smh

kr...@gmail.com <kr...@gmail.com> #71Sep 7, 2019 12:28AM

My sensors are mostly working. I find that tapping on apps sometimes takes 6 tries before it will open. Also calls are taking a couple minutes to initialize which is odd. No screenshot or auto-rotate or auto dimming issues here.

kr...@gmail.com <kr...@gmail.com> #72Sep 7, 2019 12:29AM

Double tap to wake does not work but it barely worked prior to the update.

co...@gmail.com <co...@gmail.com> #73Sep 7, 2019 01:41AM

Same issue. Phone was totally locked when making calls - had to force restart to hang up. Always on display and related features would not work. Did chat support with Google which resulted in a factory reset which temporarily resolved the issue, but I'm still having intermittent occurrences.

ow...@gmail.com <ow...@gmail.com> #74Sep 7, 2019 02:01AM

Guys please keep it on topic. I am seeing a lot of unrelated conversations which is a good way to get this issue igno and potentially never resolved

Anything, I mean ANYTHING not about broken sensors on a Pixel running Android 10 is definitely off topic

For other issu, ask around on XDA or some and if you can't find a solution, send feed to Google or open a separate bug report BUT DO NOT MENTION HERE

This is a bug report, Not a general purpose discussion thread

rk...@gmail.com <rk...@gmail.com> #75Sep 7, 2019 05:59AM

Pixle 2XL user. I've run into the problem with the sensors, calls not connecting at all, dropped calls, dropped call/call connection tones being used when they have been turned off, notifications not working, adaptive brightness not working and when a game is loading the notification bar will.drop down for sowe reason and then the game screen will flicker badly in the background. This happened with several games. The touch screen lags as well.

sa...@gmail.com <sa...@gmail.com> #76Sep 7, 2019 12:11PM

Seems like my sensors are working. Just cant make any calls on my phone since updating to Android 10. I have a phone and can't make calls. I can receive calls.

ri...@gmail.com <ri...@gmail.com> #77Sep 7, 2019 01:20PM

I have a similar issue upgraded pixel 2 to android 10 from pie after finding out there was an update and now if I try to do most things they crash, delete a single file? Crash, try and update ANYTHING through play store it crashes and never even starts the download haven't tried downloading any third party stuff but I feel that'll probably have the same result

A similar thing with calls I can make and receive calls however if I'm the receiver nothing works they can't hear me I can't hear them and none of the call GUI works, ringtone doesn't work either nor does alerts

I also had an alarm set for 9 even though I had no alarms set

ly...@gmail.com <ly...@gmail.com> #78Sep 7, 2019 02:29PM

Got the same problem on my pixel 3XL. The screen cannot walk up when having a phone call, need to hard reset to kill the call. Double tap to wake , lift to wake and auto brightness are not working either. Screen lock is not working as expect. Need to swipe from bottom to the top to unlook the screen( not happen on P).

st...@stushepherd.co.uk <st...@stushepherd.co.uk> #79Sep 7, 2019 03:50PM

Same here with my pixel 3. No sensors. When trying to make a call the screen goes black. No flip to shhh. Google customer service recommended a factory reset which was a pain. Did it anyway and still the issue persists.

ho...@gmail.com <ho...@gmail.com> #80Sep 7, 2019 04:33PM

The brightness sensors on my pixel 2xl just won't work anymore. Have to manually change brightness all the time which is very painful. Google get your act together guys

rc...@gmail.com <rc...@gmail.com> #81Sep 7, 2019 05:22PM

It might be more helpful if folks would post their build number.

ba...@gmail.com <ba...@gmail.com> #82Sep 7, 2019 05:34PM

doesn't really matter build number as people experienced this with all Q versions from beta to official

rc...@gmail.com <rc...@gmail.com> #83Sep 7, 2019 05:39PM

Okay.

za...@gmail.com <za...@gmail.com> #84Sep 7, 2019 05:57PM

I fixed this

https://forum.xda-developers.com/pixel-3/how-to/how-to-fix-sensor-issues-android-q-guide-t3965640 check out my guide

ap...@gmail.com <ap...@gmail.com> #85Sep 7, 2019 06:05PM

Your fix did not work for me
Pixel 3XL. Android Q. Rooted.

za...@gmail.com <za...@gmail.com> #86Sep 7, 2019 06:09PM

do not reboot, it doesn't stick after reboot

Il sab 7 set 2019, 20:05 <buganizer-system@google.com> ha scritto:

https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904/page19

ap...@gmail.com <ap...@gmail.com> #87Sep 7, 2019 06:12PM

Tried it again (without rebooting this time). Still not working. I tried toggling auto-rotate also. Still no luck.

ba...@gmail.com <ba...@gmail.com> #88Sep 7, 2019 06:14PM

guys at xda fixed this it seems! and it surveys to reboots! see this! Cool!!!

ni...@gmail.com <ni...@gmail.com> #89Sep 7, 2019 06:16PM

We have managed to fix the issue for you, Google.

Thank you to XDA members (too many to quote here, but link here:

https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904/)

Should you need our help in getting this issue fixed, email us.

za...@gmail.com <za...@gmail.com> #90Sep 7, 2019 06:23PM

in reply to #87 it is working for me on pixel 3. I'll investigate further

ap...@gmail.com <ap...@gmail.com> #91Sep 7, 2019 06:46PM

My post:

https://forum.xda-developers.com/showpost.php?p=80200701&postcount=190

ja...@gmail.com <ja...@gmail.com> #92Sep 7, 2019 08:52PM

Not a single sensor working, on Pixel 3

ca...@gmail.com <ca...@gmail.com> #93Sep 7, 2019 10:19PM

I've been on the beta version since April, updating to full release hasn't effected me

ba...@gmail.com <ba...@gmail.com> #94Sep 7, 2019 10:30PM

I confirm sensors fix found on xda forum worked also for pixel 3, getting an image of a good persist partition from a blueline user with sensors working of course. Solution available in xda forum - sensors bug thread. Thanks all who contributed in finding the solution, hope it is a good solution without any down sides...but so far so good!!

an...@gmail.com <an...@gmail.com> #95Sep 8, 2019 12:43AM

Same issue after installing factory image QP1A.190711.020 on my Pixel 3 XL. No rotation, light, active edge, or tilt to wake sensors.

jo...@gmail.com <jo...@gmail.com> #96Sep 8, 2019 12:52AM

I updated to Android 10 over the air by checking for system update. Since I have lost Active Edge Sensors and Adaptive Brightness. The rest seems OK. Is anyone from Google even looking at this issue?

Pixel 3
Build Number: QP1A.190711.019

lz...@gmail.com <lz...@gmail.com> #97Sep 8, 2019 06:59AM

Camera is also not working on pixle 3 XL on Android 10

st...@gmail.com <st...@gmail.com> #98Sep 8, 2019 07:44AM

also my pixel 3 After updating to Android 10 the proximity sensor no longer works, the phone hangs on call or with audio messages, Always on display does not work

ja...@gmail.com <ja...@gmail.com> #99Sep 8, 2019 03:16PM

Phone calls take a few times dialing to connect...not liking that !!!pixel
2XL. Hopefully all these reported bugs get fixed

ca...@gmail.com <ca...@gmail.com> #100Sep 8, 2019 03:49PM

Pixel 3a, updated to 10 last night via settings. Sensors not working, hey Google is not responding, home button/gesture not responding (but back button/gesture works), notifications not working, mobile data not working, long press on wifi/Bluetooth/DND etc. not working, cannot expand that panel of shortcut buttons, can't reach alarms app by tapping on the time from notifications panel.

ca...@gmail.com <ca...@gmail.com> #101Sep 8, 2019 05:17PM

Any idea of what google is doing to fix this? I have a Pixel XL, updated about 2 weeks ago, and my phone is on loop in the lock screen. I can't even unlock my phone. I have so much data on my phone as well, and even plugging it into a computer, I still have to put my pass-code in and it just loops on the lock screen...
This is terrible.

ca...@gmail.com <ca...@gmail.com> #102Sep 8, 2019 09:48PM

I am having a serious issue with placing voice calls. My pixel2 XL is unable to place a basic phone call. The screen says "calling" then it freezes up. I have tried trouble shooting it to no avail. This is a serious flaw due to me being on call 24hours a day. I'm getting ready to switch to iOS.

si...@gmail.com <si...@gmail.com> #103Sep 9, 2019 04:59AM

Proximity Sensor will cause issues mid phone call. Once removing from my ear, it will still think its engaged, cannot unlock phone during this.

Pixel 2 XL, issue been present since Beta 5

si...@gmail.com <si...@gmail.com> #104Sep 9, 2019 05:01AM

Apologies, issue present with Beta 6.

pi...@gmail.com <pi...@gmail.com> #105Sep 9, 2019 06:55AM

Yup i can confirm all these problems on Pixel 2XL, nothing works, even Do not disturb is not working.

im...@gmail.com <im...@gmail.com> #106Sep 9, 2019 07:27AM

No comments from Google, me and fcukboat found this issue since the beta6 came out, all the betas from 3 to 5 all sensors used to work, what happened to my case as what I explained at XDA is I used to be on beta with TWRP and rooted with all the sensors working, so when I decided to flash a custom ROM and eventually when beta6 came out I flashed it, fastboot, over the air with -W and reinstaling several times but beta 6 sensors are dead, tried going back to beta6 when sensors used to work, now after flashing beta5 sensors will not worked anymore. Tried the GSI version of the beta6 vbmeta and system.img all sensors are working, so when Official 10 came out, we thought it will work, but to no avail, luckily after several people at XDA figure out to dd the persist.img, all sensors are back, not sure though if it will stick if you factory reset the phone. Kudos to those XDA members who worked tirelessly to fixed this one and I hope GOOGLE will eventually do an over air fixed to this one.

vi...@google.com <vi...@google.com> #107Sep 9, 2019 09:47AM

Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

ba...@gmail.com <ba...@gmail.com> #108Sep 9, 2019 10:16AM

thanks sir. according to the info we got on xda the persist partition contains some unique information and calibration data about the HW of every specific phone, so copying over the persist partition from one phone to another is indeed fixing the sensors problem but the dirty way, it is not really so suggested it seems, for this reason it can't be probably considered a real fix but more a workaround, and getting a final/better and cleaner fix directly from google would be awesome.

regards
Rob

la...@gmail.com <la...@gmail.com> #109Sep 9, 2019 02:23PM

Having the same issue with no sensors working as well.

ly...@gmail.com <ly...@gmail.com> #110Sep 9, 2019 03:26PM

My pixel 3XL sensor was not working either with Android 10 (was working with P)
After I removed the screen protector and then the issue is fixed, the sensor functions are back to normal with Q.
The sensor algorithm seems more sensitive on Android 10

hf...@gmail.com <hf...@gmail.com> #111Sep 9, 2019 04:11PM

My pixel 2XL can not hear anything when pick up the phone calls with Android 10. After I reboot the device，I can hear the voice when I make the call. But if someone calls in, then anything went
wong, I can not hear anything either pick up the phone or call someone.
And chrome and google play store crashes at the time download started.

em...@gmail.com <em...@gmail.com> #112Sep 9, 2019 04:26PM

Sensor issue persists for me as well.

ro...@gmail.com <ro...@gmail.com> #113Sep 9, 2019 07:06PM

Pixel 1, same issue, mainly with the gyroscope, it takes me a few tries to get the orientation of my correct but is definitely happening more often since the upgrade. I noticed the brightness not adjusting properly also, didn't know it was a symptom of the update until this thread.

sa...@gmail.com <sa...@gmail.com> #114Sep 9, 2019 07:07PM

My Pixel 3's sensors are also acting up. The proximity and the adaptive brightness sensors on the Pixel worked on the beta versions of Android 10 but after upgrading to the full version, they are acting up.

fm...@gmail.com <fm...@gmail.com> #115Sep 9, 2019 07:09PM

sa...@gmail.com <sa...@gmail.com> #116Sep 9, 2019 07:21PM

For people having trouble making calls on Verizon after the update, I just uninstall my Verizon app and my pixel 3 XL now making calls. I don't know about the sensors but now I can make calls on my phone.

jk...@gmail.com <jk...@gmail.com> #117Sep 9, 2019 09:35PM

Same here pixel 2 updated to 10 and have no sensors

ja...@gmail.com <ja...@gmail.com> #118Sep 9, 2019 09:45PM

I want to thank Google for not taking time to address these issues and send out an emergency fix. since most of these issues were happening through beta but yet they chose to release the Android 10 on the unsusspecting public. Thanks for being as bad as Microsoft when it comes to fixing issues. You definitely save me a good bit of money next month when I don't buy the Google Pixel 4.

ra...@gmail.com <ra...@gmail.com> #119Sep 9, 2019 11:14PM

Pixel 3, stock, unrooted. Proximity sensor works intermittently, triggers OK but takes a long time to release. Worked perfectly prior to OTA update on 4 Sep. Confirmed behaviour using kinscreen and sensors toolbox apps.

du...@gmail.com <du...@gmail.com> #120Sep 10, 2019 12:03AM

aTOmPluS : AtOmXpLuS
Everything in AtOmXpLuS.CoM

bl...@gmail.com <bl...@gmail.com> #121Sep 10, 2019 03:01AM

I'm also having this issue on a Pixel 3 XL. Proximity sensor no longer works. In call screen is black and takes a long time to release after a call ends. Also, double-tap to wake device no longer works.

It goes without saying, but the failure of the proximity sensor, in particular, really really freaking sucks. I can't use my phone during calls. I also can't hang up during a phone call. I have to restart the phone. I also can't view notifications while on the phone, which severely impacts my ability to use the Pixel 3 XL as a work device.

Please freaking fix this issue.

li...@gmail.com <li...@gmail.com> #122Sep 10, 2019 03:26AM

I fixed the issue by removing the screen protector from my Pixel 3 XL!

I did some tests and realize that the Android 10 modified the algorithm of proximity sensor, I think the proximity sensor is too sensitive now, which can sense around 5cm, even the screen protector is quite transparent.

My phone is totally fine on Android 10 now!

ma...@gmail.com <ma...@gmail.com> #123Sep 10, 2019 08:39AM

Same problem on my Pixel 2 XL. :(
No solution, of course. They are bugs...

wj...@gmail.com <wj...@gmail.com> #124Sep 10, 2019 12:00PM

3rd Pixel phone I’ve returned.

First it was the pixel 3 proximity sensor
Second it was my pixel 3a front facing camera stopped working.
Now, after updating to android 10, I lost active edge, screen rotate, phone does not go black when I put phone to my ear after I’ve made phone call or received call .. Went to the store I purchased my phone and received a refund. Had the worst luck with this phone but thanks google! Case ID: 2-0624000027720

do...@gtempaccount.com <do...@gtempaccount.com> #125Sep 10, 2019 02:38PM

I have a Pixel 3XL on Verizon. As per previous post I uninstalled Verizon app and now phone is working on Android 10. Verizon app uninstalled was VZ Navigator.

31...@gmail.com <31...@gmail.com> #126Sep 11, 2019 10:49AM

Guys, if anyone still has problems and/or wants to fix his own persist partition, delete the cache folder on persist, install Android 9, let it bootloop for 2 min, install Android 10 again and enjoy your working sensors. A factory reset is not needed.

jo...@gmail.com <jo...@gmail.com> #127Sep 11, 2019 12:26PM

@31

How do you do what you noted above? Are there detailed instructions or a video available?

iv...@gmail.com <iv...@gmail.com> #128Sep 11, 2019 03:48PM

I have a Pixel 2 XL and after the Upgrade to Android 10 several sensors stoped working.
No ScreenLock during phonecalls, no Auto adjustment of the Screen brigthness, no Gyroscope, no Accellerator,
Would be nice to get a solution / fix for this in the next few days.

The only thing working imho is Location (GPS)

aw...@gmail.com <aw...@gmail.com> #129Sep 11, 2019 08:38PM

same issues here, proximity not releasing after a phone call ends by the other party, have to manually press power button several times, unlock, then swipe to notification of phone call to end on my device. how did this make its way into production?

em...@gmail.com <em...@gmail.com> #130Sep 11, 2019 08:55PM

Contacted Pixel support and they told me that only "a few people" have reported this issue to them and they asked me to send a bug report. After I sent them the bug report, I was asked if there was anything else they could help me with today.

Unbelievable. I was denied a replacement device because it's not technically a hardware issue. As a consumer I don't care if it's software or hardware based - but I know it wasn't my fault. I need a working phone. On asking them what my options are, the agent just apologized for the inconvenience. This situation and how Google is handling it blows my mind.

ca...@gmail.com <ca...@gmail.com> #131Sep 11, 2019 09:09PM

#130 I had waited for 2-3 days with the broken phone but then factory reset my Pixel 3a upon Google help person's suggestion, everything is working well right now.

em...@gmail.com <em...@gmail.com> #132Sep 11, 2019 09:18PM

#131 Factory Reset did not work for me Pixel 3

fi...@gmail.com <fi...@gmail.com> #133Sep 11, 2019 11:34PM

Pixel 3XL. Sensors will sporadically all stop working while phone is on. A simple restart temporarily fixes the issue.

la...@gmail.com <la...@gmail.com> #134Sep 12, 2019 02:03AM

I am having the same issues with sensors on Google Pixel 3XL.... Also my WiFi connection is constantly shutting off and then within 5-10 mins it re-connects. I didn't have this issue until I did the update and its with every WiFi device I have connected to (Home Work and Public)

ap...@opentable.com <ap...@opentable.com> #135Sep 12, 2019 12:45PM

I updated to Android 10 on my Pixel 2XL the day it came out. As others have mentioned, I did experience some sensor issues. Unlike others, however, the only sensors that had trouble were the ambient light and proximity sensor. I have never rooted, unlocked, or modded my phone in any way. It has always been on stock Android image. My update was from Android 9 to Android 10.

Oddly enough, a few days later I rebooted my phone and all sensor issues disappeared. I don't remember doing anything special other than turning off developer mode. I don't, however, think this is the reason for the failure although I don't have any ideas on why things work perfectly fine now.

This is not much of help, but perhaps just another data point.

jb...@gmail.com <jb...@gmail.com> #136Sep 13, 2019 12:54AM

Turning off developer mode and rebooting fixed sensor issues for me. Pixel 2XL. Hopefully they stay working.

th...@googlemail.com <th...@googlemail.com> #137Sep 13, 2019 07:46AM

updated Pixel 3 to Android 10...Having the same issue with no sensors working as well. No automatic display brightness, no wake up on double-tap, no display rotate.

be...@gmail.com <be...@gmail.com> #138Sep 13, 2019 07:50PM

Pixel 3: Ever since updating to Android 10 sensors are broken. Worst effect
is not being able to hang up phone calls because the screen is dark and
won't turn on. I tried setting the screen to "always on" but it still goes
blank for calls. Any reasonable fixes for this that don't involve getting a
new persist.img?

On Fri, Sep 13, 2019 at 2:46 AM <buganizer-system@google.com> wrote:

li...@gmail.com <li...@gmail.com> #139Sep 13, 2019 07:55PM

A temp solution would be to enable "power button ends call" under accessibility setting.

be...@gmail.com <be...@gmail.com> #140Sep 13, 2019 07:59PM

Thank you

On Fri, Sep 13, 2019 at 2:56 PM <buganizer-system@google.com> wrote:

slu.academia.edu/benjaminwinter <

ch...@gmail.com <ch...@gmail.com> #141Sep 13, 2019 08:18PM

I am having the same issue. When I make a call, the screen goes black, and won't allow me to hang up the call. Yes, I have a screen protector. Yes, I am clumsy so I need one. It is definitely due to the sensor by the ear being too sensitive.

Does anyone know if Google is working on this? This is my first Google phone and honestly, this is a PITA.

em...@gmail.com <em...@gmail.com> #142Sep 13, 2019 08:20PM

RE: #130 Had my RMA request granted.

da...@gmail.com <da...@gmail.com> #143Sep 14, 2019 10:24AM

I seem to be suffering with call problems, making a call, responce time tapping the app, freezing app, ending calls just like other people.

ho...@gmail.com <ho...@gmail.com> #144Sep 14, 2019 12:41PM

the application that was important to me could not be opened/error bug and sluggish so frustrating.

ve...@googlemail.com <ve...@googlemail.com> #145Sep 14, 2019 09:41PM

Though I don't face sensor problems as the most people in this thread I have major issues with the camera. After I updated my 3A to Q I cannot take photos any more with the camera app. Well I can take pictures but as soon as I navigate to the photos app the recent picture suddenly disappears and it's gone.

There is no way of taking pictures any more.....

ns...@gmail.com <ns...@gmail.com> #146Sep 14, 2019 10:18PM

i also faced sensor issues, but that was during beta. I tried to downgrade to Pie, but that didn't help the situation out any. Sensors still didn't work and WiFi didn't work either. Flashed back to Q beta 5 (maybe 6, can't remember), and the WiFi worked again, but nothing I did would fix the issue I was facing with the sensors. Ended up getting an RMA and a new device was delivered. Upgraded to Q, and it is working fine currently. Once I had the active edge go out on me for a bit, but a reboot seemed to fix that.

Something seems to be seriously wrong. This is not the first time that this issue has cropped up with the Pixel 3 devices. In my searching for things there was also a user in China (bought the phone new from a 3rd party reseller) that also ran into this issue on the help forums and nothing that he did fixed it either. Google is probably really glad they have the binding arbitration agreement in the TOS for the Pixel 3 devices (though I promptly opted out of it, both times) right now, cuz this is grounds for a class action lawsuit. Though, maybe enough people did opt out to provide enough of a group to become a class.

su...@gmail.com <su...@gmail.com> #147Sep 15, 2019 06:09AM

I have the sensor issue, doesn't happen on stock Q but happens on custom Q. Based on that, I believe it's either a vendor issue, since you can't boot custom without using the Google version of the proprietary vendor img. Or it's its issue with the new dynamic partitions and the first stage ramdisk. Obviously the sensors themselves are fine, since reverting to pie they will work.

It has to be sepolicy or a permissions issue. Given the sepolicy in the stock boot.img differs from the the output of aosp built sepolicy, using the same repos from stock manifest, I can only assume this is a result of either vendor or changes made to BoardConfig not represented in aosp source

And by differ in relation to sepolicy, I mean the stock boot.img's sepolicy when decompiled with dispol (stools) has a lot more than what aosp spits put.

lo...@gmail.com <lo...@gmail.com> #148Sep 15, 2019 05:00PM

I also have some issues. The bottom row of the home screen where Gmail, camera, phone and messages. Press them to use and they won't work. I have to restart and then they work. Been doing this since the system update. This is serious Google. You need a patch to help people.

pa...@gmail.com <pa...@gmail.com> #149Sep 15, 2019 06:16PM

Hey Google, how is this merely P2/S2?? Hundreds of users complaining for over two weeks and it takes you like a week to even assign the bug? Move faster!

sa...@gmail.com <sa...@gmail.com> #150Sep 16, 2019 12:52AM

My pixel earphone and mic stop working after 10 update, tried everything but nothing works, even the stock phone call app have same issue just like other users are facing. Surprised to see no answer or fix from Google. They are gonna lose a lot of pixel 4 sales next month for sure.

mc...@gmail.com <mc...@gmail.com> #151Sep 17, 2019 03:21AM

I have the exact same problem on the 3 and it's also killing the battery life.

Km...@cogeco.ca <Km...@cogeco.ca> #152Sep 17, 2019 10:56PM

I found the pixel 3 phone display shows too much green and not enough red in all my pictures, and is horrible to look at after upgrading to android 10. I wish I kept my phone with the previous software upgrade as I had no issues. I hope the issue with screen colour is fixed soon....not impressed. Also, the phone seems to drain the battery quicker than before.

sa...@gmail.com <sa...@gmail.com> #153Sep 18, 2019 03:49PM

I have a 1st gen Pixel XL with a Stilgut flip cover. I was running the latest stock version of Android 9 and all was well as it was with previous versions I've had on my XL). When I shut the cover, the screen went to sleep. When I opened the cover, I got the Ambient Display screen and I was a happy camper!

I upgraded to Android 10 via OTA. Since then closing the cover does not shut the screen nor does opening the cover wake the screen up again. All I can do is either press the power button to get to a lock screen or use the fingerprint scanner to unblock the phone.

I regard this as a bug/fault/error, not an "update" or an "improvement". Please fix the sensor issues ASAP.

Thank you.

dv...@gmail.com <dv...@gmail.com> #154Sep 18, 2019 05:38PM

My sensors stopped working too. Everything was fine under Android 9.0 but now none of the sensors work after the OTA update.

Please fix this issue as it's very annoying.

Thanks

th...@gmail.com <th...@gmail.com> #155Sep 19, 2019 05:39AM

I have a Pixel 1 and the lift-to-wake sensor has stopped working with my folio case after updating to Android 10 (Verizon).

Please patch this asap.

er...@gmail.com <er...@gmail.com> #156Sep 19, 2019 01:53PM

I had this problem (on a Pixel 3) until today -- a recent update to Pixel Ambient Services seems to have fixed it.

er...@gmail.com <er...@gmail.com> #157Sep 19, 2019 02:04PM

I spoke too soon -- Flip to Shh, double-tapping the screen (when it's locked), and listening to voice mail have all both worked, and failed, since the upgrade.

to...@gmail.com <to...@gmail.com> #158Sep 20, 2019 12:51AM

Pixel 3 + OTA update to 10 from 9 = slow calls, dead proximity sensor, etc.

Using power button to end calls and eventually get control back but in call am pretty much stuck if need to press digits, etc. No ability to join conference calls from calendar, etc...

as...@gmail.com <as...@gmail.com> #159Sep 20, 2019 03:26AM

Pixel 1, allowed the OS to upgrade to 10 today. Flip to wake brings up the wallpaper, but nothing else. The notifications across the top are frozen at what they were at the moment of upgrade and swiping down does nothing but freeze the screen until I press the home button twice.

st...@stushepherd.co.uk <st...@stushepherd.co.uk> #160Sep 20, 2019 07:54AM

I have similar issues. Proximity, flip to shhh and tap to wake don't work. A nightmare when trying to make calls. Especially when you have to access the keypad as it's impossible unless you disable sensors in developer mode first. I've had to assign my power button to 'end call' in accessibility to be able to hang up. Hope a fix is out soon. I've already been through safe mode and the pain of a factory reset.

ri...@gmail.com <ri...@gmail.com> #161Sep 20, 2019 03:26PM

This is happening to me too (pixel 2 XL). Proximity sensor or ambient light sensor seems to randomly give up working properly. It is mostly anoying.

lu...@gmail.com <lu...@gmail.com> #162Sep 20, 2019 10:50PM

Joining the broken sensors party, Pixel 3.

jc...@gmail.com <jc...@gmail.com> #163Sep 21, 2019 04:11AM

Ditto #162..Pixel 3a, stock Android 9, suddenly no attitude sensors... Never flashed to Q!! Last update was a security patch for Android 9 on August 1

je...@gmail.com <je...@gmail.com> #164Sep 21, 2019 06:48AM

On my Google Pixel 2XL doesn't work my Camera. It allways Crashed.

ga...@gmail.com <ga...@gmail.com> #165Sep 21, 2019 07:27AM

Proximity sensors and autobrightness not working with Android Q. Autorotation is working.
Pixel 2 xl, build QP1A.190711.020

sp...@googlemail.com <sp...@googlemail.com> #166Sep 21, 2019 02:12PM

Pixel 2XL After android 10 update my fingerprint sensor not working most time, it works when i press the wake up button on side, when phone sleeps 1 on 10 attempts maby work!!!!!!!

ca...@gmail.com <ca...@gmail.com> #167Sep 21, 2019 06:33PM

I'm a little bothered that I get notified every 6 hours to upgrade to Q, when this appears to be such a widespread and debilitating issue. I would rather not lose basic functionality of my phone. Consumers are still being pushed this update and it's definitely not stable

os...@gmail.com <os...@gmail.com> #168Sep 21, 2019 10:09PM

I've been in chat with Google for almost an hour about this issue and the chat rep said "we are are completely unaware of any of these issues related to the Android 10 update". This is seriously bothersome!

be...@gmail.com <be...@gmail.com> #169Sep 21, 2019 10:53PM

we are getting closer to next month's security update -- is there a decent chance this bug will be fixed? or should I forget about it being fixed and flash back to Pie?

jr...@gmail.com <jr...@gmail.com> #170Sep 22, 2019 09:44PM

If there are so many problems with the latest update, why was I promoted to update to it!?? Phone is acting crazy now! Calls aren't coming through, play store crashing, games crashing, calls dropping, battery literally draining a percent every 30 seconds... WTF!??? How does this get fixed???

ab...@gmail.com <ab...@gmail.com> #171Sep 23, 2019 01:56AM

Upgrade pixel 2XL yesterday, today i'm getting a green border around anything on the screen, have to double tap to get anything to work. There is no ability to swipe to get to next pages of apps, can't swipe to get off of the startup screen. What a mess - how can this be pushed to all pixel users with these problems????

rk...@gmail.com <rk...@gmail.com> #172Sep 23, 2019 06:05PM

Original Pixel XL worked awesome on P. Updated to Q and now it overheats, battery drains super fast, and play store does not function at all. It won't update or install anything and crashes after a few seconds. This WAS the best phone I ever had until this update. Please fix it!!!!

it...@gmail.com <it...@gmail.com> #173Sep 23, 2019 06:41PM

Sensors have stopped working on my Pixel 3 as well, wanted to chime in to help make it clear how many people this is affecting. I can't easily hang up phone calls, can't see my screen when I go outside to walk my dog, have to manually rotate every picture or video I take in landscape and save duplicates, can't see notifications when the phone is on the charging stand, etc. etc. It's very frustrating for all of the conveniences that made me switch to Pixel in the first place to suddenly disappear!

za...@segmint.com <za...@segmint.com> #174Sep 24, 2019 03:24PM

My Pixel 3aXL seems to have been affected by this bug today
Issues include the inability to connect to mobile data, most settings in the notification shade are gone, recent button is unresponsive. I had a similar issue when coming from P to the OTA, I then just flashed the factory image to see if that would fix the issue. Now it's back but more debilitating than before. FWIW I am rooted with a custom kernel but this issues first became apparent going from P->10, which would render the phone stock...

ba...@gmail.com <ba...@gmail.com> #175Sep 24, 2019 08:29PM

someone still experiencing the problem with sensors can check if latest OTA update just released fixes the issue?

cm...@gmail.com <cm...@gmail.com> #176Sep 24, 2019 11:55PM

I couldn't even get to the update my phone froze while I tried to reset it for the update to start I waited for it to die charged it turn on same thing and it pretty much went on for about 4 days I had to factory reset to fix it.

vi...@gmail.com <vi...@gmail.com> #177Sep 25, 2019 03:46AM

I have all of the above-mentioned issues regarding sensor failure, but mine randomly decided to inhibit this behavior exactly 2 weeks after the official release of Android 10.0. I also have the "PRIVELGE" of having a battery sensor issue where the phone always thinks my battery level is at 0% and the phone doesn't seem to show that it is charging beyond 0%. Thus, the phone dies after less than 20 seconds of use. Google Support is completely oblivious to this issue, since if they were, they would've made a fix for this for the recent Android C3 patch which I had to flash since the phone won't update unless battery level is over ~35%. GOOGLE PLEASE ADRESS THIS ISSUE!!! YOUR LACK OF RESPONSES IS FRIGHTENINGLY TERRIBLE!!

bl...@gmail.com <bl...@gmail.com> #178Sep 25, 2019 03:05PM

#175 -- I just updated to QP1A.190711.020.C3 this morning. No change to the sensor situation. Proximity sensor is still not functional. Double tap to wake is still dead. Phone screen still goes to black during phone calls. I'm on a Pixel 3 XL.

ba...@gmail.com <ba...@gmail.com> #179Sep 25, 2019 03:11PM

ok thanks for the info. so it will probably be next update to fix this issue, this is what google support told to us first reporters of this issue ;)

bl...@gmail.com <bl...@gmail.com> #180Sep 25, 2019 03:16PM

When is the next update supposed to be pushed to users?

I'm asking because I know there's a fix that involves rooting the phone and manually overwriting the persist image. I'm wondering if I should just go ahead and do that or wait it out.

ba...@gmail.com <ba...@gmail.com> #181Sep 25, 2019 03:50PM

they said should be soon, so I would wait if I were you. and if you do the persist image trick, backup your own persist partition first!

al...@gmail.com <al...@gmail.com> #182Sep 25, 2019 10:12PM

my phone upgraded this morning to android 10, now it will not turn on, seems dead, Google said to get it fixed somewhere and pay for it, i feel their software broke it, they should fix it. any ideas?

ja...@gmail.com <ja...@gmail.com> #183Sep 26, 2019 04:50AM

I have same issue. When especially when i am trying to hangup on the call. Screen is blank and does not wake up

bi...@gmail.com <bi...@gmail.com> #184Sep 26, 2019 04:43PM

My sensors (auto rotate and active edge) are not working on my Pixel 3xl with Android 10!!!

be...@gmail.com <be...@gmail.com> #185Sep 26, 2019 04:44PM

Installed the new update and sensor issue still present

[image: Saint Louis University]

Benjamin Winter, PhD

http://slu.academia.edu/BenjaminWinter>

benjaminwinter.us

On Thu, Sep 26, 2019 at 11:43 AM <buganizer-system@google.com> wrote:

https://www.androidpolice.com/2019/05/08/android-q-lets-you-quickly-disable-your-phones-sensors/

st...@stushepherd.co.uk <st...@stushepherd.co.uk> #186Sep 26, 2019 07:49PM

I also installed the update and my sensors are still not working. Proximity, tap to wake and flip to shhh. Currently on QP1A.190711.020.C3 on a Pixel 3 in the UK

ob...@gmail.com <ob...@gmail.com> #187Sep 27, 2019 12:15PM

Obedotoo@gmail.com....i have similar issue... Sensors have stopped working... I cannot wakeup the phone no matter how I try.

fo...@gmail.com <fo...@gmail.com> #188Sep 28, 2019 11:49AM

I experience the same issue here, all sensors in my Pixel 3 XL aren't working anymore after OTA upgrade to Android v10.

ro...@gmail.com <ro...@gmail.com> #189Sep 28, 2019 04:51PM

Sensors and now mobile\wifi network has stopped - factory reset without bootloader being unlocked and now cannot get past setup screen to re-enable debug model for recovery. spoke on google chat this morning - cannot help because i have a crack camera on rear when asked if there was damage. so now i have to pay $300 for insurance replacement off a free freaking upgrade that i didn't ask for.

ya...@oakbrookcorp.com <ya...@oakbrookcorp.com> #190Sep 28, 2019 04:59PM

Experiencing this on my Pixel 2 XL. Just 2 days ago, some of my sensors stopped working. They seemed to be fine after the Android 10 update until just a few days ago. Double tap to wake, ambient light sensor, proximity sensor all don't work. Active edge still works though... Really frustrating usability-wise so far. I would rather not downgrade to 9 and wait for a fix, but it seems to have fixed it for most others.

du...@gmail.com <du...@gmail.com> #191Sep 29, 2019 04:27PM

Can't search for contacts with key partial names. My contacts are there, but the search feature is not pulling them up. Haven't had a problem until I downloaded the update a few days ago.

wa...@gmail.com <wa...@gmail.com> #192Oct 1, 2019 12:32AM

Any update on these issues! Pixel 2XL phone screen goes black during calls, can't put on speaker phone or press numbers; can't check voicemail; dropping calls; unable to hang up calls; screen dead after calls and can't get to turn on for a couple of minutes...help!

vi...@gmail.com <vi...@gmail.com> #193Oct 1, 2019 07:12AM

I replaced the sensor ribbon cable and seemed to bring back the sensors for me. However the sqeeze sensor is still buggy as in keeps triggering randomly. This may be a hardware issue though.

rh...@gmail.com <rh...@gmail.com> #194Oct 1, 2019 04:40PM

I finally updated to 10 last night on a Pixel XL*. I usually try to wait for all the bugs to be fixed before updating and check issues before so I know what I'm getting into. But in the last few days the device stopped playing video / music out of its speakers. Calls & speaker phone calls work. Hoped it would fix it... Nope. Sound is still not working.

Now my play store doesn't work. I'm pending a ton of Google app update downloads. And the Play store / phone app setting screens crash every 15 or so seconds.

Haven't experienced any battery issues... But it's only been 18 hrs.

*Believe it's a refurbished XL, Google sent it to me 1.5-2 yrs ago after replacing my S5P a half dozen times. It was around the same time the Pxel 2 was released.

de...@gmail.com <de...@gmail.com> #195Oct 2, 2019 04:08AM

Pixel 3 here, screen shuts off when making or answering a call, won't come back on at all until the other end disconnects.

Tap to wake doesn't work. Lift to wake doesn't work. Face down to 'shh' doesn't work.

Active Edge and light sensor seem to work, brightness does adjust, and the Google Assistant comes up squeezing the phone.

tj...@gmail.com <tj...@gmail.com> #196Oct 4, 2019 04:17PM

Pixel 3. Proximity sensor shuts off the screen during calls. I don't use many of the other sensor features that others are reporting broken, so can't comment on those.

Potential workaround to the prox sensor at least is the screen comes back during the call if I connect a headset (wired or bluetooth). Doesn't help if you don't have a headset handy, but it at least gets the phone in a mode where it's not using the prox sensor.

em...@gmail.com <em...@gmail.com> #197Oct 4, 2019 04:45PM

Posted this workaround for the blank screen during call problem in another thread. You can disable your phone sensors with a quick dropdown in Android 10.

je...@gmail.com <je...@gmail.com> #198Oct 5, 2019 10:52PM

same here, upgrading to android 10 either with the ota or flashing the factory image results in active edge not working, flash back to Pie and all is well. hope this gets fixed soon

c....@gmail.com <c....@gmail.com> #199Oct 6, 2019 10:02PM

Phone app not functioning. Can't make or accept calls. Phone freezes and can't recover without hard restart.

ye...@gmail.com <ye...@gmail.com> #200Oct 7, 2019 04:26PM

I have the same issue......proximity sensor not working after upgrade, please fix it ASAP

st...@stushepherd.co.uk <st...@stushepherd.co.uk> #201Oct 7, 2019 08:40PM

Have completed the October system update and the problem still persists. SO frustrating. Not sure where to go from here.

wu...@gmail.com <wu...@gmail.com> #202Oct 8, 2019 03:18AM

Updated to Android 10 and all sensors stopped working.

wu...@gmail.com <wu...@gmail.com> #203Oct 8, 2019 03:18AM

Forgot to mention, Pixel 3

th...@googlemail.com <th...@googlemail.com> #204Oct 8, 2019 10:24AM

Also completed October Update today. The sensors are still not working. When will there be a fix? It is really frustrating and annoying

bl...@gmail.com <bl...@gmail.com> #205Oct 8, 2019 05:04PM

CAN WE PLEASE have a timeline for a fix, google. PLEASE.

bl...@gmail.com <bl...@gmail.com> #206Oct 8, 2019 05:09PM

#197 --> I can confirm that turning off sensors allows my phone to be used as an actual phone, now. IE, the screen doesn't go blank.

However, this means that I have to give up quick access to my camera just to use my phone as a phone.

Google. Fix your damned phones.

be...@gmail.com <be...@gmail.com> #207Oct 8, 2019 07:46PM

The temporary "turn off sensors" fix worked for me -- finally can use my phone _as a phone_ again.
I second and third the motion: can we please get some kind of timeline for a fix? :)

dj...@gmail.com <dj...@gmail.com> #208Oct 9, 2019 01:49AM

Hi, Just wanted to jump in and say I'm also having this same issue on a Pixel 3. Thanks for the turning off the sensors workaround, but that is not a great longterm solution obviously, hopefully this gets fixed soon!!

ma...@gmail.com <ma...@gmail.com> #209Oct 9, 2019 10:40AM

Got the same issue here, sensors not working, the recent update didn't help either

gu...@gmail.com <gu...@gmail.com> #210Oct 9, 2019 02:57PM

Same issue here... I got a Pixel3XL on android 10 (QP1A.191005.007)
Proximity sensor not working and its really annoying!
How can we disable the sensor?

df...@gmail.com <df...@gmail.com> #211Oct 9, 2019 03:02PM

My original pixel upgraded to the Oct 6 OTA this morning. Didn't fix the sensor problem. Still have the disabled screen on phone calls. Not having the ability to hang up on a phone call is a serious security issue.

bl...@gmail.com <bl...@gmail.com> #212Oct 9, 2019 07:14PM

https://forum.xda-developers.com/showpost.php?p=80233696&postcount=346

Google reportedly stated that the bug fix would be released in the October update.

The October update did not fix this issue.

Can we please get a response from a google dev regarding this issue?

ja...@gmail.com <ja...@gmail.com> #213Oct 10, 2019 02:36PM

same here :( just switched to Pixel 3 hence clean boot, data restore from Pixel 2XL and upgrade to Android 10.
Sensors not working.
Phone is not BL unlocked or anything, however I don't know if it was before I got it.

mj...@gmail.com <mj...@gmail.com> #214Oct 10, 2019 11:12PM

Keyboard speech to text no longer working after system update to Android 10 on a Pixel 3. Please fix this. It is my primary hands-free method. This is a safety issue.
Please fix as soon as you can,
Jennifer

dr...@gmail.com <dr...@gmail.com> #215Oct 14, 2019 09:35AM

Wow, this update must have really been rushed. Tons of things broken for me as well. Was holding off updating to 10 for a while, and it sounds like I should've kept waiting, especially if these serious known issues have existed for over a month now and made it into the "stable" release. Guess I'll have to downgrade. Would not have expected this on an official Google phone. Very, very disappointing.

[Deleted User] <[Deleted User]> #216Oct 14, 2019 09:57AM

This sensor problem is very serious, I can't operate the phone (3XL) when I listen to the phone, but still no solution is provided since September!

dr...@gmail.com <dr...@gmail.com> #217Oct 14, 2019 11:13AM

PIXEL 3XL: SINCE THE LATEST ANDROID Q BETA, LOST ALL SENSORS, ACTIVE EDGE AND FINGERPRINT TOO!!!!!

fi...@gmail.com <fi...@gmail.com> #218Oct 14, 2019 12:23PM

I have the same Sensor Problems in my Pixel 3XL. Reboot 2-3 Times per day.

Extremely annoying.

Please fix it asap.

ne...@gmail.com <ne...@gmail.com> #219Oct 14, 2019 05:57PM

All my sensors have stopped working on a Pixel 3XL. However I've never flashed a rom or used TWRP on this device so I can't see it being a corrupted persist partion for me.

ss...@gmail.com <ss...@gmail.com> #220Oct 15, 2019 11:22AM

Even i faced all these problems. None of the sensors would work. I had to change the screen protector from a tempered glass to a normal screen protector. The active edge is still not working though. I can squeeze it when i specifically go to the settings menu and adjust the squeeze settings but it won't work outside of that.
These are problems that make people dump brands

pe...@gmail.com <pe...@gmail.com> #221Oct 15, 2019 04:01PM

The October update fixed this for me until my first reboot after the installation. Now I'm back to no sensors after weeks of already having none. If this is how Google handles serious bugs on their flagship phones, this will be my last.

ni...@gmail.com <ni...@gmail.com> #222Oct 16, 2019 10:23AM

Having trouble with my phone not much is working sensor is messing up or hardly working can't turn mobile data on and keep it on froze half way through the update then came back to life lock screen don't show time anymore notification pull down bar does not work hate this I got very upset and cried so hard as thought i broke my phone I am a Google pixel 3a PLEASE GET IT FIXED ASAP PLEASE

mo...@hotmail.com <mo...@hotmail.com> #223Oct 17, 2019 02:12PM

I wish I had come to this forum before I updated to the Android 10. All the features I loved about the pixel 3 are non existent. No flp to shh,no display clock on lock screen, double tap to check screen,lift to check screen, shake to flip camera all are non functional. I feel ripped off now after spending so much on the phone. I essentially have a fake pixel 3. So so annoying I have to press my power button to check the clock or notifications. GOOGLE FIX THIS PROBLEM OR GIVE US THE OPTION TO SWITCH BACK. HEY REPLACE OUR DEVICES FOR THOSE WHO PURCHASED THEM DIRECTLY FROM YOU. VERY DISPLEASED

gr...@gmail.com <gr...@gmail.com> #224Oct 17, 2019 11:41PM

I am so very upset that this phone doesn't work properly..they better get it fixed quick. I talked to Verizon, and of course they had no clue.....the response of the special tech was "well google has good nerds, they'll get it fixed". They've be working on it for a month, and it's still not fixed. I guess next week I will take it back to Verizon and get a replacement for what I am paying for. How can they sell a Pixel 4 when the Pixel 3 doesn't work? Is this their upgrade Plan?

gu...@gmail.com <gu...@gmail.com> #225Oct 18, 2019 02:24AM

Its been 2 updates since I upgraded to Android10 and they still haven't fixed it. Is it only a few versions of the phone that have the issue or is it widespread???
Do we have an Idea if they even work on it? Priority abd Severity seems pretty high for something that long to fix...

I added the ability to hang up my call with the power button but still unable to access the keypad when doing a phonecall unless I have my earbuds connected. It is VERY annoying. I always was a google fan but as the days goes on, i'm less and less impressed by their flagship phones.. might go back to samsung...

ow...@gmail.com <ow...@gmail.com> #226Oct 18, 2019 02:46AM

Guys you do realize threatening to use other phones isn't gonna get this fixed any faster.

If I had to guess the Google developers are just as confused as to why this is occurring as you, and actively working on it (note the P1 tag). Have a little patience and let them do their job. Trust me, developers have to work to actually fix things and _it takes time_. Not like it's just a switch to flip, we're talking hundreds of millions of lines of code and thousands of possibile points of failure.

Another thing I noticed: most of you are not including logs or even such basics as what device you are using, and if you're using 100% pure Google stock. Complaining it doesn't work without any of that isn't very helpful

em...@gmail.com <em...@gmail.com> #227Oct 18, 2019 06:25AM

Except that a fix has already been identified by the community, and Google devs have already acknowledged that a fix will roll out in October. We just haven't heard anything about it since. This is a completely debilitating problem (see post 197 for my workaround), and ought not to take 1 month+ to fix.

ar...@gmail.com <ar...@gmail.com> #228Oct 18, 2019 09:26AM

Screen going blank everytime i make a call on Pixel 3 upgraded to Android 10....this is unbelievable that there is no fix yet from Google....

bl...@gmail.com <bl...@gmail.com> #229Oct 18, 2019 01:58PM

#226

This comment is infuriating. As #227 specified, the problem has *already* been identified by the community and fix has been found. That fix requires rooting one's phone and overwriting persist.img with a known-good copy.

But, moreover, threatening to use other phones for this kind of issue is perfectly legitimate. One of the primary reasons many buy Pixel phones is to get a pure Android experience. The assumption is that, at the very least, Pixel phones will offer a much more streamlined and reliable Android experience.

This is a *major* update that has introduced widespread problems. The update was pushed out TWO MONTHS AGO, and this issue has only JUST be promoted to a P1.

There is absolutely no way around this but to recognize that Google has absolutely botched the handling of this issue.

ow...@gmail.com <ow...@gmail.com> #230Oct 18, 2019 02:11PM

#229 #227
This isn't a fix. It's a workaround. Google has to figure out what the heck 10 is doing to mess up your persist partition in the first place. I guarantee that you do not know the underlying reason

An OEM can't do what you want from an OTA. They have to fix the underlying problem which is God knows what

You ever develop a ROM or heck anything? No? OK then don't tell developers how to do their job (PSA: I maintain two ROMs and two magisk modules. And let me tell you sometimes these things DO take months to fix).

And know, going on an issue tracker to complain that you're going to switch IS NOT APPROPRIATE. This isn't Facebook, it's the AOSP issue tracker.

ng...@gmail.com <ng...@gmail.com> #231Oct 18, 2019 03:30PM

I just stumbled over this thread. I posted a similar problem Sep. 6th. It has also only just (9 days ago) been updated to P1 but is still S2. I certainly agree with everybody here, that this is a P1 - S1 issue. I certainly hope it will soon be solved. Otherwise I will request a new phone from Google.

https://issuetracker.google.com/issues/140572164

Ciao
Nick

em...@gmail.com <em...@gmail.com> #232Oct 19, 2019 04:45PM

#230
I'm not telling developers how to do their jobs vis-a-vis coding. That is genuinely outside my expertise.

What I would tell them is to not break, in a seriously debilitating way, something that I purchased in the first instance. And barring that, to fix it ASAP, to actively give as workarounds, and to find a way to keep us up to date on their progress.

The difference between your hobbyist mods and my phone software is that I paid for this, and I did not elect to risk the functionality of my phone with this "update."

You may rightly dispute whether this is the right place to threaten boycott (and one might dispute whether this is the right place for us to be having this conversation at all). And you may also be right that Google may not be spurred to any more urgent action based on complaints. But surely you realize that we generally have little real leverage when it comes to corporate bad behaviour besides boycott, and surely you can sympathize both with consumers' frustrations at the same time as the coders' frustrations.

bl...@gmail.com <bl...@gmail.com> #233Oct 19, 2019 06:45PM

#230

Yes. I do. I'm a firmware developer who works in these kind of environments every day.

I can say WITH EXPERIENCE that two months of relative silence on behalf of Google devs on an issue that impacts many, many customers is absolutely reckless management.

In my line of work, updates that render key features unusable and causes basic use cases to fail is unshippable. If we discover these in the field, they become immediate priority, and our customers are aware, at least, that the issue is known to devs.

We haven't received any information from devs regarding this issue short of a second-hand post on an external forum which specified that this issue would be fixed in the October update.

bi...@gmail.com <bi...@gmail.com> #234Oct 19, 2019 08:46PM

I have not done anything beyond 'normal use' with my Pixel 3xl. Sensors not working, even after October update. Only thing I've done is had screen replaced at UbreakIfix. Please increase priority.

gt...@gmail.com <gt...@gmail.com> #235Oct 20, 2019 05:15PM

Same here on my Pixel 3XL,
"When I make a phone call, the screen goes dark and no swiping or pressing of the power button brings the screen back on. If the call goes to voicemail, you can's see the dial pad to respond to prompts." Also have a few other freezes and crashes at random times. About to revert back to Pie now, can't possibly use my phone like this. When will it be fixed??

be...@gmail.com <be...@gmail.com> #236Oct 21, 2019 11:51PM

Same issue here

le...@gmail.com <le...@gmail.com> #237Oct 22, 2019 08:03PM

Also affected by this problem. Have the latest QP1A.191005.007 on Pixel3.

yu...@gmail.com <yu...@gmail.com> #238Oct 23, 2019 11:44AM

Same here. Is there any fix yet? If I'll vring my phone to a google repair store, can they fix it on the spot?

ra...@gmail.com <ra...@gmail.com> #239Oct 23, 2019 03:09PM

Pixel3 was fine, new security update automatically restarted, prompting the update and now none of the sensors work properly. I also can't use the double-tap power button to open camera, home button has touch reaction on sensitivity but Nothing Happens, can't even swipe down to adjust screen brightness. I'm so angry, I can't even USE my phone like this. When is this going to be fixed? I would barely consider my Pixel3 "functional" as it stands now.

ph...@gmail.com <ph...@gmail.com> #240Oct 24, 2019 08:35PM

Replaced persist image file with shell dd command seems to fix it but the phone must be rooted to do that. Might be nice if it's fixed so that those that don't like to root can also get it working.

ph...@gmail.com <ph...@gmail.com> #241Oct 24, 2019 08:43PM

It would be nice if we could see what developer is doing to fix this and progress he or she is making. It's been 2 months and still no new information on when it'll be fixed

vi...@gmail.com <vi...@gmail.com> #242Oct 24, 2019 11:32PM

I talked to a Google Tech Support representative before this bug page was given a P1 status, and she told me to just wait for the next update. Wouldn't even give me a replacement device. What are the developers doing all this time?

bl...@gmail.com <bl...@gmail.com> #243Oct 29, 2019 02:36PM

To any moderator or developer monitoring this issue:

Can we expect a fix in the November update?

pe...@gmail.com <pe...@gmail.com> #244Oct 29, 2019 02:40PM

https://issuetracker.google.com/issues?q=id%3A(143505091%7C143505090%7C143505089)

pe...@gmail.com <pe...@gmail.com> #245Oct 29, 2019 02:40PM

Add a component (perstrong.online)

pe...@gmail.com <pe...@gmail.com> #246Oct 29, 2019 02:42PM

143467034, 143523899, 140476661, 140369522, 143523402, 143523401, 143523898, 143505097, 143505096, 143505094, 143487459, 143505091, 143505090, 143505089, 143523400, 143523399, 143523398, 143505098, 143468773, 143057655, 143505095, 143503334, 143512893, 143273716, 143512889

is...@gmail.com <is...@gmail.com> #247Oct 30, 2019 12:06AM

Same issue here

we...@gmail.com <we...@gmail.com> #248Oct 30, 2019 05:38AM

Same issue but restart in safe mode has sensors working?

he...@googlemail.com <he...@googlemail.com> #249Oct 30, 2019 07:10AM

Same issue with AutoBrightness, Rotation, etc...
restart in Safe Mode is working. After restart in normal mode again, all Sensors are working for a while. After a couple of hours its not working anymore. I have removed any App that i dont need. So only essential Apps for Work and messaging are installed.

su...@googlemail.com <su...@googlemail.com> #250Oct 30, 2019 06:05PM

Same issue here, I upgraded to 10 on sailfish via OTA and all sensors bricked, including proximity, accelerometer etc. Booting into safe mode makes no difference and neither does factory reset. I sideloaded latest Android p to try and revert and the sensors still didn't work! Can't honestly see how they will fix this with a software update.

vi...@google.com <vi...@google.com> #251Oct 31, 2019 12:42PM

Our Engineering team is still working on this issue. We will provide more updates as they become available.

sn...@gmail.com <sn...@gmail.com> #252Oct 31, 2019 05:21PM

Added article content,Fixed article typos,Optional artiCB le contents link,Any other way to improve this article

mu...@gmail.com <mu...@gmail.com> #253Nov 1, 2019 02:01PM

Since the latest Google 10 update, I am unable to print from my phone. I've checked all settings and no luck

le...@gmail.com <le...@gmail.com> #254Nov 2, 2019 04:47AM

Same here : no auto-rotation, no active edge, etc. since Android 10 update on my Pixel 3

pe...@gmail.com <pe...@gmail.com> #255Nov 2, 2019 07:12AM

C:\Новая папка\perstrong.htm

gu...@gmail.com <gu...@gmail.com> #256Nov 4, 2019 08:26PM

Just got the November patch on my pixel 3XL 10(QP1A.191105.003).
Still having issues with my proximity sensor.

Anyone knows if there is another issue number were work is being done regarding this? Doesn't seems to have any updates here...

I can't properly use my phone as I often need to access my dialpad while on a call.... Really frustrating...

ng...@gmail.com <ng...@gmail.com> #257Nov 5, 2019 04:13PM

To gu...@gmail.com

there is this issue

https://issuetracker.google.com/issues/140572164

It was upgraded from P2 to P1 on Oct. 9th only to be down graded again from P1 to P2 on Nov. 5th. This is really frustrating!

ni...@gmail.com <ni...@gmail.com> #258Nov 5, 2019 06:20PM

Same issue here as far as sensors not working after the November update on my Pixel 3 :(

bl...@gmail.com <bl...@gmail.com> #259Nov 5, 2019 09:37PM

No change here, either. Glad to see a google mod comment on the progress--

--but, if I'm being honest, this issue has existed since September and my patience has run out. I guess I will have to root my phone and fix this issue myself. But this will be the last Google phone I purchase.

le...@gmail.com <le...@gmail.com> #260Nov 5, 2019 10:50PM

November's upgrade fixed all my sensors except for the Magnetometer and Compass sensors.

I would like to know what physical hardware (chip) is used by these sensors as my phone says they don't exist (!).
Can someone with a Pixel 3 shared this information?

One way to find out is to install a sensor app (eg:

https://play.google.com/store/apps/details?id=ru.andr7e.sensortest&hl=en) and click the "INFO" button on the respective sensor. Attached is an example for the Barometer sensor.

Thank you in advance.

Pixel3_SensorTest1.png

94 KB

Pixel3_SensorTest2.png

62 KB

bi...@gmail.com <bi...@gmail.com> #261Nov 6, 2019 12:06AM

Neither October nor November updates corrected my Pixel 3xl sensor issues that started with Android 10. 2 swings, 2 misses.

ro...@gmail.com <ro...@gmail.com> #262Nov 6, 2019 01:39AM

Having the same issues on Pixel 2, android 10, Oct and Nov security updates applied.

sk...@gmail.com <sk...@gmail.com> #263Nov 7, 2019 08:26AM

November release has finally fixed some of the sensors. Auto rotate back working which was extremely frustrating. Still have light sensor not working so no adaptive brightness or proximity sensor. Phone is almost back to being worth what I paid for it after 2 months. Any updates on full fixes for all issues?

it...@gmail.com <it...@gmail.com> #264Nov 7, 2019 09:57AM

Me too, same issues on Pixel 2, android 10, installed both Oct and Nov security updates.

it...@gmail.com <it...@gmail.com> #265Nov 7, 2019 10:00AM

I meant the same issues like before. Nothing was fixed (unlike

comment #263

jp...@gmail.com <jp...@gmail.com> #266Nov 8, 2019 09:00PM

I bought a brand new Pixel 3a last week and within 3 days it tried to install Android 10 which I hadn't even clicked on to do. I like to look online first before I do anything like upgrade to a new version and as it turned out, it would have been a good idea if I'd been given the chance! This froze my phone up with the lighted G home screen on for two days and nothing I did would turn it off. Finally I googled the problem and found all the complaints. It did give me the fix to hold the on button down for 30+ sec no matter how many times the phone rebooted and then quit within 2 sec. After about 3-4 ups and down the old home screen came back on and I got the message that my upgrade had failed...thank goodness. I'm still on Android 9 and I'll stay there til it's fixed and the geeks say it's safe to go ahead again.

I had upgraded my old Pixel 1st gen to 10 a few weeks back and it seemed OK on that phone only that now the phone shuts off randomly when the battery is below 50% so I had to carry a portable charger pack around with me all the time. I had bought that one rehabbed over 2 years ago and the battery was getting to the point that I only got half a day out of it even with all the consuming stuff turned off, so I thought it was tinme to upgrade. But the shutting off under 50% seemed to concur with that upgrade. Now with no SIM card in it it still works great for casting to my Chromecast dongles because for some reason my Atvio and LG TV's won't accept casting from my Chromebooks, only my Samsung TV will and now that unit is in my downstairs apt that I rent out.

Waiting for the fix to arrive.

su...@googlemail.com <su...@googlemail.com> #267Nov 8, 2019 09:35PM

comment #266

: It doesn't sound like your issues are at all related to the bug that this thread is concerned with.

vi...@google.com <vi...@google.com> #268Nov 14, 2019 06:31AM

Kindly provide the below details:

- Share new bugreport on the latest build.

- We also need a couple of bugreports right after booting up the device and seeing none of the sensors are working. Is the behavior same after reboots?

gt...@gmail.com <gt...@gmail.com> #269Nov 14, 2019 07:24AM

November update not fixed my problems at all, phone still crashes every time I make a call, only option is to hold the power button down until it reboots, something I have to try multiple times before it'll work. Ridiculous!

wi...@gmail.com <wi...@gmail.com> #270Nov 14, 2019 03:32PM

I believe the latest Android OS update on my Pixel 3 has caused almost all my sensors to stop working. How do these updates make it pass QC to get pushed out to customers?
Now, auto screen rotate, auto back light control, etc do not work.

su...@googlemail.com <su...@googlemail.com> #271Nov 14, 2019 03:59PM

A bug report from when I freshly booted my phone, rebooting has never made any difference to the issue in my experience, it persists all the time. Hope you can fix this soon, it's not easy to use the phone for phone calls if the screen doesn't turn off.

bugreport-sailfish-QP1A.191005.007.A1-2019-11-14-15-45-03.zip

10 MB

bi...@gmail.com <bi...@gmail.com> #272Nov 15, 2019 07:45AM

Sensors still not working after trying the Google recommended Factory Restore. Shouldn't have even tried, if anything made symptoms worse
Pixel 3xl, Android 10. Sensors all not working.

le...@gmail.com <le...@gmail.com> #273Nov 15, 2019 04:43PM

Lost light and proximity sensor (no hangup button, just a black screen for the current call after moving phone away from face). Rebooted, light sensor came back but proximity sensor has no data. Compass or magnetic sensor broken since first android 10 upgrade (Pixel 3, now on Android 10 Nov patch)

ka...@gmail.com <ka...@gmail.com> #274Nov 17, 2019 07:23PM

Lost light sensor, squeezing sensor and auto rotation after November security uupdate. No issues before. Factory reset didn't help. I've noticed that's auto rotation sensor works once per several reboots.

ko...@gmail.com <ko...@gmail.com> #275Nov 19, 2019 02:36AM

Lost all the sensor functionality after the November security update. Double tap to wake, lift to wake, active squeeze all won't work.

vi...@google.com <vi...@google.com> #276Nov 19, 2019 03:58AM

Re-

Comment #271

, thanks for the bugreport.

Additionally, requesting affected users to please share bugreport for Pixel 3/3 XL devices.

fe...@gmail.com <fe...@gmail.com> #277Nov 19, 2019 06:47PM

All my sensors (Lost light sensor, squeezing sensor and auto-rotation) broke after the Nov Update. I have a Pixel 3.

I did a factory reset and they were still not working.

After doing a power off and power on, all the sensors don't work. Here is the bug report: bugreport-blueline-QP1A.191105.003-2019-11-19-18-42-24.zip

If I then restart my phone, the auto-rotation starts working again, but not the other sensors: bugreport-blueline-QP1A.191105.003-2019-11-19-18-36-17.zip

bugreport-blueline-QP1A.191105.003-2019-11-19-18-36-17.zip

8.7 MB

bugreport-blueline-QP1A.191105.003-2019-11-19-18-42-24.zip

9.6 MB

ka...@gmail.com <ka...@gmail.com> #278Nov 19, 2019 07:09PM

Please find reports for #274 attached. Identical symptoms as #277. First bugreport with auto rotation working, second after reboot without auto rotation. In both cases not working light sensor and squeezing. Symptoms started after Nov security update. Factory reset didn't help. Pixel 3.

bugreport-blueline-QP1A.191105.003-2019-11-19-20-01-00.zip

5.5 MB

screenshot-2019-11-19-20-01-00-1.png

249 KB

bugreport-blueline-QP1A.191105.003-2019-11-19-19-56-52.zip

5.2 MB

screenshot-2019-11-19-19-56-52-1.png

422 KB

vi...@gmail.com <vi...@gmail.com> #279Nov 24, 2019 11:04PM

Having the same issues. Proximity, ambient light, accelerometer, active edge, all not working.

https://drive.google.com/file/d/1-YZ9qtPr4w7g0qp6Nun1e2pT_PVftjvn/view?usp=drive_web (bugreport-blueline-QP1A.191105.003-2019-11-25-10-00-16.zip)

vi...@google.com <vi...@google.com> #280Nov 25, 2019 07:57AM

Please provide access to the above link.

fe...@gmail.com <fe...@gmail.com> #281Nov 25, 2019 08:01AM

Follow up to #277 . Somehow, my phone started working again after a restart, all the sensors seem to be working again. Here is the bug report. Hopefully, it helps:

bugreport-blueline-QP1A.191105.003-2019-11-24-20-12-55.zip

8.6 MB

ka...@gmail.com <ka...@gmail.com> #282Nov 25, 2019 11:47AM

Follow up #278. For me restart also helped today for all the sensors.

I've noticed that yesterday my "Google" app had an update - maybe related.

ro...@gmail.com <ro...@gmail.com> #283Nov 25, 2019 05:59PM

Ambient Light sensor failed for me a few days ago, and after doing a reboot of the phone just now, all sensors have now failed.

Running QP1A.191105.003 - have a full bugreport.

This is bad!

bugreport-blueline-QP1A.191105.003-2019-11-25-12-53-58.zip

11 MB

ro...@gmail.com <ro...@gmail.com> #284Nov 25, 2019 08:53PM

Rebooting a second time and the sensors returned (except the light/proximity one).

Rebooting a 3rd time, they disappeared. Doing a 4th reboot to safe mode and it didn't seem like they returned. Rebooting out of safe mode and they came back (minus the light/proximity one).

I think I've got the bug reports for each reboot if needed.

pa...@gmail.com <pa...@gmail.com> #285Nov 29, 2019 01:39AM

I just bought 2 brand new Pixel 3A XL's which have Android 9 on them.

System Update shows that Android 10 is available for download and install.

What is the status of these issues, has the problem been fixed or should I delay installing Android 10 on the devices?

Thanks!

ng...@gmail.com <ng...@gmail.com> #286Nov 29, 2019 06:49PM

Hi pa....

The problem has not been fixed for me. I am waiting for Google to send me a new (replacement) phone. I will try to update it to Android 10, because I simply don't want my phone on 9. But if you can wait - I would recommend that for now.

Nick

pa...@gmail.com <pa...@gmail.com> #287Nov 29, 2019 08:04PM

Hi Nick,

Thanks very much for that update. Overall we really like the phones but it is disturbing to me to see the update pushed out and having such a serious issue.

Where is the best place to check and/or be notified when the issues with the sensors after updating to Android 10 is fixed?

Thanks!

Joe

da...@gmail.com <da...@gmail.com> #288Nov 29, 2019 09:36PM

If you have a warranty on you phone - file an RMA to get a replacement. I
gave up waiting. The refurb unit I got came loaded with 9... and it
successfully upgraded. whew. Google should be ashamed for not better
supporting its customer base, breaking our devices with their software
updates. Not Cool Google.

On Fri, Nov 29, 2019 at 3:04 PM <buganizer-system@google.com> wrote:

pa...@gmail.com <pa...@gmail.com> #289Nov 30, 2019 05:42PM

Hi NIck,

How old is your phone and did you run the betas?

In researching this it seems like the problem may be caused by a corrupted /persist partition.

Our phones are brand new (only a week old) so I'm wondering if we would not experience the problem as they have not had any updates or much change for the corruption to have occurred yet?

I found the following factory images for the Pixel 3A XL as being available:

10.0.0 (QP1A.190711.020, Sep 2019) Link 1f47c677bcb3ce427103a6388e3f07fb8a03789353cfd3baceb6c24e13b62f9a
10.0.0 (QP1A.190711.020.C3, Sep 2019) Link ffac7a4a1412546609f3dddffa6f83b5dc61ad424cf625b9c71429ddd2726cb6
10.0.0 (QP1A.191005.007, Oct 2019) Link 9754d7c6c75199cc3c45eac5a9bf0ae685c3ce75e84b079e2a58af01b896e89a
10.0.0 (QP1A.191105.003, Nov 2019) Link 2c1af983da0c508f44a2c715f20850b5e7d82ee66d0ac0ab225e0cc855a04047

The first one appears to be when people updated and had the problem so I'm wondering if one of the other images fixed the sensor issues but I have not yet found a detailed change log to confirm this.

Do they post a changelog of fixes for the different images/builds?

Thanks!

Joe

ng...@gmail.com <ng...@gmail.com> #290Nov 30, 2019 10:34PM

Hi Joe,

My phone is a little over a year old. I received it shortly after the release of the pixel 3. I never had a beta version installed. Also after the update to Android 10 and the problem showed up, I tried a factory reset. This was not helpful - the problem was still there.

Ciao
Nick

ka...@gmail.com <ka...@gmail.com> #291Dec 1, 2019 09:20AM

Follow up #282. Problem seemed to be solved till first reboot. All the symptoms returned afterwards. Next reboots do not help - no light sensor, no squeezing. Auto rotation seem to work after shutdown/start, but not after reeboots (same in my original report).

I'll wait till Dec update. If it won't help I'll return the phone to the shop (second time).

bi...@gmail.com <bi...@gmail.com> #292Dec 3, 2019 07:45AM

Does the December update address the sensor issues?

su...@googlemail.com <su...@googlemail.com> #293Dec 4, 2019 09:02AM

Quite pissed off that Google pushed the December update (which it announced is the last update my sailfish pixel will ever receive) and it hasn't fixed any of the sensor issues. Seems like they've just messed it up with 10 and there won't ever be a fix coming.

em...@gmail.com <em...@gmail.com> #294Dec 4, 2019 09:34AM

As google is unable/unwilling to fix this, is there a comprehensive guide to rooting and over-writing the persist image? How risky is this procedure, and will it affect google fi features?

Thanks.

ka...@gmail.com <ka...@gmail.com> #295Dec 4, 2019 02:40PM

Dear Google, as December update didn't fix the issue, could you please provide an instruction how to solve it (if it's known) even if it requires rooting the phone and is somehow risky? For some it might be easier than arranging another warranty replacement (travelling).

bi...@gmail.com <bi...@gmail.com> #296Dec 4, 2019 05:16PM

Outrageous Google hasn't addressed this issue in one of 4 updates since they broke these phones with Android 10. Or provided some feedback on what is going on.

A real black eye for their Pixel brand. Let the RMA parade begin!

pa...@gmail.com <pa...@gmail.com> #297Dec 4, 2019 06:56PM

bi...@gmail.com,

Which Pixel device do you have where you are having the Sensor issues?

I contacted Google Support the other day to try and get something official that the issue has been addressed. He said that Google was not aware of the issues.

I pointed the support person to this discussion and was first told that Google did not comment on 3rd party sites to which I pointed out that this is not a 3rd party site and is instead a Google hosted site where users have reported the issue with the Android 10 update causing the sensors to stop working.

He did some research and then said I should to the update and be ok and sent me the following email:

Thanks for contacting Google support.

This email is in regards to the chat conversation we had today. As discussed, we recommend to go ahead and install the Android
10 update on your Pixel 3a XL device. Should you need any help, contact us or reply to this email and we'll be happy to help.

I pressed for a link to a change log for Android which show that sensor issue had been addressed but was not given one.

I have the Pixel 3A XL but have not yet upgraded to Android 10 because I've been waiting for something official which says that the issue is fixed.

Have you tried flashing back to the Android 9 OTA update?

Wouldn't that get the sensors working again?

It seems like the issue is with the /persist partition becoming corrupted.

Is there a way we could back that up and then restore after updating to Android 10 if the sensor issue occurred?

Seems like Google should have been able to issue an update which restored the /persist partition to fix the issue???

I don't understand why these problems have dragged out, getting 3 years of OS and security updates and getting faster updates/fixes was one of the big reasons we went with a Pixel.

Is this a reoccurring situation with Google updates???

Joe

su...@googlemail.com <su...@googlemail.com> #298Dec 4, 2019 07:04PM

Comment #297

: i don't know if it'll be the same for the 3A but I flashed my sailfish pixel back to Android 9 (which was a massive pain) and the issue remained so I'd say dont count on it.

pa...@gmail.com <pa...@gmail.com> #299Dec 4, 2019 07:17PM

su...@googlemail.com

Did you flash back to Android 9 using the Factory Images or the OTA Images?

Google seems to recommend using the OTA images in most cases since I believe you don't have to unlock the boot loader, however, I am wondering if you unlock the boot loader and flash with the factory image if that would restore the /persist partition and fix the sensors?

If that worked, then maybe you could backup the /persist partition, install Android 10 and then restore the /persist partition to get things working on Android 10.

Just thinking out loud here, but hoping to find a recovery option as I'd like to upgrade to Android 10 but am holding off until either a solution or a recovery option is available and verified to work.

Joe

em...@gmail.com <em...@gmail.com> #300Dec 5, 2019 01:37PM

Can anyone confirm whether flashing an OTA Android 9/Pie image will work, following these steps here:

https://developers.google.com/android/ota ?

Will I have the option then to hold off on updating to 10?

Thanks.

su...@googlemail.com <su...@googlemail.com> #301Dec 5, 2019 02:16PM

Pa...@gmail.com

Hi, yeah I flashed both the OTA update and factory images and neither worked, I'm thinking whatever got fucked up with /persist when Android 10 was installed is permanent and no software update will be able to fix it. I think the only way will be to get a new /persist from someone with the same model phone

ur...@gmail.com <ur...@gmail.com> #302Dec 6, 2019 04:56PM

Same Issue is happening with my pixel 3a xl , after I update it to android Q all sensors stopped working when everything was working fine with Pie , Is there a solution already or do I need to wait until the next update?

pa...@gmail.com <pa...@gmail.com> #303Dec 6, 2019 09:14PM

All,

FWIW, after talking to Google as well as my carrier, I updated BOTH of our Pixel 3A XL phones from Android 9 to Android 10 today.

First they installed the 2nd Sept 2019 Android 10 version (QP1A.190711.020.C3, Sep 2019) and then they installed the Oct 2019 update (QP1A.191005.007, Oct 2019), and then finally the Nov 2019 update ((QP1A.191105.003, Nov 2019).

Notably they did NOT first install the first Sept 2019 Android 10 Update (QP1A.190711.019, Sep 2019).

This leads me to wonder if the 1st Android 10 update in Sept 2019 is/was the source the problems people were having and possibly why it was not downloaded to our phones and instead they started with the 2nd Sept 2019 Android 10 update.

So far both phones seem to be working and no sensor issues and I have also rebooted as well as powered off both phones several times and then restarted to make sure everything was still working.

So far so good.

Figured I'd share with others that have been having the problems.

It would be interesting to see if those that are having the problems also are the ones that first installed the QP1A.190711.019, Sep 2019 update instead of starting with the 2nd Sept 2019 update as we did.

Hope this helps someone!

Joe

an...@gmail.com <an...@gmail.com> #304Dec 8, 2019 04:35AM

I am just a "me too". I had hoped for a fix in December, but no go. I waited too long and my phone is off warranty, so Google support only says "sorry" which is frightfully bad considering their bug introduced the issue. The suggest that I pay someone to fix my phone by sending it in or going to a repair shop, which is a 3 hour round trip drive for me. Ugly situation for what I thought was a good phone.

vi...@google.com <vi...@google.com> Dec 9, 2019 09:03AM

Reassigned to cc...@google.com.

cm...@gmail.com <cm...@gmail.com> #305Dec 9, 2019 04:02PM

I am facing the same issue on a clean, public install of Android 10.

None of the sensors (active edge, flip to shhh, proximity, ambient light, double tap to wake) work.

ch...@gmail.com <ch...@gmail.com> #306Dec 10, 2019 01:18PM

Exactly facing the same issue for me

ro...@gmail.com <ro...@gmail.com> #307Dec 12, 2019 12:58PM

An update from earlier - Just got an os update to qq1a.20191205.008 and all my sensors (including the light and proximity) have returned after the reboot. Here's hoping it's permanent!

ng...@gmail.com <ng...@gmail.com> #308Dec 12, 2019 07:07PM

I know this is not helpful for everybody, but I received my RMA phone yesterday - Pixel3 in white (I had a black one, which I liked more). I have run through all the updates to 10 (system and security). Everything is working fine - all sensors are doing what they should. I hope this will stay this way. By the way - the old phone is still not working the way it should and will be sent back to Google.

I am now on:

10(QQ1A.191205.008)

ry...@gmail.com <ry...@gmail.com> #309Dec 15, 2019 02:11PM

root/mnt/vendor/persist/sensors same here this is bullshit

bl...@gmail.com <bl...@gmail.com> #310Dec 16, 2019 08:17PM

I had my phone RMA'd, too. Was tired of waiting.

ca...@gmail.com <ca...@gmail.com> #311Dec 17, 2019 04:34AM

Saludos.
Actualice mi Redmi Note 4 a pixel experience Android 10, y el mismo fallo. Todos los sensores desactivados. Alguna solución pronto por favor!!!

ch...@gmail.com <ch...@gmail.com> #312Dec 23, 2019 02:36PM

I am also facing this issue on my pixel 3. Please come up with a solution soon

[Deleted User] <[Deleted User]> #313Dec 23, 2019 04:55PM

I am also facing this issue on my pixel 3.
Why the solution is not ready Mr Google?

mo...@gmail.com <mo...@gmail.com> #314Dec 25, 2019 12:53AM

After being forced into a factory reset by the youbreakifix repair shop (bottom speaker had gone dead) I'm having issues with all sensors. No squeeze for assisted tno proximity sensor, no double tab to wake, no auto rotation, etc etc. This being and issue for so many Pixel users, how can this not be fixed with priority? Pixel 3a xL here btw.

br...@gmail.com <br...@gmail.com> #315Dec 31, 2019 08:03AM

Auto rotate feature on my Pixel 3 is not working since updating software. Please fix this issue.

ni...@gmail.com <ni...@gmail.com> #316Dec 31, 2019 09:04AM

I am also having trouble with the sensors. I received the phone used, and when I got it all of the sensors were disabled. After trying some of the advice at:

https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904 (replacing the root/mnt/vendor/persist/sensors directory), I was able to get different sets of sensors working. Initially, I got most of the sensors to work except for the light and proximity sensors. After updating my phone, I then lost the active edge sensors too, for the squeeze to pull up google assistant.
A side note, which might need it's own bug thread. When I install the Google Play Systems update for December 1st, 2019, all of the sensors on the phone will no longer work. After about a minute of being turned on, the phone will then restart, but will not turn on the display. I then have to force a shutdown by holding the power button, and when I check the updates it shows that it is on the preinstall September 1st, 2019 update, and now none of the sensors work again.
My current build is QP1A.191105.003, but the only update that it says is available is the aforementioned Play Store update.

le...@gmail.com <le...@gmail.com> #317Dec 31, 2019 11:06AM

Since the newest update last night my Samsung Galaxy Note 10+ cannot return from the lockscreen while updating bixby voice. Starting in safe mode to get the last backup and delete the newest update prents big problems. I cannot return from the safe mode any more. Have to set up default settings. I started fresh with update from 1. st of november. I do not update android 10 anymore till next stable version. Also i can't activate my Google Pay account, because there was a message my phone was rootet or changed by the new android version. I'am confused and will return to the last android 9 version.

ni...@gmail.com <ni...@gmail.com> #318Jan 6, 2020 11:11AM

Pixel 1 - Android 10 update

After Software update to Android 10, everything worked initially - now no mic or speaker during any type of voice call beit phone or WhatsApp.

I can't use the phone and I've only just got it!

Any idea when google will issue a fix for this please I run a business and need to make phone calls!?

ma...@gmail.com <ma...@gmail.com> #319Jan 6, 2020 07:28PM

Google Pixel (1) XL user here.

Also have problems with my phone after the Android 10 update. I cant make calls cause it freezes when making or recieving calls.
I cant record my voice for google search, youtube, whatsapp or anything else.
Some times when the phone froozes because of a call, im forced to restart it, it doesnt have any sound at all, to get it back on i have to restart it again a couple of times and then its back on.
I read that if i go back to Android 9 everything will be fine again on it. I tried doing that but my phone is from Verizon and they disabled the option to unlock OEM so im stuck with this phone which the same manufacturer damaged.

cs...@redhat.com <cs...@redhat.com> #320Jan 7, 2020 02:04AM

Ambient light and proximity sensor not working on both my pixel 2 and pixel 3. What the hell!?

pa...@gmail.com <pa...@gmail.com> #321Jan 7, 2020 07:06PM

Hey! Same thing here. I have a Pixel 3 (which I RMA'd once already due to other issues). It shipped with Android 9, so I installed the Q update in the end of of October. Everything worked normally until yesterday. The phone shut off due to low battery, so I basically restarted it. That's when the sensors stopped working. No ambient light, no flip to shh, no active edge, no double tap or lift to wake. At least, the rotation sensor seems to work. I tried a factory reset and prior to that a reboot into safe mode. Still nothing. Please fix this!

Regards,
Joe

xx...@gmail.com <xx...@gmail.com> #322Jan 7, 2020 10:27PM

Proximity sensor has not been working (reading 0 distance all the time) ever since the initial Android 10 update back in September, causing always on display, phone calls screen and double tap to wake not working. Sometimes the sensor would come back to life out of nowhere but as soon as the sensor is blocked (putting it in a pocket or face down on a table), it would stop functioning again. I have talked to customer service before and was told this was a software issue they were aware of. Yet several months and updates later it still hasn't been resolved. Very disappointed. Please fix the issue asap or at least update us with the progress!

ma...@gmail.com <ma...@gmail.com> #323Jan 8, 2020 11:04AM

Hi, I had also problems with sensors not working (Pixel 3). In my case, this was fixed with January 2020 Android Security Update. After update and reboot, “Sensor Box” application shows all sensors working except Temperature Sensor which I suppose is a sensor for measuring air temperature (not sensor for CPU or battery temperature).

Regards,
Martin

j....@gmail.com <j....@gmail.com> #324Jan 12, 2020 06:46PM

Can anyone else confirm that the January update fixes the sensors?

st...@gmail.com <st...@gmail.com> #325Jan 13, 2020 10:12AM

@#324

Nope still not fixed. Have the problem on my Pixel4XL.

ol...@gmail.com <ol...@gmail.com> #326Jan 14, 2020 07:17AM

Same here on Pixel 3XL on QQ1A.200105.002 January Update. For me rebooting fixes the issue until after some time sensors not working anymore.

jo...@gmail.com <jo...@gmail.com> #327Jan 14, 2020 11:55PM

Issue just started occurring for me on my Pixel 3. No Ambient, gyroscope, active edge, or proximity.

li...@gmail.com <li...@gmail.com> #328Jan 15, 2020 04:27PM

For me it started just with the proximity/light sensor which stopped working. I tried to test it with some sensor test apps (eg Sensors) and then (a few hours after the proximity sensor stopped working) all other sensors also followed suite and now none work.

gu...@gmail.com <gu...@gmail.com> #329Jan 15, 2020 04:52PM

I had to request an RMA regarding this... Got a new phone, now its working lol...

s....@gmail.com <s....@gmail.com> #330Jan 18, 2020 04:17PM

Have the same issue of NONE of the sensors (proximity, ambient, active edge etc..) working. For me the issues started after Christmas and no matter how many resets with data wipe or restarts fixes the sensors. Contacted Google support and was denied RMA Since I was just a month over 1 year warranty period.

The proximity Sensor not working is very annoying since the screen stays on while answering the call and gathers unwanted screen touches from ear and hair.

Why is Google not doing anything about this since this is clearly Android Q update issue as reported be several users. I would like know if anybody is filing a class action lawsuit if the issue is not resolved soon.

ve...@gmail.com <ve...@gmail.com> #331Jan 20, 2020 02:41AM

Just installed January update.... And everything still not working. No sensors, no solutions. My first and my last Pixel phone

da...@gmail.com <da...@gmail.com> #332Jan 24, 2020 10:31PM

Same issue on my Pixel 3. Please fix this!

zh...@gmail.com <zh...@gmail.com> #333Jan 25, 2020 08:44AM

Same issue. But I do perform a boot loader unlock procedure but I did barely nothing but to learn how to install magisk. Then I found sensors stop to work after I flash back to latest factory image and lock the device.

he...@gmail.com <he...@gmail.com> #334Jan 25, 2020 08:46AM

The issue is also present on 3a (sargo)

om...@gmail.com <om...@gmail.com> #335Jan 26, 2020 09:58PM

Same thing happened on my Pixel 3 but before upgrading to Android 10. Tried factory resets before and after without any luck.

ma...@gmail.com <ma...@gmail.com> #336Jan 28, 2020 12:19AM

Same here, started yesterday, after some reboots sensors works, after one or two screen lock, they are lost.

wg...@gmail.com <wg...@gmail.com> #337Jan 29, 2020 04:03PM

Same issue here on Pixel 3XL, latest updates to everything, Android 10, etc. After reboot, my sensors return to normal, but then after an hour, sometimes maybe 3 to 4 hours, all of a sudden they stop working. I notice immediately because the auto brightness doesn't work. Then I squeeze for active edge, and nothing. But REBOOT FIXES it for a couple hours. I'm testing in Safe Mode today...

rm...@gmail.com <rm...@gmail.com> #338Jan 29, 2020 04:33PM

Same experience as

comment #329

. I had to request an RMA regarding this. Got a new phone, now it's working and upgraded to latest version just fine. I would like to know why this issue happened as swapping phones is no trivial task with all the 2FA tied to it.

ma...@gmail.com <ma...@gmail.com> #339Jan 31, 2020 11:03PM

So got RMA from insurance, all working fine even with the latest update.

fe...@gmail.com <fe...@gmail.com> #340Feb 5, 2020 10:14AM

Re: #281
After the security update this month (~2 days ago) my senors are not working again. Same story as last time, some sensors seem to start working again after a reset, but it is not consistent. Super annoying.

le...@gmail.com <le...@gmail.com> #341Feb 5, 2020 10:25AM

6 months of this and it starts to get old. This is tarnishing the reputation of Pixel phones and makes it hard to consider a new one when upgrading. Lack of official statement from Google is worrying for a company of this size and reputation.

ad...@gmail.com <ad...@gmail.com> #342Feb 5, 2020 10:31AM

Same issue here, Pixel 3.

om...@gmail.com <om...@gmail.com> #343Feb 5, 2020 02:13PM

The February update fixed the accelerometer (autorotation) and Active Edge (squeeze for Google Assistant) but adaptive brightness still doesn't work (and the screen doesn't even turn off when I hold the phone to my ear during calls).

The android sensors app shows these features as not supported:

LIGHT
PROXIMITY
TEMPERATURE
RELATIVE HUMIDITY

I'm glad to see some progress is finally being made towards this issue.

zh...@gmail.com <zh...@gmail.com> #344Feb 7, 2020 06:57PM

It stop working after a few reboot. I don't see progress making on my
device. February update yes.

<buganizer-system@google.com> 于 2020年2月5日周三下午10:13写道：

https://issuetracker.google.com/issues/149630955

om...@gmail.com <om...@gmail.com> #345Feb 9, 2020 05:51PM

After a couple of reboots, I lost ActiveEdge, but autorotation still works. The rest of the behavior is the same as in #343.

zh...@gmail.com <zh...@gmail.com> #346Feb 10, 2020 09:18AM

It seems a OTA update works like reboots on other people's cases. I submit feedbacks several times. Can this be fix on March or I can't use this device as my main phone any longer.

le...@gmail.com <le...@gmail.com> #347Feb 10, 2020 12:59PM

Pixel 3 here, with latest Android 10 Feb update. Sensors still intermittently broken. Rebooting the phone a few times makes them work for a while. Each reboot is a "russian roulette". This has been happening ever since Android 10 update back in ~Sep 2019.
C'mon Google, this needs to be better addressed (timely communication on progress status and a complete fix). Users are losing confidence in these phones. I'm certainly really annoyed and inconvenienced.

st...@gmail.com <st...@gmail.com> #348Feb 10, 2020 01:13PM

I'm also using a Pixel 3 (non-XL): I lost most of my sensor functionality starting in mid-January and have been watching all of the support threads. Interesting anomalies:
1) The February update briefly brought back many of my sensors (squeeze / active edge, etc). But those sensors' functionality was lost again after a restart of the phone.
2) Screen rotation has *mostly* worked. Occasionally I have to restart my phone to get screen rotation back. None of my other sensors come back with a restart (active edge, proximity sensor, etc).

st...@gmail.com <st...@gmail.com> #349Feb 10, 2020 01:22PM

One more comment: This *seems* like a software issue, but it is not clear whether it can be corrected with an update or not. If the problem is, as one Google support person hypothesized, due to corrupt sensor calibration files that are unique to individual phones, then it seems like the only fix would be to get a new phone -- unless google backs up those sensor calibration files (specific to each phone) to the cloud somewhere. I'm *really* hoping this is fixable via a software update, since I am out of warranty (only 1 year in the US).

To Google: Can you give us an update on this issue and the likelihood of a software fix? And if a software fix is not possible (despite this looking like a software problem), can you extend the warranty on these phones to cover this issue? My phone is running its stock software and gets it's updates directly from Google Fi (my service provider). It is not rooted. And it has never been abused or damaged.

da...@gmail.com <da...@gmail.com> #350Feb 13, 2020 11:17PM

I recently updated to build QQ1A.200205.002 and lost ALL sensors. Before today's update I had most sensors (lost ambient lighting six months ago). Please fix Google. This is clearly a software issue.

lm...@gmail.com <lm...@gmail.com> #351Feb 14, 2020 04:16AM

I have a Pixel 3. I have zero functioning for my internal sensors at this point. At least some of them have been out since a forced update mid-January, though I think the issue started in December since that is when Google fit stopped recording any data.

j....@gmail.com <j....@gmail.com> #352Feb 17, 2020 08:45PM

So happy to see that nothing has been done to address this issue and that I am being exposed to known security vulnerabilities as I cannot update.

lb...@gmail.com <lb...@gmail.com> #353Feb 18, 2020 06:30AM

Has anyone found a workaround for this?
Flashing a kernel ? Flashing Android 9? Some specific Android 10 build?
I tried to perform a factory reset and it didn't help.
I have Pixel 4 and all sensors can't work anymore:

lb...@gmail.com <lb...@gmail.com> #354Feb 20, 2020 07:37AM

Seems that even updating to Android R doesn't fix it.

or...@mail.huji.ac.il <or...@mail.huji.ac.il> #355Feb 20, 2020 10:56AM

Same here (pixel 3 user). All sensor functionality have stopped working yesterday, including Active edge, auto rotation and double tap.

lb...@gmail.com <lb...@gmail.com> #356Feb 21, 2020 08:30PM

@355 for Pixel 3 (or more precisely Pixel 3A), it seems there is an XDA post with a solution:

https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904

I have no idea if it really works, but I would have tried it.
Sadly I have Pixel 4 and I can't find anyone who has it and would be able to send me what's needed by this post.

be...@gmail.com <be...@gmail.com> #357Feb 24, 2020 06:08PM

Adding my name to this list. Google even sent me a replacement under my Fi contract and it had the issue out of the box...

Never have I been closer to being tempted to the dark side and finally trying an iPhone.

br...@gmail.com <br...@gmail.com> #358Feb 25, 2020 07:00AM

I have a pixel 3 with the lack of sensor function. I have gained functionality in The November and the January security updates. The most recent February update broke fat functionality again.

I've had no luck with hard resets twice.

The Google tech support chat assistant said if my hard reset didn't fix it, then I would need a new phone because it must be a hardware problem.

lb...@gmail.com <lb...@gmail.com> #359Feb 25, 2020 07:33AM

@358 You should have shown them the articles about it, and that it occurs on various Pixel devices.
It started for me on my Pixel 4 last week or so, and as opposed to older Pixel devices, I can't flash Android 9 to fix it.
You can, however. I suggest trying it out.
Maybe you could flash the version of January instead?
If you try, please let us know if indeed it fixes the issue as people wrote.

co...@gmail.com <co...@gmail.com> #360Feb 26, 2020 12:39AM

I have these issues

cu...@gmail.com <cu...@gmail.com> #361Feb 26, 2020 04:50AM

Tried using it for a universal remote app and now receiving emails that
sensors are not working after upgrading to Q.? What is Q?

On Tue, Feb 25, 2020, 6:39 PM <buganizer-system@google.com> wrote:

hy...@gmail.com <hy...@gmail.com> #362Mar 1, 2020 08:31AM

Pixel 3 running Build QQ1A.200205.002, same issue, Active Edge, Flip to Shh, Double Tap to wake, Lift to wake was working after December patch, but all all not working again after February patch.

Tried factory reset, sideload latest update, same result.

go...@google.com <go...@google.com> #363Mar 2, 2020 06:10PM

Verified by go...@google.com.

In September of 2019, some Pixel 3(XL) owners reported that the sensors stopped working on their devices after upgrading to Android 10 as reported by this bug.

Google investigated the issue and discovered that it was affecting devices with 3rd party recovery tools installed. The sensors are calibrated in the factory and the data is unique to each device. These recovery tools were causing the sensor calibration data to become corrupt/overwritten. A fix was released in the October 2019 software update.

We have started to get reports of similar issues on Pixel 1, Pixel 2, Pixel 3a, and Pixel 4, but they are unrelated to the original issue. If you are experiencing a similar issue please contact our support(

https://support.google.com/pixelphone/answer/7109524?hl=en) by clicking Contact Us at the top right of this page or via Settings > Tips & Support on your Pixel. We will help you solve the problem!

We are going to closeout this bug as it has a mix of potential issues that may be unrelated to the original reported problem. Please feel free to to open a new bug that you are experiencing after upgrading to the latest SW release. As stated above, you can also reach out to customer support so we can help address your individual problem and perhaps you can help us collect bug report/logs to get to the root cause.

lb...@gmail.com <lb...@gmail.com> #364Mar 2, 2020 06:46PM

@363 I didn't have a custom recovery on Pixel 4. I don't even think there is one yet.
And there is no support in my country (Israel).
You should fix this issue on software, because it's a software issue. Factory reset couldn't even handle it.
I actually already reported about this here (before I knew it exists for more users) :

https://issuetracker.google.com/issues/149630955

Whoever got it similar to me, out of nowhere and without any recovery, please star it.

go...@google.com <go...@google.com> #365Mar 2, 2020 06:52PM

lblb636@, Thanks for reporting your issue and we are extremely sorry that you are experiencing this issue. I'll have customer support reach out to you to understand the symptoms and get additional details such as build number etc.

le...@gmail.com <le...@gmail.com> #366Mar 2, 2020 07:02PM

@363 Like

comment #364

I also did not have any custom recovery software on my Pixel 3. Sensors come and go with reboots which is very annoying.

A couple of months ago, my phone failed to load Android (see screenshot) so I was forced to do a factory reset. That did not resolve the issue.
Not sure if Portugal has support (tried to call just now and automated message said it was outside business hours and did not state what these are).

Hope you are not closing the bug as the problem is not fixed! A someone who spend nearly 1000€ to have a Google specific phone, I would hope to get better treatment.

Pixel3.jpg

2.1 MB

go...@google.com <go...@google.com> #367Mar 2, 2020 07:06PM

leandro.morgado@ and others, please contact our support (

https://support.google.com/pixelphone/answer/7109524?hl=en) by clicking Contact Us at the top right of this page or via Settings > Tips & Support on your Pixel. We will help you solve the problem!

Like I said before, this thread has a mix bag of issues. Your individual issue may be a new issue that we may need your help troubleshooting and finding a root cause. Please file a new bug for your individual issues.

lb...@gmail.com <lb...@gmail.com> #368Mar 2, 2020 07:09PM

@365 you mean to write "364" .
Are you sure support could help me, even in my country?
How can I talk to them?
I don't see an email or some chat on the link you've provided.

This issue exists for me for at least 2 weeks now.
I don't get how it's even possible that after flashing the entire Android R image the issue still exists. Doesn't it replace the recovery anyway?
I had this device only for a few months.

hy...@gmail.com <hy...@gmail.com> #369Mar 2, 2020 07:11PM

Like the above 2 users, I have got no custom software installed, this problem is getting borderline annoying when I cannot quickly access my notifications, screen not turning back on when want to end a call, compass is not working, gos sensor can't be calibrated, all these happened after upgrading to Q

lb...@gmail.com <lb...@gmail.com> #370Mar 2, 2020 07:11PM

@367 There is no "contact us" and there is no "Settings".
See attached video of how this page looks like.

2020-03-02_21-11-22.mp4

933 KB

hy...@gmail.com <hy...@gmail.com> #371Mar 2, 2020 07:19PM

@367, I can confirm that does not work, I have sent at least 5 feedback but never a reply

go...@google.com <go...@google.com> #372Mar 2, 2020 07:21PM

lblb636@, oh no. I see it on my browser so assumed you'd do too :)
Let me check with customer support and get back if its a regional menu option. In the meantime, I have informed the team to specifically reach out to you. Please also be on the lookout for an email from support. Thanks for your patience while we figure it out.

go...@google.com <go...@google.com> #373Mar 2, 2020 07:22PM

hyrod88@, Please share the link to your bug here and customer support would reach out to you.

hy...@gmail.com <hy...@gmail.com> #374Mar 2, 2020 07:25PM

I have not logged a bug ticket, I have send multiple feedback from "Tips&Support" page but never got a reply from Google, posting on Pixel forums, all they asked me to do was factory reset which didn't fix anything.

lb...@gmail.com <lb...@gmail.com> #375Mar 2, 2020 07:35PM

@372 Can I get a VIP link on this website like on your case ?
:)

Anyway, please contact me via email. I will send you everything you want. Do note that currently the device is not rooted though, so I don't think I can send you protected files.

I suggest you to talk to someone who have a rooted device on Android 10. Could give you more information.
I wish there was a way to go back to Android 9 (some say it fixes it), but Pixel 4 doesn't seem to have this firmware on the website. Did it ever have it?

go...@google.com <go...@google.com> #376Mar 2, 2020 07:35PM

hyrod88@, I have asked customer support team to reach out to anyone willing to work with the team to gather additional bug report/logs to root cause. There are several potential root causes of this symptom, from sensor defect to memory/ROM failure to software defects. Internally, none of our system testing or stress tests have surfaces these symptoms and hence we need your help to track it down. Factory Reset should be the last option. We should be able to collect bugreport/logs and see if there are any pointers from that. Hopefully some of you can work with use to help get to the bottom of these issues.

The goal is not to ignore these issues but to have a structured process to get to the bottom of the problem and find an appropriate resolution. We really appreciate your support and patience in the meantime.

go...@google.com <go...@google.com> #377Mar 2, 2020 07:39PM

lblb636@, each of our customer is a VIP :)
Customer support will help file a ticket on the Case management system and provide you the tracking information.

hy...@gmail.com <hy...@gmail.com> #378Mar 2, 2020 07:39PM

Awesome, I shall wait for the email from support team, hopefully we will be able to get to the bottom of this issue soon. Thanks :)

lb...@gmail.com <lb...@gmail.com> #379Mar 2, 2020 07:54PM

@377 I wish you had a center in my country (Israel) so that I could just give you the device and you could give me an alternative in the meantime.

af...@gmail.com <af...@gmail.com> #380Mar 3, 2020 02:59AM

How the fk is this flag Fixed?????? Anyone can enlighten me?

st...@gmail.com <st...@gmail.com> #381Mar 3, 2020 03:11AM

Agreed. This is NOT fixed. All of us updated our phones and sometime later (often after a restart/shutdown) we lost functionality of various sensors.

zh...@gmail.com <zh...@gmail.com> #382Mar 3, 2020 02:04PM

Agreed. This is not a way to actually fix an issue.

lb...@gmail.com <lb...@gmail.com> #383Mar 3, 2020 05:09PM

@377 BTW, even if I have replaced the recovery, it should still be possible to hand over the device to someone else after a factory reset with everything clean and ready.
Flashing the firmware is supposed to replace the recovery, as far as I know.

Correct me if I'm wrong here...

go...@google.com <go...@google.com> #384Mar 3, 2020 07:24PM

lblb636@, the persist partition has sensor configurations that are burnt in at the time for factory calibrations. These are unique to each device and not backed up anywhere. Factory reset will not restore these once its destroyed or corrupted. There is no guarantee the device will perform as well as it should with the original parameters.
When you mod or install recovery tools like TWRP, they tend to create log files in the persist partition and were corrupting the sensor calibration files. Further, on the forums, several folks provided a persist.img to help resolve the issue. It's not likely to resolve it if you overwrite your persist with someone else's with different sensor calibration data.

persist partition is unlike other partitions such as system, boot.. ones its loose the factory calibrations, it cannot be restored. I hope that helps clear why only a small population of users experienced this issue post Android 10.
In Android 9 too this problem existed, but Android 9 was more forgiving than Android 10.

lb...@gmail.com <lb...@gmail.com> #385Mar 3, 2020 07:54PM

@384 Why would TWRP corrupt a sensitive file, if you say all it does is to write to logs? Wouldn't we have noticed a lot more issues by now? TWRP is quite popular.
Or is it only for Android 10?
Why do you even make it harder to use recoveries?
And why don't you provide a way to reset the device to truly factory-state, using a PC if needed? What's the use of firmware and factory-reset options if none of those truly do go back to factory state?
I think you should improve this on Android R. Now you have a chance: Investigate the issue and provide a way to fix it.

Anyway, as for people who were harmed by this issue, whether it's from recovery or not, please provide a tool to diagnose the cause of it and help you fix it.
You can use root if you wish. I will go back to Android 10 , root it, and run your tool. I didn't use TWRP. I couldn't even use it on Android 10.

go...@google.com <go...@google.com> #386Mar 3, 2020 08:06PM

lblb636@, your issue may not be related to what I explained. The explanation was for the original issue that we observed post Android 10. Please work with customer support to help capture bugreport/logs to root cause your specific issue.

bo...@gmail.com <bo...@gmail.com> #387Mar 3, 2020 08:08PM

So are our phone sensors just plain broke? Or is there a fix coming at some point?

go...@google.com <go...@google.com> #388Mar 3, 2020 08:22PM

boblightfoot100@,
It depends on what is broken, on what device and build. The symptoms may be same but the root cause may be different. For example,
* If its a hardware issue, you may have to RMA is depending on your device warranty.
* If your mods or TWRP/ other recovery tools caused the sensor calibrations to get corrupted, your device may not function as it was supposed to with the factory calibrations. There was a fix released in October to make Android 10 more forgiving similar to Android 9. But this still isnt going to be same as having the original calibrations. There is no way to recover the original calibration data once its destroyed.
* If you have not made any changes to the original device that shipped and still experience the issue, It may be a new issue that we havn't root caused. I'd suggest you work with customer support to help get to the bottom of your issue.

bo...@gmail.com <bo...@gmail.com> #389Mar 3, 2020 08:27PM

I just sent a feedback report that I believe atatched a bug report

st...@gmail.com <st...@gmail.com> #390Mar 4, 2020 02:28AM

FYI: If you look at this thread (and elsewhere on the web), you'll see that a number of us are running stock software with updates directly via the carrier (e.g. Google Fi in my case). No root access. No mods. Just the software installed on the phone at purchase and standard over-the-air updates from the carrier.

Also: Many of us lost sensor functionality long after the initial Android 10 update and long after subsequent October patch. I started experiencing problems in January of this year. All of my sensors came back temporarily after the following Android update, but functionality disappeared after a restart.

be...@gmail.com <be...@gmail.com> #391Mar 4, 2020 02:43AM

My experience is the same as above. Fi customer, no root access, no mods, no recovery tools. My sensors stopped about 5 months ago on my pixel 3. The first replacement that Google sent me had the issue out of the box! I'm now on my 2nd replacement that knock on wood has been working as it should.

bo...@gmail.com <bo...@gmail.com> #392Mar 4, 2020 01:59PM

My experience as well. No root access. No mods. Just the software installed on the phone at purchase and standard over-the-air updates from the carrier.

lb...@gmail.com <lb...@gmail.com> #393Mar 4, 2020 07:44PM

@386 I know. It's just that I wish it was possible to fix this issue already, no matter what caused it.
Some people do want a custom recovery.
In the past, for different devices, I also used those. Mostly for flashing custom ROMs. I care about other users too :)

As for the support, they asked me for something and I gave it right away, but didn't get any reply ever since.

al...@gmail.com <al...@gmail.com> #394Mar 4, 2020 10:07PM

Pixel 3 with Android 10: Auto-rotation did't work since ~3 to 4 days. Did a reboot a couple of times => didn't help. Reboot into safe mode => Didn't help. Factory reset => didn't help. Light sensor apparently not working too. Waiting for a software update for this. Otherwise, it will be my last google phone!

al...@gmail.com <al...@gmail.com> #395Mar 5, 2020 08:14PM

I should add: QQ1A.200205.002.

lb...@gmail.com <lb...@gmail.com> #396Mar 5, 2020 09:10PM

New R update still didn't fix the issue (Pixel 4) :
RPP1.200123.020

I really hope this can be fixed. I don't think that using the warranty in the store we got it will help. It's not like in the USA, where people just give a completely new device as a replacement...

al...@gmail.com <al...@gmail.com> #397Mar 8, 2020 08:36PM

is anyone from google developers actually reading this thread?! I see only people reporting the same issue since September 2019 but no reaction from google

ka...@gmail.com <ka...@gmail.com> #398Mar 29, 2020 05:24PM

I'm using Pixel 2xl, I have same issue ( sensors not working)
It suddenly happened and even my device started to restart randomly

ja...@gmail.com <ja...@gmail.com> #399Mar 30, 2020 01:59PM

None of my sensors are working

bo...@gmail.com <bo...@gmail.com> #400Mar 31, 2020 09:59PM

As of a couple days ago, it was my accelerometer and compass sensors not working. In the alst 2 days, I now have complete sensor failure. Calls are getting screwed up because the proximity sensor is broke. My phone is resetting to zero brightness for no reason I believe because the light senor is not working, Whereas my phone was at least functional before 2 days ago, I fear now it's becoming less useful. I either need a fix or a new phone.

bo...@gmail.com <bo...@gmail.com> #401Apr 7, 2020 09:46PM

The April update has been released and I downloaded and installed it. Sill no fix for us with sensors broken by Gooogle's Android 10. Google you owe us new phones.

le...@gmail.com <le...@gmail.com> #402Apr 7, 2020 10:16PM

I was contacted by Google support on the 3rd of March, provided all the
necessary info, bug report, etc. Still waiting for a reply back with a
solution.
Latest April update made no difference. Sometimes I get some sensors to
work after multiple reboots of the phone (very annoying process). A new
reboot will remove the sensors again. Some features, like squeeze touch and
proximity sensor have just stopped working altogether.

Over half a year with a crippled, expensive phone is not my idea of fun.
Expected much more from a company like Google. I was a big fan and intended
to keep upgrading within the Nexus/Pixel line but this has undermined my
confidence and trust in Google phones. I can't even resell the phone in
this state.
Really hoped for some good news but feel let down.

On Tue, 7 Apr 2020, 22:46 , <buganizer-system@google.com> wrote: