Database Develop

Xposed Not Active Error

Device rooted.And there is Chinese Cwm Recovery.
Xposed installed and rebooted after installation.
Android version is 4.2.2
Screenshots
{
"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"
}
My device is Gionee Elife E7
Sorry for my English

I?m getting the same error on my Samsung i9100g.
Not sure what needs to be done....
When I go to "Install/Update" I get:
SD Card: null
...
Could not extract Xposed-Disabler-recover.zip
Yet my extSD card is active....

I have the same problem. I hope someone can help us.
But we can still use the version 2.5.
Enviado desde mi HUAWEI P2-6011 mediante Tapatalk

Same problem here, with a Huawei G740 using latest stock ROM 4.1.2. Fortunately, I could revert to previous version to fix this.

Xposed 2.5 version framework does not work.
http://forum.xda-developers.com/xposed/gionee-elife-e7-framework-problems-t2753155

Logcat of this
This issue also happens on my Huawei Y300-0100 with stock android 4.1.1.
Heres the log
Code:
-----------------
18.5.2014 19:14:59 UTC
Loading Xposed v54 (for Zygote)...
Running ROM 'FusionX_Reborn_V2.0' with fingerprint 'Huawei/Y300-0100/hwY300-0100:4.1.1/HuaweiY300-0100/C00B199:user/ota-rel-keys,release-keys'
Errors during Xposed initialization
java.lang.ClassCastException: class android.content.res.XResources doesn't extend class android.content.res.ResourcesEx
at de.robv.android.xposed.XposedBridge.cloneToSubclass(XposedBridge.java:787)
at de.robv.android.xposed.XposedBridge.hookResources(XposedBridge.java:365)
at de.robv.android.xposed.XposedBridge.initXbridgeZygote(XposedBridge.java:267)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:117)
at dalvik.system.NativeStart.main(Native Method)
-----------------
18.5.2014 19:17:31 UTC
Loading Xposed v54 (for Zygote)...
Running ROM 'FusionX_Reborn_V2.0' with fingerprint 'Huawei/Y300-0100/hwY300-0100:4.1.1/HuaweiY300-0100/C00B199:user/ota-rel-keys,release-keys'
Errors during Xposed initialization
java.lang.ClassCastException: class android.content.res.XResources doesn't extend class android.content.res.ResourcesEx
at de.robv.android.xposed.XposedBridge.cloneToSubclass(XposedBridge.java:787)
at de.robv.android.xposed.XposedBridge.hookResources(XposedBridge.java:365)
at de.robv.android.xposed.XposedBridge.initXbridgeZygote(XposedBridge.java:267)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:117)
at dalvik.system.NativeStart.main(Native Method)

For Huawei ROMs, please use the "Disable resources API" for now. It will take some time until I (hopefully) have a fix for it.

İbo hızlı açılışı kapatırsan sorun çözülüyor..
MOD EDIT:
If the problem goes away quickly close the opening Igbo ..

rovo89 said:
For Huawei ROMs, please use the "Disable resources API" for now. It will take some time until I (hopefully) have a fix for it.
Click to expand...
Click to collapse
I am using your 2.6 framework on a modified Huawei stock ROM and no problem, this is the rom http://www.modaco.com/topic/371493-romjb411-slimstock-b199-v182-final-y300g510-15052014/

rovo89 said:
For Huawei ROMs, please use the "Disable resources API" for now. It will take some time until I (hopefully) have a fix for it.
Click to expand...
Click to collapse
Thanks, it does fix the problem on my Huawei G740 for the moment (although, as expected, XTheme Battery no longer works).
EDIT: Finally reverting to XPosed 2.51 (I missed my favorite battery theme). Any chance of having a Huawei-compatible version in a near future?

Thanks problem solved.

same error message
Framework will not work since update HTC one

Framework update error Htc one
Will not let me update error msg

cheefkeef said:
Will not let me update error msg
Click to expand...
Click to collapse
Same problem here. HTC One M7 with Sense Rom.

rovo89 said:
For Huawei ROMs, please use the "Disable resources API" for now. It will take some time until I (hopefully) have a fix for it.
Click to expand...
Click to collapse
which means "to turn off the API" hoping for a fix?
---------- Post added at 03:55 PM ---------- Previous post was at 03:48 PM ----------
ibo1996 said:
Thanks problem solved.
Click to expand...
Click to collapse
how you solved the problem? thank you ..

Xposed Not Active Error SOLUTION
cheefkeef said:
Will not let me update error msg
Click to expand...
Click to collapse
Hey dude, I was fiddling around with a couple things and I finally got it to work. Here's what you got to do:
1) Open Xposed Installer and go to Framework.
2) Press the tab under Installation Mode (it should say "Classical (write to /system directly)" and choose "Recovery (write zip to SD card, flash manually)".
3) Go back and press Uninstall - both app_process and XposedBridge.jar will have "---" under Active.
4) Press Install/Update and it will download a .zip file to a folder in your Internal SD card - keep track of where that is. (Seriously, it's a really random location. Make sure you know where the folder is.
5) Phone will reboot into recovery. Go to install, flash the .zip file and reboot your phone.
You should be good to go at that point!

Solution for HUAWEI users ONLY: http://www.modaco.com/topic/372595-how-to-use-xposed-framework-26-on-huawei-roms/#entry2212856

fonz93 said:
Solution for HUAWEI users ONLY: http://www.modaco.com/topic/372595-how-to-use-xposed-framework-26-on-huawei-roms/#entry2212856
Click to expand...
Click to collapse
Yes, this might work because this stops the ROM from using the Huawei-specific Resources subclass. Not sure about the side-effects though, I assume it will also deactivate whatever kind of theming engine they have built. I hope that a future version can work around the issues properly.

fonz93 said:
Solution for HUAWEI users ONLY: http://www.modaco.com/topic/372595-how-to-use-xposed-framework-26-on-huawei-roms/#entry2212856
Click to expand...
Click to collapse
Grande..risolto il problema..(ascend P6)..quando vuoi,sono al pepito beach(Montesilvano) e ti pago da bere..http://forum.xda-developers.com/images/icons/icon8.gif
Great .. solved the problem .. (ascend P6) .. when you want, are pepito beach (Montesilvano) and I pay you to drink .. http://forum.xda-developers.com/images/icons/ icon8.gif [/ url]

Thanks - this worked for me
Rave4No52 said:
Hey dude, I was fiddling around with a couple things and I finally got it to work. Here's what you got to do:
1) Open Xposed Installer and go to Framework.
2) Press the tab under Installation Mode (it should say "Classical (write to /system directly)" and choose "Recovery (write zip to SD card, flash manually)".
3) Go back and press Uninstall - both app_process and XposedBridge.jar will have "---" under Active.
4) Press Install/Update and it will download a .zip file to a folder in your Internal SD card - keep track of where that is.
5) Phone will reboot into recovery. Go to install, flash the .zip file and reboot your phone.
You should be good to go at that point!
Click to expand...
Click to collapse
Thanks - this was helpful. I'm new to XPosed, and was wondering why I couldn't use it after installing it.
As you pointed out,
......4) Press Install/Update and it will download a .zip file to a folder in your Internal SD card - keep track of where that is.
It took me 3 attempts until I looked closely at what the dialog box was telling me.
-RKA

[DISCUSSION] Xposed for Lollipop

It seems that many people have waited for this moment, and here we are:
Xposed for Lollipop is finally here!​
You can use this thread for discussions. Please check the read-only thread for the download links and official updates.
Edit by @Darth.
Rovo89 has been kind enough to let us add a few things to help stop the repeated questions that are asked here.... And thanks to RootSU, we'll be able to add a FAQ........ So...
Please read post 2 below.... Very carefully before posting a question here.

Unofficial Q&A
PLEASE READ:
If you have questions about which Xposed version to use, read this post and use the table to identify the correct version for your device.
If you encounter any issue or things are still unclear, try to search this thread by using the Search function before posting anything. Lots of issues/questions have already being asked and/or solved. If this doesn't work, please include information about your device, its current Android version, the files you tried to flash/install and steps to reproduce the issue in your post. This way other members are able to help you in a timely manner.
Hey everyone,
Since the primary thread information was taken to a read-only thread, the regulars here have been answering the same questions with even mor frequency, so here we hope to address some of those basic questions in brief:
Q: What does "Alpha" mean?
A:
Software goes through several stages before final release. Alpha and Beta are a couple. Beta is usually released strategically to experienced testers to get feedback and find bugs. Alpha is less mature than Beta and is often not released outside the company that produced it. We're very lucky to get alpha releases, but beware, it is expected to be buggy and you should be experienced in Android usage before taking on Alpha testing.
Q: What do I need to do BEFORE flashing Xposed?
A:
A full Nandroid Backup of your system (preferrably by using your recovery). If something goes horribly wrong during flashing/installation, you can revert all changes made to your system quite easily.
Q: What recovery can I use?
A:
The latest zips provided by @rovo89 are now signed, so any recovery should work now (including cyanogen recovery) however, Philz recovery struggles to mount system correctly and detects the recovery sdk 19 instead of the ROM recovery. You can try manually mounting system in recovery first (instructions are lower down this thread) though, you should probably move over to TWRP now.
Some of the unofficial versions are not signed zips, so you'll need a recovery that can turn off signature verification. TWRP is probably the best bet all round, as cyanogen recovery doesn't allow this.
Q: Which is the right Xposed for me?
A:
It's all getting rather confusing.
Here's what you need to know...
Almost all android devices have an ARM based CPU. A small handful of those are 64 bit (ARM64), released this year. Obviously the ones that are not 64 bit are 32 bit.
All ARM version 7 CPUs are 32 bit. Although all ARM version 8 CPUs were designed as 64 bit, some only operate in a 32 bit mode.
A small set of android devices now run 32 bit Intel CPUs, referred to as x86.
What you first need to do is find out what CPU your phone has. If its intel x86, that's quite easy to find out by reading the specs.
For others, try this:
Google "your phone CPU? “ to get the CPU name.
Google "your CPU ARM Version?“ to get the ARM version.
Example...
Google "Nexus 6 CPU" - answer Snapdragon 805
Google "snapdragon 805 ARM version?" - answer ARMv7
NOTE: For Snapdragon CPU's, check this Wikipedia article.
You can also use AIDA64 from the Google Play Store or apkmirror.com, which will tell you what ARM version you have (look for Instruction Set). Quite easy way.
Then use that information to use the table below to find the right version for your device (The second table is for users with a TouchWiz-based ROM, so mostly Samsung users. The first one is for all other users.) Links to the Xposed versions are given below the image.
EDIT: the flow chart, which was used in the past to identify the correct Xposed version one needs has been replaced by a table, which should be easier to read.
How to read the table:
If you do not know how to read the table, it is very easy. If you have a Samsung device (either with stock ROM or TouchWiz-based custom ROM), use the second table ("TouchWiz-based ROMs (Samsung users)"). If not, use the first table. Then identify your CPU ARM version as described above as well as your Android version. With those information available, go to the corresponding field in the table and that's it, you have just identified the required Xposed version for your device.
{
"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"
}
Download threads:
@rovo89 version, see post 1
@arter97 version: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463
FOR ODEXED SAMSUNG STOCK ROM (LOLLIPOP 5.0.2) USE THIS VERSION.
@wanam version: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
@SolarWarez version for MIUI-based devices: http://forum.xda-developers.com/xposed/unofficial-xposed-miui-t3367634
Q: Does this work on my rom/device?
A:
It should work. You can search the thread to see if anyone else got it to work, or you can do what everyone else does - backup and try it for yourself.
Q: What files do I need?
A:
The Xposed installer (.apk) and the flashable Framework (.zip)
Q: Error in Xposed app "xposed not yet compatible with SDK 22 or your processor architecture (armeabi-v7a)" and may also refer to libdvm.so
A:
This happens if you are using the legacy KitKat Xposed app (Xposed Installer v2.7 or below). Uninstall it and ensure you are running the latest alpha (currently: XposedInstaller_3.0_alpha4.apk) from the official rovo89 thread.
Q: Error in recovery, "wrong sdk version / wrong arm version". How to solve?
A:
Read this error very carefully.
If it says "Wrong SDK version: 22, expected 21 - 21", it means you're flashing the SDK 21 version on an SDK 22 based ROM.
Similarly, if it says "Wrong SDK version: 21, expected 22 - 22", it means you're flashing the SDK 22 version on an SDK 21 based ROM*
You're flashing the wrong zip for your ROM. Use the table above to identify the correct zip for you.
*Note, All 5.0.x ROMs are SDK21 based. All 5.1.x ROMs are SDK22 based. You're flashing the r
There is a similar, but slightly different error. If it says "Wrong SDK version: , expected 22 - 22" or it says If it says "Wrong SDK version: , expected 21 - 21" , then something else is wrong. Note the blank space after "version:"? This means it cannot determine your SDK version from the /system/build.prop.
Withing the flashable zip is an updater-binary that reads your build.prop before flashing. The line of code looking for that is below:
Code:
ui_print "! Wrong SDK version: $API, expected $XMINSDK - $XMAXSDK"
See how where the blank space is, here, it says "$API"? That is a variable that is defined below:
Code:
API=$(cat /system/build.prop | grep "ro.build.version.sdk=" | dd bs=1 skip=21 count=2)
...Which basically says:
Look for "ro.build.version.sdk=" in build prop, then save next 2 characters as API$
If $API is blank, it means it cannot find "ro.build.version.sdk=21" or "ro.build.version.sdk=22" in your build.prop.
One of two reasons cause this.
1) It's not in your build.prop (well that is extremely unlikely)
2) The updater-binary cannot mount /system properly.
So to troubleshoot, check that "ro.build.version.sdk=" exists exactly in build.prop and that there are 2 characters after it. If there are, then API should NOT be blank and probably means system is not mounting, in which case, you can try mounting system via the recovery menu. If that still doesn't work, open a terminal emulator at the root folder (in TWRP) and type the following 2 commands:
Code:
mount -o ro /system
mount -o rw,remount /system
Please also note that if this gives an error such as "cannot find system" then you may need a different recovery.
The same as above can also happen with the arm version, so if you know you're flashing the correct arm version for your device, then it's probably a system mounting issue.
Q: I can't find the latest Alpha, help!
A:
There are 2 parts of Xposed. There is the app (.apk) and the framework (a flashable .zip) and you need both.
The latest version of the app so far is alpha 3. When we talk about alpha 4 etc, these updates are just to the framework (zip). The zips are not named "alpha" though. The zips have a date in the file name instead. Read rovo89's posts clearly as he gives you that date when there is an update announcement.
Q: What is Armv7? Will it support my CPU? What about Armv8 / 64 Bit / Intel CPUs
A:
Armv7 is a CPU architecture. If you have a mainstream phone released since 2010, you most likely have Armv7. All Qualcomm and Exynos CPUs since then have been based on Armv7. Armv8 however is the architecture used in the new 64bit CPUs.
Intel CPUs are x86. They are not officially supported.
Q: Does this work on Android JellyBean/KitKat/Marshmallow?
A:
No. It's only for Lollipop.
Q: Where can I find the uninstaller?
A:
In the link found in post #1 or - in case you use wanam or arter97's version - in the corresponding threads.
Q: What's this red error about not being able to install the framework within the Xposed Installer app?
A:
It's not an error. It simply states that the framework can only be installed by recovery - which we know as we have already done it.
Q: Xposed won't work. All the files are present and correct. What to do?
A:
Check the logs in the app. If you see a line that says "found /data/data/de.robv.android.xposed.installer/config/disabled" then delete that "disabled" file and reboot. It should work.
If it doesn't work, try to do a soft reboot from within Xposed Installer app (Xposed Installer -> Framework -> Soft Reboot). Root permission has to be granted to the Xposed Installer app to do so (will be asked when clicking on the Soft Reboot button for the first time).
Q: I get in a bootloop, what to do?
A:
The first thing to try is wiping "dalvik" and cache via recovery. If this doesn't work, ensure you have flashed the correct Xposed version (this applies for Samsung users mostly). Else you can provide a log file which you can grab via ADB (search for "How to logcat" if you don't know how) and upload it either here (don't forget to link rovo89 in your post) or to rovo89's github repo (better option)
Q: TWRP states "not enough space in system". What is this about?
A:.
Not really related to Xposed, it just means that your system partition doesn't have enough free space to install Xposed. Maybe create some space by deleting Google related-apps from system that you don't need or that can be downloaded from Play Store. Ask in your device forum if you need specific advice.
Q: How do I update the Xposed framework to a newer version?
A:
You can dirty flash it through recovery (don't uninstall/wipe anything before flashing). Afterwards, wipe cache/dalvik and reboot. That's it.
Device Specific
Q: My LG device has Weather and Smartcover force closes. What to do?
A:
Those issues are fixed with Xposed framework v80 and later. If you encounter such issue, update the Xposed framework to version v80 or higher. If you are unable to update to v80 or later, you need to disable these apps before flashing. You can disable them afterwards, please see this post: http://forum.xda-developers.com/showpost.php?p=59929667&postcount=5122.
Q: I get a low on space error on my Moto. What to do?
A:
The first thing to try is wiping "dalvik" and cache via recovery.
Q: It does not work on my Huawei/Xiaomi device. What to do?
A:
Chinese OEMs change a lot of the original Android code base, so most likely Xposed is not compatible with those devices (yet). There might be some compatibility in the future, but don't expect it in the next few days.
Q: It does not work on my MIUI device. What to do?
A:
There is an XDA thread by SolarWarez dedicated to Xposed for MIUI-based devices.
Xposed MIUI

This thread was just started an already it had to be cleaned from pointless posts. Use the thanks button. Do not make pointless posts in the thread.
I understand You guys are excited but really? Come on.
If you dont have something constructive to post then dont. Do not clutter this thread Or it will be closed and only opened when the OP has something to post.

rovo89 said:
Note that this is still an alpha version and for Lollipop on ARMv7 devices only.
Click to expand...
Click to collapse
Read this after flashing zip on Note 4 Exynos.
So, just another reminder, it won't work on ARM v8 devices.

I've flashed the .zip multiple times but in the APK you provided it shows that it's not active.
HTC One M7 CyanogenMod 12 20150212-Nightly
Am I missing something?
edit: added log

Look I already posted a warning. And people dont want to listen so let me make this very clear. The next pointless post will have this thread closed and only opened for the OP.
If you are posting a bug then you better have a logcat to go along with it. If it doesnt work because you didnt read the OP then too bad.

As a ROM developer, I have concerns that this will cause a lot of bugs similar to what we faced in KitKat. Users tend to think that they should use tools like this on custom AOSP ROMs and it ends up conflicting with our stuff. Is there any way you can assist when we have issues and need to refer a user to you?

megatooth said:
Read this after flashing zip on Note 4 Exynos.
So, just another reminder, it won't work on ARM v8 devices.
Click to expand...
Click to collapse
I actually wasn't aware that ARMv8 is available. It should work for that one, too.
briann_cs said:
Bootloop in Galaxy S5 with Lollipop 5.0
Click to expand...
Click to collapse
mhboooool said:
Bootloop in Galaxy S4 i9500 with Lollipop 5.0 TW
Click to expand...
Click to collapse
As always, I can't do anything without a logcat. Same for any other issues you might notice. If the device boots, but the framework is not shown as active, the Xposed log (in the installer) might be sufficient.

Can't get it to work.
Installed the ZIP twice and the app still says framework not installed. on my Nexus 6 running stock Lollipop and FKU r14.
Well, it's an alpha for a reason. Thanks for your work dev! :victory:
EDIT: Add screenshot

rivas741 said:
Installed the ZIP twice and the app still says framework not installed. on my Nexus 6 running stock Lollipop and FKU r14.
Well, it's an alpha for a reason. Thanks for your work dev! :victory:
Click to expand...
Click to collapse
Same scenario on same setup.

Nexus 6 ist ARMv8 right? So it must work?

zelendel said:
Look I already posted a warning. And people dont want to listen so let me make this very clear. The next pointless post will have this thread closed and only opened for the OP.
If you are posting a bug then you better have a logcat to go along with it. If it doesnt work because you didnt read the OP then too bad.
Click to expand...
Click to collapse
I have done what op says I'm not retarded......after flash. app still says framework not installed and I have a g3...

Upstreammiami said:
I have done what op says I'm not retarded......after flash. app still says framework not installed and I have a g3...
Click to expand...
Click to collapse
Logcat?

rivas741 said:
Installed the ZIP twice and the app still says framework not installed. on my Nexus 6 running stock Lollipop and FKU r14.
Well, it's an alpha for a reason. Thanks for your work dev! :victory:
Click to expand...
Click to collapse
Can also confirm this issue.

GermainZ said:
Logcat?
Click to expand...
Click to collapse
I'm not near a pc... And a logcat for what it's not like it's crashing.

Logcat attached. Thanks for everything!

Use the log in the xposed installer ?

Upstreammiami said:
I'm not near a pc... And a logcat for what it's not like it's crashing.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=58829719&postcount=7
FYI: a logcat can contain much more information than about crashes. It's usually a good idea not to assume something won't be useful when you're not sure.

good job so far and i hope you can extend xposed support to SDK 19 API with ART.
many Mediatek devices will benefit and many mediatek user will love you.

Nexus 6 5.0.2 on T-Mobile US - I also flashed the file like others are saying, but the installer app shows as not installed. Here's the log from Xposed:
PHP:
02-13 16:24:20.564 I/Xposed ( 348): -----------------
02-13 16:24:20.564 I/Xposed ( 348): Starting Xposed binary version 60, compiled for SDK 21
02-13 16:24:20.564 I/Xposed ( 348): Phone: Nexus 6 (motorola), Android version 5.0.2 (SDK 21)
02-13 16:24:20.564 I/Xposed ( 348): ROM: LRX22G test-keys
02-13 16:24:20.564 I/Xposed ( 348): Build fingerprint: google/shamu/shamu:5.0.2/LRX22G/1649326:user/release-keys
02-13 16:24:20.565 I/Xposed ( 348): Platform: armeabi-v7a, 32-bit binary, system server: yes
02-13 16:24:20.565 I/Xposed ( 348): SELinux enabled: yes, enforcing: yes
02-13 16:24:21.572 I/Xposed ( 348): -----------------
02-13 16:24:21.574 I/Xposed ( 348): Added Xposed (/system/framework/XposedBridge.jar) to CLASSPATH
02-13 16:24:22.296 I/Xposed ( 348): Detected ART runtime
02-13 16:24:22.373 I/Xposed ( 348): Found Xposed class de/robv/android/xposed/XposedBridge, now initializing
02-13 16:24:22.893 I/Xposed ( 348): Initializing XposedBridge version 60
02-13 16:24:23.094 I/Xposed ( 348): Errors during Xposed initialization
02-13 16:24:23.095 E/Xposed ( 348): java.io.FileNotFoundException: No such file or directory: /data/data/de.robv.android.xposed.installer/conf/modules.list
02-13 16:24:23.095 E/Xposed ( 348): at de.robv.android.xposed.services.ZygoteService.readFile(Native Method)
02-13 16:24:23.095 E/Xposed ( 348): at de.robv.android.xposed.services.BaseService.getFileInputStream(BaseService.java:116)
02-13 16:24:23.095 E/Xposed ( 348): at de.robv.android.xposed.XposedBridge.loadModules(XposedBridge.java:405)
02-13 16:24:23.095 E/Xposed ( 348): at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:103)

[2019.5.1][Magisk] Systemless Xposed v89.3/v90.2-beta3 (SDK 21-27)

Prerequisite
Magisk is required to be installed on your device!​Magisk - The Universal Systemless Interface​
Support Devices
All Magisk compatible devices
Downloads
My Xposed zip is universal across all architectures and Android versions.
https://androidfilehost.com/?fid=1395089523397956629
Install Guide
Install the XposedInstaller in the attachments
Follow the instructions in the Magisk release thread to install Magisk on to your device
Install Xposed within Magisk Manager's Download Section, or download the zip and flash in custom recovery
For uninstallation, remove the Xposed Magisk Module within Magisk Manager
Systemless Xposed does not pass SafetyNet!!!
Credits
@rovo89 for creating Xposed
Source
All binaries are downloaded and repacked from either places:
Official build from rovo89
I did not recompile/change anything how Xposed works, the behavior should be 100% identical to original sources, if you experience any Xposed issues, please directly report to the original threads.

Changelog
v87.0
- Include fix from rovo89 to prevent bootloops in the latest security patch
- Android 5.1 (SDK 22) was broken after one Magisk upgrade, it's now Magisk version independent
v86.6 (Downloaded 126324 times)
- Update to support the new repo system of Magisk
- Fixed incompatibility of suhide
v86.5 (Downloaded 174328 times)
- Update for the new API of Magisk v4
- NOTE: In order to update to Magisk v4, you are required to uninstall Magisk completely before upgrading. Please look at the main Magisk thread for more info
v86.4 (Downloaded 16246 times)
- Revert the disable to not mount method for Android Pay
- Fixed alt version script typo
v86.3
- Use Magisk as dependancy
- Support all the way back to Android 5.0
- Android Pay
v86.2 (Downloaded 30608 times)
- Script updates, more info here
v86.1 (Downloaded 10185 times)
- Minor fixes, release notes here
v86.0
- Massive update, see release notes here
v85.7 (Downloaded 15774 times)
- Hot fix for some devices which breaks proper init commands
v85.6
- Add SELinux label when executing script, should fix the few devices that aren't working
- Massively improve the script to handle /cache to /data migration (the rare case when /data isn't available in TWRP)
- Add Pixel C support (not-tested)
- Combine all architecture into an All-In-One flash zip, users will only need to be aware of their own Android version
v85.5
- Combine image mount and bind mount into one single script, should be more reliable and cleaner, hopefully it will fix ALL previous issues
- Add more logs to boot for debugging
- Add SDK 22 support (un-tested!!)
v85.4
- The mounting method should now support all devices
- The installer will now merge Xposed Image if possible, so feel free to place your own files under /xposed
v85.3
- Improved compatibility for some recoveries with incorrect libraries
- Changed the method to mount xposed.img, hopefully will fix issues on some devices
v85.2
- Separate Systemless Xposed from SuperSU. It now uses it's own image in data (/data/xposed.img)
- Won't effect SuperSU anymore. Both are now working independently
- Massively updated flash script, should be more reliable (e.g. Prefer sukernel in su.img over bundled binary)
- (Derived from Wanam's update) Add Huawei theming engine support (details); Ensure the recompilation on Huawei EMUI Roms (details).
v85.1
- Fixed flash script not installing files issue
v85.0
- Initial release

Wow! I will test it as soon as possible!
If you agree I can merge your changes in my build and add these zip files in the available zip files list to download

Updated the OP for more information

Thanks for experimenting with this!
I haven't installed it yet - I'm currently running XtreStoLite 3.1.1 with systemless SuperSu 2.74 and a conventional Wanam Xposed arm64 v85 installation on zeroflte (Galaxy S6).
Even with the conventional Xposed installation, toggling off Xposed in the latest rev (5/29) of @DVDandroid's installer and rebooting allows Android Pay to work. ART cache didn't rebuild either as noted in your post.
This is great progress!

5upon said:
Thanks for experimenting with this!
I haven't installed it yet - I'm currently running XtreStoLite 3.1.1 with systemless SuperSu 2.74 and a conventional Wanam Xposed arm64 v85 installation on zeroflte (Galaxy S6).
Even with the conventional Xposed installation, toggling off Xposed in the latest rev (5/29) of @DVDandroid's installer and rebooting allows Android Pay to work. ART cache didn't rebuild either as noted in your post.
This is great progress!
Click to expand...
Click to collapse
Oh really?!
This is cool, it seems that the Safety net check is not that strict lol

Any one test this xposed in Galaxy S7 ?
Edit.
I try on S7 and no framework loaded. ;-(

koko115 said:
Any one test this xposed in Galaxy S7 ?
Edit.
I try on S7 and no framework loaded. ;-(
Click to expand...
Click to collapse
Please follow the OP for bug report, thanks.
Send me your boot image after flashing the zip.

topjohnwu said:
Please follow the OP for bug report, thanks.
Send me your boot image after flashing the zip.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B86MsntyFnN1ZF9vbFAzM2pHemM/view?usp=drivesdk

koko115 said:
https://drive.google.com/file/d/0B86MsntyFnN1ZF9vbFAzM2pHemM/view?usp=drivesdk
Click to expand...
Click to collapse
Your boot image seems good.
What is your actual issue?
The framework doesn't work? Did you install the Xposed Installer stated in the OP (it has been updated)?
If you have all the things above, please post the screenshot go the Xposed Installer modules section, thanks

5upon said:
Thanks for experimenting with this!
I haven't installed it yet - I'm currently running XtreStoLite 3.1.1 with systemless SuperSu 2.74 and a conventional Wanam Xposed arm64 v85 installation on zeroflte (Galaxy S6).
Even with the conventional Xposed installation, toggling off Xposed in the latest rev (5/29) of @DVDandroid's installer and rebooting allows Android Pay to work. ART cache didn't rebuild either as noted in your post.
This is great progress!
Click to expand...
Click to collapse
This is actually not true on my side.
Disabling it will not make android pay to work. I just tested it.
I have to use systemless Xposed to pass safety net check.

topjohnwu said:
This is actually not true on my side.
Disabling it will not make android pay to work. I just tested it.
I have to use systemless Xposed to pass safety net check.
Click to expand...
Click to collapse
Hmm. How did you test? I used to get blocked by SafetyNet when I tried to add a card. Today, after deactivating Xposed and rebooting, I was able to add a card, but I haven't tried to make a purchase yet.
I'll switch to systemless Xposed the next time I update my ROM. Hopefully it will become the default install method. @rovo89 mentioned the possibility of going systemless a while ago but said he didn't plan to work on it.

topjohnwu said:
Your boot image seems good.
What is your actual issue?
The framework doesn't work? Did you install the Xposed Installer stated in the OP (it has been updated)?
If you have all the things above, please post the screenshot go the Xposed Installer modules section, thanks
Click to expand...
Click to collapse
{
"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"
}

I'm still not sure from reading the op or any posts whether ap works with this. Anything conclusive?

i Found one bug
i founded one bug, is in update-binary, doesnt extract xposed.prop ,xposedbridge.jar and libxposed_art.so.

In /su i dont see any xposed files
---------- Post added 30-05-2016 at 12:04 AM ---------- Previous post was 29-05-2016 at 11:40 PM ----------
I manually put missing this 3 files to /su and works great. THX

Thank you @koko115
OP updated with a version that should be working.
I forgot to put spaces in the previous release

The x86 version has a few downloads now.
Is the x86 working as expected? Can anyone report if it works?

I'm getting hung up on this step: "Flash systemless Xposed"
Would that be to say reboot into TWRP, press Install and pick the arm64 for my HTC 10?
Thanks!!
UPDATE: That's exactly what I did, worried I bricked my phone there for a second the boot logo took very long but now it's optimizing all the apps and starting up.
UPDATE 2: Success!!

Works great! Only the app says xposed 85.0 is installed but it's actually 85.1. Probably something you didn't edit because twrp also thought it was 85.0 [emoji2]
Sent from my SHIELD Tablet K1 using XDA-Developers mobile app

Help with Volume Warning!

Hello there!
Im new here so this is my first thread here ever, so my apologies if there are existing threads like these.
My Samsung S6 (SM-G920F) keeps showing up the volume warning on bluetooth/headsets, and i want to disable that.
unfortunately i have no custom ROMs onto my S6 and if i try to install xposed framework it tells me that my processor is not compatible yet (which results in having random soft-resets).
{
"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"
}
Translation: Xposed is not (yet) compatible with Android SDK-Version 23 or the Processor arm64-v8a.
I've installed xposed-v87.1-sdk23-arm64-custom-build-by-wanam-20161125 xposed framework, maybe its the wrong one?
i do still have root and custom recovery (TWRP)
Kernel Architecture: armv8l
Architecture: 4x ARM Cortex-A57 2,10 Ghz / 4x ARM Cortex-A53 1,50Ghz
Android Version: 6.0.1
so are there any options for getting rid of the volume warning, or is there a compatible xposed framework for my S6?
Thanks for reading my issue!

MCRandy said:
Hello there!
Im new here so this is my first thread here ever, so my apologies if there are existing threads like these.
My Samsung S6 (SM-G920F) keeps showing up the volume warning on bluetooth/headsets, and i want to disable that.
unfortunately i have no custom ROMs onto my S6 and if i try to install xposed framework it tells me that my processor is not compatible yet (which results in having random soft-resets).
Translation: Xposed is not (yet) compatible with Android SDK-Version 23 or the Processor arm64-v8a.
I've installed xposed-v87.1-sdk23-arm64-custom-build-by-wanam-20161125 xposed framework, maybe its the wrong one?
i do still have root and custom recovery (TWRP)
Kernel Architecture: armv8l
Architecture: 4x ARM Cortex-A57 2,10 Ghz / 4x ARM Cortex-A53 1,50Ghz
Android Version: 6.0.1
so are there any options for getting rid of the volume warning, or is there a compatible xposed framework for my S6?
Thanks for reading my issue!
Click to expand...
Click to collapse
Your problem is that you installed an old version of the Xposed Installer app, which is for Android versions before Lollipop. The latest version is v3.1.1 and it is available in the official download thread. Just search for "Xposed Lollipop Marshmallow" and you'll find it. Furthermore, you need a special version of the Xposed framework itself, as the normal one isn't compatible with TouchWiz. Search for "wanam Xposed Samsung" for the correct thread.

Portgas D. Ace said:
Your problem is that you installed an old version of the Xposed Installer app, which is for Android versions before Lollipop. The latest version is v3.1.1 and it is available in the official download thread. Just search for "Xposed Lollipop Marshmallow" and you'll find it. Furthermore, you need a special version of the Xposed framework itself, as the normal one isn't compatible with TouchWiz. Search for "wanam Xposed Samsung" for the correct thread.
Click to expand...
Click to collapse
okay i got the xposed installer v 3.1.1. but cant find the special framework, can you send me a link please? i dont really trust myself in installing the wrong framework, i had a bootloop once...just need the right framework for my s6!
and the next thing is i dont know what odexed and deodexed means, so i need a proper tutorial on how to install the framework without any issues...

alright, sorry for the 2nd post.
you think i have the right framework now?
The red text says: It seems there is a known incompability (Samsung Touchwiz ROM) with your ROM.
You shouldnt install Xposed, Click here for more Information.
well i did install a framework fitting for Touchwiz ROM. And if thats the right framework, can i update it, or do i get the wrong framework again?

MCRandy said:
alright, sorry for the 2nd post.
you think i have the right framework now?
The red text says: It seems there is a known incompability (Samsung Touchwiz ROM) with your ROM.
You shouldnt install Xposed, Click here for more Information.
well i did install a framework fitting for Touchwiz ROM. And if thats the right framework, can i update it, or do i get the wrong framework again?
Click to expand...
Click to collapse
As long as you have installed the framework from here
https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
everything should be okay. You can try out by installing a module and see if it works.
There is a newer version of the framework available at wanam's thread (v87.1), just download it and flash it through recovery to update the framework. Don't forget to wipe cache&dalvik afterwards.
My advice: download the Uninstaller.zip in addition and place it onto your SD card. This way you can flash it to uninstall the framework in case of a bootloop.
The red text will pop up on all Samsung stock/TouchWiz-based ROM's, as the installer is only designed to install the official framework by rovo89. No need to worry about it.

Portgas D. Ace said:
As long as you have installed the framework from here
https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
everything should be okay. You can try out by installing a module and see if it works.
There is a newer version of the framework available at wanam's thread (v87.1), just download it and flash it through recovery to update the framework. Don't forget to wipe cache&dalvik afterwards.
My advice: download the Uninstaller.zip in addition and place it onto your SD card. This way you can flash it to uninstall the framework in case of a bootloop.
The red text will pop up on all Samsung stock/TouchWiz-based ROM's, as the installer is only designed to install the official framework by rovo89. No need to worry about it.
Click to expand...
Click to collapse
ahh! i see now! i was always confused by the red text! thank you very much!
EDIT: oh! one last thing, whenever i go fullscreen on youtube or camera, Touchwiz Start stops working, is it because i didnt get the latest version of the framework, is this error message dangerous what means TouchWiz Start?
TouchWiz Start stopped working.

MCRandy said:
...
EDIT: oh! one last thing, whenever i go fullscreen on youtube or camera, Touchwiz Start stops working, is it because i didnt get the latest version of the framework, is this error message dangerous what means TouchWiz Start?
Click to expand...
Click to collapse
I don't have any idea why it crashes. My best suggestion would be to check over at your device's subforum here on XDA. Maybe someone has/had a similar issue and posted a solution.
You could try to update the framework (just flash newer version through recovery and wipe cache&dalvik afterwards) and see if the issue is gone, otherwise ask for help in the above suggested subforum.

Portgas D. Ace said:
I don't have any idea why it crashes. My best suggestion would be to check over at your device's subforum here on XDA. Maybe someone has/had a similar issue and posted a solution.
You could try to update the framework (just flash newer version through recovery and wipe cache&dalvik afterwards) and see if the issue is gone, otherwise ask for help in the above suggested subforum.
Click to expand...
Click to collapse
well i updated the frame work through recovery, it just showed me framework version 87 without wanam in, so i guess its the wrong version because its not compatible with touchwiz?

MCRandy said:
well i updated the frame work through recovery, it just showed me framework version 87 without wanam in, so i guess its the wrong version because its not compatible with touchwiz?
Click to expand...
Click to collapse
Did you download the framework (v87) from wanam's thread or through the installer? If you were able to reboot your device after flashing the latest version without any bootloop, then you got the correct one. The wrong one will result in a bootloop.

Portgas D. Ace said:
Did you download the framework (v87) from wanam's thread or through the installer? If you were able to reboot your device after flashing the latest version without any bootloop, then you got the correct one. The wrong one will result in a bootloop.
Click to expand...
Click to collapse
well i updated/downloaded the framework through installer, flashed it with TWRP, cleared cache/dalvik booted the phone back up and my s6 is fully functional, so no bootloop! so that means i can keep this framework even though its not from wanam?
and what also confuses is, that the update is version 87, and wanam's is 87.1.

MCRandy said:
well i updated/downloaded the framework through installer, flashed it with TWRP, cleared cache/dalvik booted the phone back up and my s6 is fully functional, so no bootloop! so that means i can keep this framework even though its not from wanam?
and what also confuses is, that the update is version 87, and wanam's is 87.1.
Click to expand...
Click to collapse
Strange, but I have to confess my knowledge on the new Xposed Installer v3.1.1 is rather limited as I use the unofficial materialized version and always flash the framework through recovery. So my idea would be to download the latest framework version from wanam and flash it through recovery. This should indeed update your device to the latest framework version.

[Magisk][Module] EMUI 8 Debloater [8/7]

Hi everyone
i made this magisk module to "remove/hide" Huawei/Google apps from your ROM, here is a list of the the variants*:
Gapps - Debloating Extra Google Apps only while keeping Playstore/Play Services
Gapps-Keep-Only - Keeps Gapps only
Gapps-Keep-Only+ - Keeps Gapps only, while Replacing Huawei Launcher with Lean
Minimal - Debloating Extra Google/Huawei Apps only, while keeping most Huawei Apps in
Full - Debloating Most Google/Huawei Apps, while keeping Huawei Launcher
Full+ - Debloating Most Google/Huawei Apps, while Replacing Huawei Launcher with Lean
*Click on names to check debloated apps list
Screenshots of the outcome after using any of the modules:
Gapps Debloat
{
"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"
}
Gapps Keep/+
Minimal
Full/+
Download:
Drive Folder
How to use it ?, Install Module with Magisk, then reboot
How to revert back ?, Remove the module from magisk and reboot and everything should be back
Report back for any problems, so i can edit the script or look into it
Enjoy!!

Changlog:
v0.2
-Removed Gallery, Phone Manager, Files, Chrome & Screenshot related apps from Debloat list

and this also

Voted up, looks nice but unfortunately cant try as post debranding, unable to unlock bootloader with same old code.

updated all zips with less apps debloated

Have Magisk 17.1 and ZIP file is grayed out in Magisk Manager 5.9.1 . Can u help?
EDIT: Issue fixed: it was problem with file permissions

Thank you for your work buddy, it's a really useful for debloating emui I'm surprised there's not a lot of traction on this module. There's a slight problem, YouTube is removed, and I can't install vanced. I think everyone uses the YouTube app, no reason to remove it. Other than that great work.

thanks ....bought my first huawei recently ....this module works well without fc or other problems when deleting bloat from system permanently in twrp ..good job ...like previous guy said ..not sure why this isn't more popular ..:good:

Can help me? when flash It all look nice, but when reboot the phone, It module no appear un magisk
My phone is a Mate 10 lite with stock Room
It module dont work for me
I have emui 8
Magisk 20.4
What should i do?

Milor123 said:
Can help me? when flash It all look nice, but when reboot the phone, It module no appear un magisk
My phone is a Mate 10 lite with stock Room
It module dont work for me
I have emui 8
Magisk 20.4
What should i do?
Click to expand...
Click to collapse
It's an old module, so if you take a look in the module install log you'll likely see that there are a whole bunch of errors.
https://www.didgeridoohan.com/magis...em_to_install_but_arent_there_after_rebooting

Didgeridoohan said:
It's an old module, so if you take a look in the module install log you'll likely see that there are a whole bunch of errors.
https://www.didgeridoohan.com/magis...em_to_install_but_arent_there_after_rebooting
Click to expand...
Click to collapse
Ohh, i understand, thank you very mucho
Can you help me?
This is the log file
Code:
- Copying zip to temp directory
- Installing [Magisk]-EMUI-8-Full-Debloat.zip
update-binary: line 54: get_outfd: not found
Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip
inflating: module.prop
creating: common/
inflating: common/post-fs-data.sh
inflating: common/service.sh
inflating: common/system.prop
inflating: config.sh
********************
EMUI Debloater
[email protected]
********************
******************************
Powered by Magisk (@topjohnwu)
******************************
update-binary: line 101: mount_magisk_img: not found
- Extracting module files
Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip
creating: system/
inflating: system/placeholder
- Disabling bloatware apps
java.lang.ClassNotFoundException: Didn't find class "com.android.commands.pm.Pm" on path: DexPathList[[zip file "/system/framework/pm.jar"],nativeLibraryDirectories=[/system/lib64, /vendor/lib64, /product/lib64, /system/lib64, /vendor/lib64, /product/lib64]]
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:93)
at java.lang.ClassLoader.loadClass(ClassLoader.java:379)
at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
Suppressed: java.io.IOException: No original dex files found for dex location /system/framework/pm.jar
at dalvik.system.DexFile.openDexFileNative(Native Method)
at dalvik.system.DexFile.openDexFile(DexFile.java:353)
at dalvik.system.DexFile.<init>(DexFile.java:100)
at dalvik.system.DexFile.<init>(DexFile.java:74)
at dalvik.system.DexPathList.loadDexFile(DexPathList.java:374)
at dalvik.system.DexPathList.makeDexElements(DexPathList.java:337)
at dalvik.system.DexPathList.<init>(DexPathList.java:157)
at dalvik.system.BaseDexClassLoader.<init>(BaseDexClassLoader.java:65)
at dalvik.system.PathClassLoader.<init>(PathClassLoader.java:64)
at java.lang.ClassLoader.createSystemClassLoader(ClassLoader.java:224)
at java.lang.ClassLoader.-wrap0(Unknown Source:0)
at java.lang.ClassLoader$SystemClassLoader.<clinit>(ClassLoader.java:183)
at java.lang.ClassLoader.getSystemClassLoader(ClassLoader.java:1107)
Aborted
java.lang.ClassNotFoundException: Didn't find class "com.android.commands.pm.Pm" on path: DexPathList[[zip file "/system/framework/pm.jar"],nativeLibraryDirectories=[/system/lib64, /vendor/lib64, /product/lib64, /system/lib64, /vendor/lib64, /product/lib64]]
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:93)
at java.lang.ClassLoader.loadClass(ClassLoader.java:379)
at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
Suppressed: java.io.IOException: No original dex files found for dex location /system/framework/pm.jar
at dalvik.system.DexFile.openDexFileNative(Native Method)
at dalvik.system.DexFile.openDexFile(DexFile.java:353)
at dalvik.system.DexFile.<init>(DexFile.java:100)
at dalvik.system.DexFile.<init>(DexFile.java:74)
at dalvik.system.DexPathList.loadDexFile(DexPathList.java:374)
at dalvik.system.DexPathList.makeDexElements(DexPathList.java:337)
at dalvik.system.DexPathList.<init>(DexPathList.java:157)
at dalvik.system.BaseDexClassLoader.<init>(BaseDexClassLoader.java:65)
at dalvik.system.PathClassLoader.<init>(PathClassLoader.java:64)
at java.lang.ClassLoader.createSystemClassLoader(ClassLoader.java:224)
at java.lang.ClassLoader.-wrap0(Unknown Source:0)
at java.lang.ClassLoader$SystemClassLoader.<clinit>(ClassLoader.java:183)
at java.lang.ClassLoader.getSystemClassLoader(ClassLoader.java:1107)
- Setting permissions
Aborted
update-binary: line 150: unmount_magisk_img: not found
- Done
What could i do? I want use It like magisk module becasue if It can generate a bootloop, then its very easy of.solve

Milor123 said:
What could i do? I want use It like magisk module becasue if It can generate a bootloop, then its very easy of.solve
Click to expand...
Click to collapse
The module need to be updated to work with the current installation logic. That's not something I can help you with, and unfortunately it looks like @AL_IRAQI abandoned the module some time ago.

Didgeridoohan said:
The module need to be updated to work with the current installation logic. That's not something I can help you with, and unfortunately it looks like @AL_IRAQI abandoned the module some time ago.
Click to expand...
Click to collapse
Ohh understand ?, thank you very much !