Hi,
You could try taking a bugreport/"dumpsys window", which dumps the
window manager service information.
The z-order listing should be useful to see if the window is actually
added.
Something like below (Where we see that DevelopmentSettings is at the
top).
You can also see the properties of the window token that you are
interested in, in the same output (To see if it is really hidden).
<snip>
:
Application tokens in Z order:
App #4: AppWindowToken{44bd6e30 token=HistoryRecord{44ae2d88
com.android.settings/.DevelopmentSettings}}
App #3: AppWindowToken{44becb90 token=HistoryRecord{44a9bb18
com.android.settings/.ApplicationSettings}}
App #2: AppWindowToken{44becd60 token=HistoryRecord{44beca80
com.android.settings/.Settings}}
App #1: AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28
com.android.launcher/com.android.launcher2.Launcher}}
App #0: AppWindowToken{44afc5a8 token=HistoryRecord{44afab70
com.android.setupwizard/.SetupWizardActivity}}
:
</snip>
I am not too sure about the details of the window drawing though, but
I am sure someone else will be along.
On Dec 20, 5:24 pm, Alonso Hu <chuanshen...@gmail.com> wrote:
> Dear all,
> I've just met a problem these days. When keyguard is started after
> booting, I can't see anything at all. However, incredibly, when I drag
> the unlock button upward (imaging where the position is), I can unlock
> the screen.
>
> I have used the hierarchy viewer to see the view hierarchy, and see
> the correct hierarchy of views of my keyguard view. According to this
> and the correct behavior above, I believe the whole view is running
> but invisible.
> Of course I've checked the properties of the ought-to-be-visible
> objects in the hierarchy viewer and I'm sure they're visible.
>
> I just wonder that how could this be?? Is there any hint that you
> could provide me, please?
>
> On the other side, I'd like to discuss the drawing procedure in
> Android.
>
> I'm tracing the code in windowManagerService and the policy of
> PhoneWindowManager but confused about how it managed the drawing.
>
> 1. How does a view hierarchy draw?
> Is that one view root has a individual surface and each one take the
> responsibility to draw the whole view?
> If it's true. Is that mean the cause of my problem is only a problem
> inside the keyGuardViewManager?
>
> 2. What is the role of windowManagerService in drawing?
>
> Thanks for reading above all. Please provide me any possible hint if
> you have.
>
> Alonso
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
