Hi folks.
I would appreciate a little help with a problem I have.
I rooted and installed Slimbean (240 dpi)? plus formula84 gapps from the stock T Mobile junk. I have an odd issue when checking 'my apps' within google play which says 'Your device isn't compatible with this version.
I have tried to clear the application cache/data for play within settings and restarting.
Also, the camera seems to keep looking for external storage which is a little odd?
I would appreciate any advice immensely.
Cheers all.
Forgot to mention, Ive changed the dpi manually to 240 and ran through the general UI instructions after changing the DPI but still get the problem. Boo!
L-L said:
Forgot to mention, Ive changed the dpi manually to 240 and ran through the general UI instructions after changing the DPI but still get the problem. Boo!
Click to expand...
Click to collapse
Had the same problem on first build of slimbean as well. I had to repeat the steps involving changing the DPI several times before I had success with play. The latest build of slimbean should already have DPI set to 240 and since that build ,I never had a problem. I never messed with DPI on latest build.
jrleathers said:
Had the same problem on first build of slimbean as well. I had to repeat the steps involving changing the DPI several times before I had success with play. The latest build of slimbean should already have DPI set to 240 and since that build ,I never had a problem. I never messed with DPI on latest build.
Click to expand...
Click to collapse
Thanks for replying. I thought I had the latest version. After a few goes of the same process you mentioned I managed to sort it.
Yeah, it can be a pain to get working properly. The only mirror for the 240DPI build isn't working, so the other 2 links are for the 182DPI version. Otherwise, they are exactly the same. Before flashing, you could edit the build.prop to reflect the change, and it'll make it easier for the Play Store to work right off the bat.
Bloodflame said:
Yeah, it can be a pain to get working properly. The only mirror for the 240DPI build isn't working, so the other 2 links are for the 182DPI version. Otherwise, they are exactly the same. Before flashing, you could edit the build.prop to reflect the change, and it'll make it easier for the Play Store to work right off the bat.
Click to expand...
Click to collapse
Never edited build prop before but I guess I could look into it just so I know how for future reference. I'm sure its simple. Probly just open the build.prop and find where the DPI numbers are and change them?
jrleathers said:
Never edited build prop before but I guess I could look into it just so I know how for future reference. I'm sure its simple. Probly just open the build.prop and find where the DPI numbers are and change them?
Click to expand...
Click to collapse
That is exactly how to do it, or just use ROM toolbox, there is a section for build prop edits, or you can do it before you even flash the ROM. In build prop you can also edit some stuff to get an amazing benchmark, but no help to the actual performance, so kinda useless( its something with frame rates)
Sent from my Nexus 7 using xda app-developers app
Related
First SimCity wouldn't download SD data. I finally obtained the SD data and now it closes after the second splash screen. Anyone know the cause? I'm thinking maybe dpi (currently using 120).
luke1987 said:
First SimCity wouldn't download SD data. I finally obtained the SD data and now it closes after the second splash screen. Anyone know the cause? I'm thinking maybe dpi (currently using 120).
Click to expand...
Click to collapse
I'm running it on my TP right now @ 160 DPI. It's the HD version, fwiw. Try changing up your DPI, that very well could be your issue.
Switched up my dpi and it didn't help. Atleast I know it's possible. What rom are you running? Thinking about trying that statusbar mod. Could be I got the wrong SD data, but I've tried 2 different sources with same result. One even stated for adreno
Sent from my SGH-T989 using xda premium
luke1987 said:
Switched up my dpi and it didn't help. Atleast I know it's possible. What rom are you running? Thinking about trying that statusbar mod. Could be I got the wrong SD data, but I've tried 2 different sources with same result. One even stated for adreno
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I'm running AOKP, but I was able to play it on CM9 A2 nightly too. Is it the HD version or the regular version that you're trying to play? Mine runs fine w/o the statusbar tweak, too.
I too have been unable to get the SD files to download. I get an error message referring me to go to some customer support page that doesn't exist.
Can you point me to the link that you got the files from. I'll try downloading it tonight...
running CM9 A2
PMs sent. Check your inbox guys.
I can't get the files downloaded. It says NaN on the window and doesn't move... any ideas?
Sent from my cm_tenderloin using XDA
So I have solved the data file download problem by sideloading it from my EVO...
Now it force closes after the second splash, the green EA screen.
I am using cm9, 160dpi and the supreme mods rohan 1.3... other than that, its stock.
I tried changing my build prop to like a Galaxy S2, but then I changed it back.
Any suggestions?
Thanks!
Sent from my SGH-T989 using Tapatalk
kr1mson said:
So I have solved the data file download problem by sideloading it from my EVO...
Now it force closes after the second splash, the green EA screen.
I am using cm9, 160dpi and the supreme mods rohan 1.3... other than that, its stock.
I tried changing my build prop to like a Galaxy S2, but then I changed it back.
Any suggestions?
Thanks!
Click to expand...
Click to collapse
Did you get this working? I'm stuck at NaN on attempting downloading files.
After a great deal of mucking around, I got it working using my phone to install the game, and then using a titanium backup from the sdcard... and then copying the /data folder to the sdcard... it was version .12 or something, and then it worked for a short while until the app updated to .13 and it broke again...
I gave up... even when it worked, it was zoomed in and looked dumb... EA has my $ and thats all they care about at this point.
PATCH NO LONGER NEEDED!
This post used to discuss a patch I made to show the Navigation Keys in Phone GUI mode. I am happy to announce that the patch is no longer needed.
In CM9 the Phone GUI is activated anytime you set the lcd density to anything higher than 160 dpi. With the Nook Color when you go to the Phone GUI the navigation keys are suppressed.
There is a method to activate the Navigation Bar that requires no patches or zip flashes. Just add the two lines below to your local.prop file in /data. I recommend using local.prop instead of build.prop so that it is not necessary to re-edit the file after each flash of a new ROM. If you do not have this file, create an empty txt file and put these two lines in it:
qemu.sf.lcd_density=240
qemu.hw.mainkeys=0
The first line tells your system to change lcd density to put it in phone gui. You can change the 240 number to any number above 160 and the phone gui will be displayed.
The second line tells your system that your hardware has no physical keys and enables the soft key navigation bar.
Reboot.
If you want to return to 160 dpi and the tablet gui, just delete or comment out the two lines above and reboot.
Also CM has added the ability to customize the navigation bar. Go to settings, system, navigation bar and it will tell you how to do it. You can move the buttons around, add buttons, change how they perform, etc.
5-28-2012 is the last day I will be making patches.
No-moar zips! Yay!
Edit (6-24): Removed last patch. Too many users will still downloading it and it does not work properly with the current nightlies.
Removed screenshots
The board lists the latest version as only being a few bytes compared to the other earlier versions of this, is this a sign of a bad upload?
Will be giving the second to last version a try to see if this is what I hope it will be.. Thanks!
Sent from my NookColor using Tapatalk
bornagainpenguin said:
The board lists the latest version as only being a few bytes compared to the other earlier versions of this, is this a sign of a bad upload?
Will be giving the second to last version a try to see if this is what I hope it will be.. Thanks!
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
I still see 4.1MB as the size of rev 11, which is the latest.
Okay, that's screwy. On my nook it said it was only a few bytes, but now on my phone it is listing the same size as the others. Sorry for wasting your time.
Oh, a quick question while I have your attention --is there any way to get the two status layout but with a lower dpi (160)? Or are we stuck choosing between phone and tablet interface if we want more screen space?
Sent from my LG-VM670 using Tapatalk
bornagainpenguin said:
Oh, a quick question while I have your attention --is there any way to get the two status layout but with a lower dpi (160)? Or are we stuck choosing between phone and tablet interface if we want more screen space?
Click to expand...
Click to collapse
Not sure what you mean by two status layout. Do you mean status at top and navigation on bottom?
160 always gives you the tablet layout with the status bar at the bottom, with the battery and time, etc there. You can use other launchers that allow you to modify such things as icon grid layout, etc, but the full status bar remains at the bottom.
If you set anything above 160 (180, for example), it goes to phone mode with the status bar at the top, and if you use my patch, the navigation bar will be at the bottom. You can change the density to anything above 160 and my patch will work. I just chose 240 because it is what I like and gives the most market compatibility. After applying my patch, just change the value in build.prop in /system (ro.sf.lcd_density=).
Yeah, that's what I meant. I will probably give 180dpi a try next time I use the nightlies. Going to mess around with CM7.2 Kang and see how it goes. Thanks for everything, I really hope your patch is made a default option once CM9 goes stable.
Sent from my LG-VM670 using Tapatalk
Could you please check the last file again? This one: update-softkey-240dpi-4-17-Rev13.zip Thanks.
I can see it to be the same size as the others, but when I try to download it all I get is an html 404 page. update-softkey-240dpi-4-15-Rev12.zip downloaded just fine.
--bornagainpenguin
bornagainpenguin said:
Could you please check the last file again? This one: update-softkey-240dpi-4-17-Rev13.zip Thanks.
I can see it to be the same size as the others, but when I try to download it all I get is an html 404 page. update-softkey-240dpi-4-15-Rev12.zip downloaded just fine.
--bornagainpenguin
Click to expand...
Click to collapse
It downloaded fine for me just now and 23 others have downloaded it.
Sent from my Nook Color running ICS and Tapatalk
I'm also not able to download a complete Rev13. I just get a file with a length of 554. I was able to get Rev12, but it's not working with the latest builds. Thanks for all your help on this!
Sudonym said:
I'm also not able to download a complete Rev13. I just get a file with a length of 554. I was able to get Rev12, but it's not working with the latest builds. Thanks for all your help on this!
Click to expand...
Click to collapse
The old versions do not work with the latest build, that's why I updated it. I just uploaded it again. Try now.
leapinlar said:
It downloaded fine for me just now and 23 others have downloaded it.
Sent from my Nook Color running ICS and Tapatalk
Click to expand...
Click to collapse
At least ten of those were mine. I was out and about last night and yesterday morning so I tried at different places and times before asking about it. I didn't want a repeat of last time where I asked and it was fine later that day. I appreciate the effort you guys put into this kind of stuff and the last thing I want to be is a bother.
leapinlar said:
The old versions do not work with the latest build, that's why I updated it. I just uploaded it again. Try now.
Click to expand...
Click to collapse
Just downloaded it on my phone and it looked like a complete package! Thanks!
update: how long is it supposed to take on reboot to apply? I'm stuck in reboot for a while now and starting to worry...
Sent from my LG-VM670 using Tapatalk
Okay. This is not working for me at all. I don't know how many times I've flashed now. All that happens is a message about Android updating my applications and then a return to the bootanimation that never ends. Not sure where things are going wrong. :banghead:
Wish I knew what I was doing to screw things up.
Sent from my LG-VM670 using Tapatalk
bornagainpenguin said:
Okay. This is not working for me at all. I don't know how many times I've flashed now. All that happens is a message about Android updating my applications and then a return to the bootanimation that never ends. Not sure where things are going wrong. :banghead:
Wish I knew what I was doing to screw things up.
Are you flashing the Rev13 patch with a 4/18 build? That combination works for me.
Click to expand...
Click to collapse
Sudonym said:
Are you flashing the Rev13 patch with a 4/18 build? That combination works for me.
Click to expand...
Click to collapse
I tried it with that build and I tried it with the one from yesterday. In both cases, I get a message about moving applications and a return to the bootanimation. Then ten or more minutes go by while the bootanimation spins with no feedback or signs of ever getting back into the GUI.
Really frustrating.
Sent from my NookColor using Tapatalk
Sorry if this is a stupid question, but will this work with Eyeballer's nightly builds (with/without opengl) or just with the one in the "work in progress" thread?
bornagainpenguin said:
I tried it with that build and I tried it with the one from yesterday. In both cases, I get a message about moving applications and a return to the bootanimation. Then ten or more minutes go by while the bootanimation spins with no feedback or signs of ever getting back into the GUI.
Really frustrating.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
The update to the CM repo broke the packages I offer in Botbrew, which happens when they significantly update the framework apps. Leap's patches always seem to break at he same time. The behavior your describing is what happens when you match a patch and a ROM that are incompatible. I know you have had problems with the downloader, (trust me you're not alone.) Just, one more time, flash the latest build and the latest patch together. The repo did not update again, I can promise you that. I bet with all the flashing and patching, you just did not patch the right build.
I have swapped in the old system apps maybe fifteen times over the last couple days, I know what that behavior is. And I use my own version of leapinlar's patch, so I know exactly how it works and what that behavior means. If it is working for others it will work for you if it has downloaded correctly.
slack04 said:
Sorry if this is a stupid question, but will this work with Eyeballer's nightly builds (with/without opengl) or just with the one in the "work in progress" thread?
Click to expand...
Click to collapse
The system apps work in any build for the Nook Color, opengl or not.
slack04 said:
Sorry if this is a stupid question, but will this work with Eyeballer's nightly builds (with/without opengl) or just with the one in the "work in progress" thread?
Click to expand...
Click to collapse
This patch will work with eyeballer's, Samiam303's or your home built version. All you have to make sure of is that you are using a version that is reasonably close in date to the build. As CM9 evolves and improves the base files that I am patching change and old versions of the patch will not work on that build. For instance, the 4-15 patch will no longer work on 4-17 or newer builds. I try to upload new versions when that happens.
I just tested eyeballer's 4-19 non-opengl build with the 4-17 patch and it still works.
@bornagainpenguin - are you flashing the build first and booting to that to be sure the base build download is ok before you flash my patch? If you do that it should say updating only 1 application after flashing mine. You might also try manually clearing your dalvik cache. That is what it is supposed to be doing automatically when it says updating applications.
Sounds like you are having download problems with with your devices so that might be the issue too.
Sent from my Nook Color running ICS and Tapatalk
leapinlar said:
@bornagainpenguin - are you flashing the build first and booting to that to be sure the base build download is ok before you flash my patch? If you do that it should say updating only 1 application after flashing mine. You might also try manually clearing your dalvik cache. That is what it is supposed to be doing automatically when it says updating applications.
Sounds like you are having download problems with with your devices so that might be the issue too.
Sent from my Nook Color running ICS and Tapatalk
Click to expand...
Click to collapse
I am making sure I boot up to a complete Android environment (beginning the setup part where they ask you which language and your google account, etc) before rebooting to recovery to install.
I just gave it another try using eyeballer's 4-19 opengl build and everything seemed to work right up to the point where I tried to set the DPI. Using Nook Color Odds and Ends results in no change. I then try LCD Resolution (Root) which results in an error on reboot:
Code:
Unfortunately, System UI has stopped.
I suppose I could just give up and accept the 240 DPI, but I really don't want my icons to be that big...
Back to CM7 with me I suppose....
--bornagainpenguin
bornagainpenguin said:
I am making sure I boot up to a complete Android environment (beginning the setup part where they ask you which language and your google account, etc) before rebooting to recovery to install.
I just gave it another try using eyeballer's 4-19 opengl build and everything seemed to work right up to the point where I tried to set the DPI. Using Nook Color Odds and Ends results in no change. I then try LCD Resolution (Root) which results in an error on reboot:
Code:
Unfortunately, System UI has stopped.
I suppose I could just give up and accept the 240 DPI, but I really don't want my icons to be that big...
Back to CM7 with me I suppose....
--bornagainpenguin
Click to expand...
Click to collapse
What were you trying to set the dpi to? The best way to set it is to edit the build.prop file in /system manually. Change the line ro.sf.lcd_density=240 to some other value above 160. That line does not exist there until you flash my patch. Also make sure there is not a density line in local.prop in /data. Some of those density changing apps try to set density there and if they do, that setting never gets overwritten in a flash and always overrides what is in build.prop.
Sent from my Nook Color running ICS and Tapatalk
leapinlar said:
What were you trying to set the dpi to?
Click to expand...
Click to collapse
180 DPI. Trying 160 DPI just means that I lose the phone GUI
leapinlar said:
The best way to set it is to edit the build.prop file in /system manually. Change the line ro.sf.lcd_density=240 to some other value above 160. That line does not exist there until you flash my patch.
Click to expand...
Click to collapse
I've never had great luck remembering the adb commands to push and pull files. I could probably try using root explorer to copy to the SDCard and do it on the netbook? Will look into this....
leapinlar said:
Also make sure there is not a density line in local.prop in /data. Some of those density changing apps try to set density there and if they do, that setting never gets overwritten in a flash and always overrides what is in build.prop.
Sent from my Nook Color running ICS and Tapatalk
Click to expand...
Click to collapse
Just checked that out and doesn't seem to be a factor. Thanks for bringing it up so I could eliminate it though.
Sent from my NookColor using Tapatalk
How can i make the phone run 145 or 140 dpi without phone apps fc? Any help would be great as you may get a rom release by me
I don't think this is possible.
Hmm i thought there would be a way to edit the apk to run those dpi's
Ive seen a rom running on a higher dpi so it IS possible.
One that works with our Ace (at least on CM7 vo-1 based ROMs) is LCD Density Modder
Try to set it in:
ro.sf.lcd_density in build.prop
I change mine using ROM toolbox pro.
Let me know if this worked
= ====== =
Edit:
I have been running at 140 since I posted and haven't noticed any difference at all
You need somethink like root explorer to get into your system folder, copy build.prop to your sdcard, open it up at your computer and then search for this:
ro.sf.lcd_density=[Your density]
For MDPI on 3,5" is 160 normal, but for you it may be like this:
ro.sf.lcd_density=150
or
ro.sf.lcd_density=145
Copy the saved file back to sd-card, do a backup of the old one, and put the ney one into the /system folder
Let me know if it helped
ok will try, but wouldnt that still make the phone and dialertab fc
I'm still on 140 and not one fc
121C4 said:
I'm still on 140 and not one fc
Click to expand...
Click to collapse
i changed it in build prop and still FC
When I used to use 140 DPI I actually had no problem with FC's, maybe I just never ran into such app that would FC because of the change of DPI.
However, I used the app "LCD Density" to change my DPI, it should probably have the same effect as manually modifying the script but you could give it a shot.
yeah well iv been trying to change it different ways, but im not sure if it can be done on stock rom
winxuser said:
i changed it in build prop and still FC
Click to expand...
Click to collapse
winxuser said:
yeah well iv been trying to change it different ways, but im not sure if it can be done on stock rom
Click to expand...
Click to collapse
can you do it or not? Which apps force close? Why bother with stock ROM? It sucks!
I'm still running at 140 and can't see any difference graphically but it feels like my battery its lasting longer and the ui is more responsive. Might be a placebo.
121C4 said:
can you do it or not? Which apps force close? Why bother with stock ROM? It sucks!
I'm still running at 140 and can't see any difference graphically but it feels like my battery its lasting longer and the ui is more responsive. Might be a placebo.
Click to expand...
Click to collapse
nope havent been able to do it,, why stock rom,, i was going to make a rom based on stock,,, its phone.apk and dialertab.apk that force close i havent had a problem with any other program....
What dpi should I my phone from build.prop . They recommend 480x800
ChunkFlip said:
What dpi should I my phone from build.prop . They recommend 480x800
Click to expand...
Click to collapse
Try setting 80, but games are usually unaffected by build.prop changes. So maybe it will work, maybe it won't.
Didn't work . You're right it doesn't work in games. Any ideea to make it work on our device?
ChunkFlip said:
Didn't work . You're right it doesn't work in games. Any ideea to make it work on our device?
Click to expand...
Click to collapse
PA ROM or PAC ROM will do the job...I never tested myself though but people do claim it works.
nishanty13 said:
PA ROM or PAC ROM will do the job...I never tested myself though but people do claim it works.
Click to expand...
Click to collapse
in PA or PAc, it works...i was allways set up Swype to be smaller, and it works...but not using it until they change the base, 3 months without update
tried that but the rom is unstable for me . Any app that could act like paranoid ?
Yeah there's one
Firstly install xposed installer
And then install xposed app settings
With The help of xposed app settings you can change dpi per app basis
But I don't know if it will run the game fine
And google for the apps
Hi all, I cannot understand why, but since a few days (perhaps after installing new Android Revolution), I have very, very small fonts.
Here is an example taken with "CID Getter".
Same thing with other apps.
Any help is appreciated.
I'm stock and have only this on a couple of apps that don't support 1080p properly. They were updated and now looks as expected.
Check if you have some option in settings for fonts or something. As it is a custom ROM, perhaps the dev implemented something like that.
No, nothing
I do notunderstand... can tou post a screenshot of CID Getter?
It's a very small app.
I do not know if the problem is only on my phone or on the app itself.
lmerega said:
No, nothing
I do notunderstand... can tou post a screenshot of CID Getter?
It's a very small app.
I do not know if the problem is only on my phone or on the app itself.
Click to expand...
Click to collapse
For this, you need to get in touch with the developer and see if he has any suggestions. When it comes to custom roms, the source is always the best place to start. Have you tried adjusting them through your settings?
kibmikey1 said:
For this, you need to get in touch with the developer and see if he has any suggestions. When it comes to custom roms, the source is always the best place to start. Have you tried adjusting them through your settings?
Click to expand...
Click to collapse
Note that Android Revolution is a stock rom with some improvements, but the core is stock.
I was wondering if any of you has installed cid getter on his phone and could verify if the screen is like mine to understand if it is only a problem of mine.
I do not have any setting different than a stock, so I cannot adjust font size in my apps
I had xposed framework.
Removed and now everything is ok.