Related
Rooted S5 (SM-G900F) with CF-Auto Root without problems, disabled KNOX, everything worked fine. After installing the Xposed Framework (latest) the phone get super laggy. NOTE: No Xposed Modules were activated. No SHealt force closes or anything like that some users were reporting. Only clearly visible general lag everywhere. Tried uninstalling the Framework, everything went back to normal. After reinstall, the lag appeared again.(tried 3 times, 100% it's from the framework)
Baseband: G900FXXU1ANCE
The lag has no trace in LogCat so it's irrelevant.
I hope @rovo89 already knows about the problem, but for now any solution, fix or idea?
UnlimitedN20 said:
Rooted S5 (SM-G900F) with CF-Auto Root without problems, disabled KNOX, everything worked fine. After installing the Xposed Framework (latest) the phone get super laggy. NOTE: No Xposed Modules were activated. No SHealt force closes or anything like that some users were reporting. Only clearly visible general lag everywhere. Tried uninstalling the Framework, everything went back to normal. After reinstall, the lag appeared again.(tried 3 times, 100% it's from the framework)
Baseband: G900FXXU1ANCE
The lag has no trace in LogCat so it's irrelevant.
I hope @rovo89 already knows about the problem, but for now any solution, fix or idea?
Click to expand...
Click to collapse
I don't have a fix, but I have the same problem. I can live without it though, so I just uninstalled it for now.
UnlimitedN20 said:
Rooted S5 (SM-G900F) with CF-Auto Root without problems, disabled KNOX, everything worked fine. After installing the Xposed Framework (latest) the phone get super laggy. NOTE: No Xposed Modules were activated. No SHealt force closes or anything like that some users were reporting. Only clearly visible general lag everywhere. Tried uninstalling the Framework, everything went back to normal. After reinstall, the lag appeared again.(tried 3 times, 100% it's from the framework)
Baseband: G900FXXU1ANCE
The lag has no trace in LogCat so it's irrelevant.
I hope @rovo89 already knows about the problem, but for now any solution, fix or idea?
Click to expand...
Click to collapse
it's very strange, because i experience no issue at all with both xposed framework and s health.
i'm using sm-g900i and here is my set-up:
- taiwanese stockrom: my original stock rom is au vodafone firmware and it's not up-to-date so i flash this one in order to have camera at lockscreen and modify dock icons which is impossible in "australia only" stock
- i flash this rom using mobile odin pro <~~ not sure if this helps!
- i flash philz touch recovery using mobile odin pro
- install xposed framework, reboot
- update everything through goole play to make sure all system apps are up-to-date
- i haven't removed/disabled any bloat ware, just hide them (greenify donation version helps a lot here)
- no laggy performance at all
hope it helps you all!
UnlimitedN20 said:
Rooted S5 (SM-G900F) with CF-Auto Root without problems, disabled KNOX, everything worked fine. After installing the Xposed Framework (latest) the phone get super laggy. NOTE: No Xposed Modules were activated. No SHealt force closes or anything like that some users were reporting. Only clearly visible general lag everywhere. Tried uninstalling the Framework, everything went back to normal. After reinstall, the lag appeared again.(tried 3 times, 100% it's from the framework)
Baseband: G900FXXU1ANCE
The lag has no trace in LogCat so it's irrelevant.
I hope @rovo89 already knows about the problem, but for now any solution, fix or idea?
Click to expand...
Click to collapse
Xposed doesnt work correctly with rooted device only by using a custom kernel. You have to install also a custom rom.
OR ...
you have to change the build.prop, if you just only use a custom kernel with Xposed Framework.
- Take Root Explorer for example and open build.prop (to find in System)
- First uninstall Xposed Framwork again ...
- then go to build.prop to the line ( “ro.securestorage.support=true” )
- change true to false ( “ro.securestorage.support=false” )
- now reinstall Xposed Framework
- restart your device and both working well without any lags.
By rooting the phone the secure mode doesnt work anymore, so you have to change that in build.prop.
You dont need to do so with custom kernel and custom rom running, but with custom kernel and stock rom, as I told at the beginning.
cheers
cokenet said:
Xposed doesnt work correctly with rooted device only by using a custom kernel. You have to install also a custom rom.
OR ...
you have to change the build.prop, if you just only use a custom kernel with Xposed Framework.
- Take Root Explorer for example and open build.prop (to find in System)
- First uninstall Xposed Framwork again ...
- then go to build.prop to the line ( “ro.securestorage.support=true” )
- change true to false ( “ro.securestorage.support=false” )
- now reinstall Xposed Framework
- restart your device and both working well without any lags.
By rooting the phone the secure mode doesnt work anymore, so you have to change that in build.prop.
You dont need to do so with custom kernel and custom rom running, but with custom kernel and stock rom, as I told at the beginning.
cheers
Click to expand...
Click to collapse
Editing build.prop solved the lag problem with Xposed Framework, but now Shealt force closes. :|.
UnlimitedN20 said:
Editing build.prop solved the lag problem with Xposed Framework, but now Shealt force closes. :|.
Click to expand...
Click to collapse
Try to clear Data of SHealth in App Manager.
cokenet said:
Try to clear Data of SHealth in App Manager.
Click to expand...
Click to collapse
Doesn't Work, right now as it stands is if you install Xposed Installer, the phone lags an you can't use S Health anyway, but you can do the build prop edit and get rid of the lag from Xposed and still not be able to use S Health as it will now FC no matter what lol, so if we want to use Xposed and liek S Health, we can't have both.
clear Health Service data as well, it should fix your prob
Fixed it!
Hello, I have done so as it stands but then wanted my phone not boot .. what went wrong?
Cokenet you are the best. Thank you.
!! Fix gaming lag !!
cokenet said:
Xposed doesnt work correctly with rooted device only by using a custom kernel. You have to install also a custom rom.
OR ...
you have to change the build.prop, if you just only use a custom kernel with Xposed Framework.
- Take Root Explorer for example and open build.prop (to find in System)
- First uninstall Xposed Framwork again ...
- then go to build.prop to the line ( “ro.securestorage.support=true” )
- change true to false ( “ro.securestorage.support=false” )
- now reinstall Xposed Framework
- restart your device and both working well without any lags.
By rooting the phone the secure mode doesnt work anymore, so you have to change that in build.prop.
You dont need to do so with custom kernel and custom rom running, but with custom kernel and stock rom, as I told at the beginning.
cheers
Click to expand...
Click to collapse
I'm on stock ROM and kernel and had amazing lag while playing GTA San Andreas on low-medium settings. Uninstalled framework ,changed ro.securestorage=false, installed DVFS Disabler module, after that framework again and rebooted. I can run GTA SA on everything MAX with almost no lag at all. Thanks for this
cokenet said:
Xposed doesnt work correctly with rooted device only by using a custom kernel. You have to install also a custom rom.
OR ...
you have to change the build.prop, if you just only use a custom kernel with Xposed Framework.
- Take Root Explorer for example and open build.prop (to find in System)
- First uninstall Xposed Framwork again ...
- then go to build.prop to the line ( “ro.securestorage.support=true” )
- change true to false ( “ro.securestorage.support=false” )
- now reinstall Xposed Framework
- restart your device and both working well without any lags.
By rooting the phone the secure mode doesnt work anymore, so you have to change that in build.prop.
You dont need to do so with custom kernel and custom rom running, but with custom kernel and stock rom, as I told at the beginning.
cheers
Click to expand...
Click to collapse
Wow, Thank you man!!
cokenet said:
Xposed doesnt work correctly with rooted device only by using a custom kernel. You have to install also a custom rom.
OR ...
you have to change the build.prop, if you just only use a custom kernel with Xposed Framework.
- Take Root Explorer for example and open build.prop (to find in System)
- First uninstall Xposed Framwork again ...
- then go to build.prop to the line ( “ro.securestorage.support=true” )
- change true to false ( “ro.securestorage.support=false” )
- now reinstall Xposed Framework
- restart your device and both working well without any lags.
By rooting the phone the secure mode doesnt work anymore, so you have to change that in build.prop.
You dont need to do so with custom kernel and custom rom running, but with custom kernel and stock rom, as I told at the beginning.
cheers
Click to expand...
Click to collapse
I have stock rom, custom kernel. I did follow your instruction but I still get lags, my phone still freeze from time to time, like it was before chanting build.prop file. I'm using Samsung Galaxy note 4 and android 6.0.1
I Wana install this xposed but obviously it's causing too much difficulties. Gravity box is needed. I it makes rooting delicious. Like me I tried many times installing xposed from magisk manager but ended up with BOOTLOOP.
Sunshine_live90 said:
Hello, I have done so as it stands but then wanted my phone not boot .. what went wrong?
Click to expand...
Click to collapse
The build.prop value referred to (ro.secure) is in your kernel, so I wouldn't change it on most devices, or learn to love your boot-logo. The "secure storage" may be variable, but every device I've ever had said "ro.secure", which is usually not changeable on stock ROMs. Read your init.rc file to check. I have to use init.d scripts to get insecure, useful for adb as root and Xposed without all the lag.
Sent from my LG G Stylo using XDA Labs
As somebody reported thet they are experiencing lags after installing wanam xposed and other guys are doing just fine with the module working on their phone, would anybody be willing to post the guide how exactly wanam should be installed without bad cosequences for the phone and all apps to work flawlessly.
Thanks!
I'm also having this issue. It works great with Note 2, but with Note 4, it locks the whole phone. Super SU stops responding or responds with a huge delay. Only uninstalling Wanam module didn't fix the issue, I had to fully reinstall the xposed framework to bring my phone back to a normal behaviour. So far Note 2 is still my official phone until I sort out everything I need to make Note 4 works comfortably for me, so, there is still no SIM installed. Could this be the point? My phone is a 910C with NJ4 firmware. I appreciate any help.
gorcutt said:
I'm also having this issue. It works great with Note 2, but with Note 4, it locks the whole phone. Super SU stops responding or responds with a huge delay. Only uninstalling Wanam module didn't fix the issue, I had to fully reinstall the xposed framework to bring my phone back to a normal behaviour. So far Note 2 is still my official phone until I sort out everything I need to make Note 4 works comfortably for me, so, there is still no SIM installed. Could this be the point? My phone is a 910C with NJ4 firmware. I appreciate any help.
Click to expand...
Click to collapse
A user having a similar experience as yourself posted the following on another thread (I haven't tried it, since I'm still waiting for my N910C )
After installing xposed I had a serious lag problem, including apps installation lags and other general slowdown, which I resolved.
For anyone having this lag, xposed framework seems to be incompatible with S-Health and Health Services.
To resolve, do this:
Uninstall Xposed and Reboot
Wipe data of S-Health and Health Services
Freeze S-Health and Health Services (using Titanium Backup or similar)
Install xposed and reboot
Install the xposed addon XSecureStorage, enable it and Reboot
Unfreeze S-Health and Services (using Titanium Backup or similar)
Click to expand...
Click to collapse
I hope this helps...
Hmm, will try it! Thanks for the tip. Will post my results here.
Sent from my GT-N7100 using XDA Premium 4 mobile app
---------- Post added at 04:46 PM ---------- Previous post was at 04:29 PM ----------
Thanks ernani for pointing us to the solution. It works!!
I have this app as it comes with a cook ROM. No problem except I cant get some of the things to work. One example, the vol + button for flash doesnt work well.
chong67 said:
I have this app as it comes with a cook ROM. No problem except I cant get some of the things to work. One example, the vol + button for flash doesnt work well.
Click to expand...
Click to collapse
I always had issues with these "all in one" apps. Some features do actually works well in some ROMs and not in others. Gravity mod has also some nice features, most a lot similar with Wanam but in one some features works and not in the other app, so a believe both are more or less complimentary. Just a thought.
Sent from my SM-N910C using XDA Premium 4 mobile app
This is the S5 fix...
XSecureStorage
"One of the issues i noticed on GalaxyS5 was the SHealth incompatibility with Xposed (described on this thread), somehow if you are using Xposed framework, Secure storage will fails to process and save data, which leads to Sensor service hangs
This module bypass the secure storage checks on SHealth and Private mode services, and will let you load the SHealth App with no hangs and activate Private mode on Rooted Samsung devices running Xposed framework.
I did just the basic tests for SHealth because i don’t use this App anyway, it’s not easy to play football with a device on my hands/pocket ."
http://wanamlite.com/xsecurestorage/
Yes, Wanam has an option to disable XSecureStorage but (at least when I tried it) it didn't work. After installing XSecureStorage it resolved the weird lag I was having installing apps and such, and S Health works now too.
I think there was also another post that I saw with a small file that I downloaded and installed since I don't think S Health worked at first install of XSecureStorage, but after installing that and clearing data for S Health it worked.
This worked perfectly for me on my Note 4.
http://gs5.wonderhowto.com/how-to/f...hes-when-using-xposed-your-galaxy-s5-0157344/ It might have been all in my head, and maybe it even does the same thing, but following this guide seemed to make things smoother than using the option in Wanam Xposed.
There are a number of threads about these two topics, I am going to consolidate my findings here.
First off root works great on the Sprint variant, secondly so does Xposed with S-Health and private mode. You just have to be careful how you set them up. There have been a lot of posts about freezing S-health and Private mode then clearing data but from my experience that is hit or miss. There are four basic steps to getting everything working and it should be done from a factory reinstall of software.
Root using Chainfire autoroot for Sprint and Teamwin 2.8.1.1 for Sprint (NOT THE RECOVERY IN THE EASY STEP ROOT THREAD) It will fail just pull the battery and boot to download to install the recovery (buttons HOME, VOLUME DOWN, AND POWER) boot to recovery then install supersu
Download and install Xposed (not Wanam) download and install XSecure Health module install Xposed framework reboot
Activate Xsecure Health module reboot
Clear Data for Health Service and S-Health reboot
Run Private mode and set up, run S-Health and setup.
Setup your Google and Samsung accounts
If you do these steps exactly without doing anything else I can promise you will have a rooted Sprint version with Xposed, Shealth, and private mode working. When I say exactly I am serious there are a lot of things that can/will mess you up like
Signing into google or samsung on reboot after installing factory software
Starting private mode before setting up xposed
Shortcutting by doing a factory reset instead of a factory software reinstall
Restoring your data Nandroid backup (Use Titanium etc for a program by program reinstall of apps)
BTW the problem here is a little bit deeper than uninstall xposed everything works. There is a something that is changed in the software with either xposed or wanam that can permanently kill private mode until you do a factory install. At the moment I am doing Nandroids before any change I make in Xposed.
The X secure module help my 915k to get s health back after trying all other advice, thanks
Sent from my SM-T705 using XDA Free mobile app
No problem, I've found that the xsecure can help with s-health, all these steps are for getting both working
Sent from my SM-N915P using Tapatalk
Hi. Just rooted my phone last night. Installed titanium back up and other applications that needed the root privelege. This morning I tried to transfer some files to my private mode, but i doesn't transfer.after that i tried turning on my private mode in the settings menu and there it was, FAILED TO ENABLE PRIVATE MODE. TRY AGAIN. Do you guys have any fix on this? BTW i used chainfires autoroot and my model number is n910c. Hope theres a fix. Thank you!
godhandzero said:
Hi. Just rooted my phone last night. Installed titanium back up and other applications that needed the root privelege. This morning I tried to transfer some files to my private mode, but i doesn't transfer.after that i tried turning on my private mode in the settings menu and there it was, FAILED TO ENABLE PRIVATE MODE. TRY AGAIN. Do you guys have any fix on this? BTW i used chainfires autoroot and my model number is n910c. Hope theres a fix. Thank you!
Click to expand...
Click to collapse
Try using the Xposed module XSecureStorage
Installed the xposed framework and xsecurestorage module.still doesn't work?
You have to delete a file from one of your root directories. I can't remember which one though. Do a search on XDA for a you tube video showing you which one. Also Wanam 's thread on his Xsecurestorage module tell you which one as well
Remember to move stuff out of private mode before deleting the file though!
Sent from my SM-N910P using XDA Free mobile app
This forum has a search box , use it !
So, with Snapchat not working with anyone with a rooted device is there a workaround? Or do we have to wait until there is a work around? i've tried Xposed and some frameworks but that doesn't work either.
I only updated my phone today and haven't had an issue with Snapchat and root so I have no idea how long it's been going on for. Been looking across the internet and can't really come across anything solid so far, so apologies for another thread on the subject.
Sorry if this is the wrong area too.
Only solution I've found is us use the SuperSU app to uproot, then log in to SnapChat, then reroot.
If I unroot will that reset my phone or anything?
Once you do manage to log in, make a TB backup so you can restore the log-in in the future without having to unroot.
i can't log into Snapchat at all
rizb said:
So, with Snapchat not working with anyone with a rooted device is there a workaround? Or do we have to wait until there is a work around? i've tried Xposed and some frameworks but that doesn't work either.
I only updated my phone today and haven't had an issue with Snapchat and root so I have no idea how long it's been going on for. Been looking across the internet and can't really come across anything solid so far, so apologies for another thread on the subject.
Sorry if this is the wrong area too.
Click to expand...
Click to collapse
snapchat and root are no problem the problem is that snapchat check if xposed is installed or not that's why it won't log in...snapchat don't work if xposed is installed...
uninstall xposed through twrp and log to snapchat after that re-install xposed twrp
- tapatalked - from my VANTABLACK S7 EDGE
Perfectdevil said:
snapchat and root are no problem the problem is that snapchat check if xposed is installed or not that's why it won't log in...snapchat don't work if xposed is installed...
uninstall xposed through twrp and log to snapchat after that re-install xposed twrp
- tapatalked - from my VANTABLACK S7 EDGE
Click to expand...
Click to collapse
I don't have Xpsoed installed at all, that's what i'm confused about .
You can login snapchat, but you have to install systemless supersu + systemless xposed +suhide + magisk7
I can get pass safetynet check (checked today)
What I ended up doing, which works, is I wiped my phone on TWRP, reinstalled my firmware (superman) chose not to install root/Xposed, downloaded/signed into Snapchat, then rooted my phone. Long winded but it works.
Backup your snapchat data from a unrooted phone. I used titanium and restore on rooted
Just use Casper instead of original snapchat app.
Sent from my SM-G935F using XDA-Developers mobile app
You are unable to sign into Snapchat if you have the Xposed Framework enabled or Rooted.
(Rooted has never been a issue with me)
But Xposed framework is normally the cause, Even if you used Xposed or not, If the framework is present you cannot Login.
Simple Open up Xposed App (If you installed Via Superman you have have enabled to option and installed it)
From there you have a option to uninstall.
Reboot and once booted back up, login. Once logged in use Titanium Backup to backup the App plus Data.
Reinstall Xposed Framework and you should still be logged into Snapchat.
If you ever have any issues, Delete the app and restore from your backup, you have no need to uninstall Xposed as the Data is restored from the app keeping you logged into the app
mtk- said:
You can login snapchat, but you have to install systemless supersu + systemless xposed +suhide + magisk7
I can get pass safetynet check (checked today)
Click to expand...
Click to collapse
Hi, If im already rooted with supersu by chainfire and xposed installed what is the next step i have to do for install systemless, suhide and magisk or i have to start all overagain? Thanks
Sent From My Samsung Galaxy S7 Edge Duos SM-G935FD
_u2pop_ said:
Hi, If im already rooted with supersu by chainfire and xposed installed what is the next step i have to do for install systemless, suhide and magisk or i have to start all overagain? Thanks
Sent From My Samsung Galaxy S7 Edge Duos SM-G935FD
Click to expand...
Click to collapse
I have heard that just using suhide is enough to pass Snapchats new Root detection.
I have not tested as am still running the old version with Snaprefs
dave7802 said:
I have heard that just using suhide is enough to pass Snapchats new Root detection.
I have not tested as am still running the old version with Snaprefs
Click to expand...
Click to collapse
I hadnt had any problems whit SC and root untill 2 days ago either, easy fix is to unroot through the SU app, log into snap, and reflash superSU from TWRP.. worked for me
Firething said:
I hadnt had any problems whit SC and root untill 2 days ago either, easy fix is to unroot through the SU app, log into snap, and reflash superSU from TWRP.. worked for me
Click to expand...
Click to collapse
What option you used in SuperSU to unroot? I tried permanent unroot and it didnt work
Hello,
I've got a question about snapchat.
I'm sorry if im posting this in the wrong place, im new here!
I want to use snapchat 9.3.1.0 so i can use snapprefs.
I'm rooted and have xposed framework installed.
I am currently logged in in the newest snapchat version.
I made a backup of my snapchat with TB, deleted the new version of snapchat, installed snapchat 9.3.1.0, opened titanium backup and restored 'DATA ONLY'.
When i open snapchat, the app says: There are no snaps, and it says i've got no friends (which makes me sad). Any idea how i can fix this?
Thank you!
Lorenzo
It seems they recently changed things in an update. I have a rooted device with exposed, running superman rom. I used to just turn the switch off inside xposed, restart, login to snapchat, turn xposed back on and it was fine as long as I didn't log out. Now, none of that works.
My solution was to go to recovery, dirty flash my rom without root or xposed, login to snapchat, and go back and dirty flash again with root and xposed.
Way too much effort for snapchat, but it worked!
madhub said:
Just use Casper instead of original snapchat app.
Click to expand...
Click to collapse
We have a winner.
Firething said:
I hadnt had any problems whit SC and root untill 2 days ago either, easy fix is to unroot through the SU app, log into snap, and reflash superSU from TWRP.. worked for me
Click to expand...
Click to collapse
This worked. Thanks!