c,file-io,pebble-watch,cloudpebble
You can not read/write to files, use file descriptor or any of the f* functions in the Pebble SDK. If you want to store data on the watch, you should look into the Persistent Storage API....
javascript,pebble-watch,pebble-sdk,cloudpebble
I am not sure if there have been changes since the above answer, but it looks like there is in fact a way to include additional resources while keeping things tidy. On the pebbleJS page, there is the following section with an some information on the subject. GLOBAL NAMESPACE -...
pebble-watch,pebble-sdk,cloudpebble
Nope, unfortunately this isn't currently possible. Maybe in the future this will be possible by passing around some deep links.
javascript,pebble-watch,cloudpebble,pebble-js
You need to rewrite your application in C. This is currently the only way to write Pebble apps that run without a phone.
pebble-watch,pebble-sdk,cloudpebble,pebble-js
I increased the buffer size of progress_buffer, and the watchface stopped crashing. I found the value to be a minimum of 37 for the code to work. I guess the buffer needs to store more than the dots, e.g. the blank spaces.
Finally i found out solution to my question.. Here explained well. I have changed my c code to like this APP_LOG(APP_LOG_LEVEL_INFO, "Message received!"); Tuple *t = dict_read_first(iterator); while (t != NULL) { // Long lived buffer static char s_buffer[64]; APP_LOG(APP_LOG_LEVEL_INFO, "Message ready to get!"); snprintf(s_buffer, sizeof(s_buffer), "'%s'", t->value->cstring); text_layer_set_text(hello_text_layer, s_buffer);...
pebble-watch,pebble-sdk,cloudpebble
Your problem is that the JS is taking longer than the app to start. The message is sent to the JS simulator before it's ready to receive it. If you "shake" the watch (send a tap event), it will try again to transfer an image. To interact with the emulator,...
javascript,pebble-watch,pebble-sdk,cloudpebble,pebble-js
You are getting an error because < isn't allowed where you are putting it. You have a < because you have placed some HTML in the middle of your JavaScript. You say, in the comments, that you are using EJS, but if you were using the syntax shown on the...
Pebble.js is built using PebbleKit JS, so anything you can do with PebbleKit JS can be done in Pebble.js, including settings pages.
pebble-watch,cloudpebble,pebble-js
I believe what you're seeing is Pebble's handling of menus. From my experience, Pebble.js only displays a few menu items (up to 5 or so?), and will load the other menu items as the user scrolls down to them. As long as those items reappear, I'm not sure there's much...
c,arrays,pebble-watch,cloudpebble
The problem is this line static char *die_label = "D"; That points die_label to a region of memory that a) should not be written to, and b) only has space for two characters, the D and the \0 terminator. So the strcat is writing into memory that it shouldn't be....
You need to be connected to CloudPebble at the moment of the crash to get any logs. If you are, you should see something like this: [INFO ] E ault_handling.c:68 App fault! {0a7575eb-e5b9-456b-8701-3eacb62d74f1} PC: 0x8019c3d LR: ??? [WARNING ] Program Counter (PC): 0x8019c3d ??? [WARNING ] Link Register (LR): ???...
javascript,android,pebble-watch,pebble-sdk,cloudpebble
Note: Some of the links below go to Pebble API documentation, which at the time of writing is only accessible if you're logged into the developer site with your Pebble account. Getting started with Pebble development can be a little overwhelming. There are lots of moving parts, some of which...
javascript,pebble-watch,cloudpebble,pebble-js
Pebble.js streams the data of lists to the watch on demand. Six seconds sound like a lot and I have not seen that much delay but there is not much you can do short of re-building your app with the C SDK.
At build time, the Pebble SDK tries to produce the smallest possible GBitmap for each input image you provide in your appinfo.json to save precious RAM at runtime. Even when running on Basalt this could mean that you end up fewer bits per pixel (e.g. GBitmapFormat4BitPalette) where each byte on...
javascript,c,pebble-watch,pebble-sdk,cloudpebble
Solved, thanks to pedrolane on the Pebble forums. I'd forgotten to add the AppKeys in appinfo.json: "appKeys": { "day-date": 0, "gmt-offset": 1 }, (Note: If you're using CloudPebble, define these like so, on the Settings page: { "day-date": 0, "gmt-offset": 1 } i.e., without the "appKeys":, otherwise the settings page...
javascript,pebble-watch,pebble-sdk,cloudpebble
CloudPebble is lying, you can use it. I'll put a report in to fix it, so it doesn't lie to you. If you want to you can wrap the erroneous line like this so jshint won't complain. /* jshint ignore:start */ var byteArray = new Uint8Array(buf); /* jshint ignore:end */...