I’m building an Alloy-based app that runs without errors or warnings until I add the Accelerometer service:
Despite the warning, the service still appears to work correctly. Running:
pebble emu-tap --direction x+
successfully triggers the onTap callback and logs the expected output.
The App looks like working as expected. No error later on in the process.
Installing app...
App install succeeded.
[10:05:50] xsHost.c:155> instruments key: Pixels drawn,Frames drawn,Timers,Files,Poco display list used,Piu comm
[10:05:50] xsHost.c:155> d List used,System bytes free,Chunk used,Chunk available,Slot used,Slot available,Stack
[10:05:50] xsHost.c:155> sed,Stack available,Garbage collections,Keys used,Modules loaded,Parser used,Floating P
[10:05:50] xsHost.c:155> nt,Promises settled
[10:05:50] xsHost.c:155> Found mod "pebble.moddable.tech"
[10:05:50] xsHost.c:155> instruments: 0,0,0,0,0,1,0,0,0,92624,3216,8192,7344,8176,1712,6144,0,132,0,0,0,0
[10:05:50] essage_outbox.c:72> app_message_open() called with app_message_outbox_size_maximum().
[10:05:50] essage_outbox.c:73> This consumes 8200 bytes of heap memory, potentially more in the future!
[10:05:50] message_inbox.c:16> app_message_open() called with app_message_inbox_size_maximum().
[10:05:50] message_inbox.c:17> This consumes 8200 bytes of heap memory, potentially more in the future!
[10:05:50] pkjs> ./~/@moddable/pebbleproxy/proxy.js:21:0 @moddable/proxy launched
[10:05:50] pkjs> ./src/pkjs/index.js:335:0 PebbleKit JS ready
[10:05:51] xsHost.c:155> instruments: 0,3,0,0,0,2,0,0,0,74636,4964,5468,18304,19440,2864,6144,31,134,1,0,92,7
[10:05:51] pkjs> ./src/pkjs/index.js:216:0 sendAppMessage history ok
[10:05:52] xsHost.c:155> instruments: 0,1,0,0,0,2,0,0,0,74636,4436,5468,14224,19440,2928,6144,4,134,1,0,1496,0
[10:05:53] xsHost.c:155> instruments: 0,0,0,0,0,2,0,0,0,74636,4436,5468,14224,19440,208,6144,0,134,1,0,0,0
[10:05:53] xsHost.c:155> Starting accelerometer now...
[10:05:53] accel_service.c:442> Not enough memory to subscribe
[10:05:54] xsHost.c:155> instruments: 0,0,0,0,0,1,0,0,0,74636,4472,5468,14496,19440,816,6144,0,134,1,0,0,0
[10:05:55] xsHost.c:155> instruments: 0,0,0,0,0,1,0,0,0,74636,4472,5468,14496,19440,208,6144,0,134,1,0,0,0
[10:05:56] xsHost.c:155> instruments: 0,0,0,0,0,1,0,0,0,74636,4472,5468,14496,19440,208,6144,0,134,1,0,0,0
[10:05:56] xsHost.c:155> single tap x+
[10:05:57] xsHost.c:155> instruments: 0,0,0,0,0,1,0,0,0,74636,4568,5468,14656,19440,784,6144,0,134,1,0,0,0
[10:05:58] xsHost.c:155> instruments: 0,0,0,0,0,1,0,0,0,74636,4568,5468,14656,19440,208,6144,0,134,1,0,0,0
[10:05:59] xsHost.c:155> instruments: 0,0,0,0,0,1,0,0,0,74636,4568,5468,14656,19440,208,6144,0,134,1,0,0,0
[10:06:00] xsHost.c:155> instruments: 0,0,0,0,0,1,0,0,0,74636,4592,5468,14688,19440,688,6144,0,134,1,0,3,0
Pebble Tool v5.0.35 (active SDK: v4.9.169)
I’m building an Alloy-based app that runs without errors or warnings until I add the Accelerometer service:
As soon as this is initialized, the emulator logs:
Not enough memory to subscribe
Despite the warning, the service still appears to work correctly. Running:
pebble emu-tap --direction x+
successfully triggers the onTap callback and logs the expected output.
The App looks like working as expected. No error later on in the process.
Questions: