-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Browser even worse? Google broken?
- Thread starter hulk2k17
- Start date
thecloud
As rhythm raced inside, the ship came alive
Went out to the car just now to try the browser, and was unable to reproduce this. Google's home page loads and searches work just fine.
I'm on 2018.28.5 377ec8b. Are you on an older release?
I'm on 2018.28.5 377ec8b. Are you on an older release?
thecloud
As rhythm raced inside, the ship came alive
On a different firmware thread, some folks are saying that the browser didn't work for them on that same release (2018.28.5 377ec8b), but then it started working again. Maybe it's something Google did and then rolled back?
Have you tried a reboot (holding in both scroll wheels until center screen turns black)?
Have you tried a reboot (holding in both scroll wheels until center screen turns black)?
This happens when I'm on LTE and not when connected to my home WiFi.
I'm on 2018.32.2 and I did reboot the gauge cluster and center console
I'm on 2018.32.2 and I did reboot the gauge cluster and center console
timvracer
Member
Anybody else notice that a few releases ago the browser lost it's ability to zoom/shrink using pinch on the screen? Really annoying because now I can't size my Back to the Future screen just right to the half/screen browser window.
JohnnyG
Weee!
Yes, many of us. I'm confused as to why it's only some of us...
The browser is still supported by Google. What that message is saying, is that the Captcha is not supported in our browser. This means that we can't bypass the block, by letting it know that we are humans and not attack bots.
We are being blocked by Google, because, they are seeing activity that appears to be bot attacks from our network. If we could see the Captcha, we could verify we are human and could carry-on to the normal Google Search screen.
You can still use Google search by entering your search into the address bar and hitting Enter. This will return Google's results page, and is a workaround for the IP blacklisting.
The white screen/not loading, (more apparent on LTE), is a WebKit bug that was supposed to be in 32.2, but was pushed a release or two ahead.
The white screen/not loading, (more apparent on LTE), is a WebKit bug that was supposed to be in 32.2, but was pushed a release or two ahead.
thecloud
As rhythm raced inside, the ship came alive
I think he just left out a word: "a WebKit bug that was supposed to be fixed in 32.2."
deonb
Active Member
Do you really want to entertain a thought that it is the same people who created the Tesla browser that are now the ones working on EAP/FSD?
Mario Kadastik
Active Member
BIG ACH
Member
I stand corrected. Google's main page is broken again for me today with the same error as reported before
Similar threads
- Article
