06-18-2010, 12:28 PM
|
||||
|
||||
|
Re: Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS!
With my basic understanding of the system, a WakeLock is a process is preventing the phone from going into deep sleep, or a process keeps waking the phone from deep sleep... Makk would probably have a better handle on it tho :P
|
|
06-18-2010, 12:39 PM
|
||||
|
||||
|
Re: Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS!
Quote:
there is a chunk with a few wakelocks.
__________________
|
|
06-18-2010, 01:40 PM
|
||||
|
||||
|
Re: Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS!
In case you had trouble parsing that:
Code:
active wake lock vbus_present [ 201.143768] wake lock mmc_delayed_work, expired [ 201.143798] wake lock SMD_DIAG, expired [ 201.143798] wake lock SMD_DS, expired [ 216.321624] request_suspend_state: wakeup (3->0) at 211470000000 (2010-06-15 17:48:41.150000000 UTC) [ 216.321807] htc_pwrsink: ID 0, Util 38%, Total 38000 uA [ 216.321868] epson_resume [ 216.321899] msmfb: panel waking [ 216.321929] msmfb: ready, waiting for full update [ 216.321990] hw3d_late_resume: resuming [ 216.322052] tssc_manager_resume(): ts->use_irq=1 [ 216.322113] Sending arm9_low_speed 7 [ 216.326477] microp-klt: Setting lcd-backlight brightness to: 0x00 [ 216.343078] microp-klt: Setting lcd-backlight brightness to: 0x00 [ 216.359527] microp-klt: Setting lcd-backlight brightness to: 0x00 [ 216.388092] microp-klt: Setting lcd-backlight brightness to: 0x00 [ 216.468017] microp-klt: Setting lcd-backlight brightness to: 0x10 [ 216.508697] microp-klt: Setting lcd-backlight brightness to: 0x10 [ 216.538177] msmfb: full update starting [ 216.548736] microp-klt: Setting lcd-backlight brightness to: 0x10 [ 216.559326] microp-klt: Setting lcd-backlight brightness to: 0x10 [ 216.579101] microp-klt: Setting lcd-backlight brightness to: 0x10 [ 216.588714] fake vsync [ 216.588775] msmfb_start_dma 60.000 ms after vsync request [ 216.599639] microp-klt: Setting lcd-backlight brightness to: 0x20 [ 216.619323] microp-klt: Setting lcd-backlight brightness to: 0x20 [ 216.619598] msmfb: full update completed [ 216.619689] msmfb: turning on panel [ 216.619689] epson_unblank [ 216.620452] rev: got reg 0 = 0 for wrong register, expected 150000 [ 216.639343] microp-klt: Setting lcd-backlight brightness to: 0x20 [ 216.659515] microp-klt: Setting lcd-backlight brightness to: 0x20 [ 216.679473] microp-klt: Setting lcd-backlight brightness to: 0x20 [ 216.699523] microp-klt: Setting lcd-backlight brightness to: 0x30 [ 216.719177] mddi_remote_read(150000) timeout (-1 0 0) [ 216.719238] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 800061, rtd val f curr_rev_ptr 251fa03c [ 216.719818] rev: got reg 0 = 0 for wrong register, expected 150000 [ 216.819244] mddi_remote_read(150000) timeout (-1 -1 0) [ 216.819305] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 800061, rtd val f curr_rev_ptr 251fa050 [ 216.819793] rev: got reg 0 = 0 for wrong register, expected 150000 [ 216.919403] mddi_remote_read(150000) timeout (-1 -1 0) [ 216.919494] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 800061, rtd val f curr_rev_ptr 251fa064 [ 216.919586] init hitachi panel [ 216.919616] msmfb: panel awake [ 493.329986] microp-klt: Setting lcd-backlight brightness to: 0x30 [ 493.349029] microp-klt: Setting lcd-backlight brightness to: 0x20 [ 493.369049] microp-klt: Setting lcd-backlight brightness to: 0x20 [ 493.389160] microp-klt: Setting lcd-backlight brightness to: 0x20 [ 493.409423] microp-klt: Setting lcd-backlight brightness to: 0x20 [ 493.429321] microp-klt: Setting lcd-backlight brightness to: 0x20 [ 493.449432] microp-klt: Setting lcd-backlight brightness to: 0x20 [ 493.469482] microp-klt: Setting lcd-backlight brightness to: 0x20 [ 493.489501] microp-klt: Setting lcd-backlight brightness to: 0x10 [ 493.509521] microp-klt: Setting lcd-backlight brightness to: 0x10 [ 493.529571] microp-klt: Setting lcd-backlight brightness to: 0x10 [ 493.549804] microp-klt: Setting lcd-backlight brightness to: 0x10 [ 493.569976] microp-klt: Setting lcd-backlight brightness to: 0x10 [ 493.590515] microp-klt: Setting lcd-backlight brightness to: 0x10 [ 493.609985] microp-klt: Setting lcd-backlight brightness to: 0x10 [ 493.630065] microp-klt: Setting lcd-backlight brightness to: 0x00 [ 493.650146] microp-klt: Setting lcd-backlight brightness to: 0x00 [ 493.670257] microp-klt: Setting lcd-backlight brightness to: 0x00 [ 500.353454] microp-klt: Setting lcd-backlight brightness to: 0x00 [ 500.372528] microp-klt: Setting lcd-backlight brightness to: 0x00 [ 500.392883] microp-klt: Setting lcd-backlight brightness to: 0x00 [ 500.412780] microp-klt: Setting lcd-backlight brightness to: 0x00 [ 500.414855] request_suspend_state: sleep (0->3) at 494820000000 (2010-06-15 17:53:24.500000000 UTC) [ 500.486694] Sending arm9_low_speed 2 [ 500.486968] msmfb: panel sleeping [ 500.517913] epson_blank [ 500.518585] rev: got reg 0 = 0 for wrong register, expected 150000 [ 500.613342] mddi_remote_read(150000) timeout (-1 -712176016 0) [ 500.613433] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 800061, rtd val f curr_rev_ptr 251fa078 [ 500.613555] rev: got reg 0 = 0 for wrong register, expected 150000 [ 500.713409] mddi_remote_read(150000) timeout (-1 -1 0) [ 500.713470] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 800061, rtd val f curr_rev_ptr 251fa08c [ 500.714172] rev: got reg 0 = 0 for wrong register, expected 150000 [ 500.813629] mddi_remote_read(150000) timeout (-1 -1 0) [ 500.813751] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 800061, rtd val f curr_rev_ptr 251fa0a0 [ 500.813873] deinit epson panel [ 500.813964] epson_suspend [ 500.814025] htc_pwrsink: ID 0, Util 7%, Total 7000 uA [ 500.818481] active wake lock vbus_present [ 500.818542] wake lock mmc_delayed_work, expired [ 500.818572] wake lock SMD_DIAG, expired [ 500.818634] wake lock SMD_DS, expired [ 656.985351] request_suspend_state: wakeup (3->0) at 651170000000 (2010-06-15 17:56:01.710000000 UTC) [ 656.985565] htc_pwrsink: ID 0, Util 38%, Total 38000 uA [ 656.985595] epson_resume [ 656.985656] msmfb: panel waking [ 656.985687] msmfb: ready, waiting for full update [ 656.985748] hw3d_late_resume: resuming
|
|
06-18-2010, 01:44 PM
|
||||
|
||||
|
Re: Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS!
lol that looks better!
|
|
06-18-2010, 02:05 PM
|
||||
|
||||
|
Re: Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS!
sfhub, you were correct yesterday. the newest package has the user.conf with the needed line in it. i had an older one which did not. updated and trying adb now.
|
|
06-18-2010, 02:19 PM
|
||||
|
||||
|
Re: Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS!
I've done the editions to the gps.conf file with Bell's AGPS settings and I seem to still be getting long lock times (if it locks at all).
I'm not sure if 5-10 minute locks are standard but it's pretty unusable as it is. Can anybody shed some light on this? EDIT: Just went and stood outside for 5 minutes and GPSTest gave me 1 satellite. It seems to be getting worse. Last edited by 88fingerslukee; 06-18-2010 at 02:23 PM.
|
|
06-18-2010, 02:27 PM
|
||||
|
||||
|
Re: Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS!
ok got adb working
|
|
06-18-2010, 04:04 PM
|
||||
|
||||
|
Re: Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS!
Quote:
wakelocks are what they sound like -- they lock the device in the awake state (i.e. prevent sleep). I saw one on the PowerManager service (seems to be an higher level Android function to lock), as well as vbus (not sure on this one... USB maybe?), smd_diag (something on the cdma radio, which is weird since I was in airplane mode), and maybe one other. chamonix has Command Center, which will do the dmesg thing, and a bunch of other command line things, from an android interface. I haven't tried it lately, but it's there if you want to give it a shot. Seems convenient. Your dmesg seems to just be locked on vbus -- which I think is just from being connected to a charger/computer.
|
|
06-18-2010, 04:11 PM
|
||||
|
||||
|
Re: Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS!
ya vbus appears to be the usb.
would you like me to enable gps, break deepsleep, try to get it to sleep, and get you a new dmesg out of it?
|
|
06-18-2010, 04:15 PM
|
||||
|
||||
|
Re: Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS!
If you like, but I don't know if it's going to be particularly meaningful.
|
 |
|
| Tags |
| android, donut, eclair, linux |
«
Previous Thread
|
Next Thread
»
Linear Mode
|
|
All times are GMT -4. The time now is 10:10 PM.
