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
Related
Hi,
To start with, I love the screen of the Infuse 4G but I don't really have eye problems so I want the fonts to be smaller and maybe the icons too. I'm wondering if there is a way to make all the fonts smaller or make the resolution higher? Its just that I find that the texts to big for my taste so I wanted to change it. Hope someone replies to my email.
Thanks!
Find LCD density in the market, needs root though.
Nitrality, find it in the market. Its better than LCD density and it stays after boot/reboots, also has other options in which are quite useful
Big dog Infuse I997 GB KJ4
ROM Toolbox, has all the useful tools rolled into one. build.prop editor for LCD density as well as WIFI scan interval, VM heap size, etc. Also has setcpu built in, app manager, ROM utilities, et al.
Thanks guys!
Thanks guys! I've tried the LCD Density and making everything small is only good on some stuff. When it comes to the Notification bar, it gets too small to see, is there any app that you can balance everything? Or should I just create my own theme?
djbuan said:
Thanks guys! I've tried the LCD Density and making everything small is only good on some stuff. When it comes to the Notification bar, it gets too small to see, is there any app that you can balance everything? Or should I just create my own theme?
Click to expand...
Click to collapse
Try setting your LCD density at 200. That should give you a good balance.
diablo009 said:
Try setting your LCD density at 200. That should give you a good balance.
Click to expand...
Click to collapse
200 is enough but I just noticed that everything got messed up, like the positions of elements like icons, texts, labels and stuff
I'm set 182
Big dog Infuse I997 GB KJ4
djbuan said:
200 is enough but I just noticed that everything got messed up, like the positions of elements like icons, texts, labels and stuff
Click to expand...
Click to collapse
That's strange! Except for stock dialer, none of my other apps are conked! Everything is so perfect on my phone.
fargonaz said:
Find LCD density in the market, needs root though.
Click to expand...
Click to collapse
+1
I set mine between 190 and 220
I keep changing back and forth.
I agree, the screen is sooo big, there's so much workspace, that is why I run the screen density smaller and cram stuff on our huge screen
be careful too... some apps wont download from the market, you will get an error saying the app in incompatible with our device... simple way around that...
switch back to stock density (240)... download the app, run it once just to be sure... and switch back to whatever density you are comfortable running..
Hi, is there any way to change icon size's in new kitkat launcher ? Icons are waay to big and I dont want to switch to nova or anything else.
It'd require a mod to the launcher itself, that'll take a while. This was an intentional move and it looks a lot better.
Well, that is the matter of personal preference, for me it looks a waay to huge
Apex launcher has the option.
Sent from my Nexus 7 using XDA Premium 4 mobile app
I hated the general size of everything too so first thing I did was to unlock the bootloader, root and edit the build.prop to make everything smaller.
The default density is 480 but move it down to 300 or so and everything looks alright.
The launcher automatically adds more columns and rows as well which is useful.
tristancook said:
I hated the general size of everything too so first thing I did was to unlock the bootloader, root and edit the build.prop to make everything smaller.
The default density is 480 but move it down to 300 or so and everything looks alright.
The launcher automatically adds more columns and rows as well which is useful.
Click to expand...
Click to collapse
"or so"?
tristancook said:
I hated the general size of everything too so first thing I did was to unlock the bootloader, root and edit the build.prop to make everything smaller.
The default density is 480 but move it down to 300 or so and everything looks alright.
The launcher automatically adds more columns and rows as well which is useful.
Click to expand...
Click to collapse
This is a great suggestion (but I'd look into doing 380 or 400). The problem with this is that everything (even the apps) uses that density. What would be ideal is to only have the launcher use the lower density and the rest of the apps be normal. Not sure if that's possible by editing files. Any help would be appreciated.
I used texdroider_dpi to set mine at 420DPI. Looks way better now. I couldn't stand how huge the icons and everything looked. Try that out.
I'll end up using Nova prime to resize and change the icon pack.
Question: Why is 480ppi set?
Hi,
probably a stupid question, but I hope somebody can explain that to me:
- Nexus 4 build.prob setting is 320 and datasheet says 320 ppi
- Nexus 7 2013 build.prob setting is 320 and datasheet says 323 ppi
and now what the hack:
- Nexus 5 build.prob setting is 480 and datasheet says 445 ppi
Has anybody an idea what this is all about? I am confused.
Thanks for this. I think 420 is great.
I have another issue with the app drawer though. Is there a way to do vertical scrolling on the stock launch thru the build.prop file or another file that's not crazy difficult or impossible? I know nova launcher can do it, but it just isn't as nice as the experience launcher quite yet. If I can get vertical scroller i might be able to completely part with nova launcher.
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.
Was searching a little but couldn't find an answer to this. I'm interested in this phone, I was able to play with it a little, but really, the dpi is too high for a 6" screen. Would be interesting to know if/how a 400/420dpi works on this device. Thanks!
I was just going to ask the same thing actually. Last night I started messing with it but it's very weird. For one, there are two DPI lines in build.prop, which you seem to have to change both of to get any kind of change. I have them now at 400 with the view mode set to small, and it's too small. But, the weird thing is, anything over 410 is too big. It doesn't change like a normal phone does. I have a feeling the "view mode" changes shell density instead of DPI and causes some weirdness. I may mess around with some shell density commands later today to get it just right. Anyone know what the stock shell density is?
loudog3114 said:
I was just going to ask the same thing actually. Last night I started messing with it but it's very weird. For one, there are two DPI lines in build.prop, which you seem to have to change both of to get any kind of change. I have them now at 400 with the view mode set to small, and it's too small. But, the weird thing is, anything over 410 is too big. It doesn't change like a normal phone does. I have a feeling the "view mode" changes shell density instead of DPI and causes some weirdness. I may mess around with some shell density commands later today to get it just right. Anyone know what the stock shell density is?
Click to expand...
Click to collapse
Can you try Neo Density app? I don't know if it works ok with the Mate8, but I used it on phones where changing the dpi was a little problematic.
Yup. I'm at 320 with the small stock settings too
albireox said:
Can you try Neo Density app? I don't know if it works ok with the Mate8, but I used it on phones where changing the dpi was a little problematic.
Click to expand...
Click to collapse
I did, that just changes the typical ro.sf.lcd_density= value. The best I have found is that if you drop that value to 400, the "small" view mode goes to extra small. But changing the value to anything lower than 400 has no effect (I tried as low as 290) and anything over 410 seems to also have no effect on stock.
loudog3114 said:
I did, that just changes the typical ro.sf.lcd_density= value. The best I have found is that if you drop that value to 400, the "small" view mode goes to extra small. But changing the value to anything lower than 400 has no effect (I tried as low as 290) and anything over 410 seems to also have no effect on stock.
Click to expand...
Click to collapse
I guess it's ok with dpi400, should be much better than the stock. How the stock Huawei apps are scaled?
albireox said:
I guess it's ok with dpi400, should be much better than the stock. How the stock Huawei apps are scaled?
Click to expand...
Click to collapse
400 is very very small. I have 20/20 vision and love a lower dpi, but I think its too small to use on a daily basis at a typical viewing distance. Especially in the dark. I went back to stock for now.
Mostly everything scales fine, but there are weird issues as if we had used wm shell density to change the density vs build.prop. Some text/icons are cut off by the item below it in the notification panel, and backgrounds dont scale properly when swiping through home screens. Not a huge deal, but just common issues when using wm shell density, even though I didn't.
I'm on 366 dpi. Let the stock dpi setting at large then change the dpi in build.prop. The stock will change automatically after reboot to medium. For the quick toggles add this lines to build.prop : ro.config.toolbox_port_column=3
ro.config.toolbox_port_row=3
ro.config.toolbox_land_column=4
ro.config.toolbox_land_row=2
Only one issue exists, if dpi is to low the notification drop down will show the recycle bin in the middle of the screen, so it will use the half space. If u have some notification u must scroll them
Huawei Mate 8 L29~B162 using Tapatalk
dlorean said:
I'm on 366 dpi. Let the stock dpi setting at large then change the dpi in build.prop. The stock will change automatically after reboot to medium. For the quick toggles add this lines to build.prop : ro.config.toolbox_port_column=3
ro.config.toolbox_port_row=3
ro.config.toolbox_land_column=4
ro.config.toolbox_land_row=2
Only one issue exists, if dpi is to low the notification drop down will show the recycle bin in the middle of the screen, so it will use the half space. If u have some notification u must scroll them
Huawei Mate 8 L29~B162 using Tapatalk
Click to expand...
Click to collapse
Can you post a screen shot? I have a feeling yours is probably the same that I was able to achieve.
https://drive.google.com/file/d/0B7TwALBor0ngM0ZXTS1HVDdjRkk/view?usp=docslist_api
https://drive.google.com/file/d/0B7TwALBor0ngMmZRdlhvVkhQc0k/view?usp=docslist_api
https://drive.google.com/file/d/0B7TwALBor0ngLVdFdnIyWXlOaGc/view?usp=docslist_api
Huawei Mate 8 L29~B162 using Tapatalk
dlorean said:
https://drive.google.com/file/d/0B7TwALBor0ngM0ZXTS1HVDdjRkk/view?usp=docslist_api
https://drive.google.com/file/d/0B7TwALBor0ngMmZRdlhvVkhQc0k/view?usp=docslist_api
https://drive.google.com/file/d/0B7TwALBor0ngLVdFdnIyWXlOaGc/view?usp=docslist_api
Huawei Mate 8 L29~B162 using Tapatalk
Click to expand...
Click to collapse
Can you show the desktop? Trying to compare my status bar to yours. Mine was TINY.
https://drive.google.com/file/d/0B7TwALBor0ngbjl6T2FSOTllblU/view?usp=docslist_api
If u change dpi with the stock changer and then in the build.prop, u get a tiny status bar. Stay on large view and then change dpi in build.prop. Wasted some time with testing to find this out
Huawei Mate 8 L29~B162 using Tapatalk
dlorean said:
https://drive.google.com/file/d/0B7TwALBor0ngbjl6T2FSOTllblU/view?usp=docslist_api
If u change dpi with the stock changer and then in the build.prop, u get a tiny status bar. Stay on large view and then change dpi in build.prop. Wasted some time with testing to find this out
Huawei Mate 8 L29~B162 using Tapatalk
Click to expand...
Click to collapse
Yeah that's about what I got when I was doing 400 dpi and small view mode. Whats really odd is that, unlike any other phone I have had, if you bump the DPI up by 5 or 10, you don't get the minor increase in size you would expect. It just stays the same until it makes a massive change in size.
dlorean said:
https://drive.google.com/file/d/0B7TwALBor0ngbjl6T2FSOTllblU/view?usp=docslist_api
If u change dpi with the stock changer and then in the build.prop, u get a tiny status bar. Stay on large view and then change dpi in build.prop. Wasted some time with testing to find this out
Huawei Mate 8 L29~B162 using Tapatalk
Click to expand...
Click to collapse
Absolutely love your icon pack. Is it stock or downloaded?
Odesláno z mého SM-N910F pomocí Tapatalk
Is it possible to change the DPI without root ? i want tablet mode. i've tried with adb but it does not work...
Thanks
Boosik said:
Absolutely love your icon pack. Is it stock or downloaded?
Odesláno z mého SM-N910F pomocí Tapatalk
Click to expand...
Click to collapse
It's from play store, name is rotox. Using it with nova launcher.
Huawei Mate 8 L29~B162 using Tapatalk
loudog3114 said:
Yeah that's about what I got when I was doing 400 dpi and small view mode. Whats really odd is that, unlike any other phone I have had, if you bump the DPI up by 5 or 10, you don't get the minor increase in size you would expect. It just stays the same until it makes a massive change in size.
Click to expand...
Click to collapse
The stock changer and build.prop disturb each other. It's a nice feature from Huawei, but poorly implemented
Huawei Mate 8 L29~B162 using Tapatalk
I've edited build.prop directly after installing Rom. Only the ro.lcd.density to 320 and it works like a charm. The display setting changed to small automatically after reboot.
pappschlumpf said:
I've edited build.prop directly after installing Rom. Only the ro.lcd.density to 320 and it works like a charm. The display setting changed to small automatically after reboot.
Click to expand...
Click to collapse
I did 320 but lost one handed mode. Bumped it up to 380, got one hand mode back, and it is the same size on small.
Now I'm back to B152 because of this
B162 https://drive.google.com/file/d/0B7TwALBor0ngLVdFdnIyWXlOaGc/view?usp=docslist_api
B152 https://drive.google.com/file/d/0B7TwALBor0ngWXVqNmcySUZkdWs/view?usp=docslist_api
Both at 367dpi
What's going wrong with the programming for different countries?
Huawei Mate 8 L29~B162 using Tapatalk
You can change the dpi on the stock ROM without ROOT by chaging the "smallest width" setting in developer settings. I have mine set to 550 it's looks amazing!
Here is a screenshot of setting menu at 550.
You could also just change the setting in Settings > Display > Advanced > Display Size > Small
411 is default. 434 is the smallest you can go to get an extra icon of space on the status bar (meaning you can fit another icon before you get the overflow dot). 453 is the magic number for the notification side. "Small" per the post above is 484.
Worth it, you can barely notice a difference otherwise. Now if only we had an option to do ONLY the status bar... then we'd be cookin. But this will do for now.
Pure+ said:
You could also just change the setting in Settings > Display > Advanced > Display Size > Small
Click to expand...
Click to collapse
Nope it's not the same. Putting that setting on small does not work on everything. And this way you can go even smaller then the "small" setting.
Celeras said:
411 is default. 434 is the smallest you can go to get an extra icon of space on the status bar (meaning you can fit another icon before you get the overflow dot). 453 is the magic number for the notification side. "Small" per the post above is 484.
Worth it, you can barely notice a difference otherwise. Now if only we had an option to do ONLY the status bar... then we'd be cookin. But this will do for now.
Click to expand...
Click to collapse
I have the setting pure+ posted on normal and put the setting I posted on 551 I feel like that's the perfect mix for me ATM. I will keep playing with it to see if I can find a better combo.
vwgti18 said:
Nope it's not the same. Putting that setting on small does not work on everything. And this way you can go even smaller then the "small" setting.
Click to expand...
Click to collapse
It actually is. If you change the setting and go into dev options it shows the dpi changed. Only difference is it's defaulting to a predetermined dpi
Pure+ said:
It actually is. If you change the setting and go into dev options it shows the dpi changed. Only difference is it's defaulting to a predetermined dpi
Click to expand...
Click to collapse
Ah yes you are right. Thanks for the heads up.
The small setting only changes it to 484 too big for me still! I like it around 550
vwgti18 said:
Ah yes you are right. Thanks for the heads up.
The small setting only changes it to 484 too big for me still! I like it around 550
Click to expand...
Click to collapse
Full disclosure I didn't check to verify this, although I already suspected it, until you said something lol
Pure+ said:
Full disclosure I didn't check to verify this, although I already suspected it, until you said something lol
Click to expand...
Click to collapse
Yeah the olny problem doing it that way is that the change is not enough to really notice a difference.
unfortunately doing it this way compared to doing it via build.prop makes Swiftkey tiny as well
Any one have a suggestion for something in between stock 411 and small 484? Small is just a bit too much for my taste so looking for a happy medium
can we change the DPI through build.prop yet now that we have root?
I added ro.sf.lcd.density=550 and it doesnt seem to be doing anything
doing it through the developer options makes the keyboard unusable.
pr0adam said:
can we change the DPI through build.prop yet now that we have root?
I added ro.sf.lcd.density=550 and it doesnt seem to be doing anything
doing it through the developer options makes the keyboard unusable.
Click to expand...
Click to collapse
Which keyboard are you using?
I am using Gboard with dpi set to 551 and its fine.
vwgti18 said:
Which keyboard are you using?
I am using Gboard with dpi set to 551 and its fine.
Click to expand...
Click to collapse
SwiftKey but 550 was a bad example. I want to make everything smaller, so I went down to something like 450 and the keyboard was very hard to use. Same with the default Gboard
pr0adam said:
SwiftKey but 550 was a bad example. I want to make everything smaller, so I went down to something like 450 and the keyboard was very hard to use. Same with the default Gboard
Click to expand...
Click to collapse
Are you rooted? If so I can tell you how to make gboard bigger but I am not sure about Swiftkey
vwgti18 said:
Which keyboard are you using?
I am using Gboard with dpi set to 551 and its fine.
Click to expand...
Click to collapse
vwgti18 said:
Are you rooted? If so I can tell you how to make gboard bigger but I am not sure about Swiftkey
Click to expand...
Click to collapse
I am rooted yes so I would love to know besides the Gboard setting that increases the size.
pr0adam said:
I am rooted yes so I would love to know besides the Gboard setting that increases the size.
Click to expand...
Click to collapse
Here check if this will work for you! This is the method I was using on my pixel 2 xl it worked great, just one issue is sometimes I could not get the txt edit to save and had to edit the line then got to setting and force stop gboard then go back and save the text file.
https://www.xda-developers.com/gboard-tweaks-height-sensitivity/
vwgti18 said:
Here check if this will work for you! This is the method I was using on my pixel 2 xl it worked great, just one issue is sometimes I could not get the txt edit to save and had to edit the line then got to setting and force stop gboard then go back and save the text file.
https://www.xda-developers.com/gboard-tweaks-height-sensitivity/
Click to expand...
Click to collapse
Thanks for that link, worked for me on Gboard. Hopefully there will be a solution that I can still use Swiftkey but if not I will be going this route once I get home and adjust the DPI further
pr0adam said:
Thanks for that link, worked for me on Gboard. Hopefully there will be a solution that I can still use Swiftkey but if not I will be going this route once I get home and adjust the DPI further
Click to expand...
Click to collapse
I don't have the Pixel yet & I've never tried changing DPI, so forgive me if this doesn't help or if you've already tried this, but Swiftkey has a setting built in to resize the keyboard. I believe it's normally set at "medium", then there is a "large" & "largest" setting to make the keyboard bigger. Go to Swiftkey Settings>Typing>Resize.