Related
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.
Every so often my phone just refuses to wake up. I press menu and the keys light up but screen never does. I press call+menu+end to reboot and screen still doesn't wake up. Second time I try call+menu+end screen finally wakes up and device reboots. I'm running CyanogenMod 3.6.8.1 and have a custom bootscreen. Does this seem like a hardware problem or software? Any help is much appreciated, thanks.
After flashing a new ROM, the problem seemed to go away but came back. Everything seems to power on except the lcd. I can tap and hold to move an icon but nothing shows on the screen. Is there a certain app that would cause this or is it hardware? I've disabled compcache and swap and it made no difference. Any advice appreciated
I uncovered a little more info using dmesg over adb. Heres what it said
Code:
<3>[ 569.121337] Freezing of user space aborted
<4>[ 569.126312]
<4>[ 569.128173] Restarting tasks ... done.
<6>[ 569.144226] suspend: exit suspend, ret = -11 (2009-07-26 16:02:19.600952156 UTC)
<6>[ 569.536926] PM: Syncing filesystems ... done.
<4>[ 569.544097] Freezing user space processes ... (elapsed 0.00 seconds) done.
<4>[ 569.556793] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
<4>[ 569.570587] trout_sdslot_switchvdd: Disabling SD slot power
<4>[ 569.576934] trout_sdslot_switchvdd: Setting level to 2950
<6>[ 569.588989] wakeup wake lock: SMD_RPCCALL
<4>[ 569.595153] Restarting tasks ... done.
<6>[ 570.164764] suspend: exit suspend, ret = 0 (2009-07-26 16:06:04.070281996 UTC)
<6>[ 570.679016] PM: Syncing filesystems ... done.
<4>[ 570.686401] Freezing user space processes ... (elapsed 0.00 seconds) done.
<4>[ 570.702178] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
<4>[ 570.717041] trout_sdslot_switchvdd: Disabling SD slot power
<6>[ 570.717041] wakeup wake lock: gpio_kp
<4>[ 570.722290] trout_sdslot_switchvdd: Setting level to 2950
<4>[ 570.737670] Restarting tasks ... <6>request_suspend_state: wakeup (3->0) at 566131612099 (2009-07-26 16:06:43.522277832 UTC)
<4>[ 570.768218] done.
<7>[ 571.308227] mmc_queue_thread: status 0x00000900
<6>[ 571.313720] suspend: exit suspend, ret = 0 (2009-07-26 16:06:44.077117942 UTC)
<6>[ 571.537597] mddi_remote_read(150000) timeout (-1 -973073920 0)
<6>[ 571.544189] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val d curr_rev_ptr 0
<6>[ 571.657470] mddi_remote_read(150000) timeout (-1 -1 0)
<6>[ 571.662902] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val d curr_rev_ptr 0
<6>[ 571.767456] mddi_remote_read(150000) timeout (-1 -1 0)
<6>[ 571.773010] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val d curr_rev_ptr 0
<4>[ 571.783599] unknown panel id at mddi_enable
<6>[ 571.788238] msmfb: panel resume failed, not resuming fb
<6>[ 576.621246] hsusb: OFFLINE -> ONLINE
<6>[ 576.625518] hsusb: reset controller
<4>[ 576.687469] ulpi: write 0x40 to 0x31
<4>[ 576.691497] ulpi: write 0x1d to 0x0d
<4>[ 576.695434] ulpi: write 0x1d to 0x10
<6>[ 576.699768] ept #0 out max:64 head:ffa0c000 bit:0
<6>[ 576.704833] ept #1 out max:512 head:ffa0c080 bit:1
<6>[ 576.710327] ept #2 out max:512 head:ffa0c100 bit:2
<6>[ 576.715515] ept #0 in max:64 head:ffa0c040 bit:16
<6>[ 576.720642] ept #1 in max:512 head:ffa0c0c0 bit:17
<6>[ 576.726074] ept #2 in max:512 head:ffa0c140 bit:18
<6>[ 576.731597] usb: notify offline
<6>[ 576.753906] usb: suspend
<6>[ 576.936981] usb: reset
<6>[ 576.939270] usb: portchange USB_SPEED_HIGH
<6>[ 577.097961] usb: reset
<6>[ 577.100555] usb: portchange USB_SPEED_HIGH
<6>[ 577.333526] usb_mass_storage usb_mass_storage: config #1
<6>[ 578.735534] audmgr_rpc_thread() start
<6>[ 578.736206] audio_enable()
<6>[ 578.736236] ++++++++++++++++++++++++++++++
<6>[ 578.745056] audmgr: rpc_reply status 0
<6>[ 578.758941] audmgr: rpc READY handle=0x00000000
<6>[ 578.837646] audmgr: rpc CODEC_CONFIG volume=0x00002000
<6>[ 578.837738] audpp: enable
<6>[ 578.837768] adsp: opening module AUDPPTASK
<6>[ 578.850708] adsp: module AUDPPTASK has been registered
<6>[ 578.850738] msm_adsp_enable() 'AUDPPTASK'state[0] id[4]
<6>[ 578.861938] adsp: rpc event=0, proc_id=2, module=4, image=0
<6>[ 578.861999] adsp: module AUDPPTASK: READY
<6>[ 578.862304] audpp: ENABLE
<6>[ 578.862365] audio_dsp_event: CFG_MSG ENABLE
<3>[ 579.530090] audpp: DMA missed obj=20
<6>[ 582.459472] audio_disable()
<6>[ 582.462738] audio_dsp_event: CFG_MSG DISABLE
<6>[ 582.467712] audpp: disable
<6>[ 582.470825] msm_adsp_disable() 'AUDPPTASK'
<6>[ 582.475250] audpp: DISABLE
<6>[ 582.479705] adsp: closing module AUDPPTASK
<6>[ 582.484252] adsp: disable interrupt
<6>[ 582.490600] audmgr: rpc_reply status 0
<3>[ 582.520477] audmgr: DISABLED
<6>[ 582.523986] ------------------------------
[B]<6>[ 637.073669] request_suspend_state: sleep (0->3) at 632446370407 (2009-07-26 16:07:49.837036140 UTC)
<6>[ 637.187530] mddi_remote_read(150000) timeout (-1 99 0)
<6>[ 637.193176] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val d curr_rev_ptr 0
<6>[ 637.317962] mddi_remote_read(150000) timeout (-1 -1 0)
<6>[ 637.323577] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val d curr_rev_ptr 0
<6>[ 637.457519] mddi_remote_read(150000) timeout (-1 -1 0)
<6>[ 637.463104] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val d curr_rev_ptr 0
<4>[ 637.478057] unknown panel_id: 3
<4>[ 637.788482] save exit: isCheckpointed 1
<6>[ 939.424530] request_suspend_state: wakeup (3->0) at 934797200486 (2009-07-26 16:12:52.187896737 UTC)
<6>[ 939.647521] mddi_remote_read(150000) timeout (-1 -973073920 0)
<6>[ 939.653656] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val d curr_rev_ptr 0
<6>[ 939.757568] mddi_remote_read(150000) timeout (-1 -1 0)
<6>[ 939.763153] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val d curr_rev_ptr 0
<6>[ 939.867553] mddi_remote_read(150000) timeout (-1 -1 0)
<6>[ 939.872985] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val d curr_rev_ptr 0
<4>[ 939.883544] unknown panel id at mddi_enable
<6>[ 939.887969] msmfb: panel resume failed, not resuming fb
<4>[ 939.929138] msm_i2c msm_i2c.0: Warning bus was busy (5)
<6>[ 949.676208] request_suspend_state: sleep (0->3) at 945048909481 (2009-07-26 16:13:02.439605732 UTC)
<6>[ 949.797393] mddi_remote_read(150000) timeout (-1 98 0)
<6>[ 949.803283] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val d curr_rev_ptr 0
<6>[ 949.907409] mddi_remote_read(150000) timeout (-1 -1 0)
<6>[ 949.913024] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val d curr_rev_ptr 0
<6>[ 950.037567] mddi_remote_read(150000) timeout (-1 -1 0)
<6>[ 950.037628] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val d curr_rev_ptr 0
<4>[ 950.038269] unknown panel_id: 3
<4>[ 950.745727] save exit: isCheckpointed 1[/B]
Is the code in bold at the end my problem? Is my hardware broken or could this be just a software bug?
I also tried an older CM build and same thing is happening. Is this officially hardware? Would I be able to get it replaced by HTC considering I got it unlocked on eBay?
umm u might wanna wipe...n if that doesnt work..(drastic measures) run dreaming.nbh in the spl bootloader and reroot
I've wiped and flashed a different ROM twice, no luck. How do I run dreaming.nbh? From the shell in recovery?
Hi all,
I have downloaded the 6.1.0-RC2-Aria ROM a couple of days ago, installed it on my phone and everything is working great - thanks again attn1!
Now I would like to do some testing/dev with it; instead of tampering with my device.
I created a NANdroid back-up and then tried running the ROM on the SDK emulator following threads instructions found over here and other forums, e.g. :
http://forum.xda-developers.com/archive/index.php/t-572497.html
http://forum.xda-developers.com/showthread.php?t=525930&page=2
http://android.modaco.com/content/g...p-and-running-a-full-rom-with-the-market-etc/
The emulator seems to be running OK, but the kernel gets stuck before it even gives me the boot animation. (- c.f. below for the parameters passed and the kernel boot log; adb logcat does not report anything at all -)
Anyone has been able to run this particular ROM on the SDK emulator or may give me pointers as to how to do so successfully?
Thank you.
+++++++++++++++++++++++++++++++++++++++++++++++++++++
C:\android-sdk-windows\tools>emulator -avd testing -show-kernel -sdcard mycard
Uncompressing Linux............................................................................................. done, booting the kernel.
Initializing cgroup subsys cpu
Linux version 2.6.29-00261-g0097074-dirty ([email protected]) (gcc version 4.4.0 (GCC) ) #20 Wed Mar 31 09:54:02 PDT 2010
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00093177
CPU: VIVT data cache, VIVT instruction cache
Machine: Goldfish
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048
Kernel command line: qemu=1 console=ttyS0 android.checkjni=1 android.qemud=ttyS1 android.ndns=1
Unknown boot option `android.checkjni=1': ignoring
Unknown boot option `android.qemud=ttyS1': ignoring
Unknown boot option `android.ndns=1': ignoring
PID hash table entries: 2048 (order: 11, 8192 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 512MB = 512MB total
Memory: 515840KB available (2616K code, 681K data, 104K init)
Calibrating delay loop... 238.38 BogoMIPS (lpj=1191936)
Mount-cache hash table entries: 512
Initializing cgroup subsys debug
Initializing cgroup subsys cpuacct
Initializing cgroup subsys freezer
CPU: Testing write buffer coherency: ok
net_namespace: 520 bytes
NET: Registered protocol family 16
bio: create slab <bio-0> at 0
NET: Registered protocol family 2
IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
TCP established hash table entries: 65536 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 65536 bind 65536)
TCP reno registered
NET: Registered protocol family 1
checking if image is initramfs... it is
Freeing initrd memory: 160K
goldfish_new_pdev goldfish_interrupt_controller at ff000000 irq -1
goldfish_new_pdev goldfish_device_bus at ff001000 irq 1
goldfish_new_pdev goldfish_timer at ff003000 irq 3
goldfish_new_pdev goldfish_rtc at ff010000 irq 10
goldfish_new_pdev goldfish_tty at ff002000 irq 4
goldfish_new_pdev goldfish_tty at ff011000 irq 11
goldfish_new_pdev smc91x at ff012000 irq 12
goldfish_new_pdev goldfish_fb at ff013000 irq 13
goldfish_new_pdev goldfish_mmc at ff005000 irq 14
goldfish_new_pdev goldfish_memlog at ff006000 irq -1
goldfish_new_pdev goldfish_events at ff014000 irq 15
goldfish_new_pdev goldfish_nand at ff015000 irq -1
goldfish_new_pdev goldfish-switch at ff016000 irq 16
goldfish_new_pdev goldfish-switch at ff017000 irq 17
goldfish_pdev_worker registered goldfish_interrupt_controller
goldfish_pdev_worker registered goldfish_device_bus
goldfish_pdev_worker registered goldfish_timer
goldfish_pdev_worker registered goldfish_rtc
goldfish_pdev_worker registered goldfish_tty
goldfish_pdev_worker registered goldfish_tty
goldfish_pdev_worker registered smc91x
goldfish_pdev_worker registered goldfish_fb
goldfish_pdev_worker registered goldfish_mmc
goldfish_pdev_worker registered goldfish_memlog
goldfish_pdev_worker registered goldfish_events
goldfish_pdev_worker registered goldfish_nand
goldfish_pdev_worker registered goldfish-switch
goldfish_pdev_worker registered goldfish-switch
ashmem: initialized
Installing knfsd (copyright (C) 1996 [email protected]).
yaffs Mar 26 2010 13:38:48 Installing.
msgmni has been set to 1008
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
allocating frame buffer 320 * 480, got ffa00000
Console: switching to colour frame buffer device 40x30
console [ttyS0] enabled
brd: module loaded
loop: module loaded
nbd: registered device at major 43
smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <[email protected]>
eth0 (smc91x): not using net_device_ops yet
eth0: SMC91C11xFD (rev 1) at e084c000 IRQ 12 [nowait]
eth0: Ethernet addr: 52:54:00:12:34:56
goldfish nand dev0: size 6ea0000, page 2048, extra 64, erase 131072
goldfish nand dev1: size 4000000, page 2048, extra 64, erase 131072
goldfish nand dev2: size 4000000, page 2048, extra 64, erase 131072
mice: PS/2 mouse device common for all mice
*** events probe ***
events_probe() addr=0xe0854000 irq=15
events_probe() keymap=qwerty2
input: qwerty2 as /devices/virtual/input/input0
goldfish_rtc goldfish_rtc: rtc core: registered goldfish_rtc as rtc0
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: [email protected]
logger: created 64K log 'log_main'
logger: created 256K log 'log_events'
logger: created 64K log 'log_radio'
IPv4 over IPv4 tunneling driver
GRE over IPv4 tunneling driver
TCP cubic registered
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
802.1Q VLAN Support v1.8 Ben Greear <[email protected]>
All bugs added by David S. Miller <[email protected]>
VFP support v0.3: implementor 41 architecture 1 part 10 variant 9 rev 0
goldfish_rtc goldfish_rtc: setting system clock to 2010-12-05 03:32:33 UTC (1291
519953)
Freeing init memory: 104K
mmc0: new SD card at address e118
mmcblk0: mmc0:e118 SU02G 1.00 GiB
mmcblk0:
init: cannot open '/initlogo.rle'
yaffs: dev is 32505856 name is "mtdblock0"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.0, "mtdblock0"
yaffs_read_super: isCheckpointed 0
save exit: isCheckpointed 0
yaffs: dev is 32505857 name is "mtdblock1"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.1, "mtdblock1"
yaffs: restored from checkpoint
yaffs_read_super: isCheckpointed 1
yaffs: dev is 32505858 name is "mtdblock2"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.2, "mtdblock2"
yaffs: restored from checkpoint
yaffs_read_super: isCheckpointed 1
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
request_suspend_state: wakeup (3->0) at 4206070790 (2010-12-05 03:32:36.48957032
7 UTC)
init: untracked pid 34 exited
init: untracked pid 42 exited
request_suspend_state: wakeup (0->0) at 4256118986 (2010-12-05 03:32:36.53963374
7 UTC)
init: untracked pid 44 exited
init: untracked pid 53 exited
request_suspend_state: wakeup (0->0) at 9387505566 (2010-12-05 03:32:41.67101886
1 UTC)
init: untracked pid 54 exited
init: untracked pid 60 exited
init: untracked pid 68 exited
init: untracked pid 69 exited
request_suspend_state: wakeup (0->0) at 14518491192 (2010-12-05 03:32:46.8020076
30 UTC)
init: untracked pid 74 exited
init: untracked pid 82 exited
init: untracked pid 83 exited
request_suspend_state: wakeup (0->0) at 19655651551 (2010-12-05 03:32:51.9391665
92 UTC)
init: untracked pid 89 exited
request_suspend_state: wakeup (0->0) at 24731037643 (2010-12-05 03:32:57.0145514
97 UTC)
init: critical process 'servicemanager' exited 4 times in 4 minutes; rebooting i
nto recovery mode
save exit: isCheckpointed 1
save exit: isCheckpointed 1
Restarting system with command 'recovery'.
Reboot failed -- System halted
+++++++++++++++++++++++++++++++++++++++++++++++++++++
LOL, root the emulated device!
I would if I knew how to do so on the emulator itself
I have rooted my actual device, but I have no idea how to accomplish this on the emulator; could you elaborate or send links on how to do this please?
I have googled and nothing relevant has showed up other than the emulator is supposed to be already root-ed; by issuing adb root I get:
C:\android-sdk\android-sdk-windows\tools>adb root
adbd is already running as root
I also tried running the emulator with the '-shell' parameter, but got the same result and the boot process gets stuck as well...
A little bit of extra guidance would be great.
Thank you.
Hi All,
I would have posted in the developer forum under one of the CM7 threads but this is my first post on xda so here it goes:
I've been following the developer forums for a while now and I too am plagued with the wonks on my N1 with CM7. For me the wonkiness = phone not being responsive with black screen and no audio when making a phone call, then after about 15 to 25 seconds the screen shows the call and audio is back on).
This is understandable since it's still in an alpha state not ready for production so I wanted to post my logcat (running build 27) snapshot (attached) to see if it will help some developer figure out how to fix the wonk of terror.
Here's how I reproduce the wonk:
I turn my N1 on and as soon as it boots up I press the power button to shut the screen off. After about 2 to 3 minutes I press the power button, unlock my phone and try to make a call. I am guaranteed a wonk every time.
My temporary fix is the CM7 Dewonkificator Add-on. It definitely fixes my N1's wonkiness problem for the time being.
Thanks for listening!
markhm1978 said:
Hi All,
I would have posted in the developer forum under one of the CM7 threads but this is my first post on xda so here it goes:
I've been following the developer forums for a while now and I too am plagued with the wonks on my N1 with CM7. For me the wonkiness = phone not being responsive with black screen and no audio when making a phone call, then after about 15 to 25 seconds the screen shows the call and audio is back on).
This is understandable since it's still in an alpha state not ready for production so I wanted to post my logcat (running build 27) snapshot (attached) to see if it will help some developer figure out how to fix the wonk of terror.
Here's how I reproduce the wonk:
I turn my N1 on and as soon as it boots up I press the power button to shut the screen off. After about 2 to 3 minutes I press the power button, unlock my phone and try to make a call. I am guaranteed a wonk every time.
My temporary fix is the CM7 Dewonkificator Add-on. It definitely fixes my N1's wonkiness problem for the time being.
Thanks for listening!
Click to expand...
Click to collapse
If I'm not mistaken, CM has noted the source of the error (mic) and they are conjuring up a fix. It should most likely be ready to go in one of the next few nightlies.
Thanks! Didn't happen to come across that piece of information in my travels on xda forums.
markhm1978 said:
Thanks! Didn't happen to come across that piece of information in my travels on xda forums.
Click to expand...
Click to collapse
You must've taken a right instead of a left...
rickytenzer said:
If I'm not mistaken, CM has noted the source of the error (mic) and they are conjuring up a fix. It should most likely be ready to go in one of the next few nightlies.
Click to expand...
Click to collapse
That first attempt fix was released in build 27 earlier today.
Unfortunately some peoples are still reporting the call wonkiness.
rickytenzer said:
You must've taken a right instead of a left...
Click to expand...
Click to collapse
Yeah, it's pretty easy to get lost in all of the chocolaty goodness here.
baseballfanz said:
That first attempt fix was released in build 27 earlier today.
Unfortunately some peoples are still reporting the call wonkiness.
Click to expand...
Click to collapse
Thanks for the info. I am one of the unfortunate ones.
Just tried Build 28 and the phone call still wonks out. logcat snapshot attached.
Call Wonks for me on Build 29. Dewonkificator is still working as a temporary fix.
It's been hit or miss with me - no wonks until I think build 17 and then twenty-something...
It's still worth it - you get wonks in brand new phones sometimes and the solution isn't likely contained in a flash update within another 24 hours!
I will suffer the pain of wonkiness until it is finally solved by those brilliant minds working away on polishing this gorgeous CM7 port. Thank you - your efforts are REALLY appreciated here
should post this on the cyan forums if u havent already, im sure they could use it if it actually works.
Basil 123 said:
It's been hit or miss with me - no wonks until I think build 17 and then twenty-something...
It's still worth it - you get wonks in brand new phones sometimes and the solution isn't likely contained in a flash update within another 24 hours!
I will suffer the pain of wonkiness until it is finally solved by those brilliant minds working away on polishing this gorgeous CM7 port. Thank you - your efforts are REALLY appreciated here
Click to expand...
Click to collapse
I too love the CM7 port! So much that I'm about to donate $20 to buy Cyanogen some beer.
I figured instead of *****ing about how my phone calls are wonking out, I'd post some info to try and help with the situation and keep track of any wonks per build in this thread.
Have you tried Dewonkificator yet? It works really well for me. Here's the link: http://forum.xda-developers.com/showthread.php?t=935250
Buck Shot said:
should post this on the cyan forums if u havent already, im sure they could use it if it actually works.
Click to expand...
Click to collapse
I am creating an account on the Cyan forums now and will post a link to this thread.
Thanks for the suggestion.
Build 30, Wonks for me. Dewonkificator still working as a temp fix.
rickytenzer said:
You must've taken a right instead of a left...
Click to expand...
Click to collapse
lol you should have said: Sorry, but our princess is in another castle.
logcats are only half, posting dmesg's would be more helpful if any dev was going to check out your logs.
fitsnugly said:
lol you should have said: Sorry, but our princess is in another castle.
logcats are only half, posting dmesg's would be more helpful if any dev was going to check out your logs.
Click to expand...
Click to collapse
Thanks! I will look in to how to capture the dmesg's. While I look, do you have any suggestions for capturing this info?
fitsnugly said:
lol you should have said: Sorry, but our princess is in another castle.
logcats are only half, posting dmesg's would be more helpful if any dev was going to check out your logs.
Click to expand...
Click to collapse
Okay, figured it out. Attached the dmesg of my Wonkiness for Build 30.
Hi. I am on #31. The wonky is still here. dmesg output attached.
View attachment 2011-02-04-04.txt
I suppose this is a log of the wonky call:
Code:
<6>[ 644.924621] request_suspend_state: wakeup (3->0) at 640894655059 (2011-02-04 07:41:27.847267217 UTC)
<6>[ 644.927429] lcdc_resume: resuming
<6>[ 644.951568] mahimahi_ts_power: power 1
<6>[ 644.989440] lcdc_unblank: ()
<6>[ 644.990478] samsung_oled_panel_unblank: +()
<6>[ 645.281188] samsung_oled_panel_unblank: -()
<6>[ 648.953430] pcm_out: open
<6>[ 648.953918] acdb: 588 bytes for device 607, rate 48000.
<6>[ 650.724761] a1026_set_config: change to mode 1
<6>[ 650.724975] a1026_set_config: block write start (size = 56)
<6>[ 650.730865] a1026_set_config: block write end
<6>[ 650.755981] a1026_set_config: CMD ACK block read start
<3>[ 653.738586] msm_i2c msm_i2c.0: Error waiting for notbusy (0)
<3>[ 653.739074] msm_i2c msm_i2c.0: Transaction timed out
<3>[ 653.739868] msm_i2c msm_i2c.0: Error during data xfer 3e (-110)
<4>[ 653.740448] msm_i2c msm_i2c.0: Still the bus master, status 9b00, intf 0
<4>[ 653.741271] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 1
<4>[ 653.918853] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 653.919738] a1026_i2c_read: transfer error -110
<3>[ 653.920166] a1026_set_config: CMD ACK block read error
<6>[ 653.920928] a1026_i2c_sw_reset: 80020000
<3>[ 655.900756] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 655.901336] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 655.902130] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 656.080993] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 656.081573] a1026_i2c_write: transfer error -16
<3>[ 656.082000] a1026_ioctl: A1026_SET_CONFIG (1) error -110!
<6>[ 656.082824] a1026_set_config: change to mode 1
<6>[ 656.083282] a1026_set_config: block write start (size = 56)
<3>[ 658.063629] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 658.064239] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 658.065032] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 658.243072] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 658.243927] a1026_i2c_write: transfer error -16
<3>[ 658.244384] A1026 CMD block write error!
<6>[ 658.245117] a1026_i2c_sw_reset: 80020000
<3>[ 660.224914] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 660.225830] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 660.226318] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 660.405181] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 660.405761] a1026_i2c_write: transfer error -16
<3>[ 660.406524] a1026_ioctl: A1026_SET_CONFIG (1) error -16!
<6>[ 660.407012] a1026_set_config: change to mode 1
<6>[ 660.407440] a1026_set_config: block write start (size = 56)
<3>[ 662.387023] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 662.387634] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 662.388427] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 662.567291] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 662.568206] a1026_i2c_write: transfer error -16
<3>[ 662.568634] A1026 CMD block write error!
<6>[ 662.569427] a1026_i2c_sw_reset: 80020000
<3>[ 664.549560] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 664.550476] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 664.550964] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 664.729370] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 664.729919] a1026_i2c_write: transfer error -16
<3>[ 664.730712] a1026_ioctl: A1026_SET_CONFIG (1) error -16!
<6>[ 664.731170] a1026_set_config: change to mode 1
<6>[ 664.731628] a1026_set_config: block write start (size = 56)
<3>[ 666.721221] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 666.721801] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 666.722625] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 666.901550] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 666.902435] a1026_i2c_write: transfer error -16
<3>[ 666.902862] A1026 CMD block write error!
<6>[ 666.903656] a1026_i2c_sw_reset: 80020000
<3>[ 668.883361] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 668.884277] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 668.884765] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 669.063629] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 669.064178] a1026_i2c_write: transfer error -16
<3>[ 669.064941] a1026_ioctl: A1026_SET_CONFIG (1) error -16!
<3>[ 669.067352] msm_i2c msm_i2c.0: IRQ but nothing to do!, status 8302
<4>[ 669.083496] msm_i2c msm_i2c.0: Warning bus was busy (102)
<4>[ 669.085998] msm_i2c msm_i2c.0: 1 unrequested bytes read
<6>[ 669.127288] a1026_bootup_init: starting to load image (863 passes)...
<6>[ 672.336761] a1026_bootup_init: firmware loaded successfully
<6>[ 672.341888] batt: 54%, 3791 mV, -277 mA (-246 avg), 30.3 C, 728 mAh
<6>[ 672.497192] a1026_bootup_init: initialized!
<6>[ 672.658020] a1026_set_config: change to mode 1
<6>[ 672.658477] a1026_set_config: block write start (size = 56)
<6>[ 672.664947] a1026_set_config: block write end
<6>[ 672.687408] a1026_set_config: CMD ACK block read start
<6>[ 672.693542] a1026_set_config: CMD ACK block read end
<6>[ 672.747741] acdb: 974 bytes for device 2, rate 48000.
<6>[ 672.909057] acdb: 819 bytes for device 1, rate 8000.
<6>[ 673.097686] capella_cm3602_open
<6>[ 673.097869] capella_cm3602_ioctl cmd 2
<6>[ 673.098022] capella_cm3602_enable
<6>[ 673.098175] proximity 1
<6>[ 673.121124] request_suspend_state: wakeup (0->0) at 669063729306 (2011-02-04 07:41:56.016341464 UTC)
<6>[ 682.863403] capella_cm3602_ioctl cmd 2
<6>[ 682.863739] capella_cm3602_disable
<6>[ 682.864044] capella_cm3602_release
<6>[ 682.864349] capella_cm3602_disable
<6>[ 682.864868] capella_cm3602_disable: already disabled
<6>[ 682.874908] a1026_set_config: change to mode 13
<6>[ 682.875457] a1026_set_config: block write start (size = 16)
<6>[ 682.877563] a1026_set_config: block write end
<6>[ 682.907012] a1026_set_config: CMD ACK block read start
<6>[ 682.908966] a1026_set_config: CMD ACK block read end
<6>[ 682.909271] acdb: 871 bytes for device 507, rate 8000.
<6>[ 685.739837] pcm_out: release
PS @markhm1978
Compared your dmesg output with mine. It is quite the same...
dolphin77 said:
Hi. I am on #31. The wonky is still here. dmesg output attached.
View attachment 508500
I suppose this is a log of the wonky call:
Code:
<6>[ 644.924621] request_suspend_state: wakeup (3->0) at 640894655059 (2011-02-04 07:41:27.847267217 UTC)
<6>[ 644.927429] lcdc_resume: resuming
<6>[ 644.951568] mahimahi_ts_power: power 1
<6>[ 644.989440] lcdc_unblank: ()
<6>[ 644.990478] samsung_oled_panel_unblank: +()
<6>[ 645.281188] samsung_oled_panel_unblank: -()
<6>[ 648.953430] pcm_out: open
<6>[ 648.953918] acdb: 588 bytes for device 607, rate 48000.
<6>[ 650.724761] a1026_set_config: change to mode 1
<6>[ 650.724975] a1026_set_config: block write start (size = 56)
<6>[ 650.730865] a1026_set_config: block write end
<6>[ 650.755981] a1026_set_config: CMD ACK block read start
<3>[ 653.738586] msm_i2c msm_i2c.0: Error waiting for notbusy (0)
<3>[ 653.739074] msm_i2c msm_i2c.0: Transaction timed out
<3>[ 653.739868] msm_i2c msm_i2c.0: Error during data xfer 3e (-110)
<4>[ 653.740448] msm_i2c msm_i2c.0: Still the bus master, status 9b00, intf 0
<4>[ 653.741271] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 1
<4>[ 653.918853] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 653.919738] a1026_i2c_read: transfer error -110
<3>[ 653.920166] a1026_set_config: CMD ACK block read error
<6>[ 653.920928] a1026_i2c_sw_reset: 80020000
<3>[ 655.900756] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 655.901336] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 655.902130] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 656.080993] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 656.081573] a1026_i2c_write: transfer error -16
<3>[ 656.082000] a1026_ioctl: A1026_SET_CONFIG (1) error -110!
<6>[ 656.082824] a1026_set_config: change to mode 1
<6>[ 656.083282] a1026_set_config: block write start (size = 56)
<3>[ 658.063629] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 658.064239] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 658.065032] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 658.243072] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 658.243927] a1026_i2c_write: transfer error -16
<3>[ 658.244384] A1026 CMD block write error!
<6>[ 658.245117] a1026_i2c_sw_reset: 80020000
<3>[ 660.224914] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 660.225830] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 660.226318] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 660.405181] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 660.405761] a1026_i2c_write: transfer error -16
<3>[ 660.406524] a1026_ioctl: A1026_SET_CONFIG (1) error -16!
<6>[ 660.407012] a1026_set_config: change to mode 1
<6>[ 660.407440] a1026_set_config: block write start (size = 56)
<3>[ 662.387023] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 662.387634] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 662.388427] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 662.567291] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 662.568206] a1026_i2c_write: transfer error -16
<3>[ 662.568634] A1026 CMD block write error!
<6>[ 662.569427] a1026_i2c_sw_reset: 80020000
<3>[ 664.549560] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 664.550476] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 664.550964] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 664.729370] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 664.729919] a1026_i2c_write: transfer error -16
<3>[ 664.730712] a1026_ioctl: A1026_SET_CONFIG (1) error -16!
<6>[ 664.731170] a1026_set_config: change to mode 1
<6>[ 664.731628] a1026_set_config: block write start (size = 56)
<3>[ 666.721221] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 666.721801] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 666.722625] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 666.901550] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 666.902435] a1026_i2c_write: transfer error -16
<3>[ 666.902862] A1026 CMD block write error!
<6>[ 666.903656] a1026_i2c_sw_reset: 80020000
<3>[ 668.883361] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 668.884277] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 668.884765] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 669.063629] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 669.064178] a1026_i2c_write: transfer error -16
<3>[ 669.064941] a1026_ioctl: A1026_SET_CONFIG (1) error -16!
<3>[ 669.067352] msm_i2c msm_i2c.0: IRQ but nothing to do!, status 8302
<4>[ 669.083496] msm_i2c msm_i2c.0: Warning bus was busy (102)
<4>[ 669.085998] msm_i2c msm_i2c.0: 1 unrequested bytes read
<6>[ 669.127288] a1026_bootup_init: starting to load image (863 passes)...
<6>[ 672.336761] a1026_bootup_init: firmware loaded successfully
<6>[ 672.341888] batt: 54%, 3791 mV, -277 mA (-246 avg), 30.3 C, 728 mAh
<6>[ 672.497192] a1026_bootup_init: initialized!
<6>[ 672.658020] a1026_set_config: change to mode 1
<6>[ 672.658477] a1026_set_config: block write start (size = 56)
<6>[ 672.664947] a1026_set_config: block write end
<6>[ 672.687408] a1026_set_config: CMD ACK block read start
<6>[ 672.693542] a1026_set_config: CMD ACK block read end
<6>[ 672.747741] acdb: 974 bytes for device 2, rate 48000.
<6>[ 672.909057] acdb: 819 bytes for device 1, rate 8000.
<6>[ 673.097686] capella_cm3602_open
<6>[ 673.097869] capella_cm3602_ioctl cmd 2
<6>[ 673.098022] capella_cm3602_enable
<6>[ 673.098175] proximity 1
<6>[ 673.121124] request_suspend_state: wakeup (0->0) at 669063729306 (2011-02-04 07:41:56.016341464 UTC)
<6>[ 682.863403] capella_cm3602_ioctl cmd 2
<6>[ 682.863739] capella_cm3602_disable
<6>[ 682.864044] capella_cm3602_release
<6>[ 682.864349] capella_cm3602_disable
<6>[ 682.864868] capella_cm3602_disable: already disabled
<6>[ 682.874908] a1026_set_config: change to mode 13
<6>[ 682.875457] a1026_set_config: block write start (size = 16)
<6>[ 682.877563] a1026_set_config: block write end
<6>[ 682.907012] a1026_set_config: CMD ACK block read start
<6>[ 682.908966] a1026_set_config: CMD ACK block read end
<6>[ 682.909271] acdb: 871 bytes for device 507, rate 8000.
<6>[ 685.739837] pcm_out: release
PS @markhm1978
Compared your dmesg output with mine. It is quite the same...
Click to expand...
Click to collapse
It is quite the same. I am on 31 also, still experiencing the Wonkiness. Will post more logs when 32 hits.
Wonks for me on Build 32. Dewonkificator still working as a temporary fix: http://forum.xda-developers.com/showthread.php?t=935250
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...