Hi All,
I would have posted in the developer forum under one of the CM7 threads but this is my first post on xda so here it goes:
I've been following the developer forums for a while now and I too am plagued with the wonks on my N1 with CM7. For me the wonkiness = phone not being responsive with black screen and no audio when making a phone call, then after about 15 to 25 seconds the screen shows the call and audio is back on).
This is understandable since it's still in an alpha state not ready for production so I wanted to post my logcat (running build 27) snapshot (attached) to see if it will help some developer figure out how to fix the wonk of terror.
Here's how I reproduce the wonk:
I turn my N1 on and as soon as it boots up I press the power button to shut the screen off. After about 2 to 3 minutes I press the power button, unlock my phone and try to make a call. I am guaranteed a wonk every time.
My temporary fix is the CM7 Dewonkificator Add-on. It definitely fixes my N1's wonkiness problem for the time being.
Thanks for listening!
markhm1978 said:
Hi All,
I would have posted in the developer forum under one of the CM7 threads but this is my first post on xda so here it goes:
I've been following the developer forums for a while now and I too am plagued with the wonks on my N1 with CM7. For me the wonkiness = phone not being responsive with black screen and no audio when making a phone call, then after about 15 to 25 seconds the screen shows the call and audio is back on).
This is understandable since it's still in an alpha state not ready for production so I wanted to post my logcat (running build 27) snapshot (attached) to see if it will help some developer figure out how to fix the wonk of terror.
Here's how I reproduce the wonk:
I turn my N1 on and as soon as it boots up I press the power button to shut the screen off. After about 2 to 3 minutes I press the power button, unlock my phone and try to make a call. I am guaranteed a wonk every time.
My temporary fix is the CM7 Dewonkificator Add-on. It definitely fixes my N1's wonkiness problem for the time being.
Thanks for listening!
Click to expand...
Click to collapse
If I'm not mistaken, CM has noted the source of the error (mic) and they are conjuring up a fix. It should most likely be ready to go in one of the next few nightlies.
Thanks! Didn't happen to come across that piece of information in my travels on xda forums.
markhm1978 said:
Thanks! Didn't happen to come across that piece of information in my travels on xda forums.
Click to expand...
Click to collapse
You must've taken a right instead of a left...
rickytenzer said:
If I'm not mistaken, CM has noted the source of the error (mic) and they are conjuring up a fix. It should most likely be ready to go in one of the next few nightlies.
Click to expand...
Click to collapse
That first attempt fix was released in build 27 earlier today.
Unfortunately some peoples are still reporting the call wonkiness.
rickytenzer said:
You must've taken a right instead of a left...
Click to expand...
Click to collapse
Yeah, it's pretty easy to get lost in all of the chocolaty goodness here.
baseballfanz said:
That first attempt fix was released in build 27 earlier today.
Unfortunately some peoples are still reporting the call wonkiness.
Click to expand...
Click to collapse
Thanks for the info. I am one of the unfortunate ones.
Just tried Build 28 and the phone call still wonks out. logcat snapshot attached.
Call Wonks for me on Build 29. Dewonkificator is still working as a temporary fix.
It's been hit or miss with me - no wonks until I think build 17 and then twenty-something...
It's still worth it - you get wonks in brand new phones sometimes and the solution isn't likely contained in a flash update within another 24 hours!
I will suffer the pain of wonkiness until it is finally solved by those brilliant minds working away on polishing this gorgeous CM7 port. Thank you - your efforts are REALLY appreciated here
should post this on the cyan forums if u havent already, im sure they could use it if it actually works.
Basil 123 said:
It's been hit or miss with me - no wonks until I think build 17 and then twenty-something...
It's still worth it - you get wonks in brand new phones sometimes and the solution isn't likely contained in a flash update within another 24 hours!
I will suffer the pain of wonkiness until it is finally solved by those brilliant minds working away on polishing this gorgeous CM7 port. Thank you - your efforts are REALLY appreciated here
Click to expand...
Click to collapse
I too love the CM7 port! So much that I'm about to donate $20 to buy Cyanogen some beer.
I figured instead of *****ing about how my phone calls are wonking out, I'd post some info to try and help with the situation and keep track of any wonks per build in this thread.
Have you tried Dewonkificator yet? It works really well for me. Here's the link: http://forum.xda-developers.com/showthread.php?t=935250
Buck Shot said:
should post this on the cyan forums if u havent already, im sure they could use it if it actually works.
Click to expand...
Click to collapse
I am creating an account on the Cyan forums now and will post a link to this thread.
Thanks for the suggestion.
Build 30, Wonks for me. Dewonkificator still working as a temp fix.
rickytenzer said:
You must've taken a right instead of a left...
Click to expand...
Click to collapse
lol you should have said: Sorry, but our princess is in another castle.
logcats are only half, posting dmesg's would be more helpful if any dev was going to check out your logs.
fitsnugly said:
lol you should have said: Sorry, but our princess is in another castle.
logcats are only half, posting dmesg's would be more helpful if any dev was going to check out your logs.
Click to expand...
Click to collapse
Thanks! I will look in to how to capture the dmesg's. While I look, do you have any suggestions for capturing this info?
fitsnugly said:
lol you should have said: Sorry, but our princess is in another castle.
logcats are only half, posting dmesg's would be more helpful if any dev was going to check out your logs.
Click to expand...
Click to collapse
Okay, figured it out. Attached the dmesg of my Wonkiness for Build 30.
Hi. I am on #31. The wonky is still here. dmesg output attached.
View attachment 2011-02-04-04.txt
I suppose this is a log of the wonky call:
Code:
<6>[ 644.924621] request_suspend_state: wakeup (3->0) at 640894655059 (2011-02-04 07:41:27.847267217 UTC)
<6>[ 644.927429] lcdc_resume: resuming
<6>[ 644.951568] mahimahi_ts_power: power 1
<6>[ 644.989440] lcdc_unblank: ()
<6>[ 644.990478] samsung_oled_panel_unblank: +()
<6>[ 645.281188] samsung_oled_panel_unblank: -()
<6>[ 648.953430] pcm_out: open
<6>[ 648.953918] acdb: 588 bytes for device 607, rate 48000.
<6>[ 650.724761] a1026_set_config: change to mode 1
<6>[ 650.724975] a1026_set_config: block write start (size = 56)
<6>[ 650.730865] a1026_set_config: block write end
<6>[ 650.755981] a1026_set_config: CMD ACK block read start
<3>[ 653.738586] msm_i2c msm_i2c.0: Error waiting for notbusy (0)
<3>[ 653.739074] msm_i2c msm_i2c.0: Transaction timed out
<3>[ 653.739868] msm_i2c msm_i2c.0: Error during data xfer 3e (-110)
<4>[ 653.740448] msm_i2c msm_i2c.0: Still the bus master, status 9b00, intf 0
<4>[ 653.741271] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 1
<4>[ 653.918853] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 653.919738] a1026_i2c_read: transfer error -110
<3>[ 653.920166] a1026_set_config: CMD ACK block read error
<6>[ 653.920928] a1026_i2c_sw_reset: 80020000
<3>[ 655.900756] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 655.901336] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 655.902130] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 656.080993] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 656.081573] a1026_i2c_write: transfer error -16
<3>[ 656.082000] a1026_ioctl: A1026_SET_CONFIG (1) error -110!
<6>[ 656.082824] a1026_set_config: change to mode 1
<6>[ 656.083282] a1026_set_config: block write start (size = 56)
<3>[ 658.063629] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 658.064239] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 658.065032] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 658.243072] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 658.243927] a1026_i2c_write: transfer error -16
<3>[ 658.244384] A1026 CMD block write error!
<6>[ 658.245117] a1026_i2c_sw_reset: 80020000
<3>[ 660.224914] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 660.225830] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 660.226318] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 660.405181] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 660.405761] a1026_i2c_write: transfer error -16
<3>[ 660.406524] a1026_ioctl: A1026_SET_CONFIG (1) error -16!
<6>[ 660.407012] a1026_set_config: change to mode 1
<6>[ 660.407440] a1026_set_config: block write start (size = 56)
<3>[ 662.387023] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 662.387634] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 662.388427] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 662.567291] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 662.568206] a1026_i2c_write: transfer error -16
<3>[ 662.568634] A1026 CMD block write error!
<6>[ 662.569427] a1026_i2c_sw_reset: 80020000
<3>[ 664.549560] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 664.550476] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 664.550964] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 664.729370] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 664.729919] a1026_i2c_write: transfer error -16
<3>[ 664.730712] a1026_ioctl: A1026_SET_CONFIG (1) error -16!
<6>[ 664.731170] a1026_set_config: change to mode 1
<6>[ 664.731628] a1026_set_config: block write start (size = 56)
<3>[ 666.721221] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 666.721801] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 666.722625] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 666.901550] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 666.902435] a1026_i2c_write: transfer error -16
<3>[ 666.902862] A1026 CMD block write error!
<6>[ 666.903656] a1026_i2c_sw_reset: 80020000
<3>[ 668.883361] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 668.884277] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 668.884765] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 669.063629] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 669.064178] a1026_i2c_write: transfer error -16
<3>[ 669.064941] a1026_ioctl: A1026_SET_CONFIG (1) error -16!
<3>[ 669.067352] msm_i2c msm_i2c.0: IRQ but nothing to do!, status 8302
<4>[ 669.083496] msm_i2c msm_i2c.0: Warning bus was busy (102)
<4>[ 669.085998] msm_i2c msm_i2c.0: 1 unrequested bytes read
<6>[ 669.127288] a1026_bootup_init: starting to load image (863 passes)...
<6>[ 672.336761] a1026_bootup_init: firmware loaded successfully
<6>[ 672.341888] batt: 54%, 3791 mV, -277 mA (-246 avg), 30.3 C, 728 mAh
<6>[ 672.497192] a1026_bootup_init: initialized!
<6>[ 672.658020] a1026_set_config: change to mode 1
<6>[ 672.658477] a1026_set_config: block write start (size = 56)
<6>[ 672.664947] a1026_set_config: block write end
<6>[ 672.687408] a1026_set_config: CMD ACK block read start
<6>[ 672.693542] a1026_set_config: CMD ACK block read end
<6>[ 672.747741] acdb: 974 bytes for device 2, rate 48000.
<6>[ 672.909057] acdb: 819 bytes for device 1, rate 8000.
<6>[ 673.097686] capella_cm3602_open
<6>[ 673.097869] capella_cm3602_ioctl cmd 2
<6>[ 673.098022] capella_cm3602_enable
<6>[ 673.098175] proximity 1
<6>[ 673.121124] request_suspend_state: wakeup (0->0) at 669063729306 (2011-02-04 07:41:56.016341464 UTC)
<6>[ 682.863403] capella_cm3602_ioctl cmd 2
<6>[ 682.863739] capella_cm3602_disable
<6>[ 682.864044] capella_cm3602_release
<6>[ 682.864349] capella_cm3602_disable
<6>[ 682.864868] capella_cm3602_disable: already disabled
<6>[ 682.874908] a1026_set_config: change to mode 13
<6>[ 682.875457] a1026_set_config: block write start (size = 16)
<6>[ 682.877563] a1026_set_config: block write end
<6>[ 682.907012] a1026_set_config: CMD ACK block read start
<6>[ 682.908966] a1026_set_config: CMD ACK block read end
<6>[ 682.909271] acdb: 871 bytes for device 507, rate 8000.
<6>[ 685.739837] pcm_out: release
PS @markhm1978
Compared your dmesg output with mine. It is quite the same...
dolphin77 said:
Hi. I am on #31. The wonky is still here. dmesg output attached.
View attachment 508500
I suppose this is a log of the wonky call:
Code:
<6>[ 644.924621] request_suspend_state: wakeup (3->0) at 640894655059 (2011-02-04 07:41:27.847267217 UTC)
<6>[ 644.927429] lcdc_resume: resuming
<6>[ 644.951568] mahimahi_ts_power: power 1
<6>[ 644.989440] lcdc_unblank: ()
<6>[ 644.990478] samsung_oled_panel_unblank: +()
<6>[ 645.281188] samsung_oled_panel_unblank: -()
<6>[ 648.953430] pcm_out: open
<6>[ 648.953918] acdb: 588 bytes for device 607, rate 48000.
<6>[ 650.724761] a1026_set_config: change to mode 1
<6>[ 650.724975] a1026_set_config: block write start (size = 56)
<6>[ 650.730865] a1026_set_config: block write end
<6>[ 650.755981] a1026_set_config: CMD ACK block read start
<3>[ 653.738586] msm_i2c msm_i2c.0: Error waiting for notbusy (0)
<3>[ 653.739074] msm_i2c msm_i2c.0: Transaction timed out
<3>[ 653.739868] msm_i2c msm_i2c.0: Error during data xfer 3e (-110)
<4>[ 653.740448] msm_i2c msm_i2c.0: Still the bus master, status 9b00, intf 0
<4>[ 653.741271] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 1
<4>[ 653.918853] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 653.919738] a1026_i2c_read: transfer error -110
<3>[ 653.920166] a1026_set_config: CMD ACK block read error
<6>[ 653.920928] a1026_i2c_sw_reset: 80020000
<3>[ 655.900756] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 655.901336] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 655.902130] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 656.080993] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 656.081573] a1026_i2c_write: transfer error -16
<3>[ 656.082000] a1026_ioctl: A1026_SET_CONFIG (1) error -110!
<6>[ 656.082824] a1026_set_config: change to mode 1
<6>[ 656.083282] a1026_set_config: block write start (size = 56)
<3>[ 658.063629] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 658.064239] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 658.065032] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 658.243072] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 658.243927] a1026_i2c_write: transfer error -16
<3>[ 658.244384] A1026 CMD block write error!
<6>[ 658.245117] a1026_i2c_sw_reset: 80020000
<3>[ 660.224914] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 660.225830] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 660.226318] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 660.405181] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 660.405761] a1026_i2c_write: transfer error -16
<3>[ 660.406524] a1026_ioctl: A1026_SET_CONFIG (1) error -16!
<6>[ 660.407012] a1026_set_config: change to mode 1
<6>[ 660.407440] a1026_set_config: block write start (size = 56)
<3>[ 662.387023] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 662.387634] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 662.388427] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 662.567291] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 662.568206] a1026_i2c_write: transfer error -16
<3>[ 662.568634] A1026 CMD block write error!
<6>[ 662.569427] a1026_i2c_sw_reset: 80020000
<3>[ 664.549560] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 664.550476] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 664.550964] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 664.729370] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 664.729919] a1026_i2c_write: transfer error -16
<3>[ 664.730712] a1026_ioctl: A1026_SET_CONFIG (1) error -16!
<6>[ 664.731170] a1026_set_config: change to mode 1
<6>[ 664.731628] a1026_set_config: block write start (size = 56)
<3>[ 666.721221] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 666.721801] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 666.722625] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 666.901550] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 666.902435] a1026_i2c_write: transfer error -16
<3>[ 666.902862] A1026 CMD block write error!
<6>[ 666.903656] a1026_i2c_sw_reset: 80020000
<3>[ 668.883361] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 668.884277] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 668.884765] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 669.063629] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 669.064178] a1026_i2c_write: transfer error -16
<3>[ 669.064941] a1026_ioctl: A1026_SET_CONFIG (1) error -16!
<3>[ 669.067352] msm_i2c msm_i2c.0: IRQ but nothing to do!, status 8302
<4>[ 669.083496] msm_i2c msm_i2c.0: Warning bus was busy (102)
<4>[ 669.085998] msm_i2c msm_i2c.0: 1 unrequested bytes read
<6>[ 669.127288] a1026_bootup_init: starting to load image (863 passes)...
<6>[ 672.336761] a1026_bootup_init: firmware loaded successfully
<6>[ 672.341888] batt: 54%, 3791 mV, -277 mA (-246 avg), 30.3 C, 728 mAh
<6>[ 672.497192] a1026_bootup_init: initialized!
<6>[ 672.658020] a1026_set_config: change to mode 1
<6>[ 672.658477] a1026_set_config: block write start (size = 56)
<6>[ 672.664947] a1026_set_config: block write end
<6>[ 672.687408] a1026_set_config: CMD ACK block read start
<6>[ 672.693542] a1026_set_config: CMD ACK block read end
<6>[ 672.747741] acdb: 974 bytes for device 2, rate 48000.
<6>[ 672.909057] acdb: 819 bytes for device 1, rate 8000.
<6>[ 673.097686] capella_cm3602_open
<6>[ 673.097869] capella_cm3602_ioctl cmd 2
<6>[ 673.098022] capella_cm3602_enable
<6>[ 673.098175] proximity 1
<6>[ 673.121124] request_suspend_state: wakeup (0->0) at 669063729306 (2011-02-04 07:41:56.016341464 UTC)
<6>[ 682.863403] capella_cm3602_ioctl cmd 2
<6>[ 682.863739] capella_cm3602_disable
<6>[ 682.864044] capella_cm3602_release
<6>[ 682.864349] capella_cm3602_disable
<6>[ 682.864868] capella_cm3602_disable: already disabled
<6>[ 682.874908] a1026_set_config: change to mode 13
<6>[ 682.875457] a1026_set_config: block write start (size = 16)
<6>[ 682.877563] a1026_set_config: block write end
<6>[ 682.907012] a1026_set_config: CMD ACK block read start
<6>[ 682.908966] a1026_set_config: CMD ACK block read end
<6>[ 682.909271] acdb: 871 bytes for device 507, rate 8000.
<6>[ 685.739837] pcm_out: release
PS @markhm1978
Compared your dmesg output with mine. It is quite the same...
Click to expand...
Click to collapse
It is quite the same. I am on 31 also, still experiencing the Wonkiness. Will post more logs when 32 hits.
Wonks for me on Build 32. Dewonkificator still working as a temporary fix: http://forum.xda-developers.com/showthread.php?t=935250
Related
Every so often my phone just refuses to wake up. I press menu and the keys light up but screen never does. I press call+menu+end to reboot and screen still doesn't wake up. Second time I try call+menu+end screen finally wakes up and device reboots. I'm running CyanogenMod 3.6.8.1 and have a custom bootscreen. Does this seem like a hardware problem or software? Any help is much appreciated, thanks.
After flashing a new ROM, the problem seemed to go away but came back. Everything seems to power on except the lcd. I can tap and hold to move an icon but nothing shows on the screen. Is there a certain app that would cause this or is it hardware? I've disabled compcache and swap and it made no difference. Any advice appreciated
I uncovered a little more info using dmesg over adb. Heres what it said
Code:
<3>[ 569.121337] Freezing of user space aborted
<4>[ 569.126312]
<4>[ 569.128173] Restarting tasks ... done.
<6>[ 569.144226] suspend: exit suspend, ret = -11 (2009-07-26 16:02:19.600952156 UTC)
<6>[ 569.536926] PM: Syncing filesystems ... done.
<4>[ 569.544097] Freezing user space processes ... (elapsed 0.00 seconds) done.
<4>[ 569.556793] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
<4>[ 569.570587] trout_sdslot_switchvdd: Disabling SD slot power
<4>[ 569.576934] trout_sdslot_switchvdd: Setting level to 2950
<6>[ 569.588989] wakeup wake lock: SMD_RPCCALL
<4>[ 569.595153] Restarting tasks ... done.
<6>[ 570.164764] suspend: exit suspend, ret = 0 (2009-07-26 16:06:04.070281996 UTC)
<6>[ 570.679016] PM: Syncing filesystems ... done.
<4>[ 570.686401] Freezing user space processes ... (elapsed 0.00 seconds) done.
<4>[ 570.702178] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
<4>[ 570.717041] trout_sdslot_switchvdd: Disabling SD slot power
<6>[ 570.717041] wakeup wake lock: gpio_kp
<4>[ 570.722290] trout_sdslot_switchvdd: Setting level to 2950
<4>[ 570.737670] Restarting tasks ... <6>request_suspend_state: wakeup (3->0) at 566131612099 (2009-07-26 16:06:43.522277832 UTC)
<4>[ 570.768218] done.
<7>[ 571.308227] mmc_queue_thread: status 0x00000900
<6>[ 571.313720] suspend: exit suspend, ret = 0 (2009-07-26 16:06:44.077117942 UTC)
<6>[ 571.537597] mddi_remote_read(150000) timeout (-1 -973073920 0)
<6>[ 571.544189] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val d curr_rev_ptr 0
<6>[ 571.657470] mddi_remote_read(150000) timeout (-1 -1 0)
<6>[ 571.662902] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val d curr_rev_ptr 0
<6>[ 571.767456] mddi_remote_read(150000) timeout (-1 -1 0)
<6>[ 571.773010] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val d curr_rev_ptr 0
<4>[ 571.783599] unknown panel id at mddi_enable
<6>[ 571.788238] msmfb: panel resume failed, not resuming fb
<6>[ 576.621246] hsusb: OFFLINE -> ONLINE
<6>[ 576.625518] hsusb: reset controller
<4>[ 576.687469] ulpi: write 0x40 to 0x31
<4>[ 576.691497] ulpi: write 0x1d to 0x0d
<4>[ 576.695434] ulpi: write 0x1d to 0x10
<6>[ 576.699768] ept #0 out max:64 head:ffa0c000 bit:0
<6>[ 576.704833] ept #1 out max:512 head:ffa0c080 bit:1
<6>[ 576.710327] ept #2 out max:512 head:ffa0c100 bit:2
<6>[ 576.715515] ept #0 in max:64 head:ffa0c040 bit:16
<6>[ 576.720642] ept #1 in max:512 head:ffa0c0c0 bit:17
<6>[ 576.726074] ept #2 in max:512 head:ffa0c140 bit:18
<6>[ 576.731597] usb: notify offline
<6>[ 576.753906] usb: suspend
<6>[ 576.936981] usb: reset
<6>[ 576.939270] usb: portchange USB_SPEED_HIGH
<6>[ 577.097961] usb: reset
<6>[ 577.100555] usb: portchange USB_SPEED_HIGH
<6>[ 577.333526] usb_mass_storage usb_mass_storage: config #1
<6>[ 578.735534] audmgr_rpc_thread() start
<6>[ 578.736206] audio_enable()
<6>[ 578.736236] ++++++++++++++++++++++++++++++
<6>[ 578.745056] audmgr: rpc_reply status 0
<6>[ 578.758941] audmgr: rpc READY handle=0x00000000
<6>[ 578.837646] audmgr: rpc CODEC_CONFIG volume=0x00002000
<6>[ 578.837738] audpp: enable
<6>[ 578.837768] adsp: opening module AUDPPTASK
<6>[ 578.850708] adsp: module AUDPPTASK has been registered
<6>[ 578.850738] msm_adsp_enable() 'AUDPPTASK'state[0] id[4]
<6>[ 578.861938] adsp: rpc event=0, proc_id=2, module=4, image=0
<6>[ 578.861999] adsp: module AUDPPTASK: READY
<6>[ 578.862304] audpp: ENABLE
<6>[ 578.862365] audio_dsp_event: CFG_MSG ENABLE
<3>[ 579.530090] audpp: DMA missed obj=20
<6>[ 582.459472] audio_disable()
<6>[ 582.462738] audio_dsp_event: CFG_MSG DISABLE
<6>[ 582.467712] audpp: disable
<6>[ 582.470825] msm_adsp_disable() 'AUDPPTASK'
<6>[ 582.475250] audpp: DISABLE
<6>[ 582.479705] adsp: closing module AUDPPTASK
<6>[ 582.484252] adsp: disable interrupt
<6>[ 582.490600] audmgr: rpc_reply status 0
<3>[ 582.520477] audmgr: DISABLED
<6>[ 582.523986] ------------------------------
[B]<6>[ 637.073669] request_suspend_state: sleep (0->3) at 632446370407 (2009-07-26 16:07:49.837036140 UTC)
<6>[ 637.187530] mddi_remote_read(150000) timeout (-1 99 0)
<6>[ 637.193176] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val d curr_rev_ptr 0
<6>[ 637.317962] mddi_remote_read(150000) timeout (-1 -1 0)
<6>[ 637.323577] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val d curr_rev_ptr 0
<6>[ 637.457519] mddi_remote_read(150000) timeout (-1 -1 0)
<6>[ 637.463104] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val d curr_rev_ptr 0
<4>[ 637.478057] unknown panel_id: 3
<4>[ 637.788482] save exit: isCheckpointed 1
<6>[ 939.424530] request_suspend_state: wakeup (3->0) at 934797200486 (2009-07-26 16:12:52.187896737 UTC)
<6>[ 939.647521] mddi_remote_read(150000) timeout (-1 -973073920 0)
<6>[ 939.653656] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val d curr_rev_ptr 0
<6>[ 939.757568] mddi_remote_read(150000) timeout (-1 -1 0)
<6>[ 939.763153] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val d curr_rev_ptr 0
<6>[ 939.867553] mddi_remote_read(150000) timeout (-1 -1 0)
<6>[ 939.872985] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val d curr_rev_ptr 0
<4>[ 939.883544] unknown panel id at mddi_enable
<6>[ 939.887969] msmfb: panel resume failed, not resuming fb
<4>[ 939.929138] msm_i2c msm_i2c.0: Warning bus was busy (5)
<6>[ 949.676208] request_suspend_state: sleep (0->3) at 945048909481 (2009-07-26 16:13:02.439605732 UTC)
<6>[ 949.797393] mddi_remote_read(150000) timeout (-1 98 0)
<6>[ 949.803283] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val d curr_rev_ptr 0
<6>[ 949.907409] mddi_remote_read(150000) timeout (-1 -1 0)
<6>[ 949.913024] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val d curr_rev_ptr 0
<6>[ 950.037567] mddi_remote_read(150000) timeout (-1 -1 0)
<6>[ 950.037628] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val d curr_rev_ptr 0
<4>[ 950.038269] unknown panel_id: 3
<4>[ 950.745727] save exit: isCheckpointed 1[/B]
Is the code in bold at the end my problem? Is my hardware broken or could this be just a software bug?
I also tried an older CM build and same thing is happening. Is this officially hardware? Would I be able to get it replaced by HTC considering I got it unlocked on eBay?
umm u might wanna wipe...n if that doesnt work..(drastic measures) run dreaming.nbh in the spl bootloader and reroot
I've wiped and flashed a different ROM twice, no luck. How do I run dreaming.nbh? From the shell in recovery?
So i got the Tab and had a chance to use it extensively over the past few days.
Below is my day-to-day use comparison with the SGS:
1) Quadrant score is about 1000 (just like 2.2 on SGS) but THERE IS NO LAG. i have about 87 apps installed and it runs flawlessly.
2) GPS is very accurate and have a stronger lock signal. It gets a lock even at the first floor of my house, where the SGS would never lock. Too a drive from San Jose to San Francisco - it never lost track.
3) Screen has "color saturation level" option under the display settings. Even though the Tab does not have SAMOLED screen, if you pull the saturation level all the way to the max, you get a very vibrant color display. not as milky as other TFT screens.
4) The browser does not lag as much as on JPK. it is not super smooth (even with flash disabled), but it does not lag as much. i would hope this can be improved with future firmware.
5) The Tab has 444MB RAM available to the user. it usually uses 280MB. rarely i see usage goes all the way up to 328MB. There is plenty of RAM to go around and it seems to have a much better memory management algorithm than the SGS on JPK (i do not notice memory leaks).
6) Battery life on the Tab is impressive. seems like you can get about 8 hours of CONSTANT usage (i.e. with the screen on) on s single charge. Of course if you don't keep the screen on all the time, you can easily get through the day and then some.
7) Flash 10.1 runs the same as on the SGS. there is room for optimization . My DroidX runs flash much better than both SGS and the Tab.
8) The LED flash is fairly strong. it is not Xenon flash but it is fairly strong for a single LED.
9) The stereo speakers are loud and crisp on the Tab.
10) The TAB DOES fit in the back and front jeans pockets. you do not need an XXL per of jeans for it to fit. it sticks our of the back pocket but it surely fits. I would not site down though while having the tab in my pocket.
11) It has a better reception comparing to the SGS by at least 5db on average (maybe bigger and better antenna? maybe it has more power because it is not designed to be next to our heads, not sure)
12) Some apps on the Tab do not scale well. Samsung sorta have a work around by enabling "compatibility mode" by default in the Android OS. what this does is centering such apps while showing them on a smaller part of the screen. most apps i testes do scale. Those that do not are showing like the iphone apps on the ipad (smaller and in the center of the screen).
13) typing on the TAB is actually very convenient. I use smart Keyboard pro and it is extremely responsive.
14) Graphics FPS are capped at 60fps on the Tab vs 56fps on the SGS.
Overall i am extremely pleased with the Tab. it is an amazing device and very convenient and responsive to work with. Get a nice bluetooth headset and it can easily become my "work phone" while i carry it around in my bag. I am still going to be using the SGS with i want to walk around with something "lighter" LOL.
If the Tab's 2.2 stability and speed is what Samsung has i mind for the SGS, i will be fairly pleased.
The ONLY thing Samsung needs to improve on both the SGS and the Tab is the browser fluidity. I would like to see it as fluid as the Droid X with flash enabled. i know it is possible as the browsing the web on the X is an absolute pleasure.
Feel free to ask any questions you would like about the Tab. i will try to answer from time to time.
Can you actually make phone calls with it? Does it have the phone app/button like the SGS or you can only make calls via VOIP? Can you receive call? assign a number?
I'm wondering if it could replace my SGS completely and use the TAB along with a bluetooth headset to make all my calls.
I have the euro version. Yes it is a full fledged phone if you have a Bluetooth headset.
Nice comparison. Hope that some, if not all of these improvements are received by us with the official froyo update for the SGS. However, I didn't see the point in this comparison really. A phone and a tablet fit completely different applications, even if the manufacturer and the internal hardware is same...
clubtech said:
Feel free to ask any questions you would like about the Tab. i will try to answer from time to time.
Click to expand...
Click to collapse
It's a lot to ask but do you think you could:
1. Install Android Terminal Emulator on the Tab, or use adb shell if you have installed the Android SDK on your PC.
2. Restart the Tab.
3. As soon as possible after the restart, go into Terminal Emulator and type "toolbox dmesg" (Enter) at the command line
4. Also type "toolbox cat /proc/meminfo" (Enter)
4. Paste the messages you get here.
You don't need to root the device to do this.
This will let us look at the memory allocation on this device, including the memory reserved for the hardware at startup. Thanks!
Hi!
What about screen quality? Viewing angles? Do colours change when you are looking at the screen from some angle? What about minimum brightness - is it good for reading books in dark conditions? And how the screen looks under the sun?
Prasad007 said:
Nice comparison. Hope that some, if not all of these improvements are received by us with the official froyo update for the SGS. However, I didn't see the point in this comparison really. A phone and a tablet fit completely different applications, even if the manufacturer and the internal hardware is same...
Click to expand...
Click to collapse
Disagree, first I barely use the phone as a phone, if these were announced at the same time I would've seriously considered the tab instead, particularly if I could've gotten away with cheaper monthly rates and skype. Second, I think your assumption is based on having the SGS, or any smartphone, but that isn't the only audience for this device. In all likelihood, a high majority of us have an SGS, but those who do and don't will be intrigued if they are interested in both or have the SGS and were wondering what this would bring to the table.
I don't disagree with what you're saying, but this comparison is only applicable in terms of specs, features and the wide range of applications that both products can handle. I think we are forgetting that a phone is still primarily a phone! So that is no reason to put a phone and a tablet pc in the same basket. You will never see smartphones being replaced by tablets in the decades to come... In fact it would more likely be quite the opposite, for that is miniaturization. I would like to see phones with very high computing power, and that are easily, conveniently and wirelessly connectable to large screens like monitors and TVs, thereby completely replacing larger computing systems AKA Tab (or even conventional PC's for that matter...). Nanotech anyone ? ;-)
Still, the OP will seemingly be useful towards SGS owners and that's cool!
Hi Congrats on getting the Tab!
For the phone functions eg making calls, does it work without a Bluetooth headset or the speaker phone function? Ie. Could you hold it you your ear and use it like a big (albeit dorky. Heh) phone? What I want is to be able to replace my SGS completely :]
I think it's definitely in the eye of the beholder, until it's easier to replicate what you have on your screen into a computer/TV (I'm thinking wireless, DLNA not covering it, and preferably nothing like a TV-out where you are replicating the screen and therefore, I assume, requiring the screen to be on). Essentially, a wireless docking station, much like bluetooth with auto-pairing potential.
I think the fact that many people aren't interested in tablets is a sign that people don't just want smaller, they want something with plenty of function. Connecting to screens you already have with pocket computers would do that, however, I'm thinking of multimedia on the go and 4.0-4.3" barely cuts it in my book. Personally, I have absolutely no use for a 2.0" device if a 4.0" is just as powerful. If/when things get cheap and powerful enough, yes, redundancy would make me desire something that is essentially weightless and unobtrusive, but until then I don't want smaller than my 4.0" (personally, I don't try to talk for everyone, but the desire for larger devices than 3.5" somewhat speaks for itself.)
Also, I think something with the best of both worlds, small and portable, yet potential for better magazine/e-reader/multimedia on the go is here Future of Screen Technology by TATMobileUI , featured on the Engadget show. There is overlap in our thoughts and where we agree, I understand your original point better, but don't fully agree with it still. If people only wanted smaller, the iPad and Galaxy Tabs wouldn't even exist as these are smartphones masquerading as tablets (product differentiation, even archos is calling a device that might be less than 3" a tablet, it's just a buzz word in a lot of ways). Nonetheless, some good points put in by you.
TheBeano said:
It's a lot to ask but do you think you could:
1. Install Android Terminal Emulator on the Tab, or use adb shell if you have installed the Android SDK on your PC.
2. Restart the Tab.
3. As soon as possible after the restart, go into Terminal Emulator and type "toolbox dmesg" (Enter) at the command line
4. Also type "toolbox cat /proc/meminfo" (Enter)
4. Paste the messages you get here.
You don't need to root the device to do this.
This will let us look at the memory allocation on this device, including the memory reserved for the hardware at startup. Thanks!
Click to expand...
Click to collapse
$ toolbox cat /proc/meminfo
toolbox cat /proc/meminfo
MemTotal: 454248 kB
MemFree: 119708 kB
Buffers: 3892 kB
Cached: 268808 kB
SwapCached: 0 kB
Active: 105148 kB
Inactive: 200552 kB
Active(anon): 33056 kB
Inactive(anon): 0 kB
Active(file): 72092 kB
Inactive(file): 200552 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 136 kB
Writeback: 0 kB
AnonPages: 33008 kB
Mapped: 52100 kB
Shmem: 56 kB
Slab: 9124 kB
SReclaimable: 4052 kB
SUnreclaim: 5072 kB
KernelStack: 1120 kB
PageTables: 2520 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 227124 kB
Committed_AS: 602484 kB
VmallocTotal: 155648 kB
VmallocUsed: 63288 kB
VmallocChunk: 65532 kB
<4>[ 3.392077] [SIF:INF] Number of Free Block ( 25)
<4>[ 3.392088] [SIF:INF] Active Log List : Num ( 8)
<4>[ 3.392100] [SIF:INF] ===> STL Zone[ 4, 0] Open Zone Post
<4>[ 3.393005] [SIF:INF] Partition [0, 24] open is success
<4>[ 3.400760] [SIF:INF] Zone[ 4, 0]: nDgn( 0) nVbn( 33) S( 0)-E( 53)
nCPOffs( 54)
<4>[ 3.401428] [SIF:INF] Zone[ 4, 0]: nDgn( 4) nVbn( 26) S( 28)-E( 28)
nCPOffs( 29)
<4>[ 3.403713] [SIF:INF] Zone[ 4, 0]: nDgn( 1) nVbn( 67) S( 7)-E( 17)
nCPOffs( 18)
<4>[ 3.413550] [BIF: ] FSR VERSION: FSR_1.2.1p1_b129_RTM
<4>[ 3.413571] [BIF: ] FSR_BML_Open(nVol:0, nFlag:0x0, nOpenCnt:6) / 1176
line
<4>[ 3.413605] [SIF:INF] ===> STL Clst[ 0] Scan Root Info
<4>[ 3.414211] [SIF:INF] ===> STL Zone[ 0, 0] Open Zone Meta
<4>[ 3.415104] [SIF:INF] Latest Header Index ( 0) Vbn ( 2)
<4>[ 3.416408] [SIF:INF] Latest Header Clean Page Offset ( 9)
<4>[ 3.416421] [SIF:INF] POR write timer : 0x2d
<4>[ 3.416580] [SIF:INF] Latest Context BlockIdx ( 0) Offset ( 8)
Vpn ( 136)
<4>[ 3.416743] [SIF:INF] Number of Free Block ( 2)
<4>[ 3.416777] [SIF:INF] Active Log List : Num ( 8)
<4>[ 3.416795] [SIF:INF] ===> STL Zone[ 0, 0] Open Zone Post
<4>[ 3.417704] [SIF:INF] Partition [0, 20] open is success
<4>[ 3.419321] [SIF:INF] Zone[ 0, 0]: nDgn( 0) nVbn( 23) S( 2)-E( 10)
nCPOffs( 11)
<4>[ 3.422316] [SIF:INF] Zone[ 0, 0]: nDgn( 1) nVbn( 5) S( 0)-E( 17)
nCPOffs( 18)
<4>[ 3.440639] [onedram_init]
<4>[ 3.440765] [onedram_probe]
<4>[ 3.455304] [svnet_init]
<4>[ 3.466788] [modemctl_init]
<4>[ 3.466913] [modemctl_probe]
<6>[ 3.467643] modemctl xmm: PHONE ACTIVE: 0
<4>[ 3.473325] Storage device init
<4>[ 3.480423] ######## bthid_init: ########
<4>[ 3.481236] ######## bthid_init: done ########
<3>[ 3.485622] init: ro.build.id:FROYO
<3>[ 3.487717] init: ro.build.display.id:FROYO.XXJI5
<3>[ 3.492354] init: ro.build.version.incremental:XXJI5
<3>[ 3.497295] init: ro.build.version.sdk:8
<3>[ 3.501202] init: ro.build.version.codename:REL
<3>[ 3.505759] init: ro.build.version.release:2.2
<3>[ 3.510187] init: ro.build.date:2010. 09. 12. (일) 05:47:00 KST
<3>[ 3.516171] init: ro.build.date.utc:1284238020
<3>[ 3.520589] init: ro.build.type:user
<3>[ 3.524135] init: ro.build.user:root
<3>[ 3.527697] init: ro.build.host:sep-56
<3>[ 3.531429] init: ro.build.tags:release-keys
<3>[ 3.535682] init: ro.product.model:GT-P1000
<3>[ 3.539838] init: ro.product.brand:samsung
<3>[ 3.543915] init: ro.product.name:GT-P1000
<3>[ 3.547992] init: ro.product.device:GT-P1000
<3>[ 3.552244] init: ro.product.board:GT-P1000
<3>[ 3.556406] init: ro.product.cpu.abi:armeabi-v7a
<3>[ 3.561001] init: ro.product.cpu.abi2:armeabi
<3>[ 3.565332] init: ro.product.manufacturer:samsung
<3>[ 3.570024] init: ro.product.locale.language:en
<3>[ 3.574524] init: ro.product.locale.region:GB
<3>[ 3.578867] init: ro.wifi.channels:
<3>[ 3.582338] init: ro.board.platform:s5pc110
<3>[ 3.586524] init: ro.build.product:GT-P1000
<3>[ 3.590668] init: ro.build.description:GT-P1000-user 2.2 FROYO XXJI5 relea
se-keys
<3>[ 3.598125] init: ro.build.fingerprint:samsung/GT-P1000/GT-P1000/GT-P1000:
2.2/FROYO/XXJI5:user/release-keys
<3>[ 3.607842] init: ro.build.PDA1000XXJI5
<3>[ 3.611826] init: ro.build.hidden_ver1000XXJI5
<3>[ 3.616428] init: ro.build.changelist:562468
<3>[ 3.620678] init: ro.tether.denied:false
<3>[ 3.624549] init: rild.libpath:/system/lib/libsec-ril.so
<3>[ 3.629824] init: rild.libargs:-d /dev/ttyS0
<3>[ 3.634077] init: ro.sf.lcd_density:240
<3>[ 3.637890] init: ro.sf.hwrotation:90
<3>[ 3.641533] init: dalvik.vm.heapsize:48m
<3>[ 3.645438] init: ro.opengles.version:131072
<3>[ 3.649687] init: windowsmgr.max_events_per_sec:60
<3>[ 3.654459] init: keyinputqueue.use_finger_id:true
<3>[ 3.659227] init: viewConfig.adjusted_density:1.0
<3>[ 3.663910] init: ro.url.legal:http://www.google.com/intl/%s/mobile/androi
d/basic/phone-legal.html
<3>[ 3.672849] init: ro.url.legal.android_privacy:http://www.google.com/intl/
%s/mobile/android/basic/privacy.html
<3>[ 3.682819] init: ro.com.google.locationfeatures:1
<3>[ 3.687591] init: ro.setupwizard.modeISABLED
<3>[ 3.692011] init: ro.com.google.gmsversion:2.2_r5
<3>[ 3.696695] init: media.stagefright.enable-player:true
<3>[ 3.701815] init: media.stagefright.enable-meta:true
<3>[ 3.706762] init: media.stagefright.enable-scan:true
<3>[ 3.711698] init: media.stagefright.enable-http:true
<3>[ 3.716647] init: keyguard.no_require_sim:true
<3>[ 3.721066] init: ro.config.ringtone:01_Samsung_tune.ogg
<3>[ 3.726358] init: ro.config.notification_sound:01_Sherbet.ogg
<3>[ 3.732081] init: ro.config.alarm_alert:Good_Morning.ogg
<3>[ 3.737376] init: ro.config.media_sound:Media_preview_Beyond_Samsung.ogg
<3>[ 3.744050] init: net.bt.name:Android
<3>[ 3.747692] init: net.change:net.bt.name
<3>[ 3.751600] init: dalvik.vm.stack-trace-file:/data/anr/traces.txt
<3>[ 3.758019] init: ro.com.google.clientidbase:android-skt-kr
<3>[ 3.763220] init: ro.com.google.clientidbase.yt:android-skt-kr
<3>[ 3.769032] init: ro.com.google.clientidbase.am:android-skt-kr
<3>[ 3.774841] init: ro.com.google.clientidbase.gmm:android-skt-kr
<3>[ 3.780740] init: ro.com.google.clientidbase.vs:android-skt-kr
<3>[ 3.786566] init: ro.com.google.clientidbase:android-samsung
<3>[ 3.792173] init: ro.com.google.clientidbase.yt:android-samsung
<3>[ 3.798067] init: ro.com.google.clientidbase.am:android-samsung
<3>[ 3.803971] init: ro.com.google.clientidbase.gmm:android-samsung
<3>[ 3.809950] init: ro.com.google.clientidbase.vs:android-samsung
<3>[ 3.817418] init: persist.sys.country:US
<3>[ 3.819984] init: persist.sys.localevar:
<3>[ 3.824522] init: persist.service.adb.enable:1
<3>[ 3.828937] init: persist.sys.timezone:America/Los_Angeles
<3>[ 3.834401] init: persist.sys.language:en
<3>[ 3.838498] init: ro.FOREGROUND_APP_ADJ:0
<3>[ 3.841674] init: ro.VISIBLE_APP_ADJ:1
<3>[ 3.845394] init: ro.SECONDARY_SERVER_ADJ:2
<3>[ 3.849556] init: ro.BACKUP_APP_ADJ:2
<3>[ 3.853206] init: ro.HOME_APP_ADJ:4
<3>[ 3.856673] init: ro.HIDDEN_APP_MIN_ADJ:7
<3>[ 3.860661] init: ro.CONTENT_PROVIDER_ADJ:14
<3>[ 3.864907] init: ro.EMPTY_APP_ADJ:15
<3>[ 3.868555] init: ro.FOREGROUND_APP_MEM:1536
<3>[ 3.872801] init: ro.VISIBLE_APP_MEM:2048
<3>[ 3.876792] init: ro.SECONDARY_SERVER_MEM:4096
<3>[ 3.881216] init: ro.BACKUP_APP_MEM:4096
<3>[ 3.885123] init: ro.HOME_APP_MEM:4096
<3>[ 3.888848] init: ro.HIDDEN_APP_MEM:5120
<3>[ 3.892752] init: ro.CONTENT_PROVIDER_MEM:5632
<3>[ 3.897175] init: ro.EMPTY_APP_MEM:6144
<3>[ 3.901002] init: wifi.interface:eth0
<3>[ 3.904633] init: ro.bt.bdaddr_path:/data/misc/bluetoothd/bt_addr
<3>[ 3.911598] init: net.tcp.buffersize.default:4096,87380,196608,4096,16384,
110208
<3>[ 3.918091] init: net.change:net.tcp.buffersize.default
<3>[ 3.923291] init: net.tcp.buffersize.wifi:4095,87380,393216,4096,16384,110
208
<3>[ 3.930398] init: net.change:net.tcp.buffersize.wifi
<3>[ 3.935353] init: net.tcp.buffersize.umts:4094,87380,196608,4096,16384,110
208
<3>[ 3.942451] init: net.change:net.tcp.buffersize.umts
<3>[ 3.947400] init: net.tcp.buffersize.edge:4093,26280,35040,4096,16384,3504
0
<3>[ 3.954333] init: net.change:net.tcp.buffersize.edge
<3>[ 3.959284] init: net.tcp.buffersize.gprs:4092,8760,11680,4096,8760,11680
<3>[ 3.966042] init: net.change:net.tcp.buffersize.gprs
<3>[ 3.973814] init: cannot find 'dd', disabling 'create_dfta'
<3>[ 3.978236] init: init.svc.console:running
<3>[ 3.982260] init: init.svc.playlogo:running
<3>[ 3.991717] init: init.svc.pvrsrvinit:running
<3>[ 3.994847] init: init.svc.servicemanager:running
<4>[ 4.001280] [SIF:INF] Zone[ 2, 0]: nDgn( 5) nVbn( 28) S( 0)-E( 1)
nCPOffs( 2)
<3>[ 4.015334] init: init.svc.vold:running
<3>[ 4.017983] init: init.svc.notified_event:running
<3>[ 4.051242] init: init.svc.netd:running
<3>[ 4.068426] init: init.svc.debuggerd:running
<3>[ 4.095162] init: init.svc.ril-daemon:running
<3>[ 4.113133] init: init.svc.DR-deamon:running
<3>[ 4.124102] init: init.svc.mobex-daemon:running
<3>[ 4.146657] init: init.svc.glgps:running
<3>[ 4.164714] init: init.svc.zygote:running
<3>[ 4.181102] init: init.svc.media:running
<6>[ 4.183700] PVR_KWarning): SysFinalise: Version string: SGX540 S5PC110 [
475, services4/system/s5pc110/sysconfig.c]
<3>[ 4.192597] init: init.svc.killmediaserver:running
<6>[ 4.200570] warning: `rild' uses 32-bit capabilities (legacy support in us
e)
<3>[ 4.216998] init: init.svc.dbus:running
<3>[ 4.225825] init: init.svc.installd:running
<3>[ 4.228619] init: cannot find '/system/etc/install-recovery.sh', disabling
'flash_recovery'
<3>[ 4.286769] init: init.svc.keystore:running
<3>[ 4.303820] init: init.svc.immvibed:running
<3>[ 4.320610] init: init.svc.tvout:running
<3>[ 4.335457] init: init.svc.adbd:running
<3>[ 4.337927] init: init.svc.pvrsrvinit:stopped
<6>[ 4.368049] [USB] adb_enable_open
<4>[ 4.368063] [USB] enable_adb
<4>[ 4.368073] [USB] enable_adb - enable(0x10), prev_status(0x04)
<4>[ 4.368082] Here is [email protected]@@@
<4>[ 4.368121] [enable_adb]USBSTATUS_ADB
<4>[ 4.368131] [usb_change_config] list_del 'UMS Only (No debugging mode)'
<6>[ 4.368143] acm_function_config_changed
<6>[ 4.368152] mass_storage_function_config_changed
<6>[ 4.368160] adb_function_config_changed
<4>[ 4.368171] interface 0 = acm/c4d2d0c0
<4>[ 4.368180] interface 1 = acm/c4d2d0c0
<4>[ 4.368188] interface 2 = usb_mass_storage/dfa16800
<4>[ 4.368198] interface 3 = adb/c4d2d240
<4>[ 4.368673] [ap_usb_power_on]AP USB Power ON, askon: 0, mtp : 0
<4>[ 4.368684] !!!!!!!!!!! [ap_usb_power_on]AP samsung_kies_mtp_mode_flag0, m
tp:0
<3>[ 4.393758] init: init.svc.immvibed:stopped
<3>[ 4.442149] init: debug.sf.nobootanimation:0
<4>[ 4.475052] [BIF: ] FSR VERSION: FSR_1.2.1p1_b129_RTM
<4>[ 4.475074] [BIF: ] FSR_BML_Open(nVol:0, nFlag:0x0, nOpenCnt:7) / 1176
line
<4>[ 4.476774] [BIF: ] FSR_BML_Close(nVol: 0, nFlag: 0x0, nOpenCnt: 6)
<4>[ 4.560550] OTG core got reset (1)!!
<4>[ 4.710729] [USB_SWITCH] print_switch_state(1011): usbstatus = 0x1, curren
tusbstatus = 0x10
<3>[ 4.853901] init: ro.csc.country_code:ITALY
<3>[ 4.860794] init: ro.csc.sales_code:ITV
<4>[ 4.924533] acm_disconnected
<4>[ 5.179539] [USB:UMS] fsg_function_setup, return to PC fsg->nluns=2
<4>[ 5.180760] printk:do_inquiry fsg->cdrom 0 curlun->id 0
<4>[ 5.181138] printk:do_inquiry fsg->cdrom 0 curlun->id 0
<4>[ 5.186479] printk:do_inquiry fsg->cdrom 0 curlun->id 1
<4>[ 5.186869] printk:do_inquiry fsg->cdrom 0 curlun->id 1
<3>[ 5.426038] init: sys_prop: permission denied uid:2000 name:adb.connected
<4>[ 5.972389] [ wm8994.c (wm8994_startup,1556) ] Turn on codec
<4>[ 6.041874] [ wm8994.c (wm8994_set_playback_path,397) ] routing to SPK
<4>[ 6.041883]
<4>[ 6.041896] [ wm8994_p1.c (wm8994_set_playback_speaker,1707) ]
<4>[ 6.077282] [ wm8994.c (wm8994_shutdown,1586) ] Stream_type = 0, Stream_st
ate = [0x1], Codec State = [0x1]
<4>[ 6.077301] [ wm8994.c (wm8994_shutdown,1601) ] Turn off Codec!!
<4>[ 6.077313] [ wm8994_p1.c (audio_ctrl_mic_bias_gpio,313) ] MICBIAS Off
<4>[ 6.078199] [ wm8994.c (wm8994_startup,1556) ] Turn on codec
<4>[ 6.142324] [ wm8994.c (wm8994_set_playback_path,397) ] routing to SPK
<4>[ 6.142333]
<4>[ 6.142346] [ wm8994_p1.c (wm8994_set_playback_speaker,1707) ]
<4>[ 6.179672] [SIF:INF] Zone[ 3, 0]: nDgn( 5) nVbn( 71) S( 35)-E( 42)
nCPOffs( 43)
<4>[ 6.226365] [ wm8994.c (wm8994_shutdown,1586) ] Stream_type = 0, Stream_st
ate = [0x1], Codec State = [0x1]
<4>[ 6.226385] [ wm8994.c (wm8994_shutdown,1601) ] Turn off Codec!!
<4>[ 6.226397] [ wm8994_p1.c (audio_ctrl_mic_bias_gpio,313) ] MICBIAS Off
<4>[ 6.227282] [ wm8994.c (wm8994_startup,1556) ] Turn on codec
<4>[ 6.290877] [ wm8994.c (wm8994_set_playback_path,397) ] routing to SPK
<4>[ 6.290887]
<4>[ 6.290899] [ wm8994_p1.c (wm8994_set_playback_speaker,1707) ]
<4>[ 6.534725] [email protected]()
<4>[ 7.960106] [BIF: ] FSR VERSION: FSR_1.2.1p1_b129_RTM
<4>[ 7.960134] [BIF: ] FSR_BML_Open(nVol:0, nFlag:0x0, nOpenCnt:7) / 1176
line
<4>[ 9.169446] [SIF:INF] Zone[ 0, 0]: nDgn( 13) nVbn( 14) S( 0)-E( 1)
nCPOffs( 2)
<4>[ 9.565723] [BIF: ] FSR_BML_Close(nVol: 0, nFlag: 0x0, nOpenCnt: 6)
<3>[ 10.683021] init: audioflinger.bootsnd:0
<4>[ 11.458574] [email protected]()
<4>[ 11.716408] [email protected]()
<4>[ 11.876286] [email protected]_init1()
<4>[ 12.022840] [email protected]_init1()
<3>[ 12.024139] init: init.svc.samsungloop:running
<4>[ 12.362599] [email protected]
<6>[ 12.376356] modemctl xmm: PHONE ACTIVE: 1
<3>[ 12.658166] init: ril.lac:0000
<3>[ 12.660252] init: ril.cid:00000000
<4>[ 13.067815] [SIF:INF] Zone[ 2, 0]: nDgn( 1239) nVbn( 1037) S( 0)-E( 18)
nCPOffs( 19)
<4>[ 13.225751] acm_connected
<6>[ 13.415670] kernel_sec_get_debug_level_from_param: debuglevel.inf read suc
cessfully.
<5>[ 13.415692] (kernel_sec_get_debug_level_from_param) kernel debug level is
0x44494d44 !!
<3>[ 13.415975] init: ril.RildInit:1
<4>[ 13.796113] [ wm8994.c (wm8994_shutdown,1586) ] Stream_type = 0, Stream_st
ate = [0x1], Codec State = [0x1]
<4>[ 13.796133] [ wm8994.c (wm8994_shutdown,1601) ] Turn off Codec!!
<4>[ 13.796145] [ wm8994_p1.c (audio_ctrl_mic_bias_gpio,313) ] MICBIAS Off
Prasad007 said:
Nice comparison. Hope that some, if not all of these improvements are received by us with the official froyo update for the SGS. However, I didn't see the point in this comparison really. A phone and a tablet fit completely different applications, even if the manufacturer and the internal hardware is same...
Click to expand...
Click to collapse
The purpose is the compare the performance on one to one comparison to the SGS.
We would like to figure out why the Tab has 444MB RAM while the SGS is stuck with 304MB RAM.
There is also no lag with the Tab which is ineteresting.
The rest of my post is informative to the interested people.
Prasad007 said:
I don't disagree with what you're saying, but this comparison is only applicable in terms of specs, features and the wide range of applications that both products can handle. I think we are forgetting that a phone is still primarily a phone! So that is no reason to put a phone and a tablet pc in the same basket. You will never see smartphones being replaced by tablets in the decades to come... In fact it would more likely be quite the opposite, for that is miniaturization. I would like to see phones with very high computing power, and that are easily, conveniently and wirelessly connectable to large screens like monitors and TVs, thereby completely replacing larger computing systems AKA Tab (or even conventional PC's for that matter...). Nanotech anyone ? ;-)
Still, the OP will seemingly be useful towards SGS owners and that's cool!
Click to expand...
Click to collapse
Well, in this case it is a Tab that can make phone calls
I have both the SGS and the Tab and in the past few days i have been using the Tab as both my phone (with a BT headset) and as a Tablet.
I now use the SGS when i go out and i need something fits in the pocket more easily.
Honestly guys, maybe it's just me.... But I really have to be more convinced to spend a considerable amount of money on something that does lesser than my laptop, but performs equally as my phone, only less portable...
alovell83 said:
Nonetheless, some good points put in by you.
Click to expand...
Click to collapse
Likewise.
clubtech said:
<4>[ 3.392077] [SIF:INF] Number of Free Block ( 25)
<4>[ 3.392088] [SIF:INF] Active Log List : Num ( 8)
<4>[ 3.392100] [SIF:INF] ===> STL Zone[ 4, 0] Open Zone Post
<4>[ 3.393005] [SIF:INF] Partition [0, 24] open is success
<4>[ 3.400760] [SIF:INF] Zone[ 4, 0]: nDgn( 0) nVbn( 33) S( 0)-E( 53)
nCPOffs( 54)
<4>[ 3.401428] [SIF:INF] Zone[ 4, 0]: nDgn( 4) nVbn( 26) S( 28)-E( 28)
nCPOffs( 29)
<4>[ 3.403713] [SIF:INF] Zone[ 4, 0]: nDgn( 1) nVbn( 67) S( 7)-E( 17)
nCPOffs( 18)
<4>[ 3.413550] [BIF: ] FSR VERSION: FSR_1.2.1p1_b129_RTM
Click to expand...
Click to collapse
Thanks so much, but it looks like the kernel log buffer has already wrapped so we didn't get the start of the kernel boot process, you need to be about 4 seconds faster.
I'm looking for the "system memory reserved" messages to compare with this from the Galaxy S.
Have you used adb shell before? You can connect to the device quite early in the boot process and get the dmesg output then.
P.S. Tell me to take a hike if this is too much hassle. We can always wait for the open-source kernel to be released for the Tab to find this out.
Prasad007 said:
Honestly guys, maybe it's just me.... But I really have to be more convinced to spend a considerable amount of money on something that does lesser than my laptop, but performs equally as my phone, only less portable...
Likewise.
Click to expand...
Click to collapse
It's definitely not just you, but you mentioned the cause, people wanting something smaller than their laptop. Not everyone has a netbook and it's not like netbooks aren't the gold-standard for content creation either. Again, not everyone has, or even desires a smartphone. Some people don't even really want this to be "portable", they want it as an in-home e-reader with more functionality than a Kindle. There are plenty of people this device is for, there are plenty more (like you) who it isn't for.
There's one thing that is for sure, this device is all about size, as is the other iterations Samsung will put out (10" & 12"). 10M to sell in 2011, which I think is too optimistic at these prices, marketed at well over 1B people means that these devices are still largely niche devices.
I am very keen to hear what your thoughts are on the Camera.
1. What is the Camera software like?
2. Does it have similar if not the same functions as the SGS...
i.e. Shooting Mode
Single Shot/Beauty/Continuous/Self Shot/Smile Shot/Panorama/Vintage/Action Shot/Add Me/Cartoon
SCN Mode
None/Landscape/Sports/Portait/Night/Party/etc... etc..
3. What is the quality of shots like?
Can you provide any samples or links to a good sample
4. What is the Video recording like using the Camera?
5. Anything special or different?
I appreciate the Camera is a lower 3MP but I think it uses the same sensor that is fitted in the SGS.
If that is the case then it won't make that much of a difference in shooting.
Thanks in advance.
TheBeano said:
Thanks so much, but it looks like the kernel log buffer has already wrapped so we didn't get the start of the kernel boot process, you need to be about 4 seconds faster.
I'm looking for the "system memory reserved" messages to compare with this from the Galaxy S.
Have you used adb shell before? You can connect to the device quite early in the boot process and get the dmesg output then.
P.S. Tell me to take a hike if this is too much hassle. We can always wait for the open-source kernel to be released for the Tab to find this out.
Click to expand...
Click to collapse
Well the open sourch is out check the developers section i uplaoded it there..
Anyone noticed.. There is no JIT enabled there like in the build.prop in our Galaxy S Froyo roms :S
Is it the RFS filesystem?
Because i can not post in the Dev section i try it here.
On the new Utopia RC4 ROM the Wlan can not be activated, it just say's scanning is not possible an then it gets deactivated.
Sirius1977 said:
Because i can not post in the Dev section i try it here.
On the new Utopia RC4 ROM the Wlan can not be activated, it just say's scanning is not possible an then it gets deactivated.
Click to expand...
Click to collapse
Try reflashing because its supposed
to be working!!
Nope, didn't work. Tried to flash again via fastboot and at the second try i made a recovery version which also didn't make the wifi work.
Same message: Networkscan is not possible
dmesg output:
Code:
<4>[ 560.902218] register_mmc_card_pm: [WiFi] Callbacks registered successfully.
<3>[ 560.902608] [yoohoo] dhd_register_hwakeup : start
<3>[ 560.902848] [dhd_hostwakeup_isr] HostWakeup Get GPIO 94: 1
<3>[ 560.903240] [yoohoo] dhd_register_hwakeup : OK
<4>[ 560.903445] [yoohoo] dhd_enable_hwakeup : succeed irq 158
<3>[ 560.903810] [dhd_register_early_suspend] HostWakeup Get GPIO 94: 1
<4>[ 560.904012]
<4>[ 560.904017] Dongle Host Driver, version 4.217.91.0
<4>[ 561.104080] =========== WLAN going back to live ========
<6>[ 561.104328] mmc1: Slot status change detected (0 -> 1)
<3>[ 561.104886] (swift_sdcc_setup_power)vdd :12
<3>[ 561.107221] (swift_sdcc_setup_power)vdd :12
<3>[ 561.109586] (swift_sdcc_setup_power)vdd :12
<3>[ 561.112228] (swift_sdcc_setup_power)vdd :12
<3>[ 561.120059] (swift_sdcc_setup_power)vdd :12
<3>[ 561.121993] (swift_sdcc_setup_power)vdd :12
<7>[ 561.183765] mmc1: queuing CIS tuple 0x80 length 51
<7>[ 561.191050] mmc1: queuing CIS tuple 0x80 length 7
<7>[ 561.194554] mmc1: queuing CIS tuple 0x80 length 2
<7>[ 561.204207] mmc1: queuing CIS tuple 0x80 length 10
<7>[ 561.206143] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.207915] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.209852] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.211637] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.213400] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.215332] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.217095] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.219025] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.220790] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.222560] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.224492] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 561.227047] mmc1: queuing CIS tuple 0x02 length 1
<3>[ 561.228268] (swift_sdcc_setup_power)vdd :12
<3>[ 561.228515] (swift_sdcc_setup_power)vdd :12
<6>[ 561.231190] mmc1: new SDIO card at address 0001
<4>[ 561.236461] mem_prealloc: section [3] size[139264]
<4>[ 561.236671] mem_prealloc: This data is using!!!
<4>[ 561.237255] alloc static buf at cccc0000!
<4>[ 561.237451] mem_prealloc: section [4] size[0]
<4>[ 561.239636] DHD: dongle ram size is set to 393216(orig 393216)
<4>[ 561.240125] mem_prealloc: section [0] size[10312]
<4>[ 561.240371] mem_prealloc: This data is using!!!
<4>[ 561.241366] mem_prealloc: section [1] size[10300]
<4>[ 561.241623] mem_prealloc: This data is using!!!
<4>[ 561.241890] mem_prealloc: section [2] size[32768]
<4>[ 561.242338] mem_prealloc: This data is using!!!
<6>[ 561.765387] wlan0 (): not using net_device_ops yet
<4>[ 561.770128] wlan0: Broadcom Dongle Host Driver mac=00:26:e8:af:0b:bb
<4>[ 563.957310] wlan0: non-BDC packet received, flags 0x10
<3>[ 578.949398] init: untracked pid 2131 exited
<4>[ 579.974021] unregister_mmc_card_pm: [WIFI] Unregistering suspend/resume callbacks.
<4>[ 580.243393] =========== WLAN placed in RESET ========
<6>[ 580.243909] mmc1: Slot status change detected (1 -> 0)
<6>[ 580.258381] mmc1: card 0001 removed
<3>[ 580.260527] (swift_sdcc_setup_power)vdd :0
#
Hmm... also the MAC adress didn't appear the Advanced Wifi settings.
For now i'm back to RC3 and ... wifi works
It is my mistake!
Try this fix!
Hmm... simply cut & paste didn't work. How can i apply the fix?
Sirius1977 said:
Hmm... simply cut & paste didn't work. How can i apply the fix?
Click to expand...
Click to collapse
install with recovery
No chance to install in CWM
Always getting Error on applying (Status 6)
Sirius1977 said:
No chance to install in CWM
Always getting Error on applying (Status 6)
Click to expand...
Click to collapse
last fix was broken? download fix again.
Error (Status 6) again
I try to set the permissions for the .so manually
Ok... I got it
adb shell
cd /system/lib
chmod 06755 libhardware_legacy.so
exit
dont't forget to mount the system partition as r/w in root explorer
Thanks to all for the fast response.
Great ROM
Ok that was to fast.
Wifi is on and it can scan for AP's but it can't connect.
Sirius1977 said:
Ok that was to fast.
Wifi is on and it can scan for AP's but it can't connect.
Click to expand...
Click to collapse
Does your router work?
Sent from my GT540 using XDA App
Yes, meanwhile the problem was confirmed by others.
No wifi........MIROSLAV_MM where are you;-)
Edit-Forgot to add 'I love your work'
Sent from my GT540 using xda premium
sanmit said:
No wifi........MIROSLAV_MM where are you;-)
Edit-Forgot to add 'I love your work'
Sent from my GT540 using xda premium
Click to expand...
Click to collapse
RC4 has been withdrawn due to this wifi issue.
Sent from my GT540 using xda premium
i tried cm7_nand_photon_v2, but bootloop
dmesg log
Code:
<6>[ 0.000000] Initializing cgroup subsys cpu
<5>[ 0.000000] Linux version 2.6.32.21-gf9fbd2a ([email protected]) (gcc v
ersion 4.4.1 (Sourcery G++ Lite 2010q1-188) ) #27 PREEMPT Wed Jan 4 00:36:49 MSK
2012
<4>[ 0.000000] CPU: ARMv6-compatible processor [4117b365] revision 5 (ARMv6TE
J), cr=00c5387f
<4>[ 0.000000] CPU: VIPT aliasing data cache, VIPT aliasing instruction cache
<4>[ 0.000000] Machine: photon
<6>[ 0.000000] fixup: nr_banks = 2
<6>[ 0.000000] fixup: bank0 start=00200000, node=00000000, size=0ca00000
<6>[ 0.000000] fixup: bank1 start=20000000, node=00000000, size=05600000
<4>[ 0.000000] Ignoring unrecognised tag 0x00000000
<4>[ 0.000000] Ignoring unrecognised tag 0x00000000
<4>[ 0.000000] Memory policy: ECC disabled, Data cache writeback
<7>[ 0.000000] On node 0 totalpages: 73728
<7>[ 0.000000] free_area_init_node: node 0, pgdat c05b29b0, node_mem_map c08b
9000
<7>[ 0.000000] Normal zone: 1192 pages used for memmap
<7>[ 0.000000] Normal zone: 0 pages reserved
<7>[ 0.000000] Normal zone: 72536 pages, LIFO batch:15
<4>[ 0.000000] liberty_init_map_io()
<6>[ 0.000000] L210 cache controller enabled
<4>[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total
pages: 72536
<5>[ 0.000000] Kernel command line: rw?
<6>[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
<6>[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes
)
<6>[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
<6>[ 0.000000] Memory: 202MB 86MB = 288MB total
<5>[ 0.000000] Memory: 284212KB available (4280K code, 1331K data, 1148K init
, 0K highmem)
<6>[ 0.000000] Hierarchical RCU implementation.
<6>[ 0.000000] NR_IRQS:277
<4>[ 0.000000] photon_init_irq()
<6>[ 0.000000] ram_console: no valid data in buffer (sig = 0x48454150)
<6>[ 0.000000] console [ram0] enabled
<6>[ 0.000000] Calibrating delay loop... 598.01 BogoMIPS (lpj=2990080)
<4>[ 0.230191] Mount-cache hash table entries: 512
<6>[ 0.230828] Initializing cgroup subsys debug
<6>[ 0.230858] Initializing cgroup subsys cpuacct
<6>[ 0.230876] Initializing cgroup subsys freezer
<6>[ 0.230918] CPU: Testing write buffer coherency: ok
<6>[ 0.233663] NET: Registered protocol family 16
<4>[ 0.234270] photon_init() revision = 0x0
<6>[ 0.385178] YoYo--BD_ADDRESS=00:00:00:00:00:00
<6>[ 0.385580] acpu_clock_init()
<6>[ 0.385646] ACPU running at 600000 KHz
<6>[ 0.385726] ACPU speed 19200 KHz
<6>[ 0.385741] ACPU speed 120000 KHz
<6>[ 0.385755] ACPU speed 122880 KHz
<6>[ 0.385768] ACPU speed 200000 KHz
<6>[ 0.385781] ACPU speed 245760 KHz
<6>[ 0.385796] ACPU speed 320000 KHz
<6>[ 0.385810] ACPU speed 400000 KHz
<6>[ 0.385823] ACPU speed 480000 KHz
<6>[ 0.385836] ACPU speed 600000 KHz
<6>[ 0.385851] ACPU speed 768000 KHz
<6>[ 0.385865] ACPU speed 787200 KHz
<6>[ 0.385878] ACPU speed 806400 KHz
<6>[ 0.385891] ACPU speed 825600 KHz
<6>[ 0.385906] ACPU speed 844800 KHz
<6>[ 0.385920] ACPU speed 864000 KHz
<6>[ 0.385935] ACPU running at 0 KHz
<6>[ 0.385980] msm_proc_comm_wince_init: WinCE PCOM initialized.
<6>[ 0.386011] PLL0 @ f8005300: MODE=00000007 L=00000032 M=00000000 N=0000000
1 freq=960000000 Hz (960 MHz)
<6>[ 0.386046] PLL1 @ f800531c: MODE=00000007 L=0000000c M=00000004 N=0000000
5 freq=245760000 Hz (245 MHz)
<6>[ 0.386080] PLL2 @ f8005338: MODE=00000007 L=0000003e M=00000001 N=0000000
2 freq=1200000000 Hz (1200 MHz)
<6>[ 0.386103] PCB XC: 00000000
<6>[ 0.386116] AMSS version: 32.26.05.04U
<6>[ 0.386151] Acquire 'boot-time' perf_lock
<4>[ 0.390408] after msm_add_devices()
<6>[ 0.391256] photon_init_mmc
<6>[ 0.392315] msm_hsusb_set_vbus_state: 1
<4>[ 0.399266] bio: create slab <bio-0> at 0
<6>[ 0.400081] msm_i2c_probe
<6>[ 0.400286] msm_i2c_probe: clk_ctl 315, 400000 Hz
<6>[ 0.401790] Bluetooth: Core ver 2.15
<6>[ 0.401965] NET: Registered protocol family 31
<6>[ 0.401981] Bluetooth: HCI device and connection manager initialized
<6>[ 0.402006] Bluetooth: HCI socket layer initialized
<6>[ 0.402198] Switching to clocksource dg_timer
<6>[ 0.403455] NET: Registered protocol family 2
<6>[ 0.403686] IP route cache hash table entries: 4096 (order: 2, 16384 bytes
)
<6>[ 0.404316] TCP established hash table entries: 16384 (order: 5, 131072 by
tes)
<6>[ 0.404896] TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
<6>[ 0.405330] TCP: Hash tables configured (established 16384 bind 16384)
<6>[ 0.405351] TCP reno registered
<6>[ 0.405631] NET: Registered protocol family 1
<6>[ 0.405980] Unpacking initramfs...
<6>[ 0.491268] Freeing initrd memory: 720K
<6>[ 0.491970] smd_init()
<6>[ 0.491983] smd_core_init()
<4>[ 0.492001] smem_item: id=85 offset=19072 size=32=
<6>[ 0.492021] phy addr of smd_info.state=0xFF04A80
<6>[ 0.492116] smd_core_init() done
<4>[ 0.492138] smem_item: id=336 offset=8712 size=6936=
<3>[ 0.492175] msm_init_last_radio_log: last radio log is 6936 bytes long
<4>[ 0.492740] smem_item: id=13 offset=102296 size=2048=
<4>[ 0.492770] smem_item: id=14 offset=219320 size=40=
<4>[ 0.492790] smem_item: id=338 offset=219360 size=16384=
<6>[ 0.492813] smd_alloc_channel() cid=00 size=08192 'SMD_DS'
<4>[ 0.492971] smem_item: id=15 offset=137320 size=40=
<4>[ 0.492993] smem_item: id=339 offset=137360 size=65536=
<6>[ 0.493013] smd_alloc_channel() cid=01 size=32768 'SMD_DIAG'
<4>[ 0.493125] smem_item: id=16 offset=120896 size=40=
<4>[ 0.493145] smem_item: id=340 offset=120936 size=16384=
<6>[ 0.493166] smd_alloc_channel() cid=02 size=08192 'SMD_RPCCALL'
<4>[ 0.493283] smem_item: id=19 offset=104472 size=40=
<4>[ 0.493303] smem_item: id=343 offset=104512 size=16384=
<6>[ 0.493323] smd_alloc_channel() cid=05 size=08192 'SMD_CONTROL'
<4>[ 0.493435] smem_item: id=21 offset=235744 size=40=
<4>[ 0.493455] smem_item: id=345 offset=235784 size=65536=
<6>[ 0.493476] smd_alloc_channel() cid=07 size=32768 'SMD_DATA1'
<4>[ 0.493586] smem_item: id=22 offset=301320 size=40=
<4>[ 0.493606] smem_item: id=346 offset=301360 size=65536=
<6>[ 0.493626] smd_alloc_channel() cid=08 size=32768 'SMD_DATA2'
<4>[ 0.493745] smem_item: id=23 offset=366896 size=40=
<4>[ 0.493766] smem_item: id=347 offset=366936 size=65536=
<6>[ 0.493786] smd_alloc_channel() cid=09 size=32768 'SMD_DATA3'
<4>[ 0.493903] smem_item: id=29 offset=432472 size=40=
<4>[ 0.493923] smem_item: id=353 offset=432512 size=16384=
<6>[ 0.493943] smd_alloc_channel() cid=15 size=08192 'SMD_DATA9'
<4>[ 0.494058] smem_item: id=41 offset=448896 size=40=
<4>[ 0.494078] smem_item: id=365 offset=448936 size=16384=
<6>[ 0.494100] smd_alloc_channel() cid=27 size=08192 'SMD_GPSNMEA'
<4>[ 0.494225] smem_item: id=52 offset=202896 size=40=
<4>[ 0.494245] smem_item: id=376 offset=202936 size=16384=
<6>[ 0.494265] smd_alloc_channel() cid=38 size=08192 'SMD_DAL00'
<4>[ 0.494871] smem_item: id=79 offset=19200 size=40000=
<4>[ 0.494895] smem_item: id=78 offset=59200 size=8=
<4>[ 0.494915] smem_item: id=81 offset=59208 size=3000=
<4>[ 0.494935] smem_item: id=80 offset=62208 size=8=
<4>[ 0.494955] smem_item: id=407 offset=62224 size=40000=
<4>[ 0.494975] smem_item: id=405 offset=102224 size=8=
<4>[ 0.494995] smem_item: id=7 offset=8612 size=32=
<4>[ 0.495015] smem_item: id=7 offset=8612 size=32=
<4>[ 0.495845] smd_open success: [SMD_RPCCALL]
<6>[ 0.495866] SMD: ch 2 0 -> 1
<6>[ 0.495970] SMD: ch 2 1 -> 2
<4>[ 0.612405] RPC: NEW_SERVER id=0:00000001 prog=30000025:00000000
<4>[ 0.612718] RPC: NEW_SERVER id=0:00000001 prog=30000044:bbf38d5a
<4>[ 0.613001] RPC: NEW_SERVER id=0:00000001 prog=30000043:00000000
<4>[ 0.613283] RPC: NEW_SERVER id=0:00000001 prog=30000005:ac8ba7b7
<4>[ 0.613555] RPC: NEW_SERVER id=0:00000001 prog=30000061:00010001
<4>[ 0.613831] RPC: NEW_SERVER id=0:00000001 prog=30000003:00000000
<4>[ 0.614103] RPC: NEW_SERVER id=0:00000001 prog=30000060:00010002
<4>[ 0.614401] RPC: NEW_SERVER id=0:00000001 prog=3000005f:00010002
<4>[ 0.614675] RPC: NEW_SERVER id=0:00000001 prog=30000021:00000000
<4>[ 0.614948] RPC: NEW_SERVER id=0:00000001 prog=30000002:00020002
<4>[ 0.615258] RPC: NEW_SERVER id=0:00000001 prog=3000001f:00000000
<4>[ 0.615556] RPC: NEW_SERVER id=0:00000001 prog=30000000:e9fb8210
<4>[ 0.615848] RPC: NEW_SERVER id=0:00000001 prog=3000fffd:0000ffff
<4>[ 0.616151] RPC: NEW_SERVER id=0:00000001 prog=3000001d:00020001
<4>[ 0.616438] RPC: NEW_SERVER id=0:00000001 prog=3000005b:a60286b0
<4>[ 0.616726] RPC: NEW_SERVER id=0:00000001 prog=3000003c:20cebc12
<4>[ 0.617041] RPC: NEW_SERVER id=0:00000001 prog=3000003b:00000000
<4>[ 0.617336] RPC: NEW_SERVER id=0:00000001 prog=3000005a:00000000
<4>[ 0.617628] RPC: NEW_SERVER id=0:00000001 prog=30000059:00000000
<4>[ 0.617923] RPC: NEW_SERVER id=0:00000001 prog=3000001b:408f49d3
<4>[ 0.618226] RPC: NEW_SERVER id=0:00000001 prog=30000019:356f9094
<4>[ 0.618551] RPC: NEW_SERVER id=0:00000001 prog=30000055:00000000
<4>[ 0.618860] RPC: NEW_SERVER id=0:00000001 prog=30000016:008a27be
<4>[ 0.619176] RPC: NEW_SERVER id=0:00000001 prog=30000091:00010001
<4>[ 0.619500] RPC: NEW_SERVER id=0:00000001 prog=30000053:cfb85d48
<4>[ 0.619813] RPC: NEW_SERVER id=0:00000001 prog=30000014:00020001
<4>[ 0.620140] RPC: NEW_SERVER id=0:00000001 prog=30000051:00000000
<4>[ 0.620455] RPC: NEW_SERVER id=0:00000001 prog=30000013:00030001
<4>[ 0.620771] RPC: NEW_SERVER id=0:00000001 prog=30000012:00000000
<4>[ 0.621098] RPC: NEW_SERVER id=0:00000001 prog=3000fe00:a82d4624
<4>[ 0.621416] RPC: NEW_SERVER id=0:00000001 prog=30000010:00000000
<4>[ 0.621748] RPC: NEW_SERVER id=0:00000001 prog=3000006c:00000000
<4>[ 0.622068] RPC: NEW_SERVER id=0:00000001 prog=3000000f:00010001
<4>[ 0.622480] RPC: NEW_SERVER id=0:00000001 prog=3000006b:0aabc7a4
<4>[ 0.622816] RPC: NEW_SERVER id=0:00000001 prog=3000000e:052ff749
<4>[ 0.623146] RPC: NEW_SERVER id=0:00000001 prog=3000006a:00000000
<4>[ 0.623490] RPC: NEW_SERVER id=0:00000001 prog=30000068:00000000
<4>[ 0.623823] RPC: NEW_SERVER id=0:00000001 prog=30000067:00000000
<4>[ 0.624160] RPC: NEW_SERVER id=0:00000001 prog=30000048:00010004
<4>[ 0.624495] RPC: NEW_SERVER id=0:00000001 prog=3000000a:00000000
<4>[ 0.624828] RPC: NEW_SERVER id=0:00000001 prog=30000066:00020001
<4>[ 0.625196] RPC: NEW_SERVER id=0:00000001 prog=30000064:00010002
<4>[ 0.625550] RPC: NEW_SERVER id=0:00000001 prog=30000025:00000000
<3>[ 0.625570] rpcrouter: Duplicate svr
<4>[ 0.625596] RPC: NEW_SERVER id=0:00000001 prog=30000044:bbf38d5a
<3>[ 0.625613] rpcrouter: Duplicate svr
<4>[ 0.625638] RPC: NEW_SERVER id=0:00000001 prog=30000043:00000000
<3>[ 0.625656] rpcrouter: Duplicate svr
<4>[ 0.625680] RPC: NEW_SERVER id=0:00000001 prog=30000005:ac8ba7b7
<3>[ 0.625698] rpcrouter: Duplicate svr
<4>[ 0.625723] RPC: NEW_SERVER id=0:00000001 prog=30000061:00010001
<3>[ 0.625740] rpcrouter: Duplicate svr
<4>[ 0.625765] RPC: NEW_SERVER id=0:00000001 prog=30000003:00000000
<3>[ 0.625781] rpcrouter: Duplicate svr
<4>[ 0.625806] RPC: NEW_SERVER id=0:00000001 prog=30000060:00010002
<3>[ 0.625825] rpcrouter: Duplicate svr
<4>[ 0.625848] RPC: NEW_SERVER id=0:00000001 prog=3000005f:00010002
<3>[ 0.625866] rpcrouter: Duplicate svr
<4>[ 0.625891] RPC: NEW_SERVER id=0:00000001 prog=30000021:00000000
<3>[ 0.625910] rpcrouter: Duplicate svr
<4>[ 0.625935] RPC: NEW_SERVER id=0:00000001 prog=30000002:00020002
<3>[ 0.625951] rpcrouter: Duplicate svr
<4>[ 0.625976] RPC: NEW_SERVER id=0:00000001 prog=3000001f:00000000
<3>[ 0.625995] rpcrouter: Duplicate svr
<4>[ 0.626018] RPC: NEW_SERVER id=0:00000001 prog=30000000:e9fb8210
<3>[ 0.626036] rpcrouter: Duplicate svr
<4>[ 0.626061] RPC: NEW_SERVER id=0:00000001 prog=3000fffd:0000ffff
<3>[ 0.626080] rpcrouter: Duplicate svr
<4>[ 0.626103] RPC: NEW_SERVER id=0:00000001 prog=3000001d:00020001
<3>[ 0.626121] rpcrouter: Duplicate svr
<4>[ 0.626146] RPC: NEW_SERVER id=0:00000001 prog=3000005b:a60286b0
<3>[ 0.626165] rpcrouter: Duplicate svr
<4>[ 0.626190] RPC: NEW_SERVER id=0:00000001 prog=3000003c:20cebc12
<3>[ 0.626208] rpcrouter: Duplicate svr
<4>[ 0.626233] RPC: NEW_SERVER id=0:00000001 prog=3000003b:00000000
<3>[ 0.626251] rpcrouter: Duplicate svr
<4>[ 0.626275] RPC: NEW_SERVER id=0:00000001 prog=3000005a:00000000
<3>[ 0.626293] rpcrouter: Duplicate svr
<4>[ 0.626318] RPC: NEW_SERVER id=0:00000001 prog=30000059:00000000
<3>[ 0.626336] rpcrouter: Duplicate svr
<4>[ 0.626361] RPC: NEW_SERVER id=0:00000001 prog=3000001b:408f49d3
<3>[ 0.626378] rpcrouter: Duplicate svr
<4>[ 0.626403] RPC: NEW_SERVER id=0:00000001 prog=30000019:356f9094
<3>[ 0.626421] rpcrouter: Duplicate svr
<4>[ 0.626446] RPC: NEW_SERVER id=0:00000001 prog=30000055:00000000
<3>[ 0.626465] rpcrouter: Duplicate svr
<4>[ 0.626490] RPC: NEW_SERVER id=0:00000001 prog=30000016:008a27be
<3>[ 0.626508] rpcrouter: Duplicate svr
<4>[ 0.626531] RPC: NEW_SERVER id=0:00000001 prog=30000091:00010001
<3>[ 0.626550] rpcrouter: Duplicate svr
<4>[ 0.626575] RPC: NEW_SERVER id=0:00000001 prog=30000053:cfb85d48
<3>[ 0.626593] rpcrouter: Duplicate svr
<4>[ 0.626618] RPC: NEW_SERVER id=0:00000001 prog=30000014:00020001
<3>[ 0.626636] rpcrouter: Duplicate svr
<4>[ 0.626661] RPC: NEW_SERVER id=0:00000001 prog=30000051:00000000
<3>[ 0.626680] rpcrouter: Duplicate svr
<4>[ 0.626705] RPC: NEW_SERVER id=0:00000001 prog=30000013:00030001
<3>[ 0.626723] rpcrouter: Duplicate svr
<4>[ 0.626748] RPC: NEW_SERVER id=0:00000001 prog=30000012:00000000
<3>[ 0.626766] rpcrouter: Duplicate svr
<4>[ 0.626791] RPC: NEW_SERVER id=0:00000001 prog=3000fe00:a82d4624
<3>[ 0.626808] rpcrouter: Duplicate svr
<4>[ 0.626835] RPC: NEW_SERVER id=0:00000001 prog=30000010:00000000
<3>[ 0.626853] rpcrouter: Duplicate svr
<4>[ 0.626876] RPC: NEW_SERVER id=0:00000001 prog=3000006c:00000000
<3>[ 0.626895] rpcrouter: Duplicate svr
<4>[ 0.626921] RPC: NEW_SERVER id=0:00000001 prog=3000000f:00010001
<3>[ 0.626940] rpcrouter: Duplicate svr
<4>[ 0.626963] RPC: NEW_SERVER id=0:00000001 prog=3000006b:0aabc7a4
<3>[ 0.626981] rpcrouter: Duplicate svr
<4>[ 0.627008] RPC: NEW_SERVER id=0:00000001 prog=3000000e:052ff749
<3>[ 0.627026] rpcrouter: Duplicate svr
<4>[ 0.627050] RPC: NEW_SERVER id=0:00000001 prog=3000006a:00000000
<3>[ 0.627068] rpcrouter: Duplicate svr
<4>[ 0.627093] RPC: NEW_SERVER id=0:00000001 prog=30000068:00000000
<3>[ 0.627111] rpcrouter: Duplicate svr
<4>[ 0.627136] RPC: NEW_SERVER id=0:00000001 prog=30000067:00000000
<3>[ 0.627155] rpcrouter: Duplicate svr
<4>[ 0.627180] RPC: NEW_SERVER id=0:00000001 prog=30000048:00010004
<3>[ 0.627198] rpcrouter: Duplicate svr
<4>[ 0.627221] RPC: NEW_SERVER id=0:00000001 prog=3000000a:00000000
<3>[ 0.627240] rpcrouter: Duplicate svr
<4>[ 0.627266] RPC: NEW_SERVER id=0:00000001 prog=30000066:00020001
<3>[ 0.627285] rpcrouter: Duplicate svr
<4>[ 0.627310] RPC: NEW_SERVER id=0:00000001 prog=30000064:00010002
<3>[ 0.627328] rpcrouter: Duplicate svr
<4>[ 0.727580] Found SND_DEVICE_IDLE id 17
<6>[ 0.728413] Acquire 'boot-time' no_halt_lock 60s
<6>[ 0.728606] perflock_notifier_call: cpufreq lock speed 600000
<6>[ 0.728626] active perf lock 'boot-time'
<4>[ 0.728863] htc_acoustic_wince_init called
<4>[ 0.728943] htc_acoustic_wince_probe called
<4>[ 0.728958] Initialize HTC acoustic driver for wince based devices
<4>[ 0.728980] htc_acoustic_wince_probe, retrieving the smem address to copy
those params
<4>[ 0.729006] smem_item: id=135 offset=465576 size=7712=
<4>[ 0.729026] htc_acoustic_wince_probe, acoustic table smem address=0xf8171a
a8
<4>[ 0.729056] htc_acoustic_wince_probe, final addresses: volume=0xf8171aa8 w
b_volume=0xf8171c42 CE=0xf817325c ADIE=0xf817265c codec=0xf8171ddc mic=0xf02e345
0
<6>[ 0.748868] mdp_probe: initialized
<4>[ 0.749061] photon_wifi_init: start
<6>[ 0.751276] atmega-microp 0-0066: microp version [05][1B]
<3>[ 0.752128] microp_function_check: No function 2 !!
<3>[ 0.753416] microp_function_check: No function 18 !!
<6>[ 0.753633] [HS_MGR] (htc_headset_mgr_probe) ++++++++++++++++++++
<6>[ 0.754341] input: h2w headset as /devices/virtual/input/input0
<6>[ 0.754703] [HS_MGR] (hs_notify_driver_ready) HS_MGR ready
<6>[ 0.754871] [HS_MGR] (htc_headset_mgr_probe) --------------------
<6>[ 0.755171] [HS_MICROP] (htc_headset_microp_probe) ++++++++++++++++++++
<6>[ 0.758300] [HS_MGR] (headset_notifier_register) Register REMOTE_ADC notif
ier
<6>[ 0.758326] [HS_MGR] (headset_notifier_register) Register MIC_STATUS notif
ier
<6>[ 0.758350] [HS_MGR] (headset_notifier_register) Register KEY_INT_ENABLE n
otifier
<6>[ 0.758371] [HS_MGR] (hs_notify_driver_ready) HS_MICROP ready
<6>[ 0.758576] [HS_GPIO] (htc_headset_gpio_probe) ++++++++++++++++++++
<6>[ 0.758758] [HS_MGR] (headset_notifier_register) Register HPIN_GPIO notifi
er
<6>[ 0.758783] [HS_MGR] (hs_notify_driver_ready) HS_GPIO ready
<6>[ 0.758801] [HS_GPIO] (htc_headset_gpio_probe) --------------------
<6>[ 0.758828] [HS_MICROP] (htc_headset_microp_probe) --------------------
<6>[ 0.772721] ashmem: initialized
<6>[ 0.774616] fuse init (API version 7.13)
<7>[ 0.774948] yaffs built Dec 30 2011 23:14:41 Installing.
<6>[ 0.780106] alg: No test for stdrng (krng)
<6>[ 0.780211] io scheduler noop registered
<6>[ 0.780228] io scheduler anticipatory registered
<6>[ 0.780246] io scheduler deadline registered (default)
<6>[ 0.780663] mddi: init() base=0xe5858000 irq=16
<7>[ 0.780870] mddi runs at 81920000
<6>[ 0.782050] mddi cmd send rtd: int 3a000, stat 8063, rtd val f
<6>[ 0.784215] mddi: registering panel mddi_c_0101_0000
<6>[ 0.784235] mddi: publish:
<6>[ 0.785016] CABC enabled
<6>[ 0.786051] vsync on gpio 97 now 0
<6>[ 0.786291] setup_fb_info msmfb->xres 320, msmfb->yres 480
<6>[ 0.786503] msmfb_probe() installing 320 x 480 panel
<4>[ 0.786520] before register_framebuffer ()
<4>[ 0.786833] register_framebuffer ()
<4>[ 0.786848] load_565rle_image()
<6>[ 0.787323] Registered led device: lcd-backlight
<6>[ 0.789871] msm_serial: detected port #2
<6>[ 0.789981] msm_serial.2: ttyMSM2 at MMIO 0xa9c00000 (irq = 11) is a MSM
<6>[ 0.790333] msm_serial: driver initialized
<6>[ 0.790665] msm_serial_hs module loaded
more dmesg log
Code:
<6>[ 0.790831] msm_serial_hs module loaded
<6>[ 0.791026] BCM chip
<6>[ 0.791145] msm_serial_hs_bcm.0: ttyHS0 at MMIO 0xa0200000 (irq = 45) is a
MSM HS UART
<6>[ 0.791505] msm_serial_hs module loaded
<6>[ 0.795528] loop: module loaded
<6>[ 0.795686] pmem: 1 init
<6>[ 0.796600] pmem_adsp: 1 init
<6>[ 0.797358] pmem_camera: 0 init
<6>[ 0.798068] Android kernel panic handler initialized (bind=crashdata)
<6>[ 0.798216] spi_bma150_probe: G-sensor connect with microP: start initial,
kvalue = 0x0
<6>[ 0.798576] input: bma150 as /devices/virtual/input/input1
<4>[ 0.798611] bma150: Input device successfuly registered
<6>[ 0.814915] __spi_bma150_set_mode: BMA get into SLEEP mode!
<6>[ 0.815596] msm_nand: allocated dma buffer at ffa47000, dma_addr 24814000
<6>[ 0.815703] status: c03120
<6>[ 0.815720] nandid: 5500bcec maker ec device bc
<6>[ 0.815738] Found a supported NAND device
<6>[ 0.815753] NAND Id : 0xBCEC
<6>[ 0.815766] Buswidth : 16 Bits
<6>[ 0.815780] Density : 512 MByte
<6>[ 0.815795] Pagesize : 2048 Bytes
<6>[ 0.815808] Erasesize: 131072 Bytes
<6>[ 0.815821] Oobsize : 64 Bytes
<6>[ 0.815865] msm_nand: read CFG0 = aa5400c0, CFG1 = a7476
<6>[ 0.815883] CFG0 Old: 0xaa5400c0
<6>[ 0.815896] CFG1 Old: 0x000a7476
<6>[ 0.815911] CFG0 Init : 0xea5400c0
<6>[ 0.815926] CFG1 Init : 0x000a7476
<6>[ 0.815945] CFG0: cw/page=3 ud_sz=512 ecc_sz=10 spare_sz=4 num_addr_cycles
=5
<6>[ 0.815991] DEV_CMD1: f00f3000
<6>[ 0.816026] <6>NAND_EBI2_ECC_BUF_CFG: 1ff
<4>[ 0.816045] #MTD# parts in atag = 7
<5>[ 0.816070] Creating 7 MTD partitions on "msm_nand":
<5>[ 0.816096] 0x000002820000-0x000002840000 : "lkbootloader"
<5>[ 0.817178] 0x000002840000-0x000003240000 : "boot"
<4>[ 0.820128] ###BAD BLOCK 363 02D60000###
<5>[ 0.823645] 0x000003240000-0x000003c40000 : "recovery"
<5>[ 0.830331] 0x000003c40000-0x000003ce0000 : "misc"
<5>[ 0.831440] 0x000003ce0000-0x00000dce0000 : "system"
<4>[ 0.854836] ###BAD BLOCK 803 06460000###
<4>[ 0.867655] ###BAD BLOCK 977 07A20000###
<4>[ 0.871276] ###BAD BLOCK 1026 08040000###
<4>[ 0.878588] ###BAD BLOCK 1125 08CA0000###
<4>[ 0.881328] ###BAD BLOCK 1162 09140000###
<4>[ 0.891501] ###BAD BLOCK 1300 0A280000###
<5>[ 0.926496] 0x00000dce0000-0x00001eee0000 : "userdata"
<4>[ 0.947281] ###BAD BLOCK 2048 10000000###
<4>[ 0.947373] ###BAD BLOCK 2049 10020000###
<4>[ 0.967620] ###BAD BLOCK 2324 12280000###
<4>[ 0.972271] ###BAD BLOCK 2387 12A60000###
<4>[ 1.009271] ###BAD BLOCK 2863 165E0000###
<4>[ 1.069118] ###BAD BLOCK 3672 1CB00000###
<5>[ 1.090975] 0x00001f000000-0x000020000000 : "cache"
<4>[ 1.097075] ###BAD BLOCK 4049 1FA20000###
<6>[ 1.101363] PPP generic driver version 2.4.2
<6>[ 1.101598] PPP Deflate Compression module registered
<6>[ 1.101618] PPP BSD Compression module registered
<6>[ 1.106225] PPP MPPE Compression module registered
<6>[ 1.106255] NET: Registered protocol family 24
<6>[ 1.106936] tun: Universal TUN/TAP device driver, 1.6
<6>[ 1.106958] tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
<6>[ 1.107471] msm72k_udc: msm72k_probe
<6>[ 1.107498] usb: accessory detect 0
<6>[ 1.107511] usb: id_pin_gpio 19
<6>[ 1.107525] usb: dock detect 0
<6>[ 1.107538] usb: dock pin gpio 0
<6>[ 1.107538] usb: dock pin gpio 0
<6>[ 1.107630] msm72k_udc: msm72k_probe() io=e5864000, irq=47, dma=ffa48000(2
485b000)
<6>[ 1.108420] android init
<6>[ 1.108503] android_probe pdata: c05876f0
<6>[ 1.108641] android_bind
<7>[ 1.108658] android_bind_config
<6>[ 1.108678] android_usb gadget: android_usb ready
<6>[ 1.108705] msm72k_udc: msm72k_udc: registered gadget driver 'android_usb'
<6>[ 1.108840] f_adb init
<6>[ 1.108855] android_register_function adb
<6>[ 1.108870] f_mass_storage init
<6>[ 1.108883] android_register_function usb_mass_storage
<6>[ 1.108900] f_rndis init
<6>[ 1.108913] android_register_function ether
<6>[ 1.108928] serial init
<6>[ 1.108941] android_register_function serial
<6>[ 1.108956] f_projector init
<6>[ 1.109388] android_register_function projector
<6>[ 1.109406] diag init
<6>[ 1.109488] diag:msm_diag_probe(), pdev->id=0x0
<6>[ 1.109896] diag:msm_diag_probe(), pdev->id=0xffffffff
<6>[ 1.109920] android_register_function diag
<4>[ 1.109971] android_usb gadget: using random self ethernet address
<4>[ 1.110006] android_usb gadget: using random host ethernet address
<6>[ 1.110613] usb0: MAC 0e:dd:bd:bd:84:bf
<6>[ 1.110631] usb0: HOST MAC 2a:cb:95:17:4e:f0
<6>[ 1.110808] mass_storage_bind_config
<6>[ 1.110995] fsg_probe pdata: c0587ab0
<6>[ 1.111460] hsusb: IDLE -> ONLINE
<6>[ 1.111480] usb: lpm exit
<6>[ 1.111625] hsusb: reset controller
<6>[ 1.111680] android_usb gadget: Number of LUNs=1
<6>[ 1.111706] adb_bind_config
<6>[ 1.112336] diag_bind_config
<6>[ 1.113428] serial_bind_config
<6>[ 1.114288] projector_bind_config
<6>[ 1.114650] input: projector_input as /devices/virtual/input/input2
<6>[ 1.114686] projector_touch_init OK
<6>[ 1.115008] input: projector-Keypad as /devices/virtual/input/input3
<6>[ 1.115036] projector_keypad_init OK
<6>[ 1.115625] usb: product_id=0xff9
<6>[ 1.127936] synaptics_ts_probe: panel_version: 103
<6>[ 1.128251] synaptics_ts_probe: Manufacturer ID 1
<6>[ 1.129440] max_x: 734, max_y: c7d
<6>[ 1.129581] synaptics_ts_probe: max_x 1844, max_y 3197
<6>[ 1.129603] synaptics_ts_probe: inactive_x -5 -5, inactive_y -6 -479
<6>[ 1.129630] synaptics_ts_probe: snap_x 0-0 0-0, snap_y 0-0 0-0
<6>[ 1.129651] input_set_abs_params: mix_x 5, max_x 1839, min_y 6, max_y 2718
<6>[ 1.130030] input: synaptics-rmi-touchscreen as /devices/virtual/input/inp
ut4
<6>[ 1.130580] synaptics_ts_probe: Start touchscreen synaptics-rmi-touchscree
n in interrupt mode
<6>[ 1.130780] capella_cm3602_probe: probe
<6>[ 1.131106] input: proximity as /devices/virtual/input/input5
<6>[ 1.131440] capella_cm3602_setup
<6>[ 1.131878] GPIO Matrix Keypad Driver: Start keypad matrix for liberty-key
pad in interrupt mode
<6>[ 1.132111] GPIO Input Driver: Start gpio inputs for liberty-keypad in int
errupt mode
<6>[ 1.132565] input: liberty-keypad as /devices/virtual/input/input6
<6>[ 1.133626] input: lightsensor-level as /devices/virtual/input/input7
<6>[ 1.134006] set_ls_kvalue: ALS calibrated als_kadc=0x0
<6>[ 1.134025] set_ls_kvalue: no ALS calibrated
<6>[ 1.134043] set_ls_kvalue: als_kadc=0x1, als_gadc=0x1
<4>[ 1.134065] ls_table: data[0] , data[0] = 0, 0
<4>[ 1.134083] ls_table: data[1] , data[1] = 0, 21
<4>[ 1.134101] ls_table: data[2] , data[2] = 0, 4d
<4>[ 1.134120] ls_table: data[3] , data[3] = 0, dc
<4>[ 1.134138] ls_table: data[4] , data[4] = 1, 34
<4>[ 1.134156] ls_table: data[5] , data[5] = 1, 8d
<4>[ 1.134175] ls_table: data[6] , data[6] = 1, e5
<4>[ 1.134193] ls_table: data[7] , data[7] = 2, ba
<4>[ 1.134213] ls_table: data[8] , data[8] = 3, 5c
<4>[ 1.134231] ls_table: data[9] , data[9] = 3, ff
<7>[ 1.136385] __capella_cm3602_power: Turn the capella_cm3602 power on
<6>[ 1.136710] using input dev h2w headset for key reset
<6>[ 1.136800] using input dev liberty-keypad for key reset
<6>[ 1.137171] gpio_keys_scan_keys: key 1-116, 0 (20) changed to 0
<6>[ 1.137358] gpiomatrix: key 115, 0-0 (35-42) changed to 1
<6>[ 1.137988] using rtc device, msm_rtc, for alarms
<6>[ 1.138011] rs30000048:00010004 rs30000048:00010004: rtc core: registered
msm_rtc as rtc0
<6>[ 1.138113] adp1650 Led Flash driver: init
<6>[ 1.138213] Linux video capture interface: v2.00
<4>[ 1.138288] s5k4e1gx_init
<4>[ 1.138375] __s5k4e1gx_probe
<6>[ 1.138390] s5k4e1gx_vreg_enable camera vreg on
<3>[ 1.138405] sensor platform_data didnt register
<3>[ 1.138421] __s5k4e1gx_probe fail sensor power on error
<6>[ 1.138920] sctrl.node 0
<4>[ 1.138933] s5k4e1gx_sensor_probe()
<6>[ 1.138988] s5k4e1gx_probe called!
<6>[ 1.189073] s5k4e1gx_probe successed! rc = 0
<6>[ 1.189163] s5k4e1gx s->node 0
<6>[ 1.234290] s5k4e1gx_sensor_init(): reseting sensor.
<6>[ 1.234396] msm_hsusb_phy_reset
<6>[ 1.234868] sensor_lc_disable=0
<4>[ 1.326080] sensor evt version : 0x10
<4>[ 1.326096] use analog_settings_evt3
<6>[ 1.334836] s5k4e1gx_sysfs_init : kobject_create_and_add
<6>[ 1.334890] s5k4e1gx_sysfs_init : sysfs_create_file
<6>[ 1.336375] device-mapper: uevent: version 1.0.3
<6>[ 1.336828] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: d
[email protected]
<6>[ 1.336928] Bluetooth: HCI UART driver ver 2.2
<6>[ 1.336948] Bluetooth: HCI H4 protocol initialized
<6>[ 1.336965] Bluetooth: HCILL protocol initialized
<6>[ 1.337003] perflock_notifier_call: cpufreq lock speed 600000
<6>[ 1.337021] active perf lock 'boot-time'
<4>[ 1.338053] smem_item: id=134 not allocated, return 0
<6>[ 1.338163] mmc0: Qualcomm MSM SDCC at 0x00000000a0400000 irq 24,0 dma 8
<6>[ 1.338186] mmc0: Platform slot type: N/A
<6>[ 1.338201] mmc0: 4 bit data mode enabled
<6>[ 1.338218] mmc0: 8 bit data mode disabled
<6>[ 1.338236] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 100000000 Hz
<6>[ 1.338256] mmc0: Slot eject status = 1
<6>[ 1.338273] mmc0: Power save feature enable = 1
<6>[ 1.338295] mmc0: DM non-cached buffer at ffa4b000, dma_addr 0x24868000
<6>[ 1.338316] mmc0: DM cmd busaddr 0x24868000, cmdptr busaddr 0x24868300
<7>[ 1.338688] msmsdcc_platform_status_irq: 102
<6>[ 1.338715] mmc1: Slot status change detected (0 -> 1)
<6>[ 1.339050] photon_sdslot_switchvdd: Disabling SD slot power
<4>[ 1.340275] smem_item: id=134 not allocated, return 0
<6>[ 1.340348] mmc1: Qualcomm MSM SDCC at 0x00000000a0500000 irq 26,102 dma 8
<6>[ 1.340370] mmc1: Platform slot type: SD
<6>[ 1.340385] mmc1: 4 bit data mode enabled
<6>[ 1.340400] mmc1: 8 bit data mode disabled
<6>[ 1.340418] mmc1: MMC clock 144000 -> 50000000 Hz, PCLK 100000000 Hz
<6>[ 1.340438] mmc1: Slot eject status = 0
<6>[ 1.340453] mmc1: Power save feature enable = 1
<6>[ 1.340473] mmc1: DM non-cached buffer at ffa4c000, dma_addr 0x2486a000
<6>[ 1.340495] mmc1: DM cmd busaddr 0x2486a000, cmdptr busaddr 0x2486a300
<6>[ 1.341103] Registered led device: amber
<6>[ 1.341225] Registered led device: green
<6>[ 1.341353] Registered led device: button-backlight
<6>[ 1.341398] microp_led_probe: succeeded
<6>[ 1.342401] logger: created 64K log 'log_main'
<6>[ 1.342558] logger: created 256K log 'log_events'
<6>[ 1.342703] logger: created 64K log 'log_radio'
<6>[ 1.342870] logger: created 64K log 'log_system'
<4>[ 1.343385] GACT probability NOT on
<4>[ 1.343401] Mirror/redirect action on
<4>[ 1.343420] u32 classifier
<4>[ 1.343431] Actions configured
<4>[ 1.343450] Netfilter messages via NETLINK v0.30.
<4>[ 1.343566] nf_conntrack version 0.5.0 (4457 buckets, 17828 max)
<4>[ 1.343936] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Plea
se use
<4>[ 1.343960] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack modu
le option or
<4>[ 1.343981] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
<4>[ 1.344218] ctnetlink v0.93: registering with nfnetlink.
<6>[ 1.344565] xt_time: kernel timezone is -0000
<6>[ 1.344935] ip_tables: (C) 2000-2006 Netfilter Core Team
<6>[ 1.345156] arp_tables: (C) 2002 David S. Miller
<6>[ 1.345258] TCP cubic registered
<6>[ 1.345741] NET: Registered protocol family 10
<6>[ 1.346556] lo: Disabled Privacy Extensions
<6>[ 1.347240] Mobile IPv6
<6>[ 1.347261] IPv6 over IPv4 tunneling driver
<6>[ 1.347913] sit0: Disabled Privacy Extensions
<6>[ 1.348643] ip6tnl0: Disabled Privacy Extensions
<6>[ 1.348796] NET: Registered protocol family 17
<6>[ 1.348843] NET: Registered protocol family 15
<6>[ 1.348890] Bluetooth: L2CAP ver 2.14
<6>[ 1.348905] Bluetooth: L2CAP socket layer initialized
<6>[ 1.348931] Bluetooth: SCO (Voice Link) ver 0.6
<6>[ 1.348948] Bluetooth: SCO socket layer initialized
<6>[ 1.349211] Bluetooth: RFCOMM TTY layer initialized
<6>[ 1.349245] Bluetooth: RFCOMM socket layer initialized
<6>[ 1.349263] Bluetooth: RFCOMM ver 1.11
<6>[ 1.349281] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
<6>[ 1.349301] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
<4>[ 1.349448] smem_item: id=334 offset=102240 size=56=
<4>[ 1.349473] smem_item: id=136 offset=465320 size=256=
<6>[ 1.349491] [Port list] init()
<6>[ 1.349508] [Port list] Virtual Address for port_list: [f81719a8]
<6>[ 1.349526] [Port list] Physical Address for port_list: [FF719A8]
<6>[ 1.350056] wifi_nvs_init
<6>[ 1.350095] Device Wifi Mac Address: macaddr= 0:23:76:fb:c8:54
<6>[ 1.350105]
<4>[ 1.354598] htc_get_batt_info: cable status really needed an update: gpio
detected source=1, cable detected source=0
<4>[ 1.354648] htc_get_batt_info called: batt_id=270;volt=4127;tempRaw=199C;t
emp=199C;current=27;discharge=549;LEVEL=100;charging src=0;charging?0;adc_range=
4102
<4>[ 1.354680] [BAT]: initialized settings
<6>[ 1.354940] perflock_notifier_call: screen_on_policy_req 1,policy_min 4800
00
<6>[ 1.354968] perflock_notifier_call: cpufreq lock speed 600000
<6>[ 1.354986] active perf lock 'boot-time'
<6>[ 1.355011] VFP support v0.3: implementor 41 architecture 1 part 20 varian
t b rev 5
<4>[ 1.356331] smem_item: id=134 not allocated, return 0
<6>[ 1.356770] rs30000048:00010004 rs30000048:00010004: setting system clock
to 2012-01-04 01:30:28 UTC (1325640628)
<6>[ 1.357250] Freeing init memory: 1148K
<4>[ 1.357325] Warning: unable to open an initial console.
<4>[ 1.372418] smem_item: id=134 not allocated, return 0
<4>[ 1.374506] smem_item: id=134 not allocated, return 0
<4>[ 1.375573] smem_item: id=134 not allocated, return 0
<6>[ 1.382431] msm72k_udc: ulpi: write 0x1d to 0x0d
<6>[ 1.382460] msm72k_udc: ulpi: write 0x1d to 0x10
<6>[ 1.382523] usb: notify offline
<6>[ 1.382538] msm_hsusb: enable pullup
<6>[ 1.385568] msm72k_udc: usb: suspend
<6>[ 1.402318] usb: not AC charger
<6>[ 1.437415] photon_sdslot_switchvdd: Setting level to 2900
<3>[ 1.471996] init: Unable to open persistent property directory /data/prope
rty errno: 2
<6>[ 1.476298] enabling adb
<6>[ 1.476386] hsusb: ONLINE -> RESET
<6>[ 1.476403] msm_hsusb: disable pullup
<6>[ 1.476421] hsusb: reset controller
<6>[ 1.479938] adb_open
<4>[ 1.492405] smem_item: id=134 not allocated, return 0
<4>[ 1.512376] smem_item: id=134 not allocated, return 0
<6>[ 1.513603] msm_hsusb_phy_reset
<4>[ 1.515001] smem_item: id=134 not allocated, return 0
<6>[ 1.547458] photon_sdslot_switchvdd: Setting level to 2850
<4>[ 1.547540] smem_item: id=134 not allocated, return 0
<4>[ 1.547610] smem_item: id=134 not allocated, return 0
<4>[ 1.550118] smem_item: id=134 not allocated, return 0
<6>[ 1.589580] msmfb: pan_update in state(1)
<6>[ 1.589603] msmfb: full update starting
<6>[ 1.599925] gpiomatrix: key 115, 0-0 (35-42) changed to 0
<6>[ 1.602691] yaffs: dev is 32505862 name is "mtdblock6" rw
<6>[ 1.602718] yaffs: passed flags ""
<7>[ 1.602740] yaffs: Attempting MTD mount of 31.6,"mtdblock6"
<6>[ 1.633566] msmfb: full update completed
<6>[ 1.633680] msmfb: turning on panel
<4>[ 1.641243] ###BAD BLOCK 4049 1FA20000###
<7>[ 1.641260] block 82 is bad
<7>[ 1.661540] yaffs_read_super: isCheckpointed 0
<6>[ 1.662728] msm72k_udc: ulpi: write 0x1d to 0x0d
<6>[ 1.662753] msm72k_udc: ulpi: write 0x1d to 0x10
<6>[ 1.662816] usb: notify offline
<6>[ 1.662853] msm_hsusb: enable pullup
<6>[ 1.662868] hsusb: RESET -> ONLINE
<6>[ 1.665876] msm72k_udc: usb: suspend
<7>[ 1.673721] turn on backlight.
<4>[ 1.673900] smem_item: id=134 not allocated, return 0
<6>[ 1.702286] usb: send connect type -1
<4>[ 1.702325] usb_status_notifier_func: NOTIFIER Connected usb == 1
<6>[ 1.702346] fsg_set_ums_state: 1
<7>[ 1.765621] save exit: isCheckpointed 1
<6>[ 1.774656] msm72k_udc: usb: reset
<6>[ 1.774698] usb: send connect type 1
<4>[ 1.774721] usb_status_notifier_func: NOTIFIER Connected usb == 1
<6>[ 1.774743] fsg_set_ums_state: 1
<6>[ 1.774756] ums: set state 1
<6>[ 1.776936] msm72k_udc: usb: portchange USB_SPEED_HIGH
<6>[ 1.949460] msm72k_udc: usb: reset
<6>[ 1.951736] msm72k_udc: usb: portchange USB_SPEED_HIGH
<6>[ 2.166845] android_usb gadget: high speed config #1: android
<6>[ 2.166925] adb_function_set_alt: maxsize = 512
<6>[ 2.166998] ums: set state 1
<4>[ 2.336163] smem_item: id=134 not allocated, return 0
<4>[ 2.351455] smem_item: id=134 not allocated, return 0
<4>[ 2.351571] smem_item: id=134 not allocated, return 0
<4>[ 2.351618] smem_item: id=134 not allocated, return 0
<4>[ 2.351640] mmc1: host does not support reading read-only switch. assuming
write-enable.
<6>[ 2.351680] mmc1: new high speed SDHC card at address 1234
<6>[ 2.352446] mmcblk0: mmc1:1234 SA08G 7.42 GiB
<6>[ 2.352780] mmcblk0:
<6>[ 60.722268] Release 'boot-time' no_halt_lock
<3>[ 240.762271] INFO: task rpcrouter:16 blocked for more than 120 seconds.
<3>[ 240.762303] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables th
is message.
<6>[ 240.762326] rpcrouter D c045aed8 0 16 2 0x00000000
<4>[ 240.762429] [<c045aed8>] (schedule+0x444/0x4d8) from [<c013b4e0>] (rr_read
+0x14c/0x178)
<4>[ 240.762474] [<c013b4e0>] (rr_read+0x14c/0x178) from [<c013c698>] (do_read_
data+0x14/0x3a8)
<4>[ 240.762528] [<c013c698>] (do_read_data+0x14/0x3a8) from [<c0173ca0>] (work
er_thread+0x16c/0x210)
<4>[ 240.762573] [<c0173ca0>] (worker_thread+0x16c/0x210) from [<c01772b0>] (kt
hread+0x78/0x80)
<4>[ 240.762629] [<c01772b0>] (kthread+0x78/0x80) from [<c0128874>] (kernel_thr
ead_exit+0x0/0x8)
<3>[ 360.762276] INFO: task rpcrouter:16 blocked for more than 120 seconds.
<3>[ 360.762308] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables th
is message.
<6>[ 360.762331] rpcrouter D c045aed8 0 16 2 0x00000000
<4>[ 360.762424] [<c045aed8>] (schedule+0x444/0x4d8) from [<c013b4e0>] (rr_read
+0x14c/0x178)
<4>[ 360.762468] [<c013b4e0>] (rr_read+0x14c/0x178) from [<c013c698>] (do_read_
data+0x14/0x3a8)
<4>[ 360.762514] [<c013c698>] (do_read_data+0x14/0x3a8) from [<c0173ca0>] (work
er_thread+0x16c/0x210)
<4>[ 360.762558] [<c0173ca0>] (worker_thread+0x16c/0x210) from [<c01772b0>] (kt
hread+0x78/0x80)
<4>[ 360.762611] [<c01772b0>] (kthread+0x78/0x80) from [<c0128874>] (kernel_thr
ead_exit+0x0/0x8)
~ #
Hi,
I bought a second hand i9505, which i used for several days with the standard Samsung stuff.
After a few day's i installed CM11, but after a day my wifi stopped working.
Then i started googling, found several other treads with the same problem, tried those solutions.
But at the this point none of them worked for me.
Things that i tried:
-Different modems
-Stock Samsung rom
-Factory reset
-Format /system , and reflash stock rom with Odin
-Pull the battery out for 30mins
-Reconnected the Wifi antenna
-Deleted the WPA_Supplicant file
-Disable the powersaving mode under *#0011#
Al of them did not work for me.
Is there anybody who has an idea?
Thanks in advance!
sven93 said:
Hi,
I bought a second hand i9505, which i used for several days with the standard Samsung stuff.
After a few day's i installed CM11, but after a day my wifi stopped working.
Then i started googling, found several other treads with the same problem, tried those solutions.
But at the this point none of them worked for me.
Things that i tried:
-Different modems
-Stock Samsung rom
-Factory reset
-Format /system , and reflash stock rom with Odin
-Pull the battery out for 30mins
-Reconnected the Wifi antenna
-Deleted the WPA_Supplicant file
-Disable the powersaving mode under *#0011#
Al of them did not work for me.
Is there anybody who has an idea?
Thanks in advance!
Click to expand...
Click to collapse
Hi,
Maybe is hardware related did you check if the WIFI Antenna Signal Flex Cable is well connected?
https://www.ifixit.com/Teardown/Samsung+Galaxy+S4+Teardown/13947
MAX 404 said:
Hi,
Maybe is hardware related did you check if the WIFI Antenna Signal Flex Cable is well connected?
Click to expand...
Click to collapse
Thanks, but i already tried this.
Reconnected both connections, and made sure both were aligned flat on the connector.
Unfortunately without any result.
sven93 said:
Thanks, but i already tried this.
Reconnected both connections, and made sure both were aligned flat on the connector.
Unfortunately without any result.
Click to expand...
Click to collapse
Maybe is the chip....can you scan , do you see wifi networks or did you try the option wifi direct , between your phone and another unit?
MAX 404 said:
Maybe is the chip....can you scan , do you see wifi networks or did you try the option wifi direct , between your phone and another unit?
Click to expand...
Click to collapse
Well, lets hope its not the chip.
I can't turn on the wifi, if i tap the wifi button (either in settings or at the notifications area) it goes green for 0.5 sec and goes to grey right after.
Haven't tried wifi-direct as i don't have any compatible devices.
Just tried to turn on the tether service, there is states "Error" when i try to turn it on.
Is there any logfile that i can use to determine the cause?
sven93 said:
Well, lets hope its not the chip.
I can't turn on the wifi, if i tap the wifi button (either in settings or at the notifications area) it goes green for 0.5 sec and goes to grey right after.
Haven't tried wifi-direct as i don't have any compatible devices.
Just tried to turn on the tether service, there is states "Error" when i try to turn it on.
Is there any logfile that i can use to determine the cause?
Click to expand...
Click to collapse
Not sure about the log file ...
Here i found a thread , it talks about a solution but they use a SPT box, for what i see the problem is efs related, do you have an EFS backup?
http://forum.gsmhosting.com/vbb/f45...nlock-default-efs-imei-solution-here-1788263/
Nope, unfortunately i didn't backup the EFS folder.
Flashed my S2 a thousand times, with backup, never happened anything. I flash my S4 1 time without,...
Compared the content with the S2, and for me is looks like everything needed is still there. (not an expert though)
Any other ideas?
sven93 said:
Nope, unfortunately i didn't backup the EFS folder.
Flashed my S2 a thousand times, with backup, never happened anything. I flash my S4 1 time without,...
Compared the content with the S2, and for me is looks like everything needed is still there. (not an expert though)
Any other ideas?
Click to expand...
Click to collapse
1. Dial *#1234# in Stock Rom and check if your Csc is correct.
2. Reflash 2 times the stock rom.
Joku1981 said:
1. Dial *#1234# in Stock Rom and check if your Csc is correct.
2. Reflash 2 times the stock rom.
Click to expand...
Click to collapse
CSC Seems to match.
Tried flashing it 3 times in a row with the same (stock) ROM, still nothing.
sven93 said:
Hi,
I bought a second hand i9505, which i used for several days with the standard Samsung stuff.
After a few day's i installed CM11, but after a day my wifi stopped working.
Then i started googling, found several other treads with the same problem, tried those solutions.
But at the this point none of them worked for me.
Things that i tried:
-Different modems
-Stock Samsung rom
-Factory reset
-Format /system , and reflash stock rom with Odin
-Pull the battery out for 30mins
-Reconnected the Wifi antenna
-Deleted the WPA_Supplicant file
-Disable the powersaving mode under *#0011#
Al of them did not work for me.
Is there anybody who has an idea?
Thanks in advance!
Click to expand...
Click to collapse
I have the same problem. Wifi won't turn on no matter what I do. I was on cm-11-20140627-NIGHTLY-jflte and then decided to upgrade to cm-11-20140908-NIGHTLY-jflte. With that upgrade I lost wifi. I tried every possible thing that I found on forums and nothing helped. I also tried to upgrade to latest stock. I was on old bootloader until then, now I have the KNOX sh...t.
I have a feeling that something is wrong with wifi firmware. Is there a way to somehow check or reflash wifi firmware only?
regards.
ajax505 said:
I have the same problem. Wifi won't turn on no matter what I do. I was on cm-11-20140627-NIGHTLY-jflte and then decided to upgrade to cm-11-20140908-NIGHTLY-jflte. With that upgrade I lost wifi. I tried every possible thing that I found on forums and nothing helped. I also tried to upgrade to latest stock. I was on old bootloader until then, now I have the KNOX sh...t.
I have a feeling that something is wrong with wifi firmware. Is there a way to somehow check or reflash wifi firmware only?
regards.
Click to expand...
Click to collapse
Sad to hear you have the same.
Pretty strange, i haven't used the S4 since Wednesday, but the phone was still turned on, ten minutes ago i wanted to check something, turns out wifi is working again, until i decided to reboot, now its doing the same as before...
It does indeed smells software/firmware related.
Just made a dumpfile of the logs (bugreport > /mnt/sdcard/dump.txt) , and saw some interesting stuff in the kernel log:
<4>[ 9.717163] failed to power up wifi chip, retry again (5 left) **
<4>[ 9.717163]
<4>[ 9.733306] ## wifi_remove
<4>[ 9.733612] wifi_set_power = 1
<4>[ 9.733612] WiFi: trying to acquire BT lock
<4>[ 9.733612] ####btlock acquired cookie: WiFi
<4>[ 9.733642] wifi_set_power: btlock acquired
<6>[ 9.733642] ------------------------------------------------
<6>[ 9.733642] ------------------------------------------------
<6>[ 9.733642] brcm_wlan_power Enter: power on
<3>[ 9.733642] brcm_wlan_power: WL_REG_ON failed to pull up
<4>[ 9.733734] wifi_probe: set_power failed. err=-5
<4>[ 9.733734] wifi_set_power = 0
<4>[ 9.733734] ####btlock released, cookie: WiFi
<6>[ 9.733734] ------------------------------------------------
<6>[ 9.733795] ------------------------------------------------
<6>[ 9.733825] brcm_wlan_power Enter: power off
<3>[ 9.733825] brcm_wlan_power: WL_REG_ON failed to pull down
Click to expand...
Click to collapse
Then after a bit:
<4>[ 11.727294]
<4>[ 11.727294] failed to power up wifi chip, retry again (4 left) **
<4>[ 11.727294]
<4>[ 11.743499] ## wifi_remove
<4>[ 11.743835] wifi_set_power = 1
<4>[ 11.743835] WiFi: trying to acquire BT lock
<4>[ 11.743835] ####btlock acquired cookie: WiFi
<4>[ 11.743835] wifi_set_power: btlock acquired
<6>[ 11.743835] ------------------------------------------------
<6>[ 11.743865] ------------------------------------------------
<6>[ 11.743865] brcm_wlan_power Enter: power on
<6>[ 11.743865] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 1
<6>[ 11.754608] [email protected]: Start PackageManagerService
<6>[ 11.775604] [SSP] Updated 73599 bytes / 139282 bytes
<4>[ 11.977172] wifi_set_carddetect = 1
<4>[ 11.977172] brcm_wifi_status:267 status 1
Click to expand...
Click to collapse
For people who want to view the log: https://dl.dropboxusercontent.com/u/15503253/dumpfile.txt
I also get those kind of messages in my system logs:
<4>[ 1837.921936] failed to power up wifi chip, retry again (1 left) **
<4>[ 1837.921966]
<4>[ 1837.941497] ## wifi_remove
<4>[ 1837.941497] wifi_set_power = 0
<4>[ 1837.941528] ####btlock released, cookie: WiFi
<6>[ 1837.941558] ------------------------------------------------
<6>[ 1837.941558] ------------------------------------------------
<6>[ 1837.941589] brcm_wlan_power Enter: power off
<6>[ 1837.941619] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 0
<4>[ 1838.182006] wifi_set_carddetect = 0
<4>[ 1838.182037] brcm_wifi_status:267 status 0
<6>[ 1838.182067] mmc1: Slot status change detected (1 -> 0)
<4>[ 1838.187591]
<4>[ 1838.187622] failed to power up wifi chip, max retry reached, exits **
Click to expand...
Click to collapse
I also get a lot of "mmc1: Data CRC error":
<3>[ 1826.574645] mmc1: Data CRC error
<3>[ 1826.577178] msmsdcc_data_err: opcode 0x00000035
<3>[ 1826.581542] msmsdcc_data_err: blksz 4, blocks 1
<6>[ 1826.586883] sps:BAM 0x12182000 enabled: ver:0x5, number of pipes:6dhd_detach(): thread:dhd_sysioc:392 terminated OK
<4>[ 1826.651245] dhd_detach(): thread:dhd_watchdog_thread:38f terminated OK
<4>[ 1826.651336] dhd_dpc_thread: Unexpected up_cnt 0
<4>[ 1826.651428] dhd_detach(): thread:dhd_dpc:390 terminated OK
<4>[ 1826.651733] dhd_detach(): thread:dhd_rxf:391 terminated OK
<6>[ 1826.670593] CFG80211-INFO2) wl_event_handler : was terminated
<4>[ 1826.670898] wl_destroy_event_handler(): thread:wl_event_handler:38e terminated OK
<4>[ 1826.682250] dhdsdio_disconnect : the lock is released.
<4>[ 1826.683807] ## wifi_remove
<4>[ 1826.683837] wifi_set_power = 0
<4>[ 1826.683868] ####ignore lock release, cookie mismatch: WiFi owner ˙˙˙˙
<6>[ 1826.683898] ------------------------------------------------
<6>[ 1826.683898] ------------------------------------------------
<6>[ 1826.683929] brcm_wlan_power Enter: power off
<6>[ 1826.683959] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 0
<4>[ 1826.920593] wifi_set_carddetect = 0
<4>[ 1826.920623] brcm_wifi_status:267 status 0
<6>[ 1826.920654] mmc1: Slot status change detected (1 -> 0)
<6>[ 1826.928405] mmc1: card 0001 removed
<6>[ 1828.083618] synaptics_rmi4_i2c 3-0020: [0][P] 0x01
<6>[ 1828.142578] synaptics_rmi4_i2c 3-0020: [0][R] 0x00 M[4] V[5c]
<4>[ 1828.178527] wifi_set_power = 1
<4>[ 1828.178558] WiFi: trying to acquire BT lock
<4>[ 1828.178558] ####btlock acquired cookie: WiFi
<4>[ 1828.178558] wifi_set_power: btlock acquired
<6>[ 1828.178558] ------------------------------------------------
<6>[ 1828.178588] ------------------------------------------------
<6>[ 1828.178588] brcm_wlan_power Enter: power on
<6>[ 1828.178588] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 1
<4>[ 1828.411895] wifi_set_carddetect = 1
<4>[ 1828.411926] brcm_wifi_status:267 status 1
<6>[ 1828.411956] mmc1: Slot status change detected (0 -> 1)
<3>[ 1828.473205] mmc1: msmsdcc_switch_io_voltage: MCIDATIN_3_0 is still not all zeros
<3>[ 1828.480651] mmc1: CMD7: Command CRC error
<3>[ 1828.484039] mmc1: SDCC PWR is ON
<3>[ 1828.487426] mmc1: SDCC clks are ON, MCLK rate=400000
<3>[ 1828.492217] mmc1: SDCC irq is enabled
<3>[ 1828.495849] ===== SDCC-CORE: Register Dumps @phys_base=0x12180000, @virt_base=0xe337a000 =====
<3>[ 1828.504608] Reg=0x00: 0x00000001, 0x01209300, 0x00000000, 0x00000447
<3>[ 1828.510955] Reg=0x10: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.517120] Reg=0x20: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.523620] Reg=0x30: 0x00000000, 0x004c0000, 0x00000000, 0x408001ff
<3>[ 1828.529785] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.536285] Reg=0x50: 0x06000018, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.542633] Reg=0x60: 0x67356400, 0x00000000, 0x00000018, 0x00000000
<3>[ 1828.548797] ===== SDCC-DML: Register Dumps @phys_base=0x12180800, @virt_base=0xe3534800 =====
<3>[ 1828.557495] Reg=0x00: 0x00000000, 0x00010001, 0x00000000, 0x00000000
<3>[ 1828.563629] Reg=0x10: 0x00000000, 0x00001000, 0x00001000, 0x00020001
<3>[ 1828.570159] Reg=0x20: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.576477] Reg=0x30: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.582641] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.589172] ===== SDCC-BAM: Register Dumps @phys_base=0x12182000, @virt_base=0xe33d8000 =====
<3>[ 1828.597503] Reg=0x00: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.604003] Reg=0x10: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.610351] Reg=0x20: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.616516] Reg=0x30: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.623016] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.629180] mmc1: MCI_TEST_INPUT = 0x0000003e
<3>[ 1828.633697] mmc1: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0, req_tout_ms=10000
<3>[ 1828.644012] mmc1: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<3>[ 1828.650817] mmc1: RPM: runtime_status=0, usage_count=2, is_suspended=0, disable_depth=0, runtime_error=0, request_pending=0, request=0
<4>[ 1828.663024] mmc1: Skipped tuning.
<3>[ 1828.686431] mmc1: error -110 whilst initialising SDIO card
<4>[ 1830.421936]
<4>[ 1830.421966] failed to power up wifi chip, retry again (4 left) **
Click to expand...
Click to collapse
As long as I know mmc0 is internal memory and mmc2 is external sd card. Can anyone explain what mmc1 device is?
Bump...