Related
A lot of games in the android marketplace won't download because they say the NC is not compatible. What phone manufacturer and model could I put in my build.prop that would allow me to download a game that would play on the NC?
Thanks.
So i just got the NC. Rooted it with manualnooter, emmc CWM, CM7, and everything runs good! Now my market updated and i cant download certain apps! I found some help on the search button(yes, people do use it!) and i havent found anyway to solve my problems. Here are some of the solutions i have found and tried and havent worked!
http://forum.xda-developers.com/showthread.php?t=1232147
http://forum.xda-developers.com/showthread.php?t=877505&page=2
If i can go back to the old market i WILL do it! Dont care for new market at all!
903tex said:
So i just got the NC. Rooted it with manualnooter, emmc CWM, CM7, and everything runs good! Now my market updated and i cant download certain apps! I found some help on the search button(yes, people do use it!) and i havent found anyway to solve my problems. Here are some of the solutions i have found and tried and havent worked!
http://forum.xda-developers.com/showthread.php?t=1232147
http://forum.xda-developers.com/showthread.php?t=877505&page=2
If i can go back to the old market i WILL do it! Dont care for new market at all!
Click to expand...
Click to collapse
Edit your build.prop and change the screen density to 160.
I have the exact same issue and have tried all the "solutions" I have found, nothing so far helps.
I'm running of an SD, CM7 nightly from August 28, one of the later kernels.
Everything works fine except this #$%^$ market.
Ideas?
Since none of my apps seem to be affected by screen density I simply uninstalled the marker updater app and kept the old market. If you are already on the new market. Uninstall the updater app first and then go into the applications settings for the market and uninstall the last update. Clear the data and cache as well.
doncaruana said:
Edit your build.prop and change the screen density to 160.
Click to expand...
Click to collapse
Can you direct me to what needs to be changed in build.prop? Thanks.
There should be a line that says
Code:
qemu.sf.lcd_density=161
Just change the number to 160.
I did that, thought there might have been some other line to be edited there that they weren't mentioning. Thanks.
MadMikeSS said:
I did that, thought there might have been some other line to be edited there that they weren't mentioning. Thanks.
Click to expand...
Click to collapse
Start up the Terminal. Become Superuser by typing "su" and return.
Remount /system as read/write by typing:
mount -o remount,rw /system
Edit /system/build.prop and change qemu.sf.lcd_density=161 to be 160.
Then go to Applications, force-close Market and clear all its data (but do not uninstall).
Then reboot.
If this still did not work, search the Internet for the latest Google Apps zip from August, 2011. If you have Rom Manager it's the newest one listed under "Download ROM...Google Apps" window. It's even newer than what is offered on download sites that have Phiremod or CM 1.7 RC.
When Market first starts it might ask you to install a list of apps. Choose a couple of them. I've observed that Market will then automatically upgrade itself again when I do this. I've been using the newest Market app with the 160 DPI setting for about a week now and it has never stopped working. I suspect that it might be the newest Google Apps that fixes some of the magic.
Note that some things, like the on-screen keyboard, have letters that are too large due to this setting. It's really supposed to be set to 170 DPI but 160 DPI is the setting that makes the Market app work again.
patruns said:
Since none of my apps seem to be affected by screen density I simply uninstalled the marker updater app and kept the old market. If you are already on the new market. Uninstall the updater app first and then go into the applications settings for the market and uninstall the last update. Clear the data and cache as well.
Click to expand...
Click to collapse
I don't see how to uninstall the market updater. It doesn't have the option in "manage applications" to uninstall it, and it doesn't show up in astro. How can I get rid of it?
kat3k said:
I don't see how to uninstall the market updater. It doesn't have the option in "manage applications" to uninstall it, and it doesn't show up in astro. How can I get rid of it?
Click to expand...
Click to collapse
I used Titanium Back. It is free in the market.
patruns said:
I used Titanium Back. It is free in the market.
Click to expand...
Click to collapse
Thanks. I did finally see it there after I installed Root Explorer. Having access to everything on the NC, it makes me want to root my phone.
This is probably the same problem I have experienced.
Yesterday I install CM7 bootable to a new SD card I just bought. After everything installed, I found that several essential google apps, like maps, youtube, are not able to install. Market complains that my device is not compatible.
However, these apps run properly in my old SD card. The Market from the old card has been updated, and it seems it's working properly as well. I'll check the DPI setting on both card. I don't think they are different because I installed both card through the same build.
Question: how to clone the entire old card to my new card? They are from different brand, old Kingston and new Sandisk. I've used WinImage32 to clone the Kingston to the Sandisk, but it doesn't boot at all.
Intro: This is my first guide, so be nice.. This will give you access to every app on the Android Market. I have downloaded apps that were previously “incompatible” and almost ALL of the gameloft, popcap, EA, etc.. games run without FC, validate, and download their additional data without failure for MY device thus far. It will revert after a restart, but its great to get what you want without having to do TB backup/restores over and over again for stuff you forget/buy later/etc...
If you have changes you would like to see to this guide, please comment!
------------------------------------------------------------------------
UPDATE: Feb 5th
I have been tweaking the build.prop for the last month or so, and have found some modifications that will boost performance and increase your battery life. It isn't an ungodly amount, but it is noticeable to me.
The build.prop is attached to the post now, instead of uploaded to an external site.
The old 2.2.6 market is attached for apps that show as "incompatible for your device".
------------------------------------------------------------------------
Disclaimer:
I take no responsibility for anything that happens to your device. Do this at your own risk.
YOU MUST BE RUNNING CM7!
YOU MUST HAVE ROOT!
I WILL NOT SUPPORT STOCK!
IF THIS WORKED, CLICK THANKS!!
Prerequisites:
CM7
Root
Root Explorer
Titanium Backup
Attached Files
Terminal Emulator
Lets do this thing:
First, the build.prop
We are going to replace the build.prop, so make a backup of the one you have.
open RE, and head over to /system/
copy that file and put it in a safe spot
Now we are going to put this modified build.prop in the location of the old one.
download this modified build.prop to your phone’s sd card:
open RE and copy the build.prop you just downloaded
navigate to /system/ again
click Mount R/W to give RE permissions to modify these files
paste the build.prop in the /system/ directory
if it asks to overwrite, go ahead and it will make a backup of the original called build.prop.bak
restart your device
Next, the Market
Now, we’re gonna get rid of, and replace some of the market data.
Open TB and delete “or freeze if you prefer” the following from the app list:
Market
This is optional! Do this if you are installing the old market and want it to not update until you restart.
Open up TE and run the following:
pm disable com.android.vending.updater
Now, we replace the Market that we had with the downloaded ones:
install and overwrite data “if it asks” for com.android.vending_2.2.6.apk
open your app drawer
open market “you should see the old version of the market”
HAVE FUN DOWNLOADING!!!
About the build.prop:
I had been screwing around with the build.prop for a while trying to find the best combination of fingerprints and such to put as to get the most out of the market. I discovered that the GT-P1000 “GTab” had the best results, so I changed the following:
Code:
ro.product.model=GT-P1000
ro.product.brand=Samsung
ro.build.description=GT-P1000-user 2.3.3 GINGERBREAD DXJPI release-keys
ro.build.fingerprint=samsung/GT-P1000/GT-P1000:2.3.3/GINGERBREAD/DXJPI:user/release-keys
I recently threw in the following performance modifications from various threads all over the interwebs. This combination works well for me. It is already in the new build.prop, so if you find a different setting to work better for you, post it and I will give it a try.
Code:
ro.kernel.android.checkjni=0
ro.ril.disable.power.collapse=1
video.accelerate.hw=1
debug.performance.tuning=1
windowsmgr.max_events_per_sec=150
ro.media.enc.jpeg.quality=100
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
Thank you so much I have been looking for a successful attempt at changing the build.prop file before I attempted it. I am very glad you shared your knowledge.
Good deal! Glad it worked out for you.
Yeah it worked perfectly..I did skip wiping my system cache and everything worked perfectly still..once again thank you so much. Just in time for the end of the gameloft sale..lol. I really love it!
Dude I love you..lol not only did I gain access with the old market, after I rebooted and killed the terminal, I now how access to all of the apps with the updated market..it appears to be to the perfect fix for the market, at least for me anyway. I will keep you posted if anything changes. I know I still have access to all Gameloft and EA games. Bravo sir. The only thing I did differently from you walk through is I didn't system wipe before install the old android market.
Sent from my GT-P1000 using xda premium
So your MUST have cm7 installed? I am rooted but didn't install that.
ASMAteMe said:
So your MUST have cm7 installed? I am rooted but didn't install that.
Click to expand...
Click to collapse
This may work on the stock rom, but I haven't tried it. If it works out for you then I will update the OP.
Thanks a ton!
This method worked perfectly. I figured that it might have something to do with the build.prop's device fingerprints but I just never had the patience to try it.
I actually just skipped the market part and followed the replacement of the build.prop with a reboot. I still got access to apps I previously weren't able to see before while using the new market app, however Im not sure if its the entire market. I also skipped the wipe of the /system and everything is working fine.
download?
where can i download the build.prop??
Poler166 said:
where can i download the build.prop??
Click to expand...
Click to collapse
it's in the .zip file in the OP
also, due to the responses of skipping clearing the cache through twrp, i have removed it from the OP. and added another little courtesy note below the "not supporting stock" note.
nfl46 said:
I am going to try this on the ICS rom tonight.
Click to expand...
Click to collapse
Awesome, let me know if it works!
Crash
whenever i try to get to the market it just crashes ... any suggestion ?
EDIT: never mind it works now Your epic
Poler166 said:
whenever i try to get to the market it just crashes ... any suggestion ?
Click to expand...
Click to collapse
Try clearing your market data and install the attached market again and let me know if it works.
enkode said:
Try clearing your market data and install the attached market again and let me know if it works.
Click to expand...
Click to collapse
Spoke to soon when ever i try to download an app from the market it force closes and said The application Market (process com.android.vending) has stopped unexpectedly.
lordsofletterbox said:
Dude I love you..lol not only did I gain access with the old market, after I rebooted and killed the terminal, I now how access to all of the apps with the updated market..it appears to be to the perfect fix for the market, at least for me anyway. I will keep you posted if anything changes. I know I still have access to all Gameloft and EA games. Bravo sir. The only thing I did differently from you walk through is I didn't system wipe before install the old android market.
Sent from my GT-P1000 using xda premium
Click to expand...
Click to collapse
Could you elaborate how you got access to the full updated market? I tried that, and I can't download anything from it.
Awesome. Gameloft's TinTin game now recognizes my Kindle as a 3D supported device.
Sent from my CM7 Kindle Fire
I just tried this and the only thing that i had to do is copy the build.prop to /system, rename old one to build.prop.bak, set permissions for new one, force stop and clear market data from manage applications, then reboot. Everything shows up and downloads with the new market.
Poler166 said:
Spoke to soon when ever i try to download an app from the market it force closes and said The application Market (process com.android.vending) has stopped unexpectedly.
Click to expand...
Click to collapse
This may seem a little out there, but go to titanium backup and longpress the market app and move it to a user app. Attempt to open it up then close it, clear your data from the application details and reinstall the app from the zip on the OP. Install the marketupdater.apk as well.
theholyfork said:
Could you elaborate how you got access to the full updated market? I tried that, and I can't download anything from it.
Click to expand...
Click to collapse
Don't let the other users methods confuse you. If you did everything in the OP, you shouldn't have any problems. If you did, be more specific and I will try to help. No offense.
enkode said:
Don't let the other users methods confuse you. If you did everything in the OP, you shouldn't have any problems. If you did, be more specific and I will try to help. No offense.
Click to expand...
Click to collapse
Don't worry, I'm pretty good with this stuff, but when he said he had full market access I wanted to know how he did it. I can confirm that it works though, I just had to replace the build.prop you provided, force stop the market, and clear the market data, then reboot, and I can see more apps in the new updated market!
Guys,
I following the Verygreen C7 SD Card install method to install CM7 on an 8GB SD Card and I'm using it with my Nook Color 1.4.2. Using the SD Card I'm able to run Gingerbread without any problems.
The one problem I've noticed is that some of the Apps in Google Play Store don't appear compatible. The Google Play Store reads the device as "BN Nook Color" and for some apps it says "This device is not compatible with this app" -- something like that.
I've seen threads where people have changed some property in their NC (I think bild.prop or something) that allows them to show their NC as something other then BN Nook Color, like Samsung Galaxy Tab or Nexus S or Motorola Xoom or something. I cannot find instructions to do this.
How exactly do you this? Will this allow me to pick up more Apps from the Google Play Store?
Thanks!!
Use the IMEI Generator in my sig... it will allow you to change device in build.prop for some of the most common.
DizzyDen said:
Use the IMEI Generator in my sig... it will allow you to change device in build.prop for some of the most common.
Click to expand...
Click to collapse
Excellent! I will definitely give this a shot. Thank you so much for replying.
DizzyDen said:
Use the IMEI Generator in my sig... it will allow you to change device in build.prop for some of the most common.
Click to expand...
Click to collapse
I downloaded your software, but I'm not quite sure I'm understanding exactly what I need to do and how to use it.
I do have a working USB ADB connection; and I really just want to make my NC appear as a Galaxy Tab (Which I see is in the list of devices) ... do you have instructions for a n00b on how to go about doing this?
Sorry for the lack of know-how. Thanks again.
Sorry if its too late, but try this app:
I used this on my Kindle Fire and it changed the build.prop to another device. Sadly, I can't seem to get Google Play to see it as a Nexus S...
Just today I noticed a bug in the IMEI Generator that causes it to not update build.prop when using in-place updates... that will be fixed shortly...
In the meantime if you want to make the change to build.prop it is really easy to do...
adb pull /system/build.prop
edit build.prop with notepad+ or something that will not convert it to dos/windows type of text... carriage return/line feeds get hosed if you use normal notepad
the lines you want to chage are:
for Samsung GalaxyS
ro.product.model=NC_CM7 (or SCH-I500 per manufacturer)
ro.product.device=GalaxyS
ro.product.manufacturer=Samsung
ro.build.description=passion-user 2.3.6 GRK39F 189904 release-keys
for Samsung Galaxy Tab
ro.product.model=NC_CM7 (or SPH-P100 per manufacturer)
ro.product.device=SPH-P100
ro.product.manufacturer=Samsung
ro.build.description=passion-user 2.3.6 GRK39F 189904 release-keys
After above edits...
adb shell busybox remount
adb push build.prop /system
reboot Nook and wait... initial boot takes a while.
The entries for the GalaxyS are what use with CM7 on my Nook... it registers as a Samsung GalaxyS model NC_CM7 in Google Play Store... the Galaxy Tab entries are compiled from user suggestions and information from my GalaxyS phone modified to what I think the Galaxy Tab would use.
Hopefully this information is helpful.
If anyone will provide me information regarding Nexus S in the thread in my signature to have devices add to IME Generator... I will GLADLY include it in the devices.dat file... a new one is going to be uploaded very soon.
DizzyDen said:
for Samsung Galaxy Tab
ro.product.model=NC_CM7 (or SPH-P100 per manufacturer)
ro.product.device=SPH-P100
ro.product.manufacturer=Samsung
ro.build.description=passion-user 2.3.6 GRK39F 189904 release-keys
Click to expand...
Click to collapse
Dizzy,
Thanks for the update; I had used your Generator to make my NC appear as Samsung Galaxy Tab ... which it does in the market. I did use the "in-place" update.
I went ahead & used adb pull to get my build.prop, but I noticed that in my build.prop I already have the EXACT same information as above (Samsung Galaxy Tab). That tells me that your Generator did indeed insert the correct information in build.prop ... since I didn't put it there manually. I didn't need to change or modify anything.
Unfortunately, my problem persists. There are many apps, especially Tablet apps, that still come up as "This app is incompatible with your SPH-P100 device". I'm not sure why!!
Thanks.
Is this to fool Market/Play Store, the app, or both?
Is this deception needed just to get Google to allow one to install the apps in question, or do the apps themselves need to be fooled when they are installed from their .apk files and/or when they run?
aarons510 said:
Is this deception needed just to get Google to allow one to install the apps in question, or do the apps themselves need to be fooled when they are installed from their .apk files and/or when they run?
Click to expand...
Click to collapse
I think the apk files will use build.prop to figure out what device they are running on. I remember using this method to get netflix working back in the day.
I just got the CM10 installed on an sd card using bokbokan's images. Everything works great. But the Kindle app thinks it is running on a phone and everything looks super big. I can change the text size and some options but I like the tablet UI much better. Nook app does the same.
So I got this app called LCD Density and tried changing mine from the default 240 to 300. The whole Android UI adjusted itself and looked better (smaller) but the Kindle app and the Nook app were unaffected.
1. Is there a way to put these apps into Tablet mode?
2. Is there a way to stick the new density across reboots using this app?
TIA.
yelloguy said:
I just got the CM10 installed on an sd card using bokbokan's images. Everything works great. But the Kindle app thinks it is running on a phone and everything looks super big. I can change the text size and some options but I like the tablet UI much better. Nook app does the same.
So I got this app called LCD Density and tried changing mine from the default 240 to 300. The whole Android UI adjusted itself and looked better (smaller) but the Kindle app and the Nook app were unaffected.
1. Is there a way to put these apps into Tablet mode?
2. Is there a way to stick the new density across reboots using this app?
TIA.
Click to expand...
Click to collapse
Don't use the LCD app. On CM10 it is ok to change /system without worrying about resetting your device. So go to /system and look for build.prop. Edit that file with your root file manager. There is a line that ends ...density=240. Change that to 300. But you will have to edit it every time you flash a new ROM. The way to get around that is to create a file in /data named local.prop. Put this line in it.
qemu.sf.lcd_density=300
That will not get overwritten in a rom flash.
The kindle and nook apps detect how they should display themselves based on lcd density and screen size. The only way to get them into tablet mode is to REDUCE density not raise it. So you need to make a choice, higher density and phone mode, or lower density and tablet mode.
Sent from my Nook HD+ Running CM10 on SD
That's it. The problem was the app -- it wasn't changing the density correctly. I just changed it to 160 in the system/build.prop and everything switched to the tablet mode. Kindle and the Nook app work so much better but the UI looks less usable. I changed the system font to Huge and that helped a little. Two more questions:
1. Do you know what is the minimum density where Android still thinks it is a tablet? Is it 180? 200? We already know it switches to phone mode at 240. Of course, I can experiment if I can't find out.
2. Does the Nook HD's native dpi matter at all? You know how the desktop LCD screens have a native mode resolution where everything looks sharp and non-native mode where it maps the OS pixels to native pixels and everything looks blurry? I am wondering if something like that is going on here and I will have to do some dpi -> dip math to find out what is best for the Nook HD.
Thanks again.
Edit: Googling revealed 213 is the magic number. Tried 210 but I still got phone ui. Next I tried 200 and got a tablet ui with everything nicely usable. For someone else, you might want to try 190 or 180.
create or modify files in root directory
leapinlar said:
Don't use the LCD app. On CM10 it is ok to change /system without worrying about resetting your device. So go to /system and look for build.prop. Edit that file with your root file manager. There is a line that ends ...density=240. Change that to 300. But you will have to edit it every time you flash a new ROM. The way to get around that is to create a file in /data named local.prop. Put this line in it.
qemu.sf.lcd_density=300
That will not get overwritten in a rom flash.
The kindle and nook apps detect how they should display themselves based on lcd density and screen size. The only way to get them into tablet mode is to REDUCE density not raise it. So you need to make a choice, higher density and phone mode, or lower density and tablet mode.
Sent from my Nook HD+ Running CM10 on SD
Click to expand...
Click to collapse
I am new to android OS, and I apologize for the following simple question: how do I gain access for creating and modifying a file in /data in my rooted Nook HDPlus (with the set of files and steps you provided. thank you.) I tried to use the Root Browser to create a file in /data for changing my lcd density, but each time I was denied access. Do I need to somehow log into my device as a superuser (how), or do I need to change the setting (how)? Thanks again for your time, expertise, and patience.
cool2know said:
I am new to android OS, and I apologize for the following simple question: how do I gain access for creating and modifying a file in /data in my rooted Nook HDPlus (with the set of files and steps you provided. thank you.) I tried to use the Root Browser to create a file in /data for changing my lcd density, but each time I was denied access. Do I need to somehow log into my device as a superuser (how), or do I need to change the setting (how)? Thanks again for your time, expertise, and patience.
Click to expand...
Click to collapse
Are you sure you are rooted? And when you started root browser the first time, did it ask for root access and did you grant it? Open the superuser app and see if it lists root browser as being granted superuser access. If it does not, go to settings, applications, my apps, root browser and clear the data for it. Then restart root browser and if really rooted it will ask for superuser access.
Sent from my Nook HD running CM10.1 on Hybrid SD
leapinlar said:
Are you sure you are rooted? And when you started root browser the first time, did it ask for root access and did you grant it? Open the superuser app and see if it lists root browser as being granted superuser access. If it does not, go to settings, applications, my apps, root browser and clear the data for it. Then restart root browser and if really rooted it will ask for superuser access.
Sent from my Nook HD running CM10.1 on Hybrid SD
Click to expand...
Click to collapse
Following the steps you outlined, it all worked out. My Nook HD+ now is in higher resolution. The Root Browser was not in the Superuser listing, somehow. Again, thanks for the help.