I have been resetting my dpi for years without issue. Now that I am systemless rooted on the 5X, I had to use adb to change dpi. Before I always used a file editor. So for some reason, resetting in adb gets me the Swiftkey keyboard in my pic. Nothing I do seems to fix it. Tried reinstalling Swiftkey, but it comes out the same. Google keyboard is not affected, nor is anything else. Also, if i change dpi using a file editor then Swiftkey works as it should. Anybody know what is happening here?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You have to change it in the build.prop too, as far as I know. Unless there is some sort of hook to override build.prop using systemless root...?
Swiftkey flat out does not support the adb only method.
Googling "swiftkey dpi" will bring up the relevant results.
PhoenixTank said:
You have to change it in the build.prop too, as far as I know. Unless there is some sort of hook to override build.prop using systemless root...?
Swiftkey flat out does not support the adb only method.
Googling "swiftkey dpi" will bring up the relevant results.
Click to expand...
Click to collapse
Bummer. The adb method did change the build.prop(I checked), but I did not know this was a known issue with Swiftkey/adb. Thanks for the heads up.
jackdubl said:
Bummer. The adb method did change the build.prop(I checked), but I did not know this was a known issue with Swiftkey/adb. Thanks for the heads up.
Click to expand...
Click to collapse
Sounds like you have it set up correctly, but just in case, checking output with the command here might help:
https://www.reddit.com/r/nexus6/com...i_to_493_swiftkey_is_now_freaking_out/cnc198j
FWIW, I have not tried changing on my 5X but have on my Shield K1 and ran into this.
Related
Just received my T-Mobile Galaxy Note 3 SM-N900T yesterday and it's gorgeous! I used CF-Auto-Root to get root in under 30 seconds as advertised! I installed F-Droid and then Adaway, which is my ad blocker of choice, but it has a problem writing the hosts file. I was wondering if this has something to do with not having access to a particular partition? It's not really a huge ordeal and I know the device is brand new but I thought I would throw this out there just in case anyone else had noticed the issue or has a solution. Thanks in advance.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ad-free is working on my phone
[I put the pic of speedtest so you can see there's no ad's
Sent from my SM-N900T using Tapatalk 4
Make sure Busybox is up to date. If you installed it, rebooted, and it still doesn't work, try enabling USB debugging, and try again. That worked for me in the past when I had issues with it not working right.
bobbyphoenix said:
Make sure Busybox is up to date. If you installed it, rebooted, and it still doesn't work, try enabling USB debugging, and try again. That worked for me in the past when I had issues with it not working right.
Click to expand...
Click to collapse
To update my own results. I couldn't get it to work normally. I had to change the host destination in settings to /data/data/hosts, and then let the app create a symlink. Now it works great.
Sent from a Galaxy Note 3 far, far away....
I know there 's a ROM out in the dev section that fixes that, but I'd like to know how to do it manually, without flashing another ROM,,,can anyone help?
Thank you!
Is this what you're looking for?
https://play.google.com/store/apps/details?id=nextapp.sdfix&hl=en
Cablespider said:
Is this what you're looking for?
https://play.google.com/store/apps/details?id=nextapp.sdfix&hl=en
Click to expand...
Click to collapse
Thanks, I tried that but it didn't work
You can download root toolbox and there is an option for it there.
Sent from my LG-D851 using XDA Free mobile app
Get kitkat external sd fix by geeksoft.
Sent from my LG-D851 using Tapatalk
Use Root Explorer.
Enable R/W
Go to /etc/permissions
Edit platform.xml as the bottom of the picture (add "media_rw" line).
Save and reboot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mingkee said:
Use Root Explorer.
Enable R/W
Go to /etc/permissions
Edit platform.xml as the bottom of the picture (add "media_rw" line).
Save and reboot
Click to expand...
Click to collapse
This is the only way it should be done.
Thanks all for the suggestions - I tried the geeksoft apk and it did the trick. Actually, the first one I tried probably worked also, but the app I was using wouldn't work (iTag)...but i switched to another (Mp3Edit) and that worked like a charm!
Incidentally, I opened that permission xml file to look at any changes, and it appears the line was added just as it should.
Thanks again!
Has anyone noticed that any application with notification access gets that access removed on a reboot? In my situation, every time I reboot the device (G3 Tweakbox I'm looking at you) it clears the access granted to some apps, specifically Missed It! and MightyText. Its annoying having to reenable them in the setting upon every reboot (in which I won't remember too until Missed It! complains about it), thus is there any work arounds on keeping it permanently enabled? Or is this a limitation of android?
~Sent via LGLS990
RedNova1203 said:
Has anyone noticed that any application with notification access gets that access removed on a reboot? In my situation, every time I reboot the device (G3 Tweakbox I'm looking at you) it clears the access granted to some apps, specifically Missed It! and MightyText. Its annoying having to reenable them in the setting upon every reboot (in which I won't remember too until Missed It! complains about it), thus is there any work arounds on keeping it permanently enabled? Or is this a limitation of android?
~Sent via LGLS990
Click to expand...
Click to collapse
Definitely not an Android thing. Some people have complained about settings not sticking after rebooting from various stock apps. I've never had any such issues though... Which build version are you on atm?
if4ct0r said:
Definitely not an Android thing. Some people have complained about settings not sticking after rebooting from various stock apps. I've never had any such issues though... Which build version are you on atm?
Click to expand...
Click to collapse
I figured as much, as I didn't remember if I had this problem on my RAZR running CM11 last time I tried these two apps. Here's my software information, so you have everything, I'm also rooted with StumpRoot v1.2 if that matters (doubtful):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
~Sent via LGLS990
So I have tried factory and aftermarket cases as well as restoring all debloated apps. Why does my screen do this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my VS986 using Tapatalk
Do you have a different dpi?
Eddiekool12 said:
Do you have a different dpi?
Click to expand...
Click to collapse
Well I am beginning to wonder if that's been changed? I never went in and changed it. I do use xposed framework but the cover still functions as it should.
How can I make sure I am at stock dpi?
Sent from my VS986 using Tapatalk
Download an app called textdroider dpi. It will tell you what dpi the phone is currently on. Anything below 640 will put the clock off center.
Eddiekool12 said:
Download an app called textdroider dpi. It will tell you what dpi the phone is currently on. Anything below 640 will put the clock off center.
Click to expand...
Click to collapse
Awesome!
Ok it says it's 560. I wonder how that happened?
Whatever the case you fixed it! For anyone else you can keep whatever dpi you want by using xposed module App Settings. Just follow these directions https://m.reddit.com/r/lgg4/comments/3htm43/how_to_fix_lower_dpi_to_quick_circle_case/
Now I just need to figure out why the led light is randomly being stuck on even after reboot, and also enabking hot spot causes a reboot.
Simultaneously I noticed SwiftKey typing very slowly too. I uninstalled it and reinstalled it and wow it types so much faster.
Sent from my VS986 using Tapatalk
Hi guys, I hope you're doing well.
When I try to change my profile picture on many apps that need to be cropped, I just can't do it, because the picture is shown out of the screen, and I can't move properly the cropping square (the selector), I can move it only horizontally and few pixels up and down.
Here is a screenshot to make it clearer for you:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Do you have any idea on how can I solve this ?
BTW: I'm using the firmware: WW 2.20.40.164 , and I had the same problem on previous versions.
.
I think this may be to do with changing DPI. Is your DPI different than stock?
thedavefitzy said:
I think this may be to do with changing DPI. Is your DPI different than stock?
Click to expand...
Click to collapse
Thank you for the reply.
Yes, I did change the DPI. is it the cause of the issue ? because the original DPI makes things big.
Thank you @thedavefitzy
I've reset the density and the problem seems to be solved.
But, I hate the 480 dpi !
Is there a way to change the dpi and having no issue ?
---------------------------------------------------------------------------------
EDIT:
I found that the best way is to reset the density whenever I want to change a pic.
And to make it easier (instead of connecting my phone to a pc and use adb), I rooted my phone, I installed a terminal emulator and I use the command:
su(enter)
wm density reset
and then I change it back to 390 (my favourite)