Hey guys I am a newbie to app development and I have gotten as far as doing the tip calculator. I am trying to make an intervalometer app based on the ti- calculator app at the link below. Basically, it would use the headphone jack to trigger a camera remote shutter release at a predictable rate for time lapse photography on a Canon DSLR. Here is the TI-83 reference. Any idea how to do this on android. Any help or advice is greatly appreciated.
http://potatoeskillme.com/code/ti-86-intervalometer-for-canon-xti/
Dude, I'm really sorry I'm not skilled enough (yet) to help make this happen.
What a fantastic idea! I would love to see this happen.
Anyone have an idea how to access the audio port in code? I have to close the loop on the headphone jack for an instant and then release it.
You are attacking the wrong hole.
Audio jacks don't behave in the same way as the TI data jack.
Investigate using USB.
I would love to see some sort of wireless control of the camera's basic functions, similar to the hardware wireless control modules for those cameras.
Perhaps easier to accomplish and just as nice would be a way to make the camera a wi-fi storage device for those level Canon cameras. It would be sweet to snap shots to the phone for easy posting to the various places Android supports.
My guess would be that Dalvik (SDK level Code) doesn't have access to hardware level controls.
So this would have to have some Native (NDK Code) in c++ written to make it work. I don't think it would be entirely difficult for someone, but I personally have never tried to use an audio jack for anything other than..well...audio.
Kcarpenter said:
My guess would be that Dalvik (SDK level Code) doesn't have access to hardware level controls.
So this would have to have some Native (NDK Code) in c++ written to make it work. I don't think it would be entirely difficult for someone, but I personally have never tried to use an audio jack for anything other than..well...audio.
Click to expand...
Click to collapse
Yeah, that was kinda what I was afraid of. I have really bitten off more than I can chew with this project.
How I understand the wired remote works is that it just "shorts" the connection.
Now you may be able to simulate that by sending tones through the left/right and/or both poles. (one focuses the other shoots)
You could probably test if this would work by playing music through the cable and see if the camera reacts. I don't have a 1/8th to 1/16th cable or else I would try it myself because I am interested if it would work.
Here is a link of how to make a remote switch which you might find handy if you pursue this.
http://martybugs.net/photography/remote.cgi
Someone mentioned using the usb which would open a whole new world of what you can do. If you have ever played around with the canon software then you know you can control all the camera features from a computer and that should be possible to do on our phones but it would be a lot of work to write an app like that.
centran said:
How I understand the wired remote works is that it just "shorts" the connection.
Now you may be able to simulate that by sending tones through the left/right and/or both poles. (one focuses the other shoots)
You could probably test if this would work by playing music through the cable and see if the camera reacts. I don't have a 1/8th to 1/16th cable or else I would try it myself because I am interested if it would work.
Here is a link of how to make a remote switch which you might find handy if you pursue this.
http://martybugs.net/photography/remote.cgi
Someone mentioned using the usb which would open a whole new world of what you can do. If you have ever played around with the canon software then you know you can control all the camera features from a computer and that should be possible to do on our phones but it would be a lot of work to write an app like that.
Click to expand...
Click to collapse
USB is the way to go. I've written a few apps for windows that control canon cameras using the canon sdk. Unfortunately, the SDK is all C++, so a wrapper is needed to work with java. Plus there are functions that are windows specific. The other option for Linux is libgphoto2. Unfortunately, documentation is not the greatest (nor is it for csdk).
If I had more time, I would have coded this already. But all my coding time is spent programming for work.
centran said:
How I understand the wired remote works is that it just "shorts" the connection.
Now you may be able to simulate that by sending tones through the left/right and/or both poles. (one focuses the other shoots)
You could probably test if this would work by playing music through the cable and see if the camera reacts. I don't have a 1/8th to 1/16th cable or else I would try it myself because I am interested if it would work.
Here is a link of how to make a remote switch which you might find handy if you pursue this.
http://martybugs.net/photography/remote.cgi
Someone mentioned using the usb which would open a whole new world of what you can do. If you have ever played around with the canon software then you know you can control all the camera features from a computer and that should be possible to do on our phones but it would be a lot of work to write an app like that.
Click to expand...
Click to collapse
I am going to test your audio idea and see if it shorts the connection. Yeah, I wish I even knew where to begin with working on the USB. I am very new to this. The farthest I have gotten is building a potential layout for the program.
I just looked up some stuff.
I think the canon remote needs a little over 3volts to trigger the shutter. You are not going to be able to get anywhere close to that with the audio output.
I think the only option is to go through the usb.
centran said:
I just looked up some stuff.
I think the canon remote needs a little over 3volts to trigger the shutter. You are not going to be able to get anywhere close to that with the audio output.
I think the only option is to go through the usb.
Click to expand...
Click to collapse
Thank you for the info. I am downloading the Canon SDK right now(not that I have any idea what to do with it at this point).
is this still going? we are about to make the gsm hero usb-host-mode-able, then all that is missing is libgphoto2 and gphoto2... anyone fancy porting it?
First of all, sorry for my English.
I was searching in Google for something like this and I can't find nothing.
Using the usb is not simple, but the audio option is not crazy at all.
Obviously, that option will require some kind of interface, but can be much simple than the USB option.
You can generate different audio frequencies, for example, 1 KHz for focus and 5 KHz for shutter. With a filter for each frequency you can separate the signal in two circuits. Each circuit can trigger the camera with a transistor, in open collector configuration.
Whatever, if you choose one or another (USB or audio) you will must make some kind of electronic interface.
If someone can works with the software, I can do my part with the circuit. I'm sure that will be easy to build for anyone, even if you don't know electronics.
I am also looking into doing this sort of app, but I am starting with a Pentax k110d... Some camera's only require you to short out the wires, and doing so with the audio headphone jack seems to be possible, from the quick little test I just did with a media player, a 3.5mm jack extension cord, and a multimeter. When the track was playing, i got some resistance across the poles, but when I stopped it, I got nothing registering.
I had actually just given up on the headphone jack, and was looking into doing it over USB as well. I might just have to do several code paths, depending on what kind of camera the person is hooking up /ponder
Alrighty, I just did some more testing with a quick framework app that I had been working on for this. There is apparently a constant 1.7 mV on the headphone jack, which is enough to trigger the shutter release on my camera... boo urns... and when the tone is played, the voltage actually drops, because as all learned ppl know(at least those who paid some attention in physics) is that according to Ohms law, Resistance goes up, Voltage goes down.
Any progress on this?
I would love an intervalometer on Android for my Canon EOS 550D
+1 for the development of such app & hardware it may need.
i hate to bust your bubble but this died over a year ago
ya, development has kinda stalled out... I realized that it is not possible to do over the headphone jack, as there is always voltage there, and I don't know if it is possible just over usb...
The only way I can think that this would be possible would be to get ahold of a google hardware kit/arduino dev kit, and then program that.
I have done a lot of searching and have not found what I am looking for. I am looking to put a raspberry Pi in my car and use it as a media center and FM receiver. I have found how to's on making it a media center in the car but not an FM receiver also. Anyone done this? I also want to incorperate some kid of maps for navigation. I want this to be stand alone without my existing radio. I kind of a noob at the pi. I have been using one as an xbmc box in my living room for some time but thats really all.
I have come across this in case anyone else is interested in the same.
http://engineering-diy.blogspot.ro/
I know I'm missing something about AA, but let me ask this newbie question anyway. Oh silly me ..... what is/are the advantages of AA ..... what if users like me are happy with our car sound and video system but just want a Google centric pc and display in the car. You can buy Android mini pc like Minix, Tronsmart and others for around $200 USD or less. 16:9 HD displays with usb touchscreens have dropped in price, so mount one instead of the Garmin type Navi screens.
Yes, for connectivity you do need a wireless technology bridge from LTE to cat5 wired. But really (!), for $500 or less you get great Android system built into your car and you get to operate your sound system seperately. You can mirror or even 'sidesync' between car pc and phablet/phone if you want. Heck, with those smart TV type boxes you can watch all kinds of stuff. With a little thinking, you can connect audio into your existing sound system. You can use any number of ODBII devices to connect to your car's port and run the Torque app on your car Android pc to have all kinds of car diagnostics and live meters. You have almost the entire Google ecosystem available like any other device (almost).
What does Android Auto get you?
I apologize for asking such a seemingly silly question. Why does everything have to become so complicated and expensive?
The promise of Android Auto and its current reality don't quite match up yet but it is very early and I think it is a matter of time.
AA (and CarPlay) is meant to surface the most important functions of your smartphone and provide a more integrated and less distracting way of interacting with those functions. More integrated in terms of working with steering wheel functions (e.g. volume, next/prev, voice command, etc) and current media playback (e.g. pausing or muting existing audio to deliver turn-by-turn instructions). Less distracting in terms of simplified UI with less touching/typing required and more dependence on voice commands. It also eliminates non-essential notifications while driving (I don't need to see the latest Instagram post until I am parked thanks).
I think it also showcases to auto OEMs what is possible with some good design thinking. I own a 2014 VW with the most unintuitive, cumbersome, slow, frustrating navigation you could imagine. An Android Auto head unit that provides an excellent Google Maps nav experience is light years ahead of a system like that.
Dropping in a smartphone Android interface into a dashboard misses much of what AA is meant to deliver. It may be somewhat more integrated but it is no less distracting.
SCKoman said:
I know I'm missing something about AA, but let me ask this newbie question anyway. Oh silly me ..... what is/are the advantages of AA ..... what if users like me are happy with our car sound and video system but just want a Google centric pc and display in the car. You can buy Android mini pc like Minix, Tronsmart and others for around $200 USD or less. 16:9 HD displays with usb touchscreens have dropped in price, so mount one instead of the Garmin type Navi screens.
Yes, for connectivity you do need a wireless technology bridge from LTE to cat5 wired. But really (!), for $500 or less you get great Android system built into your car and you get to operate your sound system seperately. You can mirror or even 'sidesync' between car pc and phablet/phone if you want. Heck, with those smart TV type boxes you can watch all kinds of stuff. With a little thinking, you can connect audio into your existing sound system. You can use any number of ODBII devices to connect to your car's port and run the Torque app on your car Android pc to have all kinds of car diagnostics and live meters. You have almost the entire Google ecosystem available like any other device (almost).
What does Android Auto get you?
I apologize for asking such a seemingly silly question. Why does everything have to become so complicated and expensive?
Click to expand...
Click to collapse
Your "build your own Android mini-PC" idea will seem VERY complicated to "regular people".
Regular people can buy a new car with AA HU installed, and simply plug their stock Android phone in. Or buy an aftermarket HU and have any of thousands of shops install it for you. How may shops will build, configure and install a custom mini-PC ? Mp3car.com MAY do it for $10,000.00 or more I guess... (See their website for custom work.)
Android Auto, after a few years of fixes and new apps supporting it, will hopefully provide a "just works" solution.
Android/computing enthusiasts may prefer to build their own systems and spend many hours tinkering etc. Or they may just want a "just works" solution here too.
Different audiences, different requirements.
Good points .... marketing savvy ... I like.
Hi,
I have a 2015 Audi A3, which unfortunately didn't come with AA as an option (I think it was introduced in 2017). It's a real pain to install the 2017 MMI into an older car, but there are guys out there developing aftermarket Android-based headunits that basically put a whole android "phone" in the dash; which isn't a very eloquent solution and kind of overkill in my opinion. They've got their own SIM cards and you have to change the bluetooth devices the phone is paired to and whatnot. It's really not exactly what I'm looking for. I just want AA and that's it.
Anyway there's one guy who's kind of got what I'm looking for . Unfortunately because the car also didn't come with a touchscreen, I have to toggle through the menus with the knobs and steering wheel buttons, which is meh. I'd love to put a digitizer overlay on the screen and play around with it, maybe have a daughter board made up and inject the screen coordinates into the packets somehow before it's sent down to the phone. I'm more of an EE, don't really have a lot of Android dev experience but I've got a lot of microcontroller and firmware experience. Anyway that's my high level idea of how this might work, not sure if I'm going in the right direction. I did ask the guy at RSNAV (seems to be a one-man show) last night if I might have the source code after signing an NDA and I'm awaiting his response. In the meantime I want to get a plan of action going.
So I'm wondering how AA is integrated on the client-side. Obviously the manufacturer headunits aren't running Android, but they've gotta communicate somehow with the phone. I can't find this info anywhere, I'm guessing this is info Google only shares with Auto manufacturers and the Kentwoods and Pioneers of the world. But maybe I'm wrong. I'm assuming it's a protobuf-based protocol between the headunit and the phone, but I don't know.
Can anybody help me out here? Thanks.
All my android auto head units are running android operating system two Chevy and one Mitsubishi. Main reason why poplar cars get rooted head units and what not. But after market android auto head unit is probably your best choice.
Hi guys, I am new to programming and classic cars. I recently have the chance to buy a 80 model toyota and decided to make a head unit with my old samsung S3. I won't use it to control music or make calls. I just want head unit to show temperature, compass, fuel level etc. By the way, car does not have OBD or ECU, most of the reading would be analogue or through new sensors. Is it possible to attach new sensors to my old phone and read results on the screen? I believe this can be done using a raspberry pi but I am on a tight budget and if I can use what I have at hand for this project it would be really great. I add a sample image of what I have in mind to build. I want it to look genuine and proper for a classic car. Any help is greatly appreciated and I can even offer a test drive with my old beauty if you happen to swing by my vicinity
buy a Bluetooth odb2 adaptor and use the torque pro app.
I simply do not have anything to connect to OBD all the readings regarding the car are old fashion analogue. there is no central command or control.
yeah I forgot about the "classic" part. My bad. Torque will still let you use your phone sensors, so gps speedometer, and gyro based drag timer and hp estimate, but I dont know of anything else you would be able to use. Not that something doesn't exist, I just dont know what it would be.
thank you man I guess I will use the app and look for temperature on my phone.
When did 1980 start being classic, I was thinking pre-70 at least. Which model do you have? I'm trying to remember if the standard DIN size was being used then - I know it was on my mid-70s VW, but that was German, which is where the DIN came from in the first place. Dropping in a 1-DIN android head unit might be easier that rigging up something with your phone.