Coming from N5, I've played around a lot with the DPI settings, to find the perfect spot (361).
Can you also change the DPI settings on the Z2? N5 has it via editing the build.prop but don't know how Sony does this. I'm yet to receive the phone (on Tuesday) but wanna know in advance.
You can simply edit the build.props to change the dpi
Something to know about xperias is they are extremly close to AOSP with the way the firmware works
Its how xperia FWs are, they are very light
Sent from my D6503 using XDA Premium 4 mobile app
I used DPI Changer app from the play store to change mine, also allows you to backup & restore build.prop file as well
It can be a pain to find the correct DPI that doesn't cause issues with some apps, I originally changed it to 400 for a couple of weeks but that was still a bit too big, 320 was too small, 360 was fine but Tv Show Favs app layout got a bit missed up (the main screen was instead a bar on the left of the screen) Ended up settling on 370.
Oh, it's pretty much the same? Good news then!
On my N5, I use 361 due to issues that 360 causes with some apps, and hoping to do the same on soon-to-be-mine Z2, since it was the perfect spot. But if that won't work, and 370 works (as per above post), that's great! Cheers guys.
BanziBaby said:
I used DPI Changer
Click to expand...
Click to collapse
Thanks man, this works wonders!
BanziBaby said:
I used DPI Changer app from the play store to change mine, also allows you to backup & restore build.prop file as well
It can be a pain to find the correct DPI that doesn't cause issues with some apps, I originally changed it to 400 for a couple of weeks but that was still a bit too big, 320 was too small, 360 was fine but Tv Show Favs app layout got a bit missed up (the main screen was instead a bar on the left of the screen) Ended up settling on 370.
Click to expand...
Click to collapse
I'm trying to figure out why DPI Changer doesn't work for me. I also tried Texdroider, which I previously used on an LG G2 with success. Both apps appear to go through the motions, but when I apply the changes and reboot, nothing is changed.
I'm running a D6503 rooted .402, locked boot loader and I installed SuperSU from the Play Store. Running Root Checker confirms I am rooted.
I'm hoping to be able to set the DPI so it can match the look and feel of the Z Ultra
Thanks in advance for any help!
Hadn't thought of changing DPI in quite a while, actually since my Xperia Z. I'm too going to play around with DPI till I find something a bit smaller but then again not too small. I've always thought that the interface had gotten unnecessarily big after the Xperia T.
Edit: Anyone happen to notice what the original DPI value was on the Z2? I changed mine a little too quick..
If anyone likes the ZU the exact DPI is 320
For Z2 Tablet it is 140
And for default it is 480
Sent from my D6503 using XDA Premium 4 mobile app
@orbitalcomp I did have issues with SuperSU granting root to dpi changer, had to apply the new dpi twice & even then sometimes it wouldn't apply on reboot, also had issues with AdAway failing to copy & apply the new hosts file, tried using the full unroot option in SuperSU but it just stuck saying uninstalling please wait. Had to use Solid Explorer to delete the SuperSU apk file & the binary then downloaded the recovery version of clockworkmod superuser & flash that, no issues with dpi changer or AdAway or any other root apps.
Maybe it just me but I have always found SuperSU to be a bit flaky & buggy at times both on the Z2 & my old Galaxy S & Galaxy S3, never had any issues with clockworkmod superuser
I have setted DPI to 320 by editing build.prop.
Then you can apply some different DPI settings App per App using AppSettings Xposed, working great!
BanziBaby said:
@orbitalcomp I did have issues with SuperSU granting root to dpi changer, had to apply the new dpi twice & even then sometimes it wouldn't apply on reboot, also had issues with AdAway failing to copy & apply the new hosts file, tried using the full unroot option in SuperSU but it just stuck saying uninstalling please wait. Had to use Solid Explorer to delete the SuperSU apk file & the binary then downloaded the recovery version of clockworkmod superuser & flash that, no issues with dpi changer or AdAway or any other root apps.
Maybe it just me but I have always found SuperSU to be a bit flaky & buggy at times both on the Z2 & my old Galaxy S & Galaxy S3, never had any issues with clockworkmod superuser
Click to expand...
Click to collapse
Thanks for the reply, BanziBaby. Not sure if you had the same issue originally, but when installing SuperSU from the Play Store it would not update the binaries on first run. After a reboot, SuperSU would open and it was able to grant permissions to the different apps, but I guess it wasn't a full grant.
Is there anyway to install a working version of SuperSU without going through recovery? I'm assuming I have to unlock my boot loader to install a recovery, right?
sensei_sai said:
I have setted DPI to 320 by editing build.prop.
Then you can apply some different DPI settings App per App using AppSettings Xposed, working great!
Click to expand...
Click to collapse
Do the stock apps all handle the 320 dpi just like the Z Ultra, meaning there are more icons allowed on the home screen, dock, and app drawer?
I remember when I had my ZU, I was even able to install tablet apps straight from the Play Store since it apparently registered as a tablet/phone hybrid. That would be nice on the Z2 as well.
orbitalcomp said:
Thanks for the reply, BanziBaby. Not sure if you had the same issue originally, but when installing SuperSU from the Play Store it would not update the binaries on first run. After a reboot, SuperSU would open and it was able to grant permissions to the different apps, but I guess it wasn't a full grant.
Is there anyway to install a working version of SuperSU without going through recovery? I'm assuming I have to unlock my boot loader to install a recovery, right?
Do the stock apps all handle the 320 dpi just like the Z Ultra, meaning there are more icons allowed on the home screen, dock, and app drawer?
I remember when I had my ZU, I was even able to install tablet apps straight from the Play Store since it apparently registered as a tablet/phone hybrid. That would be nice on the Z2 as well.
Click to expand...
Click to collapse
When changing DPI to 320 all apps load into phablet mode (aka ZU size) and some which dont support phablet load into tablet size
In other words... No problem
Sent from my D6503 using XDA Premium 4 mobile app
I have an issue with the Xperia launcher when I change DPI..
The icons on the launcher just get smaller and smaller and unlike google now launcher it doesn't adapt to the changed DPI.
Anyone else have this? I really don't want to switch away from Sony's launcher and smaller dpi is pretty awesome on a larger screen.
lyubor said:
I have an issue with the Xperia launcher when I change DPI..
The icons on the launcher just get smaller and smaller and unlike google now launcher it doesn't adapt to the changed DPI.
Anyone else have this? I really don't want to switch away from Sony's launcher and smaller dpi is pretty awesome on a larger screen.
Click to expand...
Click to collapse
with which DPI? If I remenber well I had the same until I switched to 320 DPI, which is just perfect.
With everything I randomly tried around 400. Rebooted twice after applying 320 and it actually worked!
Ended up using the DPI Changer app, since editing the build.prop directly didn't seem to work after multiple reboots, but 361 is doing the job so far.
Success!
I was finally able to get my root and SuperSU binaries to take after some trial and error from reading the Easy Root Tool thread. Took a combination of installing the SuperSU.apk and rooting multiple times to do it.
Now I'm running 320dpi after changing the setting in DPI Changer...it looks fantastic! I always thought the Z Ultra had the best looking dpi for a smartphone, now it looks perfect on the Z2.
Couple things I noticed...the launcher now rotates to landscape, plus I'm not able to install the tablet version of Slingplayer like I could on the ZU, says it's incompatible in the Play Store. No big deal really, since the phone version works fine, I just like having the full remote of the tablet version.
Thanks to everyone for their input!
orbitalcomp said:
Success!
I was finally able to get my root and SuperSU binaries to take after some trial and error from reading the Easy Root Tool thread. Took a combination of installing the SuperSU.apk and rooting multiple times to do it.
Now I'm running 320dpi after changing the setting in DPI Changer...it looks fantastic! I always thought the Z Ultra had the best looking dpi for a smartphone, now it looks perfect on the Z2.
Couple things I noticed...the launcher now rotates to landscape, plus I'm not able to install the tablet version of Slingplayer like I could on the ZU, says it's incompatible in the Play Store. No big deal really, since the phone version works fine, I just like having the full remote of the tablet version.
Thanks to everyone for their input!
Click to expand...
Click to collapse
Can confirm that also on Z3 is 320DPI for Home launcher just amazing
Xperia Z2 dpi change
I have tried to use all application in playstore as well as build.prop editing in system but still nothing happens I'm running in marshmallow 6.0.1 with 23.5.A.1.291 build hope you could help me guys thanks
pulizpunk said:
I have tried to use all application in playstore as well as build.prop editing in system but still nothing happens I'm running in marshmallow 6.0.1 with 23.5.A.1.291 build hope you could help me guys thanks
Click to expand...
Click to collapse
You need to reboot after editing.
Sent from my Sony D6503 using XDA Labs
Related
This is probably more of a general Android question (as opposed to device-specific) and one that I've never been able to fully fix on any of my Android devices. When I change the dpi (currently on my RAZR HD XT926) it breaks several Play Store apps. Sometimes I can't download new apps because it will say "your device is not compatible..." and I can't even get updates to current apps I have installed. As soon as I change back to the default dpi and reboot, everything works perfectly. Is there a way around this when changing the dpi on an Android device?
Thanks,
caseym
Thanks
do u want to change the dpi of the app or your phone
nag xperia said:
do u want to change the dpi of the app or your phone
Click to expand...
Click to collapse
Phone. I know how to change the DPI...I just want to know if there is a way to do it and NOT break the market.
Create a file /data/local.prop with permissions set to 644. Put this line in it:
qemu.sf.lcd_density=nnn
where nnn is the dpi. Reboot.
See http://forum.xda-developers.com/showthread.php?p=29413138
This will change your display, but doesn't affect Play. It works on both my Nexus 7 and HTC Desire S.
Sent from my HTC Desire S
[update-02/21/2013]
Although changing the "garmin pilot" dpi settings did nothing but make things smaller in the app, changing the "Android System" dpi setting to 240 or lower will force the program to run as a tablet instead of the crippled phone version. Not sure if this is the same for other apps as well but I figured I would put this out there for others with the same issue.
[update-02/21/2013]
I rooted my note 2 hoping to use garmin pilot in tablet mode. I installed Jelly 'Beans' - Build 9 [02/12/13] and also Xposed framework so I can change DPI settings. However this program seems unaffected by a simple dpi change. If there is any way to hack this one program to force it to install as a tablet I would be grateful.
djpurpose said:
I rooted my note 2 hoping to use garmin pilot in tablet mode. I installed Jelly 'Beans' - Build 9 [02/12/13] and also Xposed framework so I can change DPI settings. However this program seems unaffected by a simple dpi change. If there is any way to hack this one program to force it to install as a tablet I would be grateful.
Click to expand...
Click to collapse
I haven't ever had the framework not show some difference, usually it just screws up the layout if it isn't going to work.
Do you have the app settings module active in the xposed installer app?
Ok so I was running per app dpi settings and it works perfectly for non system apps. Although, when i try to set tablet mode for settings, it will Force Close. Is there any way around this?
AldenIsRad said:
Ok so I was running per app dpi settings and it works perfectly for non system apps. Although, when i try to set tablet mode for settings, it will Force Close. Is there any way around this?
Click to expand...
Click to collapse
Can anyone help please
AldenIsRad said:
Can anyone help please
Click to expand...
Click to collapse
Honestly I never could get certain system apps to set correct dpi using touchwiz. If i remember correctly the phone dpi was the big issue for me. I didn't play around with it 2 much. It was one of the reasons I switched to aosp so i'm able to set the dpi to 240 and everything works correctly.
I'm pretty sure when you set it to tablet apk it doesn't really do anything unless there is a seperate apk for tablet settings. I remember this from a few files I extracted from Moon ROM.
Some apps can't run in lower DPIs and will fc. It also sounds like if you have the tablet option, you may have an outdated version of xposed app dpi settings. The newer one doesn't have a tab for tablet vs non tablet.
AldenIsRad said:
Ok so I was running per app dpi settings and it works perfectly for non system apps. Although, when i try to set tablet mode for settings, it will Force Close. Is there any way around this?
Click to expand...
Click to collapse
Maybe im not understanding. When you say tablet mode is that simply a dpi and res that makes setting look like on a tablet or are you running a module that does this and then you have to manually adjust the setting dpi to get it to work?
At one point when I was using the tablet mod (not the flashable one) my setting fc'd. Im not sure which might work for your case, but I might try setting the dpi you think is supposed to work then reboot. Maybe it needs a reboot after each change. (or again im not sure your situation- make a save copy of system settings app, reinstall it and make sure you change it to have the same permissions as all other sysyem apps. This would be if say you had a mod on for tablet mode and now settings was fc)
Change Pixel Density for Galaxy Note 3 and Recommended DPI Settings for System Apps.
Requires Root!
Works on any Rom!
With the Note 3 Packing a 1920x1080 resolution, the first thing I did when I got the phone was work on taking advantage of the real estate the screen has to offer. Many of the Pixel density settings from the Note 2 work on the Note 3, but keep in mind the formula changed with the new screen size and resolution change. I'm just going to call it "Preferred DPI" as most will agree, its a comfortable viewing option.
The easiest way I have found is to change the overall layout from 480 to 320, then going in and tweaking some individual apps.
Overall most of the apps will function as normal, however some system apps will not look right, especially the Dialer and Camera/Gallery views.
Note 2:
Factory DPI: 320
Preferred DPI: 240
Note 3
Factory DPI: 480
Preferred DPI: 320
To change all apps and programs to be viewed in 320 mode is to modify the build.prop settings.
There are multiple ways to do this, but the easiest I have found is to download Rom Toolbox. The Lite version will allow you to easily edit the app. Support your devs, buy pro or donate and give credit to these app & rom creators.
Rom Toolbox Lite Rom Toolbox Pro
Step 1: Changing phone pixel density from 480 to 320
Open Rom Toolbox
Go to the Performance Tab
Select the build.prop Editor
Click the Magnifying Glass to search
Type in "Density"
Click on the ro.sf.lcd_density
Change the Property Value from 480 to 320
Click YES on reboot prompt
Step 2: Download and Install Xposed Framework and App Settings Module
Without rewriting guides that are already available, you can read the general guides here on how to install Xposed Framework.
Guide by Max from High on Android
Download Xposed Framework by Xda Developer rovo89
Download Xposed App Settings Module by rovo89 & Tunstwenty
You will need to install Xposed Framework, and the Xposed App Settings Module by clicking on the above threads. The threads are maintained and updated regularly. Xposed has the ability to update itself, and also provides updates to the modules, which is a great feature.
Once these are installed you can then begin to change apps back to 480 DPI if they don't look right.
Step 3:Recommended Apps to Revert to Stock Density
You can change any app you wish, but the ones that I recommend to keep at stock DPI mainly due to cropping issues are the dialer, contacts, camera, and gallery.
I am currently running Jellybombed Rom, so you may see some extra apps in screenshots, as well as blue text.
I also ran this on the stock rooted Samsung Rom, and the Rooted Deodexed rom before going to Jellybomb.
These are my personal preferences, and im sure I have more than I need selected, but I wanted to make sure all elements worked.
Camera for example has many sub apps such as editing and trimming.
Contacts has 4 tabs for Phone, Groups, Favorites, Contacts
Phone has 4 tabs for Keypad, Logs, Favorites, Contacts.
Bolded are the most essential, the non bolded are personal preference. Feel free to add your own.
com.arcsoft.picmovie
com.arcsoft.picturesbest.app
com.android.app.popupcalculator Calculator
com.sec.android.app.camera Camera
com.sec.factory.camera Camera
com.sec.android.app.collage Samsung Gallery
com.sec.phone - Phone
com.android.contacts - Contacts
com.android.providers.telephony
com.arcsoft.picaction.app
com.arcsoft.demo.piclear
com.sec.android.gallery3d Alternate Gallery
com.google.android.gallery3d Alternate Gallery
com.lidroid.sgs.secretcode
com.android.mms - Texting
com.android.phone - Phone Dialer
com.sec.sprextension.phoneinfo
com.sec.android.mimage.photoretouching
com.sec.android.filter
com.samsung.everglades.video - Samsung Video App
com.sec.yosemite.phone
com.lifevibes.trimapp
com.sec.android.app.storycam
com.sec.android.app.videoplayer - Samsung Default Video Player
com.android.vpndialogs
ma.wanam.xposed
com.google.android.youtube
I have not had any issues with the Android Market, and DPI settings yet, however there is a module called Play Store Fixes you can run within Xposed.
The launcher I use is ADW Launcher
The current Rom used in the screenshots is Jellybomb Domination
Support Josh Beach & kevinrocksman
This is so necessary for the note 3. Thanks for the post!!
Awesome job.
Any clue what app the pen input app is? The one you activate by clicking the pen square over inputs?
It looks like it follows the app's dpi, but wondering if that can be pegged at 480 for every app?
320 feels a tinge too small. Any idea what other settings could be used easily that aren't so small?
I just went in and changed a bunch to make it better. Thanks for the suggestion.
Do you know which is the lockscreen?
Any idea what program the sview case window is under?
Sent from my SM-N900P using xda app-developers app
Jbroad572 said:
Any idea what program the sview case window is under?
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
It's not a particular program, from what I've read you would have to leave the system at 480 and individually change apps to 320 to keep the S View Window working properly :\
datajosh said:
It's not a particular program, from what I've read you would have to leave the system at 480 and individually change apps to 320 to keep the S View Window working properly :\
Click to expand...
Click to collapse
Im going back to stock deodexed this weekend to test out some things.
I had some issues with editing pictures ( mainly getting the redeye tool to work with pinch to zoom) so Im going to go back to "as close to stock" as possible to rule out any theme/app settings from Jellybombed.
Ill try to play with the factory apps a bit to get a better list.
Im one of those .. "as soon as i get a phone I root, change dpi, then freeze or remove every system app with "samsung" or "sprint" on it.. and this time around its knox to add to the list.
Then again thats what I done with hundreds of computers for the last 15 or so years, so the habit kind of carries on =)
Not a fan of bloatware =)
rawdikrik said:
320 feels a tinge too small. Any idea what other settings could be used easily that aren't so small?
Click to expand...
Click to collapse
I would love to see more screenshots. I had rooted and went to 240dpi on my original note, and love the way that looks. Still on the fence with rooting my note 3. Haven't read enough about knox, even though I know there are ways to root without tripping knox now. But I m itching to change my dpi
Thanks for the guide. I put mine at 370 dpi, which looks good for me, without being too tiny
Sent from my SM-N900P using Tapatalk
anyone tried changing DPI to "Android System" and "System UI"? I had this changed on my Note 2 (to 240) so that the settings and overall UI was smaller. I tried changing it on the Note 3 to different DPI to test out but it seem sto leave a small border right under the status bar. I tried 320, 350, 370, 400 .. I'm using Nova Launcher btw. (JellyBombed ROM)
onebelo said:
anyone tried changing DPI to "Android System" and "System UI"? I had this changed on my Note 2 (to 240) so that the settings and overall UI was smaller. I tried changing it on the Note 3 to different DPI to test out but it seem sto leave a small border right under the status bar. I tried 320, 350, 370, 400 .. I'm using Nova Launcher btw. (JellyBombed ROM)
Click to expand...
Click to collapse
Hmm surprised since your running Nova. . I thought only stock launcher did that. .
Speaking of which. . Anyone thinking about redoing the stock launcher to handle the better dpi?
Sent from my SM-N900P using Xparent Purple Tapatalk 2
cherylbaker said:
Hmm surprised since your running Nova. . I thought only stock launcher did that. .
Speaking of which. . Anyone thinking about redoing the stock launcher to handle the better dpi?
Sent from my SM-N900P using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
yea specially since it looked fine on the note2. Perhaps it's the higher res of the note3?
Does the lockscreen have a separate package? Or is it part of a larger package?
Im trying to change the phone dialer back to stock, but despite the changes it stays the same at 370. What am I doing wrong?
badnews640 said:
Im trying to change the phone dialer back to stock, but despite the changes it stays the same at 370. What am I doing wrong?
Click to expand...
Click to collapse
Try checking all 3 of these settings to 480
com.android.providers.telephony
com.sec.phone
com.android.phone
You can set them manually to 480 (stock)
If you set your overall DPI to something like 370 you need to make those apps bigger individually to 480
cherylbaker said:
Hmm surprised since your running Nova. . I thought only stock launcher did that. .
Speaking of which. . Anyone thinking about redoing the stock launcher to handle the better dpi?
Sent from my SM-N900P using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
I use a scaleable launcher ( ADW EX) for that reason.
In the past when I tried to modify the stock launcher or system UI, it would cause all kinds of force closes..
The primary reasons i believe is due to how Touchwiz integrates its widgets- like clock for example
Changing just systemUI or Launcher but not changing all the other components manually that are linked to it can trigger "Unfortunately System UI Has stopped Working" errors.
The keyboard is another one thats tied in, as well as the lockscreen.
I haven't gotten around to trying to do all of that, or learning how to yet.. which is why i made the guide with the already available apps.
By changing the overall system UI and using a different launcher, you can have the smaller slim status bar, without having everything else break, since all of the DPIs match. Then finding different processes to tweak with "App Settings" allows you to experiment safely without risking breaking everything.
One super annoying issue i had back when I did DPI tweaking on my Note 2 was if you didnt flash a replacement keyboard in recovery, you would have to setup android by continously tapping the error message all the way through phone setup until you could get to the settings screen to change the samsung keyboard to a different one. Samsung's keyboard dosen't like dpi changes on the note 2. But so far no issues personally with the note 3.
chaosrecords said:
Try checking all 3 of these settings to 480
com.android.providers.telephony
com.sec.phone
com.android.phone
You can set them manually to 480 (stock)
If you set your overall DPI to something like 370 you need to make those apps bigger individually to 480
Click to expand...
Click to collapse
Along with a hunch, I found another thread that stated to change contacts and contact storage as well as dialer storage. That fixed it.
http://forum.xda-developers.com/showthread.php?t=2440365
Quick question can u provide more detailed instructions to reverting those apps u listed back to stock dpi...I try to do it through xposed app settings but the corrections aren't taking
Sent from my SM-N900P using Tapatalk
---------- Post added at 08:14 PM ---------- Previous post was at 07:36 PM ----------
lunchboxVA said:
Quick question can u provide more detailed instructions to reverting those apps u listed back to stock dpi...I try to do it through xposed app settings but the corrections aren't taking
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Nvm phone dpi and contacts dpi both have to be changed at the same time
Sent from my SM-N900P using Tapatalk
Does anybody else have an issue when they change there dpi where whatsapp wallpaper changes to a standard white background?
Any way around it?
its annoying and i have been researching for days and cant seem to find anything to fix it.
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!