nope lol I give up after being connected to wifi hotspot thanks anyway
Nope.
- Thread starter TotallyAnxious
- Start date
- Status
I can't change the fundamental requirements of a Google product.
Any tricks to get dark assistant working? i have everything installed, call screening seems to work, but my asisstant is still the original assistant.
If coming from another kernel other than kiri, is it okay to leave the anxious magisk modules enabled and flash kiri without the kiri companion module?
cleared google app data and it seems to be working now...
Probably but you might as well flash a stock.img via twrp backup or the boot.img from somewhere. Completely eliminate the possibility of compatibility issues.
Lol (hic)
---------- Post added at 04:21 AM ---------- Previous post was at 04:21 AM ----------
Sorry... too much tequila
For anyone, has
1) call screen disappeared and
2) EX Kernel Manager sees the phone as OnePlus7Pro instead if Google Pixel 3
after installing v140.
EXKM used to see the phone as Google Pixel 3 before v140. I have removed and reinstalled these modules to be sure.
1) call screen disappeared and
2) EX Kernel Manager sees the phone as OnePlus7Pro instead if Google Pixel 3
after installing v140.
EXKM used to see the phone as Google Pixel 3 before v140. I have removed and reinstalled these modules to be sure.
This is me not raining down fury. Lol
v140 only metastasizes pre-existing cancer and has updates to the script.
It's clearly an issue on your end.
Attachments
I dont know what to say. I HAVE removed then reinstalled the modules. Only thing I have different is Elemental Kernel instead of Freak's kernel.This is me not raining down fury. Lol
v140 only metastasizes pre-existing cancer and has updates to the script.
It's clearly an issue on your end.
Any pointers?
Check Magisk log, do you have two modules editing the same build prop lines and the one from this module is being overwritten? Does this module get applied at all?
And clarifying, you removed the module by flashing it again in Magisk, right? Not just the delete button? Because it's using the unity template and all modules that use that need to be flashed again for the uninstaller script to run.
Sent from my Pixel 3 using Tapatalk
(Hey it's working lol) ^
Last edited:
If an installed module isn't working, is it truly installed? *Mind blow*
Acceptable snarky response is "was the module ever truly working?"
And then I can have one of my drug fueled freak outs as usual.
No idea. It's different from my set up. So I have no way of knowing what's going on.
Figured it out. The "Auxiliary Lens in GCam by xtrme" magisk module was conflicting. If any one can help me make these two work together, I will really appreciate it.
I'll take a look, can you send me the link to that module? (PM)
Sent from my Pixel 3 using Tapatalk
v141
GCam aux lens
@mwilky did it not me.
Hasn't actually replied to me saying I can use it lol might as well call me TotallyKanger lolol
GCam aux lens
@mwilky did it not me.
Hasn't actually replied to me saying I can use it lol might as well call me TotallyKanger lolol
That's odd, I have that exact same module and everything works fine with v140. Maybe it's the kernel you have installed.
- Status
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone