Related
I just updated Google Maps to 5.4.0 and found we get vector maps (and 3D tilt, for those who care) as well as "Cache Settings" without the build.prop edit!
This is just an FYI to those who go through the trouble of making this particular edit to the build.prop every time you flash a new ROM; now you don't have to!
I'm running CM7 nightly 61 and the build.prop as usual shows
ro.opengles.version = 65537
those build edits never did anything its just a placebo affect.
Bierce22 said:
those build edits never did anything its just a placebo affect.
Click to expand...
Click to collapse
You are mistaken. If you've tried it, you would have seen the instant difference. With vector mapping street names and places appear and re-size dynamically as your pan and zoom. They are not static tile images being loaded. Also, without the build.prop edit you couldn't even get a "Cache Settings" button when you press menu.
Have you even tried the build.prop edit or are you a troll?
I'm referring to the last bullet point info here:
http://romrepo.info/wiki/index.php?title=Sprint_HTC_Hero
I'm not talking about any other build.prop edit, in case you think I'm referring to kifno's. I know those are shady at best.
i tried the opengles stuff awhile back and they never really did anything for me.
Bierce22 said:
i tried the opengles stuff awhile back and they never really did anything for me.
Click to expand...
Click to collapse
Then you did it wrong. I did the edit for every build, c00ller's post is exactly correct. Thanks for the tip c00ller I do wonder though, since 131072 spoofed open GL 2.0, if any other apps would be affected.... I doubt it, just postulating.
Thx c00ller for the heads up!
Sent from my HERO200 using XDA Premium App
I second and third the build prop edit does work.
Hijacked aospCMod Darkhorse GB Hero
how well would this work on the hero anyway
Well I'll be damn. How come they couldn't do this at the beginning!! >_<
Because google loves to update.
#Root/Hack-Mod_Always*
Ah the updates. So bitter/sweet sometimes.
Is this of value to anyone?
http://www.multiupload.com/NPZ062QIZB
Netflix is not supported on this device. Please check the Netflix website for a list of supported devices.
krymzon40 said:
Netflix is not supported on this device. Please check the Netflix website for a list of supported devices.
Click to expand...
Click to collapse
That sucks. But I was more interested in using a .prop file that pretends to be a Nexus One and would then allow the app to work. Some folks around here are pretty bright.
Does anyone know if this works on ED12?
Seems to work on the Captivate with Gingerbread:
http://forum.xda-developers.com/showthread.php?p=13730833#post13730833
tbob18 said:
Does anyone know if this works on ED12?
Seems to work on the Captivate with Gingerbread:
http://forum.xda-developers.com/showthread.php?p=13730833#post13730833
Click to expand...
Click to collapse
Good sleuthing. Hopefully someone with Gingerbread in here will try it out.
was gonna ask the same thing. obviously if the nexus S is running it, we should be able to as well since both phone use the 1gh hummingbird but im assuming the DRM security setting are probably only found in gingerbread for us so we may have to wait unless like Zenlnsight said, possibly install a workaround so it is compatible for us on froyo
Android 2.2 phones are supported, so it doesn't seem to be a Gingerbread only thing. Maybe it's a hardware support only thing.
ZenInsight said:
That sucks. But I was more interested in using a .prop file that pretends to be a Nexus One and would then allow the app to work. Some folks around here are pretty bright.
Click to expand...
Click to collapse
This
10char
Getting Protected Apps To Show in Market (Nook example below)
Certain apps (e.g. SlingPlayer) have special settings which prevent them from being backed up normally. These apps do not appear by default in the market. To enable these apps you need to change the device fingerprint and spoof a valid device.
adb pull /system/build.prop
Edit the following line:
ro.build.fingerprint=generic/sdk/generic:Honeycomb/Nook/eng.rbrune.20110131.162619:eng/test-keys
so that it reads:
ro.build.fingerprint=google/soju/crespo:2.3.2/GRH78C/93600:user/release-keys
This spoofs the Nexus S running Android 2.3.2 per this site
Save the modified build.prop to NC.
adb remount
adb push build.prop /system/
Now clear the Market cache. On the NC, open the settings app and make the following changes:
Settings -> Manage Applications -> All -> Market
Clear Cache then Force Stop -- DO NOT clear data
Settings -> Manage Applications -> All -> Google Services Framework
Clear data then Force Stop
Then reboot the NC, for example:
adb reboot
Disconnect the USB cable.
Market should now show the protected apps.
Anyone want to try to run Netflix after messing with their build.prop file?
Going to poke around and see what I can do.
Didnt get the unsupported device popup after changing bulid.prop but after inputting my email and password the app stopped and went to the homescreen. Im restarting my phone and will try again. I may have put in the wrong login info also as I haven't logged into netflix in a long time.
After restarting the unsupported device prompt comes back and it still doesn't work. FU Netflix
What about changing ro.build.description?
I edited my build.prop, was able to get to the login screen but then got dumped to homescreen after putting in my info. I also tried incorrect info, which it informed me was wrong but did not dump me to homescreen.
Don't really know what any of this means, but it's what happened.
Has anyone tried running this on a Gingerbread rom + spoofing their build prop?
On Gingerbread it may be running a gingerbread only function...or etc..
also tried running a logcat while doing it?
Schuby said:
Going to poke around and see what I can do.
Click to expand...
Click to collapse
Schweet! Do it bro. I'm at work right now. I'm going to try it later.
Edit: I just saw replies coming in . May be I spoke to soon.
Someone posted the Nexus S 4g build.prop here:
Android Hacking Netflix thread:
http://forum.xda-developers.com/showpost.php?p=13733918&postcount=170
Nexus S 4g Build.prop file
Someone else said:
I don't know what to say - I'm watching Futurama on my Nook Color as I type here on my laptop. I changed the build.prop to match my G2, and it worked right away.
What changes did you make
ro.product.model=HTC Vision
ro.product.brand=tmobile
ro.product.name=vision
ro.product.device=vision
ro.product.board=vision
ro.product.manufacturer=HTC
ro.build.fingerprint=tmobile/htc_vision/vision/vision:2.2/FRF91/277427:user/release-keys
Also, it's not actually working on my G2 as it turns out, just on my nook, which is weird.
Click to expand...
Click to collapse
Keep in mind when you guys modify this stuff, Netflix might be leaving behind residual data in /data or the SD card. If you merely change the build.prop and re-try, it may not continue to work.
This almost works for me:
ro.product.model=HTC Vision
ro.product.brand=tmobile
ro.product.name=vision
ro.product.device=vision
ro.product.board=vision
ro.product.manufacturer=HTC
ro.build.fingerprint=tmobile/htc_vision/vision/vision:2.2/FRF91/277427:user/release-keys
I used SGS Tools to change the values
It starts playing but only audio, no video and then goes back to the main netflix screen.
found it here:
http://forum.xda-developers.com/showpost.php?p=13732640&postcount=11
haas599 said:
Didnt get the unsupported device popup after changing bulid.prop but after inputting my email and password the app stopped and went to the homescreen. Im restarting my phone and will try again. I may have put in the wrong login info also as I haven't logged into netflix in a long time.
After restarting the unsupported device prompt comes back and it still doesn't work. FU Netflix
What about changing ro.build.description?
Click to expand...
Click to collapse
Are you on Gingerbread though?
Hey guys. Can we start listing what ROMs and version of Android we are using? I only think this works with Gingerbread ROMs...like ED12.
ZenInsight said:
Hey guys. Can we start listing what ROMs and version of Android we are using? I only think this works with Gingerbread ROMs...like ED12.
Click to expand...
Click to collapse
Evo4g is supported and it doesn't have official Gingerbread yet.
As far as the Epic goes, nobody has it working yet.
The epic 4G continues to be the bastard child of support and development.
Sent from my SPH-D700 using Tapatalk
I am looking into using Skype with a bluetooth headset; however, when I make a call to anyone including the "test/echo" number the call is dropped "Call Failed" as soon as the other person answers. Has anyone experienced this or found a work around?
What ROM do you run?
I run CM7 from SD and skype hung on first screen.
I don't have any Bluetooth connected.
Beta starts fine, have nothing to test it with tho
If you don't run it already - get it from this post:
http://forum.xda-developers.com/showthread.php?t=908479&highlight=skype&page=3
Nat... I get the same call dropped.
The new skype is not "hung". There is a barely visible button right behind the taskbar on bottom. Click it n u will be able to continue.
I have same problem
nat0925 said:
I am looking into using Skype with a bluetooth headset; however, when I make a call to anyone including the "test/echo" number the call is dropped "Call Failed" as soon as the other person answers. Has anyone experienced this or found a work around?
Click to expand...
Click to collapse
I have the same problem. Even though the NC has no mic or cam, I'd like to use it to view my contact's video. Any work around?
danformer said:
I have the same problem. Even though the NC has no mic or cam, I'd like to use it to view my contact's video. Any work around?
Click to expand...
Click to collapse
I have done zero looking into this. But I do know that without 'voice capable' enabled in the framework-res, google voice and the like don't work for Nexus 7. With that changed it does.
If you have working headset audio, well I would try that next.
Edit: Here. I ran it though the auto-patcher. This allows the N7 to use Google Voice, it may do nothing for your project.
Thanks I took a look into it and didn't get much luck. Good news is that I found an alternative. Oovoo works with the nook color so I can see my friends video even though they can't see me. Thanks for the support guys.
Sent from my NookColor using Tapatalk HD
mateorod said:
I have done zero looking into this. But I do know that without 'voice capable' enabled in the framework-res, google voice and the like don't work for Nexus 7. With that changed it does.
If you have working headset audio, well I would try that next.
Edit: Here. I ran it though the auto-patcher. This allows the N7 to use Google Voice, it may do nothing for your project.
Click to expand...
Click to collapse
Mateorod, can you be more specific what you changed in framework-res? I use Google Voice a lot and it crashes on my Nook HD+ stock. I would love to fix that.
Sent from my HD+ rooted stock using Tapatalk
leapinlar said:
Mateorod, can you be more specific what you changed in framework-res? I use Google Voice a lot and it crashes on my Nook HD+ threadat.
Sent from my HD+ rooted stock using Tapatalk
Click to expand...
Click to collapse
Well usually I would tell you to just use the auto-patcher, but I haven't modified it for 4.2 yet. But that update is almost done. If this turns out too be useful to you guys the I will let you know for the future.
For right now, you will either need to be building from source, or have the latest apktool that works on Jellybean apps. Look at iBotPeaches' apktool thread, paulobrien submitted a patch that lets that work.
Decompile the framework-res.apk:
Code:
apktool if framework-res.apk
apktool d framework-res.apk
The first command installs the framework files ( reference material for apktool), usually not strictly necessary for custom ROMs but still a good idea just in case.
From there it is easy. Go to framework-res.out/core/res/red/values/books.xml and look for the boolean value "voice-capable" and change it to 'true'. You may end up enabling the Dialer as well, which you can uninstall, i believe.
Code:
apktool b framework-res.out framework-res.apk2
The above will recompile, remember to use an archive manager (7zip or something) to look inside the original framework-res.apk and move anything to framework-res.apk2 that is missing. Retitle your new apk to framework-res.apk and flash through a zip or install with adb.
Now, with a microphone, you should have VOIP calls through Google Voice, GrooveIP and the rest.
Edit: This post was updated with recompile instructions. I am not at home and wrote this off the top of ,my head, so let me know if something isn't working as expected maybe I have made a mistake. But it looks right. This mod will be in the auto-patcher for 4.2 pretty darn soon, to make it easier for everyday users.
Edit2: I just saw the post in your pm says 'Rooted HD+ running CM10" which means you can use the publically available version of the Auto-patcher and test this easily, with a restore.zip made.
mateorod said:
Well usually I would tell you to just use the auto-patcher, but I haven't modified it for 4.2 yet. But that update is almost done. If this turns out too be useful to you guys the I will let you know for the future.
For right now, you will either need to be building from source, or have the latest apktool that works on Jellybean apps. Look at iBotPeaches' apktool thread, paulobrien submitted a patch that lets that work.
Decompile the framework-res.apk:
Code:
apktool if framework-res.apk
apktool d framework-res.apk
The first command installs the framework files ( reference material for apktool), usually not strictly necessary for custom ROMs but still a good idea just in case.
From there it is easy. Go to framework-res.out/core/res/red/values/books.xml and look for the boolean value "voice-capable" and change it to 'true'. You may end up enabling the Dialer as well, which you can uninstall, i believe.
Code:
apktool b framework-res.out framework-res.apk2
The above will recompile, remember to use an archive manager (7zip or something) to look inside the original framework-res.apk and move anything to framework-res.apk2 that is missing. Retitle your new apk to framework-res.apk and flash through a zip or install with adb.
Now, with a microphone, you should have VOIP calls through Google Voice, GrooveIP and the rest.
Edit: This post was updated with recompile instructions. I am not at home and wrote this off the top of ,my head, so let me know if something isn't working as expected maybe I have made a mistake. But it looks right. This mod will be in the auto-patcher for 4.2 pretty darn soon, to make it easier for everyday users.
Edit2: I just saw the post in your pm says 'Rooted HD+ running CM10" which means you can use the publically available version of the Auto-patcher and test this easily, with a restore.zip made.
Click to expand...
Click to collapse
Thanks, will try the setting change. I want to change the framework-res on the stock HD+ which is ics. But I can try manually editing the apk.
Edit: I did edit it successfully but it did not fix my fc problem on the HD+ and GV. Thanks though.
Sent from my Nook HD+ Running CM10 on SD
Skype Call
I don't know if this helps but I just made a Skype call where they could hear me and I could hear them using a 7.1 Channel USB External Sound Card Audio Adapter I got off Amazon for like $4 so I don't know if a Bluetooth Dongle would help with getting a headset to pair and work but I am going to try that next but even if it does not work I can still use a computer headset and call people
Gamore said:
I don't know if this helps but I just made a Skype call where they could hear me and I could hear them using a 7.1 Channel USB External Sound Card Audio Adapter I got off Amazon for like $4 so I don't know if a Bluetooth Dongle would help with getting a headset to pair and work but I am going to try that next but even if it does not work I can still use a computer headset and call people
Click to expand...
Click to collapse
That is amazing. That is the first I have ever heard of anyone getting a microphone to work on the nook color. Could you provide a little more detail how you did it?
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
That is amazing. That is the first I have ever heard of anyone getting a microphone to work on the nook color. Could you provide a little more detail how you did it?
Click to expand...
Click to collapse
Someone reported using "dsp adapter (plantronics) on usb" for skype on NC in another forum...
Hey,
I bought the MLB At Bat 12 app, in order to watch games with my MLB.tv subscription.
The Note is in the compatible devices list, but I can't see the Video option.
Anyone has faced the same problem? Could it be that MLB only supports the AT&T version of the Note?
Thanks!
Edit:
MLB heard us and the International Note, AKA GT-N7000 is now a fully supported device.
Live games are working great.
Cheers!
crizolli said:
Hey,
I bought the MLB At Bat 12 app, in order to watch games with my MLB.tv subscription.
The Note is in the compatible devices list, but I can't see the Video option.
Anyone has faced the same problem? Could it be that MLB only supports the AT&T version of the Note?
Thanks!
Click to expand...
Click to collapse
There is no live feed during spring training, only radio.
Sent from my GT-N7000 using xda premium
You mean on the app?
'Cause they are streaming 150 Spring Training games. As a matter of fact, I'm watching a Red Sox game on my PS3 right now.
Yes on the app. On opening day the app will update and video will be available.
Sent from my GT-N7000 using xda premium
spring training videos are available on the streaming option. it works on my galaxy tab 10. however, I same facing the same problem on my note where there is no video icon to click on. I have already contacted MLB.TV. they say they will look into the problem and then get back to me. I suspect that the galaxy note they have on that list is the American version.
DMax99 said:
spring training videos are available on the streaming option. it works on my galaxy tab 10. however, I same facing the same problem on my note where there is no video icon to click on. I have already contacted MLB.TV. they say they will look into the problem and then get back to me. I suspect that the galaxy note they have on that list is the American version.
Click to expand...
Click to collapse
I have specifically read that you will not be able to watch on cellphones. I'll try to find it for you tomorrow.
Sent from my GT-N7000 using xda premium
I looked around and couldn't find anything saying that. I'll né gratefull if you could fid out querendo you saw that.
I've also contacted MLB suport, but they haven't answered back yet.
mlb on droid
I have a HTC Inspire which I had MLB At Bat 12 installed and it DOES offer games during spring training. I know because I was watching them up until I rooted the phone and installed a custom rom (RCmix), reinstalled mlb at bat 12 and now I do NOT have the video option.
MLB support has been a dead end. They don't even know what I'm talking about.
This is very frustrating, I was really hoping some games when not at home.
I'm having similar issues on both my Asus Transformer and Galaxy SII. Hopefully, as someone mentioned earlier, the video will be available on mobile devices on opening day.
mlb at bat/gummy rom issue
I have been watching spring training games on my paid subscription of mlb at bat on stock rom/rooted droid 4. Since I flashed gummy rom this morning, I get a video error message saying it cannot load the video. I can hear about 3 seconds of announcer audio although the screen is black and then i get the error.
Im assuming its a clash with gummy, but i was wondering if anyone else had this problem, or has a fix to make at bat gummy compatable.
Does at bat video streaming work with other custom roms?
thanks!
Anyone having any luck getting the video icon to show up on a tablet/phone?
nighthawk101 said:
Anyone having any luck getting the video icon to show up on a tablet/phone?
Click to expand...
Click to collapse
PLEASE PRESS THE THANK BUTTON IF THIS HELPS YOU!
YES!! I got this to work last year by editing the build.prop file to make my HTC HD2 running android look like a Nexus S. I even had fun with it so the market reports my phone as an HTC Nexus S.
I downloaded At Bat 12 in Feb. and the spoof still worked.
I just upgraded my phone to an HTC Sensation XE. he video icon was hidden on my new phone because it too is not officially supported.
I edited the build.prop on my new phone similarly and like magic, At Bat 12 shows the video icon now.
Here's how to do it:
0. Go to system settings->applications and clear data for At Bat 12
1. Using an app like Root Explorer, navigate to system->build.prop
2. Make sure you have r/w access and long press build.prop file to open in text editor
3. Scan build.prop file and make:
ro.product.model=Nexus S
(there may be 2 ro.product.model lines that need to be changed
ro.product.manufacturer=HTC
NOTE: These are the most important lines to change. If these don't work by themselves you can also make:
---OPTIONAL---
ro.product.brand=HTC_wwe
ro.product.name=yakjuxw
ro.product.device=maguro
4. Save build.prop file and open again to verify that changes were made. If your changes are not there, check that you are in r/w mode and repeat from step 1.
5. restart your phone, open At Bat 12 and reenter your account details.
Let me know if this helps you. If it does not, let the forum know and we can work out the kinks. This method works for sure... no exceptions.
For those of you who think MLB will somehow rescue your video capabilities on opening day..... IF YOU CAN'T STREAM VIDEO DURING SPRING TRAINING, YOU WILL NOT BE ABLE TO STREAM VIDEO ON OPENING DAY!! I highly recommend editing your build.prop.
blek42 said:
PLEASE PRESS THE THANK BUTTON IF THIS HELPS YOU!
YES!! I got this to work last year by editing the build.prop file to make my HTC HD2 running android look like a Nexus S. I even had fun with it so the market reports my phone as an HTC Nexus S.
I downloaded At Bat 12 in Feb. and the spoof still worked.
I just upgraded my phone to an HTC Sensation XE. he video icon was hidden on my new phone because it too is not officially supported.
I edited the build.prop on my new phone similarly and like magic, At Bat 12 shows the video icon now.
Here's how to do it:
0. Go to system settings->applications and clear data for At Bat 12
1. Using an app like Root Explorer, navigate to system->build.prop
2. Make sure you have r/w access and long press build.prop file to open in text editor
3. Scan build.prop file and make:
ro.product.model=Nexus S
(there may be 2 ro.product.model lines that need to be changed
ro.product.manufacturer=HTC
NOTE: These are the most important lines to change. If these don't work by themselves you can also make:
ro.product.brand=HTC_wwe
ro.product.name=yakjuxw
ro.product.device=maguro
4. Save build.prop file and open again to verify that changes were made. If your changes are not there, check that you are in r/w mode and repeat from step 1.
5. restart your phone, open At Bat 12 and reenter your account details.
Let me know if this helps you. If it does not, let the forum know and we can work out the kinks. This method works for sure... no exceptions.
For those of you who think MLB will somehow rescue your video capabilities on opening day..... IF YOU CAN'T STREAM VIDEO DURING SPRING TRAINING, YOU WILL NOT BE ABLE TO STREAM VIDEO ON OPENING DAY!! I highly recommend editing your build.prop.
Click to expand...
Click to collapse
Was having the same issue, until I found this thread - I haven't been able to test it because there are no games playing atm, however I now have the TV/Video icon
Strange issue has popped up...
For some weird reason, Exchange has stopped syncing after modifying my build.prop
I'm going to delete/add the account to see if this fixes my issue, but be weary for those looking for a workaround.
EDIT:
After removing the Exchange account and trying to re-add it, i get a FC. I reverted back to my original build.prop until someone can find a workaround for both - having exchange working + video on MLB.TV
jaypeezee said:
Strange issue has popped up...
For some weird reason, Exchange has stopped syncing after modifying my build.prop
I'm going to delete/add the account to see if this fixes my issue, but be weary for those looking for a workaround.
EDIT:
After removing the Exchange account and trying to re-add it, i get a FC. I reverted back to my original build.prop until someone can find a workaround for both - having exchange working + video on MLB.TV
Click to expand...
Click to collapse
Exactly what lines did you change from the original build.prop that caused the Exchange errors? The MLB spoof can be done with a single line change for the model ID. This spoof has been known to cause issue with a limited number of apps.
Last year, I know some people ket 2-build.props on their phone and shuttled them in and out of the system folder as needed.... this is not the most optimal solution, but can work.
Let us know if you find anymore out on the topic.
blek42 said:
PLEASE PRESS THE THANK BUTTON IF THIS HELPS YOU!
YES!! I got this to work last year by editing the build.prop file to make my HTC HD2 running android look like a Nexus S. I even had fun with it so the market reports my phone as an HTC Nexus S.
I downloaded At Bat 12 in Feb. and the spoof still worked.
I just upgraded my phone to an HTC Sensation XE. he video icon was hidden on my new phone because it too is not officially supported.
I edited the build.prop on my new phone similarly and like magic, At Bat 12 shows the video icon now.
Here's how to do it:
0. Go to system settings->applications and clear data for At Bat 12
1. Using an app like Root Explorer, navigate to system->build.prop
2. Make sure you have r/w access and long press build.prop file to open in text editor
3. Scan build.prop file and make:
ro.product.model=Nexus S
(there may be 2 ro.product.model lines that need to be changed
ro.product.manufacturer=HTC
NOTE: These are the most important lines to change. If these don't work by themselves you can also make:
---OPTIONAL---
ro.product.brand=HTC_wwe
ro.product.name=yakjuxw
ro.product.device=maguro
4. Save build.prop file and open again to verify that changes were made. If your changes are not there, check that you are in r/w mode and repeat from step 1.
5. restart your phone, open At Bat 12 and reenter your account details.
Let me know if this helps you. If it does not, let the forum know and we can work out the kinks. This method works for sure... no exceptions.
For those of you who think MLB will somehow rescue your video capabilities on opening day..... IF YOU CAN'T STREAM VIDEO DURING SPRING TRAINING, YOU WILL NOT BE ABLE TO STREAM VIDEO ON OPENING DAY!! I highly recommend editing your build.prop.
Click to expand...
Click to collapse
I'm on an international Samsung Galaxy S2 GT-I9100
I only changed ro.product.model from GT-I9100 to SGH-T989 and the TV icon is now available.
I'll test the streaming tonight.
actually, video won't load, circle just spins forever, and upon reboot, it reverts back and I can't get video..
---------- Post added at 12:08 PM ---------- Previous post was at 11:58 AM ----------
dag16 said:
can't get it to work with nook color. I did the full Nexus S, no luck. tried the build.prop settings for the Xoom (which is a supported tablet), no luck. even uninstalled and reinstalled mlb lite in case something wasn't erasing properly, but no luck.
Any suggestions?
NM: got it working!!
Thanks!!
Click to expand...
Click to collapse
****novic said:
I'm on an international Samsung Galaxy S2 GT-I9100
I only changed ro.product.model from GT-I9100 to SGH-T989 and the TV icon is now available.
I'll test the streaming tonight.
Click to expand...
Click to collapse
Using ro.product.model=SGH-T989 on the Galaxy S2 GT-I9100 works beautifully.
I can watch the Tigers - Rays game.
Good news, guys.
MLB heard us, and now the GT-7000N is a supported device.
Already watched a game from my Red Sox yesterday, picture quality is great over Wifi.
Thanks for everyone who contacted them and made this happen.
For those changing lcd density you have to re-apply your edits after each rom/nightly flash. This method prevents that by overriding lcd density by using a local.prop file in /data.
1) Restore stock lcd density in build.prop: either undo the manual edits you did, or reflash your rom .zip to restore the build.prop to stock
2) Get one of these files based on the density you liked to use: lcd-density-120 or lcd-density-132
3) Rename it to "local.prop" and save it in /data (the root of the /data folder) - if you're on your touchpad then use any file manager to do this, or download to pc and adb push to /data
4) Reboot
This should override the 160 lcd density in /system/build.prop and it will survive rom flashes and incremental updates with goo manager for my nightlies (until you wipe /data obviously). Of course you can reverse the changes by simply deleting the file and rebooting.
You are welcome to try to add other mods using this method but not all will work, and for some reason not all apps/games read local.prop.
The files I posted just contain
"qemu.sf.lcd_density=132" which overrides "ro.sf.lcd_density=132" in /system/build.prop.
You can reply to this thread with other mods that you found to be working.
nice! THanks!
thanks!
has anyone gotten the latest chrome to work work on non-standard dpi's though? Considering it is my most used app, it kinda stopped me from using a dpi other than 160.
hockey4life0099 said:
thanks!
has anyone gotten the latest chrome to work work on non-standard dpi's though? Considering it is my most used app, it kinda stopped me from using a dpi other than 160.
Click to expand...
Click to collapse
Didn't even know that's what the problem was. Dissapointing since 160 dpi make me feel like I'm holding a large phone
Sent from my DROID3 using Tapatalk 2
This is a nice mod, thanks.
murso74 said:
Didn't even know that's what the problem was. Dissapointing since 160 dpi make me feel like I'm holding a large phone
Sent from my DROID3 using Tapatalk 2
Click to expand...
Click to collapse
the iPad2 has actually the same resolution but noone ever mentioned it.
it's awesome how the resolution actually changes but causes a lot of different problems with i.e. folders.
murso74 said:
Didn't even know that's what the problem was. Dissapointing since 160 dpi make me feel like I'm holding a large phone
Sent from my DROID3 using Tapatalk 2
Click to expand...
Click to collapse
yeah, so ive been stuck on 160 for a week now and it's not as bad as i thought it would be. If there is ever a fix id be happy to try it though. Not sure why one version it would work great but on the next it would force close. Maybe the next official update will solve our problems.
Thanks, this definitely saves some time and comes in handy!
Works as it should. I just wish 132 and 120 didn't distort much of the cm9 interface.
Does this work for any build prop entry? I would like to override a ro.ril setting....would I just use qemu.ril, and how can I verify it's working?