Its not about driver design. Its namely about whoever decides which software goes into the MCU, and the reasons behind. Likely many of these drivers are mainly software implemented for some sort of generic market or generic abroad market. The mode spacing in that driver is terrible, too.
The Chinese, It use to be alot worse than it is now but thanks to several contributing members here on BLF it’s becoming rare. At least most of them are making the strobes and flashes hidden after many years of complaining about them in the main UI.
Simple and not very well R&D is cheap. Complex and well designed is expensive which has to be added to the cost of each driver. The more time the software developers spend on a UI the more it cost. We are just very fortunate to have members who do this without asking for a dime or very little money.
I couldn’t even image the cost on the hours it took to develop Anduril.
Just my opinion.
The above quote refers to a manifestation technique, which in recap is entering a theta wave brainwave state of mind (actually easier than said) and then precisely sketching out whatever it is to be manifested.
But, did you ask? And what did you asked?
First of all we need to come up with a common goal. I think something can be done here, something sort of establishing a default for number of output modes and sequence order, preferred mode spacing, memory type and hidden strobe (if anything).
For example: 4 modes low to highest, 0.1%/5%/20%/100% mode spacing, off time memory, double tap strobe.
Off time memory definition: memorizes last used mode if disconnected from power more than x seconds. This can be pretty short, like 1 or 2 seconds, as usually a half tap to change mode lasts less than that.
By opening a thread where others can see and chip in, vendors included, and once the common goal is set the petition would be formulated. Once formulated people would enter into manifesting state and command/pray the request.
This actually works a lot better than you may think at first, no need to say this to those who know.
Because the driver designers are contracted and dont actually work for the flashlight company. Also the driver designer dont actually use the flashlight or any flashlights in general so they dont have a sense what a good UI should be like.
The flip chips are safer to slice as the bonding wires are hidden and you can go fairly low when slicing. Id recommend people give it a go themselves might be a good mod to start with. Get a washer and razor and try.
Is there any point in going lower than the bonding wires? That is very little dome leftover thickness. When looking at the emitter from above and paying attention at the apparent die size, big change can be seen with dome versus no dome or as the dome is being lowered by slicing. At some point going down the optical gain starts being negligible.
The XHP50.2 has no bond wires. So you can slice right to the edge of the phosfor. It does have a few exposed ESD-wires but they are not essential for function and with a bit of luck you can even keep them whole.
Many times I’ve heard how slicing was hard to do reliably and expensive and not a practical option for anyone but modders.
Here I see KD offering something actually harder (because dicing reqiures some precision). Even if it’s not done great, I appreciate Kaidomain’s willingness to try to walk this not well treaded path. I appreciate it a lot.
Borrowed the following picture from such advertisement:
Since when is micro-USB “not convenient”? I wish people would stop pouring crap over existing technologies (or whatever) just for the newer stuff to look better. Completely unnecessary shithead attitude imho.