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!
Related
Saw this in the debugger tonight when launching the Camera app.
Code:
11-25 23:57:59.732: VERBOSE/QualcommCameraHardware(32): initCameraParameters: set parm: CAMERA_PARM_NIGHTSHOT_MODE, 0
Anyone have any ideas and/or documentation regarding this? I would love to experiment with turning the feature on, but I'm rather clueless when it comes to Java programming
look at the git repo... I will look also but many of the features we are asking for are already built in they just need final tweaks.
I've seen all sorts of fun and interesting features while reading through the source. Automatic image upload, YouTube upload (video recording?), All sorts of camera settings for doing effects. (Monochrome, solarize, etc), RAW recording, etc.
I hope someone is able to write some sort of camera app that harnesses some of this power that's available... And gives us the ability to adjust shutter speed and increase the gain in software.
ultimind said:
I've seen all sorts of fun and interesting features while reading through the source. Automatic image upload, YouTube upload (video recording?), All sorts of camera settings for doing effects. (Monochrome, solarize, etc), RAW recording, etc.
I hope someone is able to write some sort of camera app that harnesses some of this power that's available... And gives us the ability to adjust shutter speed and increase the gain in software.
Click to expand...
Click to collapse
You know there was word that Google had put those features in but pulled them out at the last minute because it wasn't working properly. I am sure we can get it working if someone was willing to try.
cool stuff. play with it and tell us what it does.
but, and im no photographer or anything, but i would assume that night shot mode would make the shutter speed even slower to capture more light, which is the opposite of what we really want for this camera.
It could be that it is in a nightshot mode and that is why it is blurry... not to mention does anyone know why Sony cameras are the best? It is the software that knows how to automatically take pictures that aren't blurred.
typically if nightshot_mode=0 by default then it is not in nightshot mode. perhaps the current camera software changes that variable i dont know.
d0nkey said:
typically if nightshot_mode=0 by default then it is not in nightshot mode. perhaps the current camera software changes that variable i dont know.
Click to expand...
Click to collapse
true... I don't think it is in the real nightshot mode but rather something with a long delay. This is why most images are blurry and some are ok.
Yeah, the dim light camera is abysmal. I keep hoping that there'll be a camera upgrade soon
When RC29 came I noticed the camera worked like 5 times better. I was even able to snap pics of the kids on the swings and they came out clear, when RC30 came it was back to blurriness as usual.
Now either I'm trippin about the improvement I noticed with RC29 or there's something in that version that sped up the focus.
My RC29 was the install from SD version.
the RC30 is the factory OTA from Google.
2JRo said:
Yeah, the dim light camera is abysmal. I keep hoping that there'll be a camera upgrade soon
When RC29 came I noticed the camera worked like 5 times better. I was even able to snap pics of the kids on the swings and they came out clear, when RC30 came it was back to blurriness as usual.
Now either I'm trippin about the improvement I noticed with RC29 or there's something in that version that sped up the focus.
My RC29 was the install from SD version.
the RC30 is the factory OTA from Google.
Click to expand...
Click to collapse
lol... didnt even notice the difference in camera quality after getting rc30
EDIT:
Magister2k7 said:
Please update first post of a thread, as Mer should run X with a latest kernel from git.
You just need to disable FB_MSM_DOUBLE_BUFFER ("Enable MSM Framebuffer double buffering") and enable framebuffer refresh thread.
Click to expand...
Click to collapse
Yeah, I kinda doomed myself from the start with how I structured this post. I'll restructure it later to be more able to show you good information.
Old start:
Mer is a more community-led version of the Maemo phone and internet tablet operating system. See http://wiki.maemo.org/Mer/ .
I was in contact with a member of that project (Stskeeps on freenode#mer), who gave me some information about porting this to phones such as the kaiser. He and I thought it would be a great way to benefit both communities (we get a good, not google-owned linux-based os for our phones, they get developers helping them make mer better). We also agreed that it would take a bit of effort.
First of all, Mer is completely designed for landscape-only, 800x480 phones at this point. It has been run well at 640x480, but that's still 4 times our native resolution, and 2 times what we can fake without crashes. The resolution problem is easily fixed by skilled theme-makers. The landscape/portrait problem should be fixed soon, given that the upcoming n900 will be a portrait/landscape phone. He said wait for the maemo conference for more on that.
The other problems we might hit basically are just the standard problems of molding the userspace around the kernel (get a phone app working, get the modem to work, etc.).
If you are serious about helping, please come to #mer and/or #htc-linux on freenode. At this point, the mer folks are probably more help to what we need to do.
INSTRUCTIONS:
At this point, quite literally nothing works, but it all almost works. Here's what I did to get that far:
1. Partition your sd card into two partitions, and make the second one ext2.
2. Unpack (with the -p option of tar) the rootfs (http://wiki.maemo.org/Mer/Releases/0.16testing , pick the q5 rootfs) to the ext2 partition. Make sure that it's not in any subfolders, but as the root of the drive.
3. Grab a zImage (or build your own) using the instructions we had in place from android. Put it on the fat side.
4. Set up HaRET on the fat side - Use a default.txt from android, get rid of the initrd, get rid of your ppp stuff (for now), and add "root=/dev/mmcblk0p2 rootwait" to the kernel cmdline.
5. mknod /dev/fb0 c 29 0 (this was my number, check using the terminal in android, cat /proc/devices for the major, and /proc/fb for the minor). Also make sure that it's within the root, not on your disk .
That should boot, giving you a ton of messages about an "incorrect resolution png" or something - that's the splash screen unable to load. Simply rename /lib/init/splash-* (two files) to something else. Once you get a terminal later, there's an actual package to remove, but this lets it go a bit further.
You also need to keep X from starting at this point - all it does is hang. I have not yet done this myself, but it should be an initscript that you just un-link.
EDIT: It wasn't X that caused the issues. It was the combination of failed splashes and consolefont. Comment out the lines with "splash" in them in /etc/init.d/check{fs,root}.sh, and re-run.
I do not know if X actually fails - doing that test now.
EDIT: hitting framebuffer issues... no X yet.
So, if you're adventurous, and preferably a dev at this point (this is completely useless to users), please try this out and make it better!
Okay, just a note: the password is "rootme".
First reply!
this is relevant to my interests. I'll take a look. I remember seeing that Maemo was made on top of Gnome. Do you know if there's a chance to get Debian apps on here? That's the big thing for me to get me working on it-- some type of desktop compatibility. Having an X-server is perfect. Looks like you're saying the resolution issue is purely theme based? How open are the devs for it for suggestions and feedback?
2nd reply
This does sound cool
already made some read about this in the new nokia n900..
its cool.. it free.. but i dont like the ui :\
lets see where this goes.. but.. for now.. for me... android (L)
Ok, just saw it's Jaunty based which is what I've been looking for in a phone.
Is there a list of features/bugs/issues and what's been developed so far? Seems like if the kernel brought to us in part by dzo will work maybe it won't be so hard to get wifi and other features working. A list is good.
I'll admit I haven't put much effort into it, but at this point X won't work, for one thing - probably have to change the resolution in a config somewhere.
Indeed, most of the hardware should be fine - I imagine, for example, once we are able to load the firmware, wifi should be good. Some code will have to change (a few things are built android-specific in the kernel), and some of the RIL stuff especially (phone, data, etc.) will have to be ported by someone who has that code and some time.
Indeed, Mer is Ubuntu-based, and so, according to their site, 95% of ubuntu apps should work perfectly. This is really nice for getting software on (aren't just limited to any applications in an app store or market.).
At this point, all we need to do is everything .
I'm going to try now to disable X and see if I can't get a few more things working.
EDIT: in response to your question about how open the mer-folk are to suggestions? The idea that I got from talking to them was that they are more than happy to get this extra help, and since they are trying to bring this to more devices, they are willing to put up with our requirements, to make this more readily available in general.
Alright, as I edited, I got some more success.
By removing the splash calls and the X starting, I can get a terminal. I edited the /etc/shadow file to have a password that I knew for root. Now, I can log in as root on the console (/dev/tty1).
I tried to start X, and I'm getting some strange framebuffer errors.
I'll keep you posted.
Wow, if we could get this working, it'd be sick! Thanks for posting, formatting now.
with all the hard work already done for the Android port, seeing devs being interested in Mer is REALLY PROMISING! Waiting for Google to open up Android even more, is frustrating...
Porting Mer and thus having a REAL linux (kernel+software stack) is what we need to leverage the dev capacity of the great XDA community. At least, this is what I feel like .
Owning both a Kaiser and 2 N800s, I'll probably try out the stuff posted here... I was keeping an eye on Mer for my N800s anyway, but using it on the Kaiser is more triggering
so devs, have courage and good luck!
Frame Buffer and X server
Unfortunately I've been quite busy lately and haven't been following the Android development as closely as I would like. (I don't think I've updated my git repo for months)
If I remember correctly, the frame buffer code in the kernel wasn't finished. That would prevent X from running. Can anyone say whether that was completed? I just wanted to mention this in order to avoid people wasting their time if it is in fact the problem.
It would be great to *eventually* see X running with hardware acceleration, can anyone point me to info about how DZO got that working? Was it reverse engineered, or did he figure out how to make some binary blob happy?
It will be nice to have some choice of Linux based distros the Kaiser and Vogue. Keep up the good work everybody, I appreciate it!
-Mysteryvortex
I've been looking at the n900 for quite some time just waiting for its release to the US next month. I know nothing about developing but I am very excited about this one, and I hope that there is a quick start to the apps that are put out for it. I was curious myself as well at how this would port to the kaiser so I could get a good hands on before I went and bought one. I would be more than happy to be a tester. I bought an iphone cause cause the little green guy is really starting to piss me off and my tilt's about to give up the ghost. I quickly gave it to my wife as the signal strength and battery life just sucks so I hope this maemo can give me what I want
mysteryvortex, Android does not use an X server at all. This was my disappointment when issues arose trying to run Ubuntu in a chroot. This is different though. We should be looking at troubleshooting the X server as top priority I think. The rest should flow. Bear in mind the kernel for Android, like I said, has nothing to do with X compatibility since Android uses its own display so the kernel should need some serious work.
poly, is the build you linked to hardware specific? Looks like a generic one. If so, then the only outstanding difference should be the kernel and if that's the case we should be able to use this on any phone we happen to have a kernel for right?
enatefox said:
mysteryvortex, Android does not use an X server at all. This was my disappointment when issues arose trying to run Ubuntu in a chroot. This is different though. We should be looking at troubleshooting the X server as top priority I think. The rest should flow. Bear in mind the kernel for Android, like I said, has nothing to do with X compatibility since Android uses its own display so the kernel should need some serious work.
poly, is the build you linked to hardware specific? Looks like a generic one. If so, then the only outstanding difference should be the kernel and if that's the case we should be able to use this on any phone we happen to have a kernel for right?
Click to expand...
Click to collapse
The build has a kernel and stuff, but don't use it. Use the regular stuff from android (or build yourself from htc-vogue).
mdrobnak from irc got mer up on his raph - thanks to the vga screen, with a quick kernel patch and some xorg.conf modification, he got X working great.
Within the next few days, I'll do some tests of the data connection and such.
enatefox said:
mysteryvortex, Android does not use an X server at all. This was my disappointment when issues arose trying to run Ubuntu in a chroot. This is different though. We should be looking at troubleshooting the X server as top priority I think. The rest should flow. Bear in mind the kernel for Android, like I said, has nothing to do with X compatibility since Android uses its own display so the kernel should need some serious work.
Click to expand...
Click to collapse
Yes, that's correct. Android doesn't use X. Many, many months ago, it was mentioned that the framebuffer in the Vouge/Kaiser kernel (which X will use) was broken. Nobody was planning to fix it since Android doesn't need it. I was just trying to point people who have time to work on supporting our phones in the right direction.
poly_poly-man: Looks like the Raphael kernel is being developed on another branch, but it sounds like the FB patch helps us?
-Mysteryvortex
poly_poly-man,
I have setup my second partition of sdcard to 512MB and extracted there Mer preserving permissions.
What I did also is to modify the x config and change resolution and also resize the Mer-logo.jpg so it fits.
After I tried to boot I went successfully through all steps (at least I think so) and a blank screen appeared to me.
Can you tell me what was the parameter to output the Haret boot sequence to a file, so I can check what passes and what fails?
Another question: The following "mknod /dev/fb0 c 29" have to be performed on root of second permission, right? If so I think the command should be ""mknod ./dev/fb0 c 29", am I correct?
Regards,
Borkata
Borkata81 said:
Another question: The following "mknod /dev/fb0 c 29" have to be performed on root of second permission, right? If so I think the command should be ""mknod ./dev/fb0 c 29", am I correct?
Click to expand...
Click to collapse
'./dev/fb0 c 29' does only work if you are in "/" (root of the filesystem) otherwise (and in all other cases) 'mknod /dev/fb0 c 29' is correct.
bye...
Borkata81 said:
poly_poly-man,
I have setup my second partition of sdcard to 512MB and extracted there Mer preserving permissions.
What I did also is to modify the x config and change resolution and also resize the Mer-logo.jpg so it fits.
After I tried to boot I went successfully through all steps (at least I think so) and a blank screen appeared to me.
Can you tell me what was the parameter to output the Haret boot sequence to a file, so I can check what passes and what fails?
Another question: The following "mknod /dev/fb0 c 29" have to be performed on root of second permission, right? If so I think the command should be ""mknod ./dev/fb0 c 29", am I correct?
Regards,
Borkata
Click to expand...
Click to collapse
It seems that even set to the right resolution, our fb does not work with X. Needs more patching than just the patches I got from the other branch. We may need to move up to the other branch, I'm not sure.
the /dev/fb0 should be replaced with /path/to/sdcard/root/dev/fb0, of course. And it's better to just get rid of all the splash references - that way, you don't get the blank screen issue.
toasty_ said:
'./dev/fb0 c 29' does only work if you are in "/" (root of the filesystem) otherwise (and in all other cases) 'mknod /dev/fb0 c 29' is correct.
bye...
Click to expand...
Click to collapse
Yes, but poly has written that user have to be in root so that was what I have asked
Question: our fb driver is msm_fb?
poly can you share which patches you tried from raph branch?
Borkata81 said:
Yes, but poly has written that user have to be in root so that was what I have asked
Question: our fb driver is msm_fb?
poly can you share which patches you tried from raph branch?
Click to expand...
Click to collapse
Oh yes, you're right. I should first read the full post before answering questions that havn't been asked
Borkata81 said:
Yes, but poly has written that user have to be in root so that was what I have asked
Question: our fb driver is msm_fb?
poly can you share which patches you tried from raph branch?
Click to expand...
Click to collapse
http://people.openezx.org/tmzt/
the msmts and vres patch. Didn't work, because there are more problems in our older kernel.
I'm interested in finding out why we aren't on 2.6.27 already...
Anyone knows if there is (will be) an open API for the infrared module they integrated on the Galaxy Tab Plus?
I have developed a remote control app, and it would be great if I could add support for the Galaxy Tab.
Thanks.
The original galaxy tab does not have an IR transmitter
Sent from a Galaxy S 2 Far Away
Anyway........I don't know if this answers your question or not but Peel comes on the tab and it sucks if you use media extenders other than apple TV. I'd imagine you'd need driver info for your app to get it working. I'd be interested in beta testing for it if you get more serious.
Sent from my GT-P6210 using Tapatalk
The original galaxy tab does not have an IR transmitter
Click to expand...
Click to collapse
Yeah, I know. I figured I could post that question here anyway. We agree that there is an integrated IR module in the Galaxy Tab Plus, right?
Anyway........I don't know if this answers your question or not but Peel comes on the tab and it sucks if you use media extenders other than apple TV. I'd imagine you'd need driver info for your app to get it working. I'd be interested in beta testing for it if you get more serious.
Click to expand...
Click to collapse
Oh yeah I'm serious man. I already have an app which require a DIY module to be able to send infrared signals (www dot zokama dot com slash androlirc). I'm working on a new version with a lot more features, and I'd like to add support for commercial hardware and take advantage of all those tablets recently released with an IR transmitter. So yes, access to the IR drivers is what I'm after.
It might have been better to post that in the "Galaxy Tab Android Development" sub-Forum actually. If a moderator comes by and feels like correcting that wrong...
Post the output of dmesg and we'll see if we can spot which device it is, then one can look for drivers/spec sheets to see how to talk to it.
You might also like to attach the output of the following command, which will list all the parts of the sysfs as it may already be accessible there:
ls -R /sys
Well, I don't actually own one and I was hoping to find someone here who does.
I've been asked for the Galaxy Tab Plus support in relation to my remote control app and I thought that it could be a cool feature. But I'd be developing it blindfolded and ask my users to test it.
What about USB IR adapters? If someone (not me, unfortunately) has USB IR and possibility to hook it to original galaxy tab, wouldn't that be one possible solution? (Really, I don't know, that's why I'm asking)...
zokama said:
Well, I don't actually own one and I was hoping to find someone here who does.
I've been asked for the Galaxy Tab Plus support in relation to my remote control app and I thought that it could be a cool feature. But I'd be developing it blindfolded and ask my users to test it.
Click to expand...
Click to collapse
I have one and I'd willing to test it out for you. Peel isn't that great and would like other options.
What about USB IR adapters? If someone (not me, unfortunately) has USB IR and possibility to hook it to original galaxy tab, wouldn't that be one possible solution? (Really, I don't know, that's why I'm asking)...
Click to expand...
Click to collapse
Yeah that would be a solution. But I already have alternatives. For example, I already have a DIY IR module that can be used. But the idea here is to get access to the integrated IR module available in the Galaxy Tab Plus.
I have one and I'd willing to test it out for you. Peel isn't that great and would like other options.
Click to expand...
Click to collapse
Cool, could you run the commands suggested by lardman, namely "dmesg" and "ls -R /sys"?
You don't need to be root for either of them, but you do either need to install a terminal application (lots on the Android Market) or use adb.
Redirect the output to a file on your SD card if you aren't using adb. I'm not quite sure whether the path to the external SD has changed for your device/version of Android, but for me it would be something similar (I've added the $ that represents the command prompt, don't type this!)
$ cd /sdcard/external_sd
$ dmesg > dmesg.output
& ls -R /sys > sysfs.output
Then copy dmesg.output and sysfs.output from the external card.
gotta wait till i get home lard but ill have it uploaded for you tonight
I have the plus pm me ill help u out
Sent from my M9300 using xda premium
ping ........
dmesg and ls ouput
I got some input from one of the users of my app who owns a Galaxy Tab Plus. I couldn't make much out of what he sent me but I hope someone outhere is more knowledgeable than I am (this shouldn't be too complicated...)
I'm limited to 87kB for txt files attachement, I'll see if that increases when I get to 8 posts (this being the 8th)
Well, didn't work out, still limited to 87K... I'm attaching a tar then...
Oh please let there be something other than that gawdawful Peel app. I had to "cheat" it and put dummy devices and settings in to finally finish the setup (kept FC when i tried to set up). Also tried to figure out how to set up more than 1 "room" in Peel and i can't.
There were the Pronto conversion apps for WinMo, why not for this?
I can already control my Z-Wave network with my android devices, was hoping to have something to do the IR stuff on this one device.
rEVOLVE said:
Oh please let there be something other than that gawdawful Peel app. I had to "cheat" it and put dummy devices and settings in to finally finish the setup (kept FC when i tried to set up). Also tried to figure out how to set up more than 1 "room" in Peel and i can't.
There were the Pronto conversion apps for WinMo, why not for this?
I can already control my Z-Wave network with my android devices, was hoping to have something to do the IR stuff on this one device.
Click to expand...
Click to collapse
+1 on this. I dont know what Peel is doing right now to correct the issues but theyre kinda slow on dev. But they do reply when you send them a message. Im still keeping my hopes up for a big change but right now' their app is almost unusable.
Yup, exactly my point.
My app is still work in progress, but it could let you use pronto codes with Android. I actually use Lirc but converters from pronto to Lirc already exist. I'm actually thinking about integrating such a converter in the app to make things easier. Anyway, back to the topic.
So far the only way I have to send IR signals is through a DIY audio2IR converter. I also have a cool version using bluetooth (www.zokama.com/androlirc). But I'd like to go further and make the most of what's out there. And get an access to the Galaxy Tab Plus IR module would be pretty cool. But I need help for that, I don't even own a GTP...
I suppose I ought to have specified to save the output of dmesg shortly after boot in order to capture the enumeration of the system devices, thanks anyway for the output you managed to get.
Looking at the output of /sys we can see a couple of devices with filenames that seem IR related, but now it's time to look at the kernel source to see whether that brings to light the particular chipset in use.
With that in mind I downloaded the kernel source (took a while to work out the product code: GT-P6210), but I can't work out which defconfig is the one to use (so I can see what is enabled in the kernel). Anyone seen any instructions for this?
I'm guessing that the kernel driver in use here is 8250 - a serial driver, so assuming that's true can do some more digging (and that should mean the interface is quite simple, does someone want to run strings on the shipped IR comms binary and see if it mentions the /dev file it uses?)
Onto other matters, I see some mention of DVB stuff in the /sys files, TV tuners and the like (e.g. xc5000, TUNER_XC2028 drivers), did this Tab 7.0 plus have a TV tuner USB dongle plugged in or is there some functionality in-built...?
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.
So after tinkering with this phone for quite awhile! With the help of another developer, we now have a decent working port of google camera for the razer phone. Portrait mode is not working in this version because portrait was introduced in version 5.1 and later. Also the razer phone has hardcoded front camera2 as legacy so there is no raw support so you will never get selfie portrait to work. Hopefully razer will remove this hardcode in Pie, but it's very unlikely. I have sold my phone so there will be no more development from me on this, I'm simply sharing back and actually CARING to have a decent camera!
First and foremost, you need to root your device and unlock the bootloader (recommended but does not have to), then replace all these chromatix files for color fix, using a file explorer of your type. I highly recommend Solid Explorer:
https://drive.google.com/open?id=1EreYInGhkaN08aay3StpHra1gluN9rUJ
After you replace the libs, install the apk and shoot. Modified to have locked 35 frames in all conditions, with raw so you can edit these amazing pictures afterwards.
https://drive.google.com/open?id=1DRab0IZ-0dY8C-AcZsIDYPfyAzmQFev-
xterminater07 said:
So after tinkering with this phone for quite awhile! With the help of another developer, we now have a decent working port of google camera for the razer phone. Portrait mode is not working in this version because portrait was introduced in version 5.1 and later. Also the razer phone has hardcoded front camera2 as legacy so there is no raw support so you will never get selfie portrait to work. Hopefully razer will remove this hardcode in Pie, but it's very unlikely. I have sold my phone so there will be no more development from me on this, I'm simply sharing back and actually CARING to have a decent camera!
First and foremost, you need to root your device and unlock the bootloader (recommended but does not have to), then replace all these chromatix files for color fix, using a file explorer of your type. I highly recommend Solid Explorer:
https://drive.google.com/open?id=1EreYInGhkaN08aay3StpHra1gluN9rUJ
After you replace the libs, install the apk and shoot. Modified to have locked 35 frames in all conditions, with raw so you can edit these amazing pictures afterwards.
https://drive.google.com/open?id=1DRab0IZ-0dY8C-AcZsIDYPfyAzmQFev-
Click to expand...
Click to collapse
I tried replacing those files to "vendor/lib" and now it says Camera Error " Can't connect to the camera". Do any of you guys have the original files? I forgot to make a back up.
matt0323 said:
I tried replacing those files to "vendor/lib" and now it says Camera Error " Can't connect to the camera". Do any of you guys have the original files? I forgot to make a back up.
Click to expand...
Click to collapse
There's no way you get a Camera Error. Are you on the latest firmware for the Razer? I did this multiple times... I don't have the stock bc I sold it already as mentioned. You can do a factory reset or reflash the rom.
Works very well and seems to stable. Been using it for two weeks now and taken ~200 photos with HDR without a single crash.
Thanks for you work!
Hey can you do this for newer versions and can we get a port with telephoto let z