Profile

Cover photo
Dan Rozwood
75 followers|48,064 views
AboutPostsPhotos

Stream

Dan Rozwood

Shared publicly  - 
 
Why did I laugh at this? 
1
Add a comment...

Dan Rozwood

Shared publicly  - 
1
Add a comment...

Dan Rozwood

Shared publicly  - 
 
Very creative.
 
Szabolcs Fejes, from Hungary, sent me pictures of this gate with a trick lock he came across.

Convenient to open for the owner, and just the right amont of "security".   No need for something impenetrable when a determined intruder could just climb over the gate.
4 comments on original post
1
Add a comment...

Dan Rozwood

AutoRemote Discussion  - 
 
I put autoremote on my FreedomPop ZTE. I installed the Pro license addon.
I had previously purchased AR from the play store. It is not registering on my ZTE that I own the pro version. I tried uninstalling and reinstalling. Also tried to wipe the play store cache and data. Still not showing up as pro. I think auto notify is acting the same way. What can I do to troubleshoot this?

Thanks! 
1
João Dias's profile photoDan Rozwood's profile photo
2 comments
 
+João Dias I will contact you direct.
Thanks!
Add a comment...

Dan Rozwood

commented on a video on YouTube.
Shared publicly  - 
 
+Tom Scott don't forget about Global Shutter cameras. They snap the whole array in one shot. Usually used for video analytics. A bit more money, but eliminates all strange rolling effects or blurring that happens due to movement vs sample rate.
1
Add a comment...

Dan Rozwood

AutoCast Discussion  - 
 
Just starting to mess with this, one of the Tutorials where it states that I need to put my AutoCast replacement home page on a dropbox account.  I searched around through the community posts and I have not seen anything that really resembles my answer.  
Anyway, I do not have a DropBox account.  DO I HAVE to have one?  Or can I cast a homepage from my phone?  I have a web server that I can run on my phone if needed.
1
João Dias's profile photoDan Rozwood's profile photo
2 comments
 
Thanks! 
Add a comment...

Dan Rozwood

Shared publicly  - 
 
Dan Rozwood originally shared:
 
Anything I can do to help support casting to a Vizio TV? It seems that they use the Chromecast protocol, or most of it.
If I load YouTube, then hit the cast button, the Tv shows up in my list of devices. This is true for Hulu and Netflix.
It does not show in my list of Chromecast services in the Chromecast program.

The Tv has a built in DLNA player called MULTIMEDIA, which allows me to display any DLNA servers. So I would be able to play anything hosted from my Bubble UPnP player on my phone, but what I am trying to do is setup a play list. The built in player only plays 1 show at a time. With my Sony NMP-200 I could have Bubble control it...as I think that is FULL DLNA, where the TV is only photography compliant. That is it can read servers, but not accept control from outside sources (as the Sony does).

With the Cast capability, I could setup a play list and just hit cast and let it rip.

What information or assistance do you need from me to help enable you to
1 reply with a good answer
2 possibly actually add this ability (cast to a caddy capable device...That is not a Chromecast)

Thanks!


1
Add a comment...
Have him in circles
75 people
Fred Kellerman's profile photo
Fred Bratteson's profile photo
Craig Hornsby's profile photo
Bob Maslen's profile photo
Eddie Sanchez's profile photo
Smith James's profile photo
Dave Blackwell's profile photo
Steve Rozwood (Steeb)'s profile photo
Tim Hoyt's profile photo

Dan Rozwood

commented on a video on YouTube.
Shared publicly  - 
 
+potpotsie , not Skype, what you want to do is a a mumble server.
That is designed to do what you want. Instead of typing chat, you talk to each other.
http://wiki.mumble.info/wiki/Main_Page

If you need help setting it up, let me know. I might be able to get some bandwidth on a server I own.

My brother and I use one when we play games together.
1
Add a comment...

Dan Rozwood

Shared publicly  - 
 
Wow
 
Am I the only one who thinks this movie is a Redbox movie? #pixelmovie
1
Jonathon Salm's profile photo
 
Lawl, I want to see that.
Add a comment...

Dan Rozwood

Shared publicly  - 
 
Interesting, for anyone using Greenify and GCM
 
Toubleshooting Guide for GCM Wake-up

GCM wake-up is considered to be one of the most unreliable feature among the experimental features, thus still stuck as donation-only.
There're many factors behind a working GCM push, and trouble with either may lead to the failure of the whole expectation.

Let's discuss the common misunderstandings first.

1. The GCM indicator in App Analyzer does not necessarily mean the app uses GCM for the very notification feature you are expecting.

The GCM indicator only means GCM-related code is in that app's package. But the app may use GCM only for some of its notifications, or only in some criterias, or even the worse, does not use at all. To find out the actual usage of GCM within an app, read the trouble shooting instructions below.

2. Not all notifications are backed by GCM push.

Most instant messaging apps and some social apps use hybrid implementation with GCM and persistent connection (in a background service) to deliver more reliable instant notification, than relying on GCM only. In this case, some of the notifications you have received may not even come from a GCM push.

Hiberated apps lose its background service and thus fall-back to a GCM-only solution, effectively reducing the reliability of notification. If you noticed obvious delay or loss of some notifications after greenifying, it's probably the case.

3. The latency of GCM is affected by many factors, most notably how your carrier restrict the persistent connection.

The foundation implementation of GCM itself is also a persistent connection to Google's server. That means if your devices failed to keep this persistent connection, the latency of GCM is out of control. Carriers all over the world do restrict persistent connection to preserve their limited capability of signalling resources (not the bandwidth), by dropping connections idle for a while. GCM use periodic heartbeat packets to keep the persistent connection, but the default interval of 28 minutes for mobile network is far beyond the connection dropping threshold of some carriers (varying from minutes to hours), causing the persistent connection to drop frequently. As a result, GCM push may delay in minutes, or even half an hour.

There's also a few carriers in the world even block the connections to Google's server in most time(China for example), causing GCM totally out of work.

----------

Now if you believe your app failed to wake up by a GCM push, follow these instructions to find the cause:

1. Open and monitor the logcat (Android log system), either on a USB-connected computer, or on your device with tool app like CatLog.

2. Set the filter to only include keyword (or tag) "GCM".

3. Let's trigger an expected GCM push (by sending an instant message from another device or so). You will soon read a line like this in logcat upon the arrival of GCM push:

I/GCM: GCM message com.joaomgcd.autoremote 0:1426418730738334%0#02db4288f9fd7ecd

This means Google Play services received the GCM message from Google's server and ready to deliver it to the corresponding app (indicated by the package name in the line, com.joaomgcd.autoremote in the example). If you cannot find this line in a reasonable time span, then it may be that app which lose the registion to GCM. Try logout and login your account, or clear the data of the app, or even uninstall and re-install it to restore its registration to GCM.

In all good situation, you should now receive the notification. If not, read on.

4. If the target app is hibernated before the arrive of GCM push and you have activated "GCM Wake-up" feature, then open Greenify ASAP (since it may hibernate again in a few minutes).

You will probably find that app is awake and listed in the "WILL HIBERNATE..." section. In this case, Greenify had managed to wake up the hibernated app and deliver the GCM message to it, but that app may failed to process it correctly and show a notification. This does happen to some apps which can't deal with GCM message upon wake-up. Try trigger another GCM push manually, if the notification shows up this time, that app falls into this category. It's hard to blame the developers for that, since they may not prepare for the arrival of GCM push when their background service is not running. So I'm still trying to figure out a better solution to make "GCM Wake-up" compatible with these apps.

5. If the app still stays hibernated, then the wake-up attempt might fail.

Back to the logcat, you probably read another line like this:

W/GCM-DMM﹕ broadcast intent callback: result=CANCELLED forIntent { act=com.google.android.c2dm.intent.RECEIVE pkg=com.joaomgcd.autoremote (has extras) }

It means the push is not delivered successfully. If you did activated "GCM Wake-up" but still read this line, then it may be Greenify's fault, except if you have disabled the notification of that app in system Settings - Apps - That App - Show notifications (unticked). Greenify checks this setting before trying to wake-up an app to deliver GCM push.

Note: As a reference, try "AutoRemoteLite" with its web interface to trigger GCM push.
29 comments on original post
1
Add a comment...

Dan Rozwood

Shared publicly  - 
 
True
1
Add a comment...
People
Have him in circles
75 people
Fred Kellerman's profile photo
Fred Bratteson's profile photo
Craig Hornsby's profile photo
Bob Maslen's profile photo
Eddie Sanchez's profile photo
Smith James's profile photo
Dave Blackwell's profile photo
Steve Rozwood (Steeb)'s profile photo
Tim Hoyt's profile photo
Links
Basic Information
Gender
Male
Apps with Google+ Sign-in