I saw you posted at CPF, too, so I’ll copy this here in case you don’t see my response there:
https://bazaar.launchpad.net/~toykeeper/flashlight-firmware/fsm/changes
Revision 446 removed muggle mode from the D18 version because there wasn’t enough memory to support muggle mode and other new features.
Revision 457, which is new in the last week after some optimization was done to the code, will add muggle mode back in.
Just a question… When I’m in temp config mode and setting current temp, so clicking during the first buzz, and then not clicking during the second buzz, the max temp will be set to 30degC, or stay unchanged? And if I click only during the second buzz, will the current temp stay unchanged?
If you do nothing, everything stays the same.
Hi, I’ll explain the thermal configuration well; I tell you right away that there is a shortcut to get to this configuration: 1) make 10 clicks from off 2) after the first flash set the current temperature: example: if the room temperature is 25 degrees ° do 25 clicks; wait for the second flash and after this second flash set the maximum temperature limit that the torch should reach before starting to lower the level; the temperature is set by default to 30 ° and therefore you have to click + 30: example: if you want to set the limit to 45 ° you have to make 15 clicks: 15 + 30 = 45; if you want to set 50 you have to do 20 clicks, 20 + 30 = 50; if you want to set the minimum you only make 1 click: 30 +1 = 31 etc. I hope I have clarified; of course you can get to this configuration also with the method you see on the diagram: click 4 from Temp Check Hello and good lighting !!
Not every flashlight with Anduril has the 10 click shortcut.
Oops …! I apologize for the inaccuracy; I believed this because all my Emisar torches with UI Anduril have the shortcut; hello and good Sunday, Ricc. 
Hi all friends! Hank told me that the current version of the d18, version 11-20, does not have a muggle mode; unlike the others, it can be reset to factory settings; it also has automatic memory and manual memory and a protection if you keep the power button pressed for a long time: if you hold it down too long, the light will automatically go down to the minimum level after a while; I can’t tell if it has other new methods too. 
10 click thermal config is enabled for:
- D18
- E01
- MF01S
- D4v2
Hi, also D4S - D4SV2 - D1 with Anduril UI, have the shortcut with 10 clicks from off to make thermal regulation; I know for sure why I have these torches.
I forgot D4Sv2, but D1 and D4S do not use 10 click thermal config in Anduril.
I have the d4s right here in my hands, and I assure you that by making 10 clicks from off I get to the thermal configuration mode; as for the D1, I have the model with Anduril UI bought from Hang and not the model with the old IOS V2 UI interface; well, I can guarantee you that the D1 with Anduril UI has the thermal configuration with 10 clicks from off; summarizing: D4S and D1 with Anduril Ui, they have the thermal configuration with 10 clicks from off. I guarantee it at 100%. At least it may be that you are talking about an old version of D4S … everything is possible; mine has 10 clicks from off; Hello and good day from Rome … here it is cold and it always rains. Riccardo. 
Do you see any
#define USE_TENCLICK_THERMAL_CONFIG
here?
You might have an older version of Anduril on your D4S. I haven’t found any hint that it was included previously. Maybe it’s a build for a different flashlight.
Hi; I believe what I have in my hands; in my hands there is a d4s and a D1 with UI Anduril that have 10 clicks from off to go to thermal configuration; to conclude, it would be better to ask someone who knows more than the two of us; I always ask my friend Hank when I have doubts; you could do like me too; good day my friend.
And I trust the code. In this case better ask ToyKeeper as she wrote this fantastic firmware.
You can also ask those who own a D4s or a D1 with Ui Anduril; my Italian friends have both torches bought from Hank and both torches have 10 clicks from off for thermal configuration; Hi friend, here in Italy it is 9 pm at night, my wife has prepared a nice steak and I go to dinner; See you tomorrow!
I don’t doubt yours (and maybe others) have 10 click thermal config, but it’s not included in the official Anduril code and my flashlight (that I flashed myself) don’t have it as well.
Are you sure that you have Anduril and not RampingIOS (the default firmware for these lights), which is very similar?
I have to do a bit of clarity: some modes of these torches (Anduril), are not written either in the manuals or illustrated on the various diagrams, but are present: if you buy the D1 with Anduril from Hank or now also from Mountain Electronics, will surely have 10 clicks from off; if you buy the D4s that I have (old model). now available only from Mountain Electronics, it will have 10 clicks from off; you can ask ToyKeeper for confirmation of this, who is a true genius; and now, my friend, let’s talk about something else: what do you think of the D4v2 in brass? I ordered it 2 days ago from Hank; I’d like to hear from you.
I’m not looking at the manuals, I’m looking at the code.
This is the wrong thread for that.
Interesting. There was a time when I had muggle mode turned off for a few build targets, because there wasn’t enough space left in the ROM. But I don’t think I sent any of those to Hank. The current versions have muggle mode again, because I was able to reduce the size enough for it to fit again… and I sent those to Hank a few days ago.
Looking at my logs, I sent Hank D18 firmware from 07-18 and 11-24. Muggle mode was cut out from 09-24 to 11-23. I’m guessing he may have grabbed updates from my site without mentioning it. Keeping things up to date is great, but not all of those builds were tested as much as I’d like for widespread use.
Also interesting. I put the 11-19 and 11-20 builds up hoping to get help with testing… but they were not intended for production use. These builds included some major changes to the kernel code, so I consider it high-risk. The testing has all gone well so far, but because the changes were large and deep, I was not planning to use any of those changes in production until they had been proven stable for a few weeks.
The good news is that everything so far suggests the kernel changes work correctly and did not break anything. But I think I may need to find a way to mark builds as “dev” or “stable” to avoid any dev builds going to production.
This is true. However, we don’t necessarily know that the drivers and firmware shipped with each light are the ones which were created for that specific light. For example, the D4S was shipped with Anduril for a while instead of RampingIOS V3, and I think it may have used the D4S V2 driver and firmware. Additionally, if the D1 has the tenclick thermal config, I wonder if it might be using a D4 V2 driver instead of the original D1 driver.
That’s a big part of why I originally wanted the version check mode to be … very detailed. I was hoping it could individually identify every build of the firmware, not just the date when it was built. This would allow one to check whether a D1 shipped with a D4 V2 firmware, for example. But it’s not easy to encode a long version string with a blinking light… at least, not in a way humans can easily parse.
So… it sounds like some unexpected versions of firmware may have been used, sometimes even on models they were not intended for. It should generally still work, but some of the details might be a little weird. Like, the ramp shape might be a little skewed, or the thermal response might be a little too slow or fast. But this shouldn’t cause any big issues.
As for tenclick thermal config, it would probably be good to have that on all Emisar builds… but it hadn’t really come up. Ever since adding factory reset, there hasn’t been much need for people to access the thermal config mode. Factory reset calibrates the sensor to 21 C.