Please add for all RealDasher android version
if Intent.SCREEN_ON
(I tried to do this on android in other ways, but the triggers don’t work for 10 seconds after the app wakes up from sleep.)
please support this post with likes, who will also solve the problem when the device comes out of sleep.
Must I remind you that I did this for you already and it did not fix the sleep mode issues on your device.
I can make this an option to settings, but as said, it will probably not fix the issues you have.
Falcom , Can you explain to me what problem is happening?
Android start with no delay
but triggers if try fix it start work afer 10 sec - it is too much for perfect
10 sec is ok fof all but intro and sweep is critical
Is the introduction by configuration or actions and triggers?
My project uses Android Car and it works perfectly, 10 seconds and everything is ready, introduction and scan.
10 sec too much , for perfect dashboard
Try to explain very detailed what you mean with 10 seconds?
In DEATHFISH 2 Joying and Ainavi Android radios connections are active and connected before screen fade-in is complete (<1 second) 100% of the time.
From what you try to explain I understand that it takes 10 seconds before triggers start running. That just cannot be true if you see any movement of the screen, as triggers are updated in UI thread. It could be somehow wrongly configured triggers, I know that its easy to do.
I hope you can see my issue here. I used hours of my time to make you a custom version with SCREEN_ON rebooting the app. It did not help on your issue. I’d like to help, but I have trouble understanding your explanations of the issue. I just cannot afford spend hours and hours trying to fix an issue that I do not fully understand.
I absolutely understand you, and I will try to describe the problem in as much detail as possible- in next letter . in order for you to assess the problem, I am sure that in the community with RealDasher we will raise funds to pay for your time.
I don’t think raising funds from community to fix an issue with your custom device is the right thing to do. Please stop pushing extra “motivation” to my way. It usually has an opposite effect.
Falcon, my project breaks the connection with the Arduino as soon as it goes into standby mode, every time it restarts it communicates with the Arduino, it starts with introduction then scanning, with the device you use the time to complete the cycle should be a maximum of 7-8 seconds. I use introduction via settings.
Arduino is not protected from interference when transferring to usb. I realized this from my own experience, and later I got acquainted with the description of the USB operation principle.
I didn’t quite understand what you described, when entering standby mode my project cuts the 5v line from the USB, thus closing RealDash, leaving standby mode it returns the 5v and starts the complete cycle. I’ve never had a problem with Arduino USB communication.