*******MAY 2016 UPDATE
Android Pay is working on the PureNexus May 2016 layers build
To attain this, delete the following files
com.google.android.camera2.xml
Located in system/etc/permissions
And
com.google.android.camera2.jar
Located in system/framework
*******BEGIN PRELIMINARY NOTES*******
-->To go from system root to systemless root,
please use the SuperSU Uninstaller zip linked below and not the unroot feature built into the SuperSU app
-->To fully unroot if on systemless root or system root, use the unroot feature in the apk
*******END PRELIMINARY NOTES*******
If, like me, you've become increasingly desirous of having Android Pay functioning on your rooted device, yet preserving that which you love about your custom setup (see thread title), this thread attempts to provide the resources you need to attain your objective.
For me, I believe that the tipping point came as a matter of principle...I wanted a feature from which I'll likely derive zero utility.
Let me be clear: I see no use whatsoever for Android Pay, and yet, like most Americans, I absolutely must have it.
I found myself returning to the same excuse, "I have a debit card, why do I even want this goofy feature?" That's a good question, but the answer is equally obvious...because it exists.
And I'd see yet another user getting the bloody thing to work on a rooted, custom rom. I hope you can see the urgency.
Just like the one ring to rule them all, the lure of Android Pay is really due to its power that it holds over us...
We Wants It...Stupid HOBBITSES
Many users have grown weary of wading through...
-->Disparate posts within rom threads
-->Dedicated threads for various elements of in the title of this thread, now scattered across xda like the diaspora of a lost tribe (how many Viper4android threads are there?)
-->Posts cross-linked within other threads for a given feature
My reticence would again solidify every time I read another post or series of posts about the precise means a given user went about obtaining Android Pay, and the commensurate loss of a different feature...or, no mention of a feature about which I cared.
So this thread is an attempt to redress these issues; specifically, after reading this, you should be able to have...
1.1-1.5. Systemless Root - If Using System Root
1.6. Updating Systemless Root Versions
2. Properly Themed Apps
2a. Hard-coded themed apps
2b. Theme Ready Google Apps
3. Layers
4. Viper4android that does not break your AUX jack or Chromecast
5. Busybox
6. Android Pay
1. Systemless Root
Whether you are running stock, or one of the few AOSP roms claiming to have Android Pay functioning on your device, this is your first step
If you are running a rooted rom, installing a pre-rooted rom, or want to flash a rom that is pre-rooted, to attain Systemless Root, you'll need the following resources...
1.1. The Latest Systemless SuperSU Zip (scroll to the bottom
http://forum.xda-developers.com/showpost.php?p=64161125
1.2. System Root Removal Tool /unSU
http://forum.xda-developers.com/showpost.php?p=63615067
1.3. Busybox for All Devices (scroll down to the section labeled "Busybox Installer")
http://forum.xda-developers.com/showthread.php?t=2239421
1.4. These Two Terminal Commands (have them in a notepad file, on your computer, or just, literally written down on a piece of paper)
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
1.5. To Install Systemless Root
1.5.1. Boot into Recovery
1.5.2. Install Pre-Rooted Rom + Gapps if Needed
1.5.3. Flash unSU Zip
1.5.4. Go to TWRP Main Menu, Go to Advanced, Terminal Command, type each command exactly as above, one at a time), hitting return in between each line
***you'll only do this once if you plan on staying on systemless root
1.5.5. Flash Systemless Root Zip
1.5.6. Flash Busybox Zip
1.5.7. Flash Custom Kernel if Desired
1.5.8. Fix Folder Permissions
-->Boot your device
-->Using Root Explorer or similar app, navigate to the folder labeled "su," as below...
{
"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"
}
-->Then hard press on the folder labeled "bin" and select the pop-up option for permissions, so below...
-->Set permissions to 0751, or deselect the check boxes as below...
1.5.8. Keep Reading, or...
Boot to System if This Is All You Want
1.6. Updating Systemless Root Versions
If you're already running Systemless Root and wish to upgrade to the latest version, follow these steps...
1.6.1. Flash latest version of SuperSU
1.6.2. Flash custom kernel if desired
***Note that if you omit the second step above, and wish to stay on a stock, no force encryption kernel (like one that ships with PureNexus), there is no need to reflash the kernel that came pre-installed with your rom. Just flash the latest version of Systemless Root.
2. Viper4android
2.1. Grab a Zip from the Viper4android Atmos Thread Here (some recommend the Viper4android Atmos Sony Beats Edition...so why the heck not?)...
http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
2.2. Flash in Recovery
3. Properly Themed Apps
If one wants properly themed apps, and since the Gapps packages that allow working Android Pay are minimal, one must add them
3.1. Hard Coded Themed Apps
Using the Team BlackOut Updater (linked below), download those you want and flash in recovery...make sure to grant the app write permissions to your internal SD storage
http://bit.ly/1OcThZg
3.1.1. Download the Gapps that you want, flash in recovery
3.2. Theme Ready Google Apps
Go to this thread, download what you want...
http://forum.xda-developers.com/android/apps-games/apps-themeable-hangouts-layers-cmte-t3113192
3.2.1. Flash is recovery
3.3. All At Once in TWRP, in Sequence
You can and should flash all of these one after the other in TWRP...here are a few reasons why...
3.3.1. If you're using Gmail, and the minimal Gapps doesn't include it, you'll now have it waiting for you upon boot
3.3.2. If you've got a ton of downloaded music from Google Music, it'll still be there waiting for you if you flash Google Music during install (ie, you'll not have to download all of your music again)
3.3.3. Do you really want to set up hangouts, Google Plus (I turn off notifications and sync for this app...why do that every bloody time...), etc?
3.5. Layers
3.5.1. Install the latest version of the layers manager, and install whatever layers your want
3.6. Busybox That Works
You've already done that
3.7. Android Pay
3.7.1. Download from the Play Store, Add Cards
3.7.2. Note that not all cards will work...it's not the fault of the tools you've been given on this site...it's symptomatic of the reality that none of your cards is issued by participating Android Pay partners
4. Test Android Pay
4.1. You can download SafetyNet Helper Sample from the Play Store...
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
The app is temperamental, and can throw up a false negative...but you will get a positive result most all of the time
4.2. Buy a dang soda, pack of gum at CVS, some cheap gift from Walgreens...I don't care from where...to see if it works (it should)
5. Odds & Ends
A few items of note...
5.1. All of your previously apps granted root permission will need so again
5.2. Stay on top of themed apps...layers can never properly theme certain apps if there's a stock version in the data partition of your device.
5.3. Thank all of the devs whose tools are linked in this thread, donate to them, and be sure to buy anything that they may have for sale...they are the best in class.
5.4. Many things may or definitely will break Android Pay, even if you've set it up properly, including Xposed, theme engine, some DPI changing apps, etc. Just be mindful that this could change if you install other items.
6. Credits
@nathanchance, for being such a good dude
@inffy, for being helpful at all times, while maintaining near pitch-perfect, subtle venom
@osm0sis, for just everything he has provided
@BeansTown106, for building his rom, and not just stumbling but actually figuring out what prevented Android Pay from working on his rom
@daveyannihilation, for being such a great guy, themer, forum moderator, and finest pineapple lover I've ever encountered
@Woody, for having done the heavy lifting on most all of this prior to me
Chainfire
Viewers like you that contribute to Public Television...thanks for your support
Good luck!
Solid work! Gonna add it to my signature and I will add it to my posts as soon as I can.
Great post, and thanks for the mention!
Venom indeed flings in my veins
Thanks for posting this. Curious what everyone is using in terms of Viper Audio? I just flashed the Huawei one for now.
Subiegsr said:
Thanks for posting this. Curious what everyone is using in terms of Viper Audio? I just flashed the Huawei one for now.
Click to expand...
Click to collapse
I am using the all-in-one package by @guitardedhero
Please link to my thread, not my zip. Thanks.
osm0sis said:
Please link to my thread, not my zip. Thanks.
Click to expand...
Click to collapse
Yes sir...taken care of it.
My apologies.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
Awesome Post. Really covers everything that has been asked over and over, all in one easy to read format.
On Viper: In my testing, I made several backups at each stage after I checked that AP was working. I am glad that I did, as some Viper packages break Pay functionality. I would stress caution and/or patience when flashing, as a backup only takes a few seconds to make, but can save a whole bunch of time. The Viper package that I have linked above is an older one from the N6-Proper device, so it requires Permissive. You are free to use whatever you want, but this works for me. I flashed XTREMEmusic 6.0, 6.2 and 7.3 and all 3 broke Pay. It has been noted that Guitaredhero's zip package works, doesn't break Pay and sounds pretty good. Your choice.
Me from another thread said:
As an aside, I have an almost completely stripped down /system partition as far as gapps go and have even substituted several TBO ThemeReady versions, as well as Clear YouTube. So if I were to put a wager on what trips the Pay failure [I am speaking in systemless root terms], I would lay bets on system/bin, /system/xbin, busybox configurations and changes to some shadow policy that no one has figured out. Because simply adding or removing apks from /system (not including any signature checked apks such as a modified GMusic or Chrome) and utilizing the /su folder correctly doesn't trip the Pay verification, at least not for me.
Click to expand...
Click to collapse
Thanks
Bookmarked in my tips folder.
I'm sure I'll refer to it many times.
viper4android link is down
Sent from my Nexus 6P using Tapatalk
Most excellent! U Rock on XDA!!
galaxys said:
Most excellent! U Rock on XDA!!
Click to expand...
Click to collapse
For so long you've had the Oregon Ducks cheerleaders in your signature. Good to see your "affection" for the cheer spans to other schools.
Woody said:
For so long you've had the Oregon Ducks cheerleaders in your signature. Good to see your "affection" for the cheer spans to other schools.
Click to expand...
Click to collapse
This is true...LOL! I'll continue to scout the teams!
galaxys said:
This is true...LOL! I'll continue to scout the teams!
Click to expand...
Click to collapse
Sometimes looking at the forums via browser really has its advantages.
I'm so glad I looked at this exchange...I'm quite thankful for those cheerleaders...they really want me to have my device exactly as I like it.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
Woody said:
Awesome Post. Really covers everything that has been asked over and over, all in one easy to read format.
On Viper: In my testing, I made several backups at each stage after I checked that AP was working. I am glad that I did, as some Viper packages break Pay functionality. I would stress caution and/or patience when flashing, as a backup only takes a few seconds to make, but can save a whole bunch of time. The Viper package that I have linked above is an older one from the N6-Proper device, so it requires Permissive. You are free to use whatever you want, but this works for me. I flashed XTREMEmusic 6.0, 6.2 and 7.3 and all 3 broke Pay. It has been noted that Guitaredhero's zip package works, doesn't break Pay and sounds pretty good. Your choice.
Click to expand...
Click to collapse
Great summary - Thanks!
I've had no issues with AndroidPay when I've used Guitaredhero's zip package - highly recommend going that route if you want V4A. Besides, the sound is considerably better with V4A and Dolby Atmos than without!
The gotcha I had for breaking Android Pay - was not removing the SU/XBIN_BIND directory (or avoiding the creation by making the appropriate entry to the .supersu file) When I jumped from SUPERSU 2.61 to 2.66 - I had missed that step.
Also - unless you need BusyBox - (V4A doesn't need it and my understanding is Layers won't in the future) - you may want to leave it out until you have an app that requires it)
luigidk said:
Great summary - Thanks!
I've had no issues with AndroidPay when I've used Guitaredhero's zip package - highly recommend going that route if you want V4A. Besides, the sound is considerably better with V4A and Dolby Atmos than without!
The gotcha I had for breaking Android Pay - was not removing the SU/XBIN_BIND directory (or avoiding the creation by making the appropriate entry to the .supersu file) When I jumped from SUPERSU 2.61 to 2.66 - I had missed that step.
Also - unless you need BusyBox - (V4A doesn't need it and my understanding is Layers won't in the future) - you may want to leave it out until you have an app that requires it)
Click to expand...
Click to collapse
Thanks for your input, and sharing your personal experience. This kind of feedback is especially helpful.
As to removing Busybox from the list, at the moment, many Viper4android packages are compatible with Android Pay, and require Busybox...for example, even though I linked one that seems pretty popular, others work, and folks may need Busybox in order to use certain Viper4android packages.
As to the new Layers Manager not requiring Busybox, I'll definitely note that once the app goes from alpha stage to final release.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
luigidk said:
Great summary - Thanks!
I've had no issues with AndroidPay when I've used Guitaredhero's zip package - highly recommend going that route if you want V4A. Besides, the sound is considerably better with V4A and Dolby Atmos than without!
The gotcha I had for breaking Android Pay - was not removing the SU/XBIN_BIND directory (or avoiding the creation by making the appropriate entry to the .supersu file) When I jumped from SUPERSU 2.61 to 2.66 - I had missed that step.
Also - unless you need BusyBox - (V4A doesn't need it and my understanding is Layers won't in the future) - you may want to leave it out until you have an app that requires it)
Click to expand...
Click to collapse
Can you link to that zip? It seems the link in the OP is down. Thanks.
Sent from my Nexus 6P using Tapatalk
micmars said:
Thanks for your input, and sharing your personal experience. This kind of feedback is especially helpful.
As to removing Busybox from the list, at the moment, many Viper4android packages are compatible with Android Pay, and require Busybox...for example, even though I linked one that seems pretty popular, others work, and folks may need Busybox in order to use certain Viper4android packages.
As to the new Layers Manager not requiring Busybox, I'll definitely note that once the app goes from alpha stage to final release.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
Click to expand...
Click to collapse
The V4A package at this forum: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137 doesn't require busybox, so that is just an option. Best V4A install out there in my opinion.
---------- Post added at 04:06 PM ---------- Previous post was at 04:05 PM ----------
darkjedi said:
Can you link to that zip? It seems the link in the OP is down. Thanks.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
For V4A? If so it is here: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
darkjedi said:
Can you link to that zip? It seems the link in the OP is down. Thanks.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
The links in the OP all work for me...
http://forum.xda-developers.com/showthread.php?t=2952137
ViPER|Audio || ViPER|Atmos 4.1 * SQ Driver * Audiophile Profile * Beats * Huawei *
They are direct downloads at the bottom of the OP...
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
luigidk said:
The V4A package at this forum: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137 doesn't require busybox, so that is just an option. Best V4A install out there in my opinion.
---------- Post added at 04:06 PM ---------- Previous post was at 04:05 PM ----------
For V4A? If so it is here: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
Click to expand...
Click to collapse
Excellent...I'll add this to the OP, along with the one provided by Woody.
Do you mind telling me...
1. The rom you're running
2. The kernel you're on
3. If you're SELinux is set to permissive or enforcing
Many thanks.
Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
Ainur JamesDSP is now available in Magisk Manager. Thanks to the devs for their great work. Enjoy!
Not working on pixel xl with magisk 14.3. Repeatedly showing the app has shut down unexpectedly. And then my system started an automatic factory wipe (good thing I forced shut down before the wipe started)
biribiribiri said:
Not working on pixel xl with magisk 14.3. Repeatedly showing the app has shut down unexpectedly. And then my system started an automatic factory wipe (good thing I forced shut down before the wipe started)
Click to expand...
Click to collapse
Yikes. I wonder if AML doesn't support Pixel yet. I will look into it and add a note to the OP. Thanks for the heads up.
biribiribiri said:
Not working on pixel xl with magisk 14.3. Repeatedly showing the app has shut down unexpectedly. And then my system started an automatic factory wipe (good thing I forced shut down before the wipe started)
Click to expand...
Click to collapse
By the way, were you running any other audio mods at the time?
s8m said:
By the way, were you running any other audio mods at the time?
Click to expand...
Click to collapse
no
I am getting a blank screen when opening jamesDSP upon flashing and rebooting. Then if I got to recovery and wipe cache and dalvik and reboot it just does a constant FC, over and over. I provided a log through ADB. I am running ABC ROM, Android O, Angler. As you can also see I have audmodlib and ainur audio as well. Also, before I wiped cache and dalvik and the JamesDSP screen was just blank it did show in notification. Basically, Not working at all here. Thanks for the work bud. The first link is the constant FC with ADB, and the second link is Matlog with the blank JamesDSP screen when opening.
https://haste.blamealexcruz.com/WoNVF1m7XX.swift
https://haste.blamealexcruz.com/8EdpzPLtrU.pl
yung40oz84 said:
I am getting a blank screen when opening jamesDSP upon flashing and rebooting. Then if I got to recovery and wipe cache and dalvik and reboot it just does a constant FC, over and over. I provided a log through ADB. I am running ABC ROM, Android O, Angler. As you can also see I have audmodlib and ainur audio as well. Also, before I wiped cache and dalvik and the JamesDSP screen was just blank it did show in notification. Basically, Not working at all here. Thanks for the work bud. The first link is the constant FC with ADB, and the second link is Matlog with the blank JamesDSP screen when opening.
https://haste.blamealexcruz.com/WoNVF1m7XX.swift
https://haste.blamealexcruz.com/8EdpzPLtrU.pl
Click to expand...
Click to collapse
Thanks - very helpful! Looking quickly at your logcat this may be related to libjamesDSPImpulseToolbox.so being placed inside /system/lib/ instead of /system/lib64/ (my device is ARM64 but accepts /system/lib/). I'll look into a workaround and update this in next build.
s8m said:
Thanks - very helpful! Looking quickly at your logcat this may be related to libjamesDSPImpulseToolbox.so being placed inside /system/lib/ instead of /system/lib64/ (my device is ARM64 but accepts /system/lib/). I'll look into a workaround and update this in next build.
Click to expand...
Click to collapse
Great! Looking forward to it.
When users provide logs...
I already submitted this to the repo. Why are you posting our module as yours? V1.1 is BETA. There's a reason why it is unreleased.
Please have this thread removed. You're going to cause issues for other users, which is already happening.
ahrion said:
I already submitted this to the repo. Why are you posting our module as yours? V1.1 is BETA. There's a reason why it is unreleased.
Please have this thread removed. You're going to cause issues for other users.
Click to expand...
Click to collapse
I'm confused... this is built off a fork of your AM3D repo but my fork is not your repo. V1.1-beta is the version I created. Like the OP says I created this module, combining your AML/Unity framework and james34602's JamesDSPManager.
If you are working on a JamesDSPManager module that is news to me (hence why I made this module). If you are working on a module that is also v1.1-beta that is quite a coincidence! Are you saying you don't want other devs building off of your AML library and sharing with the community? I thought that was welcome (you are planning a template after all) but I will remove this module if you would rather control development.
s8m said:
I'm confused... this is built off a fork of your AM3D repo but my fork is not your repo. V1.1-beta is the version I created. Like the OP says I created this module, combining your AML/Unity framework and james34602's JamesDSPManager.
If you are working on a JamesDSPManager module that is news to me (hence why I made this module). If you are working on a module that is also v1.1-beta that is quite a coincidence! Are you saying you don't want other devs building off of your AML library and sharing with the community? I thought that was welcome (you are planning a template after all) but I will remove this module if you would rather control development.
Click to expand...
Click to collapse
Ahhhh. I didn't check the GitHub repo. I thought you just built the thread with my GitHub repo (which I submitted through Magisk).
That's so weird lol.
You're good then, but using the latest sources will cause things to be wonky with the current stable version of the other mods. It will cause FC all day.
False alarm. Sorry about that! I'm still gonna make a thread for this however.
ahrion said:
Ahhhh. I didn't check the GitHub repo. I thought you just built the thread with my GitHub repo (which I submitted through Magisk).
That's so weird lol.
You're good then, but using the latest sources will cause things to be wonky with the current stable version of the other mods. It will cause FC all day.
False alarm. Sorry about that! I'm still gonna make a thread for this however.
Click to expand...
Click to collapse
OK no worries! That's a good point that using unreleased sources can cause other unwanted problems. I will take this down if you are creating a separate thread. It's probably better for everyone if you are able to manage the development of AML modules.
s8m said:
OK no worries! That's a good point that using unreleased sources can cause other unwanted problems. I will take this down if you are creating a separate thread. It's probably better for everyone if you are able to manage the development of AML modules.
Click to expand...
Click to collapse
It's up to you man. I submitted the stuff yesterday to the Magisk repo, along with a V4A as well as Unity Xposed.
Since you're looking from outside, in. Was Unity easy to configure for you? The entire point for AML is to link everything to together for Magisk. Then we created Unity to be an all in one installer. Any AML modules are encouraged and welcome. Ainur is running AML currently.
Yeah I must say Unity is really well done. I've only ever done very simple Magisk modules (for personal use) so I may not be the best judge, but there wasn't much learning curve at all with Unity. The way the patching and multi-arch handling is set up is really intuitive and logical. This module was really simple to create compared to your ViPER4Android module but it was nice not to have to think about modifying the install-binary or add custom sed commands. All in all - #impressed !
s8m said:
Yeah I must say Unity is really well done. I've only ever done very simple Magisk modules (for personal use) so I may not be the best judge, but there wasn't much learning curve at all with Unity. The way the patching and multi-arch handling is set up is really intuitive and logical. This module was really simple to create compared to your ViPER4Android module but it was nice not to have to think about modifying the install-binary or add custom sed commands. All in all - #impressed !
Click to expand...
Click to collapse
Awesome. You can thank @Zackptg5
Another addition is SETools-inject for Android, that functions like sepolicy inject that MagiskSU/SuperSU have. Essentially, it allows rootless and other forms of root to also use it via init.d. As of yet, no one has actually used SETools for this.
We've also added init.d patching, for rootless and other root methods. Essentially, ramdisk will be automatically patched for AML system modules to use init.d (even if your rom didn't support it before). So init.d patch for all Android versions, MM/N+, has been added. Currently nearly all (if not all) init.d support is broken.
ahrion said:
I already submitted this to the repo. Why are you posting our module as yours? V1.1 is BETA. There's a reason why it is unreleased.
Please have this thread removed. You're going to cause issues for other users, which is already happening.
Click to expand...
Click to collapse
I hope your mod will be in the repo soon, topjohnwu has been very picky with your soubd mods.
24imelqui said:
I hope your mod will be in the repo soon, topjohnwu has been very picky with your soubd mods.
Click to expand...
Click to collapse
It's not that he has been picky. It's just it takes some time to get approved.
Topjohnwu is a busy man.
BTW, Unity allows system mode installation natively if Magisk is not installed, includes addon..d as well.
Magisk is not required for any Unity zips.
ahrion said:
It's up to you man. I submitted the stuff yesterday to the Magisk repo, along with a V4A as well as Unity Xposed.
Click to expand...
Click to collapse
It may be a dumb question, but does your Ainur JamesDSP module require Ainur or can it run independently without Ainur installed?
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.