Hi Guys,
I know I'm VERY quiet these days as I continue my personal vendetta against the Gingerbread/ICS hw codecs... but I thought I'd share with you a log sample from the Droid 3.
http://pastebin.com/raw.php?i=aLeLSu6y
That's the entire camera init:
- All of the camera properties are setup
- 6 preview buffers are allocated and registered
- followed by a few seconds of blank preview frames being loaded to/from the 6 buffers
- and then I "back" button out of the Camera UI near the end of the log
You can see the blank preview frames in the log by searching for "Buffer was never with Ducati!! 0x45d65000"
Those blank preview frames are what's holding up the show right now.
I know a lot of what you see me doing is working on RAZR and other projects, but in reality I spend at LEAST 2 hours every night troubleshooting and trying different techniques to get our ICS buffers to be recognized by our Gingerbread hw codec system.
if it isnt one thing its another eh?
is this the ICS camera software or the blur camera?
ssinisterss said:
if it isnt one thing its another eh?
is this the ICS camera software or the blur camera?
Click to expand...
Click to collapse
On twitter he said hes working on both. It's a matter of which works first.
ssinisterss said:
if it isnt one thing its another eh?
is this the ICS camera software or the blur camera?
Click to expand...
Click to collapse
This log uses the ICS camera. You can see some of the ICS stuff being setup in the beginning.
Sent from my XT912 using XDA App
Hashcode said:
This log uses the ICS camera. You can see some of the ICS stuff being setup in the beginning.
Sent from my XT912 using XDA App
Click to expand...
Click to collapse
Hey Hash... Just to ask but did you get the email I sent you a couple days ago? I can send it again if you would like.
Hashcode said:
This log uses the ICS camera. You can see some of the ICS stuff being setup in the beginning.
Sent from my XT912 using XDA App
Click to expand...
Click to collapse
everythingwentbetterthanexpected.jpg
are these previews going to be tied into something that needs to be re written? or are they little independent executions?
ssinisterss said:
everythingwentbetterthanexpected.jpg
are these previews going to be tied into something that needs to be re written? or are they little independent executions?
Click to expand...
Click to collapse
The camera preview frames are processed asynchronously (very fast) by the ducati processor, which triggers a callback to display them to the screen (30 times a second).
So the fix for this would be the same fix that needs to happen for the hw video playback codec where buffers are allocated and handed off to the ducati to decode a Netflix movie, etc.
Hashcode said:
The camera preview frames are processed asynchronously (very fast) by the ducati processor, which triggers a callback to display them to the screen (30 times a second).
So the fix for this would be the same fix that needs to happen for the hw video playback codec where buffers are allocated and handed off to the ducati to decode a Netflix movie, etc.
Click to expand...
Click to collapse
ok, that was making sense, basically as you move forward with fixing the codecs it will get handled versus the memory tiler where you had to take steps back to clean up.
are the codecs also responsible for sound recordings and the hdmi output? i noticed i wasnt able to listen to mms'd soundclips.
Dude...you forgot a comma on line 1278457659308493702761257357 of the module source. Easy fix. LOL! Seriously...let me know if you run out of beer.
I noticed this
I/Thumbnail(1392): Fail to load bitmap. java.io.FileNotFoundException: /data/data/com.android.camera/files/last_thumb: open failed: ENOENT (No such file or directory)
I hope it helps
Droid 1 Rooted (ChevyNo1 0.9MV Kernel, LGB2.6)
Droid 3 Rooted (Hashcode gave me some Ice Cream)
gVibeR said:
Dude...you forgot a comma on line 1278457659308493702761257357 of the module source. Easy fix. LOL! Seriously...let me know if you run out of beer.
Click to expand...
Click to collapse
its really missing a comma?
ssinisterss said:
its really missing a comma?
Click to expand...
Click to collapse
I think he was joking
Sent from my DROID3 using xda premium
yea i got it after looking at the log again
I'm sure you saw this, but it looks like there are too many derefs of the the frame buffer:
02-08 11:21:21.934: E/CameraHAL(221): hardware/ti/camera/OMXCameraAdapter/OMXCameraAdapter.cpp:2945 OMXCameraAdapterFillBufferDone - pBufferHeader->nOutputPortIndex == 2
02-08 11:21:21.934: D/CameraHAL(221): hardware/ti/camera/BaseCameraAdapter.cpp:1226 __sendFrameToSubscribers - Empty Frame Queue
02-08 11:21:21.934: D/CameraHAL(221): hardware/ti/camera/OMXCameraAdapter/OMXCameraAdapter.cpp:3135 OMXCameraAdapterFillBufferDone - sendFrameToSubscribers error: -22
02-08 11:21:21.934: D/CameraHAL(221): hardware/ti/camera/BaseCameraAdapter.cpp:302 returnFrame - Frame returned when ref count is already zero!!
Click to expand...
Click to collapse
Stock D3, eagerly awaiting CM9 cam support. (Thanks for your work!)
Dude...you rock.
Sent from my XT862 using XDA App
I know that I'm not contributing anything here, but I would like to express my gratitude to you.
All of the work that you've put into porting ICS to the Droid 3 is greatly appreciated by so many of us here; and now that the Chrome for Android beta is now out, since it only works on ICS, I'm definitely not going to switch to any other rom on the D3!
Thanks so much for your hard work and for your hasty replies to anyone who asks you questions, and the best of luck to you in regards to the camera!
wgoeken said:
I know that I'm not contributing anything here, but I would like to express my gratitude to you.
All of the work that you've put into porting ICS to the Droid 3 is greatly appreciated by so many of us here; and now that the Chrome for Android beta is now out, since it only works on ICS, I'm definitely not going to switch to any other rom on the D3!
Thanks so much for your hard work and for your hasty replies to anyone who asks you questions, and the best of luck to you in regards to the camera!
Click to expand...
Click to collapse
Yep the Chrome for Android beta is yet another reason I keep banging my head against the hw codecs.
You can do it!
i was screwing around with the CM9 rom from the photon that has a working camera, and putting files into our CM9 last night and the camera UI fired up for me but there was nothing on the viewfinder. i dont even remember what i did since i did a clean flash after
ssinisterss said:
i was screwing around with the CM9 rom from the photon that has a working camera, and putting files into our CM9 last night and the camera UI fired up for me but there was nothing on the viewfinder. i dont even remember what i did since i did a clean flash after
Click to expand...
Click to collapse
lol, try it again maybe? =)
Related
MODDING THE SAMSUNG VIBRANT TO HAVE A FRONT FACING CAMERA (FFC)
DISCLAIMER: It is NOT my fault if this Breaks your Device, or if you screw it up trying to do it. blah blah you know the drill. XDA is also not responsible. This WILL void your warranty. Luckily it is easy to do.
***THIS IS ONLY FOR THE VIBRANT***
Other phones are slightly different inside
Required:
-Compatible rom (Bionix fusion or eugene's froyo or any rom that the dev specifically says ffc compatiable)
-JAC's OC/UV Kernel. Stock kernel will not work, period. Voodoo should also work KK's kernel also does not work.
-An FFC, of course (see below for where to get it)
HOW TO DO IT:
1. Open your phone
2. Remove the 7 screws or so
3. Remove the internal battery cover.
4. Remove your Vibrant camera... it is snapped in under the cam chip.
5. Using Goof OFF! or denatured alcohol or something similar, dip a q-tip in the chemical, and slightly dab the whole where it is to go.
6. Let it sit for 10-20 minutes, and repeat (or if you are anxious, don't wait...)
7. Using something plastic for the safety of the digitizer glass, and scrape out the gunk.
8. Now, definitely let everything dry before putting your phone back together, and MOST definitely before you put the battery in and turn it on. Give it 20-30 minutes to be safe... depends on the chemical used.
I used a flat head screw driver, which is metal, but if you choose this USE EXTREME CAUTION!!
For more info, go to my thread in the General section as I may have missed something/got something wrong in this post. It has been a while since I first did this mod...
Useful tidbits:
If you get force closes when trying to use a the cam, then you did not read instructions. Use the proper kernel.
Banding is present in low light conditions. This looks to be a software issue. Popular belief is that the phone is powering both cameras at the same time when either is called, and is basically confusing itself. This is a work in progress.
Software that is known to work is Fring, various lame mirror apps, etc. Android video calling is only available in Froyo, but I have not tested it recently since Eugene's R3, so I cannot confirm that it working ATM. Tango may also work.
Attached the mach.aries file for those of you that wanna chip in and do some digging. Looks like most of the things we need are in there. Attached a .rar and a .zip file... for some reason I had both? It's been a loooong couple weeks.
Epic camera: thanks to KellyLewis3985 for the dl.
http://db.tt/0DEkw9X
How to Flash:
1. Download the ZIP and put it on the root of your INTERNAL SD Card.
2. Open ROM Manager and boot into ClockWorkMod (DO NOT use Stock Recovery) or boot into recovery the manual way.
3. Navigate down to "apply sdcard: select zip" and locate the .zip file in your internal SD card. Push the power button, navigate down to "YES" and push the power button once more.
4. Let it do its thing, and reboot. First boot *may* take an extra second... Play with new cam app.
To get a cam:
Just got some more cams ordered... should have them by the weekend, so any orders now will start shipping 11/8 in the order they are received.
Go here: http://bit.ly/8ZEPW4
UPDATES:
So, now my desktop is totally dead... makes noises it shouldnt right when i turn it on... have to replace... grrr
-----------------------------------------------------
Got some donations recently, just wanted to say thanks, but the good people here on XDA do not need to pay for one kid's dooschery. I returned the donations back to you. Here is the response sent with the refunds:
Hey man, I appreciate the donation... but the overwhelming support I received the other day on xda was more than enough. This one guy got me down for a night, and you guys picked me up. No one else on xda should pay for his dooschery. Again THANKS
Click to expand...
Click to collapse
I feel that there are some things more valuable than money. I wasn't pissed about losing $30 as I was about the principle and that someone would have the audacity to rip someone off that is trying to help. Again thanks.
-----------------------------------------------------
Well, due to over whelming support, i'm not done. Last batch has sold out, and some new options have presented themselves. Also, with the help of a few others, they are getting mad progress on diving through source code working on the banding issue... Keep following this thread for progress.
-----------------------------------------------------
So.... An ebay user who is also an xda member deliberately screwed me out of a camera and the money for it, so after this batch is gone, i'm done. He never updated his address with ebay or paypal, and of course i sent it to the address i had... and he got ebay to not only refund the full price but keep the fees for the sale and money transfer. Way to say thanks to the guy that got this started... asshole. oh! i get it. he is just out of high school and is a little slow to how the world works. probably because he "works on a farm with 70 dairy cows." <- quote from him.
-----------------------------------------------------
Next batch of ffc cams are coming in for those of you who do not have one yet. New listing, donating some of the process to breast cancer research/awareness...
eBay listing here SOLD OUT
Still settling in after the move and new job... Still w/o internet at my house too... So I am limited in what else I can do right now... Hopefully getting these out will help some of you.
-----------------------------------------------------
Breaking news available via my twitter feed of #vibrantFFC. my original thread here: http://forum.xda-developers.com/showthread.php?p=7941083
-----------------------------------------------------
This thread is for android/software development of the FFC for the Vibrant. Software and ROM support is insufficient atm, so let's get that fixed.
To see how to add the FFC, check this thread: http://forum.xda-developers.com/showthread.php?t=804142
To get a camera check this thread: http://forum.xda-developers.com/showthread.php?t=804122 or hit up my ebay listing here. buying cams from the wholesaler in large quantities to provide them to you individually... Wholesaler had minimum order requirements.
Currently, I have only tested the FFC in JP3 and Bionix. Mirror app works fine, but is useless.
Video calling is doable, but not available in Bionix. Is available in JP3, but is broken.
Have not had a chance to test Tango, but Fring looks to be coded to use the rear camera...
UPDATE: there has been a lot of progress recently. Halfway through reading all of the threads... Seriously have note had much time, but should be able to finish compiling all of the info into this post soon.
-----------------------------------------------------
siirial said:
Currently, I have only tested the FFC in JP3 and Bionix. Mirror app works fine, but is useless.
Video calling is doable, but not available in Bionix. Is available in JP3, but is broken.
Have not had a chance to test Tango, but Fring looks to be coded to use the rear camera...
Any more ideas?
Click to expand...
Click to collapse
Hi, Siirial. Is that Bionix 1.7? I can't get Mirror app to work.
Tango doesn't work yet but I emailed the developers and they said it will be included in their next release
memorito said:
Hi, Siirial. Is that Bionix 1.7? I can't get Mirror app to work.
Click to expand...
Click to collapse
Ok, I am a little confused as to which thread I should be posting in. But here goes.
My FFC wont load in Mirror App using Bionix 1.8 Stock Kernel.
Here is the logcat. http://pastebin.com/biJmEhPr
----------- Edit -----------
Ok, so I finally got around to installing a Rom with a modified kernel. (Specifically Bionix 1.8 w/ Jacs)
The Mirror app now loads the FFC and the image is actually better than the rear cam at the moment.
So, it looks like whatever is going on in the kernel makes a huge difference. Perhaps someone can
take a look at the i9000 and Bell SGS Kernel's.
Posted this in the other thread and it was recommended that I post it here:
Just a thought to kick around some ideas, has anyone looked at this?
http://developer.android.com/reference/android/hardware/Camera.Parameters.html
Looks like there are a few options that could be tweaked, including 'antibanding' for 50 and 60hz
memorito said:
Ok, so I finally got around to installing a Rom with a modified kernel. (Specifically Bionix 1.8 w/ Jacs)
The Mirror app now loads the FFC and the image is actually better than the rear cam at the moment.
So, it looks like whatever is going on in the kernel makes a huge difference.
Click to expand...
Click to collapse
i believe the above it true, i am running bionix 1.8 with the kk kernel, and i cannot get the mirror app to work, will load in the jacs kernel and see the difference.
edit:
i reloaded Bionix 1.8 with Jacs oc/uv without voodoo, and can now confirm the front camera working with the mirror app, albeit grainy
Could not get FFC to work on Bionex 1.7 Stock kernel. Third the kernel info.
paradox4286 said:
i reloaded Bionix 1.8 with Jacs oc/uv without voodoo, and can now confirm the front camera working with the mirror app, albeit grainy
Click to expand...
Click to collapse
Grainy or blurry?
If blurry, you can rotate the focus ring on the actual camera. That's what Cobra did to fix his.
Received camera, installed and confirmed that mirror app works on Bionix 1.7 with JAC voodoo kernel(voodoo activated). Unfortunately, the rear camera problem still exists. Tweaking focus now via outer ring of FFC.
Just installed the new camera. Still on stock JI6 ROM. Banding happens. I recorded some video and can post it if people are interested. Might check if there is any logging that happens when the camera starts up.
memorito said:
Grainy or blurry?
If blurry, you can rotate the focus ring on the actual camera. That's what Cobra did to fix his.
Click to expand...
Click to collapse
ahh gotcha, i'll try that when i get home after work.
when using the rear camera in vignette, the area where the camera chip is gets very warm after not very much use.
maybe the stock vibrant camera data files don't place nice with the i9000 camera
Does any dev have a cam yet?
So here's a thought, can I use sgs tools-prop.editor and change the info there to mimic the i9000? I nelieve it will trick fring (and all other apps) into thinking my phone is an i9000, but I dont wanna brick my **** as my laptop is not with me to odin.
Sent from my SGH-T959 using XDA App
orells said:
So here's a thought, can I use sgs tools-prop.editor and change the info there to mimic the i9000? I nelieve it will trick fring (and all other apps) into thinking my phone is an i9000, but I dont wanna brick my **** as my laptop is not with me to odin.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
DO IT! LOL
Um, I would try it but I am on a Mac... so even worse, should it brick.
orells said:
So here's a thought, can I use sgs tools-prop.editor and change the info there to mimic the i9000? I nelieve it will trick fring (and all other apps) into thinking my phone is an i9000, but I dont wanna brick my **** as my laptop is not with me to odin.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
i dont think fring works on the i9000 either...
I read in another post that a person flashed the captivate Rom on to the vibrant and it worked..everything works good...what if we try to flash the i9000 Rom on to the vibrant...won't.that work perfectly since the settings for the camera is already set up...we should try it.
Sent from my SGH-T959 using XDA App
Video Calls
orells said:
So here's a thought, can I use sgs tools-prop.editor and change the info there to mimic the i9000? I nelieve it will trick fring (and all other apps) into thinking my phone is an i9000, but I dont wanna brick my **** as my laptop is not with me to odin.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I used SGS tools as you suggested and changed the ro.product.model to GT-I9000, rebooted, and the FFC works on the test call. I have yet to try it on Tango, because it is early in the morning and it takes two to tango. (Sorry could not resist)
Thats the ****! Where can I find the info to change it to?
Sent from my SGH-T959 using XDA App
Hey guys,
Just to let you know there is an application out there now to take care of force recalibration of the screen.
When I first got my nook I know it didn't register touch properly, so I ran some commands and it started working fine.
Decided I should make my first app something that helps people, so here you go. Checkout "nook screen recalibrate". It's a simple minimalistic application the re calibrates then reboots
Updated Version 2.0
* Better GUI
* Button to start process
* Lowered MinSDK to support froyo (untested)
Here's the market link.
Helpful since you don't have enough posts to post links yet. But thanks for this app!
Ironically when I go to the link and try to push it to my NC, it says it's not compatible. :X
Fine print mentions that is only works with GB (android 2.3 and above).
yep.. i dont think any rom uses anything lower than that
is it different from this app:
http://forum.xda-developers.com/showthread.php?t=934500
assid2 said:
yep.. i dont think any rom uses anything lower than that
Click to expand...
Click to collapse
The nookie froyo is based on 2.2.
If your software doesn't require 2.3 functionality, can you lower the required API to '7', which is the stock Android API level (2.2/Froyo)?
nolook said:
is it different from this app:
http://forum.xda-developers.com/showthread.php?t=934500
Click to expand...
Click to collapse
Not sure what exactly that application does.so can't comment.
Sent from my Nexus One
byronczimmer said:
The nookie froyo is based on 2.2.
If your software doesn't require 2.3 functionality, can you lower the required API to '7', which is the stock Android API level (2.2/Froyo)?
Click to expand...
Click to collapse
I think it should work. I shall reduce the requirements.
However there is no way to check cause my touch is working perfect now
However I find it performs better slightly if I do this once a week
Sent from my Nexus One
Updated release v2.0
Updated to version 2.0
* Better GUI
* Button to start process
* Lowered MinSDK to support froyo (untested)
Force closes on nookie 2.2
cowballz69 said:
Force closes on nookie 2.2
Click to expand...
Click to collapse
Strange, I had reduced the minimum requirements
I have no other froyo device to test on, let me check once again against an emulator
Sent from my Nexus One
Ok maybe this is in my head, but if I run this every couple nightlies, touch feels slightly better and responsive.
Maybe it's the nightly, maybe the way it interacts, maybe the screen de sensitises over time, maybe it's all in my head
If anyone cares to do some testing, that would be great
Sent from my Nexus One
cowballz69 said:
Force closes on nookie 2.2
Click to expand...
Click to collapse
Let me know if you wanna try this so I can publish to the market
Sent from my NookColor using Tapatalk
This may sound crazy but after running this I think that the screen is actually leases responsive and now shows the "ghost" touches so badly that the on screen keyboard isn't usable. Is there something to do to fix this?
Try cleaning your screen prior to running the application, make sure you don't touch the screen prior to restarting
Sent from my Nexus One using Tapatalk
kruuth said:
This may sound crazy but after running this I think that the screen is actually leases responsive and now shows the "ghost" touches so badly that the on screen keyboard isn't usable. Is there something to do to fix this?
Click to expand...
Click to collapse
same thing on my end. I ended up reflashing the latest cm7 nightly and its back to the way it was
Sent from my NookColor using Tapatalk
That's extremely strange. First time I've heard issues like this crop up. Do you have a screen guard or something
Sent from my NookColor using Tapatalk
For those who would want to try, scews the S2.
But the link from nolook actually fixes it.
nolook said:
is it different from this app:
http://forum.xda-developers.com/showthread.php?t=934500
Click to expand...
Click to collapse
edit: only fixed it for a short time. i'm back with some bad touch.
can you attach the .apk i cant go to market to download!! plsss
Hello there,
My Nexus S is arriving soon. As Nexus S doesn't have 720p video recording, I have an idea to turn our camcorder into 720p.
I tried this to my Wildfire before, and it really work, (480p for wildfire is just lag like hell)
But for Nexus S, I don't have the phone. You guys may try it out, it may not work.
Make a backup before you try it out.
1. Simply take something (e.g. pencil) and shoot it, remember the angle and position that you take the photo.
2. Go to photo gallery and check the file size (e.g. 1243kb).
3. Make a backup
4. Go to other phone's development zone (android phone with 720p and 5MP. e.g. desire s, galaxy s, wildfire s, etc) and download their rom.
5. By using a computer, open the ROM.zip with winrar, head to system/etc/ and extract media_profiles.xml.
6. Make a flashable zip together with the media_profiles.xml and flash it via recovery. [Copy and paste via root explorer may not work]
7. Reboot system and go to camera.
8. Take the things that you used just now and shoot it once again.
9. Go to gallery and check the file size. The file size will be different depending on the media_profile.xml from different ROM that you used. (e.g 2013kb)
10. Then go to camcorder and see whether you have 720p with high res setting.
11. If it doesnt work, try to flash it again.
If you still can't get 720p
1. Use root explorer, go to system/etc
2. Copy the media_profiles.xml into somewhere else that can reach when you turn on USB storage.
3. Copy it to computer and change the number of the resolution into 720p.
4. Turn it into zip and flash via recovery
5. Check the photo size and go to video see whether you have 720p.
Good luck guys.
Hope we can get 720p and I'm not responsible if anything goes wrong with your devices.
As I know, the problem to activate the 720p recording in NS is a little bit harder than change a value in a XML configuration file. Is something related to drivers and a camera harware restriction.
Anyway, we don't lose anything giving this a try.
Give it a try.. change the xml..
Sent from my HTC Wildfire using XDA Premium App
There is an hardware limitation. You can change the value, you will record a fake 720p o worse brake you camera. Are you sure this is secure?
fede91it said:
There is an hardware limitation. You can change the value, you will record a fake 720p o worse brake you camera. Are you sure this is secure?
Click to expand...
Click to collapse
There is no way you can break your camera, and it isn't a hardware issue either.
For nexus one some guy chransingh got 720p video recording
Sent from my Nexus S using XDA Premium App
dario3040 said:
There is no way you can break your camera, and it isn't a hardware issue either.
Click to expand...
Click to collapse
Yes it is. The Nexus S is missing a chip within the phone to do 720p capabilities. This was because there wasn't enough room in the phone because of Super AMOLED + NFC or something of that sort.
http://www.gsmarena.com/nexus_s_in_italy_next_month_no_samoled_but_has_720p_video-news-2251.php The Italy version has 720p. There is also a thread about this when the phone first came out. They broke down the NS and the chip was missing.
zephiK said:
Yes it is. The Nexus S is missing a chip within the phone to do 720p capabilities. This was because there wasn't enough room in the phone because of Super AMOLED + NFC or something of that sort.
http://www.gsmarena.com/nexus_s_in_italy_next_month_no_samoled_but_has_720p_video-news-2251.php The Italy version has 720p. There is also a thread about this when the phone first came out. They broke down the NS and the chip was missing.
Click to expand...
Click to collapse
I can remember reading a breakdown where they said that the chip was present
WIll try to turn into maybe 540p? I saw 720p nexus. I don't think the one I'm getting is 720p.
Sent from my HTC Wildfire using XDA Premium App
melvinchng said:
WIll try to turn into maybe 540p? I saw 720p nexus. I don't think the one I'm getting is 720p.
Sent from my HTC Wildfire using XDA Premium App
Click to expand...
Click to collapse
... Did you not read what I said?
http://www.gsmarena.com/nexus_s_in_i...-news-2251.php The Italy version has 720p. There is also a thread about this when the phone first came out. They broke down the NS and the chip was missing.
Click to expand...
Click to collapse
@dario3040: I saw a picture of it. It's not present in I9020T. Only model is the Italy version of it (it could be in other parts of Europe too)
Edit: Supercurio: @dnaltews Is VIdeo Capture 480p choice due to WebM codec limitations on this SoC? software compressor Maybe?
Swetland: @supercurio clock rate limitation of the SoC. Galaxy uses an external image processing part as a work around. Not enough PCB space in N.S.
zephiK said:
Yes it is. The Nexus S is missing a chip within the phone to do 720p capabilities. This was because there wasn't enough room in the phone because of Super AMOLED + NFC or something of that sort.
http://www.gsmarena.com/nexus_s_in_italy_next_month_no_samoled_but_has_720p_video-news-2251.php The Italy version has 720p. There is also a thread about this when the phone first came out. They broke down the NS and the chip was missing.
Click to expand...
Click to collapse
this is not the true...
read better...
maybe the italian has the chip...
I said it does have the chip. the nexus a didn't have proper 720p a android developer at google had confirmed this. So no you read better because you aren't listening to me. If 720 p was such a big deal then maybe you should of gotten another phone.
simply look on xda, a thread in general had talked about this before.
Sent from my Transformer TF101 using XDA Premium App
Aside from all the arguing.. Has anyone tried this yet?
Sent from my Nexus S 4G
The changes needed for 720p are more than just an xml file, it needs kernel changes/framework/camera/libcamera to name a few.
AdamG said:
The changes needed for 720p are more than just an xml file, it needs kernel changes/framework/camera/libcamera to name a few.
Click to expand...
Click to collapse
True. If it's that easy, why would not other developer do it ?
Just bought this nexus s..
Fell in love right away now Im having seconds thoughts :/
Has there been any advancement as far as almost getting it to work atleast? I searched my ass off.. couldn't find any progress? >:-0
Sent from my Nexus S using Tapatalk
Will get my nexus today. Will root by next week or next month. And will try it out.
Wildfire doesn't have external image processor. But It can be changed to 480p. But only able to shoot 1fps. Wildfire has sux processor
Sent from my HTC Wildfire using XDA Premium App
melvinchng said:
Will get my nexus today. Will root by next week or next month. And will try it out.
Wildfire doesn't have external image processor. But It can be changed to 480p. But only able to shoot 1fps. Wildfire has sux processor
Sent from my HTC Wildfire using XDA Premium App
Click to expand...
Click to collapse
But in our case it just disables the record button.
Sent from my Nexus S using XDA App
BuLLeT_PrOOf_wAlleTz said:
Just bought this nexus s..
Fell in love right away now Im having seconds thoughts :/
Has there been any advancement as far as almost getting it to work atleast? I searched my ass off.. couldn't find any progress? >:-0
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
I have never ever ever seen anyone post in the wrong place so badly ;-)
Totally wrong part of the forum and you posted your question in a thread which has nothing to do with it.
file from sgs XXJVP
I check this - video in "high" quality not available (no reaction on push the REC-button), only 16:9 preview. "low" quality work fine.
usa t-mobile version, cm 7 nightly 109.
xml-file from fresh sgs firmware XXJVP:
UPDATE !! The drivers for the front camera are found ! Check the latest CM9/CM10 ROM's and the drivers should be incorporated !
-----------
This topic is for devs and testers only. Please keep this topic as clean as possible. So only post if you have some new information to share.
The idea of this thread is to gather all the information we have regarding the 10.1v camera so that a developers can port the camera drivers to ICS.
What do we know already?
1. Back camera lens: Sony IMX-073 - CMOS : OV-8820 (technical specification)
2. Front camera lens: Samsung S5K5BBGX - CMOS : OV-9640
3. The Samsung Galaxy S II is using a IMX-105 lens and NOT an IMX-073 lens as we assumed. However, the CMOS chip is identical: OV-8820 in both devices. So in theory we should be able to use the same driver.
4. In HC 3.2 the device drivers are:
camera0=/dev/imx073,back,0,mono
camera1=/dev/os5k5bbgx,front,0,mono
There is a mention of IMX073 in this lib: \system\lib\libnvodm_imager.so
I guess the following files are impacted as well:\system\lib\libcamera.so
5. Honeycomb Sources for our Camera drivers (2.6 kernel):
- IMX073 & s5k5bbgx : https://github.com/cyanogen/galaxy-2636/tree/ics/drivers/media/video/tegra
- IMX073 : https://www.codeaurora.org/patches/quic/la/PATCH_MSM7x30_1969_Sony-IMX073-Driver_20100608.tar.gz
-----------------------------------------------------------------
What needs to be done?
-> Many data structures have changed between HC & ICS. There are many fundamental changes in the way memory is shared for preview/pictures/video, so that will need to be addressed. This is a rather painful process, but it can be done. There is a chance when Samsung releases the ICS rom for the 10.1, that we can use it for the 10.1v. But probably this driver will not have proper support for our camera model. So we can only hope for the best!
UPDATE: The best option is that someone writes a HAL (Hardware Abstraction Lager) module for Tegra 2 SoC's. If my information is correct, that means that the hardware calls to the SoC need to be reverse engineered. Once we have this HAL module, developers can write a wrapper around the old (Gingerbread 2.6 kernel) camera driver. With this HAL module all Tegra 2 devices have a good chance of getting the camera to work. The good news is that there are a lot of Tegra 2 devices, so the community is big and there is a fair chance a skilled developer will develop a HAL for it.
-----------------------------------------------------------------
Attempts to make it work so far
I've tried the Samsung Galaxy S II camera libs (same camera model) and the Motorola Xoom (same Tegra 2 chipset but different camera model) camera libs, but without success.
Error codes are visible in logcat:
- S II libs: signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 5b3804a2
- Xoom libs: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00010ef0
- Old HC libs: isimobile tried with the HC libs without success -> check here
-----------------------------------------------------------------
If you have any information to share, please post in this topic.
Thanks
I've been doing some more digging and I've found this driver source for the IMX073.
Could it be of any use for us?
Just a quick brainstorming:
If the module is the same as in the SII wouldn't it be possible to use the driver from the ICS update for the SII once that's out?
Update: the front camera is actually a 's5k5bbgx'
And the source code appears to be on github already (pushed by pershoot for the p5 device)
So I really think pershoot should take a look at this topic
https://github.com/cyanogen/galaxy-2636/tree/ics/drivers/media/video/tegra
already posted this in the isi ICS thread, but also suited here
In regards to make the camera working maybe pershoot, isimobile or another person with the knowledge on how to do it, XDA member twistedumbrella made the camera work for a lot of HTC devices under ICS. He had no source from HTC, he took the Gingerbread driver, decoded it and modified it so it would work with ICS. Maybe anybody can contact him to ask how he did it, so maybe we can do it too with our Honeycomb driver
Just a thought
ORiZorrie said:
What needs to be done?
-> Many data structures have changed between HC & ICS. There are many fundamental changes in the way memory is shared for preview/pictures/video, so that will need to be addressed.
Click to expand...
Click to collapse
I've asked this in the KANG thread already, but didn't receive an answer. Maybe here it may draw attention of the right ppl
XaMaB said:
Is there a chance this work (with modifications of course) for our cameras?
[WIP] - ICS Camera HAL for 2.6 kernel
Click to expand...
Click to collapse
Psyloid said:
XDA member twistedumbrella made the camera work for a lot of HTC devices under ICS.
Click to expand...
Click to collapse
I have sent him a mail. I hope he's open to that because he's not accepting private messages. In any case, I'm just trying to gather as much information as possible. We'll see if he replies or not....
XaMaB said:
Is there a chance this work (with modifications of course) for our cameras?
[WIP] - ICS Camera HAL for 2.6 kernel
Click to expand...
Click to collapse
Thanks. I have already looked into that code, but it's for Qualcomm SoC's, and not for Tegra 2. We would need a HAL (Hardware Abstraction Layer) module for Tegra 2 instead I guess...
I have done some further testing:
I back ported tegra_camera.c from the nvidia 2639 kernel. tegra_camera.c is being called from imx073, in a couple of places. The driver seems to be loading ok and if I open the camera app, it does not FC anymore, but the device "hangs". I have to forcefully reboot it to get to work again.
What it looks like is that the problem is libnvodm_imager.so. That is what we found earlier that that library have hardcoded values for the camera. The lib we are using is looking for OV5640 camera which it the transformer (TF101) camera. So unless we can get a working libnvodm_imager.so. I think we are stuck. I tried to hexedit the values in the lib to imx073/s5k5bbgx, but did not make any difference.
Comments suggestions are welcome.
Here is a portion of the logcat:
Code:
D/NvOsDebugPrintf( 112): +NvOdmImagerOpen (202):ImagerGUID= (0), Handle=0x702134
D/NvOsDebugPrintf( 112): NvOdmImagerOpen (203):Compiled at Feb 21 2012 21:26:41
D/NvOsDebugPrintf( 112): NvOdmImagerOpen (205):prop: force.camera=Unknown
D/NvOsDebugPrintf( 112): NvOdmImagerOpen (251):ioctl failed!
D/dalvikvm( 1166): GC_FOR_ALLOC freed <1K, 7% free 8489K/9095K, paused 22ms
I/dalvikvm-heap( 1166): Grow heap (frag case) to 8.770MB for 331516-byte allocation
D/NvOsDebugPrintf( 112): +SensorYuv_Open (362):compiled at Feb 21 2012 21:26:41
D/NvOsDebugPrintf( 112): +check_project (31):
D/NvOsDebugPrintf( 112): check_project (33):prop: ro.epad.model=Unknown
D/NvOsDebugPrintf( 112): -check_project (42):undefined...!
D/NvOsDebugPrintf( 112): +ParsingCustomCap (156):
D/NvOsDebugPrintf( 112): -ParsingCustomCap (171):
D/NvOsDebugPrintf( 112): SensorYuv_Open (386):Custom Cap not found, use built-in one.
D/NvOsDebugPrintf( 112): -SensorYuv_Open (397):
D/NvOsDebugPrintf( 112): +SensorYuv_GetCapabilities (422):
D/NvOsDebugPrintf( 112): -SensorYuv_GetCapabilities (427):
D/NvOsDebugPrintf( 112): NvOdmImagerGetCapabilities (535):identifier:OV5640
isimobile said:
I back ported tegra_camera.c from the nvidia 2639 kernel. tegra_camera.c is being called from imx073, in a couple of places. The driver seems to be loading ok and if I open the camera app, it does not FC anymore, but the device "hangs". I have to forcefully reboot it to get to work again.
Click to expand...
Click to collapse
https://github.com/cyanogen/galaxy-2636/blob/ics/drivers/media/video/tegra/imx073.c
If I look in the imx073.c file I don't see those references you mention apart from the header file reference 'media/tegra_camera.h'.
isimobile said:
What it looks like is that the problem is libnvodm_imager.so. That is what we found earlier that that library have hardcoded values for the camera. The lib we are using is looking for OV5640 camera which it the transformer (TF101) camera. So unless we can get a working libnvodm_imager.so. I think we are stuck. I tried to hexedit the values in the lib to imx073/s5k5bbgx, but did not make any difference.
Click to expand...
Click to collapse
The photosensor for s5k5bbgx is OV9640 (see OP -> it's mentioned in the header of s5k5bbgx.c)
The photosensor for imx073 is OV8820 (see OP)
Simply hexediting the values in the lib won't work. Reverse engineering implies that you disassemle the code, edit it (assembled language) and then assemble it again.
What we need is a HAL module for Tegra 2 SoC's, When we have that HAL module porting the device driver should be more straightforward (at least if you're a C adept) because we can reuse the old driver.
ORiZorrie said:
https://github.com/cyanogen/galaxy-2636/blob/ics/drivers/media/video/tegra/imx073.c
If I look in the imx073.c file I don't see those references you mention apart from the header file reference 'media/tegra_camera.h'.
The photosensor for s5k5bbgx is OV9640 (see OP -> it's mentioned in the header of s5k5bbgx.c)
The photosensor for imx073 is OV8820 (see OP)
Simply hexediting the values in the lib won't work. Reverse engineering implies that you disassemle the code, edit it (assembled language) and then assemble it again.
What we need is a HAL module for Tegra 2 SoC's, When we have that HAL module porting the device driver should be more straightforward (at least if you're a C adept) because we can reuse the old driver.
Click to expand...
Click to collapse
Have a look in camerafw_file_cmd_show: tegra_camera_enable_vi, tegra_camera_enable_csi
Send from my GT-P7100
Good job guys... keep up the great effort. Remember you're not making a thousand mistakes, just finding a thousand ways not to do it
Sent from my Inspire 4G using XDA
I say: drop all efforts to get a working rear camera on the Tab! I can live without that one. The front one, on the other hand, is crucial for everything from Skype, to Google Talk, to any number of other video chat apps which are way more practical on a tablet than using it as a huge camera. Front-facing first; rear-facing second
Great effort by all though; I love you guys! No homo
Just a quick note; If camera starts in the kernel, but doesn't start in Android itself, it's very likely that you will have to do some modifications to libcamera.so so that Android won't produce that error you have on the original post. I do not know exactly what the mods are, sadly, I wasn't fast enough on stalking the repositories
PookiePrancer said:
I say: drop all efforts to get a working rear camera on the Tab! I can live without that one. The front one, on the other hand, is crucial for everything from Skype, to Google Talk, to any number of other video chat apps which are way more practical on a tablet than using it as a huge camera. Front-facing first; rear-facing second
Great effort by all though; I love you guys! No homo
Click to expand...
Click to collapse
QFT
The front camera is far more valuable than the rear. If I can find some time, I may start poking around with getting this working too. I hate the idea of rolling back to stock just to use Skype.
i hate to sound like a noob since i am not a dev at all, but has anyone tried the cm9 galaxy s 2 libs since they got the camera/camcorder working properly? this has just happened in the last few days. maybe something has changed since then.
insaneturbo13 said:
i hate to sound like a noob since i am not a dev at all, but has anyone tried the cm9 galaxy s 2 libs since they got the camera/camcorder working properly? this has just happened in the last few days. maybe something has changed since then.
Click to expand...
Click to collapse
Galaxy S II has both a different camera and SoC, so its not of much help.
GazaIan said:
Galaxy S II has both a different camera and SoC, so its not of much help.
Click to expand...
Click to collapse
well, the lens is different yes, but the cmos chips is the same, which is what counts, however the soc is is different... very different lol.
insaneturbo13 said:
well, the lens is different yes, but the cmos chips is the same, which is what counts, however the soc is is different... very different lol.
Click to expand...
Click to collapse
Yeah, and if what I understood from KANG is correct... before you can do ANYTHING driver related you need to be able to communicate with the SoC. So I'm afraid that is the biggest showstopper at this time.
About the front/rear camera I think that one might work once there is an ICS update for the GTab 10.1. Normally that cam should be very similar if not identical.
ORiZorrie said:
Yeah, and if what I understood from KANG is correct... before you can do ANYTHING driver related you need to be able to communicate with the SoC. So I'm afraid that is the biggest showstopper at this time.
About the front/rear camera I think that one might work once there is an ICS update for the GTab 10.1. Normally that cam should be very similar if not identical.
Click to expand...
Click to collapse
Question is, does Samsung love us enough to get us an update
XDA member AuxLV is working on an app called Tabletizer. It's an apk that does the conversion by creating a flashable zip file on your device which you then flash in the recovery.
[APP] Tabletizer Alpha 4 (2013.03.02)
I've tried this one and it works well.
There are some other roms/patches that do have a Tablet UI option:
[PATCH] True Tablet UI (Apps+GUI) w/o DPI Change for Stock & CM10 - Update Oct11
[ROM][WIFI][CM10.1][Feb27] BeatMod CrystalClear v2.1 | Aroma | TabletUI | Sound Mods
PARANOIDANDROID 3.0 (4.2.2) | Only Rom on Android capable of Hybrid mode
Please add links to other solutions and projects or status updates, and keep general talk about TabletUI in this thread unless new a new one is created.
I updated my G+ with current status.
Sent from my Nexus 7 using Tapatalk HD
I am very interested in this as my posts in the CM 10.1 "official" thread should have made clear, but being as I'm not a developer I can't do much but sit around and hope someone with more talent than I have is capable of making it a reality. I understand that Google has decided to "move on" and just flat out give up on the tablet UI - which is odd considering it's a tablet device we're using with the Nexus 7 and not a damned phone, even so - but that's their prerogative I suppose.
For the moment I'll use Paranoid Android 3.0 when aaron is able to get a 4.2.2 build out, he's currently working on it as noted in his thread last night but it's not available just yet. I was using PA 3.0 with 4.2.1 and found it very useful for many reasons, the tablet UI functionality being the primary one.
The Nexus 7 I have is actually damaged (hence it being a $25 craigslist special) with a crack in the upper right hand corner where the previous owner had dropped it - there's a triangular area in the upper right hand side that doesn't respond to touch anymore, kinda funky how it lines up but, with PA and that tablet UI functionality it's not a real issue because I can hold the menu soft key and it'll bring up the settings for any given app anyway.
If I have to choose a specific ROM I tend to go back to "pure" CM whenever possible so, if someone can actually get the tablet UI functional in 10.1 (based on 4.2.2 at this point) I'm all for it. If not, then PA will fill the ROM role for me.
I remember seeing them introduce Honeycomb and was blown away with the interface layout and the functionality, and now they've basically just swept all that out like yesterday's garbage and I really wish I knew why. It's like seeing demos of versions of Windows that never end up being actually made into workable products - there are videos on YouTube of test versions of Windows Longhorn which was scrapped and then reborn as Vista and some of the stuff they do in those Longhorn videos is beyond cool, seriously.
Android showed some "beyond cool" capability with Honeycomb and a proper tablet UI, now it's like that stuff was a mistake or something and I completely disagree on that respect. But then again, I do understand Google's attempts at unifying the Android interface across all devices instead of having something for phones and then something for tablets, what now with ChromeOS trying to gain traction as well.
Suffice to say if someone can make it possible with CM then fantastic, if not then I'll make do with whatever I suppose. Would be nice, however...
I just want to make sure my app is of top quality, I failed two updates for LagFix when I wanted to make them quick, that will never happen again.
Sent from my HTC One X using Tapatalk 2
Your efforts, even if it proves not really possible (because of something Google has changed, etc), are greatly appreciated.
Any updates AuxLV?
Sent from my VS920 4G using Tapatalk 2
One small thing left - to create a proper updater script, will upload later today.
Sent from my HTC One X using Tapatalk 2
AuxLV said:
One small thing left - to create a proper updater script, will upload later today.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Looking forward to it.
AuxLV said:
One small thing left - to create a proper updater script, will upload later today.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
My hero!!!!
Well done on alot of good work.
I will have to be honest that I like the quick settings menu in combo with the notifications drop down. And I like the way the navigation bar is by default.
But the thing I like about the Honeycomb style ui is the settings menu. I guess compared to stock Jellybean, that might be the only thing I like alot (Just to be clear, I did not dislike other aspects). The Honeycomb notifications tray just seemed to add additional screen pressed for functions now contained within the quick settings menu.
But, still. Good job changing the ui. Its not an easy thing to do. I tried to do some changes for personal use, and seemingly small changes completely crash the system to an unusable state.
Sent from my Nexus 7 running CM10.1 (JB 4.2.2) using XDA premium app
Hey aux, where will you be posting this app? Id love to test it
First alpha as promised!
Before using: BACK UP!!!
Using:
Launch app
Click "Run tabletizer"
Wait for a few minutes
It will create update.zip file in /sdcard/data/tabletizer/temp
Flash this update.zip from CWM/TWRP recovery
Reboot
App is quite unstable at the moment, because recompilation process eats a lot of RAM and it crashes often when runs out of memory. I'm rewritting smali tool to be more friendly, but it will take some time to finish.
Thank you for your app! I ran the apk, it started the process and got to these last 3 lines:
Services are patched!
Can not recompile.
Compilation exception.
Now it hasn't done anything for 10 minutes. I'll wait a bit longer and try again.
Sent from my One S using xda premium
xparagonx said:
Thank you for your app! I ran the apk, it started the process and got to these last 3 lines:
Services are patched!
Can not recompile.
Compilation exception.
Now it hasn't done anything for 10 minutes. I'll wait a bit longer and try again.
Sent from my One S using xda premium
Click to expand...
Click to collapse
Yep, it does not work, another bug Don't wait, close it. Thanks for report. Will try to figure it out tommorow, it's 23:50 already here and I want to sleep
But at least I've found a way to deal with RAM. A temporary fix which will do for alpha.
Awww thanks so much! Looking forward to your next update!
Sent from my Nexus 7 using Tapatalk HD
Gotta admit I'm really excited for this
opz187 said:
Gotta admit I'm really excited for this
Click to expand...
Click to collapse
+1.........................:good:.........................
Alpha 2 will be uploaded later today when I get back home. Hopefuly it will do what it should After that impatient guys will be happy with TabUI and careful guys will wait for me to rewrite dex (de)compiler to be faster and much more stable.
AuxLV said:
Alpha 2 will be uploaded later today when I get back home. Hopefuly it will do what it should After that impatient guys will be happy with TabUI and careful guys will wait for me to rewrite dex (de)compiler to be faster and much more stable.
Click to expand...
Click to collapse
I'll update the op with a link when you post it. You may want to open a new thread in dev or apps section.
Sent from my Nexus 7 using Tapatalk HD
AuxLV said:
Yep, it does not work, another bug Don't wait, close it. Thanks for report. Will try to figure it out tommorow, it's 23:50 already here and I want to sleep
But at least I've found a way to deal with RAM. A temporary fix which will do for alpha.
Click to expand...
Click to collapse
You still gonna drop alpha2 tonight?