Database Info

Google play acceptable resolutions

Does anyone know acceptable resolutions for Google play? I use a thunderbolt and lower the density to 160, recently went to 190 and I like it there. The annoying party is Google play doesn't think my can rum the apps....so I change resolutions revoir install/update then return to my resolution of choice. This is a pain in the as...I've installed pdiddys market but it doesn't stay. After 1 reboot the hack is gone and I have to reinstall, reboot and I'm in the same boat again...not to mention of Google ever updates the market again I'll have to get an"updated"hack....anyone know how to find resolutions Google play well accept?

ang1dust said:
Does anyone know acceptable resolutions for Google play? I use a thunderbolt and lower the density to 160, recently went to 190 and I like it there. The annoying party is Google play doesn't think my can rum the apps....so I change resolutions revoir install/update then return to my resolution of choice. This is a pain in the as...I've installed pdiddys market but it doesn't stay. After 1 reboot the hack is gone and I have to reinstall, reboot and I'm in the same boat again...not to mention of Google ever updates the market again I'll have to get an"updated"hack....anyone know how to find resolutions Google play well accept?
Click to expand...
Click to collapse
i use this lcd density modder there is a free version or pro either way u can just change back and fourth between dpi as i use 160dpi on mine but market seems to like only 240dpi which is stock on my device other thing u can do is have 2 build.props and just replace the end tag with .bak and reboot

DJBoxer said:
i use this lcd density modder there is a free version or pro either way u can just change back and fourth between dpi as i use 160dpi on mine but market seems to like only 240dpi which is stock on my device other thing u can do is have 2 build.props and just replace the end tag with .bak and reboot
Click to expand...
Click to collapse
I want it to work like normal. no rebooting. I use room toolbox to change density. I think this whole density crap is dumb

I use LCD density modder pro. Comes with modded market that will spoof your density. Dev updates to latest market when available

you'll need a modded market + gsf. it won't be replaced on boot unless you did something very wrong.
the standard dpis are 120, 160, 240, 320

ang1dust said:
I want it to work like normal. no rebooting. I use room toolbox to change density. I think this whole density crap is dumb
Click to expand...
Click to collapse
as the user demo says it comes with modded market so no need to reboot

[Q] Increasing screen real estate (changing DPI) on P3113 stock rooted?

Hey guys,
I'm trying (without luck so far) to change the DPI setting on my tablet so that I can have more screen real estate.
I'm running stock (ICS) rooted on my Galaxy Tab 2 7" - this ROM:
http://forum.xda-developers.com/showthread.php?t=1798283
So far, I've tried:
- Editing build.prop myself to change DPI manually
- Using an app from the Play story
- Following the suggestions in this thread: http://forum.xda-developers.com/showthread.php?t=1826067
(no luck at all, because this app doesn't even include the lcd density slider)
In all cases, I either get no result, or I get a black startup screen. After each method/approach, I restore a clean backup from CWM (so the approaches aren't conflicting with each other).
I can't get anything to work. Any suggestions?

Did you try "Rom Toolbox Lite" from the play store. You need root to use it.
Performance > Build.prop Tweaks > LCD density ... pick what you want > Reboot.
Sorry if you tried that already but that's the easiest way to do it as far as i know.

May be because of stock rom try cm10 from www.teamhacksung.org you will not be disappointed i use it now marvellous !!!
Sent from my GT-I9100 using xda app-developers app

Sean_Seany said:
Did you try "Rom Toolbox Lite" from the play store. You need root to use it.
Performance > Build.prop Tweaks > LCD density ... pick what you want > Reboot.
Sorry if you tried that already but that's the easiest way to do it as far as i know.
Click to expand...
Click to collapse
I did indeed try that. Unfortunately, the LCD density simply isn't an option under the Build.prop tweaks menu. I'm guessing that this has something to do with the fact that my build.prop actually contains no reference to LCD density. The normal build.prop entry isn't there. I don't understand the nuts and bolts of this well enough to know why, but somehow, the system is getting its LCD density settings from something other than build.prop.
I've truly read every item in build.prop, and nothing appears to be related to LCD density, even by another name. It just doesn't seem to be in there, which is probably why Rom Toolbox Lite is intelligently removing that particular slider option from my view.
Mohamedselim said:
May be because of stock rom try cm10 from www.teamhacksung.org you will not be disappointed i use it now marvellous !!!
Click to expand...
Click to collapse
I'm completely open to going to CM10, but I'll tell you my reservation (and maybe you can tell me if I'm just missing something obvious):
I tried two or three of the CM10 roms yesterday. In all cases, when I booted to my homescreen, it was stuck in landscape mode. It wouldn't rotate into portrait, no matter what I did. I spent hours combing through threads, trying to figure out why one of the most basic aspects of being a tablet (the ability to rotate orientations) was not working. I finally came across a solution that required downloading a new launcher APK. I applied the solution, and it worked. But it felt glitchy, and the whole user experience situation was a bit disappointing. It didn't feel smooth, not that their was intense lag, but there was a noticeable UI performance hit (at least in my own subjective opinion).
It IS sort of killing me that I can't get the DPI to something more reasonable though - so I'm a motivated CM10-er. I just can't deal with a tablet that I'll practically never use in landscape, being stuck in landscape.

Have you tried setting/display/rotation and ticked autorotate,include lock screen and 0,90,180,270 degrees
You could also try Nova or apex launchers or go launcher hd i use it now
Sent from my GT-I9100 using xda app-developers app

Mohamedselim said:
Have you tried setting/display/rotation and ticked autorotate,include lock screen and 0,90,180,270 degrees
You could also try Nova or apex launchers or go launcher hd i use it now
Click to expand...
Click to collapse
Yep. I think it's actually a known bug.
I have somewhat mixed emotions about eschewing the bloatware of the stock Samsung experience, only to put on a 3rd party launcher after the fact. But that's a philosophical debate best had elsewhere. I think my issue with CM10 or AOSP right now, is that stuff just doesn't seem to work right on the P3113. I could be wrong - in fact, I very well might be wrong. I'm not necessarily as up to date as someone who has owned this tablet for more than 3 days. But in terms of the 10 or so hours I've spent clunking away at it this weekend, it seems like some really obvious stuff is missing. (rotation, etc).

Launcher not able to launch... Screen DPI

So i was playing around with diffrent DPI, i had it set to 160 and it worked great sure added a bunch of space. Then i went to try what it would look like at 140. Reboot and now the launcher will not startup. =(
So now I am lost in how to try and change the DPI setting or open any other app. I was able to open the browser from the keyboard shortcut and that is how i am posting now.
Any tips other than a full reset. I am running the 9.4.5.26 and am only rooted so far with some build prop edits.

And 140 would make the text larger than 160 correct?
I saw someone say they set it to 200, wow that would be some tiny text if i am thinking right.

shermanpat said:
So i was playing around with diffrent DPI, i had it set to 160 and it worked great sure added a bunch of space. Then i went to try what it would look like at 140. Reboot and now the launcher will not startup. =(
So now I am lost in how to try and change the DPI setting or open any other app. I was able to open the browser from the keyboard shortcut and that is how i am posting now.
Any tips other than a full reset. I am running the 9.4.5.26 and am only rooted so far with some build prop edits.
Click to expand...
Click to collapse
Install Nova Launcher via the market, it works across all the DPI I've tried.
160 resulted in text which was too small for my eyes, I ended up with 200, so halfway between the original 240 and 160.

First off i would like to say that I should have not been playing around with stuff after a 20 hour work day!
So i soft bricked my device after only having it for 4 days. It will only get to the asus boot screen with the loading circle. I can't really remember what all i did. It is not seen when i do adb devices but the computer does make a connect sound when i plug it in.
Time to do a bunch of searching around to see what i can do, or if any of you can point me in the direction it would be greatly appreciated!

Well I had to do a SD card reinstall of the os firmware. Time to just through all my set up hoops again.
To unlock or not to unlock that is the question...

So what DPI's does the stock launcher work at. I just did 200 and it doesn't run.
(don't mind me i am just talking to the internet out loud)

shermanpat said:
So what DPI's does the stock launcher work at. I just did 200 and it doesn't run.
(don't mind me i am just talking to the internet out loud)
Click to expand...
Click to collapse
I think it's been said that the stock launcher doesn't work with other dpis. Next time load up an alternate launcher.

shermanpat said:
So what DPI's does the stock launcher work at. I just did 200 and it doesn't run.
Click to expand...
Click to collapse
Are you still running the stock launcher? Because, if you are, the stock launcher tends to not work once you change the DPI.
You should first have a look at a 3rd party launcher (Go Launcher HD, Nova, etc.)
Change the DPI after setting up one of those launchers and you should be good to go!
(don't mind me i am just talking to the internet out loud)
Click to expand...
Click to collapse
That's okay! I know how frustrating it might be when no-one replies
Luckily, a lot of the members of xda are really helpful and always try their best to spread their knowledge!

When i set the dpi to 160 the stock launcher came up fine on first boot. but then did not work when i set to either 140 or 200. After i did the full reinstall i noticed a few ways that i could have gotten in and changed the build.prop file, but live and learn.
So far from the little i have tried other launchers I over all like the stock one.
Its nice to be able to have an android device that is not my phone that i have to make sure works all the time.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

[Q] Stock Android 4.1.2 rom for p6810 - Removing mobile no signal icon

Since I am only new to the forums I can't post in the Rom dev area.
I just installed Rom from http://forum.xda-developers.com/showthread.php?t=2481828
I was wondering if anyone knows how to remove the mobile signal icon from the status bar. It's great to have the stock Samsung Android 4.1.2 on my Galaxy Tab 7.7 wifi model, even if it's not perfect.
I have root access, so if it's just a matter of removing an app, i can uninstall it.
Peter

I'm pretty sure the process will involve de/re-compiling etc. Maybe SystemUI.apk. If you have data options in your device settings menu, settings.apk might need to be looked at as well.
Edit: I will take a look at a few things when I return home (away working).
Priority (apart from family) is a P6810 SkyHigh JB kernel, then followed by possible stock ROM mods, tweaks, or maybe a even a SkyHigh custom ROM - just for fun. Maybe not too, supporting a release takes precious time and testing, which I have very little ATM. Kernel release and support will be enough.
But last priority will be looking at (trying) removing any P6800 specific parts from the firmware, providing they don't impact the ROM or 'negative' effect on performance.
Please post any other firmware observations that shouldn't be on our Wi-Fi model.
Thanks.
UITA
Sent from my GT-I9500 using XDA Premium 4 mobile app

Remove: tw_stat_sys_signal_null* from SystemUI/res/drawable-mdpi

bodivas said:
Remove: tw_stat_sys_signal_null* from SystemUI/res/drawable-mdpi
Click to expand...
Click to collapse
Excellent, saves me the time
But I think that's just cosmetic. We need to look deeper yet.
Sent from my GT-I9500 using XDA Premium 4 mobile app

UpInTheAir said:
Excellent, saves me the time
But I think that's just cosmetic. We need to look deeper yet.
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The following APK can be safely removed : /preload/symlink/system/app/secphone.apk
It will also stop the tablet to try to access any mobile signal... Which cannot be achieved anyway as it is only a wifi version... Thus draining the battery for no reason..

obeguin said:
The following APK can be safely removed : /preload/symlink/system/app/secphone.apk
It will also stop the tablet to try to access any mobile signal... Which cannot be achieved anyway as it is only a wifi version... Thus draining the battery for no reason..
Click to expand...
Click to collapse
Thought there may be more to remove/edit, RIL etc, but it could just that simple. Thanks.
Sent from my GT-I9500 using XDA Premium 4 mobile app

obeguin said:
The following APK can be safely removed : /preload/symlink/system/app/secphone.apk
It will also stop the tablet to try to access any mobile signal... Which cannot be achieved anyway as it is only a wifi version... Thus draining the battery for no reason..
Click to expand...
Click to collapse
can I uninstalled with titanium? I cant see it in the list :S
can we remove " Sim toolkit" too?

Morloc2 said:
can I uninstalled with titanium? I cant see it in the list :S
can we remove " Sim toolkit" too?
Click to expand...
Click to collapse
I just installed the new Multi Window version of the Rom, which is great. However, I was wondering how you enable the Split screen mode. The apps all launch in resizable Windows, so you can have many running, I click on the pin button (which somewhere I read might switch modes) but it doesn't seem to work.
Elsewhere, I read that you need to change the DPI of the tablet in the build.prop file? Mine is currently on 160, I think some said 176 might be required to activate the split screen?
Anyone know the answer to this?

-error-

could it work?
sd3993 said:
Sorry about the late reply. Computer HD crashed :/
Anyways here are the steps.
1)Decompile SystemUI.apk
2)Go to com/android/systemui/statusbar/policy/StatusBarPolicy.smali <---Make a backup of this file before proceeding.
3)Find 'phone_signal_2' and delete the invoke-virtual 'setIcon()' method after it. (The invoke-virtual setIcon() method MAY NOT be immediately after 'phone_signal_2'. There maybe other lines in between. DO NOT delete those.)
4)Repeat Step 3 for EVERY instance of 'phone_signal_2'.
5)Recompile SystemUI.apk(don't forget to delete classes.dex from the 'keep' folder )
6)Push it back to your phone and change permissions to rw-rw-r
7)Reboot & Enjoy the extra status bar space
Click to expand...
Click to collapse

Morloc2 said:
could it work?
Click to expand...
Click to collapse
yes it works
EDIT:-Okay i absolutely did not notice the 4.1.2 :/
This mod was for gingerbread only. The files are very different in JB.
Process should be more or less the same but different files.

nice, so..what I need to try it?
can I connec the tab and modify this file?
ty

p3dboard said:
I just installed the new Multi Window version of the Rom, which is great. However, I was wondering how you enable the Split screen mode. The apps all launch in resizable Windows, so you can have many running, I click on the pin button (which somewhere I read might switch modes) but it doesn't seem to work.
Elsewhere, I read that you need to change the DPI of the tablet in the build.prop file? Mine is currently on 160, I think some said 176 might be required to activate the split screen?
Anyone know the answer to this?
Click to expand...
Click to collapse
I have played about, setting the dpi to 176 in build.prop does change it from windowed mode to split screen. However you need to change the default launcher from touchwiz before changing it from 160 to 176, as touchwiz is configured to only work at 160dpi, it crashes on any other dpi. The Samsung keyboard also has the same issue, so switch to google keyboard or SwiftKey before rebooting to bring the dpi into effect.
Also samsung calculator, camera and memo don't work at 176dpi. But if you get the photosphere camera from Android 4.3 from the s4 google edition it works.
I have seen that some have modified touchwiz to work at different dpi settings, so there might be another way to fix the Samsung apps.
If you change the dpi to 184/186, you get phablet mode for notifications, which looks more like the note 8 layout.
I think at different dpi the multi window changes mode. At 160 its like the note 10.1, with resizable Windows. At 176, its more like the note 8.
On a side note 176 dpi also fixed a bug in the aview app in the play store which would crash in portrait mode when launching videos from the Abc iview service.

how do you change this settings?

Morloc2 said:
how do you change this settings?
Click to expand...
Click to collapse
I changed the dpi by using es explorer from the play store, you can mount /system as read/write and then edit /system/build.prop
You set the lcd density to 176. Save and reboot. But make sure you change your launcher first, otherwise you will have touchwiz crashing. Another app that crashes when not running at 160 dpi is the Samsung task manager. But at 176 dpi, the split screen and windowed modes both work, the little pin in the left corner switches between modes
My next question if anyone knows. The v4 multiwindow systemui.apk, is different from the one in the p6810 rom, that is the one from the p6800 multiwindow post, if i replace my current systemui.apk, will this fix my not having split screen at 160 dpi?

p3dboard said:
I changed the dpi by using es explorer from the play store, you can mount /system as read/write and then edit /system/build.prop
You set the lcd density to 176. Save and reboot. But make sure you change your launcher first, otherwise you will have touchwiz crashing. Another app that crashes when not running at 160 dpi is the Samsung task manager. But at 176 dpi, the split screen and windowed modes both work, the little pin in the left corner switches between modes
My next question if anyone knows. The v4 multiwindow systemui.apk, is different from the one in the p6810 rom, that is the one from the p6800 multiwindow post, if i replace my current systemui.apk, will this fix my not having split screen at 160 dpi?
Click to expand...
Click to collapse
I tried replacing systemui.apk, and this copy crashed, so I went back to the copy that came with the new Rom (the working copy is 4 mb, where as the one in v4 was about 2.5mb).
I tried 156dpi, as a test, and Touch Wiz and Samsung apps work fine at this DPI, they don't crash, but then the split screen bar doesn't show, but the apps launched in windows do seem to snap to the width of the screen at 156dpi. So I think the Touchwiz / Samsung apps have some sort of upper DPI limit coded into them. So, if anyone knows how to increase this to 176dpi, this would make the Rom perfect.
Samsung APK's that would need fixing from what I can see are
- Touchwiz
- Task Manager
- Camera
- Calculator
- Memo

Great news. I tried the modified systemui.apk and after it initially crashed after replacing the 4mb version, I decided to reboot anyway to see if it worked. It does, but better than that it works at 160dpi. Split screen works!
Also you need the double lcd dpi setting in build.prop for the split screen bar to work properly.
So don't worry about the initial crash, swap over. You also get the multi screen layout tool on the system bar. If you get the version from the p6810 stock android 4.1.2 thread it also eliminates the no mobile signal icon. Finally its almost perfect !

The latest Multi-Window ROM is really good.
I did some basic tests and it seems quite good.
Cannot believe Samsung aren't putting together a Jelly Bean ROM for P6810...
Anyway flashed this ROM and tested a few things.
Globally it seems very good.
I have spotted a few cosmetic issues but I guess this is because this ROM was designed for the P6800:
- Mobile Data Icon still there,
- About device/Status, crashes.
One major problem I have though is the fact I cannot mount my 64GB Cruzer Fit (FAT32) with this ROM anymore.
This is quite a show stopper and was wondering if anything could be done about this.

I did some more testing. The modified systemui.apk and the samsung multiwindow can sometimes have a double split screen bar. Both work, but are seperate to each other so when you move one the app snaps to it, but you move the other and it snaps to it.
Not sure the exact trigger, but if you disable multiwindow in settings, you can still launch multiwindow apps using the system bar quick launcher at the bottom of the screen that is in the new modified systemui.apk.
If you go back to the original systemui.apk after using the new one, split screen actually works at 160 dpi. So i am guessing it makes some files that fix the issue at 160 dpi. The only slight issue is the split screen bar is slightly small at 160dpi.
Another bug with the modified systemui.apk is if you hold down the home button the google now quick launch ring appears in the wrong location, off to the side. The original systemui.apk doesn't have this issue. Anyway, just feedback incase someone can fix these bugs.

Feedback on the great ROM
I am now using this ROM on my GT-P6810 and I have to say it is really good with the Kernel from UpInTheAir.
I can now mount an external 64GB CruzerFit USB key. I am getting a strange white square in the menu bar though.
I cannot copy to the key but can read from it.
The work that has been done so far is great though. Thanks to both. How hard will it be to remove any (if possible) non GT-6800 menus, I don't know but it is very usable. I have no idea why Samsung haven't done such thing really. This tab still rocks!
There is one thing I would really love though and that will be to be able to write to external key. When I try do do so the key is unmounted automatically. The OS start writing to it the it is being dismounted...

On the fly screen DPI switching!

Ok, so in the past Huawei has decided on a few of their larger devices to go with 400 DPI instead of the standard 320 DPI that android should be at. This makes the UI a little to large. Sure you can root your phone and tweak the build.prop file for different DPI, but then icons look weird and there's other issues. 400 DPI just looks wrong to me, I'm sure some folks like it, but I really don't
I found something called "App Layout" in the settings today. This is awesome my friends.....
The "Standard" setting is 400 DPI (Default)
"Reduced" looks to be 320 DPI
There's even a custom where you can do per app DPI settings just like you can in Xposed framework!
This is truly a great piece of work from Huawei, Now we can set the DPI where we want it. Nicely done Huawei!
All we need now is to have the memory manager work a little better and I will go on record saying that other than Cyanogen or plain android, this is the best Vendor skin to date. So much you can do with it... I haven't even unlocked or rooted my phone yet and I don't think i'm going to bother (Plus I want to install all the update files without hassle since it seems like they are coming out pretty fast)

omniphil said:
Ok, so in the past Huawei has decided on a few of their larger devices to go with 400 DPI instead of the standard 320 DPI that android should be at. This makes the UI a little to large. Sure you can root your phone and tweak the build.prop file for different DPI, but then icons look weird and there's other issues. 400 DPI just looks wrong to me, I'm sure some folks like it, but I really don't
I found something called "App Layout" in the settings today. This is awesome my friends.....
The "Standard" setting is 400 DPI (Default)
"Reduced" looks to be 320 DPI
There's even a custom where you can do per app DPI settings just like you can in Xposed framework!
This is truly a great piece of work from Huawei, Now we can set the DPI where we want it. Nicely done Huawei!
All we need now is to have the memory manager work a little better and I will go on record saying that other than Cyanogen or plain android, this is the best Vendor skin to date. So much you can do with it... I haven't even unlocked or rooted my phone yet and I don't think i'm going to bother (Plus I want to install all the update files without hassle since it seems like they are coming out pretty fast)
Click to expand...
Click to collapse
Yeah, it's great if you decide to stay stock as you don't have to do much to change the DPI. You can change the DPI also without rooting by opening a command prompt in adb and running a command.

omniphil said:
Ok, so in the past Huawei has decided on a few of their larger devices to go with 400 DPI instead of the standard 320 DPI that android should be at. This makes the UI a little to large. Sure you can root your phone and tweak the build.prop file for different DPI, but then icons look weird and there's other issues. 400 DPI just looks wrong to me, I'm sure some folks like it, but I really don't
I found something called "App Layout" in the settings today. This is awesome my friends.....
The "Standard" setting is 400 DPI (Default)
"Reduced" looks to be 320 DPI
There's even a custom where you can do per app DPI settings just like you can in Xposed framework!
This is truly a great piece of work from Huawei, Now we can set the DPI where we want it. Nicely done Huawei!
All we need now is to have the memory manager work a little better and I will go on record saying that other than Cyanogen or plain android, this is the best Vendor skin to date. So much you can do with it... I haven't even unlocked or rooted my phone yet and I don't think i'm going to bother (Plus I want to install all the update files without hassle since it seems like they are coming out pretty fast)
Click to expand...
Click to collapse
Is this on the new updated roms? Because if can not find this setting on my stock 702 rom version?

Benjiro said:
Is this on the new updated roms? Because if can not find this setting on my stock 702 rom version?
Click to expand...
Click to collapse
I'm on a 703 running B108.
Settings -> Apps -> App Layout
That's what I have...

omniphil said:
I'm on a 703 running B108.
Settings -> Apps -> App Layout
That's what I have...
Click to expand...
Click to collapse
That explains that ... My 702 is still on B103 ... No official updates have come yet for the internal updater.

the only problem though is that the Microsoft Office apps such as Word does not go to tablet mode despite it being set to reducing mode but whenever I tweak the dpi to 320 via adb, it does show in tablet mode but some app icons and task manager are a bit messed up. Other apps such as Facebook or Youtube does seem to display on tablet orientation when in reducing mode.

mcdhol_24 said:
the only problem though is that the Microsoft Office apps such as Word does not go to tablet mode despite it being set to reducing mode but whenever I tweak the dpi to 320 via adb, it does show in tablet mode but some app icons and task manager are a bit messed up. Other apps such as Facebook or Youtube does seem to display on tablet orientation when in reducing mode.
Click to expand...
Click to collapse
I think that has to do with teh odd 1920x1200 rez. If it were 1920x1080 then it probably would detect phone mode/tablet mode correctly

Flash rom KangVIP, you can adjust DPI switching to 400, 380,360,340,320 dpi
http://cn.club.vmall.com/thread-6033530-1-1.html

eennap said:
Flash rom KangVIP, you can adjust DPI switching to 400, 380,360,340,320 dpi
http://cn.club.vmall.com/thread-6033530-1-1.html
Click to expand...
Click to collapse
If I switch the dpi to 320 if I'm using that rom does the UI becomes a bit weird? I just wanna ask because whenever I switch the actual dpi to 320 via adb (with the original B109 rom), some of the icons are smaller and have green background in them and other glitches.

mcdhol_24 said:
If I switch the dpi to 320 if I'm using that rom does the UI becomes a bit weird? I just wanna ask because whenever I switch the actual dpi to 320 via adb (with the original B109 rom), some of the icons are smaller and have green background in them and other glitches.
Click to expand...
Click to collapse
UI will be normal same as original B109 rom but font in app will be smaller.

mcdhol_24 said:
If I switch the dpi to 320 if I'm using that rom does the UI becomes a bit weird? I just wanna ask because whenever I switch the actual dpi to 320 via adb (with the original B109 rom), some of the icons are smaller and have green background in them and other glitches.
Click to expand...
Click to collapse
If you use Nova Launcher, that fixes the icon problem.

For the unlucky ones with 702L. I found a possible fix (still testing) to set the dpi to 320 without issues in SwiftKey being huge for example. Need to be ROOTED. So this is what I did.
1. Edit the build prop and add/change both " qemu.sf.lcd_density=320 " and " ro.sf.lcd_density=320 "
2. Use terminal emulator with
Su
Wm density 320
Reboot.
Now Wm density should show one value not 2 and SwiftKey should work as well.
Cheers.

Nice. Been looking for the SwiftKey fix. So, for this fix to be working do you need to get it rooted? Cheers
On 2nd thought, this SwiftKey problem doesn't exist on other keyboard apps like fleksy, googles own and go keyboard.

Yes you have to be rooted for that. But being rooted has of course a lot of other advantages and is easy to do once the bootloader is unlocked (I used the paid option from the root guide and I was rooted within half an hour).
I tried the other keyboards as well, seems SwiftKey uses other parts of build.prop to get dpi.
Hope I could help.