Android/AndroidTV Placeshifter client (Discussion)

[JonL]

Originally Posted by stuckless

I'm not sure exactly what that means, but I suspect no. The Android MiniClient doesn't directly deal with video outputs... thats handled by the Android OS or the Video Players.

Thanks! I had an HD300 that had this feature. It was nice having it outputting 480i/576i for DVD source iso's into my external scaler/deinterlacer.

[smak]

I just wanted to jump in and do a quick intro... I have been using SageTV since 2008. I have been checking in since things went OS and was excited to see the Android Client moving along fairly quickly.

I do not have a lot of time to code but will [hopefully] be contributed on the testing/documentation side of things.

This evening I am planning on installing on my FireTV (second gen) and Samsung S5. I also have a Shield and a first gen FireTV to play with as well.

First question: In reading through the threads it sounds like I can use the Android Client with the v7 server... Correct?

-smak

[stuckless]

Originally Posted by smak

I just wanted to jump in and do a quick intro... I have been using SageTV since 2008. I have been checking in since things went OS and was excited to see the Android Client moving along fairly quickly.

I do not have a lot of time to code but will [hopefully] be contributed on the testing/documentation side of things.

This evening I am planning on installing on my FireTV (second gen) and Samsung S5. I also have a Shield and a first gen FireTV to play with as well.

First question: In reading through the threads it sounds like I can use the Android Client with the v7 server... Correct?

-smak

It should work with V7. Somethings work a little better on V9 (mainly because of small tweaks that I've done on V9 to support things like dumb remotes, etc)

[VCRUser]

Could my problems stem from the fact that my server is v6, not v7? I've been reluctant to make a change in the server since my setup is working overall as-is.

[stuckless]

Originally Posted by VCRUser

Could my problems stem from the fact that my server is v6, not v7? I've been reluctant to make a change in the server since my setup is working overall as-is.

Could be...I can't say for sure. You could just install a v9 version somewhere and test connecting to it and see if you have the same issues.

[nyplayer]

The aspect is off on 480i shows anyway to get them to show up either 4:3 or fill?

[VCRUser]

Originally Posted by stuckless

Could be...I can't say for sure. You could just install a v9 version somewhere and test connecting to it and see if you have the same issues.

Could you point me to a thread/link for that? Will v9 run on XP?

[stuckless]

Originally Posted by VCRUser

Could you point me to a thread/link for that? Will v9 run on XP?

If you browse the open source area, there are 1 or 2 threads on the windows installer. I don't run windows, so, probably be just as easy for you to browse them, than I (My understanding is that there is a working windows installer for SageTV 9)

[mhassman]

Hi!
I'be been following this thread for a while now.. excited at the rapid progress.

I tried a earlier beta, but don't have a Bluetooth keyboard.. so, made it as far as the sagetv login screen. Noticed mention on an on-screen keyboard in newer versions.

Tonight, I removed the beta and installed rc5. The install succeeded, but i'm lacking an icon to start the app (galaxy s5 verizon android 5.0). Android mini client is a listed app, but just can't launch it. I removed rc5 and installed rc4 - same issue. I then removed rc4 and installed beta.5.. icon is back and app runs, just lacking keyboard to login.
Any thoughts on the lack of app icon post install for newer versions?
Thnx!

[KarylFStein]

Originally Posted by mhassman

Hi!
I'be been following this thread for a while now.. excited at the rapid progress.

I tried a earlier beta, but don't have a Bluetooth keyboard.. so, made it as far as the sagetv login screen. Noticed mention on an on-screen keyboard in newer versions.

Tonight, I removed the beta and installed rc5. The install succeeded, but i'm lacking an icon to start the app (galaxy s5 verizon android 5.0). Android mini client is a listed app, but just can't launch it. I removed rc5 and installed rc4 - same issue. I then removed rc4 and installed beta.5.. icon is back and app runs, just lacking keyboard to login.
Any thoughts on the lack of app icon post install for newer versions?
Thnx!

I think after RC2 it's AndroidTV devices only. At least I'm running RC2 on my tablet and phone fine, and RC5 on my SHIELD.

Swipe right (at least on RC2) to bring up a menu where you can launch a software keyboard.

EDIT: Sorry, not saying that this app is going to be AndroidTV only moving on! Just that there's a split due I imagine to different UIs. Stuckless has said that a phone/table update is going to happen too, but just has to split things.

[mhassman]

Thnx for the insight!
I installed rc2 - keyboard worked as anticipated.. though, couldn't get past the login screen.. have filed a bug report.
:-)

[trallyus]

Hey Stuckless,
I just wanted to report that the sagetv-miniclient-1.0.1.apk works great on my Hisense TV now.

I think the problem of it not being able to install in the previous post I made was due to me installing the apk without removing the client data from sage tv first is why it was giving me errors.

No more pixelization or blockiness when watching my shows either. There are some lines when watching old 480 SD recordings like the original Star Trek but I expected that.

Appreciate all the work you have done on it and will definitely keep updating in the future.

By the way , I did have to sideload the apk since the app shows up as incompatible for all my android devices but it was worth it
Trallyus

[stuckless]

Originally Posted by trallyus

By the way , I did have to sideload the apk since the app shows up as incompatible for all my android devices but it was worth it
Trallyus

The Play Store entry is only for Android TV, for now. So, for phones/tablets, you'll have to side load. (I'm assuming the HiSense is a tablet)

[trallyus]

Originally Posted by stuckless

The Play Store entry is only for Android TV, for now. So, for phones/tablets, you'll have to side load. (I'm assuming the HiSense is a tablet)

The Hisense is a sort of Google TV/ Android TV Stuckless

I bought it when Google TV's were just being phased out and they call it an Android tv but it's really a Google TV model made by Hisense as it has the Google TV guide and other apps Google TV's came with.

[stuckless]

Originally Posted by trallyus

The Hisense is a sort of Google TV/ Android TV Stuckless

I bought it when Google TV's were just being phased out and they call it an Android tv but it's really a Google TV model made by Hisense as it has the Google TV guide and other apps Google TV's came with.

got it

[smak]

Wasn't sure if I should start a new thread, but the on-screen remote was discussed several pages back...

I have been playing around with the MiniClient on a ShieldTV. Loving it. However, I am I missing one item on the "remote". The "Info" button. I tend to use that a lot with my config. Using Gemstone, I have the Recordings view grouped by show and setup that "select" opens the media list and "info" opens the options.

Rather than just ask for the feature, I figured I would give it a shot myself. So I tried adding the "info" to the onscreen remote. First time using Andriod studio so there is a learning curve. Still trying to figure out the debeg/logging stuff.

I updated the Navigation.xml file and can see the new icon on the screen.

It appears that the eventlistener in the NavigationFragment is looking at the "tag" attribute on the button which I have set as "_info". If I am reading the code correctly, the "_" should hide the onscreen remote and then pass along the "info" command. In other UserEvent file it appears that the INFO button is mapped.

However, I apparently am missing something. When I select the new icon nothing happens. Can you assist with giving a push in the right direction?

Thanks.

[stuckless]

Originally Posted by smak

Wasn't sure if I should start a new thread, but the on-screen remote was discussed several pages back...

I have been playing around with the MiniClient on a ShieldTV. Loving it. However, I am I missing one item on the "remote". The "Info" button. I tend to use that a lot with my config. Using Gemstone, I have the Recordings view grouped by show and setup that "select" opens the media list and "info" opens the options.

Rather than just ask for the feature, I figured I would give it a shot myself. So I tried adding the "info" to the onscreen remote. First time using Andriod studio so there is a learning curve. Still trying to figure out the debeg/logging stuff.

I updated the Navigation.xml file and can see the new icon on the screen.

It appears that the eventlistener in the NavigationFragment is looking at the "tag" attribute on the button which I have set as "_info". If I am reading the code correctly, the "_" should hide the onscreen remote and then pass along the "info" command. In other UserEvent file it appears that the INFO button is mapped.

However, I apparently am missing something. When I select the new icon nothing happens. Can you assist with giving a push in the right direction?

Thanks.

Glad to see you are trying this out on your own You are right in the tags with leading _ basically means to close the navigation view after the button action is performed.

From what I can tell there may be one other part that you are missing...

In the NavigationFragment.onCreateView() there is a section of code like this...

     for (int id : new int[]{R.id.nav_up, R.id.nav_down, R.id.nav_left, R.id.nav_right, R.id.nav_select, R.id.nav_pgdn, R.id.nav_pgup,
                R.id.nav_options, R.id.nav_home, R.id.nav_media_pause, R.id.nav_media_play, R.id.nav_media_skip_back, R.id.nav_media_skip_back_2,
                R.id.nav_media_skip_forward, R.id.nav_media_skip_forward_2,
                R.id.nav_media_stop, R.id.nav_back}) {
            navView.findViewById(id).setOnClickListener(buttonClickListener);
        }

You will need to add your R.id.nav_xxx id in there (ie, it's the id you have on your button in the xml). This will map an onclick handler to the button.

From everything else you described it sounds like you are doing it right.

[smak]

Originally Posted by stuckless

You will need to add your R.id.nav_xxx id in there (ie, it's the id you have on your button in the xml). This will map an onclick handler to the button.

I should have seen/known that. I have been away from coding for too long. (hangs head)

Thanks for the push I have everything working!

Since it is kind of a one off for me I do not know if you would like a pull request for the change. Let me know if you do [and I will figure out how to do that].

[stuckless]

Originally Posted by smak

I should have seen/known that. I have been away from coding for too long. (hangs head)

Thanks for the push I have everything working!

Since it is kind of a one off for me I do not know if you would like a pull request for the change. Let me know if you do [and I will figure out how to do that].

I don't mind taking a pull request for this... but out of curiousity which icon did you use for the "info"... (was there an existing one, or did you add a new one).

To do a pull request, you would have had to cloned my repo (on github) and done the work in your own repo. Then you can commit the changes back to your repo. Then in github, you can create a pull request for your change.

If you just checked out the code from my repo directly (which you can't commit to), you can still create a patch using git and just send that along.

[smak]

Originally Posted by stuckless

I don't mind taking a pull request for this... but out of curiousity which icon did you use for the "info"... (was there an existing one, or did you add a new one).

I created (errr.. copy/paste/massaged) a new icon... copied the "help" icon and replaced the question mark with an "i".

I will work on getting things pushed back to you.