Re: High Battery Consumption
 

This is an ideal powertop output. Bear in mind though that this is in offline mode. When connected to the GSM network you can probably expect around 700-800 wakeups over the 30 second period.

Re: High Battery Consumption
 

Do the procedure as detailed earlier in this thread and come back. Then we can talk.

Re: High Battery Consumption
 

i did follow your procedure
offline mode
battery out
keep in offline mode
wait 4 mins
load xterm n power top
run and lock screen
wait 50 sec
then copied n pasted??

after posting this i finished reading the thread and saw about flashlight extra doesnt uninstall all settings so done that rebooted and is now working good again

Re: High Battery Consumption
 

@vi_ This is the output after exactly following the procedure specified by you.I am on kernel version 46.I have two homescreens.No flashlight.Disabled the OM weather widget before taking this.I have been having horrible battery life like 9 hrs max.I never complained though.please help me find out the culprit. Powertop 1.13.3
status: Unknown job: pmtrackerdaemon
Sleeping for 11 seconds before sampling
Collecting data for 30 seconds
Sample interval was 30m 30s 28625us

C# | Ratio | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
C0 | 98.4% | | 1150 MHz | nan% |
C1 | 0.0% | 0.8ms |
C2 | 0.1% | 14.6ms |
C3 | 0.2% | 56.2ms |
C4 | 1.3% | 698.0ms |

IRQ# | Activity | Type | Name
--------+------------+----------------+---------------------------
56 | 432 | INTC | i2c_omap
86 | 267 | INTC | mmc1
12 | 179 | INTC | DMA
37 | 98 | INTC | gp
11 | 66 | INTC | prcm
57 | 24 | INTC | i2c_omap
21 | 9 | INTC | SGX
225 | 1 | GPIO | omap2-onenand

PID# | Activity | Name | Function Entry (Expire)
--------+------------+----------------+---------------------------
0 | 41 | <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
38 | 25D| awk | cpufreq_governor_dbs (delayed_work_timer_fn)
0 | 20 | <kernel core> | hrtimer_start (tick_sched_timer)
1548 | 19 | osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
584 | 13 | mmcqd | queue_delayed_work (delayed_work_timer_fn)
706 | 6 | bme_RX-51 | sys_timer_settime (posix_timer_fn)
844 | 4 | Xorg | queue_delayed_work (delayed_work_timer_fn)
803 | 3 | sgx_perf | queue_delayed_work (delayed_work_timer_fn)
30 | 3 | mount | setup_wb_timer (wb_timer_fn)
1533 | 2 | pdflush | blk_plug_device (blk_unplug_timeout)
771 | 2 | mce | schedule_hrtimeout_range (hrtimer_wakeup)
666 | 2 | dsme | do_nanosleep (hrtimer_wakeup)
666 | 2 | dsme | __enqueue_rt_entity (sched_rt_period_timer)
706 | 2 | bme_RX-51 | sys_timer_settime (posix_timer_fn)
706 | 2 | bme_RX-51 | do_nanosleep (hrtimer_wakeup)
706 | 2 | bme_RX-51 | schedule_timeout (process_timeout)
695 | 2D|<kernel module> | queue_delayed_work (delayed_work_timer_fn)
1 | 2D| <kernel core> | queue_delayed_work (delayed_work_timer_fn)
844 | 1 | Xorg | hrtimer_start (it_real_fn)
1323 | 1 |mafw-dbus-wrapp | queue_delayed_work (delayed_work_timer_fn)
1502 | 1 | browserd | futex_wait (hrtimer_wakeup)
1441 | 1 |tracker-indexer | schedule_hrtimeout_range (hrtimer_wakeup)
1441 | 1 |tracker-indexer | journal_get_write_access (commit_timeout)
1533 | 1 | pdflush | journal_get_write_access (commit_timeout)
1554 | 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: 97%|RET: 0%|INA: 0%| ON: 2%| now:(OFF)
per |OFF: 86%|RET: 12%|INA: 0%| ON: 1%| now:(ON)
dss |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF)
cam |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF)
core |OFF: 79%|RET: 5%|INA: 0%| ON: 15%| now:(ON)
neon |OFF: 81%|RET: 10%|INA: 7%| ON: 1%| now:(ON)
mpu |OFF: 81%|RET: 10%|INA: 7%| ON: 1%| 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 |
ckgen | CORE | PERI | 96M
| 48M | 12M | 54M
| EMU_CORE |
per | GPIO2 | GPIO3 | GPIO4
| GPIO5 | GPIO6 |

Total wakeups 1235, 41.2/s | IRQ 1076, 35.9/s | Timers 159, 5.3/s
HW wakeups 66, 2.2/s | Real gp_timers expired 98, 3.3/s
cheers.

Re: High Battery Consumption
 

If you enclose copy+paste from terminal, please use CODE-tags, like below:

Re: High Battery Consumption
 

@zimon
i googled for how to code-tag just like you said but got nothing.i copied from terminal and i pasted it to notes in my device and from there posted here.please give an idea.
regards

Re: High Battery Consumption
 

Try the new battery workwd fine ,see the links my thread:
http://www.mugen-power-batteries.com.../view/id/1357/

Re: High Battery Consumption
 

If you click "quote&Reply" on my previous post, you will see how CODE-tags are used. Also if you use [Go Advanced] there is "#"-button which will bring the CODE-start and -end tags.

In your powertop output it shows your CPU is active ("98.4%") almost whole 30s time. So something is running. You could try to see with top or with htop what process is running in the background.

Re: High Battery Consumption
 

@Thank for your kind answer.As of now i have flashed it.using very limited apps like
1.queen beecon
2.f-aircrack
3.pen pen ,conboy
4.vnc viewer
5.auto dis connect,simple brightness app.
Now i have put into re use -smartreflex
since 7.45 pm to 11.45 pm phone lost 4 percent of charging till now.at present happy with that.will see what happens.

Re: High Battery Consumption
 

install battery graph and install 5 or so apps every 2 days or so
in your idle time (sleeping) battery graph shouldnt display many (if any) purple bars if its all good install next lot of apps