HTML desktop notifications not working on Chrome 22

Starting from Chrome version 22, HTML desktop notifications do not seem to work anymore in webapp mode. The following error is thrown each time we execute the following code:

webkitNotifications.createHTMLNotification(notificationUrl);

TypeError: Object # has no method 'createHTMLNotification'

Note that chrome extension are still able to display HTML desktop notifications.

 In smshare we use HTML desktop notification to add behaviours to the notification allowing users to reply to the incoming SMS for example. Because of this issue in Chrome 22 we fell back to classic notification. Fortunately, it is possible to add an event listener on the notification and so we did.

var notificationOnClick = function(){
 notification.cancel(); 
 window.location = (some_where);
};

notification.addEventListener('click', notificationOnClick, false);

The issue was reported here. Vote too if you want a quick feedback on the issue.

Incoming sms to desktop notifications

In this post I will share with you my experience on how to make sure you'll receive your sms as desktop notifications without missing any of them.

Smshare is using some of the cutting-edge HTML5 features supported by Chrome to provide you with more real-time, faster and better communication between your smartphone and your desktop/browser.

Thanks to Websockets, smshare extension and/or smshare Chrome web app brought your with real time sms to chrome notifications, without any unnecessary requests and without having many connections opened and closed needlessly in low-message-rate situations.

However in some environments the WebSocket connection may fail due to intermediary firewalls, proxies, routers, etc. You can check if your environnment is websocket friendly on http://websocket.org/echo.html (if the send button is enabled than it is ok, otherwise you have to wait websocket standardization or jump to the troubleshooting section below).

Even if you don't have websockets support, we are able to fall back to other transport modes so that you keep receiving your sms.

To start receiving your sms on your desktop, you need to enable sms-to-desktop notifications from ether the extension (extension → right click → options ) or directly from the website at : http://smshare.fr/account/remoteCommand.html

In the later case, Chrome will ask you if you want to allow or deny desktop notifications for smshare website, just click on the allow button.

Once activated, you can check that on your smartphone : smshare home screen → menu button → preferences → Incoming sms to desktop

This is a read only preference and you can't change it from the phone for the moment.

Today bonus is that we are rolling out a new feature which allows an easy way to reply to incoming sms from desktop notification.

Troubleshooting:

If you are enable to receive your sms as desktop notifications read the following, may be you'll find an answer.

1- Running smshare web app instead of smshare extension:
Desktop notifications are sent to the extension every time a new sms is received. This is not the case if you've intalled the smshare chrome app which you need to keep open. So if you hadn't installed smshare extension, do it now.

2- 3rd-party SMS app:
If you have installed an sms application on your smartphone make sure that it doesn't swallow incoming sms event. For example Go sms pro has this feature and you need to make sure it is disabled: Go SMS Pro → menu button → Settings → Receive Settings → uncheck disable other message notification.

3- Firewall issue:
Avast antivirus on a windows machine for example will block all websocket connections, even if you make an exception in avast, it doesn't seem to work. Smshare will fall back to other transport modes (like long polling, Adobe Flash socket, …).
As websocket is the best mechanism, you may want to disable the network shield and stop the network agent, but you are warned that if you have any security problem it will be on your own responsibility, do not do it if you are not sure about it.

4- Notification permission request issue:
Sometimes, when Chrome ask you if you want to allow or deny desktop notifications for a website, and you click on the allow button, you are still unable to receive Desktop notifications.
We have been experiencing this problem after a fresh install of Chrome 12.0.742.124 on Debian 6 (squeeze, 64 bits), and then syncing data with Google account. We needed to start Chrome from a new configuration directory to get the permission correctly installed and notifications working. The user profile directory can be found in ~/.config/google-chrome
Here is a ticket to a bug report, which may not be related to the same problem we've got.
http://code.google.com/p/chromium/issues/detail?id=80063

Kudos goes to these new hosting platforms we are using: Joyent, Dotcloud, cloudfoundry and the hacky Nodester. Smshare try to spread load among these servers to keep each instance running smoothly.

smshare 1.1.8

Smshare 1.1.8 has been released since January 30, 2011. We are now using the great feature of C2DM (Cloud to Device Messagin). Thus, smshare doesn't do frequency requests to retrieve new SMS but is notified through the cloud as soon as you submit the SMS.

This feature allows better battery life saving and instantaneous SMS transmission.

The C2DM is available for Android 2.2 (Froyo) or newer only. For those of you using previous versions of Android, smshare rolls back automatically to the frequency mode.

We are already working on the next version of smshare. We will be adding a new screen that shows the history of outgoing SMS (Sent from Chrome)

We have also created a Google-group to discuss about smshare.

The website will be updated also to allow SMS submission from any browser.

See you in a couple of weeks.

Connect to your dashboard on www.smshare.fr

We have updated www.smshare.fr to introduce several improvements. The three main changes are:

• Dashboard added.

• Remote control of your smartphone.

• English language support. Do not worry about the French language which is still there. There are now two languages.

Once connected on your user space you can enable or disable smshare features.

The only available remote command today is enable / disable incoming sms forward to mail box.

This is so handy when you forgot to take your smartphone with you and you want to read your incoming sms.

You can also change your email address or password. Other new features are coming soon such the possibility to send text messages directly from the website.

The application as well as the Google Chrome extension have been updated.

smshare 1.1.4 for android is out

The most important feature of this new release is: Receive incoming sms by email.

You just need to activate the option in the preference menu:

Obviously, smshare must be connected and running in the background. Check your spam folder if you don't receive emails from smshare.

Behind the lot of code optimization, this new version includes many bug fixes. The HTC Tattoo was having troubles when inserting sms in the history.

This was caused by a missing permission. We have added it so don't panic if you see the market asking for a manual upgrade.

Finally, I want to thank Alberto for its collaboration. Also, many thanks to Matthieu (First Donor since smshare launch).

New features are under development, so stay tunned.

Android smshare 1.1.1 is out

This new version supports devices with small screen like HTC Wildfire. A preferences menu has been added.



You can now choose the refresh interval. This is the frequency at which the application connects to smshare server to check if there is new sms awaiting delivery.



By default, the refresh interval is set to 2 minutes which is a good value that save the battery life and keep the application reactive. But you can choose any value.



Remember: the smaller interval, the more battery life will be used.

Log handling in javascript

http://smshare.blogspot.com/2010/08/gestion-des-logs-en-javascript.html