Hi everyone.
I've just taken the plunge into the ROM flashing world, all thanks to the fantastic efforts of the community!
I have flashed my Desire with Oxygen (both RC6 & RC7) and it appears that my wifi has become inoperable. The details of my configuration are:
Radio: 32.54.00.32U_5.14.05.17 (have also tried 32.44.00.32U_5.09.05.30_2 and 32.48.00.32U_5.11.05.14)
Stock kernel
AlphaRev S-OFF + Oxygen HBOOT 0.93.1000
ClockworkMod-AlphaRev 2.5.1.8
I've had no problems getting all these bits sorted out, but this specific wifi issue appears to be unusual (I think).
I'm aware of the upstream signal strength issue, however the characteristics of this problem are quite different.
In essence, I'm unable to use wifi at all - when I turn it on I'll either see some or none of the networks I expect, then after a short interval (typically a couple of seconds) the list is empty.
On rare occasions I've been able to put in my network key (WPA2 in this case) and I will get an IP, but shortly afterwards the connection drops and all the networks disappear again. It's the same for open networks.
I've tried re-flashing all of the above radio versions, as well as setting the sleep policy to never and the regulatory domain to any value. The 3G data works fine, and I don't have any cellular signal issues. I've also flashed the Oxygen 1.04 Froyo ROM and everything worked perfectly. Any ROM flashing has been done after a full wipe.
I've looked through many posts about wifi issues but have not managed to find much in the way of resolve. There's been a lot of talk about re-flashing the radio/ROM and ensuring a full wipe, but I've had no luck doing that. People have also mentioned trying different kernels, but I've not yet tried that out - I would think that if the stock one works for others it should work for me.
Does anyone have any ideas? Any help would be greatly appreciated.
have you tried 32.43.0032u_5.09.00.20 i too am new to this, and this one worked for me.
Thanks for the advice - I just flashed with that radio, but unfortunately it didn't work.
don't want to sound like i'm teaching u to suck eggs but have you gone into network settings and entered it manually. sorry if this sounds insulting
stacker541 said:
don't want to sound like i'm teaching u to suck eggs but have you gone into network settings and entered it manually. sorry if this sounds insulting
Click to expand...
Click to collapse
Although I had tried that before, I just did it again and realised something potentially useful gets output to the log:
Code:
I/GPSButton( 202): Update State
D/Tethering( 128): eth0 is not a tetherable iface, ignoring
I/GPSButton( 202): Update State
V/WifiStateTracker( 128): Connection to supplicant established, state=DISCONNECTED
I/wpa_supplicant( 1680): CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00
V/WifiMonitor( 128): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
V/WifiStateTracker( 128): Changing supplicant state: DISCONNECTED ==> SCANNING
E/wpa_supplicant( 1680): Ongoing Scan action...
E/wpa_supplicant( 1680): Ongoing Scan action...
D/dalvikvm( 1465): GC_EXPLICIT freed 12K, 50% free 3461K/6791K, external 1625K/2137K, paused 65ms
E/wpa_supplicant( 1680): ioctl[SIOCGIWSCAN]: 22
[COLOR="Red"]I/wpa_supplicant( 1680): CTRL-EVENT-DRIVER-STATE HANGED
V/WifiMonitor( 128): Event [CTRL-EVENT-DRIVER-STATE HANGED]
E/WifiStateTracker( 128): Wifi Driver reports HUNG - reloading.[/COLOR]
I/wpa_supplicant( 1680): CTRL-EVENT-TERMINATING - signal 15 received
V/WifiMonitor( 128): Event [CTRL-EVENT-TERMINATING - signal 15 received]
I/wpa_supplicant( 1680): CTRL-EVENT-TERMINATING - signal 0 received
I/wpa_supplicant( 1680): CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00:00:00
I/GPSButton( 202): Update State
E/wpa_supplicant( 1680): Failed to disable WPA in the driver.
D/WifiStateTracker( 128): Reset connections and stopping DHCP
V/WifiStateTracker( 128): Supplicant died unexpectedly
E/WifiService( 128): Failed to stop supplicant daemon.
D/WifiStateTracker( 128): Reset connections and stopping DHCP
I/GPSButton( 202): Update State
D/WifiStateTracker( 128): Disabling interface
D/WifiStateTracker( 128): Disabling interface
So the driver is clearly completely failing - unfortunately there's nothing else in any of the logs that hints at a root cause.
Hi,
I don't have a solution for you, but I just wanted to tell you that you are not alone.
I have experienced the same problem. For me it is actually more random and I can't reproduce it at all.
Sometimes it would be exactly the problem as you describe it. Sometimes it would connect to wifi and everything works. Sometimes it would connect and wifi to wan works but it wouldn't connect to intranet devices (meaning connecting to my NAS gives me "no route to host" errors, but connecting to the e.g. market through wifi works).
And sometimes everything just works. Even without a reboot. Just trying a few minutes later.
I have experienced this with Oxygen, CM7 and basically any Gingerbread ROM on my Desire.
Mobile data works flawlessly.
Just my 2 cents.
xelra said:
Hi,
I don't have a solution for you, but I just wanted to tell you that you are not alone.
I have experienced the same problem. For me it is actually more random and I can't reproduce it at all.
Sometimes it would be exactly the problem as you describe it. Sometimes it would connect to wifi and everything works. Sometimes it would connect and wifi to wan works but it wouldn't connect to intranet devices (meaning connecting to my NAS gives me "no route to host" errors, but connecting to the e.g. market through wifi works).
And sometimes everything just works. Even without a reboot. Just trying a few minutes later.
I have experienced this with Oxygen, CM7 and basically any Gingerbread ROM on my Desire.
Mobile data works flawlessly.
Just my 2 cents.
Click to expand...
Click to collapse
Thanks for your input - it's good to know that I'm not alone!
My concern is that if our problems aren't a very common experience and if it isn't naturally resolved by the Nexus One OTA, it might never get fixed! Fingers crossed...
I'd just like to bump this up, as the problem still exists in the final oxygen release.
I've also tried out the DevNull ROM, but still no luck.
Also, the logs aren't showing any issues with the wifi - it's just keeps scanning and finds nothing.
sebrichards said:
I'd just like to bump this up, as the problem still exists in the final oxygen release.
I've also tried out the DevNull ROM, but still no luck.
Also, the logs aren't showing any issues with the wifi - it's just keeps scanning and finds nothing.
Click to expand...
Click to collapse
I have a similar problem with the DevNull Rom as well.
I cannot connect to the internet through my carrier.
There is no data icon on the phone when I enable it.
Wifi is working just fine, actually.
I guess the Rom has an issue with internet connectivity!!
I'm Having the exact same issues also. So do a number of my friends. I'm new to rooting world, so I don't have a solution. Are you from Canada? All the people I know that's having this issue are from Canada. Can that be the reason?
Sent from my HTC Desire using Tapatalk
gordongartrell said:
I'm Having the exact same issues also. So do a number of my friends. I'm new to rooting world, so I don't have a solution. Are you from Canada? All the people I know that's having this issue are from Canada. Can that be the reason?
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
I restarted the phone just now and everything seems to be working.
Yes, I do live in Canada but I don't think this has anything to do with it.
Restart your phone and good luck
EraqEE said:
I restarted the phone just now and everything seems to be working.
Yes, I do live in Canada but I don't think this has anything to do with it.
Restart your phone and good luck
Click to expand...
Click to collapse
Yeah, I tried rebooting and it will work for about 5 minutes, then the connection drops. It only works when I'm very close to my router. Even if I'm 10-20ft away from my router, the connection drops.
Sent from my HTC Desire using Tapatalk
I'm pretty new to this as well, in fact, I only started flashing roms yesterday!
Reinstalling the Rom might fix this.
EraqEE said:
I'm pretty new to this as well, in fact, I only started flashing roms yesterday!
Reinstalling the Rom might fix this.
Click to expand...
Click to collapse
Yea, I tried everything. No luck. I'm going to go back to one of the sense roms for the time. I have no issues with them besides the lack of smoothness compared to stock android os devices. Thanks though.
Sent from my HTC Desire using Tapatalk
Wifi Issue, try out : "In wifi settings, advanced, set regulatory domain to 14 channels. I suspect what happens is that it cures the problem for those of us with channel = auto on the accesspoint."
3G Issue : Configurate manually your access points depending on your provider, it worked for a friend.
Good Luck!
Yeh sadly I've already tried all options on the regulatory domain setting - doesn't appear to have an effect. Also, I know there are several networks visible on my computers on channels < 11.
Related
We have a repeatable GPRS Connection issue on the XDA. I would be interested to know is any person can suggest a solution, and whether any body else has found the same problem.
Whilst connecting on the move, between radio masts, the GPRS sometimes becomes stale.
The connection will timeout after some long period, or when the calling application kills the attempt. After this, every other attempt to connect will have the same result. After a hard-reset, the device will connect in a few seconds without issue as expected.
The odd part, is by examining a 'feature' of the signal stength meter (which always return 69% when connected to GPRS) it appears that the connection has been made in all cases, but the RAS server seems to think the connection is still being made. -- It seems obvious that some part of the RAS with GRPS has become stuck in some stale state to which only a reboot will fix it.
A single timeout can of course be countered by another attempt to connect. But when every subsequest attempt leads to failure, some other solution is needed.
If anybody can suggest a solution to this, I would be extreamly interested.
Thanks, Ben Clewett.
A friend of mine recently purchased a Xperia Arc, but is having serious problems with the WiFi connection. In some networks have no problem in connecting, especially in connection with no WEP or WPA protection. But in other WIFI networks, such as home, insert the password, and indicates that you are connecting to wifi, but then disconnects and sometimes tries to connect but never succeeds. The impression I get is that while you are connecting, the wifi search process refreshes too fast and lose the connection.
Android he has tested with 2.3.2 and 2.3.3 and the problem persists.
Anyone else will happen?
A greeting.
I got an x8 and the problems is the same with update to 2.1 thats why i use now this hd2 (rullz:d)
Sent from my HTC HD2 using XDA Premium App
aliniulian23 said:
I got an x8 and the problems is the same with update to 2.1 thats why i use now this hd2 (rullz:d)
Sent from my HTC HD2 using XDA Premium App
Click to expand...
Click to collapse
Anyone else?
Hey friends......try setting your wifi router's channel to a fixed value...not automatic.....channel 5 works for me...
Sent from my LT15i using XDA App
Using Apps like "KeepWiFi" has improved on my Neo up to few hours' connection even on locked screen.
WiFi Problems
I've been having WiFi issues @ home too. Mine will connect for about 5 minutes, then it will disconnect, and won't reconnect until I reboot the router.
What I've done is change the encryption from WEP to WPA. Also I've tried changing the channel setting in the Wireless setup. I've tried 5, 6 and 10 so far.
It's improved the WiFi somewhat (can go 20-45 minutes) but the problem still persists. I'm going to keep trying different channels, not much else I can do. Any suggestions would be appreciated.
Edit: I've just come across this, @work right now so I've not tried: This was happening to me too, thats because arc doesnt work with mixed g/n wireless mode (at least, on the 2 routers i've tried this on). You need to set your router to either use just N, or just G, then it works fine.
I got wifi issues. It randomly disconnects when used,like downloading from marked if the files are like 2mb+. It continues to download after a short break but still very annoying. Was hoping the 145 update would fix it but it didn't so i'm sending mine to service tomorrow.
And don't suggest different router settings or another router. Tried it all. Besides when u buy a phone like this u expect it to work on WEP,WPA,WPA2 etc.
Seems like only a few got this problem so hoping for a nice working device or a new device when i get the phone back.
My guessing it is a hardware problem
I take mine to the service and asked them to replace it, and they come up with a lame excuse, that i wait for the 2.3.4 update and it will fix this !!
It is NOT the router fault at all. You can check this link for the problem in SE support forum
http://talk.sonyericsson.com/message/71859
guys, i do faced the same problem...
i tried different wireless speed(b/g/n) or the different channel... none fix the problems
But the moment i do not use DHCP and give a fix ip to my ARC, the speed is restored, the connection did not drop and love every moment of it... give it a try.... give me a thanks if it help!
Hi guys!
I'm sorry to hear that you are still experiencing problems with Wi-Fi even if some of you have updated to Android 2.3.3 which contains improvements for Wi-Fi.
So first of all I would like to say that all of you that haven't updated to Android 2.3.3 update, do so. As you may know the launch of the update differs from market to market and is also depending on operator customization.
If you still experience problems running on Android 2.3.3 you should check if the problem remains if you connect to another router (just to be sure that this is not caused by some setting in your router)
And if problems would still remain using another router I would suggest that you leave the phone to your retailer so a service technician can examine the phone at a repair center.
BR
Johan
Sony Ericsson
Nice to see SE active tho, thumbs up.
I delivered my Arc yesterday to fix this wifi issue. Kinda has to be a hardware issue,same problem on 3 different routers.
So i hope i get a fixed or new Arc back else it's byebye Arc (and probably SE for a while as i'll buy another phone, so please fix it! Arc is such a sexeh phone and deserves to be loved and stroked on!)
My phone (XPERIA NEO) worked perfectly with 3.3.2. However since the latest 3.3.3 the wifi constantly dies when downloading large files or viewing youtube clips. I can tell you that it is not in any way related to the access points, I have reproduced this with several manufactures of wifi AP/routers.
This is a driver bug, at least the kernel logs says so.
06-05 22:03:45.001 W/KeyCharacterMap(357)Error loading keycharmap file '/system/usr/keychars/pm8058-keypad.kcm.bin'. hw.keyboards.0.devname='pm8058-keypad'
06-05 22:03:45.001 W/KeyCharacterMap(357)Using default keymap: /system/usr/keychars/qwerty.kcm.bin
06-05 22:03:46.801 W/kernel (118)[ 1137.806732] ------------[ cut here ]------------
06-05 22:03:46.801 W/kernel (118)[ 1137.806976] WARNING: at /home/hudsonslave/root/workspace/offbuild_edream3-release_matrix/HUDSON_PRODUCT/hallon/HUDSON_VARIANT/user/label/CM/out/target/product/hallon/obj/WILINK_OBJ/platforms/os/linux/build/../../../../platforms/os/linux/src/osapi.c:761 os_SignalObjectWait+0x40/0x54 [tiwlan_drv]()
06-05 22:03:46.801 W/kernel (118)[ 1137.807006] os_SignalObjectWait
06-05 22:03:46.801 W/kernel (118)[ 1137.807006] Modules linked in: tiwlan_drv sdio
06-05 22:03:46.801 W/kernel (118)[ 1137.807037] [<8003b4f8>] (unwind_backtrace+0x0/0x150) from [<800d61cc>] (warn_slowpath_common+0x48/0x60)
06-05 22:03:46.801 W/kernel (118)[ 1137.807067] [<800d61cc>] (warn_slowpath_common+0x48/0x60) from [<800d621c>] (warn_slowpath_fmt+0x24/0x30)
06-05 22:03:46.801 W/kernel (118)[ 1137.807189] [<800d621c>] (warn_slowpath_fmt+0x24/0x30) from [<7f00bb28>] (os_SignalObjectWait+0x40/0x54 [tiwlan_drv])
06-05 22:03:46.801 W/kernel (118)[ 1137.807464] [<7f00bb28>] (os_SignalObjectWait+0x40/0x54 [tiwlan_drv]) from [<7f012780>] (cmdHndlr_InsertCommand+0x130/0x1a8 [tiwlan_drv])
06-05 22:03:46.801 W/kernel (118)[ 1137.807708] [<7f012780>] (cmdHndlr_InsertCommand+0x130/0x1a8 [tiwlan_drv]) from [<7f00cc94>] (wlanDrvWext_Handler+0x1d8/0x380 [tiwlan_drv])
06-05 22:03:46.801 W/kernel (118)[ 1137.808898] [<7f00cc94>] (wlanDrvWext_Handler+0x1d8/0x380 [tiwlan_drv]) from [<804f36a8>] (ioctl_standard_call+0x64/0x3c0)
06-05 22:03:46.801 W/kernel (118)[ 1137.808898] [<804f36a8>] (ioctl_standard_call+0x64/0x3c0) from [<804f3ab4>] (wext_handle_ioctl+0xb0/0x1f4)
06-05 22:03:46.801 W/kernel (118)[ 1137.808929] [<804f3ab4>] (wext_handle_ioctl+0xb0/0x1f4) from [<803d9968>] (dev_ioctl+0x750/0x780)
06-05 22:03:46.801 W/kernel (118)[ 1137.808959] [<803d9968>] (dev_ioctl+0x750/0x780) from [<8015ca64>] (vfs_ioctl+0x2c/0x8c)
06-05 22:03:46.801 W/kernel (118)[ 1137.808990] [<8015ca64>] (vfs_ioctl+0x2c/0x8c) from [<8015d110>] (do_vfs_ioctl+0x558/0x5c4)
06-05 22:03:46.801 W/kernel (118)[ 1137.808990] [<8015d110>] (do_vfs_ioctl+0x558/0x5c4) from [<8015d1b0>] (sys_ioctl+0x34/0x54)
06-05 22:03:46.801 W/kernel (118)[ 1137.809020] [<8015d1b0>] (sys_ioctl+0x34/0x54) from [<80034f80>] (ret_fast_syscall+0x0/0x2c)
06-05 22:03:46.801 W/kernel (118)[ 1137.809051] ---[ end trace da227214a82491bf ]---
I reported this error to SEMC, but I still have not received any feedback - apart from the ticket number
Problem here too, must be 5 or 6 different threads on this forum pertaining to the same issue...affects neo, play, and arc users alike.
Any changes? Any news? This problem is very bad for me... i'am waiting for issue from SE... What are you doing with this problem, guys? Just waiting?
Hopefully this is the right place to ask this.
First, the problem I'm having with my LTE Nexus is that I will have a great signal (4 4G blue bars) and then data just stops working. Shortly after, the 4G symbol and the bars disappear entirely and I'm left with a solid gray triangle (no data connection).
I have the logcat output but don't know how to find the entries that correlate to this data drop. I'm hoping someone in here will be able to help go through the logcat. Unfortunately, with the logcat I captured, I forgot to use -v time so I couldn't correlate to the screenshot I took (to remember the time of the drop). I'll try to do that. But if someone can look over the logcat I do have, I'd appreciate it. Attached is the logcat. I had at least 4-5 of these data drops which should be reflected in the log somewhere...
More details about the problem here:
- this happened for me while driving but ALSO when I was just walking to my car, so initially I thought it might be when it tower hops, but I don't think so
- When this happens, often I have four full bars of 4G. I'll try to browse or go to the market, etc and I'll get the "no connection" error. But it doesn't seem to be signal level related or I would expect it to happen only when I had like 1 bar. Then again, if the bars don't update that often, I suppose it's possible I'm dropping from 4 bars to 0 really fast for some reason.
- Shortly after that, the 4G symbol and bars disappear and I am left with a solid gray triangle. No data connection works while this triangle is there
- About 30 seconds to a minute later, I'll get the gray bars, then shortly thereafter 4G and then blue 4G+bars.
- Every time this has happened I have been in a seemingly good 4G area. It never even tries to go to 3G. It just goes 4G -> drop/nada -> 4G. But it does do it frequently.
Ok, I collected a logcat after this data drop had occurred twice. I think I may have only caught one occurrence of it, but this message in particular looks suspicious:
01-12 12:11:09.375 D/GSM ( 375): [GsmDCT] disableApnType:fota
What is fota and why is it causing the radios to disconnect? From a little googling, fota sounds like firmware over the air.
The logcat data was bogus because I think they had rotated. I'm going to have to capture it again when it happens.
Caught a logcat/dmesg of the LTE radio crash
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
Click to expand...
Click to collapse
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
Click to expand...
Click to collapse
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.
Does anyone have any reason to believe this is a software thing or a SIM card issue? Or do I have a Nexus with a dud LTE radio?
VZW says this is "normal"
I drove to the Verizon store where I noticed this dropping happening 3-4 times before, and sure enough it did it twice on my way.
The two VZW CSRs there said it's "normal for 4G phones" in this area. Their 4G coverage map shows this is a good area (not near "extended 4G"), so are they just blowing smoke up my ass?
In every case this happens, I see a message like this:
01-13 08:58:51.194 D/RIL[C] ( 114): __silent_reset [***** SILENT RESET START *****]
Click to expand...
Click to collapse
It's not always prefaced by this message, but was in 3 of the 4 cases:
01-13 08:58:50.194 D/RIL[C] ( 114): OnFMTDataReceived STATE_CRASH_EXIT on Modem #1
Click to expand...
Click to collapse
It looks to me like the radio is crapping itself and some kind of watchdog is kicking in. What is this silent restart stuff about? I also see this message corresponding to the drops:
01-13 08:58:51.413 D/CDMA ( 376): [CdmaDCT] NOT Posting Data Connection Unavailable notification -- likely transient error
Click to expand...
Click to collapse
google bug report
Well, not sure how much good it will do, but I filed a google bug report:
http://code.google.com/p/android/issues/detail?id=24345
Bad hardware
It was a bad radio in those two Nexuses. This one I have now has not had the data/voice drop plague that the last two had. Unfortunately, it has the purple tint and banding, so hopefully when I swap it out (again ) I'll get one with a functioning radio and a good screen.
jkc120 said:
It was a bad radio in those two Nexuses. This one I have now has not had the data/voice drop plague that the last two had. Unfortunately, it has the purple tint and banding, so hopefully when I swap it out (again ) I'll get one with a functioning radio and a good screen.
Click to expand...
Click to collapse
Well, after swapping the one I had that wasn't doing this data+voice drop, this one (also manufactured 12/23) has the same radio dropping problem. I hope it's software, but I went almost a week with the last one and I only saw that message in logcat once. This phone did it 2 times today, but none prior to that in ~24 hours. hmm...
i think the issues you are having are not phone related. i also think you would be much happier with an iphone or a windows phone.
sahakiap said:
i think the issues you are having are not phone related.
Click to expand...
Click to collapse
Really? Let's re-examine the facts:
- 3 phones all manufactured on 12/23 all have frequent voice+data drops. It is NOT just dropping 4G to 3G or even just data. It affects voice and data - all the internal modems seem to get reset/reinitialized
- 3 phones all manufactured in November had some screen issues (which were not present in the 3 above) but their radios never had this voice+data drop (the last one did do it once, but only once in 6 days)
- The day I swap from the "bad radio" one to the "good radio" one, I had experienced 4-5 drops that day already. The "good radio" one had none the remainder of the day and only 1 in the next 6 days.
What are the chances it was a "network issue" that coincided with me swapping the phone in and out? Almost 0.
But I'm all ears if you care to explain how this is not a phone issue.
i also think you would be much happier with an iphone or a windows phone.
Click to expand...
Click to collapse
Hell no. I can't stand both of those platforms nor OSes. So just because I point out problems with the phone, it means I should abandon the phone and android entirely?
jkc120 said:
What are the chances it was a "network issue" that coincided with me swapping the phone in and out? Almost 0.
:
Click to expand...
Click to collapse
id say the chances of it being a network issue, while small, are still far, far greater than the chances of you getting 7 or lord knows how many defective phones from different vendors in a row. im not going to debate you nor do i really care how many phones you go through on this quest of yours however you did post on a public forum asking for comments and i just think the issue is not these phones and you would be better suited with an iphone.
sahakiap said:
id say the chances of it being a network issue, while small, are still far, far greater than the chances of you getting 7 or lord knows how many defective phones from different vendors in a row.
Click to expand...
Click to collapse
If you had read the posts instead of internally paraphrasing them incorrectly, you'd know that the previous one I had did not have this hardware problem. There are people reporting the same thing in other forums as well as the google bug I filed. I have seen a couple people report seeing this happen on their Nexus while sitting right next to person with another Nexus. It is just way too coincidental that the drops occurred while I had the other one and this one, yet didn't with the last one. But you can choose to believe whatever you want.
im not going to debate you nor do i really care how many phones you go through on this quest of yours however you did post on a public forum asking for comments and i just think the issue is not these phones and you would be better suited with an iphone.
Click to expand...
Click to collapse
Well you apparently care enough to chime in and offer no additional information other than to dismiss a technical problem you probably can't even come close to understanding. Sounds like you're the one who should be using an iphone.
jkc120 said:
It was a bad radio in those two Nexuses. This one I have now has not had the data/voice drop plague that the last two had. Unfortunately, it has the purple tint and banding, so hopefully when I swap it out (again ) I'll get one with a functioning radio and a good screen.
Click to expand...
Click to collapse
Before you swap it out, what Baseband is the phone with the good voice & data running, 1515.10 or 1515.09?
strongergravity said:
Before you swap it out, what Baseband is the phone with the good voice & data running, 1515.10 or 1515.09?
Click to expand...
Click to collapse
Unfortunately, I have already swapped it.
If you're referring to the LTE radio rev shown in odin mode, it was 10. But this one is a 10 also and dropped 3 times yesterday. Although it's been about 21-22 hours since the last drop. hmm...
Anyway, this is what I saw in odin on the "good" one:
Board Rev: LTE - 10
If it helps, I'm having the same exact issue and haven't been able to find a fix yet
I'm having the same problem... And no, I won't be swapping out for an iPhone/WP7 device...
If it helps, I'm on Baseband I515.09 v.FA02 / I515.FA02
Android 4.04 | Kernel 3.0.8-g21f62a0 | Build IMM30B
I too have this issue. Verizon doesn't know how to fix it.
Baseband i515.10
Sent from my Galaxy Nexus using Tapatalk 2
Hardware problem
Guys, this is a hardware problem. Swap your devices or send to Samsung to have it fixed.
http://code.google.com/p/android/issues/detail?id=24345
So out of the blue this started happening, been for months on the same firmware and rom (1.32.401.17 and Viper 1.9.1, and no, I don't want to update, being on this firmware and rom can't be the cause is it worked flawless for quite some months already).
A few weeks ago it started for the first time, when I noticed my whatsapp messages not being send while not even 1 second ago they did.. Took about 30 seconds before they got sent. Now during this time, WiFi was still connected, but somehow data didn't get sent over it, more or less like it was stuck in limbo..
So I started checking other apps, and during those periods (that come and go every xx min) they didn't had any connection either.
After that I checked my other devices that are on wireless (iPad, 2 more smartphones and laptop), but they all seemed to be just fine, so it wasn't the network itself.
It does happen on both the 2.4 and 5GHz bands, sometimes it doesn't happen for quite some time and then suddenly nonstop with a few min in between. Disconnecting and reconnecting to the WiFi instantly fixes it though.
Now is there somewhat I can log this happening? Does Logcat help in this case? Would something be in the logs if I could snapshot the right moment? Or are there any proper tools I can monitor and log the WiFi connection with on my phone to get a better overview how often and how long these periods happen.
I have a feeling that maybe the WiFi chip is broken? Could the heat affect this and cause it to malfunction after some time? (Since I do notice it happening more often the longer I've been using the phone for that time)
If the chip was bust you'd have no wifi at all.
The problem will be in your configuration of network settings. Try rebooting your network to make sure the NAT is working correctly and make sure that your devices can see the gateway as a dns server, also use an isp dns as dns2.
It seems to me like its timing out on the ip "rental" or it's struggling to find a dns.
I wish I stole my HTC M9. It's a pile of ****.
Nah it's defo not the network, otherwise all other devices would be affected too (as I've said above already).
The router is a proper one, not some cheap €25, but the ASUS RT-N66U Dark Knight...
Anyway, tried to run logcat when it happened.
This is what stood out when it happened (though I could upload the full log if someone is actually interested in helping me.....)
Code:
09-10 02:27:19.540 D/WifiDataStallTracker(1304): updateDataStallInfo: mDataStallTxRxSum={txSum=359823 rxSum=497417} preTxRxSum={txSum=359822 rxSum=497417}
09-10 02:27:19.540 D/WifiDataStallTracker(1304): updateDataStallInfo: OUT sent=1 mSentSinceLastRecv=5
09-10 02:27:19.540 D/WifiDataStallTracker(1304): datastall detect!!
09-10 02:27:19.540 D/WifiDataStallTracker(1304): datastall detect when RSSI is -54
09-10 02:27:19.540 D/WifiDataStallTracker(1304): datastall detect when FREQ is 5240
09-10 02:27:19.540 D/WifiDataStallTracker(1304): datastall detect, ping gateway first
09-10 02:27:19.540 D/WifiDataStallTracker(1304): gateway IP: 192.168.1.1
09-10 02:27:20.600 D/WifiDataStallTracker(1304): ping gateway pass, don't do recover
Logcat will only show you what is happening at the device. If it's a network error you won't see anything out of the ordinary.
Fyi.. All home routers are cheap. Just because you pay a few quid more doesn't mean the device is more reliable. If you want a reliable system you pay thousands for a router from a business setup that has protection from every day faults like NAT errors, unreachable dns etc.
If only one device is affected it could be network OR device. I'd only blame my device if I'd knowingly messed with the wifi or radio etc.. Otherwise it'll be the router.
I wish I stole my HTC M9. It's a pile of ****.
Info
sausje85 said:
Nah it's defo not the network, otherwise all other devices would be affected too (as I've said above already).
The router is a proper one, not some cheap €25, but the ASUS RT-N66U Dark Knight...
Anyway, tried to run logcat when it happened.
This is what stood out when it happened (though I could upload the full log if someone is actually interested in helping me.....)
Code:
09-10 02:27:19.540 D/WifiDataStallTracker(1304): updateDataStallInfo: mDataStallTxRxSum={txSum=359823 rxSum=497417} preTxRxSum={txSum=359822 rxSum=497417}
09-10 02:27:19.540 D/WifiDataStallTracker(1304): updateDataStallInfo: OUT sent=1 mSentSinceLastRecv=5
09-10 02:27:19.540 D/WifiDataStallTracker(1304): datastall detect!!
09-10 02:27:19.540 D/WifiDataStallTracker(1304): datastall detect when RSSI is -54
09-10 02:27:19.540 D/WifiDataStallTracker(1304): datastall detect when FREQ is 5240
09-10 02:27:19.540 D/WifiDataStallTracker(1304): datastall detect, ping gateway first
09-10 02:27:19.540 D/WifiDataStallTracker(1304): gateway IP: 192.168.1.1
09-10 02:27:20.600 D/WifiDataStallTracker(1304): ping gateway pass, don't do recover
Click to expand...
Click to collapse
go to WiFi Setting > Advance > set Freq to 2.4GHz
also set your WiFi router to 2.4GHz
:good:
Geeks Empire said:
go to WiFi Setting > Advance > set Freq to 2.4GHz
also set your WiFi router to 2.4GHz
:good:
Click to expand...
Click to collapse
It's a dual router, so both are being send out at the same time.
Why would I use inferior 2.4 band anyway? There's like 15++ other 2.4 SSID's in my flat, only 2 other 5GHz,..
My recommendation.
So I've seen many different answers to what seemed to be the problem with the WiFi on my new M9. After connecting, data would throttle down to near nothing and occasionally come back, if only for a moment.
The fix was ridiculously simple, navigate to "Wifi Direct" under WiFi settings and rename the device in the submenu. After spending many hours tinkering with settings, reflashing, and almost returning the phone It was difficult to believe this was the difference that made the difference. I hope this helps someone and many, many thanks to the YouTube poster Rocky Xyzz to whom I cannot link yet due to my lurker status.
So after getting my phone back from repair, I've had to restore stock, update soft- and firmware, and put viper 3.5 on it. Now the exact same is happening again, this time with data though (and happening like every 30 seconds), WiFi is just fine and has no connection issues...
thans for sharing the solution, best regards!
LLegion said:
thans for sharing the solution, best regards!
Click to expand...
Click to collapse
If you meant that as sarcastic, I haven't found a solution at all, sooooooooooooo.........
sausje85 said:
If you meant that as sarcastic, I haven't found a solution at all, sooooooooooooo.........
Click to expand...
Click to collapse
dont misundertand me, not at all, reading some of the replis i though you have found solutions, im very sorry for the misunderstanding, i have nver had this isue at all and im runnig ViperOne 3.5.0 and works perfect....to your notes i have herad of some people with same issue in Mexico with Telcel carrier but no one has been able to provide a acurate solution......
If i were you, and this is my own humble prespective...i would first backup all my info and the place my phone underwater for 20 mins and ake use of the Uh-Oh warranty protection to replace my phone with no questions, one new phone replacement:
http://www.htc.com/us/uh-oh-protection/
LLegion said:
dont misundertand me, not at all, reading some of the replis i though you have found solutions, im very sorry for the misunderstanding, i have nver had this isue at all and im runnig ViperOne 3.5.0 and works perfect....to your notes i have herad of some people with same issue in Mexico with Telcel carrier but no one has been able to provide a acurate solution......
If i were you, and this is my own humble prespective...i would first backup all my info and the place my phone underwater for 20 mins and ake use of the Uh-Oh warranty protection to replace my phone with no questions, one new phone replacement:
http://www.htc.com/us/uh-oh-protection/
Click to expand...
Click to collapse
Ah ok, no I haven't yet. It just disappeared and now is happening to data suddenly (no matter what provider or network FYI).
We don't have the uh-oh protection here in Europe, so that's a no-go.
hominine said:
So I've seen many different answers to what seemed to be the problem with the WiFi on my new M9. After connecting, data would throttle down to near nothing and occasionally come back, if only for a moment.
The fix was ridiculously simple, navigate to "Wifi Direct" under WiFi settings and rename the device in the submenu. After spending many hours tinkering with settings, reflashing, and almost returning the phone It was difficult to believe this was the difference that made the difference. I hope this helps someone and many, many thanks to the YouTube poster Rocky Xyzz to whom I cannot link yet due to my lurker status.
Click to expand...
Click to collapse
I love you
Deathmeter said:
I love you
Click to expand...
Click to collapse
Glad it helped someone.
hominine said:
Glad it helped someone.
Click to expand...
Click to collapse
can you pm me the the dudes YouTube channel? couldn't find it myself
Deathmeter said:
can you pm me the the dudes YouTube channel? couldn't find it myself
Click to expand...
Click to collapse
Done.. https://youtu. be/2dnP00FpWoU
hominine said:
So I've seen many different answers to what seemed to be the problem with the WiFi on my new M9. After connecting, data would throttle down to near nothing and occasionally come back, if only for a moment.
The fix was ridiculously simple, navigate to "Wifi Direct" under WiFi settings and rename the device in the submenu. After spending many hours tinkering with settings, reflashing, and almost returning the phone It was difficult to believe this was the difference that made the difference. I hope this helps someone and many, many thanks to the YouTube poster Rocky Xyzz to whom I cannot link yet due to my lurker status.
Click to expand...
Click to collapse
I had the same problem and this seems to have fixed it. Thanks a million! Why would an update set the WiFi Direct name to something that causes so much trouble? HTC really needs to fix this - I was almost ready to send my M9 back because music streams kept stopping!
sausje85 said:
Ah ok, no I haven't yet. It just disappeared and now is happening to data suddenly (no matter what provider or network FYI).
Click to expand...
Click to collapse
Found a solution for your device? Tried getting back to stock, does it happen ?
exebreez said:
Found a solution for your device? Tried getting back to stock, does it happen ?
Click to expand...
Click to collapse
Nope, the going back to root and updating firmware only caused it to jump from happening to wifi, to happening to data (3G/3.5G/4G), now when I'm outside my data acts the same (as in still connected but somehow no connectivity)... I've already tried what people suggested here but that didn't help me.
Seems like a hardware related issue, saw it on my m7 a year ago.
If not tried before, try to reflash the latest modem firmware.
Hey guys,
FIrst of all: Thanks for maybe helping me.
So my problem is that I have a really annoying WiFi issue with my Galaxy Tab Pro. I installed a cm13 build (Link in that style because I am not allowed to share links...)
Code:
download[B]DOT[/B]cyanogenmod[B]DOT[/B]org/?device=mondrianwifi
a month ago and have one big problem with it. Whenever I want to use WLAN to connect to the internet (or use it on my local network, whatever) it just keeps flapping. It turns on and off and on and off and so on. I thought that it would be related to my home network at first (so that it doesn't get a IP or something like that), but after I checked my DHCP and general network settings and came to the conclusion that it can't be related to that. All other devices in my network are able to get a IP (and go online). When I turn on the WiFi on the tablet and check the network settings I see that it gets a IP but looses it after 1-2 secs. The thing which makes absolute no sense to me is that after a while (turning WiFi off and on again, 3-4 times) it often is able to get and keep a IP address. After that everything works fine - often for 1-2 hours until it looses the IP again and I have to begin with the game of randomness. I checked in the known bugs and could not finde that issue listet there. So I think it is maybe not related to the cm13 build I am using..? Or not even to the device? I don't know. Maybe you can help me - would be helpful enough if someone could tell me which logs I have to check when having a WiFi issue. I am quite new to such problems and don't know how I should start the troubleshooting.
So thanks in advance and greetings,
Maik