Related
Hi all,
With Xposed just released for Lollipop I was hoping we could start a thread on experiences thus far. I'm reading conflicting user reports that it actually works on the Shield tablet and was hoping we could consolidate our findings her.
I'll be giving it a go later tonight.
Mods, if this if in the wrong forum please feel free to move.
Not sure if this is the right forum for a post like this but..
It works. I installed it on my tablet. Your module mileage may vary depending on the modules. Some things in gravity box work, some don't etc... You're gonna need to test stuffs. As always, make a backup before installing xposed!
So far so good. I'm getting the standard "Xposed is not installed error,"
but I read it is a GUI glitch due to the way the alpha build was created. I'm using ADM+, YouTube AdAway and BootManager and don't notice any major issues yet.
I've got it installed as well. Burnt Toast, CrappaLinks, and Play Store Changelog all seem to work. It's interesting that the Lollipop Xposed thread has a ton of posts about needing to put SELinux in permissive mode followed by a soft reboot in order to get Xposed to work. I did not need to do that. SELinux is set to enforcing but Xposed is working from what I can tell
I'm using Xgels and youtube adaway. Its running fine with no reboots or crashes.
I previously had tested out gravity box for notification toggles, but as I expected, its not working. I also previously had the phab7 module installed to play with the dpi, but it doesn't seem to stick through a reboot and I was only looking to get the fullscreen notif pulldown, but I can live without so i uninstalled.
I have SELinux in permissive due to Viper4Android.
Gilbot, what DPI are you looking to use? Is there a huge benefit in altering?
Works fine for me in both permissive and enforcing.
has anyone had any success with xprivacy 3.6.6? I'm running superpichu's kernel which is supposed to have SELinux set to permissive, and indeed selinux mode changer shows it as permissive without me doing anything. The problem is when i install xprivacy and activate/reboot, i get stuck in the boot screen.
sixstringedmatt said:
I have SELinux in permissive due to Viper4Android.
Gilbot, what DPI are you looking to use? Is there a huge benefit in altering?
Click to expand...
Click to collapse
I never really messed with this tablet's dpi, but I am not sure if I dig the notification pulldown width, I feel like I want more touch room and width for notifications to include more info. Its a minor thing though and I'm fine without it.
Fair enough. Let me know if you ever do some experimenting. I'm also interested about what's gained with adjusted DPI.
FYI. I tried Xposed for the 1st time and liked it. But while using gravity box (which I also really liked) my shield CONTROLLER was acting funny.
The mapping got all screwed up and the mapping app stopping working (error message) when you hold down start on controller and click the little cloud icon to download mappings.
Anyway had to del gravity box and just did away with Xposed for now.
And now controller works fine. Weird....
Anyone else having issues with the controller using Xposed moduels?
Sent from my SHIELD Tablet using XDA Free mobile app
Hi,
I had installed xposed alpha and a few modules. I had issues with it not going to sleep, and now it wouldn't turn the screen back on so I had to hard-reboot it.
How do I go about uninstalling XPosed? I did a full TWRP backup before I did xposed, if that matters.
ejohn said:
Hi,
I had installed xposed alpha and a few modules. I had issues with it not going to sleep, and now it wouldn't turn the screen back on so I had to hard-reboot it.
How do I go about uninstalling XPosed? I did a full TWRP backup before I did xposed, if that matters.
Click to expand...
Click to collapse
Restoring that backup will get rid of it.
FoxyDrew said:
Restoring that backup will get rid of it.
Click to expand...
Click to collapse
Thanks for the quick reply. Do I have to wipe first? I haven't done backups or restores in a long, long time. Like, Droid Incredible was my last modded phone. Heh.
ejohn said:
Thanks for the quick reply. Do I have to wipe first? I haven't done backups or restores in a long, long time. Like, Droid Incredible was my last modded phone. Heh.
Click to expand...
Click to collapse
Ha, I loved my Incredible. But yeah do a full wipe then restore.
I had to uninstall xposed. Massive battery drain. Couldn't root cause the issue definitively, but once I uninstalled battery is back to normal.
I'll wait for a more stable framework in the future.
My experience on Xposed
Hello guys
I have installed xposed on my shield tablet, it's work but it's difficult ( i have many bug on boot )
if i reboot whien i install a new module. the shield crash on boot i have dark scrren. reboot it's ok
!!!! I recommend to those who want to make their experience of waiting for a stable version !!!!
I'm curious on trying xposed, but I'm a little worried as it's not stable yet.
Where do I get it from?
burt_ie said:
I'm curious on trying xposed, but I'm a little worried as it's not stable yet.
Where do I get it from?
Click to expand...
Click to collapse
From here.
I had no problems so far. Only one module (awesome pop up video - twitch addon) is not working, it just F/C.
So, if you ask me, its perfectly fine. But it probably denpends on the moduls you want to install.
I have shield tablet LTE which installer do I use?
Arm, arm64, x86?
Thanks in advance I've been trying to figure this out before flashing.
Has anyone taken the recent magisk/superuser upgrades and been able to keep safetynet passing?
squandry said:
Has anyone taken the recent magisk/superuser upgrades and been able to keep safetynet passing?
Click to expand...
Click to collapse
If it's in the context of getting pokemon go working, I think this might help get what you need: https://www.reddit.com/r/TheSilphRo...around_for_the_pokémon_go/?sort=new&limit=500
squandry said:
Has anyone taken the recent magisk/superuser upgrades and been able to keep safetynet passing?
Click to expand...
Click to collapse
It's working for me with android pay.
Safetynet is passing for me using Magisk v9 & phh's Superuser r266-2, but a new version of each was released last week that chatter in other forums seem to suggest device-specific trouble with. I might try but first wanted to know if anyone else in the LePro3 world already has and had problems. My current interest in safetynet is for Android Pay and DirectvNow.
suhridkhan said:
It's working for me with android pay.
Click to expand...
Click to collapse
Thanks!
robertzas said:
If it's in the context of getting pokemon go working, I think this might help get what you need: https://www.reddit.com/r/TheSilphRo...around_for_the_pokémon_go/?sort=new&limit=500
Click to expand...
Click to collapse
Linked method is outdated ever since the introduction of November security patch.
Magisk V10 and phh SU r266 working fine for me on 20s
Upgrading worked for me too and I like how safety net check is part of the new status screen.
Seems like known issue but installing Xposed caused safetynet to fail, both before and after upgrade. Uninstalling Xposed caused safety net to pass again.
Root working and safetynet still passing on my x727 after taking the Magisk Manager upgrade to Magisk 11.1 and MagiskSu.
are all of you on a stock ROM and bootloader locked, I am using lineage OS 13, but safety net fails? do you have any idea how to fix this, just wanted to use ANDROID PAY, or do I need to be on STOCK ROM, just don't like the EUI and the status bar icons and the way they look(it's just me). Any help would greatly be appreciated=)
I am on stock ROM and unlocked bootloader. Magisk lets the unlocked bootloader stay. I don't see how safetynet could be expected to fully pass on a non-OEM supported ROM, especially over the longhaul of the cat-and-mouse game.
I don't like EUI either but changing out the launcher and even the notifications pulldown with Play Store apps helps immensely, along with using Titanium to freeze the bloatware. The main EUI remnants left after that is the lockscreen, the settings application, and the recents screen which I tolerate so as to have safetynet.
I could not pass safety net, got CM13, with MAGISK installed. Dang=)
squandry said:
I am on stock ROM and unlocked bootloader. Magisk lets the unlocked bootloader stay but I don't see how safetynet could ever pass on a custom ROM.
I don't like EUI either but changing out the launcher and even the notifications pulldown with Play Store apps helps immensely, along with using Titanium to freeze the bloatware. The main EUI remnants left after that is the lockscreen and the recents screen which I tolerate so as to have safetynet.
Click to expand...
Click to collapse
Hi, Did this but after installing MAGISK, everything passed, except FINGERPRINT got disabled, says hardware not supported. Android Pay works,just went to gas station and tried it, works flawlessly. FINGERPRINT is the problem I'm seeing now. Thanks for any help.
Sent from my LEX727 using XDA-Developers Legacy app
You mean you can't use the fingerprint sensor to unlock your phone? I am not sure, that works fine for me.
squandry said:
You mean you can't use the fingerprint sensor to unlock your phone? I am not sure, that works fine for me.
Click to expand...
Click to collapse
Yup, what boot image did you install? I think the problem was the boot image I used, are you on the 20's now? thanks
I am running the aboot from dr4stic's 19s unlocked bootloader zip, everything else is from the stock 20s OTA zip.
Ok, I have spent several hours trying to make it work and now time to ask for help. I got Leeco LePro 3 with custom Ron based on EUI, and trying to get Magisk working. First I tried installing system less SuperSU and Magisk, but it failed safety check multiple times, so I tried uninstalling SuperSU and use Magisksu, but not I am not able to move forward. I installed Magisk manager and when it try to install Magisk manager it downloads but doesn't show way to install it, I even try flashing Magisk 12 zip using TWRP, but it fails to update. Can someone please help me with getting Magisk working with safety check?
bocondo said:
I even try flashing Magisk 12 zip using TWRP, but it fails to update. Can someone please help me with getting Magisk working with safety check?
Click to expand...
Click to collapse
Flashing Magisk with TWRP should work. What do you mean by it fails to update?
I finally found a ROM for this GD phone that fully connects to my Bluetooth deck. Yay! All other ROMs besides stock and PureNexus would say "Connected (no phone). However Xposed is not working. The Xposed Installer (v3.14) says that Xposed version 89 is installed, but not active. This is my first time trying Xposed on Nougat. I've used Xposed on all previous Android versions (since the inception of Xposed). Never had this issue. The installer says to check the logs. When I tried it says that it can't read the log (no such file or directory). I'm so sick of effing with this phone. I'm still using my OnePlus One because I can't find a ROM that has fully working Bluetooth that isn't the crappy stock ROM or PureNexus (PureNexus is unfinished and abandoned). Somebody, anybody...how the eff do I get Xposed to work?
What I did:
-Full wipe (dalvik, system, data, cache)
-Flash latest PureFusion (13NOV2017)
-Flash SuperSu v2.82
-Flash OpenGapps (pico)
-First boot
-Install Xposed installer v3.14
-Reboot to recovery
-Flash Xposed v89
I've also tried using the install option from within the installer. No joy. Changed SuperSu options to be more compatible and less safe (namespace speration, trust system user, enable su during boot). No Joy.
I'm about to smash this phone with a hammer. Finally found a ROM that sorts Bluetooth and now Xposed doesn't work. Next time I'll check XDA first before buying a phone to check the current status of development.
Edit: I'd like to avoid using Magisk if possible. I can't remember which root apps, but there are some that don't work with Magisk (last I checked).
Edit 2: Tried the following without success. Exact same results. A msg on the status screen saying Xposed is installed but not active:
-Unity version of Xposed
-Magisk 14.0 + systemless Xposed framework
-Probably something else I'm forgetting
I created the missing log file and gave it the appropriate permissions but nothing ever got written to it. I suppose I could do a logcat but I can't be bothered. If Xposed doesn't work out of the box for this particular ROM I'm not going any further with it. I posted this question in the ROM thread as well.
Doc Ames said:
I finally found a ROM for this GD phone that fully connects to my Bluetooth deck. Yay! All other ROMs besides stock and PureNexus would say "Connected (no phone). However Xposed is not working. The Xposed Installer (v3.14) says that Xposed version 89 is installed, but not active. This is my first time trying Xposed on Nougat. I've used Xposed on all previous Android versions (since the inception of Xposed). Never had this issue. The installer says to check the logs. When I tried it says that it can't read the log (no such file or directory). I'm so sick of effing with this phone. I'm still using my OnePlus One because I can't find a ROM that has fully working Bluetooth that isn't the crappy stock ROM or PureNexus (PureNexus is unfinished and abandoned). Somebody, anybody...how the eff do I get Xposed to work. $20 to whoever provides me with the solution.
What I did:
-Full wipe (dalvik, system, data, cache)
-Flash latest PureFusion (13NOV2017)
-Flash SuperSu v2.82
-Flash OpenGapps (pico)
-First boot
-Install Xposed installer v3.14
-Reboot to recovery
-Flash Xposed v89
I've also tried using the install option from within the installer. No joy. Changed SuperSu options to be more compatible and less safe (namespace speration, trust system user, enable su during boot). No Joy.
I'm about to smash this phone with a hammer. Finally found a ROM that sorts Bluetooth and now Xposed doesn't work. Next time I'll check XDA first before buying a phone to check the current status of development.
Edit: I'd like to avoid using Magisk if possible. I can't remember which root apps, but there are some that don't work with Magisk (last I checked).
Click to expand...
Click to collapse
Try Magisk 14.0, install the module, download the modified apk from the module download tab, install the app, see if it works
Edit: I just read the last line, sorry
that is the only thing that i've thought about. Stock is the other way around, normal method works but topjohnwu's module doesn't. But Magisk xposed worked on every custom ROM I've used.
Choose an username... said:
Try Magisk 14.0, install the module, download the modified apk from the module download tab, install the app, see if it works
Edit: I just read the last line, sorry
that is the only thing that i've thought about. Stock is the other way around, normal method works but topjohnwu's module doesn't. But Magisk xposed worked on every custom ROM I've used.
Click to expand...
Click to collapse
I would have ultimately tried Magisk anyways if all else failed. I will try later. Probably tomorrow. If it works I'll call it solved and you get the prize.
Doc Ames said:
I would have ultimately tried Magisk anyways if all else failed. I will try later. Probably tomorrow. If it works I'll call it solved and you get the prize.
Click to expand...
Click to collapse
Nah don't want any price. a thank is enough
Which are the apps that don't work with Magisk?
@Doc Ames: it's probably just the ROM you've chosen. I've tried lots of Lineage/AOSP ROMs for the A7, Xposed has worked flawlessly in all of them.
My setup:
Vertex Carbide
Hellsgate EAS kernel, with data and cache formatted as F2FS
Phh's Superuser, for root
Busybox 1.27.2 by YashadSaraf
Xposed v89 official
No GApps, except MicroG and Play Store
I try to avoid Magisk, it's a nice concept, but systemless is more trouble than it's worth. Magisk has caused me tons of issues. I've tried it off and on for months but I keep switching back to good ol reliable Phh. I stopped using SuperSU ever since it was bought by an Asian (Chinese?) company.
Good luck!
Choose an username... said:
Nah don't want any price. a thank is enough
Which are the apps that don't work with Magisk?
Click to expand...
Click to collapse
I don't remember. If for some reason I have to use Magisk maybe I can find replacement apps.
AnonVendetta said:
@Doc Ames: it's probably just the ROM you've chosen. I've tried lots of Lineage/AOSP ROMs for the A7, Xposed has worked flawlessly in all of them.
My setup:
Vertex Carbide
Hellsgate EAS kernel, with data and cache formatted as F2FS
Phh's Superuser, for root
Busybox 1.27.2 by YashadSaraf
Xposed v89 official
No GApps, except MicroG and Play Store
I try to avoid Magisk, it's a nice concept, but systemless is more trouble than it's worth. Magisk has caused me tons of issues. I've tried it off and on for months but I keep switching back to good ol reliable Phh. I stopped using SuperSU ever since it was bought by an Asian (Chinese?) company.
Good luck!
Click to expand...
Click to collapse
Thank you for the suggestion. The issue is that there is no other ROM for the A7 (save PureNexus and stock ROMs) that will properly connect to my Bluetooth deck. I was trying to pursue a solution to the Bluetooth issue with custom ROMs for the A7 but it affects such a small number of users that nobody seems to think it's an issue. I tried the ROM you are using and had the above mentioned Bluetooth issue. I've tried a ton of ROMs. I'd rather get a fix to the Bluetooth issue so I can use whatever ROM I want. However, I posted a question about my Bluetooth issue and everybody just gave me the whole, "It's working on my machine. Must be your deck."
@Doc Ames: Well sorry to know that you're essentially forced to used a specific rom just to get your Bluetooth deck working. I don't use Bluetooth for anything but transferring files, that's worked in every ROM I've tried. But I have had issues in the past where a certain device would work on one ROM but not on another. It could be a ROM issue, or maybe an issue with the Bluetooth device you're using. Maybe a combo of both. I'm not a dev so there's nothing I can do except be sympathetic. Maybe you can elevate your issue with A7 devs so they can maybe look into whether there are underlying Bluetooth issues in their ROMs that need to be resolved. If the deck didn't cost too much, you might want to look into selling it and getting a more known, compatible deck that works with most ROMs. I guess it all just depends on how much it's worth to you to be able to run whatever ROM you want without worrying about whether your deck will work.
Good luck!
@Doc Ames,
If you haven't yet, give the UNITY Xposed package (by @ahrion) a try. On my G3 I had nothing but troubles trying to get Xposed and ParanoidAndroid working. With UNITY everything came together to my surprise.
Also just flashed it tonight on the Axon B32 stock. Far as other ROMs go I've used both unofficial and official Xposed on various ROMs like VertexOS and Dark ROM without issue.
I too stay away from Magisk so I can't speak to any of the systemless installers.
http://forum.xda-developers.com/showthread.php?t=3697756
[12/18/2017] Xposed Framework v88.9 [UNITY]
LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
marcdw said:
@Doc Ames,
If you haven't yet, give the UNITY Xposed package (by @ahrion) a try. On my G3 I had nothing but troubles trying to get Xposed and ParanoidAndroid working. With UNITY everything came together to my surprise.
Also just flashed it tonight on the Axon B32 stock. Far as other ROMs go I've used both unofficial and official Xposed on various ROMs like VertexOS and Dark ROM without issue.
I too stay away from Magisk so I can't speak to any of the systemless installers.
http://forum.xda-developers.com/showthread.php?t=3697756
[12/18/2017] Xposed Framework v88.9 [UNITY]
LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
Click to expand...
Click to collapse
Thank you for the suggestion. I tried the UNITY Xposed. No joy. Same result.
Hello guys,
Please accept my apologies if this topic was asked/discussed in other threads. I was unable to find an answer to this question with my searches.
For a while now, I have noticed that Magisk fails SafetyNet on Nougat stock ROM. If my memory serves me, it started with v16.0 and now with beta ver. 16.2 the issue is still ongoing.
Has anyone found a way to pass SafetyNet for stock ROM?
P.S. I have noticed that in Magisk Manager settings, the option "Magisk Hide" disables itself after reboot, I assume something prevents it from working properly (???).
Thanks a lot in advance,
Catalin D
I've been having the same issue and got no solutions other than using 15.3.
Isopropil said:
I've been having the same issue and got no solutions other than using 15.3.
Click to expand...
Click to collapse
Better than no solution at all!
I can confirm the same results. I went ahead and tried all versions from 15.3 to 16.3 - only 15.3 works.
Unfortunately that version is lacking something for me at least... Have you been able to get modules working in 15.3?
They fail to install directly from Magisk Manager. When I try to do it manually in TWRP, I get no errors but the modules are not there when I boot back into the system.
There's clearly some problems we're having that other devices aren't... And the fact that these problems seem to be handled silently doesn't help.
MelloZ said:
Better than no solution at all!
I can confirm the same results. I went ahead and tried all versions from 15.3 to 16.3 - only 15.3 works.
Unfortunately that version is lacking something for me at least... Have you been able to get modules working in 15.3?
They fail to install directly from Magisk Manager. When I try to do it manually in TWRP, I get no errors but the modules are not there when I boot back into the system.
There's clearly some problems we're having that other devices aren't... And the fact that these problems seem to be handled silently doesn't help.
Click to expand...
Click to collapse
I am also using 15.3 magisk with 5.5.5 manager and I have no issues. I have systemiser, debloater, busybox, greenify. the only mod that seems to be not working îs YouTube vanced. I uninstalled the system YouTube and the mod seems unable to install its version.
rzarectha said:
I am also using 15.3 magisk with 5.5.5 manager and I have no issues. I have systemiser, debloater, busybox, greenify. the only mod that seems to be not working îs YouTube vanced. I uninstalled the system YouTube and the mod seems unable to install its version.
Click to expand...
Click to collapse
Works fine here w/ same Magisk & Manager.
try this: Uninstall Vanced. Reinstall YouTube, but freeze it after install. Reboot. Redownload & install Vanced. Reboot. Unfreeze original YouTube & profit. Goodluck.
rzarectha said:
I am also using 15.3 magisk with 5.5.5 manager and I have no issues. I have systemiser, debloater, busybox, greenify. the only mod that seems to be not working îs YouTube vanced. I uninstalled the system YouTube and the mod seems unable to install its version.
Click to expand...
Click to collapse
amphi66 said:
Works fine here w/ same Magisk & Manager.
try this: Uninstall Vanced. Reinstall YouTube, but freeze it after install. Reboot. Redownload & install Vanced. Reboot. Unfreeze original YouTube & profit. Goodluck.
Click to expand...
Click to collapse
there's an even easier fix. Usually Vanced (iYTBP) doesn't work because there are two installs of Youtube (on /system/app and on /data/app) and it only replaces the one in /system. The solution is to deactivate auto-updates, then use a file manager (i recommend root browser all the way) to delete the /data/app/com.google.youtube folder (or however it is called, but the one that has the youtube apk inside).
and of course reboot after that
Whatever the problem was, it seems to have been fixed in the beta released today. (version name 16.4 - version code 1642) Working great.
Looking at his (topjohnwu's) changelog, it seems he made a ton of structure changes and improvements regarding MagiskHide, so it's no surprise this got fixed in the process.
May Magisk and the Axon 7 live long and prosper!
Hello,
I'm experienced a weird bug - when installing an APK file the phone hangs and I need to force restart it. After restarting the phone and trying to open the app being updated - a crash occurs. The update process is seemingly corrupting the app as I need to uninstall it and install again to make it work, making the associated data gone. It is frustrating, because it happens like I'd say 50/50 of times.
Happens while installing an app manually and using root in Yalp. Play Store not tested as it is not present on the phone.
The setup is Xperia X compact running latest .118 Oreo with microg, no GAPPS, Magisk, official Xposed 90 beta3,
Xposed modules: BatteryCare+, FakeGAPPS, GravityBox, XposedGmsCoreUnifiedNlp, XPrivacyLua
It did happen on Xperia X and Xperia XZ with similar setup on Oreo. I wonder if it might be caused by Xposed bundled with Xperia Software?
Actually I'm facing similar issue. I concluded it's caused by Xposed and certain modules. In fact, it's a known issue of Xposed for Oreo. According to rovo89, existing Xposed has problem with ART in Oreo.
As a workaround, now whenever I need to install/uninstall anything, I disable Xposed in Magisk first.
https://github.com/rovo89/Xposed/issues/325
Thank you @itandy for replying. Have you tried installing EdXposed instead of the regular Xposed?
Well it is basically for Pie but it is supposed to work on oreo too. Whenever I tried to install it on X compact running Oreo I got bootloop.
I have found that only some apps installation would cause a freeze and reboot. But your solution is safer of course.
Vixificent said:
Thank you @itandy for replying. Have you tried installing EdXposed instead of the regular Xposed?
Well it is basically for Pie but it is supposed to work on oreo too. Whenever I tried to install it on X compact running Oreo I got bootloop.
I have found that only some apps installation would cause a freeze and reboot. But your solution is safer of course.
Click to expand...
Click to collapse
Unfortunately EdXposed doesn't work last time I tried. It fails to boot at all.