Hello all,
I'm new to Note 3 but I've got stick to S Health using SGS4.
But any of installed ROMs such as Omega and Foxhound for SGN3 causes S Health to crash. And its only crashes when recovered from backup (of course with patch) and after filling the profile.
How could I fix it?
Phelicks said:
Hello all,
I'm new to Note 3 but I've got stick to S Health using SGS4.
But any of installed ROMs such as Omega and Foxhound for SGN3 causes S Health to crash. And its only crashes when recovered from backup (of course with patch) and after filling the profile.
How could I fix it?
Click to expand...
Click to collapse
what kind of mods do you use? xposed and especially wanam is known for causing troubles with s-health! try to disable them and look if the FC is still present!
TML1504 said:
what kind of mods do you use? xposed and especially wanam is known for causing troubles with s-health! try to disable them and look if the FC is still present!
Click to expand...
Click to collapse
Yes, I use xposed, but not Wanam. But the list of modules didnot cause such problem on SGS4.
If you mod multi window app with exposed, s.health will fc
Sent from my SM-N9005 using Tapatalk
Related
S health is crashing on launch. I have narrowed it down to the Xpose Multi window Mod [1.3]. Is there a fix for this or an updated for the Multi window mod? I found this one http://forum.xda-developers.com/showthread.php?t=2048668 but it is for the note II and its ver. 3.1 . Not sure if this will work on the S4.
Sudo_Kapa said:
S health is crashing on launch. I have narrowed it down to the Xpose Multi window Mod [1.3]. Is there a fix for this or an updated for the Multi window mod? I found this one http://forum.xda-developers.com/showthread.php?t=2048668 but it is for the note II and its ver. 3.1 . Not sure if this will work on the S4.
Click to expand...
Click to collapse
Im looking for the same thing for my Sprint S4...wondering if you ever found a fix?
Found no fix
I have not found a fix for this. I am currently on xposed v12 and am still having this problem. Multi window is more useful to me so I have learned to live with out S health.
Use multi Window manager in the Google app store. It does the same thing, and doesn't conflict with s health.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Hey guys on G900I stock rooted rom untill slimbeam or paranoid comes out, I had disabled s health and other bloat around about the time the "health service has stopped working" but also did some tweaks so i'm not sure what one caused the problem, but i've completely removed s health and i cant see anywhere in system apps/services "health service" just want it gone so the error doesn't come up. I get it about 4-5 times a day. Any help would be appreciated
Did you installed xposed framework? If yes.. That's the reason.
Sent from my SM-G900H using XDA Premium 4 mobile app
mindol81 said:
Did you installed xposed framework? If yes.. That's the reason.
Sent from my SM-G900H using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah damn, I'll uninstall it for now until a decent rom is out. Cheers dude.
Offica said:
Yeah damn, I'll uninstall it for now until a decent rom is out. Cheers dude.
Click to expand...
Click to collapse
I am having the same problem even after I unistalled xposed framework. Please advise.
To revert, you need to clear the system cache and the Shealth app cache and data.
Lots of threads on how to solve that, you can find lots of elaboration in existing threads if you search.
In short you can have Shealth and Xposed working if you disable secure storage - which breaks private mode, et cetera.
Or you can revert. Basically: Shealth, Xposed, Private mode. Pick any two.
.
Anyone had safely tested xposed on Note 4?
Tmo note 4 here, xposed seems to have broken s health and private mode from what I've found so far.
So it's pretty much the same as S5, I wonder the fix in S5 will work on Note 4. I remember changing some values in a file when I was on S5 with xposed.
Edit:
Just found what I changed last time:
Change in the build.prop:
ro.securestorage.support=false
From 'true' to 'false'.
Anyone brave enough to try?
killkyo said:
So it's pretty much the same as S5, I wonder the fix in S5 will work on Note 4. I remember changing some values in a file when I was on S5 with xposed.
Edit:
Just found what I changed last time:
Change in the build.prop:
ro.securestorage.support=false
From 'true' to 'false'.
Anyone brave enough to try?
Click to expand...
Click to collapse
Tried already, but seems doesn't work. So, I freeze S-health right away.....
There is an Xposed module that should fix this by @wanam I don't know if it will work on the Note 4 like it does on the S5 though.
HERE
badwolf94 said:
There is an Xposed module that should fix this by @wanam I don't know if it will work on the Note 4 like it does on the S5 though.
HERE
Click to expand...
Click to collapse
dude! i love you so much right now lol. i thought i was sol. i tried changing the value in build prop but it actually caused Nova Launcher to crash until i changed it back. (weird i know) has anyone tried using the module on the note 4 yet?
knarfies said:
dude! i love you so much right now lol. i thought i was sol. i tried changing the value in build prop but it actually caused Nova Launcher to crash until i changed it back. (weird i know) has anyone tried using the module on the note 4 yet?
Click to expand...
Click to collapse
The method you mentioned with the changing of the build.prop is reliant on more than just the changing of ro.securestorage.support=true.
1. Make sure you don't have Xposed installed, if you do uninstall it.
2. Then change ro.securestorage.support=true to ro.securestorage.support=false.
3. Install Xposed Framework.
4. Wipe the data from S Health and HealthService.
5. Reboot.
P.S. Pretty sure this method doesn't fix Private Mode
badwolf94 said:
The method you mentioned with the changing of the build.prop is reliant on more than just the changing of ro.securestorage.support=true.
1. Make sure you don't have Xposed installed, if you do uninstall it.
2. Then change ro.securestorage.support=true to ro.securestorage.support=false.
3. Install Xposed Framework.
4. Wipe the data from S Health and HealthService.
5. Reboot.
P.S. Pretty sure this method doesn't fix Private Mode
Click to expand...
Click to collapse
so i would rather go the module fix route then. Once we can get someone to confirm activating it doesn't hose up the phone of course.
I installed Xposed for a few hours, it made the phone very laggy, so I uninstalled it.
Scaven said:
I installed Xposed for a few hours, it made the phone very laggy, so I uninstalled it.
Click to expand...
Click to collapse
it did for me as well at first but then settled down. havent had any lag issues anymoe. It even caused my texts to send slowly. Like i said though, havent seen any other isssues of lag. S health issue is now fixed... the only issue i have is that we cant use private mode.
knarfies said:
it did for me as well at first but then settled down. havent had any lag issues anymoe. It even caused my texts to send slowly. Like i said though, havent seen any other isssues of lag. S health issue is now fixed... the only issue i have is that we cant use private mode.
Click to expand...
Click to collapse
Did you use Wanam's exposed module to fix S-Health?
Anyone tried to enable call recording with exposed? And get it working?
knarfies said:
it did for me as well at first but then settled down. havent had any lag issues anymoe. It even caused my texts to send slowly. Like i said though, havent seen any other isssues of lag. S health issue is now fixed... the only issue i have is that we cant use private mode.
Click to expand...
Click to collapse
I thought private mode was down to being rooted not xposed but I could be wrong
knarfies said:
it did for me as well at first but then settled down. havent had any lag issues anymoe. It even caused my texts to send slowly. Like i said though, havent seen any other isssues of lag. S health issue is now fixed... the only issue i have is that we cant use private mode.
Click to expand...
Click to collapse
So which method you used to fix S health? Module or the above "manual" method?
killkyo said:
So which method you used to fix S health? Module or the above "manual" method?
Click to expand...
Click to collapse
I used wanam xposed to fix it.
I was thinking that you need to be rooted to use Xposed. Is that correct?
knarfies said:
I used wanam xposed to fix it.
Click to expand...
Click to collapse
Thanks, care to share what modules are you using? Just wanna see if those that i intend to use will be working fine.
One more thing, which version of xposed are you using? I installed 2.6.1 and it just lag too much that i cannot even access wanam module.
ewingr said:
I was thinking that you need to be rooted to use Xposed. Is that correct?
Click to expand...
Click to collapse
Yes that's correct
Sent from my SPH-L710 using XDA Free mobile app
Scaven said:
I installed Xposed for a few hours, it made the phone very laggy, so I uninstalled it.
Click to expand...
Click to collapse
Disable s-health and all will be fine my friend
---------- Post added at 09:07 PM ---------- Previous post was at 09:04 PM ----------
killkyo said:
Thanks, care to share what modules are you using? Just wanna see if those that i intend to use will be working fine.
One more thing, which version of xposed are you using? I installed 2.6.1 and it just lag too much that i cannot even access wanam module.
Click to expand...
Click to collapse
Freeze s-health until a fix is found.
My phone is running fantastic at the moment.
It was laggy as crap after installing xposed.
Now its flawless.
They had this problem on the S5, the reason why it lags so much is that Xposed interferes with one of the checks that Private mode and the S Health service use, which causes the sensor for S Health to constantly hang(this causes the lag you have mentioned).
The Wanam module XSecureStorage fixes this by skipping the check the apps make.
I imagine the reason why Private Mode doesn't work even with this module, is because the Secure Element is in a different place; since this module is technically only for S5 and hasn't been update for compatibility.
Hi folks,
I am on Imperium rom v16 and I am having delays in my stock dialer app especially when I dial USSD codes for credits check etc. I have 2 power saving apps running namely PowerNap and Greenify.
I disabled powernap but didnt fixed the issue but when I disable greenify the lag was gone
So please can anyone tell me exactly which option/setting in greenfy might be causing this problem?
P.S I am using greenify donation version with xposed and no system app is greenified whatsoever
Thanks in advance..
Can u get network signal after installing imperium lolirom v16.0.
I didnt get the network signal.modem and bootloader installation shows fail using odin.
rahulpr6661 said:
Can u get network signal after installing imperium lolirom v16.0.
I didnt get the network signal.modem and bootloader installation shows fail using odin.
Click to expand...
Click to collapse
yes I can, which ver of odin u using?
Sent from my Galaxy S4 using XDA Labs
ElIT3ShOOT3R said:
Hi folks,
I am on Imperium rom v16 and I am having delays in my stock dialer app especially when I dial USSD codes for credits check etc. I have 2 power saving apps running namely PowerNap and Greenify.
I disabled powernap but didnt fixed the issue but when I disable greenify the lag was gone
So please can anyone tell me exactly which option/setting in greenfy might be causing this problem?
P.S I am using greenify donation version with xposed and no system app is greenified whatsoever
Thanks in advance..
Click to expand...
Click to collapse
Greenify uses accessibility settings. Disable them and the lag will go away. Unfortunately Greenify won't work properly if at all, so you have to decide which is more important to you: no lag or battery life.
An article posted on the portal over the weekend talked about lag caused by accessibility settings. Greenify was featured.
Strephon Alkhalikoi said:
Greenify uses accessibility settings. Disable them and the lag will go away. Unfortunately Greenify won't work properly if at all, so you have to decide which is more important to you: no lag or battery life.
An article posted on the portal over the weekend talked about lag caused by accessibility settings. Greenify was featured.
Click to expand...
Click to collapse
Thanks for the info, I will check it out..
Sent from my Galaxy S4 using XDA Labs
Hi guys,
This is an old problem that I thought was limited to one app, but recently I stumbled into it on many others.
Some drop-list selection options causes their respective app to crash, such as choosing whether the number is a mobile phone or a home phone is the stock contacts app, some buying options in eBay, etc.
Phone is on stock Kitkat ROM, rooted, Xposed installed with many modules including Wanam Xposed.
Is this a known bug that is caused by something I can uninstall? If not, I am up to suggestions on how to find out what the problem is and fix it. I know my way around so please do not hesitate to suggest advanced solutions. If nothing works I'll flash a new stock ROM and start fresh of course, but I prefer not to do that if there's a less invasive solution.
Thanks in advance for your replies.
Nawarelsabaa said:
Hi guys,
This is an old problem that I thought was limited to one app, but recently I stumbled into it on many others.
Some drop-list selection options causes their respective app to crash, such as choosing whether the number is a mobile phone or a home phone is the stock contacts app, some buying options in eBay, etc.
Phone is on stock Kitkat ROM, rooted, Xposed installed with many modules including Wanam Xposed.
Is this a known bug that is caused by something I can uninstall? If not, I am up to suggestions on how to find out what the problem is and fix it. I know my way around so please do not hesitate to suggest advanced solutions. If nothing works I'll flash a new stock ROM and start fresh of course, but I prefer not to do that if there's a less invasive solution.
Thanks in advance for your replies.
Click to expand...
Click to collapse
i guess it's an Xposed Module issue.
I can't define which xposed module does that, so you will have to test while each one is disabled, and see if the problem no longer occurs, if still occurs then disable another module and test again....etc
neither stock ROM or root cause that, so it's probably Xposed.
MigoMujahid said:
i guess it's an Xposed Module issue.
Click to expand...
Click to collapse
I thought so, I just wanted to make sure I am not missing something painfully obvious [emoji2]
Thanks for replying, and for the suggestion, will try it soon and report back.
Sorry for the delay in replying, I had a hectic few weeks.
The prpblem disappeared when I deleted the Xposed module named "Force FastScroll".
The issue is resolved now.