Dear Colin, I replicated your steps and now the screen of the emulator
appears on my Galaxy phone. However it is super laggy and I can't get past
the Home/Lock screen.
Did you manage to pass that? The guys on Google's I/O made it look so
smoothly.
I see my fingers/touch inputs go through, they lag and take a while and I
can't go passed the screen :/
On Monday, March 25, 2013 at 8:18:17 PM UTC-7, colin wrote:
>
> Yes. I built my own copy of the SdkController app and managed to track
> down the bug.
>
> The problem was (and presumably still is) that a string in the protocol
> being sent from the emulator to the app was being corrupted with four
> leading zero bytes. I didn't investigate the emulator code, but my
> assumption is that a struct-padding issue somewhere means that an extra
> word is being inserted into the stream of data when the emulator is
> compiled for MS Windows, but not for the Mac. (So the proper solution would
> be to track down where this is happening and process the relevant fields
> individually, rather than take the containing struct as a whole.)
>
> But for my purposes, I came up with a hack in the app file
> Connection.java. The string being corrupted is the channel name, causing
> the method getChannel() to return null -
>
>
>
> *public* Channel getChannel(String name){
>
> * for* (Channel channel : mChannels) {
>
> * if* (channel.getChannelName().equals(name)) {
>
> * return* channel;
>
> }
>
> }
>
> return null;
>
> }
>
>
>
> So I added a couple of lines within the above for loop to do wildcard
> matches on the only two channels that currently exist (sensor and
> multitouch) -
>
>
>
> *if* (channel.getChannelName().matches(".*sen.*")&& name.matches(".*sen.*")
> ) {
>
> *return* channel;
>
> }
>
> *if* (channel.getChannelName().matches(".*multi.*")&& name.matches(
> ".*multi.*") ) {
>
> *return* channel;
>
> }
>
>
>
> Ugly, but it got things working.
>
> To be honest, I didn't then do much with it, so I don't know if there are
> other issues. The fact that something so fundamental went unnoticed
> suggests there may well be.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Saturday, 23 March 2013 12:22:36 UTC, Sebioff wrote:
>
>> Did you get it working in the meantime? This would be such an awesome
>> tool, but I can't get it working either and not many people seem to know
>> that this even exists, so it's hard to find help...
>>
>> Am Mittwoch, 14. November 2012 00:24:38 UTC+1 schrieb colin:
>>
>>> Hi,
>>>
>>> Has anybody been able to get the SdkController app to work with the
>>> emulator? I found an old thread about this and tried to revive it, but I
>>> don't think I will be getting a reply there -
>>> https://groups.google.com/d/topic/adt-dev/TyZiFZ_Ns5Y/discussion.
>>>
>>> Given the video of it working on a Mac from Google IO
>>> <http://androiddevelopment.info/google-io-2012-whats-new-in-android-developers-tools/>,
>>>
>>> I'm wondering if there is a problem with the Windows version of the
>>> emulator.
>>>
>>>
>>
--
You received this message because you are subscribed to the Google Groups
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/android-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/android-developers/c8512e36-4aa3-4ddd-8aff-9084535048f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
