jespertt

6 ms·

1.
by jespertt 4y ago
For some reason i can't reply to your next post, dpratt - so i'll reply here. I'm not intending to blame the user. I am merely saying that this is not something that all users that set their output above 5 experience. It is d
2.
by jespertt 4y ago
Update: we now have a customer in our US Facebook Community saying that reupdated fixed his issue. ''My upgrade failed initially and impeded speaker output. Allowing the upgrade to run again resolved the issue without any further
3.
by jespertt 4y ago
Nah - that's just not true. We've pushed this update to tens of thousands of units over the past week - and we have not seen this issue reported before gHuntleys post, and then subsequently in the comments to his post in our commu
4.
by jespertt 4y ago
Previously, i mentioned the notion of it being a data corruption issue. We have integrity verification, so this is extremely unlikely, but as it is an easy check, we recommend trying this out. If you try to re-upgrade, and it skips the “tra
5.
by jespertt 4y ago
A few notes regarding the latest firmware: The sound profiles have not been changed at all. The playback time is exactly the same as before, i.e. 5 hours on max volume in Power mode. (confirming the SPL is the same) The settings for the woo
6.
by jespertt 4y ago
We have integrity verification, so this is extremely unlikely, but as it is an easy check, we recommend trying this out. If you try to re-upgrade, and it skips the “transferring” step and goes directly to “Ready to patch”, it means that the
7.
by jespertt 4y ago
Alright, a quick update after speaking with my tech team. A while ago, we realised we are seeing some failed tweeters in Gen3. The issue occurs when a. playing with the battery and the power on the battery is too low, or b. playing with onl
8.
by jespertt 4y ago
A while ago, we realised we are seeing some failed tweeters in Gen3. The issue occurs when a. playing with the battery and the power on the battery is too low, or b. playing with only the charger on high volume. In those cases, there is a p
9.
by jespertt 4y ago
Will liaise with the engineering team and revert!
10.
by jespertt 4y ago
Will liaise with the engineering team and revert!
11.
by jespertt 4y ago
Will liaise with the engineering team and revert!
12.
by jespertt 4y ago
Fair point. As a note, it's definitely not all users that are experiencing the problem, but I will liaise with our engineers and revert!
13.
by jespertt 4y ago
This is where it gets a bit more technical; our support team member mistaked the speaker for SOUNDBOKS GO (our other version), where we have pushed out an audio update. In that audio update, there is implemented a tweeter protection mechani
14.
by jespertt 4y ago
Hi Ghuntley and everyone, Jesper, CEO and cofounder of SOUNDBOKS here. Ghuntley, I’m sorry to hear about you and other people’s issues after the latest update. This is new information to us, and is definitely not something that is intended.
15.
Soundboks (YC W16) hiring a Logistics Coordinator(s3-eu-west-1.amazonaws.com)
1 points by jespertt 8y ago
16.
Soundboks (YC W16) is looking for Full Stack Developers(images.soundboks.com)
1 points by jespertt 9y ago
17.
Soundboks is hiring a front-end developer(images.soundboks.com)
1 points by jespertt 9y ago