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
I'm opening this thread for have a place where shareideas to fix our Samsung apps for fit low DPi (high Resolution).
First, i'm not a developer so we need to cooperate alltogheter for win
I have a SGT European GSM, i don't know if those mods can be applicable to any CDMA device.
I fixed 2 apps for now:
Dialer, inside Contact.apk, mostly fixed only the dialpad, still need to fix Incoming/Outcoming calls
Calculator, fixed 100%
I have used this 2 great app :
[DPI] Dialer, MusicPlayer, Calc, FM, Camera + GUIDE +utility(kinda)
Apk Manager 4.9 - Makes Modifying Ur Apk A Breeze (Windows/Linux)
Inside these threads you will find how to use them.
What i modded:
Contact.apk-----> res/layout/dialer_app.xml
Calculator.apk---> res/layout/main.xml
Install them via Adb or rootexplorer.
This thread is meant for development, for people that wanna help for that purpose, do not put your request or whatever here.
reserved.....
Hello,
Those .apk works for all gsm rom ?
Thanks for your work
P.S Sorry my bad english :-(
They come from Alterbridge (Overcome)rom but they are stock apps Galaxy Tab, if Boyppc use that stock apps then they are good for you.
Make a backup of your old apps before, just to be sure.
wallah said:
Hello,
Those .apk works for all gsm rom ?
Thanks for your work
P.S Sorry my bad english :-(
Click to expand...
Click to collapse
Thanks a lot bro, i will give a try and feedback
P.S Sorry my bad english :-(
wallah said:
Thanks a lot bro, i will give a try and feedback
Edit: everythings works fine on my tab, BOYPPC rom v3,
Thank you !!!
P.S Sorry my bad english :-(
Click to expand...
Click to collapse
P.S Sorry my bad english :-(
This is the exact reason i still use 240 and not something lower. I will let you know how it works on DiP7's rom.
Sent from my GT-P1000 using XDA Premium App
This works great running at 182. You should contact the overcome dev and see if he can include it in the next version. Thanks a lot!
I lied. Still looks bad when the phone is rining after placing a call in landscape mode.
slimdizzy said:
This is the exact reason i still use 240 and not something lower. I will let you know how it works on DiP7's rom.
Sent from my GT-P1000 using XDA Premium App
Click to expand...
Click to collapse
I really dont mind it, you see the dialer like %3 of the overall time when using the tab
Just FYI, pixel density is not the same as dpi. A lower pixel density leads to an increase in dots per inch.
knightnz said:
Just FYI, pixel density is not the same as dpi. A lower pixel density leads to an increase in dots per inch.
Click to expand...
Click to collapse
Erm, no:
http://en.wikipedia.org/wiki/Dots_per_inch#DPI_or_PPI_in_digital_image_files
http://en.wikipedia.org/wiki/Pixel_density
daniel.weck said:
Erm, no:
http://en.wikipedia.org/wiki/Dots_per_inch#DPI_or_PPI_in_digital_image_files
http://en.wikipedia.org/wiki/Pixel_density
Click to expand...
Click to collapse
Sorry, I should've said "LCD Density". Decreasing that increases PPI and DPI - well, perceptually anyway, the LCD is still fixed at 1024x600. Given that the actual screen is 6.0" x 3.5" (7.0" diag) that means a native PPI/DPI of approx 170. I've no idea how LCD density relates to these values - can someone explain?
The wiki page nicely explains why I always feel like I can fit more "stuff" onto a Windows desktop than an OS X one though
ayman07 said:
This works great running at 182. You should contact the overcome dev and see if he can include it in the next version. Thanks a lot!
I lied. Still looks bad when the phone is rining after placing a call in landscape mode.
Click to expand...
Click to collapse
I have looked into changing my tabs lcd and samaung says it will run best between
191 and 200. That we just need to find the best one for the tab. It is set at 240 stock. I have mine running at 195, and everything runs and shows up perfect. Looks like a new hd screen!
HIT THANKS IF I HAVE HELPED.
Sent from my SGH-T849 using XDA Premium App
first of all.. thanks for the links.
i was trying to edit the email.apk to display properly in landscape mode but it is force closing whenever im switching to landscape mode. im trying to display the message list on left pane to adapt to extra height but it doesnot seem to work for some reason. the file i changed is.. Email.apk\res\layout-land\p1_message_list.xml
i think the line should read
Code:
<LinearLayout android:orientation="vertical" android:id="@id/msglist" android:background="#ffffffff" android:layout_width="258.0sp" android:layout_height="fill_parent">
but its not working or may be im doing it completely wrong. please help. i have so many other apps to fix too this is my first android hack.
get root tools in the market. you can change lcd, heap size, and several other mods.
Sent from my GT-P1000 using XDA App
Can you make the stock launcher fit on 200?? And stock music sucks on locked screen..
Does anyone know if there is a work around to make Skype work after changing the DPI to 182?
i dont see any issue with skype pn 182dpi. what is the issue?
Did anyone get the Camera.apk to work with low densities? I just switched to 172 and I'm loving it. Everything looks much better.. except the Camera da FCs on startup.
Im using my galaxy note 4 in 460dpi and grren dialer button stretches. Will this fix the problem? Also how can i install this xml file
Well, As every1 knows HDPI Roms Wont work on Wildfires, But Theres some root apps that let u change ur resolution would that help them to work?
J I M said:
Well, As every1 knows HDPI Roms Wont work on Wildfires, But Theres some root apps that let u change ur resolution would that help them to work?
Click to expand...
Click to collapse
The problem is hdpi is well above our miserable 120 (I don't know the exact number between 2-300 I think, but as it higher there's a lot more leverage for changing it on hdpi) if you change it to a much higher number on a low res screen nothing will fit on the screen.
The apps allow you to change the density software side, but on the hardware side you'll still have a low res screen.
Sent from my HTC Wildfire using xda premium
Yep, the apps there just change the DPI of the device.
If you would want to get HDPI, you would need a DPI setting of around 200 DPI (look at the pic I attached) and I think that you would't really be able to see much on the screen at that DPI level.
Hi everyone!
So, let's suppose that we have a rooted LG G3 (done with the current rooting methods), running stock ROM. Because I always like to cramp as many widgets on the home screen as possible, I want to change the DPI density of the screen (usually 3-rd party launchers allow you to only rescale the shortcuts, but not the widgets). We coud use the Texdroider app from the Play store, but it changes the DPI globally, so I'm worried it might harm the phone... Another way would be to install Xposed Framework - but can it be installed already safely at this point?
Of course ruining the stock Launcher by changing the DPI is not a problem, as I always use some 3-rd party Launchers that can handle layouts more flexibly
I'm also interested in changing LCD density on G3.
Has anyone done it?
Use Per-App Modules via XPOSED to change individual app DPI
radicalisto said:
Use Per-App Modules via XPOSED to change individual app DPI
Click to expand...
Click to collapse
Tnx, but I was thinking on global change. On my old GS2 it was matter of simply editing build.prop file.
My setting was 182 which was great. But I remember that if you over do it, phone will not boot and without nandroid backup it is quite risky.
LittleCannon said:
Tnx, but I was thinking on global change. On my old GS2 it was matter of simply editing build.prop file.
My setting was 182 which was great. But I remember that if you over do it, phone will not boot and without nandroid backup it is quite risky.
Click to expand...
Click to collapse
Use Textroid - You can use Build.Prop it'll work fine, just go no lower than around 400 or you will run into issues (for the record stock is 650)
radicalisto said:
Use Textroid - You can use Build.Prop it'll work fine, just go no lower than around 400 or you will run into issues (for the record stock is 650)
Click to expand...
Click to collapse
Actually 640 is default.
Anyway, 530 is the lowest value. Any below that and apps will start to FC.
Pitty, because on 450 screen is amazing!
LittleCannon said:
Actually 640 is default.
Anyway, 530 is the lowest value. Any below that and apps will start to FC.
Pitty, because on 450 screen is amazing!
Click to expand...
Click to collapse
I went to 480 and lost icons (they became little green androids) I had to set back to 650 for default in order for it to show properly again.
radicalisto said:
I went to 480 and lost icons (they became little green androids) I had to set back to 650 for default in order for it to show properly again.
Click to expand...
Click to collapse
Exactly the same. On 530 icons are still normal.
LittleCannon said:
Exactly the same. On 530 icons are still normal.
Click to expand...
Click to collapse
I'll give 530 a shot and see. Cheers.
radicalisto said:
I'll give 530 a shot and see. Cheers.
Click to expand...
Click to collapse
It is not much as I expected, but still it is better then stock density.
It's a keeper.
changed it to 580 and its bootlooping now. any help?
well...this is kinda roundabout so it works and I'm not complaining...I disabled or removed all of my AT&T apps and the useless LG ones...so I set my dpi to 450 and changed the per app dpi to 530 for the lg apps...problem solves...especially since I barely use the lg apps.
sjavvaji said:
well...this is kinda roundabout so it works and I'm not complaining...I disabled or removed all of my AT&T apps and the useless LG ones...so I set my dpi to 450 and changed the per app dpi to 530 for the lg apps...problem solves...especially since I barely use the lg apps.
Click to expand...
Click to collapse
Could you provide a screen capture to see the difference??
I'm thinking about doing it...
Thanks
nxym said:
changed it to 580 and its bootlooping now. any help?
Click to expand...
Click to collapse
I did the same thing and I'm stuck on this wretched infinite boot loop. Did you get any help on this if so can you please post the fix to your woes?
EDIT: So I tried to use the built-in factory reset ... nothing doing. STILL boot looping. I'm wondering if I should start panicking now? haha
kobbz said:
I did the same thing and I'm stuck on this wretched infinite boot loop. Did you get any help on this if so can you please post the fix to your woes?
EDIT: So I tried to use the built-in factory reset ... nothing doing. STILL boot looping. I'm wondering if I should start panicking now? haha
Click to expand...
Click to collapse
i had to flash the kdz image and get it back to stock.
has anyone been able to change their desity to about 400 to 440 and still use the LG apps, I changed mine to 480 and all my apps like phone/messing apps stopped working?
dkotoric said:
has anyone been able to change their desity to about 400 to 440 and still use the LG apps, I changed mine to 480 and all my apps like phone/messing apps stopped working?
Click to expand...
Click to collapse
LG apps can't go below 530 DPI. You'll need to individually them to 530 or higher to keep them from crashing.
Sent from my LG-D851 using Tapatalk
partylikeaninjastar said:
LG apps can't go below 530 DPI. You'll need to individually them to 530 or higher to keep them from crashing.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
How do i individualy change them
Sent from my LG G3
dkotoric said:
How do i individualy change them
Sent from my LG G3
Click to expand...
Click to collapse
Use the Xposed Framework with the module "App Settings".
Batfink33 said:
Use the Xposed Framework with the module "App Settings".
Click to expand...
Click to collapse
Im sorry I have been using cayanogen mod for to long how and where do i get that
Sent from my LG G3
For some reason, at some point, I lost my UI sound effects.
I'm running rooted stock V10I on a D855 with the Bumped TWRP and the only things I've done so far are apply the multitasking, CTT, and G3 Speed tweaks. I first noticed when I trashed a shortcut I had on my home screen. There used to be a sound effect whenever I did that and now it's gone. I turned on the sound effects options in the sound menu, too, and I'm not getting anything either, like when I lock or unlock the screen.
Has this happened to anyone else? And if it has, how did you fix it?
Uninstal all xposed moduls,end see what is the problem
Got it.
The problem was that the build.prop editor app cut off the end of mine.
Awestrike said:
Got it.
The problem was that the build.prop editor app cut off the end of mine.
Click to expand...
Click to collapse
I edited the build.prop also and got no sound. I was so confused on why it wasnt working but thanks to you its back up now! Almost the quarter of the file was gone. Thanks alot i wonder why editing the file doesnt save properly though.
foggydisaster said:
I edited the build.prop also and got no sound. I was so confused on why it wasnt working but thanks to you its back up now! Almost the quarter of the file was gone. Thanks alot i wonder why editing the file doesnt save properly though.
Click to expand...
Click to collapse
because the build.prop is to big for the filemanager to save, so it cuts of what it can't save
i have D855 version..i have everything stock..launcher , rom everything..i have installed only Greenify app and turned on Accessibility Service for it, and some apps like Facebook, Snapchat, and Instagram..the trash sound has gone?? anyone help..thanks