Related
***REQUIRES ROOT***
This thread will serve as a discussion for modifying the LCD Density of the Samsung Glaxy Nexus. Stock density is 320 dpi, and the preferred modded density is 240 dpi. Please feel free to discuss lcd density, and notify me of anything you want added to the list.
Why modify the lcd density of your phone? Simple answer: more screen real estate.
1. How to modify you lcd density
Note: You can always go back to 320 dpi at any time by following these same steps and putting 320 back in for 240!
240 dpi is the recommended modded dpi for the Galaxy Nexus. You can however set it to whatever you want. Just know that many dpi's will cause the on screen buttons to disappear, and even possibly cause the launcher to crash. In both cases you can use the adb method to restore to 240 or 320.
241 dpi is also a good number to try. It fixes the problems some apps have when running at 240 dpi. Credit goes to g33k3r. However it will cause market incompatibilities. Read #6 to fix this.
246 will fix the contact widget, and quick contact, but it will use the old style contact info which shows a large contact image above their info, not small and to the side. Credit goes to maddler.
250 dpi OR 260 dpi OR 280 dpi are also good values if you would like a smaller than stock value, but 240 is too small for you.
Method 1 (Using an app):
Download LCD Density Modder (Free) / LCD Density Modder Pro from market. Set density to 240 or 241, apply, then reboot. There are multiple different apps that can change your dpi, but this app is guaranteed to work on the Galaxy Nexus.
Method 2 (Modify a file):
Using Root File Explorer or a similar program, modify /system/build.prop file (must mount /system as r/w).
Replace:
ro.sf.lcd_density=320
With:
ro.sf.lcd_density=240
Save and reboot.
Method 3 (Using adb):
adb pull /system/build.prop C:/build.prop
In build.prop, replace:
ro.sf.lcd_density=320
With:
ro.sf.lcd_density=240
adb remount
adb push C:/build.prop /system/build.prop
Reboot phone.
2. Apps where UI is different on 240 dpi (for better or worse, ui elements have been rearranged, but none are broken)
Launcher: Home screen icons are still 4x4 and squished into the center of the screen. App drawer and Widget drawer do not fill. There is a mod that fixes this in this thread: FIX HERE
Market: Now has 2 columns instead of one when listing apps.
Gmail: Quick access icons have been romved from the bottom and placed on the top. Only first two icons are visible, other are collapsed into the drop down menu.
People: Contact info now has a two column layout: a small icon of contact on left (static) with all of the contact info as a scrolling pane on the right (no visible divider). Favorite contact icons are much smaller.
3. Apps where UI is broken, but still useable
Sports Tracker: Some interface items dont stretch to fill the screen.
ADW /ADW Ex Launcher: There is a blue line and a menu icon above the homescreen at all times.
Speedtest.net: App shows up centered on screen, not filling whole screen.
Kindle: It still works but the text is now centered in the middle and there is a large amount of paddling around it.
4. Apps where UI is completely broken
Music: App displays incorrectly at 240 dpi. Run at 241 to fix this
5. Android UI glitches
Sometimes when selecting text the menu bar on the top of the screen will have a weird blue streak across it.
Stock ICS keyboard the popup when you press a key seems like it gets clipped off a little on the bottom.
Clicking the picture of a contact either from the people app, or from a 1x1 contact widget you no longer get the quick access popup, instead it is now the person's contact picture blown up to full screen and half cut off on the right side.
6. Market apps incompatable with device (according to market)
None that I know of. Since 240 dpi is a standard dpi for most android phones, I don't envision very many apps being incompabile. If you find an app that the market say is incompatible, you can try setting your density back to 320 temporarily in order to download it.
For those with market issues on a non-standard dpi (241, 250, 260, 280 etc.), try this:
1. Boot your phone into 320 or 240 dpi mode (depending on which kind of compatibility you want).
2. Find the Market app under manage apps. Click uninstall updates, clear data, clear cache.
3. Find Market Updater under manage apps and click Disable.
4. Open Market and accept terms of service.
5. Change dpi back to 241 and reboot.
Alternatively, LCD Density Modder Pro has the ability to download and install a modded market apk to fix market compatibility issues.
Click to expand...
Click to collapse
7. Apps that crash (with possible workarounds)
Youtube: Will crash on start. Open from landscape mode! Youtube will not crash if openened in landscape mode. You can also open youtube links from the browser and other apps just fine.
8. Before and After Photos (320 dpi on left, 240 dpi on right):
***CLICK ANY SCREENSHOT TO VIEW FULL SIZE!***
Settings:
People:
Contact Info (note that the bottom bar has merged into the top bar):
Android Market:
***RESERVED***
can you provide a screenshot?
like a before/after pic.
I think this is crazy.
The stock DPI is amazing.
Get an SGSII if you want an old-school resolution or have bad eyes.
My stock DPI is absolutely beautiful...
ericshmerick said:
I think this is crazy.
The stock DPI is amazing.
Get an SGSII if you want an old-school resolution or have bad eyes.
My stock DPI is absolutely beautiful...
Click to expand...
Click to collapse
You are completely missing the point. On Android when you change the DPI, you are essentially telling android the size at which to "scale" all objects on the screen. Notice how the Galaxy Nexus has a 720p screen yet you can only fit 4x4 icons on the desktop like the Galaxy S2? Well that is because the 320 dpi is telling android to scale those things bigger. Setting it to 240 dpi will make everything smaller and give you more screen "real estate". The resolution is still 720p.
You mention having bad eyes, but when you lower the dpi you actually need GOOD eyes because everything is smaller and harder to read if you have bad eyes.
paOol said:
can you provide a screenshot?
like a before/after pic.
Click to expand...
Click to collapse
I am going to post some screenshots later today.
YouTube crashes on launch for me when set to 240 DPI. I have not performed a wipe, though I have tried wiping the settings and cache for the app.
LadFromWales85 said:
YouTube crashes on launch for me when set to 240 DPI. I have not performed a wipe, though I have tried wiping the settings and cache for the app.
Click to expand...
Click to collapse
Ah yes, thanks for reminding me. YT crashes for me as well, however if you have the widget you can click one of the videos and it will open that video. You can search for videos from there, but you cant access the home page for some reason.
EDIT: It turns out if you open youtube in landscape mode it will work!
Well thx for the Tip with the density. But however...When I start DPI Changer I get an error "Unable to read configuration file"
Any ideas?
Sent from my Galaxy Nexus using My Thumb...
Kizura said:
Well thx for the Tip with the density. But however...When I start DPI Changer I get an error "Unable to read configuration file"
Any ideas?
Sent from my Galaxy Nexus using My Thumb...
Click to expand...
Click to collapse
Are you rooted? This requires root.
for sure iam rooted...it was the first thing i have done... and i have ARHD Custom rom installed.
Sent from my Galaxy Nexus using xda premium
Kizura said:
for sure iam rooted...it was the first thing i have done... and i have ARHD Custom rom installed.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Do you have Root File Explorer? You can use the second method i listed to change the build.prop file. You can also use adb to pull the file locally, edit it, and push it back to the phone.
Oh ok then I will do it manually
I will report back soon ...I hope xD
Sent from my Galaxy Nexus
Edit: Ok this is more awesome as it was on my DHD !!!
Really thank you for that great Tip and the Help
Kizura said:
Oh ok then I will do it manually
I will report back soon ...I hope xD
Sent from my Galaxy Nexus
Edit: Ok this is more awesome as it was on my DHD !!!
Really thank you for that great Tip and the Help
Click to expand...
Click to collapse
Awesome. Make sure to check out my modified home screen launcher to get the full effect:
http://forum.xda-developers.com/showthread.php?t=1390935
Also, if you find any apps that don't display properly or something else is wrong with them (when running in 240 dpi), please post back in this thread to help inform others.
Mhh I use adb launcher... but on top of the screen is now a blue horizontal line with the three dots for options on the right side....
Will your mod take care of this? I hope you know what I mean...
Sent from my Galaxy Nexus
Kizura said:
Mhh I use adb launcher... but on top of the screen is now a blue horizontal line with the three dots for options on the right side....
Will your mod take care of this? I hope you know what I mean...
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I have ADW Ex launcher and i see that as well. It is the default titlebar and menu system for apps in ICS. Did you experience this when in 320 dpi as well or only in 240? I haven't tested it in 320.
And no, my mod only affects the stock launcher so it will not fix your problem.
No with 320 dpi that line doesn't appear its there since I have 240 Dpi...
Tested your Launcher replacement...
Great Work
But as you said it will not fix this "line affect" in adw
Maybe in a future update in adw launcher it will be fixed.
Sent from my Galaxy Nexus
I added photos to the main post now. Click on any photo to view the original size image!
Awesome, really cool. Trying it out today to see if I like it.
Another noticed bug - if you have a contact on your home screen (single icon version), which normally pops up the quick box for the contact, this now just seems to pop up their display picture and nothing else.
I see what you mean about the contact. It also happens when in the people app and you click their picture. I added it to the first post. thanks.
I thought changing the DPI would enable the ICS for tablets UI?
Always hated that Samsung set up such amazing devices and screen sizes for 320 dpi. I run 240 dpi and everything works great other than:
- Email (cuts off 1/3 right side of screen)
- SMS/MMS (fonts too big and don't fit)
- Camera (controls in the wrong place)
- Dialer (off to the left and small)
- Calculator (same as dialer)
I tried some of the 240 dpi mods from the N7000 and N7100 forums but not all work. SMS/MMS seemed to somewhat work and camera works but it's not as functional as the new JB camera. Anyone have the skills to decompile the stock ATT Note 2 APK's for multi DPI?
ookba said:
Always hated that Samsung set up such amazing devices and screen sizes for 320 dpi. I run 240 dpi and everything works great other than:
- Email (cuts off 1/3 right side of screen)
- SMS/MMS (fonts too big and don't fit)
- Camera (controls in the wrong place)
- Dialer (off to the left and small)
- Calculator (same as dialer)
I tried some of the 240 dpi mods from the N7000 and N7100 forums but not all work. SMS/MMS seemed to somewhat work and camera works but it's not as functional as the new JB camera. Anyone have the skills to decompile the stock ATT Note 2 APK's for multi DPI?
Click to expand...
Click to collapse
+1. Love 240 but the samsung keyboard crashes and makes the system unusable
I would also love to get these apps in 240, the phone looks so much better at this setting.
If it helps, the secemail.apk found at http://forum.xda-developers.com/showthread.php?t=1984896 fixed the mail client for me.
trazbot said:
I would also love to get these apps in 240, the phone looks so much better at this setting.
If it helps, the secemail.apk found at http://forum.xda-developers.com/showthread.php?t=1984896 fixed the mail client for me.
Click to expand...
Click to collapse
Didn't work for me. Kept crashing. Have to try again then.
280 works ..Samsung Keyboard still works but is shrunk down causing a gap on the right hand side
Androider4Life said:
280 works ..Samsung Keyboard still works but is shrunk down causing a gap on the right hand side
Click to expand...
Click to collapse
Do you mean other Samsung devices or are you getting 280 on the Note 2 and if so, how? 280 was perfect on my S3.
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
Chronzy said:
Do you mean other Samsung devices or are you getting 280 on the Note 2 and if so, how? 280 was perfect on my S3.
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
Click to expand...
Click to collapse
On the note2. Editing the buildprop
In the attached picture is the build.prop at 280 and you can see keyboard is offset to left and you can see the buildprop settings
Sent from my SAMSUNG-SGH-I317 using xda premium
ookba said:
Always hated that Samsung set up such amazing devices and screen sizes for 320 dpi. I run 240 dpi and everything works great other than:
- Email (cuts off 1/3 right side of screen)
- SMS/MMS (fonts too big and don't fit)
- Camera (controls in the wrong place)
- Dialer (off to the left and small)
- Calculator (same as dialer)
I tried some of the 240 dpi mods from the N7000 and N7100 forums but not all work. SMS/MMS seemed to somewhat work and camera works but it's not as functional as the new JB camera. Anyone have the skills to decompile the stock ATT Note 2 APK's for multi DPI?
Click to expand...
Click to collapse
+1
Androider4Life said:
On the note2. Editing the buildprop
In the attached picture is the build.prop at 280 and you can see keyboard is offset to left and you can see the buildprop settings
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Ah, build prop.... Of course. Thanks! 280's about perfect on this phone as well.
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
ookba said:
Always hated that Samsung set up such amazing devices and screen sizes for 320 dpi. I run 240 dpi and everything works great other than:
- Email (cuts off 1/3 right side of screen)
- SMS/MMS (fonts too big and don't fit)
- Camera (controls in the wrong place)
- Dialer (off to the left and small)
- Calculator (same as dialer)
I tried some of the 240 dpi mods from the N7000 and N7100 forums but not all work. SMS/MMS seemed to somewhat work and camera works but it's not as functional as the new JB camera. Anyone have the skills to decompile the stock ATT Note 2 APK's for multi DPI?
Click to expand...
Click to collapse
+2
I know how to decompile and and recompile. However I do not know what to change in the apk to get us to 240dpi. I could care less about dialer, calculator.
I just want the camera correct. If someone know what to change I can do it.
hope it will help you
i tried it on My rogers Note 2 and its working well
http://forum.xda-developers.com/showthread.php?t=2001577
for clock take the 4.1.2 ..
for mms and email use Archive
I used the same OP linked above and the apps work great!!
Sent from my Galaxy Note 2!
ookba said:
Always hated that Samsung set up such amazing devices and screen sizes for 320 dpi. I run 240 dpi and everything works great...
Click to expand...
Click to collapse
Hey, can someone explain this to me? Isn't DPI dots per inch? So wouldn't 320dpi represent more dots per inch, which would look better? And since the PPI of the display is the hardware, I don't understand what changing this setting does at all. Can someone explain the advantage to picking a lower dpi? Like what gets changed that would look so much better?
Thanks.
It doesn't change the actual DPI, rather the reverse.
If you have it set to 320dpi (default) then the OS draws everything very big. Set to 240dpi then the OS draws everything smaller.
The resolution of the display doesn't change so it's not like in Windows changing the resolution.
rilot said:
It doesn't change the actual DPI, rather the reverse.
If you have it set to 320dpi (default) then the OS draws everything very big. Set to 240dpi then the OS draws everything smaller.
The resolution of the display doesn't change so it's not like in Windows changing the resolution.
Click to expand...
Click to collapse
thanks+=1
Working on the dialer now and then I will move on to the others for us so that we have stock note 2 multi-dpi mods
What other DPIs would people like to have these in?
Get xposed framework. It allows you to install mods as apk. You can then select what mods you want with what resolution. Very sweet.
There is also a call recording mod and a few others.
http://www.villainrom.co.uk/forum/forums/xposed_framework_mods/
Sent from my GT-T889 using xda premium
When I adjust the dpi to anything under a 300 touchwiz does not account for this on the homes screen the icons are smaller but everything is allocated towards the top of the screen based on the dpi. When I do 240 dpi the homescreen apps are all at the top of the screen leaving about half the screen blank and useless. Nova and Apex do not have this problem however I need the s planner widget for work. Is there a way around this?
Sent from my SGH-I317 using xda premium
jthornton71707 said:
When I adjust the dpi to anything under a 300 touchwiz does not account for this on the homes screen the icons are smaller but everything is allocated towards the top of the screen based on the dpi. When I do 240 dpi the homescreen apps are all at the top of the screen leaving about half the screen blank and useless. Nova and Apex do not have this problem however I need the s planner widget for work. Is there a way around this?
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Do what the post above you suggested. Install the xposed framework. I'm using clean rom att version. It's all set at 210 DPI. Then I set the individual apps that don't play nice with low dpis back to original dpi. Which is 320. Like calculator, camera, clock, contacts and phone.
Sent from my SAMSUNG-SGH-I317 using xda premium
I was wondering what dpi everybody is running. Currently I am running stock but was wondering if there is a good dpi level everybody is using that gives more space and does not cause force closes.
Sent from my SM-N900T using XDA Premium 4 mobile app
400. No problems with FC on any DPI in the past.
However it does mess with a lot of apps. To fix this you need the Xposed framework and an app called App Settings.
I've dialed it down to 320, sure makes things TINY but love the extra real estate. 480 on this phone is huge, reminds me of the folks running 800x600 on 21" monitors!
cpufrost said:
400. No problems with FC on any DPI in the past.
However it does mess with alot of apps. To fix this you need the Xposed framework and an app called App Settings.
I've dialed it down to 320, sure makes things TINY but love the extra real estate. 480 on this phone is huge, reminds me of the folks running 800x600 on 21" monitors!
Click to expand...
Click to collapse
400 sounds pretty high to me. i haven't rooted my N3 yet so i cant change my DPI but on my N2 i was running 280 and it seemed perfect to me. Thats what ill use on my N3
320, and I think it makes things look normal. I put it at 220 in per-app DPI and that was tiny. 320 on the Note 3 is comparable to 220 on the Note 1 which was what I always set my Note 1 to (ran it at 200 for a while even to get the Nexus 7 style tablet UI). I use per-app DPI to set the dialer and camera and other Samsung apps back to stock since they get distorted at 320dpi.
Edit: You realize the N1/N2 and N3 are not comparable in dpi right? The increased resolution means to get N2 280dpi you'll likely need 380-400. 280dpi on N3 is getting pretty small. N1 220 compares roughly to N3 320.
Sent from my SM-N9005 using xda app-developers app
rlee008 said:
400 sounds pretty high to me. i haven't rooted my N3 yet so i cant change my DPI but on my N2 i was running 280 and it seemed perfect to me. Thats what ill use on my N3
Click to expand...
Click to collapse
It's a 1080 display, 320 is definitely the lowest I'd go!
280 would definitely be small.
320 on 720 devices such as the Note II look about the same as 480 on the Note 3, in my experience.
Nice thing is it's easy to change in build.prop.
I like 360. Its a nice round number... Puns aside, I really do like this dpi.
That or 380
Sent from my SM-N900T using Tapatalk
Thanks for the replies. Okay so if I set it somewhere around 360 to 400 I will have no problems with system ui only apps that I will have to adjust with app settings module? Would I have to go into each one and adjust or adjust all at once. I have a lot of apps. Also what is the stock dpi set at? To change it I would edit it under build prop using rom toolbox?
Was wondering if you guys could post screen shots to get a better idea.
Sent from my SM-N900T using XDA Premium 4 mobile app
circuit.007 said:
Thanks for the replies. Okay so if I set it somewhere around 360 to 400 I will have no problems with system ui only apps that I will have to adjust with app settings module? Would I have to go into each one and adjust or adjust all at once. I have a lot of apps. Also what is the stock dpi set at? To change it I would edit it under build prop using rom toolbox?
Was wondering if you guys could post screen shots to get a better idea.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you use app settings you can fix issues with programs not displaying correctly OR just looking too small...
Default is 480 in build.prop.
I use root explorer, open the system folder R/W and click and hold build.prop and select open with, text editor. Make changes and it will save original as build.prop.bak. Reboot to see changes.
I can post a screen shot of the settings used in app settings. Once you get the hang of this you can adjust as you wish. With some apps I prefer to use a slightly different DPI in app settings so it's not as big as it would appear at 480 yet not as tiny as it would appear at 320. That's the nice thing as you can pick anywhere in between for a balance that suits your needs/wants.
Furthermore, all these settings will be saved/backed up if you use Titantium Backup to back up your device. That's a good thing if you're a flashaholic like I tend to be!
ignore this post please, i posted in wrong thread
cpufrost said:
If you use app settings you can fix issues with programs not displaying correctly OR just looking too small...
Default is 480 in build.prop.
I use root explorer, open the system folder R/W and click and hold build.prop and select open with, text editor. Make changes and it will save original as build.prop.bak. Reboot to see changes.
I can post a screen shot of the settings used in app settings. Once you get the hang of this you can adjust as you wish. With some apps I prefer to use a slightly different DPI in app settings so it's not as big as it would appear at 480 yet not as tiny as it would appear at 320. That's the nice thing as you can pick anywhere in between for a balance that suits your needs/wants.
Furthermore, all these settings will be saved/backed up if you use Titantium Backup to back up your device. That's a good thing if you're a flashaholic like I tend to be!
Click to expand...
Click to collapse
Globally I use default settings but I like to adjust the dpi for certain apps using App Settings. For example, for some apps I like a tablet look to them which can be achieved sometimes. Notablly this can be done with gmail app. In this case I set dpi to 320 and screen dp to 800x1280. Here is a screen shot. Maybe not for everybody but I like it.
I personally use 400 for most apps except for media player style apps as the large button interfaces help for use on the go.
That said, do you guys have issues with the gallery photo editor app and other apps that display pictures using stock libraries (or so I'm guessing) where the picture is zoomed and cropped where you cannot see the whole pic even if you try to zoom out?
So far the google gallery photo editor, the samsung photo editor and ES file explorer all have the same problem for all DPIs other than 480 applied globally or specifically to "Android System".
Even if I set the photo editors to 480, as long as the "Android System" package is not 480 the pictures will be cropped.
Thanks
mscion said:
Globally I use default settings but I like to adjust the dpi for certain apps using App Settings. For example, for some apps I like a tablet look to them which can be achieved sometimes. Notablly this can be done with gmail app. In this case I set dpi to 320 and screen dp to 800x1280. Here is a screen shot. Maybe not for everybody but I like it.
Click to expand...
Click to collapse
How did you change your dp (i assume that's the resolution) to 800x1200? I already did the global DPI change to 400, but I want to see how that resolution looks for myself.
Techngro said:
How did you change your dp (i assume that's the resolution) to 800x1200? I already did the global DPI change to 400, but I want to see how that resolution looks for myself.
Click to expand...
Click to collapse
Hi. I'm just using the xposed module called App Settings. In the screen shot you can see where I change the dpi for the gmail app and the screen dp. There are a set of dp you choose from. Some make a difference and other settings don't seem to have an effect. Might want to do a back up before trying. Sometimes a bad selection can cause problems when booting up. Hope it works out!
I run almost everything at 340, as 320 is just a little too small for me. For the Samsung apps (that I haven't removed), I either use ones modded for multi-dpi from the International Note 3, or ones that I have modded myself, at 320. I don't think I have anything that still runs at the stock 480. Having a screen this size, but with everything blown up that large just seems like an incredibly bad utilization of space to me...
Sent from my SM-N900T using XDA Premium 4 mobile app
does anyone know how to make it so that your keyboard won't shrink? I use SwiftKey and though you can make it bigger it's not big enough and of you try using app settings it messes with it and turns out all bonky. I want to go down to something like 400 but the keyboard gets a tad small.
I'm facing an issue when changing lcd density (DPI) using build.prop editor, some widgets which was working on OP1 CM 11,12,13, are not displayed fine now. also Play store has some resolution issues, like recommended developer icon !
I tried different resolutions (380,400,420,460) all with the same results.
Any clues ?
Don't change DPI globally, that's problem-prone. Instead, install Xposed with module "App settings" and change DPI only for those apps where you want it. (Another advantage is that you even additionally have more flexible options, like changing text size or using the app's tablet UI etc.)
zorro_tmh said:
I'm facing an issue when changing lcd density (DPI) using build.prop editor, some widgets which was working on OP1 CM 11,12,13, are not displayed fine now. also Play store has some resolution issues, like recommended developer icon !
I tried different resolutions (380,400,420,460) all with the same results.
Any clues ?
Click to expand...
Click to collapse
hasenbein196601 said:
Don't change DPI globally, that's problem-prone. Instead, install Xposed with module "App settings" and change DPI only for those apps where you want it. (Another advantage is that you even additionally have more flexible options, like changing text size or using the app's tablet UI etc.)
Click to expand...
Click to collapse
I changed it globally with the app "Le DPI Changer" to 360 and don't have any problems in any app.
440 is great..
i have set the dpi to 380 and have problems in the following apps:
twitter: pictures in tweets have corrupted thumbnails
whatsapp: when you want to crop a picture, it is zoomed in very much and you cannot zoom out so you can only crop 10% of an image
imgur: corrupted thumbnnails too
music player (poweramp) cover art in player notification is zoomed
i think oxygen os handles dpi differently, as i couldnt even find dpi setting in build.prop
i hope someone can fix this bc i would like to stay on oxygen until cm ports etc have dash charging
As I said: No global DPI, but Xposed module "App settings". Then you avoid any problems.
~MaX~ said:
i have set the dpi to 380 and have problems in the following apps:
twitter: pictures in tweets have corrupted thumbnails
whatsapp: when you want to crop a picture, it is zoomed in very much and you cannot zoom out so you can only crop 10% of an image
imgur: corrupted thumbnnails too
music player (poweramp) cover art in player notification is zoomed
i think oxygen os handles dpi differently, as i couldnt even find dpi setting in build.prop
i hope someone can fix this bc i would like to stay on oxygen until cm ports etc have dash charging
Click to expand...
Click to collapse
Hmm from the four apps you mentioned I only use WhatsApp, and I just tested out the cropping of a selfie, normal picture and a gallery picture, it works fine for me.
I'm on 360dpi.
Does anyone know the stock dpi value?
numbere said:
Does anyone know the stock dpi value?
Click to expand...
Click to collapse
480
Sent from my ONEPLUS A3003 using Tapatalk
I'm noticing font is pretty big in comparison to another 1080p device I have in my possession. It's DPI is set at 420 and what I'd consider perfect.
crysen said:
I changed it globally with the app "Le DPI Changer" to 360 and don't have any problems in any app.
Click to expand...
Click to collapse
Which method in the app did you use? I moved the DPI slider in the app, applied it, rebooted, but nothing changed...
Sent from my ONEPLUS A3000 using Tapatalk
rickyx32 said:
Which method in the app did you use? I moved the DPI slider in the app, applied it, rebooted, but nothing changed...
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Oh right, forgot to mention, use the other method, the slider also didn't work for me.
Users with issues,
try this method:
Create a file called local.prop in the root/data folder with this text in it:
qemu.sf.lcd_density=xxx
xxx = your dpi value
Permissions of that file should be:
rw-r-r--
Reboot.
I did not test it yet on OxygenOS as my device is not unlocked, nor rooted yet.
AcmE85 said:
Users with issues,
try this method:
Create a file called local.prop in the root/data folder with this text in it:
qemu.sf.lcd_density=xxx
xxx = your dpi value
Permissions of that file should be:
rw-r-r--
Reboot.
I did not test it yet on OxygenOS as my device is not unlocked, nor rooted yet.
Click to expand...
Click to collapse
That file already exists on mine and already has the desired DPI but it's not having any effect...
rickyx32 said:
That file already exists on mine and already has the desired DPI but it's not having any effect...
Click to expand...
Click to collapse
Use the Le dpi changer from google play, set dpi value and hit build.prop button. Accept it and reboot.
OP3 by TT
i tried to change dpi with ledpi and now my build.prop file is empty and broken. can someone upload build.prop from latest oxygen os please?
EDIT: default.prop in root can be used as a new build.prop in case u get the same problem as me, no need for upload
Anyone know where I can change DPI manually? I can't find the code in the build.prop. I don't want to rely on whack apps or toolkits...
Sent from my ONEPLUS A3000 using Tapatalk
rickyx32 said:
Anyone know where I can change DPI manually? I can't find the code in the build.prop. I don't want to rely on whack apps or toolkits...
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
it doesn't exist on builb.prop of OP3, I added it manually.
Code:
ro.sf.lcd_density=400
crysen said:
Hmm from the four apps you mentioned I only use WhatsApp, and I just tested out the cropping of a selfie, normal picture and a gallery picture, it works fine for me.
I'm on 360dpi.
Click to expand...
Click to collapse
i always had the cropping problem with WhatsApp using custom dpi. try to set a new profile picture. always zoomed and no chance zooming out. you have to change the dpi back to 480 to change your profile picture, but otherwise i have had no problems with 380 dpi.
My only qualm about this phone was the abnormally large text and padding in various apps, 440 dpi is a perfect adjustment, haven't seen any graphical glitches as of yet.
So i am running into a very strange issue that i haven't been able to find much information on. I am running the latest OOS (3.1.2) rooted, i had changed the DPI a few days ago using build prop editor and everything seemed to be working just fine, except my camera, it suddenly would freeze when a picture is taken, crash, and not produce a picture, and sometimes the picture would be just green.
Here is what iv'e tried:
removed the line from build prop editor and rebooted to get to stock DPI
changed the DPI to stock with the toolkit, then back to a different DPI, then back to stock.
removed the camera app cache
factory reset the phone
Strangely enough the camera in HDR mode appears to work just fine, but it doesn't appear to work in any other mode (including video).
Using the camera with flash always turned on in pretty much any mode seems to also work.
Atlantisman said:
So i am running into a very strange issue that i haven't been able to find much information on. I am running the latest OOS (3.1.2) rooted, i had changed the DPI a few days ago using build prop editor and everything seemed to be working just fine, except my camera, it suddenly would freeze when a picture is taken, crash, and not produce a picture, and sometimes the picture would be just green.
Here is what iv'e tried:
removed the line from build prop editor and rebooted to get to stock DPI
changed the DPI to stock with the toolkit, then back to a different DPI, then back to stock.
removed the camera app cache
factory reset the phone
Strangely enough the camera in HDR mode appears to work just fine, but it doesn't appear to work in any other mode (including video).
Click to expand...
Click to collapse
I posted about this issue a few days ago http://forum.xda-developers.com/oneplus-3/help/weird-camera-bug-t3404660
mr.shme said:
I posted about this issue a few days ago http://forum.xda-developers.com/oneplus-3/help/weird-camera-bug-t3404660
Click to expand...
Click to collapse
Sorry, didn't notice that.
I flashed back to bone stock OOS 3.1.2 and everything seems to be working now... I will attempted to change the DPI again via the toolkit.
I changed DPI with Le DPI Changer (non build.prop method) and everything is working fine. You might want to check it out.
That's why I always say that global DPI change is not a good idea, period.
Much better and additionally more flexible is using the Xposed module "App Settings" where you can run every app at an individual DPI setting and tweak some more things (e. g. having an app run with its tablet UI).
I had the same issue on OOS 3.1.3 rooted and DPI changed.
I enabled RAW mode and it fixed the issue.
crumble6 said:
I changed DPI with Le DPI Changer (non build.prop method) and everything is working fine. You might want to check it out.
Click to expand...
Click to collapse
What DPI value did you set it to? No issues with camera, icons, widgets, etc?
jiznon said:
What DPI value did you set it to? No issues with camera, icons, widgets, etc?
Click to expand...
Click to collapse
400. No issues at all except that when I use "large text" captions in snapchat they display fine on my screen but the text is much smaller and out of position on my friends' phones. Literally not a single other problem with any app I've tried though. I've heard 380 works good too. Tempted to try it but tbh I'm happy at 400 for now.
crumble6 said:
I changed DPI with Le DPI Changer (non build.prop method) and everything is working fine. You might want to check it out.
Click to expand...
Click to collapse
crumble6 said:
400. No issues at all except that when I use "large text" captions in snapchat they display fine on my screen but the text is much smaller and out of position on my friends' phones. Literally not a single other problem with any app I've tried though. I've heard 380 works good too. Tempted to try it but tbh I'm happy at 400 for now.
Click to expand...
Click to collapse
Thanks for the quick reply. So far my experience has been frustrating.
1) Changed DPI to 400 via build.prop edit. Resulted in camera issues. Could not reset DPI or change to any other value. Had to reflash OOS 3.1.3 to fix.
2) Did some research. Heard a OP3 toolkit here on xda could change DPI without issue (I believe it just uses the adb method) . Used it to change to 400. Camera is fine, but I experience wonky sizing issues with widgets, icons on notification banners, twitter photo previews, and a few other little text size issues. Tried using the toolkit to return to default DPI but it simply doesn't change anything.
3) Per your account of this app, I tried it but it us unable to make any change. Looks like I may have to reflash AGAIN, and attempt the Le DPI Changer again.
Bah.
jiznon said:
Thanks for the quick reply. So far my experience has been frustrating.
1) Changed DPI to 400 via build.prop edit. Resulted in camera issues. Could not reset DPI or change to any other value. Had to reflash OOS 3.1.3 to fix.
2) Did some research. Heard a OP3 toolkit here on xda could change DPI without issue (I believe it just uses the adb method) . Used it to change to 400. Camera is fine, but I experience wonky sizong issues with widgets, icons on notification banners, and a few other little text size issues. Tried using the toolkit to return to default DPI but it simply doesn't change anything.
3) Per your account of this app, I tried it but it us unable to make any change. Looks like I may have to reflash AGAIN, and attempt the Le DPI Changer again.
Bah.
Click to expand...
Click to collapse
Sorry, I should have mentioned. I am using Nova launcher and have changed the grid size of the desktop to 11 x 7. Things will probably behave weird if you are using the oneplus launcher.
crumble6 said:
Sorry, I should have mentioned. I am using Nova launcher and have changed the grid size of the desktop to 11 x 7. Things will probably behave weird if you are using the oneplus launcher.
Click to expand...
Click to collapse
No worries. I am also using Nova Launcher with custom grid size. Only issues on my desktop is wonky icon size with Chronus widget.
jiznon said:
No worries. I am also using Nova Launcher with custom grid size. Only issues on my desktop is wonky icon size with Chronus widget.
Click to expand...
Click to collapse
I find enabling widget overlap in Nova and then playing around with resizing widgets I can usually get them looking right in the end.
I had already posted this here but it seemed like Nobody besides me had this problem.
http://forum.xda-developers.com/oneplus-3/help/camera-issues-root-t3409764
I'm glad this issue is getting attention!
running 340 dpi, works fine for me. did it with le dpi changer
Running 290 all good using le dpi changer ?
Sent from my ONEPLUS3
I'm starting to wonder there is a magic DPI number that doesn't break the camera!! Time to test!
I found this solution on the oneplus 3 reddit. Camera works perfectly and there are no weird icons!
https://www.reddit.com/r/oneplus/comments/4satgq/changing_op3_dpi_using_buildprop_without_breaking/
Basically use qemu.sf.lcd_density=xxx instead of ro.sf.lcd_density=xxx in your build.prop!
I'm using 420 and all is awesome now!!
Huge thanks to this guy for posting the solution!!
ro.sf.lcd_density=400 in build.prop works just fine on my device running stock OOS 3.2.1.
Only manual mode is slightly misaligned inside the camera app.
Trying qemu.sf.lcd_density=400 gives me the same result btw.
I never had issues with green photos in HQ or other weird behaviour.
Running dpi 400 via manual build.prop edit since day one
and only had to repeat this after each ota.