wm size 2160x3840
wm density 640
All it s fine .i dont have any issue !
Is this real 4k now that we have marshmellow? I remember somebody saying it wasn't true 4k just by changing the density.
Also how is the 4k support with apps? Vr? And moonlight game streaming in 4k? kinda been waiting for this ever since the 4k display was announced but I can't test it until later this week.
Also I'd suggest hiding away that status and navigation bar and using an app called "simple control" .. Thers a simple command on adb to hide them. it really helps free your screen lol
tried it, having serious problems with swiftkey! It seems to be super-zoomed, only 3 buttons visible. Tried deleting it's cache.
Any suggestion?
You will have issues changing the DPI and the WM size... also the resolution is locked in the kernel, what you're doing is emulating 4K resolution....
Battery life will suffer and the device will get warm under normal load.... stick with 1080p and 320dpi , much better in my opinion
thank you, that makes sense!
Tried 320dpi right now, swiftkey still makes probs...
Interesting observation about this with DPI of 640 - the stock launcher now allows you to enable auto-rotate in the options menu. It doesn't allow you when running stock DPI or stock resolution. This leads me to assume this is the same launcher software as is running on the Xperia tablets too.
Xeon said:
You will have issues changing the DPI and the WM size... also the resolution is locked in the kernel, what you're doing is emulating 4K resolution....
Battery life will suffer and the device will get warm under normal load.... stick with 1080p and 320dpi , much better in my opinion
Click to expand...
Click to collapse
I go for 280dpi myself. May I ask why you go with 320dpi?
jplempka said:
I go for 280dpi myself. May I ask why you go with 320dpi?
Click to expand...
Click to collapse
I go for 320 dpi because I get extra space for icons 7 vs 5 vertically and I get much bigger visual space ( chrome / whatsapp ) etc.
Anything below that gives me trouble. And if you want to change your dpi you better do it in 120 steps or 180 steps ( 0 - 160- 320 -480 etc.. ) as apps seem to offer the best compatibility ( Android rule )
Xeon said:
I go for 320 dpi because I get extra space for icons 7 vs 5 vertically and I get much bigger visual space ( chrome / whatsapp ) etc.
Anything below that gives me trouble. And if you want to change your dpi you better do it in 120 steps or 180 steps ( 0 - 160- 320 -480 etc.. ) as apps seem to offer the best compatibility ( Android rule )
Click to expand...
Click to collapse
Ah ok, thanks, but 280 hasn't given me any compatibility problems with any apps (so far).
I agree with the 1080 and 320dpi. Device runs much smoother and doesn't get anywhere near as hot but still gives me the screen real-estate I was after.
Thanks
NJ72 said:
I agree with the 1080 and 320dpi. Device runs much smoother and doesn't get anywhere near as hot but still gives me the screen real-estate I was after.
Thanks
Click to expand...
Click to collapse
So what then is the default DPI? As I have not altered anything and now certain Xposed modules do not work on MM, so I am left with a dodgy layout that does not give me a great deal of space and I prefer the stock launcher.
I agree with 320,but one major problem is the incoming call screen is distorted. Try locking the device and recieve an incoming call.
I have tried all dpi and all resolutions like 2k and 4k. Nothing works expect stock 1080p and 480dpi
Mobfigurz said:
So what then is the default DPI? As I have not altered anything and now certain Xposed modules do not work on MM, so I am left with a dodgy layout that does not give me a great deal of space and I prefer the stock launcher.
Click to expand...
Click to collapse
Default DPI is 480
Sent from my Z5 Premium using XDA Labs
I agree with 320dpi,but one major problem is the incoming call screen is distorted. Try locking the device and recieve an incoming call.
I have tried all dpi and all resolutions like 2k and 4k. Nothing works expect stock 1080p and 480dpi
how about instagram. anyone having issue?
How about unlocking the bootloader and changing DPI on build.prop. Does it fix all the glitches? 320 seems to be small. I prefer 400
now...with 6.0.1 screenshoots are in 4k!
herasymcuk said:
now...with 6.0.1 screenshoots are in 4k!
Click to expand...
Click to collapse
What about battery life? How much SOT? And smoothness?
I've been using 380 DPI @ 1080, no issues with anything that I notice.
Changed to 4K, had problems with clock showing in bar at top of screen with
wm 800
and
wm 640
Hey there. How did you manage to have 6 apps in home bar? Thanks.
herasymcuk said:
now...with 6.0.1 screenshoots are in 4k!
Click to expand...
Click to collapse
I also noticed that.
But they seems to be an anti-aliased version of a full HD resolution.
I took a detail of a Chrome website screenshot in 4K and downscaled it to 1080 and here's the result:
Related
It annoys me to only have one notification icon visible in portrait mode, especially since I'm running the 7p in 140DPI mode and have plenty of space there for more icons. Does anyone know how to increase the amount of icons on the status bar?
I run mine at 130 and it seemed to be able to accommodate 4 icons (including that stupid zoom/stretch icon).
rendler said:
I run mine at 130 and it seemed to be able to accommodate 4 icons (including that stupid zoom/stretch icon).
Click to expand...
Click to collapse
Is that in portrait mode? And they actually display, not just that there seems to be room enough?
EDIT: set mine to that too and now I get multiple...weird
What do you use to set the dpi?
ALso, wouldnt this make everything else looks weird? I.e. Go Launcher, widgets, etc.
DPI changer or what it's called. Doesnt make anything look weird, just makes icons and such smaller. Gives you more room for "content".
Tried 130DPI, but changed back to 140. Don't like the added stuff ADW displays at that DPI,
What is the stock dpi? Just rooted and changed the dpi but can't remember what the default was. 160?
Sent from my GT-P6210 using xda premium
yup... its 160
edan1979 said:
yup... its 160
Click to expand...
Click to collapse
Thanks.
Sent from my GT-P6210 using xda premium
Hmm, downloaded DPI Changer and when run, it said it "...unable to read configuration file..."
I am rooted and SU show it allows DPI Changer.
wait a minute there...
won't a lower dpi than the default 160 display stuff bigger on the screen and thus have less room for icons and stuff. so, how did u get more notification icons with lower dpi?
fasacosta said:
won't a lower dpi than the default 160 display stuff bigger on the screen and thus have less room for icons and stuff. so, how did u get more notification icons with lower dpi?
Click to expand...
Click to collapse
No, but I understand why you would think that. Android decides interface element sizes based on screen size, not resolution, since a finger needs the same physically sized button no matter what resolution it's displayed at. The OS is unaware of the screen size, but is aware of its own resolution and DPI. The screen size is then given by those two numbers. If you lower the DPI the OS then thinks it has a bigger screen on its hands because the same resolution with a lower DPI than before must imply a larger screen, so it changes the layout based on that
I am trying to change the DPI with:
adb shell wm density 300
the above works correctly. but anything lower, the screen continuously flickers and is unusable.
for example, can't get the following to work:
adb shell wm density 200
any suggestions?
once we get root, this becomes very easy!!! thanks.
why would someone change the density from 480 (stock set in build.prop) to 200? i think its too low density,that all icons and text will be too small.
200 may be too low, but i like to see more contents on the screen. may be 300 is optimal.
Do you have any luck with this? When I change to 320 the navbar is blank in landscape.
ok, i am able to change the lcd density to 360 without issues.
anything less than 300 (say 280), the screen keeps flickering and it is unusable. don't know why.
deepasadish said:
ok, i am able to change the lcd density to 360 without issues.
anything less than 300 (say 280), the screen keeps flickering and it is unusable. don't know why.
Click to expand...
Click to collapse
maybe, because it too low?
DallasCZ said:
maybe, because it too low?
Click to expand...
Click to collapse
Lol. With my nexus 4 I was able to go up to 160 IIRC.
deepasadish said:
Lol. With my nexus 4 I was able to go up to 160 IIRC.
Click to expand...
Click to collapse
I dont know what is IIRc, but the DPI of nexus 4 is 318 so going to 160 is 50%.
Idol3 has 403 so 200 is below 50% (anyway in build.prom is dPI set to 480 ). I think its too low res and the system is nod made for such low res. It simly dont know how to handle it.
Just my opinion.
DallasCZ said:
I dont know what is IIRc, but the DPI of nexus 4 is 318 so going to 160 is 50%.
Idol3 has 403 so 200 is below 50% (anyway in build.prom is dPI set to 480 ). I think its too low res and the system is nod made for such low res. It simly dont know how to handle it.
Just my opinion.
Click to expand...
Click to collapse
you may be right. i am hoping with CM ROM (and good kernel) it may go all the way. for now i am satisfied with 340.
btw, chrome just doesn't go into tablet UI even at 300.
ps. IIRC - if i recall correctly. thanks.
deepasadish said:
you may be right. i am hoping with CM ROM (and good kernel) it may go all the way. for now i am satisfied with 340.
btw, chrome just doesn't go into tablet UI even at 300.
ps. IIRC - if i recall correctly. thanks.
Click to expand...
Click to collapse
how does look the syste mlike in 340DPI? it must be unreadable
deepasadish said:
I am trying to change the DPI with:
adb shell wm density 300
the above works correctly. but anything lower, the screen continuously flickers and is unusable.
for example, can't get the following to work:
adb shell wm density 200
any suggestions?
once we get root, this becomes very easy!!! thanks.
Click to expand...
Click to collapse
I totally forgot about this command to change DPI! I am so glad you posted this. I was about to root my phone just so I could change DPI. I hate big icons and text. I will end up rooting anyway but this way I don't have to eff with the build.prop as some people have said causes issues with this phone. I set mine to 360 which is perfect... Nova launcher will help me optimize from there
Thanks
DallasCZ said:
how does look the syste mlike in 340DPI? it must be unreadable
Click to expand...
Click to collapse
not really. just try it out - you have nothing to lose and you can easily revert back.
once you get used to the increased screen real estate, you will never go back.
sort of reminds me when I went from 1024x768 to 1280x1024 resolution on some monitor some 15+ years ago.
I experimented at 360 and 400. Both looked good. No strange behavior in the short time I used each of them. I'm not sure what I'll do. I liked 400 a little better than 360. But I might live with the stock 480, too, even though for some things, I preferred the lower dpi. It is like going to higher resolution on a computer monitor and this screen is big enough to benefit.
ROM Toolbox is good for these kinds of edits, though direct editing of build.props is easy enough. Make a backup of that file before you edit it.
Navbar in Landscape
deepasadish said:
you may be right. i am hoping with CM ROM (and good kernel) it may go all the way. for now i am satisfied with 340.
btw, chrome just doesn't go into tablet UI even at 300.
ps. IIRC - if i recall correctly. thanks.
Click to expand...
Click to collapse
Does your navbar work properly in landscape at 340? Mine won't work at 320, it's blank.
dbjungle said:
Does your navbar work properly in landscape at 340? Mine won't work at 320, it's blank.
Click to expand...
Click to collapse
yes, works at 340.
maigre said:
I experimented at 360 and 400. Both looked good. No strange behavior in the short time I used each of them. I'm not sure what I'll do. I liked 400 a little better than 360. But I might live with the stock 480, too, even though for some things, I preferred the lower dpi. It is like going to higher resolution on a computer monitor and this screen is big enough to benefit.
ROM Toolbox is good for these kinds of edits, though direct editing of build.props is easy enough. Make a backup of that file before you edit it.
Click to expand...
Click to collapse
Once xposed framework is working on the Alcatel Idol 3 you can use the "app settings" module to allow per app dpi settings.
Has anyone changed their phones DPI through build prop? What are some safe values?
I'll be posting a guide on how to do this soon, if you keep an eye out
Sent from my LG-H950 using XDA-Developers mobile app
404 on my Flex 2.
Use le dpi changer from play store and check"use wm shell" .
Works for any number of dpi , but lg apps will work only for dpi >400.
I am using 400 as the physical density of the screen is 403. LG got it wrong.
jmd.desai08 said:
Use le dpi changer from play store and check"use wm shell" .
Works for any number of dpi , but lg apps will work only for dpi >400.
Click to expand...
Click to collapse
This is a bad idea, because changing DPI through "wm shell density" breaks quite a few apps.
iDefalt said:
I'll be posting a guide on how to do this soon, if you keep an eye out
Click to expand...
Click to collapse
A guide for changing a single line in build.prop?
Offtopic: I´d really like to meet that guy who decided that displaying less content on a 5,5" Flex 2 than on most 4,5" phones from other manufacturers is a good idea. If it weren´t possible to fix the DPI, I would have returned the phone the day I bought it.
jmd.desai08 said:
Use le dpi changer from play store and check"use wm shell" .
Works for any number of dpi , but lg apps will work only for dpi >400.
Click to expand...
Click to collapse
what about quick settings icons? they got even bigger than before, everything else got smaller..
They get smaller with everything else
jmd.desai08 said:
They get smaller with everything else
Click to expand...
Click to collapse
Yeah, with dpi lower than 400 with texdroider dpi , they got smaller too. But with le dpi changer and dpi over 400 quicksetting icons got even bigger than default ones and text were misplaced.
My phone is on 400 dpi(changed with le dpi changer shell wm ) , everything is smaller and no text misplace (i m on gf2 mods 4.7)
Have you checked shell wm ?
jmd.desai08 said:
My phone is on 400 dpi(changed with le dpi changer shell wm ) , everything is smaller and no text misplace (i m on gf2 mods 4.7)
Have you checked shell wm ?
Click to expand...
Click to collapse
of course, without checking it, that app doesnt work. Can you post your quicksettings screenshot?
What is the difference between using these apps and just modifying the build.prop? I did modify build.prop and am quite pleased with the results, even though in 2-3 apps the text placement is a little odd.
IxBUSTERxI said:
What is the difference between using these apps and just modifying the build.prop? I did modify build.prop and am quite pleased with the results, even though in 2-3 apps the text placement is a little odd.
Click to expand...
Click to collapse
because of apps
Here you go @le grande magnetto
https://goo.gl/photos/phveyrV5R7ijARAx9
AppSettings Xposed 1.13 doesn't seem to work correctly (e.g. changing DPI works but resolution is the same). Is there another way?
I down-scaled my OPO's resolution to 720p from 1080p and now the map in Waze has bigger icons. Changing the global DPI doesn't help as everything but the map elements change. Here is how it's like: http://imgur.com/a/vsW7L (didn't show the full map to avoid giving out private info)
I've tried Screen Shift (playstore) also, but it's kinda wonky. So I'm looking for a way to make Waze think I'm still using 1080p.
virseph said:
AppSettings Xposed 1.13 doesn't seem to work correctly (e.g. changing DPI works but resolution is the same). Is there another way?
I down-scaled my OPO's resolution to 720p from 1080p and now the map in Waze has bigger icons. Changing the global DPI doesn't help as everything but the map elements change. Here is how it's like: http://imgur.com/a/vsW7L (didn't show the full map to avoid giving out private info)
I've tried Screen Shift (playstore) also, but it's kinda wonky. So I'm looking for a way to make Waze think I'm still using 1080p.
Click to expand...
Click to collapse
Why using 720p?
evronetwork said:
Why using 720p?
Click to expand...
Click to collapse
Faster/less heat/more battery especially when gaming. That's what I noticed, though YMMV
virseph said:
Faster/less heat/more battery especially when gaming. That's what I noticed, though YMMV
Click to expand...
Click to collapse
Why not go lower frequency on cpu and be ok? games use GPU so you'll be fine if you use e.g. 2GHz instead of 2.5GHz(@2.45)
If you want to cripple your phone you can do 480p, underclock it to 1.5GHz cpu and 300MHz gpu(due to 480p you won't need much gpu horsepower) and the phone should last more than 2 days easy
evronetwork said:
Why not go lower frequency on cpu and be ok? games use GPU so you'll be fine if you use e.g. 2GHz instead of 2.5GHz(@2.45)
If you want to cripple your phone you can do 480p, underclock it to 1.5GHz cpu and 300MHz gpu(due to 480p you won't need much gpu horsepower) and the phone should last more than 2 days easy
Click to expand...
Click to collapse
Why would I want to underclock when I want it to be faster? I certainly do not want to cripple my phone as you are suggesting, but I find there isn't much of a difference to the screen between 720p and 1080p.
Anyway, back on topic of how to make Waze appear correctly on 720p in OPO. Thanks.
virseph said:
Why would I want to underclock when I want it to be faster? I certainly do not want to cripple my phone as you are suggesting, but I find there isn't much of a difference to the screen between 720p and 1080p.
Anyway, back on topic of how to make Waze appear correctly on 720p in OPO. Thanks.
Click to expand...
Click to collapse
Just use 1080p, it doesn't have much difference(my above message was irony ). I'll tell you one secret, all displays have only one resolution aka native resolution, in every other resolution they don't display things properly
If you insist in keeping that config and it's only issue is in a particular app, I'd suggest you talk to the dev, he might be able to help you much better than most of us here :good:
You can use app settings, at least on android 5.1, haven't tested it on 6.0.1 yet though.
To do it I needed to change selinux from enforced to permissive. I can't remember if I used a custom app settings either but here's the one I used.
https://mega.nz/#!MYMnVZbJ!mFtkWpSlKuM7GP9Lj1gsnmNNLJuokLy9_lCpgd79TPw
Edit: it works on android 6.0.1 with dirty unicorns ROM. Don't know if you need to change selinux on this but I did anyway. You have to reboot after applying settings though.
For my settings app I have DPI at 280 and font scaling at 140 screen (dp) is 800x1200. That enables the tablet look. Some themes disable tablet mode too, so try stock theme before using app settings.
my phone currently have 240 dpi as default.. btw here is the specs https://pinoyscreencast.net/item/cherry-mobile-omega-lite-2/
so i wanna know if i can change it to 180 or 160 dpi and what will improve to my phone after lowering it.. thanks..
balot.ko said:
my phone currently have 240 dpi as default.. btw here is the specs https://pinoyscreencast.net/item/cherry-mobile-omega-lite-2/
so i wanna know if i can change it to 180 or 160 dpi and what will improve to my phone after lowering it.. thanks..
Click to expand...
Click to collapse
it only makes things smaller on a screen. So, you can fit more stuff on a screen.
Ashwinrg said:
it only makes things smaller on a screen. So, you can fit more stuff on a screen.
Click to expand...
Click to collapse
one more question, will it reduce the quality of my camera like when taking pics and recording vids?
balot.ko said:
one more question, will it reduce the quality of my camera like when taking pics and recording vids?
Click to expand...
Click to collapse
I don't think it will affect on camera or recording because it only related to display.
If you are trying to change screen dpi with build prop editing then it having a chances of bricking your device if anything goes wrong.
Instead of use "app settings" app to change dpi per app basis. But it requires xposed framework installed to be work.
Oh I have the same DPI and I lowered it to 180 easily... It won't affect the quality of anything and won't ruin anything..
You'll feel weird at the beginning then you're gonna get used to it
Just get a Root Browser then go to /system/build.prop then search for " ro.sf.lcd_density=240" and change the number to 180, save then reboot
Sent from the beige bra section at Target.