• State Not Answered
  • Replies 7 replies
  • Subscribers 20 subscribers
  • Views 1382 views
  • Users 0 members are here
Options
Related

what have changed in amoled devices since sdk 4.x

_psx_

according to errors on amoled devices

https://forums.garmin.com/developer/connect-iq/i/bug-reports/sdk-4-0-3-4-x-problems-with-arrays-on-some-devices

I suppose there is no layout when onExitSleep is called and user switch off AOD (black screen) - it's impossible to emulate this behaviour on sim.

I'm not sure it connected with sdk 4.x because I've made a refactoring connecting with storage/properties limitation.

  • 0

    it's look like in onExitSleep on amoled there is no even global vars

    Can somebody respond, please?

  • 0 in reply to jim_m_58

    1. I know what is the rule

    2. But in my examples, app run well on:

    - all devices on sim

    - all devices I have access

    and suddenly on venu/venu sq not, so what you expected when I show code? Nobody need anything more because it's enough to start working to fast fix bug. I don't want to spend more time that minimum I don't have to correct my code because there is no bug in my code if it run as as described above  it's Garmin's bug and I think Garmin should be happy to get such info because can fix it's products and instead learning how to report a bug... Sorry, I don't have time for it.

  • 0 in reply to _psx_

    btw my code in many place looks like

    if(venu)...//gramin error, workaround

    {

    }else

    {

    }

    or

    //I have to move this code to ... because from time to time there is an exception here

    //or it must be if(x != y) because if there is if(y != x) on fenix 6X 16.6 there is an error

    Do you think that it's ok? In my opinion and in my life solution is: fix or remove, quality is the most important.

    And you don't have to answer because I'm not going to participate with verbal warfare on obvious topics.

  • 0 in reply to _psx_

    The Garmin folks have all the devices.  If you provide the code they can look at things on the real device and maybe find an error is in your code or in their code.

    That's why they want to see code that shows the issue, and not just a few lines of code.  It also gives them a way to test a fix before releasing it.

    You seem to report things that no one else sees, which is another reason providing the code is needed. Garmin need to see the issue if you expect a fix.

  • 0 in reply to jim_m_58

    1. Maybe they have devices but they always can't always reproduce so solution is ... closing post as complete. And this the difference my cod run well although bug sdk... of course if it is possible 

    2. Fixing even small problem lasts months.... e.g. problem with setColor symbol on buferredBitmap on venu

    3. Of course I've found workaround and bug is rather big, but it's already not my problem, let's wait for consumer they'll write on forum truth if many of app stop working

  • 0 in reply to _psx_

    You'll get better response from Garmin if you supply full code that shows the problem.  Otherwise it could take months for them to just see the problem.  It's not that hard or time consuming to do - just zip up a project that has the problem and pass it on.