This seems like a regression from the last few days. STR on flame with 2.0 07/21/2014 OTA update: Have SIM pin enabled fro both sims. 1st PIN dialog works as expected. 2nd sim dialog starts minimized. I can see the keyboard and the top of the dialog but the input field is hidden.

Hi Arthur, can you check for this one?

QA Wanted for branch checks.

This issue does occur on Flame 2.0. The SIM 2 pin screen is shifted and the box cannot be seen after a restart of the device. I have included a screenshot of this effect. Device: Flame 2.0 BuildID: 20140721082721 Gaia: b9d19011123487009c80d1200937652d58c434a0 Gecko: d69cd84b6824 Version: 32.0a2 (2.0) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 This issue does not occur on the Flame 2.1 and Flame 1.4 builds. The Sim 2 pin screen does not shift. Environmental Variables: Device: Flame Master BuildID: 20140722092900 Gaia: cd50cb6ddeb430ddaf43e4fcf5774b9d262a8cf3 Gecko: e5ced39f443b Version: 34.0a1 (Master) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Environmental Variables: Device: Flame 1.4 BuildID: 20140722122101 Gaia: 5db3d93d68c30c1cf24499b3cda3fd881d207ea6 Gecko: 3dde355c32a1 Version: 30.0 (1.4) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 Buri and OpenC could not be used for branch checks as these devices do not have two SIM slots.

Jayme - you did not set the tracking flags. Please fix that and re-NI me. Also, if this occured in 2.0 but not in 1.4 then it is a regression.

Sorry about that.

I guess Arthur knows this code best.

Aurora Regression Window: Last working Environmental Variables: Device: Flame 2.0 BuildID: 20140718084131 Gaia: dc8e1899f934e648b8de19bbba072ccadd94f8c6 Gecko: 7a18dba0208f Version: 32.0a2 (2.0) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 First Broken Environmental Variables: Device: Flame 2.0 BuildID: 20140718103616 Gaia: 6ccd97a605e7f4ccad2fa92ac9575b35028e07a7 Gecko: c0f00b1268d6 Version: 32.0a2 (2.0) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Last working gaia / First broken gecko - Does not occur Gaia: bd2303de0be9bad0f5a3a1339c5a48c808c90e3a Gecko: c0f00b1268d6 First broken gaia / Last working gekko - Issue DOES occur Gaia: 6ccd97a605e7f4ccad2fa92ac9575b35028e07a7 Gecko: f2b8840032c5 Gaia Pushlog: https://github.com/mozilla-b2g/gaia/compare/bd2303de0be9bad0f5a3a1339c5a48c808c90e3a...6ccd97a605e7f4ccad2fa92ac9575b35028e07a7

Ryan - could this have been broken by bug 980217 ?

Sounds like a question for Wei Gao.

(In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #10) > Sounds like a question for Wei Gao. I am sorry to hear that, I have no phone with firefoxOS master/v2.0, so I can't test it locally. But v1.3t and v1.4 can work normal. Maybe that patch doesn't suit master/v2.0 as system_dialog has been restructured. So could I revert that commit on master/v2.0? I am so sorry again for so much trouble. I will be more careful afterwards. So sorry.

Why don't we let Alive or Julien weigh in first. If a backout is the verdict, both are in timezones that will be able to back this out earlier than I can anyway.

I'm really not the right person here, I merely helped Wei landing the patch :) I have needinfo alive on the regressing bug, he'll be able to help for sure.

This seems related to keyboard window. Alive, any ideas?

Moving component based on comment 14

Please backout if that really occurs. Evelyn, could we have somebody from device team to help this dear contributor to fix it?

(In reply to Alive Kuo [:alive][NEEDINFO!] from comment #17) > Please backout if that really occurs. > Evelyn, could we have somebody from device team to help this dear > contributor to fix it? I think we can just follow contributing way - if the patch Wei Gao provided causes the problem here, please back out it. Thanks.

(In reply to Evelyn Hung [:evelyn] from comment #18) > (In reply to Alive Kuo [:alive][NEEDINFO!] from comment #17) > > Please backout if that really occurs. > > Evelyn, could we have somebody from device team to help this dear > > contributor to fix it? > > I think we can just follow contributing way - if the patch Wei Gao provided > causes the problem here, please back out it. Thanks. Dear Evelyn Firstly, sorry for bringing trouble. As this issue is caused by me, I want to try my best to fix this issue. So, do you mean I should recommit a PR to revert that commit? If so, I am glad to do it right now. Do I understand you correctly or some other things I missed. Thanks.

Tim, can you help to get this resolved?

Let's fix this bug by backing out v2.0 branch patch of bug 980217, and clone a follow-up bug on 2.0 branch for bug 980217. I will talk to Alive offline so everyone have a shared understanding on how to resolve issue like this swiftly.

BTW 2.1 is unaffected based on comment 4.

Fixed by backout bug 980217 on 2.0 branch.