ServiiDroid (Android Console) - Get it on Google Play

[will]

A few more improvements, added the advanced search options (hidden by default), the ICS search view now collapses automatically when in portait mode, and i've added ratings and install count (provided the values aren't 0).

Any thoughts on other info that would be good to display, either with the titles, or in the detailed view?

Phone

device-2012-04-16-192125.png (64.61 KiB) Viewed 41267 times

Tablet

device-2012-04-16-192302.png (39.67 KiB) Viewed 41267 times

[zip]

That's looking sweet. It'd be nice to have a thumbnail there as well, but it'd have to be implemented on the serviidb side.

[moltra]

That's looking sweet. It'd be nice to have a thumbnail there as well, but it'd have to be implemented on the serviidb side.

Yes, it is looking very good. There is already a thumbnail field on serviidb. Nobody has used it so far. I wonder, If I can figure a way to generate the thumbnail automatically.

@Will client is working now, so you can use anything you want for client, I would just like to keep it constant, or if you want to do something with name and rev that is fine to, that wasy you could get some feedback on what versions are in use. ie SD06, SD07 or even further, maybe something that you get from the end user device. rom? manufacture? added to the client string. ieSD06DroidXromICS as long as the 1st part of the string is constant, I will be able to tell the different consoles apart and give the developers up to date information on usage.

[will]

Thanks. Good point I'll add the thumbnail.

@moltra Maybe put a line on the site submit page saying that thumbnails are also for the site/clients, not just for adding to Serviio.

I'll use 'ServiiDroid'.

[moltra]

Thanks. Good point I'll add the thumbnail.

@moltra Maybe put a line on the site submit page saying that thumbnails are also for the site/clients, not just for adding to Serviio.

I'll use 'ServiiDroid'.

Let me know if you want to receive all the data about uses of ServiiDroid. If so I can setup a custom report to be send to you when you want it.

[will]

OK, that could be good, we can do that later once the initial parts are in place. Any eta on the new search options (by plugin, by title and by plugin or title)?

[moltra]

I am actually in the process of writing the new SQL to return all the fields, when I complete it, it will have search fields for Plugin, Title, region.

The way I am setting it up, if the any of the search field is blank it returns all the items for that field.

ie plugin=cbs&title=the&region=us

Would search for plugin contains "cbs" and title contains "the" and region contains "us" or "worldwide"

ie plugin=cbs&&region=us

Would search for plugin contains "cbs" and region contains "us" or "worldwide" and return all titles that match region and plugin.

Is that what you are wanting?

[will]

I am actually in the process of writing the new SQL to return all the fields, when I complete it, it will have search fields for Plugin, Title, region.

The way I am setting it up, if the any of the search field is blank it returns all the items for that field.

ie plugin=cbs&title=the&region=us

Would search for plugin contains "cbs" and title contains "the" and region contains "us" or "worldwide"

ie plugin=cbs&&region=us

Would search for plugin contains "cbs" and region contains "us" or "worldwide" and return all titles that match region and plugin.

Is that what you are wanting?

I want a plugin=XXX and a title=XXX, but I would like to be able to match against either of them e.g. titleOrPlugin=XXX. The reasoning is the user is most likely to want to type in a show name or a plugin name into the box, and if I can do a OR search they should get pretty reasonable results in most cases, but If it is too general they can then restrict the search. But the point is that in most cases, they can just type and find content without thinking about it too much. I might in the future give them a drop down to select plugins, but not right away. First I want some feedback on it, then i'll see what is needed.

How the fields work those, with blank matching everything is the right way to go.

One other thing that would be nice down the road is an icon field for plugins so that the site's logo can be assigned to it. These logos can also be used for templates, and I could cross refrence them when searching for media.

[moltra]

I am actually in the process of writing the new SQL to return all the fields, when I complete it, it will have search fields for Plugin, Title, region.

The way I am setting it up, if the any of the search field is blank it returns all the items for that field.

ie plugin=cbs&title=the&region=us

Would search for plugin contains "cbs" and title contains "the" and region contains "us" or "worldwide"

ie plugin=cbs&&region=us

Would search for plugin contains "cbs" and region contains "us" or "worldwide" and return all titles that match region and plugin.

Is that what you are wanting?

I want a plugin=XXX and a title=XXX, but I would like to be able to match against either of them e.g. titleOrPlugin=XXX. The reasoning is the user is most likely to want to type in a show name or a plugin name into the box, and if I can do a OR search they should get pretty reasonable results in most cases, but If it is too general they can then restrict the search. But the point is that in most cases, they can just type and find content without thinking about it too much. I might in the future give them a drop down to select plugins, but not right away.

How the fields work those, with blank matching everything is the right way to go.

One other thing that would be nice down the road is an icon field for plugins so that the site's logo can be assigned to it. These logos can also be used for templates, and I could cross refrence them when searching for media.

I will add a search parameter called "titleOrPlugin" that will do a wile card search of both the plugin field and the title field.

I will add a thumbnail field for the plugin entry in serviidb tonight or tomorrow.

[will]

OK, thanks. I may need to change the search options in the future, but I want to get some feedback first.

[moltra]

got the search term working, still working on adding more fields. I have the language that the media resources is in added.

Here is the format for the search term.

  Code:

http://serviidb.com/api/media?titleorplugin=csi

[will]

Thanks the works well.

I have some more thoughts which i'll stick in the serviidb.com thread.

[will]

I've uploaded 1.4, the major new feature is ServiiDB.com support. As i said earlier, I won't upload the strings for translation just yet, as I'll probably need to change them around a bit.

  Code:

==== 1.4 ====
*Added (experimental) support for searching and adding online soruces from ServiiDB.com
*Improved new files check scheduling and added #57: Reschedule new files check for when the correct network connection is available
*Added the new Serviio 1.0 info to advanced


See viewtopic.php?f=17&t=5056&start=150#p42661 for full details, but I'm specifically interested in

1) Any layout/sizing issues, Android 3.1 and below tablets, especially medium sized ones will be most likely to be affected.

2) Feedback on the search options

3) Any and all other comments.

Please add lots of content to ServiiDB.com and give give the app a really good test, as always, your feedback can directly affect what goes into the app.

@people who maintain links on the forum, can you start adding them to ServiiDB.com

[zip]

great. I'll write sone News aticle for the homepage/facebook to raise awareness about the DB.

[will]

Thanks.

New update for a rare NPE in the new connection change code. Sorry it took so long, it was a 20 second fix, but I had turned the crash report notification to daily rather than instant as I was generating a load of crashes when working on the UI for ServiiDB.

  Code:

==== 1.4.1 ====
*Fixed rare FC


[will]

Any feedback on the serviidb intergration?

Moltra has just switched on quality and reliability ratings and install counts so those should start appearing now.

He has also put together a list of the top installs http://www.serviidb.com/installs currently a little under 300 sources have been added to serviio using ServiiDroid.

I have a minor update ready that adds saved searches and fixes rotation issues, if there really aren't any layout issues, i'll release that at the weekend.

[will]

I'll be uploading an update to google play in a bit. Major points are saved searches, improved rotating while adding and a few fixes for the odd FC that I saw.

  Code:

==== 1.4.2 ====
*Added #63: [ServiiDB] - Save searches
*Fixed progress dialog dissapearing when rotating while adding an item from ServiiDB to the library
*ServiiDB API update
*Minor improvements and fixes
*Prepared new strings for translation


hanz has already done the updated translation so i've just done another update.

  Code:

==== 1.4.3 ====
*Translation updates
*Fixed typo


Hi, I can't see translation of "view details" (serviidb_item_details_title) although it's translated in GetLocalization (http://www.getlocalization.com/serviidr ... 70/#796931)

My nick is Hans by the way

[will]

Hi, I can't see translation of "view details" (serviidb_item_details_title) although it's translated in GetLocalization (http://www.getlocalization.com/serviidr ... 70/#796931)

My nick is Hans by the way

Sorry, i'm quite dyslexic and easily miss read similar letters.

Your right, I was still using the hardcoded version, that will be fixed in the next release.

Thanks again for always being so quick with doing the translations

[will]

I've uploaded a new update to google play. If you have one of the affected devices, could you try the update and see if the app now works. The problem is caused by the framework.apk only accepting properties that it knew about when it was built, normally they would just be ignored.

I'm also in need of someone with an ICS device who is experiencing a FC after resuming the app to help me fix it as I cannot reproduce it in my emulator.

  Code:

==== 1.4.4 ====
*Added Italian translation - thanks to Gianni
*Added (untested) workaround for the MEIZU M9 and MX