Profile cover photo
Profile photo
Eric Mooney
2,618 followers -
'Yes, I feel emphatic about not being static'.
'Yes, I feel emphatic about not being static'.

2,618 followers
About
Eric's interests
View all
Eric's posts


It seems as though run in foreground isn't working. Every day I had to manually open the app to use it which kind of defeats the purpose. I'm on a Nexus 6p with Android 7 1.1
Any ideas?

Post has attachment

Post has attachment

+João Dias - just wanted to report an error in AutoTools Sensors when entering 18 as my value.

17.28.53/ActionArgBundle AutoTools Sensors: extra key not found in bundle:FieldsToGet
17.28.53/E FIRE PLUGIN: AutoTools Sensors / com.twofortyfouram.locale.intent.action.FIRE_SETTING: 5 bundle keys
17.28.53/E AutoTools Sensors: plugin comp: com.joaomgcd.autotools/com.joaomgcd.autotools.broadcastreceiver.BroadcastReceiverFire
17.28.53/E add wait type Plugin1 time 60
17.28.53/E add wait type Plugin1 done

Is there an official place for us to enter bugs? I know this is low priority for you but just wanted to report it.

Thanks,
Eric

Post has attachment
My pictures
PhotoPhotoPhotoPhotoPhoto
12/9/15
17 Photos - View album

Hello! I bought an AutoVera unlock key a while ago. Went to install it on another device and it wants me to pay again. I don't remember this being the normal process. Shouldn't I be able to download it as many times as I want?

+João Dias​- I'm debugging a process and in my autowear log I'm seeing this:

Messages - 2015-01-18 13:50:34.203 - {"object":{"commands":{"doubleTap":"command\u003d:\u003dclosefloatingicon","singleTap":"command\u003d:\u003ddisplayLR"},"height":50,"iconPath":"android.resource://net.dinglisch.android.taskerm/hd_aaa_ext_home","width":50,"x":100,"y":100,"showSentConfirmation":false,"assetIds":["floatingicon"],"id":"FloatingIcon","triggerCommandEvent":true,"openNow":true,"objectIndex":0,"hapticFeedback":true},"objectClass":"com.joaomgcd.autowear.floating.FloatingIcon"}

I've noticed that '=:=' is displaying as '\u003d:\u003d' in the logs. Is this die to something I'm doing wrong or are the logs just escaping the '='?

Is anyone seeing buggy behavior with AutoLocation's geofence in LolliPop? It only seems to be detecting when I'm in or out of the geofence about 30% of the time. It's very sporatic and I dont see a pattern.
I'm suspecting it's Lollipop because things work consistently on a device with KitKat. 

Post has attachment
Wait while more posts are being loaded