Related
I had a hard time finding this figured I'd share it. It fcs when you switch cameras otherwise it works good. Clear cache before flashing.
http://db.tt/32WQmGg
Sent from my LG-P999 using XDA App
Very nice. I'll throw it up for when I need to flash GAPPS. Is this the full GAPPS or just the GTalk?
*Looks like the full monte.
Full gapps
Sent from my LG-P999 using XDA App
azrowdydog said:
I had a hard time finding this figured I'd share it. It fcs when you switch cameras otherwise it works good. Clear cache before flashing.
To clarify, does it initially open with the front camera so that you can use gtalk video, or does it open with the back camera so you can't use the gtalk video chat feature? Thanks!
Click to expand...
Click to collapse
Before you install that version of gapps read the last part of this. Bottom line is 0503 gapps is not compatible with Tegra devices. http://goo-inside.me/gapps/
Not working...help?
Hey guys. I installed the latest gapps install as posted above, but google talk seems to not be any different. No video icon is displayed for contacts that I know have video capability and the Settings menu doesn't reflect having any video related options. I have a friend who owns a Nexus S with stock Gingerbread and can use google talk + vid. I also have a separate google account with a web cam. In both scenarios, I can see the other person and we can hear each other fine, but the recipient can't see me. I can see myself in the self-viewer window, so that must mean the video data isn't being sent right. Any ideas?
I'm using Cyanogenmod 7.1.0 RC1 Experimental ROM on a MyTouch 4g (HTC Glacier).
EDIT: NVM. I installed 20110613. I automatically went with the latest. Either my phone isn't supported for one reason or another or the gtalk + video isn't included in the latest gapps package. Am I missing something/confused here?
The newb needs to update his post. GTalk works, but video is not supported.
unrman said:
Hey guys. I installed the latest gapps install as posted above, but google talk seems to not be any different. No video icon is displayed for contacts that I know have video capability and the Settings menu doesn't reflect having any video related options. I have a friend who owns a Nexus S with stock Gingerbread and can use google talk + vid. I also have a separate google account with a web cam. In both scenarios, I can see the other person and we can hear each other fine, but the recipient can't see me. I can see myself in the self-viewer window, so that must mean the video data isn't being sent right. Any ideas?
I'm using Cyanogenmod 7.1.0 RC1 Experimental ROM on a MyTouch 4g (HTC Glacier).
EDIT: NVM. I installed 20110613. I automatically went with the latest. Either my phone isn't supported for one reason or another or the gtalk + video isn't included in the latest gapps package. Am I missing something/confused here?
Click to expand...
Click to collapse
did ya read the qualifier on that page...."but does not include the new Google Talk with video chat due to there being no compatible library available for non-ARM7 and non-neon board devices, from Google or another OEM. This package should work on all 2.3.4 ROMs, and has the latest Android Market update in it, which includes in-app purchase support."
Not sure if thats the answer you're looking for.....
Now that Moto Atrix 4g finally has 2.3.4 (first Tegra 2 phone) maybe we can get a hold of GTalk 2.3.4 w/ Video chat support
Link is broken
You need 20110603 GAPPS and then flash a fix. Its in the Apps thread.
MIUI has it working out of the box btw. Tested it before I left this morning.
LG G2x - 2.3.5 MIUI Love
Asus TF - Custom 3.2
Hi all,
Somebody asked me to modify Vtok to use more FFCs for froyo so here it is. Although I don't really use this app, I've tested it and is working fine on my Atrix's FFC.
There are some issues I've found on the app but for now, I'll keep it this way. Will work on improving it when I get more time
List of supported FFCs should be the same as my Skype and Yahoo mods.
Unzip the .ZIP file first and install the APK file into your devices.
I have installed it on my atrix too. I can make phone to pc and phone to phone audio/video calls easily. The main issue that I have is the draining of the battery.
If you can improve on it, that would be really great. Waiting for the updates.
Keep up the good work.
Hi guys,
As you know, our i9003 is not able to make video calls (3G or wifi). In Gingerbread doesn't work in any app, and only Tango and only in Froyo. As anyone port gtalk with video calling for our devices? Or mod some app like Skype, Tango, Fring or Ooovo to have video calls?
For a long time I have contacted a lot with the support of Tango, Fring and ooVoo. I have sent videos, many logs showing the issue, all they have asked me. But they aren't able to fix the issue. Even look at ooVoo email:
"Hi Unkalo,
Due to Ongoing Problems With This device is going to be it removed from the market. I'm sorry We Were Unable to get it working for you.
ooVoo is also available on PC and Mac, I hope you can join us there.
Best,
Roberta "
No comment. Incredible, Instead to try to fix the issue, they remove the app from our market...
Please help, together we can do it.
Yes developers please add this feature , I just waiting patiently for this feature.
I have 3 android devices and I researched and found not too many phones have this feature like s2 or sensation, none of android devices can full utilize both cameras i.e. video call over 3g and video gtalk.
We have 3g video call even I9000 dont have this feature but only thing lack is gtalk video chat.
Please develop video gtalk app.
Please..........
Sent from my GT-I9003 using Tapatalk
Video call over 3g surely works on our phone I had tested long ago on froyo 2.2.1 (xxkb3)
On wifi using VOIP it does not work so basically skype/gtalk cant be used unless they are modified for our phone.
With wifi, only works Tango and only in Froyo 100 % tested all the options. I tried mods of Skype, and doesn't work, always black screen in ginger.
Same with me.. Skype, Yahoo, Paltalk video class not working on I9003 Gingerbread,
i can see others. but they cant see me. just black screen on skype.. but. in Yahoo during video calls on Device gets reboot.. In Paltalk. video works in room. but if auto rotate is ON . itz just crashing..
how can we get video class fixed on our device ? lets shout on skype n Yahoo or to Samsung ?
thanks
Vedio call by GSM operater?
Can any body tell me that is there any problem with Video call by GSM operator with GT-9003 (in both Froyo and GB)?
techindia2010 said:
Can any body tell me that is there any problem with Video call by GSM operator with GT-9003 (in both Froyo and GB)?
Click to expand...
Click to collapse
@techindia the problem isn't videocalling by GSM operator, the problem is to make "free" videocalls using WIFI or 3G. All the apps (Gtalk, Skype, Fring, Tango, ...) have problems with our front cam (black screens, green flickering, rotation and zoom issue,..)
In the last days, I have been working with Fring and Tango support. They send to me mods of Frings and Tango, and I reported them the results, and I sent them logs, videos, and screen captures showing the issue, and they sent me a new version, I tried, and started over with logs, videos, screenn captures ...
Today, the results are:
Tango: In Froyo Ok. In gingerbread, fixed black screen, fixed rotation issue, and tango developers are working on zoom issue and audio issue.
Fring: In Froyo I think that green flickering issue, but I haven't been able to prove because I'm on Ginger. In Gingerbread: Fixed black screen, fixed rotation issue, fixed upside down issue, and fixed zoom issue. In Gingerbread after fix rotation and zoom, appears green flickering again. Fring developers are working to fix it. But they are working on it, and that's good news for our i9003, as developers tend to ignore our device.
Skype and oovoo. KO in Gingerbread (black screen) and KO in Froyo (green flickering).
Gtalk video: KO. If someone could carry a gtalk mod to our devices, would be the best of news.
I shall tell you of new results.
To see what's new today
Fring support sent to me this:
"Hi.
Our developers suspect it's a device driver issue or memory issue.
We'll keep Investigating .. I hope we find something.
I really want to thank you for your Enthusiasm and help, Could we have got so far Without it. "
Drivers or memory problem ....??
In addition, ooVoo, launched yesterday a new update, I've tried a video call to PC (I couldn't try with another i9003) and for the first time, the video works perfectly! Only with the audio I have a problem, that my voice is very very distorted ... You can try oovoo and report here your results. I'm ginger, would be nice if someone with Froyo can tell us how it goes.
Come on guys!
Does skype video call works ?
New mail from Fring support:
"The problem is we don't have the device here…
I hope that the build I'll send you (I don't have an ETA yet, the devs are on it) will reveal the correct resolution.
So far we tried 640*480 that caused the zoom issue and 320*240 that caused the flicker issue."
Anyone know how to solve the problem? Some developer can help to solve this problem with our i9003?
I really like where this is going. With online video chat our device will truly be complete.
Hi Guys,
Fring support send to me a new version, and no green flickering, no audio issue and no rotation issue, only zoom issue. Fring uses 640x480 resolution (native resolution of front cam), with 320x240 no zoom issue but appears green flickering. We can almost make video calls. I show a picture:
But using the camera's native app, using the front camera on froyo, the preview image was similar to when there is green flickering at Fing (320x240):
but after upgrading to gingerbread, the preview shows different, like full screen . I send you pictures so you can get an idea:
I think that here comes the problem of zoom, can be caused by this.
This week will prove this version of fring with my girlfriend (she has a Froyo i9003) and see how it works.
But if successful, someone could port drivers or libs of Froyo, to work well in gingerbread?Any developer could try that?
What do you think about it?
Please respond any developer
After upgrading 9003 (European, XXKPN) in GB, I observed that Hardwar H.264 decoder crash some time and that time I even cannot see anything in camera application.
Do any one face same problem? I need to restart mobile for that.
@Unkalo: could you please load that Mod for fring.
I am on KPQ, and camera app work well, I think you need reflash twice.
This version of fring generates a fring.log constantly and it's occupy much space on the sdcard, for this reason it is best to wait to take out a new release on the market soon.
well i got "XXKPN" via Kies, so i can not reflash ones again.
is there any way to reflash it?
Via odin... Please read this thread...
http://forum.xda-developers.com/showthread.php?t=1133787
You only need download XXKPQ (lastest european 2.3.6 official fw):
http://forum.xda-developers.com/showthread.php?t=1004647
Unkalo said:
Hi Guys,
Fring support send to me a new version, and no green flickering, no audio issue and no rotation issue, only zoom issue. Fring uses 640x480 resolution (native resolution of front cam), with 320x240 no zoom issue but appears green flickering. We can almost make video calls. I show a picture:
But using the camera's native app, using the front camera on froyo, the preview image was similar to when there is green flickering at Fing (320x240):
but after upgrading to gingerbread, the preview shows different, like full screen . I send you pictures so you can get an idea:
I think that here comes the problem of zoom, can be caused by this.
This week will prove this version of fring with my girlfriend (she has a Froyo i9003) and see how it works.
But if successful, someone could port drivers or libs of Froyo, to work well in gingerbread?Any developer could try that?
What do you think about it?
Please respond any developer
Click to expand...
Click to collapse
Looks very promising It would be awesome if you could upload the apks so that we could test it and give you our feedback as well
Ok, here you have, but beware the fring.log, it is getting bigger and bigger. Can you tell me how it works in Froyo?, in ginger only zoom issue, but and in Froyo? Feedback please.
If you want you can add me as Fring friend, my fring user id is: unkalo
http://www.multiupload.com/QJLKLT66PJ
No one has tried this new version?
With the new version of ooVoo, at in gingerbread, video usually works well (if you have black screen, switch off cameras and it will works well, and if not send picture, hang up video call and call again), the only problem is with the audio, is heard very distorted and not understand anything. To fix it, up or down the volume of the call volume using the physical keys on the device, and that will fix the audio issue.
For now is the best we have so far, almost 100% functional.
PD: not always works well, have many bugs, this version of oovoo isn't estable for our i9003
Hi - NaN (not a noob) to software and hacking but new to this device.
I have a rooted TF101 and wonder if anyone's hacked the device so that the front camera becomes the rear and the rear camera becomes the front.
Really just curious before I go ahead and brick my device. I'm thinking about mv /dev/ov5640 and /dev/tegra_camera but that sounds far too easy (and dangerous)...
Why would You be interested in swapping the cameras anyways? Seems to be a biit pointless to me as every app ive used with cameras it had support to use front or back.
Sent from my Transformer TF101 using xda premium
I agree
kenshin1388 said:
Why would You be interested in swapping the cameras anyways? Seems to be a biit pointless to me as every app ive used with cameras it had support to use front or back.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
I agree to this, there is no point to make the change.
Well for starters Opera 12, which includes support for getUserMedia() WebRTC extensions uses the first webcam it comes across, the rear. If I wanted to even make a mock up of a video call I would need the front camera (granted this is only good for the lab, not production).
But really I was trying to understand how the underlying media device capability works. If you simply exchange using mv /dev/mi1040 (the front camera device) and /dev/ov5640 (back camera) then it goofs the images to any app that uses cameras.
There must therefore be other layer(s) determining device capabilities, codecs, etc.
There's a file /etc/nvcamera.conf but that only seems to affect the main camera app. I swapped 1 and 0 and front and back tags, although admittedly haven't yet swapped the device ID whilst leaving the front/back tags the same.
And there's a whopping /etc/media_profiles.xml defining all the camera capabilities.
Do I need a reason? Isn't anyone even just curious doing something to push the device and learn more about the platform???
There was a point where Yahoo IM would use the back camera (when it was avaiable native to the TF). There was a member "droidx" he modified some files and got the front camera working with it. You're better off looking at modifying files as oppose to rewiring cameras.
More info here
http://forum.xda-developers.com/showthread.php?t=1087769
How to swap the cameras so Opera 12 uses front camera for getUserMedia()
Ok, here's how I did it.
Essentially you only need to swap the tags 'front' and 'back' in the file /etc/nvcamera.conf
The change is permanent across reboots, but messes the orientation/mirror image of the cameras, so the rear camera becomes a mirror image, not the front. This messes all portrait shots as the camera pic becomes upside down.
Device needs to be rooted.
Need to make /system directory read/write:
# mount -o rw,remount /system
# vi /etc/nvcamera.conf# format, cameraName=device,direction,orientation,type
This is the file before mods
# type can be 'stereo' for stereo capable, 'mono' for not stereo capable,
# 'usb' to enable searching for a usb device and where to put it in the list
# if found. Lines must be shorter then 256 characters
version=1
camera0=/dev/ov5640,back,0,mono
#camera1=/dev/ov5650,back,0,mono // 2nd camera for stereo once supported
camera1=/dev/mi1040,front,0,mono
#camera4=/dev/ov5650,back,0,stereo // virtual stereo device once supported
Change this line:
camera0=/dev/ov5640,back,0,mono
to:
camera0=/dev/ov5640,front,0,mono
And this line:
camera1=/dev/mi1040,front,0,mono
to:
camera1=/dev/mi1040,back,0,mono
Save and it works.
Please remove :/
No keep it, that's a good thing to have available to see or as a project. I love to learn things like this.
Thing O Doom said:
No keep it, that's a good thing to have available to see or as a project. I love to learn things like this.
Click to expand...
Click to collapse
I second doom. It's about pushing the limits of the device.
Good on ya for doing this.
Sent from my SCH-I500 using Tapatalk 2
I also agree. as some may not understand the reasoning, obviously oblonsky has a reason for doing this, just because everyone doesnt understand or agree with him is no reason to cut him off and remove his post... anything anyone learns or attempts to learn about android or the transformers code will progress understanding of the platform and the device. I vote let it stay and continue your endeavor fellow androidian.....
Yes, thanks guys. I'm already wondering now whether it may be possible to add new cameras, or disable cameras - do more useful stuff than swap cameras. Also I took the time to post the answer to my own question just in case it was useful to anyone else - so it would seem odd to want to remove the information that just *might* be useful to others at some point.
will this work on nougat......if not how to do it on nougat
Here is a reason to make the front camera the default camera: After getting in a terrible rain, my main camera on the back is not working anymore.
When starting a camera apps, it just quits with kind of a "connection to camera no possible" message.
Here's another reason to make the front camera as the default
I have a phone that's about 5 years old. It's been through heavy and rough usage. Hence, the connection between the motherboard and camera module are fried.
Now, when I have to login into WhatsApp Web or the WhatsApp App for Windows, I cannot because it needs a QR code scanned - which triggers the back camera.
So, I'm going to go ahead and try this, kudos!
Thanks for posting!
This was useful. Thanks. Please keep experimenting for no reasons.
SHUR1KEN said:
I have a phone that's about 5 years old. It's been through heavy and rough usage. Hence, the connection between the motherboard and camera module are fried.
Now, when I have to login into WhatsApp Web or the WhatsApp App for Windows, I cannot because it needs a QR code scanned - which triggers the back camera.
So, I'm going to go ahead and try this, kudos!
Click to expand...
Click to collapse
Uhm did it work?
Unfortunately, no, it didn't. Apparently, WhatsApp has gotten rid of the gate that used to allow for the "exploit" to happen before. I have heard of users doing it 2 years ago.
Anyway, what I had to do in my case was, I had to maintain pressure at the point on the camera module where it connects to the motherboard, while navigating to WhatsApp Web and scanning the QR code, all without even the most minute of movements. Otherwise the phone would fail to detect the camera module all over again, demanding me to repeat the whole thing again + a manual camera driver reset from my ROM settings.
Tried it like 20+ times. Succeeded in 1/20 of them... **** was tough, bro.
I finally managed to do this on my Redmi Note 5. This is probably applicable to most other devices as well.
Remount the system partition as writable:
Code:
$ su -c mount -o rw,remount /system
Edit /system/vendor/etc/camera/camera_config.xml and swap all
Code:
<Position>BACK</Position>
to
Code:
<Position>FRONT</Position>
and vice versa.
Reboot.
Do you think this will still work?
If I unroot after modifying the file, will the change persist?
Many thanks for your excellent work.
TheSnowpup said:
Do you think this will still work?
If I unroot after modifying the file, will the change persist?
Many thanks for your excellent work.
Click to expand...
Click to collapse
It still works for me at least. I think it will persist after unrooting, but I don't know how rooting works under the hood right now, so this may be incorrect.
If you try it, please report back your results!
If you are running a teamdrh rom with JB, or ICS with the 2.6.39 kernel, you can use a webcam and this hack to make skype video calls or take pictures/ record video with the stock camera app. I have tested this and it works great, skype calls are getting video and audio but i have only done a couple of five minute calls so I do not know if you will have the same luck with the MIC that I have had. on the stock camera app, if you "switch" from front to back camera, it inverts the video image, but video recording works, however on the stock app the MIC will cut off at around 10 seconds, but videolooks good, and pictures work too. All other camera apps I downloaded have worked as well.
REquirements:
1) a UVC webcam, which means compatible with Video4linux, or Video4windows, really most webcams work. The easy way if you buy one is to find on the box anything that says "no drivers/cd required." But check here: http://www.ideasonboard.org/uvc/#devices
I bought a $17 gigaware at radioshack, the cheapest one in the store.
2) You need to download this file:
https://docs.google.com/file/d/0B4ltl2zYxU7yVTVnM1RzVlBNaUE/edit?pli=1
BUT EXTRACT AND ONLY COPY THE camera.tegra.so FILE INTO your tablet's /SYSTEM/LIB/HW folder, and reboot. If you copy the other stuff you might find that your device will NO LONGER BOOT!!!
3) Plug your webcam into the usb port and in terminal run these commands:
su
chown system.camera /dev/video0
chmod 660 /dev/video0
*If you download gscript you can enter these commands once, and then it is just a couple of clicks, WAY EASIER! they need to be entered everytime you plug the webcam in, and before you run a camera/skype app.
Enjoy, I am hoping some people will test this and confirm it works for them too, please!
Credit BELONGS to Borkata at "another site" for his excellent work on the ADAM
redeyedjedi said:
http://www.tabletroms.com/forums/adam-general-development/5019-ics-external-camera-support-test.html
found this and I am wondering if he is talking about an ICS function, or just an Adam function. Either way, i was thinking the Adam is very similar to ours anyway. Anyone have a usb webcam that wants to try this, or bash me if the idea is out of the question for Gtab?? either is fine, just thought this MIGHT be useful.
Click to expand...
Click to collapse
There is a possibility that this already works on TeamDRH's ICS rom. The support has been added in the kernel awhile back but never been tested.
Thanks and much credit to rajeevvp!!!! I have gotten a webcam to stream video onto my gtab with DRH 1.3.2
Its kind've choppy, and a little blurry but works in a stable manner.
I am beggining to learn programming for android and trying to figure out a way to have any apps divert to my working video source instead of looking at the factory camera for a source. It seems it should be possible but I am just still too newb to Know any better.
If you would like to test this, then refer to this post:
http://forum.xda-developers.com/showpost.php?p=29457353&postcount=11
I have had success with a uvc compatibe webcam so far.
If you might have an idea as to how to trick the rom into looking at the usb port for its default video source I would like to know. Or if you can conclusively tell me that this is not possible I would like to know that too. My understanding is that there are two ways to approach this. One is to have the rom divert any frame capture requests to the usb video source as opposed to the original location. The other way, and probably more likely way, is to take an app like skype and hack it to go to usb for video, as opposed to the "stock camera location." Any insights would be very helpful. At least then, we could video chat with a small webcam, as opposed to no camera at all.
If this works for you, hit the thanks button on RAJEEVVP's post.
bump
That binary source code may also work on other ROMs (Froyo-, GB-, or HC-based ones)--if the Android<->HW camera interface hasn't changed. (The binary, unfortunately, doesn't load on GB and HC.)
This is how it should've been done by nVidia in the first place. I had expected them or VS/Malata to write a kernel driver for their camera which implemented the standard V4L interface. Instead, they have a binary-only shared object which directly controls the camera HW in a completely opaque way. There's hardly any camera-support code in the official (2.6.32.x) kernels at all--I was very surprised when I looked into this some time back.
nVidia's HW is nice and all, but, from now on, I'm just not going to buy any more of their products if it relies on any proprietary blobs.
rajeevvp said:
That binary may also work on other ROMs (Froyo-, GB-, or HC-based ones)--if the Android<->HW camera interface hasn't changed.
This is how it should've been done by nVidia in the first place. I had expected them or VS/Malata to write a kernel driver for their camera which implemented the standard V4L interface. Instead, they have a binary-only shared object which directly controls the camera HW in a completely opaque way. There's hardly any camera-support code in the official (2.6.32.x) kernels at all--I was very surprised when I looked into this some time back.
nVidia's HW is nice and all, but, from now on, I'm just not going to buy any more of their products if it relies on any proprietary blobs.
Click to expand...
Click to collapse
If you're down to take a peek here is where we're at with the Gtab camera on .39...
https://github.com/TeamDRH/android-tegra-nv-2.6.39-rel-14r7/commits/camera
I may not have everything??
redeyedjedi said:
3) Plug your webcam into the usb port and in terminal run these commands:
su
chown system.camera /dev/video0
chmod 660 /dev/video0
*If you download gscript you can enter these commands once, and then it is just a couple of clicks, WAY EASIER! they need to be entered everytime you plug the webcam in, and before you run a camera/skype app.
Enjoy, I am hoping some people will test this and confirm it works for them too, please!
Credit BELONGS to Borkata at "another site" for his excellent work on the ADAM
Click to expand...
Click to collapse
I found out I didn't have a dev/video0 folder. I created one but the camera fcs. Is ther supposed to be files in the video0 folder? I noticed in the audio folder there were several files. I am running DRH ICS 1.3 It didn't have the camera app installed since it didn't work anyway.
Any help would be appreciated. I restored the camera app with Ti from an earlier backup.
Thanks
btw: Thanks to all who got this working. I've been looking for something just like this.
Um, /dev/video0 is only created after you plug in your camera. You do not create this yourself. If your camera is UVC compatible, then after it is plugged in you should have /dev/video0 on the stock rom with no modifications! Did you check the link to see if it is listed?
These terminal commands give the camera permission to use the camera apps, along with the camera.tegra.so file. But, a totally unmodded rom will give /dev/video0 if your camera is compatible, because TEAMDRH already included the needed drivers. download the app "usb host controller" and open it after you plug your camera in. under the USB tab, does it register or list your camera? If so, then google your webcam, not the brand name, but the brand that is listed under "usb host controller" to see if it is UVC. My camera is a Gigaware, but under usb host controller it is listed as an MSI Starcam.
This positively works for me, but I have been waiting for anyone else to tell me it worked for them too so I can confirm. I am happy to help, because I want this to work universally as it should so it is a viable option.
Thanks
redeyedjedi said:
Um, /dev/video0 is only created after you plug in your camera. You do not create this yourself. If your camera is UVC compatible, then after it is plugged in you should have /dev/video0 on the stock rom with no modifications! Did you check the link to see if it is listed?
.
Click to expand...
Click to collapse
Thanks. I'm at work and just pulled out a cheap camera from my drawer. Not even sure what model it is. I wasn't aware though that the camera would create the folder when it is plugged in. When I get home I know I have a camera that is compatible and I will try it again.
Thanks for your help. I will let you know how it goes.
Fnally...a camera again
redeyedjedi said:
This positively works for me, but I have been waiting for anyone else to tell me it worked for them too so I can confirm. I am happy to help, because I want this to work universally as it should so it is a viable option.
Click to expand...
Click to collapse
It works. I haven't actually taken a pic or video yet, but I got a picture. I'm using my Logitech 270 HD webcam and the picture looks great. This is what I've been waiting for. I downloaded the free version if Camera ICS off the Play store. May have to buy it. The older stck camera app still FCs but the ICS one fired right up. Now I'll have to make my script.
Thanks a great deal... :good::good:
On a fresh install of the JB alpha, if you swipe left on the lockscreen instead of right, the camera app pops up, if you do a factory reset, then it will be in your app drawer!
I am so glad to hear it works for someone else.
TO use video recording or skype video, any video, you have to swap from the front to back camera. It shows an inverted image, but when you play back a recorded video, it is proper, also skype might be inverted but it looks right on the other end. I do not know why this is, but it works!!
***To clear up any confusion, the terminal commands only need to be entered once, after the camera is plugged but before you try to use any camera apps. They do not need to be re-entered until the next time you plug your webcam in, or restart the tab. With the gscript, you can put a shortcut on your homescreen, and the process becomes: plug cam in, tap one button, then load camera app or skype,etc!!
I can confirm it works with ICS Beta 1.3.2 (using the Camera ICS app). Camera, and Skype work just fine!
At last, my gTab is complete again! (well... almost...).
fosser2 said:
If you're down to take a peek here is where we're at with the Gtab camera on .39...
https://github.com/TeamDRH/android-tegra-nv-2.6.39-rel-14r7/commits/camera
Click to expand...
Click to collapse
I'll have to pass: Not enough free time. Besides, it looks like someone's already working on it--I'll just be stepping on their toes.
Random newbish question
would this be able to work on other tablets as well? albeit slightly modified and what not... i've been thinking of integrating a dell streak 7 into my dash and an external web cam would be a neat back up cam
Im gonna guess no, but it is possible. YOu need a kernel with V4l2 support, and a file like this to direct the rom to communicate with it. I know nothing about dell streaks, but if you ask a developer of the rom you're using to look at Borkata's github source you might get a solution, but I really do not know.
redeyedjedi said:
Im gonna guess no, but it is possible. YOu need a kernel with V4l2 support, and a file like this to direct the rom to communicate with it. I know nothing about dell streaks, but if you ask a developer of the rom you're using to look at Borkata's github source you might get a solution, but I really do not know.
Click to expand...
Click to collapse
Thanks, I figured that because the dell streak is a tegra 2 board, it wouldnt be too difficult, but i am definatly not a dev of any sort
I've tried this with on a gTablet, testing both G-Harmony & SmoOther Beam 4.1.2, but I haven't been able to get it working.
I'm testing it with a Microsoft HD-6000 webcam. Any suggestions on where I might look to determine if the problem is related to the ROM/approach, or the hardware?
I've already checked the UVC compatibility page. Unfortunately it's a bit out-of-date, and the HD-6000 is not yet listed, yet the sister HD-3000 is listed as supported.
Thank you in advance for any ideas!
RKM
rkmFL said:
I'm testing it with a Microsoft HD-6000 webcam. Any suggestions on where I might look to determine if the problem is related to the ROM/approach, or the hardware?
Click to expand...
Click to collapse
First, see if this Webcam test app works.