Smartwatch Kit Issue

[christopher.allison]

Hello, while the issue im having may be down to my own ignorance, Im having some trouble pairing the assembled smartwatch kit to my android phone. I have tried with the TinyCircuits app, as well as the nRF master control app which picks up the bluetooth signal, but when I try to pair it I get the error message "Couldnt pair with URT device because of an incorrect PIN or Passkey". 
I havent edited the code at all, Im simply using the TinyCircuit Smartwatch code on codebender. Im not sure where to start with all of this. Any help is much appreciated.
Thanks in advance!

[Ben Rose]

I haven't seen or heard of that message in the nRF apps. Try the nRF UART v2.0 app, which should allow you to connect and send a message to the watch- if you send a message starting with 1 or 2, it should display on the watch. Make sure you're using the latest code on codebender, and please let us know what phone and operating system version you have if it still doesn't work.

[christopher.allison]

Ok, so far we have managed to connect the watch to the tinycircuits app that we recoded so it wouldnt crash. It synced the time, and passed some text notifications (only 3). Then the app crashed again, and it keeps crashing. Not sure what other steps to take. We are doing it with windows 8 and windows 7. The phone is a Oneplus One with android 4.4.4. If you have a link to a stable version of the app, or any walkthroughs or tutorials that you could send me, that would be a big help.

[Ben Rose]

If you can post what code changes you've made and any crash reports you're still getting, that would really help us. On my Galaxy S3 with 4.4.2, the app has GUI issues that haven't yet been fixed but will stay connected for the battery life of the watch (currently about half a day) and continues sending the text notifications, so I can't reproduce these crashes.

[ralphcrutzen]

I don't know if this is any help, but this is the exception thrown by the app:

Code: [Select]

04-05 21:37:57.383  10327-10327/com.tinycircuits.tinycircuitsble E/AndroidRuntime﹕ FATAL EXCEPTION: main
    Process: com.tinycircuits.tinycircuitsble, PID: 10327
    java.lang.RuntimeException: Unable to instantiate service com.tinycircuits.tinycircuitsble.bluetoothservice.BluetoothLeService: java.lang.NullPointerException
            at android.app.ActivityThread.handleCreateService(ActivityThread.java:2574)
            at android.app.ActivityThread.access$1800(ActivityThread.java:144)
            at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1287)
            at android.os.Handler.dispatchMessage(Handler.java:102)
            at android.os.Looper.loop(Looper.java:136)
            at android.app.ActivityThread.main(ActivityThread.java:5139)
            at java.lang.reflect.Method.invokeNative(Native Method)
            at java.lang.reflect.Method.invoke(Method.java:515)
            at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:796)
            at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:612)
            at dalvik.system.NativeStart.main(Native Method)
     Caused by: java.lang.NullPointerException
            at android.content.ContextWrapper.getPackageName(ContextWrapper.java:135)
            at android.content.ComponentName.<init>(ComponentName.java:77)
            at android.content.Intent.<init>(Intent.java:3875)
            at com.tinycircuits.tinycircuitsble.bluetoothservice.BluetoothLeService.<init>(BluetoothLeService.java:45)
            at java.lang.Class.newInstanceImpl(Native Method)
            at java.lang.Class.newInstance(Class.java:1208)
            at android.app.ActivityThread.handleCreateService(ActivityThread.java:2571)
            at android.app.ActivityThread.access$1800(ActivityThread.java:144)
            at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1287)
            at android.os.Handler.dispatchMessage(Handler.java:102)
            at android.os.Looper.loop(Looper.java:136)
            at android.app.ActivityThread.main(ActivityThread.java:5139)
            at java.lang.reflect.Method.invokeNative(Native Method)
            at java.lang.reflect.Method.invoke(Method.java:515)
            at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:796)
            at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:612)
            at dalvik.system.NativeStart.main(Native Method)

I have a Nexus 5 with CyanogenMod 11.0.

[gary_f]

If you can post what code changes you've made and any crash reports you're still getting, that would really help us. On my Galaxy S3 with 4.4.2, the app has GUI issues that haven't yet been fixed but will stay connected for the battery life of the watch (currently about half a day) and continues sending the text notifications, so I can't reproduce these crashes.

Hi Ben. I like what you've done with the app so far. Do you have any plans to continue developing it? Or did you just do it as a demo for users to pick up the baton and run with it? Please let me know if you hear of anyone else taking it further or if you make an update.

Wish list for anyone who has the skills or interest:

• Notifications to scroll
• Display Facebook notifications (just incoming call and SMS seem to work at the moment?)
• Watch to initiate synch itself if it's been reset or just started running the code
• Display battery remaining as percentage for better accuracy

The battery lasted 18 hours which is good by your estimate, Ben. I guess it depends how many boards are connected. Showing approx. 25% the graphical battery level was a bit optimistic as it died about 30 mins later.

I wish TinyCircuits sold multi-function boards because it's not practical to have a watch stacked as high as an inch! I don't know why the CPU and USB/battery boards aren't combined as I can't imagine many projects leave out the USB/battery option.
Thanks.

[tinyweasel]

I'm having the exact same problem, and I've tried at least four of the Smartwatch codes on Codebender, and two different models of Xperia Z. Haaaalp...

[Ben Rose]

Hi Gary- we definitely hoped there would be more 'running with it.' A few users have made great contributions, but adding features and proper Android 5.0 compatibility takes a ton of time. Right now we're getting up to speed with an iOS version using Apple's ANCS, then hoping to get some of those features into the Android app.

I'd definitely like to spin a single board version of the watch hardware, but that's a while out for us.

Our USB boards and processor board have been separate so that you can use more than one processor board with a single adapter- processor boards are often embedded in a project without any need for USB. Keep in mind all the battery circuitry is on the processor board, the USB just supplies the 5v source.

[gary_f]

Hi Ben, thanks for your reply last week. It's good to hear from you.

I would have thought all the Apple fans would be flocking to buy the new Apple watch leaving the Android market with a much larger user base for alternative watches, kits and projects.

Keep in mind all the battery circuitry is on the processor board, the USB just supplies the 5v source.

I didn't know that. So why isn't the battery connector on the processor board too? Then we could avoid using the USB board for projects that are tight on space. But then we couldn't upload to the watch and we'd have to remove the battery to recharge. Haha! I'll wait for the combo board or let's hope chunky watches to come into fashion!

[Ben Rose]

Seems like many people have actually gone to iOS for BLE applications- maybe if Google opened up the Android Wear platform in any form.

The battery connector is on the processor board as well- everything except a nice 5V input is on there, but you can still solder on a wire with care.

[baritonehands]

I submitted a pull request for a fix to the Android app. Maybe my version will work for you?

https://github.com/baritonehands/TinyCircuits-TinyScreen-Android-App