Yikes. [ 241.564712] Killing 'b2g' (229), adj 0, B2G basically got killed and restarted, which explains the black out and the SIM coming back.
There's definitely a bug going on here; we need to narrow down these steps so that we have constant reproducible actionable items. Currently just saying 2 days twitter, when there's a lot more stuff going on is going to be hard to reproduce for anyone including the devs working on the issue. On Thu, Jan 21, 2016 at 9:27 AM, Naoki Hirata <[email protected]> wrote: > If you delete the app then the problem seems to go away; it sounds more or > less like a caching issue and/or possible memory leak somewhere ( maybe > even in the app). > > Seems like you're also getting data through your sim instead of wifi; > otherwise it shouldn't ask for your sim upon returning from the screen. > Screen going black sounds like the screen timeout hit. We should look > through the logs to see if that was the case. > > Regardless, we probably need to run a test with twitter scrolling through > several days to see if we can reproduce the issue with several days up time. > > On Thu, Jan 21, 2016 at 9:19 AM, Mihai Barbat <[email protected]> wrote: > >> Hi Kevin >> >> The issue gets worse as you keep using Twitter and it was fixed when I >> deleted the app and reinstalled it again. But in 2 days of using it >> normally it came back at the point where when I start it the whole screen >> gets black for more than 1 minute than somehow the screen recovers and it's >> asking me to input my sim code again! then all the icons are repainted and >> the homescreen appears. >> >> I updated the bug with new logs >> >> On Wed, Jan 20, 2016 at 10:21 PM, Kevin Tucker <[email protected]> >> wrote: >> >>> Hello Mihai, >>> >>> We are unable to reproduce this issue so far but we are investigating >>> this further to be sure. >>> >>> Thanks! >>> >>> On Tue, Jan 19, 2016 at 9:02 AM, Mihai Barbat <[email protected]> wrote: >>> >>>> Hi all >>>> >>>> Can you please try to run the Twitter app or access twitter.com? I get >>>> a completely black screen and I think only the Flames with V5 are affected! >>>> >>>> Btw, I am running OTA 20160119030400 >>>> >>>> Here is the bug https://bugzilla.mozilla.org/show_bug.cgi?id=1240347 >>>> >>>> Regards, >>>> Mihai >>>> >>>> _______________________________________________ >>>> dev-fxos mailing list >>>> [email protected] >>>> https://lists.mozilla.org/listinfo/dev-fxos >>>> >>>> >>> >> >> _______________________________________________ >> dev-fxos mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-fxos >> >> >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
