I don't know of any other major services that are signing tokens in the way Google does. I suspect (and hope) it will become more common over time.
As far as Facebook and Twitter go, you do have to validate the token with their API, since they are authoritative for issuing it. One thing you can do, to avoid constantly making requests to their API, is to issue your own token that the device will use when talking to your API.
It might look like this:
POST /login?access_token=twitter_token -> contact Twitter's API -> issue and return your own token
POST /api/foo?access_token=your_api_token
With that in place, there is only one call to an external validation service. The rest of the API calls use tokens which you can validate using your own database.