i am having this issue with receiving and making calls, the moment the screen is on, SystemUI will crash and reload.
The proximity sensor does not work after this, and i end up touching stuff with my cheek while talking.
I do have my doubts on xpose module S5 SystemUI Theme, but it all started randomly...
anyone having the same issue?
My Note 3 runs with Stock NG2, LeanKernel 3.6 and latest PhilZ CWM.
Yes! I have this issue as well. Not for outbound, but only for inbound. I use the Samsung flip cover, so I did not notice about the proximity sensor, but I just gave it a test and it shows identical behaviour. When receiving a call when screen is off, there is no problem at all, proximity also works.
I do not have the S5 SystemUI theme, and never used it.
Can't remember what I changed that could actually cause this. I have the following config:
Stock XXUEND3 (Latest PHN - The Netherlands firmware available)
Rooted with CF Autoroot
Running Ultimate Kernel v54 (but I had the issue already running stock kernel)
Connected with Gear 2
Frozen some Samsung bloatware with Titanium Backup
So I am following this thread!
Gerco
Well that's weird, Greenify keeps telling me it has problems hibernating com.sec.android.sviewcover, which i've disabled since i dont have one.
PS, to confirm your findings, i too had problems on stock kernel (*NG2 SEE) and i did wipe a lot of APK's, but most of them are non-samsung, i prefer RW rights over /system above scripting and debloating apps.
Do you by any chance have Xposed installed? if yes, what modules?
I've enabled the physical buttons for picking up and ending a call, if it wasnt up to them, i'd have to wait until the process re-opens so i can slide the thing...this is getting really annoying
I do have the Xposed framework loaded, with only Wanam Xposed active. I'll try to disable/remove Xposed and see if that makes things better.
<edit> Nope... Did not fix it... </edit>
Solved? I've this problem also with Galaxy S4 (I9505), i've disable Xposed, clean systemUI data, flash a stock rom (without wipe data)... still crash.
Had to wipe everything as i remember. The issue never came back.
PlutoDelic said:
Had to wipe everything as i remember. The issue never came back.
Click to expand...
Click to collapse
Thanks
Inviato dal mio GT-I9505 utilizzando Tapatalk
For me it worked again after I flashed a ROM update that became available for my region.
Sent from my SM-N9005 using XDA Free mobile app
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
Ive had a look around but cant find any answers. Is xposed framework compatible with the s5? And does Wanam xposed work? I dont wanna brick my phone trying..
Sent from my SM-G900I using xda app-developers app
Yes, it works
Wanam is the best to use
prot- said:
Ive had a look around but cant find any answers. Is xposed framework compatible with the s5? And does Wanam xposed work? I dont wanna brick my phone trying..
Sent from my SM-G900I using xda app-developers app
Click to expand...
Click to collapse
there's a thread over here with a lot of us having problems as soon as xposed is installed it crashes s health when you try to run it.
http://forum.xda-developers.com/showthread.php?p=51958422
I tried Xposed and Wanam.
The changes I made in Wanam worked but the phone boots much slower. After it has completely booted up and you're on the home screen, it also takes a long time for things to start up (things loaded in the background, such as LightFlow). Things felt sluggish in general. I uninstalled Wanam and Xposed Framework and everything is back to full speed again.
I'm going to hold off until Wanam Xposed gets some updates for S5 compatibility.
OK thanks. Good to know.
Do u know if u can get lock screen widgets working?
Sent from my SM-G900I using xda app-developers app
Hi. Sad to see. One question though. Did the phone boot fast again and everything okay after you uninstalled it?
Sent from my SM-G900F using xda app-developers app
Sevael said:
I tried Xposed and Wanam.
The changes I made in Wanam worked but the phone boots much slower. After it has completely booted up and you're on the home screen, it also takes a long time for things to start up (things loaded in the background, such as LightFlow). Things felt sluggish in general. I uninstalled Wanam and Xposed Framework and everything is back to full speed again.
I'm going to hold off until Wanam Xposed gets some updates for S5 compatibility.
Click to expand...
Click to collapse
hoping that @rovo89 will have a look into this matter.
RotteRotte said:
Did the phone boot fast again and everything okay after you uninstalled it?
Click to expand...
Click to collapse
Yep, everything was back to normal after I uninstalled them.
I'm using xposed with quite a number of mods, no slow down, no issues except for s-health, but if I ignore the crash message it still works
Tripledrop said:
I'm using xposed with quite a number of mods, no slow down, no issues except for s-health, but if I ignore the crash message it still works
Click to expand...
Click to collapse
when I get the crash error on s health it wont open and lags, are you running just xposed or wanam ? , soon as many of us installed xposed shealth crashes when you try to open it and only remedy is to uninstall xposed
It's never actually crashed when I load the app, rather I get random crashing in the background when I'm doing other things. Normal xposed
S Health app crashes when xposed enabled. No solution so far.
Sent from my SM-G900F using Tapatalk
Installed wanam module to now, and although it crashed when first loaded, second time was fine..
So you installed Xposed first then wanam?
Please post how and what steps you took and what apps you installed help others
Sent from my SM-G900W8 using Tapatalk 2
Well I only got the phone last week, installed xposed first thing, but since then I have installed countless apps and xposed mods. Changed dpi several times, all sorts of other xposed mods. Wanam I only installed today after reading this thread.
Just tried s-health again, no crash at all this time.
Ok and you have the s5 rooted and recovery installed? Weird your the 1st one that says having no problems I'm on rogers myself here g900w
ok just installed xposed.installer_v29_665be7 rebooted and my s health was working fine 100 % , then I opened xposed and installed the framework then rebooted , now my s health crashes.
so I opened xposed and uninstalled the framework , rebooted and my s health is back to normal ,but I had to relink my account and setup s health again , still with xposed installed , seems it has to do with the framework as soon I install the framework s health crashes.
Sent from my SM-G900W8 using Tapatalk 2
Yeah rooted with phils recovery, international version s5. And I do have issues, it does keep crashing on the background, but I can use shealth
Tripledrop said:
Yeah rooted with phils recovery, international version s5. And I do have issues, it does keep crashing on the background, but I can use shealth
Click to expand...
Click to collapse
ya mine was doing that at one point to , kept crashing at random times other times it wouldn't let me open s heath at all it would just crash.,
I am loving root and am very grateful for all the work put into it. I've installed xposed and it breaks my install button when trying to install new apps. Is there a work around for this? I thought it was a screen brightness app but narrowed it to xposed, any info on this?
Sent from my SM-G900V using XDA Premium 4 mobile app
I had a similar issue with this, but my phone was being completely laggy. I did a factory reset and I updated s health and my phone started being laggy. I froze s health and health service and haven't had any issues since. Running Xposed with XPrivacy, ISIS bypass, and another frowned upon module. All is working great, going to try Wanam today
I would try removing exposed completely rebooting and then freezing s health then reboot and then install xposed again
There's a security setting that's needs to be changed to false in build prop and lag goes away. The touchwiz module and xblast where causing no data and install button issues. Getting rid of one of them fixes it
Sent from my SM-G900V using XDA Premium 4 mobile app
jayandare said:
There's a security setting that's needs to be changed to false in build prop and lag goes away. The touchwiz module and xblast where causing no data and install button issues. Getting rid of one of them fixes it
Sent from my SM-G900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Fixed - Check here http://forum.xda-developers.com/showpost.php?p=53447283&postcount=5
I have Xposed installed on my AT&T GS5(I'm posting here because I think it's a generic question and the Verizon forums are where the party is at). I'm using Map Zoom Invert, RootCloak, Wanam Xposed, and GravityBox [KK]. I've ready a lot about people having lag issues with GravityBox and other modules. I haven't had any lag at all. How is everyone else's working? Is it just the Verizon models that are having lag issues?
elgiraffe said:
I have Xposed installed on my AT&T GS5(I'm posting here because I think it's a generic question and the Verizon forums are where the party is at). I'm using Map Zoom Invert, RootCloak, Wanam Xposed, and GravityBox [KK]. I've ready a lot about people having lag issues with GravityBox and other modules. I haven't had any lag at all. How is everyone else's working? Is it just the Verizon models that are having lag issues?
Click to expand...
Click to collapse
I had issues on my Verizon S5. I ended up reflashing stock firmware with odin, factory resetting, then installing towelroot and using titanium pro to freeze health service and s-health. Also used a build prop editor to change ro.securestorage.support=true to false.
After doing these things I had no more lag while using xposed or wanam xposed.
Hopefully this helps
I installed Wanam on my S5 I'm running the latest firmware NK2 and I noticed after installing wanam i don't have the option for video calls and HD calls. Anyone else have experienced this?
Hi,
using French device DS with build 23.118-10. Lollipop 5.1.1. Rooted with SuperSU 2.46 and using latest v79 xposed.
All smooth except for this:
Phone calls work until - randomly - the mike does not work anymore. Switching to hands free and back remedies the situation. Still, this being a phone, I would like rock solid calls.
Was using Amplify before and turned it off to make sure this wasn't the culprit. Still hard to diagnose.
Any ideas?
dreinulldrei said:
Hi,
using French device DS with build 23.118-10. Lollipop 5.1.1. Rooted with SuperSU 2.46 and using latest v79 xposed.
All smooth except for this:
Phone calls work until - randomly - the mike does not work anymore. Switching to hands free and back remedies the situation. Still, this being a phone, I would like rock solid calls.
Was using Amplify before and turned it off to make sure this wasn't the culprit. Still hard to diagnose.
Any ideas?
Click to expand...
Click to collapse
Issues maybe with xposed. Try uninstalling that.
Sent from my XT1562 using Tapatalk
Possible but doubt it. Also too many people using xposed. I already uninstalled Amplify to make sure its not some wakelock that is blocked or delayed...
dreinulldrei said:
Hi,
using French device DS with build 23.118-10. Lollipop 5.1.1. Rooted with SuperSU 2.46 and using latest v79 xposed.
All smooth except for this:
Phone calls work until - randomly - the mike does not work anymore. Switching to hands free and back remedies the situation. Still, this being a phone, I would like rock solid calls.
Was using Amplify before and turned it off to make sure this wasn't the culprit. Still hard to diagnose.
Any ideas?
Click to expand...
Click to collapse
I'm on Lollipop 5.1.1 as well (Canadian stock Rom). My Xposed setup is v79 sdk22 arm with SuperSU 2.62 and I haven't had any of the problems that you are having. I'm using the stock dialer. Do you have any Xposed modules that might be acting up.
Sent from my XT1563 using Tapatalk
None. Just True Silent Mode, Gravity Box and Greenify. Already tried with experimental features off etc. Anyway. Restored to stock 23.118-12 and will see if the fresh re-install fixes things. Noticed that the phone likes to fall asleep when in a call and holding against my ear... Need to press unlock button sporadically.
Hi, I've the same problem in STOCK reteu 6.0 without root, did you solve the problem???
One problem I have been having, and its extremely random (never been able to duplicate, has happened twice now) is the phone just goes completely silent on a call over Bluetooth. I switch to speaker and it works, then back to Bluetooth and it stays silent. I have to reboot the phone to get phone audio back over Bluetooth. I wonder if the issues are related, it happened once on 5.1.1 and once on 6.0.
@eloyo: Did not happen again, but might have happened once when someone dropped the call and re-called before I could switch on speakerphone.
Might have helped I reflashed the modem when installing the -32 Retasia release.
Since I rooted my note 4, I have been having random freezes and it is frustrating. I installed SimplROM, Revolution, Note 5 Port ( Kyubi or something ) and finally a stock rooted rom ( bare developer's edition ) and my phone is the whole time freezing on me. I don't use social media so I am not having background heavy tasks running, always fully erased the phone's internal memory and cache before installing a new rom and yet I still get the crashes. I hve never had that before I rooted the phone. anyone experiencing this as well ?
my phone is a N910F
stilkus said:
Since I rooted my note 4, I have been having random freezes and it is frustrating. I installed SimplROM, Revolution, Note 5 Port ( Kyubi or something ) and finally a stock rooted rom ( bare developer's edition ) and my phone is the whole time freezing on me. I don't use social media so I am not having background heavy tasks running, always fully erased the phone's internal memory and cache before installing a new rom and yet I still get the crashes. I hve never had that before I rooted the phone. anyone experiencing this as well ?
my phone is a N910F
Click to expand...
Click to collapse
I am having the same problem, lagging all 5 sec when typing or swiping on homescreen. It just happens on Touchwiz roms. The Fingerprintsensor aint working either. I tried Stock Roms, Custom Roms.
Somebody said that they fixed it on the 910T with a puerto rico stockrom but no fix for 910F.
I just installed CM12.1 and no lag.
Waiting for marshmallow for fingerprintsensor support.
Hope i could help.
Akuma360 said:
I am having the same problem, lagging all 5 sec when typing or swiping on homescreen. It just happens on Touchwiz roms. The Fingerprintsensor aint working either. I tried Stock Roms, Custom Roms.
Somebody said that they fixed it on the 910T with a puerto rico stockrom but no fix for 910F.
I just installed CM12.1 and no lag.
Waiting for marshmallow for fingerprintsensor support.
Hope i could help.
Click to expand...
Click to collapse
Mine is actually working fine and it freezes without warning or in other words I can't point out exactly when it freezes, like sometimes the camera, drop down notification bar or even the task switcher. It is random, I tried yesterday some solution which I'm not sure exactly of it's outcome but so far no freezes. I changed the securestorage value in the build.prop to false which resulted in loosing my wireless password but after I retyped it again things were fine.
stilkus said:
Mine is actually working fine and it freezes without warning or in other words I can't point out exactly when it freezes, like sometimes the camera, drop down notification bar or even the task switcher. It is random, I tried yesterday some solution which I'm not sure exactly of it's outcome but so far no freezes. I changed the securestorage value in the build.prop to false which resulted in loosing my wireless password but after I retyped it again things were fine.
Click to expand...
Click to collapse
Hi,
souns like the S-Health and Privatemode error.
you fixed it with that method. You could also use the xposed module for S-Health to fix it.
Akuma360 said:
Hi,
souns like the S-Health and Privatemode error.
you fixed it with that method. You could also use the xposed module for S-Health to fix it.
Click to expand...
Click to collapse
could you please elbarate more with this xposed module fix ?