So, I figured I'd share since I couldn't find much information on the forums about this.
I recently, within last few weeks, started having issues with the modem on my GNex.
I had been running a ROM derived from AOSP Jelly Bean without issue, except the modem seemed to get poor signal quality.
I tried to upgrade the modem once the official Sprint JB release of FH05 started spreading.
At some point afterwards it seemed the modem would inexplicably start to die periodically... (By die I mean the status would change to searching and/or not connected and the status icon would change to no service icon). I could sometimes trigger life back in at times by toggling CDMA/LTE or CDMA Only options or the data enabled options or rebooting...
I went through a period of continually trying to reflash the various radios FD02, FC12, FH05... all in an attempt to get stability.
I had persistent issues even trying to flash the radios. The LTE radio would always flash fine, but the CDMA radio would often hang in flashboot forcing me to sever connection and restart.
This never seemed to fix the issue and I began to think I might either have bad flash memory on the radio partition or there was a problem with the radio hardware causing this issue.
I then remembered I had dropped the phone on concrete and it landed on the modem side of the phone... phone seemed fine besides a few new dings, but operated ok. I considered maybe this had something to do with the state of things.
Last night I took my phone back off using these instructions: http://www.ifixit.com/Teardown/Samsung-Galaxy-Nexus-Teardown/7182/1
I basically just jostled the internals a bit hoping to fix maybe a simple misalignment...
It has been a solid 12 hours and everything seems to be running strong.
This is purely speculation, but given that I haven't been able to consistently replicate any scenario other than it not working... I am hoping this is the fix.
I hope it might help someone else, or someone else with a similar problem can confirm or provide alternate conclusion.
I am currently running:
ROM:
http://forum.xda-developers.com/showthread.php?t=1801942
LTE and CDMA FH05:
http://forum.xda-developers.com/showthread.php?t=1620036#2
TWRP 2.2:
http://teamw.in/project/twrp2/92
shadowspires said:
So, I figured I'd share since I couldn't find much information on the forums about this.
I recently, within last few weeks, started having issues with the modem on my GNex.
I had been running a ROM derived from AOSP Jelly Bean without issue, except the modem seemed to get poor signal quality.
I tried to upgrade the modem once the official Sprint JB release of FH05 started spreading.
At some point afterwards it seemed the modem would inexplicably start to die periodically... (By die I mean the status would change to searching and/or not connected and the status icon would change to no service icon). I could sometimes trigger life back in at times by toggling CDMA/LTE or CDMA Only options or the data enabled options or rebooting...
I went through a period of continually trying to reflash the various radios FD02, FC12, FH05... all in an attempt to get stability.
I had persistent issues even trying to flash the radios. The LTE radio would always flash fine, but the CDMA radio would often hang in flashboot forcing me to sever connection and restart.
This never seemed to fix the issue and I began to think I might either have bad flash memory on the radio partition or there was a problem with the radio hardware causing this issue.
I then remembered I had dropped the phone on concrete and it landed on the modem side of the phone... phone seemed fine besides a few new dings, but operated ok. I considered maybe this had something to do with the state of things.
Last night I took my phone back off using these instructions: http://www.ifixit.com/Teardown/Samsung-Galaxy-Nexus-Teardown/7182/1
I basically just jostled the internals a bit hoping to fix maybe a simple misalignment...
It has been a solid 12 hours and everything seems to be running strong.
This is purely speculation, but given that I haven't been able to consistently replicate any scenario other than it not working... I am hoping this is the fix.
I hope it might help someone else, or someone else with a similar problem can confirm or provide alternate conclusion.
I am currently running:
ROM:
http://forum.xda-developers.com/showthread.php?t=1801942
LTE and CDMA FH05:
http://forum.xda-developers.com/showthread.php?t=1620036#2
TWRP 2.2:
http://teamw.in/project/twrp2/92
Click to expand...
Click to collapse
So you just took apart and reassembled and that got it working?
Maybe
xvanwilderx said:
So you just took apart and reassembled and that got it working?
Click to expand...
Click to collapse
Tried to sell phone on ebay because the wifi adapter was showing issues with range... I bought another and it was clear that the range of the older phone was having issues...
Tried to sell on ebay and buyer couldn't activate... just sent back and I can't get it to accept a flash at all... maybe trying the taking apart trick again...
Crazy
So this is my first flash to a different ROM on my GS3. I have been rooted for a while and decided I wanted to try a different rom on 4.2.2 coming from 4.1.2 with touchwiz. I am using the Dirty Unicorns 4.2.2 ROM and I noticed my signal reception is spotty at best. I am talking data and voice together. I flashed back to my 4.1.2 touchwiz stock rom and the reception went back to normal. I did some research on this issue and started looking into APNs. I noticed the file on the Dirty Unicorns rom is full of VZW, CREDO, Sprint... but the stock Sprint ROM only has Sprint stuff. The differences in the 2 files, only looking at the Sprint settings is slightly different still.
Is this my issue? If so should I use the stock APN file?
I am using the stock MD4 baseband and my PRL is 25015. Any thoughts or troubleshooting steps are appreciated.
I did some deeper research to find that the signal reception seems to be reporting incorrectly in the Dirty Unicorns ROM. I downloaded an app from the play store called network info II. This reported my cell reception to be the same it was on the stock MD4 touchwiz rom. I also think that the signal bar is reporting the faulty reception listed in the about section of settings. I made a few phone calls and ran Pandora on the cell network with no abnormal loss of quality.
Try a app in play store
Signal Check Lite
Gives a lot of info and signal strength for data too
I like that app better than the other one I was using... Thanks for the tip!
GSXeclipsePSI said:
Try a app in play store
Signal Check Lite
Gives a lot of info and signal strength for data too
Click to expand...
Click to collapse
Back to my issue, it looks as if the phone is reporting correct numbers in the signal information fields. What it looks like it is showing is the data connection it is using. I also, sometimes, find my phone on LTE even when I connected to wireless seems interesting. I am not sure however about the signal bars at the top of the phone. Rarely ever do I see them rise above 2 bars. Maybe somebody from an AOSP rom or CM rom could chime in with an answer.. even a DEV!!
FYI: Would have posted this in the development forum but I didn't have enough posts at the time. I am also sharing my info just in case it isn't around or it helps someone else.
[SOLVED] Same problems over here
edit 10/10/13 [SOLVED]: I found this thread about Team Sonic Modem Flasher Tool. There are five available radios in the super easy package. 1-4 came up with error messages, "No SIM card," or no signal with an Unknown Baseband in the phone settings. The fifth one, "LI3" radio solved my problems.
The Flasher Tool doesn't have a means of backing up your current radio. Seems like as soon as you start installing these other radios, your original one (mine was an MB1) was gone. BTW, my phone Baseband was a long string of letters and numbers. The type of radio that you've got is the last three characters.
I was also experiencing problems with other ROMs than the stock rom on my Sprint Galaxy S3. I was running Cyanogenmod 10 release candidate, and it seems to me that the signal was way worse than with the stock rom. I would also be in downtown Seattle, certainly with LTE service, and still I was stuck at 3G. 4G/LTE seems to be a thing of the past with the newer ROMs that I've been enjoying.
At the moment I'm back to a stock ROM, CleanBean v4.2 with Android 4.1.2. It seems to be happier. But I won't be back to an area with normal cell service for quite some time.
An interesting idea that the ROMs were reporting the incorrect signal strength. But reporting 3G vs 4G incorrectly too? That seems like something else was wrong.
I was thinking perhaps it was the radio or something, but CM doesn't really mention anything about flashing specific radios.
Are you judging from actual numbers or the signal bar? The latter is notoriously inaccurate many times (and can vary depending on what rom you're using
As for not jumping on 4g when I should have been, that was my oops. I had the settings in the phone to only do CDMA/3G rather than LTE/CDMA/3G. I would flash the radio to the newest version and leave it at that. I heard from someone else in another thread that the radios don't get changed.
dkerlee said:
I was also experiencing problems with other ROMs than the stock rom on my Sprint Galaxy S3. I was running Cyanogenmod 10 release candidate, and it seems to me that the signal was way worse than with the stock rom. I would also be in downtown Seattle, certainly with LTE service, and still I was stuck at 3G. 4G/LTE seems to be a thing of the past with the newer ROMs that I've been enjoying.
At the moment I'm back to a stock ROM, CleanBean v4.2 with Android 4.1.2. It seems to be happier. But I won't be back to an area with normal cell service for quite some time.
An interesting idea that the ROMs were reporting the incorrect signal strength. But reporting 3G vs 4G incorrectly too? That seems like something else was wrong.
I was thinking perhaps it was the radio or something, but CM doesn't really mention anything about flashing specific radios.
Click to expand...
Click to collapse
As for the feeling that the signal was reported incorrectly, I learned this. Dirty Unicorns, probably most other modded ROMs as well, are reporting the TRUE data signal strength in the signal bars. I downloaded Signal Check Lite. I compared the signal reported in the ROM to what this program says and they are identical. The bars are reporting the connected network types signal strength (ie. LTE,3G). It also says to be showing the RSSP which has been widely skeptical in most threads. If you're worried about your signal, check that program before switching away from a ROM or going back to stock. I actually kind of like them displaying the good info rather than just voice signal.
Does the kernel being used have any affect on signal reception? I'm just curious because I've switched between a few different 4.3 ROMs and the quality of signal is different between them.
When I was running Slim Bean 4.3, receiving a data signal at work wasnt a big issue. This morning I flashed Liquid Smooth 4.3 and even though the numbers being reported for signal strength are very similar, data on Liquid Smooth is almost unusable. Let me reiterate; Same phone (latest PRL), same location, same radio (MD4), same signal data numbers, using 2 different 4.3 ROMs and getting 2 extremely different usability results.
I'm not blaming either ROM, so I dont want to post in said threads, but is there a reason why this would be happening?
You are using data on the cell network and not the wifi network correct? There is a slight chance that it could but it would be mostly dependent on your modems I think. I am sure the modems and the kernel interact but that is about it. Testing for my issues, I am flashing the stock kernel back in, after doing a nandroid of course.
Disclaimer: I could be speaking rubbish. If I am please feel free to correct me, as I am still trying to learn.
uodii said:
Does the kernel being used have any affect on signal reception? I'm just curious because I've switched between a few different 4.3 ROMs and the quality of signal is different between them.
When I was running Slim Bean 4.3, receiving a data signal at work wasnt a big issue. This morning I flashed Liquid Smooth 4.3 and even though the numbers being reported for signal strength are very similar, data on Liquid Smooth is almost unusable. Let me reiterate; Same phone (latest PRL), same location, same radio (MD4), same signal data numbers, using 2 different 4.3 ROMs and getting 2 extremely different usability results.
I'm not blaming either ROM, so I dont want to post in said threads, but is there a reason why this would be happening?
Click to expand...
Click to collapse
Custom ROM and stock kernel don't seem to work, at least with me. Recovering from nandroid right now.
Skeeredfitless said:
Custom ROM and stock kernel don't seem to work, at least with me. Recovering from nandroid right now.
Click to expand...
Click to collapse
On custom ROMs you run, I think its best to run the kernel that the developer incorporated into the ROM for awhile. Then if you are sure your picking the correct kernel, you can try it out, but not before a nandroid of course. A touchwiz kernel is not going to function correctly on a AOSP ROM. Can cause alot of problems, TW & AOSP kernels are 2 totally different animals.
My battery life is sucking. I am trying to improve it so I thought I might try the stock one.
joeyhdownsouth said:
On custom ROMs you run, I think its best to run the kernel that the developer incorporated into the ROM for awhile. A touchwiz kernel is not going to function correctly on a AOSP ROM. Can cause alot of problems, TW & AOSP kernels are 2 totally different animals.
Click to expand...
Click to collapse
Skeeredfitless said:
My battery life is sucking. I am trying to improve it so I thought I might try the stock one.
Click to expand...
Click to collapse
Too many factors to list can cause this, try a different ROM with a clean wipe. Never use a TW kernel on a AOSP ROM.
When I'm running an AOSP Rom, my Wifi only scans for networks after a fresh boot. Once it has connected to a network, no more scanning happens, no matter how often I tell it to. It's quite an annoyance when I have to reboot my phone every time I leave home and want to connect to a coffeeshop Wifi outside.
Once it is connected, there are not further issues - signal is good, no random disconnects or anything. Just no scanning.
Everything works fine on stock, and I've successfully tried ViperX with Sense 5, but all AOSP Roms I've been trying recently had this behavior - I have no idea what's causing it. Maybe it's an issue with the CM kernel (most Roms use some form or other of it)?
I really have no idea. Thought I'll post a question here while I go do some more troubleshooting of my own.
I also just grabbed a snippet of what I hope is the relevant part of the logs: https://paste.xinu.at/WO9zZ/
On second thought, maybe it's not AOSP based, but rather 4.3. I haven't spent much time on 4.2 with this phone, so I don't remember if the problem existed back then. If I don't find a solution, I will downgrade later to make sure.
Solved Somewhat... Not really. Worked-around maybe.
I rolled back to CM 10.1.2, and the problem went away. Seems like it wasn't AOSP causing the problem, but the new always-on feature in 4.3, which allows scanning for networks even though Wifi is switched off. I've done some searching, and other people on all kinds of devices have had problems with Wifi since this change was implemented.
Once I disabled this feature and toggled Wifi off/on once, the problem seems to be gone on CM 10.2. Not quite a proper solution, but I guess I can live with that for now, I don't really have the time, energy or experience to look into this further. Maybe somebody more enlightened than I has a proper solution.
Noob post incoming. I did my best to search around and didn't find much. Hate creating a new thread but was locked out from posting in CM dev thread for obvious reasons. Not too experienced in the world of root, so forgive my ignorance. This will hopefully be a quick question:
I've tried running the CM nightlies for the last two days on my T-Mobile M8, and the only big problem is a complete lack of cell data. It displays that I have bars, and while it cuts in and out often (which I expect), I can't get a drop of data to go through. Even at full bars.
I've seen a few people mention connection issues, but didn't see anyone saying anything about a complete lack of cell data. I'd normally just chalk it up to being a nightly build issue, but since I can't find it mentioned elsewhere, I'm wondering if maybe I'm just doing something wrong. If not, no worries, but I'd be stoked if I can run it as a daily at the moment.
Anyone have any advice on what I might be doing wrong, or how I can resolve it?
Edit:
Chrome itself displays error that "Wi-Fi and mobile data are turned off" when only wifi is turned off.
I just tested calling and SMS and both are working with Wi-Fi off. So obviously I'm maintaining some type of radio connection.
Thanks a ton in advance!
New nightly. Same problems.
Bump.
@thefunkyprimer
I just got your PM. Unfortunately I know nothing about T-Mobile and/or why you would be having the issues. What have you tried? Switching APNs? Switching from 3G to 4G? I also haven't run CM longer than five minutes in a couple years. So I'm not much use in terms of running it personally.
Try my ROM and see if data works for you. That's pretty much all I got for you at the moment. But if you did try my ROM and data works, that might be a starting point. Make sure to fully wipe your device prior to flashing.
Hi!
I love the CM flavor but keep reverting to Sense-based due to nightly bugs. Thought I'd might throw one out here this time to see if anybody can assist me.
I'm on the latest AOKP right now and it's a blast. Great rom, but my wifi keeps dropping and disconnecting.
Is is possible to do something about this? Don't really know what debug info to provide. I'm at a level where I can master flashing new roms, but the inner workings by the likes of switching kernels is beyond me. I remember back in the day we used to flash radio roms on the Leo HD2 and it had sometimes a major impact on the performance of not only the gsm data and calls, but also the wifi drivers.
Thanks!
mine solution was to change the setting, keep wifi always on sleepmode, had the same problem.