Bought a Galaxy Tab S 8.4 LTE 2 days ago. Beautiful device with great screen, but:
First thing you realize is the small font size in several apps, such as Facebook. Barely readable.
Tried to use larger font size in settings. That did some effect on some fonts, but no consistent result.
Same with the Big Font app - font sizes and overall appearance becomes inconsistent.
So the only way seemed to change DPI Settings. Which required rooting.
I did the CF autoroot thing. And fiddled with DPI settings using Texdroider app. Originally was 220 DPI. I tried 420 DPI.
Unfortunately after reboot, I was stuck at "systemui angehalten" error message, and touch screen did not respond to input.
Unfortunately I could not switch off the device (to reboot), pressing power button for ever gave no effect.
Since you cannot remove the battery on this device I had to let it run down completely over night. Then booting into Recovery (or Download Mode) was possible again.
Tried a full wipe in Recovery an rebooted. But endless systemui crash loop remained.
Will try to re-flash via Odin to get it back working.
So this thread is firstly a warning if anybody wants to change DPI settings on the Tab S.
Then some questions:
* Did anybody overcome the small fonts problem by changing DPI and which DPI setting is advisable?
* any way to force reboot in such case?
Just use xposed module appsetting to set the dpi for apps individually.
Sent from my SM-N9005 using Tapatalk
edan1979 said:
Just use xposed module appsetting to set the dpi for apps individually.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
AppSettings works well.. I changed the overall DPI to 240 because all the fonts were way too big for me.. I then reset certain apps back because some of the stock apps don't work right at different DPIs (camera, etc).
Reflashing revovered the systemui loop crash.
Tried App Settings, but no succes so far.
What do you guys set up, e.g. for facebook messenger?
Thanks!
Appsettings works great!
pibach said:
Reflashing revovered the systemui loop crash.
Tried App Settings, but no succes so far.
What do you guys set up, e.g. for facebook messenger?
Thanks!
Click to expand...
Click to collapse
I have rooted my galaxy for using exposed framework just to be able to use app settings! It then works great. You can set the font size (or dpi I guess) individually for any app. I use different settings ie for Gmail, Facebook messenger, Chrome, Tapatalk... You have to try a bit to find the perfect setting but it's a must.
Without you have tiny fonts!
ok, I installed xposed framework via its installer and then added the app settings module. For those willing to follow this route: you find instructions here: http://www.xda-developers.com/andro...tom-stock-roms-and-hello-to-xposed-framework/
Then it is possible to set DPI (or change font size) for each app individually. Text size and rendering was fine for me with 400DPI for Facebook, Tapatalk, or Nova Launcher. Tried with some other apps as well. Seemingly all look better and are more touch friendly with DPI >= 400. For comparison: stock DPI is set to 320 while real DPI is some 500+.
However it is rather inconvenient to set up each and every app individually via app settings module.
Tried to change the global DPI settings with build prob editor, but that somehow did not succeed, 320 DPI remained unchanged.
Tried with DPI changer to no effect. DPI cannot be changed via these apps. Very strange, have to investigate further.
Then tried again with textdroider, just to check - and device hangs again
No chance of rebooting or anything...but...yeah, found a trick: insert a SIM-card into the slot and then get asked to restart! Works. You can boot into recovery or download mode. Will try with adb to restore the build.prop backup...
Meanwhile - has anyone been able to set global DPI to something like 400-500 successfully? How?
If you look carefully I n the build.prop there usiually got 2 same dpi line... change both or disable one of it.
Sent from my SM-T705 using Tapatalk
Appsettings module is the best option,going in to build.prop is for overall and sends you in to a boot loop .be sure to have a backup
Nexus 5 via Tapatalk
@edan1979, I found only one line in build.prop indicating DPI settings. build.prop editor and DPI changer strangely cannot change that.
I did another test, changing DPI by editing build.prop with Root Explorer. It does change - and goes into UI crash loop
@jball, any idea, why it crashes?
pibach said:
@edan1979, I found only one line in build.prop indicating DPI settings. build.prop editor and DPI changer strangely cannot change that.
I did another test, changing DPI by editing build.prop with Root Explorer. It does change - and goes into UI crash loop
@jball, any idea, why it crashes?
Click to expand...
Click to collapse
Unfortunately I don't, I just know what happened the first time I did it.
Appsettings is the best option though
Nexus 5 via Tapatalk
pibach said:
@edan1979, I found only one line in build.prop indicating DPI settings. build.prop editor and DPI changer strangely cannot change that.
I did another test, changing DPI by editing build.prop with Root Explorer. It does change - and goes into UI crash loop
@jball, any idea, why it crashes?
Click to expand...
Click to collapse
the UI will crash since it was build for the original dpi and the ui setting as well... just install another launcher first and clear the Touchwiz data. It wont crash any longer but if you use touchwiz it wont be good looking... and some other touchwiz related apps will crash as well... that one can be settle using app setting to original dpi.
pibach said:
@edan1979, I found only one line in build.prop indicating DPI settings. build.prop editor and DPI changer strangely cannot change that.
I did another test, changing DPI by editing build.prop with Root Explorer. It does change - and goes into UI crash loop
@jball, any idea, why it crashes?
Click to expand...
Click to collapse
Samsung is too lazy to support multidpi for their apps that's made for specific DPI values.
I did not use Touchwiz. It is SystemUI that crashes...
pibach said:
I did not use Touchwiz. It is SystemUI that crashes...
Click to expand...
Click to collapse
Unless you are running CM, everything is part of Touchwiz, including SystemUI.
kenkiller said:
Unless you are running CM, everything is part of Touchwiz, including SystemUI.
Click to expand...
Click to collapse
Is it?
CM?
The DPI problem and crashes do occur as well on non Samsung devices. Don't they?
pibach said:
Is it?
CM?
The DPI problem and crashes do occur as well on non Samsung devices. Don't they?
Click to expand...
Click to collapse
Not really. I change DPI systemwide on my Nexus devices, they don't crash so easily - they are pretty much unified in terms of software.
Samsung really doesn't like to make a one size fits all firmware for the dozens of devices they release, so you get "problems" like this - to be fair, they don't really anticipate the average user to go around fooling with the DPI values.
Probably Samsung has set 320 DPI on all their devices?
pibach said:
Probably Samsung has set 320 DPI on all their devices?
Click to expand...
Click to collapse
Who knows...who cares? Their assets probably isn't made for all the existing DPIs.
Anyway, xposed app settings works fine for most apps, just gotta live with the systemUI being stuck in that.
If systemUI belongs to TouchWiz, couldn't it be replaced? How?
pibach said:
If systemUI belongs to TouchWiz, couldn't it be replaced? How?
Click to expand...
Click to collapse
Sure....Flash Cyanogenmod for it, if it exists and you don't mind losing all of Samsung's features.
Hope someone can help.
I have changed my lcd density through my build prop.
I'm using app settings in xposed and changed the sview Cover app to 480 but there is a black bar at the bottom.
Anyone know how to fix this?
jdubya45 said:
Hope someone can help.
I have changed my lcd density through my build prop.
I'm using app settings in xposed and changed the sview Cover app to 480 but there is a black bar at the bottom.
Anyone know how to fix this?
Click to expand...
Click to collapse
+1
there is a semi solution for this
usually people use rom toolbox to change the entire dpi.
first you must return the dpi to the normal 640 in rom toolbox
then in app settings Xposed change com.android.systemui dpi to 480
and then go to Android System (Android) and change the dpi back to 640
don't forget each time you must turn on the app setting and save after the change
this might effect some of the apps and show it in normal size but it will fix your problem
plus you can change any app's dpi to 480 from app settings later and make it small again.
omid_freesky said:
there is a semi solution for this
usually people use rom toolbox to change the entire dpi.
first you must return the dpi to the normal 640 in rom toolbox
then in app settings Xposed change com.android.systemui dpi to 480
and then go to Android System (Android) and change the dpi back to 640
don't forget each time you must turn on the app setting and save after the change
this might effect some of the apps and show it in normal size but it will fix your problem
plus you can change any app's dpi to 480 from app settings later and make it small again.
Click to expand...
Click to collapse
Thought id note as far as I know the stock DPI is 480.
Sent from my SM-G900A using Tapatalk
I used xposed setting to change my dpi and I used it to specify original dpi of 640 for the sviewcover app but the black bar still persists.
Rakuu said:
Thought id note as far as I know the stock DPI is 480.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
you're right, I have a galaxy note 4, I'm sorry
I'm not sure about your original dpi though, but the method should work
android:layout_gravity
android:layout_columnweight
android:layout_rowweight
what does these xml lines refer in android studio in grid layout ?
Android: layout_gravity
- If value is 1, the object occupies the width or length of the page
-2 objects of gravity value 1; Share half of the page
android:layout_columnweight
android:layout_rowweight
- Used for table_layout, rows, and columns. The same employer is used as Layout_gravity.
- For example, there are 5 columns or rows. I want them to share the page equally.
All weight values 1
srinidhikowshik said:
android:layout_gravity
android:layout_columnweight
android:layout_rowweight
what does these xml lines refer in android studio in grid layout ?
Click to expand...
Click to collapse
*requires root* tested on OB22
So after seeing the recent XDA post about enabling Google photo back up when charging, I figured I'd do some snooping around in the shared preferences files myself.
I found out you can change the amount of columns in the stock OnePlus launcher (to add more than the standard 3/4/5 columns).
To do this you need to go to:
/data/data/net.oneplus.launcher/shared_prefs/net.oneplus.launcher.prefs.xml
Then change the number in this line (at the bottom of the file) to whatever number you want.
<int name="workspace_columns" value="5" />
I don't recommend adding too many columns, as the icons will start to overlap (see the screenshots below). For medium icon size this will happen with values higher than 7-8, setting the icon size to small will prevent this to a certain extent.
After editing this line you need to force close the launcher for the changes to taken effect.
You will however still have 5 rows. This (probably) can't be changed in this way, due to the rows not being customizable in the launcher. The columns are, which is the reason this line exists.
Below are some screenshots, as you can see the icons are almost touching each other which 8 columns. The 12 columns are more a proof of concept.
Is it possible to add more rows?
This is why i'm still on nova laucher... when this will be costumizable on stock launcher? pleaaaaaaaaase...
Hello, this method is not working anymore on latest version. Can you help me what might be the problem? Also what file manager and xml editor did you use? Thanks!
albannotosska said:
Hello, this method is not working anymore on latest version. Can you help me what might be the problem? Also what file manager and xml editor did you use? Thanks!
Click to expand...
Click to collapse
I unfortunately broke my OnePlus, so I can't really help you too much with troubleshooting. Last I tested was on oos pie, so it probably should still work. I used solid explorer to edit the files.
Are you sure you are rooted? There are apps available to manage shared preferences files of all your apps. Maybe you'll have more luck if you try one of those.
stelio_kontos said:
I unfortunately broke my OnePlus, so I can't really help you too much with troubleshooting. Last I tested was on oos pie, so it probably should still work. I used solid explorer to edit the files.
Are you sure you are rooted? There are apps available to manage shared preferences files of all your apps. Maybe you'll have more luck if you try one of those.
Click to expand...
Click to collapse
I am sorry for your oneplus. The line is there and I have tried changing it but it doesn't do anything. It only happened with the latest version. I am on Pie. I am rooted with the latest Magisk, tried many explorers and many xml file editor . Anyway thank you for your reply. I will try to search and maybe I can find something.
I am using android studio version 3.0. App icon smaller compared to other apps on virtual and real device, I've done whatever can be done in android studio and in android asset studio, trim, don't trim and change shape, always my app icon smaller after installing. Cannot remove padding of the icon.
I figured it out how to fix it by creating separate icons with different resolutions.