There are quite a bunch of special characters missing from the default keyboards in iOS for iPhone and iPad – in any language. One of them is the “not equals” ≠ sign.

iOS Keyboard Not Equals Sign Missing

But how can you add missing characters to iOS?

These are the 2 easiest solutions…

  1. copy-pasting from somewhere else
  2. or use a custom text replacement shortcut

Solution 1: copy-pasting the not-equals sign

First of all, here it is – for copy-pasting the not-equals sign:

Solution 2: adding a text replacement shortcut for the not-equals sign

Secondly, if you want to use it regularly, follow these steps to add a custom text replacement shortcut:

  1. Open the iOS Settings app
  2. Go into the “General” settings
    Step 1 - iOS General Settings
  3. Open the “Keyboards” setting
    Step 2 - iOS Keyboard Settings
  4. Tap on the “Text Replacement” option
  5. Add a new entry by using for example:
    • Phrase
    • Shortcut: !=

    Step 3 - Add Text Replacement for Not Equals Sign

  6. Done – now you can type “!=” anywhere in iOS, and it will automatically be replaced with the not equals sign .

It should be self-speaking that, using this method, you can add a shortcut for any missing special characters in iOS.

 

Share:
  • 9
  • 5

9 thoughts on “Where’s the missing not equals sign ≠ in iOS on the iPhone or iPad?”

  1. “ne” might insert the character into words, and “!=” requires too much mode switching. So, I went with “+=”, because the characters are right next to each other in symbols keyset. Really, though, holding down the = key should get you a pop-up option for ≠.

  2. Thank you. Just another example of Tim Cook China’s rent boy spending more apple resources on SJW BS than on improving iOS.

  3. Thank you guys for pointing out that Apple has finally added the ≠ sign by default with the iOS 13 update! 👍

  4. Thank you for the tip. Although any savvy person ought to know about the “text replacement” setting, I for one have found mobile ios to be so tremendously, aggravatingly, impossibly idiosyncratic (i.e. I guess it’s written for people whose brains are wired differently from mine), and the nuisance shortcomings are so numerous, that I no longer try to make any sense of it. Point being, I now deal with problems on an as needed basis, & I appreciate your showing me the way in a land where documentation is sparse.
    2nd point. It’s swell that ios 19 (hyperbole to emphasize a point) includes the ≠ character. But of the >3GB of additional code that Apple wants stored and running on my tablet, this single character is so far the ONLY ~8 bits that in any way is needed by or desirable to me. So as much as some would insist that one should always be running all the latest updates, I think I’ll stick with the technique you showed.
    Thanks again.

Questions? Suggestions? Let us know with a comment!

This site uses Akismet to reduce spam. Learn how your comment data is processed.