Live Updates: COVID-19 Cases
  • World 30,941,668
    World
    Confirmed: 30,941,668
    Active: 7,431,117
    Recovered: 22,550,277
    Death: 960,274
  • USA 6,961,297
    USA
    Confirmed: 6,961,297
    Active: 2,542,822
    Recovered: 4,214,773
    Death: 203,702
  • India 5,398,230
    India
    Confirmed: 5,398,230
    Active: 1,011,732
    Recovered: 4,299,724
    Death: 86,774
  • Brazil 4,528,240
    Brazil
    Confirmed: 4,528,240
    Active: 571,613
    Recovered: 3,820,095
    Death: 136,532
  • Russia 1,097,251
    Russia
    Confirmed: 1,097,251
    Active: 171,450
    Recovered: 906,462
    Death: 19,339
  • Peru 756,412
    Peru
    Confirmed: 756,412
    Active: 124,334
    Recovered: 600,795
    Death: 31,283
  • Mexico 688,954
    Mexico
    Confirmed: 688,954
    Active: 123,959
    Recovered: 492,192
    Death: 72,803
  • South Africa 659,656
    South Africa
    Confirmed: 659,656
    Active: 54,282
    Recovered: 589,434
    Death: 15,940
  • Spain 659,334
    Spain
    Confirmed: 659,334
    Active: 628,839
    Recovered: ?
    Death: 30,495
  • Chile 444,674
    Chile
    Confirmed: 444,674
    Active: 14,319
    Recovered: 418,101
    Death: 12,254
  • France 442,194
    France
    Confirmed: 442,194
    Active: 319,346
    Recovered: 91,574
    Death: 31,274
  • Iran 419,043
    Iran
    Confirmed: 419,043
    Active: 37,293
    Recovered: 357,632
    Death: 24,118
  • UK 390,358
    UK
    Confirmed: 390,358
    Active: 348,599
    Recovered: ?
    Death: 41,759
  • Bangladesh 347,372
    Bangladesh
    Confirmed: 347,372
    Active: 88,073
    Recovered: 254,386
    Death: 4,913
  • Saudi Arabia 329,271
    Saudi Arabia
    Confirmed: 329,271
    Active: 15,383
    Recovered: 309,430
    Death: 4,458
  • Pakistan 305,031
    Pakistan
    Confirmed: 305,031
    Active: 6,572
    Recovered: 292,044
    Death: 6,415
  • Turkey 301,348
    Turkey
    Confirmed: 301,348
    Active: 27,786
    Recovered: 266,117
    Death: 7,445
  • Italy 296,569
    Italy
    Confirmed: 296,569
    Active: 43,161
    Recovered: 217,716
    Death: 35,692
  • Germany 272,080
    Germany
    Confirmed: 272,080
    Active: 19,614
    Recovered: 243,000
    Death: 9,466
  • Canada 142,774
    Canada
    Confirmed: 142,774
    Active: 9,376
    Recovered: 124,187
    Death: 9,211
  • Netherlands 91,934
    Netherlands
    Confirmed: 91,934
    Active: 85,659
    Recovered: ?
    Death: 6,275
  • China 85,269
    China
    Confirmed: 85,269
    Active: 171
    Recovered: 80,464
    Death: 4,634
  • Australia 26,885
    Australia
    Confirmed: 26,885
    Active: 2,079
    Recovered: 23,962
    Death: 844
  • S. Korea 22,893
    S. Korea
    Confirmed: 22,893
    Active: 2,545
    Recovered: 19,970
    Death: 378
  • New Zealand 1,811
    New Zealand
    Confirmed: 1,811
    Active: 67
    Recovered: 1,719
    Death: 25

Pixel 2 users with camera errors and crashes offered replacements from Google

Author at TechGenyz Google
Pixel 2 Replacement

Google is now silently replacing Pixel 2 units with sensitive proximity sensors to avoid any bad publicity, including Pixel/Pixel 2 units which are ridden with microphone issues. Second generation Pixel users who are facing fatal camera errors are no exception either.

As of mid-November last year, there had been complaints from Pixel 2 users regarding random camera crashes, with an error which stated “The camera device encountered a fatal error”, upon accessing the application, thereby rendering it incapable of further operations.

Google’s inquiries and investigations with Orrin (Google employee and also the Community Manager at Pixel User Community) asking for bug reports, the Pixel 2 replacement which they are offering necessarily imply that a software to fix the problem, has not been developed yet and fall under issues of hardware glitches.

One of the complaints, who is also an Android developer, confirmed this after looking at debug logs:

I would recommend everyone get a replacement because it seems like a hardware or power issue. I am an Android developer myself and all the debug logs indicate a hardware problem

Following is what the same user got to hear from Google Support:

The Response was to get an RMA for the issue and support said there tracking the problem and issuing replacement devices for that effected wince there is no known fix.

Relevant forum threads reveal that Google has been surreptitiously replacing affected units.

Unfortunately, there have also been reports that say that the replacements were of no help because the problem is recurring and showed up again after a while

With miscellaneous reports from several users, it is difficult to come to a conclusion about whether or not a replacement of units is the best solution to these recurring problems. However, one thing is for certain. This is the only option at hand as of now, and as a user had previously stated in one of the comments listed above, there is no harm in opting for an RMA.

Career

Subscribe