Comment 1 for bug 1565103

I can't reproduce the live call problem. For me, the bottom edge hint waits until the phone call is over. However, there ARE about 2 seconds after the phone call ends and the hint appears before the live call view switches to the normal dialer view. For those three seconds, the bottom edge of the dialer-app isn't active.

Is that what you're seeing? Or something new?

So the two problems I know about now:
- 2 seconds after received call ends
- dialer and messaging apps with 2 SIMs

For fixing the 2-second problem, I could do a hack like "wait 2 seconds before showing bottom edge for dialer" but that creates more problems. The user can enter the settings screen in those two seconds. Which also doesn't have a bottom edge. That's why the bottom hints come up as soon as you open the app for the first time, it is the only time we know what's on the screen (at least that was the hope).

For fixing the 2-SIM problem, we could probably do a hack that skips the bottom edge completely on those two apps if you have 2 SIMs in. But that also kind of sucks, since those users would probably like the hint too. And it gets into brittle cross-domain assumptions between the app and the shell.

So I guess we very quickly came to the breaking point on the shell being able to fake knowing when to show bottom edge hints.

Long term, we wanted to bring these hints into the apps anyway. That's still the best fix for this. So we can either speed up that plan, or implement some quick-and-dirty communication mechanism between these apps and the shell for when they have an available bottom edge. Maybe as simple as exposing a bool on a DBus interface that the shell can listen to. Just as a stop-gap to moving the screens.

I'll talk with Design about where we are with that plan.