Yes, exactly @justin ! That’s exactly what I’m saying! 
Finally someone who understands me… 
1 Like
I’ve found that it’s probably a combination of a technical problem and a software problem in terms of usability. It’s related to the fact that if you have Spotify connected to your r1 and while you’re entering your prompt for e.g. SunoAI, the scroll wheel suddenly jumps (due to the low sampling rate or the sampling position if it’s in an unfortunate position on a trigger point), then that’s it for the prompt and Spotify starts playing the last song. If you try to end it now, the situation that has happened to me several times now, which I described above, can occur. For this reason, unfortunately, that’s it for Spotify on my r1 for now, because otherwise I can’t use it for anything else.
1 Like
In case you definitely want to use Spotify on your r1 and with r1 as I also want to use e.g. SunoIA. As a workaround, I would simply suggest fixing the scroll wheel with adhesive tape so that it cannot jump if, for example, the problem should be not solved at the software level.
1 Like
That’s good, I use it, it works!
1 Like
Definitely a harsh criticism of rabbit AND r1 users.
2 Likes
Just for you. @RaRa (
) Nobody is perfect. 
Sorry… @everyone. 
(But it is true…)
I think we all should be able to recognize your mistakes and if possible, try to undo them, instead of continuing to go in the wrong direction. @rabbit
1 Like
Hey guys, it would be really great if more of you would vote here. Simply so that at the end we can clearly see whether there are many or few users who are currently having problems with the usability of r1 because of this Morse code story.
So please everyone vote: Thank you very much!
1 Like
I voted for No, even if I don’t have problems using this and I find it fast and better than powering the device off by pressing the button for 60 seconds. Also, it fixed the problem of the r1 powering off from pressing the button for a long time on a large inquiry.
Why did I vote for No? Because the question was “Is it intuitive?”. And no, it’s not. There is nowhere to see what I have to press except for some messages in this forum. Maybe the team can just add the info to the r1 itself, like, asking our r1 to power off and getting a reply saying it can’t do it by voice command but we can easily power it off by pressing PTT 8 times.
This way we can have voice instructions if we don’t know or forgot how to use the PTT quick actions.
4 Likes
I once asked Beta Rabbit (on my r1) what it thought about it…
I think it speaks for itself and is an absolutely correct and clear answer.
Therefore, this should definitely be reversed, because otherwise r1 will never be able to fulfil its purpose. @rabbit
2 Likes
If you can afford it, it’s best to take a few steps back and make it better than it is. That’s just good advice. On the other hand, if that’s not possible, then another really well-intentioned piece of advice would be not to overdo it with the multiple assignments of the PTT button, although I personally think that this point has unfortunately already been far exceeded. 
@rabbit
2 Likes
This is also related to this. There are several technical challenges and challenges that affect the purpose of r1. If you are not careful, these can lead to a real disaster. It is therefore more important not to work against them yourself, because otherwise r1 will eventually lose its purpose, even for those who love it. Therefore, the highest priority should always be really intuitive usability, because this is one of the pillars on which the idea of r1 is based and if you cut off this pillar, or have already cut off one, then the whole idea becomes unstable. @rabbit
1 Like
this is a little hard to answer with such short time using it. I like the simplicity of it but i wish it could feel more natural - i can’t recall how many times i accidentally took photos recently just trying to get out of vision mode.
2 Likes
Thank you, that’s exactly the problem with the whole thing. If perfectly healthy people have problems with it, what about people with serious motor problems?
I think the operation should always follow the same line. For example, to exit a function it should ALWAYS be possible to scroll up and select the back button by pressing the PTT button once and under no circumstances via this fatal Morse code thing (press the PTT button X times).
1 Like
Kids, I’ll tell you one thing. I won’t be able to come up with any more good suggestions until this bug is fixed. I really mean that because it won’t make sense for me to keep making constructive suggestions when something as fundamental as this is wrong. I really mean that. @rabbit
Besides, I think it would only be a matter of politeness if I could let one of you bunnies here express your opinion. @jesse
1 Like
so the current assign of ppt button are as follows:
- press and hold to talk
- double tap to turn on/off camera
- five tap to soft reset
- turn off the device
my opinion - for most frequent uses it’ll be just press and hold to talk and double tap to vision.
our team is evaluating a UI/touch refactor that’ll release some of the PTT duties. we will share more details later.
11 Likes
Thank you for the answer @jesse (i’ am a fan of you and i have big respect), but i would have liked a little more insight, but thanks anyway.
I’m very excited, probably as much as about 50% of all Rabbit users who love it as much as I do and don’t want it to be messed up.
Because it’s just too important for that.
1 Like
This might also be of interest.
1 Like
Ask it about a device that has a small hidden needle hole to reset. You can scroll down through the menu or ask by voice to shut down, and you will be redirected to the power-down menu, where you have to confirm that you want that manually. It is not a prank of your mate saying, “Alexa, buy a million condoms with prime today delivery.” Pressing eight times is for emergencies; you can shut it down normally via the device menu.
2 Likes
Nevertheless, it is not intuitive.
1 Like