Okay, so I've been updating each nightly ROM and have a small issue. I've gone back to RC1v2 and the issue seems to be there too, although I am now back on the latest nightly (from 11th August).
a lot of apps I have installed - lets take Facebook as a pretty bog standard example - don't show up in the "My Apps" part of the Market app. If I search for it, it says it is installed. If there was an update then it allows me to update it, but still refuses to show it in "My Apps".
Now, if I go to the web version of the Market, it tells me that Facebook is "incompatible with my T-Mobile MB525". Clearly it's lying.
I've tried clearing cache and data from the Market app - still no joy.
I've tried taking the ro.build.fingerprint line of a Defy running stock 2.2 - no luck.
Has anyone else had this problem?
How can I fix it?
Yes I always have this no matter which rom I have.
You can get it to show all apps after you update or download a new app on the market.
Sent from my MotoDefy.
Edit just tried it again amd it didn't work this time!
Edit 2 after clearing the cache (after downloading a new app from the market) it now shows all my apps.
sp8y said:
You can get it to show all apps after you update or download a new app on the market.
Click to expand...
Click to collapse
No - that's not helping. For example, I've just searched for "chess" on my phone's market app, found one and installed it. the app does not show in "My Apps", and nor do any other supposedly incompatible ones. Market on web shows installed, and yet incompatible, screen attached.
Right that's a different issue to what I was thinking.
I used to have something similar to this when I was originally on eclair & tried to download apps from the market on my laptop - said they were incompatible as they were for a more recent Android version.
Sorry can't help any further as I've not had the issue on CM7.
hmm - bizarrely I just installed the latest nightly (1116), and now all my market works again. I'm confused, but somewhat happier.
now, if I can just work out why my patcher isn't working to get transparency theming I'll be sorted...
simon211175 said:
and now all my market works again.
Click to expand...
Click to collapse
and now it doesn't. Clearly I'm doing something to cause this. Time for an investigation.
okay - the incompatibility comes when I try to rename the camera shutter sound. command I'm using is: mv camera_click.ogg camera_click.bak
Why would that cause this issue?
or apparently any command after mounting /system - at random. I give up.
In case anyone else IS following my ramblings here, I've changed ROM to WajkIUI, done nothing in the system folder, and still have incompatibility in the market.
Reloading a ROM was getting the market working - now not. The whole thing beats me.
gapps
Try flashing the latest gapps from here.
Another idea, try flashing a full nordic stock 2.2 sbf from scratch and applying CM7 again.
thanks - I'm already on the latest gapps.
I don't think flashing the sbf etc again would help, as like I've said - flashing a ROM usually fixes the problem, then I go and change stuff in /system (renaming the camera sound files, and uninstalling OI File Manager so I can get the later version in the market).
Custom dpi (lcd density) seems to cause the "incompatible" problem with the new market.
http://forum.xda-developers.com/showthread.php?t=1196417
Going back to 240 dpi and clearing market data makes everything work as it should.
You can then go back to your custom dpi, but most users are reporting the problem comes back after a while.
BenKranged said:
Custom dpi (lcd density) seems to cause the "incompatible" problem with the new market.
http://forum.xda-developers.com/showthread.php?t=1196417
Going back to 240 dpi and clearing market data makes everything work as it should.
You can then go back to your custom dpi, but most users are reporting the problem comes back after a while.
Click to expand...
Click to collapse
You're a star. That solved it. Thanks!
I had this issue also. The LCD density fix did nothing for me
i had to make changes to the build.prop file
below are the changes i made
original:
ro.build.description=umts_jordan-user 2.2.1 3.4.2-107_JDN-9 34.4.9 release-keys
ro.build.fingerprint=MOTO/jordan_tmo_us/umts_jordan/jordan:2.2.1/3.4.2-107_JDN-9/34.4.9:user/release-keys
replaced the above lines with:
ro.build.description=umts_jordan-user 2.2.1 3.4.2-107_JDN-9 34.4.9 release-keys
ro.build.fingerprint=MOTO/jordan_tmo_us/umts_jordan/jordan:2.2.1/3.4.2-107_JDN-9/34.4.9:user/release-key
these came from my stock froyo TMO ROM
am I blind, or did you really replace two lines with two identical lines?
I had a similar issue, but for some reason I have multiple accounts on for my market and the apps seem to get randomly assigned to another gmail account and will only show up when I go to that account.
I have not had any issues with the compatibility however, and I haven't flashed a new nightly since the end of Sept. but I am about to go with the first Defy stable build from CM so I guess we will see. I will make sure to back-up everything.
Hi I am using a GS2 T989 with a stock rom, with Darksides kernel, and I haven't done anything to the rom EXCEPT for change the LCD Density of the screen, and I already changed that back to 240 because I heard that changing the LCD Density could screw with some play store things.
My problem is when I go to download some apps, it says that my device is not compatible with that app. I wanna know how to fix this..
I already deleted cache and wiped the play store data via settings > applications, and it did nothing..
I am stuck, there are updates it isn't letting me get, and it's getting frustrating...
Yeah this issue has been going around. It's just the kernel.
Hello all,
I'm running into an issue when trying to change the build.prop to 240DPI. I used rom toolbox and a couple other LCD density modder apps from the play store. Each one causes my phone to get stuck at the Samsung logo, doing a cache wipe allows it to load to the "Android is updating" screen then once complete reboots and gets stuck again in boot. I am using a stock debloated rom by Geo411m. I also loaded up some 240DPI modded apps to play nicely with the new DPI but havent gotten to test it. I am using the stock touchwiz launcher, so could that be the issue?
just an update I installed Apex launcher and then removed defaults for the launcher. Set the DPI in Rom Toolbox and rebooted. I was able to successfully reboot this time. Only issue I have now is that I use the PIN unlock for the phone while crashes soon as you being entering your PIN. So looks like another system restore for me..... :crying:
forgot to mention I wiped cache and also fixed permissions.... now waiting on the restore to try it all again..
Strange...boot loops would happen to me on my Note 1 when I changed the DPI manually (like through root explorer) but when I used ROM toolbox it would work fine. If you want 240 dpi, I would suggest using DAGr8's hybrid ROM. I was running it at 240dpi with no problems. You also have to flash his multi dpi fix zip though because some of the stock apps won't be formatted properly.
Hello,
I'll try to keep it short.
Pretext:
LG G4, H815
Latest MM Build (I think 20g or something..it's the latest original stock software)
Rooted, Unlocked, XPosed, NO Android debugging enabled ( I'm an idiot )
Wanted to improve battery life, changed the resolution to 1080p via wm size 1080x1920.
-> Icons too big
Changed Density to 440 via wm density 440
Rebooted.
nothing works. Everything just crashes, cannot bring up LG Keyboard, process com.phone crashes constantly, cannot get into settings to activate Debugging, because it crashes. Basically every damn LG App crashes.
I can boot into TWRP without a problem.
I can boot into Android without a problem!
I cannot install Apps due to constant force closes of everything LG Related (even Settings)
I tried changing my build.prop and default.prop to
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
When I do that the whole thing bootloops...
Question: How can I reset density?
How can I FORCE enable Android debugging?
Hope it's not too long and greetings. All help appreciated ^^
Hi,
Is there any way to keep DPI changed after reboot? I tried with and without root and it reverts back to default after reboot
I've had the same issue. Custom DPI works on stock Android and Samsung phones, but won't stick on OxygenOS.