Related
Has anyone else noticed their DROID 4 dropping data connectivity seemingly randomly and requiring a reboot to pick it back up? I know that I am...and I'm wondering if Motorola can't make it hang onto a data connection how hash is ever going to mmake it work right.
I haven't had any issues with data at all... LTE/3G handoffs work perfectly and everything ...And no worries, I am confident the data issues will be sorted out on the ics builds!
I have them issues. If connected via wifi no problem. But still wont be connected to the network. Requires a reboot to aquire network back
Sent from my DROID4 using xda premium
podspi said:
I haven't had any issues with data at all... LTE/3G handoffs work perfectly and everything ...And no worries, I am confident the data issues will be sorted out on the ics builds!
Click to expand...
Click to collapse
Are you running on a rooted DROID 4 with safe strap installed? Just trying to narrow down the possibilities.
For the record.
Rooted and safestrap installed running stick
Sent from my DROID4 using xda premium
liquidoc said:
Are you running on a rooted DROID 4 with safe strap installed? Just trying to narrow down the possibilities.
Click to expand...
Click to collapse
Rooted stock, no safestrap.
Though I doubt safestrap is causing data issues, or fixing them for that matter.
While I do plan on flashing some custom ROMs at some point, I have to admit that I'm very happy with the stock rom. Performance is very good, smart actions are actually pretty great (though there are of course 3rd party apps that do the same thing), and the camera app works pretty well.
My only complaint are the window transitions, blech. Yea, you can disable them, but then all the eye candy goes away completely! Ah Moto, why no middle ground?
I have had data connection issues on all the ICS ROMs but data on stock has been pretty solid.
Did you just port your number from another carrier to verizon? I had the same issue plus some and called verizon and they fixed it on their end. Hope this helps.
Sent from my DROID4 using XDA
I had a few problems with my data just going out for a few minutes on the stock rom. I would be browsing the web, and then a page would just not load. I noticed my signal indicator was grey and not blue, and thus I wasn't getting a data connection. I just waited a few minutes and it came back up.
I never really though too much into it because I expect these small things to happen on such a big wireless network.
deturbanator said:
I had a few problems with my data just going out for a few minutes on the stock rom. I would be browsing the web, and then a page would just not load. I noticed my signal indicator was grey and not blue, and thus I wasn't getting a data connection. I just waited a few minutes and it came back up.
I never really though too much into it because I expect these small things to happen on such a big wireless network.
Click to expand...
Click to collapse
This is exactly what happens to me. It almost seems like a session timing out and renewing but I don't have a clue how the LTE network works.
Had the same data issue.. went to Verizon store and got a new SIM card (free) and problems cleared right up. Evidently the old SIM card did not get activated properly in their system.
I'm also having connection problems from time to time. I'm in a 3G only area. I'm running a stock non-rooted phone. Usually, I can get the connection back with a reboot. It's still a pain in the ass, I shouldn't have to deal with. I've called Verizon a few times. Its like talking to a wall with them. They act like you are the dumbest person in the world. Hopefully the next update can clear this problem.
Sent from my DROID4 using xda premium
After dealing with this problem for over 2 months I finally found an answer.
I have had this problem since day 2 and after getting the run around several times at the Verizon store (They claimed it was because they were upgrading to LTE in the area, which they said we'd have within 1 month over 2 months ago) they told me there was nothing they could do and suggested I call tech support (I don't know why I didn't think of that). I called tech support and talked to a very helpful woman, after describing my problem to her she asked me what phone I had, she knew the issue right after I told her it was the Droid 4. She told me it was a well known issue with the Droid 4 and that they expect a patch to be released at the end of the month (July) that would address the problem. She said that some people have had temporary success with toggling airplane mode (this has never worked for me but rebooting a few times does) and that having WiFi on, even when your not connected, can knock your data connection out (I have been able to reproduce this once so far).
So that's it. Keep your WiFi off when you don't need it, reboot when you have problems, and hopefully it will be fixed at the end of July.
I'm very disappointed with my Verizon store. Some of the employees I talked to owned a Droid 4 themselves and said they had the same problem and still claimed it was tower work. Either they were misinformed, stupid, or they were lying to me (who wants to buy a broken phone).
My Droid 4 does this in 4G mode. I've read that it's due to the nature of SIM cards. The network constantly vets and authorizes the card's access. If this vetting fails, you get the "white out", as I call it. It might clear up on the next pass, or you might have to reboot. My "solution" is to keep it in 3G mode. As for getting a fix at the end of the month, I'm not holding my breath, as I've read that that's VZW's standard response to just get the customer to shut up and go away.
I've been having the data dropping issue as well for the past few weeks. Running stock GB, rooted with safe strap, but have yet to flash a custom ROM. I thought the issue might be because I'm on a legacy Alltel plan with PRL 14012, which is way outdated...
Well, today I believe I finally found the source of what was causing the issue for me personally, from an unexpected source...Flipboard.
I've found myself glancing at it a bunch at red lights when I'm driving, or sitting in a waiting room, etc. Today I was driving though, and noted towards the end of my trip that this was the first time in weeks the phone hadn't once lost it's data connection for the entire drive. After reflecting for a moment on what, if anything, was different about this excursion, the only thing I could come up with is that I hadn't used Flipboard since I left the house. Even though my initial reaction was to seriously doubt a respectable app like that could cause such an issue, I had nothing else to go on. So, for the hell of it, I picked up my phone and fired up Flipboard...
Within 5-10 seconds of clicking it...BAM...gray 4g icon and no data would load. Needless to say, I uninstalled Flip**** right away...then reinstalled so I could comment on it in the market, then uninstalled again, and haven't dropped data at all in the last several hours. I also took note that a guy with a Droid Razr Maxx left a comment complaining that Flipboard was actually causing random reboots for him.
I don't know if any of you have Flip**** installed, or why you're having similar data issues, but if any of you do happen to have it installed, try uninstalling from the phone...not the market. Then, turn your phone off, pull out the SD card and SIM for a moment or so, put them back in, power up the device, and see if that might possibly help alleviate the constant data dropping. If I find I start dropping data again, without Flipboard installed, I'll update this post. Good luck.
No Flipboard on my phone. I'm glad you found an answer to your problem though.
Tappin' and talkin' with Tapatalk.
I've been having problems since Verizon turned on 4G LTE in my area. Once a day I have to remove my SIM card. If I don't, the 4G is very unreliable. Could it be a bad SIM card? Or maybe the fact that they just activated it here and they're working out the bugs? Anyone have any ideas?
I also forgot to mention, I've got a Motorola XOOM 4G LTE And have had not one single connection problem since 4G went live in my area.
Sent from my DROID4 using xda premium
I just have the data connection issue when ever i flip on wifi then disable it .. a reboot is required for data to work again regardless if i force 3g or if i am trying to use lte.. guessing it is a software bug.. i never seem to have a connection issue if wifi wasnt used prior.
Sent from my DROID4 using Tapatalk 2
podspi said:
My only complaint are the window transitions, blech. Yea, you can disable them, but then all the eye candy goes away completely! Ah Moto, why no middle ground?
Click to expand...
Click to collapse
I know this thread and comment are old, but if you use Spare Parts, you can change the Window Transition speed to Fast and then your phone seems much faster/smoother. Don't mess with Window Animation speed if you want to keep th TV-like power off blip.
My Droid 4 Connection Issues
taintphuck said:
I've been having the data dropping issue as well for the past few weeks. Running stock GB, rooted with safe strap, but have yet to flash a custom ROM. I thought the issue might be because I'm on a legacy Alltel plan with PRL 14012, which is way outdated...
Well, today I believe I finally found the source of what was causing the issue for me personally, from an unexpected source...Flipboard.
I've found myself glancing at it a bunch at red lights when I'm driving, or sitting in a waiting room, etc. Today I was driving though, and noted towards the end of my trip that this was the first time in weeks the phone hadn't once lost it's data connection for the entire drive. After reflecting for a moment on what, if anything, was different about this excursion, the only thing I could come up with is that I hadn't used Flipboard since I left the house. Even though my initial reaction was to seriously doubt a respectable app like that could cause such an issue, I had nothing else to go on. So, for the hell of it, I picked up my phone and fired up Flipboard...
Within 5-10 seconds of clicking it...BAM...gray 4g icon and no data would load. Needless to say, I uninstalled Flip**** right away...then reinstalled so I could comment on it in the market, then uninstalled again, and haven't dropped data at all in the last several hours. I also took note that a guy with a Droid Razr Maxx left a comment complaining that Flipboard was actually causing random reboots for him.
I don't know if any of you have Flip**** installed, or why you're having similar data issues, but if any of you do happen to have it installed, try uninstalling from the phone...not the market. Then, turn your phone off, pull out the SD card and SIM for a moment or so, put them back in, power up the device, and see if that might possibly help alleviate the constant data dropping. If I find I start dropping data again, without Flipboard installed, I'll update this post. Good luck.
Click to expand...
Click to collapse
I don't have Flipboard, however I noticed connection issues within 12 hours of getting my phone. At the time it was stock GB. I took it back to the store, he called tech support. Between the 2 of them, my phone was hard reset, the SD and SIM cards were pulled and the phone rebooted, they fiddled with settings, tech support tried to turn on data from their end, nothing worked. I noticed I lost my data connection when the Smart Action for battery saver clicked on. It was like it got stuck and the phone couldn't turn on data anymore. I did a factory reboot, and got data back. I turned on that first smart action, lost data connection again, it wouldn't turn back on. So I did another factory reboot, disabled that "Smart" Action, and been ok since then. I do still loose my connection, but I am able to get it back if I turn wifi on. Not sure why, but it works most of the time. Some days I still have data if I turn my wifi off, other days i have to leave wifi on if I want to use my 4g. I have my phone rooted, running GB and loving Spirit FM..(Having FM radio was the only reason why I rooted my phone..can't live without my FM!!) Is there anything I can do to get my data connection to stay on?
BTW an OTA update has occured for GB, but it doesn't seem to have fixed the problem.
As a preface: I am on JB build .489, rooted with CWM recovery installed. Locked bootloader so there is no custom kernel. I have removed bloatware and installed Xposed Framework, but have not done anything to affect the internet settings.
Now on to the actual problem:
Last night I was on the internet when my phone ran out of batteries. I stuck it onto the charger, offline charging was working fine etc.
Then when I turned the phone back on there was no internet connection whatever. The mobile data "on" in the status bar and in the setting page both work but have no real effect, but when toggled the usual Data warning messages appear, or the data traffic has been disabled message appears too. Yet despite all this no mobile internet signal icon appears in the status bar, and I cannot download internet settings and mms settings.
Wifi is a different story: when toggled in the status bar toggles, the animation for wifi on plays for around 7-10 seconds then stops, no signal is established. In the setting menu however, the actual soft button appears to be slightly greyed out, but I can still toggle that too. But once I do, the text "Turning Wifi On" appears on the page, but nothing else happens besides eventually the Wifi turning itself off. No network is found.
I haven't done anything to cause this, to the best of my knowledge. I have uninstalled the few apps which I installed last night, I have tried hard reboots, waiting until both one vibration or three vibrations when rebooting. I have tried resetting the Xposed frameworks to system default (I know it shouldn't have any bearing on it but still). The only thing that I can think of that I havenn't mentioned is that I used the Busybox installer the other day to update busybox and also install the zipalign option (didn't get round to doing anything with it though, and the internet was working fine after that for atlest a few hours) but then again this should have no bearing on my internet connectivity whatsoever.
Well... There you have it. Any and all recommendations are welcome, though I would also say that I would not like to do the usual "take a backup, repair with PC Companion" method which most people seem to suggest, so anything other than that I would appreciate as advice. I do not have logcat installed but I have ROM Toolbox installed along with a few other Root Utilities so I can get a couple of pieces of information if necessary.
So what do you all think? How do I fix my phone?
Thanks in advance!
Have you tried redownloading internet settings through Settings/Xperia/Internet Settings? That might fix the mobile broadband problem
SammiSaysHello said:
Have you tried redownloading internet settings through Settings/Xperia/Internet Settings? That might fix the mobile broadband problem
Click to expand...
Click to collapse
It just says "unable to download"
Bump. Anyone?
Please only bump a thread once every 24 hours.
I would suggest rapairing with PCComapnion or sues.
Maybe restoring a backup.
Take out SIM, give it a clean and re-insert
Apparently removing the SIM card and cleaning it worked! Mods go ahead and close this thread if you want.
Sent from my LT30p using xda app-developers app
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 all,
On my 2013 Moto X, sometimes when I turn on the wifi tethering the internet doesn't work either on tethered devices, or on my phone. If I turn the wifi tether off, my phone will connect to the internet again.
If I restart the phone and then enable tethering, I can use the internet on any device for a few minutes, then it refuses to connect. Again, if I turn tethering off on my phone, I can then get online on my phone.
I am rooted and Xposed, and don't have gobs of apps on my phone. I can't think of any app that I've installed recently that started this.
Any ideas what I could try to figure out what is going on?
You say it works for a few minutes after reboot. Do you try it immediately after the phone finishes booting up? what I'm getting at is sometimes apps start up on boot but there is a delay, so maybe a root app or Xposed module is interfering, but because of the delay right after rebooting you have a brief window to use tethering.
One way to check this is don't try to tether immediately after rebooting. instead let the phone sit for a few minutes while all the apps that run automatically on boot finish starting up. then try tether, and it should fail.
Check SuperSU to see what apps have root access and see if any of them look suspicious. you can disable superuser access temporarily from within the app.
Also check your Xposed modules. anything that deals with Wi-Fi or data, or has some option in its menus that changes Wi-Fi or data, is a suspect.
If nothing jumps out as suspicious, I'd probably temporarily uninstall Xposed access (just use the uninstall button in the Xposed installer menu, you can reinstall later, your modules will still be there, don't uninstall the actual Xposed installer app) and reboot and try tethering, and if that doesn't help then disable superuser from within SuperSU, reboot, and try tethering.
Safeboot is another option, but I'm not sure how that behaves in regards to having Xposed. Safeboot is accessed by long pressing the Power Off option that appears when you long press the power button.
Thanks for the suggestions! I'll try them out and see what happens.
I've started disabling some Xposed modules, but I need at least one in order to tether. So I'll disable them all, one by one, until it works.
Okay, so I've been working on this for a while now trying to figure out what is going on... Here's what happening:
If I turn on tethering, it will work for a few mins, then I'll still be connected to the phone hotspot, but I can't go anywhere. Web pages time out, streaming stops, that kind of thing. If I pick up my phone and try to do anything internet related when this happens, I won't have any internet connection on the phone either.
The problem persists if I turn off the hotspot or toggle airplane mode. The only way I can reestablish an LTE connection is to reboot the phone. Until then I won't have any internet connectivity.
Here's what I've done so far, and the problem still persists... Note: I'm on Verizon and have grandfathered unlimited data.
1) I have zwilie's kernel, so I removed that and restored the stock kernel. Problem still persisted.
2) I have xposed installed and several modules. I disabled and uninstalled every module except xposed itself and the moto x tether enabler. Problem still persisted.
3) I used mflash and reflashed system, boot, modems. Problem still persisted.
4) I found a different method of using hotspot that doesn't use xposed. I uninstalled xposed and used the other app. Problem still persisted.
5) I wiped the phone completely and restored to stock 4.4.4 using mflash and the stock 4.4.4 images for my phone. Rooted and reinstalled xposed and moto tether. Problem still persisted. **HT to KidJoe for his excellent guides on flashing**
6) I entered safe mode. However, because that disables all third party apps, I couldn't tether to try that, so that's an unknown.
I don't know what else to try or what else to do. We started using my wife's S4 as a hotspot, but it is starting to exhibit strange behavior as well (data only works for a while, but it will reconnect if I toggle airplane mode). It is also rooted, xposed, and using the tethering enabler.
The only other thing I can think of that I can't try is to reboot in safe mode and try tethering from that. But because the only way I know to enable tethering is to use xposed or a 3rd party app, I can't figure out how to make that work. Also, when I restored my phone, I let it install all my usual apps before I tried tethering again. I don't have a lot of apps, but if anyone knows of ones that may interfere with tethering I'd try uninstalling them.
I'd appreciate other suggestions, please!
Thanks for your time!
{edit} Added HT to KidJoe {/edit}
Okay, I have a couple other things to add...
If I use FoxFi to enable USB tethering, I can tether until the cows come home. This doesn't exactly work for what I'm wanting to do, but it does allow me to tether.
Also, for some really, really, really strange reason, if I change the SSID of the hotspot I can wirelessly tether for a while until a couple devices connect, then it drops out again until I restart the phone.
Am I looking at a really specific, really strange software bug??
Hi everyone,
I just jumped over to t-mob and got an HTC M9 (Long time HTC user, mogul, raphael, htc evo etc). Phone came with Lollipop 5.0
So for the past few days I have been using my phone and turning on my wifi hot spot to connect my tablet and laptop. I have hot spot as part of my plan. No issues at all. So before I was able to turn off auto system update, t-mobile pushed the 5.1 update to the phone while I was driving. When I got to my job, I turned on my hot spot and everything was fine, but as soon as the display on the screen turned off, I lost hotspot.
So in the help section I found that you could call HTC and I was frankly surprised, spoke to a rep and they told me they would escalate it to tier 2. Today got a call back. Basically ran through some steps and the support told me you need to leave your display on in order to use hot spot. HTC did this in order to prevent excessive battery drain . At that point I was like how much sense does that make, display on is the most battery consuming task. If I need to keep my display on in order to use hot spot, its going to burn through my battery. I spent over 6 hours before hand with hot spot on and the battery barely budged. Anyways, I was disappointed after the call. Basically HTC just told me we can't fix the problem but keep your display on and turn off the lock screen.
I have a samsung galaxy prime running 5.1.1 on the same plan, and hotspot works with the screen off.
Stupid! Anyways I was hoping the xda community had some insight into this issue.
Setting:
mobile hotspot>advanced settings>power mode>always on
********* POSSIBLE FIX ************
---------- My Specs -------------------
Just to confirm my specs.
Hotspot is part of my plan, it was turning off when my screen turned off (screen off/data off)
Android 6.0
Build Number 3.39.531.7 CL690290 release-keys
Running ViperOneM9 4.3.0 Rom which includes Root
Installed via TWRP 3.0.0-2
---------- The Fix ----------------------
Turn off mobile hot spot
Goto settings / mobile data / Access point names
You should see 2 locked APNS.
Hit the Plus Symbol and add the following settings:
Name: T-Mobile US LTE
APN: fast.t-mobile.com
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MCC: 310
MNC: 260
APN type: default,supl,mms,dun <-- that dun is missing from the similar locked APN
APN protocol: IPv4 <-- well will come back to this after reboot!
APN roaming protocol: IPv4
SAVE AND REBOOT
Now open up chrome and you should get a not connected error.
Goto to the APM we just made and change APN protocol: IPv4 to APN protocol: IPv6
Now turn on your mobile hot spot, its working for me. I still have pdanet and foxfi installed but I am not turning these on. I am using the hotspot from the quick menu set. Its showing amazing speed via speedtest and best of all working with screen off!!
********* FIX DID NOT WORK ON NON ROOTED STOCK HTC M9 ************'
Just tried the above procedure on stock htc m9 from t-mobile, its locked, not rooted and running stock marshmallow all done over OTA. Even installed pdanet (which contains foxfi) and nothing, data shuts off when screen goes to sleep.
*** Reserved For Updates ****
Same problem here. I tried several things. I'm rooted running official 5.1 software.
I was hoping the 6.0 update would fix it, but I've yet to get the chance to do it.
Good to know it isn't just me having hotspot on/off problems.
It used to work great when I first got it.. now when tethering its like nothing can stay connected for more than 30 secs before it loses it and no longer seen by other clients.. then it will show up again. Happens with all my devices so I know it is the phone itself. But the hotspot shows that it is up and running with no errors
6.0 Fails to Fix HotSpot Shutting Off Data When Display Powers Off
Guys,
So last night I updated to 6.0. I am all stock and took it OTA. Today back to square 1.
If I connect to the phone with the display off it connects (aka its showing up) but says no internet. If I wake up the display the message switches to "Connected" and the internet on the tablet works. Internet stops working as soon as the display powers off.
darkphoenix2012, So you are having the same exact problem? As soon as your display power off, you lose your hotspot connection on whatever device you are using right? Do you recall if hotspot worked fine before your 5.1 update?
From all the reading I have done, HTC must have turned off something in the dozer settings aka the new power saving options.
I came across this article: http://www.howdoitech.com/2014/08/fix-tethering-htc-one-m8/
darkphoenix2012, any chance you can get the contents of this default.xml file and post since you are rooted? I want to take a look if the values in there are causing the problem.
DssTrainer, what version of android are you running? I can see my hotspot as well just not data works from my devices.
Side By Side
So looking at a brand new HTC m9 (Running 5.0.2) as shipped from T-mobile NEXT to my HTC m9 (Running 6.0). Multiple Power options missing, as marshmallow loses options inside "Power Saver" for "Battery Optimization". M9 running 5.0.2's hotspot works with the screen off. HTC m9 running 6.0 marshmallow shuts off my hotspot with screen off as does 5.1.
I turned off every battery optimization for every application listed as noted by "Not Optimized". My HotSpot shuts off when my screen shuts off regardless. My Data Connection is being "put to sleep when screen is off" with Android version 6.0. And as far I see, there is no equivalent option inside the "Battery Optimization" Apps setting.
WTF to do now? HTC tech support = useless.
cloves said:
So looking at a brand new HTC m9 (Running 5.0.2) as shipped from T-mobile NEXT to my HTC m9 (Running 6.0). Multiple Power options missing, as marshmallow loses options inside "Power Saver" for "Battery Optimization". M9 running 5.0.2's hotspot works with the screen off. HTC m9 running 6.0 marshmallow shuts off my hotspot with screen off as does 5.1.
I turned off every battery optimization for every application listed as noted by "Not Optimized". My HotSpot shuts off when my screen shuts off regardless. My Data Connection is being "put to sleep when screen is off" with Android version 6.0. And as far I see, there is no equivalent option inside the "Battery Optimization" Apps setting.
WTF to do now? HTC tech support = useless.
Click to expand...
Click to collapse
Sadly this is the case. The only option is to keep it on a charger while tethering and select stay awake in dev options.
cloves said:
So looking at a brand new HTC m9 (Running 5.0.2) as shipped from T-mobile NEXT to my HTC m9 (Running 6.0). Multiple Power options missing, as marshmallow loses options inside "Power Saver" for "Battery Optimization". M9 running 5.0.2's hotspot works with the screen off. HTC m9 running 6.0 marshmallow shuts off my hotspot with screen off as does 5.1.
I turned off every battery optimization for every application listed as noted by "Not Optimized". My HotSpot shuts off when my screen shuts off regardless. My Data Connection is being "put to sleep when screen is off" with Android version 6.0. And as far I see, there is no equivalent option inside the "Battery Optimization" Apps setting.
WTF to do now? HTC tech support = useless.
Click to expand...
Click to collapse
The only thing I can suggest is root the device, install xposed framework and look for a module called Smart Network. Maybe that will fix it.
Sent from my HTC One M9 using XDA Labs
Thanks aestivalisakito,
Going to try to unlock my boot loader and then root today. I asked on the viper rom thread for other users to see if they had hotspot working and got a reply from one guy also on tmobile who says his works perfect with the screen off. Ill post back once I get to the bottom of the issue.
Just a little perplexed that either people don't use hotspot on the go like me or maybe just people don't post on the thread lol.
Well I got my m9 when I was with t-mobile and am still using it on metropcs (which is actually just T-Mobile) and I have to say I do remember having an issue similar to your foe a very short while and that's why I suggested the smart network solution.
But no problem glad I could help
Sent from my HTC One M9 using XDA Labs
From what I can tell so far, the feature works fine for me after doing the 6.0 update, including new radio etc.
aestivalisakito said:
The only thing I can suggest is root the device, install xposed framework and look for a module called Smart Network. Maybe that will fix it.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thanks for the suggestion aestivalisakito,
So I rooted the phone and installed the viper rom (its the only current rom that supports my tmobile firmware). Hotspot issue remains.
Also installed the xposed framework and the "Smart Network" module. I messed with a few of the options and sadly doesn't look like its fixed.
Is everyone else also on T-Mobile? Or are you guys on different carriers?
darkphoenix2012 said:
From what I can tell so far, the feature works fine for me after doing the 6.0 update, including new radio etc.
Click to expand...
Click to collapse
Dark are on you t-mobile? Did you do OTA? How did you update the radio?
Are you saying your hotspot is working now with the screen off?
Cloves I have a radio update thread to flash new radios through recovery here: http://forum.xda-developers.com/one-m9/general/recovery-flashable-radio-zip-t3122983
Secondly I was on T-Mobile until a week ago now I am on metropcs which is the same s T-Mobile (in fact they are owned by them)
Sent from my HTC One M9 using XDA Labs
---------- Post added at 09:31 PM ---------- Previous post was at 09:20 PM ----------
I just thought about something too go to settings->about->software information->more and take a screenshot and upload it for me here
cloves said:
Are you saying your hotspot is working now with the screen off?
Click to expand...
Click to collapse
Would like to know also
kc6wke said:
Would like to know also
Click to expand...
Click to collapse
No, hotspot stops working once the screen is off. It has not worked with screen off since the official firmware (5.0.2) was updated via OTA to 5.1 and same issue with 6.0.
Are you also on t-mobile and running marshmallow 6?
cloves said:
No, hotspot stops working once the screen is off. It has not worked with screen off since the official firmware (5.0.2) was updated via OTA to 5.1 and same issue with 6.0.
Are you also on t-mobile and running marshmallow 6?
Click to expand...
Click to collapse
Correct, I'm on my stock deodexed ROM. I have tried all 6.0 Roms and they are the same.
Dark says it's working for him, would like to know how.
aestivalisakito said:
Cloves I have a radio update thread to flash new radios through recovery here: http://forum.xda-developers.com/one-m9/general/recovery-flashable-radio-zip-t3122983
Secondly I was on T-Mobile until a week ago now I am on metropcs which is the same s T-Mobile (in fact they are owned by them)
Sent from my HTC One M9 using XDA Labs
---------- Post added at 09:31 PM ---------- Previous post was at 09:20 PM ----------
I just thought about something too go to settings->about->software information->more and take a screenshot and upload it for me here
Click to expand...
Click to collapse
Hi aestivalisakito,
Here is the screen shot. I am now rooted and running viperRom as an FYI. Problem still is the same.
cloves said:
Dark are on you t-mobile? Did you do OTA? How did you update the radio?
Are you saying your hotspot is working now with the screen off?
Click to expand...
Click to collapse
I did everything the "hard" way or manually. I installed both firmware packages from command prompt. There were two packages to flash separately twice, once each because of flushing during command prompt. I then flashed the official Tmo 6.0 M9 rom that was debloated and used AROMA installer. I had to actually flash it twice after I noticed google now on tap did not work. I flashed once with NOTHING other than the Tmobile account app optionally installed. Then I did a dirty flash with the same rom on top of what I was already running. After crossing my fingers and hoping for the best I actually have a 100% flawless experience. I am not sure if I'm just lucky or if there was a reason behind my dumb luck. I wish I could give more information to be helpful but currently I'm not running into any issues with WiFi tethering or ANY other problem right now. As a matter of fact I'm getting two days off the charger with NO effort to be conservative. It should be pointed out I have as clean of a clean install as I could possibly. I loathe bloat and went through the annoying steps to rebuild from scratch using playstore and LOTS of data. If there are any more questions I could possibly answer just ring my bell.
Found A Work Around!
darkphoenix2012 said:
I did everything the "hard" way or manually. I installed both firmware packages from command prompt. There were two packages to flash separately twice, once each because of flushing during command prompt. I then flashed the official Tmo 6.0 M9 rom that was debloated and used AROMA installer. I had to actually flash it twice after I noticed google now on tap did not work. I flashed once with NOTHING other than the Tmobile account app optionally installed. Then I did a dirty flash with the same rom on top of what I was already running. After crossing my fingers and hoping for the best I actually have a 100% flawless experience. I am not sure if I'm just lucky or if there was a reason behind my dumb luck. I wish I could give more information to be helpful but currently I'm not running into any issues with WiFi tethering or ANY other problem right now. As a matter of fact I'm getting two days off the charger with NO effort to be conservative. It should be pointed out I have as clean of a clean install as I could possibly. I loathe bloat and went through the annoying steps to rebuild from scratch using playstore and LOTS of data. If there are any more questions I could possibly answer just ring my bell.
Click to expand...
Click to collapse
Man I have spent so many hours on this, insanity. HTC and/or tmob really have there head up you know where.
Found a fix for now. Again I am on t-mobile, I am paying for hotspot access. Running marshmallow (6.0) took my updates via OTA. As a last ditch effort I installed PDANet which includes FoxFi. I had a license for this with my previous phone (htc Evo-rooted SOS rom) Never used Foxfi since my htc evo was rooted and I could just turn on hotspot no problem. Well go figure folks, turned on foxfi within PDAnet 4.18 and BOOM hot spot works with the screen off! Full speed no problems. Remember, you must be rooted. If you are running viper, it installs root for you. Best money I ever spent on a app!
I am in contact with another tmobile user on the forums. He is running marshmallow 6 as well. His hotspot works with this rom. BUT he installed his updates via fastboot. So based on all the info its either he has an app running wakelock, which would explain why his hotspot works with his screen off OR taking the updates via OTA is the cause. This is still a mystery to me.
Based on what dark just posted, and the user I am talking with, OTA might be the issue and/or t-mobile hacking the install to make data shut off with the screen. pda & foxfi cost 7.99, well worth the chance.
Also thought it was funny, but if I connect my usb cable and turn on pdanet (remember to hit just connect as charger when connecting your phone to laptop) I can connect to pdanet and tether but my speed is horrible! Which isn't the case with FoxFi (which lives inside of pda app) But if I exit PDAnet and then connect my phone and instead of picking usb charge, I pick tether, I get FULL SPEED. Obviously, t-mob or htc have programmed the phones like this on purpose.
If the above works, let the rest of us know!