This is going to be a bit weird and I have to say probably unrelated to opencamera specifically. I just wanted to share the pain and ask for ideas.
Xiaomi Mi MIX 2s, with OpenCamera v1.47.2, on lineageos 16 (android 9, with up to October patches) with vendor firmware 9.6.27. Essentially, latest and greatest in everything. Camera2 API enabled (it's a prereq anyway for the functionality that's buggy)
To reproduce the bug I have to
Set the ISO manually to any value
Set an exposure time that is of some sufficiently large value to make the bug noticeable. I have tested up to now successfully with values of 2 to 9s (it the maximum the devices allows). Let's call this E (yes there is math involved)
Set a Repeat for a number of photos, e.g. 5, let's call this R
Start the photo sequence
The first photo is going to have an exposure time of exactly the amount of seconds specified, but all the subsequent ones seem to have N = E * R amount of seconds as an exposure time. That is for the example above, first photo is going to have an exposure time of 2 secs, and every subsequent one is going to have an exposure time of 10s.
I know it sounds absurd, that's what I witness. The maximum for my device seems to be 35,7 seconds, so if the calculations go above that it seems to be capped at that.
I 've started noticing this as I was trying another camera up, DeepSkyCamera Beta. The fact it has the exact same behavior makes me think this is related to the vendor firmware, but I 'd like some opinions on how to verify that claim and proceed with this.
The entire idea, for those interesting, is to use a smartphone to take cheap astronomical photographs of a relatively simple nature (yes it can't compare to a normal DSLR attached to a proper mount/telescope/whatever, nevermind dedicated equipment), but it's a really affordable starting point to get to know the sport, which can be very very expensive.
Anyway, thanks for an awesome piece of software!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2019-10-27
it may be related to ticket 640?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Mark,
This is going to be a bit weird and I have to say probably unrelated to opencamera specifically. I just wanted to share the pain and ask for ideas.
Xiaomi Mi MIX 2s, with OpenCamera v1.47.2, on lineageos 16 (android 9, with up to October patches) with vendor firmware 9.6.27. Essentially, latest and greatest in everything. Camera2 API enabled (it's a prereq anyway for the functionality that's buggy)
To reproduce the bug I have to
The first photo is going to have an exposure time of exactly the amount of seconds specified, but all the subsequent ones seem to have N = E * R amount of seconds as an exposure time. That is for the example above, first photo is going to have an exposure time of 2 secs, and every subsequent one is going to have an exposure time of 10s.
I know it sounds absurd, that's what I witness. The maximum for my device seems to be 35,7 seconds, so if the calculations go above that it seems to be capped at that.
I 've started noticing this as I was trying another camera up, DeepSkyCamera Beta. The fact it has the exact same behavior makes me think this is related to the vendor firmware, but I 'd like some opinions on how to verify that claim and proceed with this.
The entire idea, for those interesting, is to use a smartphone to take cheap astronomical photographs of a relatively simple nature (yes it can't compare to a normal DSLR attached to a proper mount/telescope/whatever, nevermind dedicated equipment), but it's a really affordable starting point to get to know the sport, which can be very very expensive.
Anyway, thanks for an awesome piece of software!
it may be related to ticket 640?