Develop Bugs

How To : Install and Configure OpenVPN client

Purpose:
Tutorial to describe how to install and configure an OpenVPN client on a rooted Epic 4G Touch. This "how to" assumes you know what OpenVPN is and have a verified working OpenVPN server.
Client Requirements:
Rooted Epic 4G Touch with either:
A kernel with built-in tun support (stock kernel)
A kernel with a seperate tun.ko module (Rogue Desperado).
Tested Rom/Kernel Combinations:
Blazer 1.2 ROM (EG30 Base) with included Kernel :
Blazer 1.2 ROM (EG30 Base) with Rogue v1.3.0 "Desperado" Kernel (comes with seperate tun.ko module)
Tested Server Configurations:
Windows OpenVPN server (Bridged mode UDP).
Windows OpenVPN server (Bridged mode TCP).
Asus RT-N16 router running DD-WRT v24-sp2 (06/14/11) mega - build 17201 (Bridged mode TCP)
Install BusyBox:
If you already have BusyBox this step may be unnecessary, if you do have it BusyBox Installer should tell you where.
On your device download and install "BusyBox Installer" (by JRummy16):
https://market.android.com/details?id=com.jrummy.busybox.installer
Run the BusyBox Installer and accept the default version (BusyBox v1.19.3) and location (/system/xbin/)
Scroll down to the bottom and press the "Install" button.
{
"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"
}
Install OpenVPN Installer:
When I first installed OpenVPN I used Freidrich Schäuffelhut's installer which let me connect, however the client never got an IP address from the OpenVPN DHCP server. I had to go through the manual step of opening a terminal window on my device after I connected and typing the command "netcfg tap0 dhcp". This is due to Schäuffelhut's installer putting an OpenVPN binary that's not fully compatible with BusyBox, this can fixed by using Sascha Volkenandt's installer instead.
On your device download "OpenVPN Installer" (from Sascha Volkenandt NOT Friedrich Schäuffelhut):
https://market.android.com/details?id=de.akvsoft.droid.ovpninstall
Run the installer, keep the default path values (OpenVPN Targe Location: /system/xbin, Busybox Install Path: /system/xbin), unless you have an existing Busybox installed in an alternate location, then obviously change the Busybox install path value to that location.
Verify that "Your device is rooted" and "Busybox is installed" status lines are checked. You can ignore the yellow exlamation mark on the "TAP/TUN module is NOT installed" line, the installer said that for both kernels that I tested which worked fine, so obviously the installer's tap module detection method isn't quite flawless.
Press the Install button.
Install OpenVPN Settings:
On your device download and install "OpenVPN Settings" (Friedrich Schäuffelhut):
https://market.android.com/details?id=de.schaeuffelhut.android.openvpn
Configure OpenVPN Settings to use the tun.ko module:
The following procedure is only needed for kernels that have an external tun.ko module such as the Rogue v1.3.0 "Desperado" Kernel, not kernels with built-in tun support, such as the stock kernel.
Run OpenVPN Settings
Press the "menu"
Press the item labeled "Advanced"
Check the "Load tun kernel module" option
Press "TUN module settings"
Press item labeled "Path to tun module"
Set the textbox value to the path of your tun.ko module, for the Desperado Kernel the installed location is "/lib/modules/tun.ko", then press the "OK" button
Press item labeled "Load module using"
Choose the "insmod" option
Connect and test the VPN connection:
Make sure you have transfered your .ovpn client connection configuration file(s) and certificates to your device. The default location that the OpenVPN settings application looks for these files is in the "/sdcard/openvpn" folder (folder location can be specified in the advanced settings).
Start the OpenVPN Settings application
Make sure "OpenVPN" is checked.
Pick the .ovpn client config from list of OpenVPN configurations
After you're connected the status line should tell your IP address on the remote network.
Test your connection by pinging an IP address and/or host name on the remote network. I use Ping & DNS as my ping application.
Note: The OpenVPN Settings client doesn't pick up the remote DNS server DHCP push option so you must configure the DNS per connection configuration manually by:
Tap and Holding the OpenVPN configuration from the list.
Choosing "Preferences" from the popup menu.
Checking the "Use VPN DNS Server" option.
Press the "VPN DNS Sever" item and set it to your desired DNS server.
Troubleshooting:
Install and run Android Terminal Emulator by Jack Palevich:
https://market.android.com/details?id=jackpal.androidterm
Check for an active tap0 interface
Open terminal
type "su"
type "netcfg", one of the entries should be labeled "tap0" with a valid IP address.
Sample Client .ovpn connection configuration:
client
dev tap
proto udp
remote myhost.mydns.xxx 1184
resolv-retry infinite
nobind
persist-key
persist-tun
ca "home/ca.crt"
cert "home/client1.crt"
key "home/client1.key"
ns-cert-type server
comp-lzo
verb 3
Click to expand...
Click to collapse

Not a bad guide, well detailed.

Excellent guide. Had the same issues as you (OV would show connected but no IP address was assigned to it). Thanks!
EDIT: Working OK with Calkulin's 2.6

Very great guide, but unfortunately I read it after I already had installed the OpenVPN Installer by Friedrich Schäuffelhut...
Any tips on how to remove it so I can install Sascha Volkenandt's version?
I've already confirmed that I still have a /system/xbin/openvpn binary after I already uninstalled the OpenVPN Installer app, which makes sense, since all that stuff is done separate from the app.

jauling said:
Very great guide, but unfortunately I read it after I already had installed the OpenVPN Installer by Friedrich Schäuffelhut...
Any tips on how to remove it so I can install Sascha Volkenandt's version?
I've already confirmed that I still have a /system/xbin/openvpn binary after I already uninstalled the OpenVPN Installer app, which makes sense, since all that stuff is done separate from the app.
Click to expand...
Click to collapse
You can uninstall the program then just install Volkenandt's version. But you don't even need to do any of this unless you are still on Gingerbread. For ICS and Jellybean, just use the program OpenVPN for Android... much more simplified.

beezar said:
You can uninstall the program then just install Volkenandt's version. But you don't even need to do any of this unless you are still on Gingerbread. For ICS and Jellybean, just use the program OpenVPN for Android... much more simplified.
Click to expand...
Click to collapse
Thanks for the reply!
Any idea if OpenVPN for Android supports tap? That's the main reason why I went with the app I did. I wasnt sure if Arne's app meant 4.0+ doesnt support tap, or just 4.0...

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

[GUIDE] How to use the Note 2 at 260dpi w/ MultiDPI & Tablet Apps (Xposed, Universal)
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:
Root
ROM Toolkit Lite https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox
Xposed Framework APK http://forum.xda-developers.com/showpost.php?p=34609290&postcount=2
Xposed Tweakbox APK http://forum.xda-developers.com/showthread.php?t=1629653
Package Name Viewer https://play.google.com/store/apps/details?id=com.gijoon.pkgnameviewer
OPTIONAL Modded Samsung Keyboard http://forum.xda-developers.com/showthread.php?t=2001577 (if you want use Samsung KB)
OPTIONAL Xposed App Settings http://www.villainrom.co.uk/forum/microdownloads/xposed-app-settings.5/viewfile (if you want to set app DPI with a GUI rather than editing XML)
Step by step:
Recommend a nandroid backup before starting
Install the requirements listed above
Open Xposed Installer and tap "Install/Update" and reboot
Open Xposed Installer, to go Modules and ensure that "Xposed Tweakbox" is checked
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.
Open ROM Toolkit Lite, open the Root Browser, and browse to /data/data/de.robv.android.xposed.mods.tweakbox/shared_prefs/
Open the de.robv.android.xposed.mods.tweakbox_preferences.xml 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.
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.
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.
Reboot, you should be good.
The de.robv.android.xposed.mods.tweakbox_preferences.xml 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.xml 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:
{
"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"
}

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" />

This should be sticked. Great post
Sent from my SAMSUNG-SGH-I317 using xda premium

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

barry99705 said:
Phone locks up after the first reboot when installing the xposed framework. Running Jedi rom.
Click to expand...
Click to collapse
1+ same issue and I'm using miscom's stock International DLL1 ROM port(Type 3).

Att.Fan1982 said:
1+ same issue and I'm using miscom's stock International DLL1 ROM port(Type 3).
Click to expand...
Click to collapse
Interesting, I'm using type 2 of the same ROM. Must be one of those extra mods that Jedi uses as well.

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

VinceThePrince said:
Also getting bootloop running stock international N7105XXDLL1 after installing/update the framework and reboot
Click to expand...
Click to collapse
Which type number are you on?

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

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

Zathu said:
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
Click to expand...
Click to collapse
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

moustro said:
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
Click to expand...
Click to collapse
Hmm, don't most of these suped up ROMs like Jedi have Busybox included already? Perhaps it is the Framework version. I've updated the main post with a new link.

Zathu said:
Hmm, don't most of these suped up ROMs like Jedi have Busybox included already? Perhaps it is the Framework version. I've updated the main post with a new link.
Click to expand...
Click to collapse
Jedi doesn't have it, but it still locks up with busybox installed.

Thanks for the guide. After trying different DPIs I've found 260 feels perfect for this phone.

barry99705 said:
Jedi doesn't have it, but it still locks up with busybox installed.
Click to expand...
Click to collapse
The updated framework link should take care of that.

Zathu said:
The updated framework link should take care of that.
Click to expand...
Click to collapse
Nope. Still locks up at boot. Though with the newest installer I can no longer adb into the phone, so I get to do the battery pull and restore instead of just doing an adb shell are moving the file back from it's backup...

Just tried this today. I found it was easiest to use the gui based app settings mod. Much simpler than coding up the xml. Works great with Gmail at a low mid forced resolution and moderate dpi. I recommend a nandroid backup because I got stuck in boot the first time around.
Edit: the best apps for this I've tested were Gmail and reddit sync. Chrome was a waste of space and the play store was overly laggy.

This is awesome, thanks OP!
I found that I had to add com.android.mail to the list of 320dpi apps, or there were a few UI issues in the mail app. Loving having Chrome with the tablet UI!

Zathu said:
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" />
Click to expand...
Click to collapse
What do I do just to get this? Nexus 7 notification? Where do I add that line?

Will this mod work with stock rooted rom (jl5)? Does it need to be deodexed?
Sent from my SGH-I317M using xda premium

Immersive mod activation for certain apps with adb shell without root

Hello!
Is' it possible to activate immersive mode for certain apps over adb shell but without root access?
Did somebody tried this?
I'm asking this primary because of "issue" with status bar and Google Chrome (it's not hidden like it should be, at least for me).
Thank You all on reading and answer!
Here is shell list:
adb shell settings put global policy_control immersive.full=com.android.chrome
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Security exception: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
at com.android.providers.settings.SettingsProvider.enforceWritePermission(SettingsProvider.java:1793)
at com.android.providers.settings.SettingsProvider.mutateGlobalSetting(SettingsProvider.java:974)
at com.android.providers.settings.SettingsProvider.insertGlobalSetting(SettingsProvider.java:948)
at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:359)
at android.content.ContentProvider$Transport.call(ContentProvider.java:401)
at com.android.providers.settings.SettingsService$MyShellCommand.putForUser(SettingsService.java:387)
at com.android.providers.settings.SettingsService$MyShellCommand.onCommand(SettingsService.java:285)
at android.os.ShellCommand.exec(ShellCommand.java:96)
at com.android.providers.settings.SettingsService.onShellCommand(SettingsService.java:51)
at android.os.Binder.shellCommand(Binder.java:597)
at android.os.Binder.onTransact(Binder.java:495)
at android.os.Binder.execTransact(Binder.java:700)
I have found a solution!!!
Answer in this particular case is that to be able to change permissions man must change option in developer menu to allow granting permissions!

Getting same error.. it required write permission...
You can try this commands
adb shell pm grant com.android.chrome android.permission.WRITE_SECURE_SETTINGS
adb shell settings put global policy_control immersive.full=com.android.chrome
Enable write permission and then run immersive command.
Let me know if it works.

You can use tasker/automagic, which has been granted write secure permission. Then create a profile/trigger with the app Chrome, action turn on the immersive mode. I use Automagic and the example is 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"
}
When you scroll up, the url bar also hidden. If you swipe from top or bottom, the status bar and navbar appear as in the right one. You can choose to hide the statbar only, navbar only or both.

SunilSuni said:
Getting same error.. it required write permission...
You can try this commands
adb shell pm grant com.android.chrome android.permission.WRITE_SECURE_SETTINGS
adb shell settings put global policy_control immersive.full=com.android.chrome
Enable write permission and then run immersive command.
Let me know if it works.
Click to expand...
Click to collapse
Nope!
Didn't worked!
Here is the shell list:
adb shell pm grant com.android.chrome android.permission.WRITE_SECURE_SETTINGS
Operation not allowed: java.lang.SecurityException: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.

Desmanto said:
You can use tasker/automagic, which has been granted write secure permission. Then create a profile/trigger with the app Chrome, action turn on the immersive mode. I use Automagic and the example is here
When you scroll up, the url bar also hidden. If you swipe from top or bottom, the status bar and navbar appear as in the right one. You can choose to hide the statbar only, navbar only or both.
Click to expand...
Click to collapse
First let me thank You!
Second, my intention is to enable this on system level, without any kind of utility. If this is not possible, then i will probably give up, on my shame :silly:

Jehonan said:
Nope!
Didn't worked!
Here is the shell list:
adb shell pm grant com.android.chrome android.permission.WRITE_SECURE_SETTINGS
Operation not allowed: java.lang.SecurityException: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.
Click to expand...
Click to collapse
Ok, we all want to achieve the solution with the minimum footprint. Xiaomi's phones all have additional security for the usb debug. You have to enable the USB debugging (security settings) first (below the USB debugging) to be able to grant write secure permission, adb input and similar command. To enable it, you have to login first using your Mi Account, then pass thru the 3 times prompt and OK. Then try your adb shell command again, it should works fine now (command successful, or no error shown).

Desmanto said:
Ok, we all want to achieve the solution with the minimum footprint. Xiaomi's phones all have additional security for the usb debug. You have to enable the USB debugging (security settings) first (below the USB debugging) to be able to grant write secure permission, adb input and similar command. To enable it, you have to login first using your Mi Account, then pass thru the 3 times prompt and OK. Then try your adb shell command again, it should works fine now (command successful, or no error shown).
Click to expand...
Click to collapse
Heh, sadly after reboot all changes are history
So at least for now, no luck

Jehonan said:
Heh, sadly after reboot all changes are history
So at least for now, no luck
Click to expand...
Click to collapse
It seems my post yesterday vanish...
Your last resort is Automation app. You can try most of them first to see if it fits your need. I personally use Automagic. A simple flow with App Task Started : Chrome and Action Set Immersive Mode - without navigation. And another flow to reset it.
I have used about 40+ active flows, and still managed to get about 10+ hours SOT. So the app almost doesn't drain any battery. But it has helped throughout my daily activities, can't imagine my daily life without it anymore.

[MAGISK]Notch Killer - Videos and Apps ignores the notch

I couldn't find a working module for the 7T so I created one.
What it does?
In apps like Netflix and Full-screen games the screen stretches only until it reaches the notch.
This module basically allows to ignore the notch and stretch the display around it.
Netflix example:
Before:
{
"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"
}
After:
Click to expand...
Click to collapse
Instructions:
Download the attached zip and extract the NotchKillerOOS Directory.
Move the NotchKillerOOS directory into your phone.
Using ROOT explorer like "ES file explorer" move the folder into /data/adb/modules
Reboot your device
Go to the Developer options, click on "Display cutout" and choose "Notch killer!"
Please report any bugs.
Enjoy

Not working for me.

QbaxPl said:
Not working for me.
Click to expand...
Click to collapse
You got any error?
Wrong behavior?
Happens on a specific app?
Please explain the issue you're having.

I dont have option to choose Notch killer in Dev options.

I followed your instructions and now I have a Notch Killer Magisk module enabled and after a reboot I went to developer settings--> display cutout
There wasn't any option like Notch Killer
Please see attached screenshot

QbaxPl said:
I dont have option to choose Notch killer in Dev options.
Click to expand...
Click to collapse
MrGimpGrumble said:
I followed your instructions and now I have a Notch Killer Magisk module enabled and after a reboot I went to developer settings--> display cutout
There wasn't any option like Notch Killer
Please see attached screenshot
Click to expand...
Click to collapse
Hi please try the following steps:
1. Uninstall the NotchKillerOOS module.
2. Download the new zip that is attached to this message.
3. Extract the zip and move it to your phone.
4. Move the NotchKillerOOS directory to /data/adb/module
5. Make sure that the file structure is like the following "/data/adb/modules/NotchKillerOOS/system/product/overlay/DisplayCutoutEmulationTall/DisplayCutoutEmulationTallOverlay.apk"
and NOT like:
"/data/adb/modules/NotchKillerOOS/NotchKillerOOS/system/product/overlay/DisplayCutoutEmulationTall/DisplayCutoutEmulationTallOverlay.apk"
6. Go to Magisk manager and make sure that the module is enabled.
7. Reboo the phone and try again.
If you still have problems, please send me your "DisplayCutoutEmulationTallOverlay.apk" file that is located under /product/overlay/DisplayCutoutEmulationTall.
(The one that is on your phone, not the one that came with the module).
Let me know if it works.

yaaria said:
Hi please try the following steps:
1. Uninstall the NotchKillerOOS module.
2. Download the new zip that is attached to this message.
3. Extract the zip and move it to your phone.
4. Move the NotchKillerOOS directory to /data/adb/module
5. Make sure that the file structure is like the following "/data/adb/modules/NotchKillerOOS/system/product/overlay/DisplayCutoutEmulationTall/DisplayCutoutEmulationTallOverlay.apk"
and NOT like:
"/data/adb/modules/NotchKillerOOS/NotchKillerOOS/system/product/overlay/DisplayCutoutEmulationTall/DisplayCutoutEmulationTallOverlay.apk"
6. Go to Magisk manager and make sure that the module is enabled.
7. Reboo the phone and try again.
If you still have problems, please send me your "DisplayCutoutEmulationTallOverlay.apk" file that is located under /product/overlay/DisplayCutoutEmulationTall.
(The one that is on your phone, not the one that came with the module).
Let me know if it works.
Click to expand...
Click to collapse
Yeah bro, I can confirm it works. But there's a slight problem, the icons on the status bar tends to hide behind the notch, any way to make them hide as they reach towards the notch? (like they do in the default notch mode)

Minimilised_MR said:
Yeah bro, I can confirm it works. But there's a slight problem, the icons on the status bar tends to hide behind the notch, any way to make them hide as they reach towards the notch? (like they do in the default notch mode)
Click to expand...
Click to collapse
Unforchently for now, I cannot change the location of the status bar icons and text.
So you can switch between the mods whenever you need them.

yaaria said:
Unforchently for now, I cannot change the location of the status bar icons and text.
So you can switch between the mods whenever you need them.
Click to expand...
Click to collapse
I think it is possible to automatically set it on/off with the desired apps using Tasker. But I didn't test it yet, just thinking it'll work.
Sent from my OnePlus7T using XDA Labs

Sharing in case people who use this module would like to automate using tasker.
Use following shell command:
Enable
Code:
cmd overlay enable --user 0 com.android.internal.display.cutout.emulation.tall
Disable
Code:
cmd overlay disable --user 0 com.android.internal.display.cutout.emulation.tall
Enjoy fullscreen!

Is there any way I can use it without root (magisk) by ADB?

Thank you bro it works on my Rooted OP7T.
side note....
If you download systemuituner and turn on immersive mode it makes ur module PERFECT!!
Again thank u.... @yaaria

ryantf420 said:
Thank you bro it works on my Rooted OP7T.
side note....
If you download systemuituner and turn on immersive mode it makes ur module PERFECT!!
Again thank u.... @yaaria
Click to expand...
Click to collapse
Good to know, thank you

I have followed instructions but no way to see option notch killer in developer options under cutout...
Magisk see module, properly extracted files like u adviced...
Any ideas? Want to watch Netflix without notch
Posted using OnePlus 7T via Tapatalk

the bottom option translates to high notch. select the bottom option should be good if followed file instructions...

Oh... I was looking for "Notch Kill" not translated to Polish hehe. I selected very bottom which means like "high cutout" option and it's working. Thank you so much.
Posted using OnePlus 7T via Tapatalk

Riski3Run said:
Oh... I was looking for "Notch Kill" not translated to Polish hehe. I selected very bottom which means like "high cutout" option and it's working. Thank you so much.
Posted using OnePlus 7T via Tapatalk
Click to expand...
Click to collapse
no problem ?
---------- Post added at 02:27 PM ---------- Previous post was at 02:25 PM ----------
I personally enjoy using "systemuituner" app immersive mode "full" with this module. Its a really good combo!!! ?

Systemuituner is just app or another Magisk module?
Posted using OnePlus 7T via Tapatalk

Riski3Run said:
Systemuituner is just app or another Magisk module?
Posted using OnePlus 7T via Tapatalk
Click to expand...
Click to collapse
App located here on Xda....

These are some example screenshots of notch killer and Systemuituner immersive mode on together.. No status bar until u touch top.
I love it.
all screen!!! ?

Dolby Atmos Equaliser 7T (HD1903) (no root needed)

I was searching for the possibility to enable EQ on 7t without root, but nothing really worked, until I found Dolby Atmos DAX2 app (originaly from Razer phone)... (you can find it on apkmirror - I cannot share links yet...) works pretty well... you can even turn it off completely... maybe someone can have a use for it too...

https://www.apkmirror.com/apk/razer...x2_2-6-0-28_r1-android-apk-download/download/

Amazing!!!
Enviado desde mi HD1900 mediante Tapatalk

ChrisFeiveel84 said:
https://www.apkmirror.com/apk/razer...x2_2-6-0-28_r1-android-apk-download/download/
Click to expand...
Click to collapse
it's worked....

Thanks! With this app I disabled Dolby Atmos and everything sounds better now lol

:good:
---------- Post added at 12:19 AM ---------- Previous post was at 12:15 AM ----------
ej8989 said:
Thanks! With this app I disabled Dolby Atmos and everything sounds better now lol
Click to expand...
Click to collapse
Wow, it's truly amazing to test the demo showed in the app in order to appreciate the difference.
So once I installed the apk, how can I set it as the default app for sound? I mean, is it just turning it on? Do I have to disable the stock Dolby Atmos app? If so, how could I do that? Thank you very much.

adripgarcia96, this app and stock atmos (in settings) are only UI apps for tuning the same core dolby audio library, which is pre-installed and default already.
However stock atmos app will be always re-applying its own settings when you plug/unplug headphones (ie change output device), so to avoid mess i suggest 2 options:
1. If you have root, you can disable stock atmos tuner service ("SoundTunerService") via MyAndroidTools app.
2. If you don't have root, don't touch stock tuner in speaker mode (use only this app) and don't touch this app (use only stock tuner) with any headphones plugged.

Embox said:
adripgarcia96, this app and stock atmos (in settings) are only UI apps for tuning the same core dolby audio library, which is pre-installed and default already.
However stock atmos app will be always re-applying its own settings when you plug/unplug headphones (ie change output device), so to avoid mess i suggest 2 options:
1. If you have root, you can disable stock atmos tuner service ("SoundTunerService") via MyAndroidTools app.
2. If you don't have root, don't touch stock tuner in speaker mode (use only this app) and don't touch this app (use only stock tuner) with any headphones plugged.
Click to expand...
Click to collapse
I disabled built in dolby thru adb and just control dolby thru the app posted in this thread. Works as I intended it to.

ej8989 said:
I disabled built in dolby thru adb and just control dolby thru the app posted in this thread. Works as I intended it to.
Click to expand...
Click to collapse
Agree, adb is the deal too.
Did you also lose separate eq profiles for devices (need manual switch)? I still lack it.

ej8989 said:
I disabled built in dolby thru adb and just control dolby thru the app posted in this thread. Works as I intended it to.
Click to expand...
Click to collapse
How to do this via adb, sorry I am noob

Works great. Thank you for sharing

Works good. Tested it.

Embox said:
Agree, adb is the deal too.
Did you also lose separate eq profiles for devices (need manual switch)? I still lack it.
Click to expand...
Click to collapse
I always manual switch. The app posted in this thread has a Quick-settings toggle.
{
"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"
}
DerDavid01 said:
How to do this via adb, sorry I am noob
Click to expand...
Click to collapse
1. Install Minimal ADB and Fastboot (CLICK HERE)
2. Enable Developer Options, then turn on USB Debugging
3. Connect phone to PC, when prompted in the phone, allow debugging
4. Type
Code:
adb shell pm disable-user --user 0 com.oneplus.sound.tuner
then press enter
5. Reboot.

ej8989 said:
I always manual switch. The app posted in this thread has a Quick-settings toggle.
1. Install Minimal ADB and Fastboot (CLICK HERE)
2. Enable Developer Options, then turn on USB Debugging
3. Connect phone to PC, when prompted in the phone, allow debugging
4. Type
Code:
adb shell pm disable-user --user 0 com.oneplus.sound.tuner
then press enter
5. Reboot.
Click to expand...
Click to collapse
Hi can you post how to reenable oneplus sound tuner, just in case?
Thank you
Never mind, to re-enable the app you need to type the following in windwos command prompt:
to re-enable built in sound tuner:
Code:
adb shell pm enable com.oneplus.sound.tuner
then reboot phone
by the way with this command you can list the currently disabled apps:
Code:
adb shell pm list packages -d

Frequencies in Hz for this 10-band EQ (both this app and stock dolby tuner):
46 220 460 840 1000 2000 3000 5000 9000 13800 (Hz)
Finally, these gains will be transformed into internal 20-band dolby EQ with frequencies:
46,141,234,328,460, 656,844,1031,1313,1688, 2250,3000,3750,4688,5813, 7125,9000,11250,13800,19688 (Hz)
The tenth band (13800 hz) tunes 19688 Hz as well. Might be useful for precise tuning

Hege said:
I was searching for the possibility to enable EQ on 7t without root, but nothing really worked, until I found Dolby Atmos DAX2 app (originaly from Razer phone)... (you can find it on apkmirror - I cannot share links yet...) works pretty well... you can even turn it off completely... maybe someone can have a use for it too...
Click to expand...
Click to collapse
It works well. Thanks

Can someone share thier settings in Dolby app which they feel really makes improvement on loudspeakers

Is it not getting switched off when you change songs. For me everytime I change songs this get switched off.

Why you install this app if oxygen has an internal dolby equalizer? Is the same...

Ivixmax said:
Why you install this app if oxygen has an internal dolby equalizer? Is the same...
Click to expand...
Click to collapse
No it's not.. this app is working better and you can feel the difference only by tapping on it's dedicated qs tile, when you're playing music or videos