I wiped EVERYTHING and reflashed the ROM. It seemed to have work, but then I was at the default density. Once I used LCD Density to 220, the error happened again. It forces closes. Any help? CM7.1
mapheG2 said:
I wiped EVERYTHING and reflashed the ROM. It seemed to have work, but then I was at the default density. Once I used LCD Density to 220, the error happened again. It forces closes. Any help? CM7.1
Click to expand...
Click to collapse
It's my understanding that altering the density can breaks things, including applications... looks like you'll have to choose between your desired screen density or Wifi Calling app.
This sucks
not sure why you want to change this, on any LCD display the native resolution (and therefore LCD density) whether on a phone, computer, tablet or whatever, is always the clearest, sharpest and best looking!
The icons and text are just too big to my liking after trying LCD density. At 220, as opposed to 240, everything just looks nicer and there isn't noticeably a decrease in sharpness or clarity.
Open spare parts, enable compatibility mode, reboot. See if that fixes it.
^ Nope, I tried that before. That doesn't help. Thanks for the suggestion though!
mapheG2 said:
^ Nope, I tried that before. That doesn't help. Thanks for the suggestion though!
Click to expand...
Click to collapse
Show me a logcat!
Related
Hi
When I set the lcd density from 240 to 200, everything looks great, except the notification bar. The icons are very fuzzy and blurred, maybe CM7 got some problems with scaling them.
Someone got a solution or did someone discover the same problem?
shyv said:
Hi
When I set the lcd density from 240 to 200, everything looks great, except the notification bar. The icons are very fuzzy and blurred, maybe CM7 got some problems with scaling them.
Someone got a solution or did someone discover the same problem?
Click to expand...
Click to collapse
Running 200 here on cm 7 with no problems
shyv said:
Hi
When I set the lcd density from 240 to 200, everything looks great, except the notification bar. The icons are very fuzzy and blurred, maybe CM7 got some problems with scaling them.
Someone got a solution or did someone discover the same problem?
Click to expand...
Click to collapse
In the build.prop, next to the line qemu.sf.lcd_density=200, there's a command on something called debug.fb.rgb565=0, try deleting it.. i remember last time, when i haven't delete it, causes me some graphical issues.
SAPPH1RE said:
In the build.prop, next to the line qemu.sf.lcd_density=200, there's a command on something called debug.fb.rgb565=0, try deleting it.. i remember last time, when i haven't delete it, causes me some graphical issues.
Click to expand...
Click to collapse
well, I just tried it with having this line deleted. My phone got stuck in bootloop then :/
(Note: I had to push the build.prop with ADB on my phone, first I tried to do it on my phone with RootExplorer, I dont know why it didnt work then. I could change the file, but after reboot it was set back to normal again.)
Edit: OK maybe I just made something wrong, I did it again with the RootExplorer method, and the line "debug.fb.rgb565=0" is now gone, but i left the space there. Still no improvements, density is on 200 now Might it be CM7 that I'm using?
shyv said:
well, I just tried it with having this line deleted. My phone got stuck in bootloop then :/
(Note: I had to push the build.prop with ADB on my phone, first I tried to do it on my phone with RootExplorer, I dont know why it didnt work then. I could change the file, but after reboot it was set back to normal again.)
Edit: OK maybe I just made something wrong, I did it again with the RootExplorer method, and the line "debug.fb.rgb565=0" is now gone, but i left the space there. Still no improvements, density is on 200 now Might it be CM7 that I'm using?
Click to expand...
Click to collapse
Which CM7 did you use? Mine on signature, works great all the time.. Well, when i remember the first time i tinkering with lcd density, i tried 160 instead.. The font was so small, my homescreen looks empty enough.. Looks good, but i had some horizontal line on menu.. Increase the lcd density to 200 resolve the problem while still maintaining to look good.. No fuzzy or blurred..
Maybe yours it's no compatible to 200 like mine on 160.. Maybe the hardware itself, i don't know.. Try 210, or 220..
edit: Could u post the pic of the aforementioned prob?
I am using CM7 build #25. The launcher and apps are okie except gameloft games where they don't show in fullscreen mode :| is there any walkaround for them?
lpachuong said:
I am using CM7 build #25. The launcher and apps are okie except gameloft games where they don't show in fullscreen mode :| is there any walkaround for them?
Click to expand...
Click to collapse
Open spare parts apps (if you don't have, try searching the market), untick compatiblity mode, and reboots.. That should fix any app that didn't run fullscreen..
SAPPH1RE said:
Which CM7 did you use? Mine on signature, works great all the time.. Well, when i remember the first time i tinkering with lcd density, i tried 160 instead.. The font was so small, my homescreen looks empty enough.. Looks good, but i had some horizontal line on menu.. Increase the lcd density to 200 resolve the problem while still maintaining to look good.. No fuzzy or blurred..
Maybe yours it's no compatible to 200 like mine on 160.. Maybe the hardware itself, i don't know.. Try 210, or 220..
edit: Could u post the pic of the aforementioned prob?
Click to expand...
Click to collapse
It seems like my device is just compatible to 240 dpi, my phone is not even trying to resize that stuff, the lower I set the dpi the more it gets "unclear".
(The funny thing is, that on the stock rom, everything looks very nice and small. must be something related to the whole roms)
shyv said:
It seems like my device is just compatible to 240 dpi, my phone is not even trying to resize that stuff, the lower I set the dpi the more it gets "unclear".
(The funny thing is, that on the stock rom, everything looks very nice and small. must be something related to the whole roms)
Click to expand...
Click to collapse
Hmm, weird.. Try flashing other CM7..
SAPPH1RE said:
Open spare parts apps (if you don't have, try searching the market), untick compatiblity mode, and reboots.. That should fix any app that didn't run fullscreen..
Click to expand...
Click to collapse
Thx man
I have changed my density to 190 with LCD Density app and everything looks great.
But I have an issue, everytime I reboot my phone it goes back to 240. Then I have to use LCD Density once again and reboot to get back at 190.
Is there a solution to get around this problem?
I´m using latest CM7 nightly build #30.
snowmer said:
I have changed my density to 190 with LCD Density app and everything looks great.
But I have an issue, everytime I reboot my phone it goes back to 240. Then I have to use LCD Density once again and reboot to get back at 190.
Is there a solution to get around this problem?
I´m using latest CM7 nightly build #30.
Click to expand...
Click to collapse
I tried it once and same result for me.
Just use rootexplorer to edit the file and change the density.
Or use adb to "pull" then modify the file and "push" it back:
adb pull /system/build.prop
modify with txt editor
adb push build.prop /system/
Next time use 7zip to modify the files before flashing the ROM.
I alway modify /system/build.prop for the lcd size and /system/etc/gps.conf for time servers before flashing.
truc007 said:
I tried it once and same result for me.
Just use rootexplorer to edit the file and change the density.
Or use adb to "pull" then modify the file and "push" it back:
adb pull /system/build.prop
modify with txt editor
adb push build.prop /system/
Next time use 7zip to modify the files before flashing the ROM.
I alway modify /system/build.prop for the lcd size and /system/etc/gps.conf for time servers before flashing.
Click to expand...
Click to collapse
thanks.
but im not sure how to use adb.
i only get failed cannot write file.
I will go on with the second solution and modify the zip file before flashing the next CM7.
Thanks for your help again.
snowmer said:
I will go on with the second solution and modify the zip file before flashing the next CM7.
Thanks for your help again.
Click to expand...
Click to collapse
Really, this is very easy to do on the phone, without any extra applications. Just use a file explorer with root access (like root explorer), navigate to /system/, open your build.prop file, modify the density line (ro.sf.lcd_density=xxx) to whatever you want and reboot. 190 is working nicely for me (nightly 30/CleanDHD).
snowmer said:
thanks.
but im not sure how to use adb.
i only get failed cannot write file.
Click to expand...
Click to collapse
Sorry, forgot this.
Just type "adb remount" to mount the system in Read/Write instead of ReadOnly
If you're under linux you may need sudo (but don't think so as under w7 you don't need admin...)
I dont see any improvement by changing it to 200 its only bad look now, I will change it back to 240.
And what improvements it should give me, by changing to lower density?
Sent from my Desire HD using XDA Premium App
s2 density at 200 not booting
please assist my s2 is not booting after changing to 200 with lcd density changer on a rooted s2. heeeeeeelp
Sorry if this has already been posted before but I came across it and never heard about it before. It changes your screen size like you were changing the resolution on a monitor. I went from 240 default down to 200 and it seems like a perfect size without making everything too small
https://market.android.com/details?id=lv.n3o.lcddensity&feature=search_result
you can also change it from the build.prop...knowing how to edit it is a must for any android user imo
ugothakd said:
you can also change it from the build.prop...knowing how to edit it is a must for any android user imo
Click to expand...
Click to collapse
I really never knew about this. To me at least having the smaller scale size looks and feels better than stock. How come we dont see rom/theme releases with this mod?
I think for Developers personal preferences, also I'm not quite sure they could change the build.prop with a theme, but in the case of a Rom I believe that keeping it on a basic level works out in the best for the general population, but also allows those who are more prone to making changes on their own to go ahead and attempt it for themselves.
Thanks for the thread though man, I've been iffy about whether this app would work for the Epic, I truly appreciate it.
Yep build.prop is the way to go.
I don't think I could go back to stock density. 172 looks excellent.
dpesnt the dialer get offset to bottom left when changing the density or is that only on themed dialers?
Sent from my SPH-D700 using xda premium
JohnCorleone said:
dpesnt the dialer get offset to bottom left when changing the density or is that only on themed dialers?
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Yessir it does.
DialerOne and GoDialer are fantastic as a replacement.
darkierawr said:
Yep build.prop is the way to go.
I don't think I could go back to stock density. 172 looks excellent.
Click to expand...
Click to collapse
Omg Darkie I love you lol. 172 looks amazing.:O
Sent from my Epic 4G
darkierawr said:
Yessir it does.
DialerOne and GoDialer are fantastic as a replacement.
Click to expand...
Click to collapse
Thanks for the heads up on the alterrnate dialers darkie! "Thanks" clicked.
Sent from my SPH-D700 using xda premium
Freakin killer app.....
Thanx man
Very cool mod!...I'm not sure I can go as low as 172, but even a minor adjustment to 200 really makes a wonderful difference...I especially like the overall effect to the launcher.
One drawback though...I'm going to have to retrain my muscle memory because of the slight change in location of various things.
It'll be interesting to see if there's any way to make a minor adjustment to the default dialer so it can properly scale...Also, it looks like I'm going to have to take a look at the Wired Tether app because it looks fairly odd.
.
Edit: I solved the wierd layout in Wired Tether app using appleflap's suggestion in this thread to turn off Compatibility Mode...However, I'm on SRF 1.2, so I did it through Settings-->Lockscreen Parts-->General.
.
OK...After a data wipe of the Market app, I just noticed this density change caused the Market to identify 21 of the 102 apps I currently have installed as not compatible...Bummer.
.
xanthinealkaloid said:
OK...After a data wipe of the Market app, I just noticed this density change caused the Market to identify 21 of the 102 apps I currently have installed as not compatible...Bummer.
.
Click to expand...
Click to collapse
Sorry for not giving you the heads up.
With my density so low NOTHING works with the new ****ty market. I reverted back to the older market. Where everything is compatible.
What is the pixel density of the Evo 3D? (trying to mimic that if I can)
Also, does this app cause the New market to FC or something?
Hmmm, so does anyone know the step process to changing the density with my phone total crashing with fc? ?
place witty Epic comment here
darkierawr said:
Sorry for not giving you the heads up.
With my density so low NOTHING works with the new ****ty market. I reverted back to the older market. Where everything is compatible.
Click to expand...
Click to collapse
+1
I set my density to 180...still rocking the 2.3.6 market
|| Acer || said:
What is the pixel density of the Evo 3D? (trying to mimic that if I can)
Also, does this app cause the New market to FC or something?
Click to expand...
Click to collapse
No...The issue is with the version 3x market because there's a new compatibility check in place which references the LCD density value, so this change can cause previously installed apps to appear incompatible according the the new market removing them from your installed list
.
thatdudepoops said:
Hmmm, so does anyone know the step process to changing the density with my phone total crashing with fc? ?
place witty Epic comment here
Click to expand...
Click to collapse
Are you using the stock TouchWiz launcher?...I've read it can be problematic when doing this mod.
.
Well, I'm on my way to fixing the compressed dialpad...I did the widths to see if the pngs would stretch without looking like a 1960's color TV.
I'm gonna finish this up later, but now it's time for a RedBull break.
.
xanthinealkaloid said:
Are you using the stock TouchWiz launcher?...I've read it can be problematic when doing this mod.
.
Click to expand...
Click to collapse
I'm using zeam....
place witty Epic comment here
Has anyone been able to successfully change the LCD density on the Nitro HD yet? 320 is a little too Preschool / Fisher Price for me. I've tried 160, but get stuck with a loop at the AT&T screen. I'm going to try some different sizes and see what I can do. I'm imagining the problem has something to do with the LG customized interface.
Might want to be careful there dbjungle, messing around with that could do some serious harm.
repherb said:
Might want to be careful there dbjungle, messing around with that could do some serious harm.
Click to expand...
Click to collapse
Very true. I use an app on the market called LCD Density and it has an option to use a density temporarily.
While testing I found that 160 is just unrealistic for this device. That's what I used on my Inspire which has a much lower dpi to begin with. I am working comfortably at 265 right now, but maybe I can go just a little bit lower. Hopefully all apps are still scaling properly.
Honest question here...
What is the purpose of lowering the LCD density and what would it do?
Basically you can fit more on screen. It's not that useful for the home screen, but it's pretty cool for your web browser, tapatalk, e-mail and texting. With the stock density you can only see like one line of your own text message.
I ended up only being able to get down to 264 for my lowest density.
Sent from my LG-P930 using xda premium
It's especially useful on a phone with a 720p IPS display.
Sent from my LG-P930 using xda premium
dbjungle said:
Has anyone been able to successfully change the LCD density on the Nitro HD yet? 320 is a little too Preschool / Fisher Price for me. I've tried 160, but get stuck with a loop at the AT&T screen. I'm going to try some different sizes and see what I can do. I'm imagining the problem has something to do with the LG customized interface.
Click to expand...
Click to collapse
You can go below 264 if you turn this flag to "false" in build.prop before a reboot - tried it myself assuming you are using a different homescreen - these turn off the LG lock screen and stock lockscreen comes into play. 144 is too small but being 16X9 = 144, everything is properly aligned. 192 is also on the smaller side (144+16X3), 240 suits me....enjoy..
user.feature.lock_sui=false
Good tip. I feel like I finally have some room in my apps again now.
Sent from my LG-P930 using xda premium
OK I'm thoroughly confused.
Sent from my LG-P930 using XDA App
I was running dark 1.01, which has 160dpi default and sort of got used to it.
I moved to 27, yet using LCD density app, it won't stick to 160 on reboot
Anyone know how to get it to stay at 160, while dark is getting updated?
Thanks
Amd4life said:
I was running dark 1.01, which has 160dpi default and sort of got used to it.
I moved to 27, yet using LCD density app, it won't stick to 160 on reboot
Anyone know how to get it to stay at 160, while dark is getting updated?
Thanks
Click to expand...
Click to collapse
It will only stick if you use ROM Toolbox.
Or change it in the build prop.
thanks, that program did the trick
Mimis_69 said:
It will only stick if you use ROM Toolbox.
Click to expand...
Click to collapse
Can the DPI be changed on the fly or does it require a reboot. I'm on the same ROM as OP and love it for browsing but it also makes some apps funky so itd be sweet to be able to change on the fly.
regP said:
Can the DPI be changed on the fly or does it require a reboot. I'm on the same ROM as OP and love it for browsing but it also makes some apps funky so itd be sweet to be able to change on the fly.
Click to expand...
Click to collapse
i've used one called LCD Resolution and when it changed it, it didnt do a "full" reboot; but a quick "system restart" . thats how i update my market apps. it's a really quick restart too. just be sure to turn wifi off after it restarts and then back on. it doesnt stick for some reason.
edit: not too sure if it works on ics
Has anyone done this? I just set my density nd it looks gorgeous. The Samsung keyboard started crashing Instantly. Not a huge deal I switched to SwiftKey tablet and everything is okay. However here and there galls seems to crash now. This is keeping talk from staying logged in which is a problem. Has anyone else attempted the same thing and seeing different results? As much as I love the added screen real estate (especially the split with the keyboard and aide ide visibility) its not a better tradeoff to losing talk. Unfortunately logcat reveals no direct insight into what is causing the crash only that the process is stopping. Any advice is welcome, as I'd like to keep the rest change.. I set both density values to 240.
Sent from my SPH-L900 using Tapatalk 2
Sess said:
Has anyone done this? I just set my density nd it looks gorgeous. The Samsung keyboard started crashing Instantly. Not a huge deal I switched to SwiftKey tablet and everything is okay. However here and there galls seems to crash now. This is keeping talk from staying logged in which is a problem. Has anyone else attempted the same thing and seeing different results? As much as I love the added screen real estate (especially the split with the keyboard and aide ide visibility) its not a better tradeoff to losing talk. Unfortunately logcat reveals no direct insight into what is causing the crash only that the process is stopping. Any advice is welcome, as I'd like to keep the rest change.. I set both density values to 240.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
reboot into recovery and wipe cache and dalvik...............im having no fc issues and im running at 240 as well. g-talk works fine for me as well.
t3project said:
reboot into recovery and wipe cache and dalvik...............im having no fc issues and im running at 320 as well. g-talk works fine for me as well.
Click to expand...
Click to collapse
Did you mean you're running at 240 as well? 320 is default.
Blankrubber said:
Did you mean you're running at 240 as well? 320 is default.
Click to expand...
Click to collapse
yes, typo..........running at 240, 280 is nice as well
t3project said:
yes, typo..........running at 240, 280 is nice as well
Click to expand...
Click to collapse
Haha, okay. I switched to 240 and haven't had problems yet, other than the funky sized dialer and such.
Blankrubber said:
Haha, okay. I switched to 240 and haven't had problems yet, other than the funky sized dialer and such.
Click to expand...
Click to collapse
yea, any of the stock apps need smali edits to fit the screens with different dpi
Blankrubber said:
Haha, okay. I switched to 240 and haven't had problems yet, other than the funky sized dialer and such.
Click to expand...
Click to collapse
This fixed my dialer problem looks good! im on 240.
https://play.google.com/store/apps/...251bGwsMSwxLDEsImNvbS5tb2Rvb2h1dC5kaWFsZXIiXQ..
I also flashed the 4.2 camera witch was full screen but FC because of the 360 view thing. But im going to flash this tonight and see if its fixed.
http://forum.xda-developers.com/showthread.php?t=1996205
---------- Post added at 03:05 PM ---------- Previous post was at 03:03 PM ----------
t3project said:
yea, any of the stock apps need smali edits to fit the screens with different dpi
Click to expand...
Click to collapse
Is this hard? Maybe link me and i can try it or hopefully someone can fix it.
t3project said:
reboot into recovery and wipe cache and dalvik...............im having no fc issues and im running at 240 as well. g-talk works fine for me as well.
Click to expand...
Click to collapse
Ill give it a try. Good to hear you have no problems. There is still hope
Sent from my SPH-L900 using Tapatalk 2