I remember seeing something similar when I was changing the memory
split from 2G/2G to 3G/1G. If you have changed the memory map, it
might be something to take a look at. My init was exiting during
execve, which kinda explains the "Attempted to kill init" message.
On Dec 14, 1:02 am, Deva R wrote
Hi,
You can get the VID/PID in windows too.
http://www.omappedia.org/wiki/Support_Tools#finding_the_Vendor_ID_and_Product_ID_of_the_device
On Dec 13, 2:28 pm, Srinidhi K V wrote:
> Ashwin,
>
> When i do dmesg after connecting the device to host system this is the
> output I got
>
> [ 2914.01641
ix whatever is ailing the USB driver in
> Linux which doesn't allow it to be enumerated. Plugging into a Windows
> machine or another machine just to see if that part is consistent is a
> good thing though..
>
> -- Ashwin
>
>
>
>
>
>
>
> On Mon, Dec 13, 2010
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
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 s
-> Requested w=480 h=249
>
> > 17d16
> > <
> > (our resolution is 480x272)
> > The only difference besides the id difference is the requested width
> > and height. Undoubtedly, the correct one with height 249 is right,
> > where the height of 23 is
was happening at the
time.
-Hemanth
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
