Database Develop

Framework not active no matter what i do

my phone is the Blu VIVO IV (aka Gionee ELIFE S5.5) with kit kat and I got it rooted by following this post
http://forum.xda-developers.com/android/development/root-blu-vivo-iv-kitkat-4-4-2-t2854480
-I have superSu pro installed
-Root checker shows that I am rooted
-Mobile uncle runs (shows root) and I have no problem loading the recovery image
-unknown sources enabled
But xposed framework does not work correctly and I can't figure out what is wrong
- Xposed framework 2.6, 2.6.1 and 2.7 installs but it keeps telling me
"The latest version of Xposed is currently not active. Did you install the framework and reboot"
When I look under active and bundle. The # of active is the same as the bundled (app_ process 58 green active/ 58 bundled red)
I have reinstalled with classical, recovery (flash automatically) and recovery (manual flash). Same thing happens in all cases
If i ignore it and install modules, they do not take effect because it keeps telling me that xposed framework is not active.
- I tried xposed framework 2.5 and 2.5.1. They install and after a reboot becomes xposed is active and i don't get the message that it is unactive but i get crashes on my system ui. Gallery, mobile uncle and etc.

so i did a little more digging and I found that if check the "disable resource hooks" xposed now runs as active but most of the modules I'm using don't run
my logs shows the following
errors during xposed initialization
java.lang.ClassCastExpection: class android content res XResources doesn't extend class amigo theme core res GioneeResources
I assume that means that theming engine on my phone is interfering with Xposed?

anyone know i can get this resolved? I like to use xposed framework on blu vivo IV

rolexconfuse said:
anyone know i can get this resolved? I like to use xposed framework on blu vivo IV
Click to expand...
Click to collapse
Sorry for the obvious question, but...
are you using ART ? If so Xposed automatically deactivates itself, since it's only compatible with Dalvik !

dev>null said:
Sorry for the obvious question, but...
are you using ART ? If so Xposed automatically deactivates itself, since it's only compatible with Dalvik !
Click to expand...
Click to collapse
sorry but can you explain what ART is? I believe the phone is running Dalvik

Sorry, I found what ART was and I have the option to run ART or Dalvik and I am running under Dalvik right now under "developers Option"
Digging around in the forum I know that the Huawei phones had the same issue but then they could just edit one line in the build.prop and it worked. Unfortunately this doesn't work for me since that line is specific to just huawei phones.

help
I'm having same problem with gionee, exposed framework won't installe

Having same problem as everyone else with Gionee s5.5.

dev>null said:
Sorry for the obvious question, but...
are you using ART ? If so Xposed automatically deactivates itself, since it's only compatible with Dalvik !
Click to expand...
Click to collapse
I think you have that backwards... It switches back to dalvik...

getting the same error
'
Errors during Xposed initialization
java.lang.ClassCastException: class android.content.res.XResources doesn't extend class amigo.theme.core.res.GioneeResources

ok I sort it out
http://forum.xda-developers.com/showthread.php?t=2681678
thanks to "mundraguda"

help
rolexconfuse said:
Sorry, I found what ART was and I have the option to run ART or Dalvik and I am running under Dalvik right now under "developers Option"
Digging around in the forum I know that the Huawei phones had the same issue but then they could just edit one line in the build.prop and it worked. Unfortunately this doesn't work for me since that line is specific to just huawei phones.
Click to expand...
Click to collapse
help me...
i've huawei g700 u-10

pfff
I'm having same problem with gionee, exposed framework won't install

1-Install the xpose and open
2-Go to the framework and tap to "install/update"
3-reboot your phone
4- Again open the xpose go to framework and tap to
Installation mode" classical (write to/ system directly)
5- change the classical (write to/ system directly) to
Recovery (flash zip automatically)
6- And version change to "beta (sum box to be expected) click
7- Disabled to resource hooks click and back
Click the reboot don't click the "install/update"
And reboot your phone and enjoy:

divakark you are a hero. My Tornado 348 wouldn't work whatsoever and I followed what you said and it works perfectly thanks so much

[Q] How to get "SecureGo" working via xposed / rootcloak?

Hi fellows ...
well, I did this (xposed module repository: description)
Phone: GT-I9070P Samsung Galaxy S Advance
OS: (4.4.4)OptiROM (i9070-i9070P), ROM for the Samsung Galaxy S Advance I9070
Xposed Modules 1.0.8
Xposed Installer 2.7 experimental1
RootCloak 3.0-beta_20160731_2
RootCloak Plus 1.2
SecureGo 1.42-03
SecureGo still realises that the phone is rooted ... so no banking possible :crying: Thanks for help

b*_gently_*d said:
Hi fellows ...
well, I did this (xposed module repository: description)
Phone: GT-I9070P Samsung Galaxy S Advance
OS: (4.4.4)OptiROM (i9070-i9070P), ROM for the Samsung Galaxy S Advance I9070
Xposed Modules 1.0.8
Xposed Installer 2.7 experimental1
RootCloak 3.0-beta_20160731_2
RootCloak Plus 1.2
SecureGo 1.42-03
SecureGo still realises that the phone is rooted ... so no banking possible [emoji14] :crying: Thanks for help
Click to expand...
Click to collapse
In rootcloak, did you specifically add the securego app to it's block list?
Sent from my SCH-R220

Hi there!
Yes, in "RootCloak Plus", the entry de.fiducia.smartphone.android.securego.wl does exist.
There's another confusing circumstance: I don't know how to launch the Xposed Installer programme. The only way - for me right now - is to navigate to "downloads", and then to re-install some downloaded *.apk as an update. Then, and only then, I'm inside the Xposed Installer.
Under "Remove native root detection for apps", the box "SecureGo" is checked.

b*_gently_*d said:
Hi there!
Yes, in "RootCloak Plus", the entry de.fiducia.smartphone.android.securego.wl does exist.
There's another confusing circumstance: I don't know how to launch the Xposed Installer programme. The only way - for me right now - is to navigate to "downloads", and then to re-install some downloaded *.apk as an update. Then, and only then, I'm inside the Xposed Installer. [emoji14]
Under "Remove native rott detection for apps", the box "SecureGo" is checked.
Click to expand...
Click to collapse
In your app drawer (if Xposed is properly unstalled) should be the Xposed app. After you install an Xposed module you have to activate the module in the Xposed app and reboot for it to work. Sounds like that hasn't been done. How did you install Xposed?
Sent from my SCH-R220

OK, let's have a look: I've got a sort of menu that is pushed from the left side into the app "Xposed modules". Within this menu drawer, there's: Modules, Install Xposed Framework, More modules, Root, XDA, latest 24 hours, all unread, all marked, downloads, synchronise now, settings (translated from German).
The apps "Xposed modules" and "RootCloak" are installed from stalk Google Play Store.
The device was restarted several times, and from a certain moment on, everytime it started, I had to confirm elevated privileges (for rootcloak).
:angel:

b*_gently_*d said:
OK, let's have a look: I've got a sort of menu that is pushed from the left side into the app "Xposed modules". Within this menu drawer, there's: Modules, Install Xposed Framework, More modules, Root, XDA, latest 24 hours, all unread, all marked, downloads, synchronise now, settings (translated from German).
The apps "Xposed modules" and "RootCloak" are installed from stalk Google Play Store.
The device was restarted several times, and from a certain moment on, everytime it started, I had to confirm elevated privileges (for rootcloak).
:angel:
Click to expand...
Click to collapse
Ok, that doesn't sound can you post a screenshot of what you are talking about including the list of modules installed in Xposed?
Sent from my SCH-R220

Pardon. What does it sound like? :cyclops: Anyway, I was wrong about the Installer. I actually can access it. But I still can't launch SecureGo properly. I'm posting a *.zip file containing a log and several shots.

b*_gently_*d said:
Pardon. What does it sound like? :cyclops: Anyway, I was wrong about the Installer. I actually can access it. But I still can't launch SecureGo properly. I'm posting a *.zip file containing a log and several shots.
Click to expand...
Click to collapse
Sorry, didn't notice the typo, it looks like you are using and old version of Xposed and a BETA version of rootcloak, have you tried the stable version?
Sent from my SCH-R220

Let's have a look on what has changed:
uninstalled the beta and experimental versions
now, there's only one "RootCloak" v2.1.1 (and no longer a "RootCloak Plus" next to it), downloaded and installed from "Xposed Installer"
downloaded and installed the *.apk of "Xposed Installer" v2.6.1
I took the version numbers from the Android OS settings menu
the icon for "Xposed Modules" is no longer shown
however, I did not remove SecureGo while making changes.
I didn't have to grant elevated privileges (only when Xposed Installer installed RootCloak)
I'm posting the latest log-file!
Still not working ...

b*_gently_*d said:
Let's have a look on what has changed:
uninstalled the beta and experimental versions
now, there's only one "RootCloak" v2.1.1 (and no longer a "RootCloak Plus" next to it), downloaded and installed from "Xposed Installer"
downloaded and installed the *.apk of "Xposed Installer" v2.6.1
I took the version numbers from the Android OS settings menu
the icon for "Xposed Modules" is no longer shown
however, I did not remove SecureGo while making changes.
I didn't have to grant elevated privileges (only when Xposed Installer installed RootCloak)
I'm posting the latest log-file!
Still not working ...
Click to expand...
Click to collapse
Have you taken a look at this, maybe this could help : http://forum.xda-developers.com/showthread.php?t=3450396
Sent from my SCH-R220

Quoting the article linked above: "Requirements ... Android 6.0" ... Don't know if an OS-installation would defeat the object ...

b*_gently_*d said:
Quoting the article linked above: "Requirements ... Android 6.0" ... Don't know if an OS-installation would defeat the object ...
Click to expand...
Click to collapse
It would allow you to utilize this workaround
Sent from my SCH-R220

I don't even see the mere possibility to install Android 6 ... Or do you detect anything on the specific page?

b*_gently_*d said:
I don't even see the mere possibility to install Android 6 ... Or do you detect anything on the specific page?
Click to expand...
Click to collapse
b*_gently_*d said:
Hi fellows ...
well, I did this (xposed module repository: description)
Phone: GT-I9070P Samsung Galaxy S Advance
OS: (4.4.4)OptiROM (i9070-i9070P), ROM for the Samsung Galaxy S Advance I9070
Xposed Modules 1.0.8
Xposed Installer 2.7 experimental1
RootCloak 3.0-beta_20160731_2
RootCloak Plus 1.2
SecureGo 1.42-03
SecureGo still realises that the phone is rooted ... so no banking possible [emoji14] :crying: Thanks for help
Click to expand...
Click to collapse
Check the thread for your device, a quick Google search shows some MM ROMs for your GT-I9070P
Sent from my SCH-R220

still failure
Inspired by your previous posts and having followed your advice, I now have a phone running Android 6.0.1 Marshmallow.
I tried to install Suhide and SuperSU systemlessly [?] (or at least I think, I did it that way because I was in Recovery Mode/TWRP. There, I simply clicked "install" and did nothing but install both zip-files.
The line that stated, that a boot image had not been found and therefore the process was aborting patching the boot.img, attracted my attention.
Within the restarted Android-OS, I never found an app icon for SuperSU or Suhide. Nevertheless, I found out SecureGo's UID (10xxx) and gave the following command:
Code:
/data/adb/suhide-add 10xxx
for adding SecureGo to the blacklist.
But nothing has changed ... SecureGo still denies its job.

b*_gently_*d said:
Inspired by your previous posts and having followed your advice, I now have a phone running Android 6.0.1 Marshmallow.
I tried to install Suhide and SuperSU systemlessly [?] (or at least I think, I did it that way because I was in Recovery Mode/TWRP. There, I simply clicked "install" and did nothing but install both zip-files.
The line that stated, that a boot image had not been found and therefore the process was aborting patching the boot.img, attracted my attention.
Within the restarted Android-OS, I never found an app icon for SuperSU or Suhide. Nevertheless, I found out SecureGo's UID (10xxx) and gave the following command:
Code:
/data/adb/suhide-add 10xxx
for adding SecureGo to the blacklist.
But nothing has changed ... SecureGo still denies its job.
Click to expand...
Click to collapse
Check the suhide thread, other people have the same sort of issue, in that you are using CM SuperSU that is not systemless, need to disable it for systemless su to work
Sent from my SCH-R220

By "CM SuperSU", do you mean Cyanogenmod S.SU? Are there versions different to Chainfire's one?
I realised that, in TWRP, I can also give commands in a terminal (surprise :good. But I do believe this is Busybox ... read it somewhere, but can't tell where or when exactly.
Do I need ADB installed? I'm asking because it appears in the commands.
I noticed that, when running the Android-OS, Jack Palevich's "Terminal Emulator" is not rooted (showing $ instead of #).
But the strangest thing of all is: I cannot detect any signs that suhide or supersu are installed ... how could I possibly check this?

b*_gently_*d said:
By "CM SuperSU", do you mean Cyanogenmod S.SU? Are there versions different to Chainfire's one?
Click to expand...
Click to collapse
Yes, at least how it's implemented in the ROM
[*]I realised that, in TWRP, I can also give commands in a terminal (surprise :good. But I do believe this is Busybox ... read it somewhere, but can't tell where or when exactly.
Click to expand...
Click to collapse
Is your Busybox up to date?
[*]Do I need ADB installed? I'm asking because it appears in the commands.
Click to expand...
Click to collapse
If you have to issue these commands from your computer to the phone you would need ADB on your computer. Is ADB turned on in developer options?
[*]I noticed that, when running the Android-OS, Jack Palevich's "Terminal Emulator" is not rooted (showing $ instead of #).
Click to expand...
Click to collapse
Did you type su in Terminal Emulator?
[*]But the strangest thing of all is: I cannot detect any signs that suhide or supersu are installed ... how could I possibly check this?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Give me some time, I'll do a backup and see what you are seeing.
Sent from my SCH-R220
---------- Post added at 12:33 PM ---------- Previous post was at 12:11 PM ----------
b*_gently_*d said:
By "CM SuperSU", do you mean Cyanogenmod S.SU? Are there versions different to Chainfire's one?
I realised that, in TWRP, I can also give commands in a terminal (surprise :good. But I do believe this is Busybox ... read it somewhere, but can't tell where or when exactly.
Do I need ADB installed? I'm asking because it appears in the commands.
I noticed that, when running the Android-OS, Jack Palevich's "Terminal Emulator" is not rooted (showing $ instead of #).
But the strangest thing of all is: I cannot detect any signs that suhide or supersu are installed ... how could I possibly check this?
Click to expand...
Click to collapse
In looking at Chainfire's thread to install Systemless root, I discovered that there are special boot.img files that need to be flash, my device is not on that list. But he does have some things that might shed some light on the issue.
1) Is your device one of the supported devices?
2) If so, did you do a clean flash? Did you flash the boot.img and su zips immediately? The thread says you need to make sure to flash the systemless stuff before the built in su does anything because the systemless flashing doesn't clean up other root implementations and can create problems. That's why it is mandatory for a clean flash of the ROM.
3) After you do all that, install the SuperSU app from the play store and see what happens
Sent from my SCH-R220

I don't know how to check whether Busybox is up to date or not (I was talking about the TWRP-Terminal outside Android-OS).
When I type 'su' into the Terminal Emulator - similarly to GNU/Linux -, I have no longer got the first line, but the second of the following:
Code:
[email protected]:/ $ su
1|[email protected]:/ $ sudo
/system/bin/sh: sudo: not found
127|[email protected]:/ $
(This is a true quote from my in-OS terminal.)
I'll have to look for those boot images and the list of the supported devices ... Or would you give me a direct link? (I already gave the exact name of my device.)
What exactly is a "clean flash", and which *.img or *.zips would have to be flashed? Do you mean something like from my own smarty history? From this list I basically only did step 4 when installing MM/CM13.
There's something else: Under "Developers' options/settings" (don't know how it is in English), you can choose between "never", "when debugging via USB" and "when loading". Has this something to say?
Please give me a short reply if I should perform the whole list of steps or similar or not because I don't want to waste time only to repeat it again and again

b*_gently_*d said:
I don't know how to check whether Busybox is up to date or not (I was talking about the TWRP-Terminal outside Android-OS).
When I type 'su' into the Terminal Emulator - similarly to GNU/Linux -, I have no longer got the first line, but the second of the following:
Code:
[email protected]:/ $ su
1|[email protected]:/ $ sudo
/system/bin/sh: sudo: not found
127|[email protected]:/ $
(This is a true quote from my in-OS terminal.)
I'll have to look for those boot images and the list of the supported devices ... Or would you give me a direct link? (I already gave the exact name of my device.)
What exactly is a "clean flash", and which *.img or *.zips would have to be flashed? Do you mean something like from my own smarty history? From this list I basically only did step 4 when installing MM/CM13.
There's something else: Under "Developers' options/settings" (don't know how it is in English), you can choose between "never", "when debugging via USB" and "when loading". Has this something to say?
Please give me a short reply if I should perform the whole list of steps or similar or not because I don't want to waste time only to repeat it again and again
Click to expand...
Click to collapse
http://forum.xda-developers.com/app...rshmellow-t3219344/post63197935#post63197935
Sent from my SCH-R220

Xposed for the Note 7 after rooting with OvrDriVE's method

Ok here it is: Xposed for the new @OvrDriVE root method. I have not tested method on VZW as i do not have their phone, but this still should being this is a Samsung Note 7.
As with any custom rom's, root, add-on's, you assume all risks with modding your phone. You have been warned.
Make sure you read all of my directions below, before you start posting errors with the install. Worst case you just have to start over with @OvrDriVE s installation.
Here is the way you can install xposed on your phone after you have root. I in no way have made any files or apks, I am just posting ways you get this loaded on your phone.
Please Thank the devolopers and others that have made all these files and apks possible..
The way is to install Xposed framework via FlashFire:
1. Download FlashFire, You can get it from the app store: https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en
2. Download the Xposed Installer Apk: http://forum.xda-developers.com/showpost.php?p=58828974&postcount=1&nocache=1&z=3764362361329836
3. Download the Xposed Framework zip. <<< this is the file that you will be flashing via FlashFire: Xposed Framework.zip
4. Once you have all the files downloaded onto you computer/phone: you are ready to start. If you have'nt all ready copied all the files to your phone storage, do so now. If you did then you can move on to the #5.
5. Open FlashFire on your phone. Once it is loaded and open, click on circle with + button on the bottom right of the screen.
Then Click on Flash ZIP or OTA button.
Now select the xposed framework zip that you downloaded from #3.
Next you click the check mark on the top right of
the screen( do not change any of boxes on the left of the screen.<<< You Have Been Warned!!!!! .
Next scroll to the bottom of the screen and click the left button (flash button w the lighting bolt)
Sit back and watch FlashFire do its magic..
6. After #5 completes, you can now install the xposed installer apk from #2. Once installed open and check framework in the app and you should have this : Xposed framework version 86.1 (custom build by wanam / 2016709 is active.
7. Now go to Download in the xposed installer and download: Wanam Xposed 1.3.0 Made for Samsung Android 5 and 6 Roms by Wanam or you can download xTouchwiz by Wanam..
8. Once you downloaded it, install it, and then in the Xposed installer app- modules- you select the the app in #7 by placing a checkmark in the box on the right to activiate the modules.
9. Reboot your phone to activate the module.
10. Enjoy your efforts and customizing your phone:
If you some reason you want to uninstall xposed : flash this:xposed-uninstaller-20160211.zip

Confirmed working on my VZW Note 7 running PH1 firmware, rooted using @OvrDriVE's method.
Edit: for clarification, I used the second method (flashfire) to do this, and it worked like a charm.
Side note, you won't find Wanam Xposed 1.3.0 Made for Samsung Android 5 and 6 Roms by Wanam on xposed, it doesn't exist. Don't use Wanam Xposed either, it's been discontinued in favor of xTouchWiz. I've tested it myself and it works great, it's made by the same developer.
MOD EDIT: Large post quote put in hide tags.
Please don't quote large posts like this as it makes the thread difficult to read for other users.
galaxyuser88 said:
Ok here it is: Xposed for the new @OvrDriVE root method. I have not tested method on VZW as i do not have their phone, but this still should being this is a Samsung Note 7.
As with any custom rom's, root, add-on's, you assume all risks with modding your phone. You have been warned.
Make sure you read all of my directions below, before you start posting errors with the install. Worst case you just have to start over with @OvrDriVE s installation.
Here is 2 different ways you can install xposed on your phone after you have root. I in no way have made any files or apks, I am just posting ways you get this loaded on your phone.
Please Thank the devolopers and others that have made all these files and apks possible..
A. The first way is to use ADB to push the framework to your phone, Here is a link to the post with direction:
ADB Xposed installer
B: The second way is to install Xposed framework via FlashFire:
1. Download FlashFire, You can get it from the app store: https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en
2. Download the Xposed Installer Apk: http://forum.xda-developers.com/showpost.php?p=58828974&postcount=1&nocache=1&z=3764362361329836
3. Download the Xposed Framework zip. <<< this is the file that you will be flashing via FlashFire: Xposed Framework.zip
4. Once you have all the files downloaded onto you computer/phone: you are ready to start. If you have'nt all ready copied all the files to your phone storage, do so now. If you did then you can move on to the #5.
5. Open FlashFire on your phone. Once it is loaded and open, click on circle with + button on the bottom right of the screen.
Then Click on Flash ZIP or OTA button.
Now select the xposed framework zip that you downloaded from #3.
Next you click the check mark on the top right of
the screen( do not change any of boxes on the left of the screen.<<< You Have Been Warned!!!!! .
Next scroll to the bottom of the screen and click the left button (flash button w the lighting bolt)
Sit back and watch FlashFire do its magic..
6. After #5 completes, you can now install the xposed installer apk from #2. Once installed open and check framework in the app and you should have this : Xposed framework version 86.1 (custom build by wanam / 2016709 is active.
7. Now go to Download in the xposed installer and download: Wanam Xposed 1.3.0
Made for Samsung Android 5 and 6 Roms by Wanam
8. Once you downloaded it, install it, and then in the Xposed installer app- modules- you select the the app in #7 by placing a checkmark in the box on the right to activiate the modules.
9. Reboot your phone to activate the module.
10. Enjoy your efforts and customizing your phone:
If you some reason you want to uninstall xposed : flash this:xposed-uninstaller-20160211.zip
Click to expand...
Click to collapse

ohblindone said:
Confirmed working on my VZW Note 7 running PH1 firmware, rooted using @OvrDriVE's method.
Edit: for clarification, I used the second method (flashfire) to do this, and it worked like a charm.
Side note, you won't find Wanam Xposed 1.3.0 Made for Samsung Android 5 and 6 Roms by Wanam on xposed, it doesn't exist. Don't use Wanam Xposed either, it's been discontinued in favor of xTouchWiz. I've tested it myself and it works great, it's made by the same developer.
MOD EDIT: Large post quote put in hide tags.
Please don't quote large posts like this as it makes the thread difficult to read for other users.
Click to expand...
Click to collapse
Ok, 1.3.0 does exist on xposed app, and yes you can use xTouchwiz by wanam as well, both are good, xtouchwiz has alot of stuff removed that will not work with the new firmware but he also removed alot of stuff that he didnt think was needed, so you can try both out and you can decide what you want to use..I have used both and they both work.. Now unfortunately Wanam will not be updating any of these, but is only providing support only..

galaxyuser88 said:
Ok, 1.3.0 does exist on xposed app, and yes you can use xTouchwiz by wanam as well, both are good, xtouchwiz has alot of stuff removed that will not work with the new firmware but he also removed alot of stuff that he didnt think was needed, so you can try both out and you can decide what you want to use..I have used both and they both work.. Now unfortunately Wanam will not be updating any of these, but is only providing support only..
Click to expand...
Click to collapse
Apologies, looking at that module and it's description (saying it was only for lolipop) I figuredit wouldn't be good to install on 6.0.
I also went to it's dev page on XDA and it was stated that the module is no longer being supported.

Save for later!!

So really this works just like normal except using Flashfire. I got scared thinking I would white knuckle it like the root. Any other module issues? Using several of them? I like some of the small play store tweaks and battery saving modules on other phones, I know wanam has the only safe 'do everything gravity box for touchwiz' stuff.

Im not sure why, but after installing this to my note 7, The "Android is optimizing # of #" comes up and it optimizes 1 app only... It won't go away and everytime I reboot It happens. I sort of want xposed, but if this is happening everytime I can just go without it....

It stays on or you just get the normal startup type message that lasts for a few seconds? Does it affect anything else? Seems minor.

guthrien said:
It stays on or you just get the normal startup type message that lasts for a few seconds? Does it affect anything else? Seems minor.
Click to expand...
Click to collapse
Were you replying to me? It does 1 of 1 every boot. Its more annoying than anything really. Not worth the trouble. And if I uninstall it, the optimizing screen goes away. No one else is complaining about it so its just my problem.

So what xposed apps have been testing and what are all of you using? I haven't used xposed in a couple of years and the modules I liked seem outdated, and I'm afraid to use them. A lot of them say they are only for AOSP and to not use on Samsung and other modified forks. I was surprised at the amount of modules which were totally outdated, I'd say at least half or more were from 1-2 years ago or longer since they were last updated.
Biff I'm getting that issue as well. The first reboot it optimized all 359 of my apps, but now on every reboot it optimizes just 1 of 1 app, only takes a few seconds but it is annoying. I'm finding little utility in xposed anyhow so am not sure I'm going to bother keeping it. I didn't find the oldies but goodies like wanam, something to turn off the volume nag if too high, gravity box was very explicit not to use on Samsung, etc.

Yea I don't really seem to use anything is xposed anyways. The 1 of 1 thing is quite annoying! No one else seems to think that! I think im just gonna pass on installing this for a while..

I'm not getting the constant optimization like you guys. I did get all at once after adding it.
I'm using Amplify, GlobalS-health, Greenify, Play Store Changelog, XHangouts and Wanam's XTouchwiz, though very lightly on the last.

Optimizing apps on reboot went away after 4 or 5 reboots. Enjoying xposed but still hesitant to install modules.
Sent from my SM-N930V using Tapatalk

Really happy about this work so far. Great job and good guidance!
Ran a quick "safe" test with xTouchWiz by moving the clock from default (right) to the left side. It worked (after phone restart).
Excited, I tried System/Disable tether provisioning... Restarted the phone. Works.
Awesome.
I also have the "Optimizing 1 of 1" issue previously mentioned, but it's not often I reboot, so not too worried. Wondering if there is a way to get a log for which file is being optimized. Always good to know what's happening.

roslof said:
Really happy about this work so far. Great job and good guidance!
Ran a quick "safe" test with xTouchWiz by moving the clock from default (right) to the left side. It worked (after phone restart).
Excited, I tried System/Disable tether provisioning... Restarted the phone. Works.
Awesome.
I also have the "Optimizing 1 of 1" issue previously mentioned, but it's not often I reboot, so not too worried. Wondering if there is a way to get a log for which file is being optimized. Always good to know what's happening.
Click to expand...
Click to collapse
Atleast I know its xposed that is causing this... I believe there is a way to get logs, but I am unsure how to do this or where to get it... I rarely reboot as well, but its just bothersome to see it doinh that.

Awesome module I discovered while trying to figure out how to get rid of the ugly roaming triangle this root puts on the signal bars. It's called Flat Style Bar Indicators, some free stuff and a very nominal cost for full version. I also see that the root took away the carrier name, which can be added back with this module. You can change any aspect of the status bar, it's very cool. I made my signal bars look like an iPhone, much easier and clearer to read.

galaxyuser88 said:
Ok here it is: Xposed for the new @OvrDriVE root method. I have not tested method on VZW as i do not have their phone, but this still should being this is a Samsung Note 7.
As with any custom rom's, root, add-on's, you assume all risks with modding your phone. You have been warned.
Make sure you read all of my directions below, before you start posting errors with the install. Worst case you just have to start over with @OvrDriVE s installation.
Here is the way you can install xposed on your phone after you have root. I in no way have made any files or apks, I am just posting ways you get this loaded on your phone.
Please Thank the devolopers and others that have made all these files and apks possible..
The way is to install Xposed framework via FlashFire:
1. Download FlashFire, You can get it from the app store: https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en
2. Download the Xposed Installer Apk: http://forum.xda-developers.com/showpost.php?p=58828974&postcount=1&nocache=1&z=3764362361329836
3. Download the Xposed Framework zip. <<< this is the file that you will be flashing via FlashFire: Xposed Framework.zip
4. Once you have all the files downloaded onto you computer/phone: you are ready to start. If you have'nt all ready copied all the files to your phone storage, do so now. If you did then you can move on to the #5.
5. Open FlashFire on your phone. Once it is loaded and open, click on circle with + button on the bottom right of the screen.
Then Click on Flash ZIP or OTA button.
Now select the xposed framework zip that you downloaded from #3.
Next you click the check mark on the top right of
the screen( do not change any of boxes on the left of the screen.<<< You Have Been Warned!!!!! .
Next scroll to the bottom of the screen and click the left button (flash button w the lighting bolt)
Sit back and watch FlashFire do its magic..
6. After #5 completes, you can now install the xposed installer apk from #2. Once installed open and check framework in the app and you should have this : Xposed framework version 86.1 (custom build by wanam / 2016709 is active.
7. Now go to Download in the xposed installer and download: Wanam Xposed 1.3.0 Made for Samsung Android 5 and 6 Roms by Wanam or you can download xTouchwiz by Wanam..
8. Once you downloaded it, install it, and then in the Xposed installer app- modules- you select the the app in #7 by placing a checkmark in the box on the right to activiate the modules.
9. Reboot your phone to activate the module.
10. Enjoy your efforts and customizing your phone:
If you some reason you want to uninstall xposed : flash this:xposed-uninstaller-20160211.zip
Click to expand...
Click to collapse
Does Gravitybox work as far as nav button is concerned?

Lmax579 said:
Does Gravitybox work as far as nav button is concerned?
Click to expand...
Click to collapse
As far as gravity box goes, i have no idea if it works or not. Give it a try and post your findings.

galaxyuser88 said:
As far as gravity box goes, i have no idea if it works or not. Give it a try and post your findings.
Click to expand...
Click to collapse
It does but navbar might break system UI, is there anyway to fix UI thru adb?

spinedoc said:
Awesome module I discovered while trying to figure out how to get rid of the ugly roaming triangle this root puts on the signal bars. It's called Flat Style Bar Indicators, some free stuff and a very nominal cost for full version. I also see that the root took away the carrier name, which can be added back with this module. You can change any aspect of the status bar, it's very cool. I made my signal bars look like an iPhone, much easier and clearer to read.
Click to expand...
Click to collapse
Okay, I was skeptical at first, but realized I need to fly soon and wanted to stimulate the green battery icon in case security thinks this is a recalled Note 7. There's been so much press about the green icon meaning the phone is safe that *not* seeing one may have folks thinking it's not...
Results with this module exceeded my expectations. And no more voLTE...
Edit: Turns out this didn't permanently resolve the issue where VoLTE appears. It comes back and will linger until reboot. We'll need a real fix, either by a flashable zip or need/updated Xposed module.

Issue with new Xposed Installer 3.1 (coming from DVDandroid's fork)

With the new installers modules can't be enabled/disabled when the framework is not active.
This is a problem if one has to run the Xposed uninstaller to get out of a bootloop and wants to disable single modules afterwards

Edgar_M said:
With the new installers modules can't be enabled/disabled when the framework is not active.
This is a problem if one has to run the Xposed uninstaller to get out of a bootloop and wants to disable single modules afterwards
Click to expand...
Click to collapse
If you have disabled the framework, restart your device and uninstall the modul which makes problems

Imagine, you have installed a whole bunch of modules and you need to find out which one is causing the trouble ...
The installer just shouldn't disable the enable/disable checkboxes in the modules list on purpose in case of a framework not installed state and everything is fine. At least it was implemented like this pre 3.0

Edgar_M said:
With the new installers modules can't be enabled/disabled when the framework is not active.
This is a problem if one has to run the Xposed uninstaller to get out of a bootloop and wants to disable single modules afterwards
Click to expand...
Click to collapse
There is a flashable file to disable all modules from recovery
Sent from my SCH-R220

Edgar_M said:
Hi mattzeller! Thanks for your contribution to that topic. But please read the original post once again. Then you will see, that you are missing the point with your post. Not a big deal - let's just try to keep the good quality of XDA alive
Click to expand...
Click to collapse
I fully understand your original post. If you are in a boot loop because of a specific module, disabling all of them will ensure you get out of a bootloop without removing Xposed completely so you can figure out which one it is via logcat. If it is Xposed itself causing the bootloop, it doesn't matter what modules are installed or activated.
Sent from my SCH-R220

Magisk keeps uninstalling

Hi.
I have a HTC 10 running LineageOS 14.1. In the past 4 days I have had to re install Magisk 16.3 at least 4 times daily as it keeps uninstalling itself. I have always had this issue with Magisk but it appears to have gotten worse instead of being solved.
Any suggestions as to what I can do to improve the situation?

It's likely not uninstalling itself, but something is killing the daemon. If you figure out what (aggressive battery saving might be a culprit), it would be good...

Magisk manager tells me that "Magisk is not installed" and that version 16.3 is available to install. However when I reboot it's there again so looks like you're right. Guess I'll have to have a look for what's causing it.. Thanks.

This is happening to me on OOS open beta 6. It's not really uninstalled because all my modules are present, but root does not work and the Magisk app is gone from my apps in settings and app drawer. I have to go into recovery and reflash it. This is happening on reboots at random.

it seems after the april update on stock orea 8.0 MIA1 Xiaomi this issues has become frequant.

manan001 said:
it seems after the april update on stock orea 8.0 MIA1 Xiaomi this issues has become frequant.
Click to expand...
Click to collapse
Some users are experiencing this, and I suspect it's a MagiskHide thing. You could help investigating by doing two things:
Install a beta release (use v16.3 because of the 64-bit issue with v16.4), and provide the magisk_debug.log after Magisk "uninstalls itself". You might have to grab it from recovery, since you're loosing root.
Disable MagiskHide and let it be disabled for a while to see if the issue still occurs (to confirm if it's MagiskHide or not).

Can be caused by Greenify?

I have the same problem magisk uninstalled after installing sdw hide root & sdw mock location through xposed installer

same issue but xposed included.

LG G6 Rootet Oreo Stock debloatet Magisk 17.2. same problem. deinstalling itself

kerpert said:
Can be caused by Greenify?
Click to expand...
Click to collapse
I installed greenify and this happened......probably it is the cause

m1l4droid said:
@Didgeridoohan adding Magisk as an exception in the MIUI battery saver didn't work. Not sure what to do.
Click to expand...
Click to collapse
Me neither...
There's a relatively active GitHub issue open about this issue, but there's been nothing definitive found about it yet.
The reports about this issue are so scattered, lacking in details and undefined that it's hard to say anything either way. Some users have success if disabling MagiskHide, some not so much, etc.
Someone that is experiencing the issue need to figure out what it's about. Until then there's not much to do...

It causes because of Busybox... uninstall busybox module fixed the problem for me

Didgeridoohan said:
... but something is killing the daemon. If you figure out...
Click to expand...
Click to collapse
Definition for daemon: https://www.linux.org/threads/android-services-and-daemons.10847/
How can one figure out?

kerpert said:
Can be caused by Greenify?
Click to expand...
Click to collapse
Nope. I've uninstalled greenify and magisk stopped anyway. So it's not related to greenify.

dan60 said:
How can one figure out?
Click to expand...
Click to collapse
Possibly by saving logs at the moment the daemon is killed off. Can be tricky...
If you don't want to, or don't have the skill to figure that out, you could try this meanwhile:
https://forum.xda-developers.com/apps/magisk/magisk-installed-workaround-t3908748
Would be interesting to know if it works for everyone.

Didgeridoohan said:
If you don't want to, or don't have the skill to figure that out, you could try this meanwhile:
https://forum.xda-developers.com/apps/magisk/magisk-installed-workaround-t3908748
Would be interesting to know if it works for everyone.
Click to expand...
Click to collapse
I should probably state that the module was made using a 17 template so min magisk ver. 17. There's really no telling what's killing the daemon. Also I note in the thread if magiskd is killed manually my module doesn't work. Don't know what all that is about... I've been playing around trying to kill it off manually and restart with no success using SSH as my root access. I don't expect this to work for everyone because I don't know how their daemon is dying. For some odd reason the module works for me when my daemon dies randomly so I'm happy with that. BTW I included logging which prints time and date script detects magisk not running and if it successfully restarted. The logs located in /data/local/tmp/magiskd-helper.log. I also have .pid in /data/local/run. Create dir if non-existent and . pid should be there.

Geofferey said:
I should probably state that the module was made using a 17 template so min magisk ver. 17. There's really no telling what's killing the daemon. Also I note in the thread if magiskd is killed manually my module doesn't work. Don't know what all that is about... I've been playing around trying to kill it off manually and restart with no success using SSH as my root access. I don't expect this to work for everyone because I don't know how their daemon is dying. For some odd reason the module works for me when my daemon dies randomly so I'm happy with that. BTW I included logging which prints time and date script detects magisk not running and if it successfully restarted. The logs located in /data/local/tmp/magiskd-helper.log. I also have .pid in /data/local/run. Create dir if non-existent and . pid should be there.
Click to expand...
Click to collapse
You could let the script also dump the current logcat buffer to a file (or cyclically save logcat to a file set to a certain size) when it detects the Magisk daemon not running. Might show why it dies...

Didgeridoohan said:
... try this meanwhile:
https://forum.xda-developers.com/apps/magisk/magisk-installed-workaround-t3908748
Would be interesting to know if it works for everyone.
Click to expand...
Click to collapse
Great initiative. I installed it yesterday, but sadly my oreo moto z play got unrooted again (same as if no Magiskd-helper had been flashed). But thanks for trying to help.

dan60 said:
Great initiative. I installed it yesterday, but sadly my oreo moto z play got unrooted again (same as if no Magiskd-helper had been flashed). But thanks for trying to help.
Click to expand...
Click to collapse
When you reboot does magisk come back? Could you post output of /data/local/magiskd-helper.log? I would like to see if it even attempted.