Database Develop

Simple density tweak

This is such a simple tweak but I figured I'd share it any how...
It always amazes me how there's this badass high res screen but it ships with everything scaled up which just doesn't take any advantage of the number of pixels available.
I messed around with a few values of the "ro.sf.lcd_density" property in /system/build.prop and settled for 320 (default is 480). It does make a little on the small side but you can offset this with the regular Settings -> Display -> Font size option.
The result, is for me at least, a great improvement. I can see most of my apps in the drawer without scrolling, can see and actually read a whole website without zooming in plus the system and nav bars top and bottom now take up a much more reasonable amount of space.
Install your favorite root enabled File Explorer and mount system RW and go edit. I like http://goo.gl/NvtA8 as it runs as su & mounts system for you.

After getting stuck in a bootloop by using one of those dpi changer apps I've plucked up the courage to try again. This time I edited the build.prop myself and it worked.
It looks crazy I think I could get used to this though
Sent from my C6603 using Tapatalk 2

wow this is amazing. i always wondered why they scale it up, now i can tweak it myself. thanks!

I'm hoping that at some point someone ports Paranoid Android for the Z it will be amazing! (please, please, please!). But can someone who's applied this upload some screenshots (Settings, Notification shade, etc)? Thanks in advance!

Kallb123 said:
After getting stuck in a bootloop by using one of those dpi changer apps I've plucked up the courage to try again. This time I edited the build.prop myself and it worked.
It looks crazy I think I could get used to this though
Sent from my C6603 using Tapatalk 2
Click to expand...
Click to collapse
How about the camera app
Are the controls offset?
Sent from my C6603 using Tapatalk 2

Here's some screen shots
320 DPI, font size is normal. With small font size everything is tiny
Sent from my C6603 using Tapatalk 2

Just found the phone app doesn't scale correctly.
The buttons work, but graphics are messed up.
Sent from my C6603 using Tapatalk 2

R: Simple density tweak
I suggest you to try with the value 400: I've been using it since I got the phone and is great! A lot of space but still usable everyday. But sadly this is not a stock value ( 480 320 240 and 160 are stock afaik) and this will break play store compatibility: to fix it you have to flash a multi dpi play store mod.
And yes, the phone app does not scale properly but it's not really an issue..
Sent from my C6603 using xda premium

Tried with 320 , but I got a boot loop. Locked Z , with root and CWM .
I think I will have to reflash it from the PC companion to recover it.

Very strange. What does adb logcat say during your bootloop? Sure you didn't b0rk the file some how?

I did not look at the adb, but I'm thinking the same thing, I thing somehow the file just got corrupted ...
also after I mount R/w , twice the screen got black, reboot, root explorer, R/w and everything ok.
Once I flash with PC companion , and root it again I will try again :fingers-crossed:
Anyhow I tried also a couple of days ago with a dpi changer and the result was the same .

DeiphoneaAndroid said:
I did not look at the adb, but I'm thinking the same thing, I thing somehow the file just got corrupted ...
also after I mount R/w , twice the screen got black, reboot, root explorer, R/w and everything ok.
Once I flash with PC companion , and root it again I will try again :fingers-crossed:
Anyhow I tried also a couple of days ago with a dpi changer and the result was the same .
Click to expand...
Click to collapse
I used a dpi changer a few days ago and got a bootloop. This time I simply used ES FilevL Explorer and enabled root functions. Didn't need to mount anything, just change number, save and reboot
grievous2004 said:
I suggest you to try with the value 400: I've been using it since I got the phone and is great! A lot of space but still usable everyday. But sadly this is not a stock value ( 480 320 240 and 160 are stock afaik) and this will break play store compatibility: to fix it you have to flash a multi dpi play store mod.
And yes, the phone app does not scale properly but it's not really an issue..
Click to expand...
Click to collapse
Seems like a big gap between 320 and 480 :/
I've been thinking if using 400, as I did try on my way down to 320 abd it looked alright, but now I know it's not stock I'm not sure. Also, would we get tablet interfaces on 400 dpi?
I opened up imdb and was greeted by a nice tablet interface kinda don't want to give it up :/
Sent from my C6603 using Tapatalk 2

For apps that don't scale such as dialer I use xposed and app settings module.
Been using 380dpi for a while that works ok
Sent from my C6603 using Tapatalk 2

fards said:
For apps that don't scale such as dialer I use xposed and app settings module.
Been using 380dpi for a while that works ok
Sent from my C6603 using Tapatalk 2
Click to expand...
Click to collapse
Any chance you can give us a hint on how to use xposed, please?
Sent from my C6603 using Tapatalk 2

Set the dpi per app to the original 480 for each of the particular app such as contacts (dialer), contacts import, phone, phone contacts and phone storage and semc task switcher.
which don't scale properly at a lower res.
To install it
http://forum.xda-developers.com/showthread.php?p=39145237
Sent from my C6603 using Tapatalk 2

fards said:
For apps that don't scale such as dialer I use xposed and app settings module.
Been using 380dpi for a while that works ok
Sent from my C6603 using Tapatalk 2
Click to expand...
Click to collapse
Will 380dpi give us a tablet interface or do we need to go all the way to 320 for that?
Sent from my C6603 using Tapatalk 2

fards said:
Set the dpi per app to the original 480 for each of the particular app such as contacts (dialer), contacts import, phone, phone contacts and phone storage and semc task switcher.
which don't scale properly at a lower res.
To install it
http://forum.xda-developers.com/showthread.php?p=39145237
Sent from my C6603 using Tapatalk 2
Click to expand...
Click to collapse
Well... THANK YOU! It's almost like being on Paranoid!! You can set per app dpi, font dimension (scale) and layout (screen dp) so I can get tablet layout in the apps I'm interested while keeping the global interface (navbar and notification bar) at the desired dpi.

This is not development... Moving to themes and apps
Sent from my Z

fards said:
Set the dpi per app to the original 480 for each of the particular app such as contacts (dialer), contacts import, phone, phone contacts and phone storage and semc task switcher.
which don't scale properly at a lower res.
To install it
http://forum.xda-developers.com/showthread.php?p=39145237
Sent from my C6603 using Tapatalk 2
Click to expand...
Click to collapse
Pls pls pls share your settings for exposed, meaning all the packages with modified settings list with the applied parameters. Would be worth a million thanks.
Story is i've applied 320 dpi via build prop and everything is perfect but the dialer is coorupt. So i installed xposed and the module, hanged the dpi for the phone and contacts apps to 480, but when i open the dialer, it has ne dial button and the soft keyboard pops up...
Once again, i would really appreciate if one of you gus who reported everything to work ok could share all the relavant details i/o for me to reproduce.
Cheers
Sent from my Z using xda premium

shulmus said:
Pls pls pls share your settings for exposed, meaning all the packages with modified settings list with the applied parameters. Would be worth a million thanks.
Story is i've applied 320 dpi via build prop and everything is perfect but the dialer is coorupt. So i installed xposed and the module, hanged the dpi for the phone and contacts apps to 480, but when i open the dialer, it has ne dial button and the soft keyboard pops up...
Once again, i would really appreciate if one of you gus who reported everything to work ok could share all the relavant details i/o for me to reproduce.
Cheers
Sent from my Z using xda premium
Click to expand...
Click to collapse
I got these set to 480 and the dialer looks pretty good for me:
Contacts
Contacts Import
Contacts storage
Phone
Phone Contact
Phone/Messaging Storage
Recent Calls
I'm not sure how many of these actually relate to what you're seeing on screen, someone else will hopefully clear that up, but at the moment this is what is working for me.

[Q] Removal of Active Notifications, custom DPI

Hi Guys,
Wondering if anyone has tried (sucessfully or not) to remove Active notifications all together from the Moto X? I know I know... "It's the best part of the phone" and I agree.
But, I'd prefer a smaller DPI setting... 280 looks fantastic and provides more usability. Plus, there is an app in the market called Dynamic Notifications that works just as well and includes music controls when you pick up the phone.
I've narrowed down to the active notification settings / apk and it locking the phone up after receiving a call. Just un-ticking active notifications in settings still causes a lock. Perhaps it's deeper than just the .apk?

Well, that was easy. I disabled Active Notifications in the app manager and works perfectly. Don't know why I didn't try this before.
Using Dynamic Notifications brings back the functionality too!

mcgrathpatj said:
Well, that was easy. I disabled Active Notifications in the app manager and works perfectly. Don't know why I didn't try this before.
Using Dynamic Notifications brings back the functionality too!
Click to expand...
Click to collapse
Dynamic Notifications lights up when you pick up the phone?

Yup
Sent from my XT1060 using Tapatalk

Dynamic Notifications probably doesn't use the companion core though, so will be less battery efficient.
Sent from my HTC One using XDA Premium 4 mobile app

You're better off leaving active notifications turned on and just changing their setting back to 320 using Xposed/app settings. That's exactly what I did when I was running using 280 in the build.prop and it worked great.

How did you guys change dpi? What's default on the X?

340
Sent from my XT1060 using Tapatalk

phositadc said:
How did you guys change dpi? What's default on the X?
Click to expand...
Click to collapse
As someone mentioned, you can use XPosed. Alternately, find the line ro.sf.lcd_density=340 (or something along that line) in your build.prop file and change it to the desired number, save and reboot.

phositadc said:
How did you guys change dpi? What's default on the X?
Click to expand...
Click to collapse
320.
mcgrathpatj said:
340
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Wrong--it's 320. XHDPI is 320.

Is it 320? My mistake.
Sorry, didn't see the question for how you change the DPI...
1) have to be root
2) Reboot into recovery mode (power off. Hold vol. down + pwr for 5 sec. select recovery)
3) Open Root Explorer and navigate to /system/, long press build.prop and select open with editor.

The problem with changing the DPI for Active Display is that the notifications are no longer centered. It shifts to the left. Perhaps if you're just running it at 280, you may not notice it as much but my DPI is 245. I ended up using Xposed App Settings and changing the DPI for Active Display back to 320 and Active Display is back to the center with everything else on the phone nice and small

insanulous said:
The problem with changing the DPI for Active Display is that the notifications are no longer centered. It shifts to the left. Perhaps if you're just running it at 280, you may not notice it as much but my DPI is 245. I ended up using Xposed App Settings and changing the DPI for Active Display back to 320 and Active Display is back to the center with everything else on the phone nice and small
Click to expand...
Click to collapse
Are you changing the DPI for all other apps? Don't you find it tiresome each time you install a new app? Also, I was doing this previously, and I noticed when you open gmail, or calendar, there is a slight delay where the app in question starts as the default 320 then pops to the set DPI causing a brief graphical glitch.
I know, small, but irritating none the less.

I don't do it for each app. I just change the build.prop to set it to 245 for all apps and just change particular apps that look weird to 320 using Xposed App Settings. I haven't noticed the graphical glitch but I'll definitely look out for it in the future
Sent from my SCH-I535 using Tapatalk

insanulous said:
I don't do it for each app. I just change the build.prop to set it to 245 for all apps and just change particular apps that look weird to 320 using Xposed App Settings. I haven't noticed the graphical glitch but I'll definitely look out for it in the future
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Oh wow, so you're saying that if I change the Active Display apk back to 320, everything behaves normally?

mcgrathpatj said:
Oh wow, so you're saying that if I change the Active Display apk back to 320, everything behaves normally?
Click to expand...
Click to collapse
Indeed! :laugh:

I would love to be able to do this! But I am having some issues. I set my build.prop dpi to 240 (using ROM Toolbox), and in the Xposed/App Setting I set both the Active Display and Active Display System to 320 and the rest of the options defaulted. I then saved and rebooted.
Now my Active Notifications freezes my phone and I have to restart it.
(I reset my overall dpi to 320, everything works great just looks huge)
Do I need to change any other settings in App Settings for this to work properly? or any ideas what I'm doing wrong?
I have Moto X Dev. Running 4.4 if that makes any difference
Thanks!
---------- Post added at 02:05 AM ---------- Previous post was at 01:43 AM ----------
I think I figured it out! I didn't install the Xposed/App Settings correctly. Still a little new to Xposed.
Fixed it and so far so good.
Thanks for the info!

im not sure what i am doing wrong, but this is certainly not working for me.
build.prop is set to 250 but active notifcations is set to 320 in app settings. i see active display mentioned, not sure what that is.
any advice?
im on 4.2, it appears that active display is 4.4 or higher. this fix isnt working for me.

krsmit0 said:
im not sure what i am doing wrong, but this is certainly not working for me.
build.prop is set to 250 but active notifcations is set to 320 in app settings. i see active display mentioned, not sure what that is.
any advice?
im on 4.2, it appears that active display is 4.4 or higher. this fix isnt working for me.
Click to expand...
Click to collapse
It could be different for 4.2, I'm not sure. If you go into Xposed, then Modules, is App Settings Checked? That is what I forgot to do. You can change all the settings you want in App Settings but if it's not checked in Xposed it doesnt matter.

jswanson04 said:
It could be different for 4.2, I'm not sure. If you go into Xposed, then Modules, is App Settings Checked? That is what I forgot to do. You can change all the settings you want in App Settings but if it's not checked in Xposed it doesnt matter.
Click to expand...
Click to collapse
it is checked because i use app settings to allow the launcher to rotate, and it rotates.
EDIT: i reset my dpi to 320 and am changing system apps dpi individually, one of them caused active notifications to break, narrowing it down
EDIT AGAIN: it appears that on 4.2 active notifications relies on the setting for ANDROID SYSTEM. Lots of other apps rely on android system for their resolution also. things started to break down at this point and i couldn't have everything i wanted all at once. bummer.

[Q] No Active Display after changing LCD Density

I've been applying assorted mods and V6 Supercharging lately just to see what all I can do before I break stuff. Well, I broke Active Display and I wasn't sure what did it. I restored back to stock 4.4 and noticed that Active Display breaks when I change the LCD density lower than 320 (I'm using 280). After the phone goes to sleep a few times, it wacks out and won't let me unlock it. Shortly after it soft reboots and Active Display no longer works.
Has anyone else noticed this problem and were you able to make Active Display work with the lower density?

d3athsd00r said:
I've been applying assorted mods and V6 Supercharging lately just to see what all I can do before I break stuff. Well, I broke Active Display and I wasn't sure what did it. I restored back to stock 4.4 and noticed that Active Display breaks when I change the LCD density lower than 320 (I'm using 280). After the phone goes to sleep a few times, it wacks out and won't let me unlock it. Shortly after it soft reboots and Active Display no longer works.
Has anyone else noticed this problem and were you able to make Active Display work with the lower density?
Click to expand...
Click to collapse
The thing with changing DPI is it makes the active display go off center, and thus crash sometimes. Change back the DPI of Active Display only to stock 320 while keeping the rest of the system on 280.

anirudh412 said:
The thing with changing DPI is it makes the active display go off center, and thus crash sometimes. Change back the DPI of Active Display only to stock 320 while keeping the rest of the system on 280.
Click to expand...
Click to collapse
I didn't know you could do that. I'm on AT&T 4.4, how would I change just AD to 320? I only know how to change system through build.prop.

I found that if you change certain apps that you have set up to show notifications in active display, if you adjust the DPI you'll lose the pictures for the notification. For example, change the Messaging app to something other than 320. Poof, No more pictures.
---------- Post added at 01:02 AM ---------- Previous post was at 01:01 AM ----------
d3athsd00r said:
I didn't know you could do that. I'm on AT&T 4.4, how would I change just AD to 320? I only know how to change system through build.prop.
Click to expand...
Click to collapse
Used Xposed module. App Settings.

natezire71 said:
I found that if you change certain apps that you have set up to show notifications in active display, if you adjust the DPI you'll lose the pictures for the notification. For example, change the Messaging app to something other than 320. Poof, No more pictures.
---------- Post added at 01:02 AM ---------- Previous post was at 01:01 AM ----------
Used Xposed module. App Settings.
Click to expand...
Click to collapse
Thanks. I must have missed that one.

d3athsd00r said:
Thanks. I must have missed that one.
Click to expand...
Click to collapse
Let me know if that works. I've been wanting to change the stem DPI also

natezire71 said:
Let me know if that works. I've been wanting to change the stem DPI also
Click to expand...
Click to collapse
Will do. I might have to take a break from work to run out to my car and try this.

d3athsd00r said:
Will do. I might have to take a break from work to run out to my car and try this.
Click to expand...
Click to collapse
Man, it's late for work. You should take a break

natezire71 said:
Man, it's late for work. You should take a break
Click to expand...
Click to collapse
I work night shift, and we can't have our phones in the building. :sad:

natezire71 said:
Man, it's late for work. You should take a break
Click to expand...
Click to collapse
So something is up with my settings. When I click on "security", settings crashes. Looks like I'm going to have to wipe

natezire71 said:
Let me know if that works. I've been wanting to change the stem DPI also
Click to expand...
Click to collapse
d3athsd00r said:
Will do. I might have to take a break from work to run out to my car and try this.
Click to expand...
Click to collapse
Download the newest version from here
http://forum.xda-developers.com/showthread.php?t=2554049
While in recovery, change Active Display to 320 in App Settings module, build.prop to 280 (or whatever number you desire). Reboot, profit
Also, if anyone wants tablet mode for certain apps (I use mine on GMail, go to App Settings module, select the particular app, change DPI to around 220, and DP to 800X1280)

So I finally got around to refreshing my phone. 280 in build.prop with 320 set for active display makes the phone right where I want it with resolution and size
My new favorite phone of all time. And I don't even have AOKP, and never will
Sent from my XT1058 using XDA Premium 4 mobile app

d3athsd00r said:
So I finally got around to refreshing my phone. 280 in build.prop with 320 set for active display makes the phone right where I want it with resolution and size
My new favorite phone of all time. And I don't even have AOKP, and never will
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can you please explain how u did it? I'm lost.. Thanks!

varun.gid said:
Can you please explain how u did it? I'm lost.. Thanks!
Click to expand...
Click to collapse
You have to install Xposed and the module App Settings. Once you've rebooted and Xposed is active, go into App Settings and set the DPI on Active Display to 320. Then set your DPI in build.prop to whatever you want. Reboot and enjoy.
Sent from my XT1058 using XDA Premium 4 mobile app

DPI changes

So I am hoping I am not the only one that thanks the stock navigation bar is way too big. On my Oneplus One I had it set pretty small, but it made the phone look better, just didn't make everything look so big.
My question is has anyone changed the DPI on the G4, and if so, what did you use to do that?
I am rooted and have flashed xTreme v1.0.
Thanks.

vng10 said:
So I am hoping I am not the only one that thanks the stock navigation bar is way too big. On my Oneplus One I had it set pretty small, but it made the phone look better, just didn't make everything look so big.
My question is has anyone changed the DPI on the G4, and if so, what did you use to do that?
I am rooted and have flashed xTreme v1.0.
Thanks.
Click to expand...
Click to collapse
You just need an app like build.prop editor, ES File Explorer,or Root Explorer to find and edit text within the build.prop file. It is in the "system" folder. Once you've accessed the build.prop look for ro.sf.lcd_density and change the value from 640 to whatever you like and restart the phone. I've heard that if you go below 540 the camera app and some other apps will not work properly. I set mine to 560. Also, if you have a quickcircle case, that quickcircle app will no longer be aligned correctly as it's set for 640 dpi. Once we get xposed running or if you have a rom that allow for per-app dpi settings, you would be able to easily fix this issue.
Hopefully this helps.

willmayah said:
You just need an app like build.prop editor, ES File Explorer,or Root Explorer to find and edit text within the build.prop file. It is in the "system" folder. Once you've accessed the build.prop look for ro.sf.lcd_density and change the value from 640 to whatever you like and restart the phone. I've heard that if you go below 540 the camera app and some other apps will not work properly. I set mine to 560. Also, if you have a quickcircle case, that quickcircle app will no longer be aligned correctly as it's set for 640 dpi. Once we get xposed running or if you have a rom that allow for per-app dpi settings, you would be able to easily fix this issue.
Hopefully this helps.
Click to expand...
Click to collapse
Did you have any bootloop issues?

vng10 said:
Did you have any bootloop issues?
Click to expand...
Click to collapse
I didn't. Never had any boot loop issues throughout the whole rooting process. I have an ATT H810 model however. Just lurking on the T-Mobile page to see what development comes out now that you all have unlocked bootloader.

willmayah said:
I didn't. Never had any boot loop issues throughout the whole rooting process. I have an ATT H810 model however. Just lurking on the T-Mobile page to see what development comes out now that you all have unlocked bootloader.
Click to expand...
Click to collapse
Okay. THanks. Yeah I tried editing the build.prop and when it rebooted, it was optimizing 32 apps and when it was finishing up, it would reboot. So I am on my backup. Ill see if there are any other options or fixes to this. I just hate how big everything looks at the default.

I used an app someone in one of the G4 threads mentioned called DPI Density changer. I lowered it to 550 seems pretty good to me.

If you're unhappy with the NavBar, you can give Swipe Navigation [Root] a try. It's GREAT on the G4, the Nexus 6 and other onScreen Nav based devices. I have it set with the NavBar completely hidden and it has an outstanding swipe gesture setup to replace the NavBar buttons. It's made every app take full advantage of the display without any loss due to the NavBar sucking up some space.

Build Prop Editor on the play store works flawlessly. The DPI option is conveniently located in the side menu too. Running 540 with no issues, though the circle case will still be misaligned.

vng10 said:
Okay. THanks. Yeah I tried editing the build.prop and when it rebooted, it was optimizing 32 apps and when it was finishing up, it would reboot. So I am on my backup. Ill see if there are any other options or fixes to this. I just hate how big everything looks at the default.
Click to expand...
Click to collapse
Build prop created boot loop for me too I switched to kernel audiutor from play store and no more boot loops. Changed dpi to 530 with no issues.
Sent from my LG-H811 using Tapatalk

Dpi density changer worked for me. Nav bar is still a little big for me at 540 but its manageable. Thanks for all the help!
Sent from my LG-H811 using Tapatalk

LCD / DPI Scaling Stock ROM Rooted?

I can't get the toolkit from the other thread to recognize my device worth crap. Rooted/TWRP'd, Xposed all working fine going the manual way. I would really like to scale things down on this large beautiful screen to gain more content space though. Anyone have any ideas?

purplepenguin said:
I can't get the toolkit from the other thread to recognize my device worth crap. Rooted/TWRP'd, Xposed all working fine going the manual way. I would really like to scale things down on this large beautiful screen to gain more content space though. Anyone have any ideas?
Click to expand...
Click to collapse
You can always edit the DPI in build.prop but that will likely cause scaling issues. It does with the OnePlus 3. I imagine it would be the same with the 3T. If you want to just look for ro.sf.lcd_density. I'm pretty sure stock is set to 480, just set it to something lower like 400. There is also the per app DPI changer for xposed. You would have to set each app manually but you could set the ones that didn't work properly back to the stock setting.
Sent from my OnePlus3T using XDA Labs

Build.prop is the best method. Make sure to create a backup before editing though.

If you're rooted I recommend Le DPI Changer from the Play Store. Make sure you tick the "Use Shell WM for setting DPI". I have mine set to 400 and love it. There are also adb commands to achieve this without root but not sure if they'll work on the 1+3t

I use Easy DPI Changer from playstore and it works perfect...

are you guys not seeing the user interface glitches that I'm seeing?

kramer987 said:
are you guys not seeing the user interface glitches that I'm seeing?
Click to expand...
Click to collapse
I am seeing some glitches like quick settings mis alignment...

thesm4rt1 said:
If you're rooted I recommend Le DPI Changer from the Play Store. Make sure you tick the "Use Shell WM for setting DPI". I have mine set to 400 and love it. There are also adb commands to achieve this without root but not sure if they'll work on the 1+3t
Click to expand...
Click to collapse
Le DPI Changer failed on all normal settings minus the Build.Prop edit option. Confirmed that build.prop does work though!!! But same issue for me with the quick settings on OOS being misaligned, a bit shifted left. It's actually quite a bit left at 400DPI.
Any fix to this?

yep also getting the left shift. long press power you'll see the power off and reboot icons are messed up too. but that's about all I see. small price to pay. i don't mind it

Texdroider from play store ..??..

purplepenguin said:
Le DPI Changer failed on all normal settings minus the Build.Prop edit option. Confirmed that build.prop does work though!!! But same issue for me with the quick settings on OOS being misaligned, a bit shifted left. It's actually quite a bit left at 400DPI.
Any fix to this?
Click to expand...
Click to collapse
Worked for me with "Use Shell WM for setting DPI" toggled but yes, shifts the quicksettings to the left here as well. Android N-ify Xposed module doesn't change the quicksettings either so I assume they've done something to add the quick toggles..
cultofluna said:
Texdroider from play store ..??..
Click to expand...
Click to collapse
Texxdroider didn't work for me on the OnePLus 3t (worked on every other previous phone though).

kramer987 said:
yep also getting the left shift. long press power you'll see the power off and reboot icons are messed up too. but that's about all I see. small price to pay. i don't mind it
Click to expand...
Click to collapse
Power and reboot look fine for me at 400 DPI. Quick settings still on the left. Any fix?
Sent from my ONEPLUS A3000 using Tapatalk

I don't want my things to shift ?
Gonna hold off and just have everything smaller but desktop still painful lol

purplepenguin said:
Le DPI Changer failed on all normal settings minus the Build.Prop edit option. Confirmed that build.prop does work though!!! But same issue for me with the quick settings on OOS being misaligned, a bit shifted left. It's actually quite a bit left at 400DPI.
Any fix to this?
Click to expand...
Click to collapse
You would have to deodex the OPSystemUI.apk. Decompile it and modify it. Someone did it for the OP3. I can't remember if it was on XDA or the OnePlus community though.
Edit: That's what I meant when I mentioned scaling issues.
Sent from my OnePlus3T using XDA Labs