Related
Hey all, just a quick problem I'm having with pandora. When I'm driving around listening to pandora it will randomly stop playing a song and I'll have to skip to the next song and it will play fine again. Anyone else have this problem? I've tried reinstalling from the market, and it's persisted over several roms and 2.1 and 2.2. Any help would be great! Thanks.
Sent from my SGH-I897
Its just a bandwidth issue that mobile phones have. Its not specific to you.
Sent from my SAMSUNG-SGH-I897 using XDA App
It normally only happens 2 times a day. But latley its like 20 times... O wellj
Sent from my SGH-I897 using XDA App
I'm a bartender and I plug my phone into the sound system to play music for the whole bar when I'm working, and I often stream music. For a while, I used Pandora but it would stop like that and/or freeze up and I would have to force stop it in task manager and re open it, which takes at least a minute (and in bartending, is a lot of time not spent making money). It got to the point where Pandora would stop every 4th or 5th song. Mind you, this was the same whether I was on wifi or 3g. Anyhow, I switched to Slacker and it's been almost flawless. It also actually plays the ****ing artist that I create the radio station around.
i also had this happening to me a while ago but it seems to be sparatic with my phone, lately it has been working great with wifi and 3g. It usually happens to me though when i am on a 3g network when i want to listen to something other than my ipod. Then other times i can be at school just sitting doing my hw while listening doing hw and it starts stopping on me. Unlike you though mine seemed to stop when the screen shutoff and i would have to press play again and as soon as i did that it would stop again. Think the problem was due to ATK but dont really know if that was true
screw pandora now.
ApplCobbler said:
I'm a bartender and I plug my phone into the sound system to play music for the whole bar when I'm working, and I often stream music. For a while, I used Pandora but it would stop like that and/or freeze up and I would have to force stop it in task manager and re open it, which takes at least a minute (and in bartending, is a lot of time not spent making money). It got to the point where Pandora would stop every 4th or 5th song. Mind you, this was the same whether I was on wifi or 3g. Anyhow, I switched to Slacker and it's been almost flawless. It also actually plays the ****ing artist that I create the radio station around.
Click to expand...
Click to collapse
I have also switched to slacker in the last couple weeks and will never go back to pandora. You are correct in that you actually hear the artist you chose quite often.
My wife and I notice that a lot when we are driving home from work listening to it via bluetooth. Every 3-4 songs it does that. In the middle of the day I never have a problem. I'm pretty sure their servers are likely just getting overwhelmed.
Was beginning to think it was my phone doing it...will try slacker now.
I, too, am glad to know it's not just my phone. Everything you guys describe happens to me also.
I never heard of Slacker, but will check it out now.
This has been an issue since version 1.5 of Pandora. It's very lame.
If you can find an apk of version 1.4.x, supposedly it was more reliable.
Sent from my SGH-I897 using XDA Premium App
Found pandora 1.3 apk on droid forums and is working great! Ill post link later.
Sent from Xda Premium on a Captivate running Paragon 6
Pandora 1.3 --->https://www.box.net/pdn-android-apps/1/46972990/467842722
Downloaded the 1.3 apk..installed...froze on first song! I give up.
I think I'm done with Pandora. Anyone have any advice between Last.FM and Slacker? I'd probaly go with the premium on which ever one I decided on.
Cog 4.1 btw
Just chiming in to say I have the same problem. I only get a few songs then Pandora stops playing. Not sure if it has to do with the phone going to sleep. I have seen some posts about "Mobile Data Always On" option but I have yet to find that on the Captivate.
No its pandora! I just downgrade to 1.3 and been fine since.
Hi,
I had been using Android Auto with a Huawei P8 lite. It never crashed, but only the response times where a bit sluggish.
I got a brand new Samsung 5 Neo, and after setting up the phone, there was immediately an update to Marshmallow.
When I started using Android Auto, I was pleased to see that the overall experience was faster and better than my Huawei.
But for some reason, during (longer) drives, my Spotify (and Google Music), would crash in the middle of a song. (first a stutter, it could happen after two songs, five songs, there is no logic in it). After it crashes, Google Maps becomes unresponsive. The only thing that helps is disconnecting the cable.
After reading the web, I learned that it could have been because of the marshmallow update.
So after trying all the usual fixes (rebooting phone before using Android Auto, keep data always alive, etc), I decided to downgrade to Android 5.0.
At first sight, I thought everything was solved, but after a few days, the exact same problem started to appear
I will now try to clear the app cache, and reboot the phone each time, but I'm a bit dissapointed that it doens't work as it's supposed to work.
Any tips, remarks are welcome.
Downgrading to Android 5 didn't help, so I flashed it to a version of Android 6.
Magically the issue got away. And interesting fact, after a few days without any problem, a song started to stutter (I thought "not again"), but there was a message on android auto that said: "no internet connection", and the song paused (without the whole head unit crashing). Interesting enough, the whole playlist is available offline on my phone. So I guess, it's some sort of background data the music app needs (maybe the syncing to last.fm), that caused the issue. But glad, for some reason in this build, they handle the exception better.
Downgrading to Android 5 didn't help, so I flashed it to a version of Android 6.
Magically the issue got away. And interesting fact, after a few days without any problem, a song started to stutter (I thought "not again"), but there was a message on android auto that said: "no internet connection", and the song paused (without the whole head unit crashing). Interesting enough, the whole playlist is available offline on my phone. So I guess, it's some sort of background data the music app needs (maybe the syncing to last.fm), that caused the issue. But glad, for some reason in this build, they handle the exception better.
Searched and searched so posting here and will try in general thread in case it's not tied to the watch itself.
Background: IOS user for phone, have to - developer, had Apple Watch (hated it). Got myself a Huawei Watch 2 on a deal and loved everything about it except the useless bezel and tiny screen size. Seeing as I had a great experience, I started a hunt for an LGWS. Hunt because not a single store sold one and I'm in Chicago with LOTS of stores. So online we go. There too - few resellers. Finally found one. New. Manufacture date of May 2017.
The Watch 2 worked flawlessly as functions go. Sycn'd, stayed connected, battery life of full use (all functions on - obviously no LTE), brightness at 8, raise to view on, always on display on... end of the day going to bed around 10:30 still had 50% of battery left at worst! The only issue other than cosmetic that it had was WIFI would not connect so "automatically" so to speak. So when I sent a watchmaker face, I always had to go to settings, connectivity, wifi and wait until the SSID showed connected. Then all is fine. Transferred over and enjoyed.
So the LGWS shows up. I unpair the Watch 2, connect up the LGWS and love it. The display I expected, size is great for me and off to the races. Within an hour it went from 95% to 60%. I figured - setup blues. Ignore it. Let it fully bake and see what happens. Another hour later I'm at 30%... ok onto the charger we go. Did a full charge at 6pm, by 9pm it was flat.
LGWS background: GW 2.8 loaded, Watch 2 was still running 2.0. LGWS - cellular off, raise to view on, display brightness 4, wifi connected...
But here's what I noticed: on my phone, it consistently says disconnected - tap card to connect. I tried that about 20 times, no joy. Rebooted watch and phone... no joy. Reset watch, deleted app on phone and deleted Bluetooth pairing. Re-installed Wear app, re-paired watch, left all at stock settings except shut-off cellular and OK Google listening.
That last bit is the 6-9pm going totally flat.
So. Any ideas here? Things I see - 8 vs 2 OS... obviously IOS (I get it, but why did the Huawei work so well?) and there is nothing I can do about that. Don't know if I can downgrade to 2 to see if that makes a difference... if I do, will it self-update back to 8 when it gets a chance?
I really want to keep this watch - it's exactly what I wanted (short of strap change capability). I sure hope Google doesn't give up on Wear. As a Mac/IOS dev, I can easily say this is a superior platform for the user. Truly great stuff and I want it to improve and keep improving. The iWatch bigots are really missing out!
Thanks in advance for your tips.
Cheers!
Have you tried doing a reset?
When I got mine, it upgraded straight away so I thought "great", it's a clean watch, there can't be anything wrong with it.
Nope..
Apps didn't work.
Battery life was rubbish.
Did a reset when i got a new phone.
Apps worked without issue.
Battery takes me from 5am through to 9pm with 40% left at least, LTE is off but aod is on.
Yes - reset the watch to factory when I deleted the app, pairing etc - went totally to step 0 across the board, short of formatting over the phone itself. But I did one more reset after that last night and charged it all night. So far this morning (wrote most of my note locally last night, posted this morning) I'm holding up pretty well. Nothing running on the watch - bone stock with phone shut off and Ok Google off. 2.5 hours @ 91%. Fingers crossed that this was a fluke. But in my experience today is probably the fluke LOL.
wig said:
Searched and searched so posting here and will try in general thread in case it's not tied to the watch itself.
Background: IOS user for phone, have to - developer, had Apple Watch (hated it). Got myself a Huawei Watch 2 on a deal and loved everything about it except the useless bezel and tiny screen size. Seeing as I had a great experience, I started a hunt for an LGWS. Hunt because not a single store sold one and I'm in Chicago with LOTS of stores. So online we go. There too - few resellers. Finally found one. New. Manufacture date of May 2017.
The Watch 2 worked flawlessly as functions go. Sycn'd, stayed connected, battery life of full use (all functions on - obviously no LTE), brightness at 8, raise to view on, always on display on... end of the day going to bed around 10:30 still had 50% of battery left at worst! The only issue other than cosmetic that it had was WIFI would not connect so "automatically" so to speak. So when I sent a watchmaker face, I always had to go to settings, connectivity, wifi and wait until the SSID showed connected. Then all is fine. Transferred over and enjoyed.
So the LGWS shows up. I unpair the Watch 2, connect up the LGWS and love it. The display I expected, size is great for me and off to the races. Within an hour it went from 95% to 60%. I figured - setup blues. Ignore it. Let it fully bake and see what happens. Another hour later I'm at 30%... ok onto the charger we go. Did a full charge at 6pm, by 9pm it was flat.
LGWS background: GW 2.8 loaded, Watch 2 was still running 2.0. LGWS - cellular off, raise to view on, display brightness 4, wifi connected...
But here's what I noticed: on my phone, it consistently says disconnected - tap card to connect. I tried that about 20 times, no joy. Rebooted watch and phone... no joy. Reset watch, deleted app on phone and deleted Bluetooth pairing. Re-installed Wear app, re-paired watch, left all at stock settings except shut-off cellular and OK Google listening.
That last bit is the 6-9pm going totally flat.
So. Any ideas here? Things I see - 8 vs 2 OS... obviously IOS (I get it, but why did the Huawei work so well?) and there is nothing I can do about that. Don't know if I can downgrade to 2 to see if that makes a difference... if I do, will it self-update back to 8 when it gets a chance?
I really want to keep this watch - it's exactly what I wanted (short of strap change capability). I sure hope Google doesn't give up on Wear. As a Mac/IOS dev, I can easily say this is a superior platform for the user. Truly great stuff and I want it to improve and keep improving. The iWatch bigots are really missing out!
Thanks in advance for your tips.
Cheers!
Click to expand...
Click to collapse
Sorry to bump an old thread how is your usage the last few months? I'm confused between buying this and the huawei watch 2.
Thank you @wig
Sent from my Sony Xperia XZ1 using XDA Labs
No worries. The LGWS has been pretty decent. It seems to me that its bluetooth radio gets confused. For example, when I'm in my car, sometimes the watch disconnects or the car bluetooth disconnects. When I'm in my home office where the WIFI router is, the watch seems to disconnect as well. Beyond these weird edge cases, it stays connected and just works. The disconnecting isn't really bothering me as much as the fact that when it does, it tries to connect over WIFI and drains the battery pretty quickly. I've kind of learned to live with it and the hardware in this watch is better than the HW2. That being said, my experience with connectivity was much better with the HW2. Not sure how it's going now for those who have it. Android Wear has updated both the IOS app and the core OS and apps numerous times since I posted this. So for all I know, HW2 is doing the same thing these days. It does appear Google is trying.
As for the LGWS - go to ebay, find yourself a new one that's super cheap. I ended up getting mine for around $170 which made it a no brainer. One of these days I'll throw a SIM in it just to try it, but have bigger fish to fry at the moment.
Best of luck.
P.S. I just saw you have an android phone - so your mileage may vary and in fact will probably be MUCH better. I'm on iPhone which is 90% of the issue.
wig said:
No worries. The LGWS has been pretty decent. It seems to me that its bluetooth radio gets confused. For example, when I'm in my car, sometimes the watch disconnects or the car bluetooth disconnects. When I'm in my home office where the WIFI router is, the watch seems to disconnect as well. Beyond these weird edge cases, it stays connected and just works. The disconnecting isn't really bothering me as much as the fact that when it does, it tries to connect over WIFI and drains the battery pretty quickly. I've kind of learned to live with it and the hardware in this watch is better than the HW2. That being said, my experience with connectivity was much better with the HW2. Not sure how it's going now for those who have it. Android Wear has updated both the IOS app and the core OS and apps numerous times since I posted this. So for all I know, HW2 is doing the same thing these days. It does appear Google is trying.
As for the LGWS - go to ebay, find yourself a new one that's super cheap. I ended up getting mine for around $170 which made it a no brainer. One of these days I'll throw a SIM in it just to try it, but have bigger fish to fry at the moment.
Best of luck.
P.S. I just saw you have an android phone - so your mileage may vary and in fact will probably be MUCH better. I'm on iPhone which is 90% of the issue.
Click to expand...
Click to collapse
Thank you so much for your reply I think you have sold me the watch. Now I can continue my search to try and find one. Seems at $170 that's definitely a bargain let me know if your wanting to sell ?
Sent from my Sony Xperia XZ1 using XDA Labs
Well, this seems to be a common issue that Asus support knows nothing about. I have learned that Asus support is worthless, but I will leave that rant for another post. Anyway, I am having the same issue that many other people seem to have, but I haven't been able to find a solution for it. I have a 6P, latest Android Wear on the phone, latest Android Wear on the watch, and it usually takes 15-30 seconds for the watch to "ring" when I get a phone call. Additional details below.
Here is, in detail, what I have noticed. If I have used the watch recently (sorry, can't provide an accurate, or even estimate time fraim) it seems to work fine, however if it hasn't been used in a while, it can take 15-30 seconds for the watch to notify me of an incoming call. I am used to my pebble, where notifications that take 2 seconds are VERY long delays, usually its instant with the pebble. This also appears to be an issue when an alarm goes off. Alarm, as in set an alarm in the clock app, it takes forever to get the notification on my watch. As far as phone calls, it also seems as though if I answer the phone before the watch starts ringing, the watch can start ringing after I have answered the phone, and am talking on the phone, and the watch won't shut up until the call has ended.
I assume there is a simple fox for this, but I can't find it anywhere. For details, the watch is running 2.8.0.182823779 (Latest at the time of writing) the phone is running 8.0.0 rooted, android wear 2.9.0.185084575.gms (Latest at time of writing)
Practically begging for help here, thanks in advance.
I assume you are using stock AW 2. Everyone of us has had problems with the speed of the watch. The snapdragon 1200 seems to be to slow and old for AW 2. But if you try the ROM available here in the forum made by @janjan , it get's a little bit better.
You have to disable ZenWatch Manager on the watch and uninstall on your phone.
The Zenwatch manager actually processes lots of data before notifying the watch. Hence the lag.
First of all, I really like my galaxy watch 5 pro. I often take my LTE version when I go running, connected to my Galaxy buds live. There are certain issues I have, which drive me bananas:
When it passes a marker (for example, every mile), it breaks up the music, briefly. Usually only for the first one or two markers. And then it reappears later, sometimes. Definitely an intermittent issue. It's like, it pauses and tries to figure out what it is supposed to do: the watch is like 'Do I pause,? do I stop the music? Do I act like there's a major blast of Wi-Fi in the area news connection?' it's like it has a conflict going on inside it.
Secondly even when I've got it on do not disturb, if someone phones me or there are certain kinds of messages that go to my phone, they still forward!! The worst is if somebody calls me, it stops the music! And it's almost impossible to stop the call while running! And I can't restart the music without really fiddling around with the watch, and that is really difficult to do without losing your pace.
It's not a great running watch in my opinion. Samsung needs to fix some things here.
Am I the only one? Maybe it's my watch.
ekerbuddyeker said:
First of all, I really like my galaxy watch 5 pro. I often take my LTE version when I go running, connected to my Galaxy buds live. There are certain issues I have, which drive me bananas:
When it passes a marker (for example, every mile), it breaks up the music, briefly. Usually only for the first one or two markers. And then it reappears later, sometimes. Definitely an intermittent issue. It's like, it pauses and tries to figure out what it is supposed to do: the watch is like 'Do I pause,? do I stop the music? Do I act like there's a major blast of Wi-Fi in the area news connection?' it's like it has a conflict going on inside it.
Secondly even when I've got it on do not disturb, if someone phones me or there are certain kinds of messages that go to my phone, they still forward!! The worst is if somebody calls me, it stops the music! And it's almost impossible to stop the call while running! And I can't restart the music without really fiddling around with the watch, and that is really difficult to do without losing your pace.
It's not a great running watch in my opinion. Samsung needs to fix some things here.
Am I the only one? Maybe it's my watch.
Click to expand...
Click to collapse
A possible reason for the break in the music could be that you are switching between cell towers and there is possibly a gap in the signals, happens to me sometimes when driving down motorways. or maybe there is a setting somewhere to inform you when you reach these markers and its briefly trying to silently play another sound idk dont own the watch so cant really say what the problem is except for some general things it could be.
Secondly bugs bugs and more bugs, dislike them a lot myself lol
What fitness app are you using? I don't wear earbuds when running but Strava seems to work really well. A good fitness app will allow you to customize notifications. Maybe consider disabling wireless data when running.
It drives me bananas. I went on a run today. As it starts telling me my lap info, the music cuts out, the voice is a bit broken up, and then, when I'm in an area with trees, it must confuse the gps which makes the watch decide that I have 'lapped', and it starts giving me new lap times every 5 seconds!!! Makes it impossible to use with earbuds. MYne it is the combination of everything going on, and I admit it's a lot, data, voice ready, music to Bluetooth, gps, Samsung health app running etc... But they sell this as a WORKING solution, and it so often doesn't work properly (for me).
ekerbuddyeker said:
It drives me bananas. I went on a run today. As it starts telling me my lap info, the music cuts out, the voice is a bit broken up, and then, when I'm in an area with trees, it must confuse the gps which makes the watch decide that I have 'lapped', and it starts giving me new lap times every 5 seconds!!! Makes it impossible to use with earbuds. MYne it is the combination of everything going on, and I admit it's a lot, data, voice ready, music to Bluetooth, gps, Samsung health app running etc... But they sell this as a WORKING solution, and it so often doesn't work properly (for me).
Click to expand...
Click to collapse
I just went for a 2 mile walk while listening to earbuds through the watch and Samsung Health was monitoring it and it worked perfectly.
Ok, I may have solved the issue. Will be testing it soon. I switched from Samsung to Google text so speech engine.