Re: Using Tasker with MotoACTV Smartwatch

170 views
Skip to first unread message

Cptnodegard

unread,
May 23, 2013, 4:05:25 AM5/23/13
to tas...@googlegroups.com
The dev forum is named "Tasker - Developer". Can't get any more clearly labeled than that


Probably force closes due to lack of google maps framework




On Thursday, May 23, 2013 2:04:02 AM UTC+2, Dustin Collett wrote:
The 2 forums are not clearly labeled, and apparently I posted this in the wrong forum yesterday, but I was wondering if anyone could assist in getting tasker (and subsequently app factory created apps) functioning on the motoactv smartwatch. It runs android 2.3.4, using an OMAP3 processor. Screen size is 220px wide by 176 px tall. Typically, apps scale down nicely, however tasker only opens with a black screen, then hangs until android has me force close it. App factory apps do not show anything on the screen, though they install and the device shows them running when I open them.

Also, for what it's worth, the device already has the maps framework files installed (xml and jar files). When testing, I did not have the actual maps app installed, but was not sure if it made a difference or not.

Jenny Hawkins

unread,
May 23, 2013, 8:48:03 AM5/23/13
to tas...@googlegroups.com
Its working on mine, but I'm running the aosp ROM from xda, with gapps flashed. I couldn't get tasker to run at all on the factory or modified factory ROMs. Unfortunately, device-to-device Bluetooth seems to be toast on my ROM.

Cptnodegard

unread,
May 23, 2013, 9:21:53 AM5/23/13
to tas...@googlegroups.com
Jenny, with the ROM you're using, is it possible to do Bluetooth tethering and then use AutoRemote to allow Tasker on the phone to communicate with Tasker on the watch?

Jenny Hawkins

unread,
May 23, 2013, 10:49:38 AM5/23/13
to tas...@googlegroups.com
No, I can't get the watch and my phone to talk over Bluetooth at all. They pair, but that's it. WiFi tether works great, though. I don't know what the battery effects will be for that, though, as I've only used it for a few minutes at a time. There's an app called Intent Over Bluetooth I've been trying to use for device-to-device Bluetooth com, but I haven't been able to get it to work at even with my phone and tablet. (I don't think AutoRemote supports Bluetooth yet.)

I've asked about it in the xda thread for the ROM, but it isn't very active.

Cptnodegard

unread,
May 23, 2013, 11:22:19 AM5/23/13
to tas...@googlegroups.com
BT support for AutoRemote is apparently coming, but the question is if it will work with this anyways, if it has basic BT issues. In theory it should be able to pair just for an internet connection, and thus receive AR messages via the internet. I currently use a Sony Smartwatch, been eyeing the Motoactv, but Tasker integration would be paramount

Dustin Collett

unread,
May 23, 2013, 6:25:49 PM5/23/13
to tas...@googlegroups.com
I was unsure if the development forum was for development of the tasker app itself (of which this is entirely related), or for development of things related to future tasker versions. That is extremely vague, actually, as it only says "developers".

I am the developer of the ClearDroid rom, I am ClearD. It has google maps framework installed, as I created it that way. It did not have the actual maps app installed when I tried the first time though, so I shall try that next. Maybe it needs the physical app to function, even when the standalone app doesn't use its features.

I don't want to have to tether with my phone to run apps, though. Jenny, when I get it working, you'll probably want it too. It'll help out with a lot of functionality, from rebooting into recovery directly on the watch, to starting USB mode, to restarting ADB mode.

Dustin Collett

unread,
May 23, 2013, 6:47:52 PM5/23/13
to tas...@googlegroups.com
Maps app works perfectly, 2 maps framework files are installed (and were required for maps to function, initially), and tasker still hangs at a black screen with "tasker" at the top.

I assume jenny is using ReACTV Rom, as it's the only AOSP rom we have available. My goal is to make it work with all roms, after finding out what the issue actually is.

Dustin Collett

unread,
May 23, 2013, 8:13:17 PM5/23/13
to tas...@googlegroups.com
Another update:

I found in a very old post that someone tried before me to do it, and their logcat result had tasker waiting for a camera app. So, I took an aosp 2.3.4 camera app for the atrix, then re-signed it, and installed it via adb. Also installed maps apk via adb. Still no dice.

Pent

unread,
May 24, 2013, 2:08:45 AM5/24/13
to Tasker

Dustin Collett

unread,
May 24, 2013, 5:01:15 PM5/24/13
to tas...@googlegroups.com
Sent just now, to the "orders" email. I believe this may still be causing the error, even though a camera app is installed:

I/ActivityThread( 1993): Pub net.dinglisch.android.tasker: net.dinglisch.android.taskerm.MyContentProvider
D/szipinf ( 1993): Initializing inflate state
D/szipinf ( 1993): Initializing zlib to inflate
D/dalvikvm( 1993): GC_CONCURRENT freed 264K, 48% free 2839K/5383K, external 15K/519K, paused 3ms+4ms
D/dalvikvm( 1993): GC_CONCURRENT freed 355K, 48% free 3001K/5703K, external 15K/519K, paused 3ms+4ms
D/dalvikvm( 1993): GC_CONCURRENT freed 345K, 46% free 3160K/5831K, external 15K/519K, paused 3ms+3ms
D/dalvikvm( 1993): GC_CONCURRENT freed 225K, 43% free 3429K/5959K, external 15K/519K, paused 3ms+4ms
D/dalvikvm( 1993): GC_CONCURRENT freed 402K, 43% free 3587K/6279K, external 15K/519K, paused 4ms+5ms
I/ServiceManager( 1993): Waiting for service media.camera...
I/ServiceManager( 1993): Waiting for service media.camera...
I/ServiceManager( 1993): Waiting for service media.camera...
I/ServiceManager( 1993): Waiting for service media.camera...
I/ServiceManager( 1993): Waiting for service media.camera...
W/Camera  ( 1993): CameraService not published, waiting...
I/ServiceManager( 1993): Waiting for service media.camera...
I/ServiceManager( 1993): Waiting for service media.camera...
D/WindowManager( 1198): interceptKeyTi keyCode=4 down=true repeatCount=0 keyguardOn=true mHomePressed=false mIsUILocked=true
I/ServiceManager( 1993): Waiting for service media.camera...
I/ServiceManager( 1993): Waiting for service media.camera...
I/ServiceManager( 1993): Waiting for service media.camera...
W/Camera  ( 1993): CameraService not published, waiting...
I/ServiceManager( 1993): Waiting for service media.camera...
I/ServiceManager( 1993): Waiting for service media.camera...
I/ServiceManager( 1993): Waiting for service media.camera...
D/dalvikvm( 1833): GC_EXPLICIT freed 16K, 47% free 2887K/5447K, external 451K/899K, paused 71ms
I/ServiceManager( 1993): Waiting for service media.camera...
I/ServiceManager( 1993): Waiting for service media.camera...
W/Camera  ( 1993): CameraService not published, waiting...
I/ServiceManager( 1993): Waiting for service media.camera...
I/InputDispatcher( 1198): Application is not responding: AppWindowToken{4089c860 token=HistoryRecord{406f89a0 net.dinglisch.android.taskerm/.Tasker}}.  10010.6ms since event, 10006.0ms since wait started

Leonid Feinberg

unread,
Aug 24, 2013, 4:31:10 AM8/24/13
to tas...@googlegroups.com
Did you end up solving this?

Pent

unread,
Aug 24, 2013, 9:18:52 AM8/24/13
to tas...@googlegroups.com
No, sorry.

Pent
Reply all
Reply to author
Forward
0 new messages