Related
I've got an annoying problem with my phone where the Wifi turns off when my phone is idle or asleep. This means my WhatsApp for Web disconnects and also my Moto Connect plays up too.
I've got the same problem at home, work and parents house so can't be an issue with all 3 networks. The keep wifi on during sleep option is set to Always before anyone mentions this to me.
Phone is running Lollipop 5.0 in the UK and is NOT rooted.
I noticed it doesn't happen when the phone is charging though.
Any ideas?
Right I've now tried changing the Sleep setting to Never but get the same problem.
Also tried connecting to the router via WPS but no luck.
Router is a Superhub 2. I've ruled out that it's the Superhub as I have a Samsung Galaxy S4 Mini that is running fine without a single drop out.
Definitely something Moto X related.
I've also tried on both the 2.4GHz and 5GHz bands with same results!
Try looking within the WiFi settings on the phone. Mine has this
. Added photo
Sent from my HTC One using XDA Free mobile app
Mine is identical to yours other than the fact that I don't have the wifi optimization option.
Right I've just cleared the cache as instructed by Motorola support.
Still have the same problem even after clearing cache.
Ok I can confirm that the issue goes away when in safe mode.
This is starting to piss me off as I don't have any way of checking if it's an app affecting my wifi disconnections!!!
I've finally found and fixed the problem myself!!
I decided to turn my bluetooth on (even though it wasn't connected to any bluetooth devices). This seems to stop the phone from causing the wifi to go to sleep!
It seems like it's a bug in the Moto X Lollipop firmware. How do I report bugs to Motorola??
It's funny how most say it's apps that cause strange behaviour but for me it's been the actual Android firmware each time I've ever had an issue!
I hope it gets fixed soon.
Wutang200 said:
I've finally found and fixed the problem myself!!
I decided to turn my bluetooth on (even though it wasn't connected to any bluetooth devices). This seems to stop the phone from causing the wifi to go to sleep!
It seems like it's a bug in the Moto X Lollipop firmware. How do I report bugs to Motorola??
It's funny how most say it's apps that cause strange behaviour but for me it's been the actual Android firmware each time I've ever had an issue!
I hope it gets fixed soon.
Click to expand...
Click to collapse
It's a known bug of 5.0, and already fixed for 5.1. Source, at the "Bug fixes section".
Great that you found a workarround.
Cheers!
Manuel.
Hey glad to know it's a well known bug. The work around still doesn't work. It still keeps disconnecting all the time! Driving me mad!! If the 5.1 update doesn't fix it for me, I'll need to try and get a refund and go for something else. Shame as I really like the Moto X but I can't live with an issue as stupid as this!
I'm not sure Motorola are aware of this issue at all. See their comment below from one of their support staff I'm speaking to now:
Santhosh: We have not received any reports regarding Wi-FI issue after the Android Lollipop update but please give me a moment I will provide the solution for this issue.
His solution for the issue was to get me to do a factory reset lol. I already did this when I first got updated to Lollipop!!
Going to try doing another one now to see if it actually makes any difference. Then will install a few apps at a time or something.
I am connected to WiFi just about all of time, and I have never experienced this.
Right I've done a factory reset and started completely afresh with none of my data or apps restored. WiFi has been solid; I've not had a single drop out!
I'm going to install just a couple of apps at a time and keep an eye out if the issue comes back until I find the culprit.
Hi
My phone was perfect (until now) with the WIFI since november 2014 even after I upgraded it to 5.0
But today, it suddenly starts with this problem by itself. so I restored it to factory defaults with no luck, I installed a new firmware, and still has the bug.
So, why it shows up until now by itself without any mod, app or update?
Sorry for my English.
Today I upgraded it to 5.1 and the issue persists
I had to back to stock 4.4.4. and now my wifi has been fixed so far, working good without interruption until now.
I hope this has fix the problem from sourse, and I'll wait a few days to upgrade it again.
EDIT: Has been a month since my downgrade to 4.4.4. and my WIFI still rocks.
Just want to say that I'm having the same issue since the update to 5.1. Wifi is set to be always on during sleep, but I regularly wake up my phone only to find it connected to 4G, and switching to wifi a few seconds after waking up.
I'm on a locked bootloader (unrooted of course). I did a full reset after the update...
I'm sorry to say that I've seen more little glitches since 5.1 than anything I noticed on 5.0.
EDIT: another issue I'm having is the stock mail client not syncing saying that there is no network connection. My exchange account (push) works fine however...
Just to say the issue has started for me too since the update to 5.1.
I've done 2 factory resets but no luck trying to fix this very annoying problem.
Motorola have asked me to send my phone in for repair so I'll try that and see what happens.
I have a d5803 - relocked bootloader rooted and running a 5.1.1 rom. T-Mobile. Was working totally fine. Decided to try the 6.0 tft beta from the general section. I originally had the .2099 version but the OTA I'm at the latest.
It was great, but then I noticed sometimes my signal strength bar would have an exclamation point and my data wouldn't work. However, it still said LTE. A super quick toggle of airplane mode would revive it, and it would work again. I am a limo driver so I drive around, and it was kinda random. It would be fine in many areas for quite a while, but then would go inactive.
I figured it was a bug in the beta version, so I went back to a 5.1.1 rom. But I then noticed it still happened. I think it only happened once because I ended up trying to clear all data and completely fresh wipe to do the 6.0 version again. It still happens. I believe it tends to happen when I'm moving and it has to switch towers. Also, when I'm on a phone call, it is supposed to go to H/H+, which it does, but there is NO data connection. A phone call anytime will kill the internet.
Any ideas? I really like this 6.0 version but I might have to go back a stock tft file to see if the issue is still there. It all started when I decided to flashtool the 6.0 version.
Thanks
So after updating to 7.0 there are a couple of things I notice, firstly Chinese stuff like numbers on the dialer, music app, video app, and so forth still persist. The remote app wasn't there after the update so I manually downloaded it, now it is not connecting to devices. Battery is sometimes good, sometimes bad but this is because factory reset didn't work properly after unlocking the bootloader and after flashing the update. So if anyone has any help, and experience let's help each other
I got official 7.0 via OTA and I am really disappointed because battery is really wasted too fast. Google launcher is not working anymore...is closed after few minutes. Bluetooth is sound very bad on my media nav in car, before had no problem. I am thinking to downgrade to 6...
My VIE-AL10 by Tapatalk
My saved Bluetooth pairings keep disappearing in the Bluetooth settings since updating to Nougat, I think it's happening upon rebooting. It's annoying to have to keep pairing with my devices, especially the hands free link in the car! T719 on the German 7.0 firmware I believe, since that was the first to be released for the T719. Stock unrooted. Anyone else seeing this issue?
YrrchSebor said:
My saved Bluetooth pairings keep disappearing in the Bluetooth settings since updating to Nougat, I think it's happening upon rebooting. It's annoying to have to keep pairing with my devices, especially the hands free link in the car! T719 on the German 7.0 firmware I believe, since that was the first to be released for the T719. Stock unrooted. Anyone else seeing this issue?
Click to expand...
Click to collapse
Didn't happen to me but just so we know, after installing the nougat did you do a reset or something, like a clean install.
zeon22 said:
Didn't happen to me but just so we know, after installing the nougat did you do a reset or something, like a clean install.
Click to expand...
Click to collapse
Ah yes I did, I had to factory reset/wipe data because it wouldn't boot up after a dirty install. So I did start fresh, and everything else seems fine.
YrrchSebor said:
Ah yes I did, I had to factory reset/wipe data because it wouldn't boot up after a dirty install. So I did start fresh, and everything else seems fine.
Click to expand...
Click to collapse
Hmm so that's fine then. On top of that you are stock and unrooted
You can try 2 things
-In settings backup & reset- Do network settings reset This will as name suggests clear your wifi/ mobile data/bluetooth settings and passwords etc.
- Check if you have disabled any app which may be the cause or any app which may be causing this.
zeon22 said:
Hmm so that's fine then. On top of that you are stock and unrooted
You can try 2 things
-In settings backup & reset- Do network settings reset This will as name suggests clear your wifi/ mobile data/bluetooth settings and passwords etc.
- Check if you have disabled any app which may be the cause or any app which may be causing this.
Click to expand...
Click to collapse
Thanks for the ideas. No luck so far tho. I reset network settings, then paired with a Bluetooth speaker, rebooted, and sure enough the pairing is gone. I haven't disabled anything at all, for once I'm just running pure untouched stock unrooted lmao. I guess it could be a bug in this particular build? I have a T719. I'll look and see if it could be some app causing it, but I don't have too many apps, and definitely nothing too crazy lol.
YrrchSebor said:
Thanks for the ideas. No luck so far tho. I reset network settings, then paired with a Bluetooth speaker, rebooted, and sure enough the pairing is gone. I haven't disabled anything at all, for once I'm just running pure untouched stock unrooted lmao. I guess it could be a bug in this particular build? I have a T719. I'll look and see if it could be some app causing it, but I don't have too many apps, and definitely nothing too crazy lol.
Click to expand...
Click to collapse
You can check with other 719 users. Is this happening with wifi/5g wifi too btw?
Edit- Also found something, go to apps and select google backup transport and clear its cache and data the reboot. Might as well give this try as well
Not sure about wifi, haven't used it at all because my LTE is better than my home wifi. And I don't see that backup transport app here. Anyway, thanks for the ideas. Hopefully some other T719 owners will chime in.... I'm just not sure how many others there are. I do see a second Nougat build has been posted for my device, for United Arab Emirates, so maybe I'll install that one and see.
Same problem
Hi!
I have the same problem on my SM-T719.
Even after the second update just a month ago.
Sended it in to MOBYLIFE and they said that everything is fine and that it's my problem.
Even though I send them video proof of the opposite.
Sad...
I've been using OxygenOS 8.0.1 since it came out and I'm getting sick of the Bluetooth, dual sim, notification, and battery issues. I'm looking to switch to a stable ROM. My priorities are stability, good battery life, dual sim operation, and reduced Bluetooth issues.
My thinking was LineageOS due to my previous positive experience with CM or Nitrogen. Also Any good suggestions out there for Android 8.1?
First of all there is no stock 8.0.1 rom.
It's 5.0.1 based on Android 8.0
Secondly, me and many more users have no issues at all. So, there is no generic problem with stability with this rom. Did you perform a factory reset after you have upgraded to Oreo?
If not, then probably this is your main problem.
Unleashed by my rooted OP3T on 8.0
Oxygen OS is a very stable ROM.
One thing I have noticed that Nougat version 4.5.1 was the best considering fingerprint performance and battery back up.
Oreo 5.0.1 does not has fast fingerprint authentication as compared to it OOS 4.5.1
Sometimes I think I should switch to 4.5.1 for the best performance with best battery back up.
RASTAVIPER said:
First of all there is no stock 8.0.1 rom.
It's 5.0.1 based on Android 8.0
Secondly, me and many more users have no issues at all. So, there is no generic problem with stability with this rom. Did you perform a factory reset after you have upgraded to Oreo?
If not, then probably this is your main problem.
Unleashed by my rooted OP3T on 8.0
Click to expand...
Click to collapse
Adding to the above, there is no "perfect" or the most "stable" ROM. It all depends on your usage. All of the ROMS are thoroughly tested, and not built on unstable Device Sources like Samsung Devices. They're all stable, with no issues unless you use Xposed.
Also, I'm currently on OOS OB26 8.0, the most recent OB. Not having any issues. Maybe the problem is on your end?
ddrum2000 said:
I'm getting sick of the Bluetooth, dual sim, notification, and battery issues. I'm looking to switch to a stable ROM. My priorities are stability, good battery life, dual sim operation, and reduced Bluetooth issues.
Click to expand...
Click to collapse
I haven't had any of those issues, either. What kind of Bluetooth problems are you having? There was a known issue with this device not being compatible with BT on car stereo systems for certain makes (BWM, Volkswagon, and I think a few others), and not sure if those were fixed on OOS 5.0.1 or not. But aside from those particular car brands (not one I own) I've found BT to work really well on a variety of Bluetooth devices (earbuds/headsets, speakers, a number of car systems including rental cars).
Battery life is most dependent on network reception and individual usage patters. Don't expect that to change drastically from flashing a new ROM. Maybe some incremental improvement with a certain ROM and kernel tweaking. But again, nothing drastic.
redpoint73 said:
I haven't had any of those issues, either. What kind of Bluetooth problems are you having? There was a known issue with this device not being compatible with BT on car stereo systems for certain makes (BWM, Volkswagon, and I think a few others), and not sure if those were fixed on OOS 5.0.1 or not. But aside from those particular car brands (not one I own) I've found BT to work really well on a variety of Bluetooth devices (earbuds/headsets, speakers, a number of car systems including rental cars).
Battery life is most dependent on network reception and individual usage patters. Don't expect that to change drastically from flashing a new ROM. Maybe some incremental improvement with a certain ROM and kernel tweaking. But again, nothing drastic.
Click to expand...
Click to collapse
Thanks for all of the thoughts everyone. Let me describe the issues a little more.
1 - You are correct I am running OOS 5.0.1 with Magisk 16.4, stock kernal
2 - Bluetooth, when i connect to my BT home speaker (a BEDDI) and I play anything on TuneIn radio, the audio cuts out after 5-10 sec. I've found a workaround by pressing the play button on the radio itself but unfortunately some times this launches my previous app using audio which is never TuneIn. This was never a problem prior to Android 8
3 - Notifications and battery are linked I think. I don't receive notifications on a number different apps as I think they being put to sleep in the background. Slack is particularly problematic. I do have "advanced battery optimization" turned on but I have selected to "not optimize" the apps that I want notifications from. Notifications still do not show up.
3A - To partially mitigate this I tried turning off advanced optimization but the battery life tanks as a result
4 - Last summer I used the dual SIM functionality flawlessly while abroad (pre- android 8). In Jan I tried it again with OOS 5.0.1 and it made my entire phone sluggish, data didn't work great, there were lots of FCs etc.
I did not do a factory reset when I upgraded to OOS 8.0.1 which some people indicated could be the cause of the issues. I don't have a problem doing a factory reset but could you suggest a way to restore all of my apps and their settings after the reset since I don't want to have to spend hours setting up my phone again.
ddrum2000 said:
I don't have a problem doing a factory reset but could you suggest a way to restore all of my apps and their settings after the reset since I don't want to have to spend hours setting up my phone again.
Click to expand...
Click to collapse
Since you already have Magisk, try Titanium Backup Pro. It costs only a few $ on the Play Store, and it's definitely worth it. Or if you don't mind a slower restore and backup of app data, try the free version.
ddrum2000 said:
2 - Bluetooth, when i connect to my BT home speaker (a BEDDI) and I play anything on TuneIn radio, the audio cuts out after 5-10 sec. I've found a workaround by pressing the play button on the radio itself but unfortunately some times this launches my previous app using audio which is never TuneIn. This was never a problem prior to Android 8
Click to expand...
Click to collapse
Any issue with other music apps? Any other Bluetooth devices that you can test this on? Might be a problem with the app not being updated for Android 8 (pretty common). Or just a glitch with the particular BT device (also common).
ddrum2000 said:
Thanks for all of the thoughts everyone. Let me describe the issues a little more.
1 - You are correct I am running OOS 5.0.1 with Magisk 16.4, stock kernal
2 - Bluetooth, when i connect to my BT home speaker (a BEDDI) and I play anything on TuneIn radio, the audio cuts out after 5-10 sec. I've found a workaround by pressing the play button on the radio itself but unfortunately some times this launches my previous app using audio which is never TuneIn. This was never a problem prior to Android 8
3 - Notifications and battery are linked I think. I don't receive notifications on a number different apps as I think they being put to sleep in the background. Slack is particularly problematic. I do have "advanced battery optimization" turned on but I have selected to "not optimize" the apps that I want notifications from. Notifications still do not show up.
3A - To partially mitigate this I tried turning off advanced optimization but the battery life tanks as a result
4 - Last summer I used the dual SIM functionality flawlessly while abroad (pre- android 8). In Jan I tried it again with OOS 5.0.1 and it made my entire phone sluggish, data didn't work great, there were lots of FCs etc.
I did not do a factory reset when I upgraded to OOS 8.0.1 which some people indicated could be the cause of the issues. I don't have a problem doing a factory reset but could you suggest a way to restore all of my apps and their settings after the reset since I don't want to have to spend hours setting up my phone again.
Click to expand...
Click to collapse
Restoring all app settings after a factory reset can easily recreate the same problem.
Definitely wouldn't recommend that.
Unleashed by my rooted OP3T on 8.0
thes3usa said:
Since you already have Magisk, try Titanium Backup Pro. It costs only a few $ on the Play Store, and it's definitely worth it. Or if you don't mind a slower restore and backup of app data, try the free version.
Click to expand...
Click to collapse
I'm familiar with titanium backup. I guess a question I have is exactly what setting would you use to backup specifically apps, their data, and system settings so that I get the positive benefits of the factory reset without backing up and restoring those " problems"
redpoint73 said:
Any issue with other music apps? Any other Bluetooth devices that you can test this on? Might be a problem with the app not being updated for Android 8 (pretty common). Or just a glitch with the particular BT device (also common).
Click to expand...
Click to collapse
No the problem only seems to be TuneIn (which is a pretty common) with my Bluetooth speaker. Play music, pocket casts, and chrome seem to fine with the same speaker, BT headphones, and my BT car adapter.
redpoint73 said:
Any issue with other music apps? Any other Bluetooth devices that you can test this on? Might be a problem with the app not being updated for Android 8 (pretty common). Or just a glitch with the particular BT device (also common).
Click to expand...
Click to collapse
Sorry if this double posts...
This only seems to happen with Tunein and by BT speaker. It does not seem to happen with play music, pocket casts, or chrome with the same speaker, my BT headphones, or BT car adapter.
ddrum2000 said:
No the problem only seems to be TuneIn (which is a pretty common) with my Bluetooth speaker. Play music, pocket casts, and chrome seem to fine with the same speaker, BT headphones, and my BT car adapter.
Click to expand...
Click to collapse
If it is a common problem with TuneIn, then I would tend to think it's the app developer's problem (possibly not properly updating for Android 8). Although it is a bit odd that it only has this bug on a certain device (the speaker). So a lot of layers of complexity here. But it seems more a problem with the app and the device (speaker). Trying another ROM may indeed be a way of eliminating the OS as the cause (or at least narrowing it down).
redpoint73 said:
If it is a common problem with TuneIn, then I would tend to think it's the app developer's problem (possibly not properly updating for Android 8). Although it is a bit odd that it only has this bug on a certain device (the speaker). So a lot of layers of complexity here. But it seems more a problem with the app and the device (speaker). Trying another ROM may indeed be a way of eliminating the OS as the cause (or at least narrowing it down).
Click to expand...
Click to collapse
Thanks for the thoughts. Do you have any good methods of restoring data/settings post factory reset that won't restore the "dirty flash"?
ddrum2000 said:
Do you have any good methods of restoring data/settings post factory reset that won't restore the "dirty flash"?
Click to expand...
Click to collapse
I backup and restore my app data using Titanium Backup, like another user suggested. I've been using it as long as I've been flashing ROMs on Android devices, and it works wonderfully.
redpoint73 said:
I backup and restore my app data using Titanium Backup, like another user suggested. I've been using it as long as I've been flashing ROMs on Android devices, and it works wonderfully.
Click to expand...
Click to collapse
Are there any particular settings you like for Titanium Backup that minimize "restoring a dirty flash" ?
ddrum2000 said:
Are there any particular settings you like for Titanium Backup that minimize "restoring a dirty flash" ?
Click to expand...
Click to collapse
Your terminology is a little confusing. A "dirty flash" means you are migrating all user data. You do so by not wiping data, and flashing a ROM. If you are doing a factory reset, you are by definition wiping all user data; which is the entire point of a "factory reset".
By restoring app data after a factory reset, you might be re-introducing data that is causing the bugs (if that is in fact the cause).
One suggestion would be to backup your app data with Titanium. Wipe user data, cache and Dalvik (factory reset). Then test the ROM with the phone "clean" and only install the apps you need to test (TuneIn for the Bluetooth glitch, Slack for the notification problems). After testing for those bugs for a while, then restore app data as needed using Titanium. If the problems only arise after restoring app data with Titanium, you may need to start over (wipe again) and be selective about what data you restore.
The best case scenario, is that the bugs are improved after the factor reset and stay that way after restoring app data with TB.
Another possibility is that the bugs occur even with a "clean" setup (only install the apps which exhibit the problem). In which case, the problem is likely the app itself, or the ROM (as you initially suspected), or a combination of the two. In which case, you are back to trying a new ROM.
But basically, you need to do some testing to figure out what the culprit is, or at least narrow the possibilities.
redpoint73 said:
Your terminology is a little confusing. A "dirty flash" means you are migrating all user data. You do so by not wiping data, and flashing a ROM. If you are doing a factory reset, you are by definition wiping all user data; which is the entire point of a "factory reset".
By restoring app data after a factory reset, you might be re-introducing data that is causing the bugs (if that is in fact the cause).
One suggestion would be to backup your app data with Titanium. Wipe user data, cache and Dalvik (factory reset). Then test the ROM with the phone "clean" and only install the apps you need to test (TuneIn for the Bluetooth glitch, Slack for the notification problems). After testing for those bugs for a while, then restore app data as needed using Titanium. If the problems only arise after restoring app data with Titanium, you may need to start over (wipe again) and be selective about what data you restore.
The best case scenario, is that the bugs are improved after the factor reset and stay that way after restoring app data with TB.
Another possibility is that the bugs occur even with a "clean" setup (only install the apps which exhibit the problem). In which case, the problem is likely the app itself, or the ROM (as you initially suspected), or a combination of the two. In which case, you are back to trying a new ROM.
But basically, you need to do some testing to figure out what the culprit is, or at least narrow the possibilities.
Click to expand...
Click to collapse
Thanks for walking through your reasoning. It reinforced what I already suspected. Now I just have to experiment with it.