Database Info

Mer linux for kaiser.

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...

[Q] Camera Swap on rooted TF101

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!

$20 webcam= Skype video+camera apps working NOW!

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.

Developers and non-developers united to get better bluetooth experience at Android

The user ukdutypaid request me and
LNEt - I don't found the profile yet
Robbie P
qazzi76
sergiocabraljr
With some words:
So can anybody tell me either a) why is BT HID so 'rubbish' on Android, ie why is it so rare that anybody seems to have got it to work e.g "Look. It's a massive problem, nobody really knows how to do it. Count yourself lucky that you've got found a GB build where it does work at all. Put the problem down and walk away"; or b) what a solution might be?
I've tried rooting round in builds, until I'm blue in the face but unless the *.so file either has a BT and or an HID in the file name, then I'm in the dark.
qazzi76 ; GregórioAxiaMagno and sergiocabraljr have found various solutions for GB builds I think and I know Samsung seems to have solved the problem. (I've seen videos of the Galaxy Nexus and it worked with no problems on an SII a friend of mine has).
Could it simply be a case of isolating and extracting the magic HID file and putting it into any/all custom roms, or it's a case (for some just to make it harder reason) that the BT files have to be recompiled for each and every build; as GregórioAxiaMagno has kindly pointed out with some of his work.
The holy grail I suppose is a set of files that can be uploaded to any build by apt, that resolve the lack of BT keyboard with every/any build.
Click to expand...
Click to collapse
:good:
The point here is, as always I say, the bluetooth stack on Android is a issue like call recording. And with this cenario, I think we can join people to help on this thread to post information about mods, replacements, hacking, apps and more. Until we find the optimal solution for the largest number of phones what we can. :fingers-crossed:
All is valid: kernels, modules, CWM, apps, tips, :angel: pray... any way of help.
I will ask for you people to post solutions here, and along of the time I will quote it in the second post of this thread.
Also, I want discuss with you about an optimal solution.
So keep this thread clean and focused only about bluetooth.
No, I and nobody thinks what the bluetooth is the world conquest, I want only use the totally potential of this "old" tecnology.
I know we have other tecnologies like OTG, but this thread must be only about how to deal with bluetooth in our daily use and experiences.
Lets start! :highfive: I have your help?
Please, press thanks instead to manifest your support with posts.

Current solutions
[app][beta][2.1+] myblucon v1.0 & mybluime v1.0 - bluetooth kit to hid devices
so you buy a bluetooth mouse but your ginger won't connect it?
Or you have an bluetooth keyboard and can't write at your ice cream?
Solution for:
* ST15a/i - GB/ICS
* Others
Click to expand...
Click to collapse
Bluetooth Keyboard problem resolved
Infamous "paired but not connected."
Solution for:
* Galaxy Note GT-N7000
Click to expand...
Click to collapse
[APP]Bluetooth Keyboard Easy Connect
A service which connects your bluetooth keyboard device.
Android 2.3 has support for HID devices but is not able to connect bluetooth keyboard devices correctly (yet).
This service automates the connection to your keyboard.
Solution for:
* Many Androids
Click to expand...
Click to collapse
Solving Bluetooth connecting problems
My Desire's bluetooth allways worked like a charme untill rooting REDUX 1,2
Connecting to any previously known device, or any new once for that matter, did not work.
Some grey hairs, upgrading to Redux 2.0 and many tries later I concluded some data must be corrupted somewhere.
Deleting the content, not the files, just the content of the following files did the trick, much to my relief.
Solution for:
* HTC - Redux
Click to expand...
Click to collapse
HID Bluetooth Device FIX for 2.3.5 and 2.3.6!!
Like many of you I was extremely excited to learn that android now supports HID devices and immediately rushed out to purchase a HID-BT Keyboard. Getting home, I fired up the phone and keyboard, entered the 6 digit code to pair them and saw the device connecting and disconnecting in an infinite loop. I was crushed and disappointed.
What went wrong? As stated above this is merely a workaround. But the problem lies somewhere between the kernel and broadcom chipset. This fix will reset your bluetooth pairings. It has been tested on my Samsung Galaxy SII I727 but it should work with any other device.
Solution for:
* Many Androids
Click to expand...
Click to collapse

resv 2

:good::good::good:

Congratz... keep going

Looking here:
/data/misc/bluetoothd/<A BLUETOOTH ADDRES>
I was thinking one of this files have a value to set for make an device manually connectable. Like disabling/enabling auto connect. So the market apps to HID devies will work better.
What do you think?

I was messing into the system and looking at this path
system\etc\bluetooth
Inside, we can found some confs, so I was editing and guessing about input.conf.
So I made some mods and I will test today, but if anyone know something more about or want to test, please a hand will be cool xP.
Regards.
EDIT: yeah nothing changes... haha

[APP][3.21.16] TWC TV - VZW/ADB/HDMI checks removed & watch away from home!!

UPDATE
Development of this app will continue here: https://forum.xda-developers.com/android/apps-games/app-spectrum-tv-aka-twc-tv-t3847520
Thanks for everyone who kept this project going!
Hello here you will find the most recent TWC TV App from the android market... except it has ALL restrictions removed, NO ADB checks, NO proxy checks, NO HDMI checks, NO ROOT checks, and best of all, a method to watch ALL the channels while you're away from home, not just SOME of the channels TWC let's you watch; this can be viewed over 3g/4g/wifi... hell even 1x lol.
NOW the part I like... and maybe the reason why the root check was implemented by TWC.... you can actually WATCH live TV on any wifi, 3g/4G network away from your home! all you need is a few tools and you're on your way.... if this is of no interest to you then just scroll down to the download link
To watch outside of the home network:
Install a proxy server on a machine inside your network (a computer that can play live tv from twctv.com successfully)
I use wingate FREE edition (http://wingate.com)
Make sure you configure your router to forward traffic on that port to your machine
as a side note, make sure you assign a static IP on your local machine so your router doesn't get confused
also make sure you go to whatsmyip.org and get your external IP address (as you'll need this for the android side)
Install an app from the android market called "Auto Proxy (ROOT)"
Configure Auto Proxy to connect to your machine... here you will enter the IP you got earlier from your home machine and the port you chose when you configured wingate...
Now activate AutoProxy and all traffic will be routed through your home computer (all apps, etc...) meaning when you use the timewarner app it will think you're inside your home network!!
Make sure you turn it off once you're done watching TV, otherwise you will be consuming all of your upload bandwidth and also slow down your speeds since it has to go through the proxy...
Profit!!
Some Notes:
This app should work on any phone with gingerbread and up. (Tested myself)
Feel free to donate It took me a while to learn how to do this and it took alot endless nights
I think i should also point out that I didn't use anyone else's code to do this; I'm a lone developer and just like the challenge
I am also working on a workaround to the proxy thing... a way to watch Live TV on your cellular network alone... no proxy required (I make no promises but i'm looking into it and hopefully I'll come up with something)
I'll also try to release a new version if updates are released... try and keep everything current
Questions? need a more detailed guide or anything else? just ask! I'm here to help ... (but see post #2 first)
The 3.21.14 app would not be possible without GreenNasty... THANKS!
[CHANGELOG]
[3.21.16][v8] - App Version 4.1.8.10
Removed VPN/ADB/HDMI/Proxy restrictions
Enabled VZW Exclusive content for everyone!
Live TV and VOD DAI disabled
Fast forwarding enabled for all Video on Demand content... go ahead and skip those commercials
Enjoy!
[12.12.15][v7] - App Version 4.1.7.1
Removed Proxy/VPN/ADB/HDMI Checks
Enabled VZW Exclusive content for everyone!
Live TV and VOD DAI disabled
[11.14.15][v6] - App Version 4.1.2.32
Removed Proxy/VPN/ADB/HDMI Checks
Enabled VZW Exclusive content for everyone!
Enabled Seeking while playing VOD content (yes, you can skip ads )
Disabled DAI (Dynamic Ad Placement) in Live TV and VOD (My little bit of rebellion against all these restrictions) Google for more info
Removed regional restrictions (Now you may use the app even if you're outside the US)
[3.14.14][v5.1] - App Version 3.4.4#78
Removed Proxy and VPN checks from both Live TV and OnDemand
HDMI checks REMOVED!!!
Proxy and VPN checks removed
ADB Checks fully removed
[3.14.14][v5] - App Version 3.4.4#78
Removed Proxy and VPN checks
Partially removed HDMI checks from Live TV, OnDemand should still have same HDMI Restrictions
[8.21.13][v4.1] - App Version 3.3.1#57
I use wingate FREE edition (http://wingate.com)
Workaround for ISP Checks, now users of every network get the perks that verizon customers get
[8.07.13][v4.0] - App Version 3.3.1#57
Removed ADB Checks
Removed HDMI Checks
Removed Proxy/VPN Checks
Hope I didn't miss anything!
[7.13.13][v3.2] - App Version 3.2.1#49
Missed VPN Check... VPN should be working now
[7.10.13][v3.1] - App Version 3.2.1#49
Fixed ADB Check in Live TV - overlooked some code
[7.10.13][v3] - App Version 3.2.1#49
3g/4g/lan/etc.. streaming enabled
Proxy Checks Removed
HDMI Checks disabled (Not 100% sure on this, but if you have issues let me know)
All channels exclusive to VZW Customers are now available for everyone
Removed Root Checks
Removed Proxy/VPN Checks
Removed ADB Checks
Note: Since i actually REMOVED some of the code that performs the checks, the app might be smaller than the original app from the market (yeah i like to be efficient )
[5.17.13][v2] - App Version 3.2#44
Enabled 3G Streaming for EVERYONE! xD enjoy!
[5.15.13][v1.1] - App Version 3.2#44
Removed another HDMI check when plugging/unplugging HDMI cable while watching Live TV
[5.15.13][v1] - App Version 3.2#44
Completely new version!
Removed Root Checks
Removed ADB Checks
Removed HDMI Checks
Removed Proxy and VPN Checks
Should run smoothly on most devices! seems like TWC did some optimizations
[3.15.13][0.3] - App Version 2.6#36
Kindle Fire Fix... and potentially a fix for othe devices... if your device isn't a kindle fire then please follow directions in 2nd post
Please refer to Post #2 for download
[3.10.13][0.2] - App version 2.6#36
Removed HDMI checks!!
[3.04.13][0.1] - App version 2.6#36 (Initial Release)
Removed Root & ADB Checks
Increased buffer size to help with iffy networks
Click to expand...
Click to collapse
[Bugs/Issues]
None reported yet... let me know if you encounter any issues
[DOWNLOAD]
[3.21.16][v8] - http://www.mediafire.com/download/qrgoidy1k6jk8yp/signedTWC-TV_4.1.8.10.release.apk
Thank you all for your support! <3
[Questions/Issues?]
See post #2 and reply if you question is not addressed.
Thanks to those that made decompiling/recompiling easy!!
Don't forget to hit that thanks button if this app works for you!
donations are also appreciated... modifying something without the source code is tough... and a cup of coffee can go a long way when coding thanks for your support!

Bug List
APP Version 3.2#44: Some users report that HD doesn't work as well with the new app. Time Warner did alot of changes due to the move to streaming away from home, that means that they definetely could have messed something up.... if HD is not working properly for you and want to try the previous version (2.6#36) feel free to download it here: http://www.mediafire.com/?s3evtfhdedy3061
If you wish to decompile the app yourself, i have included comments in most of the important parts of the code that i modified... i will admin, they are HARD to understand and modify, but if you're looking to do it yourself in the future, I've helped you out
Issues/Troubleshooting
If you have tried this app and it does not work for you then i need the following information:
are you using the proxy instructions I mentioned or using the app using your home network?
MAKE SURE your device is rooted
if you are then please test it on your home network first and make sure it works (whithout ANY proxy, etc...)... if it does then let me know what issues you get when you use wingate and Auto Proxy....
if it does work on your home network but not with the proxy, then please tell me detailed instructions on how you set it up or if you need a guide on how to do so
do you have internet service through time Warner?
what device are you using?
what rom and kernel are you using, and what versions? (if you don't what kernel then just tell me which rom and version and i'll figure it out)
Are you rooted? With Super SU or just SuperUser?
All of the above checked? then i will need a logcat while the app is running Feel free to pm me the logcat ONLY after you have posted what i've requested and I'll let you know to send me a logcat... i don't want to receive random logcats and will ignore them if i haven't seen your information in this thread first!
Logcats can be taken via: adb shell logcat
OR adb shell and then type logcat, you can use the -f parameter to save it to a file rather than copying it from your command prompt to a file...
If there is anything else you think i should know, then please post that as well.... any little bit of information WILL help, trust me
I am committed to help.... but please help me by following the above instructions to make both our lives easier!
Thanks!

Will this work home lan with rooted / adb on ?
superman1101 said:
I know i haven't posted yet, but i recently got the TWC TV app and found that it doesn't work on Rooted devices or EVEN if you have ADB on!! anyways, I'm a developer but in a different language, nevertheless I looked around the forums and figured out how to modify the APK and came up with this... what better way to do my first post huh? lol
Click to expand...
Click to collapse
I really do not understand why they care if rooted / debugging is turned on?
I mean its at least a little understandable if one has an unlocked
bootloader and running on a non-standard rom.

Didn't work for me

bennettg said:
Didn't work for me
Click to expand...
Click to collapse
How come? what rom are you using, and do you get an error message?
fuzzynco said:
I really do not understand why they care if rooted / debugging is turned on?
I mean its at least a little understandable if one has an unlocked
bootloader and running on a non-standard rom.
Click to expand...
Click to collapse
There is competing theories on why they care... one of the reason i can think of (which i said in the OP) is that you can use a root app to enable traffic tunneling through a proxy (thus circumventing their "home network") restriction

Is this the phone version of the app?? Just wondering because I'm trying to get it to work on my HP Touchpad with CM10 and the signed versions I have found for the tablet are around 5mb and yours its just under 2.
Thanks!
*UPDATE*
Not sure why you version is so much smaller but it works perfectly on my tablet. I have been searching high and low for a fix and this was it. I can't thank you enough!!!

talon4x4 said:
Is this the phone version of the app?? Just wondering because I'm trying to get it to work on my HP Touchpad with CM10 and the signed versions I have found for the tablet are around 5mb and yours its just under 2.
Thanks!
*UPDATE*
Not sure why you version is so much smaller but it works perfectly on my tablet. I have been searching high and low for a fix and this was it. I can't thank you enough!!!
Click to expand...
Click to collapse
Glad it worked for you! this app is what i extracted from the app market with my EVO 3D, however i did see code segments in there for tablets so this app should be universal... let me know if you encounter any issues

Thank you! Works perfectly on my rooted Nexus 10!

I hope...
I hope you can remove the nightmare msg: "We are unable to present this channell..." in Kindle Fire 8.9 with OS 8.1.4
Thank you

field3d said:
I hope you can remove the nightmare msg: "We are unable to present this channell..." in Kindle Fire 8.9 with OS 8.1.4
Thank you
Click to expand...
Click to collapse
I wish I could, unfortunately that's a problem on the server's end, not the app... sometimes certain channels are unavailable because tw is having an issue on their end.... unless you're getting the error on every channel... right now I think Disney channel is having that issue, is it happening with a lot of channels?

Works great on nexus 10 running cm10.1 nightly thank you! I had to edit files after updating ROM now I don't have to, appreciate your work. HDMI would be a big bonus, cheers mate.

Aron_H said:
Works great on nexus 10 running cm10.1 nightly thank you! I had to edit files after updating ROM now I don't have to, appreciate your work. HDMI would be a big bonus, cheers mate.
Click to expand...
Click to collapse
unfortunately I don't have an HDMI cable to test and release a bug-free app... if you're up for it then i can give it a go and you can let me know if it works or not; I can have a new version out tomorrow if you're up for it

Great Job!!!
Just wanted to mention that I'm running your fix on my Kindle Fire and my Galaxy Tab 10.1
Thank you so much for the awesome work.

superman1101 said:
unfortunately I don't have an HDMI cable to test and release a bug-free app... if you're up for it then i can give it a go and you can let me know if it works or not; I can have a new version out tomorrow if you're up for it
Click to expand...
Click to collapse
I will happily test it, i picked up a $10 cable from walmart, its a bit short but should do the trick. I managed to poke around in the code myself, dont know what the hell im doing, but thought i would give it a go. Anyway doing a file compare with your version and the stock version, i can see quite a few changes which im sure took quite a bit of time, so i want to say Thank You again!!!

rickyq12 said:
Just wanted to mention that I'm running your fix on my Kindle Fire and my Galaxy Tab 10.1
Thank you so much for the awesome work.
Click to expand...
Click to collapse
glad to hear!
Aron_H said:
I will happily test it, i picked up a $10 cable from walmart, its a bit short but should do the trick. I managed to poke around in the code myself, dont know what the hell im doing, but thought i would give it a go. Anyway doing a file compare with your version and the stock version, i can see quite a few changes which im sure took quite a bit of time, so i want to say Thank You again!!!
Click to expand...
Click to collapse
I'm working on it right now.... just wanted to know: do you get an error message when you plug in the HDMI cable anywhere in the app? like even if you're not watching live tv? or only when you're tuned in to a channel?
UPDATE
-----------------------------------
Ok i just finished modifying the app... this is my first attempt at removing the HDMI check so don't be too harsh :/
Here you go: http://www.mediafire.com/?4w2tlc4k30t8pkt
if it works for you then i'll update the main thread with this version.

Nice !!!!
superman1101 said:
glad to hear!
I'm working on it right now.... just wanted to know: do you get an error message when you plug in the HDMI cable anywhere in the app? like even if you're not watching live tv? or only when you're tuned in to a channel?
UPDATE
-----------------------------------
Ok i just finished modifying the app... this is my first attempt at removing the HDMI check so don't be too harsh :/
Here you go: Had to delete link, wouldn't let me post.
if it works for you then i'll update the main thread with this version.
Click to expand...
Click to collapse
Nice one mate :good:, It will throw up the message box if you plug it in with app already on live TV, click OK and switch to guide and back to live and she runs great, if you startup app and your not on live tv, no message box.... Excellent work there Mate !!!

Aron_H said:
Nice one mate :good:, It will throw up the message box if you plug it in with app already on live TV, click OK and switch to guide and back to live and she runs great, if you startup app and your not on live tv, no message box.... Excellent work there Mate !!!
Click to expand...
Click to collapse
Great! There were 2 parts to edit, I fixed one because messing with the other gave me FC's... I'll mess with it some more

ok this should be it... i hope
HDMI should be working: http://www.mediafire.com/?s3evtfhdedy3061
let me know if it works or not

Look.
superman1101 said:
I wish I could, unfortunately that's a problem on the server's end, not the app... sometimes certain channels are unavailable because tw is having an issue on their end.... unless you're getting the error on every channel... right now I think Disney channel is having that issue, is it happening with a lot of channels?
Click to expand...
Click to collapse
I heard TWC app have troubles with some checkings with some ROMS maybe removing the checking when that message is shown. Look I tested on iPad, iPod, iPhone and. Samsung Galaxy Tab Android and works perfect but specific the problem is on Amazon Kindle 8.9 with iOs 8.1.4 and others in every channel no some channel is every channel the message and the message appears in no more than 30 seconds, in other words you only have around 30 seconds of video in any channel and the message is shown and other people have the same issues. If you have the code and you can check the message when is shown and remove the condition or if you have the source maybe we can see when the message is shown I can see to have an idea. If you look inside other forums in this webpage there are other people with dame problem in other devices.
Thank you

field3d said:
I heard TWC app have troubles with some checkings with some ROMS maybe removing the checking when that message is shown. Look I tested on iPad, iPod, iPhone and. Samsung Galaxy Tab Android and works perfect but specific the problem is on Amazon Kindle 8.9 with iOs 8.1.4 and others in every channel no some channel is every channel the message and the message appears in no more than 30 seconds, in other words you only have around 30 seconds of video in any channel and the message is shown and other people have the same issues. If you have the code and you can check the message when is shown and remove the condition or if you have the source maybe we can see when the message is shown I can see to have an idea. If you look inside other forums in this webpage there are other people with dame problem in other devices.
Thank you
Click to expand...
Click to collapse
Can you tell me what specific message comes up? there's different messages that come up for different scenarios, if it's only "this channel is currently unavailable at this time" then i need to know specifics... what device, what android version, rooted or not.... a logcat of the app running would also be nice... I also don't understand what you mean by "iOS 8.1.4", afaik iOS is only on apple devices ... this fix is only applicable to android devices.
Let me know if it's happening to you and let me know the specifics i mentioned and i'll see what i can do about it.