The ETHOS widget

Opened this from your droid?

Your droid's own WiFi has no internet. If this page came from a Learn more link in the app, open it on your phone's mobile data, or after reconnecting to home WiFi.

What it’s for

The DroidFX widget is a full-screen touch pad for ETHOS radios: 3 pages of 15 buttons, laid out exactly like Button Pad. Its labels and colours come from a pad file that DroidFX writes for you, so the radio always matches your droid.

PAGE 1PAGE 2PAGE 3B2EMO

1Scream

2Wave

3Alarm

4Dome Show

5Think

6Whistle

7Intruder

8—

9Periscope

10Holo

11Happy

12Sad

13—

14—

15STOPSTOP

The widget using the B2EMO pad file

Install the widget

1. Copy the widget’s droidfx folder so that you end up with scripts/droidfx/main.lua on the radio’s storage (the folder must sit directly under scripts).
2. Model → Screens: add a screen with the one-widget full-screen layout, and set the widget to DroidFX.
3. Model → Lua: enable DroidFX Btn and DroidFX Page.
4. Model → Mixes: mix DroidFX Btn to the button channel, and DroidFX Page to a free channel, both at 100 %.
5. In DroidFX, on Droid Config, set Button page to the channel DroidFX Page goes to. Pages 2 and 3 then work.

Optionally give the widget a 3-position switch to flip pages (Configure → Page switch); without one, tap the tabs on screen.

Load your pad file

1. In DroidFX, Button Pad → Set up → Export to ETHOS…, and download the pad file. It’s named after your droid (Droid Config → Droid name), e.g. B2EMO.txt.
2. Copy it into a folder named pads next to the widget’s cfg_….txt files: SCRIPTS:/droidfx/pads/, on whichever storage the widget is installed on (radio or SD card). Use USB, or Ethos Suite’s file manager.
3. On the radio, long-press the widget → Configure → Pad source → your file.

After changing buttons in DroidFX: export and copy again, then Configure → Reload pad (or reload the model). Each model can use its own pad file.

What the radio shows

Every button sends a press; DroidFX does the rest. DroidFX itself does the toggling, holding and one-shots, so the widget only reports presses. It still shows what each button does:

• a Toggle stays lit (the pressed colour with the gold outline) until you tap it again;
• a One-shot flashes;
• a Stop all button turns every lit Toggle off.

That display is the widget’s own copy, since nothing comes back from DroidFX: a press from the web page isn’t shown on the radio. The widget clears every lit button when the receiver link goes (DroidFX does too), and tapping the pad’s name clears them by hand.

Copy to built-in (in Configure) turns the pad into the widget’s own settings, if you want to tweak it on the radio. A missing or unreadable pad file shows a one-line message, and the widget falls back to its own buttons. A file from an older DroidFX says “Pad file is old — export it again”.

Trouble?

The pad file doesn’t appear in Pad source

SCRIPTS: is the storage the widget itself is installed on, the radio’s internal storage or the SD card, not necessarily the SD card. Find the widget’s own cfg_….txt files (in scripts/droidfx/) and put the pads folder right next to them, on that same storage.

If the list is still empty, Configure shows a line saying why: this ETHOS version couldn’t list the folder, the folder is empty or in the wrong place, or the first few names it found aren’t usable .txt files. Below it, the Pad file name field opens a file by typing its name (e.g. B2EMO.txt) even when the list can’t see it.

Pages 2 and 3 press page 1’s buttons

DroidFX doesn’t know the page: set Button page on Droid Config to the channel DroidFX Page is mixed to.