Related
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
I've just updated to Gingerbread, rooted using ZergRush and none of the existing LCD resolution changers seem to work, including Bladebuddy. All I get is a blank screen with the button lights on until I reboot when it then goes back to standard settings. Has anyone else seen this problem or have a fix?
TK
tadkingston said:
I've just updated to Gingerbread, rooted using ZergRush and none of the existing LCD resolution changers seem to work, including Bladebuddy. All I get is a blank screen with the button lights on until I reboot when it then goes back to standard settings. Has anyone else seen this problem or have a fix?
TK
Click to expand...
Click to collapse
Have you tried LCD Density Changer. It isn't free however.
Sent from my PG86100 using XDA App
LCD Density changer worked fine under Froyo but it also fails under Gingerbread.
tadkingston said:
LCD Density changer worked fine under Froyo but it also fails under Gingerbread.
Click to expand...
Click to collapse
I have Gingerbread 2.3.3 (my SGT-P1000 came with it) but I have since installed Overcome 7 Series v4.0.0 ROM (GB 2.3.3). I installed LCDDensity for Root by Elviss Kustans and it works just fine for me; however, it doesn't persist after a reset. If I didn't prefer the stock 240 density anyway, I'd use LCDDensity for Root to find my optimum density setting then change build.prop so my desired density would persist. (I wouldn't suggest just changing build.prop without using LCDDensity because if you modified it to an incompatible setting it would be more difficult to recover from.)
aznmode said:
Have you tried LCD Density Changer. It isn't free however.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Try an app from the market called LCD Resolution it also has an option for persistence after a reboot. I used it for some time and it was fine but the resolution change made market insist that my tab was incompatible with half of the apps in market, so I didn't need the hassle and went back to 240
I know most of you with think why would i want to increase the DPI of Galaxy note.. Lets just say a special person needs to use it and requires REALLY REALY LARGE fonts.. The largest possible hopefully.. is it possible to increase the DPI higher than 320? if so how?.. Most apps i found only limit to 320 DPI.. what is a safe DPI can i use higher than 320?.. Thanks alot..
I got it bumped up to 400, with the app LCD resolution.. However some apps like the dialer or sCalendar are un un useable because of the resolution, that could be solved by 3rd party apps, however, on major problem i am facing is the settings app gets FC.. Do you guys know any way to prevent this?.. if only there were 3rd party app alternative for settings.. what do you guys suggest?.. Is there a way around this like borrowing the settings apk from an SGSII or something.. any ideas?
I used Rom Toolbox and changed the DPI to 340 before and everything worked fine. Granted everything was big.
Sent from my GT-N7000 using Tapatalk 2 Beta-2
kotaro_14 said:
I used Rom Toolbox and changed the DPI to 340 before and everything worked fine. Granted everything was big.
Click to expand...
Click to collapse
I tried Rom Toolbox aswell.. anything about 320 makes the settings application FC..
Settings > Display > Screen Display > Font size. Wont that help?
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.
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.