[Q] How to verify hardware failure on Audio inout jack? - Galaxy S I9000 Q&A, Help & Troubleshooting

I've been using DarkyROM 10.1 for over 4 months now with no problems whatsoever.
Till a week back my headphone started not to work on the left earphone. It was time to change it. I went today to replace the headphone and when I was testing the headphone button it didn't work.
Further more I tried to test the mic on calls and it is not working. The built in mic is the only thing working.
It looks like the phone is stuck in the button pressed mode which I think mutes the mic.
I got the dmesg log and the jack info there was as the following,
/ # dmesg | grep jack
dmesg | grep jack
<6>[ 186.249633] sec_jack_set_type : jack_type = 2
<6>[ 230.395379] sec_jack_set_type : jack_type = 0
<6>[ 851.884970] sec_jack_set_type : jack_type = 2
<6>[ 908.898467] sec_jack_set_type : jack_type = 0
<6>[ 913.641106] sec_jack_set_type : jack_type = 2
<6>[ 914.764902] sec_jack_set_type : jack_type = 0
<6>[ 917.147299] active wake lock sec_jack_det, time left 1322
<6>[ 921.237020] sec_jack_set_type : jack_type = 2
<6>[ 930.587688] sec_jack_set_type : jack_type = 0
<6>[ 3053.033646] sec_jack_set_type : jack_type = 2
<6>[ 3127.994797] sec_jack_set_type : jack_type = 0
<6>[ 3139.175387] sec_jack_set_type : jack_type = 2
<6>[ 3331.251091] sec_jack_set_type : jack_type = 0
<6>[ 3334.832856] active wake lock sec_jack_det, time left 723
<6>[ 3748.558797] sec_jack_set_type : jack_type = 2
<6>[ 4256.425996] sec_jack_set_type : jack_type = 0
<6>[ 4263.752653] sec_jack_set_type : jack_type = 2
<6>[ 4273.007345] sec_jack_set_type : jack_type = 0
<6>[ 4288.558637] sec_jack_set_type : jack_type = 2
<6>[ 4294.126007] sec_jack_set_type : jack_type = 0
<6>[ 4307.354710] sec_jack_set_type : jack_type = 2
<6>[ 4307.827809] sec_jack_set_type : jack_type = 0
<6>[ 4327.778638] sec_jack_set_type : jack_type = 2
<6>[ 4329.332950] sec_jack_set_type : jack_type = 0
<6>[ 5523.733072] sec_jack_set_type : jack_type = 2
<6>[ 5568.944868] sec_jack_set_type : jack_type = 0
<6>[ 5611.345671] wakeup wake lock: sec_jack_det
<6>[ 5614.900765] sec_jack_set_type : jack_type = 2
<6>[ 5615.948397] sec_jack_set_type : jack_type = 0
<6>[ 5622.514618] wake lock sec_jack_det, expired
<6>[ 5622.719607] wakeup wake lock: sec_jack_det
<6>[ 5626.224616] sec_jack_set_type : jack_type = 2
<6>[ 5655.934294] sec_jack_set_type : jack_type = 0
<6>[ 5663.190634] sec_jack_set_type : jack_type = 2
<6>[ 5678.021070] sec_jack_set_type : jack_type = 0
Each time I plug the headphone I get nothing I remove it I get the two lines
<6>[ 5663.190634] sec_jack_set_type : jack_type = 2
<6>[ 5678.021070] sec_jack_set_type : jack_type = 0
Is it the problem that it is stuck in button pushed mode?
I tried to clear dalvik cache but it was of no use.
Would a fresh flashing do the trick? or is it a hardware damage?
P.S. When I discovered that the headphone is faulty the button was still working. it's only today that I have discovered it is not working when I tried to buy a new one.
Later on I went and installed DarkyROM 10.2.2 EE and did a date Wipe and it's the same issue, I even went further and formatted everything and went with a stock 2.3.5 and it's the same thing.
What I can think of now is a hardware failure, but I need to be 100% sure of that before sending it to the service center.
Can you guys help me with debugging this even more?
Thanks and sorry for the long thread.

Related

[Q] WiFi suddenly stopped working (error state)

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"

WiFi connection problems

Hey guys,
i'm having really bad wifi issues on various roms (KoR 1.1 + MiuiMod) and kernels (WM, Pershoot, Intersect) right now.
What happens is, i switch on wifi and it scans and finds the registered router, but when i try to connect it somehow stays stuck scanning or it says getting ip and then switches itself off again.
i pulled a log from OSMonitor and quite a lot of stuff seems to be going bad
10/30/2010 16:01:29 [INFORMATION] samsung_oled_panel_unblank: -()
10/30/2010 16:01:30 [WARNING] wifi_set_power = 1
10/30/2010 16:01:30 [WARNING] mahimahi_wifi_power: 1
10/30/2010 16:01:30 [WARNING] wifi_set_carddetect =
10/30/2010 16:01:30 [INFORMATION] mahimahi_wifi_set_carddetect: 1
10/30/2010 16:01:30 [DEBUG] mmc0: card_present 1
10/30/2010 16:01:30 [INFORMATION] mmc0: Slot status change detected (0 -> 1)
10/30/2010 16:01:30 [WARNING]
10/30/2010 16:01:30 [WARNING] Dongle Host Driver, version 4.218.248.10
10/30/2010 16:01:30 [WARNING] mmc0: queuing unknown CIS tuple 0x91 (3 bytes)
10/30/2010 16:01:30 [INFORMATION] mmc0: new high speed SDIO card at address 0001
10/30/2010 16:01:30 [WARNING] DHD: dongle ram size is set to 294912(orig 294912)
10/30/2010 16:01:31 [WARNING] wifi_get_mac_addr
10/30/2010 16:01:31 [WARNING] Firmware version = wl0: Apr 22 2010 10:02:12 version 4.218.223.0
10/30/2010 16:01:31 [WARNING] eth0: Broadcom Dongle Host Driver mac=00:23:76:b1:01:df
10/30/2010 16:01:32 [WARNING] STA connect received 1
10/30/2010 16:01:41 [DEBUG] eth0: no IPv6 routers present
10/30/2010 16:01:58 [WARNING] wifi_set_power = 0
10/30/2010 16:01:58 [WARNING] mahimahi_wifi_power: 0
10/30/2010 16:01:59 [WARNING] wifi_set_carddetect =
10/30/2010 16:01:59 [INFORMATION] mahimahi_wifi_set_carddetect: 0
10/30/2010 16:01:59 [DEBUG] mmc0: card_present 0
10/30/2010 16:01:59 [INFORMATION] mmc0: Slot status change detected (1 -> 0)
10/30/2010 16:01:59 [INFORMATION] mmc0: card 0001 removed
10/30/2010 16:02:35 [INFORMATION] batt: 89%, 4021 mV, -120 mA (-199 avg), 22.1 C, 1182 mAh
Click to expand...
Click to collapse
also check out this really long error log here:
http://pastebin.com/Si5dB9WH
this keeps going on until it just magically connects (or i give up). a reboot also solves the problem and gets me a direct connection
any idea whats going on please help me?
bump! please i still havent solved this

Nexus One Reboot Freezes what could be the problem?

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

Time and Date WAY OFF and no WIFI

Ok, I picked up a KFHD 7 cheap because it wouldnt connect to wifi.. Figured it would be a simple deal .. NOPE.. I have thrown everything at this thing from KFHD Img recovery , KFFA, Twrp and 2nd boot with and when I flashed kitkat roms it would just freeze at the blue KINDLE FIRE screen.. Nothing I have thrown at it has helped one bit.. It says my date is jan 22nd 2000 and wont let me turn on the wifi...I hit turn on wifi and it wont turn on, and date and time setting is greyed out and wont let me change.. Any have any ideas, this is driving me NUTS..
Something bad in the nvram? Think its also called the boot0block. That's just a guess, I know the Mac address for WiFi is stored there and it wouldn't be able to turn on if the address went corrupt, but I'm not so sure about how the kindles stores time, I know PC's store it in the cmos, not sure about a kindle, but I do know odd things are stored in nvram so Idk. If it were your boot0block I would have thought flashing to another ROM would have fixed it because I thought cm didn't grab the Mac address and made its own, but I could be mistaken. If you want more info try turning WiFi on/setting the time, and depending on if you are on amazon os make sure you are rooted, if your on cm I wouldn't worry it has root built in, connect kindle to PC and run a "adb shell su -c dmesg", right click in the command prompt, hit mark, highlight everything it posted and hit copy then paste it here in code brackets, depending on how big it is you may have to post it on pastebin. These instructions I gave you suck because I'm assuming your on windows, and windows doesn't have an unlimited number of lines you can scroll back in a command prompt like in Linux, you can set it to max out to either 99 or 999 lines but usually dmesg will exceed that I would think. If you know your way around a command prompt, try redirecting its output into a text file, I'm to lazy to put code brackets down so I can show you how with the right quotation right now, but here's a final tip if you do this, do it right after the device has booted go so there's not as much on the dmesg. Might also try a adb log cat at somepoint, but if there's some kinda hardware failure I would think dmesg would do the trick. Man this post was a bit more complicated and long than I intended, if you have any questions about what I said feel free to ask away.
Sent from my Amazon Kindle Fire HD using Tapatalk
I can not turn on or off the wifi. If I hit wifi it wont switch to on. I it would seem to me , that the time/date and wifi problem would be connected.. I was hoping that I would be able to get the time un greyed out and change it and everything else would fall into place.. Going to twrp, 2nd boot then kit kat today and see what happens... I have only tried custom rom once so far on this KFHD and it got stuck in KINDLE FIRE boot loop.. But I can get it to recovery to just about any amaazon OS.. Today is a new fresh day with new fresh eyes and mind , let the fun begin. One would have thought I would have bricked it by now with all the crap I have thrown at this KFHD, but hell I cant even accomplish that LOL
http://forum.xda-developers.com/showthread.php?t=2274338
Well well there is my same problem.. Time to read until my eyes bleed again..
Code:
>[ 6.264434] omap_rpmsg_mbox_callback: received echo reply from ipu !
>[ 6.272186] virtio_rpmsg_bus virtio0: creating channel rpmsg-client-sam
ddr 0x32
>[ 6.281555] virtio_rpmsg_bus virtio0: creating channel rpmsg-client-sam
ddr 0x33
>[ 6.290863] virtio_rpmsg_bus virtio0: creating channel rpmsg-omx0 addr
>[ 6.299530] rpmsg_omx rpmsg-omx0: new OMX connection srv channel: 1024
!
>[ 6.386230] virtio_rpmsg_bus virtio1: creating channel rpmsg-omx1 addr
>[ 6.394989] rpmsg_omx rpmsg-omx1: new OMX connection srv channel: 1024
!
>[ 10.175415] wm8962 3-001a: bootup time wm8962_mic_detect_boot_work is c
!!!!!!!!!!!!!!!!!!
>[ 10.433227] wm8962 3-001a: Detected removal
>[ 10.438079] wm8962 3-001a: Iphone report 0
>[ 11.936309] EXT4-fs (mmcblk0p13): recovery complete
>[ 11.942260] EXT4-fs (mmcblk0p13): mounted filesystem with ordered data
Opts: nomblk_io_submit,commit=20
>[ 11.963226] EXT4-fs (mmcblk0p12): recovery complete
>[ 11.969116] EXT4-fs (mmcblk0p12): mounted filesystem with ordered data
Opts: nomblk_io_submit,commit=20
>[ 11.997528] EXT4-fs (mmcblk0p8): recovery complete
>[ 12.003326] EXT4-fs (mmcblk0p8): mounted filesystem with ordered data m
Opts: (null)
>[ 12.033050] init: cannot find '/system/bin/uim-sysfs', disabling 'uim'
>[ 12.081939] HDCP: **** hdcp_load_keys_cb ****
>[ 12.086700] HDCP: loaded keys
>[ 12.093322] ===========ATMEL TOUCH SENSOR DETECT================
>[ 12.190643] boardIdCheck: *** board type: 803, revision: 8, variant: 0
>[ 12.197753] boardIdCheck: capable of wifi OOB
>[ 12.202758] ## wifi_probe
>[ 12.205627] wifi_set_power = 1
>[ 12.212432] bowser_wifi_power: Powering on wifi
>[ 12.218811] Atmel touch sensor vendor gpadc value: 650
>[ 12.225677] CPU1: shutdown
>[ 12.231048] Atmel touch sensor is CMI.
>[ 12.241699] loading atmel touch driver
>[ 12.278594] warning: `bluetoothd' uses 32-bit capabilities (legacy supp
n use)
>[ 12.367553] atmel_mxt_ts 2-004c: atmel touch driver version: 1.19
>[ 12.378570] wifi_set_carddetect = 1
>[ 12.389251]
>[ 12.389251] Dongle Host Driver, version 5.90.195.34
>[ 12.389251] Compiled in drivers/net/wireless/bcmdhd on Oct 18 2012 at 0
48
>[ 12.431182] mmc1: unrecognised CCCR structure version 3
>[ 12.436737] mmc1: Reverting CCCR structure version to 2
>[ 12.465881] mmc1: new high speed SDIO card at address 0001
>[ 12.472106] wifi_get_irq_number: irq number = 204 (we will be using OOB
rrupt ...)
>[ 12.480926] F1 signature read @0x18000000=0x1680a8e7
>[ 12.510375] dhdsdio_probe_attach: module maker = -1
>[ 12.515563] dhdsdio_probe_attach: module maker name = (default: semco)
>[ 12.522460] dhdsdio_probe_attach: nv_path was /system/etc/wifi/bcmdhd.c
>[ 12.529663] dhdsdio_probe_attach: nv_path set to /system/etc/wifi/nvram
_semco.txt
>[ 12.538909] dhdsdio_probe_attach: si_attach failed!
>[ 12.544128] dhdsdio_probe: dhdsdio_probe_attach failed
>[ 12.549591] wifi_set_power = 0
>[ 12.552856] bowser_wifi_power: Powering off wifi
>[ 12.557769] =========== WLAN placed in RESET ========
>[ 12.564239] android_usb: already disabled
>[ 12.568756] adb_bind_config
>[ 12.572204] adb_bind_config
>[ 12.576599] adb_open
>[ 12.666168] PVR: Installing MISR with cookie c0867278
>[ 12.692047] sr_class1p5_calib_work: core: Calibration complete: Voltage
nal=1250000Calib=1025500 margin=13000
>[ 12.728424] SMC: SecureCRC=0xBC7458DC
>[ 12.742797] Disabling non-boot CPUs ...
>[ 12.748901] PVR: Installing device LISR SGX ISR on IRQ 53 with cookie e
00
>[ 12.856994] PVR: OSUnMapPhysToLin: unmapping 65535 bytes from e8da0000
>[ 12.865844] PVR: SysFinalise: Version string: SGX revision = 1.2.0
>[ 12.890533] android_work: sent uevent USB_STATE=CONNECTED
>[ 12.902069] android_work: sent uevent USB_STATE=DISCONNECTED
>[ 12.912933] SMC PA: INFO 00000001 00:00:00.000 ------ ------ ---------
- Booting... (t=17:24:29.520) SMCXG01.06p5.36479 /PlayReady Integration
>[ 12.954345] SMC PA: INFO 00000002 00:00:00.037 ------ ------ ---------
- Booted
>[ 13.029998] HDCP: hdcp_ioctl() - ENABLE 3489373951
>[ 13.035491] HDCP: hdcp_work_queue() - START - 3489373959 hdmi=0 hdcp=1
0 evt= 1 0 hdcp_ctrl=00
>[ 13.046020] HDCP: hdcp_ioctl() - WAIT 3489373967 0
>[ 13.051971] HDCP: hdcp_work_queue() - END - 3489373974 hdmi=0 hdcp=1 au
evt=1 0
>[ 13.068939] CPU1: Booted secondary processor
>[ 13.073852] Switched to NOHz mode on CPU #1
>[ 13.077484] android_work: sent uevent USB_STATE=CONNECTED
>[ 13.091247] android_usb gadget: high speed config #1: android
>[ 13.091308] android_work: sent uevent USB_STATE=CONFIGURED
>[ 13.269714] atmel_mxt_ts 2-004c: Family ID: 161 Variant ID: 2 Version:
A Object Num: 23
>[ 13.282440] atmel_mxt_ts 2-004c: configured max finger (32) is too larg
>[ 13.289642] atmel_mxt_ts 2-004c: T53, start:148 size:5 instances:1 min_
tid:0 max_reportid:0
>[ 13.298980] atmel_mxt_ts 2-004c: T37, start:153 size:130 instances:1 mi
ortid:0 max_reportid:0
>[ 13.308502] atmel_mxt_ts 2-004c: T44, start:283 size:1 instances:1 min_
tid:0 max_reportid:0
>[ 13.317810] atmel_mxt_ts 2-004c: T5, start:284 size:9 instances:1 min_r
id:0 max_reportid:0
>[ 13.327056] atmel_mxt_ts 2-004c: T6, start:293 size:6 instances:1 min_r
id:1 max_reportid:1
>[ 13.336303] atmel_mxt_ts 2-004c: T38, start:299 size:64 instances:1 min
rtid:0 max_reportid:0
>[ 13.345703] atmel_mxt_ts 2-004c: T7, start:363 size:3 instances:1 min_r
id:0 max_reportid:0
>[ 13.354919] atmel_mxt_ts 2-004c: T8, start:366 size:10 instances:1 min_
tid:0 max_reportid:0
>[ 13.364288] atmel_mxt_ts 2-004c: T9, start:376 size:35 instances:2 min_
tid:2 max_reportid:33
>[ 13.373687] atmel_mxt_ts 2-004c: T15, start:446 size:11 instances:2 min
rtid:34 max_reportid:35
>[ 13.383300] atmel_mxt_ts 2-004c: T18, start:468 size:2 instances:1 min_
tid:0 max_reportid:0
>[ 13.392639] atmel_mxt_ts 2-004c: T19, start:470 size:16 instances:1 min
rtid:36 max_reportid:36
>[ 13.402221] atmel_mxt_ts 2-004c: T25, start:486 size:26 instances:1 min
rtid:37 max_reportid:37
>[ 13.411834] atmel_mxt_ts 2-004c: T40, start:512 size:5 instances:2 min_
tid:0 max_reportid:0
>[ 13.421142] atmel_mxt_ts 2-004c: T42, start:522 size:10 instances:2 min
rtid:38 max_reportid:39
>[ 13.430725] atmel_mxt_ts 2-004c: T43, start:542 size:7 instances:1 min_
tid:0 max_reportid:0
>[ 13.440063] atmel_mxt_ts 2-004c: T46, start:549 size:10 instances:1 min
rtid:40 max_reportid:40
>[ 13.449645] atmel_mxt_ts 2-004c: T47, start:559 size:10 instances:2 min
rtid:0 max_reportid:0
>[ 13.459075] atmel_mxt_ts 2-004c: T48, start:579 size:74 instances:1 min
rtid:41 max_reportid:41
>[ 13.468658] atmel_mxt_ts 2-004c: T52, start:653 size:15 instances:2 min
rtid:42 max_reportid:43
>[ 13.478271] atmel_mxt_ts 2-004c: T55, start:683 size:6 instances:2 min_
tid:0 max_reportid:0
>[ 13.487579] atmel_mxt_ts 2-004c: T56, start:695 size:34 instances:1 min
rtid:44 max_reportid:44
>[ 13.497192] atmel_mxt_ts 2-004c: T57, start:729 size:3 instances:2 min_
tid:45 max_reportid:46
>[ 13.571716] atmel_mxt_ts 2-004c: status = 90
>[ 13.580413] atmel_mxt_ts 2-004c: status = 0
>[ 13.587493] atmel_mxt_ts 2-004c: Config CRC 0x56184F: OK
>[ 13.593353] atmel_mxt_ts 2-004c: Resetting chip
>[ 14.014556] atmel_mxt_ts 2-004c: Matrix Size X24Y32 Touchscreen size X7
79
>[ 14.022644] atmel_mxt_ts 2-004c: Noise threshold is 30
>[ 14.028686] atmel_mxt_ts 2-004c: Noise level report enabled
>[ 14.040588] atmel_mxt_ts 2-004c: status = 0
>[ 14.074401] input: AtmelTouch as /devices/platform/omap/omap_i2c.2/i2c-
04c/input/input6
>[ 14.093841] atmel_mxt_ts 2-004c: mxt_start begin
>[ 14.099334] atmel_mxt_ts 2-004c: mxt_start end
>[ 14.118957] atmel_mxt_ts 2-004c: status = 10
>[ 14.171295] atmel_mxt_ts 2-004c: status = 0
>[ 14.197174] atmel_mxt_ts 2-004c: status = 40
>[ 15.072448] atmel_mxt_ts 2-004c: status = 0
>[ 15.108398] atmel chown of sysfs entry
>[ 15.207427] Setting up thermal policy
>[ 15.211517] Setting up thermal threshold for backlight_cooling device
>[ 15.218750] Setting up thermal threshold for charger_cooling device
>[ 15.953521] EXT4-fs (mmcblk0p13): re-mounted. Opts: discard
>[ 16.046173] EXT4-fs (mmcblk0p12): re-mounted. Opts: discard
>[ 16.144744] omap-iommu omap-iommu.0: iommu_get: ducati qos_request
>[ 16.166656] omap_hwmod: ipu: failed to hardreset
>[ 16.171569] omap-iommu omap-iommu.0: ducati: version 2.1
>[ 16.179321] EXT4-fs (mmcblk0p8): re-mounted. Opts: discard
>[ 16.695922] misc dsscomp: [e59c8400] ignoring set failure -22
>[ 16.695983] mgr_blank while GO is set
>[ 29.828186] request_suspend_state: wakeup (3->0) at 29824676516 (2000-0
17:24:46.436462404 UTC)
>[ 29.886901] <6>MPL-accODR : 28571 mHz
>[ 29.910430] <6>MPL-accODR : 5000 mHz
>[ 29.933807] <6>MPL-accODR : 14285 mHz
>[ 29.965576] bcm2076_bt_rfkill_set_power(On)
>[ 30.041564] init: no such service 'dhcpcd_:-h kindle-658e19dc9 '
>[ 30.075531] binder: 93:93 BC_REQUEST_DEATH_NOTIFICATION death notificat
lready set
>[ 30.132598] acc_open
>[ 30.135162] acc_release
>[ 33.076751] atmel_mxt_ts 2-004c: atmel plug in value 1
>[ 33.085601] atmel_mxt_ts 2-004c: atmel set charger bit 1, regval 210
>[ 33.096740] atmel_mxt_ts 2-004c: status = 10
>[ 33.113952] atmel_mxt_ts 2-004c: status = 0
>[ 33.135894] atmel_mxt_ts 2-004c: status = 10
>[ 33.159027] atmel_mxt_ts 2-004c: status = 0
>[ 39.434936] init: cannot find '/system/bin/auto_shutdown', disabling 'c
shutdown'
>[ 56.311859] binder: release proc 703, transaction 16260, not freed
>[ 56.318817] binder: release proc 703, transaction 16415, not freed
>[ 56.325439] binder: release proc 703, transaction 16419, not freed
>[ 56.332122] binder: release proc 703, transaction 16627, not freed
>[ 56.338775] binder: release proc 703, transaction 16696, not freed
>[ 73.470336] binder: release 1105:1130 transaction 16311 out, still acti
>[ 96.022827] binder: 1135:1146 transaction failed 29189, size 32-4
>[ 96.029357] binder: send failed reply for transaction 16311, target dea
>[ 106.144622] binder: release 1583:1583 transaction 19931 out, still acti
>[ 107.385406] binder: 199:396 transaction failed 29189, size 8-0
>[ 107.392028] binder: send failed reply for transaction 19931, target dea
>[ 109.815032] EXT4-fs (mmcblk0p11): re-mounted. Opts: (null)
>[ 109.832336] EXT4-fs (mmcblk0p11): re-mounted. Opts: (null)
>[ 109.842926] EXT4-fs (mmcblk0p11): re-mounted. Opts: (null)
>[ 114.747283] EXT4-fs (mmcblk0p11): re-mounted. Opts: (null)
>[ 114.990295] EXT4-fs (mmcblk0p11): re-mounted. Opts: (null)
>[ 115.016479] EXT4-fs (mmcblk0p11): re-mounted. Opts: (null)
>[ 116.162933] init: untracked pid 1155 exited
>[ 116.167510] init: untracked pid 1156 exited
>[ 116.213989] binder: 924:952 transaction failed 29189, size 0-0
>[ 130.198883] bcm2076_bt_rfkill_set_power(Off)
>[ 339.558746] request_suspend_state: sleep (0->3) at 339555236820 (2000-0
17:29:56.167022708 UTC)
>[ 339.568603] atmel_mxt_ts 2-004c: set antitouch 2 30 8 176
>[ 339.576965] atmel_mxt_ts 2-004c: mxt_stop begin
>[ 339.583892] atmel_mxt_ts 2-004c: mxt_stop end
>[ 339.593963] DSSCOMP: dsscomp_early_suspend
>[ 339.606018] DSSCOMP: blanked screen
>[ 339.699127] sr_class1p5_calib_work: core: Calibration complete: Voltage
nal=962000Calib=886240 margin=38000
>[ 339.745849] sr_class1p5_calib_work: mpu Stop sampling: Voltage Nominal=
00 samples=11
>[ 339.746002] sr_class1p5_calib_work: mpu: Calibration complete: Voltage
al=1025000Calib=848260 margin=10000
>[ 341.081726] sr_class1p5_calib_work: mpu: Calibration complete: Voltage
al=1317000Calib=1076140 margin=0
>[ 734.148132] request_suspend_state: wakeup (3->0) at 734144592289 (2000-
17:36:30.756378177 UTC)
>[ 734.177398] <6>MPL-accODR : 14285 mHz
>[ 734.200805] <6>MPL-accODR : 5000 mHz
>[ 734.223297] <6>MPL-accODR : 14285 mHz
>[ 734.426513] bq27541 3-0055: Screen off drainage: -1 % over 394812 msecs
>[ 734.433959] DSSCOMP: dsscomp_late_resume
>[ 734.444915] atmel_mxt_ts 2-004c: mxt_start begin
>[ 734.469940] atmel_mxt_ts 2-004c: mxt_start end
>[ 734.475402] atmel_mxt_ts 2-004c: status = 10
>[ 734.490356] atmel_mxt_ts 2-004c: status = 0
>[ 735.517974] atmel_mxt_ts 2-004c: got action code 1
>[ 735.676116] wm8962 3-001a: mutex locked wm8962_irq
>[ 735.681549] wm8962 3-001a: FLL locked now disable FLL lock irq
>[ 735.688293] wm8962 3-001a: mutex unlocked wm8962_irq
>[ 737.829040] smb347 3-005f: USB disconnected
>[ 737.833740] adb_release
>[ 737.836730] android_work: sent uevent USB_STATE=DISCONNECTED
>[ 737.842864] adb_open
>[ 737.862396] atmel_mxt_ts 2-004c: atmel plug in value 0
>[ 737.869018] atmel_mxt_ts 2-004c: atmel set charger bit 0, regval 242
>[ 737.876464] atmel_mxt_ts 2-004c: status = 10
>[ 737.887115] atmel_mxt_ts 2-004c: set antitouch 2 30 8 176
>[ 737.893646] atmel_mxt_ts 2-004c: status = 0
>[ 737.898925] atmel_mxt_ts 2-004c: status = 10
>[ 737.968627] atmel_mxt_ts 2-004c: status = 0
>[ 739.712158] smb347 3-005f: Spurious APSD IRQ!
>[ 740.226715] smb347 3-005f: Detected charger: SDP
>[ 740.238433] smb347 3-005f: Switching to USB5 mode
>[ 740.247619] atmel_mxt_ts 2-004c: atmel plug in value 1
>[ 740.254455] atmel_mxt_ts 2-004c: atmel set charger bit 1, regval 210
>[ 740.261932] atmel_mxt_ts 2-004c: status = 10
>[ 740.269409] atmel_mxt_ts 2-004c: set antitouch 2 30 8 176
>[ 740.289581] atmel_mxt_ts 2-004c: status = 0
>[ 740.311614] atmel_mxt_ts 2-004c: status = 10
>[ 740.334686] atmel_mxt_ts 2-004c: status = 0
>[ 740.893341] android_work: sent uevent USB_STATE=CONNECTED
>[ 740.900238] android_work: sent uevent USB_STATE=DISCONNECTED
>[ 741.076934] android_work: sent uevent USB_STATE=CONNECTED
>[ 741.090118] android_usb gadget: high speed config #1: android
>[ 741.096405] android_work: sent uevent USB_STATE=CONFIGURED
>[ 750.316772] atmel_mxt_ts 2-004c: set antitouch 20 1 0 0
>[ 918.487579] smb347 3-005f: USB disconnected
>[ 918.494598] adb_release
>[ 918.497589] android_work: sent uevent USB_STATE=DISCONNECTED
>[ 918.504699] adb_open
>[ 918.528198] atmel_mxt_ts 2-004c: atmel plug in value 0
>[ 918.537322] atmel_mxt_ts 2-004c: atmel set charger bit 0, regval 242
>[ 918.545104] atmel_mxt_ts 2-004c: status = 10
>[ 918.550598] atmel_mxt_ts 2-004c: set antitouch 2 30 8 176
>[ 918.573608] atmel_mxt_ts 2-004c: status = 0
>[ 918.598999] atmel_mxt_ts 2-004c: status = 10
>[ 918.627227] atmel_mxt_ts 2-004c: status = 0
>[ 920.938079] atmel_mxt_ts 2-004c: status = 10
>[ 920.957153] atmel_mxt_ts 2-004c: status = 0
>[ 926.690368] smb347 3-005f: Spurious APSD IRQ!
>[ 927.203369] smb347 3-005f: Detected charger: SDP
>[ 927.223205] atmel_mxt_ts 2-004c: atmel plug in value 1
>[ 927.231536] atmel_mxt_ts 2-004c: atmel set charger bit 1, regval 210
>[ 927.238769] smb347 3-005f: Switching to USB5 mode
>[ 927.243804] atmel_mxt_ts 2-004c: status = 10
>[ 927.254821] atmel_mxt_ts 2-004c: status = 0
>[ 927.269409] atmel_mxt_ts 2-004c: set antitouch 2 30 8 176
>[ 927.275787] atmel_mxt_ts 2-004c: status = 10
>[ 927.326721] atmel_mxt_ts 2-004c: status = 0
>[ 927.747619] android_work: did not send uevent (0 0 (null))
>[ 927.904907] android_work: sent uevent USB_STATE=CONNECTED
>[ 927.912109] android_work: sent uevent USB_STATE=DISCONNECTED
>[ 928.089782] android_work: sent uevent USB_STATE=CONNECTED
>[ 928.125274] android_usb gadget: high speed config #1: android
>[ 928.131622] android_work: sent uevent USB_STATE=CONFIGURED
>[ 937.316070] atmel_mxt_ts 2-004c: set antitouch 20 1 0 0
Very interesting, i'm guessing it's the boot0block, I see it turned WiFi on, ran a process where I think it checked the nvram and then failed or something because it looked like the process unloaded a module or something, then WiFi powered off. I''ll look more into it when I get back home and can look at my kindles dmesg and compare it.
Edit: o wait that was a text file, and I was half asleep.
Sent from my LG-P769 using Tapatalk
Also when I do a wipe data and cache, it takes an extremely LONG time... About an Hour
Had the exact same problem with the greyed out wifi and searched for a solution on and off for months, tried completely wiping it and restoring it to factory a couple times. It's not worth it. Ended up just sending it back to Amazon for a replacement.
dacetys said:
Had the exact same problem with the greyed out wifi and searched for a solution on and off for months, tried completely wiping it and restoring it to factory a couple times. It's not worth it. Ended up just sending it back to Amazon for a replacement.
Click to expand...
Click to collapse
Thats not an option as I am not the org. owner and I have never had it registered under my name
I'm going to see if hashcode has anymore info on this, I compared it to mine and I don't see it doing what yours is doing so I'm still guessing its the boot0, but he should know more. Also misread that line and typo'd what I was trying to say because I was sleepy.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
I'm going to see if hashcode has anymore info on this, I compared it to mine and I don't see it doing what yours is doing so I'm still guessing its the boot0, but he should know more. Also misread that line and typo'd what I was trying to say because I was sleepy.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I have another KFHD .. If the Boot0 is screwed on this one and there is no way to repair, can I pull the one off my other one and use it on this one.. I will be putting a rom on this one and have no intentions of using it as a KINDLE with amazon
OK yes you could, assuming that I understand how it works, you might ha be issues if you attempt to use both on the same router at the same time, also as long as it is the same version kindle (7") you should be fine with pulling it and flashing it over the current boot0block, however I don't recommend doing this yet until I find out the name to flash it to in fastboot mode, also recommend backing up your own boot0block just in case, hey you might get lucky and still have a partially bad boot0block with some data intact you could overwrite on the other like serial number and such. Like I said lemme talk to hashcode first, I talk to him on the Irc a bit but he doesn't always respond immediately so maybe I'll have an answer sometime tomorrow.
Sent from my Amazon Kindle Fire HD using Tapatalk
Wait i don't think i noticed this, you are still running a stock rooted amazon os? you never got cm working, it always bootlooped? If so you did wipe data correct(factory reset)? I asked hashcode about it and he said some of the wifi data is stored in the cache and to try that first off. So try a factory reset and see what happens, wouldnt mind seeing what happens on cm as well, but i would have to help you figure out whats with the bootloop you get on it if its not related to you needing to do a factory reset.
stunts513 said:
Wait i don't think i noticed this, you are still running a stock rooted amazon os? you never got cm working, it always bootlooped? If so you did wipe data correct(factory reset)? I asked hashcode about it and he said some of the wifi data is stored in the cache and to try that first off. So try a factory reset and see what happens, wouldnt mind seeing what happens on cm as well, but i would have to help you figure out whats with the bootloop you get on it if its not related to you needing to do a factory reset.
Click to expand...
Click to collapse
Yes I cant ever get a ROM to load..It always goes to the KINDLE FIRE screen and hangs or hangs awhile then will go into twrp.. Yes I have did factory reset many times. I have wiped the user data and cache in TWRP , KFFA and KF recovery programs... Driving me Batty.. Oh my other KFHD it had a temporary issue with the wifi and it all straighened out when I reflashed it.. And it never showed this crazy ass date... I am going to give twrp and 2nd BL another try tomorrow.. I really can not believe I have not bricked this thing yet..
lilmonk3 said:
Yes I cant ever get a ROM to load..It always goes to the KINDLE FIRE screen and hangs or hangs awhile then will go into twrp.. Yes I have did factory reset many times. I have wiped the user data and cache in TWRP , KFFA and KF recovery programs... Driving me Batty.. Oh my other KFHD it had a temporary issue with the wifi and it all straighened out when I reflashed it.. And it never showed this crazy ass date... I am going to give twrp and 2nd BL another try tomorrow.. I really can not believe I have not bricked this thing yet..
Click to expand...
Click to collapse
As long as you don't flash a bad bootloader or thew wrong bootloader, or maybe the wrong kernel, it should not brick to the point it won't turn on. So right now you are in stock amazon os right? i cant think of a reason why you would be going into twrp recovery when trying to boot up without having a bad system flash or something, the only time that tends to ever occur is when you flash twrp + 2nd bootloader and your amazon os isn't the same as the freedomboot image version. Give me some more info and such and i'll see what i can do.
stunts513 said:
As long as you don't flash a bad bootloader or thew wrong bootloader, or maybe the wrong kernel, it should not brick to the point it won't turn on. So right now you are in stock amazon os right? i cant think of a reason why you would be going into twrp recovery when trying to boot up without having a bad system flash or something, the only time that tends to ever occur is when you flash twrp + 2nd bootloader and your amazon os isn't the same as the freedomboot image version. Give me some more info and such and i'll see what i can do.
Click to expand...
Click to collapse
my amazon OS is 7.2.3 and following is the files I have been working with using fire flash
kfhd7-twrp-2.6.3.1-recovery.img
kfhd7-freedom-boot-7.2.3.img
lilmonk3 said:
my amazon OS is 7.2.3 and following is the files I have been working with using fire flash
kfhd7-twrp-2.6.3.1-recovery.img
kfhd7-freedom-boot-7.2.3.img
Click to expand...
Click to collapse
And tried the hashcodes kitkat.. Not sure of the file name, because I am not at home to look
Also when I go to wipe data and cache let say in KFFA, it takes close to an hour to do so... That seems jacked up
heres the rom I have been trying cm-11-20131126-UNOFFICIAL-tate.zip
Use cm-11-20140117-UNOFFICIAL-tate.zip
Sent from my Kindle Fire HD 7 using XDA Premium 4 mobile app

Internal memory bad sectors

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.

Categories

Resources