I was getting a lot of FC's from youtube and I accidently uninstalled it from Titanium before backup.
Then I went to Market and it says app not compatible with device?
First I thought because I changed screen density but even after changing it back -- NO GO
Anyone have a workaround?
I have the player rooted. Tegrak Overclocked was working but now that doesn't either.
I tried editing the build prop to changing to GT-I9000 but that didn't seem to work either
What did you use to root it, and did you mess around with your Kernel?
Yes I noticed this as well went to download YouTube and its not there ( not compatible ). I wonder i it because i am running a custom ROM are you by any chance?
I cannot download some apps from the play store. It says your device is not compatiable. I know it is compatiable because i have seen others with the app on their note. I tried downloading the original car home (i did not like the voice stock samsung one) and samsung apps which doesnt even show up in the play store anymore.
My lcd density is still 320 havent changed it.
Im running rooted saurom with no changes to OC
circuit.007 said:
I cannot download some apps from the play store. It says your device is not compatiable. I know it is compatiable because i have seen others with the app on their note. I tried downloading the original car home (i did not like the voice stock samsung one) and samsung apps which doesnt even show up in the play store anymore.
My lcd density is still 320 havent changed it.
Im running rooted saurom with no changes to OC
Click to expand...
Click to collapse
I have had several issues like this.... you need to edit your "BUILD.PROP" file with Some type of file explorer / rom toolbox or something like that.
Several lines such as "RO.xxx.device" says i717 - Where it says SGH-i7171 you should change to "GT-N7000" which is the international version. This will fix that issue - also, use the search function, there is another thread with this info already.
BigBison420 said:
I have had several issues like this.... you need to edit your "BUILD.PROP" file with Some type of file explorer / rom toolbox or something like that.
Several lines such as "RO.xxx.device" says i717 - Where it says SGH-i7171 you should change to "GT-N7000" which is the international version. This will fix that issue - also, use the search function, there is another thread with this info already.
Click to expand...
Click to collapse
Oh okay I will try looking and searching for the build prop posts. I am new to rooting and modding. Can you tell me exactly what i need to do? Do i need to purchase root explorer for this? And I'am kind of worried that by switching to the gt-n700 build prop it will make other apps which work now incompatiable and i will be in the same situation again.
Okay so to try and fix it I re installed the new saurom rom xla2 rcvi and the atnt fix. I rebooted it and restored my apps and data through titanium backup. I am now going to do a nandroid backup. But i still cannot get sme apps from the play store still uncompatible. I thought the atnt fix would fix it because it removed the r from the build.prop. But it didnt.
could you link me to the posts where this was discussed because I could not find it. also could you tell me how to do this because i was just trying to find my build prop just so i would know where to find it and i couldnt.
I just dont understand why i cant download some apps like samsung apps, omnisketch these are made for the note? I tried restoring my samsung apps from my stock rom because i backed it up with titanium but when i restored it and tried to open it, it took me to the play store and said the app was not compatible.
Hi guys...
I have a problem here. I rooted my Samsung Galaxy Ace S5830 through superuser one click and installed an app called ninja-morph from the market. This app can extract the files of an apk and we can replace objects such as image icons, in the folders in order to make them look as we want to. What happened now was that I changed the icons of two of my system apps successfully - Browser & Gallery. Then I thought of changing the icon of settings app, I tried 2 do so but what happened was that it didn't change and it started force closing. Then I went on to the web and searched for many solutions and so I downloaded an apk, shifted it to my phone an tried to install it but it didn't install. After many tries and changes through ninja-morph too I couldn't do anything. Now the problem is that I can't use wifi 'cause it needs settings. I can't even download any alternative 2 use wifi 'cause it needs wifi. I can't to anything related to internet or settings now. And worse, I just Factory Data Reseted to try if anything can be solved, but no... I just deleted all my apps. One way is to reload the software. But is it safe to do it with a root? Because I can't un-root it. Please Help Me Out.
abhaynayar said:
Hi guys...
I have a problem here. I rooted my Samsung Galaxy Ace S5830 through superuser one click and installed an app called ninja-morph from the market. This app can extract the files of an apk and we can replace objects such as image icons, in the folders in order to make them look as we want to. What happened now was that I changed the icons of two of my system apps successfully - Browser & Gallery. Then I thought of changing the icon of settings app, I tried 2 do so but what happened was that it didn't change and it started force closing. Then I went on to the web and searched for many solutions and so I downloaded an apk, shifted it to my phone an tried to install it but it didn't install. After many tries and changes through ninja-morph too I couldn't do anything. Now the problem is that I can't use wifi 'cause it needs settings. I can't even download any alternative 2 use wifi 'cause it needs wifi. I can't to anything related to internet or settings now. And worse, I just Factory Data Reseted to try if anything can be solved, but no... I just deleted all my apps. One way is to reload the software. But is it safe to do it with a root? Because I can't un-root it. Please Help Me Out.
Click to expand...
Click to collapse
Which rom are you using?
Seems your settinga apk got corrupted. Your options are:
-extract the original settings apk from the rom you're using and place it in system/app (with a root Explorer), with rw-r-r permissions.
-reflash a complete rom (custom through cwm or stock trough Odin)
Also, make a habit of backing up your original stuff before modding.
tomb20 said:
Which rom are you using?
Click to expand...
Click to collapse
i used the stock 2.2.1, but now i have flashed and solved the problem.
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!
Hi everyone,
This is not a question for my cellphone but for my ebook reader running Android 4.2.2 (rooted). I recently updated my Onyx Reader C67ML Carta2 to the latest firmware, 1.8.2. It works fine but the apps that should be running on startup are not doing it anymore. I have to start them manually everytime. I was using them for battery saving and were working pretty well (Greenify, No-frills, BootManager, Barshortcuts...) I have tried to flash again firmware 1.8.1 and update to 1.8.2 but it didn't change anything. I also tried to move these apps to system/app or downloaded a few apps (Startup, Autostart,Tasker...) to automatically start them on boot but with the same result.
Any suggestions? I really want these apps to open on startup and keep the newest firmware that has some new cool features.
I guess it's a bug in the latest firmware.