[timothy.reed]

I have ~2K flac and mp3 files in a /music/artist/album file structure managed by beets. I can see my folders in Tangera's file browser however the music player only shows ~10 artists. To see what was on the console, I tried connecting to the serial port using Serial on a Mac, however when I turn on my Tangara I get 5 bytes of garbage on the port, followed by the device rebooting. I also tried reindexing via the settings app, but no change.

Thinking maybe bad file name was causing the problem, I found and removed an album with square braces in the title; other than that, nothing jumps out.

Any suggestions on what I might look at? Thanks!

[ailurux]

We're aware of a few issues that currently cause tracks to not be indexed correctly. Here's some things that might help:

- Make sure your files are in a "Music/" directory at the top level. This is case-sensitive at the moment, so make sure that the case matches. (A fix for the case-sensitivity is coming, but not released yet).

- Make sure your music has tags, we use tags in the file to build the database. We would like to have better support for inferring things from filepaths, but it's not very well supported right now.

To get better serial output, try setting the baud rate to 115200. You could also use `idf.py monitor` with a development build of the firmware. That can help to debug this further if the previous steps don't fix it.

[timothy.reed]

Upping the baud rate to 115200 allowed me to see log data off the port - thank you!  When connecting, my Tangera goes dark/unresponsive and I get this response on the port:

ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x7 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2))
waiting for download

After disconnecting it from the USB port, it takes a couple of hours despite of toggling the lock/power switch or removing/reinserting the SD for the player to regain responsiveness and display. I don't know enough to find the port interface in the firmware code but thought I'd pass that on. 

I was also able to rebuild the library. I manually deleted .tangara-db and .queue.playlist instead of running Settings> Database> Update now and it rebuilt correctly.

Thanks again!

[jacqueline]

Upping the baud rate to 115200 allowed me to see log data off the port - thank you!  When connecting, my Tangera goes dark/unresponsive and I get this response on the port:

ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x7 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2))
[color=#666666][font=sans-serif]waiting for download

Ah, this sounds like your device was being put into firmware update mode. The RTS/DTS signals are used for this, which *normally* isn't an issue because most serial interfaces don't really touch them. Can I ask when program you were using to view the serial logs? Maybe we should warn folks about this.

[timothy.reed]

Upping the baud rate to 115200 allowed me to see log data off the port - thank you!  When connecting, my Tangera goes dark/unresponsive and I get this response on the port:
ets Jul 29 2019 12:21:46
rst:0x1 (POWERON_RESET),boot:0x7 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2))
[color=#666666][font=sans-serif]waiting for download

Ah, this sounds like your device was being put into firmware update mode. The RTS/DTS signals are used for this, which *normally* isn't an issue because most serial interfaces don't really touch them. Can I ask when program you were using to view the serial logs? Maybe we should warn folks about this.

I used the Mac third party app Serial 2, which seems to be the most popular Mac app for interacting with serial ports, to connect. I've attached a screenshot of my settings. Fair warning that I haven't had to connect to a serial device in decades so may have data bits, RTS/CTS, etc. all wrong.

Now that I know the correct port speed, I was able to use screen to connect. Here's the command line I used:
% screen /dev/cu.usbmodem2101  115200
This gives me a "→" prompt; "help" shows me the various commands "lua", "luarun", etc. To test I ran "haptic_effect" figuring it would be harmless 'til I realized I didn't know how to terminate a Tangera console command. Control-a k dumped me out of screen and unplugging my Tangera and turning it off stopped the haptic element from doing its thing, but there's probably a better way to do this.

Hope this is useful. Please let me know if there's anything else I can do to help.