<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I knew about the todo, but I missed the deadline:<br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<blockquote type="cite"><strong style="box-sizing: inherit;
font-weight: bold; color: rgb(33, 33, 33); font-family: Roboto,
sans-serif; font-size: 16px; font-style: normal; font-variant:
normal; letter-spacing: normal; line-height: 24px; orphans:
auto; text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 1; word-spacing: 0px;
-webkit-text-stroke-width: 0px;">The C2DM service will be shut
down completely on 10/20/2015</strong><span style="color:
rgb(33, 33, 33); font-family: Roboto, sans-serif; font-size:
16px; font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: 24px; orphans:
auto; text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 1; word-spacing: 0px;
-webkit-text-stroke-width: 0px; display: inline !important;
float: none;">.<span class="Apple-converted-space"> </span></span></blockquote>
<br>
...and it seems this just happened, Android push notifications are
no longer working.<br>
<br>
Anybody familiar with GCM?<br>
<br>
I'll have a look...<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 06.07.2014 um 02:09 schrieb Mark
Webb-Johnson:<br>
</div>
<blockquote
cite="mid:49BA4BBD-3971-4336-9194-4205C75951E8@webb-johnson.net"
type="cite">
<pre wrap="">Lee,
Google's habit of obsoleting APIs and services is incredibly frustrating. We just had to do this for the maps API, and it was a pita. While transition of c2dm->gcm is not hard, it is not backwards compatible so we have to support both until no one is left using c2dm (which could be a while as android users often can't update to the latest OS version). That said, gcm is API level 8 (Android 2.2) so not too bad.
The c2dm works by using the same account as used to sign binaries for the play store, so it has to be private. If you roll your own server, you need to also sign your own binaries (or re-sign the existing ones and side-load to the phone). That is the way c2dm works, and iOS is similar with its APNS.
One workaround I am very willing to do is that we already have a mechanism for servers to inter-connect to the root <a class="moz-txt-link-abbreviated" href="http://www.openvehicles.com">www.openvehicles.com</a> server. I am willing to introduce a mechanism where push notifications, by configuration, could be sent over that inter-connect and then APNS/C2DM/GCM done from the root (using its credentials). It is quite simple to do - just hasn't been a priority.
Regards, Mark
</pre>
<blockquote type="cite">
<pre wrap="">On 6 Jul, 2014, at 6:48 am, Lee Howard <a class="moz-txt-link-rfc2396E" href="mailto:lee.howard@mainpine.com"><lee.howard@mainpine.com></a> wrote:
I've got my own OVMS server going. However, I wasn't seeing notifications on my phone (Android) since moving away from tmc.openvehicles.com. Looking at the ovms_server.pl code it appears that ovms_server.conf requires this section:
[c2dm]
email=<email>
password=<password>
accounttype=<unknown>
[This "c2dm" section, along with the "server", "master", and "log" sections are undocumented in the docs/HOWTO.server.txt file.]
Okay, so it would seem that I need to set-up a C2DM account with Google and put that info into the conf file. But, Google has deprecated C2DM in favour of Google Cloud Messaging (GCM), and Google is not granting any new C2DM accounts...
<a class="moz-txt-link-freetext" href="http://developer.android.com/google/gcm/c2dm.html">http://developer.android.com/google/gcm/c2dm.html</a>
Is the C2DM account used by tmc.openvehicles.com a generic account that can be used by other OVMS servers? I suspect that it is a private account. If so, then push notifications for Android users on independent servers will necessarily require a transition to GCM.
Thanks,
Lee.
--
*Lee Howard*
*Mainpine, Inc. Chief Technology Officer*
Tel: +1 866 363 6680 | Fax: +1 360 462 8160
<a class="moz-txt-link-abbreviated" href="mailto:lee.howard@mainpine.com">lee.howard@mainpine.com</a> | <a class="moz-txt-link-abbreviated" href="http://www.mainpine.com">www.mainpine.com</a>
_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a>
<a class="moz-txt-link-freetext" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<pre wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a>
<a class="moz-txt-link-freetext" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
</body>
</html>