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
Anyone else found that when they set a custom density not all apps resize, they seem to keep the default density of the Samsung ROM? even though it has been changed. NOVA HD was one but also dialler app and camera for me.
It is also irritating that touchwiz seems to be locked to particular density as well. Anyone found any workarounds for this?
I assume you've turned Compatibility Mode off in Spare Parts? If not, try that first.
TouchWiz seems to misbehave even with that turned off, but I've had no problems with anything else being too small while running at 192 density.
you weather and clock arent squashed up into the top left hand side of your screen then, leaving about 3/4 inch column down the right hand side?
Have to wait for a good multi dpi theme or rom... but I think without cwm they'll have to wait
Sent from my GT-I9100 using XDA Premium App
Anyone else notice that the video camera starts force closing when the led density is at a non default value?
fpar said:
Anyone else notice that the video camera starts force closing when the led density is at a non default value?
Click to expand...
Click to collapse
for me it's FC's when using 180 LCD Density, 185 works fine.
fpar said:
Anyone else notice that the video camera starts force closing when the led density is at a non default value?
Click to expand...
Click to collapse
YES.!, thought it was just me, didn't realise it was density at first and ended up flashing my phone twice from scratch, second time I didn't use it and no force closes.
Custom ROMS starting to head our way now so hopefully we can get this issue resolved.
stoolzo said:
Anyone else found that when they set a custom density not all apps resize, they seem to keep the default density of the Samsung ROM? even though it has been changed. NOVA HD was one but also dialler app and camera for me.
It is also irritating that touchwiz seems to be locked to particular density as well. Anyone found any workarounds for this?
Click to expand...
Click to collapse
the camera app and the dialer isnt working very well on the resize, im only at 200 density
any fix?
Budske said:
the camera app and the dialer isnt working very well on the resize, im only at 200 density
any fix?
Click to expand...
Click to collapse
Have disabled compability mode in spare parts?
Running mine at 216 no issues so far
Sent from my GT-I9100 using XDA App
Yes, I disabled it..
Added some screens
Sent from my GT-I9100 using Tapatalk
Yeah there's quite a few oddities when changing density. I basically worked around it by replacing most of the default programs.
Dialer: DialerOne
Camera: One of the numerous camera apps in market
Music: Poweramp
Videos: mVideoPlayer
I still have to find decent replacements for Calendar and Contact list, though the contact list doesn't look bad really.
What theme are you using? I like orange
Budske said:
Yes, I disabled it..
Added some screens
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Sent from my GT-I9100 using Tapatalk
Its not a theme, its just the screengrab app that changes the colors, it is not for this phone xD
Sent from my GT-I9100 using Tapatalk
Ok, using this post as reference, I messed around with the Contacts.apk file.
I managed to resize the default dialpad to fit 200dpi.
Note that this apk was only tested on VillainRom. I don't think the signatures are compatible with normal deodexed roms.
However the scrolling aid on the right side when searching through contacts is still too small. Haven't found how to fix that yet.
EDIT: Also fixed the TouchWiz Calculator. Fits nicely on both portrait and landscape mode.
As I mentioned on another post below, if it doesn't work on your ROM, just replace the META-INF directory in my apk with the META-INF from your original apk to resign that package.
NOTE: Previous version of Contacts.apk still had misaligned landscape dialpad. I've fixed it and reuploaded.
JaeCee said:
Ok, using this post as reference, I messed around with the Contacts.apk file.
I managed to resize the default dialpad to fit 200dpi.
Note that this apk was only tested on VillainRom. I don't think the signatures are compatible with normal deodexed roms.
However the scrolling aid on the right side when searching through contacts is still too small. Haven't found how to fix that yet.
Click to expand...
Click to collapse
i wont use this cos the sigs are diferent, but if u can point me where to look to change the settings, i will make my own... or ill just upload my apk for u to fix it, or make it more resizeable.
thx for the help!
Well an easy way for you to get it to work on yours is to download the Contacts.apk that I uploaded. Copy your Contacts.apk somewhere, and open both apks in 7zip. Then just copy the META-INF directory from your apk to my apk. That basically changes the signature. Once that's done my apk should work for you.
JaeCee said:
Well an easy way for you to get it to work on yours is to download the Contacts.apk that I uploaded. Copy your Contacts.apk somewhere, and open both apks in 7zip. Then just copy the META-INF directory from your apk to my apk. That basically changes the signature. Once that's done my apk should work for you.
Click to expand...
Click to collapse
Let's take it one step further, what are the files you changed in your apk? For example, I know with the dialer, we may only need to change dialer_app.xml.
lpsi2000 said:
Let's take it one step further, what are the files you changed in your apk? For example, I know with the dialer, we may only need to change dialer_app.xml.
Click to expand...
Click to collapse
I actually went overkill on the apk. I basically grabbed the layout_resize java file from this thread and ran it on all layout xml files. Basically the script replaces all x dip references to x * 1.5 px. It's a bit unwise actually, but so far it's working as intended. Gonna test it for a few more days to see if replacing all dips broke anything.
JaeCee said:
I actually went overkill on the apk. I basically grabbed the layout_resize java file from this thread and ran it on all layout xml files. Basically the script replaces all x dip references to x * 1.5 px. It's a bit unwise actually, but so far it's working as intended. Gonna test it for a few more days to see if replacing all dips broke anything.
Click to expand...
Click to collapse
I see, yeah that was a little bit too much for me. Nonetheless keep us posted on your progress. I am currently running 182 dpi which is the safest before certain stock applications stop working.
lpsi2000 said:
Let's take it one step further, what are the files you changed in your apk? For example, I know with the dialer, we may only need to change dialer_app.xml.
Click to expand...
Click to collapse
yeah, i want to know what changes u made to fit the 200 density. and some day i will learn how to do stuff and i want to start now
Anyone has any idea how to fix this? i changed dpi to 339, from 480, with adb, I'd like to hold out a little longer for root and do it proper way in build.prop.
but is there a fix for Swiftkey?
|Night| said:
Anyone has any idea how to fix this? i changed dpi to 339, from 480, with adb, I'd like to hold out a little longer for root and do it proper way in build.prop.
but is there a fix for Swiftkey?
Click to expand...
Click to collapse
Change it back to 480 using adb???
Sent from my SGP311 using XDA Free mobile app
Id rather switch keyboard. 480 is way too much for this phone even 380 is large
|Night| said:
Id rather switch keyboard. 480 is way too much for this phone even 380 is large
Click to expand...
Click to collapse
I have a z5p and find no problem with text size or anything, what is the problem with having a DPI that high?
dude9946 said:
I have a z5p and find no problem with text size or anything, what is the problem with having a DPI that high?
Click to expand...
Click to collapse
I just find it more natrual and pleasent to look at with a smaller text size.
I was told to repost this problem in the apps thread so here I am I have a OnePlus 3 on Open Beta 13. I downloaded Google camera 4.3 and everything works except a few features are missing, but the real problem is that when I click on the "Slow Motion" option, the app crashes. I thought maybe if I did the 720 with sound mod it'd fix it, but it still force closes. I've tried with other versions, slomo still crashes. Please help
scottwitha5 said:
I was told to repost this problem in the apps thread so here I am I have a OnePlus 3 on Open Beta 13. I downloaded Google camera 4.3 and everything works except a few features are missing, but the real problem is that when I click on the "Slow Motion" option, the app crashes. I thought maybe if I did the 720 with sound mod it'd fix it, but it still force closes. I've tried with other versions, slomo still crashes. Please help
Click to expand...
Click to collapse
You have to enable HAL3.
How do I do that? Is it in the build.prop?
Generalboii said:
You have to enable HAL3.
Click to expand...
Click to collapse
Okay actually I tried enabling it through the build.prop edit (looked it up), and it still force closes :/
scottwitha5 said:
Okay actually I tried enabling it through the build.prop edit (looked it up), and it still force closes :/
Click to expand...
Click to collapse
Hmm, I dunno... Sorry. But what's wrong with the OOS camera?
Generalboii said:
You have to enable HAL3.
Click to expand...
Click to collapse
Generalboii said:
Hmm, I dunno... Sorry. But what's wrong with the OOS camera?
Click to expand...
Click to collapse
I guess there's nothing wrong with it, just looking for a change of pace and I enjoy the photosphere and lens blur options. The mod for slow motion would be great if I could just get it to work too! Any other help or suggestions??
Hi all,
Need help here. My WhatsApp textbox and send button partly cutoff / blocked. I can't see what's I'm typing in the box. It happen only when it's in pop-up view on my phone and all the time during Samsung Dex.
This happen a while after i updated to Android 5.1. No problem initially but it just appear this way now.
Kindly refer to the image sample.
Thanks in advance
rickyloh said:
Hi all,
Need help here. My WhatsApp textbox and send button partly cutoff / blocked. I can't see what's I'm typing in the box. It happen only when it's in pop-up view on my phone and all the time during Samsung Dex.
This happen a while after i updated to Android 5.1. No problem initially but it just appear this way now.
Kindly refer to the image sample.
Thanks in advance
Click to expand...
Click to collapse
Maybe uninstall and then reinstall the app?
rickyloh said:
Hi all,
Need help here. My WhatsApp textbox and send button partly cutoff / blocked. I can't see what's I'm typing in the box. It happen only when it's in pop-up view on my phone and all the time during Samsung Dex.
This happen a while after i updated to Android 5.1. No problem initially but it just appear this way now.
Kindly refer to the image sample.
Thanks in advance
Click to expand...
Click to collapse
Have you had any luck with this? i am having the same issue, i tried uninstalling and reinstalling and it happens again, this is only on my samsung tablet though.
Same problem here. Only started using dex so dont really know if this is a long standing issue or new
everybody with whatsapp problem, must change dpi to fix
AndrOmega said:
everybody with whatsapp problem, must change dpi to fix
Click to expand...
Click to collapse
Which DPI should we change? The DPI in Windows settings, or screen zoom on the phone?
snapper.fishes said:
Which DPI should we change? The DPI in Windows settings, or screen zoom on the phone?
Click to expand...
Click to collapse
on the phone with the help of this app
AndrOmega said:
everybody with whatsapp problem, must change dpi to fix
Click to expand...
Click to collapse
Ya, which dpi should we change. I'd tried to change to various dpi but it doesn't help.
Same here, for the non IT magician how do i go about doing this? haha
yes, me too. I have tried several times to email WhatsApp support, but so far there has been no response. several times there have been updates in the playstore but the result is still the same..
Same here, with Fold4! Thanks for bringing up this issue. But no solutions found yet?
This will fix that :
https://www.reddit.com/r/GalaxyFold/comments/132t6jl
pvillasuso said:
This will fix that :
https://www.reddit.com/r/GalaxyFold/comments/132t6jl
Click to expand...
Click to collapse
I don't recognize this option
okechef said:
I don't recognize this option
Click to expand...
Click to collapse
update whatsapp to the latest
then you will see that option
pvillasuso said:
This will fix that :
https://www.reddit.com/r/GalaxyFold/comments/132t6jl
Click to expand...
Click to collapse
Thanks a lot. It works perfectly now.