Hi,
Has anyone had any luck with writing Midlets for the XDA2? I'm trying to write one use the camera as a webcam (Yes, I know, a bit ambitious for my secomd midlet!)
I'm using this line:
Code:
Player vPlayer = Manager.createPlayer("capture://video");
I get a MediaException, meaning '...a Player cannot be created for the given locator.' (quoted from MMAPI JavaDoc).
Also, calling the Manager.getSupportedProtocols() method for 'mpeg/video' returns an empty list, as does calling Manager.getSupportedContentTypes() for 'capture://video'.
Has anyone else managed to access the XDA2 camera from a Midlet? If so, what is the trick?!!
cheers
Paul
I don't think anybody's managed to get access to it from native eVC++ let alone midlets, and IA style aren't revealing anything about how their app does it, so I wouldn't hold your breath for a solution... Bloody closed APIs.
Knackers!! :evil:
Cheers anyway! I'll keep poking and see what happens....
Paul
i suspect that their applications take pretty much control direct without using the winCE api
because when i start the cam my clock which it still display stop being 24h and turn to the AM/PM confusement
Now that bal666's awesome utility gives us the ability to decrypt/encrypt the NBF file, we can view and/or extract the ROM files that are normally not available to us otherwise.
One big hoopla that Windows Mobile 5.0 was supposed to have was the native ability to access the camera through their APIs, so that third-party developers could create applications without having to deal with each and every different type of camera technology in different Pocket PC and Smartphone devices.
Of course, it's apparent that HTC has still used their own software and drivers and has not given access to anyone outside of HTC. Not like Microsoft had their own Camera application (I don't know if there ever was one, but there isn't a Microsoft one on the Universal).
Developers such as ComVu with their neat PocketCaster software, are having such a difficult time making a single Windows Mobile 5.0-ready application, and have resorted to making different versions for different devices.
So... where am I going with this? Simple. Let's dump out the contents of the NK.NBF file and see if we can make our own applications with the APIs and drivers that HTC has embedded in the ROM.
I, for one, am looking forward to a internet-based videoconferencing application, much like Microsoft Portrait. Skype also announced video calls on PCs with the new version 2.0. Perhaps someone could send them some code to get video capability on the Universal?
That front-facing camera is beckoning to be used...
On a sidenote, PPL: Pocket Programming Language, allows you to easily create applications (self-contained EXE files, as a matter of fact), and also allows direct access to DLLs and APIs...
Put these two concepts together, and you can see the potential.
Create an application to...
... toggle the camera flashlight.
... do internet videoconferencing.
... do face recognition security.
Create your own camera app, phone app, game using images from the camera, etc. etc.
Another thing, though I'm not sure, but perhaps it's possible to rebuild your own ROM... remove Voice Speed Dial? Embed Voice Command, Resco Explorer, remove stupid applications or unused portions? etc. etc.
What does anyone else think about this?
BtT,
This sounds great, even having only a magician which will likely not being supported in projects like this. I still want to create my own rom with at least all the patches installed in rom. Camera & Album are taking at least 1Mb from my precious storage & apps like resco explorer are indeed must haves.
So I'm looking rorward to progress & tips in this thread & when I succeed with simple magician rom cooking I'll let you know. Don't expect any new camera apps from me, no time & no development for anymore .
Regards, M
http://research.microsoft.com/workshops/FS2005/presentations/FacultySummit_2005_Lieberman.ppt
I just realized that Windows Mobile 5 SDK contains a "common camera API" which is likely the method that third-party developers will take (or have taken) to access the camera. I have emailed Skype to see if their new 2.0 desktop version that has Video Calling can be somehow implemented on the Pocket PC, now that it is technically feasible.
I'm surprised the guys behind Microsoft Portrait haven't jumped on this yet.
Hi !!
Has anyone seen or heard of an application that lets one access the built-in camera via wlan ? I'm thinking of using my phone as a security cam ...
Thanks !!
More Camera Function for your buck
Any programmers out there? Gurus, god like creatures, avatars, superheros, and supreme beings..... PLEASE can any of you develop a program to allow us to get more functionality out of the camera:
1. As indicated, as a security camera
2. Instant Messenger or alternative instant chat by camera over WIFI rather than needing a video call
3. Perhaps even, maybe possibly, enable the camera flashlight also.....
4. Remote control operation from PC
5. Remote control operation over the web!!
I'll tip in some bucks for it and I am sure given the number of forums on this, that others will also.
Alas, mine is the JJ rather than wizard, but I think many and all would like some additional apps and functions out of the cameras.
www.comvu.com ComVu PocketCaster...
Try this one, it works very well
http://forum.xda-developers.com/viewtopic.php?t=40606
Kim
A few weeks ago I started skining the 5.04 Camera to look like 6.08. That was fairly successful, however the main issue, lag time, was of course not affected. I then started trying to hack AF into the 6.08 Camera version & had issues getting it to function as it relies on some different resources that I could not get functioning concurrently.
So, last night I started playing with a new idea. Renaming & resources from one of the two camera versions allowing for both cameras to be installed, having one called to initialization by a long camera keypress.
Anyone familar with widows mobile (Arm) executables & resource hacking willing to help out on this idea & test it?
Is this something people would like to see in a cooked rom? Would the ability to toggle the camera depending on what you need, Auto-Focus or Speed, be appealing?
It really wouldn't add too much weight to the ROM, as both Camera use primarily the same resources/DLL's. Would having a choice of a macro/micro (AF) mode bee something you'd like to see?
Hi man,
Realy great what you want to do but to be honest I don't like the camera atm cause the front camera isn't working with the 6.8 build (correct me if I'm wrong).
I would rather have both camera's supported on my Kaiser to use this build.
Together with the Opal dialer with videocall enabled that would be a awsom job!
Grtz,
Leo
Great Suggestion!
I have not looked into that at all, My last TYTNII is dead, so I am on a Tilt. If you are willing to give it a test since you have both cameras, I will look into implementing that as well.
BTW, I will be moving this into the Development & Hacking thread soon. I just wanted to start it here to see if any Kaiser users had any camera hacking experience or suggestions.
I would be glad to help you my friend.
Please let me know when you have something!
GSLEON3 said:
Great Suggestion!
I have not looked into that at all, My last TYTNII is dead, so I am on a Tilt. If you are willing to give it a test since you have both cameras, I will look into implementing that as well.
BTW, I will be moving this into the Development & Hacking thread soon. I just wanted to start it here to see if any Kaiser users had any camera hacking experience or suggestions.
Click to expand...
Click to collapse
I have been able to specifically locate the function handling the camera AF uysing IDA Pro, I also see that there appears to be some hard coding of FPS information/limits in the camera executable for the 5.04 Kaiser Camera.
This info is not present within the newer (Opal) camera as far as I can tell & may be a reason why it seems to outperform the Kaiser Stock Camera. There is also no information or AF calls within the Opal Camera executable. Hence, without a complete rewrite of the program I cannot simply integrate AF into the newer camera.
Lost...
Anyone???
I have tried renaming the resources & creating a new registry tree all to no Avail.
I seem to have enough resources available to operate trhe second camera, however I cannot get it to initialize. Anyone have any suggestions?
GSLEON3 said:
I have been able to specifically locate the function handling the camera AF uysing IDA Pro, I also see that there appears to be some hard coding of FPS information/limits in the camera executable for the 5.04 Kaiser Camera.
This info is not present within the newer (Opal) camera as far as I can tell & may be a reason why it seems to outperform the Kaiser Stock Camera. There is also no information or AF calls within the Opal Camera executable. Hence, without a complete rewrite of the program I cannot simply integrate AF into the newer camera.
Click to expand...
Click to collapse
Have you found many functions involved in the AF management, in the old version ? I'm a bit busy with the Dialer, but since we're both using IDA Pro, I may take a look to what you've documented so far in the IDA database... I'm not a big expert in camera apps, but who knows...
BJK
There are about 6 or so references. Both cameras use primarily the same resource files, so it appears to me that the AF function is coded into the executable.
I had pretty much given up on the addition of AF to the new 6.8 camera & had decided it would be easier for a novice like me to just add support for a second camera program.
However, that task is also throwing me at the moment. I have built a new cab, with renamed files & some hacks to point to the renamed files, I have also created a moddified registry tree to co-exist with the one for the OEM camera, yet when I select the newly moddified camera it tries to launch, but won't initialize.
Missing something somewhere...
GSLEON3 said:
There are about 6 or so references. Both cameras use primarily the same resource files, so it appears to me that the AF function is coded into the executable.
Click to expand...
Click to collapse
No external reference to a shared .dll ?
I had pretty much given up on the addition of AF to the new 6.8 camera & had decided it would be easier for a novice like me to just add support for a second camera program.
However, that task is also throwing me at the moment. I have built a new cab, with renamed files & some hacks to point to the renamed files, I have also created a moddified registry tree to co-exist with the one for the OEM camera, yet when I select the newly moddified camera it tries to launch, but won't initialize.
Click to expand...
Click to collapse
That's why I asked. It seems a single-threaded apartment issue. If it is an external .dll, maybe it could not be designed for multiple concurrency...
BJK
DupinBJK said:
No external reference to a shared .dll ?
That's why I asked. It seems a single-threaded apartment issue. If it is an external .dll, maybe it could not be designed for multiple concurrency...
BJK
Click to expand...
Click to collapse
When I get a moment I will post what I have found, the differences in the executables & the AF refernces & coding.
It may all be moot however, as I take a look at the Raphael camera, which allegedly has AF as well as a newer camera. We shall see.
GSLEON3 said:
When I get a moment I will post what I have found, the differences in the executables & the AF refernces & coding.
It may all be moot however, as I take a look at the Raphael camera, which allegedly has AF as well as a newer camera. We shall see.
Click to expand...
Click to collapse
Good, thanks !
Again, need to reiterate that arm executables are not my thing, however, I have hacked the Ralph Camera & it uses the same icons & resource (Mostly) as the Kaiser & Opal.
However when I build a new cab just to see if the AF is working already on the new Fuze ROM Camera I get an unsigned error message.
Can one of you ARM pros give me some insight?
Fuze Camera is new version & definitely has AutoFocus support!
Works with the existing hacked QVGA .mui & icon files, but when trying to create the cab I still get unsigned error.
Anyone???
Here is the start of an OEM QVGA package. Exe still won't launch.
Anyone want to take a look? Do I need to resign the app, the exe?
It includes all files & images resized & hacked for QVGA including the .mui files. The exe is throwing me badly though.
The OEM can be found here: http://rapidshare.com/files/159104147/HTC_Camera_6_Fuze_OEM_QVGA.rar
However, it seems the sensorSDK references are giving me the issues. Maybe need to find a way to null them out or default landscape.
If I'm understanding correctly, you'd like a switch to use the camera version with AF and the camera version without AF. Correct or am I completely missing something here? If I AM understanding correctly, then I would be all for this, as this would really make the camera on the Kaiser at least sort of useful, as opposed to only usable in certain conditions.
GSLEON3 said:
Here is the start of an OEM QVGA package. Exe still won't launch.
Anyone want to take a look? Do I need to resign the app, the exe?
It includes all files & images resized & hacked for QVGA including the .mui files. The exe is throwing me badly though.
The OEM can be found here: http://rapidshare.com/files/159104147/HTC_Camera_6_Fuze_OEM_QVGA.rar
However, it seems the sensorSDK references are giving me the issues. Maybe need to find a way to null them out or default landscape.
Click to expand...
Click to collapse
Sorry for being late...
Have you removed the signature before patching the files ? You have to remove it from each signed file you're going to patch, to be able to use it. I can do it for you, if you wish...
BJK
met3ora said:
If I'm understanding correctly, you'd like a switch to use the camera version with AF and the camera version without AF. Correct or am I completely missing something here? If I AM understanding correctly, then I would be all for this, as this would really make the camera on the Kaiser at least sort of useful, as opposed to only usable in certain conditions.
Click to expand...
Click to collapse
YES. That was the original intention of this thread.
DupinBJK said:
Sorry for being late...
Have you removed the signature before patching the files ? You have to remove it from each signed file you're going to patch, to be able to use it. I can do it for you, if you wish...
BJK
Click to expand...
Click to collapse
BJK, I would be eternally gratefull if you'd do that for me, then I can see if I can find a way to null out or hack a SensorSDK.DLL to aways import the landscape value as a return & maybe see if the results are succesful.
OT: gsleon03...dude im your neighbor lol...i live in Torrance and im up in PV once in a while.
id like to see this project come true
Hi
first, sorry that I interrupt this thread and asking about improvement of frame rate for shooting video throw HTC camera, am have Cruise and has low frame rate in video recording and I think that Kaiser has the same issue, am using the famous camera trick " run camera program, hiding the lens, power off devise and waiting for Sec's, then power on again" which rising the frame rate from 4 to 19 frame/sec in video shooting but with darkens pic, did any one analysis this trick and try to get solution for camera low rate problem or found why 6.08 camera is faster than 5.04
finaly i hope that see this project come true
secoseco said:
Hi
first, sorry that I interrupt this thread and asking about improvement of frame rate for shooting video throw HTC camera, am have Cruise and has low frame rate in video recording and I think that Kaiser has the same issue, am using the famous camera trick " run camera program, hiding the lens, power off devise and waiting for Sec's, then power on again" which rising the frame rate from 4 to 19 frame/sec in video shooting but with darkens pic, did any one analysis this trick and try to get solution for camera low rate problem or found why 6.08 camera is faster than 5.04
finaly i hope that see this project come true
Click to expand...
Click to collapse
I second that. ist there still any development?
Hey there,
I tried to create an app with the HTC One M8 and it´s Duallens "depthsensor".
The problem is that there is no way to activate the second rear camera in android.
In android.hardware.camera package there are some hidden methods like : enableSubCam...so I´ll tried to use java reflection to activate these SubCam, but it doesn´t work at all...
I need some depth information in realtime for my application and I thought with the new DualLens this would be possible.
Also I tried to understand the HTC DualLens SDK, but all this stuff works on an jpg format and without creating an new depthMap
So what do you think is the best method to access 1. the second rear camera or 2. directly some kind of depthMap with help from HTC SDK?
gurd123 said:
Hey there,
I tried to create an app with the HTC One M8 and it´s Duallens "depthsensor".
The problem is that there is no way to activate the second rear camera in android.
In android.hardware.camera package there are some hidden methods like : enableSubCam...so I´ll tried to use java reflection to activate these SubCam, but it doesn´t work at all...
I need some depth information in realtime for my application and I thought with the new DualLens this would be possible.
Also I tried to understand the HTC DualLens SDK, but all this stuff works on an jpg format and without creating an new depthMap
So what do you think is the best method to access 1. the second rear camera or 2. directly some kind of depthMap with help from HTC SDK?
Click to expand...
Click to collapse
i remember there was an app (german) that take 2 pictures at the same time from both rear cameras but the app was just to show that both work so it was like open app>automatic capture>save both pictures>exit.
got it : http://forum.xda-developers.com/showthread.php?t=2722352
yeah I´ve seen this app, but it´s hard coded on the linux kernel ...
and like I said I´ll try to calculate the depthMap in realtime, so a continious Depth-Matrix with opencv for example and not just a jpg
isn´t there a possibility to access the hardware components of an smartphone and activate them?
gurd123 said:
yeah I´ve seen this app, but it´s hard coded on the linux kernel ...
and like I said I´ll try to calculate the depthMap in realtime, so a continious Depth-Matrix with opencv for example and not just a jpg
isn´t there a possibility to access the hardware components of an smartphone and activate them?
Click to expand...
Click to collapse
Maybe this will help you
Code:
[URL="https://www.htcdev.com/devcenter/opensense-sdk/htc-dual-lens-api/htc-dual-lens-sdk-installation/"]https://www.htcdev.com/devcenter/opensense-sdk/htc-dual-lens-api/htc-dual-lens-sdk-installation/[/URL]
like I said in the first post, I´ve tried to understand the SDK, but in my oppinion it´s not for creating a file...
you´re just allowed to use the already created depth information of an jpg-file...
or has anyone made some other experiences with the SDK?
Have you solved the problem?
Hi,
I have the similar situation and would like to know if you have found a solution to this problem.
I agree with you that the SDK provided by the HTC website is for depth info extraction from already created image. The SDK is not viable for realtime depth processing.
Please let me know if you have the solution for this problem.
Thanks!
gurd123 said:
Hey there,
I tried to create an app with the HTC One M8 and it´s Duallens "depthsensor".
The problem is that there is no way to activate the second rear camera in android.
In android.hardware.camera package there are some hidden methods like : enableSubCam...so I´ll tried to use java reflection to activate these SubCam, but it doesn´t work at all...
I need some depth information in realtime for my application and I thought with the new DualLens this would be possible.
Also I tried to understand the HTC DualLens SDK, but all this stuff works on an jpg format and without creating an new depthMap
So what do you think is the best method to access 1. the second rear camera or 2. directly some kind of depthMap with help from HTC SDK?
Click to expand...
Click to collapse