Music sanctuary, Zeppelin and co, E1 personal audio. I have HEARD that E1 sells Parallel import units, but that is still unconfirmed.
Music Sanctuary has a 10% off the player as of now, so if you would like to get one, do it ASAP. It's selling for around SGD1260, which converts to about USD894. Zeppelin and Co also has an early bird discount running for the player. I got mine from Music Sanctuary anyways
From what i've heard, all the places you mentioned and actually more unlisted ones sell parallel import units too! If looking for "low-balling" prices.
The ones selling at E1 are legit stocks from the local distributor, checked with the local distributor in sg. So that should put E1 in the safe list to get Dx200, same goes for Zeppelin and Music Sanctuary.
Remember, a rumor is a rumor that does no one (including messenger) any good. if we share something that's unverified, we're just part of the problem, not the solution.
Unstop burning in for 12hr now, device is soooooooo hot
Use any normal earpiece to burn in the player. The included burn in cable when in use, does heats up the player alot.
Also if charging and playing (using burn in cable) at the same time, also heats up the player significantly.
Anyone having issues with the DX200 screen turning on? It's happened 2 or 3 times to me now. I was getting ready for my evening stroll, plugged my IEMS in and tried to turn the screen on, nothing. Held the power down to try and turn it on, as if it was off (it shouldn't have been it was on literally 3 minutes before), nothing. Unplugged iems. Tried both again. Nothing. Tried holding power button for 10 seconds. Nothing. Waited for 30 secs, tried powering it up, and it turned on. Screen shut off, I plugged my IEMS in again, nothing. Had to try again. Got it to work. It's been fine since. Weird.
Had that issue here too. funny thing is once the charging usb-c cable is removed from the player, the screen goes active. tried twice with same result.
the charging icon also doesn't appear when plugged back to power supply.
i suspect it was due to the player auto powering off from sleep mode that may have triggered this behavior. Once i get to power on the device and power off the device properly (instead of letting it auto power off), the normal behavior resumes. Do give it a try and see if it works.
Hi Paul, may need your help to log this in as a potential bug of the auto off function feature.