Related
I'm quite pissed.
Before Windows Mobile 2005, HTC did not make their camera API public, so developers could not make use of the camera.
This all changed with WM2005 and the introduction of DirectShow. For devices released in the first year (since release of WM2005), this meant that one could "simply" use DirectShow to access the cameras.
But then HTC fell back to old habits again:
The HTC TyTN (Hermes) reports only a single video mode via DirectShow: 160x120 at 7.5 fps, which is a joke. Furthermore, trying to access the front camera via DirectShow fails too: It is simply not exposed (enumerated) at all.
The HTC Mteor (Breeze) goes even one step furher: It does report 160x120 and 320x240 (both at 15 fps), but actually both modes deliver pictures at 160x120. For the 320x240 mode, everything seems to work fine: IMediaSample tells that the picture is in that resolution. The memory buffer has the correct size (320x240x12bits), but the image in the buffer is really just 160x120.
Of course I tried several ROM versions (HTC, i-mate, etc.) but no chance.
So, I'm quite pissed. I already tried calling HTC but didn't get very far (which makes sense if these restrictions are on purpose...)
Daniel
No comments on this?
Nobody every using DirectShow?
I guess I also wouldn't do it if I wasn't force to...
Daniel
So with simple words if you want to use WM5 camera api in your application you can not do it in any HTC device
So how did the makers of CoolCamera go about? I was kinda under the impression that it used wm5s camera api, or am I wrong?
I think they've rewritten the interface from scratch. Look into the CPU developers' manuals. Not a small endevour!
V
CPU Developers' manual
Hi Vijay555,
Would you be so kind to post a link to where I can get this manual ?
Thanks in advance!
I don't think anyone wrote anything from scratch nor do I think this has much to do with a CPU manual... the devs at CoolCamera may have *somehow* managed to get their hands on the infamous HTC TyTN camera api... what exactly are you referring to when you mention the CPU manual?
Also, has anyone ever found a location where this api may be available or a means to get it? HTC developer support is non existant.
Eric, what makes you so sure that they didn't write it from scratch? Maybe they did acquire illegally or otherwise HTC's intellectual property, or maybe they just did what other manfacturers do and wrote some code.
Look at the device support - it's not a single device, it's many, across many different CPUs (Intel, Omap, Samsung), across many different camera sensors and support chips. However, implementation of a camera at software level is not impossible: how else do companies sell their sensors and chipsets?
http://www.ovt.com
Ask the sensor manufacturer, they'll give you chips specs, schematics, implementation code and draft driver code.
Then, look up the SC32442A developers' manual and you'll see that it encompasses a camera interface, again with necessary schematics and hardware IO information.
Sure it's hard to write a camera interface, but once you've written one, it gets easier to support others.
V
they need to continue writing then because my camera application frequently fails in that pictures are corrupt, can't be viewed, and the picture review is just black
Sure it's hard to write a camera interface, but once you've written one, it gets easier to support others.
V
Click to expand...
Click to collapse
What kind of effort are we talking about here? Days? Weeks? Do you think this would need to run in kernel space, or we could get away with user space?
This topic has been floating around the forums for a long time now. For as long as chefs been cooking, they’ve been trying to cook their “perfect rom.” Well…unfortunately they can’t do it by themselves. They need some help from us…so this thread is for any and all feedback we may all have as users, to offer to our chefs in order to achieve our goal.
Keep in mind guys, we’re all different people, we all require different things. Let’s keep our thoughts realistic and respectful. We’re use to 3 types of roms….Full, Medium and Light (lite.) Let’s see if we can offer up a somewhat standard model and set of applications for each type of rom.
But not just apps….lets break this down to CE builds..OS tweaks…radio performance…visual preferences…..EVERYTHING!!!!
also (i know this is gonna cause an outbreak!....) if there are any outstanding issues you've been having with all coked roms across the board...feel free to mention....The more we're all aware of something the better the chance it will be addressed!
======================================================================================
((Results and conclusions))
-For the most part, we can all agree certain apps should not be cooked in because they're updated too often.
======================================================================================
((Topics and issues))
--------------------------------------------------------------------------------------------
*well i can't edit the poll...so we'll have to do this the hard way. So we have the "to be cooked or not" apps figured out. Next is the model in which the roms are produced. Like i said before...theres usually 3. Lite, Medium and full. We need to define the roll and specs of each and what they contain. Sound Off
--------------------------------------------------------------------------------------------
At the request of mr.dutty i've added a poll. Im not sure if i can do this, but i'll try to switch it up everyday with a new subject everyday or so.
* = current topic
almost was going to warn you to get some flame retardant clothing at first glance. However after reading a bit more it does not seem to be a bad idea, assuming it can be kept free from garbage. Ill put some thought and contribute what i can but not a bad idea.
A few things I look for in a cooked ROM -
Hardware keyboard performance: We're talking about a device that features a very nice full hardware keyboard, and roms should take this into account. I've encountered roms that have laggy keyboard entry, other weird keyboard entry problems, and some which work beautifully.
Careful which apps are cooked in: If an app is likely to get updated frequently, it's my opinion that it shouldn't get cooked into a rom (unless, of course, it's a PITA to install in the first place). There'd be no point cooking PointUI's Home into a ROM, as it gets updated a lot. Also, the legality of any cooked in App should be considered. For example, I'd love to see a rom that's got Opera Mini cooked in and ready to go as the default browser, which is a lot of fiddling around and hard work, rather than a rom that uses the NOT FREE Opera Mobile.
Screen Rotation Speed: Some ROMs have managed to achieve near instant screen rotation speeds, others have not. It'd be great to know what settings affect this, and cook them in.
Options: I hate Large Start Menu. I love the fact that you can easily turn it off without any side-effects. I love the fact that Quick Menu gets cooked in, but you have the option to not use it (I'm firmly in the "loving quick menu" camp though, at the moment).
Most important: Speed. I really don't feel like this device is performing quite as well as it could do. I think we could get there - I think there's still some exploring to do, and at some point there'll be a major breakthrough.
Maybe this thread is the start of all of that?
Thank you For starting this as this will alow us to find out from different individuals thier own opinions and also from different chefs as to how we can maximise the best performance out of this baby kaiser.
At the moment Im trying different stuffs
I don't know to much about this stuff, but in my last month of looking at these forums.. I think a lot of people use these
- Pocket Core Media Player
- SOme form of Registry Edit
- Task Manager (Detialed one, WTask i think it's called?)
- Pocket Screen
- Office (obviously)
- Note pad (love it)
- Touch Settings
- Query Analyzer (maybe not for everyone..)
- Slide 2 unlock (better to get that yourself probably now that I think about it)
- Schapps advanced config 1.1
- KaiserTweak
- Total Commander looks pretty usefull
- Some sort of FTP program
- I wish there was some app for linking HTC favorites in the cube to their contact record (give you option of calling,e mailing, etc, instead of a quick call)
Not very advanced stuff, but stuff I hav efound pretty usefull that i never knew about.
swtaltima said:
almost was going to warn you to get some flame retardant clothing at first glance. However after reading a bit more it does not seem to be a bad idea, assuming it can be kept free from garbage. Ill put some thought and contribute what i can but not a bad idea.
Click to expand...
Click to collapse
lol no worries man. i got my suit bag unzipped and waiting!
i guess i'll give it a go....
me myself...I prefer a Full rom. but it seems very unrealistic as to what’s in a full rom or not. I’ve been talking to dutty a bit about this and he wanted me to get some ideas and get back to him….so I guess this is the place to get it all together. For those of us with a tilt…we all know how fat the shipped att rom was. But the funny thing is…it wasn’t slow at all! This is what sparked my thoughts. How about…a full rom = a bloated rom! But not bad bloated….good bloated. I’m talking about any and all those little apps we all know and love. Such as….group sms…call firewall…opermini (files provided to set as main browser…I think that should be left up to the user,) tom tom...quick menu….Live search and all other live apps, all HTC current apps and dialers….ect ect. I wanted to include slide to unlock, point ui and pocket cm…but these apps are updated too often to cook in….but non the less would be great for a full rom. I believe the cooks can find a way to make a rom like this work!
For a media rom….pretty much the rom…plus all the htc goodies we’re all used to. And the the rest of the inessentials….things like flash lite…youtube already cooked in....ect ect. It should be kept clean and nice.
A lite rom?....nothing! lol…lite roms are for those of us who like to tinker ourselves or just don’t use a damn thing on the phone…so I think it should be just the os! And call it a day.
I think we need to add a poll of some sort to vote on what apps should be included in each rom so we can observe, study and compare what individuals use in thier roms and what they dont like.
dan13l said:
A few things I look for in a cooked ROM -
Hardware keyboard performance: We're talking about a device that features a very nice full hardware keyboard, and roms should take this into account. I've encountered roms that have laggy keyboard entry, other weird keyboard entry problems, and some which work beautifully.
Careful which apps are cooked in: If an app is likely to get updated frequently, it's my opinion that it shouldn't get cooked into a rom (unless, of course, it's a PITA to install in the first place). There'd be no point cooking PointUI's Home into a ROM, as it gets updated a lot. Also, the legality of any cooked in App should be considered. For example, I'd love to see a rom that's got Opera Mini cooked in and ready to go as the default browser, which is a lot of fiddling around and hard work, rather than a rom that uses the NOT FREE Opera Mobile.
Screen Rotation Speed: Some ROMs have managed to achieve near instant screen rotation speeds, others have not. It'd be great to know what settings affect this, and cook them in.
Options: I hate Large Start Menu. I love the fact that you can easily turn it off without any side-effects. I love the fact that Quick Menu gets cooked in, but you have the option to not use it (I'm firmly in the "loving quick menu" camp though, at the moment).
Most important: Speed. I really don't feel like this device is performing quite as well as it could do. I think we could get there - I think there's still some exploring to do, and at some point there'll be a major breakthrough.
Maybe this thread is the start of all of that?
Click to expand...
Click to collapse
point ui makes for a good debate....the reason i would cook it in is because it comes with its own update client. so even if an older version is cooked in....or an update is available a day after the rom is cooked....you just need to go into update and that will take care of that. but i do agree with the idea of frequently updated apps should be avoided.
the screen roatation is another one....i agree. i've seen it vary from rom to rom even within dutty's camp. maybe the cooks can unite and nail that one down.
I've been using different ROMs over the last month or so and what I normally go for is the lite ROM with all the performance updates. Then I add my own apps to it. From the ROMs that have applications cooked into it I may use 80-90% of it which I find is not good for me and I think this holds true for most, if not all users. Everyone has different taste/needs.
Maybe a ROM with just the OS and performance/optimization tweaks and leave the rest up to the users. They can find the cabs for everything so why bother to cook it in. The other thing with cooking in the apps if is if the app gets an update a new ROM is needed.
Or just cook your own ROM. There's enough info within the forums to make your own ROM and include whatever apps you want.
Maybe the focus should be on optimizing the OS and leave the apps to the choice of the user.
ecltech said:
I've been using different ROMs over the last month or so and what I normally go for is the lite ROM with all the performance updates. Then I add my own apps to it. From the ROMs that have applications cooked into it I may use 80-90% of it which I find is not good for me and I think this holds true for most, if not all users. Everyone has different taste/needs.
I think make a ROM with just the OS and performance tweaks and leave the rest up to the users. They can find the cabs for everything so why bother to cook it in. The other thing with cooking in the apps if is if the app gets an update a new ROM is needed.
Or just cook your own ROM. There's enough info within the forums to make your own ROM and include whatever apps you want.
Maybe the focus should be on optimizing the OS and leave the apps to the choice of the user.
Click to expand...
Click to collapse
I cooked a lot of roms but always stick with the full rom, Reason is i could take out 50mb of programs out of a rom and This doesnt give me that equvalent space and also performance sometimes are un-stable, thats my own opinion.
I think there is a halfway line with how much goodies you can install in a rom to please most people
ecltech said:
I've been using different ROMs over the last month or so and what I normally go for is the lite ROM with all the performance updates. Then I add my own apps to it. From the ROMs that have applications cooked into it I may use 80-90% of it which I find is not good for me and I think this holds true for most, if not all users. Everyone has different taste/needs.
Maybe a ROM with just the OS and performance/optimization tweaks and leave the rest up to the users. They can find the cabs for everything so why bother to cook it in. The other thing with cooking in the apps if is if the app gets an update a new ROM is needed.
Or just cook your own ROM. There's enough info within the forums to make your own ROM and include whatever apps you want.
Maybe the focus should be on optimizing the OS and leave the apps to the choice of the user.
Click to expand...
Click to collapse
all good points...i tend to agree with you. but lets not forget we're dealing with people who dont know how to hard slp...refuse to read through 30 pages of posts or even use teh search feature. so a full features rom will always be needed.
rzanology said:
all good points...i tend to agree with you. but lets not forget we're dealing with people who dont know how to hard slp...refuse to read through 30 pages of posts or even use teh search feature. so a full features rom will always be needed.
Click to expand...
Click to collapse
This is true. For a full featured ROM I think a based ROM might be better versus cooking in many apps. Here's a list that I think can be a good starting point for a base ROM. Some utilities, tweaks, visuals, etc. The rest can be managed by the user.
- Advanced Config
- GPS Test
- HTC Album
- HTC Camera (new version)
- NotePad
- Registry Editor
- Pocket RAR
- Office w/OneNote
- PDF Viewer
- psShutXP
- QuickGPS
- Total Commander
- NetCF 3.5
- ClearTemp
- KaiserTweak
ecltech said:
This is true. For a full featured ROM I think a based ROM might be better versus cooking in many apps. Here's a list that I think can be a good starting point for a base ROM. Some utilities, tweaks, visuals, etc. The rest can be managed by the user.
- Advanced Config
- GPS Test
- HTC Album
- HTC Camera (new version)
- NotePad
- Registry Editor
- Pocket RAR
- Office w/OneNote
- PDF Viewer
- psShutXP
- QuickGPS
- Total Commander
- NetCF 3.5
- ClearTemp
- KaiserTweak
Click to expand...
Click to collapse
agreed. can we all agree this should be a common app set?
rzanology said:
agreed. can we all agree this should be a common app set?
Click to expand...
Click to collapse
Thats almost what I got apart from pdf viewer which i left out for user preference with adobe reader
the most popular apps don't have to be cooked into a ROM. every ROM can be a light or medium with everything else added as shared backup files using Sprite or SPB Backup. in another thread, some folks expressed reservations about my idea of Backup Install Packs, but i still think it could work. and no one would be forced to use them. it's something at least worth trying.
after flashing a new ROM, the ROM cooker or someone else could install demo versions of the most popular apps (HTC apps, Resco, SPB, SBSH, Opera, Palm Messaging, Kaiser Tweak, TCPMP and the plugins, etc.) onto their devices. They can then make a backup of their devices and make that backup available to other users. Then if someone installs the identical ROM, they could simply install the entire backup of those applications to their own devices. Users can keep the apps they want and register them with their own serials. They could then uninstall the rest.
that would be my idea. keep all ROMs medium and lite and let users customize them to full status with backup install packs.
PointUI drove me nuts, was nice and pretty, but in the way. Then again, I don't like the Cube either. Perhaps if I set up the cube I'd use it more, mainly for the contacts though - I don't use WMP or HTC's, I use TCPMP.'
I love the apps Dutty has, especially WKTask with its launcher and battery bar, quickmenu is awesome (without the large setting).
PocketCM has asked that it NOT be cooked in so...
IMHO a ROM should be usable for as much user as possible.
For one person S2U2 is a must-have application, but others just don't like it.
So a stable, fast and clean ROM should be the best for everyone.
Everyone can add his favorite apps, or don't add apps if you don't like them!
Just my opinion. (Of course I always go for the LITE variant, cause I just don't use a lot of apps)
What I would like to see:
Pretty much the default set of apps and tools in the stock ROM. Some of general use like pocketrar could be integrated but not much more.
Larger page pool.
What I absoltely don't want to see:
Too many UI changes, trial versions, bloated battery status apps and such.
Basically I just want the latest radio, OS and default apps all in one.
Stuff that's not likely to get upgrades for quite some time like the flash player and flash lite could preferebly be integrated but other than that I don't like too much tweaking, I just want the latest versions of the default stuff and then I do my own modifications and tweaks from there.
thanks for setting this up!! But i agree should install from CABs
No, They're updated too often to even think about cooking into the rom!
We need 1 stable EMPTY ROM. And cabs what have been edited for working on the 1 stable empty rom.
THIS THREAD IS SPECIFICALLY FOR RESEARCH
So im already thinking of ideas for my next rom when the obvious occured to me, everyone has different needs. So why not try to appeal to everyone instead of just a select few.
And to the other chefs out there. This poll may help you do the same, by finding out what people want.
So here are the questions i am posing to everyone.
1. Fully loaded. This would be a rom that has alot of popular apps cooked in as well as some lesser known apps. This is something that doesnt fit everyones needs, but it also gives some unknown apps a chance to shine.
2. Medium build. This would be a rom that has just the basic's (but still built along popular apps). This would be something that includes media players and the plugins to support it (ie things like the flash bundle).
3. Business edition. This would be a rom that is built for business users in mind. it would be almost completely stripped except would still have office built in. Would also include opera. But the rest would be clean.
4. stripped build. This would be no 3rd party apps and most oem apps ripped from the build. would include ripping out office and java and would give the user the most choices of what they want to install.
I am also going to be working on a way to try to support other languages so that no one is left out. i havent officially started this yet, but will probably start ripping into some of these options this weekend. So i would appreciate input from other chefs out there on their experiences of making a WWE rom compatible with out languages.
Since this is a question that will help everyone and including the chefs, i am going to temporarily stick this.
Personally since I have at&t, my preferences would be:
1. Based on an at&t build.
2. Fully loaded.
3. Bluetooth and MSVC compatible.
But all of that is worthless without stability. The biggest mistake I see most cooks do is to be too quick to come out with the next version of their ROM too quickly. Make sure you listen to your users and tried to get all of the bugs fixed before you start trying to upgrade software and creating more bugs for yourself.
cragordon said:
Personally since I have at&t, my preferences would be:
1. Based on an at&t build.
2. Fully loaded.
3. Bluetooth and MSVC compatible.
But all of that is worthless without stability. ...
Click to expand...
Click to collapse
there we go, that's y I voted for Stripped.
Maybe i should have added another poll option that said:
"Who cares as long as its stable" lol
the_passenger said:
there we go, that's y I voted for Stripped.
Click to expand...
Click to collapse
I guess you have a point I should have thought of that before I voted. Most of the time the fully loaded ROMs don't have much stability. I don't think stripped is the answer either thought simply for the fact that the media player and stuff should be default according to his description stripped doesn't have ANYTHING @all
shogunmark said:
Maybe i should have added another poll option that said:
"Who cares as long as its stable" lol
Click to expand...
Click to collapse
Lol I second that motion.
cragordon said:
I guess you have a point I should have thought of that before I voted. Most of the time the fully loaded ROMs don't have much stability.
Click to expand...
Click to collapse
I tend to disagree with that statement. And i can only speak for myself, however when i do my fully loaded builds this ensures me that most of the popular apps are already working. And honestly i think that a stripped version would be open to more bugs because now your manually ripping everything out and leaves more room for errors. But thats just my personal opinion, this is why i made this poll.
Fully Loaded 2.0
Been reading these threads for the past three/four months. There is so much to offer with each variation of ROM, that I find it hard to keep up. Hasitant at first, but now I find myself flashing on a weekly basis. I agree about stability but having all the hot toys with some space left over and nice speed make all the more joy. Themes and all that can be added later and I haven't found them to lead to bug issues.
Keep doing what yall do... and we'll keep eating. Much respect to the Chefs!!
shogunmark said:
I tend to disagree with that statement. And i can only speak for myself, however when i do my fully loaded builds this ensures me that most of the popular apps are already working. And honestly i think that a stripped version would be open to more bugs because now your manually ripping everything out and leaves more room for errors. But thats just my personal opinion, this is why i made this poll.
Click to expand...
Click to collapse
I can see that point of view also. I have never tried one of your ROMS so I cant say. Well at least not on my kaiser i havent.
I would have to say medium because its a combination have having all the common stuff built in without any hassle to the users while still giving enough room left too customize.
I'd like to say a mixed between
Fully Loaded + Stripped
may sound stupid but hear me out
stripped build. "This would be no 3rd party apps and most oem apps ripped from the build. would include ripping out office and java and would give the user the most choices of what they want to install."
but with recommendations of new apps so it "gives some unknown apps a chance to shine."
o and with office left in
but thats just me
while on the subject wats the difference (in terms of speed and stuff) if you for e.g. have
1. 6.1 rom with office cooked in
2. 6.1 rom with office installed after
i voted business because i like a nice little rom but everything already working out of the box i.e camera, office, and the other basics. In a business rom i don't like the idea of having htc home/hcc (just my opinion) as there are programs better than that and each user should have the option to install/uninstall htc home.
Didn't vote stripped because than the camera is removed and for me all the hardware needs to be functioning on a rom. I love multimedia roms (fully loaded) but i like installing everything to my storage card so thats why i didn't vote for that particular category.
I personally like fully loaded roms best, as long as they retain speed and stability!!!! Business builds are also nice, b/c of customization, but I agree with thesire in that stripped builds are just TOO naked, I need the camera! So if I have to pick just one, I pick fully loaded!
plz cook the WWE as well... dont be bias to att.... ^_^
Business + Flash Bundle - Opera
shogunmark said:
. . .
2. Medium build. This would be a rom that has just the basic's (but still built along popular apps). This would be something that includes media players and the plugins to support it (ie things like the flash bundle).
3. Business edition. This would be a rom that is built for business users in mind. it would be almost completely stripped except would still have office built in. Would also include opera. But the rest would be clean.
4. stripped build. This would be no 3rd party apps and most oem apps ripped from the build. would include ripping out office and java and would give the user the most choices of what they want to install. . .
Click to expand...
Click to collapse
I voted stripped because I like to have as much room as possible to add in what I want and not have to worry about Memory vs. Storage Card, but from your descriptions what I would really like, is Business edition with Flash Bundle, but without Opera. I use Office like crazy, esp. Excel, and I want to be able to use TCPMP, and Java apps.
Thanks for doing this survey!
I posted "Who cares, as long as it's stable" meaning speedy, too I like everything up and running w/ room to spare, but that's a bit of an oxymoron. I installed everything I could to my storage card, figured out what continued to work from there after flashing, and most everything does (but not all...).
Lean, stable, fast works best for me. I load a bunch of Spb stuff on, and run the rest from my card. But I do like playing w/ new toys, so the fully loaded is good too. Medium fits my routine quite well. Even small works. So, who cares? As long as it's stable and fast, I can tweak and trick out the rest.
BTW, I LOVE Death, thanks so much for that!!!
I have been around for awhile, and I have learned so much from this rom flashing fixation that we all have.... Personally I try all of the roms out, then I dump ,em and take the packages I want and keep them in my kitchen , and add what I liked from each rom to my own "reheated" (I am no cook) rom. Sashimi has sure made my life easier!! So it is really hard for me to pick... I like the loaded ones, because I can snag new packages, but I like the stripped ones, so I can add my own packages. Some (most) programs use less memory when cooked than when installed from a cab file. Some programs just seem to run better when cooked, some run better with cab files... You cooks just keep doing what you are doing, because I like them all, any way you cook it!!
And by the way since I might possibly have the great Shogun's attention for a minute... how do you make that tsk file so frickin' black? I think I might have actually been the originator of the glossy black bars.cab (check my BootScreen thread) but the reason I made it was because the .tsk file could not keep the 160 saved in the registry. But your bars are black and have no highlight color... how do you do that?!
Research Poll
I would go for maximum flexibility - which in my mind means we should develop and cook a stripped, stable ROM with all of the bells and whistles as CABs that have been fully vetted and tested for stability, capability AND Viri/malware). The problem is (as is always the case), what is one man's garbage is another's man's treasure. I need a basic phone, bluetooth (hands free automobile work), contacts and calendar. WiFi is extra to me, but not to the next guy and gal. What I worry about is building "fully loaded" ROMs that end up being no different than Tilt's maddeningly bloated original AT&T ROM. Just give me the basics and I will download, cook or buy the add ons I need.
This probably means we need to restructure the poll to individually list the myriad possible and current functions of a Phone/PDA and then let individuals have, say, 10 votes and after a few weeks add up the votes and choose to incorporate into a ROM the top 10 items and all else would be developed as add-on CABs.
Just my $00.02
In real estate it is location, location, location.
In ROMs it is stability, stability, and features.
At least this is true for me, YMMV.
In detail - While I do like playing around with new ROMs, especially when I find new programs that I really like, I use my phone primarily as a business tool (e-mail, calender, etc), and secondarily as an entertainment device. My web surfing from my phone is moderate, and mostly limited to RSS feeds and then the articles behind them. I do use it as a mp3/video player on flights, but not in the car since I have XM, and I have a Tom Tom, so I only use the GPS when I forget that! My other consideration is that I have not found myself even close to worrying about memory space on the Kaiser and I usually install programs to the device for stability purposes.
So... what does all this mean for what I prefer in a ROM? Well, it means that since I can use Kaiser Kitchen, my top preference is a clean ROM that I can easily add packages to. That being said, the packages need to fully functional and stripping them from the ROM shouldn't cause other issues. My previous fave was _Alex_'s 6.0, but i have not been able to find a similar 6.1. So, if you loaded rom folders and OEM and add on package folders, that would be most awesome. Then I can choose what I want to add in (things like office that are not likely to change now, and other programs that I know are version stable) and add the other programs that I have to have but that version change all the time (phoneAlarm)
But - since that is quite possibly harder than just cooking a ROM (and not nearly as rewarding) my preference is either a business or a medium depending on what was in the medium. These are also given bonus points, since as someone pointed out, stripping out certain key applications like the camera, usually leads to stability degradation.
My $0.03 (more than 2 cents worth of typing here)
Hello devs!
I wonder if anyone is interested in/capable of implementing a manual focus feature in android, at least for G1. Hardware-wise, I think it is probably feasible since (the great dev) DZO has already done it for the Kaiser (and I have seen it in action)!
CLARIFICATION EDIT: by Manual Focus I mean controlling the focal length, not just triggering the autofocus. For example, on the Kaiser, dzo has mapped the up/down side-wheel to focus-farther/focus-nearer!
See here the source code commit.
It would be great if the implementation introduced a relevant Java-level API, or extent the current Camera API.
My idea is to use this feature to fix-focus the camera, just a few centimeters away and make barcode scanning faster, not relying so much on auto-focusing. But I'm sure that there are plenty more useful stuff that can be done with manual focus (e.g. inspiring/artistic photo captures).
I'm rather new in android-dev and not experienced enough (yet) to work on the below-Java space, that's why I'm kindly asking for someone else to have a look at it
any thoughts?
have fun,
hypest
This is a great idea. Hope to see someone working on it.
This would be awesome! Espcially for photographers like muah
lapalways05 said:
This would be awesome! Espcially for photographers like muah
Click to expand...
Click to collapse
Photographers use shoddy-quality 3MPx cameras? Is your dSLR in the shop or something?
MattKilla said:
Photographers use shoddy-quality 3MPx cameras? Is your dSLR in the shop or something?
Click to expand...
Click to collapse
No, but it's not in my pocket most or all of the time, either. In a pinch, between 3Mpixel and 0Mpixel, the photographer will usually choose the former.
marxmarv said:
No, but it's not in my pocket most or all of the time, either. In a pinch, between 3Mpixel and 0Mpixel, the photographer will usually choose the former.
Click to expand...
Click to collapse
Yeah exactly. I love my dSLR to death, but I can't always have that beast with me. My phone is ALWAYS with me. I would a lot rather take a quick shot with it than no shot at all.
To the OP. Look in the android source repo at the camera code. Or is the G1 camera drivers in the closed source area? I know the actual camera driver is (thats why 2.X didnt have a camera at first) but is the AF code there too?
As the phone has auto focus i see no reason why manual focus couldn't be coded in.
In fact, i'm surprised no one has done it yet. I remember it being done on my old LG Viewty (that had a fantastic camera) and my SE k750i and was great for the really close up shots that the auto focus can't normally achieve.
Ok I looked at the code. Here is the camera code for the MSM7xxx chips:
http://android.git.kernel.org/?p=pl...=libcamera/QualcommCameraHardware.cpp;hb=HEAD
http://android.git.kernel.org/?p=pl...;f=libcamera/QualcommCameraHardware.h;hb=HEAD
http://android.git.kernel.org/?p=pl...a=blob_plain;f=libcamera/camera_ifc.h;hb=HEAD
If you look at the first one, it does all its autofocus calls thru libqcamera. That is one of the proprietary HTC/Qualcomm drivers. Here is the code:
Code:
status_t QualcommCameraHardware::autoFocus(autofocus_callback af_cb,
void *user)
{
LOGV("Starting auto focus.");
Mutex::Autolock l(&mLock);
Mutex::Autolock lock(&mStateLock);
if (mCameraState != QCS_PREVIEW_IN_PROGRESS) {
LOGE("Invalid camera state %s: expecting QCS_PREVIEW_IN_PROGRESS,"
" cannot start autofocus!",
getCameraStateStr(mCameraState));
return INVALID_OPERATION;
}
if (mAutoFocusCallback != NULL) {
LOGV("Auto focus is already in progress");
return mAutoFocusCallback == af_cb ? NO_ERROR : INVALID_OPERATION;
}
mAutoFocusCallback = af_cb;
mAutoFocusCallbackCookie = user;
LINK_camera_start_focus(CAMERA_AUTO_FOCUS, camera_cb, this);
return NO_ERROR;
}
First off you can see its calling the QualcommCameraHardware library which is libqcamera and then the method autoFocus. I think this is a dead end.
However, for 2.X we reverse engineered the drivers since we didn't have them available. They are open source. We may be able to look at them and get how they use the AF code.
Geniusdog254, thanx for sharing your thoughts, info and findings.
I'm assuming here: if the AF is done in software, even in proprietry drivers, it may indeed be possible to use it by RE it. Best case scenario would be to find functions lingering in there, waiting to be called
I'm wondering though, if the IOCTL's dzo is using are directly triggering hardware "switches", or are they handled in the drivers...
Could you please also share links to the open sourced 2.x driver?
Geniusdog254 said:
First off you can see its calling the QualcommCameraHardware library which is libqcamera and then the method autoFocus. I think this is a dead end.
Click to expand...
Click to collapse
Maybe not. I vaguely remember that the HTC camera app from CM 4.0 or 4.1 would allow you to switch between autofocus and infinity focus. Maybe that's a start?
I found these symbols in the libqcamera.so on my CM g1 (and highlighted some interesting ones):
Code:
af_algo_config
af_algo_execution
af_algo_preview
af_check_aec_settled_cnt
[SIZE="5"][B]af_do_move_lens[/B][/SIZE]
af_done
af_do_process_exhaustive_search
af_do_process_hill_climbing
[SIZE="5"][B]af_do_reset_lens[/B][/SIZE]
af_do_safe_move
af_init_process_exhaustive_search
af_init_process_hill_climbing
af_is_active
[SIZE="5"][B]af_move_lens_to[/B][/SIZE]
af_process_focus_sensor
af_process_lens_move_done
af_process_start_focus
af_process_stats
af_read_process_type
af_read_sharpness
af_start_stats
af_stop_focus
seems to me that maybe there are suitable means for manipulating the lens/focus.
I've attached the whole readelf dump...
I'd love to see this implimented
I think that if with proprietary drivers we can't manually move the hardware, perhaps we can indirectly trick it into focusing closer, thinking that it's "autofocusing" on a close object. Either one of these methods is a bit of a longshot with a proprietary driver, but they are both worth exploring. I'd LOVE to see some control over the focus of the camera, and if we can't do it with the AOSP code, let's look at Hero.... it offers significantly more focus control, with touch-to-focus. I haven't even glanced at the code there, though, so I have no idea. I'm just throwing thoughts at the wall in hopes that one of them will stick.
Here is the code for the opensource, reverse engineered driver for eclair. Have it at, I may look & post my findings:
http://gitorious.org/eclair-camera-drivers
EDIT: Well of course I'm looking at it lol, I can't resist.
Look on line 345 of this page (they're numbered): http://gitorious.org/eclair-camera-...are_msm7k/blobs/master/libcamera/camera_ifc.h
CAMERA_PARM_FOCUS_STEP is defined. It sounds like a way to step the focus forward/backward but I don't know which way.
Also, there is a LOT of interesting things in here, including some that our hardware doesn't support, so take it with a grain of salt (it has flash & all kinds of stuff, pretty much a generic Qualcomm camera driver). Anyways, here are some of the interesting ones;
CAMERA_PARM_ISO, (duh)
CAMERA_PARM_APERTURE, (maybe change aperture speed for better shots?)
CAMERA_PARM_SHUTTER_SPEED, (better response time?)
CAMERA_PARM_HISTOGRAM, (not useful for me, but neat)
CAMERA_PARM_FPS_LIST, (this one is defined under a video section, maybe change frame rate??)
Neat huh?
Anyway, the really cool part is line 405-409:
typedef enum
{
CAMERA_AUTO_FOCUS,
CAMERA_MANUAL_FOCUS
} camera_focus_e_type;
Now I can't tell you what all this means, but I can read & tell you that that does say manual focus where it defines the options for focus type
Also, ISO options are; MAX, HIGH, DEBLUR, 100, 200, 400, 800. There are also some WB settings that we don't have available, here is the full list; AUTO, CUSTOM, INCANDESCENT, FLUORESCENT, DAYLIGHT, CLOUDY_DAYLIGHT, TWILIGHT, SHADE, MAX_PLUS_1. Most of those are available in the 1.5 HTC based camera apps, but twilight & shade aren't.
Actually speaking of the HTC camera, it does almost EVERYTHING mentioned in this code. It misses a few of them, as I said, but it has debanding, WB, brightness. It is just missing the ISO (different from brightness, I promise).
This is about all I know, that its REALLY interesting to look through, and that we should make a camera app that can use all this
Also, just to say in my last post, I DO know what all of those camera terms mean, I'm a photo buff, I just put them in terms that apply to the G1
Bump. Isn't there any other interest in this? I don't have the experience nor the time to do this, but I REALLY want it. I already looked at the code & did a writeup. Surely someone can do it...
Geniusdog254 said:
Bump. Isn't there any other interest in this? I don't have the experience nor the time to do this, but I REALLY want it. I already looked at the code & did a writeup. Surely someone can do it...
Click to expand...
Click to collapse
Hey Geniusdog254,
thanx for sharing your findings! I guess is just a matter of (spare) time. I'm personally (but slowly) trying to get into kernel building (and low-level dev in general) so to try these myself...
An already experienced and interested fellow dev would certainly help if he/she came forward
I am very interested in this as well. Has any progress been made?
lapalways05 said:
This would be awesome! Espcially for photographers like muah
Click to expand...
Click to collapse
If you are a photographer and rely on a phone camera something tells me oyu dont get much work.
My only advice at this point is to change the title of the thread to [Think Tank] camera manual focus... you'll get more devs to glance at it.
I have now researched the various 'ROMs' (actually firmware), and have narrowed the field to four. I'd like input on these. Priorities are (in order):
1. Complete Stability. I've run TomTom on WM5 for 6 years, and outside of TomTom it's a real mess. WM is so buggy I can't use it confidently for anything other than nav.
2. Good Battery. I have a friend who just got an Evo, and he says battery lasts only ~3 hours. I'm sure that's because of the large display, but also I read that several ROMs and apps really sacrifice battery on the N1. One screen I want to have dedicated to some sort of CPU/Mem/Storage monitor, so I can easily check it.
3. Lots Of Cool Features. It seems that video at 720p might be problematic as I gather it's really 3Mp upsampled, and/or it disables the still camera/flash somehow? Kernel optimizations are nice, although "deodexing" is not defined -anywhere-. I'm unlikely to stray beyond the UI built into the ROM, as it could introduce instabilities.
a. CM6 - The Big Kahouna. This ROM will likely be supported for a long time and is likely to integrate the newest kool features over time.
b. MoDaCo - Its thing seems to be stability, although a feature-by-feature comparison with CM6 leaves me confused, much less comparative usability is impossible to determine. Kitchen allows preclusion of G**gle apps.
c. LeoFroYo - The guy seems to know what he's doing, so under consideration. Comes with G**gle apps tho.
d. Kang-o-rama - an innovator whose improvements have been co-opted by others.
e. RoDrIgUeZsTyLe - I like it, but it is clearly very ill given the thread comments. Rejected.
Really? Nobody knows anything about this?
it depends on which phone u have bro, u didnt even specify that