Me? 
I never wrote code that was glitch (feature) free and don't expect it of others 
42 years in the biz and you lose all your ego...
I shall just continue to tell people not to return their flashlight because Muggle max ramp keeps dropping back to Min ramp.
(regardless of thermal settings)
What issue are you referencing? I don't use muggle mode, ever, and am not aware of problems with it. Sorry if I misled you.
Well we’ve talked about it a couple of times in the past and many more have mentioned the issues here and there. Toykeeper has been made aware of the glitch several times too.
Like I said many times, you ramp to Max ramp in muggle mode and it steps down to min ramp straight away, the problem is intermittent.
Muggle mode is potentially an excellent feature/selling point and I do feature it a lot in my reviews.
The lumen outputs are not linear. Human perception doesn’t work like that. If it uses the commonly-accepted cube-root model of brightness perception, spacing which looks “even” would be 5 lm, 19.6 lm, and 50 lm.
Anduril uses a similarly curved ramp to make it appear as if the spacing is linear… even though it’s nowhere near linear in terms of lumen numbers or power usage.
As for power usage, if you’re only at 5 to 50 lumens and it’s using a 18650 cell, you can expect like ~15 to ~150 hours of runtime per charge.
… and for finding a light with an easily-accessible control chip, I’d suggest going to Intl-Outdoor and getting an Emisar or Noctigon light plus a reflashing kit. It’s well-supported and allows reflashing with no soldering. Just unscrew the battery tube, hold the pogo pins against the driver, and run a command on a computer.
There are a few different UIs included with FSM. Anduril is the largest and most complex, but there are others which behave like a ZebraLight or Olight, and the code for those is much much simpler and easier to learn from.
Huh?
Oh. That was fixed well over a year ago, in May of 2019, while people were receiving the first batch of FW3A lights. Maukka reported it while reviewing a pre-production sample, so I fixed it right away… but at that point Lumintop had already made the drivers for the first batch, so it couldn’t be included until the second batch or later. I’ve posted about it a bunch of times to let everyone know what exactly what was broken and when/how it was fixed.
So… it has been fixed for a long time. But I can’t magically update the firmware on lights which were produced with old versions, so people with old lights might still run into that issue.
The best I can do is send updated versions to every manufacturer who is willing to use it… which I did. That may or may not include Lumintop though. Last I heard, they rejected my updates and I haven’t had any communication with them at all since last year. None of their recent FW-series lights are using firmware which was intended for those products, so I’d advise caution there.
As for Anduril 2, it doesn’t even have a muggle mode. That got removed and replaced with something better, as described in this thread’s first post.
I’ve mentioned it every Anduril light I’ve used and get the same reply especially with Astrolux “They use an older version for some reason, the latest version is bug free” but this was never true, it was glitchy til the end. Unlike Tom I use and test Muggle mode. I’ve tested more Anduril lights than most.
I had one that steps down if you continually hold the button as a safety feature and that also has the glitchy muggle mode. I thought that was the final version. But I suppose it’s academic since has the ill-fated mode is set to be abandoned.
Sunset mode having brightness and time configuration is crucial. To get to turbo you have to be at max ceiling? that’s a no no. It’s all getting a bit vanilla. Call the new Muggle mode “Vanilla mode” lol.
Yeah, please fix it, I’m soooooooooooo sick of him noting it doesn’t work in every single one of his youtube videos 
TK would know better, but Hank with the Emisars and Noctigons keeps up to date with Anduril, probably the best of all vendors, plus the fact he sells the dongle to fit his lights for re-flashing.
Would be interesting if you have Emisars or Noctigons and have seen the problem or not. I know they are a bit pricier so not sure if realistic for resale in your biz.
True with outdated versions with Astrolux, Haikelite, and Lumintop - maybe others as well. Again TK has more info on the vendors/models support.
No… There have been 129 revisions since then.
Anyway, if you don’t believe the author of the code, feel free to check the code itself. Full history is in the repository, showing exactly what was changed and when.
The issue with muggle mode dropping directly to the floor level was fixed in May 2019, and the stuck-button safety ramp-down wasn’t added until four months later. So… I don’t believe that you saw those two traits in the same version. They did not exist at the same time.
There may have been an issue, but it wasn’t that issue.
That’s my favorite part of Anduril 2… I can easily turn a hotrod light into one that’s completely safe to carry in my pocket without sacrificing nearly as much output/as many features as muggle mode did on the previous version.
If you want full turbo from off just set the ceiling to 1-click, exactly like has been the case. There is still the “2H from off” command if in complex UI too, regardless of what your ceiling setting is.
I have intermitently followed this thread, so I am sorry if I am missing the point here, but I get the impression that turbo cannot be accessed by double clicking from any point in the ramp with Anduril2?
If that is the case, I would agree with The_Flashaholic that double click to Turbo should work from every level, not just max ramp. Say you are outside and are using 30% ramp to walk while keeping the light thermally stable. You see something and you want turbo then and there. Should you have to ramp all the way up and then double click? Or turn the light off and then do 2H? That does not make sense to me in a realistic usage scenario. I believe 2C to turbo from anywhere (off or on at any level) is an absolute must.
In Anduril 1, the ceiling level was kind of meaningless, since so much of the UI ignored it and used full power instead. It was a very frequent complaint.
So in Anduril 2, the ceiling level matters more, and turbo is finally treated as a special mode. The user can still change this, of course, by setting the ceiling to full power. Then it’ll give easy direct access again. But for the many people who wanted to make their pocket rockets use sane levels instead of jumping directly to fire-starting mode, it’s now possible to do that in a more meaningful way.
I am sure I am missing something or have not understood correctly. I have always set the ceiling level on 120, which is bright (and hot) but not as much as Turbo, which is level 150, if I am not wrong.
How is it meaningless then? I have a ramp, that gets as bright as I want it to get, 120 in my case (others may choose less or more) and a special mode, Turbo, that will take the light to 150, when needed.
Say you are outside and are using 30% ramp to walk while keeping the light thermally stable. You see something and you want to jump quickly to the user-configured ceiling level. Should you have to ramp all the way up and lose the memorized level? Or turn the light off and then do 2C? That does not make sense to many of the people who sent me feedback.
It was very easy to reach turbo, but it was not so easy to avoid turbo or to reach the user’s preferred top level. This led to many people burning holes in things, or avoiding double clicks entirely, because some lights ran way too hot… and there was no way to configure the light to not do this.
Many also found it confusing that “Off 2C” and “On 2C” went to different levels. It was inconsistent and unintuitive.
However, in the new version, those issues are resolved… and it’s still possible to make turbo the easily-reached level instead, for people who want full power instead of a less dangerous high mode. To get full power back on speed dial: Go to the ramp config menu, select option 2, and click 1 time.
I guess it is a matter of preference. If I am out and see something I want to jump to overdrive. and if I do not want to use Turbo, holding the button will increase the brightness quickly enough. Losing turbo as a standard double click is a blow for me and I do not wish to have the ceiling set to 150 as I do not want the light to run away while on normal ramp.
Losing the memorized level does not seem like an issue at all, it is not any special level in any case.
I did not find it at all bad that double click from off took me to ceiling and another double click to turbo. I actually liked it and found it clever. Two bright levels, good for many occasions, not much thought needed, quick to access.
If I am a minority, I will accept it, of course, but my personal preference would be to not lose the double click to Turbo.
Maybe there can be a configuration option for New double click or Old double click mode? That would make everyone happy, if possible.
There is already a configuration option for new-vs-old double click behavior:
#define USE_2C_MAX_TURBO
This was added about three weeks ago to make it easier for people to get the old behavior back in custom builds. Depending on which light is being used, it can be pretty easy to customize. Emisar / Noctigon lights are the easiest, since they have reflashing pads and a flashing kit, but others are possible too.
That is nice, but I have no experience with programming and compiling to make the changes for my lights. It is great that it is there though! Would it be possible to activate that as a configuration option on the light instead of pre-flash?
Are you any closer to including Lume1 in your Anduril2 supported lights?
Hi, if I ported Andruil2 to also use CMake would you be interested in upstreaming it? Would make sure its easy to build on macOS, Windows, and Linux of course 
If you liked it I could probably port other stuff too