• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help anyone else seeing the signal bars completely disappear?

Well, the bad news is it still happened again so the data roaming didn't fix it (I was surprised if it would, but it did go a while without doing it again).

I caught it on logcat. I think this is the start of the "crash" of the radio (for lack of a better word at the moment):

01-12 23:17:13.727 D/RIL[C] ( 114): OnFMTDataReceived STATE_CRASH_EXIT on Modem #1
01-12 23:17:14.070 D/RILJ ( 376): [0367]> SCREEN_STATE: false
01-12 23:17:14.070 D/RILJ ( 376): [0367]< SCREEN_STATE error: com.android.internal.telephony.CommandException: GENERIC_FAILURE
01-12 23:17:14.086 D/GSM ( 376): [GsmDCT] onReceive: action=android.intent.action.SCREEN_OFF
01-12 23:17:14.086 D/GSM ( 376): [GsmDCT] stopNetStatPoll
01-12 23:17:14.086 D/GSM ( 376): [GsmDCT] overall state is CONNECTED
01-12 23:17:14.086 D/GSM ( 376): [GsmDCT] startNetStatPoll
01-12 23:17:14.125 W/ActivityManager( 182): finishReceiver called but no pending broadcasts
01-12 23:17:14.211 E/NotificationService( 182): Ignoring notification with icon==0: Notification(contentView=null vibrate=null,sound=null,defaults=0x0,flags=0x62)
01-12 23:17:14.313 E/NotificationService( 182): Ignoring notification with icon==0: Notification(contentView=null vibrate=null,sound=null,defaults=0x0,flags=0x1)
01-12 23:17:14.727 D/RIL[C] ( 114): __silent_reset [***** SILENT RESET START *****]
01-12 23:17:14.727 D/RIL[C] ( 114): ReaderLoop Terminated!
01-12 23:17:14.727 D/RIL[C] ( 114): StopRXReader: trans_fd(19) closed
01-12 23:17:14.727 D/RIL[C] ( 114): StopRXReader: trans_fd(20) closed
01-12 23:17:14.727 D/RIL[C] ( 114): StopRXReader: rfs_fd(21) closed
01-12 23:17:14.727 D/RIL[C] ( 114): __silent_reset StopRXReader() OK!
01-12 23:17:14.727 D/RIL[C] ( 114): InformNewEvent g_bexit_thread has been signaled!
01-12 23:17:14.727 D/RIL[C] ( 114): WaitForEvent g_bexit_thread is 0
01-12 23:17:14.727 D/RIL[C] ( 114): RilProcessorLoop Finished!
01-12 23:17:14.727 D/RIL[C] ( 114): RilProcessorLoop Terminated!
01-12 23:17:14.727 D/RIL[C] ( 114): __silent_reset StopRilProcessor() OK!
01-12 23:17:14.727 D/RIL[C] ( 114): CancelAllRequests [EVT]:Req(0), RX(0)
01-12 23:17:14.727 D/RIL[C] ( 114): CancelAllRequests [EVT]:Req(0), RX(0)
01-12 23:17:14.727 D/RIL[C] ( 114): __silent_reset CancelAllRequests() OK!
01-12 23:17:14.727 D/RIL[C] ( 114): __silent_reset CancelAllReceived() OK!
01-12 23:17:14.727 D/RIL[C] ( 114): [dl_boot_lte] dl_boot_lte!
01-12 23:17:14.727 D/RIL[C] ( 114): [dl_boot_lte] OPEN USB_BOOT_DEV Succeeded!
01-12 23:17:14.727 D/RIL[C] ( 114): IOCTL_MODEM_RESET
01-12 23:17:15.195 E/NotificationService( 182): Ignoring notification with icon==0: Notification(contentView=null vibrate=null,sound=null,defaults=0x0,flags=0x1)
01-12 23:17:15.219 E/NotificationService( 182): Ignoring notification with icon==0: Notification(contentView=null vibrate=null,sound=null,defaults=0x0,flags=0x1)
01-12 23:17:15.227 E/NotificationService( 182): Ignoring notification with icon==0: Notification(contentView=null vibrate=null,sound=null,defaults=0x0,flags=0x1)
01-12 23:17:16.586 D/RIL[C] ( 114): set_sysfs(): set sysfs [/sys/bus/usb/devices/usb1/power/control] IN : on
01-12 23:17:16.649 E/NotificationService( 182): Ignoring notification with icon==0: Notification(contentView=null vibrate=null,sound=null,defaults=0x0,flags=0x1)
01-12 23:17:16.742 D/RIL[C] ( 114): set_sysfs(): set sysfs [/sys/bus/usb/devices/usb1/power/control] OUT : on
01-12 23:17:16.742 D/RIL[C] ( 114): Open LTE SPI: 17
01-12 23:17:16.742 D/RIL[C] ( 114): Open imgdev: 18
01-12 23:17:16.742 D/RIL[C] ( 114): Open imgdev: 18
01-12 23:17:16.742 D/RIL[C] ( 114): Load Boot.
01-12 23:17:16.742 D/RIL[C] ( 114): Actual Size of img Header is : 2428
I then looked at the dmesg and found roughly the same corresponding timestamp there, and bingo:

<3>[ 8936.320098] host wakeup timeout ! retry..
<3>[ 8936.819183] host wakeup timeout ! retry..
<3>[ 8937.320098] host wakeup timeout ! retry..
<3>[ 8937.820068] host wakeup timeout !!
<3>[ 8937.820281] usb_tx_work usb_tx_urb_with_skb for iod(0), ret(-1)
<6>[ 8937.929779] usb 1-1: USB disconnect, device number 4
<6>[ 8937.930358] force disconnect by modem not responding!!
<6>[ 8938.054260] usb 1-1: new high speed USB device number 5 using ehci-omap
<3>[ 8952.945037] USB disconnected and not enumerated for long time
<6>[ 8952.945343] [MODEM_IF] lte_ipc0 state changed: CRASH_EXIT
<3>[ 8953.179412] usb 1-1: device descriptor read/64, error -110
<3>[ 8955.950439] [MODEM_IF] no data from sk_rx_q, modem_state : CRASH_EXIT(lte_rfs0)
<6>[ 8955.950531] [MODEM_IF] cbp71_off()
<6>[ 8955.950561] [MODEM_IF] cdma_ipc0 state changed: OFFLINE
<6>[ 8955.951171] [MODEM_IF] misc_release : cdma_ipc0
<6>[ 8955.951751] [MODEM_IF] misc_release : lte_ipc0
<6>[ 8955.952209] [MODEM_IF] misc_release : lte_rfs0
<6>[ 8955.968536] [MODEM_IF] misc_open : lte_boot0
<6>[ 8955.970245] [MODEM_IF] cmc221_reset()
<6>[ 8955.970336] [MODEM_IF] cmc221_off()
<6>[ 8955.987457] [MODEM_IF] cdma_ipc0 state changed: OFFLINE
<6>[ 8955.987670] phone_active_irq_handler : phone_state=0
<6>[ 8956.015960] [MODEM_IF] cdma_ipc0 state changed: OFFLINE
<6>[ 8956.016143] phone_active_irq_handler : phone_state=0
<3>[ 8956.147338] hub 1-0:1.0: unable to enumerate USB device on port 1
<3>[ 8956.233306] [MODEM_IF], phone_status changed to invalid!!
<6>[ 8956.295715] [MODEM_IF] cmc221_on()
<6>[ 8957.828033] [MODEM_IF] misc_release : lte_boot0
<6>[ 8957.988403] [MODEM_IF] misc_open : lte_boot0
<6>[ 8957.990173] lte_modem_spi spi4.0: IOCTL_LTE_MODEM_XMIT_BOOT - bin size: 2428
<6>[ 8958.109130] usb 1-1: new high speed USB device number 6 using ehci-omap
<6>[ 8958.120574] lte_modem_spi spi4.0: IOCTL_LTE_MODEM_XMIT_BOOT - bin size: 64288
<3>[ 8958.186340] hub 1-0:1.0: unable to enumerate USB device on port 1
<3>[ 8958.667572] lte_modem_spi spi4.0: spi_xmit - error -22
It looks to me like some sort of hardware/watchdog timeout on the LTE radio device. I.e., I think it's a hardware problem. Or could a bad SIM card theoretically trigger something like this? I would have expected some sort of Icc or SIM message from the kernel (in dmesg) if that were the case, though.

This has pretty much convinced me it's an LTE radio hardware problem, but I am going to let my logcat run over night and see if I catch any more of these. If I do, I'll try CDMA only to see if it's just the LTE radio or some sort of handoff thing.
 
This has pretty much convinced me it's an LTE radio hardware problem, but I am going to let my logcat run over night and see if I catch any more of these. If I do, I'll try CDMA only to see if it's just the LTE radio or some sort of handoff thing.

I dont think its LTE. My tmo gsm does almost the same thing. It will have 5 blue bars until i answer a call then 0 blue bars until the call is over. Then 5 blue bars again as soon as I hang up. Sometimes the calls drop or are interrupted. This doesn't happen all the time and it seems to be location specific. However I do start out with a full 5 blue bars in the places where it seems to occur.

I have watched the signal strength as the bars change from blue to grey and it doesn't seem affected interestingly enough. Its around -87. That's why I asked for help understanding solid grey triangle, grey bars, and blue bars on this phone. The problem seems more related to the bar color than the actual signal strength.
 
Mine almost seem like the phone has to wake up. I hit the screen first thing this morning, after it being off all night and its like your computer when its in sleep ot hibernate mode, it refreshed and I had 3g with grey bars and then they turned blue. Took like 15-120 seconds. Happens all during the day. I'm going to change it so the screen stays on all day and leav it hooked up to the charger if need to see what happens. I'm also going to call verizion and have a complaint put in my file.

rock on
billd
 
I dont think its LTE. My tmo gsm does almost the same thing. It will have 5 blue bars until i answer a call then 0 blue bars until the call is over. Then 5 blue bars again as soon as I hang up. Sometimes the calls drop or are interrupted. This doesn't happen all the time and it seems to be location specific. However I do start out with a full 5 blue bars in the places where it seems to occur.

I have watched the signal strength as the bars change from blue to grey and it doesn't seem affected interestingly enough. Its around -87. That's why I asked for help understanding solid grey triangle, grey bars, and blue bars on this phone. The problem seems more related to the bar color than the actual signal strength.

No what I am seeing is totally different. I won't be using voice at all and the data will just bye bye. In fact, when this happens I love voice, too. It's like all the radios just go away.

And I'm not even taking about signal strength. I'm talking real world performance. I have no data connection (things fail and say to check my internet connection, etc).
 
So is everyone's plan just to hang on and see what happens? I'm hoping an OTA will solve this but its nearing the 15th..

don't really want to get a rezound or razr.. Maybe I'll just go back to the old phone and re-purchase this when they solve the issue.
 
So is everyone's plan just to hang on and see what happens? I'm hoping an OTA will solve this but its nearing the 15th..

don't really want to get a rezound or razr.. Maybe I'll just go back to the old phone and re-purchase this when they solve the issue.

It's not clear to me that this is even happening to that many people. I know we do not represent a proper sample of all the people with this phone by any means, but I would think there would be more reports of this problem if it were happening to all Nexuses.

So I saw a couple of posts about sim card swapping fixing it. Can those who swapping the sim chime in whether it fixed it for you?

The Rezound one day was dropping to 1x off and on, but would stay on 1x for a while. I think it was network issues, but maybe it's the same problem but with different symptoms? I'm going to keep an eye on it this morning and go to the VZW store at lunch if it keeps dropping.

Luckily since I'm rooted I can keep an eye on the radio logs (adb logcat -v time -b radio) and know exactly when it happens. Though I can't easily distinguish a "normal" loss of signal (e.g. going into a bad part of the building) and the radio turning off issue that I'm seeing.
 
It's not clear to me that this is even happening to that many people. I know we do not represent a proper sample of all the people with this phone by any means, but I would think there would be more reports of this problem if it were happening to all Nexuses.

So I saw a couple of posts about sim card swapping fixing it. Can those who swapping the sim chime in whether it fixed it for you?

The Rezound one day was dropping to 1x off and on, but would stay on 1x for a while. I think it was network issues, but maybe it's the same problem but with different symptoms? I'm going to keep an eye on it this morning and go to the VZW store at lunch if it keeps dropping.

Luckily since I'm rooted I can keep an eye on the radio logs (adb logcat -v time -b radio) and know exactly when it happens. Though I can't easily distinguish a "normal" loss of signal (e.g. going into a bad part of the building) and the radio turning off issue that I'm seeing.

I had my SIM Card swapped 2 days ago and it almost seems worse! Today has been terrible. It seems like every time i look at my phone it has no connection, voice or data. I have been leaving it on 4G just to test it out. ******* I have noticed that ANYTIME it has no connection if i restart the phone it always gets a connection immediately. So to me that sounds like a software issue (hopefully!)
 
I had my SIM Card swapped 2 days ago and it almost seems worse! Today has been terrible. It seems like every time i look at my phone it has no connection, voice or data. I have been leaving it on 4G just to test it out. ******* I have noticed that ANYTIME it has no connection if i restart the phone it always gets a connection immediately. So to me that sounds like a software issue (hopefully!)

For me, I don't even have to restart the phone. It comes back to 4G within a minute, probably more like 30 seconds. If you watch it when it dies, how fast does yours come back? Mine seems to recover quickly (and the logs show the kernel is basically resetting the device), like it was powered off then back on - or mimics that behavior.

I've only had 2 drops this morning, both times I knew it was going to happen (elevator at work). I'm going to go for a test drive to a nearby VZW and see if it happens along the way. The route I'm taking has good 4G coverage and no nearby extended 4G coverage. So in theory, it should be a solid signal from here to there. If it drops more than once, I'll ask them to swap the SIM card at the store (which they will hopefully do), and see if the return trip improves.
 
I have a GNex on Tmo and I was experiencing the dropped signal, etc. I got upgraded to 4.0.2 OTA and it hasn't been happening for two days now. The radio is now XXKK6. Maybe that fixed it. Are all of you on 4.0.1?
 
I have a GNex on Tmo and I was experiencing the dropped signal, etc. I got upgraded to 4.0.2 OTA and it hasn't been happening for two days now. The radio is now XXKK6. Maybe that fixed it. Are all of you on 4.0.1?

I'm on the CDMA/LTE Nexus, it came with the 4.0.2 radio.

So you were having the same problem on the GSM Nexus? Did yours go from full or mostly full blue bars to a solid gray triangle? If it was happening on the GSM version and was fixed in the GSM 4.0.2 update, that gives me some hope for 4.0.3 on the CDMA version. But the VZW stores are telling me "all 4G phones do this". :confused: :eek:
 
I have a GNex on Tmo and I was experiencing the dropped signal, etc. I got upgraded to 4.0.2 OTA and it hasn't been happening for two days now. The radio is now XXKK6. Maybe that fixed it. Are all of you on 4.0.1?

No. Most of us on Verizon are on 4.0.2. New batches being sold now seem to be already flashed with 4.0.2. Glad that your GSM one is improved with update.
 
I called VZW tech support this morning and told her of my concern about the problem, My concern is that if it happens 5minutes after I go to sleep, and comes back after I wake up, have I lost phone service for 5 to six hours? Initially when talking to tech the girl kept saying she hasn't heard of any problems and I could tell from the conversation, that she probably new less about the phone than I did, so I asked for level two and was transferred. Level two took my info and put it in my record. I'm concerned that my 14 days is up in 3 more days and I wanted it documented. She suggested I leave it on 3g (cdma) which I told her i normally do because 4g tears up the battery and it was on 3g with no charger last nigh and did it again. I'm going to try 4g tonight. She mentioned, that keeping the phone hooked up to a charge is not good for the phone and even though she admitted it didn't have anything to do with the signal dropping.
I don't think she has an immediate answer. She said she will call me Monday @ 0800 to see if it is still doing it. I asked her about the sim card and she said if I want to swap cards she will send me one or I can go to a VZW store and get one. That's in my record. I'll hold off until I hear more.
I told her that its not a signal strength issue, that when I have blue bars, meaning I have a connection, there all full, and that's just about everywhere in Pensacola including my house.

I'm still leaning toward the phone sleeping and has to be woke up. I've never had it happen while I'm using the phone or data. Never had a call dropped since I got the phnes a week and a half ago. I'm on the 4.0.2 update. I told her my sig data of 75dbm and thats good. She offed on Monday to call Samsung and let me talk to them while she listens. She had nothing but praise for them and I probably will do that, first cause it free and second they may have an answer.
I would suggest that if you are having this problem, dial 611 and talk to tech support and have the issue logged. If you don't call they wont know there's a problem. So far they sold what, a million phones and 10 or so of us on here are having and talking about it. I think other people probably may not know its happening to them.
lol, while I was typing this i turned my phone on and had grey bars!! took 10 seconds for the 3g thingy to pop up and 5 seconds for all the bars to turn blue. my signal strength is 75 still.
I wish there was a way to plug the phone into the computer and get readings of what happening while the screen is off........
call them if your having a prob!!

dinner time!!
Billd
 
Yeah I was experiencing exactly what you guys were. Blue bars with HSPA then everything greys out, even voice. Sometimes it comes back on but sometimes it requires a reboot.

Maybe 4.0.3 will have some firmware fix for you guys. I heard there's a 4.1 down the pipe too. My gps doesnt lock as well as my nexus one did but that's a new thread.
 
Yeah I was experiencing exactly what you guys were. Blue bars with HSPA then everything greys out, even voice. Sometimes it comes back on but sometimes it requires a reboot.

Maybe 4.0.3 will have some firmware fix for you guys. I heard there's a 4.1 down the pipe too. My gps doesnt lock as well as my nexus one did but that's a new thread.

Thanks! This indeed encouraging that a similar problem on gsp/hspa+ was fixes in your update! That gives me hope! :)
 
As everyone else complains about the signal bars showing less bars, the real problem seems to be the GNex not staying connected to 3G/4G and not switching between the 3G and 4G and vice versa quickly. When I'm on 4G, even with 1 bar, I get 20+ MB down. However, if I lose 4G the device will take about 1 minute or more to connect to 3G. I would think the device would lose 4G and connect to 3G instantaneously. Instead the device seems to drop ALL data and reconnect to whatever is available.
Doing more research, it looks like 4.0.3 will be coming out with new radio code to help this problem out. Also, I read somewhere 4.0.3 will be out in late Jan 2012.
 
It was happening to me 3+ times per day. I couldn't make calls, send texts or browse. Phone was useless. Sometimes took 10 min to fix even with airplane mode reset. I couldn't take it anymore. Said no network or sim card installed. I exchanged it yesterday and got a new phone and new sim card. So far so good. Will keep you updated.
 
4 bars -61dbm right now. Also be sure the Mobile Network is enabled. I have a widget on the desktop and sometimes I accidentally touch it to off - touch it again and it's back to normal...

This is not just someone accidentally turning off mobile data. If it's the same thing I'm seeing, data and voice drop when this happens, not just data. That could explain some people's issues (or an app like juice defender misbehaving) but not all.
 
I have the same issue of dropping signal but more than anything I see my bars go grey and lose connection even though i have like 2-3 bars 4g
 
Still the same problem, I posted in another thread like this when the phone first released and nothing really changed. Currently I only have 2 bars of 3G services, and it seems to always go out when it does the hand-off between 3G and 4G and it's extremely slow.

Stuff like this questions my allegiance to android and makes me want to test drive some iTrash just based solely on the fact that it just works.
 
Still the same problem, I posted in another thread like this when the phone first released and nothing really changed. Currently I only have 2 bars of 3G services, and it seems to always go out when it does the hand-off between 3G and 4G and it's extremely slow.

Stuff like this questions my allegiance to android and makes me want to test drive some iTrash just based solely on the fact that it just works.

I don't get this sort of argument. The iPhone is not 4G. So what it comes down to is - would you rather have an iPhone or a Nexus where you set it to CDMA only? Or are you just contemplating ditching the Nexus for the iPhone just to prove a point?

It would be a cold day in hell when I switched from an open/robust/tweakable/etc OS like android on a phone with a screen 1" or more bigger to a closed/dictatorial/uncustomizable iPhone with a smaller screen. But hey, that's just me... :cool:
 
Back
Top Bottom