Long story short...was running Vegan-tab Gingeredition fine for about 2 weeks then one day got real slow and started to get endless reboot issue. NVflashed back to stock but noticed that wireless would not turn on. When activated it tried to start then gives "Error" message. I flashed to a few different ROMS and still have the same issue.
Anyone now how I can resolve this issue. Ready to throw in the towel. Thanks.
Sounds lioe hardware problem.
Yeah was thinking that myself. Maybe someone had the same issue and resolved it. We'll see.
yeah if you have done all the steps- reformatted cleared cache and dalvik like you are supposed to, it probably hardware. only other thing i could think of is trying to completely discharge the battery much like you would do with a computer "unplug" to reset a freeze up- really grasping at straws here.
make sure you are doing a data wipe/factory reset even after you nvflash. Alterntively, you can repartition teh internal SDCARD from within CWM.
ramerco said:
make sure you are doing a data wipe/factory reset even after you nvflash. Alterntively, you can repartition teh internal SDCARD from within CWM.
Click to expand...
Click to collapse
Personally I don't think that's the problem. But doesn't hurt to try.
ramerco said:
make sure you are doing a data wipe/factory reset even after you nvflash. Alterntively, you can repartition teh internal SDCARD from within CWM.
Click to expand...
Click to collapse
Tried it but still not working. Will try battery drain and see what happens.
Thanks for all suggestions.
i know you have tried different roms, but have you tried different Kernels? could be some weird issue for that too.
dexdash said:
i know you have tried different roms, but have you tried different Kernels? could be some weird issue for that too.
Click to expand...
Click to collapse
Good point. I would flash pershoots and clemsyns latest kernels and see if it changes your results.
Mantara said:
Good point. I would flash pershoots and clemsyns latest kernels and see if it changes your results.
Click to expand...
Click to collapse
kernel! that would make sense, im pretty new to the gtab but for the last few days i have been trying to load diff roms, with little success, but during my flashing on a restore to 1.2 i noticed i have a wifi problem, but i dont know how i could have hardware issue, this thing is brand new and its my babby i dont even drop it or throw it, not ever so i dont think the issue (in my case at least) is hardware issue.
Bump on this, I'm experiencing the same thing.. Any input from OP or otherwise?
Unfortunately never found a fix for it. I even took the gTablet apart to make sure the antennae wires weren't disconnected which they weren't. I believe it's a hardware issue. Tried getting Viewsonic tech support on the line but no response.
Let me know if you find anything out on your end. Good luck!
tech2pc said:
Unfortunately never found a fix for it. I even took the gTablet apart to make sure the antennae wires weren't disconnected which they weren't. I believe it's a hardware issue. Tried getting Viewsonic tech support on the line but no response.
Let me know if you find anything out on your end. Good luck!
Click to expand...
Click to collapse
I'll probably try to get it back to stock and send it back to Amazon under the assumption it's a hardware issue. Thanks for the quick reply, bc this is really bothering me..
If there is a hardware error, it may show up in the kernel or Android logs. See this thread, and get me the kernel logs first using dmesg.
I have a problem with intermittent wifi error on Flashback 8.x. Occasionally when I shut down and restart my tablet I get 'error' displayed next to wifi. Powering down and up may or may not fix it. Sometimes wiping cache via CWM works and will fix it quicker. I have attached a zip file that has two dmesg and logcat files one marked good and one marked bad. These represent working and non working wifi. Maybe somebody can make something of it.
Jim
jmbach said:
I have a problem with intermittent wifi error on Flashback 8.x. Occasionally when I shut down and restart my tablet I get 'error' displayed next to wifi. Powering down and up may or may not fix it. Sometimes wiping cache via CWM works and will fix it quicker. I have attached a zip file that has two dmesg and logcat files one marked good and one marked bad. These represent working and non working wifi. Maybe somebody can make something of it.
Jim
Click to expand...
Click to collapse
Your Wi-Fi hardware seems to be flaking out. There are clear errors in the dmesgbad.txt file:
Code:
<4>[ 66.035915] bcmsdh_sdmmc: probe of mmc0:0001:1 failed with error -110
<4>[ 66.048711] bcmsdh_sdmmc: probe of mmc0:0001:2 failed with error -110
<4>[ 66.066313] bcmsdh_sdmmc: probe of mmc0:0001:3 failed with error -110
...
<4>[ 98.368522] dhd_module_init: sdio_register_driver timeout
Error -110 is a timeout error. It means that the SDIO subsystem (through which the WLAN connected to the main board) failed to respond to a command sent to it.
rajeevvp said:
Your Wi-Fi hardware seems to be flaking out. There are clear errors in the dmesgbad.txt file:
Code:
<4>[ 66.035915] bcmsdh_sdmmc: probe of mmc0:0001:1 failed with error -110
<4>[ 66.048711] bcmsdh_sdmmc: probe of mmc0:0001:2 failed with error -110
<4>[ 66.066313] bcmsdh_sdmmc: probe of mmc0:0001:3 failed with error -110
...
<4>[ 98.368522] dhd_module_init: sdio_register_driver timeout
Error -110 is a timeout error. It means that the SDIO subsystem (through which the WLAN connected to the main board) failed to respond to a command sent to it.
Click to expand...
Click to collapse
Hi rajeevvp,
Saw those as well but did not know what error -110 meant. This only happens intermittently when going to sleep and waking up or if powering down and up. Also I do not seem to have this issue with CM7. Not sure if CM7 and FB 8.x handle initiation routines differently for wifi and this may be a problem or if it is how the drivers handle startup. I downgraded the drivers once from a post you made elsewhere and the problem was less often but not nil.
Will be willing to do more testing/debugging if you want me to or try mods to the system. Would be interesting if there was some way of polling the hardware to get more lower level information.
Anyway I am game if you are.
Jim
jmbach said:
This only happens intermittently when going to sleep and waking up or if powering down and up.
Click to expand...
Click to collapse
If I had to hazard a guess, I would say that your hardware is the problem--it doesn't initialize itself properly everytime it is activated (either when powered on or when coming out of sleep). Consider sending it back.
Also I do not seem to have this issue with CM7. Not sure if CM7 and FB 8.x handle initiation routines differently for wifi and this may be a problem or if it is how the drivers handle startup.
Click to expand...
Click to collapse
Those error messages are from the kernel (the WLAN driver, to be precise), so this is not a ROM issue. If you didn't have problems with CM7 (which version BTW?) it is likely because it had an older pershoot kernel.
If you want to try "fixing" this problem using software, your best bet is to try one of the older pershoot kernels, going back one by one, until the problem "stops"--but I doubt that it is the kernel for these reasons:
1. Pershoot hasn't modified the WiFi driver source and firmware binary blobs since April '11, so both the CM7 you had on before and the current ROM will very likely have had the same drivers. If you have a problem with the current ROM, you will very likely have a problem with CM7 if you go back to it now.
2. The SDIO/SDHC/MMC subsystem is screwy on some VS hardware. VS has a device called the gTablet, but, with slightly different hardware inside it. For eg: some people have had problems with one kind of internal SD card. Keeping this in mind--and what follows here is very speculative--I see that you have a slightly different WLAN HW: Most users, going by the collection of dmesg outputs that I have, have a MAC address (manufacturer) prefix of 'e0:2a:82'. You have: '00:27:13'. Both are assigned to the "Universal Global Scientific Industrial Co., Ltd.", but, does the difference mean slightly different hardware? I don't know, but, keep this in mind anyway.
Still, as I said, I think it's a hardware problem (or a hardware problem caused by messing around improperly with nvflash).
To verify that it's a hardware problem, try Clemsyn's kernel for your ROM. It's closer to the VS stock kernel than pershoot's is. Finally, you could also revert completely back to stock VS firmware.
rajeevvp said:
Still, as I said, I think it's a hardware problem (or a hardware problem caused by messing around improperly with nvflash).
Click to expand...
Click to collapse
If it is a hardware problem due to nvflash then is there a solution using nvflash. Also if it was due to nvflash would not the problem be consistent and not intermittent? I guess that would depend on what changes you think nvflash may have caused. All I have used it for is to flash between 1.1 and 1.2 BL using roebeet's packages.
Will try your suggestions. If it is consistent across kernels/ROMs then I agree it is hardware based.
I'll report back my findings once I am done. Might take a while since it is an intermittent problem.
Thanks for your insight.
Jim
This may sound elementary, but I am surprised no one has suggested manually pushing the wifi module to the ROM. Pershoot has had users experience this error countless times and reflashing the kernel did not work in all cases. What did work was manually pushing the wifi module through ADB or root explorer. That is my suggestion.
Related
Hi everyone.
I have recently upgraded my SGA from original 2.2.1 to 2.3.3 XXKPE and i have detected an issue when i try to use the WPA + AES combination. The phone detects the wifi but it tries to validate the password a few times and then it is disconnected...
When i tried to connect with the older firmware (Froyo 2.2.1) i could connect the first time but when i lost the connectivity my wifi changed it's state to error and the only way to reconnect was restarting the phone.
No issue detected with WEP or WPA + TKIP.
Anyone else has the same problem? If not, can you tell me your firmware version?
Many thanks in advance
Same situation: S5830 + ASUS WL500W works only with WPA TKIP. But with TKIP speed is limited to 54mbps. Android OS 2.3.4
Just picked up a Samsung Galaxy Ace running stock Android 2.3.4 (baseband S5830LUBKP7, kernel 2.6.35.7-perf-CL366939 [email protected] #1), and seem to be having this same problem.
My home wifi is set to WPA2 Personal+AES, and when the correct passphrase is entered, the Ace just continuously cycles through "Connecting... Disconnected", over and over.
If I drop back to WPA Personal+AES, I get the exact same thing. *However*, if I drop to WPA Personal+TKIP, the phone connects immediately.
I really don't want to use TKIP, as it has known exploits. Is there a known FOTA update for a US-market, unbranded Galaxy Ace that fixes this, or is there any known workaround except "don't use AES"?
try DDKQ6
after flashing DDQK6, reboot phone and enter PIN
then reboot again but in recovery and install CWM5
reboot and wipe data/cache/dalvik and reboot
evilxdeadly said:
try DDKQ6
after flashing DDQK6, reboot phone and enter PIN
then reboot again but in recovery and install CWM5
reboot and wipe data/cache/dalvik and reboot
Click to expand...
Click to collapse
Thanks for the info. I'm new to flashing phones, would kinda like to stay stock if possible, since this is my wife's phone, not my own. Am I correct in thinking DDQK6 is an Indian firmware? If so, what would differ from US-market firmware, and would I potentially lose any features or cause any unusual behavior by switching to it?
knoxploration said:
Thanks for the info. I'm new to flashing phones, would kinda like to stay stock if possible, since this is my wife's phone, not my own. Am I correct in thinking DDQK6 is an Indian firmware? If so, what would differ from US-market firmware, and would I potentially lose any features or cause any unusual behavior by switching to it?
Click to expand...
Click to collapse
Just update it over the air from setting -> about/phone -> update.
Make sure you have backed up the data like contacts and sms.
Hey, hey!! Problem with wifi? I'm an expert on this But I came with bad news, though.
What I found out:
There's indeed a bug that prevents us from connecting to this kind of wireless (eduroam, in my case). Everything seems to come from a buggy version of wpa_supplicant, everything goes well but then, in the second phase, it seems to "forget" the password or something (I'm not an expert, sorry, can't explain any better) I've been trying to change it, but no luck.
I've tried most of the stock firmwares, and custom roms as well. No luck, still the same bug.
There's an app that claims to fix the problem. wifi ace if I remember well (advanced config editor). But it didn't fix anything for me. You may want to give it a try.
I was expecting for samsung to fix it, but I've lost my faith on it. Neither google seems to be doing anything, as the bug remains on android 4.0.
I can provide you with some links, in case you want to read more about. And please, let me know if you find something.
http://forum.xda-developers.com/showthread.php?t=1255245
http://code.google.com/p/android/issues/detail?id=15631
[More in Spanish. I'm not posting it since they say more or less the same]
alexnm said:
Hey, hey!! Problem with wifi? I'm an expert on this But I came with bad news, though.
What I found out:
There's indeed a bug that prevents us from connecting to this kind of wireless (eduroam, in my case). Everything seems to come from a buggy version of wpa_supplicant, everything goes well but then, in the second phase, it seems to "forget" the password or something (I'm not an expert, sorry, can't explain any better) I've been trying to change it, but no luck.
I've tried most of the stock firmwares, and custom roms as well. No luck, still the same bug.
There's an app that claims to fix the problem. wifi ace if I remember well (advanced config editor). But it didn't fix anything for me. You may want to give it a try.
I was expecting for samsung to fix it, but I've lost my faith on it. Neither google seems to be doing anything, as the bug remains on android 4.0.
I can provide you with some links, in case you want to read more about. And please, let me know if you find something.
http://forum.xda-developers.com/showthread.php?t=1255245
http://code.google.com/p/android/issues/detail?id=15631
[More in Spanish. I'm not posting it since they say more or less the same]
Click to expand...
Click to collapse
Check the OP date?
Oops, didn't see that, sorry :$
alexnm said:
Oops, didn't see that, sorry :$
Click to expand...
Click to collapse
No need to be sorry. You're replying to a thread that's current, in that I replied to it with my own problem. (And I did so because it was the only thread that came up in the Ace forum on a search for AES, which seems to be specific to the problem. Didn't seem to make sense to start a new thread when this one covers the same topic.)
Not sure if anyone else has seen this issue. I have been having Wifi issues with almost all GB ROMs. Wifi will be working fine then just drop off and reconnect randomly. This happens while I am using it and not while sleeping. I have confirmed this with Vegan 7.1, GHarmony, and the Flash* version from Slatedroid. I do not remember having this issue with CM7, but didn't like the ROM so I changed. I really want to switch to GB but this is a show stopper. Anyone thoughts?
Update to the latest Pershoot kernel. That has some fixes for this.
If the problem still persists, try downgrading your WiFi firmware blobs.
Note, however, that the causes of WiFi drops are many. Some troubleshooting will be needed to find out the exact cause of your problem.
Thanks for the recommendations. I tried newer kernel and downgrading the Wifi blobs. Still no go. The odd thing is this only happens with GB ROMs, all Froyo ROMs are fine, and it seems to be limited to my home Wifi, which is WPA/WPA2, at work with LEAP it doesn't happen. Going to try changing some settings on my WIFI this weekend. To compare Flashpoint from Slatedroid works fine, but the GB version Flashlight has the problem. Also going to try the older Vegan 7 on 1.2 bootloader, i don't remember this happening on that or CM7 build 86.
See if this helps: It doesn't.
Code:
$ [B]su[/B]
# [B]wpa_cli -i wlan0 driver setsuspendopt 1[/B]
[I]Wait 15 secs[/I]
# [B]wpa_cli -i wlan0 driver setsuspendopt 0[/B]
Sorry most of this is greek to me as I am a NOOB. Have Gtab 3588 1.1 vegan 7.?
all of a sudden I can't connect to wifi, all my other devices at home work fine. Getting a disabled connection from home, have tried re-adding, rebooting, reseting rom, reinstalling Vegan.
I sorry I need step by step help
thx Jaye
markmac said:
Not sure if anyone else has seen this issue. I have been having Wifi issues with almost all GB ROMs. Wifi will be working fine then just drop off and reconnect randomly. This happens while I am using it and not while sleeping. I have confirmed this with Vegan 7.1, GHarmony, and the Flash* version from Slatedroid. I do not remember having this issue with CM7, but didn't like the ROM so I changed. I really want to switch to GB but this is a show stopper. Anyone thoughts?
Click to expand...
Click to collapse
I think it has to do with the AES encryption key updates and the gingerbread wifi libs. Take a look at this post to see how you can change your router settings to prevent or minimize this.
http://forum.xda-developers.com/showpost.php?p=18035185&postcount=144
gtabowner said:
Sorry mosy of this is greek to me as I am a NOOB. Have Gtab 3588 1.1 vegan 7.?
Click to expand...
Click to collapse
Exact version?
all of a sudden I can't connect to wifi, all my other devices at home work fine. Getting a disabled connection from home, have tried readding, rebooting, reseting rom, reinstalling Vegan.
Click to expand...
Click to collapse
As I said in post #2, above:
Note, however, that the causes of WiFi drops are many. Some troubleshooting will be needed to find out the exact cause of your problem.
Click to expand...
Click to collapse
However, you can:
1. Try upgrading to the latest pershoot kernel. Since you're on Vegan 7 (a Gingerbread ROM) and the 1.1 bootloader, go to http://droidbasement.com/db-blog/ and download this file boot-cm_2632.46_gb-oc-uv-xtra-vfp_fp-083111.zip from there. Copy the zip file onto your gtab, then install it using CWM.
2. If the upgraded kernel doesn't help try downgrading the firmware blobs using the link in post #2. Use the Cyanogenmod zip file.
3. If neither of the 2 steps above work, then follow this post and get me some logs.
As i thought,i have tried Vegan 7.0 and the problem is not occuring. I did have an issue with the new market but i just rolled back to original and removed the market updater. Seems like the issue is related to the 2.3.5 versions of ROMs.
rajeevvp said:
Exact version?
As I said in post #2, above:
However, you can:
1. Try upgrading to the latest pershoot kernel. Since you're on Vegan 7 (a Gingerbread ROM) and the 1.1 bootloader, go to http://droidbasement.com/db-blog/ and download this file boot-cm_2632.46_gb-oc-uv-xtra-vfp_fp-083111.zip from there. Copy the zip file onto your gtab, then install it using CWM.
2. If the upgraded kernel doesn't help try downgrading the firmware blobs using the link in post #2. Use the Cyanogenmod zip file.
3. If neither of the 2 steps above work, then follow this post and get me some logs.
Click to expand...
Click to collapse
will try this today
Thank you again. when I can get in I will find out what exact Vegan and such i am using. What info do you need? and exactly where do I find it. It says 7.0.0 when booting up
Thank you all again.
gtabowner said:
What info do you need? and exactly where do I find it. It says 7.0.0 when booting up
Click to expand...
Click to collapse
Fine, then you have a Gingerbread ROM. Just follow the instructions in post #7, above, and see if each step helps.
If steps 1. and 2. don't help you, use the instructions in the link in step 3. to get me logs which will help me troubleshoot your problem.
rajeevvp said:
If steps 1. and 2. don't help you, use the instructions in the link in step 3. to get me logs which will help me troubleshoot your problem.
Click to expand...
Click to collapse
HI,
I hope this thread is still active as I'm having very similar issue. It has started 2-3 weeks after I got my gTablet and flashed it. The usual scenario is this:
1. Reboot
2. Immediate connection to wifi
3. Starting using internet - immediate disconnect
4. After several minutes of constant connect/disconnect finally connected
5. From now it works for a few minutes, then disconnect, then reconnects, works again, disconnects again etc.
What I have already tried:
1. Changing wifi channel - no difference
2. Changing security (wpa, wep, none) - no difference
2. Downgrading blobs - no difference
3. Installing new kernel - that seem to stabilize reconnection (it reconnects more often and more reliable)
At home I'm runnig netgear WNDR3300 router with ddwrt installed. I've also tried public RoadRunner access point in the gym but the result is the same.
I'm starting to think it is a hardware problem but would like somebody to verify that. Any help greatly appreciated. Log files are attached.
Thanks,
Janusz
1. As per the logs your access point seems to be returning an invalid lease time (-1 seconds). Change the DHCP lease time to 3600 seconds (1 hour) and get me another set of logs.
2. Why does your Netgear wireless router broadcast 2 SSIDs, "PL" and "PLN" ?
My DHCP lease time was set to set to 1440 minutes (minutes is the only available unit here). I don't remember changing that so it must be a default one. I can change it to 60 minutes and rerun logs.
My router has 2 radios. I need to keep WEP encryption for my linksys internet radios that don't support WPA. Originally I only had one radio turned on with WEP but once I started getting problems with gtablet I played with different settings. Now I'm running both radios. PLN is WPA encrypted with G only connection on channel 11 and PL is WPA b/g on channel 4. They don't interfere with each other and turning one of them off or on didn't make a difference for gTablet.
Janusz
New set of logs after chaning DHCP lease time to 60 minutes. Disconnects seem to be less frequent and they reconnect almost immediately. My previous post should say that PL radio is set to WEP, not WPA.
Thanks a lot,
Janusz
januszk said:
New set of logs after chaning DHCP lease time to 60 minutes. Disconnects seem to be less frequent and they reconnect almost immediately.
Click to expand...
Click to collapse
Change the WPA Group Rekey Interval to a different value (I have it set to 1800 seconds) then reboot both the router and the gTablet. The new set of logs show that the gTab is having trouble connecting to the Netgear.
See also this post for another setting which you can try tweaking.
Done. Was set to max 99999. Still disconnects, hard to say if less or more often then before (although works way better then yesterday). New logs attached.
Thanks,
Janusz
januszk said:
Done. Was set to max 99999. Still disconnects...
Click to expand...
Click to collapse
The latest set of logs show that the gTablet is still having problems connecting to the Netgear router:
Code:
gTablet$ [B]su[/B]
gTablet# [B]logcat -d -v time | egrep -i 'connectivity|dhcp|wpa|wifi|wlan'[/B]
...
10-21 12:51:13.406 E/ConnectivityService( 1048): Attempt to connect to WIFI failed.
...
I also see that the tablet is trying to connect to SSID 'PLN'. The first set of logs had it connecting to SSID 'PL'.
Suggestions:
1. Go back to the default values for Wireless LAN Settings on the wireless router--except for the ones we changed in this thread.
2. Delete the WiFi connection from the gTablet, reboot, then set up a new connection (only for SSID 'PLN').
3. For this new connection, set the no. of channels to 11 channels--ie US channel settings. (Advanced WiFi settings)
4. Turn off any "Network Notification" in WiFi settings.
5. Go back to the stock firmware on the wireless router instead of dd-wrt.
...hard to say if less or more often then before (although works way better then yesterday). New logs attached.
Click to expand...
Click to collapse
It's still disconnecting pretty regularly. Subjective judgements can be erroneous, so use the script (attached) that I use to check these things. After making the script (which needs busybox) executable and moving it into /data/local/bin, run it like this inside a Terminal Emulator window:
Code:
gTablet$ [B]dmesg | d.awk[/B]
[63636.011275] STA connect received 1
[66204.696828] STA connect received 1: 42m 48s
You can also pass one of the previously collected dmesg*.txt files through the script:
Code:
gTablet$ [B]d.awk /mnt/sdcard/dmesg2.txt[/B]
<4>[ 33.513973] STA connect received 1
<4>[ 215.890648] STA connect received 1: 3m 2s
<4>[ 396.218500] STA connect received 1: 3m 0s
<4>[ 576.546805] STA connect received 1: 3m 0s
<4>[ 757.899052] STA connect received 1: 3m 1s
<4>[ 938.227396] STA connect received 1: 3m 0s
Thanks a lot. I'll try some of those. I'll get my tablet to one of my friends to see if this will work better with other routers. I've already tried leaving only PLN connection but it didn't make any difference. The reason why latest logs were primarily PLN were because if "forgot" settings for PL. You have suggested to change WPA key renewal and this setting is only for PLN, thats why I removed PL, which is WEP. I may try resetting to defaults but I don't really want to go back to stock firmware as it has been reported by many as buggy and unstable. Its dd-wrt that puts new lifie into it. I have the whole bunch of other wifi devices at home and everything works perfectly.
I'll also give your script a try to see where I stand at.
BTW: Do you think it may be hardware problem? I don't think the BT/WIFI module is easily replacable without replacing the whole motherboard.
In the meantime I really appreciate your help so how can I buy you a beer?
Janusz
januszk said:
BTW: Do you think it may be hardware problem?
Click to expand...
Click to collapse
Nothing in the logs indicate that this is hardware-caused. Other people, including me, have faced this before without hardware issues, so it is very likely a software problem. Our gTablet does not work well with some kinds of wireless routers. I have a software fix working on my gTab which I am in the process of testing. I'll send it upstream after I'm satisfied that it doesn't inadvertently break other things.
In the meantime I really appreciate your help so how can I buy you a beer?
Click to expand...
Click to collapse
Make a donation to your favourite charity instead--or buy a beer for a friend.
OK, will do
I've installed your custom awk script. Disconnects are every few minutes or so, well I'll live with it for now and try another router. When you have your fix ready sign me up for a beta testing.
Thanks again,
Janusz
The following is a common problem with the Atrix, so it seems:
http://forum.xda-developers.com/showthread.php?p=26120173#post26120173
Symptoms:
Try to enable the WiFi or Bluetooth : Doesn't enable BT or WiFi, sometimes will reboot phone.
Or it will constantly reboot phone, depending if you can get to the Airplane mode switch quick enough.
Sometimes in middle of calls it will reboot.
Suggested remedies
1) Format cache
2) Fix permissions
3) Replace firmware libs on /system/etc/modules/wifi
4) Detach + reattach battery clock on CPU/Accelerometer/WiFi/BT motherboard
5) Run stock ROM
6) Vote for Ron Paul
I've done the following
1 + 2 + 3 + 4 + 5. 6 doesn't seem probable to fix this case.
TWICE I've got the WiFi to work again. After that, reboot hell untill I could disable WiFi / BT.
Disclaimer : the following is a cross post from the previous forum
Kernel dumps
[ 31.028143] sdhci_tegra_wlan_detect Detecting WLAN
[ 31.028164] mot_wifi_set_carddetect: Nobody to notify
[ 31.029391]
[ 31.029395] Dongle Host Driver, version 4.218.248.32
[ 31.029400] Compiled in /tank/jokersax/cm9/kernel/moto/olympus/wifi-module/wlan/osrc/open-src/src/dhd/linux/../.. on May 7 2012 at 11:40:09
[ 31.328158] mmc1: error -110 whilst initialising SDIO card
WARNING: at /tank/jokersax/cm9/kernel/moto/olympus/lib/kobject.c:595 kobject_put+0x50/0x60()
[ 214.627572] kobject: '<NULL>' (0003da74): is not initialized, yet kobject_put() is being called.
[ 214.627581] Modules linked in: dhd(+)
[ 214.627591] Backtrace:
[ 214.627612] [<c0040010>] (dump_backtrace+0x0/0x10c) from [<c05b68c8>] (dump_stack+0x18/0x1c)
[ 214.627622] r7:c031c6c4 r6:c071fb48 r5:00000253 r4:e83a1e98
[ 214.627647] [<c05b68b0>] (dump_stack+0x0/0x1c) from [<c00bc5b8>] (warn_slowpath_common+0x50/0x68)
[ 214.627663] [<c00bc568>] (warn_slowpath_common+0x0/0x68) from [<c00bc61c>] (warn_slowpath_fmt+0x30/0x38)
[ 214.627673] r7:bf081000 r6:00000000 r5:bf076570 r4:0003da74
[ 214.627692] [<c00bc5ec>] (warn_slowpath_fmt+0x0/0x38) from [<c031c6c4>] (kobject_put+0x50/0x60)
[ 214.627701] r3:00000000 r2:c071fb80
[ 214.627720] [<c031c674>] (kobject_put+0x0/0x60) from [<c03787f0>] (put_driver+0x14/0x18)
[ 214.627729] r4:e98390c0
[ 214.627742] [<c03787dc>] (put_driver+0x0/0x18) from [<c0378938>] (driver_register+0x144/0x164)
[ 214.627757] [<c03787f4>] (driver_register+0x0/0x164) from [<c037994c>] (platform_driver_register+0x4c/0x60)
[ 214.627767] r9:00000000 r8:00000000 r7:bf081000 r6:00000000 r5:e83a0000
[ 214.627782] r4:bf078890
[ 214.627826] [<c0379900>] (platform_driver_register+0x0/0x60) from [<bf049fa4>] (wifi_add_dev+0x24/0x40 [dhd])
[ 214.627870] [<bf049f80>] (wifi_add_dev+0x0/0x40 [dhd]) from [<bf0810bc>] (init_module+0xbc/0x238 [dhd])
[ 214.627902] [<bf081000>] (init_module+0x0/0x238 [dhd]) from [<c003b5c8>] (do_one_initcall+0x40/0x1bc)
[ 214.627912] r5:e83a0000 r4:c07e0c00
[ 214.627932] [<c003b588>] (do_one_initcall+0x0/0x1bc) from [<c00f3880>] (sys_init_module+0xcc/0x200)
[ 214.627941] r9:e83a0000 r8:c003c364 r7:00046bd8 r6:00000000 r5:bf076748
[ 214.627957] r4:5c126008
[ 214.627970] [<c00f37b4>] (sys_init_module+0x0/0x200) from <c003c1e0>] (ret_fast_syscall+0x0/0x2c)
[ 214.627979] r7:00000080 r6:5e0fdb34 r5:5c126008 r4:405ad0f0
[ 214.627995] ---[ end trace 2416c978061dd5a5 ]---
[ 214.628002] Error: Driver 'bcm4329_wlan' is already registered, aborting...
Now I had some experience with WiFi kernel driver development (iMx51 + CSR based WiFi/BT combo chip).
The startup sequence on kernel level will probably go like this:
1) Kernel startup
2) ARM CPU specifics startup
3) Platform specific device setup (setup clocks)
3) Platform driver dependency registration (like, on SDIO 1 there is a WiFI chip that needs driver X to work)
4) Sub-platform driver startup (SPI, SDIO, UART, I2C)
I think this is where we fail first - Error -110 means timeout. Each MMC / SDIO chip has a MMC specific startup sequence, then depending what was given on number 3, it jumps over to SDIO (SDIO is a superset of MMC).
When our BT/WiFi chip is put into SDIO mode, the SDIO commands fail with a time out.
Possible reasons for it failing:
1) Incorrect voltages
2) Skewed clock
3) Busted chip.
4) We talk to it too fast
5) Kernel is messed up
Now, seeing that (through weird loops, check my previous post) I could get the unit running two more times, I do not think it is 3.
Why it could be 1:
Voltage rails needs to start up at the correct sequence for some chips. Like some chips will specify an operating range of between 1.8V and 3.3V. That means if it finds 5V on it, it will shut itself off. Sometimes some chips needs an initial 3V, then after 10 seconds it can be put into 1.8V (in-chip startup). Sometimes, it needs 10seconds to stabilize before you can talk to it (in our case via SDIO).
Why it isn't 1:
I've tried a lot of other kernels. It is all based off the ATT code, and they do the voltage rail setup correctly. I've even reverted back to stock code - no dice.
Why it could be 2
By removing the small cell battery, the drain on the battery was lifted. It could then store up enough current to put itself into the correct clock rate when it was put back.
Why it isn't 2
? Don't know. More needs to be known of the function of this battery. Obviously it is driving some RTC (real time clock). RTC's normally work at 32MHz, (32768, easilly divideable by 2, 4, 8 etc).
Does the Broadcom chip need this RTC? Isn't its clock lines driven by the Tegra2?
Why it could be 4
If the RTC is compromised (number 2) then init will suffer. If the Tegra's clock is not derived from the battery and the Broadcom's is, then there will be a disparity between the 2 units chatting together, as SDIO communication is clock based and not latch based (like SPI). If I'm chatting to you at 32MHz and you are 5% off, then we will not be communicating (if you are an SDIO master and I'm an SDIO slave).
Why it isn't
No idea.
Why it could be 5
Bunch of kernel errors stating un-inited modules pointing to null.
Why it isn't 5
Stock kernels also have the same problem
So, sorry folks, this issue points to a hardware problem.
Our biggest answer will be at the following:
1) What does that battery do?
2) Why is the SDIO subsystem having timeouts?
That's all for now.
Dude, I have this SAME EXACT problem. Full wiping helped temporarily, and sometimes not at all. Flashing back to stock doesn't even help. My next move is to buy a new battery.
And I was already planning on voting for Ron Paul.
I got so tired of my Atrix rebooting and the WiFi not working that I ended up downgrading back to my Captivate. :/
that does seem to me like a Hardware failure on the broadcomm bt/wifi chip =/ there seems to be a sdio/mmc1 error in your first dump, did you try removing the external sdcard ?
on the other hand, did you try to rsd flash a stock rom (not just flash it form recovery but with rsd)?
I had this issue and struggled with it for over a month. Finally, I ended up sending it back to Motorola for warranty.
It's unlocked and I didn't try to obscure that - it seemed dishonest, and this issue isn't caused by my actions as far as I can tell. I've seen lots of people online with stock handsets with the same issue.
They received it yesterday, so we'll see if they fix it. If not, I'll be happy if they let me pay to have it repaired out of warranty. Their site says out-of-warranty repairs are $110, flat, so that's not too bad. If they refuse to service it, I'll probably never buy a Motorola product again...
I did everything I could think of to try and make it work, and it got progressively worse and finally stopped working at all. The only ROMs I had used when mine died were stock, CM7 BA2TF, and the two CM9 KANGs floating around. I was using turl's v9 when it started giving me the error.
mine started doing that when i went from nottach's the darkside prefinal to turls v8 then to nottachtrix4g 1.0
I Haven't got this problems.
I've got random reboots for no reason (4-5 at day) and when trying to switch from offline mode to online always caused reboots (but after a long idle in offline)
Send it on warranty, and they replaced the MoBo (I think, they call it " Electronical Board") so I've got a new IMIEI too.
10 hours and not one single reboot. Tonight i'll try to put in offline .
Tomorrow I'll post :v
crnkoj said:
that does seem to me like a Hardware failure on the broadcomm bt/wifi chip =/ there seems to be a sdio/mmc1 error in your first dump, did you try removing the external sdcard ?
on the other hand, did you try to rsd flash a stock rom (not just flash it form recovery but with rsd)?
Click to expand...
Click to collapse
Yea, I've tried removing my sd card even while flashing back to stock using RSD.
I have the same exact problem. I found another thread referencing to it and an interesting YouTube video too. Ill post soon
Sent from my MB860 using XDA
Ok so, after the replace of the MoBo, no reboots, and this morning (after kept the phone in airplane mode in the night ,8 hours) switching to online, no reboot.
Anyway I will keep u informed if it comes back or w/e
same problem
I have also Atrix 4G (ATT) witch same problem "WiFi error"
What i ready do and check:
- reflash latest radio = NOT HELP
- flash many ROMs = NOT HELP
- wipe all = NOT HELP
- disconnect and connect internal battery = NOT HELP
- after disconnect and connect internal battery - reboot stop... and start after i try setup BT or WiFi
Also what i finde intrest:
- internal battery have 2.4 V (not 3V, but i dont know correct value)
- i cant make backup from CWM may PDS
What i plane to do:
- replace internal battery to new one
- try to make PDS repair (i finde on forum PDS repair file)
- rehot phone PCB (i have infrared soldering station)
What i serch for help
- Atrix scheme and service manual
- information about phones factory repaired witch this problem (IMEI same or changed ?)
- some one try repair own PDS for fix this problem ?
THX for any information, if i finde way - post here
ready check soft brick
I make softbrick for may Atrix - all manual erased and then install clear radio and rom = NOT HELP
I sent my root & unlocked Atrix to Motorola - they sent me a new one under warranty. I restored the factory ROM, but did not try to hide the fact that it was unlocked.
Sent from my Samsung Galaxy Tab 2.
TheTinkerer said:
... If they refuse to service it, I'll probably never buy a Motorola product again...
Click to expand...
Click to collapse
May be they read the forum too and trying to keep you as a customer
I have the same issues.... This happened to me after flashing Neutrino's CM7 ROM so I'm still thinking this is a fixable issue... I hope!
But so far no luck. Yesterday I even reset everything using the Motorola update software on my laptop. It re-locked my phone, put on the default Android recovery, and reset the ROM to un-rooted and stock. The boot screen was AT&T's logo and everything I'd expect from a fresh phone from the store. But still the WiFi settings showed an "Error" as it's status and if I click it on a few times the phone reboots just like before.
So I performed the unlock and loaded the CM Recovery and now I'm back to the ICS ROM which is awesome except I have no WiFi or Bluetooth. Data usage is adding up on my AT&T account...
Any fresh ideas are gladly welcomed.
I've never had any random wifi reboots until I installed 2.3.5 or 2.3.6 stock and custom roms. When I installed anyone's version of the two rom, my wifi signal would drop every 3 mins like clock work. I have a Beklin wireless N router at home. This only happened to me when I was using that router. All other makes worked fine (netgear, linksys, wifi hotspot, etc). I can't figure out what setting is causing this, any ideas?
Sent from my MB860 using xda premium
bigron77 said:
I've never had any random wifi reboots until I installed 2.3.5 or 2.3.6 stock and custom roms. When I installed anyone's version of the two rom, my wifi signal would drop every 3 mins like clock work. I have a Beklin wireless N router at home. This only happened to me when I was using that router. All other makes worked fine (netgear, linksys, wifi hotspot, etc). I can't figure out what setting is causing this, any ideas?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Sounds like you have a router issue and a quick place to start is do a physical reset of the router so it goes back to stock settings. Then configure it one thing at a time until the comes up again.
The issue posted here is different. We're having the wifi and bluetooth hardware malfunctioning. It's not that we have issues holding a connection to a certain router, it is that wifi on the phone won't turn on at all. Maybe there's a distant relation to the issues, but I'm thinking their unrelated.
---------- Post added at 10:43 PM ---------- Previous post was at 10:42 PM ----------
robeknight said:
I have the same issues.... This happened to me after flashing Neutrino's CM7 ROM so I'm still thinking this is a fixable issue... I hope!
But so far no luck. Yesterday I even reset everything using the Motorola update software on my laptop. It re-locked my phone, put on the default Android recovery, and reset the ROM to un-rooted and stock. The boot screen was AT&T's logo and everything I'd expect from a fresh phone from the store. But still the WiFi settings showed an "Error" as it's status and if I click it on a few times the phone reboots just like before.
So I performed the unlock and loaded the CM Recovery and now I'm back to the ICS ROM which is awesome except I have no WiFi or Bluetooth. Data usage is adding up on my AT&T account...
Any fresh ideas are gladly welcomed.
Click to expand...
Click to collapse
Btw, I've had my Atrix for about 14 months now so I can't get it replaced by warranty. I've already tried that :-(
Have you tried fastboot erase boot? Then reflash your rom
Sent from my MB860 using XDA
aaron.a said:
Have you tried fastboot erase boot? Then reflash your rom
Sent from my MB860 using XDA
Click to expand...
Click to collapse
it doesn't matter, it's a hardware issue.
I rehot BROADCOM ic - WiFi = NOT WORK
I have exactly the same problem. Wifi started to error here and there last September. Then started to get progressively worse in the winter. Then it finally crapped out in February. Just have to keep an eye on my data plan till I can get it fixed. If it is a hardware problem, would it still matter if I am unlocked?
After about two years of periodically tinkering with my G2. I'm at wits end.
I have tried every possible approach with downgrading, upgrading, using custom firmware but nothing I seem to do fixes the "Error" I get when trying to turn on the wifi. Bluetooth works fine, which leads me to believe that it's because the driver somehow got destroyed among the way way back.
I've attempted to do that *#*#5...blah blah blah, but it just cause right back to the dial pad and acts like nothing has happened.
If anyone knows of a solution, let me know. It's costing me a nice penny with a pre-paid data plan on it because it is unlocked from T-Mobile to AT&T. $15 within 2 hours.
I have searched countless forums and I've seen people have this issue but no one seems to really know of an answer.
That's either a hardware error or kernel error, try to flash las venturas kernel from reimer or flykernel
Las Venturas - No fix
Tried that kernel...no luck.
kemoba said:
That's either a hardware error or kernel error, try to flash las venturas kernel from reimer or flykernel
Click to expand...
Click to collapse
Tried both, no luck. However, now it immediately says error instead of trying to turn on then erroring out.
lifeinacoustic said:
Tried that kernel...no luck.
Click to expand...
Click to collapse
That's a hardware error then, it says error when it cant load the kernel module, if it cant load the module then probably your wifi chip is fried
I installed the Neutrino ROM (CM7) a few hours ago because I was extremely tired of dealing with the 2hr battery life I was getting from CM10.1 and kristianp's latest kernels. I'm not sure if the 38p radio was contributing to any problems or not.
I was perusing the settings; I tapped Add Account in Settings > Accounts, and my phone rebooted, after which it wouldn't go past the Moto logo and would display this message "Modem did not power up (0) Starting RSD protocol support"
I googled this, and it's a hardware problem with no way to fix it except warranty, which has expired. I can boot my phone using "Boot Android (No BP)", but this disables radio, so I cannot use my phone for communication purposes anymore. Except IM apps when I'm at home on WiFi.
Any ideas as to what I should do? I really don't think I can afford a new phone right now since I'm about to buy a laptop for school.
Ebay. $50-80.
Sent from my MB886 using xda app-developers app
txtsd said:
I installed the Neutrino ROM (CM7) a few hours ago because I was extremely tired of dealing with the 2hr battery life I was getting from CM10.1 and kristianp's latest kernels. I'm not sure if the 38p radio was contributing to any problems or not.
I was perusing the settings; I tapped Add Account in Settings > Accounts, and my phone rebooted, after which it wouldn't go past the Moto logo and would display this message "Modem did not power up (0) Starting RSD protocol support"
I googled this, and it's a hardware problem with no way to fix it except warranty, which has expired. I can boot my phone using "Boot Android (No BP)", but this disables radio, so I cannot use my phone for communication purposes anymore. Except IM apps when I'm at home on WiFi.
Any ideas as to what I should do? I really don't think I can afford a new phone right now since I'm about to buy a laptop for school.
Click to expand...
Click to collapse
I had that problem twice on my atrix and managed to boot modem again. I don't have exact solution but it was mix of booting in different modes, flashing radio, pulling battery for some time. If your modem just hang it should be possible to restart it.
krystianp said:
I had that problem twice on my atrix and managed to boot modem again. I don't have exact solution but it was mix of booting in different modes, flashing radio, pulling battery for some time. If your modem just hang it should be possible to restart it.
Click to expand...
Click to collapse
I tried flashing 38p over and over again, but it kept failing. I guess I can try booting in different modes and pulling the battery, if this has a chance of working.
txtsd said:
I tried flashing 38p over and over again, but it kept failing. I guess I can try booting in different modes and pulling the battery, if this has a chance of working.
Click to expand...
Click to collapse
I read about your storage problems. It looks like I had very similar experience. Both modem and storage started failing in the same time. To fix storage you can try flashing sbf. From what I read it rebuilds whole emmc. Another solution (that I used) was to rebuild and format partition in recovery. I have different recovery with proper support for vfat (default recovery has problems with it). If you are interested I can publish it.
I had some weird storage problems too, on two different devices, both running MROM-CM7. Both of them had a very hard time getting to 48 hours of uptime without at least one random reboot, and almost every time the reason (according to logs) was "mmcblk0: error -110 settings block erase XXX address" (XXX would be start or end) and some random sector, always different. (For what it's worth, "-110" means TIMEOUT.) After a lot of poking around, switching /data to ext3 instead of ext4 (and modifying the boot image/ramdisk accordingly) seems to have fixed it for me. No idea why ext4 would be so problematic but I'm happy for now.
krystianp said:
I read about your storage problems. It looks like I had very similar experience. Both modem and storage started failing in the same time. To fix storage you can try flashing sbf. From what I read it rebuilds whole emmc. Another solution (that I used) was to rebuild and format partition in recovery. I have different recovery with proper support for vfat (default recovery has problems with it). If you are interested I can publish it.
Click to expand...
Click to collapse
I tried booting different in different modes, pulled the battery for several minutes, and tried flashing radio to no avail. Still dead. I'm prepping to flash sbf right now. afaik vfat uses more space to store files than FAT32. Why would I want a recovery with vfat support?
EDIT: Is this the best way to flash SBF? I thought there might be a different method to go about it from CM10, but couldn't find any such methods.
ravilov said:
I had some weird storage problems too, on two different devices, both running MROM-CM7. Both of them had a very hard time getting to 48 hours of uptime without at least one random reboot, and almost every time the reason (according to logs) was "mmcblk0: error -110 settings block erase XXX address" (XXX would be start or end) and some random sector, always different. (For what it's worth, "-110" means TIMEOUT.) After a lot of poking around, switching /data to ext3 instead of ext4 (and modifying the boot image/ramdisk accordingly) seems to have fixed it for me. No idea why ext4 would be so problematic but I'm happy for now.
Click to expand...
Click to collapse
I mounted the internal SD via recovery earlier, and ran chkdsk on it in Windows. It claimed to have fixed several bad sectors, but it still didn't mount the drive after rebooting. I will try this ext3 trick too. Aren't all partitions ext3 by default anyway? Isn't that why there's an "upgrade partition to ext4" option in ROMracer's recovery?
txtsd said:
Aren't all partitions ext3 by default anyway?
Click to expand...
Click to collapse
On stock-based ROMs maybe, on CM7-based ROMs they are all ext4.
ravilov said:
On stock-based ROMs maybe, on CM7-based ROMs they are all ext4.
Click to expand...
Click to collapse
Oh. How would I go about converting them back to ext3 after flashing a CM ROM?
@KristianP @ravilov
So I flashed my phone with 1FF-olympus-user-2.3.6-4.5.1A-129_OLY-145-4-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf
and the radio and internal storage magically started to work again. The only problem I have now, which started just now, is my screen registering touches where I'm not touching it. It's really hard to type when every 3rd or 4th tap registers above the keyboard, thereby closing it.
Going to flash a fresh CM10.1 now.
Can you share the sbf download link? I just want to have a backup on my PC, in case I ever have it, I will not panic