Hi
@kandrey89
I've answered everything below. If you have any more questions just holla!
1) It’s one or the other – at the same time I have no idea if it is possible – I would guess probably yes but not sure – I’ve honestly never researched doing it at the same time but I’ll ask the firmware team and see what they say.
2) I’m going to break this into sub-sections just to make it easier to follow J
a. Only 1 can be controlled at a time. This is due to a whole raft of reasons (probably actually close to a boat load).
b. The WiFi name will always be JooVuuX due to SSID problems that we are currently fixing. However, we should have something implemented soon that allows you to identify different cameras in the app – this may be implemented once the cameras have been released but should be along pretty soon after.
c. Pushing the WiFi button activates the WiFi. This is the ONLY way to turn the WiFi on currently – the WiFi stays on until two minutes after the last command has been sent.
d. We are toying with the idea of having a setting that allows the WiFi to turn on automatically when you start the car engine but I’m still not sure about that yet so may wait for more user feedback.
3) Through either Mode 1 or Mode 2 screen. It replaces actual video.
Bugs
1) Whoops – I’ll get that changed today
2) That’s fair – I’ll clarify today
3) Not missing for me but one of my friends experienced a similar problem – it might have to do with some code so I’ll go over everything and make sure it’s working.
4) This has actually been updated haha I just haven’t updated the latest pictures. I’ll replace today.
5) I think your way is better – so do you mind if I use that?
Requests:
1- This feature we may remove for launch as at the moment no one uses it and only a very select few people will.
2- I’m not sure I follow – do you mean before they are selected? As once selected they turn to JooVuu Red (as my friends have come to label it)?
Compliments
1) Connection logs will provide us with a lot of information – they essentially allow for pretty accurate debugging. We also have a ‘send report’ feature that sends us information about the phone (android version, make, RAM, CPU, graphics, WiFi etc and NO identifying information at all). When the connection logs and report information are combined we can narrow down virtually to the line of code what is going wrong. This has allowed us to solve a lot of bugs very quickly as I’m sure the testers will attest to.
2) Originally our camera was going to have a passive light sensor and a laser. The laser would be able to monitor the distance for the car in front of you and give you warnings based on your speed. This was so accurate it was actually scary – but unfortunately, we could not implement it through the Ambarella SDK (we built a very basic prototype outside of the Ambarella SDK to show proof that it worked). The passive light sensor would work very similar to how you described but with a few minor differences (not disclosing as we still have plans for this in our next camera). The problem also with fitting a laser/passive light sensor, is space. The light sensor takes up virtually no power, but the laser takes up quite a bit. It’s just a balancing game.
Cheers,
Dan
