Hello there and please excuse me for my bad english! As the title says, I can't connect to wifi network. Well, I can but it just work sometimes and works weird. Here's the scenario:
MIUI 3.6.7 rom on a Motorola Atrix 4G.
Android 4.1.2 JZO54K
Baseband N_01.77_38P
Kernel 2.6.32.60-MB860-CM10-ged7b511
On last sunday I tried to connect to a open wifi network, all week I was connecting to my home network. The status of wifi kept on "Turning on wifi..." for a while, but nothing happened. I restarted the phone and happened the same thing. At home, the connection worked but suddenly it closed for no reason. I tried to connect it again but kept again on the "Turning on wifi..." thing and suddenly the phone restarted! Not enough, it got stucked on the very first screen (the one with the "unlocked" text and Motorola logo), so I had to do a battery pull.
I've wiped Dalvik cache, cache partition, did some full wipes, installed again the rom (I was on 3.5.31 for then, updated yesterday to 3.6.7 and still the same), changed the Baseband, installed another kernel and I'm in the same situation. It's driving me crazy.
Got a logcat with Catlog, and found some (maybe interesting) lines (you can find the whole file in ge.tt/36KSn9j/v/0 -- sorry for be unable to post a link or uploading a file here):
06-11 15:21:54.508 W/CommandListener(1415): Failed to retrieve HW addr for eth0 (No such device)
06-11 15:21:54.508 D/CommandListener(1415): Setting iface cfg
06-11 15:21:54.508 E/WifiHW (1714): Unable to open connection to supplicant on "eth0": No such file or directory
06-11 15:21:54.508 I/wpa_supplicant(11001): rfkill: Cannot open RFKILL control device
06-11 15:21:54.508 E/wpa_supplicant(11001): Could not read interface eth0 flags: No such device
06-11 15:21:54.508 E/wpa_supplicant(11001): WEXT: Could not set interface 'eth0' UP
06-11 15:21:54.508 E/wpa_supplicant(11001): eth0: Failed to initialize driver interface
06-11 15:21:55.508 E/WifiHW (1714): Supplicant not running, cannot connect
06-11 15:21:59.508 E/WifiStateMachine(1714): Failed to setup control channel, restart supplicant
Googling about this got me to this thread (drakaz.com/forum/viewtopic.php?id=120... again sorry for the links thing) and got me thinking why the net interface is listened as 'eth0' and not 'wifi0' or something. I'm pretty noob to Android but I'm sort of an average GNU/Linux user, so I checked for what is going on in the dhcpcd.conf file and founded there the hostname was writed as 'wifi0' so I changed to 'eth0'... but this thing is still the same. Can you give me a clue about what the hell is going on? Thank you so much!
Make a nandroid backup and try a different ROM (preferrably a GB/CM7 based one).
ravilov said:
try a different ROM (preferrably a GB/CM7 based one).
Click to expand...
Click to collapse
Thank you so much for your answer! I tried CM7 (both stable and nightly, I heard the last one was a bit more stable than the first one) doing full wipe, of course. But when restarting, on both cases they only reached the very first screen (the one with the Motorola logo) and after like 5 seconds the phone rebooted automatically.
The thing is I really don't want to change MIUI. I've been using it since august, 2012 and I'm in love with it. This is the first time I got an issue so serious. Is there anything else I can do? Thank you so much!
No idea really. I'd tell you to do a full wipe before flashing but you've done that already. The only thing I can think of is flashing MROM (since its kernel has early USB enumeration) and then trying to pull out some more logcats very early on. This is quite a weird error and working out a solution will definitely involve a lot of creative thinking.
ravilov said:
No idea really. I'd tell you to do a full wipe before flashing but you've done that already. The only thing I can think of is flashing MROM (since its kernel has early USB enumeration) and then trying to pull out some more logcats very early on. This is quite a weird error and working out a solution will definitely involve a lot of creative thinking.
Click to expand...
Click to collapse
After the millionth full wipe I just got to install CM7 nightly and a clean reboot. But the wifi thing is still there... Well, a fc popup dialog appears after like 10 seconds: "Sorry! Application Settings (in process com.android.settings) is not responding.". I'm going to install MROM and catch a logcat, will be back then with a logcat. Thank you so much!
So I finally could get MROM working (I guess the thing about all GB roms rebooting when are just installed is about CWM). There's still the same thing I got with CM7. I have a logcat under MROM, and another I catched before I flased MROM (using MIUI v5): As I couldn't got MROM working just after wiping all when I was with CM7, I tried flashing MIUI. It flashed normally and at startup wifi was working, but after a while the connection closed suddenly. I got a logcat from that.
So the logcat with MIUI v5 (2013-06-14-02-26-28.txt) is here: ge.tt/6AQdiSj/v/0
And the logcat with MROM (2013-06-14-15-32-55.txt) is in ge.tt/7slxiSj/v/0
Hope this can help, I will keep pending so if you want to know something just let me know. Thank you so much for your help!
Seems that this is a problem about planned obsolescence. I'm such a noob, I hadn't seen this thread before (http://forum.xda-developers.com/showthread.php?t=1656760) where they explain many people had this issue. I can't post to that thread, but seems that they never got their wifi working again as I do sometimes. This is the weirdest s**t I've ever had with an electronic device.
Related
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.
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?
I think I've messed up again. Whenever I try to turn my wifi on, it gets stuck at the "turning on" status and then crashes after a couple of minutes. I have no error messages. It just closes after some time. The last thing I remember I did regarding wifi was to recover a stored password using Wifi Password Recovery App. Then this happened.
My phone is rooted and I have cwm. I've tried basic troubleshooting like power cycling, deleting wpa supplicant file (found in a post somewhere), tried turning wifi on using allsahare play, untweaking internet, but they just didn't work.
I'm ready to flash a stock ROM. But I'm just curious if you have any other suggestions before I do it because I've read some posts saying that reflashing didn't work as well.
Please help XDA Developers!
I guess no one has the solution yet. But I have discovered something, and I hope this would help. I found the file, init.qcom.wifi.sh, using root browser. I executed it and I got a script output stating an error. WI-FI chip ID is not specified. I have attached screenshots so you may as well check them out. Also, I noticed the files under date\misc\wifi are all 0.00 B which i think means they are empty. Please help experts.
theguynamedjake said:
I guess no one has the solution yet. But I have discovered something, and I hope this would help. I found the file, init.qcom.wifi.sh, using root browser. I executed it and I got a script output stating an error. WI-FI chip ID is not specified. I have attached screenshots so you may as well check them out. Also, I noticed the files under date\misc\wifi are all 0.00 B which i think means they are empty. Please help experts.
Click to expand...
Click to collapse
First of all you've got to flash any custom rom available in order to use wifi again !!!
Now regarding this issue u've just mentioned I'll try to investigate it further !!!
Thanks man. I flashed JASP ROM and its working fine now.
Didnt work
theguynamedjake said:
Thanks man. I flashed JASP ROM and its working fine now.
Click to expand...
Click to collapse
i tried all the above methods and even when on a full cleanrom install including the jasp rom but nothing has happened please help
Try reverting back to stock temporarely with Odin, this happens in my Note 3 and used to do the same in my S2, but only with the proximity sensor. The idea is the same, replace all settings to stock and flash whatever you want after (boot the stock though and test wifi just in case).
Why this works i have no idea, but it saved my arse loads of times. I can guess some internal devices might have flags configured which could be chip based rather then ROM/emmc related, but that is only my supposition.
Hi, I have this problem while switched between ROMs. But the problem hasn't been solved even if i switch back to the older ROM. The last active process of my WiFi was when i switched back to NEAT ROM. That too worked for a few seconds on the start of boots (even reboots). Then no sign of my WiFi turning on.
I had tried many fixes such as changing the kernel as the drivers are in kernel, using some WiFi fixing apps. But nothing helped.
It is clear from the logcat that i got during turning on my WiFi, that it says WiFi drivers not loaded.
Please suggest any ideas!
1. How to properly load WiFi drivers?
2. Where is the location of the WiFi drivers?
3. How are they installed?
Kernels devs could help me out possibly..
Error log:
" --------- beginning of /dev/log/system
--------- beginning of /dev/log/main
E/WifiStateMachine( 2235): Failed to load driver"
Hi all.
I'm running xboxexpert's 4.2.1 ROM with the UI MOD and clockworkmod recoverty 6.0.3.2. I keep wifi off generally for battery unless I need it. One day turning it on it gets stuck with the "Turning wi-fi on..." text but nothing happening.
I had wifi fixer installed to see logging at one point and it's help pointed to a possible know issue where this happens and said flashing is the only fix. OK fine I'll flash. Nope, same thing.
I've tried some of the other ROMS in the hisense forum but they've all failed. aosp's throw a warning that there's no file_contexts**, it fails to umount cache. Once it gets passed symlinking and metadata the applyparsedperms throws an error: operation not supported so the install is aborted. Do I need to load a different/newer recovery mod for these?
I've also tried the stock ROM and have the same issue w/wifi getting stuck when turning on.
Every time before I flash I'm formatting everything clockwork lets me: cache, data, system, modem, sdcard, dalvik. Each time I get it to boot, wifi is stuck.
I'm a bit of an android noob so speak in small sentences please.
Thanks.
TomBodet said:
Hi all.
I'm running xboxexpert's 4.2.1 ROM with the UI MOD and clockworkmod recoverty 6.0.3.2. I keep wifi off generally for battery unless I need it. One day turning it on it gets stuck with the "Turning wi-fi on..." text but nothing happening.
I had wifi fixer installed to see logging at one point and it's help pointed to a possible know issue where this happens and said flashing is the only fix. OK fine I'll flash. Nope, same thing.
I've tried some of the other ROMS in the hisense forum but they've all failed. aosp's throw a warning that there's no file_contexts**, it fails to umount cache. Once it gets passed symlinking and metadata the applyparsedperms throws an error: operation not supported so the install is aborted. Do I need to load a different/newer recovery mod for these?
I've also tried the stock ROM and have the same issue w/wifi getting stuck when turning on.
Every time before I flash I'm formatting everything clockwork lets me: cache, data, system, modem, sdcard, dalvik. Each time I get it to boot, wifi is stuck.
I'm a bit of an android noob so speak in small sentences please.
Thanks.
Click to expand...
Click to collapse
Look here for answers or post your question here:
http://forum.xda-developers.com/t/sero-7-pro
Evolution_Tech said:
Look here for answers or post your question here:
http://forum.xda-developers.com/t/sero-7-pro
Click to expand...
Click to collapse
Tried to post there. Site wouldn't let me due to low post count.
I also haven't found a thread that has helped me yet so I figured start one so I could get my hand held through fixing this or figuring out my wifi is busted at this point.
TomBodet said:
Tried to post there. Site wouldn't let me due to low post count.
I also haven't found a thread that has helped me yet so I figured start one so I could get my hand held through fixing this or figuring out my wifi is busted at this point.
Click to expand...
Click to collapse
My tablet had a similar problem and I gave up on it, I even sent it in for warranty worked for a couple of months then it went dead... well not exactly, it works perfectly at my work's wifi, other than that it's gone. Heck I even replaced the wifi antenna and not even with the hot spot underneath it it connects to it. That was almost a year and a half ago, since then it just sits there waiting to be thrown out the window...
David C.