P2 Pro improvements

Summary:

• Merged #11 which should improve the operation of P2 Pro cameras (see PR for more details)
• Updated version

P2 Pro and Higher API verion

Summary:

• Bumped target Android SDK version to 34, min SDK version remains 21 (addressing #8)
• Added basic P2 Pro support thanks to #9
• Other minor fixes in the code

In this release I updated the API version to 34. This means that it should work better on new Android versions. The minimal version remains the same 21, meaning that it should still work on old devices but if it doesn't just use the older versions.

The P2 Pro should now show a picture, please open an issue if you have any issues with it.

Increased Temperature Offset Range

Some users reported an issue where the temperature ranges would be off by quite a bit, in order to address this the temperature offset slider (under the thermometer icon) has been increased to -100 to 100 degrees Celsius. The same notes as in version 1.0 apply.

Basic T2S+ V2 support

This release adds basic support for the T2S+ V2, which requires flat field correction on the host device. It's a bit rough, but if something isn't working properly, clicking the shutter button a few times will most likely fix it.

Some possible issues in this release:

• Android may complain about the app being old or insecure. This is due to the low API version, which allows it to run on older devices, and the lack of a Google-signed certificate. You can ignore this; the app will work fine.
• The app keeps showing "Disconnected" even after plugging in your camera. This likely means your camera has an unknown Vendor ID. If this happens, please open a new issue and attach the vendor and product IDs, which can be obtained by plugging the camera into a desktop and following this.
• The app warns about pointing the camera at hot objects. Press the shutter button to reset the message.
• The high-temperature range displays values that are too high. I haven't studied this range yet, but dividing the values by 10 should yield roughly correct results. This will be addressed in a future update.

Feel free to submit an issue if you find any other weird behaviors.