Related
Hi, can i ask,
1. Can i just change the lcd density from build.prop if im using rooted stock 4.03 lpf? If i change to 240, any problem will occur?
2. How can i set stay awake when usb plugged in this rom?
3. Do we have crt animation? Is it samsung ruin it and have to wait them fix it?
Thx everyone
Sent from my GT-N7000 using XDA Premium HD app
Ofcourse you can ask
1. Use ROM Toolbox Lite (Free) Application from market. Now go to Performance Tab & You can tweak there the lcd density. If you change density, usually nothing as such happens. Except that some widgets which are built on particular density crash. I had weather widget which used to work only in 320 density. So now it doesn't work in 280 (which is my current). I killed the widget now
What is the worst I have faced by changing the dpi? FCs, Widget Crashes & Once a bootloop. All three can be resolved by one thing: Flash back the ROM xD
2. Another app called as smart app protector (free) is in market. I guess they have a tab called 'Screen' through which you can set LCD to be awake when a particular app is running. I hope this should resolve. Not sure on this though.
3. It depends on which ROM you are in. Yes, we do have CRT animations. I am on Asylum ICS. I do have it.
If you want to go ahead and manually enable it: http://www.freeyourandroid.com/guide/enable-crt-animation
this should help you get some idea on how to.
Well, there ain't any shortcut to the manual trigger bouy!
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.
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 there any possibility to fix the dpi in phone app? I changed screen dpi from 480 to 420, and it works great everywhere. Except in phone app. It doesn't adjust to the new settings. Why is that, and is there a way to fix it?
Best regards
You can use App Settings xposed module to set dpi per app.
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.