I called the number you listed, and they confirmed that iMessage is already turned off for that number (which I did on my iPhone after switching to a Nexus 5 as well).
Most of my friends' iPhones will still send iMessages to me, and most of the time their phones don't even say delivery of the messages failed.
The tech support guy at 1-800-MY-APPLE told me that I should ask all of my friends to remove their existing text message threads with me from the messaging app. As the only proposed solution to my problem, this is already annoying enough. To make matters even worse, I just had one of my friends do exactly what they suggested, and his phone is STILL trying to send me iMessages.
It's unbelievable that Apple shows this little regard for their former customers. (Not to mention the fact that as an owner of several Apple products, I'm actually a current customer.)
From what I understand, it's less of a deliberate "HAHA SCREW YOU" and more of a caching issue on their iMessage registration side. The removal of my number took around 24 hours to propagate to their services (e.g. if a person who didn't have a thread with me put in my number, it would show green not blue) and I had to have some friends delete our chat history since my iMessage-ness was cached on their phone.
I think Apple only checks iMessage registration in pull format, e.g. when someone toggles iMessage on/off on their phone, rather than constantly checking it through some "does this phone have service" background test.
Also you don't have to call tech support. You can deregister iMessage from Settings (by turning it off) before you activate a new phone.
For bonus points, take care of false positives in this system by storing enough metadata in iMessage to deduplicate the iMessage and SMS copies.
I'd say the problem is they're keeping you signed in for too long. If my phone doesn't check in for 24 hours, shouldn't it un-register me at least until I next check in?
Apple: Broken by design, broken at inception.
Making it possible to deregister by logging into your Apple Account over the web would deal with 100% of the problem, which is people not being aware of the issue before switching off of iOS.
Edit: someone on this thread has confirmed
They could release an iMessage client for Android and PC.
It's their technology. Why should I provide the fix of a system that's not built by me, and have no control over it?
It's like saying, user x can't use a website, so he/sh should find out that there is a javascript error due to browser compatibility, and then the USER has to propose a solution with the fix in the javascript to the website owner.
Can't you assume that if a phone has iMessage open, you assume that number is active and poll to send keepalives. If the user has not opened iMessage for a while, you disassociate the number with iMesage. Before trying to send a message via iMessage, the server would check and reply if that user is still associated, if not the phone will fallback to SMS.
I know a lot of people are saying that this shouldn't even have to be a step when you switch phones, but the fact is that you chose to use iMessage for the features. It could have been turned off at any time, they are not forcing you to use it.
It would be great if there was a way to fix this without having to call (or unregister your phone number from your apple id), because of not being able to know that it's happening. But it's not like Apple is deliberately trying to keep your messages hostage. Besides, you've already switched phones.
Source: https://twitter.com/adampash/status/466316191230087168
It also just sounds like there was a bad experience with a particular tech support rep, who may be new. In my experience, these issues are ALWAYS exceptions to the $20 fee. If the 'standard' workarounds don't fix it, they will escalate you to a supervisor and put in a ticket with engineering who will resolve the issue within 48 hours.
Maybe OP will see this and give their tech support another shot. If not, the token expires in about 28 days.
*This information is less than a year old, but rules may have changed.
This is false. I just called 1-800-MY-APPLE (details in my reply to GP) and they said I had already deactivated iMessage for the number and that I needed to tell all of my friends to delete their existing threads with me. And then even that did not fix the problem.
It has been about a week and I still cannot receive text messages from iPhone users I've iMessaged in the past.
What is perhaps most frustrating is that Apple seems incapable of changing the situation. Adding insult to injury, Apple is requiring that I pay a $20 fee to speak with a technician.
This does not follow.
If I change water providers, the previous water provider does have the right to stop me from receiving more water.
Sounds like that doesn't happen.
Of course if you just throw the phone away without ever doing something to indicate it's no longer in use (to Apple, not your cell carrier) then the results are more sane. That can't happen to every one of these people though.
If my phone is stolen, so I wipe my phone via MDM. I still need to communicate, so I can use my Mac or iPad to do so transparently to the other parties.
This is a common issue whenever you do caching. Outlook fubars contacts whenever you migrate Exchange users to or from a system.
However, all it took from me was a call to Apple's customer service, I told them I had just switched off my iPhone and no longer got texts from people with iMessage and they immediately sent me to a tech that fixed the problem for me.
Have you been explaining it correctly when you call? All I said was "I had an iPhone until last week, switched to another phone but I'm still registered for iMessage"
Edit: According to my phone I called 1-800-692-7753 (Which is just 1-800-MY-APPLE) and my call took 8 mins 25 seconds total. Not too bad of an experience.