In CallNotifier.java::onDisconnect(), the incall screen is being
dismissed:
// If the InCallScreen is *not* in the foreground,
forcibly
// dismiss it to make sure it won't still be in the
activity
// history. (But if it *is* in the foreground, don't mess
// with it; it needs to be visible, displaying the "Call
// ended" state.)
if (!mApplication.isShowingCallScreen()) {
if (VDBG) log("onDisconnect: force InCallScreen to
finish()");
mApplication.dismissCallScreen();
}
So, looks like it is intentional but not sure why ??
On Mar 25, 11:29 pm, eternity <[email protected]> wrote:
> I am working on porting Android on a ARM based platform. I observed
> that, when there is call active and after few seconds screen go
> black....if other end disconnects the call, the screen remains black
> and there is no Call Disconnect UI is coming on the screen.
>
> During digging this problem, I found, in JAVA part (packages/apps/
> Phone/src/com/android/phone), the InCallScreen is considered as not a
> forground process and thus they are not showing the Disconnect UI.
> They are not trying to turn the InCallScreen as forground one and
> letting the screen keep black.
>
> I am trying to understand, is this phone package is expecting to turn
> on the backlight from somewhere else (may be from RIL or somewhere
> else).
>
> Or do I need to make changes in Phone packages itself, like calling
> wakeUpScreen() followed by displayCallScreen() in somewhere after
> onDisconnect() gets called???
>
> Any clue on this will be helpful.
>
> TIA
--
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
To unsubscribe from this group, send email to
android-porting+unsubscribegooglegroups.com or reply to this email with the
words "REMOVE ME" as the subject.
