Jump to content

  1. 0
  2. 0
  3. 0/5

Rate this Topic

- - - - -

[MOD] [CM9A2] Flashable build.prop for CM9 Alpha 2 - Fix for Chrome Beta

tenderloin buildprop alpha2 cyanogenmod chrome
  • Please log in to reply

OP eyeballer

eyeballer

TeamWin

Posted 25 February 2012 - 11:41 AM #1

While this still works for Alpha 2, it is already fixed if you run a nightly: http://rootzwiki.com...nightly-builds/

------------

The latest chrome beta checks Build_ID in the build.prop to ensure compatibility. Up until now tenderloin was building with a GB Build_ID which broke chrome compatibiltiy. This is now fixed in mainline CM9 code (see my patch here: http://review.cyanog...m/#change,13008) for future builds.

However, on Alpha 2 (which is where you should be for hw video decoding) the fix is to edit a line in build.prop. Replace "ro.build.id=GWK74" with "ro.build.id=IML74K". (Fix taken from here: http://tinyw.in/fSAb)

For those not comfortable doing this I made a flashable fix for it. Just flash the .zip in recovery over alpha 2.


Downloads

alpha2 stock (160dpi): http://tinyw.in/n6Hl

alpha2 120dpi version: http://tinyw.in/CTo5 <- flash this AFTER flashing dalingrin's 120dpi .zip

Edited by eyeballer, 28 February 2012 - 02:27 PM.

  • 7 Likes
Posted Image Posted Image

aNYthing24

aNYthing24

Average Android

  • 8 posts

Posted 25 February 2012 - 11:56 AM #2

Thanks so much.
  • 0 Likes

ReyPaez

ReyPaez

Android Beginner

  • 38 posts

Posted 25 February 2012 - 12:04 PM #3

Thanks man.
  • 0 Likes
Phone: HTC EVO 4G LTE
Rom: Stock (Rooted)
Kernel: Stock (Tweaked by Freeza)
Recovery Image: TWRP
Hardware: 003 | Radio: 1.02.12.0427 | PRI: 2.28_003 | PRL: 25004

tom1l21

tom1l21

Android Beginner

  • 16 posts

Posted 25 February 2012 - 12:09 PM #4

I've changed my DPI to the native 132 for the screen and it appears (to me at least) to be less crisp (compared to 160). Am I seeing things or is the native DPI of 132 somehow using scaled down graphics of the 160 DPI? In regards to that last sentence, I have no idea how DPI/scaling works, so it's just a guess.
  • 0 Likes

Stuart_f

Stuart_f

Android Apprentice

  • 75 posts

Posted 25 February 2012 - 12:10 PM #5

Works a treat, thank you for posting. +1 to you sir!

For those manually editing build.prop for the first time, don't forget that you need to reboot for the changes to take effect.

Edited by Stuart_f, 25 February 2012 - 12:11 PM.

  • 0 Likes

amena09

amena09

Member

  • 24 posts

Posted 25 February 2012 - 12:37 PM #6

should i upgrade the chrome beta and then flash this?
  • 0 Likes

eternalx

eternalx

Member

  • 13 posts

Posted 25 February 2012 - 02:28 PM #7

Thanks for this! But it seems to alter my 120 dpi back to 160. Is this suppose to happen? I know that both modifies the build.prop.
  • 0 Likes

Stuart_f

Stuart_f

Android Apprentice

  • 75 posts

Posted 25 February 2012 - 03:03 PM #8

Thanks for this! But it seems to alter my 120 dpi back to 160. Is this suppose to happen? I know that both modifies the build.prop.


The zip contains the line:
ro.sf.lcd_density=160

You can just flash the 120 dpi zip after eyeballer's zip or just edit the build.prop yourself.
  • 0 Likes

OP eyeballer

eyeballer

TeamWin

Posted 25 February 2012 - 03:11 PM #9

Thanks for this! But it seems to alter my 120 dpi back to 160. Is this suppose to happen? I know that both modifies the build.prop.


Updated OP with a 120 dpi version.
  • 1 Likes
Posted Image Posted Image

brentos

brentos

Android Beginner

  • 7 posts

Posted 26 February 2012 - 02:44 PM #10

You can edit the build.prop very easily with this: https://market.andro...ild.prop.editor
  • 0 Likes