Opple Light Master 4 discussion thread (new 2023 model)

I’m not exactly a flashlight enthusiast. To be more precise, this stage is in the past - there are a couple of Convoys left, and my own crafts. Lately I have been working in the field of development and small-scale production of led lighting devices of various types. So I already have a slightly different approach to this issue.

@stevechang I just got my LM4 and it has been a joy to use - despite it’s readings being rather random at times. I just wanted to say thank you to you and all others who built this and continue to dedicate their time to improving it. Thank you!

3 Thanks

I think it is not we don’t care about other lights, it’s just we prioritize our lights first. we encountered problem as I said before, there is no smooth transition when one of the LM3 team member left us, and then I was not involved in LM development at all, so I have no knowledge of the transition process.
then the magic number listed in below graph emerged when I started to proceed to this development stage, those magic numbers are for LM3 which used as7262, but for LM4 we use as7341 for those magic numbers need to be recalculated, and I have no idea of how those numbers are generated. How can I do, please tell me.

these coefficients are of great importance to bridge the AI model I constructed and the real sensor readings.

1 Thank

idea from one of the employee of the Japanese’s firm verified, seems does not work.
I don’t know why those coefficients are constants, is it applicable to a wide range of CCTs? I doubt it.

Unfortunately, that’s not my area of expertise.

I draw your attention not to coefficients - that is a separate problem.

  1. Inability to use the device in the absence of GPS/Internet access causes irritation to the user and may give a negative attitude to the device and possibly to the company’s products in general. This is a transfer of negative attitude from the device to the whole company’s products.

  2. Strong distortion of the device readings in the presence of extraneous NIR radiation (let me remind you that most people will not realize that it is present) will create in the user first misunderstanding and then distrust to the device and, accordingly, to the company’s products in general… Even if it is written in the manual, the user will forget about it completely in six months.

I don’t know what you should do with my subjective opinion - you decide for yourself.

That’s on Android. Bluetooth permissions are linked to position services. On new Android you can give the app access to your “rough position” at least.

No way to avoid that as an app dev.

1 Thank

Perhaps. I have to buy a new phone to use a 25 bucks device? )))
Maybe developers would think about the usability of their device?

GPS/internet access issue, to be frank, is none of my business.
I take a train to Shanghai and tell the PMs that you ought to do this or to do that?
the PMs would definitely say this to me “who are you? are you my supervisor? do I need you to teach me to do things?”
buddy, I told you once I @ the PMs in WeChat group, and they never reply me, making me kind of feeling embarrassed. you always thought that I am the rep of this company, that’s just not correct.

As I said, there is no way to avoid that. Every Bluetooth device in the world needs GPS access to work. It’s just how Android (and I think iOS too) works. The only alternative would be to make the device wifi instead, which would need you to set up a hotspot, them pair the device, and make usability a ton worse.

1 Thank

Sorry, maybe I’m just used to working for myself or maybe I just don’t understand some of the ins and outs of your culture.

This is … )))
BLE works fine without GPS. I write apps on Flutter to control lighting drivers via bluetooth.

AFAIK you need the Position permission whenever you do a Bluetooth device scan. When you already know the MAC address or the BLE identifier it might work without that permission, depending on the Android version.

2 Thanks

Perhaps my knowledge is 2 years out of date. ))) The last development didn’t go to release and sale because of the war (2022). Everything worked without GPS and searching for new devices.

It’s explained here:

Android 11 and below: ACCESS_FINE_LOCATION manifest permission (during installation)
Android 12 and above: BLUETOOTH_SCAN runtime permission (the user gets a confirmation popup during runtime)

1 Thank

Sorry, I don’t want to deal with this again. For me, mobile development is …! I hate languages with dynamic typing.
In any case, we can connect once, save it in the settings and don’t bother the user to turn on the GPS again, as far as I understand.

You don’t need location permission(s) if you associate the BLE device using Companion Device Manager (Android 8, Api 26) which is what Google recommends, because it sidesteps the whole issue :smiley:

The Android BLE APIs are difficult. It took me about 10 years to figure them out :upside_down_face:

1 Thank

I don’t want to understand deep into the BLE APIs ))))) It’s not my thing at all. It so happened that I had to learn Flutter and BLE at the same time, but not too deep - to the level of stable work.
But the discussion is not about that, but about the fact that the LM application should not be annoying and inconvenient for the user. IMHO.

I’d suggest you send email to our PMs directly. :rofl:

as for the precision problem, i will not give up. and we found 2 domestic suppliers for spectral chip.
but the spring festival is coming, and we’d have a long vacation from this week, lasting about around 3 weeks.

2 Thanks

Hopefully they are able to provide information without NDA. (Which is ridicolous for a simple spectral chip tbh)
An open-source cheap light analyser would be awesome.

I don’t need to advise anything. It’s not my problem.))) I have the stupidity to start my own project if I have to )))))

By the way, I wrote. No response…

Good luck!

Work-life balance is important!

1 Thank