Related
So, since the Samsung Galaxy Note has an almost ludicrously large sized screen at 5.3 inches diagonally in size, it is only natural that I want to make the most of this high-resolution screen. From what I have presently read, changing the DPI seems to be the way to fit more items onto my screen, but how will this effect general usage of the device? Firstly, will it ruin any particular apps that come pre-installed on the phone such as the S-Memo, S-Note or S-Planner apps and do the Contacts, Phone, plus Messaging applications for actual phone usage all work regardless of DPI? Also, if I were to change to a lower DPI, would this allow me to access a tablet mode within either Touchwiz or any different launchers? Unfortunately, I have yet to root my device for fear of screwing it up, as this is my first true Android device (minus an old second-hand HTC Desire which had no storage and didn't perform too well) and I am only 14 so far from the most experienced with technology. So, what would rooting involve? I am running a stock Samsung ICS ROM, which is affected by the brick bug, and should hopefully receive my Sandisk UHS-1 Micro-SD soon with a lovely 32GB of storage should rooting require external storage.
EDIT 1: I read somewhere that setting the DPI to 213 brings out a full tablet mode, whilst keeping everything readable. Is this true and, if not, what DPI settings do people recommend that still keep the screen readable but with the most information possible on it?
EDIT 1
I read somewhere that setting the DPI to 213 brings out a full tablet mode, whilst keeping everything readable. Is this true and, if not, what DPI settings do people recommend that still keep the screen readable but with the most information possible on it?
Any help would be appreciated.
https://play.google.com/store/apps/details?id=com.innodroid.dpichanger&hl=en
Brad387 said:
So, since the Samsung Galaxy Note has an almost ludicrously large sized screen at 5.3 inches diagonally in size, it is only natural that I want to make the most of this high-resolution screen. From what I have presently read, changing the DPI seems to be the way to fit more items onto my screen, but how will this effect general usage of the device? Firstly, will it ruin any particular apps that come pre-installed on the phone such as the S-Memo, S-Note or S-Planner apps and do the Contacts, Phone, plus Messaging applications for actual phone usage all work regardless of DPI? Also, if I were to change to a lower DPI, would this allow me to access a tablet mode within either Touchwiz or any different launchers? Unfortunately, I have yet to root my device for fear of screwing it up, as this is my first true Android device (minus an old second-hand HTC Desire which had no storage and didn't perform too well) and I am only 14 so far from the most experienced with technology. So, what would rooting involve? I am running a stock Samsung ICS ROM, which is affected by the brick bug, and should hopefully receive my Sandisk UHS-1 Micro-SD soon with a lovely 32GB of storage should rooting require external storage.
EDIT 1: I read somewhere that setting the DPI to 213 brings out a full tablet mode, whilst keeping everything readable. Is this true and, if not, what DPI settings do people recommend that still keep the screen readable but with the most information possible on it?
Click to expand...
Click to collapse
Hi there , you can change the Display Pixel Intensity(DPI) with many apps , you can find them on play store . DPI changer is one such app. Now coming to the other half of your querry. reducing your DPI to 213 or lower makes things look pretty small on your phone , its readable only if you have sharp eyes . And if you are on rooted stock ics or gingerbread rom or any rom which is based on stock rom from samsung then it wont change your phone UI( User Interface ) to tablet mode .
Cheer up, there are few roms with which you can change the UI to tablet mode by reducing the DPI , to be particular AOKP rom . You will get one in the development section . If you dont want all such complication , download Paranoid android latest version and quench your thirst . With a single tick of check box you can switch between phone and tablet yi
Well, thanks.
DPI can also be considered as Dots Per Inch Stock . DPI for galaxy note is 320 , lower the dpi, smaller the icons and text , tablets generally have DPI somewhere around 172 to 190 or even upto 200+, but it depends on the screen size and the display resolution too . Well if you think 320 is too much for you and if you cant take it , then reduce it to 285 which is the actual (Physical) DPI of the screen on your phone .
Here is how you calculate DPI of your screen :
The resolution of Galaxy note is 1280 *800. i.e there are 1280 pixels from top to bottom of your screen and 800 pixels from left to right
Screen diagonal length = 5.3 inch
DPI = [sqrt of ( sq of(1280) + sq of (800) ) ] / 5.3
= 285 (approximately)
Hope you can understand all this and figure out yourself what is best suited for your screen :angel:
I just upgraded from 5.0.1 to 5.1 and I've noticed that when I change my resolution from the factory default of 560 to say the native res of 493, the contact thumb nails are distorted. If I use the terminal command "wm dentity 560" to go BACK to 560, it fixes it. Normally I run 493 which is the native res for this screen.
5.0.1 does not have this issues, only 5.1.. I also tried other resolutions and I get this issue on everything but 560.
I'm using CleanROM 2.2 which is a stock based ROM.
Also I noticed pictures in some image browsing apps do not display correctly. They show as super zoomed in on one section and I an not zoom out. ES File Explorers image app does this but for example QuikPic does not.
If I go back to 5.0.1, all problems solved though.
Just wondering about other 5.1 users experiences with stuff like this.
493 is not the native DPI. PPI and DPI are NOT the same.
Just to echo what @akeller said, DPI is not linked to resolution. DPI is not the same as PPI. PPI (Pixels per Inch) are how many physical pixels are in an inch of your display. This obviously cannot be changed.
Lets say you have a 5" screen at HD resolution (1080p) and also a 10" screen at the same resolution. As you can imagine, you have the exact same amount of pixels on the display, but the display is bigger so the pixels are also bigger.
This means that assets on your screen (icons, buttons etc) will also be much bigger, so you are not taking advantage of a bigger screen as you can only fit the same amount of stuff on it. For this reason, DPI is used as a scaling method to make assets smaller, to fit more on the screen. There is no hard-and-fast rule as to what DPI to use. Generally, the bigger the display, the smaller the DPI should be to make bvetter use of it. OR, the lower the resolution, the smaller the DPI should be. There is no direct link to PPI and DPI.
After you run "wm density 493" also run just "wm density". Now you'll probably see that it reports two values, 560 and 493. The solution is to also edit build.prop (change 560 to 493).
I just want to ask. At this low dpi am i stressing my cpu more? I don't play any games. Mostly use my device for multimedia, social, forums and whatsapp. So is it fine if i keep this dpi. or its better I change it to normal like 493??
Im on N dp3
akholicc said:
I just want to ask. At this low dpi am i stressing my cpu more? I don't play any games. Mostly use my device for multimedia, social, forums and whatsapp. So is it fine if i keep this dpi. or its better I change it to normal like 493??
Im on N dp3
Click to expand...
Click to collapse
normal dpi is 560, not 493.
While setting the DPI lower doesn't affect the CPU or GPU, changing the DPI is of little benefit unless your eyesight is bad. I'd set the DPI back to stock and forget it.
I know. I was talking about small screen size in android n which is around 490. And i have it at custom 331. Is it ok? Or is it bad for performance. And cpu is doing more work?
Strephon Alkhalikoi said:
While setting the DPI lower doesn't affect the CPU or GPU, changing the DPI is of little benefit unless your eyesight is bad. I'd set the DPI back to stock and forget it.
Click to expand...
Click to collapse
I see. Thank-you. Stock is just a little too big for me. Thanks again.
akholicc said:
I just want to ask. At this low dpi am i stressing my cpu more? I don't play any games. Mostly use my device for multimedia, social, forums and whatsapp. So is it fine if i keep this dpi. or its better I change it to normal like 493??
Im on N dp3
Click to expand...
Click to collapse
The native resolution of the N6 display is 493.
Google's default is 560 that's not logically on a display of 1440 x 2560 pixels. The capabilities of the display are not fully used with Google 's idiot 560 dpi.
A dpi value of 384 or less, puts the N6 in tablet mode (2 columns in Settings menu). And the icons are smaller and more rows and columns are available.
I've used several dpi values and did not notice less battery life. Or cpu stress.
My favorite is 384.
I disagree with the sentiment that the display isn't fully or properly utilized at the DPI Google set. Naturally you're entitled to your opinion, but the Nexus 6 isn't a tablet. The tablet interface is a matter of user choice, not a design flaw. If it were a design flaw, then any 5.5" - 6" device with a QHD screen should be in tablet mode by default.
Strephon Alkhalikoi said:
I..... If it were a design flaw, then any 5.5" - 6" device with a QHD screen should be in tablet mode by default.
Click to expand...
Click to collapse
Most 5-6" recent smartphones have a display with 1080x1920 pixels (FullHD). Phones with qhd display cannot be compared with the N6 because of the lower resolution (960x540 pixels).
The N6 is one of the few with 1440x2560 pixels (WQHD)
The default dpi of 560 that Google used does not fit the native resolution of the N6 display.
You're right. I used the wrong acronym to refer to the screen, thus I will restate my point: this is not a design flaw. If it were, any device in the 5.5" - 6" range with a resolution identical to the Nexus should be in tablet mode by default. They are NOT. Even devices that have the same screen size but a lower resolution are not in tablet mode by default. This is because these devices are not tablets, even if they can be used as such.
DPI is device independent, if I recall Google's documents on the matter correctly. That number does not have to equal the device PPI of 493, thus what Google chose to use is just as valid as any other number.
Strephon Alkhalikoi said:
DPI is device independent, if I recall Google's documents on the matter correctly. That number does not have to equal the device PPI of 493, thus what Google chose to use is just as valid as any other number.
Click to expand...
Click to collapse
That's correct, but I don't agree with Google.
The default DPI 560 means in practice larger icons and titles. Too large imo. I want more and smaller icons on the main screen and in the launcher.
The tablet mode is a different thing. I think it nice to have a 2 column settings menu. That's personal. In Android N preview it doesn't work anymore.
I don't see the larger icons and titles as a problem, and Google likely doesn't see it as a problem either. I know Samsung doesn't see it as a problem, as on the Galaxy S4 they did the same thing. That device's 5" display had a PPI of 441, but a DPI of 480. Fortunately, the S4 could be rooted and the DPI changed. Something I'm sure you've done here with the Nexus 6.
Which DPI setting would be better? Samsung sets it to like 411dpi iirc, but for example http://dpi.lv/ shows it should be 522dpi for 6,3" screen with 2960x1440 resolution.
What's your opinion on this? Maybe I'm wrong?
resutatto said:
Which DPI setting would be better? Samsung sets it to like 411dpi iirc, but for example http://dpi.lv/ shows it should be 522dpi for 6,3" screen with 2960x1440 resolution.
What's your opinion on this? Maybe I'm wrong?
Click to expand...
Click to collapse
There is no "best" setting. Just play around with it and see what you like. The higher the number the smaller the content on the screen. I have mine set to 420.
Man 522 is small. I do like the layout but keyboard is way too small for my giant thumbs.
455 is best for me
Sent from my SM-N950F using Tapatalk
I use 500dpi, perfect for me. however it breaks the samung keyboard, install Gboard instead
I love small font.
since the original was 411, I adjusted to 512, and increased to 564 recently.
Loved it.
did anyone notice any obvious battery drain after increasing the dpi?
Mine is 185 dpi i lile it
Sent from my LG-P500h using XDA Free mobile app
Got mine set to 340. Still need glasses though. LoL
Sent from my SM-N950U using Tapatalk
yes i noticed a battery drain,dont know if it is from it...thats how i got to this post
I use 512, I love having a big screen real state, and yes the native keyboard is useless at this dpi, but I use A.I type since my S3, so I have no problems with it
PHP:
I am using 602, because it allows browsers like Chrome or Firefix to have tabs at the top of the browser like it would be on a laptop, which is nice if you like more of a traditional browsing experience. and when rotating the device orientation into landscape the navbar will also rotate with the display instead of staying at the bottom of the device.
Screenshot attached
Now using 2160x4440 and 560dpi .
wm size 2160x4440
wm density 560
478 and 6x6 home screen settings - if I go above I will brake the home screen settings
Hey folks,
I am using this module to enable AA on my BMW headunit:
a.aliexpress.com/_U4Jz5
It kinda works nice except for one thing, resolution is not so clear due to dpi settings. Someone else dug into the system and found that in
etc/androidauto/androidauto_config.xml
The resolution is set to 480p instead of 720p and dpi is set to 150 instead of 180.
We have no SSH access but can only upload .bin update files as we dont know the password.
Does anyone know if it would be possible to change 720p to true and up the dpi somehow?
Carplay apparantly is 720p on this unit.
<DisplayWindow><!-- Head Unit side configuration--> <X_Coordinate value="0"/> <Y_Coordinate value="0"/> <DisplayWidth value="1280"/> <DisplayHeight value="480"/> </DisplayWindow> <Display><!-- Phone side configuration--> <DisplayWidth value="232"/><!-- Physical width--> <DisplayHeight value="87"/><!-- Physical height--> <Density value="170"/> <RealDensity value="153"/> <ViewingDistance value="400"/> <Resolution480P value="true"><!-- fps: 30 or 60--> <fps value="30"/> </Resolution480P> <Resolution720P value="false"> <fps value="30"/> </Resolution720P>
Nobody?
Anyone?
Do you have a copy of the BIN? My guess is unpacking and repacking the BIN will be the hardest part of this. You probably won't be able to do this without source scripts. You are in the right place regarding the XML file inside. All android head units, regardless of what they are, have to tell our phones what resolution to serve up. If the head unit says to run 1024x600 then that is what you are getting.
An alternative would be to ask the manufacture to release an update set to the proper settings.
---------- Post added at 09:12 PM ---------- Previous post was at 09:09 PM ----------
Here you go The Andream unit you have should likely work with one of these firmwares. Do a lot of reading there before you proceed. I cannot be responsible for you flashing the wrong software to your unit.
I have a similar unit to yours and was able to get mine running at the proper resolution.
@heresy_fnord, when you say the proper resolution, what resolution are you referring to? I have the Andream (version: NBT-02B) unit myself, and flashed the latest .BIN with the AA Widescreen fix, but I feel the scale is slightly off. Text and elements are too small compared to the screen size (I have 8.8", 1280x480).
ckarv said:
@heresy_fnord, when you say the proper resolution, what resolution are you referring to? I have the Andream cool:unit myself, and flashed the latest .BIN with the AA Widescreen fix, but I feel the scale is slightly off. Text and elements are too small compared to the screen size (I have 8.8", 1280x480).
Click to expand...
Click to collapse
OK, my guess is the physical screen size is the issue. If you are certain the 8.8" screen also runs 1280x480 then the settings for DPI are probably not appropriate. Here is what I see for a 10.25" screen:
<Display>
<DisplayWidth value="244"/> 244mm is 9.6" width
<DisplayHeight value="92"/> 92mm is 3.62" height
<WidthMargin value="0"/>
<HeightMargin value="0"/>
<Density value="220"/>
<RealDensity value="133"/> This calculator indicates a real density of just a hair over 133PPI
So for example, your real density should be set to 155PPI based on that logic. I don't know what your update file was set to. I don't know what your display width and height should be set to since I don't know how the 8.8" screen measures length and width. Finally, I think they are setting the Density of the widescreen fixed update to 210 and you might try 220 which is as big as it can be set before it cuts back over to the non-widescreen view, and see if that works.
heresy_fnord said:
OK, my guess is the physical screen size is the issue. If you are certain the 8.8" screen also runs 1280x480 then the settings for DPI are probably not appropriate. Here is what I see for a 10.25" screen:
<Display>
<DisplayWidth value="244"/> 244mm is 9.6" width
<DisplayHeight value="92"/> 92mm is 3.62" height
<WidthMargin value="0"/>
<HeightMargin value="0"/>
<Density value="220"/>
<RealDensity value="133"/> This calculator indicates a real density of just a hair over 133PPI
So for example, your real density should be set to 155PPI based on that logic. I don't know what your update file was set to. I don't know what your display width and height should be set to since I don't know how the 8.8" screen measures length and width. Finally, I think they are setting the Density of the widescreen fixed update to 210 and you might try 220 which is as big as it can be set before it cuts back over to the non-widescreen view, and see if that works.
Click to expand...
Click to collapse
I've put some effort into looking into this now, basically reading 100 odd pages in the "Andream MMI Box - Wireless CarPlay & Android Auto" thread (starting on pg. 135), over at the Bimmerpost forum.
Findings:
- 720p = true setting is required to display AA in "Wide" format (ie. clock, second app on the right side of the display, map and vertical bar with "home", active app, notification and assistant buttons on the left).
- From reading results of testing over at the other forum, the Physical width/height settings did not seem to make a difference to output.
- Density on the other hand is used to scale the elements on screen, and this also impacts readability and sharpness of the objects/text.
-- from some testing, the conclusion was that "200" is the optimum value for the 1280x480, 8.8" screen, although eg. "210" was tested.
-- unsure if changing "Real Density" will make a difference to output (similar to physical measurements)
* Also, I think my scale is correct, or as specified in the firmware. Text and elements just seems so small compared to CarPlay that wife uses.
* Attached a picture of my screen with 200 dpi.
You are using a "Density" value of 220, do you have an example of what that looks like in practice?
Thanks
ckarv said:
I've put some effort into looking into this now, basically reading 100 odd pages in the "Andream MMI Box - Wireless CarPlay & Android Auto" thread (starting on pg. 135), over at the Bimmerpost forum.
Findings:
- 720p = true setting is required to display AA in "Wide" format (ie. clock, second app on the right side of the display, map and vertical bar with "home", active app, notification and assistant buttons on the left).
- From reading results of testing over at the other forum, the Physical width/height settings did not seem to make a difference to output.
- Density on the other hand is used to scale the elements on screen, and this also impacts readability and sharpness of the objects/text.
-- from some testing, the conclusion was that "200" is the optimum value for the 1280x480, 8.8" screen, although eg. "210" was tested.
-- unsure if changing "Real Density" will make a difference to output (similar to physical measurements)
* Also, I think my scale is correct, or as specified in the firmware. Text and elements just seems so small compared to CarPlay that wife uses.
* Attached a picture of my screen with 200 dpi.
You are using a "Density" value of 220, do you have an example of what that looks like in practice?
Thanks
Click to expand...
Click to collapse
- 720p = true setting is required to display AA in "Wide" format (ie. clock, second app on the right side of the display, map and vertical bar with "home", active app, notification and assistant buttons on the left).
This is accurate.
- From reading results of testing over at the other forum, the Physical width/height settings did not seem to make a difference to output.
I don't know, perhaps this is true.
- Density on the other hand is used to scale the elements on screen, and this also impacts readability and sharpness of the objects/text.
-- from some testing, the conclusion was that "200" is the optimum value for the 1280x480, 8.8" screen, although eg. "210" was tested.
-- unsure if changing "Real Density" will make a difference to output (similar to physical measurements)
* Also, I think my scale is correct, or as specified in the firmware. Text and elements just seems so small compared to CarPlay that wife uses.
Your scale of text is set by the DPI essentially. Its a combination of resolution and DPI. Basic example, if I was to set my DPI to 200, the text on my screen would be smaller.
* Attached a picture of my screen with 200 dpi.
This is a 10.25" screen with 220DPI
In your case, the one update file was made for a 10.25" screen. The thing is, there will be a DPI difference between the two even if the resolution is the same. I suspect you need check with that community to see if there is an update that maintains widescreen mode but uses the different DPI.
EDIT: To be fair, I think your screen looks "normal" but then, it looks like your clock and such are the same scale as mine. Maybe AA is just smaller text in general?