Thanks for jumping in to help. BTW, have you tried my mod on your TS10 after I fixed it?
1 Thank
I will be glad to try it… Did not realize you fixed it… do you have a link or post number?
2 Thanks
Sure thing, here’s the post: Anduril 2 feature change suggestions - #345 by dmenezes
Sorry for not having replied directly to you or at least tagging you in that post 
… and looking forward to your updated test report! 
1 Thank
I just tried that, after first backing up my own working TS10 hex.
That TS10 file does not work. The light turns on w Red Aux on High bright, but the main LEDs are blinking at the same time. I cannot turn the light on w normal main LED only.
I reflashed to my backup and everything is back to normal, but no 8C toggle…
1 Thank
It’s private.
2 Thanks
Thanks for the report! Tried to see the video but getting a"This video is private" error screen from YouTube…
2 Thanks
1 Thank
New link works. Back in traffic but at least I can see a red TS10 blinking now 
Will watch and comment further later today.
2 Thanks
I remind you that to change even firmware the correct way is to factory reset, flash, return to factory reset and test.
In other words:
1-Reset
2-Program
3-Reset
4-Use
Why?
Because data can be stored in a memory location and when the firmware is changed the data is stored in another memory location and read in another place and it has to be clean.
For that reason when programming it does a deletion but it is better to do the reset also.
This has happened to me with the ones I have received, one arrived with the main ones doing something strange and another one with the Aux in disk mode of one color and after a reset to all of them, they worked again.
It is not the case but I just remember it.
2 Thanks
Yesss!
It seems a rare alternate mode to the main ones.
As storm mixed with beacon is curious.
1 Thank
my process when installing a new hex does not use Factory Reset. I do:
- backup existing hex that I know works
- erase
- reflash with new hex
- use
If the new hex works, I then set all my option preferences, and make a new hex backup. I could not do that with the 8C hex, because the light did not work properly.
When my TS10 did not work properly with the new 8C hex. I did not try Factory Reset. Maybe someone else can test that idea.
when a new hex does not work for me, I do:
- erase
- reflash from known good backup
- use
I do not use Reset because it erases my backed up options settings for floors, ceilings, memory type, aux setting, turbo type, number of stepped modes, Simple mode or Advanced mode on startup, thermal ceiling, temperature calibration, ramp up or not on 1H, type of strobe…
If I adopt a new hex (I cannot build my own), I have to redo all the above options.
3 Thanks
That’s right! in my case I do it in other systems.
But I do backup before then reset delete and program.
Then reset and use.
But if you use the backup of course I do not reboot.
And the reset is only when using a new version.
The values are stored in one memory area and a new version can store them in other memory areas.
On startup it reads wrong values.
It is theory alone, but I do it on other micros.
So my idea is to factory reset my flashlights with my values already configured.
Temperature ceiling for example.
Edit: I already have the programmed I will test, but I only have with anduril 2:
SC31Pro
TS10
TS25
1 Thank
But I’m just commenting, it clearly happens to more users with 8C firmware.
There is some change.
I already commented it I think, for health I can’t test things when I want.
But I want to do it soon, so I see if it happens to me too.
Or maybe it will be fixed sooner.
1 Thank
I just reflashed to the 8C hex, got the same hybrid aux w flashing main
did a Factory Reset and Viola! Bob’s Your Uncle… LOL
the 8C hex works on my TS10 after a reset. Yay!
Gracias Señor @dmenezes !
thank you very much for the suggestion @litris
Muchas Gracias! 
3 Thanks
on my SC21 Pro with anduril2-r657, I always do factory reset after every reflash.
I have experienced some irregularities once among many reflashes; 3C battery check didn’t work, only aux (button LED) was flashing with fast random meaningless pattern like it has its own mind. And that happened a few hours after the reflash and of normal condition. I did factory reset again and then everything became normal.
I used it with that firmware for a few days and the problem never reoccurred.
1 Thank
I’m glad it will work for you!
1 Thank
I had a long post here about what its doing in all three versions I’m testing, since I have a glitch, just a different glitch, in each.
I’ll go back through that info later, and re-test some things based on what I just found, then post about it.
OK. So. Just found this.
factory reset.
flash 8C mod.
Factory reset.
I’ve always been doing the reset after a flash, when installing the battery the first time, since the instructions I have said to do so… Today I added the reset before flashing for good measure after the issues these other guys here have had. Figure It can’t hurt anything.
didn’t set up anything but;
- aux on high and red in standby/off.
- high and purple in lockout mode.
So I have a clear definition of locked, not locked, and aux off or not.
(I’ve actually done all my tests with these setting since its my preffered setup, and what was on when all this started. I’ve never actually tested any of this with different colors!)
No issues whatsoever, runs perfectly!!
but set Manual Memory, and suddenly it does the 30 seconds to unlocking itself if you either 7c or 8c the aux off!!
turn manual memory off, and it stops doing it!!!
doesn’t care whether you’ve set auto lock or not.
(something I found to be an issue with the stock 721rev–more on that later)
Doesn’t care which battery, or voltage range either!!
I was screwing up my test enviroment, and missing this before.
For my testing, I was setting manual memeory early on; To get an output more than moon when I 2C to momentary low in lockout mode; So I could see reactions for button presses, whether it was locked or not with aux off, etc…
I figured it was an unrelated setting… Forgetting that Any variable can change things in testing even the most simple systems… and this software is not simple lol. The rule is you change one thing, and one thing only, to get a base to compare. face palm
I swear I had it doing the glitch with a fresh reset once before, but I guess not.
I’ve reset, and retested this a few times, reflashed to make sure, etc.
Other than the issue to start, its the first consistent results I’ve had…
This might explain why both mods mess up. One is a mod of manual memory and one mods the Aux output selection… Apparently the two are tied together somewhere higher up in the program? Or it does have to do with using 8C for both mods, and thats tied to both features?
OK, thinking out loud now, I’ll stop…
Now I go back and flash the other manual memory mod from @wolfgirl42, and see if I never touch manual memory, if the aux modes screw up.
Then if I’m still sane and alive, I’ll look at the stock rev721 again.
TS11, still debugging this flashing/unlocking.
This time in toykeepers unmolested rev721;
(can’t for the life of me remember where I downloaded these hex files, I swear from the main anduril2 page… but a bit unsure. Was only like 3 or 4 days ago though.
OK, here we go!
standby aux set to high and red.
lockout aux set to high and purple.
With auto lock on(1 minute)
manual memory set (no timer)
4C to lock.
(so in lockout mode)
it blinks(~1 second off then on again) the Aux once every 30 seconds. But stays locked.
Then;
Turn off auto lock.
4C to manualy lock it
(manual memory is still set with no timer.)
then 30 seconds later it will unlock itself back to standby.(same as 3C from locked, aux blinks once and goes from purple to red)
4C to lock again and it repeats, it will unlock itself after 30 seconds as many times as I lock it.
Then;
turn manual memory off.
Auto lock is still off.
4c to lock;
functions fine, it goes over 5 minutes perfectly fine, no flash, stays locked.
then;
Set auto lock again to 1 minute.
3C to standby,
58 seconds later it locks like it should, aux changes from red to purple as it should.
And over two minutes later, there were no flashes at 30 second intervals, and its still locked.
now set manual memory again,
brings us full circle back to the start,
auto lock on set at 1 minute.
locks itself from standby in about 60 seconds. Red aux changes to purple.
Then, again, every 30 seconds, it blinks out the aux for a second, just as we started.
TL:DR
In lockout mode, with manual memory and auto lock set, it flashes the Aux every 30 seconds., stays locked.
In lockout mode with no auto lock, and manual memory set, it flashes the aux and unlocks after 30 seconds.
((ANd no, with manual memory on, it doesn’t flash the aux every 30 seconds when in standby mode. Only when locked.))
Soooo… manual memory is turning on a 30 second timer, that is checking something in lockout, or resetting something…
Only connection I know of between manual memory and lockout mode is that the manual memory level becomes the 2C momentary while locked. No man. memory set and 2C stays at a low/moonlight mode. Thats the only surface/user connection anyway… I’m not good enough to dig in the code for connections. 
Hope that was readable, and helpful to somebody. 
At this point, as I see it, the issue causing this is in the main branch code, not the mods.
so, @dmenezes you mentioned a bug report before. Do I/we now do that and send one to @tokeeper ? 
Thanks for the step-by-step guide. I can’t reproduce it with my flashlights, but I should receive a TS11 soon.
You’ve already done it by mentioning @ToyKeeper. She went silent a month ago, though. So we have to wait.
1 Thank
TK last post was June 11th. Last seen 8 hours ago. Investigation complete.