This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

235 Memory Leack

Former Member
Former Member
just one of the two:
- 235 comes with not enought memory on it
- 235 has very bad sw engineering
i point on the second one

this is three example i tested on my unit for two months and several firmware updates:
- delays when switching between screens especially cardio widget
- delays with trasfer data warning
- bad performance (abosolutely erratic data, jumps over 200bpm or under 90bpm during activities) of HR monitor depending of number of installed apps

especially cardio issue seems to a veeeery big BUG :confused:
  • Sorry, was there a question there?

    Since release the FR235 has had a number of software releases and continues to improve. If you have found a bug, please report it. If not, but you are unsatisfied with the performance then you have 2 options. Wait and hope things get better (which it seems they are), or return the product. I, for one, am happy, it's not perfect but I can see Garmin are working on getting it better

    CW
  • None of the things listed have anything to do with memory leaks or not enough memory. That entire post is essentially techspeak gibberish.
  • Former Member
    0 Former Member over 9 years ago
    why gibberish? are you a garmin engineer? or a seller?
    i'm telling you i tested these issues, so what's wrong with it? if it's not memory issue (or bad sw engineering) what else cause bad HR data with three installed app and good/real hr readings with just one?

    i'm quite happy of my 235 too, but i can tell there is some unsolved issues and i share with you (and with garmin support but level of support in garmin is very low nowadays), i repeat: what's wrong with it? :confused:
  • I haven't experienced the issues that you describe. Perhaps the HR spikes/dips you are experiencing have to do with wearing the watch too loosely?? In any case, I doubt this has to do with memory ... at least not in my case ... and I have 5 apps, 3 watch faces and 1 widget installed. Perhaps you have a faulty unit?

    Max
  • Former Member
    0 Former Member over 9 years ago
    i don't think because i have no problems uninstalling the apps but i do with apps installed so i cannot immagine what is the hardware fault in this case
    i tested it with 3 apps, one app and without some default app (meteo and virb) and the HR readings pass from 180 average and 220 uppper to 150/170 with steps according to the number of app uninstalled - the runner is the same, wrist and position is the same, track and activities are quite the same!

    see these activites as example (i have a ton)

    an example with 3 apps installed, just to see what i'm telling:
    https://connect.garmin.com/modern/activity/1159587146
    with virb and meteo widget:
    https://connect.garmin.com/modern/activity/1173330440
    without virb and meteo widget:
    https://connect.garmin.com/modern/activity/1183518699

    the last two activities are quite the same but the second one has a more precise cardio data, at least 5 bpm average less and a smooth track

    i invite you all to give it a try with and without widget and datafield to find cardio difference and share your proofs
  • I can't access your first run; you might have it set to private. I did some testing last night to see if I could reproduce what you're seeing by installing some additional apps and such. I didn't have any luck. My heart rate was actually (and surprisingly) very solid.

    Either way, I think you're grasping at straws by thinking it's a memory leak. You'd need a tool to detect memory leaks during usage, or at least have a way to monitor memory.
  • None of the things listed have anything to do with memory leaks or not enough memory. That entire post is essentially techspeak gibberish.


    This..... LOL.... None of what you described are memory leaks. The 235 is not running 256GB of memory and a 4Ghz CPU and a Terabyte hard drive so you can run every function and app on the planet. It is limited. In fact I am somewhat impressed at how much it does hold and how responsive it is for its size.
    I have not seen any of your issues either, and you will definitely have a HRM problem if the watch is not tight on your wrist.
    Are there issues with the watch, no doubt for some people. Mine has been flawless, or better put for the functions I use it for it has been flawless, and yes I am a hardware software support engineer/manager.
  • and yes I am a hardware software support engineer/manager.


    As am I.

    A plain memory leak would simply run the watch out of memory to do anything. The HR wouldn't become spotty, it would become non-existent and the whole system would likely crash. For the other scenario that some people refer to as a "leak", assuming that it could leak bad data into the HR section, your HR wouldn't be reading 220s instead of 170s... it would be reading random garbage numbers with little to no correlation to each other - the HR chart would either be a straight line on a random bad number from one recurring overwrite, or it would jump all over the place from repeated overwrites.

    You could also search the ConnectIQ Programmer section of the forums and see that the only issues relating to memory leaks are in the GarminConnect Android app, not the watch's ConnectIQ app/widget/watchface system.

    I have had zero performance difference from any # of apps, watchfaces, or widgets installed. You would need many tests containing repeated totally trashed HR data as described above - a single bad run or cadence lock or whatever else doesn't mean squat given that no OHRM 100% accurate to begin with.

    To answer your original complaints -
    Delay between screens is because the watch is not constantly sitting there waiting for your input. It is conserving battery 99.9% of the time, and has to wake itself up from so-called "low power mode" to respond to your button press the first time. Even after that, every screen you switch to requires it to swap in a whole new application - and like GRZLDVT says, this isn't running a quadcore exynos processor with 1GB RAM to hold all the apps constantly in memory for instant results, it's a low-battery-usage watch designed to maximize battery life.

    The transfer data warning is delayed intentionally to conserve battery.

    One bad run with 3 apps vs One good run with 1 app means just about nothing. Come back when you've repeated multiple test runs of the same intensity on the same path with the same HR Firmware installed with 3 apps vs 1 app (because lots of things can affect the HR accuracy a hell of a lot more than how many apps are installed). I have multiple apps installed and there has been no effect on the HR accuracy - what has had an effect is the Firmware updates over the last month in which Garmin actually changes the function on the OHRM.
  • The bug that I still have on my 235 is that with the Garmin Edge 520 often loses the transmission of heart rate.
    I tried all the releases in the 520, it's a problem of the Forerunner 235. With previous versions of the 235 never missed the transfer of cardio frequency. I would like to downgrade, do not understand how to do, the process seems to be different from the downgrade on the Edge 520 where just rename the file in update.gdu and transfer it into the yellow folder. Anyone have any idea of how to perform a successful downgrade on the Garmin Forerunner 235?
    I found older versions here http://gawisp.com/perry/forerunner/ but i don't understand how to put them on 235. Thank you.
  • Former Member
    0 Former Member over 9 years ago
    One bad run with 3 apps vs One good run with 1 app means just about nothing. Come back when you've repeated multiple test runs of the same intensity on the same path with the same HR Firmware installed with 3 apps vs 1 app...


    sorry, just for saying i do not have just 1 run vs another, but i'm testing this over a month of activites - from firmware 4.10 (with abolutely no problems with cardio) to the next updates garmin has released
    paths, workouts intensity, runner, position on the wrist etc... nothing has changed over this month except number of installed apps

    and sorry for "bad naming" it as leak: you ARE engineer, i AM NOT. this is not the point of intereset i think....