I appreciate you taking the time to look into this further and even asking around on Discord. Thatās genuinely helpful, and I respect the effort.
Regarding the multiple topics, I understand your point. However, when a problem arises unexpectedly and youāre struggling to find a solution, sometimes you try different avenues in the hope that someone who has experienced the same issue might notice and offer a solution. After all, when your phone suddenly starts malfunctioning, patience isnāt exactly the easiest thing to practise! š
Nevertheless, I understand what youāre saying.
As for the issue itself, Iām not claiming that the security update is definitely responsible. Iām simply pointing out that everything was working normally before I installed the latest security patch, and the problem started afterwards. SIM 2 now takes an unusually long time to activate but ultimately fails to do so. Thatās why I believe the software update deserves closer investigation before the issue is attributed to hardware failure.
Iām also aware that another Phone (2a) user hasnāt experienced any problems after the same update. However, one personās device working normally doesnāt necessarily rule out a software-related issue affecting another device. Differences in device configurations or individual circumstances could potentially be relevant.
Besides, Iāve already contacted the official Nothing Support team by email, so Iāll wait for their response and see what they have to say. Hopefully, more Phone (2a) dual-SIM users will join this discussion, as their experiences could help establish whether this is an isolated case or something more widespread.
Another possibility Iāve been considering is whether this issue could be related to the regional software build. Since my device is running the India build, Iām curious whether other Phone (2a) users in India who installed the same security patch have experienced similar problems, even if users in other regions havenāt.
Iām not claiming that this is necessarily a region-specific bug, but I think comparing experiences across different regions and software builds could help narrow down the cause. It would be useful to know whether this issue is isolated to my device or whether other users running the same build are experiencing something similar.
Anyway, thanks again for taking the time to investigate.