Related
Hi All.
I have a question which I am hoping someone can help with.
I have an Experia X8 in standard configeration.
I discovered an app in the app manager with no name. This was after having good reason to beleive I may have been tracked or had spy ware loaded without my knoledge.
The phone would not load apps (failed at the point of instalation).
The phone was only used for calls and texts, and had one app loaded (GOSMSPRO) for text messages.
I consulted Vodafone and Sony Erricson and they advised to take it to the police. After 3 months the police lab returned the phone saying it tested negative for spy software.
I did some research and used moborobo and ESFile explorer.
I identified the un named system app as "Picker.apk". The phone app manager reported it as version 1 (but with no name) and 44Kb size.
Moborobo reported it with name (Picker.apk) but with a size of 52.12Kb.
Sony Erricson have told me that this app should not be there, on two seperate calls on different days.
They said they had seen this kind of thing before, and offered to do a "factory reload" if I wanted.
They also said they had done "factory reloads" for people that had appeared to have spy apps on there phones, as the normal software reinstall (via PC Companion) does not reload the Rom, as I discovered.
I rooted the phone and messed arround trying to load a new ROM to clear out all that was in there, but have not got it right so far...
My question is, how did this App get into the system apps in Rom as the phone was not rooted.
I have since discovered that some spy and tracking apps have an "auto delete if Sim is changed" feature in their features list.
I did remove my contract sim and put it in my new phone, and put a pay as you go sim in the sony, before I discovered I was being tracked--Thats how I found out !
Any help, advice or thoughts would be greatly apreciated.
Best regards.
Warren.
Hi, I am having a problem installing apps via the Google play store on my PC. When I try to do this, I get an error on the phone "Error while downloading "App Name". "App Name" could not be downloaded due to an error. (906).
If I click on the error, it takes me to the app on Google play on the phone where I can successfully download and install it directly from the phone. So I have a workaround, but the phone itself is second hand so I am worried it is faulty and causing this problem (and therefore who knows what other problems might be around the corner?).
As a bit of background info, the phone came rooted on 534 firmware and I updated to 257 via PC companion. I knew this would lose root but I don't want the phone rooted anyway (don't use any rooted apps etc). However SuperSU was installed and now I can't get rid of it (unless I downgrade, root again, then remove SuperSU and upgrade once more). I don't know if the fact it was rooted has caused the problem, or perhaps the upgrade while rooted and now having SuperSU stuck on my phone is causing the problem (I've never bothered with rooting and the like for years so while I know about it, I do not know the ins and outs of rooting and it's consequences).
My question is: Does anyone else have this problem or is it likely to be a fault with the phone?
Try to clear market data and or cache.
Is it for paid apps ? You have access in your country ?
Sometime I have market error with a yellow triangle in notif bar but it is always because of network connections/ wifi. Once reconnected it is ok.
Thanks for the reply.
I've tried clearing cache and data, I've even factory reset the phone but still no good. It is for all apps, paid and free. The network connection seems to be solid (or at least it would be an awful coincidence if every time for 100+ app installs when I try to install from the pc the network happens to be down, but when I then go straight to the phone and install from there the network is back up again).
Just a question, you want to install app via your comp on your phone when it's pluged to USB cable?
Personally i use google Chrome to Phone for sending immediatly links to my phone, that works also with google app link, that will automatically launch the google store on the app you selected before sending the link.
Also rooting your phone is really necessary? Many people root their phone for doing nothing really necessary...
Nope I don't want to do this while my phone is plugged in to the computer, the phone is in my pocket while I am trying to use the Google app store on my computer to install dozens of apps to the phone.
I know rooting the phone isn't necessary, but, as I explain, the phone was already rooted and I have no need of root. Whether the phone is or isn't rooted I don't mind either way, I was just mentioning the root info in case that is a clue as to why I am having this problem.
No offense intended (really!) but I'm not concerned with how you personally use Chrome to install apps to your phone. I am explaining a problem I have with my phone and wondering if it is a known issue that other people have or whether it is a fault with my phone. I have a workaround that I can use as I explained in the first post, but I am less concerned with what the problem is and more concerned with why the problem is there in the first place (as it may be mean I'm going to run into more problems in the future).
Anywho I can only assume it isn't a common problem, so I'll investigate further.
Cheers
Hi guys, I am buying the gear, and although I do not have the note 3, just the S4, I don't care, the update is coming soon and loving gadgets, I just couldn't resist.
- Having the s4, will gear manager be available to install ? (although probably not working correctly ) I read people use it with s4 with limited functionality and was wondering how.
- I read about side loading. Will I need a proper phone for that, or will it still be possible using APK leecher directly ?
- Lastly, I guess I should root it if I expect to use any of these options...?
Thanks,
Can't wait
Elgreco333 said:
Hi guys, I am buying the gear, and although I do not have the note 3, just the S4, I don't care, the update is coming soon and loving gadgets, I just couldn't resist.
- Having the s4, will gear manager be available to install ? (although probably not working correctly ) I read people use it with s4 with limited functionality and was wondering how.
- I read about side loading. Will I need a proper phone for that, or will it still be possible using APK leecher directly ?
- Lastly, I guess I should root it if I expect to use any of these options...?
Thanks,
Can't wait
Click to expand...
Click to collapse
Hi,
- Gear manager has been updated few times "once a week" recently... so give it a try - I am on NOTE3 so I am not sure but read the threads here..
- for side-loading etc - is is all written here - get wondershare mobile go for android (free version works for 15 days...) and read the thread "Tutorial - Rooting/Nova/ATN..."
- for the third point - to side load etc - read point two tutorial..
I rooted my S4 and put an Android 4.3 ROM in. Download Gear Manager and it was working.
Note: Gear Manager won't work without Android 4.3
Elgreco333 said:
Hi guys, I am buying the gear, and although I do not have the note 3, just the S4, I don't care, the update is coming soon and loving gadgets, I just couldn't resist.
- Having the s4, will gear manager be available to install ? (although probably not working correctly ) I read people use it with s4 with limited functionality and was wondering how.
- I read about side loading. Will I need a proper phone for that, or will it still be possible using APK leecher directly ?
- Lastly, I guess I should root it if I expect to use any of these options...?
Thanks,
Can't wait
Click to expand...
Click to collapse
Gear works approximatively with a S4 under 4.2
Gear Works perfectly with a S4 with 4.3 firmware (no root needed, just update via Kies if proposed, or via Odin)
To install APK, use wondershare. It s easy to do
Root is very easy to do and the gear continue to work correctly. It will help you to proceed at some modifications where a rooted watch is needed.
I have the Gear up and running also on my Note 2. It is running smoothly. I haven't rooted yet. Not to good with adb yet but I have been thinking about it
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
received gear, issue I am having for now...
I received my gear. Issue is that since I am in Canada (fido), I downloaded gear manager but it says that it is unable to use this software since the phone (S4 ) is not yet supported.(expected that)
So I am stuck at the NFC connecting screen and don't seem to find a way to get around it ?(didn't expect that though ..lol)
So is there another way to go about it for now ?
Any suggestions would be appreciated.
Thanks.
Elgreco333 said:
I received my gear. Issue is that since I am in Canada (fido), I downloaded gear manager but it says that it is unable to use this software since the phone (S4 ) is not yet supported.(expected that)
So I am stuck at the NFC connecting screen and don't seem to find a way to get around it ?(didn't expect that though ..lol)
So is there another way to go about it for now ?
Any suggestions would be appreciated.
Thanks.
Click to expand...
Click to collapse
Try an older version of gear manager (check link in my sig)
Yeah you need a older version. I had the same problem as you with my s4. But I had a 1 hour drive back from best buy when I got my watch and found the older one during my trip.
I have the apk but I don't know how to upload it on here.
Xda says I don't have sufficient access to upload files for some reason. Maybe I can email it to whoever needs it. Pm me with your email and I'll send it to you.
I also have a working watch styler apk I can send you as well. The one in the Samsung app store wouldn't work for me either.
success connecting
ok guys, used an older version and i am connected. On to exploring and I'll post back with any progress on what I am able to do...
Thanks for the suggestions
UPDATE : Rooted the phone, all is good. Tried to install ATN but after I do, there is no option under security settings to enable ATN notifications. Notification access section does not exist at all in my security section ? What gives ?
UPDATE 2: Realized that probably gear is not rooted. I followed all steps fine but when I reboot and open explorer, it never asks me to grant access to everything. When going to data, it says it is restricted...
Elgreco333 said:
ok guys, used an older version and i am connected. On to exploring and I'll post back with any progress on what I am able to do...
Thanks for the suggestions
UPDATE : Rooted the phone, all is good. Tried to install ATN but after I do, there is no option under security settings to enable ATN notifications. Notification access section does not exist at all in my security section ? What gives ?
UPDATE 2: Realized that probably gear is not rooted. I followed all steps fine but when I reboot and open explorer, it never asks me to grant access to everything. When going to data, it says it is restricted...
Click to expand...
Click to collapse
You need android 4.3 for the notification access.
How To Charge Galaxy Gear with Cradle ?
Hi,
Probably not the right forum but i have a question though -
I bought Samsung Galaxy Gear watch from Best Buy ( Online) and all i got in the box is just the watch - no cradle, no usb cable - how am i suppose to charge the watch ? is cradle and usb cable is anywhere available which i can buy ??
Regards
A
anamaya said:
Hi,
Probably not the right forum but i have a question though -
I bought Samsung Galaxy Gear watch from Best Buy ( Online) and all i got in the box is just the watch - no cradle, no usb cable - how am i suppose to charge the watch ? is cradle and usb cable is anywhere available which i can buy ??
Regards
A
Click to expand...
Click to collapse
Cradle and power adapter should have been in the box. Suggest you return it
Sent from my GT-I9505 using Tapatalk
anamaya said:
Hi,
Probably not the right forum but i have a question though -
I bought Samsung Galaxy Gear watch from Best Buy ( Online) and all i got in the box is just the watch - no cradle, no usb cable - how am i suppose to charge the watch ? is cradle and usb cable is anywhere available which i can buy ??
Regards
A
Click to expand...
Click to collapse
Call them quickly, report the problem, and quickly return it..If this is not done, they might try to say the cradle and the power are missing and might not give you a full refund. Report it quickly..
Let us know how you make out too..
CehowardNote3 said:
Call them quickly, report the problem, and quickly return it..If this is not done, they might try to say the cradle and the power are missing and might not give you a full refund. Report it quickly..
Let us know how you make out too..
Click to expand...
Click to collapse
Thanks Guys, after fighting with bestbuy for over an hour, they have agreed to replace the box and shipover a new one with all accessories in place. it was a fault on their end.
Thanks for responses.
Hello,
I have been looking around the forums and struggling with the galaxy gear i picked up today.
I have a verizon note 2, that is rooted and using a jellybean ROM. It appears that this ROM does not support NFC, and that looks to be the only way to install gear manager.
I have downloaded numerous 1.5 and 1.2 and 1.4 gear manager APKs from these forums, and have been able to set up gear manager on the phone but it appears to not be working so well. I cannot seem to get any notifications pushed to the gear, and cannot get the weather to show on the gear.
I was going to return the gear and just be done with it, but I am now wondering if anyone has any insight into whether or not I could get a simpler stock based ROM that enables NFC and has no conflict with the gear and my note 2?
I am using the stock messenger app, and no text messages come to the gear
Update
I contacted samsung to ask if there was any way to get the most recent gear manager without NFC and they said there was not. I am wondering if anyone can post a working APK, and if anyone can link me to a verizon note 2 rom that they are using and having no issues with the gear.
The phone calls go through without issue, but no text message or any other notification seems to be pushed through.
drocksmash said:
Hello,
I have been looking around the forums and struggling with the galaxy gear i picked up today.
I have a verizon note 2, that is rooted and using a jellybean ROM. It appears that this ROM does not support NFC, and that looks to be the only way to install gear manager.
I have downloaded numerous 1.5 and 1.2 and 1.4 gear manager APKs from these forums, and have been able to set up gear manager on the phone but it appears to not be working so well. I cannot seem to get any notifications pushed to the gear, and cannot get the weather to show on the gear.
I was going to return the gear and just be done with it, but I am now wondering if anyone has any insight into whether or not I could get a simpler stock based ROM that enables NFC and has no conflict with the gear and my note 2?
I am using the stock messenger app, and no text messages come to the gear
Click to expand...
Click to collapse
Your rom has no NFC ? This is... weird ?
Regardless, why not simply install a stock samsung rom ? You can install the gear manager straight from the samsung apps store and your done ?
fOmey said:
Your rom has no NFC ? This is... weird ?
Regardless, why not simply install a stock samsung rom ? You can install the gear manager straight from the samsung apps store and your done ?
Click to expand...
Click to collapse
I am not sure how to find a stock rom that will work without causing problems. I just assumed the ROM did not support NFC as it was not working, the options are there in my settings.
Does NFC require the stock battery and back cover? I have an extended battery, but was able to find my stock battery without the cover and it would not connect.
I am currently downloading jeallybeans_b22 to flash and see if there are any issues - would you mind linking me to a rom that you think would be issue free?
Thanks for the help
drocksmash said:
I am not sure how to find a stock rom that will work without causing problems. I just assumed the ROM did not support NFC as it was not working, the options are there in my settings.
Does NFC require the stock battery and back cover? I have an extended battery, but was able to find my stock battery without the cover and it would not connect.
I am currently downloading jeallybeans_b22 to flash and see if there are any issues - would you mind linking me to a rom that you think would be issue free?
Thanks for the help
Click to expand...
Click to collapse
I don't no dude exactly, Varys from phone to phone.. I remember reading in the past some aftermarket battery's prevent NFC from working.. which is more than likely your problem.
Also your not going to receive notifications unless you use a rom based on Samsung, otherwise you will be forced to use third party applications in order to receive notifications.
fOmey said:
I don't no dude exactly, Varys from phone to phone.. I remember reading in the past some aftermarket battery's prevent NFC from working.. which is more than likely your problem.
Also your not going to receive notifications unless you use a rom based on Samsung, otherwise you will be forced to use third party applications in order to receive notifications.
Click to expand...
Click to collapse
Ok ill try and find a rom that will work better.
Can you post your gear manager apk?
Im not sure if the original back is required for nfc use but even with the stock battery the cradle did not prompt me anything.
Pretty bummed this isnt working but I do know its my fault for having a rooted note.
drocksmash said:
Ok ill try and find a rom that will work better.
Can you post your gear manager apk?
Im not sure if the original back is required for nfc use but even with the stock battery the cradle did not prompt me anything.
Pretty bummed this isnt working but I do know its my fault for having a rooted note.
Click to expand...
Click to collapse
What, No its not because of root..
Dont over complicate things, its simply because your using a aftermarket battery.
Also you dont need nfc, you can manually connect the gear via bluetooth via the galaxy gear manager app.... ALTHOUGH I highly highly highly recommend you get a Samsung based rom !
No offence intended although you dont really seem like your very confident with android & know what your talking about, I recommend using a Samsung rom first until you understand how the gear actually works..
fOmey said:
What, No its not because of root..
Dont over complicate things, its simply because your using a aftermarket battery.
Also you dont need nfc, you can manually connect the gear via bluetooth via the galaxy gear manager app.... ALTHOUGH I highly highly highly recommend you get a Samsung based rom !
No offence intended although you dont really seem like your very confident with android & know what your talking about, I recommend using a Samsung rom first until you understand how the gear actually works..
Click to expand...
Click to collapse
No offense taken at all, I have rooted every android device I have had but almost always run intro problems. I would definitely say I am not confident in this whole process. The problem I am facing now is that all of the roms in the verizon section for the note 2 are not really clear on what is close to stock and what is not
While my current rom is touchwiz based I am still trying to find one compatible with the gear.
When I said it was my fault for being rooted I just meant my fault for not understanding how to find a stock rom to revert to.
2 key ingredients to getting gear working are android 4.3 and touchwiz
nfc is only used to make connection easier, you can alwys just select to connect manually. I'm pretty sure nfc antenna is part of battery
Brendo said:
2 key ingredients to getting gear working are android 4.3 and touchwiz
nfc is only used to make connection easier, you can alwys just select to connect manually. I'm pretty sure nfc antenna is part of battery
Click to expand...
Click to collapse
Without downloading the gear manager apk from someone who posted it on XDA I could not get the phone to prompt anything and the connection failed.
After downloading the apk for gear manager I was able to get the limited connectivity set up. I am guessing this is because the ROM is not very compatible and I will try to find one that works better.
Thanks for the help guys, sorry for wasting time. I cannot find the OEM battery cover for the phone, just the OEM battery and neither work when trying to bump the cradle to it. What a silly way for samsung to deliver the download... I don't understand why there is no option for a download from them.
drocksmash said:
Without downloading the gear manager apk from someone who posted it on XDA I could not get the phone to prompt anything and the connection failed.
After downloading the apk for gear manager I was able to get the limited connectivity set up. I am guessing this is because the ROM is not very compatible and I will try to find one that works better.
Thanks for the help guys, sorry for wasting time. I cannot find the OEM battery cover for the phone, just the OEM battery and neither work when trying to bump the cradle to it. What a silly way for samsung to deliver the download... I don't understand why there is no option for a download from them.
Click to expand...
Click to collapse
No, that is not how it works. You need the gear manager to connect and you just download this from the Samsung store (or I've posted all the apks). Anyway, nfc is just used to automatically pair devices and that is all, nothing else - it's simply less user interaction this way
EDIT: nfc looks to be part of the back cover (http://allaboutsamsung.de/wp-content/uploads/2012/10/Note2_wireless_charging_2.jpg)
drocksmash said:
Without downloading the gear manager apk from someone who posted it on XDA I could not get the phone to prompt anything and the connection failed.
After downloading the apk for gear manager I was able to get the limited connectivity set up. I am guessing this is because the ROM is not very compatible and I will try to find one that works better.
Thanks for the help guys, sorry for wasting time. I cannot find the OEM battery cover for the phone, just the OEM battery and neither work when trying to bump the cradle to it. What a silly way for samsung to deliver the download... I don't understand why there is no option for a download from them.
Click to expand...
Click to collapse
You can download gear manager directly from the app called "samsung apps", its considered bloat to some developers.. so it may be stripped out of the rom your using.
Brendo said:
No, that is not how it works. You need the gear manager to connect and you just download this from the Samsung store (or I've posted all the apks). Anyway, nfc is just used to automatically pair devices and that is all, nothing else - it's simply less user interaction this way
Click to expand...
Click to collapse
Exactly.
fOmey said:
You can download gear manager directly from the app called "samsung apps", its considered bloat to some developers.. so it may be stripped out of the rom your using.
Exactly.
Click to expand...
Click to collapse
Update
Thanks for all the help guys. I got a 4.3 ROM and still had issues so I'm just going to return it.
Deleted
I had an issue with the same thing where the nfc would only bring up an empty tag also my gear wouldn't connect to my phone via bluetooth so I had to unroot and go back to stock which I hate funny thing is I have null on my gear wish I could be rooted on my phone I hate this bloatware main reason why I rooted
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Mcca21 said:
I had an issue with the same thing where the nfc would only bring up an empty tag also my gear wouldn't connect to my phone via bluetooth so I had to unroot and go back to stock which I hate funny thing is I have null on my gear wish I could be rooted on my phone I hate this bloatware main reason why I rooted
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
ThNks
HELP! I erased NFC tag inside Galaxy Gear Cradle !!!!!
Does anyone have the actual text that was written into the NFC Tag on the Galaxy Gear Cradle??
I have stupidly erased the tag whilst fooling around!
From memory.. it was partly something like //samsungapps
Please help!!!!!
ukgearguy said:
Does anyone have the actual text that was written into the NFC Tag on the Galaxy Gear Cradle??
I have stupidly erased the tag whilst fooling around!
From memory.. it was partly something like //samsungapps
Please help!!!!!
Click to expand...
Click to collapse
OK it's now fixed. I did it myself. (downloaded Samsung Tag Writer which wrote the missing data back onto the NFC part of the charging cradle.)
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
quordandis said:
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
Click to expand...
Click to collapse
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.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
I rooted and installed xposed/wanam and no problems whatsoever.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
It's not root that screws up your phone. It's something that you do after rooting that screws up the phone.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
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?
quordandis said:
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
Click to expand...
Click to collapse
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.
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
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.
jdock said:
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.
Click to expand...
Click to collapse
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
quordandis said:
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
Click to expand...
Click to collapse
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.
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.
quordandis said:
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?
Click to expand...
Click to collapse
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.
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.
Click to expand...
Click to collapse
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.
quordandis said:
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
Click to expand...
Click to collapse
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.
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 ))
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.
quordandis said:
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
Click to expand...
Click to collapse
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!
Sent from my iPad using Tapatalk
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.
shortydoggg said:
It's not root that screws up your phone. It's something that you do after rooting that screws up the phone.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Spot on
Sent from my SM-G900T using Tapatalk
barondebxl said:
Spot on
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
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
shortydoggg said:
It's not root that screws up your phone. It's something that you do after rooting that screws up the phone.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
- 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.......
quordandis said:
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.......
Click to expand...
Click to collapse
]
Dunno whats wrong with your setup, but my rooted phone works fine in my wife's Ford and my Subaru.