NEW!!! Chrome Beta (4/17/2012) not working after update

cvcduty · Apr 17, 2012

Yet again, Google Chrome Beta is broken after the latest update. I have ICSSGS RC4.2 and just updated Chrome Beta to the latest release. And as before, this update fails the Chrome Beta to launch on my Cappy... so beware...

I am using my old copy as before until someone figures out how to fix it...

... again...

cmilldrummin · Apr 18, 2012

Running 4.0.4 AOKP build 32 and it works with no problems.

Sent from my glitched ICS Captivate using XDA App

cmilldrummin · Apr 18, 2012

Have you tried editing your build.prop, which was the easiest fix for the previous chrome issues?

Sent from my glitched ICS Captivate using XDA App

cvcduty · Apr 18, 2012

cmilldrummin said:
Have you tried editing your build.prop, which was the easiest fix for the previous chrome issues?

Sent from my glitched ICS Captivate using XDA App

I can and I will but what should the build.prop entry be to allow Chrome to load properly?
The thing is, I can find the new update with no issues. It installs fine, it just refuses to open. It hangs and then dumps me to the main window.
So, can someone give me suggestions as to what the right build.prop entry should be and I will try it.

Thanks

cmilldrummin · Apr 18, 2012

Look at your build.prop and the line that says ro.build.id= should match the line that reads ro.build.display.id=. If either one says gingerbread edit it to match the other and reboot your device.
Sent from my glitched ICS Captivate using XDA App

objectuser · Apr 19, 2012

Chrome is working for me on my Captivate, running Slim ICS (even though Chrome is fairly buggy and annoying in one or two places).

cvcduty · Apr 19, 2012

cmilldrummin said:
Look at your build.prop and the line that says ro.build.id= should match the line that reads ro.build.display.id=. If either one says gingerbread edit it to match the other and reboot your device.
Sent from my glitched ICS Captivate using XDA App

Ok. So my build.prop shows as such.
ro.build.id=IML74K
ro.build.display.id=SGH-I897-user 4.0.3 IML74K eng.onecosmic.20120204.223407 test-keys

So what has to match? Do I edit the display ID=IML74K??? and delete the rest?

cmilldrummin · Apr 19, 2012

Make a backup before doing so, but yes chrome beta does a check to see if that line is correct. If it's says something other then what a stock ROM would say, it won't run. So change it as you already described and it should work fine. But again make sure to make a backup of your build prop before doing so, just in case.

Sent from my glitched ICS Captivate using XDA App

nnchoudhari · Apr 20, 2012

cmilldrummin said:
Make a backup before doing so, but yes chrome beta does a check to see if that line is correct. If it's says something other then what a stock ROM would say, it won't run. So change it as you already described and it should work fine. But again make sure to make a backup of your build prop before doing so, just in case.

Sent from my glitched ICS Captivate using XDA App

I tried this change .. no success

cmilldrummin · Apr 20, 2012

Did you reboot after editing and make sure the change stuck?

Sent from my glitched ICS Captivate using XDA App

sbu888 · Apr 20, 2012

cmilldrummin said:
Did you reboot after editing and make sure the change stuck?

Sent from my glitched ICS Captivate using XDA App

I have same problem too. Updated build.prop and reboot but still not work

cvcduty · Apr 20, 2012

sbu888 said:
I have same problem too. Updated build.prop and reboot but still not work

Ok... It seems that some people are using what I posted as a direction to change the build.prop to make the Chrome work... Actually, what I put on my earlier post is my exact build.prop what is NOT allowing the Chrome to work... so some one needs to provide an exact line entry. Please do not use my post as this is how my stock (ICSSGS ICS RC4.2) build.prop looks like...

Sorry for the confusion.

Limitz Cash · Apr 22, 2012

I downloaded chrome beta, but I cannot even install it. Something about a para phase error. Idk

Sent from my Serendipity VII flashed Captivate using xda premium

elmerct · Apr 22, 2012

I'm not sure if your situation is the same, but upgrading an existing chrome install didn't work for me. It crashed whenever I tried to open it. I uninstalled the one I had then installed the latest one from the play store. Its been working fine since. Running Slim 3.4 btw.

Sent from my SGH-I897 using xda premium

bravomail · Apr 23, 2012

You guys should tell me why I should bother getting Chrome? Isn't stock browser Chrome based with HW accel by Samsung?

technosapien · Jun 26, 2012

I've just tested this problem myself, and if you have LCD density set to 120 that's the cause of the issue. Set it back to 160 in build.prop or using dalingrin's CWM zip, and it works....

technosapien · Jun 28, 2012

Fixed in latest update to Chrome... now works at lcd density of 120.

technosapien said:
I've just tested this problem myself, and if you have LCD density set to 120 that's the cause of the issue. Set it back to 160 in build.prop or using dalingrin's CWM zip, and it works....

bravomail · Jun 28, 2012

BTW Chrome release works. How do you like it? Beta was superbuggy, would not render certain websites, or leave white holes.

arceusg · Aug 25, 2012

still won't work on custom roms

Sent from my YP-G70 using xda app-developers app

wwcjr91 · Aug 25, 2012

arceusg said:
still won't work on custom roms

Sent from my YP-G70 using xda app-developers app

What do you mean by "won't work"? It's working on my captivate.

NEW!!! Chrome Beta (4/17/2012) not working after update

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

New member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Member

Senior Member

arceusg

Guest

Senior Member

Similar threads