Ben, I think the heat issue could be tracked under bug 1176544. Gabriele found an issue with the BackgroundHangMonitor. We disabled it in bug 1180533 because it's also affecting flame ( bug 1130725 ). The Aries device is being tracked here : bug 1173140.
I'm concerned that there might be fall outs from bug 1180533, so I asked US/Euro QA to be aware of this and watch out for weird issues from apps that are in the background, esp in automation. I haven't had a chance to reach out to the Taipei team as I just found out about this. I'm also concerned about Pluot Sorbet in terms of battery usage and I will try to be testing to see if this may also be causing some battery drain. I think we're making some progress on the battery drain issue and I hope that we will have a newer dogfood build either late this week or possibly next week some time. Regards, Naoki On Mon, Jul 6, 2015 at 6:06 AM, Benjamin Francis <[email protected]> wrote: > Just wanted to quickly mention that my Z3C foxfooding device has been > getting very hot after about 20 minutes of web browsing, using the > foxfooding build it came flashed with. Hotter than I've ever noticed the > Flame get, though that might be in part due to the materials it's > constructed from. > > Ben > > On 2 July 2015 at 10:22, Jovan Gerodetti <[email protected]> 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 >> [email protected] >> https://lists.mozilla.org/listinfo/dev-b2g >> >> > > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g > >
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
