I was under the impression that the LCD density was decided by the ROM within the build.prop and that one would have to change the build.prop with every new install. A few days ago, I used ROMtoolbox to change the pixel density to 445 in slimkat. All went well, but since then, I have installed 2 slim updates that I'm certain were 361ppi that automatically changed themselves to 445ppi on install. Both updates were full wipes. Is this normal? Does changing the build.prop of a ROM change something in your phone forever? It doesn't really matter, I just assumed that the build.prop was ROM controlled and that I would have to adjust it with each new update or ROM.
Related
Hi,
yesterday i almost bricked my pad. At least i think so.
What i did was to copy a build.prop for US SKU insted of WW.
What that meant was that i couldn't get pass ASUS logo and the boot sequence didn't even start. At least i think this is a reason. Can't think of anything else. Except I have also temporarily unrooted it with OTA root keeper.
Anyway, long story short is that the only thing that helped me get my pad to life again was to manually update it to version .26 with a microSD card.
Because before this i have tried wipe data option and didn't help i have lost all my sd data, but that is a small price.
I went and started to get my pad in order and tweaks i had before. Rooted, changed build.prop and installed my own bootanimation.
I usually create my own folder for boot animations inside the /system/media and change the bootanimation_config_04.txt to pioint to my new zip. After restart, however, there was a weird bootanimation i have never seen before - android text, thats all.
I thought i did something wrong, because this always worked and i was surprised. Maybe a typo or something and the system provided with backup one....don't know.
So, i have searched and searched. No help. Whatever i did i always got that weird android animation.
Finally i have installed a bootanimation app from market, installed some random animation via that app and rebooted.
Huh, the animation changed, Dafuq?
So I looked at app settings and the location that it installs zip to is /data/local
My questions:
Is this normal? Why doesn't the old way work (/system/media), do i have a faulty installation?
Everything up until now looks pretty OK, except i am now getting a google maps crashes that i never had before.
I am away this week so i can't test everything, but it seems OK, except for some minor things. For example some games i had before cant be found on the market etc (dark knight, nfs). Maybe this is becouse of DPI changes.
Aynway, is this normal? What to do to get my /system/media way of bootnaimations back?
Thanks!
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.
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:
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?