Shadow Dash open when charging

[LT401Vette]

But the toast messages appear correct?
It is recognizing the charge and discharge states, just does not fall asleep and does not disconnect?
If you exit shadow dash with the FTDI plugged in does it fall asleep?

[kizzoalfa]

But the toast messages appear correct?
It is recognizing the charge and discharge states, just does not fall asleep and does not disconnect?
If you exit shadow dash with the FTDI plugged in does it fall asleep?

Hi,

it recognize the states, you can see from the log as well.

As I see it will go to 30% backlight but fails to sleep.

After I exit SD it goes to sleep, yes. Also exit BT.

In case I exit, it goes to 30% backlight becasue there is no screen activity and than goes to sleep.

Zoltan

[kizzoalfa]

But the toast messages appear correct?
It is recognizing the charge and discharge states, just does not fall asleep and does not disconnect?
If you exit shadow dash with the FTDI plugged in does it fall asleep?

Hi,

it recognize the states, you can see from the log as well.

As I see it will go to 30% backlight but fails to sleep.

After I exit SD it goes to sleep, yes. Also exit BT.

In case I exit, it goes to 30% backlight because there is no screen activity and than goes to sleep.

Zoltan

Hi Phil,

May this help.

As I checked today when I plug my adapter (Lava one) into the tablet without any external connection to MS3 or to the charger, the tablet recognize it as "USB connector connected".

I than connected to Lava adapter to MS3, and also to the charger (no charge yet.).

Launched MS3. No indication about FDI connection, tablet stay offline, and turn screen off as screen timeout dictate.

Turned ignition on. Tablet come back from sleep, connects to MS3, going online (first time this takes about 10s.)

Turned ignition off. MS3 recognoze and display: discharging. Right after this in 1-2s it say connected to FTDI device and not going to sleep.

I can turn IGN back on, MS3 start (much faster, 1-2s) and everything is fine as far as connection.

So I can confirm, that the tablet recognizes the power states but somehow forcing to connect even in discharge mode.

I also checked if required I can root the tablet.

Thanks,

Zoltan

[kizzoalfa]

But the toast messages appear correct?
It is recognizing the charge and discharge states, just does not fall asleep and does not disconnect?
If you exit shadow dash with the FTDI plugged in does it fall asleep?

Hi, some video about the sequence. Not the best movie but I hope it help to understand some more the problem.

https://youtu.be/mC0tpNbQ_4o

[LT401Vette]

Perhaps I should get you a build that does not launch on FTDI connect. I wonder if that is triggering the reaction.

[kizzoalfa]

Perhaps I should get you a build that does not launch on FTDI connect. I wonder if that is triggering the reaction.

If possible, yes, I would appreciate it. You can email it to kizzoalfa@yahoo.com for trial but it can be also an option and the future releases can keep it if it is the solution, especially if others report the same issue.

(Also does it possible to remove the not connected notification from the dash screen and just indicate it in some small icon or something?)

Thanks,

Zoltan

[LT401Vette]

(Also does it possible to remove the not connected notification from the dash screen and just indicate it in some small icon or something?)

Yes on a permanent install I can see where that would be desirable.

[kizzoalfa]

(Also does it possible to remove the not connected notification from the dash screen and just indicate it in some small icon or something?)

Yes on a permanent install I can see where that would be desirable.

Hi I saw 1.32 is out, but it has no change in connectivity:( Can you please make some custom build for trial as you mentioned above?

Thanks,

Zoltan

[LT401Vette]

I did make a change I was hoping would help your scenario, but couldn't test it.
I'll try to get you a build with launch on ftdi connect disabled. Maybe that will work..

[kizzoalfa]

I did make a change I was hoping would help your scenario, but couldn't test it.
I'll try to get you a build with launch on ftdi connect disabled. Maybe that will work..

Hi,

unfortunately it does the same as before. I see the same, if the autoconnect is disabled than it should work.

Thanks,

Zoltan

[LT401Vette]

I just sent you a 1.32a that has launching SD on USB connect turned off.

For me it does not wake up now when connecting an FTDI cable, but does when connecting power. I am using a tablet where it is the same port though.

[kizzoalfa]

Hi Phil,

first of all thank you very much for the support.

I have tried the 1.32a and it goes to sleep but it does becasue it looks like right after discharging the Android system loose / force remove the paired USB device.

When I first time connect to MS3 than a normal window appear from systems that "Allow the app shadowdash to access USB device?" I can click Ok and mark "remember my setting" but it looks like the window come up periodically and does not remember my setting, however after a while it acept and SD start to connect, show the message found FTDIxx.

As soon as I remove charge, the discharging message appear and also in approx. 2 sec the window come up "Allow the app shadowdash to access USB device?". If I do nothing than it goes to sleep with the window on the screen, however when I turn charge back on, the message still there and asking for rights, periodically, and sometimes a message: no FTDI device / USB device found.

I do not know if it help but I have MSdroid also installed. IN case of the first connect when I accept that SD can use the USB device sometimes it also asked rights - right after I allowed SD - for MSdroid.

So it is looks like that once the default USB pairing is removed it ask a new one, however sleep is possible but connection became broken. (Also app re - connection time is suffering.)

Thanks,

Zoltan

[kizzoalfa]

Hi Phil,

as I mentioned to you the 1.32 version looks fine and what it should after I made some HW modification on my table charge interface.

I tested it for 1 hour and sleep, wake up is fine and follow ignition control.

I am very happy and also showed the dash in my car to my colleagues. They really liked it as well.

As it looks like this issue is solved, can you investigate the following for SD to enhance functionality:

- Trip and economy fields

- Odometer with some save into a variable at ignition OFF event and loaded at ignition on event?

- Some correction on dash layout: remove not connected message from the main screen and show it as an icon somewhere, also does it possible to change the status messages (like charge, FTDI conn. etc.) to some small, or let the user turn them off and have just some high level message about the status like: Key on, MS3 connected, initializing connection, online, Key off, offline.

I also installed this to change the 15s timeout to 5s after ignition OFF: https://play.google.com/store/apps/deta ... eentimeout

Thanks,

Zoltan

[LT401Vette]

I think it still needs a tweak to the initial startup logic as you pointed out earlier, it will try to connect on startup even if there is no power.

I am over due to add the Trip and Economy fields.

[kizzoalfa]

I think it still needs a tweak to the initial startup logic as you pointed out earlier, it will try to connect on startup even if there is no power.

I am over due to add the Trip and Economy fields.

Hi,

I made a change in my HW setup and I added a small relay controlled by charge. In case there is no charge I open my tablets USB_ID pin which is pulled to GND by default by 20kohms.

With the change the tab does not want to connect after discharge state - my previous connected to FTDI device after discharge is not present any more and sleep is possible.

Did you mean this section of the startup logic to tweak or is there some other change you would add?

Did you see some other behavior as well?

Thank you very much for your time and support.

Zoltan

[LT401Vette]

What I have seen is if I have the power disconnected, then open SD it will start trying to connect to the controller even if it doesn't lock the screen.

[kizzoalfa]

What I have seen is if I have the power disconnected, then open SD it will start trying to connect to the controller even if it doesn't lock the screen.

Hi Phil,

do you see any realistic plan when can you release some modified version of the SD including some of the changes we discussed (Trip meter section, repair Speed display in kph, connection issues you noticed, some screen fine tuning if not connected with status icon messages)?

Thanks,

Zoltan

[LT401Vette]

As soon as I get the next TS Release into beta testing...
This has been going longer than expected...

[kizzoalfa]

As soon as I get the next TS Release into beta testing...
This has been going longer than expected...

Hi Phil,

I have tested SD wired into my car for 5 days. I found approx. 10 times that during re - connection SD forget to connect, and a message: SD did not respond, do you want to send report appeared.

This happened after I left the tablet in the car for hours in discharge state.

Sometimes I found SD not following the discharge state and does not turn display off after 15s. I need to quit SD in this cases and than go to system / display settings, change disp. timeout to 30s than back to 15s. After this ceremony SD recognize the charge and follow toast messages.

I also noticed that during every 2nd HOT restart (SD did not restarted just power cycled) the app is very slow and need about 10 - 15 s to refresh display in close to real time.

I had approx. 9 time a failure, which is something like burn 9 page failed right after I turned IGN off.

I attached an appdebug from today. May it is useful for you.

By looking into the datalog and have some understanding on SD I see that you completely check the tune after startup. Can this be part of the slow startup? What is the slow part here compared to TS? In the past I built a serial port based HW which requested data from MS3 by sending the command A. I know it is a different animal but can SD be speed up by entering into some low level Dashboard mode? For example I do not want to upload tune files, share etc. Neither want to tune any parameters via SD. Do you see that by some way it can be simplified and get a benefit from this to gain faster connection, display rate, appear more real time?

I hope you can be successful with TS release and fix the issues with SD.

Thanks for your support.

Zoltan