FLIR One Developer / Blog / Topics / dairy queen feedback / Issue with Flir One and Samsung Galaxy S8+ devices

Issue with Flir One and Samsung Galaxy S8+ devices

Home Forums FLIR ONE SDK Development Android development Issue with Flir One and Samsung Galaxy S8+ devices

This topic contains 11 replies, has 9 voices, and was last updated by Profile photo of jack jack 3 weeks, 6 days ago.

Viewing 12 posts - 1 through 12 (of 12 total)

  • Author


  • #8174

    Profile photo of Milos



    my team and me are having strange issue with Samsung Galaxy S8+ mobile devices and Flir One thermal cameras.

    Our application records thermal images for:



    RenderedImage.ImageType.ThermalRadiometricKelvinImage types.

    When we capture thermal images using two Samsung Galaxy S8+ devices we get different results.
    What does that mean? That means that on the first ‘GOOD’ device we get proper values for both thermal image types.
    However on the 2nd – ‘BAD’ device we get wrong values for ThermalRadiometricKelvinImage data. Each value we received is: 22314 EXACTLY.

    Both Samsung Galaxy S8+ devices are running latest OS and OS patches provided by Samsung.

    Issue is possible to reproduce on ‘BAD’ device older OS and OS patches too.

    Do you have any idea what can cause the problem that we are describing and what do you suggest us to do?
    Are there any ‘certified’ Android devices that you can suggest to us to use instead of Samsung Galaxy S8+?

    Thank you in advance!

    • This topic was modified 2 years, 1 month ago by Profile photo of Milos Milos. Reason: Messed up html


    Profile photo of Milos


    After intensive testing and verifying that we are performing tuning, i am sure that camera is tuned every time, however for every Radiometric Kelvin type’s pixel we are getting the same values again and again (that is: 22314). Sometimes, we get good data. It lasts for some time (hour for example), but it starts returning 22134 again.


    Profile photo of Allison


    Hi Milos,

    I apologize for the delay in response.

    Our developers are currently looking into this issue. During your testing, were you only using the latest version of the SDK or did you also try using the older version also available here If you haven’t and have a chance to, that would be really helpful.

    There have been some temperature issues with the latest SDK that we are still working towards resolving.

    Thank you,
    Allison Torchia


    Profile photo of Milos



    yes, we tried the latest SDK, but we have also the same issue with the older one we primary use: Flir SDK 1.2.8.

    Best regards!


    Profile photo of Milos


    I got this issue with Samsung Galaxy S9+ with Android 9. Here are some details (if helpful):

    Flir info:
    Battery level: 56
    Flir SDK info:
    Version name: 1.2.8
    Version code: 128
    Detected repeating value: 22314
    Tuning state: ApproximatelyTuned

    After a half of hour, camera recovered and started returning good values again! No change in our application codebase was done!


    Profile photo of Raleigh


    Just what I needed, worked a treat, thank you! psiphon


    Profile photo of Ute


    It solved my problem…Thank you so much for it


    Profile photo of johnson


    It solved my problem…Thank you so much


    Profile photo of maya


    omg it solved worked fine thanks for the solution DQFanSurvey


    Profile photo of pinni


    Tell Garden Fresh Survey, the restaurant is looking for your candid feedback to learn your overall satisfaction with Souplantation & Sweet Tomatoes foods and services.
    Tell Garden Fresh Survey


    Profile photo of ronny


    Thermal imaging and night vision technology is often confused, but each have their own unique features and strengths. The potential uses for


    Profile photo of jack


    Tested devices with which the camera works: Google Pixel XL, Google Nexus 6P, Samsung Galaxy S8, Samsung Galaxy S8+, Samsung Galaxy A5.href=””>website

Viewing 12 posts - 1 through 12 (of 12 total)

You must be logged in to reply to this topic.