I think someone was suggesting that it might be something within the lollipop bootloader.
I just tried with android lollipop trying to download the firefox for android on my testing phone for aries and I'm finding that I lost 2 to 3 % battery power in the last hour. On Thu, Jul 2, 2015 at 2:57 PM, Dave Hylands <dhyla...@mozilla.com> wrote: > Actually, it feels like something outside b2g. The numbers posted for b2g > don't seem too out of whack. > > I'm guedsing that something related to the logcats is causing the problem. > > Does trace.sh only show the b2g processes? > > On Thu, Jul 2, 2015 at 7:03 AM, Gabriele Svelto <gsve...@mozilla.com> > wrote: > >> Same issue here, I noticed that the battery drained overnight and the >> phone didn't even have the data connection on (nor wifi enabled). I've >> run my own scripts this morning monitoring the system for 10 minutes and >> the main b2g process woke up ~120 times. So either something landed in >> the system app that causes the system to wake up unnecessarily or it's >> something within Gecko. I'll try to run a bisection if I have enough >> time to. >> >> Gabriele >> >> On 02/07/2015 11:22, Jovan Gerodetti wrote: >> > Hey everyone, >> > >> > Since yesterday I noticed that my new Flame is constantly quite hot and >> > yesterday the battery drained a lot quicker than before. >> > >> > Did anyone else experience similar issues before? >> > >> > I ran the trace.sh script to see which apps use most CPU time >> > >> > NAME PID WAKEUPS RUNTIME NEW >> > b2g 215 1055 1484 ms no >> > (Nuwa) 469 2 68 ms no >> > Homescreen 967 85 21 ms no >> > Loqui IM 1122 156 161 ms no >> > Built-in Keyboa 1141 79 17 ms no >> > Smart Collectio 214 116 28 ms no >> > Find My Device 1454 79 17 ms no >> > Usage 11301 97 31 ms no >> > (Preallocated a 13005 100 940 ms yes >> > >> > and in logcat the same few lines constantly show up >> > E/QCALOG ( 325): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver >> > target [OS-Agent] >> > W/SocketClient( 196): write error (Broken pipe) >> > E/QCALOG ( 325): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown >> > deliver target [OS-Agent] >> > E/QCALOG ( 325): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown >> > deliver target [OS-Agent] >> > W/SocketClient( 196): write error (Broken pipe) >> > E/QCALOG ( 325): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver >> > target [OS-Agent] >> > E/QCALOG ( 325): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown >> > deliver target [OS-Agent] >> > E/QCALOG ( 325): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown >> > deliver target [OS-Agent] >> > W/SocketClient( 196): write error (Broken pipe) >> > W/SocketClient( 196): write error (Broken pipe) >> > E/QCALOG ( 325): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver >> > target [OS-Agent] >> > W/SocketClient( 196): write error (Broken pipe) >> > E/QCALOG ( 325): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown >> > deliver target [OS-Agent] >> > E/QCALOG ( 325): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown >> > deliver target [OS-Agent] >> > W/SocketClient( 196): write error (Broken pipe) >> > >> > I already did a few reboots but the issue persists. >> > >> > >> > Regards, >> > Jovan >> > >> > >> > _______________________________________________ >> > dev-b2g mailing list >> > dev-b2g@lists.mozilla.org >> > https://lists.mozilla.org/listinfo/dev-b2g >> > >> >> >> >> _______________________________________________ >> dev-b2g mailing list >> dev-b2g@lists.mozilla.org >> https://lists.mozilla.org/listinfo/dev-b2g >> >> > > _______________________________________________ > dev-b2g mailing list > dev-b2g@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-b2g > >
_______________________________________________ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
