Related
running galaxy s5 here on rogers G900W8 all info in my signature.
rooted with twrp recovery installed ,
when I install Xposed framework and reboot my S Health app crashes " unfortunately S health has stopped"
I don't have any moduals installed , I think another post back in this thread said it had to do with the multi window but mine is off and nothing enabled on it. I attached my logs not much there but I have also uninstalled s health app cleared data and reinstalled it and xposed a few times to no avail
someone reported it had to do with the multi window but I don't use that feature and never turned it on.
just trying to make it so I am able to use an xposed or wanam and still be able to use s health without it crashing.
ex-28 said:
running galaxy s5 here on rogers G900W8 all info in my signature.
rooted with twrp recovery installed ,
when I install Xposed framework and reboot my S Health app crashes " unfortunately S health has stopped"
I don't have any moduals installed , I think another post back in this thread said it had to do with the multi window but mine is off and nothing enabled on it. I attached my logs not much there but I have also uninstalled s health app cleared data and reinstalled it and xposed a few times to no avail
someone reported it had to do with the multi window but I don't use that feature and never turned it on.
just trying to make it so I am able to use an xposed or wanam and still be able to use s health without it crashing.
Click to expand...
Click to collapse
Mine does the same. S Health crashes and does not work at all. No heart beat monitor for me. The only way to get S health back is to uninstall xposed then restore a backup and reinstall S Health
jawmail said:
Mine does the same. S Health crashes and does not work at all. No heart beat monitor for me. The only way to get S health back is to uninstall xposed then restore a backup and reinstall S Health
Click to expand...
Click to collapse
ok so its not just me , I need to figure out how to correct this I really need xposed.
I asked the same q on another thread , response was the following . but I don't understand it , as I don't use multi window at all hoping and preying someone else comes along to shed some light on this matter.
@rovo89
It seems that this module still tries to activate itself by manipulating the modules.list with root permissions. I just installed it myself and indeed that happened. I wasn't asked, not even informed, and it wasn't reflected in the Xposed UI. So it's basically operating like a root kit. That's especially bad when users suspect a bug in the framework because they seemingly didn't have any active modules.
Please solve this bug (or feature) as soon as possible. You can open the Xposed Installer directly in the modules section, but manipulating its files is not acceptable.
FYI, on my stock AT&T S5 I had S Health "go bad" a little bit, finishing building a Samsung ID and updating it from their store fixed it.
Don't know if that helps or not, just a data point.
ex-28 said:
ok so its not just me , I need to figure out how to correct this I really need xposed.
I asked the same q on another thread , response was the following . but I don't understand it , as I don't use multi window at all hoping and preying someone else comes along to shed some light on this matter.
rovo89
It seems that this module still tries to activate itself by manipulating the modules.list with root permissions. I just installed it myself and indeed that happened. I wasn't asked, not even informed, and it wasn't reflected in the Xposed UI. So it's basically operating like a root kit. That's especially bad when users suspect a bug in the framework because they seemingly didn't have any active modules.
Please solve this bug (or feature) as soon as possible. You can open the Xposed Installer directly in the modules section, but manipulating its files is not acceptable.
Click to expand...
Click to collapse
You forgot to use the @ to mention @rovo89.
Good to hear I'm not the only one either. S Health stopped opening from the exact same steps as OP.
I tried disabling and enabling the app, re-downloading the updates from Samsung but that didn't fix it.
Any information on why S Health crashes would be helpful.
Have you tried uninstalling the updates for s health? I'm stuck with the g900a for now so i don't have xposed yet, but when s health updated it would constantly error out until i got rid of the update.
Greycloak42 said:
Have you tried uninstalling the updates for s health? I'm stuck with the g900a for now so i don't have xposed yet, but when s health updated it would constantly error out until i got rid of the update.
Click to expand...
Click to collapse
I used TitaniumBackup to merge the update into the system. It didn't like that, caused my wifi to go haywire.
Moving the health app out to a user app fixed it though.
jawmail said:
Mine does the same. S Health crashes and does not work at all. No heart beat monitor for me. The only way to get S health back is to uninstall xposed then restore a backup and reinstall S Health
Click to expand...
Click to collapse
Xeio said:
I used TitaniumBackup to merge the update into the system. It didn't like that, caused my wifi to go haywire.
Moving the health app out to a user app fixed it though.
Click to expand...
Click to collapse
so you have s health running with xposed or wanam installed ?
i did not install Xposed framework but root the phone, after that the S health stopped running and popped up a failure notice, it might be due to root, I guess.
siyue78 said:
i did not install Xposed framework but root the phone, after that the S health stopped running and popped up a failure notice, it might be due to root, I guess.
Click to expand...
Click to collapse
I don't think root is the problem , as my phone and many others arerooted with twrp installed and shealth was working 100 % something to do with the xposed and / or wanam
divineiniquity said:
Good to hear I'm not the only one either. S Health stopped opening from the exact same steps as OP.
I tried disabling and enabling the app, re-downloading the updates from Samsung but that didn't fix it.
Any information on why S Health crashes would be helpful.
Click to expand...
Click to collapse
I had the same issue after installing xposed. I had to uninstall it and then convert s health to a user app and completely uninstall it (clearing data and/or removing updates didn't work for me). Also I removed updates from HealthService. After that I install S health again from Samsung store and is working again.
S Health is bugged as hell right now though.
Sent from my SM-G900H using XDA Premium 4 mobile app
mindol81 said:
I had the same issue after installing xposed. I had to uninstall it and then convert s health to a user app and completely uninstall it (clearing data and/or removing updates didn't work for me). Also I removed updates from HealthService. After that I install S health again from Samsung store and is working again.
S Health is bugged as hell right now though.
Sent from my SM-G900H using XDA Premium 4 mobile app
Click to expand...
Click to collapse
after you reinstalled s health is it running ok now with xposed installed ? if so could you please give more details on the steps you took and it is just xposed or wanam you have
I haven't reinstall xposed yet... Getting SHealth to work again has been a pain. Better to wait for a fix.
Sent from my SM-G900H using XDA Premium 4 mobile app
mindol81 said:
I haven't reinstall xposed yet... Getting SHealth to work again has been a pain. Better to wait for a fix.
Sent from my SM-G900H using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yah it took me a while to get s health working again as well , hoping for a fix soon.
Can confirm this on a Sprint S5. Rooted with chainfire autoroot and installed xposed and TWRP 2.7 and had S Health and Healthservices crashing like a drunk teenager. Uninstalled xposed and rebooted, S health now works. Guess I have to sit through Youtube ads for a while.
Ahh... Thought the problem was only for me. Hope @rovo89 could fix it soon.
may be can help to find the problem
hi everybody, i am a noob in android ect, BUT maybe it can help you : i am on i9500 omegaV20 perseus18, i modded my phones with root explorer, i add libs, perms, framework ect, modify my build prop /SM-G900F/kltexx/jfltexx , i did a lot of upgrade in samsung app store, AND I GOT S5 APPs WORK perfect, health widget work ect all works, and i got xposed ...
so to resume : i got S5 healths WORKING perfectly with xposed. hope it can help you.
Yup I also installed a different rom all working great now
Sent from my Sm-G900W8 using Tapatalk
I had the same concern, and after installing a new firmware on the SM-G900f .
I took the opportunity to not do the update shealth and securestorage..I can enjoy and wanam, Xposed
no problems with health
Having used xposed before and it messed up shealth I'm a little reluctant to use it again, does anyone know if it now works or if it still causes issues with it? I use the gear fit and would like to continue using it. Anything anyone knows would be helpful.
Thanks.
I'm still having issues with it not letting S-Health open. I've tried several solutions that have worked for others with no luck.
Ah i see, so others have reported it working for them? My phones OK, I'd just like the flexibility to use the mods if possible.
When I tried it last, it opened but slowed the phone down so much it was unusable until u kill the process.
Anyone else have any input about this?
Just found an xposed downloaded called "XSecure Storage". I installed it and now S-Health is working great!
Works.
That works on my mine. Thank you!!
Nice one slick dealers
I have already problems with S Health
Secure_storage is true
XSecureStorage is active
I use the Build Prop Editor to change the value to false, but after a restart the value ist at true
At S Health I have Problems to restore and backup my Data.
I used xstreolite and have s-health and xposed working flawlessly together. maybe xposed was updated since then
I'm using xsecure have you updated xposed? It needs to be on a new version. I'm using the latest stable version, think it's 32
Hey guys .. Really didnt wanted to open a new thread but i was reading through many threads in the past days and didnt find a solution. Ive installed viper4android as system app and changed selinux to permissive. But it just doesnt work
Is there anybody facing the same or is there anything i missed?
Thanks in advance
This is what driver status says...
Btw im on lp 30b with stock kernel
I'm getting the same problem on my ls980 (Sprint var.)
I'm running a lollipop ROM, (Resurrection Remix)
This is in lollipop 5.1, however.
Very sad though... I LOVE viper. Probably one of my biggest reasons for root, besides custom ROMs and Xposed.
Hopefully this will be looked into.
---EDIT---
My driver status is listed as abnormal, and not enabled.
Probably means I'm even worse off than you
Collserra said:
I'm getting the same problem on my ls980 (Sprint var.)
I'm running a lollipop ROM, (Resurrection Remix)
This is in lollipop 5.1, however.
Very sad though... I LOVE viper. Probably one of my biggest reasons for root, besides custom ROMs and Xposed.
Hopefully this will be looked into.
---EDIT---
My driver status is listed as abnormal, and not enabled.
Probably means I'm even worse off than you [emoji14]
Click to expand...
Click to collapse
I'm on D802 lollipop and viper4android installed. It worked very nicely for few days. But suddenly stopped working. I've tried reinstalling many times and even added the build.prop settings mentioned in one thread.
But now it just doesn't work. The status says abnormal. And whenever I open the app, music stops playing. Hope someone can help us.
Alleks1802 said:
Hey guys .. Really didnt wanted to open a new thread but i was reading through many threads in the past days and didnt find a solution. Ive installed viper4android as system app and changed selinux to permissive. But it just doesnt work
Is there anybody facing the same or is there anything i missed?
Thanks in advance
Click to expand...
Click to collapse
Collserra said:
I'm getting the same problem on my ls980 (Sprint var.)
I'm running a lollipop ROM, (Resurrection Remix)
This is in lollipop 5.1, however.
Very sad though... I LOVE viper. Probably one of my biggest reasons for root, besides custom ROMs and Xposed.
Hopefully this will be looked into.
---EDIT---
My driver status is listed as abnormal, and not enabled.
Probably means I'm even worse off than you
Click to expand...
Click to collapse
droidfan88 said:
I'm on D802 lollipop and viper4android installed. It worked very nicely for few days. But suddenly stopped working. I've tried reinstalling many times and even added the build.prop settings mentioned in one thread.
But now it just doesn't work. The status says abnormal. And whenever I open the app, music stops playing. Hope someone can help us.
Click to expand...
Click to collapse
Check my guide for poweramp and v4a, it might just be the thing to fix it.
Thanks man. It turned out that somehow my selinux had become enforcing. Changed it to permissive and things work as expected.
Check ,,Use ,,NuPlayer'' '' in developer setting.
And install SELinux Enabler script via recovery : http://blastagator.ddns.net/dorimanx.php
I own a Coolpad Note 3 running on Android 5.1 Lollipop and packs MT6753 MediaTek 64-bit octacore processor and 3GB RAM. After rooting this device, when I installed Xposed Framework, though it installed successfully but shows a message that this version isn't supported yet. What is this message and when is this platform going to get supported. This was heartbreaking because the major reason of rooting the device was this Framework.
What version of Xposed did you attempt to install? What method did you use to install? What does it say in the log file? We cannot help you without this information.
Details of installed version of Xposed Framework
Spott07 said:
What version of Xposed did you attempt to install? What method did you use to install?
Click to expand...
Click to collapse
First, I tried official version of Xposed Installer for lollipop devices. It was a failure(a message popped out after installing that Xposed is not yet supported on this processor platform). Then I referred to the blog Android Beat(How to install Xposed framework on Android 5.1 Lollipop) and downloaded this file "xposed-v78-sdk22-arm64.zip". I flashed it using custom recovery based on CWM. I was stuck in a boot loop after that. Then I was left with no option but to flash my stock ROM as I had no backup at that time.
TheGuyIsHere said:
First, I tried official version of Xposed Installer for lollipop devices. It was a failure(a message popped out after installing that Xposed is not yet supported on this processor platform). Then I referred to the blog Android Beat(How to install Xposed framework on Android 5.1 Lollipop) and downloaded this file "xposed-v78-sdk22-arm64.zip". I flashed it using custom recovery based on CWM. I was stuck in a boot loop after that. Then I was left with no option but to flash my stock ROM as I had no backup at that time.
Click to expand...
Click to collapse
Please refer to the official Xposed for Lollipop thread, especially post #2. There you'll find an FAQ about common issues and a table to identify the correct Xposed version. You need to flash the correct .zip file through recovery (as you have done before) and install the Xposed_Installer_alpha3.apk afterwards. After flashing, wipe cache&dalvik, as Xposed alters a lot of files in your system, so this step is highly recommended. If this does not solve your issue, search the thread, there have been several questions about Mediatek compatibility before.
Your initial error (Xposed not compatible) was due to the fact that you tried to install the old Xposed installer for KitKat, which is not compatible with Lollipop.
Noted.
I am definitely going to refer to that thread and will update here after that. Thanks for your precious time.
Some advancements
A guy using Coolpad note 3 tried a method to install Xposed and it worked(to some extent though). What he did was he installed busybox, flashed the Xposed zip files. After rebooting, he still got caught in a bootloop but after 15-20 boot loops(seems like it depends on no. of apps installed as each time his phone booted, percentage of optimising apps increased), he was finally able to start his phone. Now under Xposed settings, he checked disable resourced hooks and rebooted. He got Xposed Framework active status after rebooting. A no. of apps which modify UI like gravitybox, xblastools, greenify in root mode etc were not working. But a few others worked quiet well. Could anyone throw some light on this issue?
TheGuyIsHere said:
A guy using Coolpad note 3 tried a method to install Xposed and it worked(to some extent though). What he did was he installed busybox, flashed the Xposed zip files. After rebooting, he still got caught in a bootloop but after 15-20 boot loops(seems like it depends on no. of apps installed as each time his phone booted, percentage of optimising apps increased), he was finally able to start his phone. Now under Xposed settings, he checked disable resourced hooks and rebooted. He got Xposed Framework active status after rebooting. A no. of apps which modify UI like gravitybox, xblastools, greenify in root mode etc were not working. But a few others worked quiet well. Could anyone throw some light on this issue?
Click to expand...
Click to collapse
Unless you're the one trying it, and you can supply full logcats for the entire multi-reboot process, we probably can't know for sure.
Spott07 said:
Unless you're the one trying it, and you can supply full logcats for the entire multi-reboot process, we probably can't know for sure.
Click to expand...
Click to collapse
I will try it myself and hopefully provide logcats for the entire multi-boot process.
Can you please share which version of xposed you used because I did the same and it was stuck on bootloop then I realized that the % of starting up apps was increasing gradually but after 3-4 attemps it went down and started from zero and so I flashed it again.
I think the issue is that i used xposed arm64-v78 sdk22 but my device is arm64-v8a, and I guess xposed is not yet released for arm64-v8a sdk22 devices.
So finally with this thread I got a hope to try it again and please share as much info as you can coz its gonna help others a lot
I came back here to give the good news that I did it.
But glad to know that we already got the tutorial.
One problem: donkey guard module is not working, showing unfortunately donkey guard has stopped working.
Any solution???
Btw thank you so much coz know a lot of people have been searching for it from aaa long time.
mukeshkhan2008 said:
I came back here to give the good news that I did it.
But glad to know that we already got the tutorial.
One problem: donkey guard module is not working, showing unfortunately donkey guard has stopped working.
Any solution???
Btw thank you so much coz know a lot of people have been searching for it from aaa long time.
Click to expand...
Click to collapse
DonkeyGuard module won't work on lollipop. Any app that changes system behaviour seems to have not worked on this platform yet. Refer to this post for more info:
https://m.reddit.com/r/Android/comments/2vt70q/xposed_for_lollipop_is_out_lets_get_a_list_of/
mukeshkhan2008 said:
I came back here to give the good news that I did it.
But glad to know that we already got the tutorial.
One problem: donkey guard module is not working, showing unfortunately donkey guard has stopped working.
Any solution???
Btw thank you so much coz know a lot of people have been searching for it from aaa long time.
Click to expand...
Click to collapse
can u please tell me how to install xposed in cp3?
Using which phone?
mukeshkhan2008 said:
I came back here to give the good news that I did it.
But glad to know that we already got the tutorial.
One problem: donkey guard module is not working, showing unfortunately donkey guard has stopped working.
Any solution???
Btw thank you so much coz know a lot of people have been searching for it from aaa long time.
Click to expand...
Click to collapse
U used it on Coolpad Note 3???
TheGuyIsHere said:
I own a Coolpad Note 3 running on Android 5.1 Lollipop and packs MT6753 MediaTek 64-bit octacore processor and 3GB RAM. After rooting this device, when I installed Xposed Framework, though it installed successfully but shows a message that this version isn't supported yet. What is this message and when is this platform going to get supported. This was heartbreaking because the major reason of rooting the device was this Framework.
Click to expand...
Click to collapse
Hello I have the same phone too but how did you root it
Rooting method
arjithpraison said:
Hello I have the same phone too but how did you root it
Click to expand...
Click to collapse
Here is the step-by-step guide to root Coolpad Note 3:
http://www.anythingultimate.in/2015/10/how-to-root-coolpad-note-3.html?m=1
Follow the guide and you will be successfully able to root your phone. Best of luck!
Do hit thanks if this post helped you.
wanting xposed un istaller for coolpad note 3
Hey i m installing xposed version 78 running good but u want to fully un root & un install xposed frame work for getting new android version update marsh mallow 6.0 for this mobile in next week so i want to update thats why i want fully un root also ( im using super su ) so plz help.me suggeat which vesion of unistaller i want to use for rempving xposed frame work
santosh reddy 143 said:
Hey i m installing xposed version 78 running good but u want to fully un root & un install xposed frame work for getting new android version update marsh mallow 6.0 for this mobile in next week so i want to update thats why i want fully un root also ( im using super su ) so plz help.me suggeat which vesion of unistaller i want to use for rempving xposed frame work
Click to expand...
Click to collapse
You can find the uninstaller in the same thread where you have found the correct Xposed framework version for your device. Use the same specs (SDK version, ARM version) as for the Xposed framework for the uninstaller and flash it. Don't forget to wipe cache&dalvik afterwards.
I installed xposed but when I click reboot it says
de.robv.android.xposed.installer/cache/busybox-xposed: not found
sxda7 said:
I installed xposed but when I click reboot it says
de.robv.android.xposed.installer/cache/busybox-xposed: not found
Click to expand...
Click to collapse
did you install busybox?
Nergal di Cuthah said:
did you install busybox?
Click to expand...
Click to collapse
yes but i don't know why it keeps saying that everytime i try to reboot xposed
I don't know why but the installed modules of Xposed are not working ... I'm using version 89 and version 3.1.5 of Xposed. My Note 4 is the N910C. Already uninstalled and reinstalled and it did not work. On my mother's Galaxy Note 4 too. The Android we use is MM 6.0.1. Can anyone give a suggestion?
S3Killer said:
I don't know why but the installed modules of Xposed are not working ... I'm using version 89 and version 3.1.5 of Xposed. My Note 4 is the N910C. Already uninstalled and reinstalled and it did not work. On my mother's Galaxy Note 4 too. The Android we use is MM 6.0.1. Can anyone give a suggestion?
Click to expand...
Click to collapse
1. Why not asking directly to xposed threads, probably you can get more answers there?
Also try to provide logs to the module developer so that he can have a look into it.
2. If I may, my suggestion would be to stop using that cancer called xposed.
It has 2 major issues:
A. it's a (wide) security hole - it is using a hijacks method ("hooking") and can modify the structure of the os to do whatever they want. This is why the battery life of xposed-enabled phones is worse and performance takes a hit. Actually xposed recompiles the entire ROM after it is installed.
B. it creates bugs by breaking the API's of system and/or user apps.I
I have the same phone and used xposed long time ago (2-3 years ago). But now I'm happy with Lineage OS and also good use of spen.
Check it on the exynos threads, if you like.
You choose.