[taivlam]

Is this considered the default orientation for Tangarine's buttons?

To the extent I get to define a default, sure? It means that in the default button layout, the triangle is a back arrow and the X is the stop/clear queue button, which makes sense to me. But it fits in any of the 8 possible orientations.

Which functions are the square and circle buttons set to?

[morl0ck]

Not currently, but there could be!

I think what I'm going to do is do a quick DFM pass, send off a small batch of the boards to be professionally assembled to whatever extent seems like a good trade of money for time (ugh, I'd pay someone solely to reliably solder the FFC connector on for me), and throw them on... Tindie? Do people still use Tindie? Is there a thing people use instead of Tindie? Is there a thing like CrowdSupply but just the warehouse part and not the crowdfunding part?

I don't expect too many more to ever be made, and I'm going to be moving later this year so I don't want to commit to too many more projects, but there are a couple more people who want one and can't build one themselves, and this seems like a reasonable thing to do.

Thanks for the reply. Yes, people do still use tindie

[emily]

Which functions are the square and circle buttons set to?

In the default config, long-pressing bottom-left clears the queue, and pressing bottom-right goes to the now-playing screen.

[emily]

Got a DM about this today, so update:

I have all the parts on hand to assemble a second batch of these. Average of what people sent me for the pay-what-you-want batch was around $50 shipped, so that's probably what it'd be for a fixed-cost batch?

However, I'm moving across the country sometime in the next few months, and that and related things have been taking up all my free time and mental energy. So I don't know at the moment whether I'll get back to this before then. I might, but I might not. I'm not going to take anyone's money before I have finished things to sell them, though; there isn't anywhere near enough money involved in this particular project to justify crowdfunding or paid preorders.

(This is also why the Lua input PR has been languishing recently. There's one very tricky memory corruption bug remaining, and I have not had the chance to sit down and figure out wtf is happening. Sorry about that.)

[taivlam]

(This is also why the Lua input PR has been languishing recently. There's one very tricky memory corruption bug remaining, and I have not had the chance to sit down and figure out wtf is happening. Sorry about that.)

I got a little anxious with my Tangarine lying around and I wanted to try to at the very least determine if the faceplate device works.  (@redshift got Tangarine to work, so I thought maybe I could get custom firmware to work.)  I felt like a fish out of water trying to build the Tangarine firmware from source.

1. Before I started, I installed `esp-idf` from the AUR and also followed its own corresponding directions for installation.
   
2. First, I used this Git branch: https://codeberg.org/bloop/tangara-fw/sr...ut-drivers
   
3. Next, I used this command: `git clone https://codeberg.org/bloop/tangara-fw.git && cd tangara-fw && git switch emily/lua-input-drivers`
   
4. I followed the build directions from upstream: https://codeberg.org/cool-tech-zone/tang...UILDING.md
   

Resolved, see below.

However, I have encountered an issue: when I've tried to flash the Tangarine firmware, Tangara now enters a boot loop situation.  At first, it will turn on seemingly normal.  However, only the volume buttons and lock slider work.  None of the Tangarine buttons work when pressed.  About 28 seconds after booting up, Tangara will restart.  Is this the memory corruption bug that you've mentioned?  (I should've realized that there was a bit of foreshadowing, as I noticed Tangara restart by itself after successful firmware flashing via the CLI.)  Or have I done something wrong with building from source?

One observation: the SD card menu icon isn't immediately displayed if I don't provide any user interaction.  However, the menu can be brought up if you (rather quickly) manually eject and reinsert Tangara's SD card.  (The effect doesn't last long, however, as Tangara will boot loop).

The one good thing I learned is that I can use the Tangara Companion GUI to "flash" the upstream Tangara firmware if any custom firmware isn't working out as expected.  When I flash the normal firmware (even with the Tangarine face plate), Tangara doesn't experience the same boot looping situation.

(I'm a bit nervous that I might've not reassembled my Tangara with Tangarine gently earlier today.  I currently don't have the vanilla faceplate with me, but it should be back in my possession tomorrow.  Regardless, I believe the signs right now don't indicate that there was hardware damage with the flex cable.)

[taivlam]

The last step to allow Tangarine to work properly is to save this `input.lua` file into the root directory of your Tangara's SD card: https://codeberg.org/bloop/tangarine/src.../input.lua

Otherwise, Tangara will boot loop without `input.lua`.  (I hope this tip helps anyone who uses Tangarine in the future.)

[emily]

Ah, yes, without an input.lua it won't know what to do with the buttons. It's expected that the buttons don't work without it.

But that shouldn't cause crashing; that's very much not expected behavior. This does perhaps explain why jacqueline seemed to get much more frequent crashes than I did; I either had an SD card with input.lua inserted, or had the SD card out entirely. I will look into that when I get back around to this.

The one good thing I learned is that I can use the Tangara Companion GUI to "flash" the upstream Tangara firmware if any custom firmware isn't working out as expected.

This is the result of some good design choices on CTZ's part; it's *very* hard to brick the Tangara by messing with the main ESP firmware. (SAMD firmware is probably harder to recover, but that's okay, because nobody ever needs to mess with the SAMD firmware anyway.)

[taivlam]

So, is there a way to tell the difference between if the bottom right/southeast button on my Tangarine is physically broken vs. if the firmware isn't working as intended?  Right now, I can't use the SE button to go to the "Now Playing" menu.

I've only used Tangarine for a bit, but I feel confident that all other buttons works.  So far, I like how Tangara lets me go through playlist entries much quicker than the default touchwheel faceplate.

[emily]

Latest commit on the lua-input branch should fix the crashing that happens when input.lua is missing.

So, is there a way to tell the difference between if the bottom right/southeast button on my Tangarine is physically broken vs. if the firmware isn't working as intended?  Right now, I can't use the SE button to go to the "Now Playing" menu.

There's no reason that specific button should behave differently than the others, assuming you have a mapping for it in input.lua. You could try replacing your input.lua with the script I use for hardware testing, and watching the debug console (idf.py monitor from your build environment); it'll print all the button states whenever they change.

If it's a hardware problem, you could try just... pushing the button really hard to nudge it back into working. I had to do that occasionally on my original prototype.