android-tesla-devel Mailing List for Tesla

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

I wanted to know whether there is any plan to support other linux
distribution. Just tried out Tesla with opensuse host and it fails to log
in.

-- 
-: Parth Buch :-

Hi Rob,

I'll take a look tonight when I get home. I know that some files are
autogenerated by Eclipse and have to be ignored, but those 3 don't
sound right...

Cheers,

Sean

On Wed, Feb 16, 2011 at 12:40 AM, Robert Johnson <sk8...@gm...> wrote:
> Do you have the default.properties file for tesla? Or any other ideas? I am
> having trouble getting the project to run and noticed it was in .gitignore
> as well as
> src/tesla/app/service/business/ICommandController.java
> src/tesla/app/service/business/IErrorHandler.java.
> Thanks,
> Rob
>
> On Thu, Jan 20, 2011 at 9:40 AM, Sean Hodges <sea...@go...>
> wrote:
>>
>> Great, you now have commit access to the project. The clone URL should be:
>>
>> git clone
>> ssh://rjo...@an.../gitroot/android-tesla/android-tesla
>>
>>
>>
>> On Thu, Jan 20, 2011 at 1:55 PM, Robert Johnson <sk8...@gm...>
>> wrote:
>> > My sourceforge account name is rjohnson189.
>> > Thanks,
>> > Rob
>> >
>> > On Thu, Jan 20, 2011 at 5:54 AM, Sean Hodges
>> > <sea...@go...>
>> > wrote:
>> >>
>> >> Hi Robert,
>> >>
>> >> It seems I need a valid Sourceforge account from you to give you
>> >> commit access to the Tesla project...
>> >>
>> >> If you could register with Sourceforge (if you haven't already) and
>> >> give me your username; I'll add you to the project member list so you
>> >> can contribute if/when you get chance. Some fixes to the Banshee
>> >> support would be brilliant, support for that player has been getting
>> >> less attention in Tesla for a while now. No need to let me know when
>> >> you can get involved, just feel free to dig in when you can :)
>> >>
>> >>
>> >> Sean
>> >>
>> >>
>> >> On Tue, Jan 11, 2011 at 12:06 AM, Robert Johnson <sk8...@gm...>
>> >> wrote:
>> >> > I think I may try to fix a bug with retrieving the playlists for
>> >> > banshee
>> >> > (shows current artists songs kind of), also when you choose a song it
>> >> > doesn't play the song chosen. If you get around to setting me up for
>> >> > commit
>> >> > that would be great. Otherwise I can send patches, if I get around
>> >> > messing
>> >> > with it.
>> >> >
>> >> > On Sun, Jan 9, 2011 at 5:53 PM, Sean Hodges
>> >> > <sea...@go...>
>> >> > wrote:
>> >> >>
>> >> >> Robert,
>> >> >>
>> >> >> Sorry for the lack of updates. I've finally applied your patch
>> >> >> upstream and published a new APK. Thanks for your work!
>> >> >>
>> >> >> It took me a little longer than I hoped as I needed to set up an
>> >> >> Ubuntu 10.10 install to test the patch and search around for my APK
>> >> >> signing key, which I hadn't used since Feb last year :)
>> >> >>
>> >> >> If you do decide to do any more work on Tesla, let me know and I can
>> >> >> arrange to give you commit access to the Sourceforge repository.
>> >> >> This
>> >> >> way you'll be able to commit work directly upstream and I can sign a
>> >> >> new release on request much more quickly. Of course if you prefer to
>> >> >> email patches, I'm happy to continue receiving those instead.
>> >> >>
>> >> >>
>> >> >> Thanks,
>> >> >>
>> >> >> Sean
>> >> >>
>> >> >>
>> >> >> On Tue, Jan 4, 2011 at 11:38 PM, Sean Hodges
>> >> >> <sea...@go...> wrote:
>> >> >> > Hi Robert,
>> >> >> >
>> >> >> > Very sorry, I hadn't forgotten I simply haven't had any free time
>> >> >> > to
>> >> >> > spend on it over the holiday.
>> >> >> >
>> >> >> > Thanks for the nudge though! I'm free tomorrow eve so will take a
>> >> >> > look
>> >> >> > at getting it merged in then.
>> >> >> >
>> >> >> >
>> >> >> > Thanks,
>> >> >> >
>> >> >> > Sean
>> >> >> >
>> >> >> >
>> >> >> > On Tue, Jan 4, 2011 at 4:18 AM, Robert Johnson
>> >> >> > <sk8...@gm...>
>> >> >> > wrote:
>> >> >> >> Did you forget, obviously I have the changes on my phone but
>> >> >> >> maybe
>> >> >> >> others
>> >> >> >> would benefit from them.
>> >> >> >>
>> >> >> >> On Dec 15, 2010 2:59 AM, "Sean Hodges"
>> >> >> >> <sea...@go...>
>> >> >> >> wrote:
>> >> >> >>> Robert,
>> >> >> >>>
>> >> >> >>> The patch is definitely welcomed, we've had a few people report
>> >> >> >>> the
>> >> >> >>> issue now but no'one was free to investigate a fix. A cursory
>> >> >> >>> glance
>> >> >> >>> at the patch looks good to me. I'll get it committed and will
>> >> >> >>> arrange
>> >> >> >>> another release in the next couple of days.
>> >> >> >>>
>> >> >> >>>
>> >> >> >>> Thanks,
>> >> >> >>>
>> >> >> >>> Sean
>> >> >> >>>
>> >> >> >>>
>> >> >> >>> On Tue, Dec 14, 2010 at 1:52 AM, Robert Johnson
>> >> >> >>> <sk8...@gm...>
>> >> >> >>> wrote:
>> >> >> >>>> I've created a patch for Tesla to make it work with ubuntu
>> >> >> >>>> 10.10.
>> >> >> >>>> Starting up dbus on ubuntu 10.10, and possibly earlier
>> >> >> >>>> versions,
>> >> >> >>>> appeared
>> >> >> >>>> to
>> >> >> >>>> give a welcome message before success\n as a response.
>> >> >> >>
>> >> >> >
>> >> >
>> >> >
>> >
>> >
>
>

Hello Ettore,

How is your progress with Tesla?

I checked in your change to the DBUS connection script; it will be
included in the next release, so you hopefully won't need your
work-around. Thanks again for your contribution. I'm also working on
various fixes that should improve support for Ubuntu 10.10/11.04.
There were a number of changes to some of the supported players that
are causing communication problems. These will also be in the next
release.

If you are interested, I could send you a beta build to help me test
these changes? Nothing strenuous, just installing the APK on your
phone and letting me know if any issues crop up/persist when trying to
use it.

If you receive errors for only certain media players, it would be very
useful if you could describe what you see, to help when debugging.
Tesla does have a bug tracker here:
http://sourceforge.net/apps/trac/android-tesla/report/1, but emailing
android-tesla-devel list (as you have been already) is just as
welcome, whichever you prefer...

Thanks,

Sean

2011/1/17 Ettore Chimenti <ek5...@gm...>:
> Hi again,
> last night I tried to access my archbox with Tesla... and I developed a
> workaround.
>
> I decided to put the missing variables in .ssh/environment manually, and
> edit /etc/ssh/sshd-config. And it finally WORKS!
>
> Ok, Tesla have now the control of my dbus server, but it crashes with almost
> all the players (with force close or a big error) on my Galaxy S i9000.
>
> Another thing, I installed tracker to query the library... but tesla
> generates no output when querying! Configuration problem?
>
> The only player I used to control pretty good was banshee... But it's a bit
> slow and I get some fc sometimes...
>
> Today I will try another player, like MPD, or songbird.
>
> Keep up!
> -----
> Ek5
> Il giorno 17/gen/2011 09.50, "Sean Hodges" <sea...@go...> ha
> scritto:
>
>>
>> Ettore,
>>
>> Of course, I completely missed your attachment when I replied just then :)
>>
>> The change looks good, I'll give it a test tonight. If you manage to
>> build it yourself then let me know how you get on. If all goes well
>> I'll merge it in for the next release.
>>
>> Thanks,
>>
>> Sean
>>
>>
>>
>> On Mon, Jan 17, 2011 at 8:46 AM, Sean Hodges
>> <sea...@go...> wrote:
>> > Hi Ettore,
>> >
>> > Great to hear you're looking at improving the project! Those session
>> > cookies are set by a shell script in the assets/ directory, see:
>> >
>> >
>> > http://android-tesla.git.sourceforge.net/git/gitweb.cgi?p=android-tesla/android-tesla;a=blob;f=assets/scripts/attach_dbus_session.sh
>> >
>> > You can usually run these scripts directly on your machine in a
>> > terminal to make testing easier; but since we're dealing with an SSH
>> > connection I find it is always worth not assuming anything until the
>> > script has been tested on an Android phone.
>> >
>> > Running Tesla on the Android emulator should work without any problems
>> > (let me know otherwise). If you want to run the APK on your physical
>> > device, you will probably need to uninstall the one you installed from
>> > the Android Market first, since that one is signed with my key. After
>> > this, you should be able to upload it using Eclipse as an "unsigned
>> > application package"... Again let me know if you hit problems!
>> >
>> > Good luck with your changes, if you manage to get something going let
>> > me know and I'll install Arch in a VM to test it and get the code
>> > merged in.
>> >
>> >
>> > Sean
>> >
>> >
>> >
>> > 2011/1/16 Ettore Chimenti <ek5...@gm...>:
>> >> Hi there,
>> >>
>> >> I have downloaded Tesla few days ago, and I liked the project a lot!
>> >>
>> >> Unfortunatly, I have never been able to make it work on my Arch
>> >> Linux...
>> >> The problem is (I wrote on Ubuntu forum twice) that SSH shell doesn't
>> >> keep the same environment of a normal shell and XDG_SESSION_COOKIE and
>> >> DBUS_SESSION_ADDRESS are missing!
>> >>
>> >> I tried to execute attach_dbus_session.sh, but it didn't recognise the
>> >> $XDG_SESSION_COOKIE variable in ssh shell on localhost...
>> >> But if I try to execute it in a normal shell it gives me a beautiful
>> >> "Success!" output.
>> >>
>> >> Inside ~/.dbus/session-bus there is a file called like the
>> >> XDG_SESSION_COOKIE variable (sounds
>> >> like .dbus/session-bus/ee0b0ca6360ee7ef016c7078000007c6-0) and inside
>> >> it
>> >> there are the missing variables DBUS_SESSION_BUS_ADDRESS,
>> >> DBUS_SESSION_BUS_PID and DBUS_SESSION_BUS_WINDOWID.
>> >>
>> >> Now, it's a matter of editing the attach_dbus_session.sh in order to
>> >> read it and re-set the missing variables!!
>> >>
>> >> Thank you for the beautiful project!
>> >>
>> >>
>> >> P.S.: I'm pretty noob at android, so I tried to update the apk, but it
>> >> looks like it must be resigned with some key of yours.
>> >>
>> >> -----
>> >> EK5
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> Protect Your Site and Customers from Malware Attacks
>> >> Learn about various malware tactics and how to avoid them. Understand
>> >> malware threats, the impact they can have on your business, and how you
>> >> can protect your company and customers by using code signing.
>> >> http://p.sf.net/sfu/oracle-sfdevnl
>> >> _______________________________________________
>> >> Android-tesla-devel mailing list
>> >> And...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/android-tesla-devel
>> >>
>> >>
>> >
>
> ------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand
> malware threats, the impact they can have on your business, and how you
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Android-tesla-devel mailing list
> And...@li...
> https://lists.sourceforge.net/lists/listinfo/android-tesla-devel
>
>

Hi again,
last night I tried to access my archbox with Tesla... and I developed a
workaround.

I decided to put the missing variables in .ssh/environment manually, and
edit /etc/ssh/sshd-config. And it finally WORKS!

Ok, Tesla have now the control of my dbus server, but it crashes with almost
all the players (with force close or a big error) on my Galaxy S i9000.

Another thing, I installed tracker to query the library... but tesla
generates no output when querying! Configuration problem?

The only player I used to control pretty good was banshee... But it's a bit
slow and I get some fc sometimes...

Today I will try another player, like MPD, or songbird.

Keep up!
-----
Ek5
Il giorno 17/gen/2011 09.50, "Sean Hodges" <sea...@go...> ha
scritto:
>
> Ettore,
>
> Of course, I completely missed your attachment when I replied just then :)
>
> The change looks good, I'll give it a test tonight. If you manage to
> build it yourself then let me know how you get on. If all goes well
> I'll merge it in for the next release.
>
> Thanks,
>
> Sean
>
>
>
> On Mon, Jan 17, 2011 at 8:46 AM, Sean Hodges
> <sea...@go...> wrote:
> > Hi Ettore,
> >
> > Great to hear you're looking at improving the project! Those session
> > cookies are set by a shell script in the assets/ directory, see:
> >
> >
http://android-tesla.git.sourceforge.net/git/gitweb.cgi?p=android-tesla/android-tesla;a=blob;f=assets/scripts/attach_dbus_session.sh
> >
> > You can usually run these scripts directly on your machine in a
> > terminal to make testing easier; but since we're dealing with an SSH
> > connection I find it is always worth not assuming anything until the
> > script has been tested on an Android phone.
> >
> > Running Tesla on the Android emulator should work without any problems
> > (let me know otherwise). If you want to run the APK on your physical
> > device, you will probably need to uninstall the one you installed from
> > the Android Market first, since that one is signed with my key. After
> > this, you should be able to upload it using Eclipse as an "unsigned
> > application package"... Again let me know if you hit problems!
> >
> > Good luck with your changes, if you manage to get something going let
> > me know and I'll install Arch in a VM to test it and get the code
> > merged in.
> >
> >
> > Sean
> >
> >
> >
> > 2011/1/16 Ettore Chimenti <ek5...@gm...>:
> >> Hi there,
> >>
> >> I have downloaded Tesla few days ago, and I liked the project a lot!
> >>
> >> Unfortunatly, I have never been able to make it work on my Arch
> >> Linux...
> >> The problem is (I wrote on Ubuntu forum twice) that SSH shell doesn't
> >> keep the same environment of a normal shell and XDG_SESSION_COOKIE and
> >> DBUS_SESSION_ADDRESS are missing!
> >>
> >> I tried to execute attach_dbus_session.sh, but it didn't recognise the
> >> $XDG_SESSION_COOKIE variable in ssh shell on localhost...
> >> But if I try to execute it in a normal shell it gives me a beautiful
> >> "Success!" output.
> >>
> >> Inside ~/.dbus/session-bus there is a file called like the
> >> XDG_SESSION_COOKIE variable (sounds
> >> like .dbus/session-bus/ee0b0ca6360ee7ef016c7078000007c6-0) and inside
it
> >> there are the missing variables DBUS_SESSION_BUS_ADDRESS,
> >> DBUS_SESSION_BUS_PID and DBUS_SESSION_BUS_WINDOWID.
> >>
> >> Now, it's a matter of editing the attach_dbus_session.sh in order to
> >> read it and re-set the missing variables!!
> >>
> >> Thank you for the beautiful project!
> >>
> >>
> >> P.S.: I'm pretty noob at android, so I tried to update the apk, but it
> >> looks like it must be resigned with some key of yours.
> >>
> >> -----
> >> EK5
> >>
> >>
------------------------------------------------------------------------------
> >> Protect Your Site and Customers from Malware Attacks
> >> Learn about various malware tactics and how to avoid them. Understand
> >> malware threats, the impact they can have on your business, and how you
> >> can protect your company and customers by using code signing.
> >> http://p.sf.net/sfu/oracle-sfdevnl
> >> _______________________________________________
> >> Android-tesla-devel mailing list
> >> And...@li...
> >> https://lists.sourceforge.net/lists/listinfo/android-tesla-devel
> >>
> >>
> >

Ettore,

Of course, I completely missed your attachment when I replied just then :)

The change looks good, I'll give it a test tonight. If you manage to
build it yourself then let me know how you get on. If all goes well
I'll merge it in for the next release.

Thanks,

Sean

On Mon, Jan 17, 2011 at 8:46 AM, Sean Hodges
<sea...@go...> wrote:
> Hi Ettore,
>
> Great to hear you're looking at improving the project! Those session
> cookies are set by a shell script in the assets/ directory, see:
>
> http://android-tesla.git.sourceforge.net/git/gitweb.cgi?p=android-tesla/android-tesla;a=blob;f=assets/scripts/attach_dbus_session.sh
>
> You can usually run these scripts directly on your machine in a
> terminal to make testing easier; but since we're dealing with an SSH
> connection I find it is always worth not assuming anything until the
> script has been tested on an Android phone.
>
> Running Tesla on the Android emulator should work without any problems
> (let me know otherwise). If you want to run the APK on your physical
> device, you will probably need to uninstall the one you installed from
> the Android Market first, since that one is signed with my key. After
> this, you should be able to upload it using Eclipse as an "unsigned
> application package"... Again let me know if you hit problems!
>
> Good luck with your changes, if you manage to get something going let
> me know and I'll install Arch in a VM to test it and get the code
> merged in.
>
>
> Sean
>
>
>
> 2011/1/16 Ettore Chimenti <ek5...@gm...>:
>> Hi there,
>>
>> I have downloaded Tesla few days ago, and I liked the project a lot!
>>
>> Unfortunatly, I have never been able to make it work on my Arch
>> Linux...
>> The problem is (I wrote on Ubuntu forum twice) that SSH shell doesn't
>> keep the same environment of a normal shell and XDG_SESSION_COOKIE and
>> DBUS_SESSION_ADDRESS are missing!
>>
>> I tried to execute attach_dbus_session.sh, but it didn't recognise the
>> $XDG_SESSION_COOKIE variable in ssh shell on localhost...
>> But if I try to execute it in a normal shell it gives me a beautiful
>> "Success!" output.
>>
>> Inside ~/.dbus/session-bus there is a file called like the
>> XDG_SESSION_COOKIE variable (sounds
>> like .dbus/session-bus/ee0b0ca6360ee7ef016c7078000007c6-0) and inside it
>> there are the missing variables DBUS_SESSION_BUS_ADDRESS,
>> DBUS_SESSION_BUS_PID and DBUS_SESSION_BUS_WINDOWID.
>>
>> Now, it's a matter of editing the attach_dbus_session.sh in order to
>> read it and re-set the missing variables!!
>>
>> Thank you for the beautiful project!
>>
>>
>> P.S.: I'm pretty noob at android, so I tried to update the apk, but it
>> looks like it must be resigned with some key of yours.
>>
>> -----
>> EK5
>>
>> ------------------------------------------------------------------------------
>> Protect Your Site and Customers from Malware Attacks
>> Learn about various malware tactics and how to avoid them. Understand
>> malware threats, the impact they can have on your business, and how you
>> can protect your company and customers by using code signing.
>> http://p.sf.net/sfu/oracle-sfdevnl
>> _______________________________________________
>> Android-tesla-devel mailing list
>> And...@li...
>> https://lists.sourceforge.net/lists/listinfo/android-tesla-devel
>>
>>
>

Hi Ettore,

Great to hear you're looking at improving the project! Those session
cookies are set by a shell script in the assets/ directory, see:

http://android-tesla.git.sourceforge.net/git/gitweb.cgi?p=android-tesla/android-tesla;a=blob;f=assets/scripts/attach_dbus_session.sh

You can usually run these scripts directly on your machine in a
terminal to make testing easier; but since we're dealing with an SSH
connection I find it is always worth not assuming anything until the
script has been tested on an Android phone.

Running Tesla on the Android emulator should work without any problems
(let me know otherwise). If you want to run the APK on your physical
device, you will probably need to uninstall the one you installed from
the Android Market first, since that one is signed with my key. After
this, you should be able to upload it using Eclipse as an "unsigned
application package"... Again let me know if you hit problems!

Good luck with your changes, if you manage to get something going let
me know and I'll install Arch in a VM to test it and get the code
merged in.

Sean

2011/1/16 Ettore Chimenti <ek5...@gm...>:
> Hi there,
>
> I have downloaded Tesla few days ago, and I liked the project a lot!
>
> Unfortunatly, I have never been able to make it work on my Arch
> Linux...
> The problem is (I wrote on Ubuntu forum twice) that SSH shell doesn't
> keep the same environment of a normal shell and XDG_SESSION_COOKIE and
> DBUS_SESSION_ADDRESS are missing!
>
> I tried to execute attach_dbus_session.sh, but it didn't recognise the
> $XDG_SESSION_COOKIE variable in ssh shell on localhost...
> But if I try to execute it in a normal shell it gives me a beautiful
> "Success!" output.
>
> Inside ~/.dbus/session-bus there is a file called like the
> XDG_SESSION_COOKIE variable (sounds
> like .dbus/session-bus/ee0b0ca6360ee7ef016c7078000007c6-0) and inside it
> there are the missing variables DBUS_SESSION_BUS_ADDRESS,
> DBUS_SESSION_BUS_PID and DBUS_SESSION_BUS_WINDOWID.
>
> Now, it's a matter of editing the attach_dbus_session.sh in order to
> read it and re-set the missing variables!!
>
> Thank you for the beautiful project!
>
>
> P.S.: I'm pretty noob at android, so I tried to update the apk, but it
> looks like it must be resigned with some key of yours.
>
> -----
> EK5
>
> ------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand
> malware threats, the impact they can have on your business, and how you
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Android-tesla-devel mailing list
> And...@li...
> https://lists.sourceforge.net/lists/listinfo/android-tesla-devel
>
>

Hi there,

I have downloaded Tesla few days ago, and I liked the project a lot!

Unfortunatly, I have never been able to make it work on my Arch
Linux... 
The problem is (I wrote on Ubuntu forum twice) that SSH shell doesn't
keep the same environment of a normal shell and XDG_SESSION_COOKIE and
DBUS_SESSION_ADDRESS are missing!

I tried to execute attach_dbus_session.sh, but it didn't recognise the
$XDG_SESSION_COOKIE variable in ssh shell on localhost...
But if I try to execute it in a normal shell it gives me a beautiful
"Success!" output.

Inside ~/.dbus/session-bus there is a file called like the
XDG_SESSION_COOKIE variable (sounds
like .dbus/session-bus/ee0b0ca6360ee7ef016c7078000007c6-0) and inside it
there are the missing variables DBUS_SESSION_BUS_ADDRESS,
DBUS_SESSION_BUS_PID and DBUS_SESSION_BUS_WINDOWID.

Now, it's a matter of editing the attach_dbus_session.sh in order to
read it and re-set the missing variables!!

Thank you for the beautiful project!

P.S.: I'm pretty noob at android, so I tried to update the apk, but it
looks like it must be resigned with some key of yours. 

-----
EK5

Robert,

Sorry for the lack of updates. I've finally applied your patch
upstream and published a new APK. Thanks for your work!

It took me a little longer than I hoped as I needed to set up an
Ubuntu 10.10 install to test the patch and search around for my APK
signing key, which I hadn't used since Feb last year :)

If you do decide to do any more work on Tesla, let me know and I can
arrange to give you commit access to the Sourceforge repository. This
way you'll be able to commit work directly upstream and I can sign a
new release on request much more quickly. Of course if you prefer to
email patches, I'm happy to continue receiving those instead.

Thanks,

Sean

On Tue, Jan 4, 2011 at 11:38 PM, Sean Hodges
<sea...@go...> wrote:
> Hi Robert,
>
> Very sorry, I hadn't forgotten I simply haven't had any free time to
> spend on it over the holiday.
>
> Thanks for the nudge though! I'm free tomorrow eve so will take a look
> at getting it merged in then.
>
>
> Thanks,
>
> Sean
>
>
> On Tue, Jan 4, 2011 at 4:18 AM, Robert Johnson <sk8...@gm...> wrote:
>> Did you forget, obviously I have the changes on my phone but maybe others
>> would benefit from them.
>>
>> On Dec 15, 2010 2:59 AM, "Sean Hodges" <sea...@go...> wrote:
>>> Robert,
>>>
>>> The patch is definitely welcomed, we've had a few people report the
>>> issue now but no'one was free to investigate a fix. A cursory glance
>>> at the patch looks good to me. I'll get it committed and will arrange
>>> another release in the next couple of days.
>>>
>>>
>>> Thanks,
>>>
>>> Sean
>>>
>>>
>>> On Tue, Dec 14, 2010 at 1:52 AM, Robert Johnson <sk8...@gm...>
>>> wrote:
>>>> I've created a patch for Tesla to make it work with ubuntu 10.10.
>>>> Starting up dbus on ubuntu 10.10, and possibly earlier versions, appeared
>>>> to
>>>> give a welcome message before success\n as a response.
>>
>

Robert,

The patch is definitely welcomed, we've had a few people report the
issue now but no'one was free to investigate a fix. A cursory glance
at the patch looks good to me. I'll get it committed and will arrange
another release in the next couple of days.

Thanks,

Sean

On Tue, Dec 14, 2010 at 1:52 AM, Robert Johnson <sk8...@gm...> wrote:
> I've created a patch for Tesla to make it work with ubuntu 10.10.
> Starting up dbus on ubuntu 10.10, and possibly earlier versions, appeared to
> give a welcome message before success\n as a response.

Dear Sean,

On Wed, 2010-10-27 at 14:53 +0100, Sean Hodges wrote:
> It sounds like we are not properly checking for a motd message when
> starting the interactive BASH shell (which we need to keep passing
> commands quickly at runtime). I expect the reason it is working for
> your manual test is because you are not invoking an interactive
> session, and that the motd is not being returned to a non-interactive
> one.

ok, I expected something like that.  I guessed that a non-interactive
session is used.  I could not find this in the code. Therefore my test.
But, as you say, my guess was wrong.

FYI: 10.04 had a similar motd, but it worked with Tesla (same version).

> I have a few things to look into for Tesla this weekend. I'll take a
> look and let you know my findings. A quick scout on the Web turns up
> this:
> 
> https://bugs.launchpad.net/ubuntu/+bug/660470
> 
> If you upgraded from 10.04 then this may-or-may-not be the issue.

This is definitely not my problem.  I don't have the two motd's.  Also I
have here two machines, upgraded from 10.04 (worked before) and a
complete fresh set up.  Same problem on both.

> Either way, a temporary solution might be to rename the /etc/motd file
> on your computer to something like "motd_DISABLED", so that it isn't
> dumped to SSH sessions.

This is doing the trick for the moment.  Clear straight forward idea,
I'm becoming old, that I didn't had this thought.

I can send you more information, if you need something to solve the real
problem.  I like the idea to help this great app.

Ciao,
Matthias

Hey Matthias,

Thanks for reporting the issue and looking into it. I'll upgrade one
of my machines to 10.10 and see if I can reproduce what you're seeing.

It sounds like we are not properly checking for a motd message when
starting the interactive BASH shell (which we need to keep passing
commands quickly at runtime). I expect the reason it is working for
your manual test is because you are not invoking an interactive
session, and that the motd is not being returned to a non-interactive
one.

I have a few things to look into for Tesla this weekend. I'll take a
look and let you know my findings. A quick scout on the Web turns up
this:

https://bugs.launchpad.net/ubuntu/+bug/660470

If you upgraded from 10.04 then this may-or-may-not be the issue.
Either way, a temporary solution might be to rename the /etc/motd file
on your computer to something like "motd_DISABLED", so that it isn't
dumped to SSH sessions.

Cheers,

Sean

On Tue, Oct 26, 2010 at 10:17 PM, Matthias GRZESCHIK <s.s...@gm...> wrote:
> Hej Tesla developers,
>
> since upgrading my Ubuntu to the 10.10 version I realized problems
> during the connection.  The mobile (Sony Ericsson XPERIA X10 mini) is
> showing the following message:
>
>> Init script failed with output: Linux shuttle 2.6.35-22-generic
>> #34-Ubuntu SMP Sun Oct 10 09:26:05 UTC 2010 x86_64 GNU/Linux
>> Ubuntu 10.10
>>
>> Welcome to Ubuntu!
>>  * Documentation:  https://help.ubuntu.com/
>>
>> 72 packages can be updated.
>> 22 updates are security updates.
>>
>> Last login: Tue Oct 26 22:30:03 2010 from abulafia.local
>>
>> success
>
> With the same mobile it worked pretty well with the previous Ubuntu
> version.
>
> I was digging a little bit in the Tesla code (version 0.13 from git,
> same version on the mobile) and found, that in CommandServices.java
> (about line 150) a command is sendet and awaits "success" as response.
> As I understand, the sendet command is the script
> attach_dbus_session.sh.  If I call this script by something like:
>
>> ssh 192.168.1.2 "sh attach_dbus_session.sh"
>
> I get only the "success" on the screen.  I have no clue, why the Ubuntu
> messages from a usual interactive login are attached to the response of
> the command.
>
> Do you have any idea, how I could help to pin down the real problem to
> solve it?
>
> Best regards,
> Matthias
>
> PS. I'm not sure, what is the criteria to choose between the devel and
> users list.  Sorry, if it was wrong.
>
>
> ------------------------------------------------------------------------------
> Nokia and AT&T present the 2010 Calling All Innovators-North America contest
> Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
> http://p.sf.net/sfu/nokia-dev2dev
> _______________________________________________
> Android-tesla-devel mailing list
> And...@li...
> https://lists.sourceforge.net/lists/listinfo/android-tesla-devel
>

Hej Tesla developers,

since upgrading my Ubuntu to the 10.10 version I realized problems
during the connection.  The mobile (Sony Ericsson XPERIA X10 mini) is
showing the following message:

> Init script failed with output: Linux shuttle 2.6.35-22-generic
> #34-Ubuntu SMP Sun Oct 10 09:26:05 UTC 2010 x86_64 GNU/Linux
> Ubuntu 10.10
>
> Welcome to Ubuntu!
>  * Documentation:  https://help.ubuntu.com/
> 
> 72 packages can be updated.
> 22 updates are security updates.
> 
> Last login: Tue Oct 26 22:30:03 2010 from abulafia.local
>
> success

With the same mobile it worked pretty well with the previous Ubuntu
version.

I was digging a little bit in the Tesla code (version 0.13 from git,
same version on the mobile) and found, that in CommandServices.java
(about line 150) a command is sendet and awaits "success" as response.
As I understand, the sendet command is the script
attach_dbus_session.sh.  If I call this script by something like:

> ssh 192.168.1.2 "sh attach_dbus_session.sh"

I get only the "success" on the screen.  I have no clue, why the Ubuntu
messages from a usual interactive login are attached to the response of
the command.

Do you have any idea, how I could help to pin down the real problem to
solve it?

Best regards,
Matthias

PS. I'm not sure, what is the criteria to choose between the devel and
users list.  Sorry, if it was wrong.

Hi Rich,

Both Hardy and Lenny need the "libpam-ck-connector" package to be
installed manually before Tesla will work, this package is only
installed by default in Intrepid and above (and Squeeze as well, I
believe). I discovered this just recently, and updated the
installation instructions on the site.

At present, the 0.9 build is the RC for the upcoming stable release,
though I intend to make at least one more point release before next
week. If the package I mentioned does not fix the problem for you,
then I will run some more tests against 8.04 and see if I can
reproduce your issue.

Thanks,

Sean

On Sun, Oct 25, 2009 at 5:21 PM, Rich Jones <ri...@an...> wrote:
> Can you link me to an rc? I've never had it work with 8.04 hardy or debian
> lenny, although I have seen in work with 9.04 jaunty.
>
> R
>
> On Oct 25, 2009 8:23 AM, "Sean Hodges" <sea...@go...> wrote:
>
> OK, so as the subject title suggests, I'm hoping to start thinking
> about a stable release of Tesla in the near future. The app has got to
> the point that the majority of people using it are not getting
> frequent crashes, and all the basic functionality is there (at least
> for players that currently support it).
>
> There's still plenty more to do, such as playlist support for the
> other players, a music/video collection browser, and general
> performance improvements. But I think we might want to draw a line
> under what we have now, and start working on new features under a new
> release series. Additionally, 1.0 has always been the release I have
> intended to put on Google's Android Market (and perhaps Archos' AppLib
> market as well), so for that reason I am keen for it to be stable
> enough to withstand the vigorous user review system on the Android
> Market.
>
> I don't think this project is big enough to do a round of voting, so
> for now I'll treat silence as a "yes". In particular, I'm interested
> if anyone thinks there are any issues that should be escalated
> *before* doing the 1.0 release.
>
> As a target, I'll say that the release is currently planned for
> Saturday next week.
>
>
> Thanks,
>
> Sean
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Android-tesla-devel mailing list
> And...@li...
> https://lists.sourceforge.net/lists/listinfo/android-tesla-devel
>

OK, so as the subject title suggests, I'm hoping to start thinking
about a stable release of Tesla in the near future. The app has got to
the point that the majority of people using it are not getting
frequent crashes, and all the basic functionality is there (at least
for players that currently support it).

There's still plenty more to do, such as playlist support for the
other players, a music/video collection browser, and general
performance improvements. But I think we might want to draw a line
under what we have now, and start working on new features under a new
release series. Additionally, 1.0 has always been the release I have
intended to put on Google's Android Market (and perhaps Archos' AppLib
market as well), so for that reason I am keen for it to be stable
enough to withstand the vigorous user review system on the Android
Market.

I don't think this project is big enough to do a round of voting, so
for now I'll treat silence as a "yes". In particular, I'm interested
if anyone thinks there are any issues that should be escalated
*before* doing the 1.0 release.

As a target, I'll say that the release is currently planned for
Saturday next week.

Thanks,

Sean

On Fri, Oct 16, 2009 at 12:29:18 +0100 (+0100), Sean Hodges wrote:
> Hey Adrian, thanks for your feedback!

Tis nothing compared to the app  :-)

> > a) it would be nice to be able to specify an alternative SSH port
[snip]
> Perhaps we should be checking for a ":" in the host field, and split
> the port number out of there... It could default to 22 when no port
> has been specified.

Heh - I did try that just FYI so it's not a bad idea.

> > b) my .bashrc has "set -o nounset" which causes problems.  perhaps
> > "env|grep.." or somesuch instead?
> 
> The nounset setting should not be an issue if the script succeeds.
> Nonetheless, I'll see if there is some other way we can check for a
> environment variable's existence. "env | grep X" is an option here,
> though I suspect there must be a cleaner way somehow.

Actually that does seem to be a read herring, I thought it was causing
problems with "echo $XDG_SESSION_COOKIE" since that wasn't set.

> > c) there is an 'if [[ "$QUERY_ENVIRON" != "" ]]' line. This is extended
> > test syntax - which aren't actually part of the POSIX standard so some
> > shells don't support them. 'if ! [ "$QUERY_ENVIRON" ]' should work
> > nicely.
> 
> Ah, this is an artifact of the little-to-no testing that Tesla has had
> with non-Bash sessions, I will switch to korn and tcsh and do some
> testing. If you've already done some work on this, a patch would be
> great.

- if [[ "${QUERY_ENVIRON}" != "" ]]; then 
+ if ! [ "${QUERY_ENVIRON}" != "" ]; then 

should do it - the rest looks fine.

> > d) even though I've turned off b) and I'm using bash, it's still
> > failing for me - it dumps the shell script to the screen - the last
> > bit is:
> > ....
> > else echo Could not find dbus session ID in user environment; fi; :-
> > grep:
> 
> I think there are some underlying issues that have not been tested for
> yet. Can you tell me which distro and shell you are using? I'll fire
> up a VM and see if I can reproduce all the issues you've mentioned.

Debian (unstable), bash shell.

> The initialisation script ultimately runs the following command on
> your system: http://pastie.org/657349. Running it manually on the

Ah, that's handy - I was going to go digging and ran out of time. 

The problem was that XDG_SESSION_COOKIE wasn't set.  I thought "how on
Earth can you expect that to be set on a new SSH session?".

It turns out "apt-get install libpam-ck-connector" is the answer :-)

So it's now working (just testing play/pause to Banshee) \o/ 

Thanks ever so much for the quick reply.

Adrian
-- 
bitcube.co.uk - Linux infrastructure consultancy
Puppet, Debian, Red Hat, Ubuntu, CentOS, ...

Hi guys, this looks really nice :-)

I'm hitting a few problems ATM, but they are all really pretty small:

a) it would be nice to be able to specify an alternative SSH port
b) my .bashrc has "set -o nounset" which causes problems.  perhaps
"env|grep.." or somesuch instead?
c) there is an 'if [[ "$QUERY_ENVIRON" != "" ]]' line. This is extended
test syntax - which aren't actually part of the POSIX standard so some
shells don't support them. 'if ! [ "$QUERY_ENVIRON" ]' should work
nicely.
d) even though I've turned off b) and I'm using bash, it's still
failing for me - it dumps the shell script to the screen - the last
bit is:
....
else echo Could not find dbus session ID in user environment; fi; :-
grep:

Thanks,

Adrian
-- 
bitcube.co.uk - Linux infrastructure consultancy
Puppet, Debian, Red Hat, Ubuntu, CentOS, ...

2009/10/14 Peter Baldwin <and...@pe...>:
> Hi,
>   I read about your project and wanted to let you know that you're welcome
> to borrow any code you might find useful from my project at
> http://code.google.com/p/android-vlc-remote/
>   If you need to scan for media servers on a LAN, you might find this
> Activity useful.  If you find a nice way to reliably fetch album art or a
> way to do dvd navigation, please let me know! :)
>
> ~Peter

Hello Peter,

Thanks for getting in touch, I've been aware of your project for some
time now and would be happy to cooperate on features. There are some
neat characteristics in android-vlc-remote that this project has
turned to as a reference already. I'll be sure to check out the server
scanning activity soon, it may prove very useful.

Fetching artwork and DVD navigation are definitely on the high
priority list at the moment, and I'll keep you up to date on progress.
At this point, I've got music artwork collected from Last.fm on the
fly, and it seems to work very reliably. From a cursory glance at your
code, it appears you are getting the artwork from VLC itself. Your
approach would probably provide more accurate matches (as the user may
have organised their music collection), but I guess you might be able
to fall back on the Last.fm API if the artwork is not available on the
local machine.

You can see the main section of my implementation here:
http://github.com/seanhodges/Tesla/blob/master/src/tesla/app/mediainfo/provider/LastfmProvider.java

I also have some code that integrates with flicklib to collect artwork
for videos, but it's incomplete right now. I'll point you to it when
there is something to see.

Cheers,

Sean

Hi,
  I read about your project and wanted to let you know that you're welcome
to borrow any code you might find useful from my project at
http://code.google.com/p/android-vlc-remote/
  If you need to scan for media servers on a LAN, you might find this
Activity<http://code.google.com/p/android-vlc-remote/source/browse/#svn/trunk/src/org/peterbaldwin/client/android/portsweep>useful.
 If you find a nice way to reliably fetch album art or a way to do
dvd navigation, please let me know! :)

~Peter

Hey all,

Anyone who wants to try the new playlist stuff early, I've enabled it
in the source code. If you don't have a dev environment and would like
me to build you a snapshot I'll be more than happy to.

At this stage, I've got the UI activity working, and back-end support
for VLC and Amarok (1 and 2). I'm working on Rhythmbox support at the
moment, which is a little tricky because people don't always deal with
playlists in Rhythmbox - my intention is to display the tracks for the
selected album instead.

Right now, I'm having some difficulty when changing the playing
song/video in both Amarok 2 and VLC (Amarok 1.4 works OK though).
You'll notice that the current implementation steps up or down the
playlist until it finds the entry you selected, rather than setting it
immediately. I've discovered that the MPRIS specification (that these
players comply to) does not provide a means to "set" the entry. So,
I've worked-around it by incrementally calling Next() or Prev()
repeatedly until the playing track ID matches the one that was
selected in Tesla. The result is far from ideal, the process is slow,
and the player plays each track momentarily as it navigates to the
selection, which is why I decided not to include it in the last
release. I'm researching other options, and if anyone has any
suggestions I'll be grateful for the extra help!

Sean

Hello!

Do you guys want Tesla to be on the Market? I have a developer account and
wouldn't mind being the Market maintainer.

Thoughts?

Rich

2009	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep (2)	Oct (6)	Nov	Dec
2010	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct (3)	Nov	Dec (1)
2011	Jan (6)	Feb (1)	Mar	Apr	May (1)	Jun	Jul	Aug	Sep	Oct	Nov	Dec

android-tesla-devel Mailing List for Tesla

android-tesla-devel — Project development list