[MODULE] Disable thermal throttling on android_device_oneplus_oneplus2 - Magisk

Just something that I wrote for my own sanity because copying it back to /system after each and every ota was a pain
This is for oneplus2 only
Also, I'm not responsible for any damage caused by this module to your device. You are the one choosing to do these modifications and not me
Now with all of that out of the way, the latest version can be found at https://raw.githubusercontent.com/a...ce_oneplus_oneplus2/master/ZEROTHROTTLING.zip but I will also upload on xda
Repo link: https://github.com/anupritaisno1/DisableThermalThrottling-android_device_oneplus_oneplus2

Nothing to see here

Perfect module to play VR games and watch your headset burn

Support for s5 g906s rom lineage 7.1.1 rom?

Related

[EXPERIMENTAL] [UNOFFICIAL] Xposed for arm64 devices | 5.1 and 5.0 versions available

arm64 is now officially supported: See here
Old OP
Hello Everyone,
I have successfully compiled Xposed for android 5.1.x for arm64 devices.
I have so far tested this on my Nexus 9 running a custom CyanogenMod based Android 5.1 ROM with SELinux disabled (It may work on ROM's with SELinux enabled but testing has to be conducted.).
Install zip is attached to this post. (The SDK 22 one) This will only install Xposed framework for Android 5.1 for arm64 devices. Please see the original Lollipop post to get the other files you need. (Hint: you only need the Xposed APK from that post.)
I compiled this based off of @romracer's source code for Xposed on Android 5.1.x.
So far I have tested the module Lolistat, It seems to be working well.
Please be patient during boot, let your device boot 10 minutes before reporting that it is "bootlooping"
====================
For Android 5.0.x
I have also compiled Xposed for Android 5.0.x for arm64 devices. I have had mixed results from testers so far. The install zip is also attached to this OP (The SDK 21 one). Many HTC M9 users have reported this caused a boot-loop for them. This will only install Xposed framework for Android 5.0.x for arm64 devices. Please see the original Lollipop post to get the other files you need. (Hint: you only need the Xposed APK from that post.)
Remember to always backup all data before using. Use at your own risk.
Please note: There will most likely be arm64 related bugs with both of these. See this post for more information.
Please be patient during boot, let your device boot for 10 minutes before reporting that it is "bootlooping"
just in case...
I got a new m9 in the box, thinking about waiting to activate it since xposed wouldn't work on it yet.
Sim-X said:
I got a new m9 in the box, thinking about waiting to activate it since xposed wouldn't work on it yet.
Click to expand...
Click to collapse
I could also compile Xposed arm64 for android 5.0 if there is enough interest.
Sim-X said:
I got a new m9 in the box, thinking about waiting to activate it since xposed wouldn't work on it yet.
Click to expand...
Click to collapse
Somebody would need to be willing to test, but I could try to compile Xposed for it.
Well, if you're willing to test and support it, you can post unofficial files for testing...
I have a Nexus 9 with Android 5.0 myself and it's running fairly well. I haven't used any complex modules though.
Be aware that 64-bit ROMs need different handling in a couple of places and break some expectations. For example, initZygote() will be executed twice, as there are two app_processXX processes now. Modules might not expect this. I also didn't succeed to enforce a certain startup order of the processes (app_process64 before app_process32) yet, so results might be a bit random. There are probably more differences like this and it's generally more complex than on 32-bit ROMs. That's why I have only posted files for ARM so far. On the other hand, if you're willing to look into issues that come up (e.g. installation problems, crashes, things that are not working) and do some pre-analysis, that's fine and could bring the project forward. If nothing to major comes up, I can then also include official files with the next version. Additional support would be very welcome anyway.
Framework installation zip attached to OP.
good
Only for 5.1?
auggie246 said:
Only for 5.1?
Click to expand...
Click to collapse
I made a version for android 5.0 but I would need somebody to test it before I release it.
5.0 for samsung galaxy s6 ?
koko115 said:
5.0 for samsung galaxy s6 ?
Click to expand...
Click to collapse
Are you kidding? Move along!
subscribed.
Feel free to post any problems you have with this here. (arm64 related problems)
Rastapop 5.1 on n9 with selinux on. I can install xposed fine but rebooting after enabling YouTube adaway and gravitybox causes a never ending boot logo
YouTube adaway works fine
For me
Guitarboarder28 said:
Rastapop 5.1 on n9 with selinux on. I can install xposed fine but rebooting after enabling YouTube adaway and gravitybox causes a never ending boot logo
Click to expand...
Click to collapse
From my understanding, gravitybox is not compatible with Android 5.1 at all.
joshuabg said:
From my understanding, gravitybox is not compatible with Android 5.1 at all.
Click to expand...
Click to collapse
Ohhh didn't even think about that. Would make sense
Thanks for taking this on, joshuabg. I couldn't believe it when I saw this thread. I thought that 5.1 jumped the arm64 shark and we'd never see xposed for N9.
Anyway, I flashed on AICP 4/6 with FireIce K8.3, SELinux disabled and it booted just fine. Tried the following modules, and I see what rovo meant in his post above. It's really hit or miss with the modules just like the [SUPER ALPHA] xposed for 32 bit arm devices. Thanks again for rolling this out to test.
YouTube Adaway - seemed to work, jumped to dozens of random videos and no ads
Minmin Guard - app opened and seemed to operate normally but I think it may have blocked ads across the board without my telling it to do so. I think it also caused an XDA Free force close on opening that wouldn't go away
Swype Tweaks - caused Swype to FC anytime the keyboard should have launched
Yup my bad. Gravitybox says right in the description it'll cause a boot loop on 5.1. Everything is working perfectly. Thanks!

[UNOFFICIAL] Xposed for Samsung Lollipop by arter97

/* Intro */
3 months after the first functional Xposed for Lollipop by @rovo89 was introduced,
now here comes *somewhat* functional Xposed for Samsung Lollipop firmware.
Embrace yourself.
/* Technical background */
Why were Samsung users left out of the Xposed party?
Because Samsung has massively customized ART runtime included in their firmwares compared to AOSP.
And plus, because the system partition has so little space left, they have additionally implemented xz decompression on top of ART.
Those 2 main reasons has differentiated Samsung's ART from the rest of the ROM's ART.
More technical information on post 2.
/* Disclaimer */
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this project
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
/* Prerequisite */
Due to my skills limitation, only deodex'ed ROMs are supported for now.
For more explanations, checkout post 2.
/* Supported firmwares */
Every ARMv7(32-bit) Samsung Lollipop Android 5.0 deodex'ed firmware should work.
But please note that I have tested this only on Galaxy S4, Note 3 and S5.
For 64-bit, please check http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 by @wanam
For 32-bit on Android 5.1, I cannot develop on it as I don't have any 32-bit devices capable of running Android 5.1.
/* Before you download ... */
Donate to @rovo89
Donate to @wanam
Show your thanks to @_riddle
Without these people, this would not have been possible at all.
/* Details about binaries */
CyanogenMod's ART runtime changes merged - Performance improvements
Compiled using Linaro GCC 4.8
Method in-lining optimizations made in Android 5.1 merged
Few Android M ART runtime changes which were early-adopted by Samsung merged
-O3 and other compiler optimizations added
Release separated to "exynos" and "snapdragon" versions for more compiler optimizations
Optimize everything enabled
/* Download */
Attached below on XDA
/* How to install */
1. No matter what you do, back-up first.
2. Install XposedInstaller app from http://forum.xda-developers.com/showthread.php?t=3034811
3. Flash the attached Xposed framework zip on the custom recovery.
/* How to uninstall for V1 ~ V7 */
1. Flash the attached Xposed uninstaller zip on the custom recovery.
/* v75+ sticky note */
With v75 and up, this port do not longer touches core-libart.jar, thanks to @wanam.
This would potentially increase compatibility and fix other weirdness such as malfunctioning email app.
However, this introduces some variables.
First, there are more versions that you should choose.
Exynos and Snapdragon is quite self-explanatory, but there are now new "requestConcurrentGC" version for maximizing compatibility.
Don't know what to choose? Don't worry, it won't break your device if you install a wrong one.
If you install a wrong one, the installer will simply tell you that you should go with the other version.
As far as my testing goes, only the Korean Note 3 firmwares should install "requestConcurrentGC" version.
Uninstaller part have changed too.
You need to use uninstaller provided directly by @rovo89.
Do not use my uninstaller for v75 and up.
/* Technical information and Q&A */
Q: What took you so long?
A: @rovo89 has explained himself. http://forum.xda-developers.com/showpost.php?p=58949255&postcount=3
Q: Okay, you don't seem like a better developer than @rovo89. How did you do it?
A: Of course not. This is the main reason why deodex'ed ROM is a prerequisite.
Samsung has implemented all sorts of funny stuffs on their version of ART. See the link above.
To workaround this, converting a ROM to deodex'ed format somewhat brings back the oat formats to *AOSP-like* dex format(Huge thanks to @_riddle).
After deodexing is done, we can use source-built ART binaries with minimal modifications.
But due to my coding skills, I had to modify core-libart.jar to make it work again.
The core-libart.jar differs from every single device out there and it'll be a real headache to match with 1 ART binary version. That's why I've included the core-libart.jar on the installation zip file.
The included core-libart.jar has 2 different versions to correspond on the type of ROM user is using.
1 : Firmwares with appStartup
2 : Firmwares without appStartup
After deodexing, installing new ART stuffs, we can start the boot-up sequence.
Unfortunately again, /system/bin/installd passes some arguments that AOSP version of dex2oat do not understand. To bypass this, I've patched oat tools to ignore unimplemented arguments.
Now we can see the good old "Android is upgrading" pop-up and go have a cup of coffee while it dexopts all those hundreds of bloatwares.
Q: Fantastic, but now I get a continuous logcat burps - http://pastebin.com/MxeAE76n
A: To avoid that, that's why I've put 2 different versions of core-libart.jar. But unfortunately on those cases, my installer has failed to recognize which version your ROM uses.
During the installation, the installer will output a message on which core-libart.jar is installed on your system.
After you see that logcat stuffs, please change to the opposite version of core-libart.jar the installer told you.
So for example, if the installer says core-libart1.jar is installed, extract the zip and replace /system/framework/core-libart.jar with core-libart2.jar within the zip.
Q: How do I deodex my ROM?
A: @joeldroid and @svadev have an awesome tool for you to deodex your ROM.
Go check http://forum.xda-developers.com/and.../script-app-joeldroid-lollipop-batch-t2980857 and http://forum.xda-developers.com/galaxy-s5/general/tool-deodex-tool-android-l-t2972025
Both worked flawlessly for me.
Q: Gimme tha sources!
A: https://github.com/arter97/android_art/tree/samsung-lollipop
Q: AAA and BBB modules are incompatible!
A: Most likely because they don't support Touchwiz Lollipop *yet*.
Q: You mother father gentleman, you bricked my phone!
A: Unfortunately, I had tested those only on 3 devices which, ironically, has the same processor. Maybe Exynos family is not support, I don't know.
I told you to back-up beforehand. Post log and we can probably work together and add your device/ROM supported.
/* Changelog */
v75
Xposed v75 merged
(Fixes boot issue with latest Android 5.0 firmwares)
Method changed to use @wanam's XposedBridge
/* v75+ sticky note */
With v75 and up, this port do not longer touches core-libart.jar, thanks to @wanam.
This would potentially increase compatibility and fix other weirdness such as malfunctioning email app.
However, this introduces some variables.
First, there are more versions that you should choose.
Exynos and Snapdragon is quite self-explanatory, but there are now new "requestConcurrentGC" version for maximizing compatibility.
Don't know what to choose? Don't worry, it won't break your device if you install a wrong one.
If you install a wrong one, the installer will simply tell you that you should go with the other version.
As far as my testing goes, only the Korean Note 3 firmwares should install "requestConcurrentGC" version.
Uninstaller part have changed too.
You need to use uninstaller provided directly by @rovo89.
Do not use my uninstaller for v75 and up.
V6
Xposed v71 merged
Possible performance degradation issue fixed
Releases renamed to "exynos" and "snapdragon", now the "exynos" version is properly optimized for Exynos processor
Uninstaller added
Optimize everything enabled
V5
Xposed v65 merged - Now compatible with alpha4
Do not attempt to use uninstaller provided by rovo89, it will brick your device for now - TODO
V4
ART runtime & Xposed binary changes by rovo89 merged - Fixes logging and some other misc issues
CyanogenMod's ART runtime changes merged - Performance improvements
Compiled using Linaro GCC 4.8
Method in-lining optimizations made in Android 5.1 merged
Few Android M ART runtime changes which were early-adopted by Samsung merged
Few core-libart.jar smali durps fixed
-O3 and other compiler optimizations added
Release separated to "generic" and "krait" versions for more compiler optimizations
Generic - Devices with Exynos or other non-Krait Snapdragon SoCs; If you don't know which to choose, go with Generic.
Krait - Devices with Quadcore Krait Snapdragon SoCs.
V3
Another version of core-libart.jar added for GT-i9505 compatibility
(Firmwares without isMdfEnforced)
This update is unnecessary for devices which already runs Xposed with no issues.
V2
Source code modification attempted to hopefully fix boot issues with devices like Galaxy Alpha.
https://github.com/arter97/android_art/commit/eed217701cc2d3a57f940c5bd69b393c768777a9
This update is unnecessary for devices which already runs Xposed with no issues.
/* Known issues */
- Galaxy Alpha users apparently get a bootloop with this.
A kind user provided a logcat, will look into it ASAP.
Solved with V2.
- GT-I9505 users apparently get a continuous Google Apps FCs with this.
Solved with V3.
Thank you!!!!! How do we go about reverting it just in case anything were to happen? Does this have the same issue as darkera13's guide where you can't install apps?
Sweet! Any chance of supporting the S6 in the future?!
Damn no support for s6 edge
---------- Post added at 05:55 PM ---------- Previous post was at 05:54 PM ----------
Looks great though. No decomiling involved
SuperSmashedBro said:
Thank you!!!!! How do we go about reverting it just in case anything were to happen? Does this have the same issue as darkera13's guide where you can't install apps?
Click to expand...
Click to collapse
Exactly same .
Goood good
works fine on my galaxy s5 dous BOC2
xposed moudle and install apk normally works fine
darkera13 said:
Exactly same .
Click to expand...
Click to collapse
Which one is the original method yours or arter's?
I'm confused?
AMAZING!!!!!
arter you're genius!
noobiedev83 said:
Which one is the original method yours or arter's?
I'm confused
Click to expand...
Click to collapse
Me. I show a demo video 1 week ago. I public it first, even dont say but he base on my work is the true.
Xposed dont work with Samsung Lollipop Roms long time ago, the long time enough for all of you think this mission is impossible until i public my guide and he public after that about few hours.
darkera13 said:
Me. I show a demo video 1 week ago. I public it first, even dont say but he base on my work is the true.
Xposed dont work with Samsung Lollipop Roms long time ago, the long time enough for all of you think this mission is impossible until i public my guide and he public after that about few hours.
Click to expand...
Click to collapse
It should at least give you credit for that because I do remember seen your post a week ago
darkera13 said:
Me. I show a demo video 1 week ago. I public it first, even dont say but he base on my work is the true.
Xposed dont work with Samsung Lollipop Roms long time ago, the long time enough for all of you think this mission is impossible until i public my guide and he public after that about few hours.
Click to expand...
Click to collapse
Um, no offense but your method quite differs from mine.
I left out String.clear() and modified core-libart.jar to be compatible universally.
Your guide did not help me in anyways.
And I was also working on this weeks ago. Just didn't share it with the world which were *not-working* then.
arter97 said:
Um, no offense but your method quite differs from mine. And I was also working on this weeks ago. Just didn't share it with the world which were *not-working* then.
I left out String.clear() and modified core-libart.jar to be compatible universally.
Click to expand...
Click to collapse
You know what you do. Dont lie yourself.
To be honest, i tried both methods and @arter97 's methods worked for me without any hassle.
Kudos to you for making this work.
noobiedev83 said:
It should at least give you credit for that because I do remember seen your post a week ago
Click to expand...
Click to collapse
Here http://forum.xda-developers.com/showpost.php?p=60747729&postcount=2645
and here http://forum.xda-developers.com/showpost.php?p=60748574&postcount=29
darkera13 said:
You know what you do. Dont lie yourself.
Click to expand...
Click to collapse
Stealing is the least thing to do on my mind, as I have gone through the same thing over and over.
Ask my Twitter's followers.
I can personally guarantee you that I have not stolen anything from you.
Ask me how I did it more specifically, I'll happily explain it to you.
Working on Note 4 PopRocks Rom N910T
arter97 said:
Please note that I have tested this only on Galaxy S4, Note 3 and S5.
Click to expand...
Click to collapse
You think this will work on Albe95 S6 Rom port (GT-I9505)? :fingers-crossed:

[DEPRECATED] [Module][2018.10.4] Miracast, Tethering HDMI Enabler + USB Debugging Notification Dis

THIS PROJECT IS NO LONGER SUPPORTED.
Code:
# <Module name goes here>
## Copyright (C) 2017-2018, VR25 @ xda-developers
### License: GPL v3+
---
#### DISCLAIMER
This software is provided as is, in the hope that it will be useful, but without any warranty. Always read/reread this reference prior to installing/upgrading. While no cats have been harmed, I assume no responsibility under anything which might go wrong due to the use/misuse of it.
A copy of the GNU General Public License, version 3 or newer ships with every build. Please, read it prior to using, modifying and/or sharing any part of this work.
To prevent fraud, DO NOT mirror any link associated with this project.
---
#### DESCRIPTION
Hide USB Debugging notification, enable tethering, HDMI (& HDMI mirroring), and wireless display mirroring (Miracast). More features may come.
---
#### PRE-REQUISITES
- Magisk v15+
---
#### SETUP STEPS
1. Install/upgrade from Magisk Manager or custom recovery.
2. Reboot.
3. Go to Settings > Display > Cast > 3 dots; tick the "Enable wireless display" checkbox.
---
#### LINKS
- [Facebook Page](https://facebook.com/VR25-at-xda-developers-258150974794782/)
- [Git Repository](https://github.com/Magisk-Modules-Repo/<repo name goes here>/)
- [XDA Thread](https://forum.xda-developers.com/apps/magisk/module-miracast-tethering-enabler-adb-t3611335/)
---
#### LATEST CHANGES
**2018.10.4 (201810040)**
- Magisk 15+ support
- Set prop values aggressively.
You should note it's for marshmallow mainly. Doesn't work on Nougat for many devices. Untested on android O.
LazerL0rd said:
You should note it's for marshmallow mainly. Doesn't work on Nougat for many devices. Untested on android O.
Click to expand...
Click to collapse
I've tested only on Moto Z Play stock Nougat and LineageOS based ROMs. You may be right. Perhaps some manufacturers hardcode their ROMs to bypass this kind of modification. I don't have any other device to test this on. I'll post a poll to see how that goes. Thanks.
VR25 said:
I've tested only on Moto Z Play stock Nougat and LineageOS based ROMs. You may be right. Perhaps some manufacturers hardcode their ROMs to bypass this kind of modification. I don't have any other device to test this on. I'll post a poll to see how that goes. Thanks.
Click to expand...
Click to collapse
Well, ik on Nexus it doesn't work in any stock based Nougat ROM.
Will it work in Kitkat or Lollipop?
Raynelfss said:
Will it work in Kitkat or Lollipop?
Click to expand...
Click to collapse
Yes, but it may not work on some devices/ROMs. You should try and report back.
LazerL0rd said:
Well, ik on Nexus it doesn't work in any stock based Nougat ROM.
Click to expand...
Click to collapse
Yes. Miracast on LineageOS only work for now. (It's just fixed this problem, no magisk module, no editing build prop)
VR25 said:
After installing and rebooting, go to Settings > Display > Cast > Click the 3 dots > Enable Wireless Display > Done.
Now you can mirror your phone's screen to any Miracast supported device, such as TVs and Windows 10 PCs.
Note: this may not work on some devices/ROMs.
Click to expand...
Click to collapse
Is there a uninstaller incase it doesn't work on my phone? Running resurrection remix 7.1.2
n0013z said:
Is there a uninstaller incase it doesn't work on my phone? Running resurrection remix 7.1.2
Click to expand...
Click to collapse
Usually, this doesn't cause any issue in case it doesn't work. You can easily remove it from the Magisk Manager app. Alternatively, you can also mount magisk.img from recovery and delete the folder "magiskmiracast" inside /magisk.
Use this recovery flashable zip
https://forum.xda-developers.com/attachment.php?attachmentid=4081169&d=1489956274
to mount magisk.img to /magisk.
Miracast is working for me but only for some minutes I play videos, show some pictures and the screen freeze only in my Smartv.
I play videos and more with Allcast and it doesn't happen
Sent from my Moto G (5) Plus using XDA Labs
No luck for me
Oneplus 2 a 2003 rr 5.8.3
Not working on OP3T on OOS
Tried it and it kills magisk and xposed without mercy. Samsung galaxy on5 stock touchwiz 6.0.1
Shen Ron said:
Tried it and it kills magisk and xposed without mercy. Samsung galaxy on5 stock touchwiz 6.0.1
Click to expand...
Click to collapse
Something is wrong with TouchWiz.
So, do I need to be rooted? Or can it be flashed from stock recovery on my zte blade v7 lite (android 6.0) without damage being done? Also I do believe the device needs specific hardware, correct me if I'm wrong!?...
Has anyone tested this on OnePlus 3T?
gb_14 said:
Has anyone tested this on OnePlus 3T?
Click to expand...
Click to collapse
Heyyo, lol literally four posts above yours.
ThE_MarD said:
Heyyo, lol literally four posts above yours.
Click to expand...
Click to collapse
Oh yeah, sorry, I haven't noticed.
HTC One m9, bad boys one m9 nougat 4.1 rom.
I dont have a display option in the settings (probably because of sense)
Only have display and gestures but no cast option inside.
I installed on my S7 Edge Nougat ... But I did not find in any menu the options to activate. Has anyone had this problem? I also tried to test mirroring with an LG TV and could not.

Official Xposed Framework for Android Nougat is Here – Download your Favorite Modul

As the Android ecosystem has matured over the years, fewer and fewer users find reasons why they should root their device. There’s a growing trend of users choosing to stay on the stock firmware, either because they find the experience satisfactory or don’t want to play a cat-and-mouse game with Google’s SafetyNet API. But if you asked a user back in early 2016 why they rooted their phones, perhaps the number one reason that was given was so they could install the Xposed Framework. It’s been over a year since Android 7.0 Nougat was first released, but the long wait is finally over: official Xposed Framework for Android Nougat is finally available.
Why install the Xposed Framework?
Want to get custom ROM features without flashing a custom ROM? The mother of all Xposed Modules for tweaking your ROM, known as GravityBox, has you covered. Want to customize display settings on a per-app basis? Try App Settings. How about customizing certain applications like Hangouts? Or modifying Instagram so you can download whatever posts you like?
posed gives developers the ability to modify pretty much whatever they want—mostly aimed at individual applications but even system-wide features can be modified. The examples we listed is just the tip of the iceberg. The number of additional features you can add or apps you can modify is incredible—just search through the official Xposed Module repository to see for yourself. Keep in mind that some modules might need to be updated for this new release and for Nougat support, so be sure to check before installing them on your Nougat ROM!
How do Xposed Modules work?
The gist of it is that the Xposed Framework allows modules to “hook” into the Java methods of any application—be it user-installed or a system application. Xposed lets modules execute their own methods before, during, or in place of the original methods of the target application.
For instance, imagine a method used in the Gmail application that posts notifications for new emails. By default, the method creates a new notification with buttons to archive/delete or reply to the email. A Xposed Module could be made to hook into this method and add a new button such as “mark as read.” (Yes, there’s already a Module for just that.)
The above is an over-simplification of the end result of what the Xposed Framework allows its modules to do. The Framework itself is incredibly complex and making it work nearly universally on rooted devices—without needing a custom ROM—is why Xposed for Android Nougat has taken so long to complete. *install at your own risk, I'm not responsible for anything you do to your device.
Source link:
XDA
https://www.xda-developers.com/official-xposed-framework-android-nougat/
https://forum.xda-developers.com/showthread.php?t=3034811
Xposed
http://repo.xposed.info/
Installation:
Download the xposed zip file and flash it in recovery (framework files)
Now install the xposed apk
Reboot mobile
*dont open the app before installing the zip
Download link:
xposed-v88.2-sdk24-arm64.zip (7.0)
http://dl-xda.xposed.info/framework/sdk24/arm64/
xposed-v88.2-sdk25-arm64.zip (7.1)
http://dl-xda.xposed.info/framework/sdk25/arm64/
Xposed 3.1.4.apk
https://forum.xda-developers.com/attachment.php?attachmentid=4319220&d=1509453299
Download any module of your choice
http://repo.xposed.info/module-overview
What's the point of this thread? Is it just to get a few likes? Xposed is well known and people should refer to the original Xposed thread.
Besides your instructions are wrong.. and please be careful of which framework you use.. on stock it is sdk24 on other customers roms it depends on the Android version.
spunxhoe said:
What's the point of this thread? Is it just to get a few likes? Xposed is well known and people should refer to the original Xposed thread.
Besides your instructions are wrong.. and please be careful of which framework you use.. on stock it is sdk24 on other customers roms it depends on the Android version.
Click to expand...
Click to collapse
I use what I want, you don't want to take care about me and this thread., head to the source link to read the full thread that's all.

[UNOFFICIAL][MAGISK MODULE] Active Edge Mod for Edge Sense Plus - continuation for patch levels 2021-01-05 and later

EDIT: It's too annoying to maintain and edit 6 separate threads. The installer works across all devices, so please visit this post for the latest version: https://forum.xda-developers.com/t/...or-patch-levels-2021-01-05-and-later.4226343/
Thanks!
NOTE: Download link in the OP will install mod for the current patch level down to January 2021. It will detect your current patch level and install the correct file. For earlier system builds from 2020 and prior, please use the official discontinued module on the Magisk Manager repo. I did not clone the entire Active Edge Mod repository; my unofficial repository only hosts January 2021 and later builds.
Changes:
I know, I know... I said I was done with releasing my Unofficial Active Edge Mod installer, yet here's another month's update. I might keep doing it for those that update immediately and want it a bit sooner, so long as it's fortunate enough to happen on a day when I'm able to do it relatively quickly. Since I'm building these anyway and sending them over to the dev, for now, to upload to the official Magisk repo, for now I don't mind also updating it here a bit sooner. Anyway, more on this below and some of the headache involved moving forward...
04-05-2021: Soooo... the script I wrote to churn these out as quickly as possible as Google releases the updates, relied on system image dumps on GitRip... unfortunately the domain was seized by the FBI (lol) and so it looks like the old dumper is no longer updating his Android dumps repo on GitRip. Fortunately, mikalovtch pointed me over to a new source that hosts such system dumps, and I was able to get these done relatively quickly afterwards. OP is updated with the 04-05-2021 installer now!
03-02-2021: Meant to post an update a week or two ago. Noticed the magisk module on the official Magisk repo now says [RE-CONTINUED], so there really isn't much need for me to continue updating this anymore! As a final gift, I ran my batch builder script and built the modded apk's for all variants for the 2021-03-05 patch level, and download link for the module installer is in the OP.
02-02-2021: February 2021 mod is now uploaded. Updated installer is in the link in the OP.
02-01-2021: Modified and uploaded modded SystemUIGoogle.apk files for 3 / 3 XL / 3a / 3a XL to GitHub repository. Updated Magisk installer slightly to accommodate this, and removed a few unnecessary lines. Won't make any difference if you already installed the first release.
i5lee8bit said:
ONLY WORKS FOR PIXEL 4 XL "CORAL" AND PIXEL 4 "FLAME"!!!!
(WON'T EVEN INSTALL ON OTHER DEVICES, SO DON'T BOTHER)
tl;DR - A continuation of the "[Discontinued]Active Edge Mod for Pixel devices" Magisk module on the Magisk Module Repository, discontinued and last released for 2020-12-05 patch level. This is simply the same exact mod applied to the 2021-01-05 patch level. PLEASE DO NOT BOTHER THE ORIGINAL DEV FOR ANY SUPPORT - THIS IS AN UNOFFICIAL MOD.
Click to expand...
Click to collapse
awesome work mate, love this mod. i saw ur post on pixel 4xl forum first and downloaded and flashed that. everything seems 2b working fine! but then i noticed this thread posted seperately on our phone's forum. is there any difference between them?? just wanna make sure that i flashed the rite file. thx again for all mate
vdevl said:
awesome work mate, love this mod. i saw ur post on pixel 4xl forum first and downloaded and flashed that. everything seems 2b working fine! but then i noticed this thread posted seperately on our phone's forum. is there any difference between them?? just wanna make sure that i flashed the rite file. thx again for all mate
Click to expand...
Click to collapse
Yep, you flashed the right file. Both posts link to the same zip file. The module installer, like the original module, gathers your device information and then downloads the correct file for your device and installs it. Even has an MD5 hash checksum check to make sure it's all good before installing. It was actually a really fun little project to work on, and interesting to see how Jan designed it to be semi-automated, with several fail-safe checks. For example, there's a post fs data script to also disable the module automatically if the user upgrades the system patch level and hasn't yet upgraded the module, likely to ensure the systemuigoogle mod isn't incompatible with the new update and potentially cause issues. Really well designed by the original dev!
How do I actually map it? I have installed on my pixel 4xl but it only opens an unusable google assistant UI.

Categories

Resources