Related
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.
Hi Guys....
I change my HTC Kaiser TYTN II to Android from Winmo rom cooked by shifu
suvil.com/products_freeaudiobt_en.html#product/gallery/free_audio_bt_2.jpg
My Bluetooth headset Suvil works fine to WinMO
Hard SPL 3.29
Radio 1.70.19.09
WinMO rom By shifu
Then i tried Android rom
Not so super froyo by kyle
fresh froyo by dark prince
I cant make my bluetooth headset media buttons to work
I tried to update the:
Hard SPL
3.34
3.56
Radio
1.71.09.01
1.65.21.18 downgrade
Kernels
L1q1d .32/.25
dzo .25
myns .32
still no luck! Cannot use the play/pause rewind/forward button functions
if i click the play/pause twice , it calls the last person on my log
Please help me Masters. TIA!
Thanks for letting me know that. Cheers!
Maybe we can figure it out. It has always bothered me a bit, but never enough to look into the problem. I know that it works fine on some other Android phones. We need to poke around and see if there is any debugging output that can be enabled for Bluetooth. We have all the source code, but sometimes it is like looking for a needle in a haystack.
If I recall, the build you mentioned was based on Fresh Froyo, so that's the source code to look at. Also, Scooter1556 made a CyanogenMod buiid of Gingerbread from different sources, and I haven't tried that very much. Can anyone report whether bluetooth controls work there?
I have to confess that I've been using my Tilt2 (HTC Rhodium) recently, with xdandroid. It is very similar to Fresh Froyo, but faster because the device has more memory. The larger screen helps too. But the battery meter is poor like ours was a year ago, so I have a little work ahead of me on that device. Yet I haven't abandoned the Kaiser completely. No promises, but I'll poke around and see if I can figure out how the bluetooth pause, play, next, previous, and volume buttons work in WinMo and why they don't do anything in our Android builds.
BTW: I don't know about the radio, but the best kernel so far is the Scooter1556 kernel with separated cache, especially for NAND installs.
n2rjt said:
Maybe we can figure it out. It has always bothered me a bit, but never enough to look into the problem. I know that it works fine on some other Android phones. We need to poke around and see if there is any debugging output that can be enabled for Bluetooth. We have all the source code, but sometimes it is like looking for a needle in a haystack.
If I recall, the build you mentioned was based on Fresh Froyo, so that's the source code to look at. Also, Scooter1556 made a CyanogenMod buiid of Gingerbread from different sources, and I haven't tried that very much. Can anyone report whether bluetooth controls work there?
I have to confess that I've been using my Tilt2 (HTC Rhodium) recently, with xdandroid. It is very similar to Fresh Froyo, but faster because the device has more memory. The larger screen helps too. But the battery meter is poor like ours was a year ago, so I have a little work ahead of me on that device. Yet I haven't abandoned the Kaiser completely. No promises, but I'll poke around and see if I can figure out how the bluetooth pause, play, next, previous, and volume buttons work in WinMo and why they don't do anything in our Android builds.
BTW: I don't know about the radio, but the best kernel so far is the Scooter1556 kernel with separated cache, especially for NAND installs.
Click to expand...
Click to collapse
As a diamond user, i hope you can fix the whole pack... Rhodium, Fuse, Diamond, and Topaz
n2rjt said:
Maybe we can figure it out. It has always bothered me a bit, but never enough to look into the problem. I know that it works fine on some other Android phones. We need to poke around and see if there is any debugging output that can be enabled for Bluetooth. We have all the source code, but sometimes it is like looking for a needle in a haystack.
If I recall, the build you mentioned was based on Fresh Froyo, so that's the source code to look at. Also, Scooter1556 made a CyanogenMod buiid of Gingerbread from different sources, and I haven't tried that very much. Can anyone report whether bluetooth controls work there?
I have to confess that I've been using my Tilt2 (HTC Rhodium) recently, with xdandroid. It is very similar to Fresh Froyo, but faster because the device has more memory. The larger screen helps too. But the battery meter is poor like ours was a year ago, so I have a little work ahead of me on that device. Yet I haven't abandoned the Kaiser completely. No promises, but I'll poke around and see if I can figure out how the bluetooth pause, play, next, previous, and volume buttons work in WinMo and why they don't do anything in our Android builds.
BTW: I don't know about the radio, but the best kernel so far is the Scooter1556 kernel with separated cache, especially for NAND installs.
Click to expand...
Click to collapse
OMG!!! Some Masters did reply to my post!...Hope im not too late for this!
I have a friend who is using Samsung I5510 built with Froyo 2.2.2
and media buttons on my headset works fine
Well the problem is dont know how to extract the driver or configuration of that ROM and install it to my kaiser. (i dont know as well if android works that way)
Just the forward/next Play/Pause buttons are not working, never mind the Volume control as Bluetooth headset has its own controller
Hope this helps and thanks in advance!!!
If you look here:
https://opensource.samsung.com/index.jsp
you can see that samsung released its I9000 ginger kernel and platform.
However I keep reading in many places that samsung didn't release all the I9000 drivers.
Therefore I have a couple of questions
Which drivers have been released by samsung (phone, bluetooth, screen, camera, ...)?
Which drivers have not been released (grapich hardware acceleration, camera, phone, ....)?
Since I have been using CM7, I have wondered if at least the phone, bluetooth and all the radio stuffs work as a stock rom. In other word if the phone and BT work for some exploits or if they work exactly as a stock rom because they use an official driver.
I'm asking that because I don't like the thought of my brain unecessary burned with too much EM power just because the phone and BT part work for some fancy exploit.
The same things for 3G and all radio stuff.
I do not care if the video acceleration or other non radio stuff are an hack and do not rely on official drivers.
Can anyone clarify the situation?
Hi All,
Hopefully in the right section as I didn't want to add more threads to the dev section but feel free to tell me to move to there is this is the wrong place....
I have an in car dock for my phone and for some time now it hasn't worked with the CM builds. SGSIII users were also facing the same problem up until November last year when they got the relevant patches merged into the CM nightlies to re-enable it for their phones.
I was hoping that the CM team for the N7000 would be kind enough to add it into their to-do list? It's the only thing that is missing from CM10.1 for me and I am sure there must be others out there that would love to have this back in the rom.
thanks!
From the discussion thread....
http://forum.xda-developers.com/showthread.php?p=38900841
Entropy512's statement:
"Needs audio HAL work. I provided the instructions for getting the path data in a few places, don't remember exactly where. I haven't had much time lately, even less motivation to mess with Haxxinos4 devices.
Apply http://review.cyanogenmod.org/#/c/19294/ to a kernel running with the old blob HAL, connect to dock audio, grab the path data from dmesg.
Then add it to our audio HAL. I MIGHT be able to do it with just a dmesg from above - that's the time consuming part I haven't had any chance to mess with."
Quite an impressive coincidence isn't it?! I have nothing to do with this, I promise!
AA1973 said:
From the discussion thread....
http://forum.xda-developers.com/showthread.php?p=38900841
Entropy512's statement:
"Needs audio HAL work. I provided the instructions for getting the path data in a few places, don't remember exactly where. I haven't had much time lately, even less motivation to mess with Haxxinos4 devices.
Apply http://review.cyanogenmod.org/#/c/19294/ to a kernel running with the old blob HAL, connect to dock audio, grab the path data from dmesg.
Then add it to our audio HAL. I MIGHT be able to do it with just a dmesg from above - that's the time consuming part I haven't had any chance to mess with."
Click to expand...
Click to collapse
I'm interested in digging this out. Anyone know what Entropy512 means by blob HAL?
apparently, he's talking about some binary module for audio HAL (wikipedia: binary blob)
i was hoping it had to do with some aosp module (libstagefright or so)
nonetheless, would be great if someone with experience could provide pointers.
apparently, this has already been implemented for the nexus 7 through CM10.1
http://forum.xda-developers.com/showthread.php?p=40079493&highlight=audio#post40079493
need to look in to effort to move this over to the Note
Hi...
Not having USB audio implemented in the latest CM versions is really my only problem with stepping up from 4.0.4 (CM 9.1).
So please, if anyone can spare the time to take a look at this, i'd be eternally thankful...!
...ongoing
FYI...:
There is an Cyanogen issue for this. Unfortunately i'm not yet allowed to post links...
But check out jira on the cyanogenmod site and look for dock audio...status is unresolved.
Dmesg/logcat from CM9 patched dock insertion
AA1973 said:
From the discussion thread....
http://forum.xda-developers.com/showthread.php?p=38900841
Entropy512's statement:
"Needs audio HAL work. I provided the instructions for getting the path data in a few places, don't remember exactly where. I haven't had much time lately, even less motivation to mess with Haxxinos4 devices.
Apply http://review.cyanogenmod.org/#/c/19294/ to a kernel running with the old blob HAL, connect to dock audio, grab the path data from dmesg.
Then add it to our audio HAL. I MIGHT be able to do it with just a dmesg from above - that's the time consuming part I haven't had any chance to mess with."
Click to expand...
Click to collapse
I followed your instructions and have attached a dmesg/logcat from the time related to the insertion/removal of the dock. I attempted to use apollo to output some music but it repeatedly crashed, I changed the volume level several times instead as the volume change tone outputs via the dock audio. Hopefully you will have time to have a look and see whether it would be possible to apply the necessary changes to CM10.1
Thanks
Links onTopic
Here are two interesting links for the whole usb audio topic for android. I thought this may save some people looking for it..:
Cyanogen Mod issue
Google Issue
The Google issue has lately been closed for commenting, but as several issues have been mergred into it, my hopes are high that implementation is at least being looked into right now.
I've finally given up on the in-car USB-dock solution. So i've switched to bluetooth audio. This step made very clear to me, that the audio quality from USB was even more horrible than i thought (compared to BT). Can anyone comprehensively explain to me what kind of signal "comes out" of the USB?
Sorry if this question has been asked before but I did some searching and was unable to find a straight answer anywhere and my question is a bit different.
Is there any hope for getting the Sixaxis PS3 Controller app working properly on any of the Android builds for the Touchpad. CM9 is the only thing it worked on as far as I can tell.
CM 10.1, 10.2, 11, as well as the offshoots, none of them connect to the controller. They connect to other bluetooth things I've tried, like keyboards and speakers, but no PS3 controller. Any other controllers work that I'm not aware of?
I've heard people saying something along the lines of there being an issue with the bluetooth stack on the newer ROMs, or that it is just a problem with the newer Androids in general. Though my phone, Galaxy S4, is running a 4.4.4 Slimkat build, with the 3.4 kernel, and it connects to the controller no problem.
I greatly appreciate all the Touchpad developers and all you guys have done to keep this thing alive, it's simply amazing. I'm just wondering if any of you have any idea as to why this aspect doesn't work and if it is even feasible to get it working? As it's a large factor in determining what ROM I will run on my Touchpad. I have no problem staying on CM9 if that's what it comes down to, but if we could somehow get it working on KitKat or Lollipop, that would be fantastic.
I'm willing to do whatever to help if someone is able to help me. I'm no developer but I'm very comfortable with a computer and with flashing ROMs and whatnot, as well as troubleshooting issues, so I'd be able to test some things out, take some logs of things, in order to help someone more literate in the development side of things see what is going on and where the problem may lie. I'm sure I'm not the only one wishing this would work, and I'll help to get it working in any way I can.
Thanks in advance, guys.
DBak451 said:
Sorry if this question has been asked before but I did some searching and was unable to find a straight answer anywhere and my question is a bit different.
Is there any hope for getting the Sixaxis PS3 Controller app working properly on any of the Android builds for the Touchpad. CM9 is the only thing it worked on as far as I can tell.
CM 10.1, 10.2, 11, as well as the offshoots, none of them connect to the controller. They connect to other bluetooth things I've tried, like keyboards and speakers, but no PS3 controller. Any other controllers work that I'm not aware of?
I've heard people saying something along the lines of there being an issue with the bluetooth stack on the newer ROMs, or that it is just a problem with the newer Androids in general. Though my phone, Galaxy S4, is running a 4.4.4 Slimkat build, with the 3.4 kernel, and it connects to the controller no problem.
I greatly appreciate all the Touchpad developers and all you guys have done to keep this thing alive, it's simply amazing. I'm just wondering if any of you have any idea as to why this aspect doesn't work and if it is even feasible to get it working? As it's a large factor in determining what ROM I will run on my Touchpad. I have no problem staying on CM9 if that's what it comes down to, but if we could somehow get it working on KitKat or Lollipop, that would be fantastic.
I'm willing to do whatever to help if someone is able to help me. I'm no developer but I'm very comfortable with a computer and with flashing ROMs and whatnot, as well as troubleshooting issues, so I'd be able to test some things out, take some logs of things, in order to help someone more literate in the development side of things see what is going on and where the problem may lie. I'm sure I'm not the only one wishing this would work, and I'll help to get it working in any way I can.
Thanks in advance, guys.
Click to expand...
Click to collapse
I've got it to work, will try it on lollipop.