Play progress doesn’t sync on the google nest hub display on a stand alone basis as well as across iphone in the google podcast hub
up until couple of month ago I was able to resume podcasts in progress and continue playing from the exact time mark in the same episode were I last Paused the podcast in the google nest hub display speaker.
since that time this function stopped working in the google nest hub display while it is only working now on my iphone with the google podcast app with the same user email address.
since that time when resuming a podcast in the google nest hub display speaker it continues playing from the exact time mark in the same episode that was paused in my iphone with the google podcast app. in other words the play in progress sync only in the iphone google podcast app which also control the podcast in the nest hub speaker.
bottom line there is a conflict between my iphone google podcast app and the podcast service in my google nest hub display speaker
I should note that I have tried every possible trouble shoot including replacing all my nest hub displays devices to new devices while simultaneity reinstalling the google home app. even after deleting the google podcast app from my iphone or loging in from a different user email address the problem still persist
Did you contact google to report the issue?
the more people contact google directly to complain about this problem the more likely that they will resolve it eventually Rather sooner than later. There for it would be very helpful if you could kindly contact Google directly to complain/inform about this problem via the following to channels of communication:
1. You can call google home customer care to report the issue
1 (855) 971-9121
2. In addition you should also submit a voice massage via the Google Home Hub smart speaker directly to the developers team by using the voice command “Hey Google send a feedback” and than you can use what I wrote as a guidance to convey the problem
I would highly appreciate if you could keep me posted if and when you were successful to resolve this problem 😁
I speculate that this issue will resolve with the 3rd generation devices
I had other issues in the past that I was able to resolve only after switching from the 1st generation to the 2nd generation devices
David for your connivence, I started a new thread on the same issue but with more articulate description of the problem and a more effective and better and better searchable title, I would very much apricate if u can give a like in the new thread as well as replay with the same comment that u provided in the current thread so I can potentially delete this thread and replaced with the new thread
Please click on the link to the new thread:
It looks like we haven't heard back from the OP so I'm going to go ahead and lock the thread. If you have any further questions or concerns, feel free to create a new thread.
Have a great day,