Hello all...
Has anyone else been having buffering issues at the beginning of Google Play Music streaming songs? The music will go for a second, stop, go for another couple of seconds, stop, and then play fully. This is on Normal quality and is in places where I can do a speedtest at over 10mbit/sec. Often it's 20mbit or more. It seems like this started happening when the new 3.x firmware was released. I never had buffering before.
I've tried everything from uninstalling/clearing data to clean flashing ROMs. Same thing, and it shouldn't be happening with the bandwidth I have available.
Thanks.
A
Ive noticed this as well. Have not noticed any difference in quality of music but i have noticed it start, buffer, play, buffer, play..
I also am in a strong cellular spot with LTE and often 15+mb down. So i am convinced its not a thru put issue. I have not noticed it on WiFi so ill keep a look out for that.
Alpione said:
Hello all...
Has anyone else been having buffering issues at the beginning of Google Play Music streaming songs? The music will go for a second, stop, go for another couple of seconds, stop, and then play fully. This is on Normal quality and is in places where I can do a speedtest at over 10mbit/sec. Often it's 20mbit or more. It seems like this started happening when the new 3.x firmware was released. I never had buffering before.
I've tried everything from uninstalling/clearing data to clean flashing ROMs. Same thing, and it shouldn't be happening with the bandwidth I have available.
Thanks.
A
Click to expand...
Click to collapse
I've had GPM problems as well. Sometimes what you describe, sometimes the song starts, plays a few seconds then stops completely. All on good data connections, sometimes happens on WiFi. I also have the latest FW but I flashed right after I got the phone so I have nothing to compare it to.
While we're on the subject of music, does anyone experience crackling when moving the 3.5mm jack during playback? Sometimes the crackling really bothers me when I'm walking.
No crackling that im aware of on my unit.
From past experience that crackling can be from dirty connectors or a bad connection. What your hearing is the arching or electrical components momentarily loosing then regaining contact with each other. OR if it is securely connected in its possible the connector is being stressed to much and possibly coming loose from the board.
The last alternative is your headphones were not made very well and the crackling is coming from damaged or poorly soldered connection inside the male plug.
To test this out try a different cable or different wired headphones with a different cable. IF the crackling stops its your cable and not your phone connector.
I have had these start/stop issues at the beginning of tracks using both my cellular network and Wi-Fi...very strange.
I'm also experiencing this issue. It's very distracting. ARHD 21.0 on latest firmware.
Good to hear that I'm not the only one. I did a support chat with Google Play's support techs and they couldn't figure it out. Frustrating.
I've had the issue on ARHD and Venom. I was using the default modem/radio in the new international firmware and tried changing it to the latest AT&T radio. I got significantly better speeds on the AT&T radio but the skipping problem was still there.
Weird.
A
Ok, so I finally solved this after trying a ton of things.
I've got the AT&T variant and, like many of us, had been using the international firmware and ROMs (ARHD, Venom, etc.) This Google Play buffering problem seemed to start when I upgraded to the latest 3.x firmwares. I decided to test out that theory by going back to AT&T-specific firmwares and used this thread: http://forum.xda-developers.com/att...-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
I first tried wiping everything and flashing the 3.28.1540.5 firmware and ROM, which is 4.4.4 not officially released by AT&T but apparently for the identical Dev edition. Didn't work. Buffering problem was still there.
I decided to go back to total stock and flashed the officially released AT&T 4.4.3 version - 2.22.1540.4. Eureka! Everything works great now, and LTE speeds have jumped from 10-20mbit down to 30-40. That's especially interesting because I had already tried swapping out the international modem/radio with AT&T's 1.16 version. That only got me to 20. Flashing the whole firmware and stock ROM got me to 40.
So this is a good lesson - even though the phone hardware is identical and we complain about the carriers taking forever for updates, there obviously is value in what they do to optimize these ROMs for their own network.
A
I decided to go back to total stock and flashed the officially released AT&T 4.4.3 version - 2.22.1540.4.This is still us developer build:silly:. If using the build in my thread it has been modified for ATT specifically. All firmwares in my thread are for the US Developer device, but are modified for ATT as thats my carrier.
Alpione said:
Ok, so I finally solved this after trying a ton of things.
I've got the AT&T variant and, like many of us, had been using the international firmware and ROMs (ARHD, Venom, etc.) This Google Play buffering problem seemed to start when I upgraded to the latest 3.x firmwares. I decided to test out that theory by going back to AT&T-specific firmwares and used this thread: http://forum.xda-developers.com/att...-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
I first tried wiping everything and flashing the 3.28.1540.5 firmware and ROM, which is 4.4.4 not officially released by AT&T but apparently for the identical Dev edition. Didn't work. Buffering problem was still there.
I decided to go back to total stock and flashed the officially released AT&T 4.4.3 version - 2.22.1540.4. Eureka! Everything works great now, and LTE speeds have jumped from 10-20mbit down to 30-40. That's especially interesting because I had already tried swapping out the international modem/radio with AT&T's 1.16 version. That only got me to 20. Flashing the whole firmware and stock ROM got me to 40.
So this is a good lesson - even though the phone hardware is identical and we complain about the carriers taking forever for updates, there obviously is value in what they do to optimize these ROMs for their own network.
A
Click to expand...
Click to collapse
Wonders_Never_Cease said:
I decided to go back to total stock and flashed the officially released AT&T 4.4.3 version - 2.22.1540.4.This is still us developer build:silly:. If using the build in my thread it has been modified for ATT specifically. All firmwares in my thread are for the US Developer device, but are modified for ATT as thats my carrier.
Click to expand...
Click to collapse
Ha! Too damned many versions.
Regardless, I'm good to go for now.
A
Related
Need some help here. I never usually need help, been modding everything possible on Android for years now. But can't figure this one out, getting worried.
Had my LTE Nexus since launch day. No issues like this before.
Been on all Team Kang AOKP toro ROM updates since release, always on the latest. Stock kernel. Was on build 20 since it came out.
Yesterday at work, had a few bugs from probably not data wiping from build 19, so I wiped it all and re-flashed 20 again. Restored Titanium and started re-setting things up, I believe these are the only things I did. I was at work where I would normally have minimal, but some, service.
Ever since around there, I have not once had a bit of 3G or 4G service. I have not seen the 3G logo for even an instant, only few, gray bars. Wifi works fine of course. It's possible I even lost service before wiping and re-flashing, but I can't recall or didn't notice.
I tried all the usual stuff, wiping everything again, re-flashed AOKP 20, re-flashed other/older ROMs, re-flashed latest radio, restored old Nandroid backups, pulled battery and sim card and put back/rebooted...NOTHING IS WORKING. Also, I have driven through several towns since yesterday so I know it's not a local outage. Also, other people with Verizon phones here have service fine.
I have basically torn the phone down software-wise and nothing has fixed the issue. I still have no service. Each time I re-flash a ROM, it always makes me go on Wifi when it wants me to sign into Google...it never picks up mobile service then or after.
The About>Status screen says:
Network: Verizon Wireless
Signal Strength: shows an actual number reading that changes
Service State: In Service
Roaming: Not roaming
Mobile network state: Disconnected
Please suggest things I can try, but I guaranteed I have already tried them. Can't understand or imagine what is causing this, because I did nothing different than I normally do.
Also, I posted this on Rootz as well, and many replies so far. Still no luck though.
If you have an idea I can try, maybe post there instead at this point for me?
Thanks guys in advance.
http://rootzwiki.com/topic/16407-bi...ile-service-since-yesterday-tried-everything/
It seems a radio problem. Try to flash the stock ROM from Google.
tigajr said:
It seems a radio problem. Try to flash the stock ROM from Google.
Click to expand...
Click to collapse
Well I did go back to many random earlier, more stock custom ROMs in hopes of a fix, but nothing so far. I am currently back on the stock 4.0.2 ROM that is rooted and deodexed by Bigxie, but I guess I can go all the way back to stock 4.0.1 or 0.2. Will try now.
Went to Verizon and it looks like the sim card swap did it. The girl there was nice and did it without hesitation for me.
She showed me in her computer how under my family account, it wasn't even fully showing my device or something like that. Not sure if it wasn't there at all or if it just didn't show that I had a 4g phone activated on the account...but I'm sure it was related.
Sucks to have to get a swap and still don't know what caused it or if its related to flashing roms, but at least it works! No issues since...
It is possible, but unlikely and no reasonable explanation, that your sim somehow got affected doing all the flashing and stuff.
Sent from my Nexus in Texas.
So, I figured I'd share since I couldn't find much information on the forums about this.
I recently, within last few weeks, started having issues with the modem on my GNex.
I had been running a ROM derived from AOSP Jelly Bean without issue, except the modem seemed to get poor signal quality.
I tried to upgrade the modem once the official Sprint JB release of FH05 started spreading.
At some point afterwards it seemed the modem would inexplicably start to die periodically... (By die I mean the status would change to searching and/or not connected and the status icon would change to no service icon). I could sometimes trigger life back in at times by toggling CDMA/LTE or CDMA Only options or the data enabled options or rebooting...
I went through a period of continually trying to reflash the various radios FD02, FC12, FH05... all in an attempt to get stability.
I had persistent issues even trying to flash the radios. The LTE radio would always flash fine, but the CDMA radio would often hang in flashboot forcing me to sever connection and restart.
This never seemed to fix the issue and I began to think I might either have bad flash memory on the radio partition or there was a problem with the radio hardware causing this issue.
I then remembered I had dropped the phone on concrete and it landed on the modem side of the phone... phone seemed fine besides a few new dings, but operated ok. I considered maybe this had something to do with the state of things.
Last night I took my phone back off using these instructions: http://www.ifixit.com/Teardown/Samsung-Galaxy-Nexus-Teardown/7182/1
I basically just jostled the internals a bit hoping to fix maybe a simple misalignment...
It has been a solid 12 hours and everything seems to be running strong.
This is purely speculation, but given that I haven't been able to consistently replicate any scenario other than it not working... I am hoping this is the fix.
I hope it might help someone else, or someone else with a similar problem can confirm or provide alternate conclusion.
I am currently running:
ROM:
http://forum.xda-developers.com/showthread.php?t=1801942
LTE and CDMA FH05:
http://forum.xda-developers.com/showthread.php?t=1620036#2
TWRP 2.2:
http://teamw.in/project/twrp2/92
shadowspires said:
So, I figured I'd share since I couldn't find much information on the forums about this.
I recently, within last few weeks, started having issues with the modem on my GNex.
I had been running a ROM derived from AOSP Jelly Bean without issue, except the modem seemed to get poor signal quality.
I tried to upgrade the modem once the official Sprint JB release of FH05 started spreading.
At some point afterwards it seemed the modem would inexplicably start to die periodically... (By die I mean the status would change to searching and/or not connected and the status icon would change to no service icon). I could sometimes trigger life back in at times by toggling CDMA/LTE or CDMA Only options or the data enabled options or rebooting...
I went through a period of continually trying to reflash the various radios FD02, FC12, FH05... all in an attempt to get stability.
I had persistent issues even trying to flash the radios. The LTE radio would always flash fine, but the CDMA radio would often hang in flashboot forcing me to sever connection and restart.
This never seemed to fix the issue and I began to think I might either have bad flash memory on the radio partition or there was a problem with the radio hardware causing this issue.
I then remembered I had dropped the phone on concrete and it landed on the modem side of the phone... phone seemed fine besides a few new dings, but operated ok. I considered maybe this had something to do with the state of things.
Last night I took my phone back off using these instructions: http://www.ifixit.com/Teardown/Samsung-Galaxy-Nexus-Teardown/7182/1
I basically just jostled the internals a bit hoping to fix maybe a simple misalignment...
It has been a solid 12 hours and everything seems to be running strong.
This is purely speculation, but given that I haven't been able to consistently replicate any scenario other than it not working... I am hoping this is the fix.
I hope it might help someone else, or someone else with a similar problem can confirm or provide alternate conclusion.
I am currently running:
ROM:
http://forum.xda-developers.com/showthread.php?t=1801942
LTE and CDMA FH05:
http://forum.xda-developers.com/showthread.php?t=1620036#2
TWRP 2.2:
http://teamw.in/project/twrp2/92
Click to expand...
Click to collapse
So you just took apart and reassembled and that got it working?
Maybe
xvanwilderx said:
So you just took apart and reassembled and that got it working?
Click to expand...
Click to collapse
Tried to sell phone on ebay because the wifi adapter was showing issues with range... I bought another and it was clear that the range of the older phone was having issues...
Tried to sell on ebay and buyer couldn't activate... just sent back and I can't get it to accept a flash at all... maybe trying the taking apart trick again...
Crazy
edit: can't post links, too much noob.
go to google code, search for -- Issue 38563: Upgrade to 4.1.2 broke tethering --
My tethering appears to have gone to crap since 4.1.2
There are quite a few variables so I'm not sure where the problem is, on top of that the issue is not 100% consistent.
It appears that when I am not tethered I get a decent ping on my phone (150ms, 95%)
Shortly after initiating a tether my connection goes straight to hell (300-3000ms 50%)
My laptop is often even worse than my phone.
This is usually with a full 5 bars of 'H'.
I'm gathering the ping stats from my phone with terminal emulator.
I'm using a MacBook Air.
I will try to reproduce the issue with my nexus 7 when I have some spare time.
Anyone else experiencing something similiar?
luck02 said:
edit: can't post links, too much noob.
go to google code, search for -- Issue 38563: Upgrade to 4.1.2 broke tethering --
My tethering appears to have gone to crap since 4.1.2
There are quite a few variables so I'm not sure where the problem is, on top of that the issue is not 100% consistent.
It appears that when I am not tethered I get a decent ping on my phone (150ms, 95%)
Shortly after initiating a tether my connection goes straight to hell (300-3000ms 50%)
My laptop is often even worse than my phone.
This is usually with a full 5 bars of 'H'.
I'm gathering the ping stats from my phone with terminal emulator.
I'm using a MacBook Air.
I will try to reproduce the issue with my nexus 7 when I have some spare time.
Anyone else experiencing something similiar?
Click to expand...
Click to collapse
http://code.google.com/p/android/issues/detail?id=38563
I, like many others have had this problem since 4.1.2, rolled back to 4.1.1 and WiFi tethering worked again. Back to 4.1.2, stopped working again. Installed 4.2 on Gnex yesterday hoping for fix but still no good.
As 4.1.2 is "old hat" now I have started new issue at Google for 4.2 here
code.google.com/p/android/issues/detail?id=39618
Please anybody with same problem go there and add to report.
DO NOT turn it into a *****ing thread like so many here on xda.!!! The item to which luck02 referred for 4.1.2 at code.google.com is just full of twats ranting about their phone suppliers charges for data and crap like that.
code.google.com is to report faults and bugs and by everybody contributing pertinent information maybe Google will look for a fix. Trolling and whinging does nothing but obscure the facts...... please respect this. Just tell them model number, build and describe fault - thanks
Well there is definitely some ranting and twats involved but to my mind that's just part and parcel of being on the internet. Ignore and contribute as you can. Has anyone tried the CM build on the GNEX? Also, has anyone confirmed / denied whether third party wifi tether applications resolve the issue (requires root)?
Actually even more importantly, has anyone isolated where the breakage is actually occurring? I'm assuming it's something in the drivers / networking layer that is screwing up the routing between incoming data and the wifi layer...
I will probably downgrade if nothing else works.
So I got frustrated and rooted / installed clockwork recovery.
Moved to CM 10 and still have the same issue. I'm thinking it's actually a carrier issue for me at this point.
My carrier term expires in January and I'll probably go to a different carrier then.
Will follow up with more information as I have it, I may roll back to an older version of CM to confirm the problem is still occurring.
luck02 said:
So I got frustrated and rooted / installed clockwork recovery.
Moved to CM 10 and still have the same issue. I'm thinking it's actually a carrier issue for me at this point.
My carrier term expires in January and I'll probably go to a different carrier then.
Will follow up with more information as I have it, I may roll back to an older version of CM to confirm the problem is still occurring.
Click to expand...
Click to collapse
Definitely not carrier for me, proved by numerous attempts and firmware this weekend. Gnex running 4.1.1 everything works perfectly. Let phone do ota to 4.1.2, broke WiFi tethering and Bluetooth to vehicle completely. Reinstalled 4.1.1 thro Odin and re-partitioned at same time so completely clean install, WiFi tethering and Bluetooth worked perfectly. Continued on complete wipe track by then installing 4.1.2 thro Odin with re-partition (thus removing possibility that incremental upgrade to 4.1.2 was to blame) still no WiFi tethering or Bluetooth.
Did same for 4.2 using Odin still didn't work. Returned to 4.1.1 using Odin, everything worked.
Even made my own Odin package using radio from 4.1.1 (even tho supposedly same as 4.1.2) system and other files from 4.2 - same result, nothing worked.
To eliminate doubt used same sim card in two HTC phones running 4.0.4, both showed correct working and tethering and Bluetooth. Conclusion, not carrier/ supplier related, but surely random hardware/ firmware incompatibility on some examples of Gnex for unfortunate souls such as us
Tried two WiFi tethering apps with exact same result... shows tether as working, greyed out WiFi icon on tab and no go on laptop or desktop....I have spent hours on this to no avail
Have you tried any network diagnostics while not tethered?
I may be getting carrier and 4.1.2 issues. I was running some ping tests while not tethered yesterday. Full 5 bars of 'H+' running CM10 and I was getting horrible signal. More than 50% dropped packets and long ping times.
I'll roll back to an older CM sometime soon and see if there's a difference over the next couple of days.
Thank you,
stinky73 said:
Definitely not carrier for me, proved by numerous attempts and firmware this weekend. Gnex running 4.1.1 everything works perfectly. Let phone do ota to 4.1.2, broke WiFi tethering and Bluetooth to vehicle completely. Reinstalled 4.1.1 thro Odin and re-partitioned at same time so completely clean install, WiFi tethering and Bluetooth worked perfectly. Continued on complete wipe track by then installing 4.1.2 thro Odin with re-partition (thus removing possibility that incremental upgrade to 4.1.2 was to blame) still no WiFi tethering or Bluetooth.
Did same for 4.2 using Odin still didn't work. Returned to 4.1.1 using Odin, everything worked.
To eliminate doubt used same sim card in two HTC phones running 4.0.4, both showed correct working and tethering and Bluetooth. Conclusion, not carrier/ supplier related, but surely random hardware/ firmware incompatibility on some examples of Gnex for unfortunate souls such as us
Click to expand...
Click to collapse
I'm Noob, I got problem same error on 4.2 and 4.2.1, this issue over half a month.
I have google some website, found have several people like us have this issue and still no idea to fix it...
Mostly couldn't connect to laptop or Mac Book. For me is PlayStation Vita (firmware 2.0 Wifi only)
My PS Vita could deal with my galaxy Nexus on 4.1.2 , but 4.2 is could reach Internet correctly.
I have tried several Wi-Fi Device to connect my Galaxy Nexus,
My PC , My PS3, My PSP, My Uncle Galaxy Nexus 4.1.1 (Samsung image) are working fine.
Only my PS Vita couldn't...
But base on others, have same issue on other device, so I did think this issue may cause by 4.2.
Base on this issue, I have try "wifi-tether" , whatever this download on Google play! or "3.3 pre-2" on their website.
I have it running on Factory 4.2 , 4.2.1 Rooted + Super user, this couldn't work correctly.
Running on KALO 2.0 ROM, this have error on "Clamping MMS"....
No Luck for me.
My GNexus is only one device at the moment, which could let my PS Vita online... I have some PS Vita game need running online.
This force me stay on 4.1.2 and try disable System update notification next minute, for several weeks or month until the solution come...
Or... Anyone could build a patch which could let 4.2 using 4.1.2 Wi-Fi tethering engine?
Hello all. I have my Note rooted with a custom recovery, but I have not flashed a rom. Well, I have flashed a few, but I've since gone back to stock and re-rooted because the bluetooth issues are a dealbreaker for me.
Here is the actual question. I've been getting a lot of updates from samsung. I came from an HTC Evo - and HTC rarely did updates. Has Samsung really released 3-4 updates in the last 2 weeks? Or is my phone just not properly installing them? The android version is 4.1.1, also not sure if this is all the way current. I just checked on the update your phone page in the system settings and it says I am current...
I'm running the same thing as you (stock, rooted with custom recovery) and I have not had an update recently. Mine is currently 4.1.1 as well, with the L900VPALJC build. I agree that it's the BT streaming that's keeping me from custom roms right now
bl4ckllama said:
I'm running the same thing as you (stock, rooted with custom recovery) and I have not had an update recently. Mine is currently 4.1.1 as well, with the L900VPALJC build. I agree that it's the BT streaming that's keeping me from custom roms right now
Click to expand...
Click to collapse
I've had issues not only with A2DP, but also with call quality on BT as well. It sounds choppy and has TERRIBLE range on at least 3 different roms...Paranoid Android is awesome on our 5.5" screen, but I cant talk on the phone or use Slacker radio Hopefullt someone does a better job with the BT drivers sometime soon.
I imagine once the CM blue tooth problems are fixed the roms using it will get stepped up. I downloaded Macksrom today to run a trial to see how the improvements are. Though now that I know ADW isn't messing up my phone anymore I may just stick with stock for now. I have a current backup and I'm feeling bored, so I'll most likely **** around with it this weekend
So ever since the update to 4.4.4, my spotify no longer works over cellular. It only works over WiFi now. Checking on tmobile forums, it appears that it's an issue that a good number of m8 users on tmobile are having after this update. Is there a way to roll back to 4.4.3 until they get this sorted out? I'm on stock, not rooted.
TriBeard said:
So ever since the update to 4.4.4, my spotify no longer works over cellular. It only works over WiFi now. Checking on tmobile forums, it appears that it's an issue that a good number of m8 users on tmobile are having after this update. Is there a way to roll back to 4.4.3 until they get this sorted out? I'm on stock, not rooted.
Click to expand...
Click to collapse
It sucks but I'm glad it's not just me. I switched over to Google Play Music premium for the time being. I have actually noticed this problem in the past too only with Spotify. But now it seems like it wont work at all on cellular unless i'm listening to a downloaded playlist.
Paging Dr B said:
It sucks but I'm glad it's not just me. I switched over to Google Play Music premium for the time being. I have actually noticed this problem in the past too only with Spotify. But now it seems like it wont work at all on cellular unless i'm listening to a downloaded playlist.
Click to expand...
Click to collapse
I reached out to spotify support, and they said that it was a known issue that they're working on. What has worked for me so far, at least somewhat, is creating a new APN with the same settings as the stock one, but setting the APN mode to IPV4 only. I also changed the mode from GSM/HSPA/LTE to just GSM/HSPA, and so far, it works most of the time like this. I never had LTE in my area anyway, which makes it a little more strange that the last part would have any effect, but it seems to have helped some. I hope they update it soon though. I started checking out rdio, but didn't like it nearly as much, and I can't endorse google play music with their 10 authorizations in a year thing.