FORUMS

HTC Delivering Ads Straight to Sense Home

HTC’s 2015 has been a year marked by a desperate search for revenue.The HTC One M9 … more

Galaxy S6 & Edge get €100 Price Cut—New Models Incoming

Samsung has dropped the price of both the Galaxy S6 and S6 Edge by … more

How To Port Fully Featured Sony Xperia Z4 Camera

Xperia Z4’s hardware may not impress, but its software is definitely … more

Experimental TWRP Available For Moto G 2015

XDA Senior Member squid2 has posted experimental builds of TWRP for the Moto G … more

[GUIDE] How to use the Note 2 at 260dpi w/ MultiDPI & Tablet Apps (Xposed, Universal)

64 posts
Thanks Meter: 46
 
By Zathu, Member on 27th December 2012, 04:35 PM
Post Reply Subscribe to Thread Email Thread
Warning: Some people have reported boot loops after installing Xposed Framework. I've used it successfully with miscom's stock International DLL1 ROM port and scrosler's deodexed I317UCALK7 without an issue. I'm wondering if the issue could be with odexed ROMs and will take any reports on failures odexed vs deodexed.

The Note 2 ships with 320dpi configured in the build.prop file, making visual elements huge and easier to use farther away from your face or to accommodate bad vision. To maintain a screen real estate per inch ratio similar to that of a regular Android phone, you'll need to do a few easy tweaks which are easily reversible. This guide also includes tweaks to make Chrome, Gmail, gReader Pro use their tablet UI.

None of this is new, but I haven't found it documented anywhere that well. I've experimented with a dozen different DPIs, tried the multi-DPI mods, and found this to overall by the easiest and most stable route.

Requirements:
Step by step:
  1. Recommend a nandroid backup before starting
  2. Install the requirements listed above
  3. Open Xposed Installer and tap "Install/Update" and reboot
  4. Open Xposed Installer, to go Modules and ensure that "Xposed Tweakbox" is checked
  5. Open Xposed Tweakbox once, then close it. Don't enable anything here, it wasn't designed for the Note 2 and may break your phone.
  6. Open ROM Toolkit Lite, open the Root Browser, and browse to /data/data/de.robv.android.xposed.mods.tweakbox/shared_prefs/
  7. Open the de.robv.android.xposed.mods.tweakbox_preferences.x ml and modify it to include your DPI/UI mods. You can start with everything in my example file below after "START DPI MODS". Either copy & paste the text or replace the file with my example through Dropbox or USB.
  8. Open ROM Toolkit Lite again, swipe over to Performance, go into build.prop editor, scroll all the way down, tap one of the "ro.sf.lcd_density" items, change 320 to 260.
  9. If you want the stock Samsung keyboard to work, you'll have to get the modded version linked above for your ROM version. My personal goal is to keep the stock APKs untouched on my phone, so I just use the AOSP 4.2 keyboard, which scales fine to any DPI. Setting the Samsung keyboard DPI in the XML file doesn't work like it does with apps.
  10. Reboot, you should be good.

The de.robv.android.xposed.mods.tweakbox_preferences.x ml file needs to be configured to sets all of the apps that would break to a fixed 320dpi and enables Tablet mode for some Google apps. I use Nova launcher instead of TW and have it's DPI set to 300. To tweak your other apps, add them to this file using the package names found using Package Name Viewer.

You can see in the example how tablet mode is force by adding a line. There's a few other apps you could add here, such as Settings, but I found Settings to be a little too tight. This line sets tablet mode for Chrome:
Code:
<int name="dpioverride/com.android.chrome/swdp" value="600" />
To go further, the DPI of Chrome can be changed (in this case to match the Nexus 7, with this:
Code:
<int name="dpioverride/com.android.chrome/density" value="213" />
Our issue of Samsung compatibility is solved by adding lines such as this:
Code:
<int name="dpioverride/com.sec.android.app.camera/density" value="320" />
My de.robv.android.xposed.mods.tweakbox_preferences.x ml file:
Code:
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<map>
<int name="low_battery_low" value="15" />
<int name="num_signal_bars" value="4" />
<boolean name="unplug_turns_screen_on" value="true" />
<int name="long_home_press_behaviour" value="2" />
<int name="statusbar_clock_color" value="-4276546" />
<boolean name="battery_full_notification" value="true" />
<boolean name="statusbar_color_enabled" value="false" />
<boolean name="statusbar_clock_color_enabled" value="false" />
<boolean name="show_ongoing_ime_switcher" value="true" />
<int name="low_battery_close" value="20" />
<boolean name="phone_increasing_ringer" value="true" />
<int name="low_battery_critical" value="5" />
<int name="statusbar_color" value="-16777216" />
<!-- START DPI MODS -->
<!-- Play Store Keeper required to prevent DPI Errors in Play Store -->
<int name="dpioverride/com.android.vending/density" value="320" />
<!-- Tablet Mode Mods -->
<int name="dpioverride/com.android.chrome/swdp" value="600" />
<int name="dpioverride/com.noinnion.android.greader.readerpro/swdp" value="600" />
<int name="dpioverride/com.google.android.gm/swdp" value="600" />
<!-- Samsung Compatibility DPI Retainers -->
<int name="dpioverride/com.sec.android.app.voicerecorder/density" value="320" />
<int name="dpioverride/com.sec.android.app.camera/density" value="320" />
<int name="dpioverride/com.sec.android.app.videoplayer/density" value="320" />
<int name="dpioverride/com.sec.android.app.popupcalculator/density" value="320" />
<int name="dpioverride/com.sec.android.app.launcher/density" value="320" />
<int name="dpioverride/com.android.contacts/density" value="320" />
<int name="dpioverride/com.android.phone/density" value="320" />
<int name="dpioverride/com.android.smspush/density" value="320" />
<int name="dpioverride/com.sec.android.app.clockpackage/density" value="320" />
<int name="dpioverride/com.sec.android.app.FlashBarService/density" value="320" />
<int name="dpioverride/com.sec.android.mimage.photoretouching/density" value="320" />
<int name="dpioverride/com.android.calendar/density" value="320" />
<!-- Custom DPI Settings -->
<int name="dpioverride/com.teslacoilsw.launcher/density" value="300" />
<int name="dpioverride/com.android.chrome/density" value="213" />
<!-- END DPI MODS -->
</map>
Screenshots:






Last edited by Zathu; 3rd January 2013 at 08:49 PM.
The Following 8 Users Say Thank You to Zathu For This Useful Post: [ View ]
 
 
27th December 2012, 05:04 PM |#2  
Zathu's Avatar
OP Member
Thanks Meter: 46
 
More
I've also found that you can set the notification bar to the Nexus 7 style tablet size by adjusting the System UI swdp, although it's a little ugly with my toggles.

Add this line:
Code:
<int name="dpioverride/com.android.systemui/swdp" value="600" />


The Following User Says Thank You to Zathu For This Useful Post: [ View ]
27th December 2012, 05:36 PM |#3  
ahmarchi's Avatar
Senior Member
Flag Greensboro
Thanks Meter: 179
 
More
This should be sticked. Great post

Sent from my SAMSUNG-SGH-I317 using xda premium
27th December 2012, 09:31 PM |#4  
barry99705's Avatar
Senior Member
Thanks Meter: 140
 
More
Phone locks up after the first reboot when installing the xposed framework. Running Jedi rom.
28th December 2012, 01:48 AM |#5  
Att.Fan1982's Avatar
Senior Member
Flag Miami Gardens, Florida
Thanks Meter: 219
 
Donate to Me
More
Quote:
Originally Posted by barry99705

Phone locks up after the first reboot when installing the xposed framework. Running Jedi rom.

1+ same issue and I'm using miscom's stock International DLL1 ROM port(Type 3).
28th December 2012, 01:51 AM |#6  
Zathu's Avatar
OP Member
Thanks Meter: 46
 
More
Quote:
Originally Posted by Att.Fan1982

1+ same issue and I'm using miscom's stock International DLL1 ROM port(Type 3).

Interesting, I'm using type 2 of the same ROM. Must be one of those extra mods that Jedi uses as well.
28th December 2012, 03:10 AM |#7  
Member
Thanks Meter: 4
 
More
Also getting bootloop running stock international N7105XXDLL1 after installing/update the framework and reboot
28th December 2012, 02:29 PM |#8  
Zathu's Avatar
OP Member
Thanks Meter: 46
 
More
Quote:
Originally Posted by VinceThePrince

Also getting bootloop running stock international N7105XXDLL1 after installing/update the framework and reboot

Which type number are you on?
28th December 2012, 03:22 PM |#9  
Senior Member
Flag OKC
Thanks Meter: 138
 
More
Does anyone have this working? I have tried three different ROMs( asylum, Jedi, and miscoms ROM #2) and two kernels with no luck. I boot loop after installing the first mod

Sent from my SGH-I317 using xda app-developers app
28th December 2012, 03:38 PM |#10  
Zathu's Avatar
OP Member
Thanks Meter: 46
 
More
It's always worked on miscom type 2 for me. I wonder if the framework installer has changed since I got it installed. I've pulled the framework installer off of my phone, can someone try it with this?

http://db.tt/1YKhPYcX
The Following User Says Thank You to Zathu For This Useful Post: [ View ]
28th December 2012, 04:43 PM |#11  
Senior Member
Flag OKC
Thanks Meter: 138
 
More
Quote:
Originally Posted by Zathu

It's always worked on miscom type 2 for me. I wonder if the framework installer has changed since I got it installed. I've pulled the framework installer off of my phone, can someone try it with this?

http://db.tt/1YKhPYcX

I don't know if it was installing busybox from the market this time or the copy of your framework installer but I got it working! Thank you!

Sent from my SGH-I317 using xda app-developers app

Read More
Post Reply Subscribe to Thread

Tags
dpi, guide, root, tablet, xposed
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes