I flashed one of the Sense 3.0 roms today and found that the entire rom is slightly-off scale. The best way to see this is to add an analog clock, and it looks like it is flattened with the horizontal diameter longer than the vertical one. I did some calculations and this is because:
Code:
Kingdom: qHD = 960/540 = 1.777...
Incredible: 800/480 = 1.666...
So as you can see, the Kingdom is a bit "taller", and thus directly translating the images from the Kingdom will lead to the screen appearing a bit stretched horizontally. I don't have much experience, but I can tell that adjusting EVERY image in a rom is probably extremely difficult.
So why not, instead of messing with images, modify the display?
Obviously we can't make our displays taller into
Code:
1.777... * 480 = 854
854 by 480, so instead we can make our displays narrower. With some math:
Code:
800 * (540/960) = 450
so we can make our displays 800x450 by chopping off 15 pixels from each side with some software hacks. Also, we could get around images being distorted by setting LCD density higher so that the images would fit.
That last part with LCD density is a bit iffy, but I'm sure that you devs can get it to work.
(Sorry if this is in the wrong section. I thought it would fit better in Development than in General.)
pianoplayer said:
I flashed one of the Sense 3.0 roms today and found that the entire rom is slightly-off scale. The best way to see this is to add an analog clock, and it looks like it is flattened with the horizontal diameter longer than the vertical one. I did some calculations and this is because:
Code:
Kingdom: qHD = 960/540 = 1.777...
Incredible: 800/480 = 1.666...
So as you can see, the Kingdom is a bit "taller", and thus directly translating the images from the Kingdom will lead to the screen appearing a bit stretched horizontally. I don't have much experience, but I can tell that adjusting EVERY image in a rom is probably extremely difficult.
So why not, instead of messing with images, modify the display?
Obviously we can't make our displays taller into
Code:
1.777... * 480 = 854
854 by 480, so instead we can make our displays narrower. With some math:
Code:
800 * (540/960) = 450
so we can make our displays 800x450 by chopping off 15 pixels from each side with some software hacks. Also, we could get around images being distorted by setting LCD density higher so that the images would fit.
That last part with LCD density is a bit iffy, but I'm sure that you devs can get it to work.
(Sorry if this is in the wrong section. I thought it would fit better in Development than in General.)
Click to expand...
Click to collapse
It won't work changing the density has been tried the only way to resize is to use the m10 decoder and go through trial and error..
JoelZ9614 said:
It won't work changing the density has been tried the only way to resize is to use the m10 decoder and go through trial and error..
Click to expand...
Click to collapse
How does the m10 decoder work? Is it multiplatform or Windows/Linux only, and GUI or terminal? If it works on Mac and is terminal-based, I will be willing to M10 all day (through Automator).
pianoplayer said:
How does the m10 decoder work? Is it multiplatform or Windows/Linux only, and GUI or terminal? If it works on Mac and is terminal-based, I will be willing to M10 all day (through Automator).
Click to expand...
Click to collapse
Using search I Found this
I just asked all my friends, and not one of them could even see it wasnt perfect circle...your talking less than a percent off here? is it big enough of a problem to warrant 40 hours of man power to fix?
Afteraffekt said:
I just asked all my friends, and not one of them could even see it wasnt perfect circle...your talking less than a percent off here? is it big enough of a problem to warrant 40 hours of man power to fix?
Click to expand...
Click to collapse
In my hour running Incubus' alpha, the bottom of the screen gets cut off in certain apps. I'd imagine the OP's suggested changes might fix that as well, and that's a dealbreaker for me.
Afteraffekt said:
I just asked all my friends, and not one of them could even see it wasnt perfect circle...your talking less than a percent off here? is it big enough of a problem to warrant 40 hours of man power to fix?
Click to expand...
Click to collapse
Well, maybe 5%, but text is also wider than original. Very bad to my picky eyes.
Thats odd, Im comparing my phone (Sense 3.0) to my friends Stock Unrooted dinc, and i can barely see a different, except my images are higher quality.
So nobody can see it? Everything just looks so... off.
Sense 3.0 changed alot of the dimensions anyways, as I said most things are .9 images, and wont distory unless severe dimension changes, and .111 difference is pretty small.
I also noticed that text is wider-spaced. Can anybody see that?
I'm starting to think I'm paranoid...
Vernox701 said:
Using search I Found this
Click to expand...
Click to collapse
"The devs have not made an official thread for their official release yet"
pianoplayer said:
"The devs have not made an official thread for their official release yet"
Click to expand...
Click to collapse
Yea they did http://forum.xda-developers.com/showthread.php?t=1060648
JoelZ9614 said:
Yea they did http://forum.xda-developers.com/showthread.php?t=1060648
Click to expand...
Click to collapse
Oh. Dang, it's an EXE. No automator unless someone wants to get this running in Crossover
Related
Hello Guys,
I am new to android and it's very interesting for me to go through the discussions of rooting and other stuff. Brilliant!!
I just bought wildfire recently and hmm.. resolution is disappointment for me. I despirately need two things:
1. Hack for HVGA resolution.
2. Live wall paper.
It seems live wall paper is possible from my understandin after reading threads though. Is it possible and please advice me on this regard.
Thank you in advance.
Dude, no hack can push things over hardware limits... I m no android developer, but if you need higher resolution look for another android deveice..
vijaykr1985 said:
Hello Guys,
I am new to android and it's very interesting for me to go through the discussions of rooting and other stuff. Brilliant!!
I just bought wildfire recently and hmm.. resolution is disappointment for me. I despirately need two things:
1. Hack for HVGA resolution.
2. Live wall paper.
It seems live wall paper is possible from my understandin after reading threads though. Is it possible and please advice me on this regard.
Thank you in advance.
Click to expand...
Click to collapse
check lcd density thread in themes and apps
I already checked lcd density app, but seems doesnt work perfectly.
I duno about you... but i think it will be really really hard for software to alter the hardware of a phone. hvga on the wildfire would be awesome... but not any sooner
vijaykr1985 said:
I already checked lcd density app, but seems doesnt work perfectly.
Click to expand...
Click to collapse
not the app, i mean check the thread! you cant use the app u must change manually in system/build.prop
!!
i am using LCD Density for root. it works fine for me, on wildpuzzle v8
resolution reverts back to standard after reboot but it takes a few seconds to change again. and i don't reboot that often.
LCD Density changer never worked for me. But LCD Density for root (different program similar name) works fine and allows me to set my density to 100 (where 120 is default density) this certainly changes the resolution, whether it changes it to HVGA i dont know, but it is deffo higher resolution. with launcher pro set to 5 rows and 5 columns i have a lovely looking phone now. just waiting for our super fantastic devs to look into an overclock kernel and i will be set
I think you need to set density to 76 (not sure) to reach HVGA resolution and your screen looks fine though. Thanks for your information.
vijaykr1985 said:
I think you need to set density to 76 (not sure) to reach HVGA resolution and your screen looks fine though. Thanks for your information.
Click to expand...
Click to collapse
ahh, i am well off then lol. with LCDDensity for root the lowest you can go is 100.
but like one poster above me said, i spose if you want a HVGA screen you pay the premium price for it. i am happy with my wildfire, i have to be, my wife won't let me buy a new phone for another year! i go through to many apparently. we will see though, if i buy a desire she may not know the difference
Not Possible IMO , Though I have also Worked with LCD Density Changer (Beansoft) Wildfire Looks Good With Density 100 / 110 , Any lower than than and the menu text and the Notification Icons looks Crappy.
We would need Hardware Upgrades (Better LCD) In Order to Increase it :-/ I So wish we had Better screen , Resolution is the worst Issue on Wildfire.
I just tried lcd density changer, 110 setting did nothing and 100 setting screws up the lockscreen slider and makes it laggy.
^^ Do it by small Changes , The Stock Lockscreen looks good at 100/110 , The HTC One Screws up.
I hate the Icons at Notification Bar , at 100 , too Small
true, it was the htc one that screwed, im looking at a mod to disable lock screen altogether though. kept it at 120 and did the 5 columns and 5 rows launcher pro mod.
You guys do realise that it's impossible to get HVGA on a QVGA screen?
LCD Density changer gives effect of Hi-Res Screen, but it makes a lot of apps look worse (Paper Toss is a prime example of this)
All it does is rescale some UI elements, not changes any hardware
LOL , Yeah We know LCD Density is just about "Feel-Good-Factor"
beardyone said:
i am using LCD Density for root. it works fine for me, on wildpuzzle v8
resolution reverts back to standard after reboot but it takes a few seconds to change again. and i don't reboot that often.
LCD Density changer never worked for me. But LCD Density for root (different program similar name) works fine and allows me to set my density to 100 (where 120 is default density) this certainly changes the resolution, whether it changes it to HVGA i dont know, but it is deffo higher resolution. with launcher pro set to 5 rows and 5 columns i have a lovely looking phone now. just waiting for our super fantastic devs to look into an overclock kernel and i will be set
Click to expand...
Click to collapse
hi
Thanks for that
It works perfect, 110 is the best for me looks ok beter then 120
HCDR.Jacob said:
You guys do realise that it's impossible to get HVGA on a QVGA screen?
LCD Density changer gives effect of Hi-Res Screen, but it makes a lot of apps look worse (Paper Toss is a prime example of this)
All it does is rescale some UI elements, not changes any hardware
Click to expand...
Click to collapse
i seeeeeee. i read the full disclaimer now on the lcddensity app and it does say it 'virtually' changes resolution or something similar. it was something new to try anyway, and it looks good i have had the phone for 3 weeks now and i dont think there has been a single night where i havent had it in my hands flashing roms and trying apps.
Oh well. So no other way to make resolution high?
Resolution Can't Increased Without a hardware Upgrade , So No Can Do.
110 seems to look best on the wildfire ... at least for me
Anyone have a good source yet for wallpapers to fit our screens?
Thanks
-D
I've been making my own. 960x854 seems to be correct resolution to not have to crop the image when you set it inside the phone.
Essem said:
I've been making my own. 960x854 seems to be correct resolution to not have to crop the image when you set it inside the phone.
Click to expand...
Click to collapse
Right on for the correct resolution size. I will make some wallpapers for the XOOM and Bionic and share them with you guys.
Sent from my DROID BIONIC using xda premium
That's not right, the correct resolution is 1080x960. Resolution for Android wallpapers as a rule of thumb is if you have HxW, the size for the wallpaper is 2*WxH
Essem said:
I've been making my own. 960x854 seems to be correct resolution to not have to crop the image when you set it inside the phone.
Click to expand...
Click to collapse
What program do you use to edit the resolution to 960x854???
Berzerker7 said:
That's not right, the correct resolution is 1080x960. Resolution for Android wallpapers as a rule of thumb is if you have HxW, the size for the wallpaper is 2*WxH
Click to expand...
Click to collapse
I second this. 1080x960 is definitely correct.
960x854 seems to work but if you scale it up to a height of 960 (correct background height) you will see that 854 scales to 1079. 1 px off.
EDIT: Photoshop is the best program to resize, but I believe MS Office Picture Manager can do it too...if you are on Windows
I use Zedge, works fine for me
Essem said:
I've been making my own. 960x854 seems to be correct resolution to not have to crop the image when you set it inside the phone.
Click to expand...
Click to collapse
Thanks for the right dimensions! Time to make some wallpapers not!
Sensei mods wallpaper resolution fits perfect
Wallpaper Guidelines?
Is there a certain guideline for creating wallpapers for the bionic? I've created wallpapers in the past for different devices and they look great, but they look like crap on my bionic. I've done some searching and it seems that a lot of people are noticing that too. Guessing its just a matter of the type of display the bionic has. Some images look great on the bionic, while some look terrible. So I'm wondering if there is some sort of specifics for how you create and save the image files to ensure they look great on the bionic's screen? Is it the image's pixel per inch? Is it the color profile? Is it the image mode as in RGB or CMYK? Or the image mode as in 8-bit, 16-bit or 32-bit? I'm trying to find the magic combo here.
Any help would be appreciated.
KahilYoung said:
Is there a certain guideline for creating wallpapers for the bionic? I've created wallpapers in the past for different devices and they look great, but they look like crap on my bionic. I've done some searching and it seems that a lot of people are noticing that too. Guessing its just a matter of the type of display the bionic has. Some images look great on the bionic, while some look terrible. So I'm wondering if there is some sort of specifics for how you create and save the image files to ensure they look great on the bionic's screen? Is it the image's pixel per inch? Is it the color profile? Is it the image mode as in RGB or CMYK? Or the image mode as in 8-bit, 16-bit or 32-bit? I'm trying to find the magic combo here.
Any help would be appreciated.
Click to expand...
Click to collapse
I dont think any wallpaper will ever look "great" on the bionics screen, especially compared to other phones. The colors just look too far off to me.
Yeah, but still...would like to know the how and why. I can find and load some images that I find as wallpaper and they look great. Others look really bad...to the point where it is all pixelated and the color is off.
There has to be some kind of standards we can follow.
1080 x 960 is the best size, especially if you want your wallpaper to scroll with your desktop. 24 or 32 bit color depth also works well. Using smaller images and/or lower color depth can cause banding and dithering in wall paper images. I think that's part of the reason a lot of people complained about the Bionics display - Google pulled in wall paper from their previous phones back-up and those images got scaled to fit the QHD screen on the Bionic. Happed to me anyway. I had some favorite wall papers on my Droid 2 that were 960 x 854. When my Bionic pulled down my Google data it tried to scale those images and some of them looked like crap-easpecially if they had gradient areas. After re-sizing them to 1080 x 960on my PC and replacing the 960 x 854 versions they looked much better.
BleedingEdj said:
1080 x 960 is the best size, especially if you want your wallpaper to scroll with your desktop. 24 or 32 bit color depth also works well. Using smaller images and/or lower color depth can cause banding and dithering in wall paper images. I think that's part of the reason a lot of people complained about the Bionics display - Google pulled in wall paper from their previous phones back-up and those images got scaled to fit the QHD screen on the Bionic. Happed to me anyway. I had some favorite wall papers on my Droid 2 that were 960 x 854. When my Bionic pulled down my Google data it tried to scale those images and some of them looked like crap-easpecially if they had gradient areas. After re-sizing them to 1080 x 960on my PC and replacing the 960 x 854 versions they looked much better.
Click to expand...
Click to collapse
I've tried that and it doesn't work 99% of the time. Most of the time they still look like crap. In the past, if I've ever had a banding issue, all I had to do was add a little noise to the image to help break it up a bit. Seems like no matter what I try the images will look great on a computer screen or on other devices, but not on my Bionic. Still can't figure out why some images I find look good while others don't...
Hi folks!
I was just wondering what is the best DPI settings for our note without hindering usability.
I would like a general opinion.
320dpi fanboys not welcome!
Sent from my GT-N7000 using xda premium
i run gingerbread at 240dpi, and ICS alpha at 213dpi
seem to be the best ones for each android version
160dpi on GB and well on ICS makes everything a little bit to small
240dpi is perfect due to 90% of phones being stock at this.
*s-memo does mess up on any dpi not 320dpi so remember that
213dpi on ICS brings out full tablet mode but keeps the screen readable
Where can i find info on this ics alpha? id love to give it a shot.
---------------------------
Yeah it's a Galaxy Note, are you jealous?
deymayor said:
Where can i find info on this ics alpha? id love to give it a shot.
Click to expand...
Click to collapse
Here we go...
http://forum.xda-developers.com/showthread.php?t=1423795
And keep this in mind:
KNOWN BUGS
Bluetooth is unstable. Don't rely on it just yet
Battery Usage doesn't work.
MTP Mode does not work. You need to push/pull files via adb
Camera doesn't work. Will be that way until we can get our hands on a ICS
leak for the Galaxy Note
Best regards
[bs]
I've set mine to 240, and loving it. I think it's the best setup for usability and aesthetic for the Gnote. I don't think I would ever go back to the default DPI after switching it to 240.
240
From my experience 240 is by far the best. It is too small for me, but I have poor eyesight (one of the main reasons for buying the Note). For most people it should be fairly easy to adjust too, I would think.
I'm sorry, how do you change DPI?
cswithxda said:
I'm sorry, how do you change DPI?
Click to expand...
Click to collapse
LCD Density Modder
240 dpi the best
cswithxda said:
I'm sorry, how do you change DPI?
Click to expand...
Click to collapse
https://market.android.com/details?id=com.birdapi.android.dpi
Sent from my GT-N7000 using xda premium
Thanks guys. Another Root App Looks like I'll need to get into the water now.
BTW, what is the stock DPI? 284?
cswithxda said:
Thanks guys. Another Root App Looks like I'll need to get into the water now.
BTW, what is the stock DPI? 284?
Click to expand...
Click to collapse
320, btw why u are so scared to root your phone?
Yeah 240dpi is pretty awesome so much screen to work with. Only problem is my eyes are kinda bad but I still love it regardless.
Sent from my Galaxy Note GT-N7000
cmon guys... DPI? that's for printers...
The correct term for screens is PPI, and, it's a physical characteristic of the screen, it's impossible to change a screen's PPI after it's manufactured.
The 320dpi, 240dpi thing that you talk about and which android refers to as lcd density internally is like a virtual pitch, the spacing between each pixel displayed on the screen.
That's why when you decrease the spacing between each pixel from 320 to 240 for example you get much more spacing on the screen cause more pixels fits on the screen.
So a more correct term than DPI or PPI is PITCH. (which isn't also 100% correct cause you can't also change pitch of a screen as it is fixed, but it's like a virtual pitch setting that we can change to "fool" the OS into displaying things as if the phone had a different screen installed)
EdgaBimbam said:
320, btw why u are so scared to root your phone?
Click to expand...
Click to collapse
Because this device is kinda expensive for a Android new comer to try the water
I need to get familiar with all different kinds of commands more...
I wasn't really scared to root the phone as I may have sounded either
cswithxda said:
Because this device is kinda expensive for a Android new comer to try the water
I need to get familiar with all different kinds of commands more...
I wasn't really scared to root the phone as I may have sounded either
Click to expand...
Click to collapse
There are so many advantages to rooting. Imagine running your very own Windows PC without admin rights? That what carriers, and even vendors like Samsung, are trying to force on us. It's BS.
Elusivo said:
cmon guys... DPI? that's for printers...
The correct term for screens is PPI, and, it's a physical characteristic of the screen, it's impossible to change a screen's PPI after it's manufactured.
The 320dpi, 240dpi thing that you talk about and which android refers to as lcd density internally is like a virtual pitch, the spacing between each pixel displayed on the screen.
That's why when you decrease the spacing between each pixel from 320 to 240 for example you get much more spacing on the screen cause more pixels fits on the screen.
So a more correct term than DPI or PPI is PITCH. (which isn't also 100% correct cause you can't also change pitch of a screen as it is fixed, but it's like a virtual pitch setting that we can change to "fool" the OS into displaying things as if the phone had a different screen installed)
Click to expand...
Click to collapse
And the point is?
Sent from my GT-N7000 using xda premium
[OT]
The point is that using a correct term to name something is sometimes not bad at all
[/OT]
Even though lowering the "virtual density" to 240 will allow for more real estate on the display, I am not totally sure that the need to consult an ophalmologist won't increase likewise after that.
It is looking good when you take a snapshot though.
jaiiscool said:
And the point is?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
It was just a comment, maybe not the best place for it but the point is just to try and clear up some of the confusion that sometimes happens when ppl dive into the actual DPI meaning.
Elusivo said:
cmon guys... DPI? that's for printers...
The correct term for screens is PPI, and, it's a physical characteristic of the screen, it's impossible to change a screen's PPI after it's manufactured.
The 320dpi, 240dpi thing that you talk about and which android refers to as lcd density internally is like a virtual pitch, the spacing between each pixel displayed on the screen.
That's why when you decrease the spacing between each pixel from 320 to 240 for example you get much more spacing on the screen cause more pixels fits on the screen.
So a more correct term than DPI or PPI is PITCH. (which isn't also 100% correct cause you can't also change pitch of a screen as it is fixed, but it's like a virtual pitch setting that we can change to "fool" the OS into displaying things as if the phone had a different screen installed)
Click to expand...
Click to collapse
Nah, i think we'll continue with the term "DPI" (Dots Per Inch) But you're right, there's a huge difference between DPI and PPI, but that's not the case since no one has used the term "PPI" here.
I just read the XDA article for the Z5 Premium and how it switches automatically between 1080p and 4k resolution when it sees fit. I think this is an excellent idea for developers to implement into their ROMs. Why don't we have such a feature? Or even a simple toggle that we can select that would change the build.prop or something to switch between QHD and 1080p? Would it be too hard to included or something?
Just wondering, its a really neat feature.
Nick
Because there's little to no benefit for dropping down to 1080 on this device
Sent from my Nexus 6 using XDA Free mobile app
slosrtnick said:
I just read the XDA article for the Z5 Premium and how it switches automatically between 1080p and 4k resolution when it sees fit. I think this is an excellent idea for developers to implement into their ROMs. Why don't we have such a feature? Or even a simple toggle that we can select that would change the build.prop or something to switch between QHD and 1080p? Would it be too hard to included or something?
Just wondering, its a really neat feature.
Nick
Click to expand...
Click to collapse
Probably no one has thought of it. By the way, turning pixels off to produce lower resolution on an AMOLED screen will make the screen much less bright. Perhaps not ideal on our already not bright screen.
Not sure what the build.prop has to do with this though?
akellar said:
Because there's little to no benefit for dropping down to 1080 on this device
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
If it's done right, saving power for each pixel turned off and GPU working less to render images. I reckon it would make a bit of difference.
danarama said:
Probably no one has thought of it. By the way, turning pixels off to produce lower resolution on an AMOLED screen will make the screen much less bright. Perhaps not ideal on our already not bright screen.
Not sure what the build.prop has to do with this though?
If it's done right, saving power for each pixel turned off and GPU working less to render images. I reckon it would make a bit of difference.
Click to expand...
Click to collapse
It's been thought of, it's been done, and it's been shown to provide little to no benefit. If simply changing this isn't what you're referring to then it's not possible without reverse engineering display drivers.
http://forum.xda-developers.com/nexus-6/general/change-nexus-6-to-resolution-1080x1920-t3016819
akellar said:
It's been thought of, it's been done, and it's been shown to provide little to no benefit. If simply changing this isn't what you're referring to then it's not possible without reverse engineering display drivers.
http://forum.xda-developers.com/nexu...x1920-t3016819
Click to expand...
Click to collapse
I saw that thread a while back, but i'm talking about auto switching when the gpu demands for it and switching it back when you don't need it. I assume Sony is doing this because they saw an increase in battery life, so it may be worth it for us as well. Just another cool feature for ROM devs to add to their ROM. Or if they figure out a script or algorithm to make it automatic, then at least have a toggle or something in the quick settings. Or if we don't see any difference going to 1080p, then how about 720p? That has to do something, as it only would run half of the screen's pixels. Sony's screen is IPS, i believe, so we should benefit more than them because we also don't have to power a backlight as well as the pixels.
danarama said:
Not sure what the build.prop has to do with this though?
Click to expand...
Click to collapse
I thought changing the native resolution had something to do with changing a setting in the build.prop. Maybe I misunderstood, as I didn't look too much into it at the time. Definitely didn't watch the youtube vid posted on that thread.
Nick
slosrtnick said:
I saw that thread a while back, but i'm talking about auto switching when the gpu demands for it and switching it back when you don't need it. I assume Sony is doing this because they saw an increase in battery life, so it may be worth it for us as well. Just another cool feature for ROM devs to add to their ROM. Or if they figure out a script or algorithm to make it automatic, then at least have a toggle or something in the quick settings. Or if we don't see any difference going to 1080p, then how about 720p? That has to do something, as it only would run half of the screen's pixels. Sony's screen is IPS, i believe, so we should benefit more than them because we also don't have to power a backlight as well as the pixels.
I thought changing the native resolution had something to do with changing a setting in the build.prop. Maybe I misunderstood, as I didn't look too much into it at the time. Definitely didn't watch the youtube vid posted on that thread.
Nick
Click to expand...
Click to collapse
Changing the native resolution to 720p wouldn't result in pixels being turned off. The phone would just render images in blocks of 4 pixels. It would look like ass, but hey, battery life or something.
akellar said:
It's been thought of, it's been done, and it's been shown to provide little to no benefit. If simply changing this isn't what you're referring to then it's not possible without reverse engineering display drivers.
http://forum.xda-developers.com/nexus-6/general/change-nexus-6-to-resolution-1080x1920-t3016819
Click to expand...
Click to collapse
I'm not sure about how that works, but it isn't turning off the pixels. As I said...
danarama said:
If it's done right
Click to expand...
Click to collapse
If the GPU thinks it is rendering to a HD display and the other pixels are turned off, then yes, it would make a bit of difference - but you would need to do both for any difference to be even slightly noticeable I bet.
Title speaks for it self... Stayed a bit with 515 (and even 600) and although I like the spacing and screen size it's kind of fatiguing to the eyes; to a level in which i guess I ran more to my laptop... Just realized it today
Wanna go back and I went with 411 but not sure if this is the default one. Anyway all looks very crisp and sharp now
384 dp is the default
Wow... Thanks... Seems kind of big tbh... Thought was higher than the 411 I found elsewhere for sure not smaller
ccezar2004 said:
Wow... Thanks... Seems kind of big tbh... Thought was higher than the 411 I found elsewhere for sure not smaller
Click to expand...
Click to collapse
it's because you're so used to the small sizes now lol
Been at 593 since I got it and never going back.
Why this particular value? Just curious. I've seen that after 600'ish even app layouts are changing... Like it's a tablet or sorts...
I tried a few values, and yeah, around 600 some things won't display correctly, 593 was the value I settled on, looks good and small, display everything right, and never had a reason to change it again.
Hello can you upload a screen shot to see how things are with this DPI please ?
I don't know if this works for long, but here it is.
Quick Share
Expired
linksharing.samsungcloud.com