ALDLdroid

[Six_Shooter]

Have you tested this on an actual android device (with comms) or just in the dev environment?

I'm supposed to be getting that Android device soon...

[3400tZ]

Have you tested this on an actual android device (with comms) or just in the dev environment?

I'm supposed to be getting that Android device soon...

Come on Chris, have you seen my video and/or screenshots ?

I always test with real devices only, the Android emulator isn't that great, doesn't support Bluetooth for example... not sure about USB. :P

So far I've tested with my tablet (Asus TF300) and phone (HTC One V). Both works great.

[Six_Shooter]

Come on Chris, have you seen my video and/or screenshots ?

I always test with real devices only, the Android emulator isn't that great, doesn't support Bluetooth for example... not sure about USB. :P

So far I've tested with my tablet (Asus TF300) and phone (HTC One V). Both works great.

Yes, I have, the last few looked like a laptop was used for testing... That's why I asked.

[3400tZ]

I think so?

Just opened TunerPro RT and then looked at my Android phone. There's a lot in TP on a PC that won't be needed with TP on an Android, even less on a phone. The entire data log file will have to be able to be saved and emailed. But since you have basically a dashboard you can pick and choose what you want to see and use, I think what needs to be supported is anything in Values or Bitmasks!

History tables aren't going to be much help on a phone... monitors would be to small to find trends or glitches... your making dash boards... have to be able to read codes that are set or switches on or off.

I'm still wondering what I would do with this? It's a cool toy, but for tuning? I'd just need my laptop! That said for personal use I could do a data log without the laptop and email it for later review. The ability to reflect the phone off windsheild as a second dashboard at night is a cool feature.

Now what excites me is the GPS functions, (Latitude, longitude, azimuth, bearing, altitude, accel x/y/z axis)! If this is in same data log then we could probably make history tables, graphs etc... and have a way to time! Like a dyno or 1/4 mile run! That adds a whole new demention to data logs from TP!

One thing I just thought of and thought I'd pass it on in hopes of helping... while comparing TP on my laptop and TP on my phone is your doing all this work on a.... whatever that thing is? A tablet? In all reality all these options and adjustments need to be done on a much smaller scale for the cell phone.

If you want testing done on android phone I have one. Would need to be able to load the $42 ADX. Which brings up another issue... maybe. This ECM is 160 Baud and I think your working with 8192 Baud.

HTH!

I have experience tuning with Android device (on MegaSquirt) so let me give you my opinion on that. I like to use my phone for data logging. Its the smallest thing I have that can data log and get the job done. For data logging, you really don't need more so for that alone, the app is really nice (and you get the extra sensors logged as well which is a cool bonus as you said) For tuning, on a phone, it's a major pain. It's still cool to be able to do little tune tweak (adjusting idle cells of VE table for example) with it but I wouldn't start a full tune using that.

On the other hand, a 10" tablet is pretty much the same size as most netbook. I also have the keyboard dock for my tablet which make it a touch screen netbook pretty much. It's apparently very similar to a laptop as both of you guys seemed a bit confused about it :P That make tuning a lot easier then on a phone and the touch screen and everything else of the Android device make it a great tuning platform. If this app get full tuning capability at some point and you have a 10" tablet, you could end up liking this setup for then you laptop, trust me :)

So already, it has advantages TunerPro doesn't have like logging extra sensors and portability being the two main one IMO but of course it's not a TunerPro competitor, just a great complement.

The 160 baud is indeed an issue. I don't have a 160 baud ECU so I cannot test that and I would assume it doesn't currently work.

Yes, I have, the last few looked like a laptop was used for testing... That's why I asked.

Fair enough, I understand the confusion :P Trust me, it is an Android tablet (running Android 4.2) docked into a keyboard :P

[Six_Shooter]

I also have a '7747 ($42/160 baud) ECM that is set up to be used with my test bench, one of the many ECMs I can bench test. ;)

[3400tZ]

You could test but I'm 99% sure it won't work :/ Does that ECU use the same harness as a '7730 ? Or you have a different test harness for every ECU you have ? :|

[Six_Shooter]

You could test but I'm 99% sure it won't work :/ Does that ECU use the same harness as a '7730 ? Or you have a different test harness for every ECU you have ? :|

I have a different harness made up for each ECM I use, other than ones that can be shared. I.E. the '7730 and '7749 can use the same harness, but they can also use the same codes, so the other reason to switch between them is to test for actual hardware differences, which there are a couple. The '7747 uses a different harness than the '7730, different than the '7165, different than the '7427, different than the '7060...