This is a discussion on WTF Tuning Paraphernalia - Android Dashboard Project within the Tuning: Electronic Engine Management forums, part of the Tech & Modifying & General Repairs category; Originally Posted by zax Whatevs. Definitely not getting your cash for last night now....
I figured it out.
Nerd explanation: Git was only downloading the manifest file.. basically a list of files I need to use. Google uses a linux based tool called 'repo' to go through the manifest and download those files. I was looking in my Git directory for the files. Who knew that cygwin (the linux-ish app that I need to run repo) created another directory that has a different root other than the drive itself.
I has mad files. gauge p0rn soon to come.
Maybe old news or maybe not applicable but Parrot looks to be honing in on something interesting here...
Hands-On With Parrot's Latest (And Maybe Greatest) Android-Powered Head Unit | Autopia | Wired.com
No clue on the flexibility like a rooted Android phone/tablet but it is the slickest Android device mounted in a car I have seen yet.
Not as many parts left over this time... what am I missing?
I just want to be able to flash maps and pull learning view. If I'm going to be logging/tuning I would rather have my laptop anyways, but it would be nice to be able to leave the house on an e85 map and not have to worry about bringing my laptop around in case I need to fill up 93.
I've toyed with the idea of working on it myself, but I'm way too busy to start on it right now.
UPDATE: Nothing. Fought with it for a couple hours. The accessory protocol they use is not nearly as simple as they make it seem.
I did get the arduino code to at least compile and upload. It's not being recognized by the tablet though. Need to set up the android bridge to read the log over wifi... Hard to debug with the tablet not plugged into the laptop.
Haven't had much time to work on this project since we recently started working a lot more hours.
Fuel pressure sender
...Will be used along with a few nicely placed 'T's and plugs . Using a resistance based sensor would be a lot easier than a thermocouple starting out. Will get there though.
Got wifi logcat set up - can now view debug information over wifi while the tablet is connected to my controller.
Worked out another bug on the controller.
Progress. I just want to get this thing talking to the tablet already. Always the worst part of a project I feel.
Over a month and all you did was make a light turn on and off??
WTF tuning is an appropriate name
JK glad to see there's progress man!
First Mods: What to do and what not to do
Current Car: 2014 Golf TDI
Previous Cars:2012 WRB WRX Hatch, 2004 RSX-S, 1998 Grand Prix GTP
"Isn't it amazing how smart you feel when you just aren't being stupid?"
Biggest lesson learned: When two open source companies say they are working together... and will make your life easier... DON'T LISTEN.
It looks like google upgraded their framework for jellybean... and didn't even update their own source/example code. WTF?
Got two way communication going. Pretty smooth as well luckily.
Two main issues:
-Only connects when NOT in USB debugging mode (extremely annoying for debug reasons)
-Does not reconnect to the application without closing/destroying the application completely.
Next goal is to work on those two issues and get a fragment based UI done. This should set me up on my way to a more functional program. Included will be the digital I/O application I have done as well as an analog I/O one with a 'gauge' or visual meter of some sort connected to a potentiometer.
Projects in a fun spot right now. I can actually debug my issues and work through stuff as opposed to guess/flash/write/throw something.
this is an old thread, but i'm digging it up because i was literally about to start doing the same thing. well, the same premise at least. any updates with this? or did you just say f it?