• Seestar
  • Seestar V2.2.0 does not work on my tablet, a Samsung Galaxy

I have been using V2.1.0 and it has been working very well. Updated to V2.2.0 this week and I no longer receive preview images on my tablet. I also have an S20 Samsung phone and it continues to work.

There has been rumor that the RAM requirements have changed with V2.2.0 from 2gb to 6gb. If so, please provide a method of downgrading back to V2.1.0, as I have no need to buy a tablet at this time. I use my existing tablet for outreach using the Seestar S50 and, while I would miss the latest features, Version 2.1.1 works well enough for me.

    OK, let's get this RAM stuff straight.
    It would be ridiculous to require 2-4 GB of RAM to control a device. No way. Seestar app uses a bit more than 500MB when controling your Seestar. In the case if you want to process your images on a mobile device, then you'll need a lof of RAM. 6-8 GB or more. Stacking, registering and other processes use a big amount of RAM. But the control funcions need less than 600MB. I've got an old Samsung Galaxy Tab A 10.1 with 2 GB of RAM. Works perfectly with the Seestar. A bit slow, but no issues at all, even with the new app/firmware.

      Darryl Sorry for the trouble, could you take a picture of the problem?
      And the requirement of RAM in android device has always been 6GB

      Gulyas K
      Totally agree with you, my tablet worked very, very well until the last update and the first release mosaic version 2.1.1 was perfect so I would like to roll back to that also

        I was provided a link by ZWO Seestar tech support (using the bug report feature in the app) that let me install V2.2.0 Build 2.

        This Build 2 of the latest app fixed the problem and my tablet (Samsung Galaxy Tab A with 3gb RAM) is working well again. I am able to see the preview images as they are taken.

        Build 2 did not change the firmware on the Seestar device, so the issue, whatever it was, was fixed by a change in app software only.

        Wighter This has been requested many times on this forum. ZWO is either unwilling or unable to provide a mechanism to roll back to previous versions, even when the newer ones are worse. There seems to be no way but forward, whether you like it or not.

          starnet59 Updates are not the cause of the problem, we keep updating in order to better optimize the product problems and meet the needs of users. Android phones or tablets can use the previous version without updating, but can't use the optimized new version and new features; IOS system will be forced to update due to system reasons. Thank you for your understanding and trust.

          2 months later

          Sorry but this is not correct and not true. I have a Xiaomi 14 with Android 15 phone and it works fine, tablet Xiaomi Pad 6 with Android 14 and it doesn't work, and finally, an old tablet Samsung Galaxy Tab A (2016) with Android 8 AND WORKS FINE. This is not a software related issue, it seems a hardware or model related problem.
          Please, solve this and stop making silly excuses.
          Thanks.

          5 days later

          The later updates for android needs 6gb ram to work, I had to get a new tablet to make it work.

          На андроиде можно расширить виртуальную оперативную память хоть до 6 или более гб. У меня на старом планшете такой фокус сработал.

          This is not correct. My Xiaomi have 8Gb and doesn't work, my old Samsung have 4Gb and it work.
          Try it again...

            9 days later

            cjE8Q42y
            Is there something wrong? How did you determine that? Maybe it could be the wrong version of Android

            Have you read my previous post???, Android 14 is incorrect version??, Android 8 works fine. Please, enlighten me, wich is the correct version???

              [unknown]
              Sorry for the misreading, that may not be a device configuration issue or something else. Does your phone have enough memory left to run?
              Don't be offended, I'm just trying to find out more things to find out why.

              cjE8Q42y
              Sorry for the misreading, that may not be a device configuration issue or something else. Does your phone have enough memory left to run?
              Don't be offended, I'm just trying to find out more things to find out why.

              Write a Reply...