The OP said he JUST got his device a month ago in his top post. It's not clear if it's a second hand device or not, but the fact that there are multiple programs installed that he apparently doesn't recognize would indicate it's probably a second-hand device. Given that, I simply stated it would be far easier to backup what little content he's personally put on it in the past month, and re-flash it, rather than try to diagnose and undo what someone else did to it before he owned it! That's not chafe, it's common sense. As I already noted, there's a lot of IRQ and dss activity going on, which indicate a bad setting or possibly faulty hardware. (Kudos to Andrew_b: Yes, it could be an external component, like bad wifi point, or a bluetooth device like I mentioned earlier.) I put in the post above alternate things to check for or try if he's trying to avoid doing a reflash. At no point did I say "the ops o(sic) recourse is a complete reflash". Please don't put words in my mouth, saying I said something when clearly I said no such thing. (That's called lying in my country...) Sad that you find the need to be-little my comments to cover for your suggesting useless "fixes" like telling someone that uninstalling a tutorial video or a non-active app installer will help with their battery usage.
Powertop 1.13.3 Sleeping for 11 seconds before sampling Collecting data for 30 seconds Sample interval was 00m 30s 16449us C# | Ratio | Avg/dura | Frequency | Ratio --------+--------+----------+-----------+--------+ C0 | 1.6% | | 1150 MHz | nan% | C1 | 0.0% | 0.2ms | C2 | 0.7% | 3.2ms | C3 | 23.8% | 35.7ms | C4 | 73.9% | 96.9ms | IRQ# | Activity | Type | Name --------+------------+----------------+--------------------------- 12 | 2098 | INTC | DMA 11 | 347 | INTC | prcm 202 | 297 | GPIO | wl1251 56 | 125 | INTC | i2c_omap 37 | 70 | INTC | gp 57 | 58 | INTC | i2c_omap PID# | Activity | Name | Function Entry (Expire) --------+------------+----------------+--------------------------- 38 | 40D| awk | cpufreq_governor_dbs (delayed_work_timer_fn) 0 | 38 | <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer) 705 | 14 | bme_RX-51 | sys_timer_settime (posix_timer_fn) 0 | 11 | <kernel core> | hrtimer_start (tick_sched_timer) 705 | 6 | bme_RX-51 | schedule_timeout (process_timeout) 784 | 4 | mce | tsc2005_start_scan (tsc2005_esd_timer_handler) 0 | 3 | <kernel core> | queue_delayed_work (delayed_work_timer_fn) 10 | 3 | omap2_mcspi | neigh_add_timer (neigh_timer_handler) 705 | 3 | bme_RX-51 | sys_timer_settime (posix_timer_fn) 701 | 2D|<kernel module> | queue_delayed_work (delayed_work_timer_fn) 667 | 2 | dsme | do_nanosleep (hrtimer_wakeup) 667 | 2 | dsme | __enqueue_rt_entity (sched_rt_period_timer) 705 | 2 | bme_RX-51 | do_nanosleep (hrtimer_wakeup) 1344 | 1 | eapd | fib6_force_start_gc (fib6_gc_timer_cb) 1 | 1D| <kernel core> | queue_delayed_work (delayed_work_timer_fn) 1826 | 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: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF) per |OFF: 97%|RET: 0%|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: 73%|RET: 23%|INA: 0%| ON: 1%| now:(ON) neon |OFF: 73%|RET: 23%|INA: 0%| ON: 1%| now:(ON) mpu |OFF: 73%|RET: 23%|INA: 0%| 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 | ckgen | CORE | PERI | 96M | 48M | 12M | 54M | EMU_CORE | per | GPIO2 | GPIO3 | GPIO4 | GPIO5 | GPIO6 | Total wakeups 3128, 104.3/s | IRQ 2995, 99.8/s | Timers 133, 4.4/s HW wakeups 91, 3.0/s | Real gp_timers expired 70, 2.3/s