Hi. I had a question about the "493dpi" versions of some ROMs I've seen. Basically, what's to gain by using a 493 dpi ROM? I read one of the nexus phones has native 493, but the system sets it to 560 or so. Why would they do that? Is something similar going on with the xt1254? Basically if someone could give me a cliff notes version of what the heck this is about, if appreciate it. Thanks!
elderlypunk said:
Hi. I had a question about the "493dpi" versions of some ROMs I've seen. Basically, what's to gain by using a 493 dpi ROM? I read one of the nexus phones has native 493, but the system sets it to 560 or so. Why would they do that? Is something similar going on with the xt1254? Basically if someone could give me a cliff notes version of what the heck this is about, if appreciate it. Thanks!
Click to expand...
Click to collapse
I think it's supposed to save battery at the cost of image quality. I'm not sure about that though. Why someone would want to do anything to mess up the Turbo's beautiful screen is beyond me, but to each their own.
Right? Granted I had some crummy phones in the past, but this display is something else! Anyways, I figured it has to have something to do with "pretty" vs. performance (what doesn't?), but I am operating from a position of ignorance.
elderlypunk said:
Hi. I had a question about the "493dpi" versions of some ROMs I've seen. Basically, what's to gain by using a 493 dpi ROM? I read one of the nexus phones has native 493, but the system sets it to 560 or so. Why would they do that? Is something similar going on with the xt1254? Basically if someone could give me a cliff notes version of what the heck this is about, if appreciate it. Thanks!
Click to expand...
Click to collapse
We actually have 640 dpi for the Quark (Moto Turbo, Droid Turbo, Moto Maxx). Dots Per Inch, which is software based.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We have 565 ppi (Pixel Per Inch)-- which shows Steve Jobs LIED when he said the human eye couldn't see more than 300 ppi. But then he had an iPhone to sell which had a little more than 300 ppi. Funny how that works. Most of the media never called him on it except for Wired magazine who interviewed an optical research scientist who said Jobs was full of crap (but he said it in a scientific way). Proof is our phones.
You can change the DPI but not the PPI (baked into the hardware). But it will break some apps. I've done it before on other phones, but I wouldn't do it any more.
Related
Hello there! I just rooted and installed CyanogenMod a few days ago and have been loving it except for the really small font size on the Lock Screen. Stock 1.6 was much bigger for me. I spent a little bit of time on #cyanogenmod and from my interactions there I've gotten a little confused about where the problem/feature/change lies. Bear with me for a second and please note that while this may seem entirely cosmetic to some of you it really does affect the way I use my phone. I understand if many of you won't care about such a small thing...I'm admittedly anal about these kinds of things and now curious, too, and I'm sure some of you themers out there can relate:
On my myTouch 32B T-Mobile Stock 1.6* before I rooted, the lock screen font size was large and quite visible from the distances I desired reading it from. My memory is blurry on whether it got bigger from 1.5 to 1.6 or stayed the same size (please comment if you have any insight).
After rooting and installing CM, the first thing I noticed was the reduced font size of the lock screen. I'm surprised that my googling and forum searching didn't yield anyone else curious about the font reduction...maybe it bothers me more than it should.
See for yourself:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The shot on the left was taken by me and the one on the right is borrowed from the Contact Owner website (the first shot online I could find that matches what I was used to in 1.6).
So the reason I'm posting this up here is to ask:
How big is your font size in 1.5? 1.6? CM? Was it weird for me to have such a large font? Do your experiences coincide with mine or differ? Do you also desire a larger lock screen if yours is indeed as small as mine? Devs: do you have insight into what kind of steps I could go through to make the font bigger? I have not yet taken the plunge into the SDK or taken a peak at the AOSP source, though I'm planning on both at some point, so pardon the naivete. I'm also aware there are complete lock screen replacements like Stericson's, and that could be an eventual solution if I don't turn anything up, but the stock screen has suited me just fine up until this point.
It seems a shame to not be using all those wonderful pixels to there fullest when my $500 smartphone is acting as my timepiece!
Thanks if you have any info.
*Pardon me if I'm in the wrong place, I know there's a Sapphire section but I felt inclined to post in a place that is a little more Cyanogen oriented, a little more Q&A oriented, and besides I really don't think this has to do with hardware.
Hi, I've just found this post having the same issue. I've moved from 1.5 to CM and that was one thing that I miss from stock... Did you find the solution?
adameqq said:
Did you find the solution?
Click to expand...
Click to collapse
Unfortunately I did not. Just learned to live with it... It's reassuring to see that someone else noticed the change, though.
Any updates?
Nope. Anyone have a suggestion for a better place to put this post? I'm thinking maybe Android Development and Hacking > Android Themes now that that exists.
Is this something I should just repost manually over there or does a mod want to move it for me?
Thanks!
I ran the GLBenchmark on my Nook Color, then on my DINC and a few others and finally grabbed a bit more results from their website and this is what I got.
Turns out, the NC isn't a bad gaming platform at all. We already suspected that but cold hard numbers are a welcome confirmation.
Also interesting: if you have a solid disposable income, the Galaxy Tab is the leader of the pack. And if you have a solid disposable income AND speed scares you, the Streak seems like a good fit.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Would a froyo upgrade improve those numbers?
Looks to me on first glance that the NC would match the highest scores with some overclocking.
Homer
Yes, I was thinking that overclocking would be good. We won't see this until a custom kernel is released, though.
And no, unfortunately I do not think that Froyo would give us any improvement; these tests run native code, not Java, so a JIT won't make a difference.
Those numbers look suprisingly good. I use a DINC too and was expecting the NC numbers to be lower, not higher!
Just a shot in the dark but I am wondering, did you by any change change the refresh rate of the nook from the 48000 to 68000 (or 66461) before you ran these test?
Just wondering considering the 2 test that were hitting the mid 40's could possibly may have been vsynced down instead of allowing them to go higher perhaps?
No idea if this would apply to an android system, but would it hurt to check?
An intriguing thought, indeed.
I will see if the refresh rate hack "takes." I've read that many people are having trouble convincing their NC.
RoboRay said:
Those numbers look suprisingly good. I use a DINC too and was expecting the NC numbers to be lower, not higher!
Click to expand...
Click to collapse
That is the one conclusion that I did not feel like voicing in my original post: "Oh, no, my poor Dinc."
I can't help but feel I am imagining the washed out effect I see on my N7, perhaps I am just too used to the amoled saturation. Thought pictures of my N7 looking like others would help me feel better about it. Feel free to show if yours looks any different! Of course now that I'm looking at the pic I just took it doesn't show much difference, but in person it does.
Both at 75% brightness:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm personally happy with the screen on the Nexus7. You can't compare it to a Super AMOLED+ screen though. The latter is much better quality with a higher contrast ratio.
I do notice some light bleeding around the edge, but I can live with that. Watching movies, everything looks great.
No point in other people posting pictures of their Super AMOLED phones vs Nexus 7.
AMOLED = Much more vivid colors.
And yes, the Nexus 7 will look 'washed out'
Why is it that this tablet is the least expensive contender on the market and the screen is NOT better than the highest end most expensive table screen?
T-Slice said:
Why is it that this tablet is the least expensive contender on the market and the screen is NOT better than the highest end most expensive table screen?
Click to expand...
Click to collapse
Maybe because it's the "least expensive contender"?
/sigh
/facepalm
nxt said:
Maybe because it's the "least expensive contender"?
/sigh
/facepalm
Click to expand...
Click to collapse
LOL. I think he was being sarcastic
As far as screens, your comparing Mercedes quality (tablet) to Bentley quality (samoled gnex).
Sent from my Nexus 7
Yeah. Sorry for the sarcasm. It just bugs me. I love this thing. Everytime I interact with it I am pleasantly surprised.
i have nothing to add to this thread except that the OP's camera sucks.
nxt said:
Maybe because it's the "least expensive contender"?
/sigh
/facepalm
Click to expand...
Click to collapse
hah, it is an ipad camera...does suck indeed. I just wanted a little reassurance that it's normal, all good. I'm cool with it, just wanted to make sure I'm in the norm. Have no one around to compare to.
Has anyone pulled the .apk and gotten it to work? I just want manual shutter. Picked up the S6a just for battery, almost got the N5 just for manual mode.
I could have sworn the S6 allowed for a "pro" more controlled experience. Is Manual exposure not anywhere; I recently just got my S6 back from repair so I haven't had much hands on use. I'll go ahead and check myself, but I could have sworn that it was advertised.
Also, I think this goes along more in the Help/Q&A section, but I could always be wrong
Exposure you are correct, I'm referring to shutter. You can have up to a 10 second shutter on the N5 which would be badass.
When I was posting on the Q&A, it said that only answers could be posted... I wouldn't mind a discussion also.
Is exposure different from shutter?
Yep... I might want a long shutter with a small aperture vs short shutter with a wide open aperture, the exposure could end up being very similar but very different effects.
Ah! I'm not an avid photographer frankly (I'm sure it will show). I did indeed look around, and yeah you're right no noticeable shutter control. I'll hang around the N5's section. From my memory, someone was able to port N5's functions over to the S6 over here on XDA or over at Reddit. For the apk though, we would need a rooted N5 or OTA file to extract it from likely. If they share similar API's, getting it to work shouldn't be impossible.
I supposed the timer is something entirely different from what you want. I just noticed it and saw the option to set for 10 seconds, but thought I'd ask.
These are a couple examples of what can be done with REALLY long shutter:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
loudaccord said:
These are a couple examples of what can be done with REALLY long shutter:
Click to expand...
Click to collapse
Fantastic looking! Looks like there was a system dump for the N5. I could look into extracting what I need from that, but haven't looked into it in detail - yet. Will get to it later when the day settles down.
Hey guys I just changed my display resolution to 1920x1080 with density 420
with adb without root to improve battery life.
I am happy with the results, can't tell the difference that much and hope to get more juice,
but some of the images are distorted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://imgur.com/yHBhwMC
http://imgur.com/Hv5uve0
http://imgur.com/FUTeTyB
Is it supposed to be like this?
and is there any way to fix this?
Thanks!
To fix, reset your resolution to stock. I don't know who came up with the idea that changing the resolution would help battery life, but while it won't hurt it won't help either. It would be like me changing the resolution of a laptop from 1600x900 to 1024x768. The images get distorted at the new resolution but all the pixels are still drawing power as needed to display the images. The display on the Nexus 6 or any smartphone for that matter is no different.
right, its just people that don't know better that keep telling others that reducing your "screen size" will improve your battery. but it will not.
Strephon Alkhalikoi said:
To fix, reset your resolution to stock. I don't know who came up with the idea that changing the resolution would help battery life, but while it won't hurt it won't help either. It would be like me changing the resolution of a laptop from 1600x900 to 1024x768. The images get distorted at the new resolution but all the pixels are still drawing power as needed to display the images. The display on the Nexus 6 or any smartphone for that matter is no different.
Click to expand...
Click to collapse
simms22 said:
right, its just people that don't know better that keep telling others that reducing your "screen size" will improve your battery. but it will not.
Click to expand...
Click to collapse
Oh...well thanks for the replies! Guess I'll just switch back to 1440p then.
It totally baffles me that people buy a super-resolution phone and then play with the internals, with all the risks that tweaking carries, just to degrade the display. It's also never made sense to me that it would make any difference anyway, since the same number of pixels still have to be manipulated (as Strephon says) even if they're duplicating the same colour.