Closed GoogleCodeExporter closed 9 years ago
The first obvious error is that the last 5 params above should have been a
single param.
Original comment by rdamazio@gmail.com
on 19 Oct 2010 at 6:25
Note that exactly the 5th param is being passed as:
'{description}'
And that translates to:
'"NOT charging, remaining charge: 84% "'
But Windows is passing to my program only:
'"NOT charging, remaining charge: 84%
That's why it's not a single param. Everything after that last character is
being cut off, and so the quotes have no effect. Initially I wasn't using any
quotes since the notifier already adds the double quotes. I then tried escaping
it with single quotes around it to debug it, but then I realized what was
really going on.
I'm not familiar with the notifier source, but I bet that garbage character,
that appears as blank on the logs, is the culprit of the problem.
I just tested without encryption on, and it is still not working.
Original comment by djbr...@gmail.com
on 19 Oct 2010 at 6:34
Yeah, there is a garbage character in the "description" field, I've noticed it
while implementing USB communication and fixed it already, did not file an
issue though. As you've said, the program already puts parameters in double
quotes so you don't have to. A simple bat file with "echo %1 - %2 - %3 - %4 -
%5 - %6" should print all parameters correctly.
Here is an exe file with the fix:
http://dl.dropbox.com/u/1401233/248/android-notifier-desktop.exe
Thank you for posting a detailed report :)
Original comment by lehph...@gmail.com
on 19 Oct 2010 at 7:15
Issue 254 has been merged into this issue.
Original comment by lehph...@gmail.com
on 22 Oct 2010 at 7:30
Sorry for the delay, I didn't get updates from the issue on my email for some
reason.
I just tried the exe you supplied, and it seems the garbage character is gone.
I'll try it on Linux later, but you can already mark this issue as closed I
think.
Original comment by djbr...@gmail.com
on 16 Nov 2010 at 2:11
Great.
Original comment by lehph...@gmail.com
on 16 Nov 2010 at 2:14
Original issue reported on code.google.com by
djbr...@gmail.com
on 19 Oct 2010 at 6:06