Database Develop

LCD Density - keeping settings through reboots

Anyone know why the screen density you set (either using LCD Density or modifying build.prop directly) doesn't keep when rebooting? TIA

What do you think the optimal density is and does it make a noticeable difference?

I like 140 - makes the screen look very nice and smooth. All apps seem to run fine, with the "stretch apps" fix.

ethanwinkley said:
I like 140 - makes the screen look very nice and smooth. All apps seem to run fine, with the "stretch apps" fix.
Click to expand...
Click to collapse
what "stretch apps" fix do you mean? are you talking about messing with the manifest file the .apk file?

post pics please!

Sorry, I couldn't remember before... spare parts is the name of the app you need to install. Then, go in there and set Compatibility Mode disabled - reboot. This stretches apps that run in less than full screen.

ethanwinkley said:
Sorry, I couldn't remember before... spare parts is the name of the app you need to install. Then, go in there and set Compatibility Mode disabled - reboot. This stretches apps that run in less than full screen.
Click to expand...
Click to collapse
Have had that running. Does not work on all apps though. I thought maybe I missed something new. Thanks though.
Sent from my HTC HD2 using XDA Premium App

[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.

DPI?

Is it just me or just everything seem really big on this phone even with the font set to small? I feel like my S5 can fit a ton more content on the screen and they are supposed to be the same resolution. I.e. my keyboard takes up almost half the screen on the X. It feels like still 720p...

km8j said:
Is it just me or just everything seem really big on this phone even with the font set to small? I feel like my S5 can fit a ton more content on the screen and they are supposed to be the same resolution. I.e. my keyboard takes up almost half the screen on the X. It feels like still 720p...
Click to expand...
Click to collapse
This is amoled technology, it looks like pixelated as u said but it have many advantage, amoled can produce much high ratio of color saturation than other screen, there are only one screen technology that can truly turn off pixel where black picture is, I mean at black colour, pixels are off, means true black you cant find any faint or visible black that is cool feeling when you see at black especially at night... This feature is my favorite.
Sent from my XT1033 using XDA Free mobile app

Mandeep148 said:
This is amoled technology, it looks like pixelated as u said but it have many advantage, amoled can produce much high ratio of color saturation than other screen, there are only one screen technology that can truly turn off pixel where black picture is, I mean at black colour, pixels are off, means true black you cant find any faint or visible black that is cool feeling when you see at black especially at night... This feature is my favorite.
Sent from my XT1033 using XDA Free mobile app
Click to expand...
Click to collapse
I dont think you understood my original question.

Yeah, the DPI is set pretty crazy on the phone. First thing I did was root and change the density to 380 instead of 480. That fixed the problem for me.

l2and said:
Yeah, the DPI is set pretty crazy on the phone. First thing I did was root and change the density to 380 instead of 480. That fixed the problem for me.
Click to expand...
Click to collapse
Which app did you use?

If you are rooted just use a File explorer to edit the build.prop.
Be aware that the Camera app will no longer function if you change the DPI

knitler said:
If you are rooted just use a File explorer to edit the build.prop.
Be aware that the Camera app will no longer function if you change the DPI
Click to expand...
Click to collapse
lol that is ridiculous - need a camera

km8j said:
lol that is ridiculous - need a camera
Click to expand...
Click to collapse
If you want to change the build.prop, you'll need to mount /system as well.
After doing that, install Xposed and used the "App Settings" module. After the restart, go to app settings and change the DPI back on the camera and moto display if you're using the active notifications to 480 (com.motorola.camera and com.motorola.motodisplay). After that, you should be good to go with everything else. If you come across another app that looks funny or doesn't load, go back to app settings and change it.

l2and said:
If you want to change the build.prop, you'll need to mount /system as well.
After doing that, install Xposed and used the "App Settings" module. After the restart, go to app settings and change the DPI back on the camera and moto display if you're using the active notifications to 480 (com.motorola.camera and com.motorola.motodisplay). After that, you should be good to go with everything else. If you come across another app that looks funny or doesn't load, go back to app settings and change it.
Click to expand...
Click to collapse
But this cans the camera?

I tried the moto X in at&t store and also noticed the icons and text being a lot bigger. I tried using nova launcher and this displayed everything normally. I think the stock google now launcher is the problem

viking2.0 said:
I tried the moto X in at&t store and also noticed the icons and text being a lot bigger. I tried using nova launcher and this displayed everything normally. I think the stock google now launcher is the problem
Click to expand...
Click to collapse
Yes, Google launcher has bigger icons that stock Android launcher.

Yes but everything is that way. Even individual apps are simply huge

Yeah they definitely should have tweaked the DPI for this phone. Most of it is fine (for me) but the icons are ridiculously large. Not going to give up the camera app to change it though.

km8j said:
But this cans the camera?
Click to expand...
Click to collapse
It will force the camera to stop working until you go into app settings using xposed and set the DPI to the camera back to 480. Once you do that, the camera will work just fine.

......

Hmmm anyone else notice that the active display time and lock icon is all screwed up after changing dpi

Changing the DPI on active display app works

The annoying part is that Moto Display is only compatible with the stock DPI. I went from 480 to 400 today and everything is fine besides that and stock camera app crashes on opening. However, I use Google Camera so meh.

Yup, if you need your active display back. Change com.motorola.display back to 480.

There are a couple apps in the play store that will change the DPI for you.. DPI changer, texdroider DPI. Both work great. As mentioned, use the Xposed module "app settings" to change any app that is acting up, back to stock DPI. I've got the VZW variant, I may have to make an exchange to the pure edition. I myself prefer a much smaller DPI, as well as hiding my nav keys and enabling pie via LMT. Not to mention the Xposed module "Tinted Status Bar" which improves the look of the interface dramatically.

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