[Release Candidate] Dolby Atmos™

Search This thread


Recognized Developer
Sep 18, 2014
It did not work placing it there. You were referring to the install.sh file in your module correct?
No, the manifest.xml file

---------- Post added at 02:10 AM ---------- Previous post was at 02:10 AM ----------

Not sure what the side effects of removing broadcast radio line, but I guess it related with wifi and cellular data?
If so, I noticed no problems on my OP3 after removing the line.
Just tried activating hotspot, and it works
Interesting. Can you post a full logcat and dmesg?


Senior Member
Apr 8, 2013
Follow This

First you need to install Viper4Android From MagiskApp Then Reboot After That Install Dolby Atmos Here ( https://www.androidfilehost.com/?fid=746010030569962641 ) And Then Reboot Again Lastly Install AML ( Audio Modification Libary ) From MagiskApp , Reboot . And Done .

Handsomely Work On Mi A1 Oreo 8.1 Custom Rom XD , Dont Forget To Click The Thanks Button Hehehe

Hi mate,
sorry if I rise up old post of yours.

I followed your method for my A1.
I can enable Viper4Android, but i can't launch dolby atmos. it's always forced closed. did you experience the same?

btw, the sound quality is much improved tho.

I finally can make both dolby atmos and V4A works! yeay!
after following your instructions, and reboot, I realized that my AML is not activated. So I reinstall it, and then everything works!

Last edited:


Oct 20, 2015
I've a 3t running OOS ob 24. I've installed viper atmos port and aml. Sometimes I can't play music from local files streaming services works fine (Spotify/play music). Reboot fielxes the issue not convenient thought.


Senior Member
Nov 16, 2007
No, I've never been able to boot with DU ROM. I was functional early in the previous thread on stock OOS 5.0.0. I just tried the latest Unity build and it bootlooped with basically the same errors, but yours added that audioserver had died:

1. Make backup
2. Go to edit /system/vendor/manifest.xml
3. Remove this part:

4. Reboot, install DA and enjoy ;)
It worked! I removed those lines and flash the last standard version and voilá, i have dolby installed running OxigenOS Beta 7.
Thx! :)

Sent from my OnePlus 5 using XDA Labs


Senior Member
Feb 26, 2013
I just flashed DA from this thread and I'm not satisfied with the audio quality. Ahrion's DA port sounds far superior to this one. I am NOT trying to demean the hard work put up by the dev. Kudos to him. He did an amazing job of porting DA to Oreo devices. It's just that the sound feels bloated and the awesomeness of DA isn't just there. And another problem is that If I flash it along with the V4A, although DA works, V4A doesn't process any audio. AML didn't do the trick. And in some cases I have faced problem like losing mobile network (No SIM card detected) after flashing DA. That's quite weird.

Device: Galaxy S6 Duos. Tested on Nexus OS, AOSP Extended and RR oreo. All being official 8.1.0 builds.
  • Like
Reactions: MArtyChubbs


Senior Member
Jan 7, 2016
I just flashed DA from this thread and I'm not satisfied with the audio quality. Ahrion's DA port sounds far superior to this one. I am NOT trying to demean the hard work put up by the dev. Kudos to him. He did an amazing job of porting DA to Oreo devices. It's just that the sound feels bloated and the awesomeness of DA isn't just there. And another problem is that If I flash it along with the V4A, although DA works, V4A doesn't process any audio. AML didn't do the trick. And in some cases I have faced problem like losing mobile network (No SIM card detected) after flashing DA. That's quite weird.

Device: Galaxy S6 Duos. Tested on Nexus OS, AOSP Extended and RR oreo. All being official 8.1.0 builds.
Try the dax-default file attached. Place it in the system/Dolby/etc folder in the zip and rename it after deleting the original one and reflash the mod.
If still too loud and overeffected, bring all the EQ bands to -12 db.


  • dax-default_edited.xml
    143.3 KB · Views: 18
  • Like
Reactions: salehin4070


Senior Member
1. Make backup
2. Go to edit /system/vendor/manifest.xml
3. Remove this part:
<hal format="hidl">
4. Reboot, install DA and enjoy ;)

Finally i have it working on my OnePlus 5 with LineageOS 15.1!
Thanks man! no strange behaviour whatsoever


Recognized Developer
Sep 18, 2014
Last edited:
  • Like
Reactions: giveme13s


Senior Member
Sep 17, 2007
Try this one: https://www.androidfilehost.com/?fid=818070582850506017
I didn't see anything unusual related to the removed section in the logs so who knows :)
Tried flashing it.
Failed flashing at first attempt, error message was "Please install Magisk v15.3+"
... I use Magisk ver 16.3....
So I edited file "update-binary" and commented out following lines:
#if [ ! -d $MAGISKBIN ] && [ ! -d /data/magisk ]; then
  #ui_print "- System install detected"
#elif [ ! -f $MAGISKBIN/util_functions.sh ]; then
  #[ ! -z $MAGISK_VER_CODE -a $MAGISK_VER_CODE -ge $MINMAGISK ] || require_new_magisk
  #ui_print "- Magisk install detected"
Tried flashing for 2nd attempt, succeeded :)
No boot loop and DA works


Oct 20, 2015


  • Screenshot_20180406-195657.png
    230.9 KB · Views: 738


Recognized Developer
Sep 18, 2014
Tried flashing it.
Failed flashing at first attempt, error message was "Please install Magisk v15.3+"
... I use Magisk ver 16.3....
So I edited file "update-binary" and commented out following lines:
#if [ ! -d $MAGISKBIN ] && [ ! -d /data/magisk ]; then
  #ui_print "- System install detected"
#elif [ ! -f $MAGISKBIN/util_functions.sh ]; then
  #[ ! -z $MAGISK_VER_CODE -a $MAGISK_VER_CODE -ge $MINMAGISK ] || require_new_magisk
  #ui_print "- Magisk install detected"
Tried flashing for 2nd attempt, succeeded :)
No boot loop and DA works

I see what happened, this one should have that fixed: https://www.androidfilehost.com/?fid=962187416754473447
  • Like
Reactions: giveme13s


Recognized Developer
Sep 18, 2014
@Zackptg5 do you know why this doesn't work on note 8

Can't say for certain but probably due to heavily modified audio components by samsung being incompatible with parts (likely the audioserver) of this mod. Not much you can do about it unfortunately

@guitardedhero, @Zackptg5 . Please tell me why when i switch "dialogue enhancer" and "bass enhancer" nothing not happening? Sound not change. It is only at me?

I don't develop the app so couldn't tell you. However both of those enhancers seem pretty subtle when I use them. I only notice them with better headphones (or it's just placebo lol)

Working as expected :good:

Sweet, so this will be the next unity build then (same as before, just reposting the link for others): https://www.androidfilehost.com/?fid=962187416754473447
  • Like
Reactions: Alex Tian8800

Top Liked Posts

  • There are no posts matching your filters.
  • 228
    Release Candidates for 9.0+ begin on page 458 and on Telegram.

    The troubleshooting guide for Release Candidates is in this post.

    updated 20200206

    YouTube™ Link!
    "Listen to the Dolby Atmos™ Difference!"

    Dolby Atmos™
    Android Oreo


    • Dolby Atmos™ Digital Signal Processer with effects and Graphic User Interface ported from the latest ZTE™ Axon 7 Android Oreo firmware intended for all Android devices on Android Oreo.

    • Dolby Atmos™ sound effects applied to media audio output supporting various media players.

    • Flexible custom recovery installation archive supporting Magisk and SuperSU installations as well as existing audio mod installations - fully supporting Enforcing SELinux Mode:

      • Multiple installation scenarios available using the included arise_parameters.prop that is automatically copied to /sdcard if not already there. When edited by the user in this /sdcard location, arise_parameters.prop can:

        • Instruct an installation directly to /system if a Magisk user prefers a /system installation over the Magisk module installation.

        • Instruct a system-less module installation using /su if a SuperSU user with the system-less SuperSU installation prefers a module installation for a variety of reasons such as insufficient /system space to accommodate a /system installation or the convenience of a persistent installation unaffected by rom updates.

    • An independent build maintained by @[B]Zackptg5[/B] fully integrated with Unity:

      • Active accommodation of existing and future Magisk modules relevant to audio modification.

      • Flashing the installation archive over a current installation results with an uninstallation of the Dolby Atmos™ Magisk module.

      • @[B]Zackptg5[/B] explains the nuances a bit further here.

    • A minimum of SDK 26 (Android 8.0) is required for installation to begin, else Exit 1 will abort the recovery installation activity.

    • A root solution or a capable kernel is required in order to automate the execution of scripts during boot to allow the appropriate sepolicy rules necessary for Dolby Atmos™ functionality while in Enforcing SELinux mode.

    • Third party audio effects and DSP's such as ViPER4Android (<--
      link to @[B]docnok63[/B]'s solution :highfive:) may require some extra effort to allow processing due to Dolby Atmos' dependency on its output_session_processing music effect.

    • Performing a backup of the /system partition in recovery is encouraged for users receiving a /system installation:

      • TWRP > Backup > Check System > Edit name, if desired > Swipe to perform backup operation

    • Confirm device requirements are met and installation results are acceptable.

    • Confirm an escape route is available in the event of unsuccessful device boot or unsatisfactory experience.

    • Confirm successful download and location of downloaded archive(s).

    • Boot to recovery > Install > *.zip > Swipe to perform installation operation > Advanced > Copy Log > Reboot

    • Updating procedure is no different unless specified otherwise.

    Additional Information:

    • Unsuccessful device boot:

      • If experiencing a bootloop...

        ! ! DO NOT GIVE UP ! !

      • Wait until at least 60 seconds have passed, hold down the device's Power button until a reboot is initiated... and then give up if a successful boot fails to occur.

    • Escape routes for unsuccessful/unsatisfactory installations:

      • Magisk Module Installation:

        • If booted, navigate to /magisk using a capable file manager application and delete /dolbyatmos before rebooting the device. If experiencing an unsuccessful device boot, boot to recovery using the appropriate hardware button combination for the device, install the Magisk Recovery Management archive attached below, and follow the given instructions to delete the Magisk module (/magisk/dolbyatmos).

      • SuperSU /system installations:

        • Restore Backup in recovery if available: TWRP > Restore > appropriate backup folder > Check System > Swipe to perform Restore operation

        • Install the currently installed rom zip in recovery without any partition wipes or install a different rom zip according to the rom developer's installation instructions.

    • Reporting bugs/failures:

      • An acceptable report will include the /sdcard/recovery.log received after the installation session before booting from recovery even if the recovery session appeared to be free from any error. An acceptable report will include relevant information/details to equip me to efficiently address the report.

    • Auditing:

      • Assessing the installation is encouraged for all users and is especially helpful when the collected information is included in reports of less than perfect experiences.

      • Dumpsys:

        • The dumpsys utility in Android can be a very valuable troubleshooting tool, especially audio output processing related issues, when targeting the audioflinger service. Recommended terminal applications include Terminal Emulator for Android and Termux.

        • In Android Terminal:
          dumpsys media.audio_flinger
          su -c dumpsys media.audio_flinger

        • The output generated upon tapping the Enter key is the information of interest and can be copied from the Terminal and pasted with a report, if necessary.

        • This output includes the list of successfully configured audio sound effect libraries and any successfully created effect-chains from one or more of those libraries when combined with the successful installation of an appropriate apk, Dolby Atmos being one of many examples.

      • Logging:

        • The log utility in Android is another valuable tool for many various purposes, including troubleshooting. This utility is most convenient when used with a logging application such as Matlog in order to utilize features such as word filtering and syntax highlighting among others.

        • Using the logging application's search feature, the user can filter the displayed log output using words or characters relevant to this Dolby Atmos™ port such as: dolby, dax, dlb, dseffect and include that relevant log output with reports, if necessary.

    • Testing:

      • The possibility of my experience being different from others' experiences is always present!

      • Those meeting the installation requirements may certainly test against various aspects stated as facts within this OP such as incompatibility with other audio effects, requirement of Permissive SELinux Mode :highfive:, etc.

    • Vulnerabilities:

      • The installation, as with any device content, is not immune to impact from existing and future installations of custom content. This custom content may remove or modify necessary content, or introduce conflicting content preventing Dolby Atmos™ from functioning as intended by this mod's installation. Security measures can block these scenarios from occuring but will typically be implemented only after the discovery of such cases of "breaking" Dolby Atmos™ functionality, in which case, the relevant vulnerability will be omitted from this particular section.

      • Vulnerability: --

        • Scenario: --



    • Code:
      [B]Standard 20180219 -[/B]
      - Expiration met for the Dolby Atmos
      Demo Video component after confirmation
      of its lack for volume support indicated a
      native "bug" and not a porting shortcoming.
      - A reduction of 67MB, uncompressed, now
      totaling 15.49MB uncompressed, without
      the Dolby Atmos Demo Video component.
      - Abandonment of the recently introduced
      libsurround_proc.so library (suspect of recent
      audio unpleasantness) from the Nokia
      6 Official Oreo build that was paired with
      that same firmware's Dolby Surround Sound
      Settings' menu as an additional apk that is
      currently still included and still in its trial
      - SUBSTANTIAL adjustments, additions, and
      improvements to every script - installation
      and boot scripts, the most comprehensive
      update for this shell component thus far.
      [B]Unity 20180220 -[/B]
      - Added the debloated apk.

      [B]Standard 20180218 -[/B]
      - Updated installation script and
      functions with Magisk (1540).
      - Adjustments to boot scripts.
      - Added surround processing library
      from the native CustDolbySettings.apk
      firmware (Nokia 6 Official Oreo).
      - Temporary icon change for
      [B]Unity 20180218 -[/B]
      - Reworked bootmode support for devices
      with separate vendor partitions, added
      dolby surround app.
      [B]Standard 20180216 -[/B]
      - Fixed a critical error in libswvlldp.so's
      effect configuration in the XML
      - Several adjustments to boot scripts.
      [B]Unity 20180216 -[/B]
      - Fix issues users with devices that use
      audio_effect.xml were having. Thanks to
      [user=7073442]@manhong2112[/user] for the patience
      and troubleshooting.
      [B]Standard 20180215 -[/B]
      - Added new CustDolbySettings.apk
      from the latest Nokia 6 official Oreo
      firmware (untested/experimental).
      - Slight change in post-fs-data.sh
      boot script.
      [B]Standard 20180214 -[/B]
      - Correction to Pixel 2/2 XL detection.
      [B]Unity 20180214 -[/B]
      - Adjustments to unique audio effects
      configuration preparation.
      [B]20180214 -[/B]
      - Minor corrections and enhancements.
      [B]20180213-2 -[/B]
      - Adjustment to SuperSU /su
      module installation.
      [B]20180213-1 -[/B]
      - Completed the incomplete service.sh
      script mistakenly thought as completed.
      [B]20180213 -[/B]
      - Extensive reworking of boot scripts
      aimed at device boot success and
      [B]20180212-1 -[/B]
      - Samsung compatibility attempt
      via the disabling of the SoundAlive
      music output_session_processing
      [B]20180212 -[/B]
      - Corrected library_migration function.
      [B]20180211-1 -[/B]
      - Testing new library migration
      [B]20180211 -[/B]
      - Accommodation for audio_effects.xml
      configurations lacking
      <postprocess></postprocess> section.
      - Adjustments to boot scripts focused
      on device boot success.
      [B]20180210 -[/B]
      - Resolved accidental omission of
      [B]20180209-3 -[/B]
      - Don't be helpful, be harmless.
      [B]20180209-2 -[/B]
      - Corrections and adjustments to
      /system installations.
      - Automatic audioserver restoration
      during all system-less installations.
      [B]20180209-1 -[/B]
      - Correction to audio_effects.xml
      [B]20180209 -[/B]
      - Correction to typo preventing
      audio_effects.xml manipulation.
      [B]20180208-4 -[/B]
      - Minor adjustments and improvements.
      [B]20180208-3 -[/B]
      - ...
      [B]20180208-2 -[/B]
      - meh.
      [B]20180208-1 -[/B]
      - More than enough changes to
      likely introduce new errors.
      [B]20180208 -[/B]
      - Script corrections and enhancements.
      [B]20180207-2 -[/B]
      - Does it even matter at this.point??
      [B]20180207-1 -[/B]
      - Like it even makes a difference...
      [B]20180207 -[/B]
      - Various corrections and adjustments.
      [B]20180206-2 -[/B]
      - Redundant changelog is redundant.
      [B]20180206-1 -[/B]
      - Further error corrections.
      [B]20180206 -[/B]
      - Various error corrections.
      [B]20180205-1 -[/B]
      - Various error corrections.
      [B]20180205 -[/B]
      - Initial release integrating Unity
      installation and scripts courtesy
      of @ahrion and @Zackptg5.
      [B]20180202 -[/B]
      - Corrected a critical error recently
      introduced by "reckless thumbing"
      to the audio effects configuration
      operation for /system installations.
      - The Magisk binary's --mountimg
      function is once again used for
      mounting the Magisk image volume
      if the standard mount attempt is
      - Various enhancements.
      [B]20180201 -[/B]
      - Boot scripts completely
      - Bundled Magisk's 1531 binary in
      an attempt to access its functions
      during the recovery session instead
      of the existing binary for certain
      Magisk-specific operations.
      - Various corrections and refinements.
      [B]20180131-1 -[/B]
      - Minor adjustments.
      [B]20180131 -[/B]
      - Numerous corrections and refinements.
      - Enforcing SELinux Mode fully supported.
      - No longer affects SELinux mode in any way.
      [B]20180129-1 -[/B]
      - Minor corrections.
      [B]20180129 -[/B]
      - Numerous changes/improvements
      to all scripts.
      [B]20180127 -[/B]
      - Numerous changes/improvements
      across the entire archive.
      [B]20180126-6 -[/B]
      - Slight adjustment to scripts.
      [B]20180126-5 -[/B]
      - Boot scripts restructuring and
      enhancements targeting successful
      device boot and additional
      [B]20180126-4 -[/B]
      - Does it even matter at this point??
      [B]20180126-3 -[/B]
      - Reverted the recent option
      introducing unsuccessful results.
      [B]20180126-2 -[/B]
      - Redundant changelog is
      [B]20180126-1 -[/B]
      - Corrected, yet another, error
      introduced with the latest
      option that would only affect those
      installations utilizing this option.
      [B]20180126 -[/B]
      - Various corrections of errors
      introduced with the changes to
      accommodate the recently added
      [B]20180125-3 -[/B]
      - Corrected duplicate
      output_session_processing entry
      for module installations.
      [B]20180125-2 -[/B]
      - Added option to install custom
      dolbyserver instead of native
      audioserver for those unable to
      successfully boot with the native Axon 7
      Oreo /bin/audioserver. (Refer to
      arise_parameters.prop for full details)
      - Updated arise_parameters.prop.
      [B]20180125-1 -[/B]
      - Updated apk internal filesystem
      and information (Does NOT affect
      installation success-rate).
      [B]20180125 -[/B]
      - Adjustment to Xposed detection.
      [B]20180124-1 -[/B]
      - Unique atmos library and effect
      UUID to accommodate native Dolby
      [B]20180124 -[/B]
      - Adjustment to Magisk variables with
      existing audio effects configurations.
      [B]20180122-2 -[/B]
      - Mount magisk.img with Magisk's
      util_functions.sh if initial mount
      attempt was unsuccessful.
      [B]20180122-1 -[/B]
      - Correction to audio effects
      configuration manipulation.
      [B]20180122 -[/B]
      - Correction of introduced errors.
      [B]20180121 -[/B]
      - Extensive adjustments to installation script.
      - Addressed Pixel, Samsung, /su module, and
      general installations.
      - Removed previously bundled music player.
      - Beginning of DolbyAtmos.apk customization
      and experimentation.
      [B]20180120-1 -[/B]
      - Conservative shift of boot scripts.
      [B]20180120 -[/B]
      - Various and discriminate installation
      and boot script adjustments.
      [B]20180119-3 -[/B]
      - Third time's the charm??
      [B]20180119-2 -[/B]
      - Yet another correction to boot script.
      [B]20180119-1 -[/B]
      - Correction to boot script.
      [B]20180119 -[/B]
      - Extensive adjustments to systemless
      module creation and boot script.
      - Removed build properties.
      - Default installations intended to
      accommodate HTC devices.
      [B]20180117-1 -[/B]
      - Correction to
      [B]20180117 -[/B]
      - Various script corrections.
      - Recovery Management zip now supports
      SuperSU's /data/su.img and is now included
      in the Dolby Atmos zip for convenient access.
      [B]20180114-4 -[/B]
      - More script corrections.
      [B]20180114-3 -[/B]
      - Script error correction.
      [B]20180114-2 -[/B]
      - Further script changes.
      [B]20180114-1 -[/B]
      - Adjustment to supported .prop detection.
      - Removed experimental /*_contexts patches.
      - Various script changes.
      [B]20180114 -[/B]
      - Corrected Magisk module installation.
      - Added systemless installation option
      for SuperSU users (/su/dolbyatmos).
      - Updated /sdcard/arise_parameters.prop
      (will overwrite the no longer supported .prop).
      - Various script changes.
      [B]20180112-2 -[/B]
      - Added missing setprop section
      to script in /system installations.
      [B]20180112-1 -[/B]
      - Added two library dependencies
      to accommodate devices without
      either library. (@Zackptg5)
      - Adjustment to vendor partition
      audio effects configuration
      detection. (@Zackptg5)
      - Added Xposed alert describing
      potential conflict and potential resolution
      of Dolby Atmos functionality. (@MMWolverine)
      - Added /system free space detection,
      resolution methods, and installation exit
      for /system installations destined to fail due
      to insufficient space to accommodate the
      Dolby Atmos system.
      Massive shout out to the many users
      responsible for the current success rate
      enjoyed by this Dolby Atmos Oreo solution!
      [B]20180112 -[/B]
      - Updated Magisk module.prop to 1530
      [B]Initial Release -[/B]

    Release Candidate 1:
    • 32-bit and 64-bit installations from a single zip.

    • Axon 9 Pro apk and effect library used in both 32-bit and 64-bit installations to provide the most consistent experience for all users.

    • This allows 32-bit users to avoid the 3dB GEQ boost limit as well as any license check by Lenovo.

    • Removed much of the verbose messaging during the installation.

    • Refinements and minor corrections to every single script.

    • Install ACDB 0.45 if not already installed.

    • Uninstall any existing Dolby Atmos™ installation and reboot.

    • Install RC1 in Magisk Manager or in custom recovery.

    • Save installation log before rebooting.

    • Apply your best effort to find a failure or force a failure of functionality by any reasonable means - deleting/overwriting something will not count, obviously.
    God, I miss him...
    Android Oreo Database

    /system/bin/audioserver <-- Drive link

    • Purpose and Contribution:

      • Introduced with Android Nougat, audioserver appears as its own binary after years of being a component of /system/bin/mediaserver in all Android firmware.
      • Introduced with Android Nougat, vendor provided Dolby Atmos™ software audio solutions appear with a new media.dolby_memoryservice that is compiled into /system/bin/audioserver as well as a unique system library typically appearing as /system/vendor/lib/libdlbmemoryservice.so.
      • These new components are crucial to a functional Dolby Atmos software solution and there is currently no known way of achieving any amount of success without them.
      • While porting the very first Nougat Dolby Atmos system available, courtesy of ZTE™ Axon 7’s initial Nougat firmware image, I discovered this implementation and a functional port was finally available.
      • However, using a Nexus 6 at the time, I was able to evade nearly all bootloop scenarios with much of what would cause a bootloop scenario for others.
      • It took no time to determine that this new media.dolby_memoryservice component was going to be a challenge in achieving a viable Dolby Atmos Nougat port.
      • To begin, results were determined: Successful device boot or Unsuccessful device boot.
      • Stock firmware seemed to fare much better than custom firmware, even for just a single device.
      • A pattern began to emerge for me when focusing only on the audioserver binary: Stock firmware had an audioserver file size range (21.50KB-21.53KB) and Custom firmware had an audioserver file size range of its own (21.58KB-21.60KB).
      • Not a significant difference, unless you were looking for a difference.
      • This assessment presented an effective predictibility of an installation scenario's success and failure with nearly 100% accuracy (nearly only because every possible scenario is not documented).
      • This audioserver database is intended for those that have determined a single scenario as successful or as unsuccessful due to the native audioserver binary in their device’s rom being overwritten or symlinked over with the audioserver native to the ZTE™ Axon 7 Oreo firmware AND NOT A RESULT OF ANY OTHER FILE OR SCRIPT OPERATION!!
      • Simply, those with success have the easier path requiring nearly no effort other than uploading the native audioserver from their firmware along with the firmware build.prop to the WIN audioserver folder.
      • Those contributing to the FAIL audioserver folder with the native audioserver along with the firmware build.prop will only be able to do so after some personal testing to ensure the audioserver switching is the exclusive cause of an unsuccessful device boot after flashing the Dolby Atmos installation archive in recovery.

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone