Hi everyone,
I'm having a problem with my G1.
Each time i try to turn the Wi-Fi on, i follow this steps (spoil !!) :
- Settings -> Wireless controls -> and the i click on Wi-Fi,
wich changes the lower text to "Turning on..."
Ok, but this step take something like 1 minute and after all this time, i can read : "Unable to stop Wi-Fi" (or sometimes "Unable to start Wi-Fi"),
I got this problem 5 days ago, and this is really a pain in the arse, because the only way i can download applications is using Wi-Fi (I'm french) and i can't !
I have tried everything :
- Turn Off/On G1
- Remove/Replace battery
- Reset to factory data
- Back to RC29 (thx to you )
- Root my G1 with JF1.41 mod (Thx so much !!)
But the problem is still there,
And i can't get it back to T-Mobile, because i bought it on eBay and i live in France...
So... can anybody help ?
Thx
Hi,
Same problem here. Edit: It does this 4 times on 5. And even if if finally starts, it hangs some time after.
Additionally I've googled (almost) all night long to find some clues but nothing concrete
First, an issue is open here: http://code.google.com/p/android/issues/detail?id=1124
I get this line in logcat:
Code:
D/wlan_loader( 574): ConfigMge start rc = -1
that shows a problem. Normally it should be "rc = 0".
I've digged into the code but it is very complicated (state machine, etc...) so I could not figure where the problem resides.
I also have this in dmesg:
Code:
<4>[ 1425.145012] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 1425.145867] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
I don't know if this means a hardware problem.
I also suspect a bug in the proprietary file "/system/etc/wifi/Fw1251r1c.bin" but I've not found any other version on the net, even in "not so clean ways".
The size of the file on my G1 is 194188 bytes.
I have installed RC33 ADP1 by Jesus Freke but it did not solved the problem.
Can anyone look at the size of this file on his G1 and tell me if it is different? And if it is the case possibly send it to me?
The only solution I've seen on the net is to send back the phone to T-Mobile for a replacement but unfortunately I live in France and I got it from US by unusual ways so it is not a possibility for me .
Any clue / advice will be gladly accepted
Thanks in advance.
Mid'.
I have the same problem...
I was wondering if either of you figured out what to do to get around this. I'm in the US and am having the same problem. I was also working for about a week before this behavior started ("Unable to start Wi-Fi", "Unable to stop Wi-Fi").
I have seen other posts where this is intermittent. It isn't with me. Once it quit working, I haven't been able to get anything but the error messages.
If someone has found a way around this, I would appreciate any help you can provide.
Regards
Steve
You three should post what third party apps you have installed.
I am having this same issue after flashing the new google ION R2
I'm also having this issue after flashing Ion.
Same Issue
I started having this issue before the Ion rom. It wasn't intermittent, just stopped working.
Same problem here
Code:
<4>[ 1425.145012] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 1425.145867] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
CRB43, factory reset, nothing works.
Does anybody have an idea on how to solve this? It seems to be a known problem bij T-Mobile.
I'm running JF1.51 and WiFi is horribly flaky. It will work great for a few seconds then go deaf.
If I toggle it off and on it will work for a little bit again.
EDIT: I'm also getting the "low voltage" error message.
I've looked at this a little bit, and it looks like a ring buffer problem.
As I said before, my WiFi will work great for a while then go deaf.
Disabling/enabling through the Settings GUI will restore operation for a couple of minutes, tops.
Here's what I think might be relevant dmesgs:
Code:
<6>[88157.446136] request_suspend_state: sleep (0->3) at 88153591964926 (2009-06-27 20:57:10.146884034 UTC)
<4>[88157.467956] deinit sharp panel
<4>[88157.996398] select 4913 (app_process), adj 15, size 3053, to kill
<4>[88157.996734] send sigkill to 4913 (app_process), adj 15, size 3053
<4>[88158.236358] save exit: isCheckpointed 1
<6>[88282.505401] request_suspend_state: wakeup (3->0) at 88278651260580 (2009-06-27 20:59:15.206149170 UTC)
<6>[88282.615966] rev_crc_err_count 1, INT 23a001
<6>[88282.616332] rev: unknown reverse packet: len=0009 type=0049 CURR_REV_PTR=1617500b
<6>[88282.616851]
<6>[88282.617126] 09<6> 00<6> 49<6> 00<6> 00<6> 80<6> 00<6> 60<6> 00<6> 80<6> 0a<6>
<6>[88282.620574] mddi: resetting rev ptr
<6>[88282.621154] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val e curr_rev_ptr 1617500b
<4>[88282.666717] init sharp panel
<4>[88287.779876] select 4943 (app_process), adj 15, size 2991, to kill
<4>[88287.780731] send sigkill to 4943 (app_process), adj 15, size 2991
<4>[88295.748840] select 4951 (app_process), adj 15, size 2992, to kill
<4>[88295.749694] send sigkill to 4951 (app_process), adj 15, size 2992
<6>[88298.065185] TIWLAN: Driver unloading
<4>[88298.066314] sdio_reset_comm():
<7>[88298.154388] TIWLAN: Releasing SDIO resources
<7>[88298.158172] TIWLAN: SDIO resources released
<4>[88298.160217] wifi_remove
<4>[88298.160552] trout_wifi_set_carddetect: 0
<7>[88298.160827] mmc0: card_present 0
<6>[88298.161346] mmc0: Slot status change detected (1 -> 0)
<4>[88298.161712] trout_wifi_reset: 1
<6>[88298.172302] mmc0: card 0002 removed
<4>[88298.233215] trout_wifi_power: 0
<6>[88298.996520] TIWLAN: Driver unloaded
Here's a little more that I'm getting when the WiFi stops. Is this driver OSS or a proprietary blob?
Code:
<3>[ 1097.459899] init: untracked pid 364 exited
<4>[ 1101.746643] wds: 0020 @ 01
<6>[ 1101.747192] qmi: wds: got handle 0x17aaafb0
<4>[ 1101.747711] wds: 0022 @ ff
<6>[ 1101.748168] qmi: wds: CONNECTED
<4>[ 1101.750244] wds: 002d @ 01
<4>[ 1101.750701] qmi: got network profile
<6>[ 1101.752502] rmnet_open()
<6>[ 1685.105285] request_suspend_state: wakeup (3->0) at 1679298966064 (2009-06-27 21:55:33.740494873 UTC)
<6>[ 1685.217498] rev_crc_err_count 1, INT 23a001
<6>[ 1685.218078] rev: unknown reverse packet: len=0009 type=0049 CURR_REV_PTR=1617500b
<6>[ 1685.218383]
<6>[ 1685.218658] 09<6> 00<6> 49<6> 00<6> 00<6> 80<6> 00<6> 60<6> 00<6> 80<6> 0a<6>
<6>[ 1685.222137] mddi: resetting rev ptr
<6>[ 1685.222595] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val e curr_rev_ptr 1617500b
<4>[ 1685.288696] init sharp panel
<4>[ 1692.515502] wds: 0021 @ 01
<6>[ 1692.515838] qmi: wds: network stopped
<6>[ 1692.546508] rmnet_stop()
<4>[ 1693.342254] wds: 0022 @ ff
<6>[ 1693.342864] qmi: wds: DISCONNECTED
<6>[ 1704.187591] TIWLAN: Driver unloading
<4>[ 1704.188781] sdio_reset_comm():
<7>[ 1704.266632] TIWLAN: Releasing SDIO resources
<7>[ 1704.267944] TIWLAN: SDIO resources released
<4>[ 1704.270568] wifi_remove
<4>[ 1704.271057] trout_wifi_set_carddetect: 0
<7>[ 1704.272521] mmc0: card_present 0
<6>[ 1704.272979] mmc0: Slot status change detected (1 -> 0)
<6>[ 1704.276489] mmc0: card 0002 removed
<4>[ 1704.280487] trout_wifi_reset: 1
<4>[ 1704.332305] trout_wifi_power: 0
<6>[ 1704.543151] TIWLAN: Driver unloaded
<4>[ 1705.308166] wds: 0020 @ 01
<6>[ 1705.308715] qmi: wds: got handle 0x17aaafb0
<4>[ 1705.309234] wds: 0022 @ ff
<6>[ 1705.309661] qmi: wds: CONNECTED
<4>[ 1705.311370] wds: 002d @ 01
<4>[ 1705.311798] qmi: got network profile
<6>[ 1705.313690] rmnet_open()
<6>[ 1709.503326] TIWLAN: Driver loading
<4>[ 1709.504211] wifi_probe
<4>[ 1709.504486] trout_wifi_power: 1
<4>[ 1709.714965] trout_wifi_reset: 0
<4>[ 1709.766632] trout_wifi_set_carddetect: 1
<7>[ 1709.767303] mmc0: card_present 1
<6>[ 1709.767608] mmc0: Slot status change detected (0 -> 1)
<3>[ 1712.275085] mmc0: Command timeout
<4>[ 1712.282226] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 1712.283081] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
<6>[ 1712.290405] mmc0: new SDIO card at address 0001
<6>[ 1712.296447] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 1712.302520] TIWLAN: Driver initialized (rc 0)
<4>[ 1712.303436] TIWLAN: 1251 PG 1.2
<6>[ 1712.303863] TIWLAN: Driver loaded
<4>[ 1721.950164] wds: 0021 @ 01
<6>[ 1721.950500] qmi: wds: network stopped
<6>[ 1721.976440] rmnet_stop()
<4>[ 1726.546569] select 151 (app_process), adj 15, size 3009, to kill
<4>[ 1726.547149] select 158 (app_process), adj 15, size 3081, to kill
<4>[ 1726.547454] select 311 (app_process), adj 15, size 3246, to kill
<4>[ 1726.547973] send sigkill to 311 (app_process), adj 15, size 3246
<4>[ 1730.936798] wds: 0022 @ ff
<6>[ 1730.937652] qmi: wds: DISCONNECTED
I had the problem, i redid everything. just flashing the phone didn't help. downloaded the jf1.51 and did it again. logs would say wifi drivers not found. and guess what i checked and there were not there... I don't know 'who' or 'what' deleted them...
The only thing II suspect is the Backup program available on market for root users...or the "Privacy for rooted phones" prog
Same problem
Experiencing the same problem with my UK T-Mobile G1 (JF v1.51). Tried wiping, reseting, turning device off and on and removing battery, nothing has worked.
Is there any solution yet? I don't have any new apps installed and it is a fresh update, the problem was there prior to updating to jf v1.51
Any help will be appreciated
Did anyone manage to fix this? could it be related to the SDCard you are using?
Does everyone with non-working wifi on a G1 have this?
3 days ago, after I apply a chinese character sorting patch, i met this problem. So I wiped my phone, repartitioned my sdcard, reflashed the CM404 rom. And finnally got my wifi back.
But today I had this problem back again. I'm thinking is it because the sdcard I'm using is taking up to much battery power, so that the wifi module could not acquire enough power? This recalls me that I changed my sdcard exactly 3 days ago, right before I met this problem for the first time.
I am from India and G1 is very expensive over here. So, a friend bought me G1 from US and it reached in my hand yesterday . It is a T-Mobile G1. Was having same issue with Wifi and was showing "WiFi unable to start" . I tried rooting it and flashing with various ROM - issue remained. Lastly I downloaded a application from Market and installed. Named : WiFi Fixer by Zanshin-g1 .that software is written for completely different reason.
Code:
Does your wifi "hang" while still connected? Wifi Fixer keeps wifi working automatically, with optional wifi lock.
0.3.1 Cupcake, Disable function, warning if Wifi Notification is on
0.2.9 Added support for Landscape
*Wifi Fixer Classic also available*
But somehow it fixed my issue
Thanks Zanshin-g1.
bidhata said:
I am from India and G1 is very expensive over here. So, a friend bought me G1 from US and it reached in my hand yesterday . It is a T-Mobile G1. Was having same issue with Wifi and was showing "WiFi unable to start" . I tried rooting it and flashing with various ROM - issue remained. Lastly I downloaded a application from Market and installed. Named : WiFi Fixer by Zanshin-g1 .that software is written for completely different reason.
Code:
Does your wifi "hang" while still connected? Wifi Fixer keeps wifi working automatically, with optional wifi lock.
0.3.1 Cupcake, Disable function, warning if Wifi Notification is on
0.2.9 Added support for Landscape
*Wifi Fixer Classic also available*
But somehow it fixed my issue
Thanks Zanshin-g1.
Click to expand...
Click to collapse
Thanks Bidhata ,
but it tried that application and initially at first run it worked . but then once i got dc , the problem came back. since then i am not able to have the wifi truned on .
so the issue remains ..
Did you check the permission of this file: /data/misc/wifi/wpa_supplicant.conf
osoft said:
Did you check the permission of this file: /data/misc/wifi/wpa_supplicant.conf
Click to expand...
Click to collapse
This gave me the idea of how to fix, and its relativley simple... please correct me if I have made a grave error, but it seems to work so meh:
enter your terminal emulator and type the following:
su
(allow the request when asked)
chmod 777 /data/misc/wifi/wpa_supplicant.conf
exit the terminal
try powering up your wifi, it seems to be pretty stable as of now. This began occuring after I left my home's wireless range without turning wifi off and having the Wireless Helper app installed from the market...needless to say I have uninstalled said app and done this mod.
Whats funny about my situation is that if i use the DREAIMG.nbh file to flash back to rc29 my wifi works fine if i then upgrade to jf 1.5 still works fine upgrade to the latest cyanogen stable still works fine. Then a couple of days later poof "Unable to start wifi" intermittently and then a few days later permanently. Even if i downgrade to jf again still no wifi until i re-flash rc29 again. Weird thing is before i downgrade to jf 1.5 i run a fastboot erase on all the pertinent partitions. The only one that doesn't get flashed or erased in the downgrade to 1.5 is the radio rom. This leads me to believe that either my hardware is on it's way out or something that gets set in the radio rom from cyanogen 4.0.4 gets carried over no matter what rom you flash until the radio is erased and re-flashed. Mind you the second one is a totally just a guess with no proof to back it up. I also tried to chmod 777 /data/misc/wifi/wpa_supplicant.conf like said in the last post but to no avail.
Related
Hi,
I have tested all possible ROMS (Beast, Utopian, NI, CyanogemMod, EdenX,...) and I encounter the same problem: the interface goes in Error after some time. When I flash and start using it, it's woking fine, but after some time (counted in minutes, not in days), network is down and in the Network settings panel, I get the message "error". Sometimes the interface comes back up, but at some point, it stays in error and in logcat I have
E/WifiService( 1242): Failed to load Wi-Fi driver.
Dmesg gives:
Code:
[<4>[ 1190.039532] Dongle Host Driver, version 4.218.223.1
<4>[ 1198.044261] __ratelimit: 17 callbacks suppressed
<4>[ 1198.048915] dhd_module_init: sdio_register_driver timeout
I also see other errors in the dmesg output:
Code:
<4>[ 1180.754089] dhdsdio_dpc: FAILEDnewstatusREAD, LINE 4092
<4>[ 1180.836536] dhdsdio_dpc: failed backplane access over SDIO, halting operation 1
<4>[ 1180.844034] dhdsdio_dpc: failed backplane access over SDIO, halting operation 1
<4>[ 1180.851469] dhdcdc_query_ioctl: dhdcdc_msg failed w/status -5
<4>[ 1180.871027] dhd_ioctl_entry DONGLE_DOWN,__FUNCTION__
<4>[ 1180.954228] dhd_start_xmit: xmit rejected pub.up=1 busstate=0
<4>[ 1180.960068] dhd_start_xmit: Event RELOAD send up
<4>[ 1180.964706] BUG wlan0 code -19 qlen 0
<4>[ 1186.978451] dhd_ioctl_entry DONGLE_DOWN,__FUNCTION__
<4>[ 1190.019110] bcmsdh_sdmmc: probe of mmc0:0001:1 failed with error -5
I attached logcat and dmesg files.
Before I send my unit to repair, anyone having seen the same problem? Is this really a hardware problem, and if yes, how comes it works fine for some time before breaking?
I've just seen in the dmesg that there are badblocks on mtdblock4. Could that be the reason?
Code:
<4>[ 35.143702] yaffs: Attempting MTD mount on 31.4, "mtdblock4"
<6>[ 35.163593] tegra_nand tegra_nand: Block 0x92d is bad [chip=0,offset=0x125a0000]
<3>[ 35.170984] tegra_nand tegra_nand: Reading OOB data of bad block
I hope someone can help me as I'd rather not send my adam back for repair!
Thanks
Raph
Try the unbricking procedure (not sure it will actually help though). A fresh flash with NVFlash might get you up and running again though the bad sectors do concern me.
Because i can not post in the Dev section i try it here.
On the new Utopia RC4 ROM the Wlan can not be activated, it just say's scanning is not possible an then it gets deactivated.
Sirius1977 said:
Because i can not post in the Dev section i try it here.
On the new Utopia RC4 ROM the Wlan can not be activated, it just say's scanning is not possible an then it gets deactivated.
Click to expand...
Click to collapse
Try reflashing because its supposed
to be working!!
Nope, didn't work. Tried to flash again via fastboot and at the second try i made a recovery version which also didn't make the wifi work.
Same message: Networkscan is not possible
dmesg output:
Code:
<4>[ 560.902218] register_mmc_card_pm: [WiFi] Callbacks registered successfully.
<3>[ 560.902608] [yoohoo] dhd_register_hwakeup : start
<3>[ 560.902848] [dhd_hostwakeup_isr] HostWakeup Get GPIO 94: 1
<3>[ 560.903240] [yoohoo] dhd_register_hwakeup : OK
<4>[ 560.903445] [yoohoo] dhd_enable_hwakeup : succeed irq 158
<3>[ 560.903810] [dhd_register_early_suspend] HostWakeup Get GPIO 94: 1
<4>[ 560.904012]
<4>[ 560.904017] Dongle Host Driver, version 4.217.91.0
<4>[ 561.104080] =========== WLAN going back to live ========
<6>[ 561.104328] mmc1: Slot status change detected (0 -> 1)
<3>[ 561.104886] (swift_sdcc_setup_power)vdd :12
<3>[ 561.107221] (swift_sdcc_setup_power)vdd :12
<3>[ 561.109586] (swift_sdcc_setup_power)vdd :12
<3>[ 561.112228] (swift_sdcc_setup_power)vdd :12
<3>[ 561.120059] (swift_sdcc_setup_power)vdd :12
<3>[ 561.121993] (swift_sdcc_setup_power)vdd :12
<7>[ 561.183765] mmc1: queuing CIS tuple 0x80 length 51
<7>[ 561.191050] mmc1: queuing CIS tuple 0x80 length 7
<7>[ 561.194554] mmc1: queuing CIS tuple 0x80 length 2
<7>[ 561.204207] mmc1: queuing CIS tuple 0x80 length 10
<7>[ 561.206143] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.207915] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.209852] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.211637] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.213400] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.215332] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.217095] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.219025] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.220790] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.222560] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.224492] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.227047] mmc1: queuing CIS tuple 0x02 length 1
<3>[ 561.228268] (swift_sdcc_setup_power)vdd :12
<3>[ 561.228515] (swift_sdcc_setup_power)vdd :12
<6>[ 561.231190] mmc1: new SDIO card at address 0001
<4>[ 561.236461] mem_prealloc: section [3] size[139264]
<4>[ 561.236671] mem_prealloc: This data is using!!!
<4>[ 561.237255] alloc static buf at cccc0000!
<4>[ 561.237451] mem_prealloc: section [4] size[0]
<4>[ 561.239636] DHD: dongle ram size is set to 393216(orig 393216)
<4>[ 561.240125] mem_prealloc: section [0] size[10312]
<4>[ 561.240371] mem_prealloc: This data is using!!!
<4>[ 561.241366] mem_prealloc: section [1] size[10300]
<4>[ 561.241623] mem_prealloc: This data is using!!!
<4>[ 561.241890] mem_prealloc: section [2] size[32768]
<4>[ 561.242338] mem_prealloc: This data is using!!!
<6>[ 561.765387] wlan0 (): not using net_device_ops yet
<4>[ 561.770128] wlan0: Broadcom Dongle Host Driver mac=00:26:e8:af:0b:bb
<4>[ 563.957310] wlan0: non-BDC packet received, flags 0x10
<3>[ 578.949398] init: untracked pid 2131 exited
<4>[ 579.974021] unregister_mmc_card_pm: [WIFI] Unregistering suspend/resume callbacks.
<4>[ 580.243393] =========== WLAN placed in RESET ========
<6>[ 580.243909] mmc1: Slot status change detected (1 -> 0)
<6>[ 580.258381] mmc1: card 0001 removed
<3>[ 580.260527] (swift_sdcc_setup_power)vdd :0
#
Hmm... also the MAC adress didn't appear the Advanced Wifi settings.
For now i'm back to RC3 and ... wifi works
It is my mistake!
Try this fix!
Hmm... simply cut & paste didn't work. How can i apply the fix?
Sirius1977 said:
Hmm... simply cut & paste didn't work. How can i apply the fix?
Click to expand...
Click to collapse
install with recovery
No chance to install in CWM
Always getting Error on applying (Status 6)
Sirius1977 said:
No chance to install in CWM
Always getting Error on applying (Status 6)
Click to expand...
Click to collapse
last fix was broken? download fix again.
Error (Status 6) again
I try to set the permissions for the .so manually
Ok... I got it
adb shell
cd /system/lib
chmod 06755 libhardware_legacy.so
exit
dont't forget to mount the system partition as r/w in root explorer
Thanks to all for the fast response.
Great ROM
Ok that was to fast.
Wifi is on and it can scan for AP's but it can't connect.
Sirius1977 said:
Ok that was to fast.
Wifi is on and it can scan for AP's but it can't connect.
Click to expand...
Click to collapse
Does your router work?
Sent from my GT540 using XDA App
Yes, meanwhile the problem was confirmed by others.
No wifi........MIROSLAV_MM where are you;-)
Edit-Forgot to add 'I love your work'
Sent from my GT540 using xda premium
sanmit said:
No wifi........MIROSLAV_MM where are you;-)
Edit-Forgot to add 'I love your work'
Sent from my GT540 using xda premium
Click to expand...
Click to collapse
RC4 has been withdrawn due to this wifi issue.
Sent from my GT540 using xda premium
I've been playing about with the EOS build of ICS for the Xoom MZ604, and seem to have a unique problem. The wireless constantly drops, every few minutes or so. It was installed after a full wipe of stock (factory reset and cache format with CWM), firstly with revision 30 which dropped every 5 mins or so, and then with 32 (again, full wipe prior to install), which drops every minute or so.
I noticed this when running dmesg:
Code:
<4>[ 3937.928526] ------------[ cut here ]------------
<4>[ 3937.928716] WARNING: at net/wireless/scan.c:403 cfg80211_bss_update+0x24/0x384()
<4>[ 3937.928805] Modules linked in:
<4>[ 3937.929063] [<c0042e64>] (unwind_backtrace+0x0/0xf0) from [<c007070c>] (warn_slowpath_common+0x4c/0x64)
<4>[ 3937.929231] [<c007070c>] (warn_slowpath_common+0x4c/0x64) from [<c007073c>] (warn_slowpath_null+0x18/0x1c)
<4>[ 3937.929329] [<c007073c>] (warn_slowpath_null+0x18/0x1c) from [<c0460a78>] (cfg80211_bss_update+0x24/0x384)
<4>[ 3937.929499] [<c0460a78>] (cfg80211_bss_update+0x24/0x384) from [<c0460f70>] (cfg80211_inform_bss_frame+0x198/0x1d0)
<4>[ 3937.929673] [<c0460f70>] (cfg80211_inform_bss_frame+0x198/0x1d0) from [<c02851b8>] (wl_inform_single_bss+0x2c0/0x34c)
<4>[ 3937.929844] [<c02851b8>] (wl_inform_single_bss+0x2c0/0x34c) from [<c0285520>] (wl_inform_bss+0x44/0xa8)
<4>[ 3937.930011] [<c0285520>] (wl_inform_bss+0x44/0xa8) from [<c0285bf0>] (wl_escan_handler+0x394/0x4cc)
<4>[ 3937.930176] [<c0285bf0>] (wl_escan_handler+0x394/0x4cc) from [<c0284b48>] (wl_event_handler+0xac/0x17c)
<4>[ 3937.930350] [<c0284b48>] (wl_event_handler+0xac/0x17c) from [<c003e5d8>] (kernel_thread_exit+0x0/0x8)
<4>[ 3937.930442] ---[ end trace 1b75b31a2719eeee ]---
<3>[ 3937.930602] CFG80211-ERROR) wl_inform_single_bss : cfg80211_inform_bss_frame error
<4>[ 3943.236683] ------------[ cut here ]------------
<4>[ 3943.237118] WARNING: at net/wireless/scan.c:403 cfg80211_bss_update+0x24/0x384()
<4>[ 3943.237760] Modules linked in:
<4>[ 3943.238488] [<c0042e64>] (unwind_backtrace+0x0/0xf0) from [<c007070c>] (warn_slowpath_common+0x4c/0x64)
<4>[ 3943.239169] [<c007070c>] (warn_slowpath_common+0x4c/0x64) from [<c007073c>] (warn_slowpath_null+0x18/0x1c)
<4>[ 3943.239853] [<c007073c>] (warn_slowpath_null+0x18/0x1c) from [<c0460a78>] (cfg80211_bss_update+0x24/0x384)
<4>[ 3943.240252] [<c0460a78>] (cfg80211_bss_update+0x24/0x384) from [<c0460f70>] (cfg80211_inform_bss_frame+0x198/0x1d0)
<4>[ 3943.240940] [<c0460f70>] (cfg80211_inform_bss_frame+0x198/0x1d0) from [<c02851b8>] (wl_inform_single_bss+0x2c0/0x34c)
<4>[ 3943.241621] [<c02851b8>] (wl_inform_single_bss+0x2c0/0x34c) from [<c0285520>] (wl_inform_bss+0x44/0xa8)
<4>[ 3943.242304] [<c0285520>] (wl_inform_bss+0x44/0xa8) from [<c0285bf0>] (wl_escan_handler+0x394/0x4cc)
<4>[ 3943.242975] [<c0285bf0>] (wl_escan_handler+0x394/0x4cc) from [<c0284b48>] (wl_event_handler+0xac/0x17c)
<4>[ 3943.243670] [<c0284b48>] (wl_event_handler+0xac/0x17c) from [<c003e5d8>] (kernel_thread_exit+0x0/0x8)
<4>[ 3943.244326] ---[ end trace 1b75b31a2719eeef ]---
<3>[ 3943.244684] CFG80211-ERROR) wl_inform_single_bss : cfg80211_inform_bss_frame error
<4>[ 3943.278521] wl_bss_connect_done succeeded status=(0x9)
<6>[ 3943.328742] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
<4>[ 3943.336519] wlan0: set promisc 0 failed
<4>[ 3943.348994] wlan0: set promisc 0 failed
<4>[ 3943.354353] wl_bss_connect_done succeeded status=(0x11)
Not sure if this is what is needed to debug it, if not tell me what is needed. Any ideas why I'm getting this? I've had a bit of a search, but I can't see anything relevant on XDA or via Google. Under stock, never had an issue with wireless. And I do appreciate that EOS is very much beta at the moment.
VaKo said:
I've been playing about with the EOS build of ICS for the Xoom MZ604, and seem to have a unique problem. The wireless constantly drops, every few minutes or so. It was installed after a full wipe of stock (factory reset and cache format with CWM), firstly with revision 30 which dropped every 5 mins or so, and then with 32 (again, full wipe prior to install), which drops every minute or so.
I noticed this when running dmesg:
Code:
<4>[ 3937.928526] ------------[ cut here ]------------
<4>[ 3937.928716] WARNING: at net/wireless/scan.c:403 cfg80211_bss_update+0x24/0x384()
<4>[ 3937.928805] Modules linked in:
<4>[ 3937.929063] [<c0042e64>] (unwind_backtrace+0x0/0xf0) from [<c007070c>] (warn_slowpath_common+0x4c/0x64)
<4>[ 3937.929231] [<c007070c>] (warn_slowpath_common+0x4c/0x64) from [<c007073c>] (warn_slowpath_null+0x18/0x1c)
<4>[ 3937.929329] [<c007073c>] (warn_slowpath_null+0x18/0x1c) from [<c0460a78>] (cfg80211_bss_update+0x24/0x384)
<4>[ 3937.929499] [<c0460a78>] (cfg80211_bss_update+0x24/0x384) from [<c0460f70>] (cfg80211_inform_bss_frame+0x198/0x1d0)
<4>[ 3937.929673] [<c0460f70>] (cfg80211_inform_bss_frame+0x198/0x1d0) from [<c02851b8>] (wl_inform_single_bss+0x2c0/0x34c)
<4>[ 3937.929844] [<c02851b8>] (wl_inform_single_bss+0x2c0/0x34c) from [<c0285520>] (wl_inform_bss+0x44/0xa8)
<4>[ 3937.930011] [<c0285520>] (wl_inform_bss+0x44/0xa8) from [<c0285bf0>] (wl_escan_handler+0x394/0x4cc)
<4>[ 3937.930176] [<c0285bf0>] (wl_escan_handler+0x394/0x4cc) from [<c0284b48>] (wl_event_handler+0xac/0x17c)
<4>[ 3937.930350] [<c0284b48>] (wl_event_handler+0xac/0x17c) from [<c003e5d8>] (kernel_thread_exit+0x0/0x8)
<4>[ 3937.930442] ---[ end trace 1b75b31a2719eeee ]---
<3>[ 3937.930602] CFG80211-ERROR) wl_inform_single_bss : cfg80211_inform_bss_frame error
<4>[ 3943.236683] ------------[ cut here ]------------
<4>[ 3943.237118] WARNING: at net/wireless/scan.c:403 cfg80211_bss_update+0x24/0x384()
<4>[ 3943.237760] Modules linked in:
<4>[ 3943.238488] [<c0042e64>] (unwind_backtrace+0x0/0xf0) from [<c007070c>] (warn_slowpath_common+0x4c/0x64)
<4>[ 3943.239169] [<c007070c>] (warn_slowpath_common+0x4c/0x64) from [<c007073c>] (warn_slowpath_null+0x18/0x1c)
<4>[ 3943.239853] [<c007073c>] (warn_slowpath_null+0x18/0x1c) from [<c0460a78>] (cfg80211_bss_update+0x24/0x384)
<4>[ 3943.240252] [<c0460a78>] (cfg80211_bss_update+0x24/0x384) from [<c0460f70>] (cfg80211_inform_bss_frame+0x198/0x1d0)
<4>[ 3943.240940] [<c0460f70>] (cfg80211_inform_bss_frame+0x198/0x1d0) from [<c02851b8>] (wl_inform_single_bss+0x2c0/0x34c)
<4>[ 3943.241621] [<c02851b8>] (wl_inform_single_bss+0x2c0/0x34c) from [<c0285520>] (wl_inform_bss+0x44/0xa8)
<4>[ 3943.242304] [<c0285520>] (wl_inform_bss+0x44/0xa8) from [<c0285bf0>] (wl_escan_handler+0x394/0x4cc)
<4>[ 3943.242975] [<c0285bf0>] (wl_escan_handler+0x394/0x4cc) from [<c0284b48>] (wl_event_handler+0xac/0x17c)
<4>[ 3943.243670] [<c0284b48>] (wl_event_handler+0xac/0x17c) from [<c003e5d8>] (kernel_thread_exit+0x0/0x8)
<4>[ 3943.244326] ---[ end trace 1b75b31a2719eeef ]---
<3>[ 3943.244684] CFG80211-ERROR) wl_inform_single_bss : cfg80211_inform_bss_frame error
<4>[ 3943.278521] wl_bss_connect_done succeeded status=(0x9)
<6>[ 3943.328742] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
<4>[ 3943.336519] wlan0: set promisc 0 failed
<4>[ 3943.348994] wlan0: set promisc 0 failed
<4>[ 3943.354353] wl_bss_connect_done succeeded status=(0x11)
Not sure if this is what is needed to debug it, if not tell me what is needed. Any ideas why I'm getting this? I've had a bit of a search, but I can't see anything relevant on XDA or via Google. Under stock, never had an issue with wireless. And I do appreciate that EOS is very much beta at the moment.
Click to expand...
Click to collapse
You have more than enough posts, why not post this on EOS dev thread? Or on the bug reporting site?
My MZ604 running the EOS 32 ROM refused to connect to a wifi network earlier. I went into the wifi settings to select the network and it said something about it avoiding the low signal or whatever (I don't remember exactly what it said) even though that network's signal was excellent. It was when it tried to connect to it that it showed the signal as being poor to nonexistent. I'm connected to my home network fine but I hope that issue doesn't repeat itself on a regular basis.
|Sent with XDA Premium via my X°°M ΔKΔ the antithesis to the iPad|
I haven't had any issues with wifi on 29, 30, 31, or 32.
Did you by chance try a different access point or reset router? Just wondering sometimes the simple things cause the issues.
okantomi said:
You have more than enough posts, why not post this on EOS dev thread? Or on the bug reporting site?
Click to expand...
Click to collapse
Because I'm not entirely sure it is a bug with EOS. I'm running the same hardware and software build as many other people, yet seem to be the only one with this problem. And I don't think "my wireless is unstable" is good enough to log a bug report without additional details, which I don't know how to obtain.
jaekidd1012 said:
My MZ604 running the EOS 32 ROM refused to connect to a wifi network earlier. I went into the wifi settings to select the network and it said something about it avoiding the low signal or whatever (I don't remember exactly what it said) even though that network's signal was excellent. It was when it tried to connect to it that it showed the signal as being poor to nonexistent. I'm connected to my home network fine but I hope that issue doesn't repeat itself on a regular basis.
Click to expand...
Click to collapse
chasehq11 said:
I haven't had any issues with wifi on 29, 30, 31, or 32.
Did you by chance try a different access point or reset router? Just wondering sometimes the simple things cause the issues.
Click to expand...
Click to collapse
I get the same issue with different AP's, and the when it drops the scan can't pickup any of the AP's near me.
VaKo said:
Because I'm not entirely sure it is a bug with EOS. I'm running the same hardware and software build as many other people, yet seem to be the only one with this problem. And I don't think "my wireless is unstable" is good enough to log a bug report without additional details, which I don't know how to obtain.
I get the same issue with different AP's, and the when it drops the scan can't pickup any of the AP's near me.
Click to expand...
Click to collapse
Create a bug report for it.
It looks like the wifi driver is crashing for some reason.
If you could log the issue at https://bugs.teameos.org and provide a description of what security your access point has, if it has any special characters in the name etc.
Please also attach outputs from dmesg and logcat.
http://bugs.teameos.org/show_bug.cgi?id=37
Thanks mate. If you need any more details then tell me.
Hi,
I bought a second hand i9505, which i used for several days with the standard Samsung stuff.
After a few day's i installed CM11, but after a day my wifi stopped working.
Then i started googling, found several other treads with the same problem, tried those solutions.
But at the this point none of them worked for me.
Things that i tried:
-Different modems
-Stock Samsung rom
-Factory reset
-Format /system , and reflash stock rom with Odin
-Pull the battery out for 30mins
-Reconnected the Wifi antenna
-Deleted the WPA_Supplicant file
-Disable the powersaving mode under *#0011#
Al of them did not work for me.
Is there anybody who has an idea?
Thanks in advance!
sven93 said:
Hi,
I bought a second hand i9505, which i used for several days with the standard Samsung stuff.
After a few day's i installed CM11, but after a day my wifi stopped working.
Then i started googling, found several other treads with the same problem, tried those solutions.
But at the this point none of them worked for me.
Things that i tried:
-Different modems
-Stock Samsung rom
-Factory reset
-Format /system , and reflash stock rom with Odin
-Pull the battery out for 30mins
-Reconnected the Wifi antenna
-Deleted the WPA_Supplicant file
-Disable the powersaving mode under *#0011#
Al of them did not work for me.
Is there anybody who has an idea?
Thanks in advance!
Click to expand...
Click to collapse
Hi,
Maybe is hardware related did you check if the WIFI Antenna Signal Flex Cable is well connected?
https://www.ifixit.com/Teardown/Samsung+Galaxy+S4+Teardown/13947
MAX 404 said:
Hi,
Maybe is hardware related did you check if the WIFI Antenna Signal Flex Cable is well connected?
Click to expand...
Click to collapse
Thanks, but i already tried this.
Reconnected both connections, and made sure both were aligned flat on the connector.
Unfortunately without any result.
sven93 said:
Thanks, but i already tried this.
Reconnected both connections, and made sure both were aligned flat on the connector.
Unfortunately without any result.
Click to expand...
Click to collapse
Maybe is the chip....can you scan , do you see wifi networks or did you try the option wifi direct , between your phone and another unit?
MAX 404 said:
Maybe is the chip....can you scan , do you see wifi networks or did you try the option wifi direct , between your phone and another unit?
Click to expand...
Click to collapse
Well, lets hope its not the chip.
I can't turn on the wifi, if i tap the wifi button (either in settings or at the notifications area) it goes green for 0.5 sec and goes to grey right after.
Haven't tried wifi-direct as i don't have any compatible devices.
Just tried to turn on the tether service, there is states "Error" when i try to turn it on.
Is there any logfile that i can use to determine the cause?
sven93 said:
Well, lets hope its not the chip.
I can't turn on the wifi, if i tap the wifi button (either in settings or at the notifications area) it goes green for 0.5 sec and goes to grey right after.
Haven't tried wifi-direct as i don't have any compatible devices.
Just tried to turn on the tether service, there is states "Error" when i try to turn it on.
Is there any logfile that i can use to determine the cause?
Click to expand...
Click to collapse
Not sure about the log file ...
Here i found a thread , it talks about a solution but they use a SPT box, for what i see the problem is efs related, do you have an EFS backup?
http://forum.gsmhosting.com/vbb/f45...nlock-default-efs-imei-solution-here-1788263/
Nope, unfortunately i didn't backup the EFS folder.
Flashed my S2 a thousand times, with backup, never happened anything. I flash my S4 1 time without,...
Compared the content with the S2, and for me is looks like everything needed is still there. (not an expert though)
Any other ideas?
sven93 said:
Nope, unfortunately i didn't backup the EFS folder.
Flashed my S2 a thousand times, with backup, never happened anything. I flash my S4 1 time without,...
Compared the content with the S2, and for me is looks like everything needed is still there. (not an expert though)
Any other ideas?
Click to expand...
Click to collapse
1. Dial *#1234# in Stock Rom and check if your Csc is correct.
2. Reflash 2 times the stock rom.
Joku1981 said:
1. Dial *#1234# in Stock Rom and check if your Csc is correct.
2. Reflash 2 times the stock rom.
Click to expand...
Click to collapse
CSC Seems to match.
Tried flashing it 3 times in a row with the same (stock) ROM, still nothing.
sven93 said:
Hi,
I bought a second hand i9505, which i used for several days with the standard Samsung stuff.
After a few day's i installed CM11, but after a day my wifi stopped working.
Then i started googling, found several other treads with the same problem, tried those solutions.
But at the this point none of them worked for me.
Things that i tried:
-Different modems
-Stock Samsung rom
-Factory reset
-Format /system , and reflash stock rom with Odin
-Pull the battery out for 30mins
-Reconnected the Wifi antenna
-Deleted the WPA_Supplicant file
-Disable the powersaving mode under *#0011#
Al of them did not work for me.
Is there anybody who has an idea?
Thanks in advance!
Click to expand...
Click to collapse
I have the same problem. Wifi won't turn on no matter what I do. I was on cm-11-20140627-NIGHTLY-jflte and then decided to upgrade to cm-11-20140908-NIGHTLY-jflte. With that upgrade I lost wifi. I tried every possible thing that I found on forums and nothing helped. I also tried to upgrade to latest stock. I was on old bootloader until then, now I have the KNOX sh...t.
I have a feeling that something is wrong with wifi firmware. Is there a way to somehow check or reflash wifi firmware only?
regards.
ajax505 said:
I have the same problem. Wifi won't turn on no matter what I do. I was on cm-11-20140627-NIGHTLY-jflte and then decided to upgrade to cm-11-20140908-NIGHTLY-jflte. With that upgrade I lost wifi. I tried every possible thing that I found on forums and nothing helped. I also tried to upgrade to latest stock. I was on old bootloader until then, now I have the KNOX sh...t.
I have a feeling that something is wrong with wifi firmware. Is there a way to somehow check or reflash wifi firmware only?
regards.
Click to expand...
Click to collapse
Sad to hear you have the same.
Pretty strange, i haven't used the S4 since Wednesday, but the phone was still turned on, ten minutes ago i wanted to check something, turns out wifi is working again, until i decided to reboot, now its doing the same as before...
It does indeed smells software/firmware related.
Just made a dumpfile of the logs (bugreport > /mnt/sdcard/dump.txt) , and saw some interesting stuff in the kernel log:
<4>[ 9.717163] failed to power up wifi chip, retry again (5 left) **
<4>[ 9.717163]
<4>[ 9.733306] ## wifi_remove
<4>[ 9.733612] wifi_set_power = 1
<4>[ 9.733612] WiFi: trying to acquire BT lock
<4>[ 9.733612] ####btlock acquired cookie: WiFi
<4>[ 9.733642] wifi_set_power: btlock acquired
<6>[ 9.733642] ------------------------------------------------
<6>[ 9.733642] ------------------------------------------------
<6>[ 9.733642] brcm_wlan_power Enter: power on
<3>[ 9.733642] brcm_wlan_power: WL_REG_ON failed to pull up
<4>[ 9.733734] wifi_probe: set_power failed. err=-5
<4>[ 9.733734] wifi_set_power = 0
<4>[ 9.733734] ####btlock released, cookie: WiFi
<6>[ 9.733734] ------------------------------------------------
<6>[ 9.733795] ------------------------------------------------
<6>[ 9.733825] brcm_wlan_power Enter: power off
<3>[ 9.733825] brcm_wlan_power: WL_REG_ON failed to pull down
Click to expand...
Click to collapse
Then after a bit:
<4>[ 11.727294]
<4>[ 11.727294] failed to power up wifi chip, retry again (4 left) **
<4>[ 11.727294]
<4>[ 11.743499] ## wifi_remove
<4>[ 11.743835] wifi_set_power = 1
<4>[ 11.743835] WiFi: trying to acquire BT lock
<4>[ 11.743835] ####btlock acquired cookie: WiFi
<4>[ 11.743835] wifi_set_power: btlock acquired
<6>[ 11.743835] ------------------------------------------------
<6>[ 11.743865] ------------------------------------------------
<6>[ 11.743865] brcm_wlan_power Enter: power on
<6>[ 11.743865] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 1
<6>[ 11.754608] [email protected]: Start PackageManagerService
<6>[ 11.775604] [SSP] Updated 73599 bytes / 139282 bytes
<4>[ 11.977172] wifi_set_carddetect = 1
<4>[ 11.977172] brcm_wifi_status:267 status 1
Click to expand...
Click to collapse
For people who want to view the log: https://dl.dropboxusercontent.com/u/15503253/dumpfile.txt
I also get those kind of messages in my system logs:
<4>[ 1837.921936] failed to power up wifi chip, retry again (1 left) **
<4>[ 1837.921966]
<4>[ 1837.941497] ## wifi_remove
<4>[ 1837.941497] wifi_set_power = 0
<4>[ 1837.941528] ####btlock released, cookie: WiFi
<6>[ 1837.941558] ------------------------------------------------
<6>[ 1837.941558] ------------------------------------------------
<6>[ 1837.941589] brcm_wlan_power Enter: power off
<6>[ 1837.941619] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 0
<4>[ 1838.182006] wifi_set_carddetect = 0
<4>[ 1838.182037] brcm_wifi_status:267 status 0
<6>[ 1838.182067] mmc1: Slot status change detected (1 -> 0)
<4>[ 1838.187591]
<4>[ 1838.187622] failed to power up wifi chip, max retry reached, exits **
Click to expand...
Click to collapse
I also get a lot of "mmc1: Data CRC error":
<3>[ 1826.574645] mmc1: Data CRC error
<3>[ 1826.577178] msmsdcc_data_err: opcode 0x00000035
<3>[ 1826.581542] msmsdcc_data_err: blksz 4, blocks 1
<6>[ 1826.586883] sps:BAM 0x12182000 enabled: ver:0x5, number of pipes:6dhd_detach(): thread:dhd_sysioc:392 terminated OK
<4>[ 1826.651245] dhd_detach(): thread:dhd_watchdog_thread:38f terminated OK
<4>[ 1826.651336] dhd_dpc_thread: Unexpected up_cnt 0
<4>[ 1826.651428] dhd_detach(): thread:dhd_dpc:390 terminated OK
<4>[ 1826.651733] dhd_detach(): thread:dhd_rxf:391 terminated OK
<6>[ 1826.670593] CFG80211-INFO2) wl_event_handler : was terminated
<4>[ 1826.670898] wl_destroy_event_handler(): thread:wl_event_handler:38e terminated OK
<4>[ 1826.682250] dhdsdio_disconnect : the lock is released.
<4>[ 1826.683807] ## wifi_remove
<4>[ 1826.683837] wifi_set_power = 0
<4>[ 1826.683868] ####ignore lock release, cookie mismatch: WiFi owner ˙˙˙˙
<6>[ 1826.683898] ------------------------------------------------
<6>[ 1826.683898] ------------------------------------------------
<6>[ 1826.683929] brcm_wlan_power Enter: power off
<6>[ 1826.683959] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 0
<4>[ 1826.920593] wifi_set_carddetect = 0
<4>[ 1826.920623] brcm_wifi_status:267 status 0
<6>[ 1826.920654] mmc1: Slot status change detected (1 -> 0)
<6>[ 1826.928405] mmc1: card 0001 removed
<6>[ 1828.083618] synaptics_rmi4_i2c 3-0020: [0][P] 0x01
<6>[ 1828.142578] synaptics_rmi4_i2c 3-0020: [0][R] 0x00 M[4] V[5c]
<4>[ 1828.178527] wifi_set_power = 1
<4>[ 1828.178558] WiFi: trying to acquire BT lock
<4>[ 1828.178558] ####btlock acquired cookie: WiFi
<4>[ 1828.178558] wifi_set_power: btlock acquired
<6>[ 1828.178558] ------------------------------------------------
<6>[ 1828.178588] ------------------------------------------------
<6>[ 1828.178588] brcm_wlan_power Enter: power on
<6>[ 1828.178588] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 1
<4>[ 1828.411895] wifi_set_carddetect = 1
<4>[ 1828.411926] brcm_wifi_status:267 status 1
<6>[ 1828.411956] mmc1: Slot status change detected (0 -> 1)
<3>[ 1828.473205] mmc1: msmsdcc_switch_io_voltage: MCIDATIN_3_0 is still not all zeros
<3>[ 1828.480651] mmc1: CMD7: Command CRC error
<3>[ 1828.484039] mmc1: SDCC PWR is ON
<3>[ 1828.487426] mmc1: SDCC clks are ON, MCLK rate=400000
<3>[ 1828.492217] mmc1: SDCC irq is enabled
<3>[ 1828.495849] ===== SDCC-CORE: Register Dumps @phys_base=0x12180000, @virt_base=0xe337a000 =====
<3>[ 1828.504608] Reg=0x00: 0x00000001, 0x01209300, 0x00000000, 0x00000447
<3>[ 1828.510955] Reg=0x10: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.517120] Reg=0x20: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.523620] Reg=0x30: 0x00000000, 0x004c0000, 0x00000000, 0x408001ff
<3>[ 1828.529785] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.536285] Reg=0x50: 0x06000018, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.542633] Reg=0x60: 0x67356400, 0x00000000, 0x00000018, 0x00000000
<3>[ 1828.548797] ===== SDCC-DML: Register Dumps @phys_base=0x12180800, @virt_base=0xe3534800 =====
<3>[ 1828.557495] Reg=0x00: 0x00000000, 0x00010001, 0x00000000, 0x00000000
<3>[ 1828.563629] Reg=0x10: 0x00000000, 0x00001000, 0x00001000, 0x00020001
<3>[ 1828.570159] Reg=0x20: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.576477] Reg=0x30: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.582641] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.589172] ===== SDCC-BAM: Register Dumps @phys_base=0x12182000, @virt_base=0xe33d8000 =====
<3>[ 1828.597503] Reg=0x00: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.604003] Reg=0x10: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.610351] Reg=0x20: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.616516] Reg=0x30: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.623016] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.629180] mmc1: MCI_TEST_INPUT = 0x0000003e
<3>[ 1828.633697] mmc1: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0, req_tout_ms=10000
<3>[ 1828.644012] mmc1: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<3>[ 1828.650817] mmc1: RPM: runtime_status=0, usage_count=2, is_suspended=0, disable_depth=0, runtime_error=0, request_pending=0, request=0
<4>[ 1828.663024] mmc1: Skipped tuning.
<3>[ 1828.686431] mmc1: error -110 whilst initialising SDIO card
<4>[ 1830.421936]
<4>[ 1830.421966] failed to power up wifi chip, retry again (4 left) **
Click to expand...
Click to collapse
As long as I know mmc0 is internal memory and mmc2 is external sd card. Can anyone explain what mmc1 device is?
Bump...
Hi,
so my S5(SM-900F) shows a black screen, but is otherwise functional. I don't know if it's a software or hardware issue, neither really makes sense to me.
Here's whats happened:
I wanted to flash cyanogenmod, phone seemed functional
Tried to flash twrp (3.0.1) with heimdall, got a bunch of errors
Tried a bunch of stuff, got it to flash twrp using heimdall-git
Phone got stuck in a boot loop
At this point I was annoyed and decided to reset it, which I did with kies
Here's where the screen issue started. After booting the screen was black. Phone showed S5 logo upon startup, download mode worked fine.
Touchscreen worked (managed to activate Talkback. In Hungarian), so the hardware seemed fine.
Googled and tried the million tips to fix a black screen, nothing worked
Screen randomly worked until reboot/lock
Fully charged the battery, screen worked until battery was at 70%, then black screen after locking with power button
Here's a kernel log from around that time:
dmesg
Nothing sticks out to me, log shows the backlight being adjusted which might be related.
This is the log I saved however, when I looked at it in the console I saw a few more things (see below)
Hoping it was a weird software issue I tried to flash cyanogenmod again, this time got into recovery (had to hold Vol Up+Home for more than half a minute), but got "kernel not seandroid enforcing" upon boot, then black screen and periodical vibration
Reset again
Wanted to see whether the screen would fail after some time in download mode, worked until battery was empty
Suddenly the screen's black in download mode, too, even though it worked for days
Here's a current bugreport.txt containing
Code:
***
<6>[ 157.910750] mipi_samsung_disp_send_cmd: get_my_check(0)!
<6>[ 157.910764] mipi_samsung_disp_send_cmd: get_my_check(0)!
<3>[ 157.910772] [mdnie lite] is negative Mode On = 0
<6>[ 157.910780] mdss_dsi_cmds_send: get_my_check(0)!
<3>[ 157.910791] [mdnie lite] mDNIe_Set_Mode end , UI_MODE(0), DYNAMIC(0), OUTDOOR_OFF_MODE(0), ACCESSIBILITY_OFF(0)
<6>[ 157.910801] mdss_dsi_panel_on : --
<6>[ 157.911850] mipi_samsung_disp_send_cmd: get_my_check(0)!
<6>[ 157.911858] mipi_samsung_disp_send_cmd: get_my_check(0)!
<6>[ 157.911867] mdss_dsi_cmds_send: get_my_check(0)!
<6>[ 157.911874] mdss_dsi_cmds_send: get_my_check(0)!
<6>[ 157.911880] mdss_dsi_cmd_receive: get_my_check(0)!
<6>[ 157.911887] read_reg : A[1] : .
<3>[ 157.911893] Error reading LCD NV data count(-19), read_size(1)!!!!
<6>[ 157.911900] mipi_samsung_disp_send_cmd: get_my_check(0)!
<3>[ 157.912839] Panel has gone bad, sending uevent - PANEL_ALIVE=0
<6>[ 157.912847] DISPLAY_ON
<6>[ 157.912862] mdss_mdp_overlay_on: mdss_mdp_overlay_on: --
<6>[ 157.912890] mdss_fb_blank_sub: FB_NUM:0, MDSS_FB_UNBLANK --
<6>[ 157.928517] __mdss_fb_perform_commit: kickoff done!
<6>[ 157.928534] mdss_fb_update_backlight: mfd->bl_level (255), bl_updated (0)
<6>[ 157.928546] mipi_samsung_disp_send_cmd: get_my_check(0)!
<6>[ 157.946943] mdss_fb_blank_sub: FB_NUM:1, MDSS_FB_UNBLANK ++
<6>[ 157.946959] mdss_mdp_overlay_on: mdss_mdp_overlay_on: ++
<6>[ 157.946977] mdss_mdp_overlay_on: mdss_mdp_overlay_on: --
<6>[ 157.947007] mdss_fb_blank_sub: FB_NUM:1, MDSS_FB_UNBLANK --
<6>[ 157.950265] hdmi_edid_sysfs_rda_modes: '4,19,32,33,34,3,18,1'
<6>[ 157.951605] hdmi_tx_get_vic_from_panel_info: 1920x1080 p30 16/9 is supported
<6>[ 157.951622] mdss_fb_blank_sub: FB_NUM:1, MDSS_FB_BLANK ++
<6>[ 157.951799] mdss_fb_blank_sub: FB_NUM:1, MDSS_FB_BLANK --
<6>[ 157.951809] mdss_fb_blank_sub: FB_NUM:1, MDSS_FB_UNBLANK ++
<6>[ 157.951819] mdss_mdp_overlay_on: mdss_mdp_overlay_on: ++
<6>[ 157.951831] mdss_mdp_overlay_on: mdss_mdp_overlay_on: --
<6>[ 157.951964] mdss_fb_blank_sub: FB_NUM:1, MDSS_FB_UNBLANK --
***
<4>[ 158.012453] WARNING: at /home/dpi/qb5_8814/workspace/KLTE_EUR_OPEN/android/kernel/drivers/video/msm/mdss/mdss_mdp_util.c:105 mdss_mdp_set_intr_callback+0x10c/0x12c()
<6>[ 158.012461] replacing current intr callback for ndx=8
Those I also saw before the previous dmesg.
The -19 read bytes seems especially dubious, from a quick look at the source it does not seem like an errno, don't know if it's related to the problem anyway.
Current Android version: 6.0.1
Kernel: 3.4.0
Build: MMB29M.G900FXXS1CPG9
So what's going on? Is this some weird hardware issue? Do the ways download mode and android control the screen differ? What difference does the battery make?
Is it software? Both?
I've searched the forum and found e.g this, but nothing that helped me out.
Thank you for your help,
NoR8quoh1r
heimdall?
Flash stock ROM from here with ODIN
http://updato.com/firmware-archive-select-model?r=BTU&v=&q=G900F
Heimdall is broken thw cm wiki is outdated use odin next time
Sent from my SM-G900F using Tapatalk
azooz95 said:
Heimdall is broken thw cm wiki is outdated use odin next time
Click to expand...
Click to collapse
It isn't broken, it's just iffy. Still would recommend Odin though, I use arch Linux and just find a Windows laptop and do whatever needs to be done there.
Sent from my Galaxy S5 using XDA Labs
*Detection* said:
heimdall?
Flash stock ROM from here with ODIN
Click to expand...
Click to collapse
Tried it, did not make a difference
Rakuu said:
It isn't broken, it's just iffy. Still would recommend Odin though, I use arch Linux and just find a Windows laptop and do whatever needs to be done there.
Sent from my Galaxy S5 using XDA Labs
Click to expand...
Click to collapse
Yeah, had no problems with the newest version, tho. Fellow Archlinux user here .