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:
Hi,
I am new to the p7. I am used from my Samsung and nexus devices to adapt via build.prop DPI in order to see more things on screen.
Build.prop has no DPI setting. How (which app?) Proved to securely change DPI? And what is stock DPI for 1080 and 720p (rog)?
Thanks
No one feeling the need to show more on screen? [emoji22]
Hi,
Have you found a solution for this yet?
I've recently got myself a P7 and I'm trying to get something similar to 240 dpi(like my s3).
People have mentioned ROG tech, but I can't find that option anywhere.
ROG setting is under Settings - Power Saving, then menu (upper right corner) setting.
Rog? I tgought its resolution (I.e HD 720p instead of full HD1080p)? Is there also a setting for density hidden besides ROG?
rog doesnt do the trick
I've activated ROG, but all it does it help the battery to last longer, by reducing performance and screen res.
What I (and op) are looking for, is something to change the dpi (pixel density/LCD density). Like on samsung phones, you can do it through build.prop
No one managed to edit dpi?
Still have a problem...
Where.is the rog option in emui3?
changing dpi on P7 ??? such little screen ?? NO POINT it is tiny already ..
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?
Hello,
A happy owner of this phone, that said, can we via some homebrew apk change the screen refresh rate and screen resolution? get the phone on a just 1080p @ 24 fps, think how much then the massive bat, would last, if there is a dev out there, i could (and most likely others) donate a beer to be able to use it +<3
edit: what do you know.. it does exist on s20 video, think its easier, can someone get that pkg for us ?
edit2 : found this app unfortunately, still cant change resolution, and refresh rate cant go below 60hz..
Cheers
We can change resolution
Remove OneUI Lags/Slowness
1. Download Easy DPI Changer (Play Store)
2. Set DPI to 340
3. Set Resolution to 775x1680
4. Download Termux
5. Enter commands
5.1. su (Accept Magisk Pop-up)
5.2. settings put secure sysuiroundedsize 1
6. Set smaller font size in Settings
7. Enjoy!
For more join Telegram group
@Sagarking Ty so much for the reply,
Btw i posted a request for the dev of the the tweak linked above in edit 2
and he replied :
"
Atrosincity said:
Can you add support for Galaxy m21, only quick dose mod working for now, it does have a FHD+ resolution, if u can manage the ability to change resolution to HD+, less than the locked 60hz refresh rate would be a bonus, ill be glad to support
Click to expand...
Click to collapse
Added. Try to clear app data and open while connected to the internet.
Hoowee, Ty so much matey, i can confirm resolution change to HD+ working.. definitely getting the full version asap. i posted a question/request bout this in the galaxy m21 forum, I ll update the post there to make sure more ppl using M21 know bout this fabulous tweak. thx again <3 from morocco. "
Since i promised tribalfs to support his app, Ill do.
Tll try Easy DPI Changer + your method for 1st half of ramadan, and update here which method is best for more battery life, ty again for the help.
Back from a good away time, paid the homebrew galaxy max hz, as promised, his latest version, does not unfortunately support screen refresh rate, of our M21, but offer a quick switch between 2 resolution:
1560px X 720px @ 280dpi (fps fixed @60)Hz
2340px X 1080px @420 dpi (fps fixed @60)Hz
personally i dont see much of a difference, @ lower resolution for my 44 old years eyes.. but not much battery saving on the other hand
The app, offer a quick doze mod on screen off with 3 presets (base, plus, max)
Thats it ,
up to you if you want those funtions enough to support the dev..
Cheers !!
@Sagarking "settings put secure sysuiroundedsize 1"
think this messed up the roundness of my display.., can i have undo it, or get the default setting?
Hi guys,
I used to use this method with mostly all of my devices in the past: LG G3, Galaxy S5, Amazon Kindle Fire tablets (including 8'' and 10''). All of them work just fine. But not this Pixel5!
Using the "adb shell wm size" command. I changes the screen resolution of my devices down a notch, for example from 1440p to 1080p, or 1080p to 800p and so on. Then I adjust the density accordingly. They all turn out the Ok-ish screen resolution and have a much better GPU performance for gaming.
My current S10 has the native changing resolution from Samsung, So I don't use it for my S10.
But with the Pixel 5, there is a problem. The camera cut - out on the screen become so weird and placed on the off center position, and the Pixel 5 is unusable
I really love to use my pixel 5 at 720p or 900p, and I believe the Adreno 620 (snapdragon 765G) on the Pixel 5 will handle game at the lower resolution much much better.
Does anyone have a fix for this? please help!
Thank you for your reading!
P.S: OMG, this was my bad for posting the thread into the wrong sub-forum. It was on the other tab of my web-browser. Thank you very much for moving it to the right place, Moderator!!
Why are you not changing the resolution in the settings like you do on the Samsung? A quick search suggest the Pixel 5 has such an option. You're best doing it the official way to guarantee everything will work correctly.
Because you're changing the resolution and DPI through what is basically a developer option, I think whatever is handling the camera cutout (An app? The WM? Android?) is not updating its position and that causes it to be misplaced. Therefore, I dont think you find a simple fix for this. Sorry.
richhaynes said:
Why are you not changing the resolution in the settings like you do on the Samsung? A quick search suggest the Pixel 5 has such an option. You're best doing it the official way to guarantee everything will work correctly.
Because you're changing the resolution and DPI through what is basically a developer option, I think whatever is handling the camera cutout (An app? The WM? Android?) is not updating its position and that causes it to be misplaced. Therefore, I dont think you find a simple fix for this. Sorry.
Click to expand...
Click to collapse
You must be mistaken the Pixel 5 with other phones, since we don't have the option for such a changing the resolution in the settings.
If you mean the display size? It's just a density change, not the resolution.
Thank you for your contribution anyway!
Hi, have you sovled the problem? I encountered a similar condition.