[Gr8h8m]

With these reports of temporarily bricked Polys it might be a good idea to collate any thoughts about being able to reproduce it so that others might avoid it til a fix is forthcoming.
So far there's been talk of changing the default Bluetooth pin triggering it. Anyone else?

 

[RiseFall123]

There's someone here which use Poly/Mojo combo for a stable desktop solution for the main speakers rig?

I am little afraid about the switching each time the Poly from the Mojo when I need optical, but I could live with it I think...

 

[frankraindog]

ok, I really need someone now to help me out, I don't know what do anymore.
Received Poly today.
First tried go figure app to configure. But no device was found. So I've connected to poly's own "open" wlan.
Tried to figure out what firmware poly is on but I couldn't.
So I've configured poly to connect to my wlan. which it did. I can play to poly via bubble upnp and the libery sitting in my basement.
I've inserted an sd card which is still empty in poly.
tried gofigure again. nothing tried ipad and iphone
tried to connect to bluetooth first, nothing
so i've tried to figure out which firmware poly is on again.
but trying the ip that poly has on my network I'll get ERR_CONNECTION_REFUSED

Made a scan of the device which services are online which are
mpd(tcp)
raop(tcp)
sftp-ssh(tcp)
ssh(tcp)
+ UPNP
+bonjour

so I've tried a second wlan, same here.

now I've left the device on for 3 hours connected to wlan, hoping that it will make a firmware update. but still no connection with gofigure.

so what can I do to get it working?

 

[StevieDvd]

ok, I really need someone now to help me out, I don't know what do anymore.
Received Poly today.
First tried go figure app to configure. But no device was found. So I've connected to poly's own "open" wlan.
Tried to figure out what firmware poly is on but I couldn't.
So I've configured poly to connect to my wlan. which it did. I can play to poly via bubble upnp and the libery sitting in my basement.
I've inserted an sd card which is still empty in poly.
tried gofigure again. nothing tried ipad and iphone
tried to connect to bluetooth first, nothing
so i've tried to figure out which firmware poly is on again.
but trying the ip that poly has on my network I'll get ERR_CONNECTION_REFUSED

Made a scan of the device which services are online which are
mpd(tcp)
raop(tcp)
sftp-ssh(tcp)
ssh(tcp)
+ UPNP
+bonjour

so I've tried a second wlan, same here.

now I've left the device on for 3 hours connected to wlan, hoping that it will make a firmware update. but still no connection with gofigure.

so what can I do to get it working?

You need to get Poly to shutdown, boot up and search/download for firmware, then shutdown and restart to apply firmware.

Whilst it is connected to your network Poly stays on, so you need to shut it down completely to get a clean reboot. if it has just the one Wi-Fi connection registered take it out of range and switch Poly (off making sure all lights go out). The bring it back in range, restart Poly and give it 20mins to apply the firmware.

Then connect your iPhone to the same network and launch goFigure app - and hopefully you'll be up & running.

 

[huangwan]

With these reports of temporarily bricked Polys it might be a good idea to collate any thoughts about being able to reproduce it so that others might avoid it til a fix is forthcoming.
So far there's been talk of changing the default Bluetooth pin triggering it. Anyone else?

I was thinking it might be good to fully drain my Poly while it's kinda working as to avoid the brick mode. What do you guys think.

 

[frankraindog]

You need to get Poly to shutdown, boot up and search/download for firmware, then shutdown and restart to apply firmware.

Whilst it is connected to your network Poly stays on, so you need to shut it down completely to get a clean reboot. if it has just the one Wi-Fi connection registered take it out of range and switch Poly (off making sure all lights go out). The bring it back in range, restart Poly and give it 20mins to apply the firmware.

Then connect your iPhone to the same network and launch goFigure app - and hopefully you'll be up & running.

I don't know if I get you right. I've turned mojo and poly off, all light are out and my network monitoring says it is offline now.
Now I just switch it on again an leave it on for 20 mins?

 

[Gr8h8m]

I was thinking it might be good to fully drain my Poly while it's kinda working as to avoid the brick mode. What do you guys think.

Lol! Very droll. But I was being serious!

 

[frankraindog]

Poly seems to have really bad network response. I've a unifi mesh network and poly is near to one of the access point.
64 bytes from 192.168.178.140: icmp_seq=443 ttl=64 time=62.232 ms
64 bytes from 192.168.178.140: icmp_seq=444 ttl=64 time=78.524 ms
64 bytes from 192.168.178.140: icmp_seq=445 ttl=64 time=98.011 ms
64 bytes from 192.168.178.140: icmp_seq=446 ttl=64 time=3.430 ms
64 bytes from 192.168.178.140: icmp_seq=447 ttl=64 time=38.108 ms
64 bytes from 192.168.178.140: icmp_seq=448 ttl=64 time=63.298 ms
64 bytes from 192.168.178.140: icmp_seq=449 ttl=64 time=5.310 ms
64 bytes from 192.168.178.140: icmp_seq=450 ttl=64 time=105.307 ms
64 bytes from 192.168.178.140: icmp_seq=451 ttl=64 time=22.978 ms
64 bytes from 192.168.178.140: icmp_seq=452 ttl=64 time=44.365 ms
64 bytes from 192.168.178.140: icmp_seq=453 ttl=64 time=67.231 ms
64 bytes from 192.168.178.140: icmp_seq=454 ttl=64 time=89.692 ms
64 bytes from 192.168.178.140: icmp_seq=455 ttl=64 time=111.655 ms
64 bytes from 192.168.178.140: icmp_seq=456 ttl=64 time=27.896 ms
64 bytes from 192.168.178.140: icmp_seq=457 ttl=64 time=49.553 ms

macbook to router same access point but a few meters away

64 bytes from 192.168.178.1: icmp_seq=184 ttl=64 time=6.916 ms
64 bytes from 192.168.178.1: icmp_seq=185 ttl=64 time=6.491 ms
64 bytes from 192.168.178.1: icmp_seq=186 ttl=64 time=3.677 ms
64 bytes from 192.168.178.1: icmp_seq=187 ttl=64 time=2.430 ms
64 bytes from 192.168.178.1: icmp_seq=188 ttl=64 time=3.491 ms
64 bytes from 192.168.178.1: icmp_seq=189 ttl=64 time=2.965 ms
64 bytes from 192.168.178.1: icmp_seq=190 ttl=64 time=2.346 ms
64 bytes from 192.168.178.1: icmp_seq=191 ttl=64 time=3.697 ms
64 bytes from 192.168.178.1: icmp_seq=192 ttl=64 time=5.455 ms
64 bytes from 192.168.178.1: icmp_seq=193 ttl=64 time=6.070 ms
64 bytes from 192.168.178.1: icmp_seq=194 ttl=64 time=2.088 ms
64 bytes from 192.168.178.1: icmp_seq=195 ttl=64 time=1.960 ms
64 bytes from 192.168.178.1: icmp_seq=196 ttl=64 time=3.587 ms
64 bytes from 192.168.178.1: icmp_seq=197 ttl=64 time=2.250 ms
64 bytes from 192.168.178.1: icmp_seq=198 ttl=64 time=1.828 ms
64 bytes from 192.168.178.1: icmp_seq=199 ttl=64 time=4.561 ms



6

 

[Priaptor]

Poly seems to have really bad network response. I've a unifi mesh network and poly is near to one of the access point.
64 bytes from 192.168.178.140: icmp_seq=443 ttl=64 time=62.232 ms
64 bytes from 192.168.178.140: icmp_seq=444 ttl=64 time=78.524 ms
64 bytes from 192.168.178.140: icmp_seq=445 ttl=64 time=98.011 ms
64 bytes from 192.168.178.140: icmp_seq=446 ttl=64 time=3.430 ms
64 bytes from 192.168.178.140: icmp_seq=447 ttl=64 time=38.108 ms
64 bytes from 192.168.178.140: icmp_seq=448 ttl=64 time=63.298 ms
64 bytes from 192.168.178.140: icmp_seq=449 ttl=64 time=5.310 ms
64 bytes from 192.168.178.140: icmp_seq=450 ttl=64 time=105.307 ms
64 bytes from 192.168.178.140: icmp_seq=451 ttl=64 time=22.978 ms
64 bytes from 192.168.178.140: icmp_seq=452 ttl=64 time=44.365 ms
64 bytes from 192.168.178.140: icmp_seq=453 ttl=64 time=67.231 ms
64 bytes from 192.168.178.140: icmp_seq=454 ttl=64 time=89.692 ms
64 bytes from 192.168.178.140: icmp_seq=455 ttl=64 time=111.655 ms
64 bytes from 192.168.178.140: icmp_seq=456 ttl=64 time=27.896 ms
64 bytes from 192.168.178.140: icmp_seq=457 ttl=64 time=49.553 ms

macbook to router same access point but a few meters away

64 bytes from 192.168.178.1: icmp_seq=184 ttl=64 time=6.916 ms
64 bytes from 192.168.178.1: icmp_seq=185 ttl=64 time=6.491 ms
64 bytes from 192.168.178.1: icmp_seq=186 ttl=64 time=3.677 ms
64 bytes from 192.168.178.1: icmp_seq=187 ttl=64 time=2.430 ms
64 bytes from 192.168.178.1: icmp_seq=188 ttl=64 time=3.491 ms
64 bytes from 192.168.178.1: icmp_seq=189 ttl=64 time=2.965 ms
64 bytes from 192.168.178.1: icmp_seq=190 ttl=64 time=2.346 ms
64 bytes from 192.168.178.1: icmp_seq=191 ttl=64 time=3.697 ms
64 bytes from 192.168.178.1: icmp_seq=192 ttl=64 time=5.455 ms
64 bytes from 192.168.178.1: icmp_seq=193 ttl=64 time=6.070 ms
64 bytes from 192.168.178.1: icmp_seq=194 ttl=64 time=2.088 ms
64 bytes from 192.168.178.1: icmp_seq=195 ttl=64 time=1.960 ms
64 bytes from 192.168.178.1: icmp_seq=196 ttl=64 time=3.587 ms
64 bytes from 192.168.178.1: icmp_seq=197 ttl=64 time=2.250 ms
64 bytes from 192.168.178.1: icmp_seq=198 ttl=64 time=1.828 ms
64 bytes from 192.168.178.1: icmp_seq=199 ttl=64 time=4.561 ms



6

YUP I get very similar results.

I was told to attach a second dedicated wireless router to my mesh and set it up as a dedicated 2.4Ghz just for POLY and I get the same results with the same dropouts.

Nothing has changed for me with firmware upgrades although with my replacement POLY I am definitely getting less dropouts than before

 

[Staxton]

Poly seems to have really bad network response. I've a unifi mesh network and poly is near to one of the access point.
64 bytes from 192.168.178.140: icmp_seq=443 ttl=64 time=62.232 ms
64 bytes from 192.168.178.140: icmp_seq=444 ttl=64 time=78.524 ms
64 bytes from 192.168.178.140: icmp_seq=445 ttl=64 time=98.011 ms
64 bytes from 192.168.178.140: icmp_seq=446 ttl=64 time=3.430 ms
64 bytes from 192.168.178.140: icmp_seq=447 ttl=64 time=38.108 ms
64 bytes from 192.168.178.140: icmp_seq=448 ttl=64 time=63.298 ms
64 bytes from 192.168.178.140: icmp_seq=449 ttl=64 time=5.310 ms
64 bytes from 192.168.178.140: icmp_seq=450 ttl=64 time=105.307 ms
64 bytes from 192.168.178.140: icmp_seq=451 ttl=64 time=22.978 ms
64 bytes from 192.168.178.140: icmp_seq=452 ttl=64 time=44.365 ms
64 bytes from 192.168.178.140: icmp_seq=453 ttl=64 time=67.231 ms
64 bytes from 192.168.178.140: icmp_seq=454 ttl=64 time=89.692 ms
64 bytes from 192.168.178.140: icmp_seq=455 ttl=64 time=111.655 ms
64 bytes from 192.168.178.140: icmp_seq=456 ttl=64 time=27.896 ms
64 bytes from 192.168.178.140: icmp_seq=457 ttl=64 time=49.553 ms

macbook to router same access point but a few meters away

64 bytes from 192.168.178.1: icmp_seq=184 ttl=64 time=6.916 ms
64 bytes from 192.168.178.1: icmp_seq=185 ttl=64 time=6.491 ms
64 bytes from 192.168.178.1: icmp_seq=186 ttl=64 time=3.677 ms
64 bytes from 192.168.178.1: icmp_seq=187 ttl=64 time=2.430 ms
64 bytes from 192.168.178.1: icmp_seq=188 ttl=64 time=3.491 ms
64 bytes from 192.168.178.1: icmp_seq=189 ttl=64 time=2.965 ms
64 bytes from 192.168.178.1: icmp_seq=190 ttl=64 time=2.346 ms
64 bytes from 192.168.178.1: icmp_seq=191 ttl=64 time=3.697 ms
64 bytes from 192.168.178.1: icmp_seq=192 ttl=64 time=5.455 ms
64 bytes from 192.168.178.1: icmp_seq=193 ttl=64 time=6.070 ms
64 bytes from 192.168.178.1: icmp_seq=194 ttl=64 time=2.088 ms
64 bytes from 192.168.178.1: icmp_seq=195 ttl=64 time=1.960 ms
64 bytes from 192.168.178.1: icmp_seq=196 ttl=64 time=3.587 ms
64 bytes from 192.168.178.1: icmp_seq=197 ttl=64 time=2.250 ms
64 bytes from 192.168.178.1: icmp_seq=198 ttl=64 time=1.828 ms
64 bytes from 192.168.178.1: icmp_seq=199 ttl=64 time=4.561 ms



6

I'd be curious to know what make and model WiFi/Bluetooth chip is being used in Poly? Perhaps Chord can tell us?

 

[frankraindog]

so I've tried what steviedvd told me to. same as before.
so now I've wasted about 5 hours on this, tomorrow I will return this little pice of crap to the dealer

 

[StevieDvd]

so I've tried what steviedvd told me to. same as before.
so now I've wasted about 5 hours on this, tomorrow I will return this little pice of crap to the dealer

Sorry about that seems it's more a network thing then.

If it helps I have done my firmware updates at work by using iPhone hotspot as I'm not allowed to connect unauthorised equipment to the network. If you can get access to Poly web page and add your iPhone details that could get you around the network issue to do the firmware update. Whether that improves connection to the routers you have is a different matter.

 

[Matt Bartlett]

so I've tried what steviedvd told me to. same as before.
so now I've wasted about 5 hours on this, tomorrow I will return this little pice of crap to the dealer

Before going back to the dealer please can you PM me or contact info@chordelectronics.co.uk so we can check whether your Poly has successfully
contacted the update server to update the firmware. Then we can help your further.

 

[frankraindog]

Sorry about that seems it's more a network thing then.

If it helps I have done my firmware updates at work by using iPhone hotspot as I'm not allowed to connect unauthorised equipment to the network. If you can get access to Poly web page and add your iPhone details that could get you around the network issue to do the firmware update. Whether that improves connection to the routers you have is a different matter.

so what you think is wrong with my network, instead of something being wrong with the poly?

I can promise that the network is setup correct as my daily business is It professional and the unifi mesh is some of the best hardware on the market today which allows to stream 4k video to every corner oft the house.

I'll try the iphone hotspot , regardless to the matter that i think it is useless.
but i welcome you trying to help.
but if the poly is not able to update in a normal enviroment it stays crap in my opinion and will go back to where it came, if it updates or not

iphone hotspot didn't work out same as before.
so before this poly hits the wall it finds it way back to where it came from

 

[NYanakiev]

@Matt Bartlett

I just had a “pleasant” moment with Poly. It has generally been smooth sailing for me since the release of GoFigure.

After two days of no Poly action, it first refused to connect to my home wifi. Things worked out after rebooting my router but Poly kept misbehaving- it was alternating blue/green every 10-15 seconds and refusing to connect to Glider.

I tried reinstalling Glider (twice)- the only thing that helped was doing a factory reset- the whole process took me 30 minutes!!

The Chord contractor clearly has some bug squishing to do!