Hi,
I am facing a new problem with my android market updated version 3.4.4 .If I search an item in the market,it shows the result with the message that "your device isn't compatible with this item ". But if I download the same item from the developer's site ,it works without any problem.This thing happens for free apps even original Google apps like google goggles.As a result I could not able to update it regularly. Can anybody explain me please,why this thing is happening???
HTC Explorer,android 2.3.5
idhbar said:
Hi,
I am facing a new problem with my android market updated version 3.4.4 .If I search an item in the market,it shows the result with the message that "your device isn't compatible with this item ". But if I download the same item from the developer's site ,it works without any problem.This thing happens for free apps even original Google apps like google goggles.As a result I could not able to update it regularly. Can anybody explain me please,why this thing is happening???
HTC Explorer,android 2.3.5
Click to expand...
Click to collapse
Have you changed screen density, perhaps?
What about qqlauncher pro ,ez launcher ,tencent desktop and so many apps which are all running well in my set but not allowed to download it from market.
HTC Sense 3.5, Android 2.3.5
same as op. i have changed screen density and it's annoying not being able to download/update apps that work just fine
If you changed your LCD density recently, change your LCD density back to its original number and then clear the Market data...you should be able to install those apps then...and then you can change your LCD density back to what you had it set at.
you dont have to clear the market data but it does involve a reboot, install the app, then reboot again to set the desired density again.
very annoying and long winded
Its problbly the app on the app store dosent support your current device, and the app you got from the developers site was probably modified to work on you device..
Like some apps have been modded to work on qvga and hvga phones.
Change youe product details in system/build.prop if your phone is rooted and change to anu desired phone type as needed. Be carefull of it though,and make a backup of that file first. That always do the trick don't forget change back to it's original state once the app is installed.
Sent from my blek krupuk
lexobys said:
Change youe product details in system/build.prop if your phone is rooted and change to anu desired phone type as needed. Be carefull of it though,and make a backup of that file first. That always do the trick don't forget change back to it's original state once the app is installed.
Sent from my blek krupuk
Click to expand...
Click to collapse
So, are we sure that the DPI setting doesn't matter if you change the build.prop file correctly? Or do we need to do both?
Which items did you need to change, and, what do you think is the best current choice?
I followed directions I found in one thread and edited my build.prop file, didn't work [I'm using a rooted Nook Tablet]
I installed Eris market fix and problem resolved.
Can you provide the link for eris market fix ?
HTC Sense 3.5,Android 2.3.5
superlimau said:
I installed Eris market fix and problem resolved.
Click to expand...
Click to collapse
On the Evo3D, or on a Eris?
idhbar said:
Can you provide the link for eris market fix ?
HTC Sense 3.5,Android 2.3.5
Click to expand...
Click to collapse
Here man, Try this...
https://market.android.com/search?q=eris+market+fix
Eris market fix not working for my set.
HTC Sense 3.5,Android 2.3.5
LCD modder pro from the market includes a special market that fixes it
Sent from my ARCHOS 80G9 using xda premium
I got my solution here http://forum.xda-developers.com/showthread.php?t=1515021
Your Device Isn't Compatible With This Item
I gave my step-son my Galaxy S, and when he goes to the Market, it wont let him download, or update any applications. All it says is "your device isnt compatible with this item." The phone works, like it has service..its on a plan, and its connected to HIS gmail account, it just wont let him update any of the apps. is there anything i can do about it? maybe master reset it?
styndall said:
If you changed your LCD density recently, change your LCD density back to its original number and then clear the Market data...you should be able to install those apps then...and then you can change your LCD density back to what you had it set at.
Click to expand...
Click to collapse
. This worked great for me! Your a ROM saver . Thanks and I did hit the thanks button!
Related
I know that for streakdroid 1.9.1 and before, there's option in install.txt to enable the compatibility for gameloft games.
However, I've jump to DSC gingerbread. For now, I'm having problem with the compatibility with gameloft games..（my lcd density is 160) any idea how to fix this problem?
Thanks a lot guys ！！
Could you be more specific about encountered incompatibility?
Hmmm.. When I browse with phone, the apps couldn't be found thru the market. And if I browse from computer in the android Market, and it shows that the game is not compatible with ur device. The game is mentioned is Brothers in Arms 2. Besides that, for yesterday android market 10 cents promotion, only 9 apps are showing up for me, the one dint show is one of the gameloft game. I also tried to download the apk, and after I installed, it failed to download the data package, and said that the device is not compatible. Thanks for helping me solving the problem ya, and thanks
Have you tried using market enabler to fake mobile provider?
If this doesn't help, i'll look for another fingerprints.
I don't have it handy, but the fingerprint for a Nexus S allowed me to download Asphalt 6. I reverted back to the original though before I could test the game.
Found it!
In your build.prop, find the line that starts with ro.build.fingerprint= and replace it with this one:
ro.build.fingerprint=google/sojua/crespo:2.3.6/GRH78C/93600:user/release-keys
Reboot your phone and see if it works. Make sure you make a copy of your original build.prop though just in case.
You must be rooted to do this.
n0p & lordmorphous,
Thanks for the fast response for u guys, will try it later ^_^
Anyway, thanks u guys for the great DSC rom =)
you could try getting games from gameloft wap store??
Find out what version is compatible and download it
Someone said xperia x10 mini versions work??
I have had some luck with htc desire versions as well (just dont choose any samsungs)
older adreno phone versions should be compatible.. (reminds me I need to update my gaming thread asap)
Update:
I've tried both methods, results returned seem to be the same ><
Update 2: I think is the gameloft compatibility issue.. even installed the apk file, it still failed to download the data over wifi, mentioning that the game is not compatible with your device, ask for refund. Same happen to my fren's moto ..
I'm running DSC ROM and in order to get some apps (Sleepy Jack, Tetris Free) showing up in the Market, I changed the fingerprint to:
ro.build.description=3.06.405.1 CL150597 release-keys
ro.build.fingerprint=htc_wwe/htc_ace/ace:2.3.5/GRJ90/150597.1:user/release-keys
They were succesfully installed, so what are the reasons to change the build.prop back to the DSC default?
I think there's no reason Thank you for sharing this fingerprint.
_n0p_ said:
I think there's no reason Thank you for sharing this fingerprint.
Click to expand...
Click to collapse
Thank you for answering and off course a great ROM!
So the only thing is that the Android Market now thinks that my device is a HTC Desire HD.
FYI: In order to make the spoof fingerprint work, I also changed
ro.product.brand=htc_wwe
ro.product.name=htc_ace
ro.product.device=ace
ro.product.board=spade
ro.product.manufacturer=HTC
After editing the build.prop I've had to 'Clear data' from Market app and Google Services Framework, reboot into StreakMod to Clear cache partition, Wipe dalvik cache and Fix permissions.
Djezpur said:
I'm running DSC ROM and in order to get some apps (Sleepy Jack, Tetris Free) showing up in the Market, I changed the fingerprint to:
ro.build.description=3.06.405.1 CL150597 release-keys
ro.build.fingerprint=htc_wwe/htc_ace/ace:2.3.5/GRJ90/150597.1:user/release-keys
They were succesfully installed, so what are the reasons to change the build.prop back to the DSC default?
Click to expand...
Click to collapse
thanks ! u brighten up my days
This tweak will make the camera failed to work
It seems that since Google updated Market to Google Play, I can't access or install a bunch of apps that I want.
The two that bother me right now are 'Lookout Mobile Security' and 'Firefox for Android'. If I search Google Play, neither show up in search results. If I use the browser and go directly to either Firefox's or Lookout's site to install, I get redirected to Google Play and the Install button in both cases is grayed out and nothing happens.
And I'm very unhappy that I can no longer download the apks using my computer and side load/install it.
????????????
I'm on a standard Nook Color, with the newest stable release running in EMMC:
Android version: 2.3.7
Kernel version: 2.6.32.9
Mod version: CyanogenMod 7.1.0-encore
Build No: GWK74
Everything else works fine and I have no other problems or complaints.
Can someone give me some things to try and get this working???
(is this the correct forum for this type of problem??? or can someone please direct me to the right place?? I didn't want to post this to the development forum.)
Same problem here, with last build of Mirage.
I modified the build.prop file, identifying as HTC Vision.
Playstore (in desktop) now shows HTC Vision as my device.
But still no full access to market with my nook, I can't see gmail app, for example.
I tried again to change build.prop with Nexus S as device.
Playstore has not even noticed the change.
Any hint ?
filigi said:
Same problem here, with last build of Mirage.
I modified the build.prop file, identifying as HTC Vision.
Playstore (in desktop) now shows HTC Vision as my device.
But still no full access to market with my nook, I can't see gmail app, for example.
I tried again to change build.prop with Nexus S as device.
Playstore has not even noticed the change.
Any hint ?
Click to expand...
Click to collapse
I don't have your Rom, but never had problems with Nightly Cm7 or needed to change build.prop file.
Did you try again with flashing recommended gapps for your ROM?
Unleashed from my Revolutionized Desire HD
Yes, I flashed again gapps after having wiped cache and data, and restored stock build.prop.
Now market works again.
I think I lost full market access when I changed the resolution, using LCD resolution, though this app doesn't seem to change anything in build.prop.
Maybe the solution is there: http://forum.xda-developers.com/showthread.php?t=1580827
The market has always been weird on my Nook. It randomly decides to not allow me to install some apps one day, then will allow me to install the next. Not sure what the cause is either. Just says the device is not compatible.
filigi said:
Yes, I flashed again gapps after having wiped cache and data, and restored stock build.prop.
Now market works again.
I think I lost full market access when I changed the resolution, using LCD resolution, though this app doesn't seem to change anything in build.prop.
Maybe the solution is there: http://forum.xda-developers.com/showthread.php?t=1580827
Click to expand...
Click to collapse
Any report of a fix yet? My Nook has also weirded out after changing LCD resolution!
Taken from the samiam's old cm9 thread
If you notice that some apps are missing from the market, this may be due to the fact that these ICS builds for the nook do not include support for apps which request phone permissions. Although this ideally would be fixed by developers not requesting phone permissions for their app unless it absolutely needs to be phone-specific, you can also fix it by flashing the telephony-permissions-fix.zip file located in the misc folder. You will likely want to flash this file immediately after flashing your rom.
Click to expand...
Click to collapse
greenmuggy said:
Taken from the samiam's old cm9 thread
Click to expand...
Click to collapse
Helped with a few but not what I was hoping... bit it did help
Sent from my SPH-D700 using XDA
Anything other than the standard LCD densities will not allow access to some applications. There is a list somewhere that I had bookmarked, but must have deleted it. If you search for the densities that are standard (MDPI, HDPI, etc) and set it, it may help.
Yeah, these missing apps are most likely a result of a non-standard LCD Density. To fix this, you can install a hardcoded 160 dpi play store that does not run an LCD Density check. If for any other reasons you can't access apps (different country or whatever), this hardcoded play store will let you.
See the thread with DL links here: (http://forum.xda-developers.com/showthread.php?t=1551118)
Make a backup of your vending.apk in /system/app/, and then rename the hardcoded play store to vending.apk. Place the hardcoded vending.apk in system/app/, change permissions to rw-r--r--, and reboot. Should work right away. If not, follow the additional instructions in the link above.
I take no credit nor liability for the results of following these instructions. Make backups of every file you replace and you should be alright.
Hello,
Well, im not new to custom roms. I think im pretty experienced with it. But i found no solution for my Problem yet.
I tried many Roms for my Ace, but with some I have the problem, when I try to install an app, the Market says my device is not supported.
With other Roms it works perfectly.
For example:
I tried the Miracle Rom V2 based on CM7.2: Everything works Perfectly.
Now I tried Miracle Rom V3 based on CM7.2, too: For example Maps, Mail, SoundHound and many many other Apps are not Possible to install. "Not Supported".
Thank you for your help
try to replace it with another rom.....
Sent from my GT-S5830 using XDA
lol, thats not the answer id like to hear^^
there must be a reason for that problem. It isnt solved with just installing another rom
try another version for map etc
for me anything work perfect
i use miracle v3
Sent from my ACE
okay, you can download market, or gmail from market?
then it seems like its a problem of my installation..
Ill try to flash it again
moflolo said:
okay, you can download market, or gmail from market?
then it seems like its a problem of my installation..
Ill try to flash it again
Click to expand...
Click to collapse
yes i can
or u can search in other thread for map.apk (application)
sory for my english languange
sent from my phone ⢄
"hear what people say..respect other member bro"
yes of course i could.
But there are many many other Apps which doesnt work, where i cant download another version very easy.
For example "heise", its a german computer magazine. I cant download the app and i dont know where i can download it. It would be hard work to search for any app, i cant install, for other versions
Edit:
Success. A reinstallation of the rom solved it. Weird problem. Does anybody have an idea where it comes from?
2nd Edit:
Too early. Still problems..
Most problems on first install are commonly solved by applying wipes before and after installation.
Sent from my GT-S5830 using XDA
Im still having the same problems. But everytime i try with different Apps.
I tryed a full wipe, before and after flashing.
I even formatted everything before and after installation.
This thing is really annoying!
Problem is solved!
For anyone having the same problem:
I used a density modder to change the display resolution to 140. That makes the market to no-know the phone, because it has the wrong resolution.
Solution:
I bought "LCD Density Modder Pro" from Market to change the Density. Then I activated the option "Fix Market Compability Issues" which installs a modified Market.apk to make the market think the phone still has the resolution 160
I'm having same issue. All the apps on my phone say this is not compatible with your device!
Rooted my phone 2 days ago, everything else stock!
Hi,
I tried to change DPI through LCD density modder app to dpi 226 in my sgs2.
After that the phone dont boot-up and got stuck at yellow triangle screen
I can go to CMW mode but dnt have any backup in that.i flashed Cf root again to check if that work,but nothing happen
NOTE: it got bricked because of change in DPI.not because of flashing wrong kernel so Flashing kernel wont help me
What to do,please help me
Can you mount USB in CWM to change the kernel ?
Because some kernels, like Siyah (I THINK ! I don't use Siyah...) purpose to clear some folder including DPI section...
So you can try to take one of this kernels, flash one, and find this option...
I'm not sure, just a supposition
UlbaWan- said:
Can you mount USB in CWM to change the kernel ?
Because some kernels, like Siyah (I THINK ! I don't use Siyah...) purpose to clear some folder including DPI section...
So you can try to take one of this kernels, flash one, and find this option...
I'm not sure, just a supposition
Click to expand...
Click to collapse
Missed the part about it not being a kernel issue, did you?
hungryheart said:
Hi,
I tried to change DPI through LCD density modder app to dpi 226 in my sgs2.
After that the phone dont boot-up and got stuck at yellow triangle screen
I can go to CMW mode but dnt have any backup in that.i flashed Cf root again to check if that work,but nothing happen
NOTE: it got bricked because of change in DPI.not because of flashing wrong kernel so Flashing kernel wont help me
What to do,please help me
Click to expand...
Click to collapse
You should be able to connect to your computer in CWM recovery mode, and edit the dpi setting in your build.prop file.
failing that, worst case scenario, just copy a new rom to ya sd and flash it in cwm, a custom one
seriously, you got bitten my friend, next time, do a nandroid backup and backup ya efs folder, double protection, coz seriously if ya gonna mess with stuff like the build.prop then ya need a backup plan.
If you really want to alter the dpi, then check the lcd density changers on google play, theres a few, but i know a couple of them let you test the dpi out first to see if it works on ya phone, if it doesnt it reverts back.
ctomgee said:
You should be able to connect to your computer in CWM recovery mode, and edit the dpi setting in your build.prop file.
Click to expand...
Click to collapse
As above;
1. Download & instal Windows PC programs "Android Commander" and "NotePad++ "(not NotePad)
2. Boot into CWM Recovery
3. Connect to PC USB & allow/edit for any drivers to instal
4. Run Android Commander
5. Navigate to system/build.prop & copy to PC & edit ro.sf.lcd_density=240 with NotePad++. Check there are no entries added by the app (delete them if so) Save and exit
6. Replace build.prop with edited version
7. Exit program, connect USB and reboot
8. All else fails, wipe cache/Dalvik and reflash ROM.
Hope this helps
Edit: don't forget to remove/delete the LCD Modder app from data/app with Android Commander before rebooting, otherwise it may force your previous density changes and back to square one.
You can also extract the build.prop from your ROM download zip with 7Zip and use above method to replace it.
Sent from my GT-I9100 using xda premium
Thank you all for your help
when i flashed CF-ROOT,i didn't work,but when i flashed STOCK KERNEL,it worked
i saw the odin log,stock rom has factory image file which correct the DPI.i think so
Thanks for giving your precious time
I found this thread through google, so thought i might post my experiences for the next person that finds this the same way, maybe some of it will be relevant...
So i did the same thing with my galaxy Note: changed DPI with LCD density modder app, restarted and the phone wouldn't get past the white samsung screen.
I followed UpInTheAir's guide to step 7, but phone still wouldn't start. I hadn't made a backup of the EFS folder so i was getting pretty scared at this point as loading a new rom will wipe this folder and render the phone useless (as far as i understand)
I was reading elsewhere that the permissions need to be set to rw-r--r-- on the build.prop file, so i tried doing this with Android Commander with the phone in CWM recovery. Android Commander was spazzing out, error message when the program opens, constant "loading" bar going, but i just ignored all that. I went to /system/build.prop properties and tried to set the permissions to rw-r--r-- but after accepting that and going to properties again it hadn't updated the permissions.
I've never flashed a ROM before, or changed kernel, but i decided this might be a good time to learn.
I loaded franco.Kernel-r5 for galaxy Note (sorry if this is irrelevant in an S-II forum) but loading into CWM that is built into this kernel (i think it was a different version than i was using before) i was then able to update the permissions with Android Commander(tho it was still spazing out).
Restarted and BOOM she loaded. Understandably i was thanking God big time at that point
anyway, hopefully something in this mess of a post might come in useful to somebody , thanks for the good info UpInTheAir!
Hello, I had the same problem and had to re-flash the firmware.
I've seen on dpi changers comments on market that A LOT OF PEOPLE get the softbrick.
i want to change my dpi.
how am i supposed to do it ?
I can't believe my phone can't stand changing DPI.
Ive changed mine a few times by altering the build prop file but the icons were never centered properly. Eveything was smaller but moved towards top left of the screen. Since then i used Density Modder pro with no issues.
Sent from my GT-I9100 using xda app-developers app
I have the same problem but i cant even get into cwm recovet. what can i do?
"Unfortunatelly System UI has Stopped!"
Hello everyone!
I have a HUGE problem with my Galaxy S4 i9500 and I really need someone's help here... I changed the pixel density/screen resolution, with the "Density changer" from the "Pimp my rom" app (I'm root user) and I can't use my phone AT ALL(not even the status bar)!!. I can only access the Lock Screen and the Lock Screen shortcut icons(could because I tried formating the phone but nothing changed so now only lock screen)... Also lock screen is super small, because I think I clicked the 200dpi(I THINK) option.When I unlock the phone, to access to the UI the screen is total black and this 2 messages are being deplayed : "Unfortunatelly, System UI has stopped" and "Unfortunately,TouchWiz Home has stopped",I don't have CWM Recovery flashed. Please reply! :crying: HELP!
Yiannis Hadjittofis said:
Hello everyone!
I have a HUGE problem with my Galaxy S4 i9500 and I really need someone's help here... I changed the pixel density/screen resolution, with the "Density changer" from the "Pimp my rom" app (I'm root user) and I can't use my phone AT ALL(not even the status bar)!!. I can only access the Lock Screen and the Lock Screen shortcut icons(could because I tried formating the phone but nothing changed so now only lock screen)... Also lock screen is super small, because I think I clicked the 200dpi(I THINK) option.When I unlock the phone, to access to the UI the screen is total black and this 2 messages are being deplayed : "Unfortunatelly, System UI has stopped" and "Unfortunately,TouchWiz Home has stopped",I don't have CWM Recovery flashed. Please reply! :crying: HELP!
Click to expand...
Click to collapse
First of all you will get better answers if you asked in your device's relevant thread, TouchWiz Home usually doesn't take too well to dpi changes, you need to install a custom launcher app like apex or Nova, try installing one via adb, and then reboot and select your custom launcher as default when the system prompts you to select a launcher.
Sent from my GT-I9100 using xda app-developers app
Thanks for the reply
king_below_my_lord said:
First of all you will get better answers if you asked in your device's relevant thread, TouchWiz Home usually doesn't take too well to dpi changes, you need to install a custom launcher app like apex or Nova, try installing one via adb, and then reboot and select your custom launcher as default when the system prompts you to select a launcher.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your help!! My phone is ok now..
same issue
Having the same issue I'm using Asus memo pad smart 10. Stuck in the boot screen after I tried to change my LCD density through ROM toolbox. Been like that for days. Do I need to follow the same procedure?
Thx
If you can enter recovery then flash maybe some DPI changer or what
Sent from my GT-I9100 using xda app-developers app
can't use recovery when I try to, it gives me a android lying on its back with the message "error" managed to wipe data though, now I can boot it fully however when I get to my lock screen it says that UI launcher ASUS keyboard and audio wizard have all stopped
corrupted apps?
king_below_my_lord said:
First of all you will get better answers if you asked in your device's relevant thread, TouchWiz Home usually doesn't take too well to dpi changes, you need to install a custom launcher app like apex or Nova, try installing one via adb, and then reboot and select your custom launcher as default when the system prompts you to select a launcher.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
i have this issue two but i factory reset my tablet because that would fix it and now the setup doesn't work and i can't fix it and the only thing i can do is the recovery menu if that helps if you have some sort of solution please let me know
many thanks ben
Try resetting via adb
ben12345678901 said:
i have this issue two but i factory reset my tablet because that would fix it and now the setup doesn't work and i can't fix it and the only thing i can do is the recovery menu if that helps if you have some sort of solution please let me know
many thanks ben
Click to expand...
Click to collapse
Encountered the same error using screen shift (https://forum.xda-developers.com/android/apps-games/app-screen-shift-change-screen-t3138718) I may be too late but I hope It may help somebody
For JB 4.3 and above:
Code:
wm size reset
wm density reset
wm overscan reset
Below JB 4.3:
Code:
am display-size reset
am display-density reset
i have the same problem but with my rooted galaxy note 4, i used an app to change my dpi but i set it from 640 to 140 and now the phone doesnt do anything except show me "Unfortunately the system ui has stopped" and it doesnt even show any icons, just my wallpaper and the tiny little error,, i tried fixing it with adb commands but my pc isnt authorized to my phone and i dont have a way to authorize it but usb debugging was on but i dont thing that will help, what do i do???
3ryl said:
i have the same problem but with my rooted galaxy note 4, i used an app to change my dpi but i set it from 640 to 140 and now the phone doesnt do anything except show me "Unfortunately the system ui has stopped" and it doesnt even show any icons, just my wallpaper and the tiny little error,, i tried fixing it with adb commands but my pc isnt authorized to my phone and i dont have a way to authorize it but usb debugging was on but i dont thing that will help, what do i do???
Click to expand...
Click to collapse
Try booting your device into safe mode, it should boot without loading the app that you installed to modify dpi. If you successfully boot into safe mode, you can uninstall the app then reboot.
Sent from my LGL84VL using Tapatalk
here is situation:
1. I had rooted 1.4.2 with not blocked OTA and my NT updated to 1.4.3.
2. It is obvious that root and some apps stopped working and some of them even disappeared from the device (like WinAmp for example).
3. I rooted 1.4.3 with SDcard method and it looked like things are fine until I started to get my apps back.
4. I used FIREFOX as a main browser with 1.4.2 update and after registering at Play store on rooted 1.4.3 I read that FIREFOX is incompatible with my device!!! What the hell?
5. Also, my NT registered at Play as NEW device, not the old one as I had - so it seems my serial changed or something has changed in the build.prop or somewhere else in the identification part of device.
6. Besides, after root, i started installing apps and it seems Notification bar has some sort of glitches - it does not clear all the messages and keeps the last downloaded file in the list...
Can anyone point me how to fix incompatibility issue?
---------------
Now, second situation:
7. I reverted back to 1.4.2 with the img file from this post: http://forum.xda-developers.com/showthread.php?t=1663836
8. But the thing is that I want to try 1.4.3 again
9. I downloaded official update from B&N and put it onto the SDCard
10. It boots and progress bar starts to move but at some point (25% of bar) it shows me exclamation icon with '!' and says "Please restart your device and try again..."
What is this issue and how it can be fixed?
Thanks in advance.
Honestly, I have had similar issues with the play store and my Nook on 1.4.3 but if you want to block OTA updates more effectively, I have been told that the updater cannot run if you have CWM flashed rather than the stock recovery image. When I screwed my Tablet up I found that I couldn't get it to load the acclaim_update.zip or any update files until I reflashed the stock recovery image rather than CWM.
titanshadow said:
Honestly, I have had similar issues with the play store and my Nook on 1.4.3 but if you want to block OTA updates more effectively, I have been told that the updater cannot run if you have CWM flashed rather than the stock recovery image. When I screwed my Tablet up I found that I couldn't get it to load the acclaim_update.zip or any update files until I reflashed the stock recovery image rather than CWM.
Click to expand...
Click to collapse
Can you share the links or files that get your nook back to normal state?
I've been reading and reading a lot the forum but still miss something important. Step-by-step guide would be much appreciated, if possible.
I have found the same problem. When I run CM7 on the NT from an SD card, I have no app compatibility issues. But when I run from rooted stock 1.4.3, I get the app compatibility error. I even tried pasting the build.prop file from CM7 into 1.4.3 but that did not correct the problem. The same apps are coming up as not compatible. What else is the Market looking at to determine compatibility?
Nook Color
Eustace2 said:
I have found the same problem. When I run CM7 on the NT from an SD card, I have no app compatibility issues. But when I run from rooted stock 1.4.3, I get the app compatibility error. I even tried pasting the build.prop file from CM7 into 1.4.3 but that did not correct the problem. The same apps are coming up as not compatible. What else is the Market looking at to determine compatibility?
Click to expand...
Click to collapse
This was actually a fix for Nook Color... to modify the build.prop. If you copy/pasted the entire build.prop I would think it would work.
One other thing to do is
1.) manage google play
2.) clear data
3.) uninstall updates
4.) manage google market
5.) clear data
6.) manage google services framework
7.) clear data
8.) reboot
This didn't always work and I had to do this a couple time. Not sure if which step made a difference or what order but it eventually worked. And I could see as many apps as my Captivate (Galaxy I).
Anyway, again, this worked for Nook COLOR and not Tablet. Or at least I havent figured Table yet. If you figure it out. Let me know.
My recent attempt was to copy the build.prop from Nexus and I got black screen after start up. Now I had to unbrick my device and I'm back to square one.
Good luck.. Keep me posted!!!!
@rtabasco - Good plan, but it didn't work. Even when I uninstalled the update and just used the Market app. Looks like 1.4.3 may have changed something other than the build.prop file. I'll keep poking around. It would help if the Play Store would provide a little more detail about the compatibility issue.
This just gets even more strange...
Restored with 1.4.2 image from http://forum.xda-developers.com/showthread.php?t=1663836 and Google Play (after root with sdcard method) says "FIREFOX is incompatible..."
Also tried to restore with NT_stock_1.4.2_Ribbon_Root_B&N.zip from http://forum.xda-developers.com/showthread.php?t=1494367 and Google Play still says "FIREFOX is incompatible..." Besides 'Go Weather EX' is incompatible too - this is ridiculous.
Anyone has idea how to overcome this?
PepeladZ said:
This just gets even more strange...
Restored with 1.4.2 image from http://forum.xda-developers.com/showthread.php?t=1663836 and Google Play (after root with sdcard method) says "FIREFOX is incompatible..."
Also tried to restore with NT_stock_1.4.2_Ribbon_Root_B&N.zip from http://forum.xda-developers.com/showthread.php?t=1494367 and Google Play still says "FIREFOX is incompatible..." Besides 'Go Weather EX' is incompatible too - this is ridiculous.
Anyone has idea how to overcome this?
Click to expand...
Click to collapse
What is your DPI ? Do you have an easy ( free ) way to try 160 ? . The market is your friend.
old_fart said:
What is your DPI ? Do you have an easy ( free ) way to try 160 ? . The market is your friend.
Click to expand...
Click to collapse
I am set at 160 dpi and that didn't help.
old_fart said:
What is your DPI ? Do you have an easy ( free ) way to try 160 ?. The market is your friend.
Click to expand...
Click to collapse
You mean - can I access 'build.prop' and change DPI there to 160? I probably can, but why exactly 160?
Why not default "169.33333"? As I understand CM7 has '160'?
it took me less than a minute to find this one... please do more searching and reading... thank you !
http://www.youtube.com/watch?v=uKlO9gkmsKk
PepeladZ said:
You mean - can I access 'build.prop' and change DPI there to 160? I probably can, but why exactly 160?
Why not default "169.33333"? As I understand CM7 has '160'?
Click to expand...
Click to collapse
Apart from the issue we are discussing in this thread that we can't figure out, a lot of compatibility issues with a rooted NT could be eliminated by changing the screen DPI to 160 in the build.prop file. My guess is that most of the apps were written for phones with 800x480 displays (or other dimensions that are easy multiples of 800x480). Making that change had worked for me to get access to most apps I wanted until this most recent problem that has been caused by changes in 1.4.3 or in the Play Store, or both working together.
Eustace2 said:
Apart from the issue we are discussing in this thread that we can't figure out, a lot of compatibility issues with a rooted NT could be eliminated by changing the screen DPI to 160 in the build.prop file. My guess is that most of the apps were written for phones with 800x480 displays (or other dimensions that are easy multiples of 800x480). Making that change had worked for me to get access to most apps I wanted until this most recent problem that has been caused by changes in 1.4.3 or in the Play Store, or both working together.
Click to expand...
Click to collapse
Thanks for explanation. I looked in build.prop from CW7 and DPI there is set to 160. I will try and report if this solved at least firefox problem.
old_fart said:
it took me less than a minute to find this one... please do more searching and reading... thank you !
http://www.youtube.com/watch?v=uKlO9gkmsKk
Click to expand...
Click to collapse
Thank you for video, but I was not asking how to edit text document, but rather what this change will give me.
Well, BNs build.prop has separate settings for X and Y dimensions. Following the logic, it does not matter if DPI is set via one command or via two... Anyway, simply changing to 160 DPI and rebooting did not help me with firefox compatibility in play store as well as other apps that were noted to show incompatible.
Any other suggestions and ideas would be very much welcome!