Related
THIS IS AN OLD THREAD
Stable releases have moved to the new thread here:
http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
-------------------------------------------------------------
SuperSU is the Superuser access management tool of the future
!!! SuperSU requires a rooted device !!!
SuperSU allows for advanced management of Superuser access rights for all the apps on your device that need root. SuperSU has been built from the ground up to counter a number of problems with other Superuser access management tools.
Features include:
- Superuser access prompt
- Superuser access logging
- Superuser access notifications
- Per-app notification configuration
- Temporary unroot
- Deep process detection (no more unknowns)
- Works in recovery (no more segfaulting)
- Works when Android isn't properly booted
- Works with non-standard shell locations
- Always runs in ghost mode
- Wake on prompt
- Convert to /system app
- Complete unroot
- Backup script to survive CyanogenMod nightlies
- Icon selectable from 5 options + invisible
- Theme selectable from 4 options
- Launch from dialer: *#*#1234#*#* or *#*#7873778#*#* (*#*#SUPERSU#*#*)
NOTE: Not all phones take both codes. On some phones you need to use single *# instead of double *#*#
The Pro version additionally offers:
- OTA survival mode (no guarantees)
- Full color-coded command content logging (input/output/error)
- Per-app logging configuration
- Per-app user override
- Grant/deny root to an app for a set amount of time
- PIN protection
- Per-app PIN protection
- Adjust auto-deny countdown
PROTIP:
For extra performance, disable notifications. Logging does not impact performance much.
Redistribution
Yes, you are allowed to embed the (free, non-Pro) SuperSU apk and su binaries in your own custom ROMs ! As is standard (and done by the attached ZIP), normal is to use /system/app/Superuser.apk for the apk and /system/xbin/su for the binary.
Want to help translate ?
See SuperSU project on GetLocalization ! http://www.getlocalization.com/supersu/
Download:
SuperSU on Google Play (free)
SuperSU *Pro* on Google Play (Pro/donate addon, requires free version)
TWRP / FlashFire installable ZIP:
Stable: http://download.chainfire.eu/supersu-stable
Beta: http://download.chainfire.eu/supersu-beta
Latest: http://download.chainfire.eu/supersu
Note that if you are already rooted, installing through Play is by far the easiest way to install SuperSU !
Issues installing / updating binaries ?
There's a thread for that: http://forum.xda-developers.com/apps/supersu/support-update-failures-t2907365
Education
Want to learn how to use "su" correctly from your own apps ? How-To SU !
ROM Developers
Feel free to include the (free version, unmodified) SuperSU APK in your ROMs. You do not need to ask me for permission to include it.
It would be nice if you would include minor advertisement in your ROM description, such as "Powered by SuperSU", or "Please support SuperSU". This is not a requirement, merely a request.
Who, what, why ?!
As you may know, I make a lot of apps that use or require root. I also release rooted kernels. I run into a lot of issues with existing Superuser tools. More importantly, a lot of my users run into these issues as well and then email me about it. So I decided to do something about this. Doesn't mean these were problems you have ever seen, or will ever see.
And thus, I have written - pretty much from scratch - SuperSU. I have taken the su binary command line parameter parsing from Superuser, to make sure that is compatible. Aside from that, it is completely rewritten, because how I wanted to do a number of things was incompatible with the existing codebase.
This is not a stab at ChainsDD, or his skills. He has done great work and will no doubt continue to do so, however, I felt the need for some of these changes, and thus made them. This is an early release, so I expect there will be some unforseen issues somewhere.
From now on, all CF-Root and Mobile ODIN Pro (EverRoot) releases will be built around SuperSU.
Please note that SuperSU is not hardened-security-tested or reviewed, and may be exploitable (... as may other solutions ...).
Changelogs
Changelogs continued from the previous post ...
26.12.2015 - v2.65
- (systemless) Add /su/xbin to su.img and PATH
- ZIP: Fixed force close issue when custom boot image is used
- ZIP: Reworked remounting (prevents bugged write to r/o /system on flo)
- ZIP: Added warning that first reboot may take a few minutes/loops
20.12.2015 - v2.64 - BETA
- (systemless) Detect more boot image partition names
- (systemless) Blank partitions before writing to them
- (systemless) Ask to restore boot and recovery images on full unroot
- (systemless) Implement "uninstall competing superuser apps"
- (systemless) Samsung: prevent "KERNEL IS NOT SEANDROID ENFORCING" warning
- (systemless) Cleanup system install properly if present, fixes a number of possible bootloops
- ZIP: 6.0+: Detect firmwares that can reload sepolicy from /data and use system-based root on these ("allow init kernel:security { load_policy }")
- supolicy: Additional SELinux patches for M (reduced logging only)
- Update translations
10.12.2015 - v2.62 - BETA
- (systemless) Do not attempt to patch fstab symlinks
- (systemless) Implement feature to en/disable Superuser
- (systemless) Poor man's overlay on /system/xbin for compatibility reasons (hopefully temporary) [BINDSYSTEMXBIN]
- (systemless) ZIP: Add reading setup variables from /system/.supersu and /data/.supersu
- (systemless) ZIP: Add option to patch /system to rw in fstab [FSTABSYSTEMRW]
- (systemless) ZIP: Added call to custom patcher script, if any (/data/custom_boot_image_patch.sh)
-2 (systemless) ZIP: Fix calling wrong script name for custom patcher script
-2 (systemless) ZIP: Improve APK overwrite
-3 (systemless) ZIP: Do not move backups from /cache to /data, just copy them
07.12.2015 - v2.61 - BETA
- (systemless) Fix kernel partition detection for some Intel devices
- (systemless) Added warning not to allow TWRP to install its own SuperSU version
- (systemless) Wipe /data/security/ on flash
- (systemless) Simplified kernel partition detection
- (systemless) Added /system cleanup if needed, /data cleanup always
- (systemless) Fix fstab verity removal for devices that do not list partition in the option
- Full unroot: set partition read/write before writing to it
- ZIP: Silence many error message writing to TWRP's recovery log
- ZIP: Added more documentation to the script
05.12.2015 - v2.60 - BETA
- (systemless) Fixed ZIP installer breaking Pro
- (systemless) Added automatic kernel patcher to ZIP installer
- (systemless) Added sukernel tool
- (systemless) Bind mount /system/[x]bin/su to /su/bin/su
- (systemless) Fixed cleanup options in settings
- (systemless) Now available for 5.1.x (by default for Samsung only, full unroot/reflash system before update)
- Made reworked context switching available to 5.1.x (testing, should come to more APIs soon)
- Fixed recursive mount issue on Samsung 5.1.x that could ultimately lead to root being lost
30.10.2015 - v2.56 - BETA
- Support for systemless su binary locations
10.10.2015 - v2.52 - BETA
- Adjusted more policies for M
- Fixed an issue with reading logs on M
- Reworked --context/--cn parameter (testing, currently M only, should eventually move to all APIs)
08.10.2015 - v2.51 - BETA
- Add support for x86 PIE binaries
06.10.2015 - v2.50 - BETA
- Fixed tapjacking protection not working < 4.4.3 (AOSP issue 54193)
- Updated libsupol headers
- armv5/x86 binaries now NDK built instead of AOSP
- supolicy adjustments for Samsung 5.1.1
- Removed extra donation feature
- Toybox support
28.04.2015 - v2.49 - BETA
- Fixed some audits on 5.x (found on S6)
02.04.2015 - v2.48 - BETA
- TWRP/M9 issue fixed
02.04.2015 - v2.47 - BETA
- Improved King removal
- Detect 'OEM' (bad) TWRP
13.02.2015 - v2.46
- Backupscript adjustments
- Remove more alternate su binaries
20.01.2015 - v2.45
- Installer adjustments
- Backupscript adjustments
- Updated language files
07.01.2015 - v2.44 - BETA
- su.d scripts no longer use logwrapper, this can prevent some scripts from running
- supolicy timing adjustment (MotoG 2014 fix?)
03.01.2015 - v2.43 - BETA
- Backuptool script adjusted again
- Fix native NPE in username resolution
- Fix some update failures when coming from a different root tool on 5.0
- LD_PRELOAD sanitization
- (C) 2015
21.12.2014 - v2.42 - BETA
- Fix rootfs remount issue that could lead to strange behavior on (for example) HTC M7 and M8
- Backuptool support for /system/su.d
- Some policy adjustments for CM12
17.12.2014 - v2.41 - BETA
- Improved dumpstate work-around
- Improved killing dead per-uid daemonsu
- Backuptool support for Lollipop
16.12.2014 - v2.40
- /system/su.d now executed for all daemonsu firmwares
- Adjust sysinit context if present
- Updated language files
10.12.2014 - v2.39 - BETA
- Skip reverse connection watch on firmwares using supolicy (SGS5 5.0 fix?)
- Fixed daemonsu not starting on truly permissive Lollipop
- Adjust daemonisation code
- Small L theme adjustments
- Updated language files
07.12.2014 - v2.38 - BETA
- Watch for and kill dead per-uid daemonsu (SGS5 5.0 fix?)
- Fix crash on clearing logs on 2.x
- Fix possible NPE on open
- Fix possible NPE on en/disable root
- Moved additional donations to the bottom of settings
- Small L theme adjustments
01.12.2014 - v2.37 (Gingerbread? )
- Binary update requires less space on /system
- Updated language files
28.11.2014 - v2.36
- Use material theme on 5.0 when launched from settings
- Fixed crash on 2.x and 3.x devices
- Fixed TWRP installer issue for 4.2
- Updated language files
27.11.2014 - v2.35 - RELEASE NOTES
- Fix mount namespace separation somtimes being disabled
- Donations via IAPs (user request)
25.11.2014 - v2.30 - BETA - RELEASE NOTES
- Layout adjustments for Nexus Player
- Installer adjustments for latest TWRPs
- Hiding icon now also hides from Leanback launcher
- Icon replacements
- ACCESS_SUPERUSER permission is gone
20.11.2014 - v2.27 - BETA - RELEASE NOTES
- 3rd generation app_process hijack
19.11.2014 - v2.24, v2.25 - BETA - RELEASE NOTES
- Updated policy patches
17.11.2014 - v2.23 - BETA - RELEASE NOTES
- Add PID tracer (--id) option to su
- Updated policy patches
16.11.2014 - v2.22 - BETA
- Fixed double refresh icon in logs in Holo theme (one should be delete)
- Add option to stop asking about disabling KNOX
- Updated backuptool script
- Disallow root access via daemonsu
- Updated policy patches
- Added kernel patching support
- API >= 19: run /system/su.d/* after SELinux policy patched
- Hide OTA survival option on L, not currently supported
- Adjust app title based on Pro status
- Fix disconnected daemonsu process gobbling up CPU
- More L theming
05.11.2014 - v2.19 - BETA
- Fixed various issues with 64-bit
- Fixed various issues with 5.0 path handling
- Fixed notifications sometimes showing up, even when disabled
- More L theming
04.11.2014 - v2.18 - intermediate Nexus9 version only
- Fixed various issues with 64-bit
- Apps fragment logs area hidden and refreshed automatically
- More L theming
31.10.2014 - v2.17 - BETA - RELEASE NOTES
- Fix inifinite loop caused by forced language change
- Fix SIGSEGV in daemonsu on sugote close with non-pty STDIN
- Clear app's data directories after full uninstall - https://code.google.com/p/android-developer-preview/issues/detail?id=531
- supolicy now linked dynamically
- setprop supolicy.loaded 1, and execute /system/xbin/supolicy_post.sh after supolicy runs at system boot
- Allow SuperSU GUI to be used without an up-to-date binary
- More L theming
25.10.2014 - v2.16 stable-ish
- Fix UID based grants being forgotten on reboot
- Fix display names of some edge cases (excluding in logs), and prevent these from being forgotten on reboot
- Various theme options added
- Added some basic material theming for L (no backport to 4.x), now default
- Automatic restart app if theme changed
- Automatically restart app if language is changed
- Fixed multilanguage support on L
23.10.2014 - v2.15 - BETA
- Fix sugote crash (NDK builds only) (cause for endless loading on apps/logs tab)
- Fix binary detection if switched from enforcing to permissive after boot
- Fix supolicy requirement < 19, not used there (yet)
15.10.2014 - v2.14
- Moved up PIE, MIPS and ARMV7 support from 4.1+ to 4.2+, fixes installer issues on 4.1 with OTA survival enabled
(fixes a number of binary update issues)
10.10.2014 - v2.13 - RELEASE NOTES
- Improved support for Android TV (adjusted icon, disable some features, use device default theme by default, etc)
- Updated language files
05.10.2014 - v2.12 - BETA
- Parse UID names to numbers manually if the system fails to do it
- Fix system user not gaining root even if "trust system user" enabled
- Transition to init context if started in init_shell context (if possible)
- Adjust boot sequence for encrypted devices
- Support MCS for -cn/--context switch
- Silence a larger number of audits on latest AOSP/L
- Many small changes to fix support for latest AOSP/L
- Secondary users are no longer able to change trust system or respect CM settings
25.09.2014 - v2.11 - BETA
- Fixed several errors in the binary updater related to both SELinux and 64-bit binaries
- Added experimental supolicy binary
24.09.2014 - v2.10 - BETA
- Fix root access being forgotten for apps interested in overlay hide notifications
- Check for removed apps at boot, and forget their settings if re-authentication is enabled
- Amazon Appstore support
- Updated language files
19.09.2014 - v2.09 - BETA
- Remove APK restriction to install to ARM and X86 only (issue for MIPS)
- Adjust recovery binary installer (some commands may have failed in 2.08)
- Notify interested apps (with root granted) when overlays need to be hidden
12.09.2014 - v2.08 - BETA
- Transition to init context if started in kernel context
- Experimental builds for armeabi-v7a, arm64-v8a, x86-64, mips, mips64
- Fixed erroneous fd close that could cause su session freezes
08.09.2014 - v2.06 - BETA
- Fixed occasional freezes and wrong exit code in sugote
02.09.2014 - v2.05 - BETA
- Remove busybox dependency in TWRP/CWM binary updater
- Fixed missing sugote-mksh in backupscript
- Fixed install script wiping out SuperSU Pro
- Added option to disable mount namespace separation
19.08.2014 - v2.04 - BETA
- Fix bug where grant as default access still showed a prompt
- Added reboot button in dialog after binary update
- Added tapjacking protection - may cause issues with screen dimming apps!
- Added removing Team Venom SU
- Added new dalvik-cache paths to clear on package maintenance
07.08.2014 - v2.03 - BETA
- Fix exitcode sometimes being wrong when full content logging is enabled
- Fix automatic OTA survival
27.07.2014 - v2.02 - RELEASE NOTES
- Fix internal zygote crashes on L preview
- Fix issues with L preview when SELinux set to permissive
- Fix un/reinstall of apps causing a UID mismatch, causing auto-deny
- Added notification telling user when binary needs to be updated
- Updated language files
30.06.2014 - v2.01 - RELEASE NOTES
- Update normal, TWRP/CWM, and CF-Auto-Root installers for changes in "L" preview (no binary update)
18.06.2014 - v2.00
(includes all v1.98 and v1.99r1/2/3/4/5 changelogs)
- Fixed issue in CWM/TWRP binary updater
- Update backuptool script for sugote
- Fixed binary detection issue on 4.2.2 and older
- Fixed context switch issue that could prevent confirmation popups from showing
- Fixed some installer issues
- Fixed an in-app update issue
- Further updates for new AOSP changes
- Fix prompt dialog timer display
- Prevent prompt dialog closing when tapping outside window
- Requests are automatically denied after 10 seconds if the screen is not unlocked
- Fixed property access on 4.2.2 and older
- Fixed busybox-related version detection issue (busybox symlinking FTL)
- Fixed occasional automatic refresh of displayed logs not happening
- Added toast display of silently denied apps during screen-off (notifications enabled, HoneyComb+)
- Fixed case where u:r:system_server:s0 context did not work (sugote-mksh added)
- Tapping outside of popup dialogs no longer closes them
- Fixed boot complete detection
- Default for respect CM root settings is now false
- Updated language files
18.05.2014 - v1.97 - RELEASE NOTES
- Massive implementation changes for next version of Android (devs: see How-To SU update and G+ post)
- Permissive SELinux installs now also use non-system mksh by default
- Fixed current working directory sometimes not being copied
- Fixed rare issue that could lead to high CPU use
- Fixed a few binary update failure causes
- Some special cases of failed binary update are now auto-corrected at boot
- Hardcode shell commands to toolbox instead of symlinks
- Updated language files
27.03.2014 - v1.94
- Fix FC for latest Note2 and S5 firmwares
06.02.2014 - v1.93 - RELEASE NOTES
- Add --mount-master option to su binary
- Fix for am crash (no GUI popups) when daemonsu started from an exceptionally early init.d
- Improved terminal support (changing dimensions)
- Remove daemonsu STDOUT/STDERR noise
- Cleaned custom process names
- Updated language files
20.01.2014 - v1.91
- New -cn/--context parameter for su binary (devs: see How-To SU update)
- Handle mksh being switched out for sh
- Daemon forces new session immediately at launch (moved up)
- Fixed reading dynamic properties on 4.4 (update ASAP if 4.4 user)
- Fixed issue where root wasn't granted on CM
- Updated language files
10.01.2014 - v1.89 (non-Play)
- Add support for Samsung 4.4
- Update copyright notices to 2014
17.12.2013 - v1.86
- Fixed non-priv root on some SELinux/Enforcing devices
- Fixed crash on credit display on older devices
- Updated language files
15.12.2013 - v1.85
- Fix su to non-root user on 4.3+
- Fix su permission reset on 4.4 (will not be an issue until Samsung comes out with stock 4.4 ROMs)
- Fix am crash due to external storage not being defined
- App now offers to install backup script if ROM supports it
- Expand trust system setting to include all higher-than-shell users
- Added credits display
- Completely removed nag capability
- Lots of code changes
26.11.2013 - v1.80
- Fixed x86 breakage
- Workaround x86 (bionic) credential checking failure
- Fixed ZIP oddities that may break installation
- Binary now denies root if PIN code set previously but GUI not present
- Su during boot behavior is now configurable (allow if no GUI installed)
- Renamed temporary internal shell
- Added question to disable KNOX popups if present
- Added option to enforce ACCESS_SUPERUSER permission
- Fixed some devices losing root
20.11.2013 - v1.75
- Added xxxhdpi icons (if available)
- Fixed issues with sd-ext based ROMs
- Updated language files
17.11.2013 - v1.72 BETA
- Fixed OTA survival 4.3 --> 4.4
- Fixed unresponsive tabs on 2.x devices
- Fixed white flicker when using dark theme
- Fixed issue with language resetting on some firmwares
- Fixed upgrading from CWM SU to SuperSU on 4.3+ without reboot
- Added mgyun root (vroot) uninstall procedure
- Added xxhdpi icons (if available)
- Stop touching .has_su_daemon
- Several dozen security hardening commits (mini-audit by Kevin Cernekee)
13.11.2013 - v1.69
- XBIN mode (some new roots need this)
- Slightly adjusted binary installer
- Backup script installation now available for all backuptool-capable ROMs
- Fixed su-ing to a non-root user not working on some 4.3+ firmwares
- Fixed BOOTCLASSPATH vulnerability (CVE-2013-6774)
- Fixed notification sanitization vulnerability (CVE-2013-6775)
- Fixed possible closed special files vulnerability
- Updated language files
10.09.2013 - v1.65
- Brought back ARMv5 compatibility
- Fixed compatibility issues with Android 2.x
- Updated language files
- ZIP: combined ARM+x86 support
05.09.2013 - v1.60
- Added SELinux+Enforcing compatibility (for new SGS4 ROMs)
- Fixed (newest) CWM versions asking you question that break root if answered wrongly
- Fixed issue with the TWRP/CWM binary installer
- Fixed 4.3 OTA survival looping
31.08.2013 - v1.55
- 4.3: Reworked OTA survival - should work properly now, and no longer causes OTA errors (also: +i removed from install-recovery)
- Daemon: client ENV is now provided to su'd calls
- Updated language files
29.07.2013 - v1.51
- Some 4.3 time-handling code caused problems on < 4.3 devices, making some root apps stop working
29.07.2013 - v1.50
- Daemon: proper storage mounts
- Daemon: per-uid mount namespace
- Daemon: another exitcode issue fix
- Daemon: adjusted reload code
- Daemon: descriptive process names
- GUI: added reboot advisory after binary update
- ARCH: Only ARMv7 and X86 are now supported, ARMv5 dropped
- ZIP: install also to install-recovery.sh and init.d
27.07.2013 - v1.45
- Daemon: fixed exitcode not always being passed from child shell to calling process
- Daemon: fixed possible credential check bypass
- GUI: now also updates install-recovery.sh
25.07.2013 - v1.43
- Daemon: code/security mini-audit by Joshua J. Drake
- Daemon: cwd is now respected
- Daemon: auto-daemon feature
- Deamon: fixed cpu spike issue
- Daemon: symlinks sdcard (temporary)
- TWRP-based update: fixed script error
- GUI: Added 4.3 update notice
- GUI: Removed full content logging global warning
- Updated language files
04.07.2013 - v1.41
- Fixed issue with TiBu in daemon mode
- Updated language files
03.07.2013 - v1.39
- Fixed full content logging with terminal apps
- Logs now use monospace fonts
- Added daemon mode for hard-to-root firmwares
15.06.2013 - v1.34
- Fixed various problems when accessibility options are enabled
- Fixed NPE in log screen
- Updated language files
07.06.2013 - v1.32
- Fixed bug in detection ACCESS_SUPERUSER permission
- Updated language files
21.05.2013 - v1.30
- Updated binary to work on some newer Samsung firmwares
- Nagging has done its job for now - disabled again
- Added backup script and CWM SU files to full unroot file removal
- Added option to remove other superuser apps
- Updated languages files
03.03.2013 - v1.25
- Fixed permission display on Play
- Fixed crash on open and immediate close
- Ask again time choice is now remembered per-app
- Updated language files
28.02.2013 - v1.20
- Added basic tablet theme
- New prompt activity for >= API 14 (Android 4.0)
- Changed default theme+icon to light+emblem (you can change it back in settings, if you want)
- Fixed custom dialog box themes in light+darkactionbar theme
- Fixed issues with the light theme
- Various minor modifications to UI
- Several security improvements
- Added TWRP/CWM binary installer
- android.permission.ACCESS_SUPERUSER - detection and display (disabled by default, see settings)
- Fixed process name detection issue
- Freeloader option (I'm not sure this is staying, so enjoy it while you can)
- Internal refactoring
- Updated language files
23.02.2013 - v1.10
- Added support for x86 devices
- Added basic multi-user support
- Language files updated
20.02.2013 - v1.05
- Fixed possible issue with OTA survival
- Fixed su binary notification freeze issue when suid bit lost
- Fixed background root command freeze when suid bit lost
- Improved su binary version and root presence detection
- Added cleanup stage (detected when needed) before converting to system app, to prevent settings loss
- Language files updated
02.01.2013 - v1.04
- PIN code now survives uninstalling Pro (vuln. fix)
- Fixed pm freeze in logs/settings (USB debugging)
- Fixed various util freezes (convert to system, uninstall) (USB debugging)
- Fixed minor UI text issues
- Language files updated
31.01.2013 - v1.03
- Fixed pm crash in logs/settings
- Reduce nag frequencey to 10%
- Add NoNag APK
- Language files updated
30.01.2013 - v1.02 - NOTES ON DUMPSTATE (click)
- Fixed (another) crash on icon change on Android versions older than 4.0.3
- Launch SuperSU through secret codes: *#*#1234#*#* and *#*#7873778#*#* (*#*#SUPERSU#*#*). Not all phones take both codes. On some phones you need to use single *# instead of double *#*#
- Update su binary parameter parsing to add Google-naive style params
- Dumpstate blacklist
- Language files updated
29.01.2013 - v1.01
- Fixed crash on icon change on Android versions older than 4.0.3
- Adjusted (un)installer code to remove .odex files and remove dalvik caches
- Adjust default icon in manifest
- Dumpstate no longer goes into infinite loop (dumpstate shouldn't kill phone anymore, but this has not fixed dumpstate being triggered - workaround !)
- Language files updated
- Adjusted update ZIP to remove .odex files, overwrite OTA survival binary, remove dalvik caches
28.01.2013 - v1.00 - RELEASE NOTES (click)
- Icon now selectable from 5 options, or hide completely from launcher (see note)
- Theme now selectable from 4 options
- (Pro) Added option to grant/deny with a timer (hold grant/deny button in popup for two seconds)
- Added option to convert to system app
- Added option to trust system user without confirmation
- (Pro) Added option to adjust auto-deny countdown
- (Pro) Added option to PIN protect on a per-app base
- Added option to auto-refresh apps/logs tab
- Fixed "ask again" being forgotten
- CyanogenMod: Added to option to respect/ignore DevOptions --> Root Access setting
- CyanogenMod: Added option to install addon backup script (survive update flashes)
- Fixed 7" tablets now use (improved) large PIN panel
- Free space detection issue work-around (may fix a number of binary installation failures)
- Alternate remount method (may fix binary installation issues on Android 2.x)
- Updated su binary parameter parsing
- Updated su binary to add user-related environment variables
- Adjusted cleanup and copyright texts
- Fixed autoclose upon cleanup complete
- Faster preference text loading
- Faster settings tab fragment instantiation
- Reworked native debug logging
- Reworked shell detection, now includes /system/bin/mksh fallback
- Adjustments that may reduce problems for S-ON users
- Added nag message to non-Pro (with option to disable)
- Language files updated
...
* to start hidden SuperSU from ADB shell with root rights: am start -a android.intent.action.MAIN -n eu.chainfire.supersu/.MainActivity
04.12.2012 - v0.99
- More Android 4.2 related fixes
- Disabled text correction on labels
- Updated languages
14.11.2012 - v0.98
Preliminary update for Android 4.2's multi-user capabilities.
Only the main user can run the UI and gain root access.
Secondary user's apps will not be granted root, nor can
those users change SuperSU configuration.
This is all temporary. Proper multi-user support is being
worked on.
Note that if a non-user process (like ADB shell) needs to
prompt for root, that prompt will always appear on the
MAIN user's screen !
Click to expand...
Click to collapse
29.10.2012 - v0.97
- Fixed issue with modified AOSP su binary
- Fixed wrong translation crashing app on toast
- Fixed possible exploit (preventive)
- Modified system and shell user - no longer granted root by default
- Added "ADB shell" display
- Added warning to selecting full content logging
- Added method for apps to disable (by default only) full content logging if known to be problematic (<meta-data android:name="eu.chainfire.supersu.meta.contentlogging.problematic" android:value="true" />, see How-To SU)
- Updated languages
29.08.2012 - v0.96
- Fixed occasional issue with OTA
- Fixed possible exploit (preventive)
22.08.2012 - v0.95
- Fixed action bar icon sizes
- Fixed a few JellyBean-related issues
- Added automatic binary updated during boot if needed and possible
- New logo/icons
- Updated languages
16.07.2012 - v0.94
- Fixed possible NPE crash at startup
- Fixed possible ANR freeze at boot
- Fixed possible ANR freeze at package removal
- Fixed crash with too many logfiles (auto-empties logs!)
- Updated various internal functions to be async
- Updated chattr version (fixes some instances of root loss)
- Added "clear logs" action to actionbar in logs tab
- Updated languages
03.07.2012 - v0.93
- Fixed a possible delay issue (receiver deadlock)
- Updated languages
21.06.2012 - v0.92
- Fixed app detail spinners becoming invisible
- Fixed app detail button layout (diff. for port/land)
- Fixed log detail crash at rotate
- Fixed language override stick at display rotation
- Fixed display of languages without countries in override
- Fixed potential low space installation issue
- Fixed icon rearrange issue (except when low on space)
- Updated languages
18.06.2012 - v0.91
- Fixed root permission check (OTA survival)
- Fixed a number of possible installation failures
- Fixed language detection crash issue
- Added multilanguage support (27 languages and counting)
11.06.2012 - v0.90
- Fixed various texts
- Fixed various crash issues
- Fixed various non-response issues
- Fixed possible security issue
- PIN code now requires verification before changing
- Added title and navigation to log detail activity
07.05.2012 - v0.89
- Fixed stay-on-top issue
- Fixed possible exploit
- Improved security
23.04.2012 - v0.88
- Fixed a number of performance issues
- Added re-authentication option
- Apps now sorted alphabetically
- Voodoo OTA Root Keeper backup removed at binary install
26.03.2012 - v0.87
- Fixed an issue with several apps re-requesting root
- Fixed a number of reported crashes
- Fixed a few ANRs
26.03.2012 - v0.86
- Fixed a cleanup issue
26.03.2012 - v0.85
- Fixed issue if root is disabled during update
25.03.2012 - v0.84
- Modified OTA survival behavior - re-enable this setting if needed !
- Modified SH search order
- Modified backup shell location
- Added cleanup for reinstallation option
- Added cleanup for switching superuser app option
- Added cleanup for full unroot option
- If the APK is not installed, root is always granted
17.03.2012 - v0.83
- Fix command not visible
- Fix zombie process freeze
- Fix zombie process cleanup
- Fix -c followed by multiple parameters
- Fix high cpu load issue
- Fix STDIN closed relay
- Fix log display bug
- Fix swipe empty tabs
- Improved swipe behavior
- Added app title
- Added refresh button
14.03.2012 - v0.80
- Reversed swipe direction
- Adjusted touch response
- Adjusted request queueing
- Adjusted time counter
- Non-prompt notifications now async
- Permissions auto-removed if an app is uninstalled
12.03.2012 - v0.78
- Adjusted prompt-on-boot behavior
- Adjusted request serialization
- Added swiping between tabs
- Fixed force user setting
- Pro: fixed faulty SuperSU restored message
10.03.2012 - v0.75
- Adjustment to OTA survival (better!)
- Slight speedup in Settings
- Fixed native settings update after temp-re-root
- Clear data no longer clears PIN code
- Layout: Prompt: Grant and Deny switch positions (ICS style)
- Layout: AppDetail: Save and Cancel switched positions (ICS style)
- Layout: Added xlarge PIN layout
10.03.2012 - v0.74
- Proper command escaping
- Fixed inifinite loop
- Fixed notification broadcast (should fix all freezing issues)
09.03.2012 - v0.73
- Fixed su binary detection problem
- Fixed two FC's in settings
- Disabled some debug stuff that was left enabled in v0.72
09.03.2012 - v0.72
- Minor adjustments to install script
- Fixed issue with really old SU version detection
09.03.2012 - v0.71
- Fix permission problem due to faulty installation
- Added error message if device is not yet rooted
- Cancelling binary update now closes app
09.03.2012 - v0.70
- Initial public release
Changelogs
01.10.2017 - v2.82 - SR5 - RELEASE NOTES
- suinit: Fix (flashed) TWRP 3.1.1 compatibility on Pixel (XL)
- FBE: allow FBE devices to boot unencrypted (unless KEEPFORCEENCRYPT is set)
18.09.2017 - v2.82 - SR4 - RELEASE NOTES
- ZIP: Fix an incompatibilty with CFAR
- ZIP: Fix slot detection breaking if no /vendor present
- ZIP: If unmounting fails, retry lazily
- sukernel: Fstab patch: fix case where verify removal could break slotselect
- sukernel: Adjust system_root cpio import
- sukernel: Detect and use stock boot image backups created by other tools
- supolicy: Add some Oreo policies
- suinit: Fix boot case where bootloader unexpectedly doesn't enforce dm-verity
13.08.2017 - v2.82 - SR3 - RELEASE NOTES
- sukernel: Fix external sdcard issue on Samsung devices running custom ROMs
- launch_daemonsu: Abort if su binaries missing
- ZIP: Fix FlashFire compatibility in SBIN mode
- SBIN: Add /sbin/supersu/bin and /sbin/supersu/xbin to PATH (root shells only)
- SBIN: Fix policies for /sbin-based services
- SBIN: Fix /sbin-based symlinks not always properly resolving
- ZIP: Add support for bzip2/lz4/lzo/lzma/xz compressed kernels and ramdisks (lz4 @ 1.5.0 format)
08.08.2017 - v2.82 - SR2 - RELEASE NOTES
- ZIP: Support order-swapped /etc/recovery.fstab
- ZIP: Cope with /system being a symlink to /system_root/system
- suinit: Fix remount /system r/w issue on Pixel(XL)+OPreview
- sukernel: Fix pre-patched ramdisk detection for reduced system_root footprint
- ZIP+suinit: Fix recovery going to ramdump on Pixel(XL)
- Added "BIND SBIN" mode, mounts files in /sbin instead of /su, stores files directly in /data instead of su.img (new default for O+)
- Systemless: all file contexts are restored at boot, see /path/to/su/mount/file_contexts
09.06.2017 - v2.82 - SR1 - RELEASE NOTES
- ZIP: Detect AVB signature on input boot image, and sign output image accordingly (force with SIGNBOOTIMAGE, custom keys in /tmp/avb)
- ZIP: Samsung/7.0+: if /data is not currently encrypted, disable encryption (unless KEEPFORCEENCRYPT or REMOVEENCRYPTABLE are set)
- ZIP: Detect TWRP UI slot switch (Pixel/XL: 3.1.0-RC2+)
- ZIP: Further improve /system device detection
- ZIP: Support compiling sepolicy from split CILs
- ZIP: Kernel patch: support LZ4 compressed kernels (new format only)
- ZIP: Mount /vendor
- ZIP: Add /vendor/lib[64] to LD_LIBRARY_PATH
- ZIP: Initial Pixel+ODP2 support
- ZIP+APK: Fixes in boot partition detection
- sukernel: Allow cpio-add of 0-byte files
- sukernel: Add dtb (in-kernel only) related features
- suinit: Improve logging
- suinit: Support pre-mounting /system and /system_root (ODP2+)
- sukernel+suinit+ZIP: Reduce system_root footprint by dynamically importing entries at boot
- supolicy: Adjustments for ODP3
28.05.2017 - v2.82 - Work-In-Progress / TEST-1
- supolicy: Newer libsupol version used
- su: Fix sdk parameter not always being passed to supolicy in system mode
26.05.2017 - v2.82 - CCMT - RELEASE NOTES
- su: Fix su.d scripts running in the wrong mount context (introduced by ODP sdcardfs fix)
- CCMT: Remove Feedback screen and associated permissions
(v2.81 == v2.79 SR3 with patched version code)
24.05.2017 - v2.80 - CCMT
- CCMT: Update language files
- CCMT: Update guide screen
- CCMT: Update privacy policy screen
- CCMT: Updater: remove 4.3 and 5.0 specific upgrade messages, replace with generic; and detect if root must be manually updated
- CCMT: Add feedback screen
- CCMT: Drop support for Android 2.1 and 2.2. Minimum is now 2.3 (SDK 9, up from 7)
11.04.2017 - v2.79 - SR5 - Not publicly released
- su: Update mount namespace separation code to improve sdcardfs compatibility
- su: Fix kernel panic on ODP1/2 on 5X/6P
- su: Fix ODP1 compatibility on Pixel (XL)
- launch_daemonsu: Revert previous ODP1 work-around
- sukernel: Add option to patch out optional /data encryption (encryptable)
- suinit: cleanup /boot
- ZIP: Get boot image from fstab last-effort
- ZIP: Add REMOVEENCRYPTABLE flag to force disable encryption on newer Samsung firmwares
23.03.2017 - v2.79 - SR4 - RELEASE NOTES - ODP1/6P/5X only
- ZIP: Fix slow /dev/random on some devices, apparently freezing install at "Creating image"
- ZIP: Fix LD_LIBRARY_PATH for hex-patch execution
- supolicy: Fix applying deferred allow rules
- supolicy: Fix setting impossible XPERM causing policy corruption
- supolicy: Add policies for ODP1
- launch_daemonsu: Work-around kernel panic on ODP1 on 5X/6P. Forces service mode for ODP1 on all devices.
14.01.2017 - v2.79 - SR3 - RELEASE NOTES
- Fix erroneously deleting SuperSU's copy of app_process on 6.0 since 2.79-SR1
- GUI: Fix app_process requirement detection when supersu context used
- Fully eliminate sugote binary, no longer needed due to SELinux handling improvements in earlier versions
- Support /system/xbin/sush as default shell
- Adjust LD_PRELOAD filtering to exclude suhide's libraries
- ZIP: Motorola: default to systemless mode
03.01.2017 - v2.79 - SR2 - RELEASE NOTES
- supolicy: fix some segfaults(NPEs) in pre-7.0 sepolicy handling
- ZIP: write boot block device once instead of twice (@_alexndr)
- (c) 2017 + CCMT
22.12.2016 - v2.79 - SR1 - RELEASE NOTES
- Expand Samsung detection
- GUI: reworked portions to work with 'supersu' context on 7.0+
- GUI: fix binary update notice when superuser disabled by user in some cases
- su: reworked portions to work with 'supersu' context on 7.0+
- su/GUI: improve responsiveness when device busy on 7.0+
- sukernel: fix cpio restore failure with very short filenames
- sukernel: no longer patches file_contexts(.bin)
- sukernel: revert force seclabel (no longer needed with 'supersu' context)
- supolicy: add "create", "auditallow", "auditdeny" policy commands
- supolicy: support "*" for permission/range parameter of "allow", "deny", "auditallow", "auditdeny", "allowxperm" policy commands
- supolicy: --live/--file no longer apply default patches if custom patches are supplied
- supolicy: --sdk=X option added (required for 7.0+)
- supolicy: reworked all SELinux rules for 7.0+, run as 'supersu' context
- ZIP: Separate slotselect and system_root logic
- ZIP: Adjust system/system_root device and mount-point detection
- ZIP: Fix minor errors in documentation
- ZIP/frp: Explicitly label /su
15.12.2016 - v2.79 - CCMT
- CCMT: Change "Upgrade to Pro" button color
30.11.2016 - v2.78 - SR5 - RELEASE NOTES
- Fix shell-based scripts/services possibly not being executed on 7.x firmwares
- Add SecurityLogAgent to Samsung KNOX detection
- sukernel: force seclabel
15.11.2016 - v2.78 - SR4 - RELEASE NOTES
- sukernel: improve FBE detection
- suinit: TWRP compatibility on slot-based systems
- ZIP: TWRP compatibility on slot-based systems
03.11.2016 - v2.78 - SR3 - RELEASE NOTES
- Fix 'Full Unroot' on slot-based systems
- sukernel: replace system symlink with bind mount
- sukernel: add missing slot check for system_root import
- sukernel: fix ramdisk backup segmentation fault
- supolicy: adjust priv_app policy to be able to call su
- launch_daemonsu: adjust su.img size detection
- ZIP: improve loop device setup
- ZIP: add factory reset protection (FRP variable, default if slots used)
29.10.2016 - v2.78 - SR2 - RELEASE NOTES
- File-based-encryption support
- CCMT: Add privacy policy dialog
- CCMT: Update translation files
- su+gui: support /system_root paths
- sukernel: add kernel binary extract/replace
- sukernel: add kernel cmdline extract/replace
- sukernel: add system_root import
- sukernel: add slot-kernel patch
- sukernel: support /boot paths
- suinit: new binary component
- launch_daemonsu: restructure to support /su in initramfs or system_root
- ZIP: Support systemless on 5.0 (requires 3rd party patches)
- ZIP: Support for A/B slot systems with / inside system partition
15.09.2016 - v2.78 - SR1 - RELEASE NOTES
- subinary: Adjust app_process detection with manipulated mount namespaces
- subinary: Adjust Zygote PID detection to prefer 64-bit
- subinary: Fix possible NPE in LD_PRELOAD sanitization
- subinary: In systemless mode, ensure PATH contains /su/bin and /su/xbin
- supolicy: Ensure zero-on-alloc for new rules
- supolicy: Fix parsing allowxperm with multiple sources/targets in a single definition
- ZIP/Systemless: Give su.d 60 seconds to execute (from 4 seconds)
01.09.2016 - v2.78 - CCMT
- CCMT: Change default icon from Emblem to Material
- CCMT: Update detection activity
- CCMT: Update guide activity
- CCMT: Update translation files
27.08.2016 - v2.77 - BETA - RELEASE NOTES
- ZIP/Systemless: Support for hexpatches (Note7)
- ZIP/Systemless: Additional logging in daemonsu launcher script
05.07.2016 - v2.76
- Clear logs now asks for confirmation
- Fixed memory leak that could ultimately lead to reboots or root not working
- Fixed an issue that might have causes root loss on temporary unroot
- ZIP/Systemless: /data/su.img resized from 32M to 96M, to make sure enough space is available for systemless modes such as xposed
- ZIP/Systemless: launch daemon on post-fs-data, if supported by device (6.0+, fallback to service)
- CCMT: Added guide screen for new users
19.05.2016 - v2.74-2 - BETA - RELEASE NOTES
- supolicy/sukernel: Prevent security updates to SELinux from being applied
- sukernel: backup and restore modified ramdisk files, to be able to re-root if boot image backup got lost
- ZIP: Only show TWRP warning on TWRP v2.x
10.05.2016 - v2.72 - BETA - RELEASE NOTES
- Add support for ChromeOS boot images (Pixel C)
- supolicy: Fix logging to logcat for some processes on some firmwares
- supolicy: Fix fsck of /data/su.img being denied on some firmwares
- ZIP: Add LESSLOGGING flag
- ZIP: Add KEEPVERITY flag
- ZIP: Add KEEPFORCEENCRYPT flag
- ZIP: Also read flags from /cache/.supersu (aside from /data/.supersu and /system/.supersu)
31.03.2016 - v2.71 - BETA
- Massive speed improvement in handling permissive domains
- N/RC/BETA merged with normal BETA release
14.03.2016 - v2.70 - BETA RC - RELEASE NOTES
- Rewrote re-enabling root after temp-disable
- supolicy: Improve permissive domain handling
- N: Disable forced encryption
- N: Fix remounting /system for some apps (relatime becomes noatime for ro mounts)
- ZIP: call users scripts without setting LD_LIBRARY_PATH
13.03.2016 - v2.69 - BETA RC - RELEASE NOTES
- su: Escape from audit-based safe mode
- supolicy: Update to new v30 sepolicy format
- supolicy: Add support for special case M sepolicy format
- supolicy: Add support for XPERM rules
- sukernel: Add support for binary version of file_contexts
- ZIP: Create mount point in ramdisk instead of script
- ZIP: Add support for binary version of file_contexts
- BINDSYSTEMXBIN: Now disabled by default
- launch_daemonsu: Perform fsck before mounting
28.02.2016 - v2.68 - BETA - RELEASE NOTES
- su: Add -mns/--mount-namespace option
- su: Fix issue with sdcard on Note4/5.1
- sukernel: Fix issue where writing to /dev could truncate early at 64k barriers
- supolicy: Fix logcat issue on Omni/CM/etc
- supolicy: Disable AUDITDENY entries, to make debugging easier for devs
- supolicy: Extend fake-permissive to work with new Samsung firmwares
- ZIP: Fix TWRP log truncating and screen output on installs embedded in other ZIPs
- ZIP: Improve loopback device setup handling
- ZIP: Add PERMISSIVE flag
- ZIP: Move variable reading to after /system and /data have been mounted
- ZIP: Added call to custom patcher script, if any (/data/custom_ramdisk_patch.sh)
- ZIP: chmod 0751 /su/bin
21.01.2016 - v2.67 - BETA
- (systemless) Improved deep sleep fix for Samsung 5.1+
- (systemless) Added fallback method to mounting /su on system boot
- supolicy: fix bug copying system_server capabilities to init
- supolicy: replaced transitions: copy capabilities and attributes, silence audits
- supolicy: work-around shell-based services being executed as undefined_service on Samsung 5.1+
- sukernel: refuse to patch ChromeOS boot image
- FSTABSYSTEMRW: flag removed; worked around remount /system r/w issue
- ZIP: improved handling of loop devices
- ZIP: detect boot image partition being a symlink to a file on /data, and skip wipe if so
- Updated translation files
03.01.2016 - v2.66 - BETA
- (systemless): Add deep sleep fix for Samsung 5.1+
- supolicy: Adjust Samsung 6.0 init shell
- ZIP: Patch recovery SELinux policy
- ZIP: Improve su.img mounting
Changelogs continue in the next post ...
(reserved)
Nice, I shall be updating my version
Sweet dude
Awesome update !
Will SuperSU be able to manage the su binary included on a userdebug build of AOSP? Or does SuperSU download its own binary?
Thanks
crachel said:
Will SuperSU be able to manage the su binary included on a userdebug build of AOSP? Or does SuperSU download its own binary?
Click to expand...
Click to collapse
SuperSU uses it's own binary.
Can I just say this is badass !!! Just saying !!
Chainfire said:
SuperSU uses it's own binary.
Click to expand...
Click to collapse
can i remove existing SU app from my ROM and install this one? or do i have to keep both of them?
After flashing this, though i have granted the permissions, still apps say that, it did not get the permissions for root access and the screen just stays blank!
grgsiocl said:
can i remove existing SU app from my ROM and install this one? or do i have to keep both of them?
Click to expand...
Click to collapse
You can remove the existing SU app, SuperSU is a full replacement, binary and APK.
Thanks. Cool
Small update to v0.71. Primarily to fix a freak installation issue I had on one of my devices.
Temporary unroot and apps
Will this work around the problem of purchased Google movies that won't play because the app checks for root? Also with Google Wallet now checking for rooted devices I wanted to see if this was a true work around.
Thanks The Great ChainFire!
p.s. how can i remove the original superuser on my device? i cant find it on titanium backup?
thanks!
edit: i removed it!
rolandroland said:
Will this work around the problem of purchased Google movies that won't play because the app checks for root? Also with Google Wallet now checking for rooted devices I wanted to see if this was a true work around.
Click to expand...
Click to collapse
I'm not sure about movies (they are not available in my country) but I know wallet checks a number of things... your build.prop fingerprint must be correct, you may not have /system/app/Superuser.apk present (the CWM ZIP installs this!) and no "su".
It can work with SuperSU, but it's tricky.
Thank you sir for this! I will probably be buying the pro version but I know this is just the initial release of this app. It would be nice to get a workaround for video's. I tried ghost mode on superuser and it still wouldn't let me play movies. They have it locked down lol.
Looks excellent, going to give it a shot.
Great app, thank very much. Gone pro happily
Just a quick report. All is well other than having removed Superuser (and rebooted), I checked all my rooted apps for functionality and they were all fine except one. When I checked I was still able to adjust autostart permissions using Gemini App Manager, I was informed that 'Superuser' had to be installed for the app to work. I reinstalled Superuser (in addition to SuperSU) and the problem went away.
Thanks again!
- MultiFunctionsPlus Is The Successor Of MultiFunctions
- The Main Difference: The Pre-Activated Functions = Flashing MultiFunctionsPlus + Activator = Flashing MultiFunctions Only Or Deactivating The Pre-Activated Functions = Flashing MultiFunctionsPlus Only = Flashing MultiFunctions + Deactivator
Click to expand...
Click to collapse
MultiFunctionsPlusPage 1 Of 2Introduction:
A Module To Do The Next Functions [Clearing DalvikCache-PlayStoreWithServices-MagiskHideList, Changing The SELinux Mode, Booting The Android Into Safe Mode, Opening Magisk In Core Only Mode, Controlling The Virtual Memory (Swap), Changing The Swappiness Value, Keeping MagiskDaemon-MagiskHide Running, Changing DoubleTap2Wake(DT2W) Status, Fixing PlayStore Device Certification Status - Passing SafetyNet, Enabling The Low Ram Configurations, Disabling The Other Magisk Modules, Disabling The Magisk General Scripts & More].
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Installing/Configuring Apps, Modules, Scripts Or HideList, Check Activator (+Bootloop/Bootscreen/Blackscreen Resolver For Apps, Modules, Scripts & HideList) In Below
- P.S. All Functions Are Deactivated/Disabled By Default And The Needing To Activate Each Wanted Function Is Described In Below
- P.S. All Functions Can Be Used With Any-Rooting-Tool Except The Ones For Magisk Users Only As Described In Below
Current Version: MultiFunctionsPlus v1.0.3.4.2.4B7 - Activator v1.0.0.17A4.0.0 - QuickFix4Busybox v0.0.0.0.0.3
Recommendations:
- For Magisk Users Only, Disabling MagiskCoreOnlyMode From The Section Of Settings In Magisk Manager & Rebooting The Device Are Required To Load The Modules
- For Activating Any Function Using Any Root File Explorer Such MiXplorer To Access The Part Of Data Thru Root, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/<TheFunction>/Inactive And Then Reboot The Device
- P.S. In-Case Of Moving/Deleting The File Of Disable In Error, Deleting The Folder Of Status (/data/DreamerMods/MultiFunctionsPlus/Status) & Rebooting The Device Will Create The File Of Disable Again
- Activator Is A Bootloop/Bootscreen/Blackscreen Resolver For Apps, Modules, Scripts & HideList (P.S. MultiFunctionsPlus Is Required To Be Flashed Before Using Activator) So Actually There Is No Needing To Flash It To Use Any Function Such SELinuxModeInverter
- After Flashing The Module Of Activator & Rebooting The Device, It Will Do Its Functionality & Remove Itself
- P.S. For Any Magisk Version Below v14.0(1400), Use Any Method To Flash The Module As Described In Below Except Magisk Manager
- P.S. For Some Versions Of Magisk, Use QuickFix4Busybox As A Resolver For The Issue Of Internal Magisk Busybox Which Prevents Some Of Commands From Executing
Created: Nov.30.2019
Updated: Feb.22.2020
Download Link: Click Here (To Ensure That The Module Will Work Properly, Kindly Do What Are Mentioned In The Description)
** Magisk Installer: It Supports Magisk Only
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To v20.1(20100)
- For The Module Which Is Ended Its Name With v19000P (Or MMTEx1.x), It Supports Magisk v19.0(19000) To The Latest Version
** Unity Installer: It Supports Any-Rooting-Tool Such SuperSU, Lineage-AddOnSU & Magisk
- P.S. If You Flash The Same Version Of Module Twice, The Module Will Remove Itself But If The Version Of Second Time Is Higher Than The Version Of First Time, The Module Will Update/Upgrade Itself
- For The Module Which Is Ended Its Name With Unity1.5.x, It Supports Magisk v15.3(1530) To The Latest Version
- For The Module Which Is Ended Its Name With Unity1.5.4Ax, It Supports Magisk v8(800) To The Latest Version
- For The Module Which Is Ended Its Name With Unity4.x, It Supports Magisk v18.0(18000) To The Latest Version
- For The Module Which Is Ended Its Name With Unity5.x, It Supports Magisk v19.0(19000) To The Latest Version
Installation:
- Magisk Manager --> Modules --> Add (+) --> Choose The Downloaded File --> Reboot
- Or Flash It Thru A Custom-Recovery Such TWRP Recovery --> Reboot
- Or Flash It Thru ADB Sideload --> adb sideload TheFileNameOfModule.zip --> Reboot (P.S. Renaming The File To Have A Short One Is Recommended Such mfm.zip Before Using ADB Sideload)
- Or Using A Flash-Tool (Flasher) Such EX Kernel Manager, FK Kernel Manager, FlashFire Or Flashify --> Flash ZIP File --> Reboot
The Description: (1)
1- DalvikCache Cleaner (Advanced Dalvik/ART Cache Cleaner)
- Clearing The Dalvik Cache
- Doing The Same Functionality Of Wiping Dalvik/ART Cache Thru TWRP Recovery
- Removing All Remnants Of The Uninstalled Apps & Resolving/Fixing Some Issues With The Installed Apps
- Maybe It Takes About 5 Min. To Finish The Process
- After Doing Its Functionality, Check The Free Space Of Internal Storage Which Should Be Increased/Maximized A Little Bit
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of DalvikCacheCleaner, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/DalvikCacheCleaner/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
2- PlayStoreWithServicesData Cleaner (Advanced PS-GMS Data Cleaner)
- Clearing The Data Of Google Play Store & Google Play Services
- One Of The Methods To Resolve/Fix The Battery Draining & Re-Check PlayStore Device Certification Status
- After Doing Its Functionality, Check PlayStore Device Certification Status (Google PlayStore --> Settings --> Play Protect/Device Certification) Which Should Be Hidden For A While During Getting Its Status From Google
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of PlayStoreWithServicesDataCleaner, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/PlayStoreWithServicesDataCleaner/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
3- MagiskHideList Cleaner (Including MagiskHide Enabler & MagiskHideList Backup) [For Magisk Users Only]
- Clearing MagiskHideList [All Added Apps/Activities/Processes In MagiskHideList]
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Adding App/Activity/Process To MagiskHide, Use The Function To Clear All Apps/Activities/Processes From MagiskHideList Which Maybe Caused The Bootloop/Issue
- Activating The Function = Doing Its Functionality, Taking A Backup Of HideList & Disabling Itself
- For Activating The Functionality Of MagiskHideListCleaner, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskHideListCleaner/Inactive And Then Reboot The Device
- Additional Feature (Deactivating The Main Function + Activating The Sub-Function Of BackUp [Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskHideListCleaner/BackUp/Inactive And Then Reboot The Device] = Taking A Backup Of HideList)
- Additional Feature (Deactivating The Main Function + Putting A Copy Of The File Of HideList.txt Into The Folder Of Retrieving [Copy The File Of HideList.txt From /data/DreamerMods/MultiFunctionsPlus/MagiskHideListCleaner/BackUp/HideList.txt To /data/DreamerMods/MultiFunctionsPlus/MagiskHideListCleaner/BackUp/Retrieving And Then Reboot The Device] = Retrieving/Restoring The Last Saved MagiskHideList)
- Additional Feature (Activating The Sub-Function Of HideEnabler [Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskHideListCleaner/Hide/Inactive And Then Reboot The Device] = Enabling MagiskHide Once At Every Booting)
Click to expand...
Click to collapse
4- SELinuxMode Inverter (Advanced SELinux Mode Changer/Manager)
- Inverting The Default Android SELinuxMode During Startup ([From Permissive To Enforcing] Or [From Enforcing To Permissive])
- The Function Changes The SELinuxMode For The Entirety Of The Device's Uptime Until Next Reboot
- The Default Android SELinuxMode Can Be Either Enforcing Mode Or Permissive Mode Which Depends On The Installed/Flashed Rom/Kernel
- SELinux Enabled Kernel/SELinux Development Mode Is A Main Point To Use The Function (The Installed/Flashed Rom/Kernel Must Have The Ability To Switch Between Enforcing Mode & Permissive Mode)
- Enforcing Mode Is Preferable For Security (Specially Banking Apps) & Permissive Mode Is Preferable For Mods (Specially Audio Mods)
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of SELinuxModeInverter, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SELinuxModeInverter/Inactive And Then Reboot The Device
- Some Issues Which Are Related To Rooting-Tool/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Resolving The Issue Of Bootloop/Bootscreen/Blackscreen Which Changes The SELinuxMode Within 5 Min. After Rebooting & The Fast Mode Can Be Used For Changing The SELinuxMode At Booting But You Need Firstly To Do What Are Mentioned In The General Steps]
- For Activating The Fast Mode, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SELinuxModeInverter/Wait/Active And Then Reboot The Device
=============================
The General Steps- SELinux Enabled Kernel/SELinux Development Mode Is Required Which Means The Installed/Flashed Rom/Kernel Has The Ability To Switch Between Enforcing Mode & Permissive Mode
- To Check The Above Mentioned Ability, Install Terminal Emulator From PlayStore --> Open It -->
-----> For Getting The Current Android SELinuxMode, Write su --> Click On Enter --> Write getenforce (Most Devices) Or sestatus (Some Devices) --> Click On Enter
-----> For Setting The Current Android SELinuxMode, Write su --> Click On Enter --> Write setenforce 0 (For Permissive Mode) Or setenforce 1 (For Enforcing Mode) --> Click On Enter
-----> Check Again The Current Android SELinuxMode
-----> If The Mentioned Steps Worked/Succeeded, Activate The Function Of SELinuxModeInverter
-----> Enforcing Mode Is Preferable For Security (Specially Banking Apps) & Permissive Mode Is Preferable For Mods (Specially Audio Mods)
-----> If The Mentioned Steps Didn't Work/Succeed, It Means The Flashed Rom/Kernel Hasn't The Ability To Switch Between Enforcing Mode & Permissive Mode So Flash Another Rom/Kernel Which Supports The Ability Of Changing SELinux Mode
- P.S. Maybe The Flashed Rom/Kernel Hasn't The Ability To Switch Between Permissive Mode & Enforcing Mode During Startup So You Can Use Only The Wait Mode (Not The Fast Mode)
Click to expand...
Click to collapse
5- SafeMode Enabler
- Booting The Android Into SafeMode
- In-Case Of Facing A Bootloop Issue Due To Installing/Configuring An App, Use The Function To Remove Any App/Its Data Manually Which Maybe Caused The Bootloop/Issue (Rebooting The Device Manually Is Required To Get Back To The NormalMode)
- The Function Disables All Installed Apps (User Apps) & Also The Root Access By Enabling SafeMode & After Booting, Remove The Data/Uninstall Any App Which Caused The Bootloop/Issue (From Settings --> Apps --> The App --> Storage --> Clear Data/Uninstall) Then Reboot
- SafeMode Gives The Device The Ability To Not Open Any App Which Is Installed As A User App, And A "Safe Mode" Badge Will Appear In The Lower Left Corner Of The Screen
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of SafeModeEnabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SafeModeEnabler/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
6- MagiskCoreOnlyMode Enabler [For Magisk Users Only]
- Opening Magisk In CoreOnlyMode
- In-Case Of Facing A Bootloop Issue Due To Flashing A Module, Use The Function To Remove Any Module Manually Which Maybe Caused The Bootloop/Issue (Disabling MagiskCoreOnlyMode & Rebooting The Device Are Required To Load The Modules)
- The Function Disables All Magisk Modules By Enabling MagiskCoreOnlyMode & After Booting, You Can Disable MagiskCoreOnlyMode From The Section Of Settings In Magisk Manager Then Removing/Disabling The Module(s) Which Caused The Bootloop/Issue From The Section Of Modules In Magisk Manager Then Reboot
- CoreOnlyMode Gives The Device The Ability To Get Into The Android Directly With User Interface Which Means The User Can Use The Device With All Features/Functionalities Except Magisk Modules Even Before Removing The Module(s) Which Caused The Bootloop/Issue
- Enabling CoreOnlyMode Keeps MagiskSU, MagiskHide & Systemless Hosts Activated, But No Modules Are Loaded/Enabled
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of MagiskCoreOnlyModeEnabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskCoreOnlyModeEnabler/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
7- Swap Controller (RAM Management)
- Swap Is A Part Of Android RAM Management Which Depends On 2 Important Factors Which Are Swap Space & Swappiness Value
- Swap Is A Virtual Memory Which Allows Physical Memory RAM To Be Extended Using A Portion Of Internal Storage Where Android Moves Inactive Processes/Apps Into Virtual Memory To Make Space For New/Active Ones
- The Function Is Divided Into 2 Sub-Functions [SwapEnabler & SwapDisabler] For Improving Responsiveness/Performance
- SwapEnabler Re-Calculates Swap Space & Sets The New Size But SwapDisabler Sets Swap (Total) Size To Be 0 [It Can Be Checked Using DiskInfo From PlayStore]
- The Default Swappiness Value Is 35 For SwapEnabler & 0 For SwapDisabler
- The Function Disables Also KSM/UKSM For Reducing The Battery Drain & Lowering The CPU Usage
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of SwapEnabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SwapController/Enabler/Inactive And Then Reboot The Device
- For Activating The Functionality Of SwapDisabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SwapController/Disabler/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
8- Swappiness Changer (RAM Management)
- Swap Is A Part Of Android RAM Management Which Depends On 2 Important Factors Which Are Swap Space & Swappiness Value
- Swap Is A Virtual Memory Which Allows Physical Memory RAM To Be Extended Using A Portion Of Internal Storage Where Android Moves Inactive Processes/Apps Into Virtual Memory To Make Space For New/Active Ones
- There Are 3 Levels Of Swappiness Value [Low For 10, Mid For 30 & High For 60] For Improving Responsiveness/Performance [It Can Be Checked Using DiskInfo From PlayStore]
- The Function Disables Also KSM/UKSM For Reducing The Battery Drain & Lowering The CPU Usage
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of Low Swappiness, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SwappinessChanger/Low/Inactive And Then Reboot The Device
- For Activating The Functionality Of Mid Swappiness, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SwappinessChanger/Mid/Inactive And Then Reboot The Device
- For Activating The Functionality Of High Swappiness, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SwappinessChanger/High/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
9- MagiskDaemonHide Keeper (MagiskDaemon-MagiskHide Running Keeper) [For Magisk Users Only]
- The Function Is Divided Into 2 Sub-Functions [HideKeeper & DaemonKeeper] For Keeping Both Of MagiskDaemon & MagiskHide Running (Which Is Recommended To Be Used If Only Needed)
- HideKeeper Aims To Resolve The Issue Of Intermittent Work Of MagiskHide By Re-Enabling MagiskHide Every A Certain Time
- DaemonKeeper Aims To Resolve The Issue Of Losing Root Access Randomly (Or Magisk Is Not Installed) By Re-Starting MagiskDaemon Every A Certain Time
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of HideKeeper, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskDaemonHideKeeper/Hide/Inactive And Then Reboot The Device
-----> Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Re-Enabling MagiskHide Every 36 Min. & The Fast Mode Can Be Used Re-Enabling MagiskHide Every 18 Min.]
-----> For Activating The Fast Mode, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskDaemonHideKeeper/Hide/Wait/Active And Then Reboot The Device
- For Activating The Functionality Of DaemonKeeper, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskDaemonHideKeeper/Daemon/Inactive And Then Reboot The Device
-----> Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Re-Starting MagiskDaemon Every 10 Min. & The Fast Mode Can Be Used Re-Starting MagiskDaemon Every 5 Min.]
-----> For Activating The Fast Mode, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskDaemonHideKeeper/Daemon/Wait/Active And Then Reboot The Device
Click to expand...
Click to collapse
10- DT2WStatus Inverter (DoubleTap2Wake Enabler/Disabler)
- Inverting The Default DT2W Status During Startup ([From Disabled To Enabled] Or [From Enabled To Disabled])
- The Function Changes The DT2W Status For The Entirety Of The Device's Uptime Until Next Reboot
- The Default DT2W Status Can Be Either Enabled Or Disabled Which Depends On The Installed/Flashed Rom/Kernel
- The Installed/Flashed Rom/Kernel Must Support The Feature Of DT2W (DoubleTap2Wake)
- Activating The Function = Inverting The Default DT2W Status
- For Activating The Functionality Of DT2WStatusInverter, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/DT2WStatusInverter/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
11- MagiskDeviceSpoofingTool Enabler (Device Emulator For Device Certification & SafetyNet) [For Magisk Users Only]
- Fixing PlayStore Device Certification Status & Passing SafetyNet
- The Function Changes Some Properties Of Build.Prop For The Entirety Of The Device's Uptime Until Next Reboot
- The Function Changes The Device Fingerprint To Another Certified One (Currently Pixel 2 XL)
- MagiskHide Must Be Working Properly Which Is A Main Point To Pass SafetyNet
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of MagiskDeviceSpoofingToolEnabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskDeviceSpoofingToolEnabler/Inactive And Then Reboot The Device
- Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Resolving The Issue Of Blackscreen & The Fast Mode Can Be Used For Resolving The Issue Of Non-Persistent After Rebooting]
- For Activating The Fast Mode, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskDeviceSpoofingToolEnabler/Wait/Active And Then Reboot The Device
- P.S. The Device's Fingerprint Can Be Checked Using Device Info HW From PlayStore - SafetyNet Can Be Checked Using Either Magisk Manager Itself Or SafetyNet Helper Sample From PlayStore - Root Detection Can Be Checked Using RootBeer Sample From PlayStore
- P.S. Maybe Activating Both Functions Of PlayStoreWithServicesDataCleaner & DalvikCacheCleaner Are Required
- P.S. The Most Famous Reasons Of Root Detection Are Magisk Itself, Installed Rom/Kernel, Loaded Prop, Installed App, File/Folder In The Internal/External Storage & External Connection Thru Internet
Click to expand...
Click to collapse
12- LowRamConfig Enabler (RAM Management)
- Enabling The Low Ram Configurations For Low Ram Device
- The Function Changes The Low Ram Configurations For The Entirety Of The Device's Uptime Until Next Reboot
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of LowRamConfigEnabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/LowRamConfigEnabler/Inactive And Then Reboot The Device
- Some Issues Which Are Related To Rooting-Tool/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Resolving The Issue Of Blackscreen & The Fast Mode Can Be Used For Resolving The Issue Of Non-Persistent After Rebooting]
- For Activating The Fast Mode, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/LowRamConfigEnabler/Wait/Active And Then Reboot The Device
Click to expand...
Click to collapse
13- MagiskModules Disabler [For Magisk Users Only]
- Disabling The Other Magisk Modules
- In-Case Of Facing A Bootloop Issue Due To Flashing A Module, Use The Function To Remove Any Module Manually Which Maybe Caused The Bootloop/Issue
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of MagiskModulesDisabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskModulesDisabler/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
14- MagiskGeneralScripts Disabler [For Magisk Users Only]
- Disabling All Magisk General Scripts Of /data/adb/service.d & /data/adb/post-fs-data.d
- In-Case Of Facing A Bootloop Issue Due To Flashing A Module Or Placing A Script, Use The Function To Remove That Script Manually
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of MagiskGeneralScriptsDisabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskGeneralScriptsDisabler/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
General Info:
- To Disable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Check Box/The True Icon --> Reboot
- To Enable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Uncheck Box --> Reboot
- To Uninstall The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Bin Icon --> Reboot
- To Disable The Module For All Users [Non-Magisk Users & Magisk Users], Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/Status/Active And Then Reboot The Device
- To Enable The Module For All Users [Non-Magisk Users & Magisk Users], Delete The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/Status/Active And Then Reboot The Device
- To Uninstall The Module For All Users [Non-Magisk Users & Magisk Users] (Unity), Re-Flash The Module
>>>Dreamer(3MF)<<<
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
Other Modules
----------------------------------------------------------------------------------------------------------------
MultiFunctionsPlusPage 2 Of 2
Changelog:
v1.0.3.4.2.4B7: Improving The Code & Updating The Function Of [MagiskDeviceSpoofingTool Enabler] To Emulate "Pixel2XL"
v1.0.3.4.2.4B6: Fixing Minors, Improving The Code & Supporting All Magisk Versions From Magisk v8(800) To The Latest Version
v1.0.3.4.2.4B4: Fixing Minors, Improving The Code & Supporting All Magisk Versions From Magisk v13.1(1310) To The Latest Version
v1.0.3.4.2.4B0/2: Improving The Code & Updating To Magisk v20.x
v1.0.3.4.2.4/4A1: Fixing Minors & Improving The Code
v1.0.3.4.2.3L: Improving The Code
v1.0.3.4.2.3F: Improving The Code, Adding The Function Of [MagiskModules Disabler] For Disabling The Other Magisk Modules & The Function Of [MagiskGeneralScripts Disabler] For Disabling The Magisk General Scripts
v1.0.3.4.2.3A/B: Improving The Code, Adding The Function Of [MagiskDeviceSpoofingTool Enabler] For Passing The SafetyNet & The Function Of [LowRamConfig Enabler] For Enabling The Low Ram Configurations
v1.0.3.4.2.2: Initial Release
Click to expand...
Click to collapse
The Description: (2)
*** Re-Flashing The Module Of MultiFunctionsPlus With Keeping The Same Configurations:
- Re-Flash The Module Of MultiFunctionsPlus (Don't Reboot) & Move The Folder Of MultiFunctionsPlus From The Folder Of 4U [/data/DreamerMods/4U/MFP] To The Folder Of DreamerMods (/data/DreamerMods) Then Reboot
Click to expand...
Click to collapse
*** Activator (+Bootloop/Bootscreen/Blackscreen Resolver For Apps, Modules, Scripts & HideList): Activating Some Functions Of MultiFunctionsPlus For Once To Resolve Some Issues (P.S. MultiFunctionsPlus Is Required To Be Flashed Before Using Activator)
- Flash The Module Of MultiFunctionsPlus (Don't Reboot) & Flash The Module Of Activator (Reboot Now) For Activating Some Functions [DalvikCache Cleaner, MagiskHideList Cleaner, SafeMode Enabler, MagiskCoreOnlyMode Enabler, MagiskModules Disabler & MagiskGeneralScripts Disabler] For Once To Resolve Some Issues
- Booting The Android Into SafeMode For Giving The Ability To Remove Any App/Its Data Manually Which Maybe Caused The Bootloop/Issue (Rebooting The Device Manually Is Required To Get Back To The NormalMode)
- Clearing DalvikCache For Removing All Remnants Of The Uninstalled Apps & Resolving/Fixing Some Issues With The Installed Apps
- Clearing All Apps/Activities/Processes From MagiskHideList Which Maybe Caused The Bootloop/Issue [For Magisk Users Only]
- Disabling The Other Magisk Modules Which Maybe Caused The Bootloop/Issue [For Magisk Users Only]
- Disabling All Magisk General Scripts Which Maybe Caused The Bootloop/Issue [For Magisk Users Only]
- Opening Magisk In CoreOnlyMode To Deactivate All Modules For Giving The Ability To Remove Any Module Manually Which Maybe Caused The Bootloop/Issue (Disabling MagiskCoreOnlyMode & Rebooting The Device Are Required To Load The Modules) [For Magisk Users Only]
- Flashing/Re-Flashing The Module Of Activator Will Activate The Above Mentioned Functions (Even-If Magisk Is In Core Only Mode For Magisk Users)
Click to expand...
Click to collapse
*** Execution Mode: The Execution Mode Of Script/Module
- There Are 2 Modes [Execution In Normal Mode & Execution In Background Mode]
- Execution In Normal Mode: Executing The Script/Module Based On The Priorities Of Rooting-Tool/Rom/Kernel Itself Is Maybe A Proper Mode For Some Cases
- Execution In Background Mode (The Default One): Resolving The Issue Of Blocking The Other Scripts/Modules From Starting Early Due To The Execution Time Of Code Is Long & Also Related To Rooting-Tool/Rom/Kernel Itself (Such Losing The Functionality Of Xposed After Installing The Module Or Activating Any Function)
- For Activating Execution In Normal Mode, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/Status/Background/Active And Then Reboot The Device
- For Activating Mode Of Execution In Background Mode, Delete The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/Status/Background/Active And Then Reboot The Device
Click to expand...
Click to collapse
*** FAQ/Notes:
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Installing/Configuring Apps, Modules, Scripts Or HideList, Check Activator (+Bootloop/Bootscreen/Blackscreen Resolver For Apps, Modules & HideList) In Above
- After Flashing The Module Of Activator, MagiskHideList Will Be Cleared And For Retrieving/Restoring The Last MagiskHideList, Check The Function Of MagiskHideList Cleaner In Above
- All Functions Are Deactivated/Disabled By Default And The Needing To Activate Each Wanted Function Is Described In Above
- In Case Of Deleting The Folder Of Any Unwanted Function Such SELinuxModeInverter (/data/DreamerMods/MultiFunctionsPlus/SELinuxModeInverter) & Rebooting The Device, The Code Will Not Check The Unwanted Function Which Is Equivalent To The Permanent Deactivation/Removal Of The Unwanted Function So The Same Step Can Be Done With Any Unwanted Function (P.S. For Retrieving/Restoring The Unwanted Function, Deleting The Folder Of Status & Rebooting The Device Are Required)
- P.S. Deleting The Folder Of Status (/data/DreamerMods/MultiFunctionsPlus/Status) & Rebooting The Device Will Create The File Of Disable Again
- For Activating Any Function, Copying The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/<TheFunction>/Inactive (P.S. Negating The Negation Is A Form Of Affirmation) & Rebooting The Device Are Required
- Disable MagiskCoreOnlyMode From The Section Of Settings In Magisk Manager Which Is Required As An Essential Step To Activate Any Function (Disabling MagiskCoreOnlyMode & Rebooting The Device Are Required To Load The Modules)
- For Re-Flashing The Module Of MultiFunctionsPlus With Keeping The Same Configurations, Check The Details In Above
Click to expand...
Click to collapse
*** In-Case Of Failure: After Doing Successfully The Above Mentioned Steps
- During The Installation Process, Take The Screenshot After Flashing The Module & Send It
- Send These Logs (/data/MultiFunctionsPlus.log, /data/DreamerMods/MultiFunctionsPlus/Log/MultiFunctionsPlus.log, /data/DreamerMods/MultiFunctionsPlus/Log/MultiFunctionsPlusData.log & /data/DreamerMods/MultiFunctionsPlus/Log/MultiFunctionsPlusOld.log)
- Complete Info About The Device, The Used Rom, The Used Kernel & The Used Rooting-Tool
- Send The Folder Of DreamerMods (/data/DreamerMods)
- Send The Screenshots Of (Magisk Manager --> Main Screen, Magisk Manager --> Modules, Magisk Manager --> SuperUser & Magisk Manager --> Log --> SuperUser) [For Magisk Users Only]
- Send Magisk Log (Magisk Manager --> Log --> Magisk) [For Magisk Users Only]
- Send The Screenshot Of SuperUser Of The Used Rooting-Tool [For Non-Magisk Users]
- Send Full Logcat (Using Logcat Extreme From PlayStore)
Click to expand...
Click to collapse
>>>Dreamer(3MF)<<<
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
Other Modules
----------------------------------------------------------------------------------------------------------------
Reserved For News/Updates #0
Reserved For News/Updates #1
Reserved For News/Updates #2
Waiting for upload, don't see them yet.
Sent from my SM-N910F using Tapatalk
u81 said:
Waiting for upload, don't see them yet.
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
Could I Ask You To Send The Screenshots Of The Following?
-Settings --> Apps --> Instagram --> Storage
-Settings --> Apps --> WhatsApp --> Storage
-Settings --> Apps --> Messenger --> Storage
-Settings --> Apps --> SoundCloud --> Storage
u81 said:
Waiting for upload, don't see them yet.
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
Check This Post https://forum.xda-developers.com/ap...al-media-cache-advanced-t3799155/post76705484.
Don't have sound cloud
{
"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"
}
YouTube attached as well
Sent from my SM-N910F using Tapatalk
YouTube screenshot
Sent from my SM-N910F using Tapatalk
I'm only updated to Alexander's DevBase5.8 + RamKernel RC7 + Magisk v15.3 + Greenify a few hours ago so the current storage usage is possibly much smaller than normal. (Data not wiped)
It should be up to normal size by tomorrow, I'd say.
Sent from my SM-N910F using Tapatalk
u81 said:
I'm only updated to Alexander's DevBase5.8 + RamKernel RC7 + Magisk v15.3 + Greenify a few hours ago so the current storage usage is possibly much smaller than normal. (Data not wiped)
It should be up to normal size by tomorrow, I'd say.
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
Kindly Send Also A Screenshot Of Your Internal Storage (Unhide Option Should Be Selected)
Is this what you're looking for?
Sent using Tapatalk
Samsung Note4 - SM-910F - Alexander's DevBase5.8 + RamKernel RC7 + Magisk v15.3 + Greenify
Motorola G5S+ - Stock
u81 said:
Is this what you're looking for?View attachment 4517147
Sent using Tapatalk
Samsung Note4 - SM-910F - Alexander's DevBase5.8 + RamKernel RC7 + Magisk v15.3 + Greenify
Motorola G5S+ - Stock
Click to expand...
Click to collapse
No, From Your File Browser.
Is this what you're looking for?
If not, please share your screenshot and I'll find how to get that screenshot from my phone
Sent using Tapatalk
Samsung Note4 - SM-910F - Alexander's DevBase5.8 + RamKernel RC7 + Magisk v15.3 + Greenify
Motorola G5S+ - Stock
Deleted
Will these do?
Sent using Tapatalk
Samsung Note4 - SM-910F - Alexander's DevBase5.8 + RamKernel RC7 + Magisk v15.3 + Greenify
Motorola G5S+ - Stock
I was thinking about one thing related to your modules. They're useful, but it'll be kinda messy sometime, since you're creating a lot of different modules, separately.
Since all of them have similar purposes (clear caches from something), how about you merge all of them into a single module, with an interactive terminal interface? I guess it'd be a great update, and not only easier to you to maintain and organize all of those modules, but easier to others to find them and use. Just a quick thought.
abacate123 said:
I was thinking about one thing related to your modules. They're useful, but it'll be kinda messy sometime, since you're creating a lot of different modules, separately.
Since all of them have similar purposes (clear caches from something), how about you merge all of them into a single module, with an interactive terminal interface? I guess it'd be a great update, and not only easier to you to maintain and organize all of those modules, but easier to others to find them and use. Just a quick thought.
Click to expand...
Click to collapse
Currently There Are 8 Modules [WiFi Connection State On Status Bar - App Shortcut & Widget In Notification Area - SELinux Mode Inverter (Advanced SELinux Mode Changer) - Microsoft Intune Company Portal Hider - Tez Hider - Clear Dalvik Cache (Advanced Dalvik/ART Cache Cleaner) - Clear Google PlayStore With Services Data (Advanced PS-GMS Data Cleaner) - Clear Social Media Cache (Advanced Social Media Apps Cache Cleaner)] So What Do You Think?
Dreamer(3MF) said:
Currently There Are 8 Modules [WiFi Connection State On Status Bar - App Shortcut & Widget In Notification Area - SELinux Mode Inverter (Advanced SELinux Mode Changer) - Microsoft Intune Company Portal Hider - Tez Hider - Clear Dalvik Cache (Advanced Dalvik/ART Cache Cleaner) - Clear Google PlayStore With Services Data (Advanced PS-GMS Data Cleaner) - Clear Social Media Cache (Advanced Social Media Apps Cache Cleaner)] So What Do You Think?
Click to expand...
Click to collapse
Nice, but I was talking specifically about these cache related modules, not the others, I forgot to mention that. Merging them into a single module seems to be a nice idea. But well, just a thought as I said.
Hi guys, Those who know what Tasker is, can be aware of the status of the root core in Magisk.
DESCRIPTION
Some people, unfortunately I'm one of them, are having troubles with the Magisk root core being disabled randomly and suddenly on the Redmi Note 7.
And who knows? It's maybe happening across other different devices
So, this will periodically check if the device keeps having root access. Otherwise, a notification will be generated when not detected, and will offer you the option to reboot it.
This project includes an Initial Setup task that needs to be executed when it is imported from TaskerNet
(It can be deleted after imported)
Notes:
- Use it only if necessary.
- It uses the 'TIME_TICK' intent when rebooted ONLY. The rest of the time longer checks are used (30' by default).
- All is bundled into a single prj file, so import it as a project.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
To download the latest version of the profile you can go here. Enjoy it
Activate VoLTE & VoWIFI on custom/stock ROMs with any Carrier
Yes, yes, I know that this is not the first thread with activation VoLTE and VoWIFI. But my thread will be more convenient and easier to understand.
ATTENTION ! ! ! These methods were only tested with OnePlus 7 Pro. Not 7,8,910 Series.
ONLY ONEPLUS 7 PRO MODEL ! ! ! So please don't PM me if you haven't OnePlus 7 Pro.
OnePlus devices support all the most modern services that are offered to their subscribers by mobile operators around the world.
This guide is universal method for VoLTE & VoWiFi activation on both OOS and custom ROMs. Root is needed in some cases.
Before using this guide, please read second post in this article. It is important to understand which firmware is used in your ROM.
Also you can check Carrier List in third post.
Spoiler: New method (A12/A12.1/A13 ROM)(OOS11/OOS12 FW)
Download and install QPST and Qualcomm Drivers from releases page on GitHub
Download and install USB Gadget Tool from https://f-droid.org/ru/packages/net.tjado.usbgadget/
Plug-in your phone into PC, and don't forget to enable MTP and ADB
Open USB Gadget Tool and turn on next modes (if they turned off) :
( cser.dun.O , diag.diag, diag.diag.mdm , ffs.adb , gsi.dpl , gsi.rmnet , qdss.qdss , qdss.qdss.mdm )
Further actions depending on what you need: EFS or PDC
IMPORTANT!!! Don't forget to disconnect and reboot your OP7Pro after using any mode (If you want use both EFS and PDC, then use PDC, after that, disconnect and reboot OP7Pro, then repeat all steps from beginning for EFS)
Spoiler: For EFS Explorer
Excecute " setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb " in adb shell with su (root):
adb shell su setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
Then check that all COM ports are added in QPST Configuration, one of these ports will be SDM855 - our device
Open EFS Explorer
Profit
End of guide for EFS Explorer
Spoiler: For PDC Tool
Excecute " setprop sys.usb.config diag,serial_cdev,rmnet,adb " in adb shell with su (root):
adb shell su setprop sys.usb.config diag,serial_cdev,rmnet,adb
Then after 10 seconds disable in USB Gadget Tool app next modes : "diag.diag and diag.diag.mdm"
After that open PDC Tool
Profit
End of guide for PDC Tool
Depending on what you need follow the 7-13 p. from Old Method instructions. This new method was tested on crDroid 8.
Spoiler: Old method (OOS 9-10 ROM and FW only)
OnePlus devices support all the most modern services that are offered to their subscribers by mobile operators around the world. To enable and configure IMS services requires a minimum of time and effort, it is very rare now, for which many thanks to OnePlus. Also doesn't need root
On OOS 9.5.9 and higher after entering the code *#800# and *#801# select "EngineerMode"
Instruction:
1. You need to activate IMS service on your Carrier side. On some carrier IMS is activated by default.
2. Install Qualcomm QPST Diag port x64 / QPST 2.7.474 software on your computer (links below)
Important: there should be no other Qualcomm drivers on the computer, disable them, otherwise error messages will appear!
3. Enter * # 800 # in the stock dialer, and then click oneplus Logkit - next - Function Switch - next - activate VoLTE switch, VoWifi switch and VT switch.
Then reboot the device and turn on VoLTE and VoWIFI in the settings of your SIM card (“Settings” –– “WiFi and Internet” ––––– “SIM-card and network” “VoLTE and Calls via WI-FI”). If the switches “VoLTE switch”, “VoWifi switch”, “VT switch” are NOT available in your “oneplus Logkit”, install this version
OEMLogKit.apk or OEMLogKit_1.0-1.apk
and EngineeringMode.apk
4. Now you need to connect your mobile phone to the computer via the “USB cable”.
5. Open the dialer enter this code *#801#.
6. After entering the code correctly, a new menu appears, turn on there "Full-port switch"
7. Now you start the program on your PC: “PDC” from the QPST software package and select your smartphone from the list of connected devices.
8. Right-click on the line “Oversea-Commercial_DS” in the section of the “Deactivate” menu that opens, select “Sub0” and “Sub1”.
9. Next, in the list of available profiles, select "Profile that will be good for your country and Carrier, check the list below", right-click on it and in the section of the menu that opens, select "SetSelectedConfig", "Sub0" and "Sub1".
10. Now again click on the profile line “Profile that will be good for your country and Carrier, check the list below” and below in the program window click the “Activate” button.
11. Now go back to the MENU of item 6 of this menu instruction. Turn off the item "Full-port switch", reboot your smartphone and the VoLTE or VoWiFi logo should be displayed in the status bar.
12. ViLTE (video over LTE) may or may not work, depending on the services of your mobile Carrier.
13. If u have an issue with VoLTE (may go in default setting after reboot - DC Commercial), then do next after step 8 : Click on “Oversea-Commercial_DS” again and below click on the “Remove” button.
If you want to activate VoLTE on stock OOS 11 ROM then you can use this simple guide.
If you have any Questions or issues related to my guide you can ask me on Telegram (link in my profile). Before asking me on Telegram please follow ALL steps without exception!
Firmware explanation:
Activation method depends on what firmware you have installed. Not OS (crDroid, LineageOS, Pixel Experience), but firmware (fw).
There are 4 versions of fw for OnePlus 7 Pro for now : | OOS 9 | OOS 10 | OOS 11 | OOS 12 |
If you have installed OOS 9 or OOS 10 then use Old method from top post.
If you have installed OOS 11 or OOS 12 then use New method from top post.
You can ask developer about what version of firmware installed on your custom ROM.
Carrier choice:
Spoiler: Carrier list
Australia - Optus - Telefonica_UK_Commercial
Australia - Telstra - Telefonica_UK_Commercial
Belgium - Orange - Telefonica_UK_Commercial
Belgium - Proximus - India_Volte_Vodafone
Brazil - Claro - Telefonica_UK_Commercial
Brazil - TIM - Volte_OEM_lab
Canada - Bell - Telefonica_UK_Commercial
Canada - Telus - Telefonica_UK_Commercial
Czech Republic - O2 - Telefonica_UK_Commercial
France - Orange - Orange_Commercial_France
France - Orange - Telefonica_UK_Commercial
France - RED SFR - Telefonica_UK_Commercial
Greece - Cosmote - H3G_Denmark_Commercial
Israel - 012 mobile - Telefonica_UK_Commercial
Israel - Partner - Telefonica_UK_Commercial
Kenya - Faiba - ROW_Commercial
Ksa Saudi Arabia - Zain ksa - Germany
Ksa Saudi Arabia - Zain ksa - India_Volte_Vodafone
Ksa Saudi Arabia - Zain ksa - Telefonica_UK_Commercial
Mexico - ALTAN - Telefonica_UK_Commercial
Netherlands - KPN - Norway Telia Commercial
Norway - Telenor - India_Volte_Vodafone
Poland - Orange - DT_Poland_Commercial
Poland - Plus Polkomtel - ROW_Commercial
Romania - Orange RO - India_Volte_Vodafone
Romania - Vodafone RO - India_Volte_Vodafone
Russia - All Carriers - Telia_Finland
Russia - MegaPhone Region not Moscow - Volte_OEM_lab
Slovakia - Orange - DT_Slovakia_Commercial
Sri Lanka - Dialog - India_Volte_Vodafone
Sri Lanka - MobitelSriLankaTelecom and Dialog - Telefonica UK, Commercial
Switzerland - Wingo (Swisscom) - Netherlands_VoLTE_Vodafone
Turkey - TurkTelekom - India_Volte_Vodafone
If you could not find your country or operator, then there are two options:
1. Try to use: India_Volte_Vodafone or Telefonica_UK_Commercia . Thees are most common modes.
2. Try to search your country and operator here and here
Also if you enabled VoLTE with some config that doesn't represented in the list, then please leave a message in this thread in next format:
Country - Carrier - Mode
ex.
Russia - MTS - Telia_Finland
This will be helpful for other members of xda community. Also i update list of carriers from time to time.
Check here, did a video guide in English on the same.
Cheers
Doesn't work on custom roms and doesn't even look like you tested this on Android 10 at all.... Which is what most people are using now..
Blackcrane said:
Doesn't work on custom roms and doesn't even look like you tested this on Android 10 at all.... Which is what most people are using now..
Click to expand...
Click to collapse
Working fine on PE. It doesn't work, if custom ROM didn't support it
Blackcrane said:
Doesn't work on custom roms and doesn't even look like you tested this on Android 10 at all.... Which is what most people are using now..
Click to expand...
Click to collapse
Once you enabled using this method u don't need to do same all over on custom ROM, enable Volte option and restart the ROM and it should works.
And working fine on Android 10 as well.
Working on both tested myself.
Thank you for the guide, is it necessary to actually perform step number 8? Seems so permanent;
9. Now click on “Oversea-Commercial_DS” again and below click on the “Remove” button.
And I see per the previous guide;
https://forum.xda-developers.com/oneplus-7-pro/help/force-enable-volte-vowifi-t3934227
"Click on Oversea-Commercial_DS again and click on remove -- DO NOT CLICK REMOVE, JUST DE-ACTIVATE IT - your settings stick after a reboot, so no longer need to remove the profile (at least on my device my profiles stick, also makes it easier to go back to default)"
cantenna said:
Thank you for the guide, is it necessary to actually perform step number 8? Seems so permanent;
9. Now click on “Oversea-Commercial_DS” again and below click on the “Remove” button.
And I see per the previous guide;
https://forum.xda-developers.com/oneplus-7-pro/help/force-enable-volte-vowifi-t3934227
"Click on Oversea-Commercial_DS again and click on remove -- DO NOT CLICK REMOVE, JUST DE-ACTIVATE IT - your settings stick after a reboot, so no longer need to remove the profile (at least on my device my profiles stick, also makes it easier to go back to default)"
Click to expand...
Click to collapse
Thank u! Added in end of guide (optionally)! Btw i also sometimes have this issue, but on latest beta - just deactivate is good for me too
how the IMS service is activated?
efx_d3 said:
how the IMS service is activated?
Click to expand...
Click to collapse
U need to activate it on ur Carrier side. On most Carriers it's enabled by default.
jimmy123322 said:
U need to activate it on ur Carrier side. On most Carriers it's enabled by default.
Click to expand...
Click to collapse
So, do I need to speak to my operator and request that they activate this service?
as this did not work for me, I think this IMS service is not active in my operator...
when i update i lose these settings
efx_d3 said:
So, do I need to speak to my operator and request that they activate this service?
as this did not work for me, I think this IMS service is not active in my operator...
Click to expand...
Click to collapse
Idk, maybe yes
Not working with Bell Canada
I have followed your handy guide with one issue, I can't get it to work for Bell Canada. I have tied multiple varieties. I initially used the Telefonica_UK_Commercial that is listed and made calls drop after 30 sec or so. When I used *#*#4636#*#* and selected the option in the top right and then IMS it showed VoLTE as inactive even though the symbol was present. I tried ATT_VoLTE and it shows VoLTE but no VoWIFI. I'm not sure if it worked or not. IMS showed VoLTE as active. I didn't really leave it to try it as I can't chance more dropped calls. I went back to the Oversea-Commercial_DS as it works for calls. I have contacted my carrier to ensure the IMS settings for VoLTE and VoWiFi are enabled on the carrier side.
2 things, first is you should add to your guide to ensure USB Debugging is enabled as I found it wouldn't work without.
2nd is when I make calls I have the HD symbol while calling, does this not mean it is using VoLTE already even without the symbol present in the status bar? Seems to be conflicting info regarding the HD calls symbol while actually in a call.
Lastly, not going to lie, the VoLTE and VoWiFi symbols are a little obnoxious on the stock ROM. Most other phones are fairly small or just an add on to the existing phone symbol.
Any suggestions for Canadian carriers to verify/ensure this is working correctly?
At step 7, when i open the app. my device is not listed.
jimmy123322 said:
Yes, yes, I know that this is not the first thread with activation VoLTE and VoWIFI. But my thread will be more convenient and easier to understand.
OnePlus devices support all the most modern services that are offered to their subscribers by mobile operators around the world. To enable and configure IMS services requires a minimum of time and effort, it is very rare now, for which many thanks to OnePlus. Also doesn't need root
On OOS 9.5.9 and higher after entering the code *#800# and *#801# select "EngineerMode"
Instruction:
1. You need to activate IMS service on your Carrier side. On some carrier IMS is activated by default.
2. Install Qualcomm QPST Diag port x64 / QPST 2.7.474 software on your computer (links below)
Important: there should be no other Qualcomm drivers on the computer, disable them, otherwise error messages will appear!
3. Enter * # 800 # in the stock dialer, and then click oneplus Logkit - next - Function Switch - next - activate VoLTE switch, VoWifi switch and VT switch.
Then reboot the device and turn on VoLTE and VoWIFI in the settings of your SIM card (“Settings” –– “WiFi and Internet” ––––– “SIM-card and network” “VoLTE and Calls via WI-FI”). If the switches “VoLTE switch”, “VoWifi switch”, “VT switch” are NOT available in your “oneplus Logkit”, install this version
OEMLogKit.apk or OEMLogKit_1.0-1.apk
and EngineeringMode.apk
4. Now you need to connect your mobile phone to the computer via the “USB cable”.
5. Open the dialer enter this code *#801#.
6. After entering the code correctly, a new menu appears, turn on there "Full-port switch"
7. Now you start the program on your PC: “PDC” from the QPST software package and select your smartphone from the list of connected devices.
8. Right-click on the line “Oversea-Commercial_DS” in the section of the “Deactivate” menu that opens, select “Sub0” and “Sub1”.
9. Next, in the list of available profiles, select "Profile that will be good for your country and Carrier, check the list below", right-click on it and in the section of the menu that opens, select "SetSelectedConfig", "Sub0" and "Sub1".
10. Now again click on the profile line “Profile that will be good for your country and Carrier, check the list below” and below in the program window click the “Activate” button.
11. Now go back to the MENU of item 6 of this menu instruction. Turn off the item "Full-port switch", reboot your smartphone and the VoLTE or VoWiFi logo should be displayed in the status bar.
12. ViLTE (video over LTE) may or may not work, depending on the services of your mobile Carrier.
13. If u have an issue with VoLTE (may go in default setting after reboot - DC Commercial), then do next after step 8 : Click on “Oversea-Commercial_DS” again and below click on the “Remove” button.
List of Carriers and Mode presented below
List of Carriers and Mode:
Greece - Cosmote - H3G_Denmark_Commercial
Czech Republic - O2 - Telefonica_UK_Commercial
Belgium - Orange - Telefonica_UK_Commercial
France - Orange - Telefonica_UK_Commercial
France - Orange - Orange_Commercial_France
France - RED SFR - Telefonica_UK_Commercial
Turkey - TurkTelekom - India_Volte_Vodafone
Norway - Telenor - India_Volte_Vodafone
Belgium - Proximus - India_Volte_Vodafone
Netherlands - KPN - Norway Telia Commercial
Brazil - Claro - Telefonica_UK_Commercial
Switzerland - Wingo (Swisscom) - Netherlands_VoLTE_Vodafone
Kenya - Faiba - ROW_Commercial
Australia - Optus - Telefonica_UK_Commercial
Sri Lanka - Dialog - India_Volte_Vodafone
Canada - Telus - Telefonica_UK_Commercial
Canada - Bell - Telefonica_UK_Commercial
Romania - Vodafone RO - India_Volte_Vodafone
Romania - Orange RO - India_Volte_Vodafone
Mexico - ALTAN - Telefonica_UK_Commercial
Russia - All Carriers - Telia_Finland
Russia - MegaPhone Region not Moscow - Volte_OEM_lab
If you could not find your country or operator, then there are two options:
1. Try to use: India_Volte_Vodafone or Telefonica_UK_Commercia . Thees are most common modes.
2. Try to search your country and operator here and here
Also if u enable VoLTE with some config, then please leave a message in this thread in next format:
Country - Carrier - Mode
ex.
Russia - MTS - Telia_Finland
This will be helpful for other members of xda community. Also i will add new config weekly.
App for checking VoLTE on GP Store
Big thanks for @dagoban and @jamal2367 for writing instructions and 4pda.ru for updating some info
Original thread - LINK
If i have any Questions u can ask me on Telegram (link in my profile)
Click to expand...
Click to collapse
Help
vladvlad12 said:
Help
Click to expand...
Click to collapse
Check your drivers at PC. Phone must be shown as COM port.
jimmy123322 said:
Check your drivers at PC. Phone must be shown as COM port.
Click to expand...
Click to collapse
It is not, just that
vladvlad12 said:
It is not, just that
Click to expand...
Click to collapse
2. Install Qualcomm QPST Diag port x64 / QPST 2.7.474 software on your computer (links below)
Important: there should be no other Qualcomm drivers on the computer, disable them, otherwise error messages will appear!
Evolution X 7.9.2 for the OnePlus 8, 8 Pro, 8T & 9R [instantnoodle] [instantnoodlep][kebab][lemonades]
{
"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"
}
Living, Breaking, Keep Evolving.
Pixel UI, customization and more, we are Evolution X!
- Team Evolution X -
@joeyhuab (Founder/Lead Developer)
@peaktogoo (Project Manager/Co-Founder)
@AnierinB (Project Specialist/Co-Founder)
Reach us on Twitter! @EvolutionXROM
Check out our website!
Spoiler: Feature List
Code:
Themes
- Theming Settings (Style, Color Source, Accent Color, Accent Background, Background Color, Luminance, Chroma, Tint Background)
- Custom Themes (Black, Clear, Vivid, Paint In The Snow, Espresso)
- Dark Theme Schedules
- Lock screen Clock Fonts (16 Fonts)
- Headline/Body Fonts (53 Fonts)
- SB Icon Packs (10 Styles)
- SB Signal Icon Packs (14 Styles)
- SB WiFi Icon Packs (10 Styles)
- System Icon Shape Packs (16 Styles)
- 3 Button Navbar Styles (10 Styles)
Status bar
- Status Bar Lyrics
- Clock Styles (Right, Center, Left)
- Clock & Date Configs (Auto Hide, Hide Duration, Show Duration, Seconds, AM/PM, Font Size, Date Position/Case/Format)
- SB Logo Pack (20 Styles, Right/Left)
- Network Traffic Indicators
- Battery Icon Styles (19 Styles)
- Battery Percent (Hidden, Inside Icon, Next To Icon)
- Battery Bar (Thickness, Alignment, Blend Colors, Reverse Direction, Colors, Animation)
- System SB UI Tuner
- Data Disabled Icon (On/Off)
- Old Style Mobile Data
- 4G Instead Of LTE
- Roaming Indicator
- WiFi Type Icon
- Colored Icons
- Notification Count
- Bluetooth Battery Status
- Mic/Camera Privacy Indicator
- Location Privacy Indicator
- Media Projection Privacy Indicator
Notifications
- ReTicker
- App Colored Background For Reticker
- Heads Up (Time Out, Importance Threshold, Less Boring, Stoplist/BlockList)
- Force Expand Notifications
- Notification Sound If Active
- Kill App Button
- Blink Flashlight For Incoming Call (When Ringing, When Silent, When Entierly Silent, Always)
- Blink Flashlight For Notifications
- In-Call-Vibrations (Connect, Waiting, Disconnect)
Quick Settings
- Clock
- Clock Font Size
- Date
- Battery Style (15 Styles)
- Battery Percent Location (Hidden, Inside Icon, Next To Icon)
- Battery Estimates
- Secure QS Tiles Requires Unlocking
- Quick QS Pulldown (Disabled, Right, Left, Always)
- Brightness Slider (Never, Expanded, Always)
- Brightness Slider Position (Top, Bottom)
- Auto Brightness Icon
- Hide Labels
- Label Text Size
- Smart Pulldown
- Vertical Layout
- Columns In Portrait (2-5)
- Columns In Landscape (2-6)
- QS Tile Animation Style (3 Styles)
- QS Tile Animation Druations (3 Speeds)
- QS Tile Animation Interpolator (8 Styles)
- Vibration On Touch
- Vibration On Touch Duration
- QS Footer Warnings
- Show Data Usage
- User Account Icon
- Edit Icon
- Power Menu Shortcut
- Running Services Shortcut
- Settings Shortcut
- Clear All Button (10 Styles, 5 Backgrounds)
Power Menu
- System Settings (Hold PWR Assistant + Hold Duration)
- Disable Power Menu On LS
- Power
- Restart
- Advanced Reboot Options
- Screenshot
- On-The-Go Mode
- Settings
- Lock Down
- Emergency
- Device Controls
- Users
- Logout
- Bug Report
Gestures
- System Settings
- Quick Tap
- Volume Button Playback Control
- Swipe To Screenshot
- Brightness Control
- PWR Button Torch
- Double Tap To Sleep Status Bar
- Double Tap To Sleep Lock screen
- AOSP Gestures
- Pill Length
- Pill Radius
- Hide IME Button Space
- Back Gesture Animation
Lock screen
- Edge Light
- Always On Fingerprint
- UDFPS Icon Picker (55 Styles)
- UDFPS Animation Picker (38 Styles)
- Lock screen Charging Info
- Hide Status Bar
- Hide QS During Secure Lock screen
- Media Cover Art (5 Filters)
- Ripple Effect
- Fingerprint Authentication Vibration
- Fingerprint Error Vibration
Buttons
- Navigation Bar
- Compact Layout
- Invert Layout
- Show Vol Panel On Left
- Per App Vol Control
- On-Screen NavBar
- Reorient Volume
- Volume Rocker Wake
- Keyboard Cursor Control
- Alert Slider Notifications
- Alert Slider Pulse
- Block Alert Slider In Pocket Mode
- Click To Partial Screenshot
Animations
- Screen Off Animation (3 Styles)
- Power Menu Animations (11 Styles)
- Android P Animation Style
Miscellaneous
- AOD Display Schedule
- Google Services
- Parallel Space
- Game Space
- Smart Pixels
- App Lock
- Launch Music App On Headset Connection
- Unlimited Photos Storage
- Unlock Higher FPS In Games
- Netflix Spoof
- Pulse Music Visualizer (Navbar, LS, Ambient)
- Volume Panel Timeout
- Jitter Test
- Ignore Secure Window Flags
- Show CPU Info
- Toast App Icon
- Sensor Block Per Package
- Wakelock Blocker
- Alarm Blocker
- Default USB Configuration
- Radio Info
Evolution X Launcher
- Icon Packs
- Notification Dots
- Icon Size
- Icon Font Size
- Max Lines For App Label
- Lock Layout
- Add App Icons To Home
- Dark Status Bar
- Double Tap To Sleep
- Wallpaper Scrolling
- Wallpaper Zooming
- At A Glance
- Swipe To Access Google Feed
- Hide/Show Status Bar
- Top Shadow
- Icon Labels On Desktop
- Hotseat Background
- Google Search bar
- Themed Icons
- Corner Radius
- Themed Icons In App Drawer
- App Drawer Search bar
- Icon Labels In App Drawer
- App Drawer Row Height
- App Drawer Background Opacity
- Recents Background Opacity
- Recents Scroll Vibration
- Recents Screenshot
- Recents Google Lens
- Recents Clear All
- Suggestions In All Apps List
- Suggestions On Home
- Blocked Suggestions
- Parallel Space
- Taskbar
- Rotation
- Hidden & Protected Apps
Spoiler: Device specific feature List
Code:
My signature Universal OPlusExtras application:
- Awesome alert slider (Notification/Flashlight/Brightness/Rotation/Ringer/Notification & Ringer/Refresh rate/ExtraDim/NightLight/ColorSpace)
- Ambient display gestures (raise2wake)
- Kcal
- Per-app refresh rate
- DC-Dimming toggle
- Auto HBM toggle (with lux adjustment preference)
- Power efficient Workqueue toggle
- MSM touchboost toggle
- fsync toggle
- Adrenoboost preference (off, light, medium, aggressive
- FPS overlay (9 Positions, 11 Colors & accent, 9 Sizes
- Powershare toggle
- Game mode toggle (240hz touch sampling rate)
- USB-OTG toggle
- USB2.0 Fastcharge toggle
- System Vibration Strength preference
• Google restore isn't functioning at this time.
You tell me
DO NOT FLASH GAPPS, ALREADY INCLUDED
DO NOT flash instantnoodlep (8 Pro) on instantnoodle (8) or vice versa, else you will semi brick your device! The only way to recover from this is by purchasing an EDL DEEP FLASH cable and using it in-conjunction with msmtool.
Please note that we ship OOS13 F.10 abl.img on 8, 8 Pro, 8T & 9R to bypass the BL unlocked warning!
Please note that we ship a Custom logo.img on 8, 8 Pro, 8T & 9R to better match the ROM!
First Time Install (8 & 8 Pro)
1. Be on any version of OOS12 or OOS13 (F.63 firmware is included in these builds)
2. Download vbmeta, recovery, and rom for your device from here
3. Reboot to bootloader
4. fastboot flash vbmeta vbmeta.img
fastboot flash recovery recovery.img
fastboot reboot recovery
5. While in recovery, navigate to Apply update -> Apply from ADB
6. adb sideload rom.zip (replace "rom" with actual filename)
7. Format data, reboot to system & #KeepEvolving
First Time Install (8T & 9R)
1. Be on the latest OOS13 (F.63 for 8T & F.22 for 9R)
2. Download copy_partitions, vbmeta, recovery, and rom for your device from here
3. Reboot to bootloader
4.fastboot flash vbmeta vbmeta.img
fastboot flash recovery recovery.img
fastboot reboot recovery
5. While in recovery, navigate to Apply update -> Apply from ADB
6. adb sideload copy_partitions.zip (press "yes" when signature verification fails) and then reboot to recovery
7. Repeat step 5 and adb sideload rom.zip (replace "rom" with actual filename)
8. Format data, reboot to system & #KeepEvolving
Update (8, 8 Pro, 8T & 9R)
1. Reboot to recovery
2. While in recovery, navigate to Apply update -> Apply from ADB
3. adb sideload rom.zip (replace "rom" with actual filename)
4. Reboot to system & #KeepEvolving
OTA
1. Check for update. If available, select "Download and install" (approx 10-15 min)
2. Reboot & #KeepEvolvingFirmware Update (8, 8 Pro, 8T & 9R)https://forum.xda-developers.com/t/...lution-x-7-5-01-13-2023.4480927/post-87295281
Android version: 13.0_r49
Security patch level: May 2023
Build author: Anierin Bliss
Kernel Source: https://github.com/Evolution-X-Devices/kernel_oneplus_sm8250
Clang version: 14.0.6
ROM Developer: joeyhuab
Source code: https://github.com/Evolution-X
Credits: @jabashque @LuK1337 @mikeioannina @ZVNexus from LineageOS
Spoiler: OnePlus 8 (Instantnoodle) latest downloads
rom:
https://sourceforge.net/projects/evolution-x/files/instantnoodle/evolution_instantnoodle-ota-tq2b.230505.005.a1-06020228-unsigned.zip/download
recovery:
https://sourceforge.net/projects/ev...ntnoodle/recovery_erofs/recovery.img/download
vbmeta:
https://sourceforge.net/projects/evolution-x/files/instantnoodle/vbmeta/vbmeta.img/download
Spoiler: OnePlus 8 Pro (Instantnoodlep) latest downloads
rom:
https://sourceforge.net/projects/evolution-x/files/instantnoodlep/evolution_instantnoodlep-ota-tq2b.230505.005.a1-06020056-unsigned.zip/download
recovery:
https://sourceforge.net/projects/ev...tnoodlep/recovery_erofs/recovery.img/download
vbmeta:
https://sourceforge.net/projects/evolution-x/files/instantnoodlep/vbmeta/vbmeta.img/download
Spoiler: OnePlus 8T (kebab) latest downloads
rom:
https://sourceforge.net/projects/evolution-x/files/kebab/evolution_kebab-ota-tq2b.230505.005.a1-06020305-unsigned.zip/download
recovery:
https://sourceforge.net/projects/evolution-x/files/kebab/recovery_erofs/recovery.img/download
vbmeta:
https://sourceforge.net/projects/evolution-x/files/kebab/vbmeta/vbmeta.img/download
copy_partitions:
https://sourceforge.net/projects/evolution-x/files/kebab/copy_partitions/copy_partitions.zip/download
Spoiler: OnePlus 9R (lemonades) latest downloads
rom:
https://sourceforge.net/projects/evolution-x/files/lemonades/evolution_lemonades-ota-tq2b.230505.005.a1-06020354-unsigned.zip/download
recovery:
https://sourceforge.net/projects/evolution-x/files/lemonades/recovery_erofs/recovery.img/download
vbmeta:
https://sourceforge.net/projects/evolution-x/files/lemonades/vbmeta/vbmeta.img/download
copy_partitions:
https://sourceforge.net/projects/evolution-x/files/lemonades/copy_partitions/copy_partitions.zip/download
Commonly asked questions & answers:
Q: Why am I getting "error cannot read" while attempting to sideload the ROM
Spoiler: Answer
Well, you should be using the latest platform-tools and have it added to PATH. A lot of unofficial drivers floating around on the internet install outdated adb/fastboot along with the drivers. Please refrain from installing these as well as minimal adb & fastboot; Use the official google driver and official platform-tools instead.
Alternatively you can prefix each adb/fastboot cmd with ./ while in the platform-tools folder via powershell or bash, etc.
For example:
./adb sideload ./rom.zip
This basically tells the shell "Hey, I want to execute this local binary rather than the one in PATH".
Q: I'm a windows user and my device is not being listed when I run adb/fastboot devices. I'm using the latest platform-tools, what could be the reason for this?
Spoiler: Answer
Use the official Google USB driver
Q: I'm a linux user and my device is not being listed when I run adb/fastboot devices. I'm using the latest platform-tools, what could be the reason for this?
Spoiler: Answer
Set up udev rules
Q: Why is MTP and/or Android Auto not working?
Spoiler: Answer
Set the default USB configuration in Settings > The Evolver > Miscellaneous > USB Configuration
Don't see your question? Well, feel free to post a comment in this thread, we will reply as soon as we can. We'd appreciate if users used XDA FIRST and the telegram group as a LAST RESORT.
To be continued (I'm sure).
Firmware update:
FLASHING THE WRONG DDR TYPE WILL SEMI BRICK YOUR DEVICE. THE ONLY WAY TO RECOVER FROM THIS IS BY PURCHASING AN EDL DEEP FLASH CABLE AND USING IT IN-CONJUNCTION WITH MSMTOOL!!
Spoiler: Method 1
1. Check your DDR type using the following command:
adb shell getprop ro.boot.ddr_type
0 = ddr4
1 = ddr5
if getprop returns an empty value, use the following commands instead (requires root):
adb shell
su
cat /proc/devinfo/ddr_type
DDR4 = DDR4
DDR5 = DDR5
1. Download and flash the firmware zip that matches your device and DDR type:
8 (instantnoodle)
8 Pro (instantnoodlep)
8T (kebab)
9R (lemonades)
2. Reboot to recovery and then sideload the ROM.
Spoiler: Method 2
8 (instantnoodle)
8 Pro (instantnoodlep)
8T (kebab)
9R (lemonades)
Custom Kernels:
Custom kernels may be flashed at YOUR OWN RISK. However, we will not provide extended support regarding such and it is up to YOU, the end user to make your reports in the appropriate thread for X kernel, not in this thread.
Obtaining root:
Let it be known that we will not assist anyone with bug reports until they have disabled all modules and restored to the default, unpatched kernel that is shipped with the ROM!
Root can be obtained by either one of the following methods.
Spoiler: Method 1 (flashing magisk.apk/zip)
1. Download the Magisk.apk on your pc (you can change the file extension to .zip if you wish, though it is not required).
2. Reboot to recovery
3. Navigate to Apply update -> Apply from ADB
4. adb sideload magisk.apk (replace "magisk" with actual filename)
Spoiler: Method 2 (patching boot.img)
1. Download the full rom.zip from post #2 of this thread
2. Download payload-dumper-go that corresponds to the architecture of your pc
3. Run payload-dumper-go against the rom.zip
4. Grab boot.img from the extracted folder and transfer it to your device
5. Patch the boot.img with the magisk application and transfer the patched image to your pc
6. Reboot to bootloader
7. fastboot flash boot boot.img (replace "boot" with actual filename)
Retaining root across OTA updates:
When an OTA update is available, let it download and install. Before rebooting simply open Magisk Manager and click on the first "install" button and select "install to inactive slot". Once it's done, reboot and enjoy.
Reporting bugs and submitting logs:
In most cases logs should be provided when reporting bugs. This can be done by enabling USB debugging in developer options of the device, connecting it to your PC and running one of the following cmds depending on the type of bug/issue while reproducing it:
General system log
adb logcat > logcat.txt
Kernel log
adb shell su -c dmesg > dmesg.log
Please provide a detailed description of the bug/issue as well as link/upload the log you had taken.
There are exceptions to this as some issues are unable to be caught in logs. In this case, it is expected that users provide clear and accurate steps to reproduce the issue.
Getting involved in the development:
We've set everything up in such a way where all you need to do is install AOSP build dependencies, initialize a repo client, init the tiramisu branch of our manifest, sync the code and lunch your device (e.g lunch evolution_instantnoodlep-userdebug); Roomservice will automatically sync all device specific dependencies for you to compile without error. There is no need to manually clone anything due to this and applies to OnePlus 6, 6T, 7, 7 Pro, 7T, 7T Pro, 8, 8 Pro, 8T, 9R, 9 & 9 Pro (enchilada, fajita, guacamoleb, guacamole, hotdogb, hotdog, instantnoodle, instantnoodlep, kebab, lemonades, lemonade & lemonadep).
Device and ROM source changes can be submitted on github to the appropriate repositories by making pull requests via comparing forks. Please follow the google patch format for commits and triple check your changes by compile testing and verifying they're correct. Please retain proper authorship if you are not the author!
AB sir Pro.
Noice ! Can't wait to test
W W W W Whaaaaat!!!! Already! So fast, you guys are legends!
So can I dirty flash from 6.7? or have to clean install?
I'm sure you'll get round to adding the features, but does this have the same evolver features as 6.7?
Best dev ever
d3viou5 said:
W W W W Whaaaaat!!!! Already! So fast, you guys are legends!
So can I dirty flash from 6.7? or have to clean install?
I'm sure you'll get round to adding the features, but does this have the same evolver features as 6.7?
Click to expand...
Click to collapse
You can dirty, but it's in alpha stage.. so you shud be ready for bugs.
thanks dev. does magisk work?
david1907 said:
thanks dev. does magisk work?
Click to expand...
Click to collapse
Yup
OPlusExtras are back
Great job Anierinb! Man do you work quick! Can't wait to update to this and get all the cool android 13 stuff
So I did a dirty flash from 6.7 to 7 and all went well......
Is there a folder somewhere for the latest builds? I still have the version without the OnePlusExtras.
I guess without the Evolver there's no OTA.
Great job BTW. There are bugs as expected, but love how we have access to this so early!
d3viou5 said:
So I did a dirty flash from 6.7 to 7 and all went well......
Is there a folder somewhere for the latest builds? I still have the version without the OnePlusExtras.
I guess without the Evolver there's no OTA.
Great job BTW. There are bugs as expected, but love how we have access to this so early!
Click to expand...
Click to collapse
I don't think the new build is uploaded yet, but in any case you can check his SF folder
I have a c33 fw installed and on a custom a12 based rom.. Can I dirty flash the rom on top of it?
Updates with OPlusExtras, fixed BT, NFC and safetynet are up on SF
just a query, does anyone use this ROM without ROOT ?
AnierinB said:
Updates with OPlusExtras, fixed BT, NFC and safetynet are up on SF
Click to expand...
Click to collapse
Time to flash
I know this is alpha, so fully expecting this, but pretty much every installed app crashes.
Any reason for this?
I did dirty flash, my lazyness could certainly be a contributing factor.
Battery life is tuly aweful.
But hey, it's A13. V4A, Root, Safetynet, GCAM Mods All good......
d3viou5 said:
I know this is alpha, so fully expecting this, but pretty much every installed app crashes.
Any reason for this?
I did dirty flash, my lazyness could certainly be a contributing factor.
Battery life is tuly aweful.
But hey, it's A13. V4A, Root, Safetynet, GCAM Mods All good......
Click to expand...
Click to collapse
I just installed the latest version and came here just to post this. Initially Youtube and Chrome were crashing but after the App data wipe for youtube, it's working.
But chrome and KIWI browser are not at all working. haven't tested all apps though.
Looks like all Chrome depending apps are crashing. like (OLX, etc)
Biggest concern is : Screen Casting is auto connecting to my TV though i dont initiate it. I disconnect and after a few seconds it re connects