3

I'm looking to get a clearer idea of the factors that affect the maximum allowed size of app messages incoming to the watch. The maximum size that the SDK guarantees will work is 124 bytes, and the docs say that "in some context, Pebble might be able to provide your application with larger inbox/outbox. You can call app_message_inbox_size_maximum() and app_message_outbox_size_maximum() in your code to get the largest possible value you can use."

I tried this out on my pebble and app_message_inbox_size_maximum() returned 2044 (which is more than enough for my app), but I imagine that's not reliable across pebbles? What is the "some context" the docs mention?

Charles
  • 50,943
  • 13
  • 104
  • 142
Ismail Badawi
  • 36,054
  • 7
  • 85
  • 97
  • I forked an app (https://github.com/arytbk/jewishclock2) and ran it in the cloudpebble emulator. I found that on the emulator Aplite it has a bug, but in my Pebble Time it's ok. It turned out that in the emulator (but only in Aplite) it fails because of app_message_open(app_message_inbox_size_maximum(), 32); Changing it to app_message_open(app_message_inbox_size_maximum()/2, 32); "fixes" the problem in emulator. Today I asked my friend who has a Pebble 1 to test the original version, and it works for him (though he uses the https://elbbep.cpfx.ca/ firmware) Is this an emulator bug? – Gavriel Oct 13 '16 at 23:51

2 Answers2

1

When developing apps, I'd say the biggest thing to remember is that the message has to exist within your app's memory space while it's being processed. app_message_open allocates the space for you, which comes out of the 24kb that contains your app binary and app heap (see the Pebble Dev FAQ). So, ~2kB for AppMessages may or may not be a problem.

However, the app_message_xxx_size_maximum functions can't know how much RAM you are eventually going to use for other stuff. Since you can't resize the inboxes, you have to get it right the first time using your own judgement.

Beyond that, who knows. PebbleOS is closed source, so there's no easy way to figure out what's going on under the hood. But, we can try! First, since there is no way to check the in/outbox size, we might assume that the OS does not resize the inbox/outbox after it has been created. Then, since the OS does not allow >1 app to run at once, one could surmise that the size limits would be consistent across app launches on the same hardware. Finally, the maximum size should only get larger as time goes on, since reducing it would run the risk of breaking apps that relied on a particular size.

cpf
  • 409
  • 4
  • 10
1

There are two factors that will impact how much memory is available:

  1. Are you talking to a JavaScript program or to a iOS/Android program using the PebbleKit iOS/Android libraries?

    In the case of JavaScript, you will have much more memory available because Pebble will use the same buffer that is used for installing apps and upgrading the firmware. Unfortunately the channel to communicate with third party apps written with the PebbleKit native libraries is much smaller (about 500 bytes).

  2. The version of Pebble OS you are using

    There will be small differences between versions but nothing major.

Community
  • 1
  • 1
sarfata
  • 4,625
  • 4
  • 28
  • 36