[Tip] How to change DPI settings on NST - Nook Touch General

Protip :
tutorial on howto increase Nook's "resolution" by changing /system/build.prop
http://forum.xda-developers.com/showthread.php?t=823522

Can someone do a compare?
I scanned the thread and performed the following actions:
First I used the "test" commands to experiment with settings. I discovered that I liked a density setting of 133 best.
# setprop qemu.sf.lcd_density 133
# busybox killall system_server
So I modified my /system/build.prop by changing the line
#ro.sf.lcd_density=240
to
ro.sf.lcd_density=133
and rebooted.
So, everything is certainly smaller, but as I have only one NST, I cannot determine if I think the text is sharper because I can't do a side-by-side comparison. So, is there somebody out there with two NSTs who is willing to make this change to one of them and then do a side-by-side comparison and report back?

David0226 said:
So, everything is certainly smaller, but as I have only one NST, I cannot determine if I think the text is sharper because I can't do a side-by-side comparison. So, is there somebody out there with two NSTs who is willing to make this change to one of them and then do a side-by-side comparison and report back?
Click to expand...
Click to collapse
You can do few screenshots and compare them side-by-side.

screenshots?
how do you do a screnshot on nook? , ( for those of us that don't know) , thanks

steelworker said:
how do you do a screnshot on nook? , ( for those of us that don't know) , thanks
Click to expand...
Click to collapse
dude...wtf?
Just type "screenshot android" into your search engine.
I use 'ddms' via adb.
http://www.makeuseof.com/tag/how-to-capture-screenshots-with-your-android-mobile-phone/

No real difference
Here are two screen shots I took. (Thanks for the link osowiecki). The first was taken with the density set to 160 (standard) and the second with it set to 120. There is some difference in the size of the header and footer lines, but I see no real difference in the size of the book text. Setting the density to 120 does allow the standard B&N library app to display nine titles on one screen instead of six. Otherwise I see no difference when using the standard B&N reader.
I did these tests using the LCDDensity app.

Here are screenshots of the library app in each density ...

I can't confirm any changes for text based books, but it definitely helps with converted comics. No idea why the screenshots are green, used "screenshot" tool from within adb shell. Tried with default DPI, 133, 120, and also pulled the image from the unconverted CBR for comparison.

neoman4426 said:
No idea why the screenshots are green ...
Click to expand...
Click to collapse
My screenshots taken with the screenshot tool in ADB shell were green also. You will get better results by following the procedure outlined in the link in osowiecki's post.

Was the first thing I tried, couldn't get it to recognize my device. I'm not sure if it's a wired ADB only thing, or a "doesn't work on Linux for some reason" thing or what. ah well, I kind of like the green look

Related

Reduce LCD Density Setting in Build.Prop For Higher Res Look

Update: I installed Spare Parts, as mentioned by appelflap later in this thread, disabled compatibility mode, then followed the directions in this post, and I have a working status bar, good resolution, and in a better place in most cases.
Update: Check out appelflap's APK that makes this whole process a lot easier. Note that some users are reporting a black screen after using the file, so be prepared in case you have to use adb shell to put your original build.prop file in place. If you do not want to risk it, Notepad++ makes for an easy edit once you pull the file to your PC. If you have fallen prey to the black screen problem, lpsi2000 found a solution that uses an update.zip approach.
In the /system/build.prop file, I changed this line:
ro.sf.lcd_density=240
Click to expand...
Click to collapse
to this:
ro.sf.lcd_density=160
Click to expand...
Click to collapse
This is a setting that Google normally recommends if you have a larger screen (like Dell's Streak), but the side effect of using it on the 800x480 screen of the captivate is that everything is smaller.
With this, menus have smaller text (more options on screen), in-app buttons are smaller, and it just has the same feeling of being on a PC and moving from a low resolution LCD monitor to a high resolution LCD monitor.
There are a couple of glitches so far. It appears that some apps want to render in the previous resolution. For example, Skyfire and Root Explorer would not render in full screen, Android Market renders full screen but the search is in the old resolution, and the status bar is slightly garbled but still usable. Also, the dial pad is smaller (as you would expect showing a picture made for a low res display on a high res display) but the rest of the phone app is fine. The camera app fills the screen just like it did before.
With this setting, I really feel like I'm getting some use out of the high resolution display on this phone.
The apps that are rending in the low res mode of the original setting seem to be pulling their setting from somewhere else. Does anybody have an idea where that setting may be? After trying this, I can't imagine going back to what almost seems like an "accessibility mode".
I've only used LauncherPro with this setting, so no idea how the Samsung launcher looks. I attached screenshots of what some things look like. I can put some game screenshots in another post if anybody is interested. 3D games look sharper to me in this mode, but I have no scientific way of testing if it is because it is rendering in higher res or if my own excitement is clouding my vision.
Update: I suspect the missing setting is found in the /system.prop file. It has the ro.sf.lcd_density=240 setting. I tried changing it to 160, but it keeps going back to 240 after a reboot of the phone. Any ideas how to make this stick?
Warning:: TWLauncher does not play well with these changes. Make sure to have LauncherPro set up as your default launcher before trying this.
So you're pulling it off the cappy then editing putting back....do you need to change permissions?
The way that I pulled it out to edit on my PC was with this:
adb pull /system/build.prop
Click to expand...
Click to collapse
You will need root access in order to put the changed file back. What I did was
adb push build.prop /sdcard
Click to expand...
Click to collapse
I then used Root Explorer to copy the build.prop from /sdcard to /system. I didn't change any permissions other than just copying the file and rebooting.
Wow man that's pretty cool, it's got a few little glitches but nothing serious. One of the things I wish I could so though is make my Beautiful widgets clock go all the way across the top. I'm not sure if this is a placebo effect (I donno if that's possible since this should have nothing to do with it) but it seems like my soft buttons respond more often....I'm prolly nuts but it doesn't seem like I need to push....push...%$^&*^ PUSH.....and back to home.
I'm hoping someone will have a great idea on how to keep the /system.prop file from updating itself on boot. I'm thinking that if we can get the ro.sf.lcd_density=240 setting to stick to 160 after a reboot, that might fix the few instances where an app won't render full screen.
I've tried chmod 666 system.prop and chown root.root system.prop but it still gets returned to normal after rebooting.
Wow I'm excited to test this out. Couldn't we get someone to code this into the startup script theoretically?
Edit: Tried it out. Really really nice. If only we could get the rest of the apps to work the right way... right res.
One thing also that's cool is in launcherpro you can add more columns to the drawer so you can fit an insane amount of apps on screen.
Sent from my GT-I9000 using Tapatalk
Also out of curiosity, have you tried any other DPI like 200? Our does it need to be either or to keep it proportional?
Sent from my GT-I9000 using Tapatalk
Lower resolution works as well. Here are some comparisons. 160, 240, 320. 200, since someone asked.
wow, this could REALLY be nice.. Just need to fix everything, but like others have said no HUGE things that cause it to be unusable, but I would love to see everything correct.
Also out of curiosity, have you tried any other DPI like 200? Our does it need to be either or to keep it proportional?
Click to expand...
Click to collapse
No, the only reason I chose 160 was because it is listed as "MDPI" in the Android SDK. (We were using "HDPI" with 240.)
I only figured it was a "supported" number, so I started there, but most any number will do. You can see a chart where it recommends certain numbers based on resolution or screen size, but I think these recommendations are to cover everybody, which includes folks who can't (easily) see small text or icons.
The chart that shows Google's recommendations is here.
reading around, it seems that the files need to be put back to read only.
phlunkie said:
reading around, it seems that the files need to be put back to read only.
Click to expand...
Click to collapse
I thought so also, but you don't need to. All I'm doing is copying it with root explorer to sd, then using astro to edit the line and root explorer to put it back. Reboot and your GTG. Everything works fine.
Sent from my GT-I9000 using Tapatalk
So the settings are sticking after a reboot? I will have to try this when I get home.
Sent from my SAMSUNG-SGH-I897 using XDA App
phlunkie said:
So the settings are sticking after a reboot? I will have to try this when I get home.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
After I edited the build.prop and the build.prop.bak files in the /system directory it works fine after reboot. A problem that I have is that TouchWiz force closes after editing the files.
Using this on SGS made:
- notification bar unreadable (kindof text overlap@240160 setting).
- Launcher pro works.
- Market scales nice.
- big list's buttons are now nice
//edit: changed to 200 - seems to be great compromise.
@up
Bad practice. U shouldnt have edited ur build.prop.bak file, becouse it is actually a backup of original build.prop, made by RootExplorer (guess). In case u want to revert to original content, u just delete edited file and delete .bak from this one.
xan said:
Using this on SGS made:
- notification bar unreadable (kindof text [email protected] setting).
- Launcher pro works.
- Market scales nice.
- big list's buttons are now nice
//edit: changed to 200 - seems to be great compromise.
@up
Bad practice. U shouldnt have edited ur build.prop.bak file, becouse it is actually a backup of original build.prop, made by RootExplorer (guess). In case u want to revert to original content, u just delete edited file and delete .bak from this one.
Click to expand...
Click to collapse
Any pics? Love to see the difference.
Sent from my Nexus One using XDA App
Here they are.
I'm trying to figure out how to make those other applications also use the full screen when at a different resolution. I tried the method here
http://forum.xda-developers.com/showthread.php?t=739647
to run a script that rewrites the /system.prop file, and it didn't fix anything, so either that is not where the applications are getting the property from, or we need to rewrite the file earlier in the boot process.
Are you sure those apps are graphically able to scale? Maybe touchwiz does not take scaling into account (at least with native apps) because the screens are all 4 inches.

Atrix Screen Color profile

Hello,
I`m new on this device and just make a color profile that seems to be acceptable.
It`s not perfect but usefull to simulate in photoshop how an image will looks like on the Atrix. It`s good for themers.
Just download attached file and put the .icc file in windows\system32\spool\drivers\color. Then in photoshop : CTRL-Y, go to menu display/image format and choose the profile. Also tick Keep RVB numbers.
As you can see in the attached picture, atrix screen is not able to reproduce all the sRGB color space, (very) bad screen ...
Note that if your monitor is not correctly calibrated this will not be useful.
Enjoy.
That's a very spikey gamut. I just made my own using a Huey and Argyll on Linux. I ran an X server on my Atrix and had the 'dispread' program display on it. My result is much more like sRGB, just transposed a little in the green direction.
I've attached the profile I made and screen shots of 'iccexamin' displaying the gamut of your profile and mine.
IanTester said:
That's a very spikey gamut. I just made my own using a Huey and Argyll on Linux. I ran an X server on my Atrix and had the 'dispread' program display on it. My result is much more like sRGB, just transposed a little in the green direction.
I've attached the profile I made and screen shots of 'iccexamin' displaying the gamut of your profile and mine.
Click to expand...
Click to collapse
Thanks for that, I didn`t know about this linux soft and will try later.
What sensor are you using (mind is spyder3) ? Did you run a calibrate or profile only process ?
My first impressiom is that my profile shows me a better result in photoshop. I will test it with other images.
Calibration subject is a headache subject ...
A new and better profile attached.
@IanTester, I think you have a problem in your calibration process.
an other one. seems slightly better ...
What exactly do you mean by "calibration"? The documentation for Argyll says that calibration of a display means "1) Changing controls or internal settings that it has. 2) Applying curves to its color channels."
I've made a second profile using the same data as before but using a different "algorithm" argument with colprof. The previous profile used '-as', which generated a "shaper + matrix", this one used "-aX" to generate "XYZ cLUT + matrix".
I understand the basics of colour management but don't really know much about generating profiles. The dry and error-prone documentation for Argyll doesn't help much. Basically I have a shell script that I run to profile my monitor and it seems to work with the few colour-managed programs I have. Any help would be welcome.
IanTester said:
What exactly do you mean by "calibration"? The documentation for Argyll says that calibration of a display means "1) Changing controls or internal settings that it has. 2) Applying curves to its color channels."
I've made a second profile using the same data as before but using a different "algorithm" argument with colprof. The previous profile used '-as', which generated a "shaper + matrix", this one used "-aX" to generate "XYZ cLUT + matrix".
I understand the basics of colour management but don't really know much about generating profiles. The dry and error-prone documentation for Argyll doesn't help much. Basically I have a shell script that I run to profile my monitor and it seems to work with the few colour-managed programs I have. Any help would be welcome.
Click to expand...
Click to collapse
Hello,
I just installed dispcalGUI on my Fedora partition. It seems to be a good calibration soft, easier to use than argyll ...
Then I tried to configure a remote desktop via VNC but it`s too slow. The image generated on linux arrives to late on the android screen ... :laugh:
So I need your help too. What apps are you using to have a copy of your linux desktop on your phone ?
There are usually two modes when using a colorimeter : calibration & caracterization. Wee need the second one as it is just to use the profile to simulate the atrix screen. Calibration is to be loaded into the graphic card and correct as well as possible the screen colors. I don`t know any app able to load a color profile in android system, unfortunately.
Is it more clear ? Sorry for english ...
Can any one tell me of Software for windows that would allow me to output my screen via HDMI? I have the hardware but no available Linux terminal to run it.
Sent from my MB860 using xda premium
There's no way to apply a color profile system wide in Android?
There kinda is. If you're on CM, you can go to Settings > CyanogenMod settings > Interface > Render effect. There you'll find a predefined set of somethings that can loosely be called color profiles.
Oh yeah I almost forgot about that one.

[Mod][MotoActv] Tweaks+Mods Pack!

ive gathered some things and did a few tests on my MotoActv since ive gotten it and did some tweaks here and there and i added the following features to mine and put them into a flashable zip for u all
-init.d support (plus some scripts to make it faster then ever) (tested and working (makes two files in sdcard on boot to show it) (picks and chooses when to work now for some reason, so i put an app i made that loads scripts when onCreate()'d and sometimes on-boot)
-Viper4Android sound system (only works for bluetooth headsets if enabled, but its sounds better with good settings)(see credits)
-OpenVPN (idk if theres a use for us but i added the required files (no GUI)
-UsbEnabler.apk (see credits)
-Adblock host (hopefully it works i havent been able to test yet)
-lag-free entropy (so far seems to work, as im not lagging switching launchers anymore)
-MotoActv DPI (my own personall app i made for Changing dpi from 90,100, and stock(120)
-Sqlite3 + init.d sqlite3 optimizer
-Busybox Run-parts (for init.d, still picks and chooses when to work)
-100 Dpi When-Flashed (can be changed back to stock with the MotoActv DPI app i made)
-minor-to-major tweaks from init.d scripts and other methods
-DalvikCache2Sd (not sure if it truly tested working, but i do have a tiny bit more space+no lag like other 2SD methods
soon to be added:
I take bare minimum credit for these, i mostly used this personal zip for when i update my MotoActv's rom, this can be universal for other androids, but it was initially made to the MotoActv watch running custom roms
Credits to give:
(will edit when i get forum post urls and OP's names)
Viper4Android:
OP = @zhuhang
Thread = http://forum.xda-developers.com/showthread.php?t=2191223
UsbEnabler:
OP = @fagalto
Thread = http://forum.xda-developers.com/showthread.php?t=2396138
init.d scripts, OpenVpn, Entropy:
i extracted from the rom on my phone so idk where they originally came from
Init.d App(unreleased w/o mod_pack)+MotoActv DPI:
OP:me @jkok for developing and publishing
Thread (MotoActv DPI):
http://forum.xda-developers.com/showthread.php?t=2435370
Gallery+Live Wallapapers:
Google, But @ClearD for giving me the zip with the script+apks
the zip:
i put together, made the script, signed+released for general use for others:
future credits will be made when i add more things.
Download:
Reusable Download Link
Awesome!
Here's a zip (with changed mounting, again; this time using the exact same one that I use for the rom) of the Live Wallpapers + Gallery apks. Hopefully, this one will work fine.
ClearD said:
Awesome!
Here's a zip (with changed mounting, again; this time using the exact same one that I use for the rom) of the Live Wallpapers + Gallery apks. Hopefully, this one will work fine.
Click to expand...
Click to collapse
well thanks ClearD i can do the script just fine, some of the mountpoints are universal like what i use
umount("/system");
or
run_program("xbin/mount", "/system"); (might be wrong on the xbin part, just going by memory
run_program("xbin/umount", "/system");
but the resolution on the galery on your motoactv rom is too big for it, it resizes dont get me wrong, but it needs to do a single horizontal row cause if u overscroll to the farest right u see there is second or more rows going down, imma fine the sourcecode for the galery2.apk, and make a single-row version when i find it =)
jkok said:
well thanks ClearD i can do the script just fine, some of the mountpoints are universal like what i use
umount("/system");
or
run_program("xbin/mount", "/system"); (might be wrong on the xbin part, just going by memory
run_program("xbin/umount", "/system");
but the resolution on the galery on your motoactv rom is too big for it, it resizes dont get me wrong, but it needs to do a single horizontal row cause if u overscroll to the farest right u see there is second or more rows going down, imma fine the sourcecode for the galery2.apk, and make a single-row version when i find it =)
Click to expand...
Click to collapse
Ah, sweet! That sounds good. I couldn't get it to mount properly any other way so far, but it could have been something as simple as a typo. If it does actually work, then I might use that in the future. That's the one I tried with the last iteration.
ClearD said:
Ah, sweet! That sounds good. I couldn't get it to mount properly any other way so far, but it could have been something as simple as a typo. If it does actually work, then I might use that in the future.
Click to expand...
Click to collapse
the universal way i do my scripts is
mount("ext3", "MTD", "system", "/system");
unmount("/system");
and it always seemed to work for me, so thats why i call it universal anyways
but the other ways i posted seemed to work for me when i tried em, i just used this way cause it was in a zip for a motoactv rom (i think it was yours or the battery mod)
Opps! i was wrong, its not
run_program("xbin/mount", "system");
its
run_program("sbin/mount", "system");
lol i had to check my other mod zips lol
jkok said:
the universal way i do my scripts is
mount("ext3", "MTD", "system", "/system");
unmount("/system");
and it always seemed to work for me, so thats why i call it universal anyways
but the other ways i posted seemed to work for me when i tried em, i just used this way cause it was in a zip for a motoactv rom (i think it was yours or the battery mod)
Click to expand...
Click to collapse
Lol no doubt, I went through the same thing with the battery mod, looking over and over for one that worked better. I'd prefer the xbin/mount method, but for some reason, it was hit and miss on my end with end users. Not sure why, unless busybox wasn't set up right somehow.
Just updated the mod_pack with more features!
Sorry but the only thing i havent really been able to fix that well way the init.d it seemed to workwhen i first released this mod_pack, but it seems to pick+choose when to work, so i added 2 other methods for init.d (one of which is an app i made, yet to release that loads the scripts when the app is onCreate()'d and sometimes on-boot when SuperUser allows it)
but there are some great new features that WILL work, along with some of my own personall apps, tweaks, and clock faces =)
Again: this mod_pack is meant for MotoActv's running a custom rom, and Not meant for AOSP based MotoActv Roms
Tested and confirmed working (except init.d that picks and chooses) on @ClearD 's ClearRom 1.2.0 T2 (and my own personal (un)Official 1.2.1 T1 i made for him)
For some reason all of the mods are being denied superuser, any ideas? I am setup to automatically allow all requests
Edit: Installed SuperSU and my problem has been resolved
Has there been anything definitive about the entropy thing? The last consensus I saw by anyone not potentially making money from a fix is that at best it's just forcing the processor to stay awake, decreasing battery life.
Saeviomage said:
Has there been anything definitive about the entropy thing? The last consensus I saw by anyone not potentially making money from a fix is that at best it's just forcing the processor to stay awake, decreasing battery life.
Click to expand...
Click to collapse
well by my testing before my motoactv went kaput it didnt affect the battery any noticeable amount, but it did solve some-to-all of the lag from switching launchers on the ClearDroid 1.2.0_T2 rom, i cannot make or update this mod-pack anymore because i dont like submitting a mod-pack that is untested, and since my motoactv went kaput i cannot test it anymore but if u have any questions feel free to ask and ill try to answer the best i can for now =)
not sure what is the right place to ask this... How does DPI change work? Does it mean the "system" screen resolution is changed? Let say, what is the "Full Screen" resolutions in 90/100/stock(120?) dpi's??? Where to read about it if it is not so simple???
yuiop0 said:
not sure what is the right place to ask this... How does DPI change work? Does it mean the "system" screen resolution is changed? Let say, what is the "Full Screen" resolutions in 90/100/stock(120?) dpi's??? Where to read about it if it is not so simple???
Click to expand...
Click to collapse
Dont worry its ok to ask here, since i made this app after all , i might as well answer how this works =)
well to make it shorter and more understandable to alot more people:
Yes, it is the overall resolution of the screen:
DPI (dots-per-inch) is more like the size range to view images/displays/graphics on ANY of your LCD/LED Screened devices including androids, I-craps(iPhones/ipods )(sorry i dont like apple too much, bad excperiences, dont get offended if u like it as its just my personal preferences), blackberries, windows phones, TV's, computer Monitors, etc:
the stock setting for HDPI phones (the more common screened ones now) is 240, say if u lower it, the images get smaller, if u raise it it gets bigger (maybe even too big for the screen to handle correctly);
but since the MOTOACTV has a smaller screen as u can obviously see (if u have one that is, as i dont know others posesions =P), its default for the stock rom is 120 (1/2 of HDPI if u notice the math) and 120 is as big as it should go cause say for example 130 dpi, it makes the images slightly too big for the screen, but slightly smaller values (100 is usually smallest for alot of peoples eyes for the watch, but for some people like me that like them a tad smaller for sharp small details, i put 90), but literally the smaller the amounts go, the smaller the images(and possible errors, i.e ES File Explorer crashes below 120 DPI untill u restore to 120+) , and for the smaller screen we have u cant go too big (121+), or too small (>=90-100), so i put those details of 90,100,and 120 (no 110 as it doesnt make too much of a difference by what i saw)
but there is (a) way(s) to check what DPI u are at currently:
METHOD1.check your build.prop file under /system/build.prop by doin these ADB commands (**new line is a new command**) (commands stop at <EOC>)
adb remount
adb pull /system/build.prop
<EOC>
check somewhere using notepad for this line (NOTE: if u want to edit to push to your device use notepad++, search for it on google if u dont already have it, as regular notepad corrupts it)
ro.sf.lcd_density=(your current DPI is displayed here)
if u decide to change it that way and want to apply it MAKE A BACKUP!!!, then change it in notepad++ and save it, then goto the directory it is in in the terminal/command prompt and do (**new line is a new command**) (commands stop at <EOC>)
adb remount
adb push build.prop /system/build.prop
adb shell chmod 644 /system/app/build.prop
adb reboot
<EOC>
METHOD 2: Any DPI Checking/changer app (there might be some good free ones, i.e. pimpmyrom has a density changer (DPI changer) that works the same as mine i think, it changes the DPI value in the Build.prop and it WILL stick over reboots, just not rom flashes (as it overwrites it and my change)
if u want to see how i did this(if u understand java/android applications) u can check This app on my github, its acually fairly easy and lightweight compared to others
https://github.com/kittleapps/MotoActvDPI
and the exact class that does this (using a library), is this
https://github.com/kittleapps/MotoA...om/KittleApps/app/motoactvdpi/MainScreen.java
as u can see it changes it to 90,100, and 120 quite simply (with root access of course)
and sorry for this long message but it explains not only your question, but possible future questions on how this app works =)
jkok said:
but there is (a) way(s) to check what DPI u are at currently:
METHOD1.check your build.prop file under /system/build.prop by doin these ADB commands (**new line is a new command**) (commands stop at <EOC>)
adb remount
adb pull /system/build.prop
<EOC>
check somewhere using notepad for this line (NOTE: if u want to edit to push to your device use notepad++, search for it on google if u dont already have it, as regular notepad corrupts it)
ro.sf.lcd_density=(your current DPI is displayed here)
if u decide to change it that way and want to apply it MAKE A BACKUP!!!, then change it in notepad++ and save it, then goto the directory it is in in the terminal/command prompt and do (**new line is a new command**) (commands stop at <EOC>)
adb remount
adb push build.prop /system/build.prop
adb shell chmod 644 /system/app/build.prop
adb reboot
<EOC>
METHOD 2: Any DPI Checking/changer app (there might be some good free ones, i.e. pimpmyrom has a density changer (DPI changer) that works the same as mine i think, it changes the DPI value in the Build.prop and it WILL stick over reboots, just not rom flashes (as it overwrites it and my change)
if u want to see how i did this(if u understand java/android applications) u can check This app on my github, its acually fairly easy and lightweight compared to others
https://github.com/kittleapps/MotoActvDPI
and the exact class that does this (using a library), is this
https://github.com/kittleapps/MotoA...om/KittleApps/app/motoactvdpi/MainScreen.java
as u can see it changes it to 90,100, and 120 quite simply (with root access of course)
and sorry for this long message but it explains not only your question, but possible future questions on how this app works =)
Click to expand...
Click to collapse
There is a 3rd method as well.
Method 3 = Install the Xposed framework and app settings apk found here: http://forum.xda-developers.com/showpost.php?p=44034334&postcount=2315
This will allow per app DPI settings rather than one global setting.
In order for this to work correctly, make sure you move both the Xposed Installer and App Settings apks to the phone after installation and reboot as well.
I like running some apps at 120, others at 100, 90, and even 70 w/ modded font sizes and this allows for all those combinations.
Artimis said:
There is a 3rd method as well.
Method 3 = Install the Xposed framework and app settings apk found here: http://forum.xda-developers.com/showpost.php?p=44034334&postcount=2315
This will allow per app DPI settings rather than one global setting.
In order for this to work correctly, make sure you move both the Xposed Installer and App Settings apks to the phone after installation and reboot as well.
I like running some apps at 120, others at 100, 90, and even 70 w/ modded font sizes and this allows for all those combinations.
Click to expand...
Click to collapse
that is true, but i didnt include that cause i was seeing people having issues with xposed-framework on the MOTOACTV on a few threads, and tbh i made this app+inlcuded in modpack before that method was usable for MOTOACTV (or gingerbread in general), thats kinda why i havent updated the modpack in a while (including the fact mine is damaged for some time now), i managed to fix mine up somewhat but it only turns on the backlight and no button combos work but to turn on backlight XD, so no fastboot recovery, boot-to-system, or quickboot :S and since the device is discontinued i cant get a real fix XD, so unless i personally test the things i put in this modpack, i cant make new versions to distribute for device stability reasons (e.g. in case it is corrupted and breaks someone elses device, as it is un-tested, since i dont have a device to test it on)
jkok said:
that is true, but i didnt include that cause i was seeing people having issues with xposed-framework on the MOTOACTV on a few threads, and tbh i made this app+inlcuded in modpack before that method was usable for MOTOACTV (or gingerbread in general), thats kinda why i havent updated the modpack in a while (including the fact mine is damaged for some time now), i managed to fix mine up somewhat but it only turns on the backlight and no button combos work but to turn on backlight XD, so no fastboot recovery, boot-to-system, or quickboot :S and since the device is discontinued i cant get a real fix XD, so unless i personally test the things i put in this modpack, i cant make new versions to distribute for device stability reasons (e.g. in case it is corrupted and breaks someone elses device, as it is un-tested, since i dont have a device to test it on)
Click to expand...
Click to collapse
Sorry to hear that. I personally haven't loaded the mod pack yet. Was looking into cherry picking parts of it when I saw the question on DPI. I thought it was a general question.
In any case, I personally have not had any issues with Xposed on my actv. What issues have you heard about?
jkok - thank you so much for the explanations. It's become more clear for me but I'm not so experienced in android/development so I have some more questions related to dpi on actv.
My practical interest in this is - to investigate the possibility to run igo primo on this device (for route planning/voice navigation) because I'm not happy with Motorola map application (walk/run outdoor mode). I have some ideas how to modify igo's data.zip for specific screen resolutions (at least I managed to make "custom 640x480" data.zip for primo 2.4.0 WM for htc DIAM100) but I need to know what is the "Full Screen" resoluton (for igo and other applications) in different dpi modes on actv (ClearD 1.2.0 rom currently, just in case). Is it the same - 176x220 for all dpi's (I don't think so as the size of icons/fonts/etc are different). So, the real question is - what is the screen resolution I need to set up in data.zip to try to run igo primo on motoactv. To know that I need to understand if dpi change affects the "full screen resolution" in motoactv/android. And, once more, sorry if the question looks stupid (already explained etc) as I'm not developer...
yuiop0 said:
jkok - thank you so much for the explanations. It's become more clear for me but I'm not so experienced in android/development so I have some more questions related to dpi on actv.
My practical interest in this is - to investigate the possibility to run igo primo on this device (for route planning/voice navigation) because I'm not happy with Motorola map application (walk/run outdoor mode). I have some ideas how to modify igo's data.zip for specific screen resolutions (at least I managed to make "custom 640x480" data.zip for primo 2.4.0 WM for htc DIAM100) but I need to know what is the "Full Screen" resoluton (for igo and other applications) in different dpi modes on actv (ClearD 1.2.0 rom currently, just in case). Is it the same - 176x220 for all dpi's (I don't think so as the size of icons/fonts/etc are different). So, the real question is - what is the screen resolution I need to set up in data.zip to try to run igo primo on motoactv. To know that I need to understand if dpi change affects the "full screen resolution" in motoactv/android. And, once more, sorry if the question looks stupid (already explained etc) as I'm not developer...
Click to expand...
Click to collapse
well im not familiar with those apps, as for the resolutions/dpi im not sure of that :S it could possible be found on google, as basic hdpi (240 dpi), usually is around 480*800, and 120 dpi is like the motoactv 220*176, so i guess there isnt a ratio it follows, just sizing of images maybee :S, but i also just became a developer more resently withing the last 2 years so im still learning

Changing the resolution of Default to 2K without root

I tried the adb Shell to change the Size of default Screen size from 1080 to 2k. This i did with Mac. My phone is not rooted.
Open terminal
adb shell
Then type
wm size 1440x2560
and to go back to default use
wm size 1080x1920
It works with reboot as well.
If we change the density from 480 - 640 using WM density 640. Icons looks very small. I think by default Sony doesn't supply icons for that density. Not sure if someone already said this. You can issue the same using mobile terminal emulator as well. You can download that app from Play Store.
I am not able to take screenshot as i get "Couldn't capture screenshot. Content may be protected or the memory may be full."
Try and let me know. If it is already mentioned here. Apology. Please close this
Francis.
With Nova Launcher. With the below settings. The Phone looks awesome.
wm size 2160x3840
wm density 800
The Phone looks awesome. But with default launcher icons are so small.
sweeet i am watching this thread. thx alot
This doesn't work with the mobile terminal with unrooted Phone. Just an update. You can use both Mac and Windows CMD for doing this.
what is the default pixel density of xperia z5 premium??
480
fesar said:
I tried the adb Shell to change the Size of default Screen size from 1080 to 2k. This i did with Mac. My phone is not rooted.
Open terminal
adb shell
Then type
wm size 1440x2560
and to go back to default use
wm size 1080x1920
It works with reboot as well.
If we change the density from 480 - 640 using WM density 640. Icons looks very small. I think by default Sony doesn't supply icons for that density. Not sure if someone already said this. You can issue the same using mobile terminal emulator as well. You can download that app from Play Store.
I am not able to take screenshot as i get "Couldn't capture screenshot. Content may be protected or the memory may be full."
Try and let me know. If it is already mentioned here. Apology. Please close this
Francis.
Click to expand...
Click to collapse
My apologies for being a complete noob but could you give me an exact procedure for how to do this on Windows? I desperate need to change the awful DPI on this otherwise perfect phone.
@Traczyc
Download android sdk tools open up adb shell enter the commands hes given and done. Its all the same on windows.
Btw It looks great thanks fesar
sfex3best said:
@Traczyc
Download android sdk tools open up adb shell enter the commands hes given and done. Its all the same on windows.
Btw It looks great thanks fesar
Click to expand...
Click to collapse
Thanks, I managed to figure it out and I can confirm that it works! This is just so awesome! It's just too bad that the screenshot function doesn't work on any resolution above 1080P.
I got also one more question. When you change the resolution using ADB, does the phone actually start to output content in that resolution or is it just an illusion?
Traczyk said:
Thanks, I managed to figure it out and I can confirm that it works! This is just so awesome! It's just too bad that the screenshot function doesn't work on any resolution above 1080P.
I got also one more question. When you change the resolution using ADB, does the phone actually start to output content in that resolution or is it just an illusion?
Click to expand...
Click to collapse
2k resolution on YouTube becomes available, so I guess it works
Edit: One more thing, if everything has this weird scaling a reboot usually fixes this.
Happy new year!
I confirmed the change with some screen resolution apps and in YouTube and it both confirms it as 2k. I hope Sony makes this as permanent and with an option for real 4k as well.
fesar said:
I confirmed the change with some screen resolution apps and in YouTube and it both confirms it as 2k. I hope Sony makes this as permanent and with an option for real 4k as well.
Click to expand...
Click to collapse
Didn't you say you were running it in 4K now?
fesar said:
With Nova Launcher. With the below settings. The Phone looks awesome.
wm size 2160x3840
wm density 800
The Phone looks awesome. But with default launcher icons are so small.
Click to expand...
Click to collapse
Sent from my E6853 using XDA Free mobile app
"wm size" only emulates resolution, so real resolution is still FHD and 4K upscaling won't work when you are not watching image/video.
Real resolution is controlled by kernel:
https://github.com/AndroPlus-org/an...rm/boot/dts/qcom/dsi-panel-satsuki.dtsi#L3025
AndroPlus said:
"wm size" only emulates resolution, so real resolution is still FHD and 4K upscaling won't work when you are not watching image/video.
Real resolution is controlled by kernel:
https://github.com/AndroPlus-org/an...rm/boot/dts/qcom/dsi-panel-satsuki.dtsi#L3025
Click to expand...
Click to collapse
Yes agreed. But I prefer having my resolution on the visual screen to be better than 1080p.
fesar said:
Yes agreed. But I prefer having my resolution on the visual screen to be better than 1080p.
Click to expand...
Click to collapse
Tks
With Nova Launcher prime and Tesla Unread With the below settings.
The Phone looks awesome.
wm size 2160x3840
wm density 800
but i also have the screenshots problems? I have also tried to delete or rename Pictures folder but problem still remain.
Any solution?
Tks
jumbonosich said:
Tks
With Nova Launcher prime and Tesla Unread With the below settings.
The Phone looks awesome.
wm size 2160x3840
wm density 800
but i also have the screenshots problems? I have also tried to delete or rename Pictures folder but problem still remain.
Any solution?
Tks
Click to expand...
Click to collapse
I'm actually new to using adb. Does anyone mind doing a step by step guide on how to do this? I would greatly appreciate your help and time.
Any screen shots and evidence, like the youtube app.
is it possible to change the dpi of navigation bar thru adb shell?
nvm
image hosting 10mb limit
imgupload

HOWTO: Reduce screen resolution, preserve battery life enhance framrate

I thought it would be good to have this in one seperate thread. The PRIV has a great qHD display but I don't think qHD resolutions make any sense on mobile devices. Problems like framedrops, low framerates, heat and battery draining can be the result.
Luckily, although the PRIV is unrootable, the commands wm density and wm size still work when applied through adb shell with USB debugging turned on. (If you don't know how to do this, there are many tutorials out there).
The PRIV has a native resolution of 2560x1440 @ 560ppi. We will change this to 1920x1080 @ 420ppi. To do so enter the following two lines:
Code:
adb shell wm size 1080y1920
adb shell wm density 420
Then reboot your device manually or simply enter:
Code:
adb reboot
To reset everything to normal enter:
Code:
adb shell wm size reset
adb shell wm density reset
Then reboot.
Hope this is helpful to you. Now I really like my PRIV and get stellar battery life and SoT:
WORKING ! thank You for that
After applying and rebooting, only a third of the screen was filled by the UI in the center and was very small. The rest was blank, not even navigation displayed.
Tried on the Priv bought from Blackberry direct on the latest update.
Calnyx said:
After applying and rebooting, only a third of the screen was filled by the UI in the center and was very small. The rest was blank, not even navigation displayed.
Tried on the Priv bought from Blackberry direct on the latest update.
Click to expand...
Click to collapse
Worked for me.
did execute these commands in this order on my computer with adb:
adb shell wm size 1920x1080
adb shell wm density 420
adb reboot
Done.
its wrong because to put it correct should be
adb shell wm size 1080x1920 ( not 1920x1080 )
Been at 1080p for the past couple of months and haven't had any issues
Used this: http://forum.xda-developers.com/note-4-verizon/general/dpi-resolution-changer-program-root-t3217199
Sent from my STV100-3 using XDA-Developers mobile app
Working
Nice, great man
Rotkaeqpchen said:
...
The PRIV has a native resolution of 2560x1440 @ 560ppi. We will change this to 1920x1080 @ 420ppi. To do so enter the following two lines:
Code:
adb shell wm size 1920x1080
adb shell wm density 420
...
Click to expand...
Click to collapse
Setting a higher density enlarges the fonts for better readability (which might be important for people in their 40ies ). I experienced setting values 450 or 480 is still OK. Higher values hide some things from the productivity bar.
Unfortunately, picture password is not working any more.
It seems that the display needs about 150 mAh per hour with the reduced resolution. Can someone check the initial energy consumtion to quantify the gain (if any).
Thanks
Here is a screenshot of the current energy consumption.
I will try out the commands later.
For comparison:
Time on: 2h 4m 25s
Computed power use: 436 mAh
With default resolution.
Anyone know how to correct the corrupt BBM icon in the HUB after the resolution/DPI change? The BBM icon turns huge on any density change and it looks incredibly ugly.
After having the reduced resolution active for one week, I'm switching back to default. It seems that for daily use there isn't much difference. I observed a couple of scaling issues (mainly with BB apps but also others) and decided it's not worth. I guess it will make one for sure when playing 3d games, but that's not my device usage.
p09 said:
After having the reduced resolution active for one week, I'm switching back to default. It seems that for daily use there isn't much difference. I observed a couple of scaling issues (mainly with BB apps but also others) and decided it's not worth. I guess it will make one for sure when playing 3d games, but that's not my device usage.
Click to expand...
Click to collapse
The reason why BlackBerry apps get affected is because they don't follow proper Material design guidelines. Sadly I feel that this is something that will plague devices for a while to come. So far I too am not noticing much difference in performance or battery life.
is there a way to pin the image on the bottom right of the screen?
also, does it completely ignore touches outside of the image? ...or am I reading wrong and the image will be stretched over the entire screen?
Sent from my STV100-1 using XDA-Developers mobile app
p09 said:
After having the reduced resolution active for one week, I'm switching back to default. It seems that for daily use there isn't much difference. I observed a couple of scaling issues (mainly with BB apps but also others) and decided it's not worth. I guess it will make one for sure when playing 3d games, but that's not my device usage.
Click to expand...
Click to collapse
The screen uses only almost half of the energy when it's in FullHD mode. That's a HUGE difference I can live with those little scaling issues here and there.
priv resolution, dpi
i change just the resolution, does it have a point, i do not wana change the dpi for the fact that is going to overscale a lot of thing, and for exemple i can not change my whatsapp photo if i change the dpi....
What about 720p-mode which is more natural to upscale on qHD than 1080p? Has anyone tried?
u.b.o.o.t said:
What about 720p-mode which is more natural to upscale on qHD than 1080p? Has anyone tried?
Click to expand...
Click to collapse
I tried but it's very ugly so I prefer 1080p
phong1892 said:
I tried but it's very ugly so I prefer 1080p
Click to expand...
Click to collapse
Interesting thread. I just bought a new phone because the priv battery is dying, and I couldn't find a new one. But I had to drop screen resolution to do that, since I didn't want a physically larger device. I miss the sharp resolution and greater "real estate" of the priv screen.
Sent from my moto x4 using Tapatalk

Categories

Resources