I wanted to get the Nokia N95 but can't go back to non touch screen phones. So the tilt was my only choice. But after having used it for a month I wish htc would have put some more thoughts in their design. The following would have made the phone even much better:
- 3D graphics. Camera and video are a pitty to use. The qualcomm chip is more powerful than what the phone is currently providing.
- Speaker would have been better placed at the sides rather than behind. The phone can't stand on its side either so am left with placing the phone with the screen facing down. The P3300 was a joy to use. Placing the phone on any surface actually enhanced the audio playback.
- Htc would have at least provided a 3.5mm audio adapter considering the price of the phone or included a jack so people can use any earphone of their choice. The depth of the phone allows this feature to be implemented without any problem.
I love my Tytn 2, best PDA yet
Only thing I want and many others is 3D Drivers, this would then give great 3d graphics capability considering the power of that chip, provide tons better video playback with very high quality settings and should improve the camera performance all in one go
Other than that the phone for me perfect
Speaker Sucks! Headphone connector!
joe mboule said:
. . . - Speaker would have been better placed at the sides rather than behind. The phone can't stand on its side either so am left with placing the phone with the screen facing down. The P3300 was a joy to use. Placing the phone on any surface actually enhanced the audio playback.
- Htc would have at least provided a 3.5mm audio adapter considering the price of the phone or included a jack so people can use any earphone of their choice. The depth of the phone allows this feature to be implemented without any problem.
Click to expand...
Click to collapse
I agree with these 2 thoughts 100%.
The speaker is very tinny, and really dumb to have on the back side. My Cingular 8125 Wizard had WAY better speakers, but even a decent mono speaker on the side would be acceptable, since we're really going to use a headset for any decent stereo sound.
Which brings us to the second point, that connecting ANY decent headphone is a pain in the arse, whether it's a 2.5 or 3.5 mm jack that the headset has.
Beaming
I wish that my Tilt could beam information like my other PDA's have in the past. I see that I have the option to beam in the software, but no "beamer" to initiate the action.
maiahsdad said:
I wish that my Tilt could beam information like my other PDA's have in the past. I see that I have the option to beam in the software, but no "beamer" to initiate the action.
Click to expand...
Click to collapse
You CAN beam with the Tilt. Just through bluetooth, not infrared.
kareem9nba said:
You CAN beam with the Tilt. Just through bluetooth, not infrared.
Click to expand...
Click to collapse
WAY COOL! Now... I've made the device that I want to beam information to; discoverable, and my device is discoverable. But here's the thing... I can beam information to the other device, but NO devices can beam to me for some reason. I'm using 4 devices just in case one device is in disrepair. But they all can bluetooth information to each other back and forth, and I can bluetooth information to all of them, but NONE of them can bluetooth information to me although they all discover my device when searching. I have disabled the beaming authorization in my device so that wouldn't be an issue. But SOMETHING is keeping others from beaming (bluetooth) information to me.
Any ideas?
Flash light would be nice for us blind in the dark folks.
I'd like:
1. Mass Storage Mode, the WM5 app does'nt seem to work
2. TV out
3. USB Host
4. Better Drivers
5. I'm happy with the cam, but the only niggle is with night mode, I've been getting some superb daylight pics from the phone.
shoulda came with a 2.5 m headphone jack.
I want better drivers for all the radios
This should be running LinuxArm/DebianArm/any linux distro(WM6 sucks - too much locking up)
maiahsdad said:
WAY COOL! Now... I've made the device that I want to beam information to; discoverable, and my device is discoverable. But here's the thing... I can beam information to the other device, but NO devices can beam to me for some reason. I'm using 4 devices just in case one device is in disrepair. But they all can bluetooth information to each other back and forth, and I can bluetooth information to all of them, but NONE of them can bluetooth information to me although they all discover my device when searching. I have disabled the beaming authorization in my device so that wouldn't be an issue. But SOMETHING is keeping others from beaming (bluetooth) information to me.
Any ideas?
Click to expand...
Click to collapse
Under Comm manager>Settings>Bluetooth>FTP enable file sharing.
Surur
improvements
1) better keyboard
2) faster processor
3) faster graphics
4) better slide design, with the screen springs and tilts automatically
5) earphone jack redesign
6) more prominent power button
7) better GPS reception, wifi reception
...
...
Most importantly, HTC should have given us a very fast processor. You want wishlist? this is impossible. These are just to shoot HTC on their product flaws.
Hello,
First things first:
This is my first post here. I live in Brazil, and I work as a software developer. I have always liked technology and gadgets, and I bought my first smartphone a few years ago.
It was a Nokia N-Gage QD. I loved it, because it had a wonderful OS (Symbian S60 1st Edition). But the hardware was quite limited, with a ~100 MHz processor, 16 MB memory, used very slow MMC cards, and the main problem was the screen, which was only 176x208, 4k colors, and very low contrast. Since it was a S60 device it also had no touchscreen. It also didn't have a MP3 player.
About a year ago I decided it was time for an upgrade. A friend of mine bought a Motorola A1200i (also known as Ming). I really loved it when she showed it to me. It is quite a bit smaller than the N-Gage, has a beautiful 320x240 touchscreen, pretty decent specs (312 Mhz Intel processor, 48 Mb memory, MicroSD support), the most beautiful user interface I have ever seen, and lots of built in applications.
But it has some very serious issues, most of them because of the limited Linux OS. Since it's Linux, there are absolutely no commercial applications, the only ones available are distributed freely by Linux fans.
I started looking for a better device, and found the Kaiser. It has pretty much everything I want that my phone doesn't have: a real OS, .Net support (which is my favorite programming platform), Wifi, GPS, 3G.
I read lots and lots of reviews, news and posts about it. I am aware of the driver issues, and I have also read that the battery doesn't last long.
Well, but anyway, some questions I have:
1. Music: I listen to music almost every day on my phone. I also have an original Motorola S9 headset, which I really really like. I will keep it to use with the Kaiser too. My phone has some issues with A2DP. The pitch is a little higher than it should, and sometimes I have to reconnect to get it working. But what I really dislike is that only RealPlayer streams to A2DP devices. All other applications need a wired headset. How good is the Kaiser for music with a Bluetooth headset?
2. Texting/messaging: I also text a lot. Since my phone has no keyboard, I use a virtual one, very similar to the one found on WM. How much faster is the physical keyboard? Some people say the keys are a little hard to press, is that true? And is the keyboard good enough for moderate use or I would be better off with a Bluetooth keyboard?
3. Web: I also like to browse the web on my phone. I use Opera Mini, because I really like its features, and it synchronizes with my desktop Opera, so I can have the same bookmarks. Is Mini also the best choice on Kaiser?
4. Video: This one I wish I could use more, but I don't because the application I use doesn't stream to Bluetooth headsets. But anyway, my phone is pretty decent when it comes to video playing. I can play 320x240 XVid videos at around 25 FPS. Can the Kaiser achieve this kind of performance even without proper drivers? AFAIK WM handles A2DP streams, so in theory any application can use them. Does that mean I can watch videos with my Bluetooth headset?
5. Battery: How much does it last with real life use? I don't mind if it doesn't last very long, as long as it lasts at least a full day with heavy use. My phone lasts for around 2.5 days with light use, and listening to 3 hours of music with Bluetooth make it last a day less. But it's still good, because I only have to charge it at night.
6. Application: And how about developing applications? .Net seems almost too easy to be true. Do I really only have to compile the application on Visual Studio and install it? No 99 step building and deploying process like my old Symbian phone had?
7. Games: I don't play games that much, I don't even have any game installed on my PC, but it can be a good passtime when on the go. On my N-Gage QD I had a few games that were really good, and some emulators. Because of the limited resolution I could only play Gameboy games, but it could also emulate SNES. And there were many games I liked on the SNES. Can the Kaiser run it? How are the controls?
8. File transfer: Does it support PAN protocol, so I can browse the folders on the SD through Bluetooth? Once I saw a friend of mine doing it with a Dell X51 and it's much much better than OBEX.
I guess that's it for now. I looked for guides that would answer my questions, but didn't find any. Is there a FAQ or something?
Any help will be greatly appreciated, and I hope I can retribute if/when I buy a Kaiser myself.
Thanks!
Smaniac said:
Hello,
First things first:
This is my first post here. I live in Brazil, and I work as a software developer. I have always liked technology and gadgets, and I bought my first smartphone a few years ago.
It was a Nokia N-Gage QD. I loved it, because it had a wonderful OS (Symbian S60 1st Edition). But the hardware was quite limited, with a ~100 MHz processor, 16 MB memory, used very slow MMC cards, and the main problem was the screen, which was only 176x208, 4k colors, and very low contrast. Since it was a S60 device it also had no touchscreen. It also didn't have a MP3 player.
About a year ago I decided it was time for an upgrade. A friend of mine bought a Motorola A1200i (also known as Ming). I really loved it when she showed it to me. It is quite a bit smaller than the N-Gage, has a beautiful 320x240 touchscreen, pretty decent specs (312 Mhz Intel processor, 48 Mb memory, MicroSD support), the most beautiful user interface I have ever seen, and lots of built in applications.
But it has some very serious issues, most of them because of the limited Linux OS. Since it's Linux, there are absolutely no commercial applications, the only ones available are distributed freely by Linux fans.
I started looking for a better device, and found the Kaiser. It has pretty much everything I want that my phone doesn't have: a real OS, .Net support (which is my favorite programming platform), Wifi, GPS, 3G.
I read lots and lots of reviews, news and posts about it. I am aware of the driver issues, and I have also read that the battery doesn't last long.
Well, but anyway, some questions I have:
1. Music: I listen to music almost every day on my phone. I also have an original Motorola S9 headset, which I really really like. I will keep it to use with the Kaiser too. My phone has some issues with A2DP. The pitch is a little higher than it should, and sometimes I have to reconnect to get it working. But what I really dislike is that only RealPlayer streams to A2DP devices. All other applications need a wired headset. How good is the Kaiser for music with a Bluetooth headset?
2. Texting/messaging: I also text a lot. Since my phone has no keyboard, I use a virtual one, very similar to the one found on WM. How much faster is the physical keyboard? Some people say the keys are a little hard to press, is that true? And is the keyboard good enough for moderate use or I would be better off with a Bluetooth keyboard?
3. Web: I also like to browse the web on my phone. I use Opera Mini, because I really like its features, and it synchronizes with my desktop Opera, so I can have the same bookmarks. Is Mini also the best choice on Kaiser?
4. Video: This one I wish I could use more, but I don't because the application I use doesn't stream to Bluetooth headsets. But anyway, my phone is pretty decent when it comes to video playing. I can play 320x240 XVid videos at around 25 FPS. Can the Kaiser achieve this kind of performance even without proper drivers? AFAIK WM handles A2DP streams, so in theory any application can use them. Does that mean I can watch videos with my Bluetooth headset?
5. Battery: How much does it last with real life use? I don't mind if it doesn't last very long, as long as it lasts at least a full day with heavy use. My phone lasts for around 2.5 days with light use, and listening to 3 hours of music with Bluetooth make it last a day less. But it's still good, because I only have to charge it at night.
6. Application: And how about developing applications? .Net seems almost too easy to be true. Do I really only have to compile the application on Visual Studio and install it? No 99 step building and deploying process like my old Symbian phone had?
7. Games: I don't play games that much, I don't even have any game installed on my PC, but it can be a good passtime when on the go. On my N-Gage QD I had a few games that were really good, and some emulators. Because of the limited resolution I could only play Gameboy games, but it could also emulate SNES. And there were many games I liked on the SNES. Can the Kaiser run it? How are the controls?
8. File transfer: Does it support PAN protocol, so I can browse the folders on the SD through Bluetooth? Once I saw a friend of mine doing it with a Dell X51 and it's much much better than OBEX.
I guess that's it for now. I looked for guides that would answer my questions, but didn't find any. Is there a FAQ or something?
Any help will be greatly appreciated, and I hope I can retribute if/when I buy a Kaiser myself.
Thanks!
Click to expand...
Click to collapse
Generally I'm of the opinion that the Kaiser isn't right for very many people, but to answer your questions:
1. If you have a good pair of BT headphones, listening to music on them is simple. This is true on most WM devices.
2. Biggest problem I have is that the spacebar has two sensors (clicks on left and right which you'll probably end up pressing both at once) which is a really stupid design move. On top of that, the Kaiser does not register double presses of a button (i.e. it would have written out that part as "preses of a buton") unless you type very slowly. Some people find various onscreen solutions better, but in general I find the keyboard adequate.
3. Opera Mini is the easiest to use at the moment.
4. No. And yes to your second question.
5. It will not last a day with heavy use.
6. Don't know.
7. Go to Howard Forums and search for a post on emulators by menneisyys.
8. Yes, WM supports PAN protocol.
1. Music works pretty well except for an issue where the sound stops for a fraction of a second every few minutes or so.
2. The keyboard isn't as good as it could be(especially with that weird random lag it sometimes has) but still way better than an onscreen keyboard.
3. I like Opera Mobile, but I'm too cheap to pay for it so I'm using PIE.
4. Coreplayer is supposed to release a version well suited for the Kaiser in a couple of months. It costs money though.
5. Two days in light use in an Edge area. 6 hours in an 'H' area listening to music, using google maps, surfing the internet.
6. Yes compared to other environments, writing on the compact framework is a thing of wonderous joy.
7. I've had alot of problems getting these things usable. They don't seem to be actively developing them much.
8. Don't know.
Overall it's like owning classic corvette and having to use it as a commuter car. You love it but you also can't help but hate it sometimes.
Thank you very much for your help, both of you. You pointed me in the right direction. Now I know I can expect CorePlayer 1.2 to be great. And I don't really mind paying for software, because since I earn money from it I also recognize its value. Besides, $25 will be pretty cheap considering its benefits.
2 things that got me really disappointed though seem to be keyboard and battery. About the keyboard, I will wait for the official release in Brazil next month, so I can test it. But is the battery really that bad? Maybe I can live with it, I can recharge it at work when needed, because it charges by USB from what I have read.
Anyway, I know this phone isn't perfect. There is and will never be any perfect device. But even considering its flaws, it seems to be excellent.
I wish the video driver issue was really solved though. It would make it even more attractive to everyone.
Thank you very much for your time again.
Blowfish64 said:
7. Go to Howard Forums and search for a post on emulators by menneisyys.
Click to expand...
Click to collapse
Thanks for the promotion
That's no longe rneeded - in the meantime, I've migrated all my Bibles in the local Wiki (it took me SEVERAL days to do so... thousands of articles...)
See http://wiki.xda-developers.com/inde...s - for both games and productivity platforms
Smaniac said:
2 things that got me really disappointed though seem to be keyboard and battery. About the keyboard, I will wait for the official release in Brazil next month, so I can test it. But is the battery really that bad? Maybe I can live with it, I can recharge it at work when needed, because it charges by USB from what I have read.
Click to expand...
Click to collapse
Disable 3G; then, it'll be a lot better. See my related Bible at http://wiki.xda-developers.com/inde...(GPRS & EDGE) modes to optimize battery life! and http://wiki.xda-developers.com/inde...(auto-)terminate unnecessary data connections
Blowfish64 said:
1. If you have a good pair of BT headphones, listening to music on them is simple. This is true on most WM devices.
Click to expand...
Click to collapse
Justa quick warning: the Kaiser uses the A2DP implementation of the MS BT stack. While it's definitely better than that of previous OS'es (WM5 - see http://wiki.xda-developers.com/inde...nes) quality: Light at the End of the Tunnel? for more info on this), it's still worse than decent A2DP implementations like those of Nokia or the dumbphones / media players of Samsung. You won't really notice the difference if you only listen to, say, disco music; with classical / folk / world music, the difference is HUGE.
That is, if you REALLY need A2DP, go for a non-WM device or get an additional, cheap A2DP source; for example the Samsung YP-T9J.
I really recommend ALL the A2DP-related articles at http://wiki.xda-developers.com/inde...for 1. DUN and connectivity issues; 2. gaming for more info.
Blowfish64 said:
Smaniac said:
8. File transfer: Does it support PAN protocol, so I can browse the folders on the SD through Bluetooth? Once I saw a friend of mine doing it with a Dell X51 and it's much much better than OBEX.
Click to expand...
Click to collapse
8. Yes, WM supports PAN protocol.
Click to expand...
Click to collapse
The OP seems to have confused the File Transfer Profile with PAN. They have nothing to do with each other. BT PAN can be used to transfer files - but FT is much-much better suited for this task. (BTW, PAN isn't really supported, only in server mode - see my related articles.)
Fortunately, the Kaiser, being WM6 (as opposed to earlier OS'es), supports FT - unless your particular rebrander has removed the support.
Smaniac said:
7. Games: I don't play games that much, I don't even have any game installed on my PC, but it can be a good passtime when on the go. On my N-Gage QD I had a few games that were really good, and some emulators. Because of the limited resolution I could only play Gameboy games, but it could also emulate SNES. And there were many games I liked on the SNES. Can the Kaiser run it? How are the controls?
Click to expand...
Click to collapse
For emulation, currently, it's plain useless. See the emulation-related threads here.
If you want DECENT emulation capabilities, currently, your ONLY choice is the Dell Axim x50v / x51v.
Menneisyys said:
Thanks for the promotion
That's no longe rneeded - in the meantime, I've migrated all my Bibles in the local Wiki (it took me SEVERAL days to do so... thousands of articles...)
See http://wiki.xda-developers.com/inde...s - for both games and productivity platforms
Click to expand...
Click to collapse
Nice articles, one thing that really got me interested was ScummVM. I only knew the desktop version, had no idea there was a WM version.
Menneisyys said:
Disable 3G; then, it'll be a lot better. See my related Bible at http://wiki.xda-developers.com/inde...(GPRS & EDGE) modes to optimize battery life! and http://wiki.xda-developers.com/inde...(auto-)terminate unnecessary data connections
Click to expand...
Click to collapse
Well, I won't be using 3G all of the time, so that might be a viable solution. Great to know there is a simple application to do that.
Menneisyys said:
Justa quick warning: the Kaiser uses the A2DP implementation of the MS BT stack. While it's definitely better than that of previous OS'es (WM5 - see http://wiki.xda-developers.com/inde...nes) quality: Light at the End of the Tunnel? for more info on this), it's still worse than decent A2DP implementations like those of Nokia or the dumbphones / media players of Samsung. You won't really notice the difference if you only listen to, say, disco music; with classical / folk / world music, the difference is HUGE.
That is, if you REALLY need A2DP, go for a non-WM device or get an additional, cheap A2DP source; for example the Samsung YP-T9J.
I really recommend ALL the A2DP-related articles at http://wiki.xda-developers.com/inde...for 1. DUN and connectivity issues; 2. gaming for more info.
Click to expand...
Click to collapse
The main reason for me to play music on my phone is that I don't need to carry a whole different device. So buying something else just for music isn't an option. But I'll try it for myself, it will probably be better than my current Linux RealPlayer, which is really bad.
Menneisyys said:
The OP seems to have confused the File Transfer Profile with PAN. They have nothing to do with each other. BT PAN can be used to transfer files - but FT is much-much better suited for this task. (BTW, PAN isn't really supported, only in server mode - see my related articles.)
Fortunately, the Kaiser, being WM6 (as opposed to earlier OS'es), supports FT - unless your particular rebrander has removed the support.
Click to expand...
Click to collapse
Yep, you are right, I meant FT, not PAN. Sorry.
Menneisyys said:
For emulation, currently, it's plain useless. See the emulation-related threads here.
If you want DECENT emulation capabilities, currently, your ONLY choice is the Dell Axim x50v / x51v.
Click to expand...
Click to collapse
Emulation isn't a must for me, but it would be nice to have.
A friend of mine has a Dell x51v, and I REALLY hate it. I don't mean to offend who has one, but I just see it as a very bulky device with no kind of network connection whatsoever.
Thank you very much for the feedback. I'm starting to really like this community already.
battery isnt that bad, i get a good few hours of music over a2dp, a good few hours browsing time and ive got putty and messenger runing on the thing all the time over gprs - what i find realy kills the battery is how long you have the screen on, if i keep the screen on a lot, ill be down to mid 30%ies after a ful day - if i go a bit lighter ill still have about 50% by the time i goto bed.
the keyboard is ok - the double tap problem does bug me but ive trained myself to avoid it (mostly ) im writing this post on my kaiser, way faster than if i were to use an onscreen keyb but i have nails (and slender fingers) so i guess that makes it easier to hit the keys.
i can play transcoded (down to native 320x240) video just fine at decent fps (dont know exact framerate) - i dont notice any lag or stuttering - though im sure i wont need to transcode in the future when some drivers are released.
cant say about the audio quality over a2dp - ive never had issue with it, i actually think its quite good quality, but the loudspeaker on the back is so loud it does distort the sound quite often even if its set to a low level (sounds like its reverberating or smt)
all in all im happy with my kaiser given its few blemishes
Smaniac said:
The main reason for me to play music on my phone is that I don't need to carry a whole different device. So buying something else just for music isn't an option. But I'll try it for myself, it will probably be better than my current Linux RealPlayer, which is really bad.
Click to expand...
Click to collapse
It all depends on the music genre you listen to - and also the headphones you use. Some are just horrible with the MS BT stack; this is why I'm using a different, non-Microsoft gadget (Nokia N95) as an A2DP source. WAAAY better - there is just no comparison.
Smaniac said:
Emulation isn't a must for me, but it would be nice to have.
A friend of mine has a Dell x51v, and I REALLY hate it. I don't mean to offend who has one, but I just see it as a very bulky device with no kind of network connection whatsoever.
Click to expand...
Click to collapse
It indeed doesn't have a phone ("only" Wi-Fi / BT). However, if you're seriously into gaming / emulation, you will want to consider getting it - in addition to your Kaiser (it's pretty cheap now). The Kaiser is, currently, plain bad at both emulation, the touchscreen tap-and-hold CPU usage issues and the D-pad department.
fusi said:
battery isnt that bad, i get a good few hours of music over a2dp, a good few hours browsing time and ive got putty and messenger runing on the thing all the time over gprs - what i find realy kills the battery is how long you have the screen on, if i keep the screen on a lot, ill be down to mid 30%ies after a ful day - if i go a bit lighter ill still have about 50% by the time i goto bed.
the keyboard is ok - the double tap problem does bug me but ive trained myself to avoid it (mostly ) im writing this post on my kaiser, way faster than if i were to use an onscreen keyb but i have nails (and slender fingers) so i guess that makes it easier to hit the keys.
i can play transcoded (down to native 320x240) video just fine at decent fps (dont know exact framerate) - i dont notice any lag or stuttering - though im sure i wont need to transcode in the future when some drivers are released.
cant say about the audio quality over a2dp - ive never had issue with it, i actually think its quite good quality, but the loudspeaker on the back is so loud it does distort the sound quite often even if its set to a low level (sounds like its reverberating or smt)
all in all im happy with my kaiser given its few blemishes
Click to expand...
Click to collapse
As I can see everything is a matter of particular use and taste. Good to know that someone is really happy with it, I hope I will be too. Thanks for the info!
Menneisyys said:
It all depends on the music genre you listen to - and also the headphones you use. Some are just horrible with the MS BT stack; this is why I'm using a different, non-Microsoft gadget (Nokia N95) as an A2DP source. WAAAY better - there is just no comparison.
Click to expand...
Click to collapse
I use a Motorola S9, and I listen to a lot of different stuff (rock, pop, classical, and so on). I have tried it briefly on the Dell x51v and the quality was good, however it seems my friend was using a different BT stack. By the way, is that information correct? He told me MS one didn't support FT protocol, so he installed another one, and now it has it.
Menneisyys said:
It indeed doesn't have a phone ("only" Wi-Fi / BT). However, if you're seriously into gaming / emulation, you will want to consider getting it - in addition to your Kaiser (it's pretty cheap now). The Kaiser is, currently, plain bad at both emulation, the touchscreen tap-and-hold CPU usage issues and the D-pad department.
Click to expand...
Click to collapse
I'm not really into it. I don't even play games on my PC. I only play my Nintendo Wii for a few hours a week.
Like I said it would be a nice plus, but not a requirement.
It would be nice if I could play some slow-paced games like Chrono Trigger or Final Fantasy 6 though. Is it possible?
Thanks!
Menneisyys said:
The Kaiser is, currently, plain bad at both emulation, the touchscreen tap-and-hold CPU usage issues and the D-pad department.
Click to expand...
Click to collapse
Menneisyys,
Do you have any reason to believe the Polaris/Cruise will be better at this?
Hi.
I've used 4-5 GPS apps and I couldn't find option to set a sound (in my case beeping sound) when I gain vertical speed. I wanna use my tilt like a paragliding variometer cause i can't look at the phone and enjoy the view .
So is there app that have that option or could you make one plz.
You can search on youtube to see how variometer works.
A paragliding variometer can have up to three ways of letting you know your vertical speed. Audio sound, digital readout or analog clockface. Some varios are quite basic, like the simple audio-only vario with nothing but an Off/On switch.
Let's have a quick look at each type in turn.
The audio sound indication. If you are going up faster than a pre-set value, you hear a beep-beep tone which increases in pitch the stronger the lift is. Different models have different sounds. Some of them have a sink-alarm as well, warning you with another sound that you are sinking faster than some pre-set value.
Click to expand...
Click to collapse
The TyTN II is missing the hardware required
arminf said:
I've used 4-5 GPS apps and I couldn't find option to set a sound (in my case beeping sound) when I gain vertical speed. I wanna use my tilt like a paragliding variometer
Click to expand...
Click to collapse
Firstly welcome to XDA-DEV arminf! I know exactly what you're after but the HTC TyTN II (and consequently also the Tilt) isn't equipped with enough hardware to be able to do that. There's no Barometric capsule to sense changes in air pressure and no accelerometer so it's no can do using just the phone. Interestingly the Tomtom Navigator version that came with my TyTN II has a setting for which units pressure is to be displayed in (but it has no way of getting that info). Maybe with future products if you let HTC know you'd like this capability included, they may listen (oh, and don't forget to ask for complete driver support while you're at it ). The Touch Pro has an accelerometer but I don't know if it's capable of sensing acceleration in the right plane and whether it can be harnessed using software for this specific purpose.
Surely it should be doable. GPS gives your 3d position, so all software has to do is give compare the positions and times of two subsequent positions to work out the vertical speed.
It should be quite simple for someone who actually has a clue how to program for Windows Mobile
Flying Kiwi said:
Firstly welcome to XDA-DEV arminf! I know exactly what you're after but the HTC TyTN II (and consequently also the Tilt) isn't equipped with enough hardware to be able to do that. There's no Barometric capsule to sense changes in air pressure and no accelerometer so it's no can do using just the phone. Interestingly the Tomtom Navigator version that came with my TyTN II has a setting for which units pressure is to be displayed in (but it has no way of getting that info). Maybe with future products if you let HTC know you'd like this capability included, they may listen (oh, and don't forget to ask for complete driver support while you're at it ). The Touch Pro has an accelerometer but I don't know if it's capable of sensing acceleration in the right plane and whether it can be harnessed using software for this specific purpose.
Click to expand...
Click to collapse
Thanks
Wow you are really into variometers , and i know that Tilt doesn't have Barometric capsule, but I was trying to improvise with GPS. So i just need that beeping sound on some GPS app when I'm going up
dancj said:
Surely it should be doable. GPS gives your 3d position, so all software has to do is give compare the positions and times of two subsequent positions to work out the vertical speed.
It should be quite simple for someone who actually has a clue how to program for Windows Mobile
Click to expand...
Click to collapse
Keep in ming though that the GPS inside the TILT uses a perfect sphere model for the planet (AFAIR). So it is possible that you will get a number of false posities/negatives on an extremely uneven terrain...
But yes, in principle it should work.
TyTN II hardware still not up to the task
Whats needed for the intended purpose is something that reacts instantaneously (or very close to it) and with imense accuracy to sense when it's rising or decending and at what rate. If the device is to slow or not accurate enough (and I believe relying solely on the TyTN IIs GPS would present these issues) then you'd end up flying right through the thermal and out the other side or through the ridge lift and into the rotor etc.
When I first bought my bicycle and was looking for a GPS device to go on it (before I bought my TyTN II) I was looking at Garmin pocket GPS units one of which had an aneroid capsule built in. I checked their website and this model is still being sold and this is what it says "For extra-precise climb and descent data, Edge 305 also incorporates a barometric altimeter to pinpoint changes in elevation." Having used the TyTN II's GPS with TomTom Navigator, Google Maps and Microsoft Live Mapping, and seen how it sometimes struggles with basic 2 D mapping, I definitely wouldn't trust it to be up to speed in what the OP wants - irrespective of what software is coupled up to it.
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.