Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
S4 i9505 SIM card not detected #44
Comments
thestinger
added
the
Type: bug
label
Oct 13, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Oct 13, 2015
Contributor
There was a similar issue in the past due to missing firmware, but I thought it was dealt with. Does wifi work for you?
|
There was a similar issue in the past due to missing firmware, but I thought it was dealt with. Does wifi work for you? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
bitterman1970
commented
Oct 13, 2015
|
Yep, wifi is absolutely fine |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment|
Can you try the oldest build that's published? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
bitterman1970
commented
Oct 13, 2015
|
Will try with the oldest build I can see, 1002 |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Oct 13, 2015
Contributor
The old problem that's now fixed also caused the Baseband version entry in Settings -> About phone to appear as Unknown instead of listing the version. That's worth checking.
|
The old problem that's now fixed also caused the Baseband version entry in Settings -> About phone to appear as Unknown instead of listing the version. That's worth checking. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Oct 13, 2015
Contributor
That part works for me on the latest build but I'll need to check out the SIM card issue.
|
That part works for me on the latest build but I'll need to check out the SIM card issue. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
bitterman1970
Oct 13, 2015
First thing I did was compare the baseband on the Cyanogenmod build and the 1013 Copperhead build and they were the same
bitterman1970
commented
Oct 13, 2015
|
First thing I did was compare the baseband on the Cyanogenmod build and the 1013 Copperhead build and they were the same |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Oct 13, 2015
Contributor
One easy thing to try would be enabling PaX soft mode in Settings -> Developer settings and rebooting (needs to be unlocked by repeatedly clicking on the build information in About phone). I don't think that's the issue though.
It would be helpful if you could provide the logs from adb logcat.
|
One easy thing to try would be enabling PaX soft mode in Settings -> Developer settings and rebooting (needs to be unlocked by repeatedly clicking on the build information in About phone). I don't think that's the issue though. It would be helpful if you could provide the logs from |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
bitterman1970
Oct 13, 2015
Okay, going to try the 1002 build in a while, will also try to get the logs.... Although I'm a bit of a noob moron at this stuff lol
bitterman1970
commented
Oct 13, 2015
|
Okay, going to try the 1002 build in a while, will also try to get the logs.... Although I'm a bit of a noob moron at this stuff lol |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Oct 13, 2015
Contributor
No problem. I'm just very eager to fix it. I use a Nexus 5 as my main device so the SIM card features on the S4 don't get tested much. It's possible it broke everywhere, but I'd expect that someone would have told me by now. It's more likely that there's a problem specific to the radio in some regions.
|
No problem. I'm just very eager to fix it. I use a Nexus 5 as my main device so the SIM card features on the S4 don't get tested much. It's possible it broke everywhere, but I'd expect that someone would have told me by now. It's more likely that there's a problem specific to the radio in some regions. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
bitterman1970
Oct 13, 2015
OK, tried 1002 build, same issue...... Will try to get logs tomorrow and I'll get them off to you.
bitterman1970
commented
Oct 13, 2015
|
OK, tried 1002 build, same issue...... Will try to get logs tomorrow and I'll get them off to you. |
thestinger
added this to the Beta release milestone
Oct 13, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
bitterman1970
Oct 14, 2015
Trying to attach logcat.txt but not being allowed to...any other way i can get it to you?
bitterman1970
commented
Oct 14, 2015
|
Trying to attach logcat.txt but not being allowed to...any other way i can get it to you? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment|
You can email it to daniel.micay@copperhead.co. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
bitterman1970
commented
Oct 14, 2015
|
Email sent |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment|
Okay, got it. I'll look into it in a bit. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
bitterman1970
commented
Oct 14, 2015
|
First time I've ever used logcat, so I hope it was of some use. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
bitterman1970
Oct 14, 2015
As I said, I went back to build 1002 and was still getting the same issue...
bitterman1970
commented
Oct 14, 2015
|
As I said, I went back to build 1002 and was still getting the same issue... |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Oct 14, 2015
Contributor
Yeah, the logs pointed me in the right direction but I can replicate the problem locally so I can get anything I need here.
|
Yeah, the logs pointed me in the right direction but I can replicate the problem locally so I can get anything I need here. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
bitterman1970
commented
Oct 14, 2015
|
I hope you're able to find a solution to this glitch soon :) |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Oct 17, 2015
Contributor
I got this to work by reverting a bunch of changes, just need to narrow it down to one specific feature now.
|
I got this to work by reverting a bunch of changes, just need to narrow it down to one specific feature now. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Oct 17, 2015
Contributor
And... now it's not working. I guess I need to start by building vanilla CyanogenMod. I wonder if this is another case where their public build instructions, etc. do not result in a working build.
|
And... now it's not working. I guess I need to start by building vanilla CyanogenMod. I wonder if this is another case where their public build instructions, etc. do not result in a working build. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Oct 18, 2015
Contributor
Still narrowing this down, just takes a really long time to do builds.
|
Still narrowing this down, just takes a really long time to do builds. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
bitterman1970
commented
Oct 18, 2015
|
No worries, looking forward to testing ;) |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Oct 18, 2015
Contributor
On the positive side, I have it narrowed down to the Bionic changes. Just need to figure out which, and then why it happens. Hoping it's an obvious issue like a simple memory corruption case detected by OpenBSD malloc.
|
On the positive side, I have it narrowed down to the Bionic changes. Just need to figure out which, and then why it happens. Hoping it's an obvious issue like a simple memory corruption case detected by OpenBSD malloc. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Oct 19, 2015
Contributor
It's definitely caused by OpenBSD malloc, but it's unclear what goes wrong. There are no obvious related errors in the logs and seemingly no crashes. Hm...
|
It's definitely caused by OpenBSD malloc, but it's unclear what goes wrong. There are no obvious related errors in the logs and seemingly no crashes. Hm... |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Oct 19, 2015
Contributor
Finally narrowed this down. It's a use-after-free bug in Samsung's proprietary rild daemon. The OpenBSD malloc junk filling feature breaks it and it manages to not crash or print any error message. The Freeguard feature actually triggers a proper crash on the use-after-free. I'll include an ugly workaround for this in the next ROM (disabling junk filling for /system/bin/rild on the S4 - no impact to other devices or other processes on the S4).
|
Finally narrowed this down. It's a use-after-free bug in Samsung's proprietary rild daemon. The OpenBSD malloc junk filling feature breaks it and it manages to not crash or print any error message. The Freeguard feature actually triggers a proper crash on the use-after-free. I'll include an ugly workaround for this in the next ROM (disabling junk filling for /system/bin/rild on the S4 - no impact to other devices or other processes on the S4). |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Oct 19, 2015
Contributor
AFAICT this is fully worked around and will be included in the next ROM (doing a clean build right now).
|
AFAICT this is fully worked around and will be included in the next ROM (doing a clean build right now). |
thestinger
closed this
Oct 19, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
bitterman1970
commented
Oct 19, 2015
|
Will test this out asap and get back to you |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment|
The 20151019 build is now published with the fix for this. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
bitterman1970
Oct 19, 2015
Tried new build, no baseband now.......hang on ,restarted twice, baseband now detected....
bitterman1970
commented
Oct 19, 2015
|
Tried new build, no baseband now.......hang on ,restarted twice, baseband now detected.... |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
bitterman1970
commented
Oct 19, 2015
|
looking ok now |
bitterman1970 commentedOct 13, 2015
Have tried the last 2 builds, 1009 and 1013 and in both cases I'm getting a sim card not detected error. I've tried the latest Cyanogenmod nightly build with no issues with the sim card.