Related
Hi, I am fairly new to Android development. I have a question regarding the Galaxy S. What is the stock screen density of this phone in 2.1? I am trying to create the Galaxy S environment on an emulator so that I can test my application (I do not own one of these phones). Does the density change in later versions?
I have read hxxp://developer.android.com/guide/practices/screens_support.html
I know that the phone screen resolution is 480x800.
I am not sure what type of screen it is (Normal or Large), hence I cannot determine the density.
Is there an easy way of determining the density and screen type of a phone?
Thanks!
I do not know how to find out a density of other phones thought its a standard
But Samsung Galaxy S I9000 should have 240 (as seen in build.prop ro.sf.lcd_density=240 ) as the standard one and no it doesn't change in the versions.
(I use 200 though looks nicer )
Hmm, strange. The application seems to work fine with that configuration, yet one of the users is reporting an issue. I wonder if he changed the density..
Thanks for your help!
What kind of issue?
Well tell that guy to download spare parts and unticks "compatibility mode" if he is using changed density it may help him.
Grr. It was a simple user error. He thought the background picture was not appearing in the center, when it was. Just the way the picture is.
I started fiddling with making the application accessible to other densities. The AVD comes with a large screen, medium density skin (480x800/480x854 at 160dpi). Are there actually any devices that use that kind of setup? I ran my application at those settings, and for some reason it is loading the mdpi resource, which is designed for a normal screen (640x480).
Thanks for your help Pagot!
I always used 290 on my nexus 4 and it was great.
I really don't like how big the icons are stock. Any suggestions?
Sent from my XT1095 using Tapatalk 2
I use Nova, Google Launcher icons are stupidly big
320 maybe
I wouldn't go 320... the stock value is 480.
I use 440, it's perfect for me. It could be smaller (but 320 is WAY too small), but with the large screen and bumbling one-hand use 440 is perfect. Plus if you don't use XGELS to modify the launcher settings, it adds a 5th column in the app drawer.
I will also add: if you change the DPI at all, Moto Display will be weird. It's just graphical, off center and funky icons. Xposed module App Settings allowed me to change the DPI of just Moto Display back to 480 and problem solved.
how do you change the dpi? the large icons are bugging me too
_bottle_ said:
how do you change the dpi? the large icons are bugging me too
Click to expand...
Click to collapse
The large icons aren't a dpi issue, it's just the style of the Google launcher
_bottle_ said:
how do you change the dpi? the large icons are bugging me too
Click to expand...
Click to collapse
Edit the build.prop.
I just use the app "textdroider dpi" to adjust mine
Just rooted 5.0. On 4.4.4, I had my DPI at 400 with the Xposed Module App Settings to correct Moto Display. Obviously, that's not an option on Lollipop. So, my questions is, does anyone know a way to correct this while maintaining a similar DPI to 400 and do it without Xposed?
Crooke356 said:
Just rooted 5.0. On 4.4.4, I had my DPI at 400 with the Xposed Module App Settings to correct Moto Display. Obviously, that's not an option on Lollipop. So, my questions is, does anyone know a way to correct this while maintaining a similar DPI to 400 and do it without Xposed?
Click to expand...
Click to collapse
Yeah I just switched to 400 and I'm having the same issue, anyone have a fix for this?
ggmask said:
Yeah I just switched to 400 and I'm having the same issue, anyone have a fix for this?
Click to expand...
Click to collapse
Don't think there really is a fix.. With xposed you could do per app DPI.. I've learned to deal with it being a little off center using 420 dpi
CWick4141 said:
Don't think there really is a fix.. With xposed you could do per app DPI.. I've learned to deal with it being a little off center using 420 dpi
Click to expand...
Click to collapse
That was my plan but then I noticed that after some time it seemed to re-center, but the actual active portion of the screen doesn't. So I have to slide to the left of the actual unlock icon to unlock it (???). Weird.
I'm interested too, those icons and applications are too big for me. I feel like we don't benefit of the entire 5.2" screen 1920x1080 and 441 ppi... it shows exactly the same amount of content as a 4.2" screen with 150 ppi. I would be happy to find a little fix too, I have not enough skills to build it.
Maybe the key is to come back to Nexus' line, but the Moto X 2014 seem so perfect except that point.
Just install nova launcher
Sent from my XT1095 using Tapatalk
Tried it. Indeed the desktop is better, but each time I launch an application like Youtube, Whatsapp or Settings for example, it feels I'm a old person who needs very big font size. I would like to see more on my screen, with smaller font size then.
Setting ourself the DPI would have been great.
I edit with pro build dpi with root explorer , perfect.
regards
Anybody else noticed that the phone icon hasn't updated to the flatter one after update?... Looks out of place
Well, I decided to keep my XT1092 and try it out with some tweaks. I'm on Lollipop 5.0 (22.21.19 reteuall).
I firstly unlocked the bootloader, secondly I rooted it with Multitool 4.1, and finally I used "adb shell wm density XXX" to change the DPI to 360.
PERFECT : I have no glitches at all, even Active Display is OK. So I recommend this very easy method to be happy with a good screen DPI.
Edit : my bad, after the 1st reboot, I have same problem with Active Display, but it's worth it.
There will be Xposed soon I hope, then I'll take it back.
StiiLe said:
Well, I decided to keep my XT1092 and try it out with some tweaks. I'm on Lollipop 5.0 (22.21.19 reteuall).
I firstly unlocked the bootloader, secondly I rooted it with Multitool 4.1, and finally I used "adb shell wm density XXX" to change the DPI to 360.
PERFECT : I have no glitches at all, even Active Display is OK. So I recommend this very easy method to be happy with a good screen DPI.
Edit : my bad, after the 1st reboot, I have same problem with Active Display, but it's worth it.
There will be Xposed soon I hope, then I'll take it back.
Click to expand...
Click to collapse
I found this too, but ended up going back to stock DPI for another reason as well: the back button does not get properly sized when you adb the DPI, it looks too big. Same goes for some of the status bar icons (for example the battery is larger than other buttons). Then there's the glitches like your profile icon in hangouts being way too big, the top developer icon in play store being way out of position, and the triple dots under the middle word suggestion on google keyboard being too large. Changing DPI is just a hassle and makes the phone uglier, which is a real bummer because this phone desperately needs a better DPI setting.
ggmask said:
I found this too, but ended up going back to stock DPI for another reason as well: the back button does not get properly sized when you adb the DPI, it looks too big. Same goes for some of the status bar icons (for example the battery is larger than other buttons). Then there's the glitches like your profile icon in hangouts being way too big, the top developer icon in play store being way out of position, and the triple dots under the middle word suggestion on google keyboard being too large. Changing DPI is just a hassle and makes the phone uglier, which is a real bummer because this phone desperately needs a better DPI setting.
Click to expand...
Click to collapse
I don't have your problems...
Maybe it depends on which number DPI you are, mine seems OK with all of this. Also, I set "Small" font size in the settings. I got one "big" problem for me anyway, I can't use Swiftkey with this, there is a strange bug with this keyboard, I will post an screenshot later.
since I changed the stock DPI to 520(via ADB) , I'm having a couple apps acting out, SwiftKey being the main offender to the point is rendered useless
I tried clearing data/uninstall but it didn't solve the issue. I'm stock rooted. Anyone knows how to fix this?
Change your DPI back. You can't modify system appearance and expect everything to cooperate!
Donjuanal said:
Change your DPI back. You can't modify system appearance and expect everything to cooperate!
Click to expand...
Click to collapse
^^^ This.
I am using 380 dpi and it works great on everything though. 380 puts the phone into tablet mode, but using dpi numbers that are not necessarily tied to anything can cause issues.
EniGmA1987 said:
^^^ This.
I am using 380 dpi and it works great on everything though. 380 puts the phone into tablet mode, but using dpi numbers that are not necessarily tied to anything can cause issues.
Click to expand...
Click to collapse
Dang. That would make everything tiny.
sgloki77 said:
since I changed the stock DPI to 520(via ADB) , I'm having a couple apps acting out, SwiftKey being the main offender to the point is rendered useless
I tried clearing data/uninstall but it didn't solve the issue. I'm stock rooted. Anyone knows how to fix this?
Click to expand...
Click to collapse
Change it to a DPI that Google recognizes ... Multiples of 80 .... Nexus 6 is 560 g3 is 640 etc .... So go back to note 3 which is 480... This also keeps your apps from breaking because some apps won't install when you have a non Google play store DPI
Sent from my Nexus 6 using Xparent BlueTapatalk 2
Skripka said:
Dang. That would make everything tiny.
Click to expand...
Click to collapse
Na, it's perfect size. You get to see so much on screen without everything being so small you cant read it.
nexus6R3plicant said:
Change it to a DPI that Google recognizes ... Multiples of 80 .... Nexus 6 is 560 g3 is 640 etc .... So go back to note 3 which is 480... This also keeps your apps from breaking because some apps won't install when you have a non Google play store DPI
Click to expand...
Click to collapse
Really? I never knew that. Odd that 380 works perfect since that is not a multiple of 80 and it puts the Nexus 6 into tablet mode. Ill try 400 later and see how it is.
EniGmA1987 said:
Na, it's perfect size. You get to see so much on screen without everything being so small you cant read it.
Really? I never knew that. Odd that 380 works perfect since that is not a multiple of 80 and it puts the Nexus 6 into tablet mode. Ill try 400 later and see how it is.
Click to expand...
Click to collapse
The first ones had DPI of 160 then the s2 etc was 240 etc and so forth
Sent from my Nexus 6 using Xparent BlueTapatalk 2
finally got it to work
I used BuildProp Editor and changed the line ro.sf.lcd_density 520 for a 520 DPI
all apps are scaling correctly now no need to go back to those gigantic icons on stock DPI
sgloki77 said:
finally got it to work
I used BuildProp Editor and changed the line ro.sf.lcd_density 520 for a 520 DPI
all apps are scaling correctly now no need to go back to those gigantic icons on stock DPI
Click to expand...
Click to collapse
I was able to change my density using the following ADB shell commands, but it caused a few glitches with apps as others mentioned (Play Store, KeePass2Android keyboard, DSub, etc):
Code:
adb shell
wm density 480
exit
Perhaps those glitches are due to the build.prop still having the default density after applying ADB shell commands:
Code:
ro.sf.lcd_density 560
Next, I tried using a couple of different build prop editing apps, but none actually change the file even though I'm granting root access. Can anyone advise why this might be? Which app specifically did you use (play store link)?
Another method I tried was editing a copy of build.prop using a text editor, then used TWRP to replace the original and set permissions to 644. This caused my phone to get stuck at the colored dots boot screen, and forced me to do a nandroid restore in TWRP.
Seems like this should be easier...any advice?
acc3d said:
I was able to change my density using the following ADB shell commands, but it caused a few glitches with apps as others mentioned (Play Store, KeePass2Android keyboard, DSub, etc):
Code:
adb shell
wm density 480
exit
Perhaps those glitches are due to the build.prop still having the default density after applying ADB shell commands:
Code:
ro.sf.lcd_density 560
Next, I tried using a couple of different build prop editing apps, but none actually change the file even though I'm granting root access. Can anyone advise why this might be? Which app specifically did you use (play store link)?
Another method I tried was editing a copy of build.prop using a text editor, then used TWRP to replace the original and set permissions to 644. This caused my phone to get stuck at the colored dots boot screen, and forced me to do a nandroid restore in TWRP.
Seems like this should be easier...any advice?
Click to expand...
Click to collapse
use https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi its so simple.
Wait 380 put's the phone in Tablet mode?
Do apps think it's a tablet then? I'm missing Xposed and Tablet Metrics for making Spotify think I've got a tablet so I can use the skip song feature for free.
---------- Post added at 08:33 AM ---------- Previous post was at 08:02 AM ----------
Oh wow multiples of 80 actually do fix things that break! I had changed my DPI from 560 to 490 and it looked GREAT but various icons inside of apps were broken in the sense that they did not display correctly. I changed my DPI to 480, a multiple of 80 and everything displays correctly now.
I did not know Google used multiples of 80, you would think some of the quick change apps would reflect that or let you know that!
Thanks everyone!
I just tried the adb shell wm density trick to change it to 480
Looks soo much better, but i had the visual problems.
I used custom DPI on my nexus 5 with XPOSED reporting stock DPI to play store to install apps.
I want to use 480 for the nexus 6 , but i have to be rooted to edit.
Using CF autorrot is just as easy as it was for the nexus 5?
I know i need to oem unlock, i havent done that. After unlocking, using CF auto root gives me SU. Will sideloading OTA-s stiil work with root or not?
I read that since lollipop , OTAs dont work if you have any modification. It was working fine with my rooted nexus 5 on Kitkat, but since lollipop something changed.
How do I change the DPI?
---------- Post added at 08:08 AM ---------- Previous post was at 08:08 AM ----------
konaman said:
How do I change the DPI?
Click to expand...
Click to collapse
Never mind I see the app above
I'm having some difficulties with keyboard after changing the dpi to 480 so i am going back to stock dpi.
nexus6R3plicant said:
Change it to a DPI that Google recognizes ... Multiples of 80 .... Nexus 6 is 560 g3 is 640 etc .... So go back to note 3 which is 480... This also keeps your apps from breaking because some apps won't install when you have a non Google play store DPI
Sent from my Nexus 6 using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Where did you get that info? Why multiples of 80? Supposedly the native DPI of the Nexus 6 should be 493 and that's not a multiple of 80
Here's some info I found on reddit
"
The old "decide layout based on DPI" method has been deprecated since Honeycomb. Android guidelines since 3.2 indicate apps should specify a tablet layout based on the minimum resolution-independent "space" it needs to look comfortable -- the system will tell the app if that is actually the case.
Also, 480 dpi is in fact one of the "native" resolutions (XXHDPI) Google advises devs to include alternate resources in. So at 480, the system would not have to scale graphic resources for most apps, possibly making them look better. And no, 480 should not force common apps into tablet layout (source: Note 3 at native 480 dpi).
I do agree that scaling to even numbers is better; the best is to shoot for a multiple of 4 or 8, just because of how resizing algorithms work in general. So if 480 doesn't float your boat, 492 would be a very good alternative."
https://www.reddit.com/r/nexus6/comments/2mwtl9/psa_while_rooted_set_your_n6_to_its_native_493_dpi/
Chad_Petree said:
Where did you get that info? Why multiples of 80? Supposedly the native DPI of the Nexus 6 should be 493 and that's not a multiple of 80
Here's some info I found on reddit
"
The old "decide layout based on DPI" method has been deprecated since Honeycomb. Android guidelines since 3.2 indicate apps should specify a tablet layout based on the minimum resolution-independent "space" it needs to look comfortable -- the system will tell the app if that is actually the case.
Also, 480 dpi is in fact one of the "native" resolutions (XXHDPI) Google advises devs to include alternate resources in. So at 480, the system would not have to scale graphic resources for most apps, possibly making them look better. And no, 480 should not force common apps into tablet layout (source: Note 3 at native 480 dpi).
I do agree that scaling to even numbers is better; the best is to shoot for a multiple of 4 or 8, just because of how resizing algorithms work in general. So if 480 doesn't float your boat, 492 would be a very good alternative."
https://www.reddit.com/r/nexus6/comments/2mwtl9/psa_while_rooted_set_your_n6_to_its_native_493_dpi/
Click to expand...
Click to collapse
That thread is BS. The native PPI (pixels per inch).is 493. DPI is *nothing* to do with PPI. It's something entirely different. DPI is a Scaling method to make things bigger or smaller and has no direct relationship to pixels.
If you have a 5" screen with a 1080p resolution and a 10" screen with a 1080p resolution, they both have the same amount of pixels. So the pixels are much bigger on 10" screen, so all the buttons, icons etc would also be much bigger. This is not making good use of a bigger screens. So android implemented DPI to allow these assets to be scaled. What they are scaled to is completely subjective. There's no hard and fast rule. And they're Scaling within a set resolution so there is no loss of quality either.
Tablet mode comes in at under 300 DPI in later versions I believe.
danarama said:
That thread is BS. The native PPI (pixels per inch).is 493. DPI is *nothing* to do with PPI. It's something entirely different. DPI is a Scaling method to make things bigger or smaller and has no direct relationship to pixels.
If you have a 5" screen with a 1080p resolution and a 10" screen with a 1080p resolution, they both have the same amount of pixels. So the pixels are much bigger on 10" screen, so all the buttons, icons etc would also be much bigger. This is not making good use of a bigger screens. So android implemented DPI to allow these assets to be scaled. What they are scaled to is completely subjective. There's no hard and fast rule. And they're Scaling within a set resolution so there is no loss of quality either.
Tablet mode comes in at under 300 DPI in later versions I believe.
Click to expand...
Click to collapse
Now I'm confused, I didn't know the nexus 6 had a 493 PPI , I used a website to calculate the DPI and went it , and it said 493 and then I read that post, and I even found another web which says the nexus a 493 dpi :/
http://dpi.lv/
Chad_Petree said:
Now I'm confused, I didn't know the nexus 6 had a 493 PPI , I used a website to calculate the DPI and went it , and it said 493 and then I read that post, and I even found another web which says the nexus a 493 dpi :/
http://dpi.lv/
Click to expand...
Click to collapse
I believe its 493 for stock but 560 for aosp. regardless, I enjoy using 532 DPI.
simms22 said:
I believe its 493 for stock but 560 for aosp. regardless, I enjoy using 532 DPI.
Click to expand...
Click to collapse
560 is stock stock stock. Which makes for some funny big icons
Chad_Petree said:
Now I'm confused, I didn't know the nexus 6 had a 493 PPI , I used a website to calculate the DPI and went it , and it said 493 and then I read that post, and I even found another web which says the nexus a 493 dpi :/
http://dpi.lv/
Click to expand...
Click to collapse
That's because those sites are sort of wrong.
Forgetting android for a moment, in the printing industry and by extension, IT, DPI means Dots Per Inch. Literally how many dots in an Inch can be printed on a page. Dots and pixels seem very interchangeable at this point, but even there they are not. When a print designer mocks up a product for review, the pixels in electronic format do not translate to how many dots a printer can print. But because these two ideas are (somewhat incorrectly) seen as synonymous, and essentially a pixel on a screen is technically a "dot", the incorrect terms are used when it comes to screen technology.
All those sites that say the DPI is 493 are wrong. They mean PPI. The link you posted even uses PPI and then interchanges it with DPI. For screen hardware though, it certainly should be PPI.
Where we get even muddier here is that even the android developer documentation uses DPI to reflect the screen density as dots per inch. But android is using this in the software and not in the hardware. DPI is used to tell the OS what screen it has and from that the OS and Apps can decide how they should be displayed. Where as it seems right that the DPI should be set the same as the PPI, this rarely is the case. As we see with the nexus 5 and 6, Google set the DPI in android higher than the PPI because it looks better. So when Google are setting the DPI different to the PPI, we must be careful how we use these terms. The native PPI of the N6 i 493 but the native DPI is 560.
Edit > Further clarifying statement..PPI is a physical characteristic of a screen. DPI is a virtual representation of a screen.
Hi Guys,
If you wanna be normaly screen size (not original screen size of Htc Desire 510) than download this apk to your phone:
https://play.google.com/store/apps/details?id=com.nomone.resolution_changer&hl=hu
NOMone Resolution Changer (its free)
Open the app and you see
"Width" "Height" "DPI"
Change Width to 720
Change Height to 1280
Change DPI to 312
and click on apply
Or second way:
Open the app
Click on "Select device template"
and choose Motorola Moto X or Htc One X
Click on apply and you done
If you dont like this sizes,dont worry,apk will restore stock sizes after 10 sec and after 1 minutes too.
I hope its helped to some people.
Good Luck to all.
Use this all the time (different app, same effect) but it can seriously eat ram depending how far up you go. While it makes stuff look prettier, it can slow down your device.
Also our aspect ratio is weird. 720x1280 causes a border effect. Use 768x1366 at 300dpi. Looks great and uses the same amount of ram.
I don't know if it's just me or not but everything seems tiny on my screen, including the HTC home,back, and recent apps button.
this does not work on my 510.
any idea why?
do i have to be rooted?
hlebleh said:
this does not work on my 510.
any idea why?
do i have to be rooted?
Click to expand...
Click to collapse
Yes.
I've done this with a different app, but now my widgets & some other stuff seem rather disproportional.
Any way to fix this?
Other than this, however. The 720P looks much better on this phone. Thanks for the tip.
---
UPDATE: The biggest problem so far that I'm experiencing is that I cannot use my favorite keyboard. The buttons are out of place. Too big, can't fit the space allocated. SwiftKey & TouchPal are both out.
All the resolutions dont suit it they are all too big
After changing resolution, reboot your phone. The resolution will stick but everything else will resize to normal. If it doesn't, lower your DPI. All issues regarding "stuff size" should be resolved by lower DPI. Experiment, you'll find what works for you.
But again, RAM is an issue. I've asked pattyboi to adapt Swap into his kernel so I can test out RamExpander. With Swap enabled we should see a bit of a performance boost, but it can be risky if you don't know what your doing. Until we have a Swap capable kernel (and it actually works) were stcuk with what we got. From what I've read up on it, Swap seems like a viable solution to many performance issues with the 510
Okay so I'm really puzzled about how you can just change the resolution, how does it work??? Does the screen have a resolution more than the stock 480-800? I dont understand
So, that changing resolution? Is that works at all?
So I am hoping I am not the only one that thanks the stock navigation bar is way too big. On my Oneplus One I had it set pretty small, but it made the phone look better, just didn't make everything look so big.
My question is has anyone changed the DPI on the G4, and if so, what did you use to do that?
I am rooted and have flashed xTreme v1.0.
Thanks.
vng10 said:
So I am hoping I am not the only one that thanks the stock navigation bar is way too big. On my Oneplus One I had it set pretty small, but it made the phone look better, just didn't make everything look so big.
My question is has anyone changed the DPI on the G4, and if so, what did you use to do that?
I am rooted and have flashed xTreme v1.0.
Thanks.
Click to expand...
Click to collapse
You just need an app like build.prop editor, ES File Explorer,or Root Explorer to find and edit text within the build.prop file. It is in the "system" folder. Once you've accessed the build.prop look for ro.sf.lcd_density and change the value from 640 to whatever you like and restart the phone. I've heard that if you go below 540 the camera app and some other apps will not work properly. I set mine to 560. Also, if you have a quickcircle case, that quickcircle app will no longer be aligned correctly as it's set for 640 dpi. Once we get xposed running or if you have a rom that allow for per-app dpi settings, you would be able to easily fix this issue.
Hopefully this helps.
willmayah said:
You just need an app like build.prop editor, ES File Explorer,or Root Explorer to find and edit text within the build.prop file. It is in the "system" folder. Once you've accessed the build.prop look for ro.sf.lcd_density and change the value from 640 to whatever you like and restart the phone. I've heard that if you go below 540 the camera app and some other apps will not work properly. I set mine to 560. Also, if you have a quickcircle case, that quickcircle app will no longer be aligned correctly as it's set for 640 dpi. Once we get xposed running or if you have a rom that allow for per-app dpi settings, you would be able to easily fix this issue.
Hopefully this helps.
Click to expand...
Click to collapse
Did you have any bootloop issues?
vng10 said:
Did you have any bootloop issues?
Click to expand...
Click to collapse
I didn't. Never had any boot loop issues throughout the whole rooting process. I have an ATT H810 model however. Just lurking on the T-Mobile page to see what development comes out now that you all have unlocked bootloader.
willmayah said:
I didn't. Never had any boot loop issues throughout the whole rooting process. I have an ATT H810 model however. Just lurking on the T-Mobile page to see what development comes out now that you all have unlocked bootloader.
Click to expand...
Click to collapse
Okay. THanks. Yeah I tried editing the build.prop and when it rebooted, it was optimizing 32 apps and when it was finishing up, it would reboot. So I am on my backup. Ill see if there are any other options or fixes to this. I just hate how big everything looks at the default.
I used an app someone in one of the G4 threads mentioned called DPI Density changer. I lowered it to 550 seems pretty good to me.
If you're unhappy with the NavBar, you can give Swipe Navigation [Root] a try. It's GREAT on the G4, the Nexus 6 and other onScreen Nav based devices. I have it set with the NavBar completely hidden and it has an outstanding swipe gesture setup to replace the NavBar buttons. It's made every app take full advantage of the display without any loss due to the NavBar sucking up some space.
Build Prop Editor on the play store works flawlessly. The DPI option is conveniently located in the side menu too. Running 540 with no issues, though the circle case will still be misaligned.
vng10 said:
Okay. THanks. Yeah I tried editing the build.prop and when it rebooted, it was optimizing 32 apps and when it was finishing up, it would reboot. So I am on my backup. Ill see if there are any other options or fixes to this. I just hate how big everything looks at the default.
Click to expand...
Click to collapse
Build prop created boot loop for me too I switched to kernel audiutor from play store and no more boot loops. Changed dpi to 530 with no issues.
Sent from my LG-H811 using Tapatalk
Dpi density changer worked for me. Nav bar is still a little big for me at 540 but its manageable. Thanks for all the help!
Sent from my LG-H811 using Tapatalk