Camera RAW callback - EVO 4G Q&A, Help & Troubleshooting

Hi Guys,
I've done some searching and cannot seem to find anything recent about this issue. I'm wanting to write a camera application that shoots and stores the raw camera data from the EVO.
It looks like someone has put together a class that will take the byte array and dump it to DNG format which would be ideal. However, when the callback fires, I get an empty byte array and a null pointer exception.
Now, I'm not sure it's a coding error because the jpg callback works just fine.
Some older threads seem to imply that the raw callback doesn't actually do anything. I think there is one where a google developer said they thought they should nuke it all together....but that was 2008, I think.
So can this callback actually do anything? Does the SDK from HTC give me lower level access to the camera? What are my options? I think the camera in the EVO is okay, but the jpg compression just doesn't seem good to me....
Thanks!

Crud, since I'm new I can't post a link to the google thread I was referencing above with the dev saying he'd like to deprecate raw, but the thread id is: 65191ea020f6bb27 if anyone is interested. But that was in 2/2009.....
It looks like the Android dev implies they might add or support native signal processing, which would be fine but I have no idea how one might accomplish this in Java....(isn't the point of java to work at an abstracted layer?).
Anyway, I'll amend my questions to include this: do any of the ROMs out there support either native signal processing or raw camera call backs?
Maybe this is something I need to take directly to google?

Related

looking for XDA'sII camera dll or API - HELP

hello all,
i've been looking for a camera api or dll.
Right now developing a camera relatede program and i need to control the camera.
thank you!
simón
sims said:
Ive been looking for a camera api or dll.
Right now developing a camera relatede program and i need to control the camera.
Click to expand...
Click to collapse
We needed the same thing last week. The company that built the software (IAstyle, http://www.iastyle.com) got bought by HTC recently, and it doesn't look like they'll be selling much any time soon.
and one would resell or offer this api? it will help a lot the comunity
sims
Uhh I NEED THAT too
If anybody sdk or any clue how internaly camera comunicates... (does it use direct show system?)
LET ME KNOW pls!
I will try to use classic trick by capturing screen buffer while picture soft is running...
then my soft will put it to jpg remove jpg header and in sequence it will send it to my video stream server which then distributs it on broadband computer to more users which they will see something like this http://spaced.no-ip.com
however camera has 1 bug its picking up GSM-GPRS signal induction lines... anyway there is always way around it.[/quote]
i need the camera specification, to caputure images using my application. But there's no way for achieving this information.
please, if someone have the idea or where i can ask for....
sims
do you think that these drivers will work on an xda2?
sims

Developing against HTC libs

I'm trying to figure out how to write an app that uses HTC API's. Specifically I want my app to switch scenes but I can't figure out how to call in to their libraries.
I unzipped Rosie.apk and it is only resources, no java.
it's the classes.dex
Right but how do I import something from a dex in eclipse and build it?
manicmethod said:
Right but how do I import something from a dex in eclipse and build it?
Click to expand...
Click to collapse
no way.
.dex is compiled, not source.
does java have a way to forward-declare classes so I can tell java they'll be there when it tries to run?
I haven't done much (read: any) actual development on Android yet, as I just got my Hero recently (developing solely on an emulator? ewww), but isn't the typical way of interacting with other applications on Android through Intents and Actions?
Browsing through the AndroidManifest.xml file in Rosie.apk, there seems to be a reference to com.htc.launcher.ThemeChooser.action.theme_change - Maybe this would be a place to start?
Ah yes, I'm still in the mindset of calling other peoples interfaces to do things. Thanks for the tip.
trying to figure out what to do with it will be fun, I'm sure
So com.htc.launcher.ThemeChooser.action.theme_change launches the chooser. I need to be able to change the scene under the covers by telling it what theme to switch to, any one have any ideas?
Glad to see that you made a little bit of progress I did some more searching, but this time in Rosie.odex. I found an ACTION_THEME_CHANGE string. Perhaps it could be something like this:
Component Name: com.htc.launcher.ThemeChooser.action.theme_change
Action: ACTION_THEME_CHANGE
Data: ?
Like I mentioned, I'm new to this stuff I'm not sure if there is a way to log or monitor intents (that would sure make this easy, wouldn't it?).
After looking at this more I think I need to hook into the htc settings content provider and see if I can change the settings like that. I found this in the manifest.xml:
E: provider (line=191)
A: android:name(0x01010003)="LauncherProvider" (Raw: "LauncherProvider")
A: android:readPermission(0x01010007)="com.htc.launcher.permission.READ_SETTINGS" (Raw: "com.htc.launcher.permission.READ_SETTINGS")
A: android:writePermission(0x01010008)="com.htc.launcher.permission.WRITE_SETTINGS" (Raw: "com.htc.launcher.permission.WRITE_SETTINGS")
A: android:authorities(0x01010018)="com.htc.launcher.settings" (Raw: "com.htc.launcher.settings")
so according to http://developer.android.com/guide/topics/providers/content-providers.html it looks like the Uri should be:
Uri u = Uri.parse("content://com.htc.launcher.settings");
except when I try that I get an exception saying that is an invalid URI :\
I'm not sure that it would be a setting. I mean, I'm sure you could find an attribute to set, but I don't think the switch would be instantaneous (likely requiring a reboot to show), unless there is something listening for changes to the settings. I could be wrong, of course.
Figured it out:
final Uri u = Uri.parse("content://com.htc.launcher.settings/widget_workspaces");
And the resulting table has
_id, display_name, created, status, and ancestor_id
So I think I can change status and then figure out how to throw a notify
I guess you were right, it looks like the widget_workspaces table has all the scenes available but the status field doesn't do what I assumed it would, rather it looks like it indicates whether a scene was shipped by HTC, is your saved scene or is unsaved.
I was really hoping this would do it because I don't know where to look now.
Well, looking at the ddms, it seems like I am wrong. It looks like ThemeChooser activity will do the swapping itself after you have selected a different scene. So it doesn't look like you will be able to make use of HTC's packages to do the swapping for you. Unfortunately, the only thing I can think that you could do next, is figure out how it is storing the scenes and load it and call all of the loading functions yourself...
Well, I have no way of calling their loading functions so I guess I'm out of luck :X
Check out smali and baksmali to snoop around in the classes.dex.
P
I used ddx1.7 to snoop in the dex files and found the tables and everything they were storing settings in. Unfortunately it looks like they neither store the current active scene in the table nor have an intent to call that will switch it without popping up the dialog.
It looks like what I want to do isn't possible.

Evo front-facing camera only does mirror images

The HTC Evo front-facing camera will not take an image in standard left-right format. I can see the argument for providing a mirror image to the display when setting up a picture (self-portraits), but the result (the actual picture) should not be mirrored.
If using Skype through Fring to video chat (which is really cool, BTW if just a little choppy) the video feed I'm providing to the other party is again mirrored.
It's clear there is a deliberate manipulation of the images going on here, but I can't make out why they would do that. Is there some fix, upgrade, or setting that will clear the problem?
I have not yet rooted my phone, and honestly I'm new to Android (much more familiar with security unlocking and re-flashing WinMo phones up to this point) so I might need the less-than-expert explanation if that's what's needed. ;-)
Thanks!
Rich
I remember a few people talking about this right after google i/o, I think they found a way to fix it, ill look around a bit to try to find the thread. It could be a setting in the camera settings also..
**
Looked around, but couldn't find a solution, but a few people think its a software issue, and has to do with qik and fring. Im not sure though.
nvm, i was wrong

Trying to modify Camera.so to bring back some 1.2 functionality

Been a lot of complaints on other forums about the crippled camera app in bada 2.0 and I'd like to restore some of the fuctionality from 1.2. Perhaps it's not actually possible as all I have seen is the KK5 app brought back to enable front camera, and no 1.2 app for bada 2.0 to restore some of the other missing functions like pause in video recording or editing options. So if this is waste of time please let me know, but I though the main problem was passing the sequrity check which has now been solved thanks to kubika. SO if possible this is the precise scope of the project:
It's not just the ability to pause a video recording, or edit anything after, there's a lot of other stuff too...
NO Image Quality selection
NO countinous/sequance shoot mode
NO sharpness, saruration, contrast adjustment... but still have auto contrast check box... as oppesed to what?!?!?
NO thumbnail or info view for picture when reviewing from cammera app
NO edit fuction for anything from anywhere as already mentioned... though admittedly if I really want to edit a pic I'll probably do it on my PC anyway.
Although a noob at this I do have some expeciance with PC's, and my understanding is that bada apps are in C++ so if one can decompile and recompile the camera app. Then ALL missing functions, with possible exception of editing that probably calls on seperate app, should be easily recoverable in the bada 2.0 camera app. I've actually checked the samsung developer website, and it gives guidelines on how to implemnet many of these functions if whishing to create your own app, so the code should be easy to reinsert even for me in their own app. The one problem may be creating/inserting buttons/tiles for the menus if not already available but simply uncalled, which I hope is actually the case since one can easily recover the record call button.
The main issue is I don't know how to decompile the two apps to read and compare the code, and then recompile them, so could someone please point me to the appropriate program(s) with hopefuly some instructions on how to use them. I think this is something that may be appreciated by many since we can now more easily upload modified apps, and is a relatively simple mod for a noob to atempt... so if anyone can offer some help with that to get me started, it's a project I'd be looking to take up .
innovative ..
liked your idea.
+1
to keep it simple, you can't 'decompile' a binary code to a c++ code, the compiling process is a one-way procedure..

Change default photo names to something more meaningful

Hello,
Does anyone know if there is a way to change the standard name format Google gives images: IMG_20160101_121728.jpg to something else like N5X_01Jan16_12.45.11.jpg? I found one app that seems to do this after the fact here: https://play.google.com/store/apps/details?id=ro.ciubex.dscautorename
I was just wondering if there was another native way in-camera phone to do it? Or is there another app some recommend?
Lastly, does anyone know what the last set of digits represent in the name? I know the first represent the date.
Thanks,
Derek
dereksurfs said:
Lastly, does anyone know what the last set of digits represent in the name? I know the first represent the date.
Click to expand...
Click to collapse
The time, in 24-hour format.
I doubt there's any way to change the name format. You could whip up a shell command to change them.
the standard camera app does not have an option for that.
also, as crachel pointed out, the second set of digits is the time of recording in 24h format.
this way the values are all ordered from largest to smallest (Y/M/D_H:M:S) and therefor will always be in chronological order.
as you see the file names include already everything you want (apart from the N5X part), just in numerical form, and in an order that is at least for machines easier to work with.
if you still want another format i'd be curious of what you would expect from that.
Interesting, when I looked at the last set of numbers, they did not match the timestamp of the file system. So I thought they were just random unique numbers. But if I look at EXIF data on Google Photos, the time looks correct. So, at least they provide more meaningful information than I initially thought. I would still prefer a more reader friendly format like the one I posted above for my own archival purposes. IMG is too generic as I have many cameras along with their associated images. I could care less what Google or anyone thinks is machine friendly. I program for a living and know user experience trumps whatever someone assumes is easiest on a computer. Plus, a computer can read any format since its simply a date pattern. I just prefer another pattern.
I've looked into the last 6 numbers too. In my findings it's the second when the photo/video was taken/started recording. Same for exif. The filesystem contains the second when it was finished written to "disk".
Also sometimes you get _1, _2, ... after that if more photo was recorded in the same second.

Categories

Resources