Tuner Studio running on Android OS ?

[Carlos]

Hi,
I am absolutely impressed by the features and performance of TS. Phil, thanks for the fantastic work !

It didn't take too long until (even ) I was able to start tuning my MS II.

The more I am using it, the more I am fed up with carrying around my bulky laptop, which meanwhile is a bit worn out by doing so.

So I am looking for a more handy solution, i.e. a tablet device running on Android OS.
I have read several posts having searched for "Android", however I finally didn't understand the status quo of TS on Android as there are many developer specific expressions and discussions. Some related to processors, Linux and what not...I am not a developer, just a dummie user

So simple quiestion is:
Does TS run on a tablet device based on Android OD 2.3 (or 3.0), connecting through micro USB or bluetooth (maybe by using serial to USB, or serial to BT adapter on the MS side)

thanks a lot

C.

PS: If it is not available yet, I would be willing to support the development by some $$$. Maybe a post should be opened up to collect funds for such a development, as I am pretty confident Android, beside MAC OS will remain in the Tablet market.
I know money isn't all, more often time constraints are the issue, but money can help, I guess.

[LT401Vette]

So simple question is:
Does TS run on a tablet device based on Android OD 2.3 (or 3.0), connecting through micro USB or bluetooth (maybe by using serial to USB, or serial to BT adapter on the MS side)

Simple answer: No, TunerStudio will not run on an Android OS tablet.

More detail: While the TunerStudio underlying core components can be leveraged on Android, the entire UI needs to be rewritten. This sort of makes sense too, you would ultimately want the UI to work differently on a smaller touch screen interface.

Current solutions: I actually have 2 Android efforts, that are now finally getting core focus.:
- A Basic Data Logger. This does not use TunerStudio components, it is a new app that communicates with the MS via bluetooth for capturing data logs and provides basic run time read outs. There is no tuning capability in this app and I don't plan to ever put in direct tuning capabilities here as to sensibly do so, you must be able to decipher ini files. This is just about ready for beta testing, I am currently working on server side components and integration with the server. I am shooting for the end of this week, the android side is easily ready, the server side stuff is more work now. After the beta goes out I think I will put a fixed set of gauges on it, that keeps getting too tempting, I just keep stopping myself so I get the beta out first.

- The real Android Tuning App - This app is based on TunerStudio components so it can read and understand TunerStudio Projects and ini files. This app will start with nice dashboards and data logging. The current goal for the dashboard is to be able to use TunerStudio's dashboard designer. But this will keep growing into a full blown tuning app as I build the UI components. I very much want to have the initial versions of this out before spring, to get complete tuning will take some time.

[Carlos]

Phil,
thanks for the clear answers, now I do understand.
Your planned timing works well for me, as I'll take my car off the road next month anyway.
So I'll be patient and wait until spring or so. If you want beta testers... I am definitely interested.
C.

[Nitrobanshee]

Can you tell us what Bluetooth adaptor we need to beta test with, so I can be ready?

[LT401Vette]

I'm still collecting these for testing. But the FireFly fits the bill well.
It has a male plug and powers off pin 9.

Those are 2 points to keep in mind, neither are must have, but are nice.

Also I should mention one I know has been giving me trouble, the IO Gear GBS301, my phone any Pad just don't seem to like connecting to that.

[presurized]

This is just about ready for beta testing, I am currently working on server side components and integration with the server.

I'm ready for that beta testing, Let's have it!!

[LT401Vette]

The android side is pretty much ready for testing, but the holdup has been on the server side. The server does the log transformations and gives easier file access. So I am currently building out a new server and getting the very stripped down site up and running.

[Nitrobanshee]

The android side is pretty much ready for testing, but the holdup has been on the server side. The server does the log transformations and gives easier file access. So I am currently building out a new server and getting the very stripped down site up and running.

You lost me on that one, are the data logs going to your server?

[stevieg]

The android side is pretty much ready for testing, but the holdup has been on the server side. The server does the log transformations and gives easier file access. So I am currently building out a new server and getting the very stripped down site up and running.

You lost me on that one, are the data logs going to your server?

probably a server to download the app through?

steve

[adamnreeves]

I think probably the "Server" Phil is talking about is probably a server thread in the application, the core if you like. The other components will be child threads which do their stuff and communicate to the server thread, etc.

[LT401Vette]

Sorry, that wasn't very explanatory...

This first Android Logger app logs to an FRD format file so it can support all firmwares current and future, even though it does not load TunerStudio Projects.
The trouble with FRD format is that it can not be understood by MegaLogViewer or pretty much anything else that doesn't read ini files with the settings. So what this means is that before you can load the logs into MegaLogViewer they need to be transformed into the regular msl file.

There are ways to do this:
- TunerStudio will transform the FRD files, similar to how it does the MS3 SD logs. Basic FRD format 1.0 translation has been in TunerStudio for years now.
- Server side transformation.

So this Android Logger will let you do either, you can copy the frd files off the device and let TS transform them, or let it automatically upload frd's, then when you log in you can download them to your PC as a standard msl. There are several reasons I want to support the server model also:
- Simplicity. While many people know there phone well and have plenty of utility apps to move the frd's to their PC's, there are plenty of others that would have to figure out how to get the files over and translate them into something viewable.
- Enhancements - The FRD format is quickly changing... Some of the first enhancements are to be able to log GPS and accelerometer data as most phones these days support that. The FRD 1.0 format doesn't. Several other enhancements as simple as Comments in MARK's to say what sort of MARK it was, there is no support for that in FRD 1.0. So that means every time I add a feature to the FRD format, you would have to upgrade TS to the latest beta or alpha to log the new feature. Server side abstracts you from that. I can just add the new feature to the server, then it will be in TS at a later time. If you are using TS transformations only, I will leave the new features as optional preferences so TS can still transform.
- Other upcoming features that I have been looking to get done for the longest time. This new site will really help integrate TS with the Android Apps or even running TS on multiple computers.

[presurized]

This new site will really help integrate TS with the Android Apps or even running TS on multiple computers.

WOW!. That sound Great!! Cant Wait!!

[shadowplane676]

- Enhancements - The FRD format is quickly changing... Some of the first enhancements are to be able to log GPS and accelerometer data as most phones these days support that.

Are you inferring that the logger program would be able to log the accelerometer/GPS data from the phone and include that in the logged data from MS? That'd be pretty darn cool IMO as the vast majority of any androidOS phone these days has the hardware built in for GPS/Accelerometers. Especially if TS can be adapted to pull the location info and map it via Google maps. Possibly even incorporate a lap timer function as well...

[LT401Vette]

Are you inferring that the logger program would be able to log the accelerometer/GPS data from the phone and include that in the logged data from MS?

Yes, exactly that.

[Nitrobanshee]

Phil is the man, I can not wait.

[bubba2533]

Jailbroken iPhone supported? plz

[Black99rt]

Are you inferring that the logger program would be able to log the accelerometer/GPS data from the phone and include that in the logged data from MS?

Yes, exactly that.

This is EXACTLY what I was interested in. Good stuff Phil.

[skipstr]

Hi Guys,
Been lurking here for quite a while now. Very excited about the possibility of using my android phone as a portable dash. Any movement in that direction I've missed?
Thanks to Phil for all the hard work!!!!!

[wicked93gs]

I am also wanting to know if theres any progres made for the full tuning app(dont care about yet another method to datalog except as it pertains to communication via bluetooth, which I understand is critical to getting an android device to communicate with MS). I am reaching the point that carrying around even a netbook is a pain, but I have to do it since I will constantly need to make changes over the next 6 months as things will constantly be changing with my setup. An in dash tablet would simplify things so much...ideally on a cheap android tablet

[LT401Vette]

There were a lot of core foundational components that needed to be built to for this to be driving in the long term direction I have in my head, the data logger uses these and helps to get that going. The web site and services are just about ready for general beta testing use, so I will have the data logger out there quite soon. Then focus can go on getting the tuning components going. That will be incremental as a lot widgets will need to be written. I expect to first have real dashboards, then start getting ways to do general settings and table changes.