Related
Disclaimer: I've searched the forums day after day and have found nothing that helps me in any way.
Hey guys, I'll get right down to this:
I've got a Moto X VZW MM 32GB, initially shipped with 4.2.2 and running 4.4 as soon as I got it activated.
Everything on the Moto X works great, fluid graphics, fast app opening, battery (for the most part). But I've got a bone to pick with bluetooth, as well as Android OS.
First off, the bluetooth bugs, or what I'd like to call, The Blues.
Problems
- I have Pioneer Premier FH-P800BT, running great for the past 6 months or so. I originally had a Galaxy Nexus from VZW, with CM10.2 on it and bluetooth worked flawlessly, save for an obvious quality issue with phone calls/echo cancellation. A2DP and HSP/HFP would connect immediately as soon as the car came on. With my Moto X, HFP/HSP connects fine on powerup of the radio, but A2DP will not, and my phone shows "Connecting..." in bluetooth settings. When I first pair the phone (or re-pair), all profiles connect and audio works without a hitch. But every time after, it doesn't work that way. I can get around the issue by putting my radio in pair mode and turning on bluetooth, which essentially re-pairs the devices together, and that works. I think the biggest thing is that my radio connects HSP/HFP first, and then A2DP, and the phone is expecting both at the same time, and this causes the glitch I'm having. I haven't FR'd yet because this could be something that a FR won't fix (aka software issue that wasn't fixed by Moto).
- On all bluetooth devices with A2DP, sometimes the quality is great, sometimes it does what I like to call a "stucho" aka a stutter/echo. The best way I can explain it is if you've ever heard a record skip back and keep playing the same part, multiply that by like 100x. Or better example, for you Galaxy Nexus users (other phones too, if they do it) when your phone would freeze from being overloaded, and it ultimately crashed (non responsive to anything, screen won't come on, or maybe stuck on) and the audio get's hung. The sound does that on the Moto X, but it continues playing the track without pausing/skipping. It's extremely annoying, and mostly occurs when surfaceflinger is active (I'd assume that's what it is), as it's when anything animation-wise caused by user input occurs. I've also had the audio deteriorate in the same manner, but after it does the weird stucho effect, the audio slows down a bit, noticeable, like, listening to "We Found Love" by Rihanna sounded like a man singing it, and then it will speed up and go too fast after about a minute, and then resume normal playback. Despite completely pausing on my Galaxy Nexus, that phone never did have the audio issues this Moto X does, and it occurs on every A2DP device I've tried (BMW iDrive, Hyundai Sonata factory radio, Philips SBT series, my Pioneer headunit).
Second issue I'm having: Android OS
- I've tried ART and running Dalvik as the runtime, and on both, after weeks of running them, I notice that throughout the day, 3-4% battery drain per hour, with nothing in recent apps, wifi on, and all VZW software except for backup assistant disabled. I'm not complaining because I tend to make it to the end of the day with 2 1/2 hours SOT and and about 10% left on battery, but I'm curious as to why it's not making it any further. I don't have much installed. Dropbox, Facebook, Exchange account, Wallet, and other programs that don't run in the background (OS Monitor, Dots (game), etc). While my SOT can show 2 1/2 hours, it's only taking like 35% of the battery while Android OS shows like 20% or more, and shows CPU time around 1:45 hrs.
Any insight on either of these issues would be appreciated. I love the phone, everything else is perfect, but these 2 things are kinda irking me because I know this isn't the way the phone should be operating, moreso with the bluetooth bug.
Bump
My Bluetooth works fine on my old Motorola visor mount device...music and stuff goes through my radio.
As far as battery goes....go to the general section and read the "how's your battery life " thread. Every bit of troubleshooting and issues is already there.
Good luck!
Sent from my Moto X cellular telephone...
Glad to hear that yours is working great, mine usually does. I'll also add that call quality is top notch over bluetooth, much cleaner than on my Gnex. It's just A2DP sometimes will do the above mentioned, and it's so annoying. Using the headphone jack it is fine, it's specific to bluetooth.
As for battery tips, I've tried a good portion, short of rooting the device and greenifying it. I ran my Gnex forever, and I kid you not, swapped/flashed at least 60 roms, so I know what I'm doing in terms of de-bloat and rooting and such, but if not for these bugs, I'd be happy with the phone itself.
Thanks for the tips though I'll look, but in the mean time, anybody else ever noticed what I'm talking about?
kj2112 said:
My Bluetooth works fine on my old Motorola visor mount device...music and stuff goes through my radio.
As far as battery goes....go to the general section and read the "how's your battery life " thread. Every bit of troubleshooting and issues is already there.
Good luck!
Sent from my Moto X cellular telephone...
Click to expand...
Click to collapse
I don't have stutter/echo problems but after taking a call on it and trying to go back to music the app acts like it is playing but no music is heard. I have to cycle BT on/off or cycle the power on the adapter. This is on a car adapter, the Kinivo BTC450. The adapter was flawless with an iPhone 5s and pretty good with a nexus 5. I am hoping it is 4.4 bugs and 4.4.2 will clear it up. It is supposed to launch Feb. 1 in Europe with 4.4.2 so hopefully we'll all see an update. I'm tinkering with the idea of going back to 4.2.2 to see if it is any better.
Sent from my XT1053 using Tapatalk
Well, I've solved 2 of the 3 problems I was having. Android OS no longer takes over my battery, and thankfully, more people today had posted that Snapchat was a battery hog on 4.4 (or on any OS version for that matter). And I wasn't just hallucinating, considering at 50% battery, SOT was ~ 1 hr while Android OS showed like almost 2 hours of being active, and percentages were like 33-35% for SOT, and 20-25% for Android OS. So I think now that 33mins of SOT at 90% battery and Android OS only showing 5% usage, issue's resolved
Bluetooth stuttering was seemingly with all audio services on my phone, but after I tinkered, I found anything that passed through the built-in EQ was stuttering when surfaceflinger was active. And oddly enough, only with bluetooth, and not even all the time. So in short, disabling the EQ on the phone seems to have fixed the weird jerking/echo/stucho sound period. I'll test a bit further, but so far that seems to be good.
Did a bit more testing in regards to A2DP issues, and found that in a newer Sonata (2013 Limited) the factory bluetooth links to A2DP and HSP/HFP within 30 seconds and both work properly. In my car though (Sentra) with an aftermarket Pioneer headunit (model number in the 1st post) the headunit must connect in a different matter, as HSP/HFP always connects immediately but A2DP tries to connect and it fails out. I have to re-pair the phone to the headunit each time to get both to pair properly. I'll test more with this but for now, this is still a bug, hopefully 4.4.2 will fix these issues.
So disabling the audio effects in the audio menu fixed the stuttering for you? Going to give that a sit tomorrow as well as uninstalling snap chat
Sent from my XT1058 using Tapatalk
I can confirm that for the past 2 days, with the Audio Effects/EQ disabled, I have no stutter with audio over bluetooth, it plays much smoother now. Also, uninstalling Snapchat has 100% resolved my Android OS battery drain. I was only getting an hour and a half of SOT with 30% battery left before, and now I successfully hit 50% battery with right at 2 hours SOT, so it's definitely made a huge difference. That's with dropbox, exchange account, facebook, and a few other random apps running. Worth a shot to see if it really does it for you, but YMMV
murso74 said:
So disabling the audio effects in the audio menu fixed the stuttering for you? Going to give that a sit tomorrow as well as uninstalling snap chat
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
balleron24z said:
Did a bit more testing in regards to A2DP issues, and found that in a newer Sonata (2013 Limited) the factory bluetooth links to A2DP and HSP/HFP within 30 seconds and both work properly. In my car though (Sentra) with an aftermarket Pioneer headunit (model number in the 1st post) the headunit must connect in a different matter, as HSP/HFP always connects immediately but A2DP tries to connect and it fails out. I have to re-pair the phone to the headunit each time to get both to pair properly. I'll test more with this but for now, this is still a bug, hopefully 4.4.2 will fix these issues.
Click to expand...
Click to collapse
Any resolution on this? I have the exact same problem with my Pioneer head unit. So annoying having to repair every time!
Only problem I'm having with Bluetooth in my car is that incoming phone calls break my audio connection. Instead of resuming, the audio ceases and i have to unpair and repair to get my audio back.
balleron24z said:
A2DP and HSP/HFP would connect immediately as soon as the car came on. With my Moto X, HFP/HSP connects fine on powerup of the radio, but A2DP will not, and my phone shows "Connecting..." in bluetooth settings. When I first pair the phone (or re-pair), all profiles connect and audio works without a hitch. But every time after, it doesn't work that way. I can get around the issue by putting my radio in pair mode and turning on bluetooth, which essentially re-pairs the devices together, and that works. I think the biggest thing is that my radio connects HSP/HFP first, and then A2DP, and the phone is expecting both at the same time, and this causes the glitch I'm having. I haven't FR'd yet because this could be something that a FR won't fix (aka software issue that wasn't fixed by Moto).
Click to expand...
Click to collapse
I am experiencing a similar bug.
Subaru Outback 2013 with Navigation (Fujitsu-10). I can pair the device just fine, but the automatic connection doesn't work at all. It will just say "Automatic connection has failed" on the navigation screen, and no indication on the phone.
That is what happens when I turn on the car when the phone has Bluetooth already enabled.
If I turn bluetooth off and back on again, it connects.
If I go into the bluetooth menu and tap CAR MULTIMEDIA, it connects.
The only thing that doesn't work is the *automatic* connection.
Like you, I previously had a Samsung Galaxy Nexus. I was running CM 10.2 and CM11 on it, both worked perfectly well with Bluetooth in the car.
Se7enLC said:
I am experiencing a similar bug.
Subaru Outback 2013 with Navigation (Fujitsu-10). I can pair the device just fine, but the automatic connection doesn't work at all. It will just say "Automatic connection has failed" on the navigation screen, and no indication on the phone.
That is what happens when I turn on the car when the phone has Bluetooth already enabled.
If I turn bluetooth off and back on again, it connects.
If I go into the bluetooth menu and tap CAR MULTIMEDIA, it connects.
The only thing that doesn't work is the *automatic* connection.
Like you, I previously had a Samsung Galaxy Nexus. I was running CM 10.2 and CM11 on it, both worked perfectly well with Bluetooth in the car.
Click to expand...
Click to collapse
If you search for "kitkat bluetooth issues" you will find multiple issues reported about different phones. In 4.4 Google went with a new BlueTooth implementation that broke compatibility with some of the devices. My Moto X DE (GSM) is at 4.2.2 and is perfectly compatible with my built-in car entertainment system, so I am probably never upgrading since downgrade from 4.4.2 is not possible.
JoeSchmoe007 said:
If you search for "kitkat bluetooth issues" you will find multiple issues reported about different phones. In 4.4 Google went with a new BlueTooth implementation that broke compatibility with some of the devices.
Click to expand...
Click to collapse
It was actually 4.2 where Android switched from BlueZ to BlueDroid. In 4.3 and 4.4 there were significant developments to "finish" that implementation. On my Nexus, 4.2 was worthless, but 4.3 and 4.4 worked great. It's certainly possible that Motorola botched something with their upgrade to 4.4 - or maybe Motorola had their own Bluetooth stack separate from AOSP.
My Moto X DE (GSM) is at 4.2.2 and is perfectly compatible with my built-in car entertainment system, so I am probably never upgrading since downgrade from 4.4.2 is not possible.
Click to expand...
Click to collapse
Downgrade on a Developer Edition is certainly possible, that's kind of the whole point of a developer edition!
Se7enLC said:
...
Downgrade on a Developer Edition is certainly possible, that's kind of the whole point of a developer edition!
Click to expand...
Click to collapse
I don't think this is correct. See this post: http://forum.xda-developers.com/moto-x/moto-x-qa/flashed-4-4-2-partition-table-gpt-bin-t2657468/post50555443 GPT flash is non-reversible and can prevent downgrade.
Here is another quote from now deleted thread:
This is a simple chart what can and can't not be downgraded, Thanks to Dray_jr :thumbup:
the only OTA that can downgrade is 4.4 to 4.2.2 Post Cam
here is what we know right now that might make more sense
4.4 to 4.2.2 Pre Cam will Brick
4.2.2 Post Cam to 4.2.2 Pre Cam will Brick.
4.4.2 to to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
Click to expand...
Click to collapse
If you have tested and working instructions on how to downgrade from 4.4.2 to 4.2.2 on 1053 I really would like know them.
JoeSchmoe007 said:
I don't think this is correct. See this post: http://forum.xda-developers.com/moto-x/moto-x-qa/flashed-4-4-2-partition-table-gpt-bin-t2657468/post50555443 GPT flash is non-reversible and can prevent downgrade.
Click to expand...
Click to collapse
Huh, that's news to me. Thanks for that link. This is what I get for thinking the Moto X would be just like a Nexus device.
To answer a few questions regarding this:
1: You most certainly CAN flash any ROM you wish to a DE Moto X, you just need to unlock the bootloader. When the BL is unlocked, it allows you to flash whatever you want. Look it up and do your homework, it's essentially a Nexus, without the AOSP out of the box.
2: The if 4.4 had so many bluetooth bugs, then why did my Gnex running AOSP 4.4 (the hacked together one that had driver bugs) work PERFECT, and I mean legit PERFECT with bluetooth on all devices I used? The point is moot with the bluetooth stack being bugged. Obviously Google tested this on MANY of their internal devices before releasing to Nexus devices and the AOSP branch. Y'all have no logic if you believe otherwise. I DO, however, agree that it's possible that Moto is using a non-standard or non-AOSP bluetooth stack, or they have modified the bluetooth config to the point where it doesn't work.
4.4.2 for the Moto X didn't fix my problem, although it supposedly did fix some bluetooth bugs. I can still use the phone with a 2013 Hyundai Sonata Limited's bluetooth, and it pairs perfectly every time. This seems to be a hardware-specific issue, as I see people with older model Pioneer/Kenwood/etc. Bluetooth 2.0 headunits having issues, as well as with some hands-free BT units too. But on newer vehicles, some radios don't have the problem. I'm gonna file another ticket with Moto and see if I can provide proof to the problem.
Guys....aside from keeping your warranty, the DE is no different than any other moto x with an unlocked bootloader. I don't know why people keep saying its any more than an x that gets a warranty.
You cannot downgrade with any less risk of bricking than any other unlocked moto x.
I hope this rumor of the dev edition being special in this regard ends quickly...before there's a tonne of "I'm bricked" threads.
No moto x is a nexus. There is no downgrading the bootloader without heavy risk. The stories you've read here about downgrading bricks WILL happen to the dev edition just like the other unlocked moto's. Mark my words.... please.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 09:39 PM ---------- Previous post was at 09:37 PM ----------
Careful who's advice you follow here guys....unless you have money to burn.
And yes...totally agree with the above.....do your homework.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 09:42 PM ---------- Previous post was at 09:39 PM ----------
Se7enLC said:
Huh, that's news to me. Thanks for that link. This is what I get for thinking the Moto X would be just like a Nexus device.
Click to expand...
Click to collapse
No. Downgrading is a HUGE brick risk. Trust me.
Moto x's are nothing like a nexus when it comes to the bootloaders.
Dev edition is like the rest....but you keep warranty. That's all!
Sent from my Nexus 5 using Tapatalk
kj2112 said:
Guys....aside from keeping your warranty, the DE is no different than any other moto x with an unlocked bootloader. I don't know why people keep saying its any more than an x that gets a warranty.
Click to expand...
Click to collapse
Because on Verizon, it's the only one that has an unlockable bootloader. Unlocked bootloader USED to mean that you can run any code you want on it, and recover mistakes using fastboot. And unless I'm mistaken, it still means that. The GPT thing is concerning, but there's still nothing preventing executable code from being run, it's just the partition table that is different, and the old ROM images cannot be written to it.
You cannot downgrade with any less risk of bricking than any other unlocked moto x.
Click to expand...
Click to collapse
How is that the case, though? Does fastboot stop working? Can you not re-flash a 4.4.2 image once provided by motorola? Do recovery consoles not flash? Can they no longer write to flash? And the real question - is it just because the older android images and recovery consoles do not understand GPT, or is there something actively preventing it? I know I've painted myself into a corner the last time I switched a drive to GPT and had a hard time finding a LiveCD that could mount it, but that was years ago. I'm crossing my fingers that it's only a matter of time before parted finds its way into CWM and TWRP.
I hope this rumor of the dev edition being special in this regard ends quickly...before there's a tonne of "I'm bricked" threads.
Click to expand...
Click to collapse
Agreed. Personally, I'm disappointed with the Moto X in this regard. I'm glad to now be informed of this, and I hope others look into it themselves as well.
Se7enLC said:
Because on Verizon, it's the only one that has an unlockable bootloader. Unlocked bootloader USED to mean that you can run any code you want on it, and recover mistakes using fastboot. And unless I'm mistaken, it still means that. The GPT thing is concerning, but there's still nothing preventing executable code from being run, it's just the partition table that is different, and the old ROM images cannot be written to it.
How is that the case, though? Does fastboot stop working? Can you not re-flash a 4.4.2 image once provided by motorola? Do recovery consoles not flash? Can they no longer write to flash? And the real question - is it just because the older android images and recovery consoles do not understand GPT, or is there something actively preventing it? I know I've painted myself into a corner the last time I switched a drive to GPT and had a hard time finding a LiveCD that could mount it, but that was years ago. I'm crossing my fingers that it's only a matter of time before parted finds its way into CWM and TWRP.
Agreed. Personally, I'm disappointed with the Moto X in this regard. I'm glad to now be informed of this, and I hope others look into it themselves as well.
Click to expand...
Click to collapse
I can't speak for what dev edition means on other phones....but for the Moto x, Dev edition means you can unlock bootloader, same as many other models....though your warranty is still good......and once unlocked, its EXACTLY the same as any other unlocked Moto x as far as flashing rules and RISKS.
I don't claim to be an expert on precisely why and what causes a brick, but I've read more than enough on here lately to know that downgrading from 4.4.2 is playing with fire. LOL
Funny....I just went to flash a 4.2.2 rom on my Nexus 7 the other day and got an error about incompatible boot loader (I was on 4.4.2 at the time) and I remembered, crap...that's right! So I flashed the previous bootloader version....then the 4.2.2 rom. Done ...10 minutes and zero issues. LOL. Not sure why Motorola had to make things harder/different.
Sent from my Nexus 5 using Tapatalk
Back to the original topic - I took the upgrade to 4.4.2 last night:
- Disabled things like XPosed
- Re-flashed stock recovery (using fastboot)
- Applied update
- Re-flashed CWM recovery
- Re-applied root and xposed
I didn't do anything else, apart from app upgrades that happened to come in. When I got in my car this morning it immediately automatically connected. Could be a coincidence, or maybe that upgrade fixed the bug.
EDIT: I was in and out of the car probably half a dozen times today, works perfectly now, auto-connected every time!
I can't connect to the Wi-Fi at my work on my Nexus9 or my MotoX. I believe it is due to Android 5.0. I've seen a few articles about corporate Wi-Fi accounts having issues with lollipop.
Is there a fix on the way?
Does anyone else have this problem?
We just got a Moto X yesterday, and it upgraded itself to Lollipop just a few minutes ago. And, now it refuses to connect to our home wi-fi. The connection screen is stuck on "authenticating." It worked fine before the upgrade. Any suggestions for fixes would be greatly appreciated.
I have had this problem on the nexus 6. Haven't had a chance to try the moto x on lollipop yet at work. Seems to be related to having a space or dash in the network name. Here is the link to the google issue tracker about it in this post.
http://forum.xda-developers.com/showthread.php?p=56939561
Has anyone had any issues with tethering performance? The tethering works for me, but in my car I have a 2012 Nexus 7 mounted in the dash, and while commuting each day I play music and videos from Youtube. My last 4 phones, S3, Note 2, Moto X (2013), and One M8, have all worked as a hotspot just fine for the tablet, but I noticed with my Nexus 6, videos will buffer for 5-10 seconds every 5-10 seconds making them unwatchable.
Speed tests were also slow for the in-dash N7 (1-2 mbps), so I tried with my M8 tethered to the N6, and speed test results were better but it still cannot play video steadily. I have two N6's, and the one I was using was rooted and unencrypted, so I considered that maybe it was something to do with the unencrypted kernel, perhaps a bad driver, so I tested with my other N6 which is only rooted and it seemed to work better. I was able to stream video on every device except the N7, however it did perform better on speed tests when tethered to the encrypted kernel N6. The only device that I can get to stream Youtube when tethered to the decrypted N6 is the other N6.
TL, DR: My testing so far is kind of inconclusive, but I basically just wanted to see if anyone else was noticing anything similar and if you had any ideas. This is really a big deal to me, possibly a showstopper for me if I can't figure something out.
earthtodigi said:
Has anyone had any issues with tethering performance? The tethering works for me, but in my car I have a 2012 Nexus 7 mounted in the dash, and while commuting each day I play music and videos from Youtube. My last 4 phones, S3, Note 2, Moto X (2013), and One M8, have all worked as a hotspot just fine for the tablet, but I noticed with my Nexus 6, videos will buffer for 5-10 seconds every 5-10 seconds making them unwatchable.
Speed tests were also slow for the in-dash N7 (1-2 mbps), so I tried with my M8 tethered to the N6, and speed test results were better but it still cannot play video steadily. I have two N6's, and the one I was using was rooted and unencrypted, so I considered that maybe it was something to do with the unencrypted kernel, perhaps a bad driver, so I tested with my other N6 which is only rooted and it seemed to work better. I was able to stream video on every device except the N7, however it did perform better on speed tests when tethered to the encrypted kernel N6. The only device that I can get to stream Youtube when tethered to the decrypted N6 is the other N6.
TL, DR: My testing so far is kind of inconclusive, but I basically just wanted to see if anyone else was noticing anything similar and if you had any ideas. This is really a big deal to me, possibly a showstopper for me if I can't figure something out.
Click to expand...
Click to collapse
What is your license number? If you are watching videos while driving, I don't to be anywhere near you.
Yup...
I'm seeing insanely slow teathering speeds as well. On an LTE connection with my phone, data on the Nexus 6 is running real speedy like speedtest shows 54Mbps down, 20 up) but the connection on my Nexus 9 tethered to it is dragging butt at 3.22Mbps down and 3.39 up.
Anyone else got a horror story? I'm thinking there's some built in limiting going on here, which I like not at all. Bought my Nexus 6 from T-Mobile. Shouldn't make any difference with a Nexus device, but just in case something's changed, that may be important.
I did some more testing, and figured out that it seems to be related to the bluetooth being on, causing interference or something. Any device that I tether to my N6 seems to crawl if that device has its bluetooth turned on. This is apparently a known issue for the N7, but I have never encountered it before at all.
USB Tethering is fine w/bluetooth on
USB Tethering is fine w/bluetooth on. However, my wifi tehtering is only 0-1 mbps download with bt on.
Odd issue with my Droid Turbo. Google services and certain apps, including Reddit Sync, facebook and youtube, all lag/hang over wifi. Over LTE there is no lag.
I have a 6th gen (newest) Airport Extreme with firmware 7.7.3 (latest) and notice the same slow, laggy performance on the 2.4ghz and 5ghz network. Passowrd is a WPA2 Personal (AES).
I've seen reports so far on a lot of newer android devices (4.4.4 and lolipop) with slow wifi performance, not just the turbo. Curious if any of the other owners here have laggy wifi? Sometimes it will start to load and hang, hit refresh and it'll load 50% of the way, refresh it again and it will finally load.
I've tried a factory reset, clearing problematic apps cache, uninstalling and re-installing problematic apps, resetting router/modem, changed my phones wifi profile dhcp to 8.8.8.8/8.8.4.4, no change in the wireless performance.
Only thing I haven't tried is a new wireless channel on my router. But since both 2.4ghz and 5ghz display the same problem, I ruled that out.
Funny thing is a speedtest over wifi gives me my full 100 down. Once it loads it's fast, just takes 20-30 seconds of lag before loading.
Thanks all!
I started a thread on reddit about it. Other Droid Turbo owners are experiencing the same exact issues. Posting a link for reference.
http://www.reddit.com/r/droidturbo/comments/2wdb7c/slow_wifi_lag_with_google_services_and_certain/
jhmn7 said:
Odd issue with my Droid Turbo. Google services and certain apps, including Reddit Sync, facebook and youtube, all lag/hang over wifi. Over LTE there is no lag.
I have a 6th gen (newest) Airport Extreme with firmware 7.7.3 (latest) and notice the same slow, laggy performance on the 2.4ghz and 5ghz network. Passowrd is a WPA2 Personal (AES).
I've seen reports so far on a lot of newer android devices (4.4.4 and lolipop) with slow wifi performance, not just the turbo. Curious if any of the other owners here have laggy wifi? Sometimes it will start to load and hang, hit refresh and it'll load 50% of the way, refresh it again and it will finally load.
I've tried a factory reset, clearing problematic apps cache, uninstalling and re-installing problematic apps, resetting router/modem, changed my phones wifi profile dhcp to 8.8.8.8/8.8.4.4, no change in the wireless performance.
Only thing I haven't tried is a new wireless channel on my router. But since both 2.4ghz and 5ghz display the same problem, I ruled that out.
Funny thing is a speedtest over wifi gives me my full 100 down. Once it loads it's fast, just takes 20-30 seconds of lag before loading.
Thanks all!
I started a thread on reddit about it. Other Droid Turbo owners are experiencing the same exact issues. Posting a link for reference.
http://www.reddit.com/r/droidturbo/comments/2wdb7c/slow_wifi_lag_with_google_services_and_certain/
Click to expand...
Click to collapse
I've noticed the same thing. I've tried it from a netgear R8000 and a Asus rt-ac3200. Same exact thing. I notice it with chrome and google+ alot. Don't have a fix though
civiksi said:
I've noticed the same thing. I've tried it from a netgear R8000 and a Asus rt-ac3200. Same exact thing. I notice it with chrome and google+ alot. Don't have a fix though
Click to expand...
Click to collapse
Thanks for the reply. I was waiting to see if anyone else experienced these problems before I posted back.
At least for me, this slow and lag filled wifi experience is ruining the droid turbo. Fingers crossed issues are resolved with lolipop
jhmn7 said:
Thanks for the reply. I was waiting to see if anyone else experienced these problems before I posted back.
At least for me, this slow and lag filled wifi experience is ruining the droid turbo. Fingers crossed issues are resolved with lolipop
Click to expand...
Click to collapse
I chatted with moto last night about the laggy and poor ranged wifi and a couple other issues. I have a screen flicker when using google messenger and capacitive buttons stop working at times. They had me factory reset last night (which I really didn't want to do). They said if it doesn't help they will send me a new device.
I've had a weird half-load the page, stall, then finish loading thing going on for awhile (droid turbo).
Chrome, Firefox, Dolphin, all behave the same. Speed tests are fine, I've had zero wifi
connectivity problems other than the antenna is weak on these phones, IM/SMS works fine,
I seem to get the stalls in youtube but not netflix that I can tell but that's some pretty
iffy observation. The page loading behavior is steady.
I think that it loads fine on LTE, I can click wifi OFF when a page is stalled and it loads.
I can follow the same link and open in a different browser and it'll load right up if I leave it on LTE.
Something is up, I can't tell what but it's been there awhile now. It's really, really, really annoying.
Factory reset didn't fix it, and it did it with no apps installed.
If L don't pop up soon and fix this, bye bye Turbo, will miss your battery..
I'm getting a replacement device for the screen flicker. Let you know if it helps any of the page loading problems but I doubt it.
civiksi said:
I'm getting a replacement device for the screen flicker. Let you know if it helps any of the page loading problems but I doubt it.
Click to expand...
Click to collapse
Please do, I'd love an update once you get the new turbo!
jhmn7 said:
Please do, I'd love an update once you get the new turbo!
Click to expand...
Click to collapse
I'm not holding my breath but I bought this the day it came out. Unless the early ones had a problem I expect to see no difference. The lack of replies here either means no one has the problem or just lack of commenting.
I have the slow loading also. I did the factory reset but it seems as I put more apps on it's getting slow again and stalls at times. would a new device fix this?
jhmn7 said:
Please do, I'd love an update once you get the new turbo!
Click to expand...
Click to collapse
I got a new one today but didn't have a lot of time to play with it. It came late due to the snow then I had to go snow blow. Google+ is definitely way better but Chrome pages still stall during loading. I'll update when I have more time to play with it. Any apps you want me to compare?
civiksi said:
I got a new one today but didn't have a lot of time to play with it. It came late due to the snow then I had to go snow blow. Google+ is definitely way better but Chrome pages still stall during loading. I'll update when I have more time to play with it. Any apps you want me to compare?
Click to expand...
Click to collapse
Hey, glad you got the replacement! The play store always stalls, along with reddit sync. If you could test either of those, that's be great
Thanks much man!
jhmn7 said:
Hey, glad you got the replacement! The play store always stalls, along with reddit sync. If you could test either of those, that's be great
Thanks much man!
Click to expand...
Click to collapse
After really playing with it I don't think its any better especially on Chrome. Google+ is the only thing that seems improved. I have tried it on all of the newest ac3200 routers as well.
On the plus side my battery life has been awesome. But still the wifi sucks. My old device had a build date of 9/28. The new one is 11/8.
I still kinda think there is a router chipset that the Turbo doesn't like. I have this problem at work, despite it being a 100/100 connection. At home on 50/5, its just fine, be it 5ghz or 2.4.
civiksi said:
On the plus side my battery life has been awesome. But still the wifi sucks. My old device had a build date of 9/28. The new one is 11/8.
Click to expand...
Click to collapse
This is sad, I will be sending mine back and just wait for the m9 plus. I didn't realize how much I used wifi until i starting having wifi issues.
Thanks for the update
rsalas187 said:
This is sad, I will be sending mine back and just wait for the m9 plus. I didn't realize how much I used wifi until i starting having wifi issues.
Thanks for the update
Click to expand...
Click to collapse
I feel the same way, but am beyond the return period. I started a broader search and it seems like the Moto X has similar wifi issues. Maybe it's more of a Motorola issue.
I'm using a 6th gen airport extreme, how about you?
jhmn7 said:
I feel the same way, but am beyond the return period. I started a broader search and it seems like the Moto X has similar wifi issues. Maybe it's more of a Motorola issue.
I'm using a 6th gen airport extreme, how about you?
Click to expand...
Click to collapse
I started off with a Netgear D6230 , Then I bought a ASUS RT-AC87U and saw no difference so I returned that and kept my D6230 . I had no problem buying a new router but it was only 6 months old and made no sense. My ipads ran fine on both routers along with two xbox's, GS4, GS3, Samsung TV Roku. BTW I ordered a Nexus 6 , I will miss the battery life.
Same issues here. Hope to get some traction!
Here 's the thread on the Motorola forum about the turbo app data lag over wifi.
https://forums.motorola.com/posts/06a2f3c5ca
Thought I'd pass it along.
I have a netgear r7000 and r8000. I've noticed if upnp, usb features are enabled, or dhcp is used, these erroneous issues tend to occur. Since disabling, i haven't had any of these issues. Also comcast turned up ipv6, which was also an issue...disabled in the routers and in my switch, and issues disappeared. Turbo wifi works excellenet
Seeing this issue on both my unlocked x4 running latest build (retus - PWWS27.1.3) and my fiance's Android One variant (running latest I assure you, can't get the info from her atm) where our phones will drop from the wifi in the house, and then immediately reconnect as if nothing happened.
Running a Netgear AC2350 r7500v2 with latest firmware (V1.0.3.26) through Verizon FIOS.
A lot of the reports and issues I'm reading about on other sites sound a lot like what the Pixel devices are going through, albeit they seem to be a little more centered around mesh networks, of which I don't have in use.
So pretty much, anyone else having weird issues relating to wifi on 8.0? If it's possible to go back to 7.1 I might give that a shot just to see if it's for sure an Oreo problem or not.
I had the same issue. I had to disable IPv6. I also got the phone replaced, the replacement does the same thing if IPv6 is enabled.
IPV6 on the router end you mean?
**UPDATE** Just checked, not enabled through my router.
thetolsonator said:
IPV6 on the router end you mean?
**UPDATE** Just checked, not enabled through my router.
Click to expand...
Click to collapse
Yes on the router. Before I upgraded the replacement, I think the WiFi was working fine. Something might be wrong with the Oreo update.
If you contact Motorola, they will replace it, my replacement didn't come with Oreo.
Motorola knows there's issues with the WiFi, but don't seem to care much. Not just the X4, if you search Google, you'll find some of their other phones with WiFi issues too.
tcrapper said:
Yes on the router. Before I upgraded the replacement, I think the WiFi was working fine. Something might be wrong with the Oreo update.
If you contact Motorola, they will replace it, my replacement didn't come with Oreo.
Motorola knows there's issues with the WiFi, but don't seem to care much. Not just the X4, if you search Google, you'll find some of their other phones with WiFi issues too.
Click to expand...
Click to collapse
Yuuuuuuup. Been finding a lot of people with the same problems. Instead of digging up old threads, figured it'd be worthwhile to start one here to bring more attention to the problem.
Now to find out if it's possible to get nougat back on...