In over 20 years of cell phone usage, this issue has to be the single most frustrating problem I have ever encountered. Absolutely incredible the number of Samsung owners who are having this issue and totally ridiculous that no official solutions from either Samsung or Google have been issued.
Over the last couple of months [~ 1 year old S4 Mini Duos i9192 international version], I have been experiencing this insane problem. I have read nearly every post and thread available online about this matter. I have tried all of the offered solutions without long-term success [with the exception of disassembling the phone and placing foam on the SIM tray ribbon].
However, I have finally made a single change on my i9192 phone settings which, for the last 48 hours, seems to have stopped the problem from recurring.
Phone details:
Samsung S4 Mini Duos i9192 [int'l version] - Android 4.2.2 Rooted - Baseband i9192XXUAMF9
The single change I made is under Jellybean Settings > More Networks > Mobile Networks > Network Mode...for both my SIM cards.
Originally, the network mode was set as GSM/WCDMA (auto connect), especially for main SIM 1.
I changed the option to GSM Only.
That's it.
No clue if this will be a long-term solution to the issue or why it would even make a difference at all. I can only report that 48hours+ and I have not had a single recurrence of this pathetic SIM CARD REMOVED error since making this change to GSM ONLY.
Just throwing this out there for anyone else who may be having this issue to possibly try out.
Good luck everyone...
-lestatar
UPDATE:
Well, it has been 5 whole days since I made the change above and the amazing news is that I have not had a single recurrence of the issue.
It is looking like one cause of the problem may be this setting, which, if set to Mobile Networks GSM & WCDMA (autoconnect) may cause the error. Guessing this setting may have issues with local carriers and how they change each mode whenever needed due to limitations in signal range/etc....
At least in MY case for this issue.
Incredible...both the severity and widespread nature of this problem and also the seemingly endless "solutions" that have varying success for each case.
UPDATE 2:
Well, since I made that tiny change, I have now gone 9 consecutive days WITHOUT getting this ridiculous error. Confidence is getting high that for me the problem is now gone for good.
I am now convinced, at least in my case, that the problem was indeed caused by the phone setting for GSM>WDCMA automatic handoffs according to network availability was working improperly.
Amazing...just amazing.
YMMV...
-les