yashsingh1/xdaforums huggingface dataset:
[Droid Ultra Q&A, Help & Troubleshooting] mrwinkle:
After rooting my droid ultra i am not able to wave over my phone and activate my active display. I am not blaming the root because i have been playing with different xposed modules, especially gravity box. I guess i'm looking for someone to steer me in the right direction maybe to get it fixed without recovering using safestrap although i'm not sure if it was even working right after rooting. I really enjoyed this feature because i keep my phone on my desk. All other ways of activating are working as normal.

I have used App master to delete some of the bloatware, the modules i am currently using are GB, Xposed Call Blocker, Xposed Full Screen Call Picture, and Youtube Adaway.

thanks in advanced.
[Droid Ultra Q&A, Help & Troubleshooting] BillyTheRatKing:
That was a feature?

As far as I knew it was activated by movement of the device, not by waving a hand over the screen. If I pick it up it turns on.
[Droid Ultra Q&A, Help & Troubleshooting] akellar:
Yeah I'm not aware of any proximity sensor activation either.
[Droid Ultra Q&A, Help & Troubleshooting] doogald:
As I recall, the prox sensor will keep Active Display from turning on (so, it won't show if it's in your pocket or turned face-down), but, I agree, I don't remember anything about waving activating it. It never does for me, on a stock unrooted Maxx.
[Samsung Galaxy Core.] StariX37:
Feel free to ask any queries....

RISK EVERYTHING

Press Thanks :thumbup: If I Helped:)

SENIOR MEMBER

NEWBIE DEVELOPER

LEARNING THE ART OF DEVELOPING KERNELS :D

PHONE : SAMSUNG GT I8262, SAMSUNG GT S5360
[HTC Hurricane] mackaby007:
Might be old news to most of you, but I've been struggling of late to find a English ROM for the SPV C550. Thanks to Rafet, we have a link to an SDAII English ROM: Choose the second link as the first is a Russian Qtek ROM.

Thanks again Rafet.
[HTC Hurricane] Prerna:
Hi,

Thanks for the post. I am also willing to change the ROM of my C550.

Now, the second link goes to a rom in ...Turkish!

Could you check and let us know where to find an English one, if any?

:)
[AT&T Samsung Galaxy S 5] quordandis:
I've been a devoted rooter ever since my very first android phone, the Motorola Atrix (the very first phone with a fingerprint reader!). Loved it! After that, I had dutifully rooted my Samsung Galaxy S II Skyrocket, and then the Galaxy S 4 (before the update that put the whole phone on crazy lock-down). At first, I was very unhappy with not being able to root the ATT S5, but once I detoxed myself from the root addiction, I found that I really enjoyed the phone and everything worked really well. No FCs, no weird compatability issues because of the Xposed Framework and/or Wanam Xposed. Sure, I have to live without ad blocking or being able to tether (on a grandfathered unlimited data, so no tethering plan for me), and most missed is the inability to use TiBu (although I have found that Helium does a decent enough job).

So, after having been rooted for about 48 hours, I decided to undo the mess. I followed the instructions posted here on how to ODIN the original firmware and then perform the OTA update again. Took me a few hours to get my phone back to the state (more or less) it was in pre-root - especially with the help of Helium (paid for Premium, really worth it).

Anyone else experience something similar? Have another reason for de-rooting? Curious.....

I'd be more inclined to keep root on this device if things didn't get so screwed up with it....it was almost like a full time job keeping it operational with all the "moving pieces" so-to-speak (the real clincher for me was that the phonebook transfer via BT to my car was so screwed up post-root, that it just wasn't worth having it - especially in light of my discovery that after I've detoxed myself from the root addiction and still enjoyed my phone).

--Q
[AT&T Samsung Galaxy S 5] FilthyFord:
I think it's all about what you do with a rooted phone that either makes it a full time job or not just to keep it up and running smooth. Me for instance could really care less about custom roms and what not. I like root just for removing bloatware to make the phone and battery better. And in the case of the AT&T s5 the ability to change my default storage to the external sd card. Once that is done I tweak with it for a week or so finding the best performance settings and enabling tether and then I just leave it alone.
[AT&T Samsung Galaxy S 5] Greycloak42:
I rooted and installed xposed/wanam and no problems whatsoever.
[AT&T Samsung Galaxy S 5] shortydoggg:
It's not root that screws up your phone. It's something that you do after rooting that screws up the phone.
[AT&T Samsung Galaxy S 5] davew41:
No issues here, I was happy to root and remove the att and samsung bloatware.

I am also not a fan of touchwiz and that will take a while before we have an unlocked boot loader and are able to load custom roms..

To each their own it is no more of a pain in the ass to run a rooted phone vs a non rooted phone. Im at a loss as to why you think it was that much trouble?
[AT&T Samsung Galaxy S 5] charrog:
I understand where you are coming from, I enjoy root for the ability to use Tibu and remove bloat. I also was like you I had a granfathered plan since 1997, the BellSouth mobility day's. I just recently changed to the Mobile data share plan, after analyzing my data usage for the last couple of years I realized my data was under 12 gigs a month for the whole family. I signed up for the 15 gig data share plan have saved $ 40 dollars or more per month. Just a heads up you may want to look into it. Oh and as for tethering it is included in the mobile data share plan.
[AT&T Samsung Galaxy S 5] quordandis:
I assure you that Xposed and Wanam definitely interfere with some of the phone's processes. In fact, there's a whole thread here that describes the steps you have to take to remove the lag on your phone and allow you to use S Health (which I do). But then, other things get screwy, because the ro.securestorage.support property is set to true because other processes rely on it, so now I have a whole slew of other issues that arise from it.

I can tell you from the outset, all I did was root, install xposed, install wanam, and installed the ISIS Root Bypass module, and then all these issues came from that. I just felt it wasn't worth it, and I can easily freeze/disable/turn off the bloatware so I don't have issues with that, per se.

--Q
[AT&T Samsung Galaxy S 5] jdock:
The stuff I really wanted root for doesn't cause any ongoing weirdness. I was getting along ok without root but I am a LOT happier now:

- permanently disable the annoying, super-loud boot sound without having to resort to workarounds

- disable the tether provisioning check (my plan includes tethering, but on more than one occasion the provisioning check failed and told me to try later)

- full use of BBS and Greenify to monitor/tame battery suckers

- TiBu for freezing (I don't attempt to delete the bloatware) and backups too

- sdfix to gain full access to my sd card

To me, all of that stuff with the exception of the tether provisioning check really should be possible for everyone if they want it. And the tether check could at least reasonably cache your status.

xposed modules are probably the biggest culprit in rooted-user problems (even more than people deleting stuff they shouldn't), and while I love a lot of the customizations xposed allows (a big one for me was being able to show the setting in the messaging app that says not to turn on the screen when a message comes in - no more pocket-crap for me!), I could live without that. The one xposed module I would say I might miss is Xprivacy. I'm relatively conservative in what I block, but it is amazing the info our apps can have access to.
[AT&T Samsung Galaxy S 5] quordandis:
Hmm....perhaps I'll revisit rooting again....and keep off of xposed....I too miss xprivacy - keep it nice and updated on my Xoom and S4 ;)

Would not mind just using root for tethering, tibu and sdfix.....Do you have links to the tethering and sdfix solution you used? I guess the real litmus test here is if my car's bluetooth doesn't get all EFFED up on the phonebook. The weirdest thing....after I rooted (even before xposed) I would activate voice recognition and say "Call Home" it would repeat back to me in confirmation "Call Home" in the lovely female robotic voice. Then proceed to dial someone completely different. VERY weird.

--Q

PS - I'm not a newb user here...been delving into the guts of phones back when I had the old school Windows Mobile devices :D
[AT&T Samsung Galaxy S 5] cjna:
The only thing I did after I rooted my phone was to get rid of the boot sound and used sdfix to be able to use my sd card. But I was having random problems with some apps not working. I would have to uninstall the app and reinstall it to get it to work again. This was really annoying since I was on a trip and really needed to use the apps without all the bother. So I decided to install xposed to try to fix the problems I was having. That just made everything worse--more apps that I use a lot stopped working. After that I used Kies3 to get back to unrooted stock and reinstalled all my data from backup. I am using silent boot to get rid of the boot sound and adjusting to the way I have to use my sd card now. I plan to wait a while before I try root again.

This will be my first smart phone that I am using unrooted. But everything is working now and I have the most annoying things fixed without root.
[AT&T Samsung Galaxy S 5] tabascoz28:
Sticking with root. Agreed that it's what you do after root that messes things up. Sometimes when you have the power, you don't stop to think whether you should make changes. Unfortunately the phones are built now where many apps have their hands in others to make the user experience "better". The users in this instance are the general masses who just want a phone to work by statistics. It fails to acknowledge that some people think differently. Sometimes I pick up my sister's phone and wonder why she would have the launcher do what she did but that's her phone.

Would I un-root? That's a firm no good buddy. I appreciate everyone's input in making the rooting process less of a landmine but I would never give up the ability to do what I want at, the time that I want. The first thing I did was freeze att.update.software among other att software. (To the author of the post, att did a pretty good job in making everything work in it's first iteration). Then on to battery extending, greenify and wakelock detector. Finally I will delve into customizing my UI but like the author said, Touchwiz doesn't bother me that much, I just sped things up in the developer's option. Because I'm not a heavy phone user I am now getting about 3 days from my charge and still able to get my message updates albeit on my terms, not pushed to me. Also, not having to see ads anymore? Priceless.

And because of everyone else's efforts, I can still go into UPS in case of those times that I find I can't get access to a charger, which now a days, is not that often.
[AT&T Samsung Galaxy S 5] jdock:
For the sd permissions I used this sdfix app from the play store. There are several and they just edit /system/etc/permissions/platform.xml for you, so you could do it manually too.

I have to admit, for the tether provisioning, right now I'm using the option in Wanam Xposed just because it was quick. Supposedly the X Tether module works too. A non-xposed method is here but I didn't try it since the xposed module worked. On my old phone it was as simple as using an sql editor to change the entitlement_check setting in /data/data/com.android.providers.settings/databases/settings.db - I don't see that in the GS5, but it may be that the default is 1 and just adding it with a value of 0 will work.

Another idea I hadn't tried (no need to) was the old standby wifi tether for root users app; it might not work as-is for the GS5 but it's just a frontend for a couple of scripts that might be fairly easy to get working since the basic idea is the same and not magic at all (load the wifi device modules, start the wpa_supplicant on it, start a dhcp server on it, setup routing/iptables, and off you go - none of that needs to check to see if you're allowed; the obvious downside is no fancy gui to start/configure/monitor it). On my old phone, I used this as a framework for my own script that brought wifi up simultaneously with mobile data - not operating as a hotspot, but connecting to my home wireless - and then I could run a socks proxy on my phone and use that from anything on my home network, wireless or wired.

That is weird, and if the only thing you did was root, I can't see any reason for something like that to happen.

Edit: this thread has another method for disabling the provisioning check, which looks like a great way if you don't want to use xposed or modify framework.apk.
[AT&T Samsung Galaxy S 5] cstayton:
It takes time to learn what you can and can't tweak once you have "root", each device is different, each users needs are different. Where battery life and de-bloating may important to one it might very well be insignificant to another, Development is time consuming and with xPosed and the modules that go with it every time Google comes out with an updated OS or Samsung, HTC,LG or Motorola come out with a device it requires the devs to step back and re-evaluate the code and make appropriate adjustments for the best behavior, modifications for compatibility or in the worst case scenario a complete re-write. We all read (or should read) the disclaimers with every tweak or mod we do and as always if it doesnt work or causes bad behavior we can remove it.
[AT&T Samsung Galaxy S 5] LuckyColdJohnson:
I had small issues at first. Then I used Kies 3 to restore. Started over and immediately rooted. Installed Xposed and all 6 of my favorite Modules. Also did the Tool Kit (Dev Sec) Phone is flying fast and has great battery life. I have no issues at all.

I love root......(( I have the s 5 Active ))
[AT&T Samsung Galaxy S 5] LoSt180:
I guess I'm a very conservative rooter. I don't freeze apps unless I know what they are, so there's some on the "safe to freeze" list that I still have enabled. After having CM running on my Galaxy S II Skyrocket for so long, I was really impressed with the S5. Really the only thing I missed was AdFree Android. However having CM made my Skyrocket last a lot longer than it would have on the stock ROM, I only upgraded because the hardware started getting wonky.

So after root, I've only installed AdFree, SDFix, and froze a few bloat apps that were persistently in the running apps list that I couldn't disable in stock form. Really helped with battery life too, I can't use phone much during the day due to my job, but battery life jumped from 75-80% at the end of the day to around 90% if I don't touch it (~85% if I check FB during lunch for a few minutes).

There's a few more tweaks that I would like, but seeing all the issues with Xposed, I'll either deal or figure out a manual change at some point. Maybe I'll research what the ro.securestorage.support module is, since disabling it is really why I haven't tried Xposed. (Yes, I wanted root access, but I don't want to make my phone any less secure than I have to.)

tl;dr If you like the phone is stock form, go easy on the modifications after getting root.
[AT&T Samsung Galaxy S 5] cantenna:
Wow, I completely 110% disagree with everything you have mentioned here, this has not at all be my experience at all but then again I'm tech savvy. If I were you I would be buying apple products. I for one of the opinion, if I cant root it, I don't want it and won't pay money for it. That goes for knox 0x1 bootloaders as well. Samsung won't see another dime from me again! :)
[AT&T Samsung Galaxy S 5] Russ77:
I'm rooted. I froze at&t's crap, chat on, hangouts, and google+.

freezing ANYTHING Samsung seems to create a huge mess on this device.
[AT&T Samsung Galaxy S 5] barondebxl:
Spot on
[AT&T Samsung Galaxy S 5] quordandis:
Apparently, not entirely true. Here's one for you:

Pre-root, the phone connects just fine via bluetooth to my car. Upon initial pairing, I get a request to allow reading of contact list, phone history and messages. I agree. Car syncs contacts and saves to internal car temp memory (this sync occurs each time the car is turned on and the BT connection is established). Activate voice recognition to "Call Home" - car confirms with audible prompt "Call Home. Say yes, no or correction" to which I would reply "Yes" and then the car would call the contact labeled as "Home" on my phone which it synced.

Now, run towelroot, reboots phone with JUST root (su binary). Phone loads up just fine. Car establishes bluetooth connection. Tell it to "Call Home" everything proceeds as expected. I confirm with "yes" and it proceeds to dial a completely different phone number even though the voice prompt confirmed that I indeed wanted to call "home."

Ok - so I unpair the car from the phone, and delete the phone profile from the car. Decide to start from scratch. Phone pairs with the car and I allow the syncing of contacts, etc as was the case pre-root. Attempt to "Call Home" again and the same weird phenomenon occurs where it will confirm it's calling home, then proceed to dial a completely different contact. Ok. I clear the phonebook and force it to resync the contacts. Same issue. Ok. Unpair car from phone, delete phone from car.

Reboot phone into stock recovery and wipe cache. Try pairing again and do the whole shebang. SAME FREAKING ISSUE WITH THE CONTACT SYCN. Meanwhile, ONLY rooted the phone with the added su binary. No other root-enabled apps installed or used. Haven't even USED su yet to do anything other than run "adb shell" and confirm su works. (didn't even install a root checker).

I decide to UNROOT by installing supersu then using it to unroot. Reboot, unroot successful, no su binary, and remove supersu. Pair phone and car again, go through the steps and lo' and behold! CONTACT SYNC WORKED AND CAR DIALS APPROPRIATE CONTACT.

So, in reference to

- that's probably true in most cases, just not in this one. I'm not saying it's the root per se, but certainly something about the su binary or how the phone gets rooted through the exploit or something definitely screws something up.......
[AT&T Samsung Galaxy S 5] robstunner:
]

Dunno whats wrong with your setup, but my rooted phone works fine in my wife's Ford and my Subaru.
[AT&T Samsung Galaxy S 5] Cjohns8792:
I have been rooted since the day after it was released to us. I have had 0 issues. Also I have not installed x posed. Many of these issues come from the modifications and root request permissions that end up giving errors, not the root itself. As a matter of fact I have even installed safe strap and everything still works. Next step is KoolKit rom once it finishes downloading. Almost have everything I need and zero issues.
[AT&T Samsung Galaxy S 5] robstunner:
Yep, people hack up their phone with UI mods and xposed and then complain that root alone is ruining their life. I root my phone for adaway and TiBu. I've never installed xposed on this or any device. That being said my S5 is not just fine, but better (greenify and adaway).
[AT&T Samsung Galaxy S 5] Cjohns8792:
On my S4 I was able to use clockwork mod recovery instead of safestrap and did use x posed but that is only because I had been so familiar with CWM and Odin on that phone that I didn't mind having to reset from stock on my pc. This phone worries me because I am not used to safestrap but only time will tell.
[AT&T Samsung Galaxy S 5] quordandis:
LOL Clearly Nissan has issues with it.....oh well.

I know it seems silly, but with this issue, it's not worth it for me to root, even though I REALLY WANT TO if for no other reason than for TiBu, sdfix and adaway......*sigh* guess we'll see.....
[AT&T Samsung Galaxy S 5] Todd727:
I rooted and then I edited the permissions for the SD card. That seemed to cause a problem and I lost my BT access. Ended up doing a factory reset and ran TR again. This time I used SDFix. No issues, so I obviously fat fingered something. Since the do over, I've had no issues. My Ford downloaded my contacts fine, I've de-bloated, and am running much faster. No ads either. Sorry it didn't work out for you.
[AT&T Samsung Galaxy S 5] eortizr:
If you have an XDA user account and you are unhappy with Root, then you should not be a member .lol :laugh:
[AT&T Samsung Galaxy S 5] imitenotbecrazy:
100% that ^

Root itself inherently does nothing that would change your experience. Its what YOU do with root that could mess something up. Don't blame root. Blame yourself
[AT&T Samsung Galaxy S 5] quordandis:
With all due respect to both imitenotbecrazy and eortizr - I have seniority over both of you (as far as who has an older XDA account). Your opinions are all well and good, and you're quite entitled to have them, but I assure you, someTHING does change in the phone after Towelroot. Like I said, I'm not saying it's the presence of the su binary, perhaps it's the exploit that was used to gain root access, but after recounting the steps I took, I cannot see what else it could be.

If you're so sure it's not root, then perhaps you'd like to gander a guess as to what it could be that would be causing this very strange issue? Or, in the very least, offer another perspective that might help get to the bottom of this. Trolling the forums to just say nonsense like:

or

Is neither helpful, nor useful and only serves to make you feel better because you think that you've put someone else down.

So, if either of you are interested in actually getting to the bottom of this mystery, I'm open to hearing your constructive thoughts and ideas. Otherwise, perhaps it's best to keep your useless comments to yourselves :D
[AT&T Samsung Galaxy S 5] cjna:
I agree. My previous smartphones have been Sony Xperia's (X10,ION, TL) which AT&T stopped supporting. So I have quite a bit of experience with rooting and flashing ROMs. This is the first time that JUST rooting has caused me problems.
[AT&T Samsung Galaxy S 5] shortydoggg:
Root usually doesn't break the phone. People do, however; every generalization has its exceptions. Perhaps root alone did cause the issue. However, unless you reflash your stock Rom back to its initial state, factory reset, and then re-root without any excess apps or settings (starting over from a completely fresh state), and then show that there is still a problem, then you're going to find it very difficult to convince people around here that there is not something in your current user settings that is possibly conflicting with your root.
[AT&T Samsung Galaxy S 5] RVD26:
So what is the consensus here, don't install xposed?
[AT&T Samsung Galaxy S 5] cheddleson:
I have been following awhile now, trying to decide if I want to root or not, and from what I have seen, most problems that have been mentioned seem to involve xposed. If someone has problems, might be worth starting fresh and not adding xposed to see if the issues persist.
[AT&T Samsung Galaxy S 5] jdock:
I think xposed is still worth it - just be prepared to experiment a bit if something weird happens. The nice thing about xposed modules is they do not make permanent changes.

I just noticed a strange issue today, where calls would always be on speaker when I answered. Turned out to be caused by a wanam xposed setting that shouldn't be related to calling at all. Started off by disabling wanam altogether, and when that worked, I enabled it again and turned off a bunch of options until I found the culprit. Easily dealt with!
[AT&T Samsung Galaxy S 5] TitaniumBarbell:
Sorry for my ignorance but what is "Tibu"?
[AT&T Samsung Galaxy S 5] LoSt180:
Titanium Backup
[AT&T Samsung Galaxy S 5] DORID USER:
after root, I was having random problems with some apps not working. I would have to uninstall the app and reinstall it to get it to work again