I've always used AOSP roms and now I'm back on TW roms (CleanRom 6 currently).
I used a DPI changer app that modifies /system/build.prop and everything seems fine. However, there are some apps that look odd with DPI changes such as the Phone and the Camera. I've attempted to use the Xposed framework and settings to change the DPI of these apps back to 320, but it doesn't seem to do anything.
Am I doing something wrong?
EDIT: I figured out what I was doing. I didn't have the Xposed Settings enabled in the installer. The only thing I haven't fixed is the size of the Phone's Dialer. Everything else works. The Dialer looks like this.
Related
Hi All,
First off, my N5 is stock rooted, running Xposed Framework with Gravity Box, Xuimod and Unicon modules. I can't pinpoint the exact moment this started happening, but I'm pretty sure it was before I installed Xposed Framework. Anyways, check out the attached pics. I post this question here because I don't have this issue on my N7 2013, so I'm assuming (hoping?) that it's just an issue with the current Maps and the N5. It looks like the blue from the oceans appears like big jagged blobs over land. When I zoom in, it gets progressively better, but it's just kind of annoying when you're trying to look at a big area, and most of it's covered by the blue blobs. I've tried clearing cache and data for the Maps app, as well as reverting back to the factory version that comes on 4.4.2 (v7.4.0?). None of these helped. Is anybody else seeing these issues?
Sent from my Nexus 5 using xda app-developers app
I get this same problem. Even on areas which I have saved for use offline!
are you using stock DPI, i had the same problem i was using 439 when i changed back to 480 problem fixed it self
I have the exact same issue, everything was fine a week ago, now its all glitched up. Older versions of Maps dont improve anything. Im also rooted and on 439 dpi with xposed etc.
Hah. Same story here 439 DPI.
I used Xposed module App Settings to change DPI to 480 in Google maps. Fixed.
EDIT: also, in case anyone is interested, I reverted LCD Density to 480, turned off the notification bar tweaks in Gravitybox, cleared data in Google Play Store then rebooted a couple of times. I got updates for Candy Crush and Instagram and was able to finally install Amazon UK app. All three seem to be incompatible with LCD_density 439
Wow! Thanks to everyone for replying! I feel kinda dumb right now. I, too, am using a DPI of 439. What's weird is I've been using 439 since I've had my Nexus, and have used Maps before and it was perfectly fine. Then, out of the blue, this started happening. After posting, I suspected the DPI as well, but when I changed it back to 480, it was still happening. I probably did something wrong last night, because when I reverted back to 480 this morning, it fixed the issue. I guess it's time to finally install App Settings in Xposed like outofthisworld to make sure it doesn't happen again. Thanks again to everyone. :good:
I've been stuck two days now trying to change the default launcher on my MIUI ROM. It sounds like a simple task, but for some reason, it isn't. The problem is when I switch to another launcher, pressing home always returns to the MIUI default launcher, no matter what I do.
Some of what I have already tried:
1) I've allowed MIUI to give full root permissions to the launchers. But I cannot clear defaults or manage permissions for MIUI's launcher in settings, as it is greyed out.
2) Tried setting the launchers to set themselves as default (and keep in memory), within their own settings wherever possible.
3) I've tried several apps promising to change defaults to allow for alternative home launchers. None worked.
4) Tried changing BUTTONS (in Android settings) to have the HOME button do nothing or open recent apps. No matter what, it always quits the 3rd party launcher and returns to home of MIUI launcher.
5) I tried freezing MIUI's launcher and running Apex. This finally worked to keep Apex as default! Except after I rebooted, it got stuck on boot and I LOST EVERYTHING.
5) I upgraded MIUI unofficial ROM to 4.2.2, then 4.9.19. No difference.
6) If there is an option to "set default launcher" in a given app, and I try to set it to that launcher, it will only allow the MIUI system launcher as an option, and automatically return me to the MIUI launcher!
As far as I can tell, the problem does not appear to be related to: the phone, the ROM, or the launcher app. Why, because I had ADW working fine for years over a slightly previous version of this MIUI ROM (v4.1.2). I can't remember when things changed, but probably some time after trying Apex. But now, setting the launcher to ADW again changes nothing, the system still returns to MIUI home.
ROM: MIUI v5, (Blackwing182) version: 4.9.19
Android: JB 4.2.2
Phone: Samsung Galaxy S3
Cyanoid said:
I've been stuck two days now trying to change the default launcher on my MIUI ROM. It sounds like a simple task, but for some reason, it isn't. The problem is when I switch to another launcher, pressing home always returns to the MIUI default launcher, no matter what I do.
Some of what I have already tried:
1) I've allowed MIUI to give full root permissions to the launchers. But I cannot clear defaults or manage permissions for MIUI's launcher in settings, as it is greyed out.
2) Tried setting the launchers to set themselves as default (and keep in memory), within their own settings wherever possible.
3) I've tried several apps promising to change defaults to allow for alternative home launchers. None worked.
4) Tried changing BUTTONS (in Android settings) to have the HOME button do nothing or open recent apps. No matter what, it always quits the 3rd party launcher and returns to home of MIUI launcher.
5) I tried freezing MIUI's launcher and running Apex. This finally worked to keep Apex as default! Except after I rebooted, it got stuck on boot and I LOST EVERYTHING.
5) I upgraded MIUI unofficial ROM to 4.2.2, then 4.9.19. No difference.
6) If there is an option to "set default launcher" in a given app, and I try to set it to that launcher, it will only allow the MIUI system launcher as an option, and automatically return me to the MIUI launcher!
As far as I can tell, the problem does not appear to be related to: the phone, the ROM, or the launcher app. Why, because I had ADW working fine for years over a slightly previous version of this MIUI ROM (v4.1.2). I can't remember when things changed, but probably some time after trying Apex. But now, setting the launcher to ADW again changes nothing, the system still returns to MIUI home.
ROM: MIUI v5, (Blackwing182) version: 4.9.19
Android: JB 4.2.2
Phone: Samsung Galaxy S3
Click to expand...
Click to collapse
Have you already attempted setting ADW as the default launcher, immediately going into the directory where the MIUI launcher .apk is, deleting it, and then rebooting? Make a full system backup first, of course.
If you do that, I believe your system will have no choice but to use ADW upon booting.
I do not want to use ADW any longer, but yes, I just did that (after installing a third earlier version of the Blackwing MIUI ROM, v3.9.27). I did not remove the MIUI apk, but froze it (same effect). The phone did not boot into ADW. It just froze on the MIUI logo screen. I also can't set ADW as the default launcher, via settings.
I've literally spent an entire day on this problem, and still can't quite pin it down, because all this *used* to work. I had this same ADW app with one of the aforementioned versions of MIUI, running for ages with over 200 apps on the phone. My best guess is it must be a conflict with one of the installed apps, but then..... why is it acting up *now*?!.
On top of everything, I did a back up of my system&apps with ROM Toolbox AND the MIUI Backup app before messing with the MIUI launcher and having to redo the ROM. Now when I try to restore, *both* of those apps no longer have their backups! (insert angry emoticon)
It's looking like I can no longer use MIUI on my Galaxy S3.... the only ROM I ever liked! :crying:
I noticed that no matter how often I keep reinstalling XPosed and GravityBox I always get the error message that the GravityBox framework is not responding. Is this a Rom based issue or is there some way to fix this?
EDIT:// So I realized it is a Huawei general issue. I installed Xposed 2.5.1 (and changed ro.config.hwtheme to 0 in the build.prop). Now I am able to properly install GravityBox and run it. The problem now is if I for example activate PIE controls or change something from the status bar (and reboot) nothing changes. Even if I activate immersive mode for both sides only the nav bar disappears. Nothing else happens tho.
EDIT2:// So some functions do work. I can use the GravityBox nav bar (although it makes the recent app icon disappear) while some functions like the PIE control simply do not work. Is there some fix?
EDIT3:// Using the GravityBox Navbar the buttons only work on the Homescreen. As soon as you enter an app you have to restart the os in order to quit the app.
fasa123 said:
I noticed that no matter how often I keep reinstalling XPosed and GravityBox I always get the error message that the GravityBox framework is not responding. Is this a Rom based issue or is there some way to fix this?
EDIT:// So I realized it is a Huawei general issue. I installed Xposed 2.5.1 (and changed ro.config.hwtheme to 0 in the build.prop). Now I am able to properly install GravityBox and run it. The problem now is if I for example activate PIE controls or change something from the status bar (and reboot) nothing changes. Even if I activate immersive mode for both sides only the nav bar disappears. Nothing else happens tho.
EDIT2:// So some functions do work. I can use the GravityBox nav bar (although it makes the recent app icon disappear) while some functions like the PIE control simply do not work. Is there some fix?
EDIT3:// Using the GravityBox Navbar the buttons only work on the Homescreen. As soon as you enter an app you have to restart the os in order to quit the app.
Click to expand...
Click to collapse
GravityBox works best with AOSP Roms and Roms that are very close to AOSP I think there is a mention in the app.
Quoting from the official repo that can be found here http://repo.xposed.info/module/com.ceco.kitkat.gravitybox
GravityBox is a module which primary goal is to provide the users of AOSP devices
with a tweak box to turn their vanilla AOSP ROM into custom ROM packed with additional features and tweaks
without need to flash anything. Most of the preferences can be changed on-the-fly without rebooting.
Click to expand...
Click to collapse
It's not Huawei's fault ,if you are trying to install an application and configure it, that is supposed to run in vanilla environment into a heavily customized ROM like EMUI and MIUI if we count XIAOMI too.
Give a try to Xblast Tools , does almost the same than GravityBox, and seems to be more compatible (at least for me).
Does everything I wanted from GB.
And don't post on GB thread, you will not be the welcome (Huawei rom, blablabla ... read the red warnings ... )
For some reason my XPosed installation doesnt work anymore. Tried reinstalling always shows that the Service isn't started. Only disabling rescource apis make it run. This emui stuff is really annoying. I'd love to have an aosp rom
fasa123 said:
For some reason my XPosed installation doesnt work anymore. Tried reinstalling always shows that the Service isn't started. Only disabling rescource apis make it run. This emui stuff is really annoying. I'd love to have an aosp rom
Click to expand...
Click to collapse
Did you tried Xblast Tools ?
Yes I did it worked after installing XPosed 2.5.1. Though most of the stuff is heavily bugged while the rest doesn't even work. I guess we really need a vanilla rom. Honestly even GravityBox worked more with 2.5.1
fasa123 said:
Yes I did it worked after installing XPosed 2.5.1. Though most of the stuff is heavily bugged while the rest doesn't even work. I guess we really need a vanilla rom. Honestly even GravityBox worked more with 2.5.1
Click to expand...
Click to collapse
Weird, most of the things I wanted work (Circle Battery Icon, Custom Navbar, Skip Track, Cursor move with VolKeys).
Hello a little bump , do you advise me to install xposed framework on Honor 6 with EMUI 3.0 ?
So I have been fiddling with this for a long time. Messing around, having to do restores. Ran the cm 12.1 rom build for a while (the one Erwan started as an unofficial port) but the cut off top of the screen really got to me after a week.
So I went back to my stock rooted ROM and tried messing with changing the DPI in the build.prop and changing settings in the Xposed module App Settings.
Below I have a Google drive link to the xml file for the set of apps you need to have enabled and set to stock DPI for a system wide build.prop edited DPI while no longer running into crashes. Basically all I have done is set all the stock/system apps that cause issues when changing dpi system wide, just import the xml, change your dpi to whatever you like (I suggest 580/540 if you want to take real advantage of screen space)
I have included the second screen DPI set to the stock 640 but if the kinda glitched icons really bug you just disable the settings on it or adjust to a different DPI to try and minimize the weirdness. The second screen app will just appear smaller if you disable its settings in App Settings and won't cause any crashes.
App Setting XMl file for import: https://drive.google.com/file/d/0B0IaZuuoHo5MejB2NjdFTmhieXM/view?usp=docslist_api
If anybody finds any issues with the xlm or some app is crashing that I might not use or haven't used since I tried this, post it, and I'll try an keep an updated xlm available that's as stable as possible while giving us back some real screen space everywhere else.
Thanks for the work on creating this. Apologies, but the part I am missing is how do I use this file? I have build prop open and am ready to change my system resolution.
What is the exact procedure to accomplish this?? I imported the xml to App Settings first then changed the DPI in build.prop to 540, I rebooted the phone and it stuck at the LG logo for like 20 minutes, then came the "Android is Starting - Optimising app ** of ***" it completes and automatically reboots again to go through the same sort of loop.
I had to reflash the TOT to be able to use the phone again. I just finished restoring my apps but I lost everything.
Could you please provide a detailed procedure of how to change the dpi without the risk of reformatting the phone each time.
Am using the H962 (Dual SIM - Taiwan)
Sent from my LGE V10 using XDA Labs
Whenever I receive a call I get "Unfortunately, Call has stopped." My DPI is set to 520 using the build.prop editor in Rom Toolbox Pro. Any ideas?
masaichris said:
What is the exact procedure to accomplish this?? I imported the xml to App Settings first then changed the DPI in build.prop to 540, I rebooted the phone and it stuck at the LG logo for like 20 minutes, then came the "Android is Starting - Optimising app ** of ***" it completes and automatically reboots again to go through the same sort of loop.
I had to reflash the TOT to be able to use the phone again. I just finished restoring my apps but I lost everything.
Could you please provide a detailed procedure of how to change the dpi without the risk of reformatting the phone each time.
Am using the H962 (Dual SIM - Taiwan)
Sent from my LGE V10 using XDA Labs
Click to expand...
Click to collapse
I think you have to change the DPI with apps you can find in playstore because when you change it throw bulid.prop the phone won't start
Sent from my LG-H960 using XDA-Developers mobile app
Did you make sure the permissions were set to rw-r-r
Sent from my LG-H901 using XDA-Developers mobile app
Any news in this dpi issue? Love the phone, hate the dpi.... so big
tdmsbn said:
So I have been fiddling with this for a long time. Messing around, having to do restores. Ran the cm 12.1 rom build for a while (the one Erwan started as an unofficial port) but the cut off top of the screen really got to me after a week.
So I went back to my stock rooted ROM and tried messing with changing the DPI in the build.prop and changing settings in the Xposed module App Settings.
Below I have a Google drive link to the xml file for the set of apps you need to have enabled and set to stock DPI for a system wide build.prop edited DPI while no longer running into crashes. Basically all I have done is set all the stock/system apps that cause issues when changing dpi system wide, just import the xml, change your dpi to whatever you like (I suggest 580/540 if you want to take real advantage of screen space)
I have included the second screen DPI set to the stock 640 but if the kinda glitched icons really bug you just disable the settings on it or adjust to a different DPI to try and minimize the weirdness. The second screen app will just appear smaller if you disable its settings in App Settings and won't cause any crashes.
App Setting XMl file for import: https://drive.google.com/file/d/0B0IaZuuoHo5MejB2NjdFTmhieXM/view?usp=docslist_api
If anybody finds any issues with the xlm or some app is crashing that I might not use or haven't used since I tried this, post it, and I'll try an keep an updated xlm available that's as stable as possible while giving us back some real screen space everywhere else.
Click to expand...
Click to collapse
Still using this? Need a smaller system DPI!
I recently rerooted my Flex 2 and ever since then my DPI simply will not change with build.prop. I have tried changing the permissions of build.prop, used several different apps to change it, etc. After reboot, the value on the line is what I changed it too, but the actual DPI does not change. Similarly, when using LE DPI Changer, even when I change it thru build.prop and it saves, LE DPI Changer still reads my current DPI as 480.
The only way I can change my DPI is using the WM Shell (I had my DPI set with this method before I got root), but this breaks several apps and is not preferred.
Anyone know what is going on here?