Hey all,
for some reason I have a infinite boot loop on my rooted Note (the boot animation plays, but then it restarts); firmware version is stock XXLSZ with root and CWM Recovery 6.0.3.0/PhilZ Touch 4.
I have not done anything to the OS since I fixed it up the last time a month ago; and once again I have no backup of the data on the internal memory.
How can I find out what is broken, and how do I get the data off the phone with CWM recovery? adb shell works and the data in /data, /system and /emmc still appears to be there, however I can't mount /sd-ext - cwm says "can't mount /dev/block/mmcblk1p2 /sd-ext (no such file).
dmesg shows this here:
<3>[ 7.713599] c0 mmc1: cmd 17 data timeout error
<3>[ 7.713903] c0 mmcblk1: error -110 transferring data, sector 5, nr 3, cmd response 0x900, card status 0x0
<3>[ 7.714072] c0 end_request: I/O error, dev mmcblk1, sector 5
<3>[ 9.225020] c0 mmc1: cmd 17 data timeout error
<3>[ 9.225481] c0 end_request: I/O error, dev mmcblk1, sector 7
<3>[ 9.981223] c0 mmc1: cmd 18 data timeout error
<3>[ 10.737259] c0 mmcblk1: error -110 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0
<3>[ 10.737431] c0 end_request: I/O error, dev mmcblk1, sector 0
<3>[ 11.493134] c0 end_request: I/O error, dev mmcblk1, sector 1
<3>[ 12.248358] c0 mmc1: cmd 17 data timeout error
<3>[ 12.248804] c0 end_request: I/O error, dev mmcblk1, sector 2
<3>[ 13.004323] c0 mmcblk1: error -110 transferring data, sector 3, nr 5, cmd response 0x900, card status 0x0
<3>[ 13.759713] c0 mmc1: cmd 17 data timeout error
<3>[ 13.759997] c0 mmcblk1: error -110 transferring data, sector 4, nr 4, cmd response 0x900, card status 0x0
<3>[ 14.515904] c0 mmc1: cmd 17 data timeout error
<3>[ 15.271589] c0 mmc1: cmd 17 data timeout error
<3>[ 17.539288] c0 mmc1: cmd 17 data timeout error
<3>[ 17.539595] c0 mmcblk1: error -110 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0
<3>[ 18.295005] c0 mmc1: cmd 17 data timeout error
<3>[ 18.295297] c0 mmcblk1: error -110 transferring data, sector 1, nr 7, cmd response 0x900, card status 0x0
<7>[ 18.725004] c0 usb: set_config_number single config
<7>[ 18.725108] c0 usb: set_interface_count next_interface_id=2
<7>[ 18.729004] c0 usb: set_config e mass_storage[0]
<7>[ 18.729131] c0 usb: set_config e adb[1]
<7>[ 18.729239] c0 usb: SET_CON
<7>[ 18.729487] c0 usb: android_work config=c0b77704,connected=1,sw_connected=1
<7>[ 18.730247] c0 usb: android_work sent uevent USB_STATE=CONFIGURED
<7>[ 20.098554] c0 usb: set_config_number single config
<7>[ 20.100774] c0 usb: set_config_number single config
<7>[ 20.100879] c0 usb: set_interface_count next_interface_id=2
<3>[ 21.317770] c0 mmc1: cmd 17 data timeout error
<3>[ 21.318081] c0 mmcblk1: error -110 transferring data, sector 5, nr 3, cmd response 0x900, card status 0x0
<3>[ 21.318253] c0 end_request: I/O error, dev mmcblk1, sector 5
<3>[ 22.073490] c0 mmc1: cmd 17 data timeout error
<3>[ 22.829455] c0 mmcblk1: error -110 transferring data, sector 7, nr 1, cmd response 0x900, card status 0x0
<3>[ 22.829743] c0 Buffer I/O error on device mmcblk1, logical block 0
Click to expand...
Click to collapse
To me this sounds like a dead SD card (can't test though, no other SD reader), but even without the SD card the phone refuses to boot :/
Any idea how to get at least the phone booting again or where to look for errors?
When doing a dmesg|grep mmc without the SD, I get
dmesg|grep mmc
<6>[ 2.035409] c1 dw_mmc dw_mmc: clock source 0: sclk_dwmci (80000000 Hz)
<3>[ 2.035839] c1 mmc0: Version ID 0x5342230a.
<6>[ 2.036227] c1 mmc0: FIFO WMARK FOR RX 0x20 WX 0x10. ###########
<6>[ 2.036920] c1 mmc0: MSHCI controller on samsung-mshci [dw_mmc] using IDMA
<6>[ 2.037542] c1 s3c-sdhci s3c-sdhci.2: clock source 2: sclk_mmc (8888888 Hz)
<6>[ 2.037914] c1 mmc1: vtf_2.8v regulator found
<7>[ 2.038207] c1 Registered led device: mmc1::
<6>[ 2.039448] c0 sdhci_set_ios : MMC Card ON samsung-hsmmc
<6>[ 2.039522] c0 mmc1: SDHCI controller on samsung-hsmmc [s3c-sdhci.2] using ADMA
<6>[ 2.039802] c0 mmc1: card removed.
<6>[ 2.039929] c0 s3c-sdhci s3c-sdhci.3: clock source 2: sclk_mmc (8888888 Hz)
<3>[ 2.040095] c0 mmc2: no vmmc regulator found
<7>[ 2.040405] c0 Registered led device: mmc2::
<6>[ 2.040749] c0 mmc2: SDHCI controller on samsung-hsmmc [s3c-sdhci.3] using ADMA
<3>[ 2.065390] c0 mmc0: cmd 52 response timeout error
<3>[ 2.065799] c0 mmc0: cmd 52 response timeout error
<3>[ 2.071569] c0 mmc0: cmd 8 response timeout error
<3>[ 2.071985] c0 mmc0: cmd 5 response timeout error
<3>[ 2.072351] c0 mmc0: cmd 5 response timeout error
<3>[ 2.072712] c0 mmc0: cmd 5 response timeout error
<3>[ 2.073074] c0 mmc0: cmd 5 response timeout error
<3>[ 2.073460] c0 mmc0: cmd 55 response timeout error
<3>[ 2.073840] c0 mmc0: cmd 55 response timeout error
<3>[ 2.074218] c0 mmc0: cmd 55 response timeout error
<3>[ 2.074596] c0 mmc0: cmd 55 response timeout error
<6>[ 2.096913] c0 mmc0: VYL00M: 15010056594c30304d196b9c70418ed1
<4>[ 2.109437] c0 mmc0: Voltage range not supported for power class.
<3>[ 2.109486] c0 mmc0: power class selection to bus width 8 failed
<4>[ 2.109746] c0 mmc0: Voltage range not supported for power class.
<3>[ 2.109795] c0 mmc0: power class selection to bus width 8 ddr 2 failed
<6>[ 2.110081] c0 mmc0: new high speed DDR MMC card at address 0001
<6>[ 2.110881] c0 mmcblk0: mmc0:0001 VYL00M 14.6 GiB
<6>[ 2.117703] c0 mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12
<6>[ 2.175199] c1 sdhci_set_ios : MMC Card OFF samsung-hsmmc
<6>[ 3.776696] c1 EXT4-fs (mmcblk0p9): recovery complete
<6>[ 3.776832] c1 EXT4-fs (mmcblk0p9): mounted filesystem with ordered data mode. Opts: (null)
<6>[ 4.001439] c0 EXT4-fs (mmcblk0p7): recovery complete
<6>[ 4.001574] c0 EXT4-fs (mmcblk0p7): mounted filesystem with ordered data mode. Opts: (null)
<4>[ 5.878636] c0 EXT4-fs (mmcblk0p10): warning: mounting fs with errors, running e2fsck is recommended
<6>[ 5.892909] c0 EXT4-fs (mmcblk0p10): recovery complete
<6>[ 5.892945] c0 EXT4-fs (mmcblk0p10): mounted filesystem with ordered data mode. Opts:
<6>[ 15.762233] c0 lun0: unable to open backing file: /dev/block/mmcblk1p1
<6>[ 15.762407] c0 lun1: unable to open backing file: /dev/block/mmcblk1p1
<6>[ 15.762519] c0 lun0: unable to open backing file: /dev/block/mmcblk1p1
<6>[ 15.762628] c0 lun1: unable to open backing file: /dev/block/mmcblk1p1
Click to expand...
Click to collapse
Boot into Philz recovery and make a nandroid backup. Make sure preload is included. Then go to wipe data factory reset. Choose clear before new rom install. Once done go to backup and restore and restore the nandroid you made. Then boot up. Check what happens.
nokiamodeln91 said:
Boot into Philz recovery and make a nandroid backup. Make sure preload is included. Then go to wipe data factory reset. Choose clear before new rom install. Once done go to backup and restore and restore the nandroid you made. Then boot up. Check what happens.
Click to expand...
Click to collapse
A nandroid backup would backup to the SD card, which is a) totally full and b) presumed dead, I'd need something that works over USB...
What can it be backed up to internal storage?
nokiamodeln91 said:
What can it be backed up to internal storage?
Click to expand...
Click to collapse
Internal storage is full to the brim, too, and I dont have any money left to buy other SD card. Also, won't the internal storage be overwritten by flashing ROM?
No. It will not be. Try cleaning the internal storage by mounting it in recovery using the mounts and storage menu and then mount usb storage. Then connect to pc. Check for drives
nokiamodeln91 said:
No. It will not be. Try cleaning the internal storage by mounting it in recovery using the mounts and storage menu and then mount usb storage. Then connect to pc. Check for drives
Click to expand...
Click to collapse
Yeah, I'm pulling the card contents now, will need two hours - lol, 2.8MB/s transfer speed! -.-
Looks like the memory has issues. I can not make a backup of /data - it always crashes somewhere. Either it locks up or it reboots without errormessage.
When doing a tar cvf /emmc/data.tar /data, it always crashes at data/log/dumpstate_ril_RESET_BY_CP_SILENTRESET_20130422194108.log; I'll just exclude data/log and try again - but is it possible that I have a defective memory chip?!
Try running a scan in recovery.
e2fsck - f - c - y /dev/block/mmcblk0p10
****. Apparently I have one of the broken ones:
/sys/devices/platform/dw_mmc/mmc_host/mmc0/mmc0:0001 # cat name hwrev fwrev manfid oemid date type serial cid
cat name hwrev fwrev manf
id oemid date type serial cid
VYL00M
0x0
0x0
0x000015
0x0100
08/2011
MMC
0x6b9c7041
15010056594c30304d196b9c70418ed1
Click to expand...
Click to collapse
Can I somehow scan for defective blocks and "blank" them like with badblocks on a PC?
Related
Hallo.
I have problem with enabling Wi-Fi.
I try lots of thing to fix it:
update radio 3 times,spl,software
backup from nandroid from 2 months ago
try with 3 difrent SD cards...
but wifi still don't work.
How to diagnose this problem,it's hardware or software?
it's copy of my issue from CM issues:
Code:
What steps will reproduce the problem?
1.Attempt to enable Wi-Fi
What do you see?
[B]Unable to start Wi-Fi[/B]
What did you expect to see?
[B]Wi-fi was enabled[/B]
Please include the following info from FASTBOOT mode
MODEL? DREA1100 PVT 32B
HBOOT? 0.95.0000
RADIO? 2.22.19.261
Which version of CyanogenMod? 4.1.6
Did you wipe before flashing? yes
Have you tried running fix_permissions? yes
Have you tried rebooting? yes
Please attach a logcat of the issue.
E/WifiService( 2004): Failed to load Wi-Fi driver.
D/SettingsWifiEnabler( 2443): Received wifi state changed from Unknown to
Enabling
D/SettingsWifiEnabler( 2443): Received wifi state changed from Enabling to
Unknown
Please provide any additional information below.
Wifi Cyanogenmod normally work in 4.1.6, I was connected to a wifi
network, because I moves ,lost my coverage of this network, when I wanted
to re-connect, system wrote to me "Unable
to enable wi-fi", I came home I did wipe, CM Uploader 4.1.9.2, wifi still
does not work, update to 4.1.10.1, I did wipe, fix_permission ... wifi
doesnt work...
<6>[ 212.900848] TIWLAN: Driver loading
<4>[ 212.907043] wifi_probe
<4>[ 212.909759] trout_wifi_power: 1
<4>[ 213.118225] trout_wifi_reset: 0
<4>[ 213.171936] trout_wifi_set_carddetect: 1
<7>[ 213.176422] mmc0: card_present 1
<6>[ 213.179931] mmc0: Slot status change detected (0 -> 1)
<3>[ 215.729705] mmc0: Command timeout
<3>[ 215.740417] mmc0: Command timeout
<3>[ 215.749969] mmc0: Command timeout
<3>[ 215.759490] mmc0: Command timeout
<3>[ 215.769287] mmc0: Command timeout
<3>[ 215.779052] mmc0: Command timeout
<3>[ 215.788818] mmc0: Command timeout
<3>[ 215.798583] mmc0: Command timeout
<3>[ 215.808624] mmc0: Command timeout
<3>[ 215.818969] mmc0: Command timeout
<3>[ 223.187896] tiwlan_module_init: Timed out waiting for device detect
<4>[ 223.195373] wifi_remove
<4>[ 223.198242] trout_wifi_set_carddetect: 0
<7>[ 223.202545] mmc0: card_present 0
<6>[ 223.208404] mmc0: Slot status change detected (1 -> 0)
<4>[ 223.214935] trout_wifi_reset: 1
<4>[ 223.272033] trout_wifi_power: 0
<4>[ 237.738372] msm_i2c msm_i2c.0: Warning bus was busy (3)
<4>[ 243.077178] wds: 0021 @ 01
<6>[ 243.080200] qmi: wds: network stopped
<6>[ 243.184936] rmnet_stop()
<4>[ 260.505035] wds: 0020 @ 01
<3>[ 260.508117] qmi: wds: network start failed (000e)
<4>[ 260.513275] wds: 0022 @ ff
<6>[ 260.524932] qmi: wds: DISCONNECTED
<6>[ 274.452270] TIWLAN: Driver loading
<4>[ 274.458374] wifi_probe
<4>[ 274.461273] trout_wifi_power: 1
<4>[ 274.669494] trout_wifi_reset: 0
<4>[ 274.723083] trout_wifi_set_carddetect: 1
<7>[ 274.727508] mmc0: card_present 1
<6>[ 274.730987] mmc0: Slot status change detected (0 -> 1)
<3>[ 277.279205] mmc0: Command timeout
<3>[ 277.288909] mmc0: Command timeout
<3>[ 277.299011] mmc0: Command timeout
<3>[ 277.308959] mmc0: Command timeout
<3>[ 277.319641] mmc0: Command timeout
<3>[ 277.330718] mmc0: Command timeout
<3>[ 277.341583] mmc0: Command timeout
<3>[ 277.352416] mmc0: Command timeout
<3>[ 277.362243] mmc0: Command timeout
<3>[ 277.371734] mmc0: Command timeout
<3>[ 284.735900] tiwlan_module_init: Timed out waiting for device detect
<4>[ 284.743316] wifi_remove
<4>[ 284.749725] trout_wifi_set_carddetect: 0
<7>[ 284.754089] mmc0: card_present 0
<6>[ 284.758148] mmc0: Slot status change detected (1 -> 0)
<4>[ 284.763793] trout_wifi_reset: 1
<4>[ 284.821655] trout_wifi_power: 0
Definitely sounds like hardware. Where did you get your G1?
in Polish operator, brand new one "Era G1"
before the last weekend Wifi work absolutly normal.
ps.
It is a good thread for technical issues??
Flash a different ROM/build... do a wipe and reformat your sd card... post back with results plx
kingklick said:
Flash a different ROM/build... do a wipe and reformat your sd card... post back with results plx
Click to expand...
Click to collapse
Don't post it here if you want to continue on XDA
dan0zone said:
Don't post it here if you want to continue on XDA
Click to expand...
Click to collapse
PM me, sorry forgot
i flashed my old nandroid backup...with difrent rom...still Wifi not work...I also try with 3 diffrent Sd card with ( 1 Fat32 or 1 Fat32 + Ext2 or Fat32 + Ext2 + Swap) stiil the same with wifi...
When i try "busybox insmod wlan.ko" i reciving "device not found"
I scared...that can be hardware problem...but this will be strange becouse , wifi before that issue work perfecly normal,phone never fall...i taking good care with it.
ps.
if i do something wrong with posting please tell me,becouse like You see..i register long time ago,but to today reading was enought to me...but now i first time need help...
Kashue said:
Hallo.
Sorry for posting the same post...in 2 places...but on Q&A wasn't any construtive answers...
I have problem with enabling Wi-Fi.
I try lots of thing to fix it:
update radio 3 times,spl,software
backup from nandroid from 2 months ago
try with 3 difrent SD cards...
but wifi still don't work.
How to diagnose this problem,it's hardware or software?
it's copy of my issue from CM issues:
Code:
What steps will reproduce the problem?
1.Attempt to enable Wi-Fi
What do you see?
[B]Unable to start Wi-Fi[/B]
What did you expect to see?
[B]Wi-fi was enabled[/B]
Please include the following info from FASTBOOT mode
MODEL? DREA1100 PVT 32B
HBOOT? 0.95.0000
RADIO? 2.22.19.261
Which version of CyanogenMod? 4.1.6
Did you wipe before flashing? yes
Have you tried running fix_permissions? yes
Have you tried rebooting? yes
Please attach a logcat of the issue.
E/WifiService( 2004): Failed to load Wi-Fi driver.
D/SettingsWifiEnabler( 2443): Received wifi state changed from Unknown to
Enabling
D/SettingsWifiEnabler( 2443): Received wifi state changed from Enabling to
Unknown
Please provide any additional information below.
Wifi Cyanogenmod normally work in 4.1.6, I was connected to a wifi
network, because I moves ,lost my coverage of this network, when I wanted
to re-connect, system wrote to me "Unable
to enable wi-fi", I came home I did wipe, CM Uploader 4.1.9.2, wifi still
does not work, update to 4.1.10.1, I did wipe, fix_permission ... wifi
doesnt work...
<6>[ 212.900848] TIWLAN: Driver loading
<4>[ 212.907043] wifi_probe
<4>[ 212.909759] trout_wifi_power: 1
<4>[ 213.118225] trout_wifi_reset: 0
<4>[ 213.171936] trout_wifi_set_carddetect: 1
<7>[ 213.176422] mmc0: card_present 1
<6>[ 213.179931] mmc0: Slot status change detected (0 -> 1)
<3>[ 215.729705] mmc0: Command timeout
<3>[ 215.740417] mmc0: Command timeout
<3>[ 215.749969] mmc0: Command timeout
<3>[ 215.759490] mmc0: Command timeout
<3>[ 215.769287] mmc0: Command timeout
<3>[ 215.779052] mmc0: Command timeout
<3>[ 215.788818] mmc0: Command timeout
<3>[ 215.798583] mmc0: Command timeout
<3>[ 215.808624] mmc0: Command timeout
<3>[ 215.818969] mmc0: Command timeout
<3>[ 223.187896] tiwlan_module_init: Timed out waiting for device detect
<4>[ 223.195373] wifi_remove
<4>[ 223.198242] trout_wifi_set_carddetect: 0
<7>[ 223.202545] mmc0: card_present 0
<6>[ 223.208404] mmc0: Slot status change detected (1 -> 0)
<4>[ 223.214935] trout_wifi_reset: 1
<4>[ 223.272033] trout_wifi_power: 0
<4>[ 237.738372] msm_i2c msm_i2c.0: Warning bus was busy (3)
<4>[ 243.077178] wds: 0021 @ 01
<6>[ 243.080200] qmi: wds: network stopped
<6>[ 243.184936] rmnet_stop()
<4>[ 260.505035] wds: 0020 @ 01
<3>[ 260.508117] qmi: wds: network start failed (000e)
<4>[ 260.513275] wds: 0022 @ ff
<6>[ 260.524932] qmi: wds: DISCONNECTED
<6>[ 274.452270] TIWLAN: Driver loading
<4>[ 274.458374] wifi_probe
<4>[ 274.461273] trout_wifi_power: 1
<4>[ 274.669494] trout_wifi_reset: 0
<4>[ 274.723083] trout_wifi_set_carddetect: 1
<7>[ 274.727508] mmc0: card_present 1
<6>[ 274.730987] mmc0: Slot status change detected (0 -> 1)
<3>[ 277.279205] mmc0: Command timeout
<3>[ 277.288909] mmc0: Command timeout
<3>[ 277.299011] mmc0: Command timeout
<3>[ 277.308959] mmc0: Command timeout
<3>[ 277.319641] mmc0: Command timeout
<3>[ 277.330718] mmc0: Command timeout
<3>[ 277.341583] mmc0: Command timeout
<3>[ 277.352416] mmc0: Command timeout
<3>[ 277.362243] mmc0: Command timeout
<3>[ 277.371734] mmc0: Command timeout
<3>[ 284.735900] tiwlan_module_init: Timed out waiting for device detect
<4>[ 284.743316] wifi_remove
<4>[ 284.749725] trout_wifi_set_carddetect: 0
<7>[ 284.754089] mmc0: card_present 0
<6>[ 284.758148] mmc0: Slot status change detected (1 -> 0)
<4>[ 284.763793] trout_wifi_reset: 1
<4>[ 284.821655] trout_wifi_power: 0
Click to expand...
Click to collapse
corp769
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Senior Member
Join Date: Feb 2009
Posts: 196
Definitely sounds like hardware. Where did you get your G1?
Someone did respond to you in a very constructive manner ???? please read the rules ..Q&A is there so therads like these don't get started here !!!!
in normal Polish operator "Era" , the phone was brand new.
if it be necessary i have a guarantee
Q&A are watching 30 people
Development over 300 it's beter chance to get answer
I recently had the same issue an posted my problem here on XDA and got the same answer. "Its probably the hardware" After flashing every rom I could think of even rc29 I decided to take my chances with returning it for a warranty exchange through my provider (T-mobile). I just called them up and acted completely dumb about it. Told them my problem and followed whatever they said they wanted me to do. After 3 calls back to them, they sent me a replacement free of charge. Just don't mention anything about flashing or root etc. Each G1 in under a 1 year warranty from the time of purchase. You should be fine
I had this problem with my phone having wiped it and pushed wpa_supplicant.conf to my phone.
Turns out the permissions of the file were incorrect which stopped the wifi from working.
chmod 777 /data/misc/wifi/wpa_supplicant.conf
fixed it temporarily, but needed to be done again after a reboot. I then tried chown system.wifi /data/misc/wifi/wpa_supplicant.conf
but by the time I rebooted I also had upgraded to the newest
CyanogenMod (4.1.11.1)
So maybe that fixed it instead...
I don't have wpa_suplicant.conf in /data/misc/wifi but i moved it from /system/etc/wifi/
Change permission to but wifi still don't work...on mondey i go to network provider about warianty.,but it's strange...how wifi broken?is fault of software or normal electronic bad manufacter part...
Network error,answer posted 2 times...sry
Kashue said:
in normal Polish operator "Era" , the phone was brand new.
if it be necessary i have a guarantee
Q&A are watching 30 people
Development over 300 it's beter chance to get answer
Click to expand...
Click to collapse
So you knowingly BROKE THE RULES OF THE FORUM?
You know that will get you banned, then you will get ZERO answers, right?
both threads have been merged
next time stick to the rules
problem solved
To bring wifi to work service use somthing like this:
"Rigid-Flex Board ASSY,Daughterboard,Dream" 51H10069-00M
There was no other way...using software...i was hardware problem,but I don't know why that happend...phone newer fall,or nothing similiar.
Mod can close topic,there will not be any more update.
I 've got the same problem with my G1.....
"Error" or "Unable to start Wifi".
It's hardware issue...
I tried to put my G1 at the freeze for about 2-3 hours.
After this, wifi worked for about 20 minutes...
I think Wifi chip on daughter board is burned and it's working only if it's cold...
(...when I mean cold, I mean an icy G1 )
The only solution is daughter's board replacement......
(...or apply some thermal grease on the chip ???????)
What do you think.....???????
Hi, I have been using a stable early version of CM5 on my T-Mobile G1 for about 5 months and one day (about 1 week ago) the WiFi failed while connecting to my home network, and since then, the WiFi has been in an error state; not being able to bee off or on. On the Power Widget, the WiFi indicator has a faded blue bar and even trying to enable it within the Android settings fails and says "error" as the state (as opposed to "Connected" or "Off").
I have tried rebooting, shutting down, removing the battery for a minute, and even wiping completely and re-flashing with CM 6.0 DS stable, yet the issue persists.
Oddly, when I do "netcgf" in the terminal emulator, I don't see a eth0 or wlan0 to tiwlan0 as a device. I only get this:
lo UP 127.0.0.1 255.0.0.0 0x00000049
dummy0 DOWN 0.0.0.0 0.0.0.0 0x00000082
ifb0 DOWN 0.0.0.0 0.0.0.0 0x00000082
ifb1 DOWN 0.0.0.0 0.0.0.0 0x00000082
rmnet0 DOWN 0.0.0.0 0.0.0.0 0x00001002
rmnet1 DOWN 0.0.0.0 0.0.0.0 0x00001002
rmnet2 DOWN 0.0.0.0 0.0.0.0 0x00001002
usb0 DOWN 0.0.0.0 0.0.0.0 0x00001002
So I though my wlan hardware was not initialized properly, so I went through dmesg and the driver seems to have loaded and encountered an error and then uloaded as seen by the following:
<6>[ 364.669433] TIWLAN: Driver loading
<4>[ 364.669952] wifi_probe
<4>[ 364.672363] trout_wifi_power: 1
<4>[ 364.859588] trout_wifi_reset: 0
<4>[ 364.902343] trout_wifi_set_carddetect: 1
<7>[ 364.902770] mmc0: card_present 1
<6>[ 364.902984] mmc0: Slot status change detected (0 -> 1)
<4>[ 367.466888] mmc0: card claims to support voltages below the defined range. These will be ignored.
<6>[ 367.473815] mmc0: new SDIO card at address 0001
<6>[ 367.481750] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 367.495544] TIWLAN: Driver initialized (rc 0)
<4>[ 367.497406] TIWLAN: 1251 PG 1.2
<6>[ 367.497924] TIWLAN: Driver loaded
<4>[ 367.916229] select 611 (android.protips), adj 9, size 3310, to kill
<4>[ 367.916900] send sigkill to 611 (android.protips), adj 9, size 3310
<3>[ 370.497741] mmc0: Data timeout
<3>[ 370.497863] SDIO_SyncRead: failed (-110)
<3>[ 370.498382] TIWLAN: TIWLAN: Failed to start config manager
<6>[ 387.593353] TIWLAN: Driver unloading
<6>[ 389.263336] TIWLAN: 4241.654203: sdio_reset_comm():
<4>[ 389.286865] mmc0: Error resetting SDIO communications (-110)
<7>[ 389.554901] TIWLAN: Releasing SDIO resources
<7>[ 389.557556] TIWLAN: SDIO resources released
<4>[ 389.560882] wifi_remove
<4>[ 389.561370] trout_wifi_set_carddetect: 0
This repeats a few times before the phone just gives up trying to load the driver.
Another instance later on of afailed attempt to load the driver is shown here:
TIWLAN: Driver loading
<4>[ 482.536315] wifi_probe
<4>[ 482.536773] trout_wifi_power: 1
<4>[ 482.767944] trout_wifi_reset: 0
<4>[ 482.815704] trout_wifi_set_carddetect: 1
<7>[ 482.815948] mmc0: card_present 1
<6>[ 482.816345] mmc0: Slot status change detected (0 -> 1)
<4>[ 485.376586] mmc0: card claims to support voltages below the defined range. These will be ignored.
<6>[ 485.380371] mmc0: new SDIO card at address 0001
<6>[ 485.387268] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 485.397033] TIWLAN: Driver initialized (rc 0)
<4>[ 485.398773] TIWLAN: 1251 PG 1.2
<6>[ 485.399230] TIWLAN: Driver loaded
<3>[ 487.699493] mmc0: Data timeout
<3>[ 487.699829] SDIO_SyncRead: failed (-110)
<3>[ 487.701110] TIWLAN: TIWLAN: Failed to start config manager
<4>[ 489.264953] select 704 (android.vending), adj 7, size 3865, to kill
<4>[ 489.265380] send sigkill to 704 (android.vending), adj 7, size 3865
<6>[ 505.471527] TIWLAN: Driver unloading
<6>[ 507.093597] TIWLAN: 64.402242: sdio_reset_comm():
<4>[ 507.117187] mmc0: Error resetting SDIO communications (-110)
<7>[ 507.379547] TIWLAN: Releasing SDIO resources
<7>[ 507.382232] TIWLAN: SDIO resources released
<4>[ 507.385589] wifi_remove
<4>[ 507.386077] trout_wifi_set_carddetect: 0
<7>[ 507.386901] mmc0: card_present 0
<6>[ 507.387359] mmc0: Slot status change detected (1 -> 0)
<6>[ 507.388397] mmc0: card 0001 removed
Has anyone experienced this and/or have a fix? It seems like I need to replace a file or two for the TIWLAN driver.
I have attached the entire dmesg from first boot of CM6 to now, which is about 5 minutes worth (not much).
Thanks a lot,
Mike
Sorry to bump this, but I would like some sort of guidance if I can fix this so I don't have to buy a new phone I love my G1. No keyboard compares.
I made some fixes, change some permissions and now I get one and only one error cosistenly in dmesg when trying to start the WiFi, and hence the TIWLAN driver.
<6>[31876.845947] TIWLAN: Driver loading
<4>[31876.846466] wifi_probe
<4>[31876.846832] trout_wifi_power: 1
<4>[31877.008209] trout_wifi_reset: 0
<4>[31877.049407] trout_wifi_set_carddetect: 1
<7>[31877.049682] mmc0: card_present 1
<6>[31877.049896] mmc0: Slot status change detected (0 -> 1)
<4>[31879.608001] mmc0: card claims to support voltages below the defined range.
These will be ignored.
<6>[31879.611785] mmc0: new SDIO card at address 0001
<6>[31879.623321] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[31879.637817] TIWLAN: Driver initialized (rc 0)
<4>[31879.638366] TIWLAN: 1251 PG 1.2
<6>[31879.638610] TIWLAN: Driver loaded
<3>[31880.067932] config_partition: Error writing size
<3>[31880.068664] TIWLAN: TIWLAN: Failed to start config manager
<6>[31899.710571] TIWLAN: Driver unloading
<6>[31901.334014] TIWLAN: 3652.788872: sdio_reset_comm():
<4>[31901.357391] mmc0: Error resetting SDIO communications (-110)
<7>[31901.620971] TIWLAN: Releasing SDIO resources
<7>[31901.627258] TIWLAN: SDIO resources released
<4>[31901.630523] wifi_remove
<4>[31901.631561] trout_wifi_set_carddetect: 0
<7>[31901.632049] mmc0: card_present 0
<6>[31901.632507] mmc0: Slot status change detected (1 -> 0)
<6>[31901.633911] mmc0: card 0001 removed
<4>[31901.639007] trout_wifi_reset: 1
<4>[31901.682708] trout_wifi_power: 0
<6>[31901.848754] TIWLAN: Driver unloaded
The culprits are
<3>[31880.067932] config_partition: Error writing size
<3>[31880.068664] TIWLAN: TIWLAN: Failed to start config manager
I have no idea why the partition size is trying to be written (or perhaps the file size of the config file?) but that is preventing what would otherwise be a smooth loading of the WiFi driver.
If anyone has any suggestions or can provide any help, I would greatly appreciate it!
Thanks in advance,
Mike
Same here
gtabmx said:
Hi, I have been using a stable early version of CM5 on my T-Mobile G1 for about 5 months and one day (about 1 week ago) the WiFi failed while connecting to my home network, and since then, the WiFi has been in an error state; not being able to bee off or on. On the Power Widget, the WiFi indicator has a faded blue bar and even trying to enable it within the Android settings fails and says "error" as the state (as opposed to "Connected" or "Off").
I have tried rebooting, shutting down, removing the battery for a minute, and even wiping completely and re-flashing with CM 6.0 DS stable, yet the issue persists.
Oddly, when I do "netcgf" in the terminal emulator, I don't see a eth0 or wlan0 to tiwlan0 as a device. I only get this:
lo UP 127.0.0.1 255.0.0.0 0x00000049
dummy0 DOWN 0.0.0.0 0.0.0.0 0x00000082
ifb0 DOWN 0.0.0.0 0.0.0.0 0x00000082
ifb1 DOWN 0.0.0.0 0.0.0.0 0x00000082
rmnet0 DOWN 0.0.0.0 0.0.0.0 0x00001002
rmnet1 DOWN 0.0.0.0 0.0.0.0 0x00001002
rmnet2 DOWN 0.0.0.0 0.0.0.0 0x00001002
usb0 DOWN 0.0.0.0 0.0.0.0 0x00001002
So I though my wlan hardware was not initialized properly, so I went through dmesg and the driver seems to have loaded and encountered an error and then uloaded as seen by the following:
<6>[ 364.669433] TIWLAN: Driver loading
<4>[ 364.669952] wifi_probe
<4>[ 364.672363] trout_wifi_power: 1
<4>[ 364.859588] trout_wifi_reset: 0
<4>[ 364.902343] trout_wifi_set_carddetect: 1
<7>[ 364.902770] mmc0: card_present 1
<6>[ 364.902984] mmc0: Slot status change detected (0 -> 1)
<4>[ 367.466888] mmc0: card claims to support voltages below the defined range. These will be ignored.
<6>[ 367.473815] mmc0: new SDIO card at address 0001
<6>[ 367.481750] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 367.495544] TIWLAN: Driver initialized (rc 0)
<4>[ 367.497406] TIWLAN: 1251 PG 1.2
<6>[ 367.497924] TIWLAN: Driver loaded
<4>[ 367.916229] select 611 (android.protips), adj 9, size 3310, to kill
<4>[ 367.916900] send sigkill to 611 (android.protips), adj 9, size 3310
<3>[ 370.497741] mmc0: Data timeout
<3>[ 370.497863] SDIO_SyncRead: failed (-110)
<3>[ 370.498382] TIWLAN: TIWLAN: Failed to start config manager
<6>[ 387.593353] TIWLAN: Driver unloading
<6>[ 389.263336] TIWLAN: 4241.654203: sdio_reset_comm():
<4>[ 389.286865] mmc0: Error resetting SDIO communications (-110)
<7>[ 389.554901] TIWLAN: Releasing SDIO resources
<7>[ 389.557556] TIWLAN: SDIO resources released
<4>[ 389.560882] wifi_remove
<4>[ 389.561370] trout_wifi_set_carddetect: 0
This repeats a few times before the phone just gives up trying to load the driver.
Another instance later on of afailed attempt to load the driver is shown here:
TIWLAN: Driver loading
<4>[ 482.536315] wifi_probe
<4>[ 482.536773] trout_wifi_power: 1
<4>[ 482.767944] trout_wifi_reset: 0
<4>[ 482.815704] trout_wifi_set_carddetect: 1
<7>[ 482.815948] mmc0: card_present 1
<6>[ 482.816345] mmc0: Slot status change detected (0 -> 1)
<4>[ 485.376586] mmc0: card claims to support voltages below the defined range. These will be ignored.
<6>[ 485.380371] mmc0: new SDIO card at address 0001
<6>[ 485.387268] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 485.397033] TIWLAN: Driver initialized (rc 0)
<4>[ 485.398773] TIWLAN: 1251 PG 1.2
<6>[ 485.399230] TIWLAN: Driver loaded
<3>[ 487.699493] mmc0: Data timeout
<3>[ 487.699829] SDIO_SyncRead: failed (-110)
<3>[ 487.701110] TIWLAN: TIWLAN: Failed to start config manager
<4>[ 489.264953] select 704 (android.vending), adj 7, size 3865, to kill
<4>[ 489.265380] send sigkill to 704 (android.vending), adj 7, size 3865
<6>[ 505.471527] TIWLAN: Driver unloading
<6>[ 507.093597] TIWLAN: 64.402242: sdio_reset_comm():
<4>[ 507.117187] mmc0: Error resetting SDIO communications (-110)
<7>[ 507.379547] TIWLAN: Releasing SDIO resources
<7>[ 507.382232] TIWLAN: SDIO resources released
<4>[ 507.385589] wifi_remove
<4>[ 507.386077] trout_wifi_set_carddetect: 0
<7>[ 507.386901] mmc0: card_present 0
<6>[ 507.387359] mmc0: Slot status change detected (1 -> 0)
<6>[ 507.388397] mmc0: card 0001 removed
Has anyone experienced this and/or have a fix? It seems like I need to replace a file or two for the TIWLAN driver.
I have attached the entire dmesg from first boot of CM6 to now, which is about 5 minutes worth (not much).
Thanks a lot,
Mike
Click to expand...
Click to collapse
I'm having the same problem. I've done a factory reset and went to wifi settings. As soon as I tried to turn on the wifi again the word "error" came back.
Someone please help
Same here. mine started this sh*t 2 days ago. been runnin cm6.1.1 for bout 3 weeks now.
Hi,
I face the same issue with my developer phone 2..
Okay.. it resumed after factory data reset!
A more detailed survey of this error can be found on the android-tether developer website.. I cannot post links as i am a new member here... But it can be found as the first google link for the search string "google code issue 1124"
So i have two nexus's one is perfect. However I also have my old one (before htc sent me the new one) it has a major problem were the phone will usually not boot and if it does after a few minutes of use will reboot and vibrate a bunch of times.
So what do you guys think could be the problem??? I'm thinking the logic board?
I'm asking because i am thinking about fixing it myself
Do an ADB logcat.
The phone doesn't have to completely boot to start it. This is the best way to determine at what point the phone stops. I use these when I get a boot loop.
K I will try that and post back
Sent from my Nexus One using XDA App
Search the forum using "vibrations" keyword.
Ok so i plugged her in and it booted up. So i ran adb logcat and started messing around. It crashed while recording this is the last couple lines... I don't know how to copy from cmd???? So have type it out
Code:
E/CameraInput < 59>: Recording is not ready <iPeer 0x1fc94 iState 2 iWriteState
1 iClockState 0>, frame dropped
I/AudioHardwareQSD< 59>: AudioHardware pcm playback is going to standby.
And that's it thats last thing before it crashed and turned off... Any ideas what means in english? something about audio but i don't know if that is realated
EDIT: And yes it is the seven vibrations problem
What radio are you using?
Jack_R1 said:
What radio are you using?
Click to expand...
Click to collapse
5.12 right now but i have tried all of them. Same problem. Almost all the kernels and roms too. from stock to cyanogen to miui.
Non make a difference. The phone clearly has a hardware problem i just want to identify which piece of hardware
"adb bugreport" will help much more.
Also, "cat /proc/kmsg" and "cat /proc/last_kmsg", too.
Clear cache
Sent from my Nexus One using XDA App
I have cleared cache a hundred times...
I am going to try the other adb commands
Tech_Boy said:
Ok so i plugged her in and it booted up. So i ran adb logcat and started messing around.
It crashed while recording this is the last couple lines... I don't know how to copy from cmd???? So have type it out
Click to expand...
Click to collapse
Right click anywhere in the window itself and select: edit, then select all
After everything is highlighted again right click on anywhere on the window and select: edit, then copy
You can then paste this into a notepad to edit it, or whatever.
Also as mentioned, try adb bugreport as well that could help.
Ok this is what i got. I don't understand much of it, so i don't know what i am looking for.
I ran the first two the third gave a file no found error... Also I notice cmd didn't copy the whole thing, like when it reaches a certain amount of lines it cuts off the top stuff
Code:
en=1 layout=34 uiMode=17 seq=4}
mShownFrame=[0,0][480,800] last=[0,0][480,800]
mFrame=[0,0][480,800] last=[0,0][480,800]
mContainingFrame=[0,0][480,800] mDisplayFrame=[0,0][480,800]
mContentFrame=[0,38][480,800] mVisibleFrame=[0,38][480,800]
mContentInsets=[0,38][0,0] last=[0,38][0,0] mVisibleInsets=[0,38][0,0] last=
[0,38][0,0]
mDrawPending=false mCommitDrawPending=false mReadyToShow=false mHasDrawn=tru
e
Window #2 Window{44ac0690 SurfaceView paused=false}:
mSession=Session{44b399c8 uid 10028} [email protected]
mAttrs=WM.LayoutParams{(0,38)(480x762) gr=#33 ty=1000 fl=#24218 fmt=-3}
mAttachedWindow=Window{44b7ce48 com.android.launcher/com.android.launcher2.L
auncher paused=false} mLayoutAttached=true
mBaseLayer=21000 mSubLayer=1 mAnimLayer=21010+0=21010 mLastLayer=21010
mToken=WindowToken{44ac0630 [email protected]}
mRootToken=AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.
launcher/com.android.launcher2.Launcher}}
mAppToken=AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.l
auncher/com.android.launcher2.Launcher}}
mViewVisibility=0x8 mLastHidden=true mHaveFrame=true mObscured=true
mPolicyVisibility=true mPolicyVisibilityAfterAnim=true mAttachedHidden=true
Requested w=480 h=762 mLayoutSeq=316
mGivenContentInsets=[0,0][0,0] mGivenVisibleInsets=[0,0][0,0]
mConfiguration={ scale=1.0 imsi=0/0 loc=en_US touch=3 keys=1/1/2 nav=3/1 ori
en=1 layout=34 uiMode=17 seq=4}
mShownFrame=[0,38][480,800] last=[0,38][480,800]
mFrame=[0,38][480,800] last=[0,38][480,800]
mContainingFrame=[0,0][480,800] mDisplayFrame=[-10000,-10000][10000,10000]
mContentFrame=[0,38][480,800] mVisibleFrame=[0,38][480,800]
mContentInsets=[0,0][0,0] last=[0,0][0,0] mVisibleInsets=[0,0][0,0] last=[0,
0][0,0]
mDrawPending=false mCommitDrawPending=false mReadyToShow=false mHasDrawn=tru
e
Window #1 Window{44b7ce48 com.android.launcher/com.android.launcher2.Launcher
paused=false}:
mSession=Session{44b399c8 uid 10028} [email protected]
mAttrs=WM.LayoutParams{(0,0)(fillxfill) sim=#20 ty=1 fl=#110100 fmt=-2 wanim
=0x1030001}
mBaseLayer=21000 mSubLayer=0 mAnimLayer=21005+0=21005 mLastLayer=21005
mToken=AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.laun
cher/com.android.launcher2.Launcher}}
mRootToken=AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.
launcher/com.android.launcher2.Launcher}}
mAppToken=AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.l
auncher/com.android.launcher2.Launcher}}
mViewVisibility=0x8 mLastHidden=true mHaveFrame=true mObscured=true
Requested w=480 h=800 mLayoutSeq=316
mGivenContentInsets=[0,0][0,0] mGivenVisibleInsets=[0,0][0,0]
mConfiguration={ scale=1.0 imsi=0/0 loc=en_US touch=3 keys=1/1/2 nav=3/1 ori
en=1 layout=34 uiMode=17 seq=4}
mShownFrame=[0,0][480,800] last=[0,0][480,800]
mFrame=[0,0][480,800] last=[0,0][480,800]
mContainingFrame=[0,0][480,800] mDisplayFrame=[0,0][480,800]
mContentFrame=[0,38][480,800] mVisibleFrame=[0,38][480,800]
mContentInsets=[0,38][0,0] last=[0,38][0,0] mVisibleInsets=[0,38][0,0] last=
[0,38][0,0]
mDrawPending=false mCommitDrawPending=false mReadyToShow=false mHasDrawn=tru
e
mWallpaperX=0.5 mWallpaperY=0.0
mWallpaperXStep=0.25 mWallpaperYStep=0.0
Window #0 Window{44aa38e8 com.android.wallpaper.nexus.NexusWallpaper paused=fa
lse}:
mSession=Session{44a8e370 uid 10029} [email protected]
mAttrs=WM.LayoutParams{(0,0)(fillxfill) gr=#33 ty=2013 fl=#318 fmt=-1 wanim=
0x1030075}
mIsImWindow=false mIsWallpaper=true mIsFloatingLayer=true mWallpaperVisible=
false
mBaseLayer=21000 mSubLayer=0 mAnimLayer=21000+0=21000 mLastLayer=21000
mSurface=Surface(name=com.android.wallpaper.nexus.NexusWallpaper, identity=4
)
Surface: shown=false layer=21000 alpha=1.0 rect=(0,0) 480 x 800
mToken=WindowToken{449909f0 [email protected]}
mRootToken=WindowToken{449909f0 [email protected]}
mViewVisibility=0x0 mLastHidden=true mHaveFrame=true mObscured=true
Requested w=-1 h=-1 mLayoutSeq=318
mGivenContentInsets=[0,0][0,0] mGivenVisibleInsets=[0,0][0,0]
mConfiguration={ scale=1.0 imsi=0/0 loc=en_US touch=3 keys=1/1/2 nav=3/1 ori
en=1 layout=34 uiMode=17 seq=4}
mShownFrame=[0,0][480,800] last=[0,0][480,800]
mFrame=[0,0][480,800] last=[0,0][480,800]
mContainingFrame=[0,0][480,800] mDisplayFrame=[-10000,-10000][10000,10000]
mContentFrame=[0,0][480,800] mVisibleFrame=[0,0][480,800]
mContentInsets=[0,0][0,0] last=[0,0][0,0] mVisibleInsets=[0,0][0,0] last=[0,
0][0,0]
mAnimating=false mLocalAnimating=false mAnimationIsEntrance=true mAnimation=
null
mDrawPending=false mCommitDrawPending=false mReadyToShow=false mHasDrawn=tru
e
mWallpaperX=0.5 mWallpaperY=0.0
mWallpaperXStep=0.25 mWallpaperYStep=0.0
All active sessions:
Session Session{44bcab88 uid 1000}:
mNumWindow=3 mClientDead=false [email protected]
4a1cd90
Session Session{44b399c8 uid 10028}:
mNumWindow=2 mClientDead=false [email protected]
49a1ed8
Session Session{44a8e370 uid 10029}:
mNumWindow=1 mClientDead=false [email protected]
4960760
Session Session{44ac1528 uid 10018}:
mNumWindow=0 mClientDead=false [email protected]
49c5ee0
Session Session{44af3498 uid 1000}:
mNumWindow=3 mClientDead=false [email protected]
4af4eb8
All tokens:
Token null:
token=null
windows=[Window{44af4960 StatusBar paused=false}, Window{44b24fa0 TrackingVi
ew paused=false}, Window{44af8488 StatusBarExpanded paused=false}]
windowType=-1 hidden=false hasVisible=true
Token [email protected]:
[email protected]
windows=[]
windowType=2011 hidden=false hasVisible=false
Token HistoryRecord{44b27e28 com.android.launcher/com.android.launcher2.Launch
er}:
token=HistoryRecord{44b27e28 com.android.launcher/com.android.launcher2.Laun
cher}
windows=[Window{44b7ce48 com.android.launcher/com.android.launcher2.Launcher
paused=false}]
windowType=2 hidden=true hasVisible=true
app=true
allAppWindows=[Window{44b7ce48 com.android.launcher/com.android.launcher2.La
uncher paused=false}, Window{44ac0690 SurfaceView paused=false}]
groupId=5 appFullscreen=true requestedOrientation=5
hiddenRequested=true clientHidden=true willBeHidden=false reportedVisible=fa
lse
numInterestingWindows=3 numDrawnWindows=3 inPendingTransaction=false allDraw
n=true
startingData=null removed=false firstWindowDrawn=true
Token [email protected]:
[email protected]
windows=[Window{44aa38e8 com.android.wallpaper.nexus.NexusWallpaper paused=f
alse}]
windowType=2013 hidden=true hasVisible=true
Token HistoryRecord{44ae2d88 com.android.settings/.DevelopmentSettings}:
token=HistoryRecord{44ae2d88 com.android.settings/.DevelopmentSettings}
windows=[Window{44b4d8a0 com.android.settings/com.android.settings.Developme
ntSettings paused=false}]
windowType=2 hidden=false hasVisible=true
app=true
allAppWindows=[Window{44b4d8a0 com.android.settings/com.android.settings.Dev
elopmentSettings paused=false}]
groupId=6 appFullscreen=true requestedOrientation=-1
hiddenRequested=false clientHidden=false willBeHidden=false reportedVisible=
false
numInterestingWindows=2 numDrawnWindows=2 inPendingTransaction=false allDraw
n=true
startingData=null removed=false firstWindowDrawn=true
Token [email protected]:
[email protected]
windows=[Window{44ac0690 SurfaceView paused=false}]
windowType=-1 hidden=false hasVisible=true
Token HistoryRecord{44afab70 com.android.setupwizard/.SetupWizardActivity}:
token=HistoryRecord{44afab70 com.android.setupwizard/.SetupWizardActivity}
windows=[]
windowType=2 hidden=true hasVisible=true
app=true
groupId=2 appFullscreen=true requestedOrientation=-1
hiddenRequested=true clientHidden=true willBeHidden=false reportedVisible=fa
lse
numInterestingWindows=1 numDrawnWindows=1 inPendingTransaction=false allDraw
n=true
Token HistoryRecord{44a9bb18 com.android.settings/.ApplicationSettings}:
token=HistoryRecord{44a9bb18 com.android.settings/.ApplicationSettings}
windows=[Window{44b446f8 com.android.settings/com.android.settings.Applicati
onSettings paused=false}]
windowType=2 hidden=true hasVisible=true
app=true
allAppWindows=[Window{44b446f8 com.android.settings/com.android.settings.App
licationSettings paused=false}]
groupId=6 appFullscreen=true requestedOrientation=-1
hiddenRequested=true clientHidden=true willBeHidden=false reportedVisible=fa
lse
numInterestingWindows=1 numDrawnWindows=1 inPendingTransaction=false allDraw
n=true
startingData=null removed=false firstWindowDrawn=true
Token HistoryRecord{44beca80 com.android.settings/.Settings}:
token=HistoryRecord{44beca80 com.android.settings/.Settings}
windows=[Window{44b2c1d8 com.android.settings/com.android.settings.Settings
paused=false}]
windowType=2 hidden=true hasVisible=true
app=true
allAppWindows=[Window{44b2c1d8 com.android.settings/com.android.settings.Set
tings paused=false}]
groupId=6 appFullscreen=true requestedOrientation=-1
hiddenRequested=true clientHidden=true willBeHidden=false reportedVisible=fa
lse
numInterestingWindows=1 numDrawnWindows=1 inPendingTransaction=false allDraw
n=true
startingData=null removed=false firstWindowDrawn=true
startingWindow=null startingView=null startingDisplayed=true startingMovedfa
lse
Window token list:
#0: WindowToken{44af47b0 token=null}
#1: AppWindowToken{44afc5a8 token=HistoryRecord{44afab70 com.android.setupwiza
rd/.SetupWizardActivity}}
#2: WindowToken{449909f0 [email protected]}
#3: WindowToken{44ae24d0 [email protected]}
#4: AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.launcher/
com.android.launcher2.Launcher}}
#5: WindowToken{44ac0630 [email protected]}
#6: AppWindowToken{44becd60 token=HistoryRecord{44beca80 com.android.settings/
.Settings}}
#7: AppWindowToken{44becb90 token=HistoryRecord{44a9bb18 com.android.settings/
.ApplicationSettings}}
#8: AppWindowToken{44bd6e30 token=HistoryRecord{44ae2d88 com.android.settings/
.DevelopmentSettings}}
Wallpaper tokens:
Wallpaper #0 WindowToken{449909f0 [email protected]}:
[email protected]
windows=[Window{44aa38e8 com.android.wallpaper.nexus.NexusWallpaper paused=f
alse}]
windowType=2013 hidden=true hasVisible=true
Application tokens in Z order:
App #4: AppWindowToken{44bd6e30 token=HistoryRecord{44ae2d88 com.android.setti
ngs/.DevelopmentSettings}}
App #3: AppWindowToken{44becb90 token=HistoryRecord{44a9bb18 com.android.setti
ngs/.ApplicationSettings}}
App #2: AppWindowToken{44becd60 token=HistoryRecord{44beca80 com.android.setti
ngs/.Settings}}
App #1: AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.launc
her/com.android.launcher2.Launcher}}
App #0: AppWindowToken{44afc5a8 token=HistoryRecord{44afab70 com.android.setup
wizard/.SetupWizardActivity}}
mCurrentFocus=Window{44b4d8a0 com.android.settings/com.android.settings.Develo
pmentSettings paused=false}
mLastFocus=Window{44b4d8a0 com.android.settings/com.android.settings.Developme
ntSettings paused=false}
mFocusedApp=AppWindowToken{44bd6e30 token=HistoryRecord{44ae2d88 com.android.s
ettings/.DevelopmentSettings}}
mInputMethodTarget=null
mInputMethodWindow=null
mWallpaperTarget=null
mCurConfiguration={ scale=1.0 imsi=0/0 loc=en_US touch=3 keys=1/1/2 nav=3/1 or
ien=1 layout=34 uiMode=17 seq=4}
mInTouchMode=true mLayoutSeq=345
mSystemBooted=true mDisplayEnabled=true
mLayoutNeeded=false mBlurShown=false
mDimShown=true current=0.0 target=0.0 delta=-0.004 lastAnimTime=0
mInputMethodAnimLayerAdjustment=0 mWallpaperAnimLayerAdjustment=0
mLastWallpaperX=0.5 mLastWallpaperY=0.0
mDisplayFrozen=false mWindowsFreezingScreen=false mAppsFreezingScreen=0 mWaiti
ngForConfig=false
mRotation=0, mForcedAppOrientation=-1, mRequestedRotation=0
mAnimationPending=false mWindowAnimationScale=1.0 mTransitionWindowAnimationSc
ale=1.0
mNextAppTransition=0xffffffff, mAppTransitionReady=false, mAppTransitionRunnin
g=false, mAppTransitionTimeout=false
mStartingIconInTransition=false, mSkipAppTransitionAnimation=false
mLastEnterAnimToken=AppWindowToken{44bd6e30 token=HistoryRecord{44ae2d88 com.a
ndroid.settings/.DevelopmentSettings}}, mLastEnterAnimParams=WM.LayoutParams{(0,
0)(fillxfill) sim=#110 ty=1 fl=#10100 fmt=-1 wanim=0x1030001}
DisplayWidth=480 DisplayHeight=800
KeyWaiter state:
mLastWin=null mLastBinder=null
mFinished=true mGotFirstWindow=true mEventDispatching=true mTimeToSwitch=0
[dumpsys: 3.3s elapsed]
C:\android-sdk-windows\tools>
Code:
<6>[ 5.608520] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 64000000 Hz
<6>[ 5.608764] mmc0: Slot eject status = 1
<6>[ 5.608886] mmc0: Power save feature enable = 1
<6>[ 5.609039] mmc0: DM non-cached buffer at ffa04000, dma_addr 0x279bd000
<6>[ 5.609283] mmc0: DM cmd busaddr 0x279bd000, cmdptr busaddr 0x279bd300
<6>[ 5.610229] mmc1: Qualcomm MSM SDCC at 0x00000000a0400000 irq 26,0 dma 8
<6>[ 5.610443] mmc1: 4 bit data mode enabled
<6>[ 5.610595] mmc1: MMC clock 144000 -> 50000000 Hz, PCLK 64000000 Hz
<6>[ 5.610839] mmc1: Slot eject status = 0
<6>[ 5.610961] mmc1: Power save feature enable = 1
<6>[ 5.611206] mmc1: DM non-cached buffer at ffa05000, dma_addr 0x279be000
<6>[ 5.611328] mmc1: DM cmd busaddr 0x279be000, cmdptr busaddr 0x279be300
<6>[ 5.612396] logger: created 64K log 'log_main'
<6>[ 5.612640] logger: created 256K log 'log_events'
<6>[ 5.612945] logger: created 64K log 'log_radio'
<6>[ 5.613128] logger: created 64K log 'log_system'
<4>[ 5.613586] GACT probability NOT on
<4>[ 5.613800] Mirror/redirect action on
<4>[ 5.613952] u32 classifier
<4>[ 5.614074] Actions configured
<4>[ 5.614318] Netfilter messages via NETLINK v0.30.
<4>[ 5.614501] nf_conntrack version 0.5.0 (6171 buckets, 24684 max)
<4>[ 5.614929] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Plea
se use
<4>[ 5.615081] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack modu
le option or
<4>[ 5.615295] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
<4>[ 5.615570] ctnetlink v0.93: registering with nfnetlink.
<6>[ 5.616058] xt_time: kernel timezone is -0000
<6>[ 5.616394] ip_tables: (C) 2000-2006 Netfilter Core Team
<6>[ 5.616729] arp_tables: (C) 2002 David S. Miller
<6>[ 5.616943] TCP cubic registered
<6>[ 5.617279] NET: Registered protocol family 10
<6>[ 5.617980] lo: Disabled Privacy Extensions
<6>[ 5.618896] Mobile IPv6
<6>[ 5.619049] IPv6 over IPv4 tunneling driver
<6>[ 5.619720] sit0: Disabled Privacy Extensions
<6>[ 5.620330] ip6tnl0: Disabled Privacy Extensions
<6>[ 5.620666] NET: Registered protocol family 17
<6>[ 5.620819] NET: Registered protocol family 15
<6>[ 5.620971] Bluetooth: L2CAP ver 2.14
<6>[ 5.621215] Bluetooth: L2CAP socket layer initialized
<6>[ 5.621337] Bluetooth: SCO (Voice Link) ver 0.6
<6>[ 5.621582] Bluetooth: SCO socket layer initialized
<6>[ 5.621917] Bluetooth: RFCOMM TTY layer initialized
<6>[ 5.622070] Bluetooth: RFCOMM socket layer initialized
<6>[ 5.622314] Bluetooth: RFCOMM ver 1.11
<6>[ 5.622436] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
<6>[ 5.622680] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
<6>[ 5.622894] ThumbEE CPU extension supported.
<6>[ 5.623596] clock_late_init() disabled 18 unused clocks
<4>[ 5.623809] mahimahi_wifi_init: start
<6>[ 5.624206] VFP support v0.3: implementor 51 architecture 0 part 0f varian
t 0 rev 1
<4>[ 5.652435] regulator_init_complete: incomplete constraints, leaving ldo2
on
<4>[ 5.653320] regulator_init_complete: incomplete constraints, leaving ldo1
on
<4>[ 5.654083] regulator_init_complete: incomplete constraints, leaving dcdc3
on
<4>[ 5.654968] regulator_init_complete: incomplete constraints, leaving dcdc2
on
<4>[ 5.655853] regulator_init_complete: incomplete constraints, leaving dcdc1
on
<6>[ 5.657379] rs30000048:00010000 rs30000048:00010000: setting system clock
to 2010-11-23 19:51:55 UTC (1290541915)
<6>[ 5.657714] Freeing init memory: 120K
<4>[ 5.657867] Warning: unable to open an initial console.
<6>[ 5.745422] keychord: using input dev h2w headset for fevent
<6>[ 5.745574] keychord: using input dev mahimahi-keypad for fevent
<6>[ 5.745971] keychord: using input dev mahimahi-nav for fevent
<6>[ 5.748168] yaffs: dev is 32505859 name is "mtdblock3"
<6>[ 5.748443] yaffs: passed flags ""
<4>[ 5.748565] yaffs: Attempting MTD mount on 31.3, "mtdblock3"
<4>[ 5.915313] mmc1: host does not support reading read-only switch. assuming
write-enable.
<6>[ 5.915496] mmc1: new high speed SDHC card at address aaaa
<6>[ 5.916229] mmcblk0: mmc1:aaaa SU04G 3.69 GiB
<6>[ 5.916625] mmcblk0: p1
<4>[ 5.956512] yaffs: restored from checkpoint
<4>[ 5.956970] yaffs_read_super: isCheckpointed 1
<6>[ 5.996093] yaffs: dev is 32505861 name is "mtdblock5"
<6>[ 5.996337] yaffs: passed flags ""
<4>[ 5.996459] yaffs: Attempting MTD mount on 31.5, "mtdblock5"
<6>[ 6.100860] batt: 83%, 4030 mV, -237 mA (0 avg), 27.0 C, 1128 mAh
<6>[ 6.108581] batt: charging OFF
<4>[ 6.298553] block 164 is bad
<4>[ 6.373718] block 410 is bad
<4>[ 6.429870] block 594 is bad
<4>[ 6.436859] block 617 is bad
<4>[ 6.514953] block 873 is bad
<4>[ 6.581939] block 1092 is bad
<4>[ 6.585266] block 1103 is bad
<4>[ 6.612121] block 1191 is bad
<4>[ 6.626129] block 1237 is bad
<4>[ 7.622741] yaffs_read_super: isCheckpointed 0
<6>[ 7.628631] yaffs: dev is 32505860 name is "mtdblock4"
<6>[ 7.628753] yaffs: passed flags ""
<4>[ 7.628997] yaffs: Attempting MTD mount on 31.4, "mtdblock4"
<4>[ 7.773559] block 93 is bad
<4>[ 7.794616] block 162 is bad
<4>[ 7.836578] block 299 is bad
<4>[ 7.836853] block 300 is bad
<4>[ 7.903015] block 519 is bad
<4>[ 7.987426] yaffs_read_super: isCheckpointed 0
<3>[ 8.017700] init: service 'console' requires console
<3>[ 8.062011] init: cannot execve('/system/etc/install-recovery.sh'): Permis
sion denied
<3>[ 8.110382] init: cannot find '/system/bin/dspcrashd', disabling 'dspcrash
d'
<6>[ 8.125823] acpuclk_set_vdd_level got regulator
<6>[ 8.545745] warning: `rild' uses 32-bit capabilities (legacy support in us
e)
<6>[ 8.679840] SMD: ch 0 1 -> 2
<6>[ 8.681640] qmi: smd closed
<6>[ 8.682006] SMD: ch 50 1 -> 2
<6>[ 8.682312] qmi: smd opened
<6>[ 8.683135] qmi: smd closed
<6>[ 8.683471] SMD: ch 51 1 -> 2
<6>[ 8.683807] qmi: smd opened
<6>[ 8.684265] qmi: ctl: wds use client_id 0x01
<6>[ 8.684936] qmi: ctl: wds use client_id 0x01
<6>[ 8.685455] qmi: smd closed
<6>[ 8.685913] SMD: ch 52 1 -> 2
<6>[ 8.686523] qmi: smd opened
<6>[ 8.687438] qmi: ctl: wds use client_id 0x01
<6>[ 9.907592] a1026_bootup_init: starting to load image (863 passes)...
<6>[ 12.805664] a1026_bootup_init: firmware loaded successfully
<6>[ 12.966003] a1026_bootup_init: initialized!
<6>[ 12.968688] htc-acoustic: open
<3>[ 12.969726] smd_alloc_channel() cid 41 does not exist
<3>[ 12.969848] smd_alloc_channel() cid 47 does not exist
<6>[ 12.973327] htc-acoustic: mmap
<6>[ 12.973541] htc-acoustic: ioctl
<6>[ 12.973632] htc-acoustic: ioctl: ACOUSTIC_UPDATE_ADIE called 59.
<6>[ 12.976440] htc-acoustic: ioctl: ONCRPC_UPDATE_ADIE_PROC success.
<6>[ 12.977264] htc-acoustic: release
<6>[ 12.997161] audio: init: codecs
<6>[ 12.997375] SMD: ch 43 1 -> 2
<6>[ 13.109802] dal_attach: status = 0, name = 'DAL_AQ_AUD'
<6>[ 13.109985] audio: init: INIT
<6>[ 13.110290] audio: init: OPEN control
<6>[ 13.495880] audio: init: attach ACDB
<6>[ 13.496215] SMD: ch 48 1 -> 2
<6>[ 13.606018] dal_attach: status = 0, name = 'DAL_AM_AUD'
<6>[ 13.606140] audio: init: attach ADIE
<6>[ 13.606628] dal_attach: status = 0, name = 'DAL_AM_AUD'
<6>[ 17.041503] lcdc_unblank: ()
<6>[ 17.041748] samsung_oled_panel_unblank: +()
<6>[ 17.256103] msm_kgsl: initilized dev=1 mmu=on
<6>[ 17.256561] misc kgsl: firmware: requesting yamato_pm4.fw
<6>[ 17.263732] misc kgsl: firmware: requesting yamato_pfp.fw
<3>[ 17.265991] init: untracked pid 87 exited
<3>[ 17.271881] init: untracked pid 88 exited
<6>[ 17.325988] samsung_oled_panel_unblank: -()
<6>[ 25.646606] capella_cm3602_open
<6>[ 25.647003] capella_cm3602_ioctl cmd 2
<6>[ 25.647918] capella_cm3602_disable
<6>[ 25.648040] capella_cm3602_disable: already disabled
<6>[ 25.648162] capella_cm3602_ioctl cmd 1
<6>[ 25.655303] request_suspend_state: wakeup (3->0) at 21809722976 (2010-11-2
3 19:52:15.497955355 UTC)
<6>[ 25.672088] capella_cm3602_ioctl cmd 1
<6>[ 32.422729] request_suspend_state: sleep (0->3) at 28577117998 (2010-11-23
19:52:22.265350377 UTC)
<6>[ 32.422851] capella_cm3602_ioctl cmd 1
<7>[ 32.423767] flashlight_control: mode 0 -> 0
<6>[ 32.423767] flashlight_control: off
<6>[ 32.426666] capella_cm3602_ioctl cmd 1
<6>[ 32.439849] lcdc_blank: ()
<6>[ 32.439971] samsung_oled_panel_blank: +()
<6>[ 32.645751] samsung_oled_panel_blank: -()
<6>[ 32.647949] mahimahi_ts_power: power 0
<6>[ 32.655822] lcdc_suspend: suspending
<4>[ 32.701049] save exit: isCheckpointed 1
<4>[ 32.706878] save exit: isCheckpointed 1
<4>[ 32.739654] save exit: isCheckpointed 1
<6>[ 32.763153] active wake lock kgsl
<6>[ 32.763275] active wake lock PowerManagerService
<6>[ 32.763366] wake lock mmc_delayed_work, expired
<6>[ 32.763549] wake lock qmi0, expired
<6>[ 32.763671] wake lock qmi1, expired
<6>[ 32.763763] wake lock qmi2, expired
<6>[ 32.763977] wake lock SMD_DS, expired
<6>[ 33.365203] request_suspend_state: wakeup (3->0) at 29519592363 (2010-11-2
3 19:52:23.207824742 UTC)
<6>[ 33.367401] lcdc_resume: resuming
<6>[ 33.367919] mahimahi_ts_power: power 1
<6>[ 33.369537] capella_cm3602_ioctl cmd 2
<6>[ 33.369750] capella_cm3602_disable
<6>[ 33.369842] capella_cm3602_disable: already disabled
<6>[ 33.369964] capella_cm3602_ioctl cmd 1
<6>[ 33.372253] capella_cm3602_ioctl cmd 1
<6>[ 33.415130] lcdc_unblank: ()
<6>[ 33.415252] samsung_oled_panel_unblank: +()
<6>[ 33.697570] samsung_oled_panel_unblank: -()
<6>[ 33.960021] cable_status_update: status=1
<6>[ 33.985809] msm72k_udc: OFFLINE -> ONLINE
<6>[ 33.986114] hsusb: reset controller
<6>[ 34.045654] msm_hsusb_phy_reset: success
<6>[ 34.195678] msm72k_udc: ulpi: write 0x0c to 0x31
<6>[ 34.195861] msm72k_udc: ulpi: write 0x31 to 0x32
<6>[ 34.195983] msm72k_udc: ulpi: write 0x1d to 0x0d
<6>[ 34.196166] msm72k_udc: ulpi: write 0x1d to 0x10
<6>[ 34.196929] msm72k_udc: ept #0 out max:64 head:ffa02000 bit:0
<6>[ 34.197143] msm72k_udc: ept #1 out max:512 head:ffa02080 bit:1
<6>[ 34.197235] msm72k_udc: ept #2 out max:512 head:ffa02100 bit:2
<6>[ 34.197448] msm72k_udc: ept #3 out max:512 head:ffa02180 bit:3
<6>[ 34.197540] msm72k_udc: ept #4 out max:512 head:ffa02200 bit:4
<6>[ 34.197753] msm72k_udc: ept #5 out max:512 head:ffa02280 bit:5
<6>[ 34.197845] msm72k_udc: ept #6 out max:512 head:ffa02300 bit:6
<6>[ 34.198059] msm72k_udc: ept #7 out max:512 head:ffa02380 bit:7
<6>[ 34.198150] msm72k_udc: ept #8 out max:512 head:ffa02400 bit:8
<6>[ 34.198364] msm72k_udc: ept #9 out max:512 head:ffa02480 bit:9
<6>[ 34.198547] msm72k_udc: ept #10 out max:512 head:ffa02500 bit:10
<6>[ 34.198760] msm72k_udc: ept #11 out max:512 head:ffa02580 bit:11
<6>[ 34.198883] msm72k_udc: ept #12 out max:512 head:ffa02600 bit:12
<6>[ 34.200134] msm72k_udc: ept #13 out max:512 head:ffa02680 bit:13
<6>[ 34.200225] msm72k_udc: ept #14 out max:512 head:ffa02700 bit:14
<6>[ 34.200439] msm72k_udc: ept #15 out max:512 head:ffa02780 bit:15
<6>[ 34.200531] msm72k_udc: ept #0 in max:64 head:ffa02040 bit:16
<6>[ 34.200744] msm72k_udc: ept #1 in max:512 head:ffa020c0 bit:17
<6>[ 34.200836] msm72k_udc: ept #2 in max:512 head:ffa02140 bit:18
<6>[ 34.201049] msm72k_udc: ept #3 in max:512 head:ffa021c0 bit:19
<6>[ 34.201141] msm72k_udc: ept #4 in max:512 head:ffa02240 bit:20
<6>[ 34.201354] msm72k_udc: ept #5 in max:512 head:ffa022c0 bit:21
<6>[ 34.201446] msm72k_udc: ept #6 in max:512 head:ffa02340 bit:22
<6>[ 34.201660] msm72k_udc: ept #7 in max:512 head:ffa023c0 bit:23
<6>[ 34.201751] msm72k_udc: ept #8 in max:512 head:ffa02440 bit:24
<6>[ 34.201965] msm72k_udc: ept #9 in max:512 head:ffa024c0 bit:25
<6>[ 34.202148] msm72k_udc: ept #10 in max:512 head:ffa02540 bit:26
<6>[ 34.202270] msm72k_udc: ept #11 in max:512 head:ffa025c0 bit:27
<6>[ 34.202453] msm72k_udc: ept #12 in max:512 head:ffa02640 bit:28
<6>[ 34.202575] msm72k_udc: ept #13 in max:512 head:ffa026c0 bit:29
<6>[ 34.202758] msm72k_udc: ept #14 in max:512 head:ffa02740 bit:30
<6>[ 34.202880] msm72k_udc: ept #15 in max:512 head:ffa027c0 bit:31
<6>[ 34.203094] usb: notify offline
<6>[ 34.203216] msm_hsusb: enable pullup
<6>[ 34.206329] msm72k_udc: msm72k_udc: suspend
<6>[ 34.226043] batt: charging SLOW
<6>[ 34.312683] msm72k_udc: msm72k_udc: reset
<6>[ 34.314941] msm72k_udc: msm72k_udc: portchange USB_SPEED_HIGH
<6>[ 34.473693] msm72k_udc: msm72k_udc: reset
<6>[ 34.475982] msm72k_udc: msm72k_udc: portchange USB_SPEED_HIGH
<4>[ 34.696075] ### notify_usb_connected(1) ###
<6>[ 34.696228] android_usb gadget: high speed config #1: android
<6>[ 34.696716] msm72k_udc: ept #3 in max:512 head:ffa021c0 bit:19
<6>[ 34.696929] msm72k_udc: ept #2 out max:512 head:ffa02100 bit:2
<6>[ 34.985809] binder: release 289:289 transaction 2744 out, still active
<6>[ 35.002349] binder: 79:223 transaction failed 29189, size 4-0
<6>[ 35.002593] binder: send failed reply for transaction 2744, target dead
<6>[ 55.218261] binder: 79:147 transaction failed 29189, size 52-0
<6>[ 59.133666] batt: 83%, 4060 mV, 58 mA (-68 avg), 27.1 C, 1126 mAh
<6>[ 67.028320] enabling adb
<6>[ 67.028472] msm_hsusb: disable pullup
<6>[ 67.045684] msm_hsusb: enable pullup
<6>[ 67.048828] msm72k_udc: msm72k_udc: suspend
<6>[ 67.056182] adb_open
<6>[ 67.206604] msm72k_udc: msm72k_udc: reset
<6>[ 67.206665] usb: notify offline
<6>[ 67.206878] adb_release
<6>[ 67.207946] adb_open
<6>[ 67.208740] msm72k_udc: msm72k_udc: portchange USB_SPEED_HIGH
<3>[ 67.209564] init: sys_prop: permission denied uid:2000 name:adb.connected
<6>[ 67.367462] msm72k_udc: msm72k_udc: reset
<6>[ 67.369750] msm72k_udc: msm72k_udc: portchange USB_SPEED_HIGH
<4>[ 67.581878] ### notify_usb_connected(1) ###
<6>[ 67.581970] android_usb gadget: high speed config #1: android
<6>[ 67.582031] msm72k_udc: ept #4 in max:512 head:ffa02240 bit:20
<6>[ 67.582061] msm72k_udc: ept #3 out max:512 head:ffa02180 bit:3
<6>[ 67.582763] msm72k_udc: ept #3 in max:512 head:ffa021c0 bit:19
<6>[ 67.582824] msm72k_udc: ept #2 out max:512 head:ffa02100 bit:2
<3>[ 68.069061] init: sys_prop: permission denied uid:2000 name:adb.connected
<6>[ 115.879241] batt: 83%, 4089 mV, 251 mA (230 avg), 27.6 C, 1129 mAh
<6>[ 165.942657] batt: 84%, 4094 mV, 250 mA (254 avg), 28.0 C, 1134 mAh
cat<6>[ 216.020111] batt: 84%, 4099 mV, 248 mA (249 avg), 28.2 C, 1137 mAh
<6>[ 266.188140] batt: 84%, 4104 mV, 248 mA (249 avg), 28.5 C, 1140 mAh
<6>[ 316.250946] batt: 84%, 4104 mV, 246 mA (248 avg), 28.7 C, 1145 mAh
What ROM and Kernel are you using? You usually get boot stalls or lockups from an incompatible kernel.
Ok, I'll spell it out:
ROOT. You need it to see system logs.
Then wait until it crashes with reboot.
Then run:
adb shell cat /proc/last_kmsg > c:\last_kmsg.log
adb shell cat /proc/kmsg > c:\kmsg.log
(here you'll need to stop it after 20-30 sec by Ctrl-C)
adb bugreport > c:\bugreport.log
Then you'll have 3 files in C:\, which you need. Upload here, maybe something will be better understandable from them.
ok thanks i will try to do that
GchildT said:
What ROM and Kernel are you using? You usually get boot stalls or lockups from an incompatible kernel.
Click to expand...
Click to collapse
Hi to all
I didn't want to open a new thread because of the sam problem.
So I have Nexus One, and it restarts randomly after a period of use. When the phone restarts it is stuck on the "X" sign, until it reboots again, and again... and I have to remove battery and wait for a while to turn it back on.
Anybody have any idea what this could be, and could it be this conflict.
Android version: 2.3.3
Baseband version: 32.50.00.32U_5.12.00.08
Kernel version: 2.6.35.7-59423-g008607d4
[email protected]#1
Build number: GRI40
HBOOT: 0.35.0017
Radio-5.12.00.00
Current recovery: RA Recovery V2.2.1
Code:
<3>[ 418.504575,0] mmc0: Timeout waiting for hardware interrupt.
<6>[ 418.504738,0] sdhci: =========== REGISTER DUMP (mmc0)===========
<6>[ 418.504825,0] sdhci: Sys addr: 0x4000f001 | Version: 0x00003802
<6>[ 418.504975,0] sdhci: Blk size: 0x00007200 | Blk cnt: 0x00001600
<6>[ 418.505060,0] sdhci: Argument: 0x00573c00 | Trn mode: 0x0000002b
<6>[ 418.505224,0] sdhci: Present: 0x01e80106 | Host ctl: 0x00000035
<6>[ 418.505309,0] sdhci: Power: 0x0000000b | Blk gap: 0x00000000
<6>[ 418.505459,0] sdhci: Wake-up: 0x00000000 | Clock: 0x00000007
<6>[ 418.505544,0] sdhci: Timeout: 0x0000000a | Int stat: 0x00000000
<6>[ 418.505694,0] sdhci: Int enab: 0x03ff800b | Sig enab: 0x03ff800b
<6>[ 418.505777,0] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
<6>[ 418.505925,0] sdhci: Caps: 0x642dc8b2 | Caps_1: 0x00008004
<6>[ 418.506009,0] sdhci: Cmd: 0x0000193a | Max curr: 0x00000000
<6>[ 418.506094,0] sdhci: Resp 1: 0x454d3038 | Resp 0: 0x00000900
<6>[ 418.506243,0] sdhci: Resp 3: 0x00000900 | Resp 2: 0x47070e0f
<6>[ 418.506326,0] sdhci: Host ctl2: 0x00000004
<6>[ 418.506408,0] sdhci: ADMA Err: 0x00000003 | ADMA Ptr: 0x23f4b490
<6>[ 418.506557,0] mmc0: clk: 50000000 clk-gated: 0 claimer: mmcqd/0 pwr: 10
<6>[ 418.506704,0] mmc0: rpmstatus[pltfm](runtime-suspend:usage_count:disable_depth)(0:0:0)
<6>[ 418.506787,0] sdhci: ===========================================
<6>[ 418.506935,0] mmc0: bytes to transfer: 31457792 transferred: 2883584
<3>[ 418.539062,0] mmcblk0: error -110 transferring data, sector 5716992, nr 1024, cmd response 0x900, card status 0xc00
<3>[ 418.544473,0] end_request: I/O error, dev mmcblk0, sector 5716992
<3>[ 418.544922,0] end_request: I/O error, dev mmcblk0, sector 5718016
<3>[ 418.545214,0] end_request: I/O error, dev mmcblk0, sector 5719040
<3>[ 418.545529,0] end_request: I/O error, dev mmcblk0, sector 5719848
<3>[ 418.545811,0] end_request: I/O error, dev mmcblk0, sector 5720872
<3>[ 418.546161,0] end_request: I/O error, dev mmcblk0, sector 5721896
<3>[ 418.546378,0] end_request: I/O error, dev mmcblk0, sector 5730304
<3>[ 418.546656,0] end_request: I/O error, dev mmcblk0, sector 5731328
<3>[ 418.547002,0] end_request: I/O error, dev mmcblk0, sector 5732352
<3>[ 418.547284,0] end_request: I/O error, dev mmcblk0, sector 5733376
<3>[ 426.584573,0] mmc0: Timeout waiting for hardware interrupt.
<6>[ 426.584668,0] sdhci: =========== REGISTER DUMP (mmc0)===========
<6>[ 426.584819,0] sdhci: Sys addr: 0x00000310 | Version: 0x00003802
<6>[ 426.584904,0] sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000310
<6>[ 426.585054,0] sdhci: Argument: 0x0058bc00 | Trn mode: 0x0000002b
<6>[ 426.585139,0] sdhci: Present: 0x01f80000 | Host ctl: 0x00000035
<6>[ 426.585287,0] sdhci: Power: 0x0000000b | Blk gap: 0x00000000
<6>[ 426.585371,0] sdhci: Wake-up: 0x00000000 | Clock: 0x00000007
<6>[ 426.585519,0] sdhci: Timeout: 0x0000000a | Int stat: 0x00000000
<6>[ 426.585605,0] sdhci: Int enab: 0x03ff800b | Sig enab: 0x03ff800b
<6>[ 426.585754,0] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
<6>[ 426.585839,0] sdhci: Caps: 0x642dc8b2 | Caps_1: 0x00008004
<6>[ 426.585987,0] sdhci: Cmd: 0x0000193a | Max curr: 0x00000000
<6>[ 426.586136,0] sdhci: Resp 1: 0x00000000 | Resp 0: 0x00000900
<6>[ 426.586219,0] sdhci: Resp 3: 0x00000900 | Resp 2: 0x00000000
<6>[ 426.586365,0] sdhci: Host ctl2: 0x00000004
<6>[ 426.586448,0] sdhci: ADMA Err: 0x00000007 | ADMA Ptr: 0x23f40320
<6>[ 426.586597,0] mmc0: clk: 50000000 clk-gated: 0 claimer: mmcqd/0 pwr: 10
<6>[ 426.586681,0] mmc0: rpmstatus[pltfm](runtime-suspend:usage_count:disable_depth)(0:0:0)
<6>[ 426.586829,0] sdhci: ===========================================
<6>[ 426.586914,0] mmc0: bytes to transfer: 401408 transferred: 401408
<3>[ 426.591186,0] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
<3>[ 426.591384,0] mmcblk0: error -110 transferring data, sector 5815296, nr 784, cmd response 0x900, card status 0x0
<4>[ 426.592095,0] blk_update_request: 53 callbacks suppressed
<3>[ 426.592180,0] end_request: I/O error, dev mmcblk0, sector 5815296
<3>[ 426.592481,0] end_request: I/O error, dev mmcblk0, sector 5816080
<3>[ 426.592738,0] end_request: I/O error, dev mmcblk0, sector 5817104
<3>[ 426.593064,0] end_request: I/O error, dev mmcblk0, sector 5818128
<3>[ 426.593321,0] end_request: I/O error, dev mmcblk0, sector 5819152
<3>[ 426.593635,0] end_request: I/O error, dev mmcblk0, sector 5820176
<3>[ 426.593762,0] end_request: I/O error, dev mmcblk0, sector 5824512
<3>[ 426.594080,0] end_request: I/O error, dev mmcblk0, sector 5825536
<3>[ 426.594283,0] end_request: I/O error, dev mmcblk0, sector 15094616
Those IO errors are write requests going to mmcblk0, which is the internal memory. Does this mean the end of the phone? I just have had this phone for less than 2 months and haven't flashed a whole lot (2 times so far). How can the internal memory start going bad so fast? Does anybody know if this is SLC NAND or MLC NAND that they use for internal memory?
I have a full TWRP backup of the phone which I can use to restore. Is it possible to "TRIM" or "ERASE" the NAND somehow to reset it completely? Just like SSDs.
The phone is seeing some weird behaviour during boot where it boot loops during the early boot some times and then eventually boots up fine. But most of the time works fine after that.
phone rebooted by itself and was stuck in the booting state.
started investigating, and at the moment I am not even able to update the recovery it fails, both via odin/Heimdall or via TWRP.
Recovery: TWRP 2.8.7.0 installed
ROM: [LOLLIPOP][5.1.1][Cyanogenmod 12.1][UNOFFICIAL][8.10.2015]
The dmesg logs are filled with
<3>[ 37.054840] c0 mmc0: cmd 23 response timeout error
<3>[ 37.059222] c0 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 37.066226] c0 mmcblk0: command error, retrying timeout
<3>[ 37.088482] c0 mmc0: cmd 23 response timeout error
<3>[ 37.092903] c0 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 37.102748] c0 mmcblk0: command error, retrying timeout
<3>[ 37.117883] c0 mmc0: cmd 23 response timeout error
<3>[ 37.122089] c3 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 37.129295] c3 mmcblk0: command error, retrying timeout
<3>[ 37.141923] c0 mmc0: cmd 23 response timeout error
<3>[ 37.146304] c3 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 37.153287] c3 mmcblk0: command error, retrying timeout
<3>[ 37.166353] c0 mmc0: cmd 23 response timeout error
<3>[ 37.170884] c3 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 37.177695] c3 mmcblk0: command error, retrying timeout
<3>[ 37.190754] c0 mmc0: cmd 23 response timeout error
<3>[ 37.195130] c3 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 37.202084] c3 mmcblk0: command error, retrying timeout
<3>[ 37.215368] c0 mmc0: cmd 23 response timeout error
<3>[ 37.219653] c3 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 37.226813] c3 mmcblk0: command error, retrying timeout
<3>[ 37.239558] c0 mmc0: cmd 23 response timeout error
<3>[ 37.243875] c3 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 37.250954] c3 mmcblk0: command error, retrying timeout
<3>[ 37.265033] c0 mmc0: cmd 23 response timeout error
<3>[ 37.269364] c3 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 37.276410] c3 mmcblk0: command error, retrying timeout
<3>[ 37.289442] c0 mmc0: cmd 23 response timeout error
<3>[ 37.293791] c3 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 37.300788] c3 mmcblk0: command error, retrying timeout
<3>[ 37.313867] c0 mmc0: cmd 23 response timeout error
<3>[ 37.318164] c3 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 37.325330] c3 mmcblk0: command error, retrying timeout
<3>[ 37.338418] c0 mmc0: cmd 23 response timeout error
<3>[ 37.342160] c3 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 37.349837] c3 mmcblk0: command error, retrying timeout
<3>[ 37.362909] c0 mmc0: cmd 23 response timeout error
<3>[ 37.366600] c3 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 37.374292] c3 mmcblk0: command error, retrying timeout
<3>[ 37.885821] c0 mmc0: cmd 23 response timeout error
<3>[ 37.889182] c3 mmc0: it occurs a critical error on eMMC it'll try to recover eMMC to normal state
<6>[ 38.480110] c3 mmc0: recovering eMMC has been done
<3>[ 38.480204] c3 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x900
<3>[ 38.486643] c3 mmcblk0: not retrying timeout
<3>[ 38.490870] c3 end_request: I/O error, dev mmcblk0, sector 65408
<3>[ 38.515659] c0 mmc0: cmd 23 response timeout error
<3>[ 38.519042] c3 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 38.527080] c3 mmcblk0: command error, retrying timeout
<3>[ 38.532752] c0 mmc0: cmd 23 response timeout error
<3>[ 38.537041] c3 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 38.545159] c3 mmcblk0: command error, retrying timeout
<6>[ 38.550534] c3 EXT4-fs (mmcblk0p3): recovery complete
<3>[ 38.550638] c0 mmc0: cmd 23 response timeout error
<3>[ 38.554999] c3 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 38.562984] c3 mmcblk0: command error, retrying timeout
<6>[ 38.568338] c3 EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts:
<7>[ 38.568403] c3 SELinux: initialized (dev mmcblk0p3, type ext4), uses xattr
<3>[ 38.568883] c0 mmc0: cmd 23 response timeout error
<3>[ 38.572970] c3 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 38.580999] c3 mmcblk0: command error, retrying timeout
<3>[ 38.621181] c0 mmc0: cmd 23 response timeout error
<3>[ 38.624546] c3 mmc0: it occurs a critical error on eMMC it'll try to recover eMMC to normal state
<6>[ 39.230076] c3 mmc0: recovering eMMC has been done
<3>[ 39.230136] c3 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x900
<3>[ 39.236469] c3 mmcblk0: not retrying timeout
<3>[ 39.240761] c3 end_request: I/O error, dev mmcblk0, sector 6086528
<6>[ 39.263717] c3 EXT4-fs (mmcblk0p13): mounted filesystem with ordered data mode. Opts:
<7>[ 39.263783] c3 SELinux: initialized (dev mmcblk0p13, type ext4), uses xattr
<3>[ 39.264240] c0 mmc0: cmd 23 response timeout error
<3>[ 39.267647] c0 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
<3>[ 39.275658] c0 mmcblk0: command error, retrying timeout
<3>[ 39.315442] c0 mmc0: cmd 23 response timeout error
<3>[ 39.318816] c3 mmc0: it occurs a critical error on eMMC it'll try to recover eMMC to normal state
<3>[ 39.320110] c0 [HOTPLUG IN] check_up 1400000>=500000 && 274>200
<3>[ 39.320187] c0 CPU_UP 1
<4>[ 39.341768] c1 CPU1: Booted secondary processor
<6>[ 39.341844] c1 notifier_call_chain : NOTIFY BAD tick_notify
<6>[ 39.451906] c1 Switched to NOHz mode on CPU #1
<6>[ 39.939846] c0 mmc0: recovering eMMC has been done
<3>[ 39.939902] c0 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x900
<3>[ 39.950116] c3 mmcblk0: not retrying timeout
<3>[ 39.953403] c3 end_request: I/O error, dev mmcblk0, sector 19332968
<3>[ 39.959191] c3 end_request: I/O error, dev mmcblk0, sector 19332976
<3>[ 39.965443] c3 end_request: I/O error, dev mmcblk0, sector 19332984
<3>[ 39.965491] c3 end_request: I/O error, dev mmcblk0, sector 19332992
<3>[ 39.965566] c3 end_request: I/O error, dev mmcblk0, sector 19333000
...
<3>[ 39.966579] c3 end_request: I/O error, dev mmcblk0, sector 19333216
Click to expand...
Click to collapse
Sometimes, when I try to erase Dalvik cache, cache, the phone just reboots.
seems to be the problem with the internal MMC FLASH. Is there any hope to restore it, or there is no hope and its a hardware failure.
Hello and thank you for using Q&A,
as I can read there is a sector error and this means the EMMC storage is broken. Did you enable any mods like swap or zram?
Kind regards
Trafalgar Square
Trafalgar Square said:
Hello and thank you for using Q&A,
as I can read there is a sector error and this means the EMMC storage is broken. Did you enable any mods like swap or zram?
Kind regards
Trafalgar Square
Click to expand...
Click to collapse
No, did not enable anything. No additional mods, just a standard CM.
The only thing that that was out of the ordinary is that the phone was left in the car for a night and it was -2C here in Köln. In the morning, the phone was stuck in the boot loop. Not sure whether it relevant or just a pure coincidence.