This is making excuses for a poor decision to try and deflect the negative feedback. The “wall penetration” line of reasoning is utter nonsense. (Yes, it’s technically true, but in the real world, it is a pretty minor factor.) The real reason to include 5GHz is because 2.4GHz is so over-saturated as to be nearly useless in many homes. Especially if you live in a dense urban area (as I do).
But the 2.4GHz they have is probably built into whatever SoC chip they used for the Poly and the 2Go, and they wanted to shave some pennies and not use a more capable part. Kind of ridiculous when you consider the price premium they charge for these devices…
In which case you can still configure it to connect to a 2.4GHz SSID. It’s just plain stupid that they didn’t use a dual-band radio and offer people the best of both worlds.
So can totally vouch for this piece of support kit drastically reducing the heat generated from 2go/Hugo 2. There is still heat but on a scale of 1 to 10 it is now 2 at most, previously had been 8 or 9
This link is not working for some reason - if you search " Tincogo (2 Pack) Adjustable Iron Display Stand Easel Foldable Tablet" once you are on Amazon this will find it.
Of course I would reckon any kind of tablet/iPad support stand would do the trick.
I’ve had the Hugo 2/2go for 6 days, listening with ZMF Verité Closed headphones. Setup was pretty easy, and I like the synergy with the headphones. When it works, it’s great. But… now and then, and a lot more this afternoon, the dreaded “loading slowly” error message showed up on my phone, and tracks skipped. Both local files and Qobuz. All my other Roon gear is wired, zero problems since he was set up last summer. WiFi is Ubiquiti AmpliFi with several mesh points, one of them pretty close to where I was sitting. My 2.4GHz neighborhood is pretty crowded, but a WiFi monitoring app does not show anything horrible, my own network is between -55 and -45dBm.
I sometimes find that if I have to power off 2Go when it loses network connection, and then it can take ages before it will power on again when pressing the config button. I’ve sometimes seen it take 15 minutes before it will power on. Anybody else experience this?
I had the same problems! Now I put a Amplifi Meshpoint directly (2m…) next to my place and the problems are gone. In my case I had to plug in the meshpoint ( and wait 2 minutes…) before starting the 2go. Otherwise the 2Go connected to the Amplifi Router and did not change to the meshpoint…
Some pretty heated discussions taking place about the performance of the 2Go over on the Headfi forum. Seems many people experiencing problems, especially with poor wifi performance/network dropouts. Chord representatives look in to that forum, and have posted some comments. I have attached a link below which is from a timeframe that begins when I started to look in to the discussion a couple of weeks ago, although if you dont want to wade through that things get a bit tasty during the last few days worth of comments
Wow, that’s a long thread, not sure I want to wade through all the gunk there 2go WiFi is definitely touchy. Even walking with the Hugo2+2go from my study to the backyard, approximately 5m, caused the Roon connection to fail. Once sitting in the yard 2m from one of our AmpliFi meshpoints, perfect. I suspect that 2go WiFi stutters when it tries to switch channels/meshpoints. As another example, placing the assembly on a table with a metal leg caused stutters.
You will have noticed though that Matt from Chord has posted there will be a new firmware update rolled out today/tomorrow
“Stage one of the firmware rollout has just completed.
There are now new versions of Gofigure for Android and iOS released which will be available across the world over the next 24 hours. V 1.2.90 for Android , V2.05 for iOS.
These include bug fixes and some essential updates for the new 2Go firmware”
"Here is a basic list but primarily the update to Gofigure is to optimise operation with the upcoming firmware release.
• playlist refresh
• battery status fix (requires updated firmware)
• additional radio stations
• DSD/bit perfect volume fixing
• general prompt message fixes
• BT pin when connecting via WiFi fix
• toggle switch changes (Android)
• WiFi network settings stability improvements
• music services login credentials fix
• manual SUBMIT button in WiFi settings fix
• WiFi switching wait message"
When listening to Tidal MQA tracks via 2Go/Hugo 2 just wondering is there a recommended setting for MQA Capabilties? Mine is currently set to Renderer Only.
Hugo 2 does not do ANY MQA processing. Set it to “none” in hardware and optionally enable the MQA Core Decoder in advanced options to have Roon do the first decode.
It’s a generic default. The renderer markings SHOULD be inaudible, since they are in the lower 7 bits of the 24-bit sample. But they are still there, and if your DAC/etc is doing additional processing, who knows. The correct setting is “none”.
I have 3 DACS, two of which are MQA capable. My preference is to always let Roon do the MQA decoding and the two MQA DACs do the MQA rendering. I set my Oppo non-MQA DAC to “none.” When using it, I normally stream from Qobuz.
2go WiFi is definitely touchy. Even walking with the Hugo2+2go from my study to the backyard, approximately 5m, caused the Roon connection to fail. Once sitting in the yard 2m from one of our AmpliFi meshpoints, perfect. I suspect that 2go WiFi stutters when it tries to switch channels/meshpoints. As another example, placing the assembly on a table with a metal leg caused stutters.