Related
Hi,
I have a problem with Whatsapp program. It works perfectly fine when it comes to sending messages, although I have a problem with staying connected. The messages are delayed (sometimes it's even over 30 minutes) and when I simply wanna unlock my phone and text someone, the person won't receive my message until I reconnect my mobile data (grey clock icon on the left of my message). I've already seen many instructions on the net, like reinstalling Whatsapp, rebooting my phone, checking if my sync works and all that, but none of them worked for me. It really starts to annoy me, but I like this program alot and I don't want to give up on it that fast. So is there any way to force Whatsapp to stay connected full-time ?
I'm using MiniCM-2.2.0 with latest nAa Kernel.
Regards
Bump, spent the whole night browsing the net for similliar topics and found nothing...
ziemny said:
Hi,
I have a problem with Whatsapp program. It works perfectly fine when it comes to sending messages, although I have a problem with staying connected. The messages are delayed (sometimes it's even over 30 minutes) and when I simply wanna unlock my phone and text someone, the person won't receive my message until I reconnect my mobile data (grey clock icon on the left of my message). I've already seen many instructions on the net, like reinstalling Whatsapp, rebooting my phone, checking if my sync works and all that, but none of them worked for me. It really starts to annoy me, but I like this program alot and I don't want to give up on it that fast. So is there any way to force Whatsapp to stay connected full-time ?
I'm using MiniCM-2.2.0 with latest nAa Kernel.
Regards
Click to expand...
Click to collapse
well maybe you shouldn't give up on whatsapp but the ROM instead. What i mean is, maybe something inside the ROM/kernel wasn't installed properly and you could try reinstalling ROM and/or kernel... I know it's a stupid solution but it saved me many times when i couldn't find the answer anymore
bubr3g said:
well maybe you shouldn't give up on whatsapp but the ROM instead. What i mean is, maybe something inside the ROM/kernel wasn't installed properly and you could try reinstalling ROM and/or kernel... I know it's a stupid solution but it saved me many times when i couldn't find the answer anymore
Click to expand...
Click to collapse
Thank you for your reply. I already had the problem on previous ROMs (I mainly used MiniCM). Maybe I'll give GingerDX a shot. I'll tell you how it went.
Regards
Did you leave the app in background? When you leave Whatsapp, dont click back button, try clicking home button?? Dont move app to SD if you did!
Hit The THANKS Button If I Helped You!
Sent From My W8 Using Tapatalk
lucastan96 said:
Did you leave the app in background? When you leave Whatsapp, dont click back button, try clicking home button?? Dont move app to SD if you did!
Hit The THANKS Button If I Helped You!
Sent From My W8 Using Tapatalk
Click to expand...
Click to collapse
i belive that whatsapp is running in background by default, so as programs such as viber, hotmail, etc. but we all know that this can be checked under settings > applications > running applications
but i agree that moving whatsapp to SD could be the problem, although i had no problem when i moved it to SD
I didn't move it to SD card and I don't use any task killer. Process manager says it is running in the background. Still no idea how to fix it.
if it isn't because of moving to SD, and it is running in background, if it isn't because of ROM (you've said that you have used some ROMs before and that there was the same problem), if your data settings work normally (sync and stuff), if the problem persist on wifi and 3g and edge,...
it occurs to me that it can only be due to two things, maybe you installed cracked version of whatsapp due to 1-year-free expiration, or maybe something went wrong when you installed your current kernel
P.S. whatsapp is 70% of communication on my X8, and i understand you very well when you say that you won't give up on it so easily
bubr3g said:
if it isn't because of moving to SD, and it is running in background, if it isn't because of ROM (you've said that you have used some ROMs before and that there was the same problem), if your data settings work normally (sync and stuff), if the problem persist on wifi and 3g and edge,...
it occurs to me that it can only be due to two things, maybe you installed cracked version of whatsapp due to 1-year-free expiration, or maybe something went wrong when you installed your current kernel
P.S. whatsapp is 70% of communication on my X8, and i understand you very well when you say that you won't give up on it so easily
Click to expand...
Click to collapse
I didn't crack anything, I'm still on trial. If I wanted to get another free year, I'd change my phone number I also reinstalled the kernel too.
EDIT: Now it works properly on WIFI only. Still disconnects after couple of minutes on 3G.
EDIT2: It seems like reinstalling GDX and Alfs finally worked for me. Thanks for all the help guys
Another update:
after a few hours I'm back to the point where I started... the problem's still there. I'm really pissed off now -.-
ziemny said:
Another update:
after a few hours I'm back to the point where I started... the problem's still there. I'm really pissed off now -.-
Click to expand...
Click to collapse
It is only logical that Whatsapp won't implement itself right on your phone... This is all ridicoulos right know, because for as far as i know, you almost tried every solution possible, you've changed to other ROM, heck, you've even changed to other kernel and it still doesn't work.
You said it worked for a while, maybe some of the settings you've changed, and apps you've installed AFTER it was all working properly was interfering with your newly applied settings and/or installed apps
bubr3g said:
It is only logical that Whatsapp won't implement itself right on your phone... This is all ridicoulos right know, because for as far as i know, you almost tried every solution possible, you've changed to other ROM, heck, you've even changed to other kernel and it still doesn't work.
You said it worked for a while, maybe some of the settings you've changed, and apps you've installed AFTER it was all working properly was interfering with your newly applied settings and/or installed apps
Click to expand...
Click to collapse
I've installed Advanced Task Killer to see if it's the problem with Whatsapp, but it didn't block me from receiving the messages or anything. I uninstalled ATK and like an hour later, the problem occured again. I'll reinstall the kernel and the ROM again and leave it with only Whatsapp installed for a day. If that doesn't work, I might just buy an Xperia Neo V :S
Maybe it's because I connect to another network instead of my providers one ? I have data roaming enabled and stuff and I connect to Plus instead of Play (even though Play says they allow such things). Could this cause the problem ?
Or Swype Beta maybe ? I'm running out of ideas...
I just found out that when Whatsapp's not showing the "last seen" date (not connected), when I enter any website in the browser and return to Whatsapp, it shows the "last seen" properly. But I still have no idea what can this be...
ziemny said:
I've installed Advanced Task Killer to see if it's the problem with Whatsapp, but it didn't block me from receiving the messages or anything. I uninstalled ATK and like an hour later, the problem occured again. I'll reinstall the kernel and the ROM again and leave it with only Whatsapp installed for a day. If that doesn't work, I might just buy an Xperia Neo V :S
Maybe it's because I connect to another network instead of my providers one ? I have data roaming enabled and stuff and I connect to Plus instead of Play (even though Play says they allow such things). Could this cause the problem ?
Or Swype Beta maybe ? I'm running out of ideas...
Click to expand...
Click to collapse
Wait, does it work normally when you are on wi-fi? try to test whatsapp when you are strictly on wifi (wich means that you turn off celluar data, data roaming and national roaming), so that we can definitly exclude the problem of wifi.
if the problem isn't in wifi, try to connect on your providers network (PLAY) instead of other network (PLUS), and see if the problem persists
if the probelm still persists i belive there is counterinterfering with some application...
i know that i'm offering too much possible solutions, but i think that this can only be solved by method of trying out every possibility
bubr3g said:
Wait, does it work normally when you are on wi-fi? try to test whatsapp when you are strictly on wifi (wich means that you turn off celluar data, data roaming and national roaming), so that we can definitly exclude the problem of wifi.
if the problem isn't in wifi, try to connect on your providers network (PLAY) instead of other network (PLUS), and see if the problem persists
if the probelm still persists i belive there is counterinterfering with some application...
i know that i'm offering too much possible solutions, but i think that this can only be solved by method of trying out every possibility
Click to expand...
Click to collapse
As from what I see for the last 30 minutes, it's working fine on WIFI. I also tried switching to Play and disabling the roamings, but it still kept disconnecting.
The apps I have installed:
- Barcode Scanner
- Battle.net Mobile Authenticator
- Dolphin Browser
- exDialer & exContacts
- GG (Polish messenger, but I doubt it causes any errors as I just installed it recently)
- GO SMS Pro
- Real Player
- Root Uninstaller Pro (I only uninstalled DSP Manager)
- Whatsapp obviously
- ColorNote
- Nexus ICS Minimal Analog Clock
That's pretty much everything I have. I didn't change anything in the settings of GingerDX itself. I'm really helpless here...
huh, nothing from that list shouldn't interfere with anything... maybe you should put back ATK and see what exactly happens with whatsapp when it disconnects from network
i'm really running out of ideas
It's pretty simple. It's got nothing to do with your ROM, kernel, 3G or WiFi - AFAIK. Rather, I think it's to some extent do to your connectivity. The app's refresh interval apparently varies. Seems worse when you have many long threads. Deleting a few threads seems to work from time to time. I however use another android device & I assure you the problem is in no way restricted to the X8
Saipro said:
It's pretty simple. It's got nothing to do with your ROM, kernel, 3G or WiFi - AFAIK. Rather, I think it's to some extent do to your connectivity. The app's refresh interval apparently varies. Seems worse when you have many long threads. Deleting a few threads seems to work from time to time. I however use another android device & I assure you the problem is in no way restricted to the X8
Click to expand...
Click to collapse
So it's normal that I get my messages delayed by around 30 minutes or even more ? I clear my logs every day, so I think the messages should arrive like... instantly :S
ziemny said:
Hi,
I have a problem with Whatsapp program. It works perfectly fine when it comes to sending messages, although I have a problem with staying connected. The messages are delayed (sometimes it's even over 30 minutes) and when I simply wanna unlock my phone and text someone, the person won't receive my message until I reconnect my mobile data (grey clock icon on the left of my message). I've already seen many instructions on the net, like reinstalling Whatsapp, rebooting my phone, checking if my sync works and all that, but none of them worked for me. It really starts to annoy me, but I like this program alot and I don't want to give up on it that fast. So is there any way to force Whatsapp to stay connected full-time ?
I'm using MiniCM-2.2.0 with latest nAa Kernel.
Regards
Click to expand...
Click to collapse
Hi,
Do you still have the problem of the messages getting delayed?
I have the same problem since three months now I think.
I have already tried everything you guys said here.
I have no problems what so ever on WI-FI but only on 3G.
I think it has something to do with Whatsapp, maybe even with our accounts in specific.
Did you ever fix this problem?
Because I am having it on my Samsung Nexus S.
I found that when I send a message, and I am running whatsapp in the background I still woulnd't recieve the messages.
So I hope you found the solution and could maybe share? :angel:
ziemny said:
Another update:
after a few hours I'm back to the point where I started... the problem's still there. I'm really pissed off now -.-
Click to expand...
Click to collapse
try using supercharger v6 with script manager & use use multitasking settings
forum.xda-developers.com/showthread.php?t=991276
Hey guys,
Yesterday I bought Galaxy Gear. I currently own Galaxy S3 that I would like to pair with Gear.
I'm on custom SlimBean ROM with Android 4.3. I have installed the APK Gear Manager that is floating around the forum here (around 17mb), it installs without the problem, but when it comes to pairing I get a little popup that some part of Samsung SDK is not supported and the connection is being broken. Did anyone else get it to work with S3?
I have time till next saturday to decide whatever I will keep it or not, maybe there will be a solution by then. I can always return it to the store.
hurdlejade said:
Hey guys,
Yesterday I bought Galaxy Gear. I currently own Galaxy S3 that I would like to pair with Gear.
I'm on custom SlimBean ROM with Android 4.3. I have installed the APK Gear Manager that is floating around the forum here (around 17mb), it installs without the problem, but when it comes to pairing I get a little popup that some part of Samsung SDK is not supported and the connection is being broken. Did anyone else get it to work with S3?
I have time till next saturday to decide whatever I will keep it or not, maybe there will be a solution by then. I can always return it to the store.
Click to expand...
Click to collapse
update us if you manage to get it to work considering samsung said that it will pair with teh s3 once it updates to 4.3 :good:
sure, no problem, but my hands are tied at the moment, unless someone have some other idea how i could possibly pair it.
Can I ask does the watch display basic functions I.e time,camera etc ? Or is it stuck a the pairing icon?
Sent from my Nexus 7 using xda app-developers app
maybe there is a way to go further, but i don't see such option. it's stuck at pairing and only display battery left.
gear got gs3 and my gear paired without any issues. My gs3 is stock rom, downloaded the gear manager from Samsung app store and it all worked fine! There are some things that don't work - s voice, weather, can't install any new apps from Samsung app store but pretty much everytjing else works (calling, transfer of pics and videos, changing clock face, etc). Any questions, pls ask!
Rooted Stock Rom on my S3 and it paired fine with my 1st Watch (That went back to Best Buy, since I wasn't paying $300 until it was fully working - and my new one will be here tomorrow - had to take the 30% deal).
So it paires and the functions that worked, worked well ... Like the previous post - No apps / etc ... But Calls worked, pictures, etc
Sdr001 said:
gear got gs3 and my gear paired without any issues. My gs3 is stock rom, downloaded the gear manager from Samsung app store and it all worked fine! There are some things that don't work - s voice, weather, can't install any new apps from Samsung app store but pretty much everytjing else works (calling, transfer of pics and videos, changing clock face, etc). Any questions, pls ask!
Click to expand...
Click to collapse
May i know do we need to root inorder to use? i have download Gear Manager from other website, it allow me to install and connected to S Gear, but on my watch just keep showing Sync screen with phone which doesnt work at all.
Let me know where did u download and method to connect.
Thanks.
desmond047 said:
May i know do we need to root inorder to use? i have download Gear Manager from other website, it allow me to install and connected to S Gear, but on my watch just keep showing Sync screen with phone which doesnt work at all.
Let me know where did u download and method to connect.
Thanks.
Click to expand...
Click to collapse
No, it's not rooted, I installed the earliest version of the manager and that one seems to be the only one that works. Today stupidly I went to Samsung app store and tried to install the new version... as the install wasn't working I deleted the version I had - and this was a mistake as new versions seem to be compatible only with 4.3. After searching this site, I've found the version that works again thankfully! so if you click here: http://forum.xda-developers.com/showthread.php?t=2484065&page=4 and install the app from the last post - this should work. Let me know how you get on.
for anyone curious, using this rom: http://forum.xda-developers.com/showthread.php?t=1910947 and this Gear Manager apk: http://depositfiles.com/files/pmgqxv9c5 will get you paired up with your Galaxy Gear.
Everything connected right up no problem.
The only issue is no notifications, which is the main reason I wanted this but its only a temporary issue. Hopefully.(c'mon 4.3 update :fingers-crossed
Camera, calls, even incoming calls, work fine, can change app settings and everything. I was even able to load GamboyColor AD and play some pokemon on it lol.
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.
Hey folks,
I've got a stock, unrooted Galaxy S4 Active. Recently I've been having a lot of trouble with it...
Long and short of it is, at some random, arbitrary point, it will lose all service - internet, calling, GPS, and text messaging - until I turn airplane mode on and off again. Then it immediately begins to work again, only to lose all service at some random point again. It could work fine for up to two days, or it could work for 20 minutes or so. I'm baffled.
Worth considering:
It never seems to "lose service" while actively being used, though that could simply be luck.
Sometimes GPS works, sometimes it doesn't.
It never "turns back on" on it its own - ever. Only a hard reset or an airplane mode toggle will fix it.
It doesn't SAY that it's out of service - for all intents and purposes, it looks like it's working fine. It's only when you try to USE one of the services and they don't work that you notice something's up. For this reason, I couldn't use Tasker to automatically airplane on/off based on network availability.
While it isn't working, calls to it go straight to voicemail.
After an airplane mode toggle, I immediately receive all missed texts and missed call notifications.
What I've tried:
Upgrading versions OTA via AT&T.
Downgrading versions via AT&T's files, via USB.
Factory reset.
Changing the APN (though I MAY have done this wrong/not changed it correctly, and after it didn't work any better, I removed the added APN).
If anyone can help, I'd be extremely grateful. Thanks!
Put the APN settings below to check and see
Sent from my SGH-I537 rooted, running GPE 4.4.4 ROM
Xanthos58 said:
Put the APN settings below to check and see
Sent from my SGH-I537 rooted, running GPE 4.4.4 ROM
Click to expand...
Click to collapse
Mine does the same thing as the OP. It's really really really pissing me off. Not only can you not tell till you try to do something you don't know you're missing calls and txts till you reboot. Mine is also stock running 4.4.2 OTA. Getting close to saying screw it and getting a gs5. OP, did you ever find a solution? Rebooting 15 times a day and not getting calls is getting really old.
My s4 active does the same. ..... as well as my s3. I'm wondering if it is network related. I also have a Samsung ativ s Windows 8 phone that does that as well.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
spyre said:
Mine does the same thing as the OP. It's really really really pissing me off. Not only can you not tell till you try to do something you don't know you're missing calls and txts till you reboot. Mine is also stock running 4.4.2 OTA. Getting close to saying screw it and getting a gs5. OP, did you ever find a solution? Rebooting 15 times a day and not getting calls is getting really old.
Click to expand...
Click to collapse
Yup, getting the exact same issue on 4.4.2 OTA but rooted so no bloatware and running the google now launcher. Fix would be great.
Same thing happens to me constantly in my house, I believe it has to do with low signal on LTE and it switching it HSPA.
Yah, still happening. Anyone find a solution?
I find thay if I can connect to wifi shortly, network is back... also switching airplane mode momentarily works as well. Faster than a reboot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
I too was having this problem... and I suspected it was one of the xposed modules doing it. Once I disabled all of the modules, I've had no more problems.
But since some of you are saying this is happening even on your stock/non-rooted phones I don't know what to think.
camattin said:
I too was having this problem... and I suspected it was one of the xposed modules doing it. Once I disabled all of the modules, I've had no more problems.
But since some of you are saying this is happening even on your stock/non-rooted phones I don't know what to think.
Click to expand...
Click to collapse
Interesting, I also have xposed installed. Which modules did you have running? Maybe we can cross check them. I have the following:
Wanam Xposed
XPrivacy
YouTube AdAway
RootCloak
Xposed GEL Settings
pinyata said:
Interesting, I also have xposed installed. Which modules did you have running? Maybe we can cross check them. I have the following:
Wanam Xposed
XPrivacy
YouTube AdAway
RootCloak
Xposed GEL Settings
Click to expand...
Click to collapse
I had the following enabled (and haven't reenabled any of them since turning them off):
AppOpsXposed
DisableBatteryFullAlert
KitKat SD Card Full
NoSafeVolumeWarning
Wanam Kit
Wanam Xposed
YouTube AdAway
And I'm pretty sure I didn't enable Kit & Xposed at the same time, and don't recall which one was enabled when I disabled 'em all.
I might try reenabling them all minus the two Wanam* modules and see how it behaves. As pointed out, though, sometimes it's hard to know when it's acting funny! :-/
So far so good... over 24 hours and I haven't had to cycle airplane mode. I've had these modules enabled:
AppOpsXposed
DisableBatteryFullAlert
KitKat SD Card Full Access
NoSafeVolumeWarning
YouTube AdAway
Maybe I'll be bold tomorrow and enable Wanam Kit tomorrow and see how things go from there.
Well, the problems have persisted but ATT just released an OTA update that says it fixes connectivity issues with calls and texts. I'm really excited now. Almost done with the update and looking forward to a phone that actually works!
Hello everybody,
I'm struggling to find a way to automatically answer incoming calls on my Moto G 2nd gen (stock ROM) when the Bluetooth headset is connected. When I bought the phone, i.e., before the Lollipop update, I used a third-party application (Handsfree) to answer incoming calls when the Bluetooth is connected. After the update to v5.0.2, neither Handsfree nor any other similar application I found on the Play Store seems to work anymore, and I always have to manually click the headset button to answer the call, which is quite unpractical.
I searched on the internet a little bit, and it looks like this feature has been removed (!!??) with the Lollipop update, but other websites report that the feature is still present in Motorola Assist, which I couldn't manage to get working since I couldn't find any option for automatic answer in the Driving Mode, nor anywhere else. Any ideas? Is perhaps this feature available on some custom ROM, such as Cyanogenmod?
Thank you very much!
Even i am looking for the solution might be lollipop update broken all apps which use to automatically answer the calls
st1led said:
Hello everybody,
I'm struggling to find a way to automatically answer incoming calls on my Moto G 2nd gen (stock ROM) when the Bluetooth headset is connected. When I bought the phone, i.e., before the Lollipop update, I used a third-party application (Handsfree) to answer incoming calls when the Bluetooth is connected. After the update to v5.0.2, neither Handsfree nor any other similar application I found on the Play Store seems to work anymore, and I always have to manually click the headset button to answer the call, which is quite unpractical.
I searched on the internet a little bit, and it looks like this feature has been removed (!!??) with the Lollipop update, but other websites report that the feature is still present in Motorola Assist, which I couldn't manage to get working since I couldn't find any option for automatic answer in the Driving Mode, nor anywhere else. Any ideas? Is perhaps this feature available on some custom ROM, such as Cyanogenmod?
Thank you very much!
Click to expand...
Click to collapse
Tasker can do this, and SO much more. Its brilliant for automating anything on your android device
Duck86 said:
Tasker can do this, and SO much more. Its brilliant for automating anything on your android device
Click to expand...
Click to collapse
Thank you for your suggestion. I tried to achieve this functionality with a Tasker script, taking inspiration from here: tasker.wikidot.com/btautoanswer. Actually, the link seems to refer to some older version of Tasker, because I had to to do slightly different steps. However, the functinality "Take call" which seems to be crucial to do what I want is "unavailable on this device". This is confirmed by the tasker changelog: tasker.dinglisch.net/changes/changes4.6.html
Removed
action Take Call: not available on Lollipop+ (Google not granting the needed permission)
Click to expand...
Click to collapse
How did you do that with Lollipop?
U need to root for tasker to work for picking up the call automatically... google ruined the lollipop
I see. I will try and let you know. Should I see the Take Call action as available upon rooting?
st1led said:
I see. I will try and let you know. Should I see the Take Call action as available upon rooting?
Click to expand...
Click to collapse
so how can i take call with tasker on lollipop?
robertusIT said:
so how can i take call with tasker on lollipop?
Click to expand...
Click to collapse
Sorry for not following up. I don't have access to the device at the moment since the request for help in this thread was originally meant for another person. I won't be able to try the solution bloodhound42 suggested before a couple of months, unfortunately. Feedback is appreciated if some adventurer wants to try first!