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
At least, it's successfully compiling on a 64-bit machine. Good work
Google!
Hopefully, there will be less pain for a full upgrade compared to
eclair-froyo as the jump doesn't seem to be as high on the backend
side...
Grégoire
On Dec 19, 8:38 pm, G2 grego...@gentil.com wrote:
And no need to
I have created the class which implements the Binder
interface(Service). I am able to send the data to it from client.
If I want to send the asynchronous response back to client, do I need
to implement Binder interface at client as well?
With Regards
Vinayakumara T V
--
unsubscribe:
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
The following patch works for me in order to compile Gingerbread on a
32-bit machine:
--- a/external/clearsilver/java-jni/Android.mk 2010-12-20
09:30:02.379792000 -0800
+++ b/external/clearsilver/java-jni/Android.mk 2010-12-20
02:20:58.871792000 -0800
@@ -34,8 +34,8 @@
LOCAL_CFLAGS += -fPIC
Copy the content into a file named compile-on-32-bit.patch and type:
patch -p1 compile-on-32-bit.patch
Grégoire
On Mon, 2010-12-20 at 11:29 -0800, n179911 wrote:
How can I apply this patch after I check out the source code from android
site?
Thank you.
On Mon, Dec 20, 2010 at 11:01
Did they also start using Java 1.6 or newer for the build as well by
any chance? I already knew about the 64-bit environment change and
thus have been building my Eclair version under that..
Regards
-- Ashwin
On Mon, Dec 20, 2010 at 3:35 AM, G2 grego...@gentil.com wrote:
At least, it's
Yes, 1.6 is needed now,
Grégoire
On Mon, 2010-12-20 at 14:38 -0500, Ashwin Bihari wrote:
Did they also start using Java 1.6 or newer for the build as well by
any chance? I already knew about the 64-bit environment change and
thus have been building my Eclair version under that..
Regards
Gregoire,
That's excellent..thanks for the confirmation..
-- Ashwin
On Mon, Dec 20, 2010 at 2:42 PM, Gregoire Gentil grego...@gentil.com wrote:
Yes, 1.6 is needed now,
Grégoire
On Mon, 2010-12-20 at 14:38 -0500, Ashwin Bihari wrote:
Did they also start using Java 1.6 or newer for the
Thanks for replying.
After I execute dumpsys, it seems that it works normally.
Since the keyguard is not a application at all, I can see the
information in the window information, like below:
Window #6 Window{43e09bd8 Keyguard paused=false}:
mSession=Session{43dd8500 uid 1000}
Hi,
The patch below is nice!
Some additional information.
1. we have to comment out the error statement in main.mk(just added
for the sake of being complete).
build/core/main.mk:80
$(warning
)
-$(error stop)
+#$(error stop)
2. I use a
Hi all,
Reply for my post. For now I don't think it would be caused by any
problem about layout.
I find a workaround, that is to delay the keyguard execution (addview
in windowmanager).
I think it may be like race condition. What I've changed is just to
delay the execution for one second, and
Hi,
It is good that you have a workaround in place!
It is does seem unlikely to be a problem in layout, since it shows up
correctly sometimes.
It could be related to the timing of the layout as you say.
How about using invalidate() on the view after adding?
In
Who can tell me? Thank you very much~
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
14 matches
Mail list logo
