Pixel 2 XL - Screen goes black when making calls

Issue: 
Screen goes black once you press the dial button to make a call. You then have to lock and unlock the phone to be able to hang up.

Fix: 
Open Settings > Apps & Notifications > All Apps > Phone > Storage

Clear Cache
Clear Data

This fixed the issue for me (also big thanks to google support [shoutout to Paul.A])


If you find this article useful please leave me a comment.

Pixel 2 XL screen flashing bright white on lock AKA the 'Pixel Flashbang'

After updating to OREO 8.1 my screen started flashing when I lock the phone (one really bright white flash) and then the ambient display kicks in. in a dark room, this is very noticeable.

Suspected issue:
I'd say it's almost a race condition when the screensaver is turned on. Kind of like the screen is being told to turn on and then the instructions on what to show are just slightly slower and therefore the screen assumes you want all pixels full brightness until the instructions for the ambient screen are sent through. BUT I'm not a Google engineer so don't take my word for it.

Workaround:
Turn off ambient display

Fix:
Wait for Google to patch this (send them lots of bug reports)

Notes: After disabling the ambient screen and rebooting, I then turned ambient display back on and now the issue isn't occurring anymore (more testing required)

If you find this article useful please leave me a comment.

Update:
It's now 24 hours later and the phone has started to flash white again on locking and sometimes when waking up It's now slightly random it will flash when the screen has to wake up. I am now even more sure that this is probably a software bug in the ambient display software.

Update2: 15/12/2017
I found that there is a software called 'Pixel Ambient Services' in the apps. I cleared the 'cache' and the 'data' from this app/service. Currently, my screen isn't flashing on lock or wake now. I will continue to monitor and report on the issue here.

Update 3: 18/12/2017

The issue is back again. I'm going to call this a 'Pixel Flashbang' from now on as that's what it's like at 6 AM in the morning when I wake up and look at my phone. Clearing the above app cache stops it for awhile but it comes back and the issue is now intermittent. 

Update 4: 20/12/2017

I chatted with Google support and they said that there is no known fix yet but engineers are looking into it.

Update 5: 03/01/2018

Still the same issue no matter which workaround is applied.

Rebooted in safe mode and still the same issue flashbangs on wake up of the screen.

Update 6: 05/01/2018 No update from Google about this. 

More info 

http://www.redmondpie.com/is-your-pixel-2-xl-screen-flashing-while-locking-unlocking-youre-not-alone/

http://www.androidpolice.com/2017/11/08/pixel-2-xl-screens-flashing-locking-unlocking/

https://9to5google.com/2017/11/08/google-pixel-2-xl-screen-flashing/

Final update: 

The Feb 2018 firmware update seemed to have resolved this issue. 

Pixel 2 XL - Boot loop issue

My wife's brand new Pixel 2 XL (2 weeks old) decided it would be really fun to get itself stuck in a boot loop. Wife looked down at phone to see it rebooting and thought that was odd. left it alone for an hour while stayed stuck on the 'G' boot screen with a scrolling progress bar.

About an hour later I got to look at it and talk to google support. they just advised to get into the recovery screen and try a 'shutdown'. This didn't fix the issue. Google then offered to replace the device saying there was a hardware issue.

I ended up resolving the issue before having to replace the phone. I had to wipe all the user data and do a factory reset from the recovery bootloader and this allowed the phone to boot correctly.

Total damage:
- Lost some photos and videos from that day
- Had to reload EVERYTHING again.
- Major pain in the ass.
- Confidence has been lost in this google product. Will this issue happen again?

If you find this article useful please leave me a comment.

Internet Explorer 11 failing on prerequisite KB2729094 even though the required prerequisites are already installed

I've found that on PC where WMI is slow to respond it can cause issues with upgrading to IE11.

WMI query for Hotfixes timed out. Query string: 'Select HotFixID from Win32_QuickFixEngineering WHERE HotFixID="KB2729094"'  Error: 0x00040004 (262148).

I've found that on some systems running this query can take a good 4-5 minutes to respond. by the time the query returns something IE11 has already quit out and exited the install with a "0x00009C47 (40007) - Required updates failed to download." error.  (interesting though it will still return a 0 to say it upgraded successfully which is a different issue).

In this case opening WBEMTEST and running "Select HotFixID from Win32_QuickFixEngineering WHERE HotFixID="KB2729094"" before hand can help. when you run the query multiple times the second time the query is run it's much faster.

Generally this only affects the slowest of slow machines (ones without SSD's)

If you find this article useful please leave me a comment.

SSRS The attempt to connect to the report server failed

turns there was no closing tab in the web.config for  

I closed the section with

and then restarted SSRS and this fixed the issue.

If you find this article useful please leave me a comment or click on an ad to show your support.

Fix Blurry or non-smooth fonts in 8.1 and chrome

After upgrading to Windows 8 and trying to use chrome I noticed that the fonts in Chrome became very hard to read. The text was blurry.

Simple to fix

1. Right-click on Desktop and select "Screen resolution" option.
2. Now click on "Make text and other items larger or smaller" link.
3. Enable "Let me choose one scaling level for all my displays" option and apply the changes.
4. Sign out and sign back in to Windows 8 and this should resolve your issue 

If you find this article useful please leave me a comment or click on an ad to show your support.

Citrix Forums : Receiver 4 USB Power Issues ...

Just keep an eye for this issue.. if you install v14.0.0.91 of Citrix Receiver on XP you may find that the electrical current rating for your USB ports dropping from 500ma to 100ma. This is not enough current to run anything beyond a USB keyboard.

There is an updated version of the c:\windows\system32\drivers\ctxusbm.sys floating around that fixes the issue on XP devices. Contact your citrix support to obtain the updated file. We replaced the file and rebooted the issue is fixed on XP devices.

Citrix Forums : Receiver 4 USB Power Issues ...:

'via Blog this'

If you find this article useful please leave me a comment or click on an ad to show your support.