[Q] Chrome on ICS problems - General Questions and Answers

Recently upgraded my DINC to ICS using Abduction v1.81 and I'm having a problem with Chrome Beta. When I launch it initially everything seems fine, it asks for log-in info which is provided and then shows the tab and search icons. When actually entering a web address, though, the entire page is blank. It would seem that it is going to the address but nothing ever shows, regardless of what website is chosen.
I have searched the Abduction forum to no avail, no one else seems to be having this problem after the AOKP Build 26 update, or at least hasn't spoken of it. Possibly an HWA problem?
HTC Incredible
Abduction ICS v1.81
V6 SuperCharger (tried Chrome before/after running scripts...same issue)
Holo-mod
No other mods to speak of really. Any ideas would be appreciated.

chrome beta
i have had the same problem on my nexus s 4g running 4.0.4 and it would only open up and it would be blank and foreclose shortly after i noticed that it is a rom problem because i just flashed a new rom and chrome has been working great maybe do a back up and try a new rom see if that helps!

Related

Offical Netflix app released for us!!

http://www.engadget.com/2011/05/12/netflix-releases-android-app-for-select-htc-phones-samsung-nexu/
And it works!
Edit: My current setup is a AMOLD dinc, running CM7 with 2.3.3. 16GB msd in to.
Download from market:
https://market.android.com/details?id=com.netflix.mediaclient
Netflix is apparently blocking unsupported devices when you try to login, I uploaded the apk to my xoom to test it and it did not let me login.
I have the app and have not yet been able to get it to load. I just get a black screen.
However, I noted that the details on the market page state it is official for the Incredible running 2.2, and I'm running CM7.
Has anyone else tried with CM7?
Assuming there are indeed compatibility issues, I'm hopeful the devs will find a way to make it work, because I'm not looking forward to going back to stock, but I need Netflix.
(Actually. Right now, I'm thinking about loading up one of the dual-boot options with some stock Froyo. This is worth the effort.)
Edit: The dual-boot option is awesome and all... But then, I tried again in CM7, and I found that I spent a few hours heavily tweaking my phone for nothing but the thrill; the app works, and I was watching Ong Bak 3 in seconds. Since I don't need a Sense rom, I undid the dual-boot configuration.
So. Works on CM7.
Just saw this. Not showing up for me in the market. I assume its a CM7 thing.
Maybe we can find locate an apk.
Sent from my DInc
Just installed! Going to test now! Biggest app missing since switching from iPhone 4!
Sent from my Nexus S using XDA App
Here's a market link.
http://market.android.com/details?id=com.netflix.mediaclient
I am up and running on CM7.0.0.
Sent from my DInc
Im running evervolv and it works fine for me
Sent from my DInc
no it works. i had to scroll down in the market a bit to find it. i was able to watch a movie also
apk please!
Can someone pull the apk please? I know it probably won't work, but I can't wait to try running it on my DX and Xoom!
Installed from the market, but all I get is a black screen for a long time, then an FC...
CM 7.0.3
Just tested and it does stream on CM7.
Works fine for me as well.
CM7.0.3
running CM 7.0.2.1 DINC, and program will shut off right after I try to log in
If somebody could post the APK, Thunderbolt folks would be grateful. I know it is blocking unsupported devices, but our devs want to take a crack at it. Thanks!
I am on CM Nightlies and it doesn't work. Considering a move to 7.0.0.3 just for netflix.
Works for me on CM and my DInc
Here's the apk
Working on my DX!!!
I'm streaming Law and Order right now!
Greatest.
Day.
Ever.
(until it stops working again like last time hopefully not)
Xoom trial coming soon.....!!
buya97 said:
running CM 7.0.2.1 DINC, and program will shut off right after I try to log in
Click to expand...
Click to collapse
Im getting the exact same thing on latest CM7 nightly
Running stock (rooted) 2.2 and mine force closes immediately after trying to launch the app. Somebody mentioned something about Flash 10.3 so I updated and still get force close. Any ideas?
Not sure if this info helps, but it works fine on mine:
CyanogenMod-7-04172011-NIGHTLY-Inc
[email protected] #1
Sorry, I'm not sure how that converts to the actual nightly number, but its what I was able to gleen out of the Rom Manager.

[Q] Persistent problem with BBC iplayer and embedded clips ever after new ROM

Hi,
Any thoughts, ideas comments greatly appreciated.
Since purchasing my Desire S I have never been able to play BBC iPlayer or the embedded clips in the BBC website (specificaly those showing highlights of Scottish Football - yes, that's probably a good thing!).
One of the reasons for experimenting with Rooting and flashing a new ROM was the hope that this would provide the solution I needed as no amount of updating and reinstalling Adobe Flash, using different versions of this or using different browsers seemed to make any difference. Changing news.bbc.co.uk/... to cdnedge.bbc.co.uk/... doesn't work either and doesn't actually address the iplayer issue either.
Now, running a rooted Desire S with a Custom ROM, I thought that this would resolve whatever hidden issue was causing the problem.
All other video types play fine in the stock video player, so I don't think its a hardware issue.
Meant to add. I can hear sound fine, and can see the scroll bar marking progress of the iplayer episode/eweb clip as well. It's just simply that the video is missing.
Could there be an issue with the phone itself?
Mod Version: CyanogenMod 7 10082011 NIGHTLY
Device: HTC Desire S
Radio : 20.281.30.085AU_3805.06.02.03_M
Kernel : [email protected]#1
Now this may be entirely unrelated and possible a shade off-topic, but if I use my DS internet browser to check my flash version using URL:
http://www.adobe.com/software/flash/about/
It tells me that I have version 10.1 installed (note: take care not to confuse this with the boxes which say what versions are available)
Even after installing Flash version 11 from Android Market, the web page above still tells me that I have version 10.1 on my DS.
Other people claim that their DS responds with version 11 on this page, so I'm puzzled. But even after installing Flash 11 right from factory-reset settings it still reads wrong for me. Perhaps it's related to phone ROM version.
Flash 11 never seems to use any of it's cache on my DS - I do wonder if it's actually "connected" to my web browser at all!
- Steve
Exact same problem with me. Iplayer just shows a black screen.
Sent from my HTC Desire S using xda premium

Has anyone tried the Chrome Beta apk with MeDroid?

I installed a Chrome Beta apk I got from some of the other forums here at XDA, but I seem to be getting FCs every time I launch the app, was wondering if anyone got it working or if anyone has found a fix for this issue.
It requires hw acceleration. Won't work for us yet until we get that achieved.
Sent from my Nexus One using xda premium
That makes sense, I did manage to download an apk that does not FC every time, but I can't really says it's usable.
Here's hoping the CM9 team or some other dev manages to make it work someday.
ryuz4ki said:
That makes sense, I did manage to download an apk that does not FC every time, but I can't really says it's usable.
Here's hoping the CM9 team or some other dev manages to make it work someday.
Click to expand...
Click to collapse
I got it directly from the market and it loads but all pages are blank.
Sent from my Nexus One using xda premium
I can't download it from the market since I don't live in the US, but I get the same results as you, it loads but all pages are blank, and I can see the synced results on the omnibox but no page returns.
I have it installed. No FC's, but it doesn't work. As stated, it needs hardware acceleration. It went through the entire setup, sign in, and import of all normal information. But when you try to load anything, you stare at a blank screen.
have u try texasice' ROM, igoogle chrome beta work great with ICS AOSP
For anyone wanting latest Chrome beta without modifying build.prop, go here:
http://forum.xda-developers.com/showthread.php?t=1515900
I flash the "MeDroidMOD 1.4.0 HWA" ROM that can run chrome browser,but it can't switch tab.So my chrome browser has many tabs and can't close it.
Have any one know to solve it?
s2170801 said:
I flash the "MeDroidMOD 1.4.0 HWA" ROM that can run chrome browser,but it can't switch tab.So my chrome browser has many tabs and can't close it.
Have any one know to solve it?
Click to expand...
Click to collapse
Update to 1.4.2 fixes Chrome beta so you may want to give it a go.
I tryied once downloaded from dropbox and it works fine but a little slow
I tryied once downloaded from dropbox and it works fine but a little slow

[Q] No Facebook Notifications On UCLB3 Based ROM's

Hello all. Been reading and learning for awhile now and just registered on the forum. Firstly I want to say thanks to the Mods, Devs, testers, and anyone who has posted information on these forums. Thanks to you all I can keep my old phone going with cool and relevant software! I'm new to flashing so decided to start with Gingerbread based ROM's on my Infuse so that I can see the progression and learn. I flashed Emancipation A1 first and really liked it. However, I could never get FB notifications to work despite all of the app settings being correct. I decided to give AEON v1.4SL a try so I flashed it. I tried FB first thing and had the same issue. I tried a factory reset and then put FB.apk, SNSaccount.apk, SNSprovider.apk, and updateandfeed.apk, from the deleted apps package of AEON, in /system/app. I let FB update to v3.8 and still had no luck. I then Heimdall'ed back to stock UCLB3 and tried FB v3.8 and it worked perfectly. All of my other notifictions (gmail, outlook, yahoo, gtalk) work fine. Any help with this issue would be much appreciated. Thanks!
I would really like to get the Facebook notification issue worked out. Am I the only one who has this problem on Emancipation A1 and Aeon 1.4SL? Do other custom 2.3.6 UCLB3 ROM's work properly with FB notifications? Please help, I have searched this issue and can't find anything that resolves it.
Hi all. I realize not many people are using Gingerbread based ROM's at this point in the game. In case anyone is, I have some more details for this issue. I flashed Legend 4.1 ICS Edition and had the same Facebook issue. I then started FB messaging myself from my Girlfriends phone while watching running services on my phone. As soon as the message came through on my tablet sitting next to me, I would see one or two additional services pop in for FB on my infuse. Still no notification would ever display. So its like the FB app sees the message but the launcher won't fire a notification. I tried different launchers and had the same result. The closest I ever got was with AEON 1.4 SL using the Xperia Home launcher. Xperia Home would show a message count on the FB shortcut but nothing in the notification bar. Anyone have any ideas?
Casper36 said:
Hi all. I realize not many people are using Gingerbread based ROM's at this point in the game. In case anyone is, I have some more details for this issue. I flashed Legend 4.1 ICS Edition and had the same Facebook issue. I then started FB messaging myself from my Girlfriends phone while watching running services on my phone. As soon as the message came through on my tablet sitting next to me, I would see one or two additional services pop in for FB on my infuse. Still no notification would ever display. So its like the FB app sees the message but the launcher won't fire a notification. I tried different launchers and had the same result. The closest I ever got was with AEON 1.4 SL using the Xperia Home launcher. Xperia Home would show a message count on the FB shortcut but nothing in the notification bar. Anyone have any ideas?
Click to expand...
Click to collapse
check out your notifications status in FB maybe it's unchecked
FB settings were all correct. I hashed over and over every setting. I've moved to CM9 to try it out. FB notifications function properly with CM9.

[Q] Chrome keep hanging on big part CM and OMNI

Hi
I can't post in real thread so it is here , I'm on big part from beginning (Everest XOOM) and at first everything works great but in last two weeks problem start both on Chrome and Chrome Beta.
I try dalvik wipe , cash wipe, try to use ART , try to reinstall both applications , to remove flash player and finally switch from OMNI to CM11 but there is still same problem
so if anybody have any suggestion it would be great
Many thanks in advance
I install ElementalX-Xoom-2.1 ( full version not vanilla ) and enable zrom and it is better I can work little longer on Chrome but eventually problem occurs again ...
gtrhr said:
I install ElementalX-Xoom-2.1 ( full version not vanilla ) and enable zrom and it is better I can work little longer on Chrome but eventually problem occurs again ...
Click to expand...
Click to collapse
I also had serious problems with Chrome constantly freezing and crashing on my Xoom wifi upgraded to Kitkat Omnirom 4.4.2. I've installed version 33 as advised in another thread (a developer one that doesn't allow me to post there), using an apk file linked on that thread.
I haven't tested this yet but, assuming it works ok, how do I stop it from updating automatically? Any idea on how we'll know when an update appears that is safe to install, and will work?
Chrome Beta
I had the same problem too. Chrome on Omni and TeamEOS kept freezing. Only to kill the running app was helpful till it freezes again.
Then I've installed Chrome Beta (v37.0.2062.55) and since then everything seems ok. Until now no more freezes.
Maybe anybody else to prove that?
Simple fact of the matter is, KK is just slow on the Xoom. I'm amazed that we even saw 4.4, seeing as how mine (wingray) is over 4 years old.
I ran CM11 there for a while, but the constant freezing of Chrome and the slow clunkiness of the interface was enough to drive me back to CM10.1

Categories

Resources