I've rooted the phone and tried to change the god awful 640 density to something less wasteful, but am getting blocked in every manner:
- Root Explorer lets me edit and save the file, and even tells me that a backup has been created, but not changes are made (build.prop still has 640 immediately after, and no build.prop.bak is created)
- adb pull, edit and push also fails, telling me I've got RO filesystem, but adb remount doesn't work and suggests that I run adb root first, which results in this lovely message:
adbd cannot run as root in production builds
Has anyone been able to fit more things on their screen?!
su
wm density ###
I just used terminal emulator.
rayman2k1 said:
I've rooted the phone and tried to change the god awful 640 density to something less wasteful, but am getting blocked in every manner:
- Root Explorer lets me edit and save the file, and even tells me that a backup has been created, but not changes are made (build.prop still has 640 immediately after, and no build.prop.bak is created)
- adb pull, edit and push also fails, telling me I've got RO filesystem, but adb remount doesn't work and suggests that I run adb root first, which results in this lovely message:
adbd cannot run as root in production builds
Has anyone been able to fit more things on their screen?!
Click to expand...
Click to collapse
Are you using Xposed by any chance?
There's a module name "App Settings " , which let you change dpi per app? Without changing default system density....
Other than that to u can change it the way @Kama45 mention above.
DrakenFX said:
Are you using Xposed by any chance?
There's a module name "App Settings " , which let you change dpi per app? Without changing default system density....
Other than that to u can change it the way @Kama45 mention above.
Click to expand...
Click to collapse
figured that xposed would be the way to go. i have never installed xposed as most of the knobs i like twiddling were exposed by my rom of choice. if @Kama45's suggestion doesn't pan out, i might go that route
Delete
---------- Post added at 02:25 PM ---------- Previous post was at 02:17 PM ----------
Kama45 said:
su
wm density ###
I just used terminal emulator.
Click to expand...
Click to collapse
I just did this from ad shell and literally saw the screen change when I hit enter. I figured a reboot would be needed to take the change.
Does this change build.prop? I see ro.sf.lcd_density still shows 640.
And it survived the reboot.
Thanks!
thanks for the hints guys. however, wm density didn't work for me. i'm not going to dip in the xposed pool.
this phone's rom absolutely sucks. i think i'm just going to use my opo until someone with more smarts than me gets more gooder roms to runny on my phoney.
wifi drops every minute or so. downloads stop when screen is off. photos taken look terrible.
Barsky said:
Delete
---------- Post added at 02:25 PM ---------- Previous post was at 02:17 PM ----------
I just did this from ad shell and literally saw the screen change when I hit enter. I figured a reboot would be needed to take the change.
Does this change build.prop? I see ro.sf.lcd_density still shows 640.
And it survived the reboot.
Thanks!
Click to expand...
Click to collapse
strange. i don't see any change.
(have tried from terminal emulator and from adb shell)
EDIT: WHOA!! 'adb shell wm density 538' finally worked woohoo!! thank you!
rayman2k1 said:
thanks for the hints guys. however, wm density didn't work for me. i'm not going to dip in the xposed pool.
this phone's rom absolutely sucks. i think i'm just going to use my opo until someone with more smarts than me gets more gooder roms to runny on my phoney.
wifi drops every minute or so. downloads stop when screen is off. photos taken look terrible.
Click to expand...
Click to collapse
TBH, Along with Nova and a couple xPosed modules and this density fix, I am pretty darn happy. Sure, I'd change things. I'd like to remove quicktiles rather than just rearrange, for instance.
rayman2k1 said:
strange. i don't see any change.
(have tried from terminal emulator and from adb shell)
EDIT: WHOA!! 'adb shell wm density 538' finally worked woohoo!! thank you!
Click to expand...
Click to collapse
the problem with " adb shell wm density (command line) " is that causes some issues with other apps, that's the only reason why i use Xposed Module name " App Settings v1.13 " you can change DPI (density) per app and doesn't effect other system or users apps. but glad works for you.
rayman2k1 said:
thanks for the hints guys. however, wm density didn't work for me. i'm not going to dip in the xposed pool.
this phone's rom absolutely sucks. i think i'm just going to use my opo until someone with more smarts than me gets more gooder roms to runny on my phoney.
wifi drops every minute or so. downloads stop when screen is off. photos taken look terrible.
Click to expand...
Click to collapse
Try turning off smart power. Also go into power management and turn off power management per app. Otherwise when phone sleeps it throttles wifi and CPU performance.
Yaya444 said:
Try turning off smart power. Also go into power management and turn off power management per app. Otherwise when phone sleeps it throttles wifi and CPU performance.
Click to expand...
Click to collapse
Yeah I definitely did that and it resolved some issues. I'm still seing wifi drops for no apparent reason (screen on)
rayman2k1 said:
Yeah I definitely did that and it resolved some issues. I'm still seing wifi drops for no apparent reason (screen on)
Click to expand...
Click to collapse
I noticed problems with this phones wifi but doesn't drop for me. The signal on wifi bounces up and down. The Qualcomm wifi soc on this phone tops out at 433Mbps max. Also noticed much weaker overall signal strength than many other similar devices. ZTE went cheap on the wifi and maybe gimped the antenna design.
http://forum.xda-developers.com/axon-7/help/command-to-root-changes-to-persist-t3440276
I believe you haven't disabled system write protection many forums show this if it is your problem please post so others are aware when reading this. If this doesnt fix post too so can help further build.Prop edits should stay after reboot.
rayman2k1 said:
strange. i don't see any change.
(have tried from terminal emulator and from adb shell)
EDIT: WHOA!! 'adb shell wm density 538' finally worked woohoo!! thank you!
Click to expand...
Click to collapse
Did it mess up dialer, bell size and maps inapp icons?
Sent from my ZTE A2017U using Tapatalk
herzzreh said:
Did it mess up dialer, bell size and maps inapp icons?
Click to expand...
Click to collapse
It did. I ended up turning off write-protect on /system using the instruction at the link that @bhint15 provided, then editing the build.prop file, which is the preferred method of changing density throughout I believe
bhint15 said:
http://forum.xda-developers.com/axon-7/help/command-to-root-changes-to-persist-t3440276
I believe you haven't disabled system write protection many forums show this if it is your problem please post so others are aware when reading this. If this doesnt fix post too so can help further build.Prop edits should stay after reboot.
Click to expand...
Click to collapse
Thank you. That did the trick. I'm disappointed my google-fu didn't turn it up...
Also I used xposed to fix dialer and other apps to do per app dpi back to 640 I'm running 460 system dpi
rayman2k1 said:
It did. I ended up turning off write-protect on /system using the instruction at the link that @bhint15 provided, then editing the build.prop file, which is the preferred method of changing density throughout I believe
.
Click to expand...
Click to collapse
It indeed is. Does layout get messed up when you change DPI using this menthod? This is, honestly, my only reason for rooting.
herzzreh said:
It indeed is. Does layout get messed up when you change DPI using this menthod? This is, honestly, my only reason for rooting.
Click to expand...
Click to collapse
I don't think that it does. My dialer looks fine and the notification bell (which I think is a ridiculous "feature" to begin with) is also not gigantic like it was with "wm density 538". I haven't installed xposed...
That sounds promising! After you using 538?
Sent from my ZTE A2017U using Tapatalk
herzzreh said:
That sounds promising! After you using 538?
Click to expand...
Click to collapse
Yep. See attached
Related
Info from this thread originally - http://forum.xda-developers.com/showthread.php?t=760805
Since we are using larger screens google recommends we change our dpi from 240 to 160, this probably looks fine for stock builds but on sense builds everything looks crazy. I currently have mine(on a sense build) at 210 however feel free to change it to what is best for you.
to perform this modification
pull the build.prop from /system/build.prop
open the file using a text editor and change ro.sf.lcd_density=240 to ro.sf.lcd_density=160(or whatever number you choose)
then push the file back to /system/build.prob
(i used a paid app called root explorer for this process)
if you want you use terminal emulator or adb here are the commands:
su
cp /system/build.prop /sdcard
then once youve edited the file
cp /sdcard/build.prop /system
you can use the same commands over adb by entering adb shell
download the spare parts app from the market and untick the compatibility mode then reboot (this fixes the issues some apps have with scaling)
the result of this mod is more things fit on the screen e.g. lists and web pages and games like raging thunder 2 look better as they arent being stretched out as much.
i recommend for a sense build: 200 to 220
for a vanilla build 160-220
if anyone has any better numbers please post
SCREENSHOTS ON NEXT PAGE
TO MAKE USE OF THE EXTRA SPACE ON THE HOMESCREEN INSTALL ADW LAUNCHER AND SET THE COLUMNS AND ROWS TO 6X6 (SCREENSHOTS ON PAGE 6) , THE SAME CAN BE DONE FOR THE APP DRAW
http://members.ping.de/~sven/dpi.html
input the values for HD2, you get ~217 dpi if you want to be anal about it
I wonder what effect not specifying any DPI would have...
this would be great if the lockscreen wallpaper would be retained... changing the dpi messes with the static wallpapers set...
I've tried 200, looks ok. I've always thought that we need to up the dpi, at 240 its way too huge for our screen.
160 messed everything up for me, the notification bar etc only filled half the screen. Other than that it looked awesome though! 200 might be the best, would be good to hear other opinions, not got a great deal of time to test
Is there a way to do it without Root Explorer?
FreakyFerret said:
Is there a way to do it without Root Explorer?
Click to expand...
Click to collapse
Go to your windows mobile, then edit the same file from the same folder of the Android. (not sure whether this works on all build, Shu8i build does work)
jubeh said:
http://members.ping.de/~sven/dpi.html
input the values for HD2, you get ~217 dpi if you want to be anal about it
I wonder what effect not specifying any DPI would have...
Click to expand...
Click to collapse
217 looks like 220 and leaving it blank sets it 160(thats what it looks like i cant tell really since it is blank)
pongster said:
this would be great if the lockscreen wallpaper would be retained... changing the dpi messes with the static wallpapers set...
Click to expand...
Click to collapse
would using a higher res wallpaper fix this?
Jragar said:
160 messed everything up for me, the notification bar etc only filled half the screen. Other than that it looked awesome though! 200 might be the best, would be good to hear other opinions, not got a great deal of time to test
Click to expand...
Click to collapse
160 on sense didn't mess up my status bar although some widgeds dissappeared. Which build are you using?
Interesting thread. I am using Mattc 1.5b Froyo. Anybody tries this? I am afraid of screwing my almost perfect setup.
Let me know what setting you used.
xkravenx said:
Interesting thread. I am using Mattc 1.5b Froyo. Anybody tries this? I am afraid of screwing my almost perfect setup.
Let me know what setting you used.
Click to expand...
Click to collapse
im on the same build as you with 210
copy out ur android folder onto ur hardisk as backup before u do the mod and u are safe if ur screen becomes black or u dun like it or it glitches badly and u cant modify it since u cant see the screen display properly..
This is sick,now my screen looks massive.Thx 4 the info..
"I pity the fool that owns an iPhone 4"
Sent from my HD2 using XDA App
please can you post before and after pictures
with 220 most of the apps doesnt scale properly and some doesnt work at all. Back to 240.
I set mine to 210.
It's hard to see the difference. I use MattC 1.5b with Froyo version...
The icons for "folder organizer" look smaller. But everything else seems to be the same. e.g. the htc sense applications, home, etc.
Maybe my mind is playing tricks on me.
here are some screenshots from the dpi changed from 240 to 200
xcooling said:
please can you post before and after pictures
Click to expand...
Click to collapse
This is what I've tried with mattcnexusleo1.1_512....
the 240 / 200:
I like the 200, it makes the keyboard smaller enough for me to type easier.
**mods please delete my post. JJbdoggg raced me to it...only sec's late sorry...
the settings wont keep on shu8i builds... weird... i tried modifying build.prop both on the phone and on pc... after pushing and rebooting it doesnt change, it actually changes back to 240... i tried the spare parts workaround, unchecking compat. mode and still no luck. any ideaS?
palosjr said:
the settings wont keep on shu8i builds... weird... i tried modifying build.prop both on the phone and on pc... after pushing and rebooting it doesnt change, it actually changes back to 240... i tried the spare parts workaround, unchecking compat. mode and still no luck. any ideaS?
Click to expand...
Click to collapse
Yeah your right same goes with me. I can't change it either that is why i used mattcnexusleo1.1_512 build. It worked with it...
palosjr said:
the settings wont keep on shu8i builds... weird... i tried modifying build.prop both on the phone and on pc... after pushing and rebooting it doesnt change, it actually changes back to 240... i tried the spare parts workaround, unchecking compat. mode and still no luck. any ideaS?
Click to expand...
Click to collapse
/android/root/system/build.prop
apeatan said:
Yeah your right same goes with me. I can't change it either that is why i used mattcnexusleo1.1_512 build. It worked with it...
Click to expand...
Click to collapse
You change build for that ? o-o
Shubcraft have cyanogen mod, wich is much more easier to make updates, no need to push anything and its great if you do a mistake see post above
-great tip thanks ! My screen looks really huge now at 200.. The appdraw is impressive too ... I'll wait for tomorrow to see if these smaller fonts are still readable with the sun.
I tried searching for this info but I found nothing.
I'm trying to change the LCD density to something bigger on the E3D. Is it possible on the current method of temp rooting? If so what is the best setting?
I tried the LCD density changer app (at 280) and it turned the screen black and my phone froze. Anyone have any tips on this?
mmafighter077 said:
I tried searching for this info but I found nothing.
I'm trying to change the LCD density to something bigger on the E3D. Is it possible on the current method of temp rooting? If so what is the best setting?
I tried the LCD density changer app (at 280) and it turned the screen black and my phone froze. Anyone have any tips on this?
Click to expand...
Click to collapse
Have you tried a lower setting? LCD density might not work since theres not a kernel source yet...
I'm assuming the screen shuts off and takes a little bit for the settings to take effect. I also assume it requires a reboot... but it's because root does not stick all the way... So it doesn't work.
So at this time, I believe density change... is unsupported.
I think your both right. When I tried editing the build.prop file it would freeze up the super manger.
I seem to remember now that you mention it that I had to reboot my other android phone when when I changed the density. Of course that wouldn't work on a phone that you lose root when you reboot.
the screen turns black when I save the changes. I wait like ten minutes and it stays black.
I don't want to make the density smaller. I want to make everything look bigger.
Try using the fast boot option to reboot.. I do that and I get to keep root!
Sent from my HTC 3VO
kkman107 said:
Try using the fast boot option to reboot.. I do that and I get to keep root!
Sent from my HTC 3VO
Click to expand...
Click to collapse
+1
10 characters
But as soon as you apply the density change... screen goes black. You can't get to Fast reboot...
-3
enough chars for a valid post.
I know on my og EVO it did a soft reboot (straight to the boot animation) which in our case would not clear the RAM. So in theory it should work but I'm not sure. I'll try it when I get home in a couple days
Sent from my PG86100 using XDA Premium App
bump this now that s-off is achieved. anybody got it to work? i got s-off but im still on black screen with lcd density changer
Bentenrai said:
bump this now that s-off is achieved. anybody got it to work? i got s-off but im still on black screen with lcd density changer
Click to expand...
Click to collapse
+1 would be nice on this qhd screen..
I GOT it to work changing from 240 to 200 didn't try going bigger when i got the black screen I pulled the battery and rebooted so far I think its sticky !
Sent from my limited edition EVO 4D!
if you have S-OFF, just adb shell into phone and gain root...then edit the /system/build.prop file to look for density and change the value and reboot.
Sorry for bumping if someone's mentioned this before, but after trying to a find an app to easily change the density for months and continuously failing, i was quite excited when i realized Font changer has a density changing setting in it and it works flawless, now i can take advantage of this qHD screen. So happy!
TimidRat said:
Sorry for bumping if someone's mentioned this before, but after trying to a find an app to easily change the density for months and continuously failing, i was quite excited when i realized Font changer has a density changing setting in it and it works flawless, now i can take advantage of this qHD screen. So happy!
Click to expand...
Click to collapse
Simplest way would be to use root explorer and edit the value in system/build.prop
Or
Use adb pull /system/build.prop
Edit the value with NotePad++ and
adb push build.prop /system
adb shell
chmod 644 /system/buildp.prop
Sent from my HTC EVO 3D X515m using xda premium
j4n87 said:
Simplest way would be to use root explorer and edit the value in system/build.prop
Or
Use adb pull /system/build.prop
Edit the value with NotePad++ and
adb push build.prop /system
adb shell
chmod 644 /system/buildp.prop
Sent from my HTC EVO 3D X515m using xda premium
Click to expand...
Click to collapse
I know I just wanted an app to change it quick and easily though cause some games don't play well with the 192 density setting I prefer. I know 192 is tiny on the 3d but I love it, feels like I'm using a tablet.
Actually root toolbox pro works perfectly... but I believe for actual density changes on everything you need n asop rom
Sent from my PG86100 using xda premium
I use 200, definitely a good balance between being smaller and too small. Before viperROM Final is out, I'm going to add density control into viperControl so that you don't even have to use an app
-viperboy- said:
I use 200, definitely a good balance between being smaller and too small. Before viperROM Final is out, I'm going to add density control into viperControl so that you don't even have to use an app
Click to expand...
Click to collapse
Yeah 200 is a sweet spot. And that would be an amazing addition to an awesome rom! I remember Magnus included it in one of the destroyer roms on the og and ever since then 240 is rediculously huge too me, its like a 600×800 Res on a computer haha. I'm still in shock I never noticed font changer had a option to change LCD density, and the fact that it has it, and its free! I don't understand why a font changer would have this option, but I'm definitely not complaining.
j4n87 said:
Simplest way would be to use root explorer and edit the value in system/build.prop
Or
Use adb pull /system/build.prop
Edit the value with NotePad++ and
adb push build.prop /system
adb shell
chmod 644 /system/buildp.prop
Sent from my HTC EVO 3D X515m using xda premium
Click to expand...
Click to collapse
u cant honestly think going with the adb method and using notepad++ is "simpler" then clicking an app on the phone and typing the density u want right there..
but anyway.. yeah, ive been using font changer for a while to change both my fonts and density.. (back in my htc hero days..)
i go with 220.. even tho i like the way 200 looks overall, it makes the market too small and also sets the keypad in the dialer off center..
This is my first post here.
I recently switched from iPhone to Note 2. I was very drawn towards a large screen with lots of real estate. The note 2 out of the box didn't do it for me. However, I read the discussions about the international version and people changing the DPI with ROMs and other methods and figured if they could do it, so could I.
After waiting 5 weeks for my pre-order to arrive, then a week for the developers to provide a root option, I finally have my wish. Here is how I did it.
1. Root
2. Install a custom launcher (I installed nova, which works for me.) Set it as default
3. Install a new keyboard and set it as default
4. Install LCD Resolution from play store. I found nowhere that discussed this option, but I tested on a GS3, GS1, and Droid Charge and it worked better than the other DPI changers.
5. Set PPI to 240 in LCD Resolution. Uncheck Always Set on Boot until you know it will be stable. This caught me in a boot loop on the GS3. The only other res I tried was 160 and it failed.
6. Reboot.
It should work great. There are a few things to note:
1. The camera looks bad. I have not replaced it with a new one yet. - Please post any suggestions.
2. The calculator and dialer dont look amazing but are usable.
3. Email in portrait doesn't use the whole screen. I use it in landscape and it great.
4. Clock does not work, but can be replaced easily. I have not found a new alarm to use yet. - Please post any suggestions.
If you get another DPI to work well, let us know.
Otherwise, this is a great mod if you need more real estate on your new screen without loosing any of the s-pen or other stock functionality.
Thanks to those of you who helped root...
hmm, doesn't seem to work for me. The prompt in the app to reboot doesn't do anything.
Can we see some screen caps?
just do it manually it doesnt cause boot loops. You can change it to any DPI you want.
Use root explorer
navigate to "System/Build props"
Hold down "build props"
choose "open with"
then choose "text editor"
scroll down a few lines look for "ro.sf.lcd_density=320"
Change the 320 to whatever you want, I use 240.
click "save and exit",
reboot your device,
profit.
Why would you want to change it if it makes stuff look bad?
you can also edit the build.prop via rom toolbox really easily and the results are attached. 240dpi is first 320dpi is second.
Your Samsung keyboard will also crash at 240dpi but you can replace it with this one made by bala_gamer http://forum.xda-developers.com/attachment.php?attachmentid=1501015&d=1353535434
blackbass595 said:
Why would you want to change it if it makes stuff look bad?
Click to expand...
Click to collapse
I haven't done it yet but a lower dpi would be great on this phone. It would let you take more advantage of such a large screen real estate.
guthrien said:
I haven't done it yet but a lower dpi would be great on this phone. It would let you take more advantage of such a large screen real estate.
Click to expand...
Click to collapse
maybe but i just dont wont to change something that breaks other things. to each his own though.
blackbass595 said:
maybe but i just dont wont to change something that breaks other things. to each his own though.
Click to expand...
Click to collapse
It doesn't really break anything from what I've noticed, just makes a few things appear a bit differently, but still fully functional. It's worth a shot if you're interested in doing it, and you can always change back if you find it unmanagable. Personally, a per app dpi would be ideal, because you don't always prefer every app to be at 240 dpi. But I really like it, especially with the on screen nav buttons, which even those make some apps SLIGHTLY off, but still plenty usable, and worth the small inconvenience. To each their own though.
Sent from my SCH-I605 using xda premium
sleevasteve said:
It doesn't really break anything from what I've noticed, just makes a few things appear a bit differently, but still fully functional. It's worth a shot if you're interested in doing it, and you can always change back if you find it unmanagable. Personally, a per app dpi would be ideal, because you don't always prefer every app to be at 240 dpi. But I really like it, especially with the on screen nav buttons, which even those make some apps SLIGHTLY off, but still plenty usable, and worth the small inconvenience. To each their own though.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Where did you get the nav keys?
Thanks.
Sent from my SCH-I605 using Tapatalk 2
leyvatron said:
Where did you get the nav keys?
Thanks.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=35037379
Sent from my SCH-I605 using xda premium
Mibuix0r said:
you can also edit the build.prop via rom toolbox really easily and the results are attached. 240dpi is first 320dpi is second.
Your Samsung keyboard will also crash at 240dpi but you can replace it with this one made by bala_gamer http://forum.xda-developers.com/attachment.php?attachmentid=1501015&d=1353535434
Click to expand...
Click to collapse
Is there anyway I can get the steps to you method I tried using the apps but it didn't work and now I got a white line at the top of the screen. Am flashing back to stock root to see if it will remove it. I also tried root explore but would lose the multi window edit option. Now am going for ROM tool box. Any pointers would be great.
dandel0074 said:
Is there anyway I can get the steps to you method I tried using the apps but it didn't work and now I got a white line at the top of the screen. Am flashing back to stock root to see if it will remove it. I also tried root explore but would lose the multi window edit option. Now am going for ROM tool box. Any pointers would be great.
Click to expand...
Click to collapse
The white line is probably the miui battery bar, see if its on in settings> custom settings> battery bar settings. As far as the dpi, just use a root explorer to go into system>Apps>build.prop, then long press build.prop and open in text editor and change the line with "screen/lcd density" and change the value to 240(or whatever you want). Hit menu and save/exit then reboot. You are correct that you lose the edit function in multi windows, but you can always change back to edit your apps, then switch back. The change only takes 10 seconds.
Sent from my SCH-I605 using xda premium
sleevasteve said:
http://forum.xda-developers.com/showthread.php?p=35037379
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Cant get it to work.
What am I doing wrong? Do I have to be 240 dpi?
Root explorer > edit prop > scroll to bottom and add > qemu.hw.mainkeys=0 > and save
Sent from my SCH-I605 using Tapatalk 2
leyvatron said:
Cant get it to work.
What am I doing wrong? Do I have to be 240 dpi?
Root explorer > edit prop > scroll to bottom and add > qemu.hw.mainkeys=0 > and save
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Now reboot. You don't have to be at any certain dpi.
Sent from my SCH-I605 using xda premium
Why you would want to is easy. Ever used a tablet and seen tablet mode on apps? Stock DPI prevents apps from entering tablet mode and that was one feature I was looking very forward to with such a big screen.
leyvatron said:
Cant get it to work.
What am I doing wrong? Do I have to be 240 dpi?
Root explorer > edit prop > scroll to bottom and add > qemu.hw.mainkeys=0 > and save
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I couldn't get that to work either. I think it ma be a touchwiz conflict.
Just experienced my 2nd screen/sleep of death today, and unfortunately I'm thinking it's from the dpi. Going to change and will report back if I discover otherwise. I'll also leave my nav bar on, just to eliminate that variable. Bummer...I really hope we can incorporate a per app dpi on this phone at some point, maybe paranoid android(as long as it's reasonably compatible with the s-pen).
I also noticed my "android system" under battery was going through the roof. It was going over the screen %, but now that I changed the dpi back, it's already back under.
Sent from my SCH-I605 using xda premium
I get a error in root explorer when trying to edit the dpi in the build.prop
It will not let me change the setting to 240...any ideas? yes im rooted, root permissions granted for root explorer...etc.
droidstyle said:
I get a error in root explorer when trying to edit the dpi in the build.prop
It will not let me change the setting to 240...any ideas? yes im rooted, root permissions granted for root explorer...etc.
Click to expand...
Click to collapse
Make sure to use text editor or something similar. I had to long press it and "open with" for it to let me edit anything.
Sent from my SCH-I605 using xda premium
I don't see a dpi setting in build.prop, but it looks like its set to 400 dpi instead of the normal 320. The icons are huge...
Anyone able to fix that?
Solved.
omniphil said:
I don't see a dpi setting in build.prop, but it looks like its set to 400 dpi instead of the normal 320. The icons are huge...
Anyone able to fix that?
Click to expand...
Click to collapse
1)Root
2)Install busybox
3) install terminal and enter commands
> su
> mount -o rw,remount /system
> chattr -R -i /system
4) Delete or rename / system / set_immutable.list [set_immutable.list.old]
5) added/change to build.prop " qemu.sf.lcd_density=320 " and " ro.sf.lcd_density=320 "
Thanks!
With the DPI set to 320 it seems like it ends up breaking alot of other things unfortunately. I guess I'll just stick to 400
Swiftkey Keyboard for example gets all goofy for some reason. Which is odd because it worked fine at 320DPI on 4.2.2. So there must be something else besides just changing the DPI to make things work correctly.
Very strange that they choose 400 DPI...
ashish1607 said:
1)Root
2)Install busybox
3) install terminal and enter commands
> su
> mount -o rw,remount /system
> chattr -R -i /system
4) Delete or rename / system / set_immutable.list [set_immutable.list.old]
5) added/change to build.prop " qemu.sf.lcd_density=320 " and " ro.sf.lcd_density=320 "
Click to expand...
Click to collapse
omniphil said:
Thanks!
With the DPI set to 320 it seems like it ends up breaking alot of other things unfortunately. I guess I'll just stick to 400
Swiftkey Keyboard for example gets all goofy for some reason. Which is odd because it worked fine at 320DPI on 4.2.2. So there must be something else besides just changing the DPI to make things work correctly.
Very strange that they choose 400 DPI...
Click to expand...
Click to collapse
Haven't rooted yet but will as soon as I find some time.
In meantime, have you tried xposed framework? Wonder if that works... Per App module would do wonders I think...
i am using d[i of 240. i like display this fine. Also everything seems to work fine at 240, except icons screwed a bit. i use "hacker's keyboard". its working fine.
i tried dpi of 250, 280 etc. things were broken when i used it.
Sent from my X1 7.0 using XDA Free mobile app
ashish1607 said:
i am using d[i of 240. i like display this fine. Also everything seems to work fine at 240, except icons screwed a bit. i use "hacker's keyboard". its working fine.
i tried dpi of 250, 280 etc. things were broken when i used it.
Sent from my X1 7.0 using XDA Free mobile app
Click to expand...
Click to collapse
I noticed the weird skewed icons too when I tried 320dpi.
Ya know, I hadn't even thought about Xposed Framework, i'm gonna install that and see how that works...
Really wish we had a custom recovery, Normally I'd take a full backup before messing with stuff, just makes me a little nervous...
Xposed Framework didn't seem to work.. I can install it fine and I even did this....
"With a proper build.prop editor:
Find this line: ro.config.hwtheme=1 (or 2, it depends on your device)
Change to: ro.config.hwtheme=0
This will disable Huawei Theme Engine
WITH THIS YOU DON'T NEED TO DISABLE RESOURCE HOOKS"
But it still doesn't activate, i'm guessing because writing to the /System is being blocked by Huawei.
There's also a warning message about using Xposed with Huawei roms as Huawei uses a theme engine too.
So I don't know.. If I had a way to make a snapshot backup i'd go a little deeper. But it seem troublesome...
forgot to mention, i tried xposed also. some modules are working. but app-setting, wanam exposed are not working.
i made system writable by removing immutable-list and those remount rw command.
double tap statusbar to lock is working for example.
Sent from my X1 7.0 using XDA Free mobile app
I have Huawei Mediapad X1, with KitKat 4.4.2, last version B010, and rooted.
I've checked with AnTuTu Benchmark that tablet is 400 dpi, but, ...all seems to run correctly.
Icons are normal, text sizes are normal, and all the apps I use seem to run normal.
What are exactly the problems using 400 dpi instead of standard 320 dpi?
loJaume said:
I have Huawei Mediapad X1, with KitKat 4.4.2, last version B010, and rooted.
I've checked with AnTuTu Benchmark that tablet is 400 dpi, but, ...all seems to run correctly.
Icons are normal, text sizes are normal, and all the apps I use seem to run normal.
What are exactly the problems using 400 dpi instead of standard 320 dpi?
Click to expand...
Click to collapse
Many apps, including Google+ and Now Launcher, will not install or run.
Also, many text and other graphical elements, such as the included keyboards, are humorously large on the screen.
At 320, the device felt like a phablet. At 400, the device feels like a overly large phone.
Sent from my LG-D803 using Tapatalk
realeze said:
Many apps, including Google+ and Now Launcher, will not install or run.
Also, many text and other graphical elements, such as the included keyboards, are humorously large on the screen.
At 320, the device felt like a phablet. At 400, the device feels like a overly large phone.
Sent from my LG-D803 using Tapatalk
Click to expand...
Click to collapse
Yes, it's what I suppose,
anyway, I've installed the X1 as a carputer, and I am running Chrome, Poweramp, MusicXMatch, Sygic, Google Apps, etc, etc, etc.without problems.
The included keyboards also have normal size.
It's very strange, because AnTuTu says my tablet is 400 dpi, but all seems normal.
Well, I suppose i'm lucky
loJaume said:
Yes, it's what I suppose,
anyway, I've installed the X1 as a carputer, and I am running Chrome, Poweramp, MusicXMatch, Sygic, Google Apps, etc, etc, etc.without problems.
The included keyboards also have normal size.
It's very strange, because AnTuTu says my tablet is 400 dpi, but all seems normal.
Well, I suppose i'm lucky
Click to expand...
Click to collapse
Can you share pics and details of your carputer installation? I am thinking of ways to do the same...
realeze said:
Can you share pics and details of your carputer installation? I am thinking of ways to do the same...
Click to expand...
Click to collapse
Yes.
You can find some images in this Thread
You can see the tablet is well integrated with car. I used Huawei Mediapad X1 because I had some size limitations, and this one is the smallest 7" tablet I've found.
I used CarHome Ultra as frontend, and some apps for multimedia (Poweramp, MusicXmatch, Google Play Music), GPS car navigation (Sygic, Google Navigation), OBD2 (DashCommand), etc, etc, etc.
I connected tablet headset output to my car audio AUX input.
The tablet puts automatically on/off when I start engine. I used "Actions" app to automatize WakeUp/Sleep depending on charging state. Tasker app is more powerful, but It was impossible to install.
It's very important to charge the tablet with a 5V-4A regulator like this one in DX. It's important to charge battery quickly!
Also, I used an app -don't remember the name- to put tablet in lowest consumption to minimize battery drain when is sleeping.
Well, if you do the same, show us the project, ...and luck!
Back to 4.2.2
No kidding, that 400 dpi in 4.4.2 is WAY to large. Thought I could live with it, but can't. It's perfect in 4.2.2, so back I went!
Hi all,
I have found a way to change the dpi without root, just using adb and cmd and it worked like a charm...well, almost. There are a couple of UI glitches that appear when you reduce (or increase for that matter) the dpi.
Firstly, the icons on the home screen mess up, but that's not SUCH an issue as you can install another launcher or in my case, find an icon pack that doesn't show the mess up quite as much (my preferable choice because you see the icons set in different areas of the UI, such as the notifications shade and recents menu, settings, etc.)
Secondly, and the most annoying, is the crop function messes up in the weirdest way. Whether it be when changing wallpaper or trying to crop a picture in CamScanner, the image you choose appears zoomed in and there is no way to zoom out or even move the image around, only zoom in further.
Now, my question is, has anyone managed to find a suitable dpi that MIUI does not have a problem with, or are there some standard dpi's MIUI uses apart from 480? Or has anyone found a way around any of these issues (or any other issues they may have encountered when changing the dpi)? Last but not least, is there a custom version of MIUI out there, or a rom that has it's visuals (and camera app) but custom tailored to suit various dpi's and other modifications?
I really cannot live with the stock dpi of 480, it's like using a phone made for old people, waaaay too large EVERYTHING on a large screen, I want to see more on a large screen. But I also am not yet prepared to go off MIUI as I really like their UI, visually, and I know any other rom will lose a lot of camera quality amoungst some other things like battery life, etc.
Thanks guys in advance for any advice.
Use 400 DPI ..There is no issue ..I am using it from 1Month
Sent from my Redmi Note 3 using XDA-Developers mobile app
Anands3 said:
Use 400 DPI ..There is no issue ..I am using it from 1Month
Sent from my Redmi Note 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Which method?
Sent from my kenzo using XDA-Developers mobile app
Textdroider App from play store
Sent from my Redmi Note 3 using XDA-Developers mobile app
If the original one is 386 I think 400 is kinda useless... Or did you mean 300?
Original is 403dpi if I'm not mistaken. I set mine to 375 and it's absolutely perfect..
Default density is 480.
Code:
[email protected]:/ $ wm density
Physical density: 480
Zak108 said:
Hi all,
I have found a way to change the dpi without root, just using adb and cmd and it worked like a charm...well, almost. There are a couple of UI glitches that appear when you reduce (or increase for that matter) the dpi.
Firstly, the icons on the home screen mess up, but that's not SUCH an issue as you can install another launcher or in my case, find an icon pack that doesn't show the mess up quite as much (my preferable choice because you see the icons set in different areas of the UI, such as the notifications shade and recents menu, settings, etc.)
Secondly, and the most annoying, is the crop function messes up in the weirdest way. Whether it be when changing wallpaper or trying to crop a picture in CamScanner, the image you choose appears zoomed in and there is no way to zoom out or even move the image around, only zoom in further.
Now, my question is, has anyone managed to find a suitable dpi that MIUI does not have a problem with, or are there some standard dpi's MIUI uses apart from 480? Or has anyone found a way around any of these issues (or any other issues they may have encountered when changing the dpi)? Last but not least, is there a custom version of MIUI out there, or a rom that has it's visuals (and camera app) but custom tailored to suit various dpi's and other modifications?
I really cannot live with the stock dpi of 480, it's like using a phone made for old people, waaaay too large EVERYTHING on a large screen, I want to see more on a large screen. But I also am not yet prepared to go off MIUI as I really like their UI, visually, and I know any other rom will lose a lot of camera quality amoungst some other things like battery life, etc.
Thanks guys in advance for any advice.
Click to expand...
Click to collapse
Is it possible to change the density using terminal emulator directly on phone? Or do I need to have PC?
GarbeVR said:
If the original one is 386 I think 400 is kinda useless... Or did you mean 300?
Click to expand...
Click to collapse
No, the original is 480, which is too large...where did you get the number 386 from? perhaps it is another one of their phone's stock DPI, which means MIUI might not warp on this DPI value? Will check it out, but any information you have, please let me know
h4gH said:
Is it possible to change the density using terminal emulator directly on phone? Or do I need to have PC?
Click to expand...
Click to collapse
Not sure about that, I only tried it from the pc, sorry.
Zak108 said:
Not sure about that, I only tried it from the pc, sorry.
Click to expand...
Click to collapse
OK will try at home then.
Just to be sure - phone has to be in FASTBOOT mode to accept ADB commands from PC right?
used some of the suggested DPI's but...
so, thanks guys, used some of the suggested DPI values, 386 and 375, and mostly everything works fine....except still some small issues with the icons and the cropping. try and set a wallpaper for a whatsapp group for example, photo shows as zoomed in and cannot zoom out to choose a crop of the WHOLE image like I used to....have attached some screenshots of what happens to my icons....is this possibly because I am not rooted that the DPI value is not getting set in to the system correctly? Is anyone who is rooted facing the same issues or not?
might convince me to root, this is the first device i have managed to be happy without rooting lol
h4gH said:
OK will try at home then.
Just to be sure - phone has to be in FASTBOOT mode to accept ADB commands from PC right?
Click to expand...
Click to collapse
No, no need....as long as you have ADB drivers installed and you are launching the CMD from within the ADB folder, it will work. Oh and of course USB debugging enabled and the first time it tried to access the phone for ADB details, you will need to allow it to by hitting remember and ok on the phone
h4gH said:
Is it possible to change the density using terminal emulator directly on phone? Or do I need to have PC?
Click to expand...
Click to collapse
Yes. I do bellow commands with Terminal Emulador on Android. My Device is Kenzo with MIUI 8:
su
wm density 400
The value you change to your preferred
Enviado de meu Redmi Note 3 usando Tapatalk
Zak108 said:
so, thanks guys, used some of the suggested DPI values, 386 and 375, and mostly everything works fine....except still some small issues with the icons and the cropping. try and set a wallpaper for a whatsapp group for example, photo shows as zoomed in and cannot zoom out to choose a crop of the WHOLE image like I used to....have attached some screenshots of what happens to my icons....is this possibly because I am not rooted that the DPI value is not getting set in to the system correctly? Is anyone who is rooted facing the same issues or not?
might convince me to root, this is the first device i have managed to be happy without rooting lol
Click to expand...
Click to collapse
Which theme is this?
BlueJeans said:
Which theme is this?
Click to expand...
Click to collapse
Roger Rabbit...I think at the time of the screenshots I was using a different theme for the status bar, but can't remember as I am now using Eureka 8 Pro. Roger Rabbit is the base theme though, quite like the grey simplicity.
GarbeVR said:
If the original one is 386 I think 400 is kinda useless... Or did you mean 300?
Click to expand...
Click to collapse
The original isn't near 386. I went down to 380 and everything it far smaller than a 6 dpi difference. I'd say stock is closer to 430 - 450
Yes man, you was right the original DPI is 440, the app textdroiderDPI was showing me an incorrect value of 386 (maybe a little bug...).
Setting it on 440 with LeDpiChanger gave me a full stock MIUI size
Stock is 480DPI, changers give bad result...just root and change build.prop ro.sf.lcd_density=
Denis:) said:
Stock is 480DPI, changers give bad result...just root and change build.prop ro.sf.lcd_density=
Click to expand...
Click to collapse
Thank you sir, this works for me on MIUI 8.1.1.0 global stable, change my screen density to 420. Icons are perfect.