Database Develop

Is there a solution to the browser black screen in 4.4?

Has anyone found a work around for the black browser screen in the 4.4 based roms? I see it in the evervolv and cyanogen 11 builds. I love 99% of kitkat on the touchpad, but with 2 step verification I can't do a clean install. HTML email is all black too.
Thanks to all the devs for their continued work on our orphaned touchpads. Your work is well appreciated.

If you have two android devices, you can use titanmium to backup and restores app from one device to the other device

jaltman said:
Has anyone found a work around for the black browser screen in the 4.4 based roms? I see it in the evervolv and cyanogen 11 builds. I love 99% of kitkat on the touchpad, but with 2 step verification I can't do a clean install. HTML email is all black too.
Thanks to all the devs for their continued work on our orphaned touchpads. Your work is well appreciated.
Click to expand...
Click to collapse
I to am having this exact issue, are you also having mediaprovider crash in the background? if not it may be unrelated. also are you using legacy display or media? are you getting overlay log spam? and if you are using legacy repos which ones?
Sorry if the questions seem random, but they may help me track down where this issue lies.
Also do you remember when you first experienced this issue?

Kits the current kernel. It will be fixed. Nothing as a user you can do. Let the developers have more time.

Moody66 said:
Kits the current kernel. It will be fixed. Nothing as a user you can do. Let the developers have more time.
Click to expand...
Click to collapse
I'm getting it working with Chrome browser.

jaltman said:
Has anyone found a work around for the black browser screen in the 4.4 based roms? I see it in the evervolv and cyanogen 11 builds. I love 99% of kitkat on the touchpad, but with 2 step verification I can't do a clean install. HTML email is all black too.
Thanks to all the devs for their continued work on our orphaned touchpads. Your work is well appreciated.
Click to expand...
Click to collapse
The latest opera browser works for me.:good:

I had not used Android since 2.2. Last night finally I decided to flash my TP. The first thing I tried after flashing was web browsing and saw the black screen. I thought I did something wrong and almost restarted the flashing process. Then I installed Chrome and it works fine.

Applies to Milaq's CM11 KK 4.4.2 and Evervolv/ASOP 4.4 update for the TouchPad (tenderloin). As others have reported the devs are still working updating 3.6 kernel. Reportedly the kernel changes will resolve the black box issue in default browser api.
So we need to live with the 2.6.35 kernel or a while longer. Until then apps utilizing default browser api in KitKat on the Touchpad are problematic. At least Chrome, Firefox and Opera are working.

Sorry for digging up an old thread but I am having this issue and not sure what to do. I reset my Google password. Since I have 2 step auth, it forces me through the browser to do the Google Signin, however the default browser has black screen. I have installed Chrome on the device, which works, but no matter what I do, I cannot make the signin go through Chrome, it always goes through the default browser with the black screen. So at the moment, I can't use my Google account with my TouchPad
Does anyone have a work around for this?
I am running the latest Evervolv nightly ev_tenderloin-nightly-2014.04.10.zip which was installed via the EV updater.

PSA new firmware out 17977

Was just changing my settings when I realized my version had changed.
Haven't noticed any front facing changes thus far but only got to look at it for a couple of seconds.

I've had it on mine for almost two weeks. I don't know what has changed.

I have had it too for a while, not really noticed any difference, except maybe Screen Mirroring MIGHT (though it is completely possible it is placebo) be less laggy.
Dan
Sent from my Nexus 7 using XDA Free mobile app

From the looks of it there are some WiFi driver changes in the kernel, as well as some changes to how eureka_shell loads its whitelist (it no longer has many apps pre-assigned in the /apps.conf file, and now seems to be mainly web driven)

ddggttff3 said:
From the looks of it there are some WiFi driver changes in the kernel, as well as some changes to how eureka_shell loads its whitelist (it no longer has many apps pre-assigned in the /apps.conf file, and now seems to be mainly web driven)
Click to expand...
Click to collapse
Does that mess with Eureka in any significant way?

Asphyx said:
Does that mess with Eureka in any significant way?
Click to expand...
Click to collapse
nope

ddggttff3 said:
nope
Click to expand...
Click to collapse
Will there be an update to Eureka or an updated stock with updates disabled ? I can not cast the BBC sports app with version 17250 on my 2 rooted Chromecast. Works fine on my none rooted 17977

revoxs said:
Will there be an update to Eureka or an updated stock with updates disabled ? I can not cast the BBC sports app with version 17250 on my 2 rooted Chromecast. Works fine on my none rooted 17977
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2638103
I hope to have 17977 posted there, and a Eureka ROM version soon. Still working on testing the ROM ATM.

Oops. updates issues from google.

Hi all, chromecast is on build 17977 eureka , keep coming up with
Oops, we are having issues updating your chromecast to the latest
version. Some features may not work. Visit chromecast.com/update
to get help.
How do i resolve this problem? ,currently no longer able to
Cast screen.
Your Ever Faithful Servant!!
Grassden
P.S. Did a reboot from eureka setting page, it show chromecast background
then came up the Oops message , impresume from google?

grassden32 said:
Hi all, chromecast is on build 17977 eureka , keep coming up with
Oops, we are having issues updating your chromecast to the latest
version. Some features may not work. Visit chromecast.com/update
to get help.
How do i resolve this problem? ,currently no longer able to
Cast screen.
Your Ever Faithful Servant!!
Grassden
P.S. Did a reboot from eureka setting page, it show chromecast background
then came up the Oops message , impresume from google?
Click to expand...
Click to collapse
im able to use everything fine,
can cast from PC, and mobile etc ..

i have 4 chromecasts, 3 on the new hubcap exploit and one on the older exploit all doing the same thing for the last 2 days
one is a developer registered device and 3 are just normal and all 4 of them keep showing the "opps issues updating screen"
i have tried different whitelist sources and disabled/enabled updates on the team eureka web panel and nothing stops them from getting this message
the chromecasts still work and allow me to cast apps and mp4's and stuff to them, it seems its just the google/chromecast homescreen that drops out and shows this message

More info
Hi all, thanks for replys, here my info on my chromecast,
Eureka 17977.001 (24/07/2014)
Internet: Available
Serial: 342101ZLXGX
Settings page is eureeka rom and all enable , whitelist is eureka
Question 1. Would a force check update in debug page solve the issue ? (Reason i asked is basically iv not got the
Knowledge to know if that would help!) Chuckles
2. Cast screen on my samsung s4 (i9505 model) stop working after oops message appears.
Your Ever Pathetic Servant
Grassden

I experience the same problem.
For anyone else also dealing with this, please note that the Chromecast does work, it's simply the homescreen that displays this instead of the usual photos.

Solved!?
Hi all, hmm did a restart on my i9505 phone , did a cast screen and it eorking!!
But still we still have to understand where,how to resolve the oops message on starting chrmecast.
Yours Ever Pathetic Servant
Grassden

My CC imported from Amazon US during the short sales glitch window, rooted since day 1, OTA turned off in Eureka settings, now sowing oops screen instead of images?

I have the same issue.
Running the latest build from Eureka with OTA turned on.

heres a question, are those slideshow pics it normally displayed, local? or actually from google themselfs !?
if so surely it via that... detects not on correct firmware so send that screen instead ?

miniminus said:
heres a question, are those slideshow pics it normally displayed, local? or actually from google themselfs !?
if so surely it via that... detects not on correct firmware so send that screen instead ?
Click to expand...
Click to collapse
I have not yet seen this message on my unit but it does suggest that something about the default screen (which DOES load it's pictures rom Google Servers) Is doing some Version checking and reporting that your version is not up to date with what Google has as the latest ROM...
As long as the unit continues to work it shouldn't be a problem.
And once Team Eureka does a full EOD of the latest update and sends it to us this problem and message will probably go away.

EDIT: I'm not up to date, clearly. Thanks, minimus.

simonklit said:
Been looking a bit around. It seems that if you disable Team Eureka OTA Updates in the web-panel, then the message disappears, and the old photos are back.
Click to expand...
Click to collapse
then you missed the msg from the devs, saying just reboot the CC several times, and it will sort it self out ...
(which in effect happerned when you adjust the setting as you did.. the CC rebooted etc ..making it appear tthat ytou have to do that to fix it,
whenl all you needed to do was just a reboot !)

miniminus said:
then you missed the msg from the devs, saying just reboot the CC several times, and it will sort it self out ...
(which in effect happerned when you adjust the setting as you did.. the CC rebooted etc ..making it appear tthat ytou have to do that to fix it,
whenl all you needed to do was just a reboot !)
Click to expand...
Click to collapse
Definitely missed that one. Thanks!

Same here!
simonklit said:
Definitely missed that one. Thanks!
Click to expand...
Click to collapse
Hi all , Chuckles i second that thought! Never saw any news about the issue on feedly. (It just collects android news in general.) Which is usually where i get on my bit and pieces of knowledge on android basically, so curious as to how many chromecasts were affected by the issue?
Your ever pathetic servant
Grassden

grassden32 said:
Hi all , Chuckles i second that thought! Never saw any news about the issue on feedly. (It just collects android news in general.) Which is usually where i get on my bit and pieces of knowledge on android basically, so curious as to how many chromecasts were affected by the issue?
Your ever pathetic servant
Grassden
Click to expand...
Click to collapse
It was only happening on rooted devices running Eureka Rom which is why you probably didn't hear much about it other than here

green screen in Chromecast

First of all I don't know if this is a general question or modding-related as I am running leankernel 1.5 and latest Rastapop but are other people (running custom or not) successfully casting their phone's screen to Chromecast? I am not talking about separate apps like Youtube etc. they do work fine on me as well. The problem appears when I just connect my entire phone through the "Casting" tile from quick settings in order to do some picture browsing or use an app or a game through my tv. Then my tv just shows a "dead" green screen and that's it

It's a bug with all custom roms right now. Although some roms have the feature working. If you're asking which roms, find it yourself as I don't remember the roms with the feature fixed.
Sent from my Nexus 6 using Tapatalk

Does that mean that stock 5.0.1 is free of this bug? It would be a reason to revert back to it since custom roms are not offering that many of the traditional "extra" features yet.

Works fine ok on stock rom with stock or custom kernels

mclisme said:
Does that mean that stock 5.0.1 is free of this bug? It would be a reason to revert back to it since custom roms are not offering that many of the traditional "extra" features yet.
Click to expand...
Click to collapse
The stock ROM works.

Thanks guys

mclisme said:
Thanks guys
Click to expand...
Click to collapse
There's a button for that

Chromecast Mirroring

Hi all, someone had problems with mirroring phone with chromecast? App like youtube are ok, but total mirroring disconnects instantly.
With one plus 3 (not T) all was ok.
Ty

Simone365 said:
Hi all, someone had problems with mirroring phone with chromecast? App like youtube are ok, but total mirroring disconnects instantly.
With one plus 3 (not T) all was ok.
Ty
Click to expand...
Click to collapse
I will have to try this when I get home and I will let you know

Seems to be a bug from SO. Many people is complaining about this in the official OnePlus community.

mikeazores said:
Seems to be a bug from SO. Many people is complaining about this in the official OnePlus community.
Click to expand...
Click to collapse
ah nice, i didn't find anything. Thank you for the info.

I have the same problem... I don't know what to do...

same problem here - 1+3t see my chromecast device , attempts to connect and... thats all

I've not screwed around with this problem much since I don't "cast screen" aside from netflix which works (as said here). I did some screen casting from CM in the past, But::
I've experience the identical symptoms of this problem on CM13, CM14, etc, with their built in cast command. I don't know if it'll be identical or of any help, but I had to get rid of all of the /system partition based "cast" (whatever it's called in this version), from /system/apps ./priv-apps and other /system-like places..
When you are sure you've got it all gone, using root explorer or adb or whatever you prefer (of course, you have to be rooted) , then reboot, then install Google Home(chromecast) from the play store. That worked fine in the CM's. I'll see if I can dig up the correct file names & folders that apply to this version and get back to this thread if I do.
I'll be happy to be the guinea pig, so don't do this unless you want to take a chance on screwing up your phone, until I report back.
Edit 1: Of course, the 3t does it differently. They're using all /data spaces for the cast, and since I've installed "google home" I have to get rid of it first to figure out which files remain. Here is what there is right now, not that there is anything worth doing with it unless I've uninstalled Google Cast via play store:
/data/data/com.google.android.gms/cache/cast_mirroring_raw_events.log.gz
/data/data/com.google.android.gms/shared_prefs/google_cast.xml
/data/data/com.google.android.gms/shared_prefs/PREF_CAST_SENDER_ID.xml
/data/data/com.google.android.gms/shared_prefs/CastDeviceCache.xml
/data/data/com.google.android.gms/shared_prefs/CAST_ACTIVE_NETWORK_MAP.xml
/data/data/com.google.android.gms/shared_prefs/googlecast-setting-prefs.xml
/data/data/com.google.android.gms/shared_prefs/PREF_CAST_SENDER_NONCE.xml
/data/data/com.google.android.gms/app_sslcache/cast.google.com.443
/data/data/com.google.android.apps.chromecast.app
/data/data/com.google.android.apps.chromecast.app/shared_prefs/com.google.android.apps.chromecast.app_preferences.xml
/data/app/com.google.android.gms-1/lib/arm64/libgcastv2_base.so
/data/app/com.google.android.gms-1/lib/arm64/libgcastv2_support.so
/data/app/com.google.android.gms-1/lib/arm64/libjgcastservice.so
/data/app/com.google.android.apps.chromecast.app-1
/data/dalvik-cache/profiles/com.google.android.apps.chromecast.app
Click to expand...
Click to collapse
And a log of cast from settings:

same problem but I am happy that Netflix and Spotify works.