s health won't launch after root - Galaxy Note 4 Q&A, Help & Troubleshooting

I dunno what's wrong, but obviously my s health stopped working after rooting the phone using CF AUTO ROOT. Anyone having the same problem?

wm2001wm2001 said:
I dunno what's wrong, but obviously my s health stopped working after rooting the phone using CF AUTO ROOT. Anyone having the same problem?
Click to expand...
Click to collapse
You can install xpose framework, and install wanam > under security hacks > (enable) disable secure storage
if not work, go setting > application > s health > clear data
it can fix =)

xoo88 said:
You can install xpose framework, and install wanam > under security hacks > (enable) disable secure storage
if not work, go setting > application > s health > clear data
it can fix =)
Click to expand...
Click to collapse
Thank you for your fast and accurate reply... and that solve my problem instantly

Yeah!! you are welcome
many feature at wanam, you can play around with it =)

Dear Friends,
please look here.:
http://repo.xposed.info/module/ma.wanam.xshealth
This Module works fine with Note 4 and you must not change the secure Settings with build.prop
XSecureStorage module bypass the secure storage checks on SHealth and Private mode services, this will let you load the SHealth App with no hangs and activate Private mode on Rooted Samsung devices running Xposed framework.
Why we do that? because somehow if you are using Xposed framework on GalaxyS5 (and the newest Samsung flagships), Secure storage will fails to process and save data, which leads to a Sensor service hangs.
Click to expand...
Click to collapse
Install and activate the attached apk in Xposed Installer and S-Health works fine.
best regards

N9005 said:
Dear Friends,
please look here.:
http://repo.xposed.info/module/ma.wanam.xshealth
This Module works fine with Note 4 and you must not change the secure Settings with build.prop
Install and activate the attached apk in Xposed Installer and S-Health works fine.
best regards
Click to expand...
Click to collapse
i had same problem clear data didnt work and wanam was causing the phone to freeze and lag really badly so i unrooted it and tried to do factory reset but it wouldnt reset when i pressed erase everything nothing happened so i reset through recovery and it wouldnt restart after that it was stuck on samsung logo in the end i had to download and reflash stock rom anybody know why thats happened as i like the wanam features but dont want that heart in the mouth moment again if i try to root it agin...

Don't worry the steps is easy
1. new phone (after factory store or flash rom by odin)
2. root it
3. install xposed and wanam
4. enable it under wanam > security hacks > "disable secure storage"
5. clear data under setting > application manager > shealth
6. reboot, shealth will be work!
good luck

xoo88 said:
You can install xpose framework, and install wanam > under security hacks > (enable) disable secure storage
if not work, go setting > application > s health > clear data
it can fix =)
Click to expand...
Click to collapse
Awesome, thank you! I had the same issue and your solution fixed mine too!

xoo88 said:
You can install xpose framework, and install wanam > under security hacks > (enable) disable secure storage
if not work, go setting > application > s health > clear data
it can fix =)
Click to expand...
Click to collapse
I was having same problem u have to download free ROM Toolbox lite From play store then go to performance click on Build.prop editor then go down and click on ro.securestorage.support change True to False. And reboot then it will work perfect.

this was really quick thanks guys now i can start doing some exercise
s health working properly

Related

S Health

Has anyone had issues with s health after root. For some reason it fust force closes. I can wipe cache and it will let me input my personal info but after that it just force closes
Rodman27 said:
Has anyone had issues with s health after root. For some reason it fust force closes. I can wipe cache and it will let me input my personal info but after that it just force closes
Click to expand...
Click to collapse
Do you by chance have Xposed framework with a multiwindow module? Try disabling the module.
I do not. All I have done is root the phone. The program was working after rooting was done however after a reboot maybe a couple hours later it started the force close.
Rodman27 said:
I do not. All I have done is root the phone. The program was working after rooting was done however after a reboot maybe a couple hours later it started the force close.
Click to expand...
Click to collapse
Not sure then. Only time I've seen issues is when multiwindow Xposed hack was used.
You haven't frozen any apps/bloat in TiBu have you?
I'm rooted and mine works just fine. I use it everyday.
Started Over
I finally just used Odin and all is good:good:. Thanks everybody for trying to help.
I am having the same issue. I have Xposed installed with the Xposed Wallet hack, but not the multi- window hack. I used "Multi Window Manager" from the play store to manage my MW, so I uninstalled that to see if that was causing the problem. No luck.
Running Nottach's P-Rom, Xposed framework, Xposed Wallet Hack, the CASUAL Root-Recovery.
i have rooted, debloated, done Xposed multi window hack (not enabled) and TiBU frozen apps; S Health crashes every time. so i froze it; didnt use/need/want it before.
oddly it reminded me of the 'health' functions on a watchphone i had from 2008; it had a period/ovulation calculator. wtf.
Sorry for thread jacking -- but is there a way to have the Shealth pedometer keep running all the time?
netsyd said:
Sorry for thread jacking -- but is there a way to have the Shealth pedometer keep running all the time?
Click to expand...
Click to collapse
Mine worked when I had a widget.
Sent from my GT-I9505 using Tapatalk 4 Beta
just got an 4.3 update for my S4 LTE. upon checking the S-health there are dashboard missing and some bug to be fix
missing dashboard: (needed badly)
1. Blood Glocuse
2. Blood Pressure
Bugs to be Fix
1. food tracker - searching food and selecting crash, and changing the quantity for saved meal.
added dashboard (graet
1. workout, running walking and cycling with maps (gps) (replace running mate)
thats it, hope samsung see this..
Rodman27 said:
I finally just used Odin and all is good:good:. Thanks everybody for trying to help.
Click to expand...
Click to collapse
I edited my build.prop following these instructions I found online, everything now works wonderfully!
Make sure the Xposed isn’t installed.
We need to change build.prop file inside the system partition, you can also get it done manually by using a file manager app or get a build prop editor on play store.
Once you find the build.prop file, look for the “ro.securestorage.support=true” line.
Now change the line to “ro.securestorage.support=false”.
Install the Xposed framework again.
The final step is wiping S Health app data, head to System -> App Manager -> ALL -> S Health then wipes the data. Now your Galaxy S5 should be able to runs Xposed framework and S Health simultaneously without any problems.

Xposed crashes gapps on reboot/download mode

Hi guys,
I successfully installed xposed framework + wanam app and have been messing around with getting various mods looking lovely.
The one mod i really wanted the most was the 4 way reboot menu.
Everytime i reboot/ hot boot or download mode using the 4 way reboot menu all gapps (gmail, youtube, maps etc) crashes. Ive un-installed the framework and reinstalled which was a shot in the dark really.
I then read about clearing the google services framework data in application manager. This did fix the issue but only until a later reboot and gapps crashes again and again.
Have i missed a simple solution?! Thanks in advance.
p.s. am on cf rooted btu mk8 with su permissions given to wanam and xposed.
Other modules i have are multiple widgets.
I think what u have to do is:
- Go SuperSU
- Delete root perms APPs Xposed and Wanam
- Install again Xposed and give new root perms and reboot
- Install again Wanam and give new root perms and reboot
- Ur apps shouldnt crash now
- Enjoy
Joku1981 said:
I think what u have to do is:
- Go SuperSU
- Delete root perms APPs Xposed and Wanam
- Install again Xposed and give new root perms and reboot
- Install again Wanam and give new root perms and reboot
- Ur apps shouldnt crash now
- Enjoy
Click to expand...
Click to collapse
I followed the above advice and all seems to be working correctly! Top advice. Thanks. :good:

remove icon Blocking mode

How to remove the icon of Blocking mode?
Thx Francesco
You need a rooted device and Xposed framework
RubbaBand said:
You need a rooted device and Xposed framework
Click to expand...
Click to collapse
The device il rooted i have download and install xposed framework, now witch module i need?
Thx
malebolge said:
The device il rooted i have download and install xposed framework, now witch module i need?
Thx
Click to expand...
Click to collapse
First make sure you installed Xposed framework
By entering the app and going to > Framework > install/update
Then reboot
Now download and install Wanam Xposed
Then go to notification panel then scroll down and select "hide blocking mode notification"
Then reboot
RubbaBand said:
First make sure you installed Xposed framework
By entering the app and going to > Framework > install/update
Then reboot
Now download and install Wanam Xposed
Then go to notification panel then scroll down and select "hide blocking mode notification"
Then reboot
Click to expand...
Click to collapse
All work fine!!
Thanks a lot!!!!
malebolge said:
All work fine!!
Thanks a lot!!!!
Click to expand...
Click to collapse
Anytime bro

[FIX] OxygenOS Wakelock

Many people have been having a problem with the SystemUpdateService Wakelock from Google Play Services on their OnePlus One. On other custom roms people have been able to fix it by disabling Wakeup in Google play services in Privacy Guard. I tried that using appops using Xposed but the wakelock was still there even after disabling Wakeup to Google Play services.
Looking at how CM12 Nightlies fixed the issue I learned how to fix it on Oxygen OS.
Method 1 (Tasker)- credit Dimitris Psallidas
* Tasker and Root required
** tested and survives reboot
1. Create a profile based on "Event > System > Device Boot"
2. Add a "Run Shell" action with the command
"pm enable com.google.android.gms/.update.SystemUpdateService"
and tick the "Use Root" option
3. Add a "Run Shell" action with the command
"pm disable com.google.android.gms/.update.SystemUpdateService"
and tick the "Use Root" option
https://plus.google.com/112425488314892935797/posts/VqubRkcTpEE
Method 2 - credit Calkulin
This method fixes the problem at the source by flashing a zip file through your custom recovery. It will fix the wakelock until play services updates. Then you will have to flash a new updated zip. Find it here: http://forum.xda-developers.com/one...mod-google-play-services-update-wake-t3078082
Method 3
First, you need to download Disable Service from the Play Store, it requires root. Then under the System tab you need to go to Google Play Services and enable SystemUpdateService. That will fix your wakelock. You will notice that there is another SystemUpdateService under Google Services Framework, but leave that one disabled. -
This method is a Temporary Fix. You must enable that service again after a Reboot. OxygenOS disables it by default on boot which causes the wakelock.
http://forum.xda-developers.com/optimus-l9/general/carbonrom-wakelock-systemupdateservice-t3059218
Already posted it on the Ox OS thread.
jdtimothy said:
Does anyone no now to enable the service on boot with Tasker? I don't know if a terminal command or a script could be used to enable that service.
Click to expand...
Click to collapse
Yup. This was posted for CM back when it had the same wakelock: https://plus.google.com/112425488314892935797/posts/VqubRkcTpEE
Thanks, those methods work great for automatically taking care of the problem.
It's by far easier:
- Xposed
- Install "Wakelock Terminator" from the Play Store
- Search for the Play Services, filter the wakelock "SystemUpdateService"
kurtextrem said:
It's by far easier:
- Xposed
- Install "Wakelock Terminator" from the Play Store
- Search for the Play Services, filter the wakelock "SystemUpdateService"
Click to expand...
Click to collapse
Not working with oxygen os (5.0.2)
I did this Tasker fix on mine and holy crap what a difference. Back to similar battery life as when I was running stock 4.4.4.
denyo81 said:
Not working with oxygen os (5.0.2)
Click to expand...
Click to collapse
You need to download xposed for 5.0
Jgard said:
I did this Tasker fix on mine and holy crap what a difference. Back to similar battery life as when I was running stock 4.4.4.
Click to expand...
Click to collapse
Can you guide me configuring tasker ? I never used it actually. Please tell me a step by step procedure as I am a total noob in this.
I pretty much haven't ever gotten Tasker to work because it requires a lot of effort. But if you follow the OP, it's really easy to figure out. (this is my way of saying I barely know what I'm doing and don't feel qualified to explain how to do it)
jdtimothy said:
Many people have been having a problem with the SystemUpdateService Wakelock from Google Play Services on their OnePlus One. On other custom roms people have been able to fix it by disabling Wakeup in Google play services in Privacy Guard. I tried that using appops using Xposed but the wakelock was still there even after disabling Wakeup to Google Play services.
Looking at how CM12 Nightlies fixed the issue I learned how to fix it on Oxygen OS.
Method 1 (Tasker)- credit Dimitris Psallidas
* Tasker and Root required
** tested and survives reboot
1. Create a profile based on "Event > System > Device Boot"
2. Add a "Run Shell" action with the command
"pm enable com.google.android.gms/.update.SystemUpdateService"
and tick the "Use Root" option
3. Add a "Run Shell" action with the command
"pm disable com.google.android.gms/.update.SystemUpdateService"
and tick the "Use Root" option
https://plus.google.com/112425488314892935797/posts/VqubRkcTpEE
Method 2
First, you need to download Disable Service from the Play Store, it requires root. Then under the System tab you need to go to Google Play Services and enable SystemUpdateService. That will fix your wakelock. You will notice that there is another SystemUpdateService under Google Services Framework, but leave that one disabled. -
This method is a Temporary Fix. You must enable that service again after a Reboot. OxygenOS disables it by default on boot which causes the wakelock.
Click to expand...
Click to collapse
Works like a charm thank you very much
HUGE THUMBS UP! This totally fixed my battery issue! Thank you so much!!!
Sent from my A0001 using XDA Premium HD app
Any fix without root. I can't root for work apps on phone.
What a difference this makes... Loving oxygen with xposed... It does everything I want and rock solid stable. Thanks for this fix!
A.VOID said:
Any fix without root. I can't root for work apps on phone.
Click to expand...
Click to collapse
This will work for you but you need a custom recovery to flash
http://forum.xda-developers.com/one...mod-google-play-services-update-wake-t3078082
Calkulin said:
This will work for you but you need a custom recovery to flash
http://forum.xda-developers.com/one...mod-google-play-services-update-wake-t3078082
Click to expand...
Click to collapse
Was there another non-root solution? The two methods in the op speak to root.
I have twrp recovery installed now
I haven't seen any that don't require root but then again, I didn't really look since I fixed the source of the issue the first time I saw it on my phone
Calkulin said:
I haven't seen any that don't require root but then again, I didn't really look since I fixed the source of the issue the first time I saw it on my phone
Click to expand...
Click to collapse
I posted your fix as a method on the original post. Thanks for your contribution.
works great thanks

How To Use Universal Gms Doze In Pie Roms

This is a guide to implement universal Gms Doze in pie Roms
Note - this is a temperory fix
Process
- Install universal Gms doze module From Magisk manager
- reboot
- go to device admin tab under security in Settings and just disable find my device
- then go to apps and Notification > Advanced > special App access > battery optimisation > all apps
If google play services showing under apps then it is good to go
Note - as this is a temporary fix you have to disable find my device after every reboot.
@gautam said:
This is a guide to implement universal Gms Doze in pie Roms
Note - this is a temperory fix
Process
- Install universal Gms doze module From Magisk manager
- reboot
- go to device admin tab under security in Settings and just disable find my device
- then go to apps and Notification > Advanced > special App access > battery optimisation > all apps
If google play services showing under apps then it is good to go
Note - as this is a temporary fix you have to disable find my device after every reboot.
Click to expand...
Click to collapse
Why need gms doze module? Pie is already optimize.
People experience crashes after enabling doze in magisk.
If u want fix for google service drain then use agni kernel. There is option to enable.
Black_Stark said:
Why need gms doze module? Pie is already optimize.
People experience crashes after enabling doze in magisk.
If u want fix for google service drain then use agni kernel. There is option to enable.
Click to expand...
Click to collapse
I am just using it from many days - didn't experience any crash
cant enable the optimising option in the menu. it enters but it doesnt select, a fix for that ?
nevermind , i fixed it
darkdemoneyes said:
cant enable the optimising option in the menu. it enters but it doesnt select, a fix for that ?
nevermind , i fixed it
Click to expand...
Click to collapse
Follow the process it will
@gautam said:
Follow the process it will
Click to expand...
Click to collapse
I followed it doesn't set play services to optimise
我想试试效果

Categories

Resources