maemo.org - Talk - Announce: USB Mode (easy switch to USB host mode) [in Extras-Devel]

maemo.org - Talk (https://talk.maemo.org/index.php)

- Nokia N900 (https://talk.maemo.org/forumdisplay.php?f=44)

- - Announce: USB Mode (easy switch to USB host mode) [in Extras-Devel] (https://talk.maemo.org/showthread.php?t=85658)

Re: Announce: USB Mode (easy switch to USB host mode) [in Extras-Devel]

Quote:

Originally Posted by Freddie (Post 1370063)

Sorry if I irritated you, but pls also note that this featured on 2 different issues but the solution appears to be the same, "get the right kernel first".

am still workin on it, thanks so very much for your assistance. Will update when/if I get thru successfully.

No, the solution is "setup the correct repositories first" ;)

Re: Announce: USB Mode (easy switch to USB host mode) [in Extras-Devel]

Quote:

Originally Posted by freemangordon (Post 1370065)

No, the solution is "setup the correct repositories first" ;)

....workin on it now.

Re: Announce: USB Mode (easy switch to USB host mode) [in Extras-Devel]

usbmode on my device is not working. I have all vitals installed . I am getting a timeout error I think . Seeing the error is too difficult since it fades away too quickly. Should i increase the sleep time in usbmode.sh as stated in previous posts?

Re: Announce: USB Mode (easy switch to USB host mode) [in Extras-Devel]

I would like to report that I have successfully used the N900 as a serial console using a TTL USB cable + screen from the repos. Great sutff!

Re: Announce: USB Mode (easy switch to USB host mode) [in Extras-Devel]

Can somebody tell me which timeouts needs to be increased? I will release new version with fixed host mode with charging support and I'd like to fix timeouts, so usbmode will work for more devices.

Re: Announce: USB Mode (easy switch to USB host mode) [in Extras-Devel]

Re up:

(...)

Code:

charger_mode boost

sleep 4



usb_enum

sleep 3

(...)

...worksforme. Even for picky hard drives. 5 and 4, respectively, would mean additional second for every operation, just to be on a safe side, so it may be even better idea.

/Estel

Re: Announce: USB Mode (easy switch to USB host mode) [in Extras-Devel]

Hi there, I have a battery drainage problem. I installed KP52 + CSSU v21.2011.38-1Tmaemo9.1on newly re-flashed n900 and then installed usbmode. So now, about 20% of battery drains over the night time period! I hope someone knows how to deal with it?

Re: Announce: USB Mode (easy switch to USB host mode) [in Extras-Devel]

Quote:

Originally Posted by evropean (Post 1425720)

Try using powertop to id. the process. Search this forum and /or wiki for details of use.

I assume you mean that the device was OK up UNTIL you installed usbmode, ie. you tested enough to know it was not something installed earlier on.

Re: Announce: USB Mode (easy switch to USB host mode) [in Extras-Devel]

Quote:

Originally Posted by handaxe (Post 1425747)

As you suggested, I have used powertop, so thats what I've got:

Quote:

Code:

~ $ root 





BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso31+0cssu0) built-in shell (ash) 

Enter 'help' for a list of built-in commands. 



Nokia-N900:~# powertop 

Powertop 1.13.3 

status: Unknown job: pmtrackerdaemon 

Sleeping for 11 seconds before sampling 

Collecting data for 30 seconds 

Sample interval was 00m 30s 10376us 



C# | Ratio | Avg/dura | Frequency | Ratio 

--------+--------+----------+-----------+--------+ 

C0 | 14.2% | | 1150 MHz | nan% | 

C1 | 0.5% | 2.5ms | 

C2 | 52.7% | 14.3ms | 

C3 | 13.4% | 103.1ms | 

C4 | 19.2% | 821.0ms | 



IRQ# | Activity | Type | Name 

--------+------------+----------------+--------------------------- 

37 | 1100 | INTC | gp 

61 | 974 | INTC | i2c_omap 

11 | 634 | INTC | prcm 

56 | 437 | INTC | i2c_omap 

57 | 270 | INTC | i2c_omap 

86 | 85 | INTC | mmc1 

21 | 52 | INTC | SGX 

12 | 23 | INTC | DMA 

25 | 1 | INTC | OMAP 



PID# | Activity | Name | Function Entry (Expire) 

--------+------------+----------------+--------------------------- 

0 | 878 | <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer) 

782 | 141 | mce | schedule_hrtimeout_range (hrtimer_wakeup) 

38 | 81D| awk | cpufreq_governor_dbs (delayed_work_timer_fn) 

0 | 24 | <kernel core> | hrtimer_start (tick_sched_timer) 

15231 | 19 | osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup) 

679 | 18 | dsme | __enqueue_rt_entity (sched_rt_period_timer) 

590 | 8 | mmcqd | queue_delayed_work (delayed_work_timer_fn) 

709 | 6 | bme_RX-51 | sys_timer_settime (posix_timer_fn) 

847 | 5 | Xorg | hrtimer_start (it_real_fn) 

847 | 5 | Xorg | queue_delayed_work (delayed_work_timer_fn) 

590 | 5 | mmcqd | schedule_timeout (process_timeout) 

782 | 4 | mce | tsc2005_start_scan (tsc2005_esd_timer_handler) 

1190 | 3 | location-proxy | queue_delayed_work (delayed_work_timer_fn) 

679 | 3 | dsme | do_nanosleep (hrtimer_wakeup) 

1 | 3D| <kernel core> | queue_delayed_work (delayed_work_timer_fn) 

782 | 3 | mce | queue_delayed_work (delayed_work_timer_fn) 

809 | 2 | sgx_perf | queue_delayed_work (delayed_work_timer_fn) 

29675 | 2D|<kernel module> | queue_delayed_work (delayed_work_timer_fn) 

709 | 2 | bme_RX-51 | sys_timer_settime (posix_timer_fn) 

709 | 2 | bme_RX-51 | do_nanosleep (hrtimer_wakeup) 

709 | 2 | bme_RX-51 | schedule_timeout (process_timeout) 

1106 | 2 |hildon-status-m | schedule_hrtimeout_range (hrtimer_wakeup) 

18455 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 

6223 | 1 | apt-worker | addrconf_verify (addrconf_verify) 

18481 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 

1113 | 1 | hildon-home | schedule_hrtimeout_range (hrtimer_wakeup) 

18507 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 

18533 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 

758 | 1 | hald | schedule_hrtimeout_range (hrtimer_wakeup) 

18559 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 

18585 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 

1 | 1 | <kernel core> | inet_initpeers (peer_check_expire) 

18611 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 

18637 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 

590 | 1 | mmcqd | schedule_timeout (process_timeout) 

18663 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 

18689 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 

590 | 1 | mmcqd | cfq_completed_request (cfq_idle_slice_timer) 

1115 | 1 | hildon-desktop | queue_delayed_work (delayed_work_timer_fn) 

23608 | 1 | browserd | futex_wait (hrtimer_wakeup) 

782 | 1 | mce | schedule_timeout (process_timeout) 

18715 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 

18759 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 

1082 | 1 | iphbd | schedule_hrtimeout_range (hrtimer_wakeup) 

30 | 1 | mount | setup_wb_timer (wb_timer_fn) 

18785 | 1 | sleep | do_nanosleep (hrtimer_wakeup) 

18321 | 1 | powertop | do_nanosleep (hrtimer_wakeup) 



Power domain activity breakdown 

Domain | % of time spent in states 

--------+---------+---------+---------+---------+---------- 

usbhost |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF) 

sgx |OFF: 96%|RET: 0%|INA: 0%| ON: 3%| now:(OFF) 

per |OFF: 32%|RET: 52%|INA: 0%| ON: 15%| now:(ON) 

dss |OFF: 23%|RET: 0%|INA: 0%| ON: 76%| now:(OFF) 

cam |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF) 

core |OFF: 14%|RET: 4%|INA: 62%| ON: 19%| now:(ON) 

neon |OFF: 19%|RET: 13%|INA: 52%| ON: 15%| now:(ON) 

mpu |OFF: 19%|RET: 13%|INA: 52%| ON: 15%| now:(ON) 

iva2 |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF) 



Clock activity breakdown at end of period 

Domain | Active clocks 

--------+---------------+---------------+------------------ 

core | SDRC | HSOTGUSB_IDLE | OMAPCTRL 

| MAILBOXES | 

wkup | GPT1 | 32KSYNC | GPIO1 

| WDT1 | SR1 | SR2 

| 

ckgen | CORE | PERI | 96M 

| 48M | 12M | 54M 

| EMU_CORE | 

per | GPIO2 | GPIO3 | GPIO4 

| GPIO5 | GPIO6 | 



Total wakeups 4819, 160.6/s | IRQ 3576, 119.2/s | Timers 1243, 41.4/s 

HW wakeups 122, 4.1/s | Real gp_timers expired 76, 2.5/s 

Nokia-N900:~#

few more tests gave me nearly same figures.

can someone help me to identify using this piece of information, what is the problem of battery darinage?
probably it started to drain the battery even after I installed kernel power on newly re-flashed phone, so what is my next step?

Re: Announce: USB Mode (easy switch to USB host mode) [in Extras-Devel]

This likely is o/t for the thread :-) Did you lock the screen during the sampling?

Clearly your device is spending a long time in in state C2. Mine is ca. 85% in C4. But first, apples with apples, so check what I asked above and do so.

Others chip in here who know better than I. Methinks given the new setup, a reflash may be easiest, step by step checking at each point that thge device is behaving.