Related
Hi devs,
I was trying to compile the eclair AOSP with hero profile. Everything compiled correctly and it boots up on my hero but why does my touchscreen not work??
Anyone could give me a hand on why the touchscreen is not working on my hero? I am using godmode kernel.
Thanks in advance,
Use this kernel + wlan.ko:
http://github.com/loxK/android_device_htc_hero/blob/froyo/kernel
http://github.com/loxK/android_device_htc_hero/blob/froyo/wlan.ko
maxisma said:
Use this kernel + wlan.ko:
http://github.com/loxK/android_device_htc_hero/blob/froyo/kernel
http://github.com/loxK/android_device_htc_hero/blob/froyo/wlan.ko
Click to expand...
Click to collapse
Thanks Maxima!
But this is for Froyo or also working for eclair?
And another question is it a special kernel config that I need to enable for the touchscreen to work? As I did use a working .config from another 2.1 rom.
Giving those files a go anyhow
Argh! I recompiled the kernel with the config from the kernel you posted. But still touchscreen does not work..
Also the unlock (pincode) screen does not popup so I cant make any calls.
Can anyone please give me some hints on why this is happening?
In the kernel is a AOSP-version of the touchscreen driver and a Sense-version. Don't know why the difference is there, but if you look at your kernel source files you'll see a file in there with 'AOSP-fix' in the filename. Use that version of the .c file (overwrite the original or backup the original first) and compile your kernel. The touchscreen will work now.
Or (like the previous answers) use an already compiled kernel with this fix in it
dipje said:
In the kernel is a AOSP-version of the touchscreen driver and a Sense-version. Don't know why the difference is there, but if you look at your kernel source files you'll see a file in there with 'AOSP-fix' in the filename. Use that version of the .c file (overwrite the original or backup the original first) and compile your kernel. The touchscreen will work now.
Or (like the previous answers) use an already compiled kernel with this fix in it
Click to expand...
Click to collapse
Ah! Thanks. Recompiling
btw and what about the pincode popup issue? Why am I not getting that popup when starting the phone?
Works! Nice! Thanks. And my other Question? Pincode unlock is not poping up. I cant get a signal from my provider
Anyone has a clue?
I have tried to enable keyguard options to false/true 0/1 but still no joy.
Now checking settings it seems my build is not seeing the baseband versions. It says: Unknown.
Maybe this is something anyone has experience with?
Shakor said:
I have tried to enable keyguard options to false/true 0/1 but still no joy.
Now checking settings it seems my build is not seeing the baseband versions. It says: Unknown.
Maybe this is something anyone has experience with?
Click to expand...
Click to collapse
RIL-library..
maxisma said:
RIL-library..
Click to expand...
Click to collapse
Cool. Thanks checking this out.
Still no joy.. Argh
Dear all,
Did anyone succeed extracting kernel configuration from I9000XXJP3? Kernel version is 2.6.32.9, the vermagic is "2.6.32.9 mod_unload ARMv7"
extract-ikconfig doesn't work on it.
I succeeded extracting a zImage gzipped payload, but it seems not to contain any configuration in it (see attached).
/proc/config.gz doesn't exist, Samsung open source package (downloaded from Samsung open source site) contains only Android 2.1 Eclair or previous versions.
My target is to build tun.ko and, eventually, ext3/ext4 modules to make them working in Samsung Galaxy S I9000 with rooted I9000XXJP3.
Any idea?
Without froyo source code or a good Samsung Kernel (es. for himem capable) I think is impossible to play good with theses beta roms.
Ciao
Any news? I need tun.ko for jp3 too..
I have tried to compile the 2.6.32.9 kernel editing the .config in 2.6.9, the module tun.ko is accepted by the device, but I get a kernel panic!
redsh said:
I have tried to compile the 2.6.32.9 kernel editing the .config in 2.6.9, the module tun.ko is accepted by the device, but I get a kernel panic!
Click to expand...
Click to collapse
Did you use the stock linux kernel? Or the common from android.kernel.org?
I'm trying the same thing actually. Isn't there any default config for the processor that might work? I tried with the config from .29 but when loading the module it says wrong format.
try to build 2.6.32 with the 2.6.29 config ("yes" all missing stuff)
turn on your galaxy, adb push the tun.ko
try to load it, it will say "missing symbols" blabla
find the config options that match those symbols, enable them, recompile, try again
Great to see some people who are hacking the kernel! Keep it up!
But I'm afraid it is not going to be as easy as dropping aries_rev03_defconfig as .config in a 2.6.32 kernel tree and doing 'make oldconfig'. That's because many of Samsung's changes have not been included in the newer mainline kernel versions yet.
Samsung added quite a lot of low-level board support for their dev boards (and for the SGS, of course), did some customization and added a few drivers which you will need to forward-port to the newer kernel.
Please have a look at this thread, in which I've started a breakdown of the Samsung patches against Android Eclair's 2.6.29 kernel.
The best course of action I think is to git clone Android's kernel from AOSP, checkout the android-2.6.29 branch, apply Samsung's patches to that, then attempt to rebase your tree to a newer kernel version. (Note, you may want to start with small steps, to get a feel for what you're up against )
Note that there probably will be lots of merge conflicts which you need to resolve, and after dealing with all those, you also have to make sure that everything else that's merged still works as expected, but at least that will show you the amount of work involved. You will basically be doing all the work that Samsung is doing right now for their kernel for FroYo. It will be interesting to follow their progress on the mailing lists and on IRC.
bilboa1 said:
try to build 2.6.32 with the 2.6.29 config ("yes" all missing stuff)
turn on your galaxy, adb push the tun.ko
try to load it, it will say "missing symbols" blabla
find the config options that match those symbols, enable them, recompile, try again
Click to expand...
Click to collapse
Thats exactly what I did, but I got wrong module format... which is a fatal error. I need to invest further in the used config... maybe i did not pick up the right one properly..
miki4242 said:
Great to see some people who are hacking the kernel! Keep it up!
But I'm afraid it is not going to be as easy as dropping aries_rev03_defconfig as .config in a 2.6.32 kernel tree and doing 'make oldconfig'. That's because many of Samsung's changes have not been included in the newer mainline kernel versions yet.
Samsung added quite a lot of low-level board support for their dev boards (and for the SGS, of course), did some customization and added a few drivers which you will need to forward-port to the newer kernel.
Please have a look at this thread, in which I've started a breakdown of the Samsung patches against Android Eclair's 2.6.29 kernel.
The best course of action I think is to git clone Android's kernel from AOSP, checkout the android-2.6.29 branch, apply Samsung's patches to that, then attempt to rebase your tree to a newer kernel version. (Note, you may want to start with small steps, to get a feel for what you're up against )
Note that there probably will be lots of merge conflicts which you need to resolve, and after dealing with all those, you also have to make sure that everything else that's merged still works as expected, but at least that will show you the amount of work involved. You will basically be doing all the work that Samsung is doing right now for their kernel for FroYo. It will be interesting to follow their progress on the mailing lists and on IRC.
Click to expand...
Click to collapse
Yes that would be a lot of work. Maybe its better to just wait until they release the kernel from froyo. I read that they release their opensource stuff rather fast. But just for adding a module like ext4 I don't think you need those patches, because imho they didn't touch the fs of the kernel. We just need an adaquate kernel config and adding modules should be possible.
Phlogiston said:
Thats exactly what I did, but I got wrong module format... which is a fatal error. I need to invest further in the used config... maybe i did not pick up the right one properly..
Click to expand...
Click to collapse
Make sure you're using the same kernel version number and build number, because samsung kernels do not have the option to load incorrect module versions
Yes i've set the subversion as well but without the patches from samsung its impossible it seems. We need to wait and hope that they release the froyo kernel sources soon....
bilboa1 said:
Make sure you're using the same kernel version number and build number, because samsung kernels do not have the option to load incorrect module versions
Click to expand...
Click to collapse
Are you sure they set CONFIG_MODVERSIONS? It's off in the downloadable sources.
Just compare the output of `modinfo -F vermagic <yourmodule>` to `modinfo -F vermagic <modulewhichloads>` or to /proc/version .
did this get solved yet? I google'd for the tun.ko file for my i9000 using jp3 but nothing yet... if you have a proper one for the MoDaCo version here please attach it! ~
I think I saw someone's post with tun.ko for FroYo beta somewhere in these forums, I mean i9000 Android Dev. One of the guys here has found a way to compile kernel for jp* here. I am sure.
I actually found it attached somewhere in the forum and it was 1,5447 mb big I think it was... but it still didn't work for me so I presumed the kernel or something must have been wrong.
Hi all,
I have Fat Free Froyo installed with the latest 14th Jan 2011 kernel voguimg-240x320-2.6.32-froyo-14-01-11_14.nbh edited to froyo & panel type 2 from t029000.massey.ac.nz but Google Goggles needs ipv6 support.
Is this a kernel problem or a problem with the build itself? I am experienced in linux, so can modprobe or insmod the ipv6.ko but I don't know where to get it from
Any help would be appreciated!
(message for kernel's developers) take this man! he can dev ipv6!
Jumping the gun there a bit
I triage bugs and work on stuff for Ubuntu. Have also ported a few linux bits to ppc64 (PlayStation 3).
I'm pinching the ipv6.ko from slayhers latest kernel build, hopefully that will work insmod-ding or modprobing it into the kernel thru the terminal on the Kaiser itself.
So, fingers crossed, this may be solved in 5 minutes!!
Didn't work, it must be compiled for a different platform...
Anyone have or know where to get a kernel for the Kaiser with ipv6 support, or failing that the correctly built ipv6.ko for the Kaiser so that it can be insmodded?
Getting it compiled in the kernel is the easy bit, although it does use up a lot of space which is limited in the kaiser's kernel so a little tweaking is needed. Getting it to work with the Kaiser's modem and the builds we currently use is a different matter unfortunately. It will take a bit of modding for it to work but it's more then achievable with a bit of free time. Wish i could buy that stuff!!If i get a chance i will get you the ipv6 module for the kaiser's kernel or a kernel with support for it so you can have a play.
I definitely look forward to it! If I knew how and what to modify I'd do it myself, but I thought arch-specific kernels had to be compiled on the arch itself? If that's the case, I can see how free time would be needed, it'd take hours or days to compile the linux kernel at 400MHz
I have compiled kernels before so if/when I learn how to do it myself, I could start to use my own git repo for more recent daily builds or something.
I'm also thinking about starting working on some *buntu stuff (I know Ubuntu is there for the Kaiser, but soem tweaks would help if I get a chance.)
Hmm, a little Googling goes a long way http://www.androidonhtc.com/wiki/Get_Involved << was hard to find that,so hopefully I can add ipv6 somewhere in the 'make menuconfig' options for the kernel.
Are the standard kernel options used by "make vogue_defconfig" ok to use, i.e. will it build a normal useable kernel so that everything works?
xteejx said:
Hmm, a little Googling goes a long way http://www.androidonhtc.com/wiki/Get_Involved << was hard to find that,so hopefully I can add ipv6 somewhere in the 'make menuconfig' options for the kernel.
Are the standard kernel options used by "make vogue_defconfig" ok to use, i.e. will it build a normal useable kernel so that everything works?
Click to expand...
Click to collapse
Yes, that is th correct make file to use. I have built the kernel with IPV6 support, haven't tested it but have attached the module to the post for you to try
Brilliant! I'll try it sometime within the next couple of days, although I might myself be working on a blazing fast kernel specifically for the HTC Kaiser, and it is SERIOUSLY!!!! fast, even at 400MHz I can notice a massive increase in speed with the exact same build, but I haven't economised too much.
I can see the the options for ipv6 in the ncurses menuconfig, so I guess it's just a case of enabling it and building the zImage right?
I seem to be having the old problem with the wifi though, and I know it's kernel related, but there are only patches for it, i.e. the wlan.ko, but can't see how to implement it myself so it's an all-in-one solution
When I get the hang of the Kaiser hardware properly, I might just push through a newer kernel from the armlinux site so watch this space
xteejx said:
I might myself be working on a blazing fast kernel specifically for the HTC Kaiser, and it is SERIOUSLY!!!! fast, even at 400MHz I can notice a massive increase in speed with the exact same build
Click to expand...
Click to collapse
How have you managed that??? What have you done?
I have no idea how it happened, perhaps the other devs add a load of useless options, but all I did was follow the instructions at that link above and compiled a zImage from the 2.6.32 arm branch, using the 2010 arm tools. Used NBHeditor to edit it for Kaiser, panel 2, froyo, flashed it and bang (not literally thank god).
I can't answer any better than that. I used the default options (for now at least) that the vogue build script uses for the kernel, but bluetooth, camera and gps work. No internet connection as yet either through the network or wifi, dumno what I've missed there, and no ipv6 (but can add that easily enough). Wifi doesn't work either, but I'm working on it, although that MAY be the reason why it's so fast...maybe it's missing a few options...still unsure at this point.
I notice that although this is an open community, and people attach NBHs, there are no changelogs or anything showing what the people have done with the kernel to implement some options, so it's kinda holding me back at the minute.
xteejx said:
I notice that although this is an open community, and people attach NBHs, there are no changelogs or anything showing what the people have done with the kernel to implement some options, so it's kinda holding me back at the minute.
Click to expand...
Click to collapse
That isn't true, all tested changes are pushed to git, you can see what has been changed and how from here: http://androidhtc.git.sourceforge.n....git;a=shortlog;h=refs/heads/htc-vogue-2.6.32
*facepalm!*
Didn't see that, will bookmark it and keep an eye on it, perhaps work with it. Thanks for the link
the androidhtc.com site is not related directly to the develop project because no developer is connected to it. Also the git repository it not hosted in linux to go but on sourceforge (so download the correct git). That site is very outdated.
wifi works if you use the correct branch (on sourceforge) and modules.
Am I right in thinking that http://androidhtc.git.sourceforge.n...7c0bf5edc4f5c6d64ce4df29254e8332ce26b;hb=HEAD is the prebuilt kernels and nbhs from the source at http://androidhtc.git.sourceforge.n...og;h=62f075ddd13f378fd252be94c77e4f93d12584fb ??
I think I'm looking at the right tree now.
Flashing the latest NBH: VOGUIMG-320-FROYO-01-16-11.NBH still gives me the wifi error. Do I need to manually add the wlan.ko to it or ??
I could've sworn that an NBH I flashed before had all that in the NBH and it worked fine.
Ok, got it back to how I had it:
Flashed latest.NBH from http://androidhtc.git.sourceforge.n...7c0bf5edc4f5c6d64ce4df29254e8332ce26b;hb=HEAD and dropped androidupdate.tgz to the /andboot folder of the SD card, installed update thru the boot menu and done.
So in reality there's nothing stopping me grabbing the same kernel source, building it and adding ipv6 support in the ncurses kernel config menu and making an NBH from it and flashing that over, and then doing the androidupdate.tgz, although I think with HTCFlasherGUI you can flash a zImage directly right??
Is there something wrong with the git at http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/kernel.git;a=summary I can't get access, it's showing old stuff. It looks closed since git clone rejects me
xteejx said:
Is there something wrong with the git at http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/kernel.git;a=summary I can't get access, it's showing old stuff. It looks closed since git clone rejects me
Click to expand...
Click to collapse
No, nothing wrong with it. Just do:
git clone git://androidhtc.git.sourceforge.net/androidhtc/kernel.git
You then need to set it to the correct branch using 'git checkout -b <branch you want> '
It's the 2.6.32 branch you are interested in, you can find out exactly what it's called using 'git branch -a' which will list the available branches.
Cool. Knew something went wrong somewhere, had to be me lol!
I added that ipv6.ko to the NAND via a androidupdate.tgz (only way I could do it), and it didn't work, something about incorrect module format (or something like that).
Are there any prebuilt kernels or NBHs for the Kaiser that include ipv6? Either as a module that I can insmod it in the terminal or built-in?
I hate being upstaged by people that can use Goggles without any problems.
I know slayher's kernels have ipv6, but I flashed the new stock one from http://forum.cyanogenmod.com/topic/4434-froyo-kernels-by-slayher/ and it didn't work. I mean the kernel did, but Goggles didn't - couldn't insmod it either - same invalid module format as the ipv6.ko scooter did for me
Also the git clone didn't work:
Initialized empty Git repository in /home/name/android-git/kernel/.git/
fatal: The remote end hung up unexpectedly
Hello freinds,
I have a microsoft lifecam cinema hd webcam which I want to connect through my note2.is there any tutorial to add module to the kernel and make it working.
I am a windows user btw.
So anybody know if I can do it on window pc.
I know this thread should be in q/a section but due to any reason my question is not visible to that section.
Thanks in advance...
liondroid said:
Hello freinds,
I have a microsoft lifecam cinema hd webcam which I want to connect through my note2.is there any tutorial to add module to the kernel and make it working.
I am a windows user btw.
So anybody know if I can do it on window pc.
I know this thread should be in q/a section but due to any reason my question is not visible to that section.
Thanks in advance...
Click to expand...
Click to collapse
Even if it were possible, why do you want to add another camera to the device?
Edit: You however did pique my curiosity whether this can be done and perhaps it can!. The camera model you have mentioned is supported by the Linux UVC driver (check here: http://www.ideasonboard.org/uvc/). This is a part of the standard kernel source (it's located at /drivers/media/video/uvc)
So basically, you need to compile the 'uvcvideo.ko' module. I don't know if this can co-exist with the existing camera driver, so you may have to disable the driver for the front / back cameras and compile the uvcvideo driver in or as a module.
Good luck!
seltaeb said:
Even if it were possible, why do you want to add another camera to the device?
Edit: You however did pique my curiosity whether this can be done and perhaps it can!. The camera model you have mentioned is supported by the Linux UVC driver (check here: http://www.ideasonboard.org/uvc/). This is a part of the standard kernel source (it's located at /drivers/media/video/uvc)
So basically, you need to compile the 'uvcvideo.ko' module. I don't know if this can co-exist with the existing camera driver, so you may have to disable the driver for the front / back cameras and compile the uvcvideo driver in or as a module.
Good luck!
Click to expand...
Click to collapse
The stock front camera has a bad low light visibility where as the microsoft lifecam has a very good visiblity even in the room with all lights off, at night ofcourse (the light source is only the screen itself falling on my face)
As i already know this is possible. Take a look..
http://www.youtube.com/watch?v=taZ3zd37nMI
I think there is no option other than to install linux on my pc and give a try.
Any suggestions would be appreciated.
liondroid said:
The stock front camera has a bad low light visibility where as the microsoft lifecam has a very good visiblity even in the room with all lights off, at night ofcourse (the light source is only the screen itself falling on my face)
As i already know this is possible. Take a look..
http://www.youtube.com/watch?v=taZ3zd37nMI
I think there is no option other than to install linux on my pc and give a try.
Any suggestions would be appreciated.
Click to expand...
Click to collapse
Although unsupported, I believe it is possible to build the kernel on Windows under Cygwin. Have a look here for setting up the build environment etc on Windows: http://forum.xda-developers.com/showthread.php?t=1686310. Note that Samsung's recommended toolchain is actually 4.4.3 (but you might be able to find that with a bit of Googling).
Alternately, I can build the uvcvideo.ko module for you. However, I am going away from tomorrow morning for a long weekend, so you might have to wait till Sunday evening unless I manage to find some time to do it tonight itself. Otherwise you can try requesting someone else here to build it for you - it only takes a few minutes.
seltaeb said:
Although unsupported, I believe it is possible to build the kernel on Windows under Cygwin. Have a look here for setting up the build environment etc on Windows: http://forum.xda-developers.com/showthread.php?t=1686310. Note that Samsung's recommended toolchain is actually 4.4.3 (but you might be able to find that with a bit of Googling).
Alternately, I can build the uvcvideo.ko module for you. However, I am going away from tomorrow morning for a long weekend, so you might have to wait till Sunday evening unless I manage to find some time to do it tonight itself. Otherwise you can try requesting someone else here to build it for you - it only takes a few minutes.
Click to expand...
Click to collapse
it will be a great help if u can create the module for me. Thanks in advance
liondroid said:
it will be a great help if u can create the module for me. Thanks in advance
Click to expand...
Click to collapse
This is more a driver issue than kernel. And even though there may be linux drivers for your webcam. Google has not yet fully merged the android kernel into the linux family, so it may not be possible to port. I wish you all the luck though :fingers-crossed:
AndroHero said:
This is more a driver issue than kernel. And even though there may be linux drivers for your webcam. Google has not yet fully merged the android kernel into the linux family, so it may not be possible to port. I wish you all the luck though :fingers-crossed:
Click to expand...
Click to collapse
uvcvideo.ko is a module which contains almost all webcam drivers including mine.It can be implemented to android kernel also.See the video link in previous posts.I already managed to get uvcvideo.ko, now trying to add to the kernel source. Hope I am going in right direction.
liondroid said:
uvcvideo.ko is a module which contains almost all webcam drivers including mine.It can be implemented to android kernel also.See the video link in previous posts.I already managed to get uvcvideo.ko, now trying to add to the kernel source. Hope I am going in right direction.
Click to expand...
Click to collapse
Seems like the reverse direction actually. You already got your module compiled and now you are changing the source?
PS: So you no longer want me to compile the uvc module for you?
Sent from my GT-N7100 using Tapatalk 2
seltaeb said:
Seems like the reverse direction actually. You already got your module compiled and now you are changing the source?
PS: So you no longer want me to compile the uvc module for you?
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
one of my frend is a linux user so i asked him to do for me but he messed up the kernel so pls sir I am waiting for ur work.
liondroid said:
one of my frend is a linux user so i asked him to do for me but he messed up the kernel so pls sir I am waiting for ur work.
Click to expand...
Click to collapse
Here you go. This is an ODIN flashable kernel (unzip it and flash the .tar file using the PDA section in ODIN). The module is located in /lib/modules.
PS: The kernel is compiled from stock sources, except for addition of the lulzactiveQ governor (pegasusQ is still default) and a couple of other patches (missing touchkey drivers and AndreiLux's firmware naming / boot-up time reduction fix).
Edit: Added only the module in uvcvideo.zip. Unzip & copy it to your phone somewhere and insmod it to load. If it doesn't work with your stock kernel, please use the full kernel against which it is built (provided above).
And here's the Samsung stock kernel from DDLJ3, in case you want to revert back. Again, ODIN-flashable after unzipping.
I might be a bit off topic:
Is there anyway to load an under volt module?
I've always been using Tegrak over clock ultimate but it's not updated since 2 months..
And it's obviously not working on our beloved gsn2
I'd love to stay as stock as possible but with under volt
TMaLuST said:
I might be a bit off topic:
Is there anyway to load an under volt module?
I've always been using Tegrak over clock ultimate but it's not updated since 2 months..
And it's obviously not working on our beloved gsn2
I'd love to stay as stock as possible but with under volt
Click to expand...
Click to collapse
Please just use AndreiLux's excellent kernel to accomplish this.
Sent from my GT-N7100 using Tapatalk 2
Well I'll give it a try, but in term of battery life I've never had better results than stock kernels, that's why I was asking
seltaeb said:
And here's the Samsung stock kernel from DDLJ3, in case you want to revert back. Again, ODIN-flashable after unzipping.
Click to expand...
Click to collapse
Thankyou so much sir, will let u know after trying it.
seltaeb said:
Even if it were possible, why do you want to add another camera to the device?
Edit: You however did pique my curiosity whether this can be done and perhaps it can!. The camera model you have mentioned is supported by the Linux UVC driver (check here: XXXurl omittedXXX is a part of the standard kernel source (it's located at /drivers/media/video/uvc)
So basically, you need to compile the 'uvcvideo.ko' module. I don't know if this can co-exist with the existing camera driver, so you may have to disable the driver for the front / back cameras and compile the uvcvideo driver in or as a module.
Good luck!
Click to expand...
Click to collapse
Hello, excuse my off topic but i have a similar need:
i have an Android mk3188 tv box that has uvcvideo support in the kernel i'm using. the Camera is in the list of supported cam (093a:2700 - iSonic W002)
When i connect the camera i receive the following message:
[10501.638841] usb 1-1.3: Product: USB2.0_Camera
[10501.643370] usb 1-1.3: Manufacturer: PixArt Imaging Inc.
[10501.657777] uvcvideo: Found UVC 1.00 device USB2.0_Camera (093a:2700)
[10501.673615] input: USB2.0_Camera as /devices/platform/usb20_otg/usb1/1-1/1-1.3/1-1.3:1.0/input/input5
[10559.678208] qtaguid: ctrl_counterset(s 1 10112): insufficient priv from pid=422 tgid=364 uid=1000
[10560.472909] DWC_OTG: dwc_otg_hcd_urb_enqueue urb->transfer_buffer address not align to 4-byte 0xed6abaca
[10560.482867] uvcvideo: Failed to query (GET_DEF) UVC control 2 on unit 3: -1 (exp. 2).
[10560.492619] DWC_OTG: dwc_otg_hcd_urb_enqueue urb->transfer_buffer address not align to 4-byte 0xed6abaaa
[10560.502458] uvcvideo: Failed to query (GET_DEF) UVC control 3 on unit 3: -1 (exp. 2).
[10561.087346] qtaguid: ctrl_counterset(s 0 10047): insufficient priv from pid=422 tgid=364 uid=1000
I have tried to set /dev/video0 chmod to 666 but the error message is the same.
How can i update uvcvideo from 1.00 to 1.10? i need to recompile kernel or there are others solutions?
can i use uvcvideo.ko provided in this thread? how can i do?
Thank you
seltaeb said:
Here you go. This is an ODIN flashable kernel (unzip it and flash the .tar file using the PDA section in ODIN). The module is located in /lib/modules.
PS: The kernel is compiled from stock sources, except for addition of the lulzactiveQ governor (pegasusQ is still default) and a couple of other patches (missing touchkey drivers and AndreiLux's firmware naming / boot-up time reduction fix).
Edit: Added only the module in uvcvideo.zip. Unzip & copy it to your phone somewhere and insmod it to load. If it doesn't work with your stock kernel, please use the full kernel against which it is built (provided above).
Click to expand...
Click to collapse
Is file uvcvideo.ko specifically for galaxy note or can i use it on a different device?
Is this still required for UVC video to work or does it work on the latest ROMs/kernel?
I've read it works out of the box on the Nexus 7 but I don't have webcam to test on my Note2.
Nevermind. I tried the app Dashcam which checks for UVC driver. GFs S3 does not pop up an error while my Note2 (and my HTC Desire 601) do.
Apologize for possible OT, but I can't find an always working (and stable) SSH daemon app for the Zenfone2's Lollipop
This is what I tried, any of them PAID apps:
QuickSSHd - too old, not even starts
SSHDroid Pro - sometime starts, only first time after reboot, but only without root and higher ports (>1024)
RRooted SSH/SFTP Daemon - always refusing connections
Ssh Server Pro (olive tree) - seems promising, but very poor of binaries
The Dropbear service hanging issue seems the root of this problem
Thanks for any hint
I can't even find a proper ssh binary. I just tried sshd from an x86 cyanogen port (RAZRi, I think). Got this after loading appropriate library in lib (same as client)
1|[email protected]:/ # sshd
CANNOT LINK EXECUTABLE: could not load library "libssh.so" needed by "sshd"; caused by cannot locate symbol "EVP_ripemd160" referenced by "libssh.so"...
Good luck sir
Blades said:
I can't even find a proper ssh binary. I just tried sshd from an x86 cyanogen port (RAZRi, I think). Got this after loading appropriate library in lib (same as client)
1|[email protected]:/ # sshd
CANNOT LINK EXECUTABLE: could not load library "libssh.so" needed by "sshd"; caused by cannot locate symbol "EVP_ripemd160" referenced by "libssh.so"...
Good luck sir
Click to expand...
Click to collapse
Hi,
I followed the following guide which you can get from googling "Compiling-Dropbear-for-a-Nexus-7-tablet". Sorry, I can't post any links yet as my post counts are still below 10
The difference with the info from the website above is that we don't need to cross compile if you're compiling in a Linux x86-64 system. Just need to make a static binary.
Let me know if you have any questions and I'll try to help out.
Cheers.
wolfdude said:
The difference with the info from the website above is that we don't need to cross compile if you're compiling in a Linux x86-64 system. Just need to make a static binary.
Let me know if you have any questions and I'll try to help out.
Click to expand...
Click to collapse
Thanks for your answer.
Sorry but I can't get the exact entry-point, bypassing all the NDK / X-compiling stuff, as we're on a x86_64 architecture
Referring to the "simplified" version of your link (here: https://nerdoftheherd.com/articles/cross-compiling-dropbear-rsync-android/ ),
how should I compile the Dropbear source ?
Something like this ?
Code:
./configure \
--disable-zlib --disable-largefile --disable-loginfunc --disable-shadow --disable-utmp --disable-utmpx --disable-wtmp \
--disable-wtmpx --disable-pututline --disable-pututxline --disable-lastlog \
CFLAGS='-Os -W -Wall -fPIE' LDFLAGS='[COLOR="Red"]-static[/COLOR] -fPIE -pie'
... right before make-ing ?
Thanks for any further hint in the right direction
Hi,
I didn't refer to that site you have posted BUT that site does have a link at the bottom to the site where I followed.
From that site, what I did was :-
1) Download dropbear v58 (dropbear-2013.58.tar.bz2). I know this is older but the patch available is based on this version.
2) Download patch (dropbear-patch2) from that site.
3) Apply patch to the original dropbear (v58) source.
4) Run configure :-
./configure --disable-zlib --disable-largefile --disable-loginfunc \
--disable-shadow --disable-utmp --disable-utmpx --disable-wtmp \
--disable-wtmpx --disable-pututline --disable-pututxline --disable-lastlog
5) Run make :-
STATIC=1 MULTI=1 SCPPROGRESS=0 PROGRAMS="dropbear dropbearkey scp dbclient" make strip
6) You should end up with "dropbearmulti" which is a static binary that you can then copy over the the phone & go on from there.
There are some issues with that version of the code (v58+patch). Namely the "scp" doesn't work (but I have found the offending code in scp.c and found a workaround).
Let me know if you need more details. If I have some time, I might look at getting the latest dropbear version & working out a patch for it to get it to work on android x86.
Cheers.
wolfdude said:
Hi,
I didn't refer to that site you have posted BUT that site does have a link at the bottom to the site where I followed.
[...]
There are some issues with that version of the code (v58+patch). Namely the "scp" doesn't work (but I have found the offending code in scp.c and found a workaround).
Let me know if you need more details. If I have some time, I might look at getting the latest dropbear version & working out a patch for it to get it to work on android x86.
Cheers.
Click to expand...
Click to collapse
Yes of course. The main link you weren't able to post is:
http://blog.xulforum.org/index.php?post/2013/12/19/Compiling-Dropbear-for-a-Nexus-7-tablet
Actually that procedure seemed too complex as mostly dealing with the cross-compiling issue, which didn't apply to x86 case.
So I named the derivative one
Thanks for pointing out the static compiling is done within MAKE and not CONFIGURE phase... I'm quite newbie in those flags so I do appreciate any of your words
About issues, what about using the latest v67 for Dropbear sources ? (see here)
If the patch doesn't work for such different version, I guessed commenting out the interactive password line would be enough
I'm trying to compile it this way and - for instance - replace the binaries in one of the SSHD packages I named in the OP...
Thank you again for your time
Val3r10 said:
About issues, what about using the latest v67 for Dropbear sources ? (see here)
If the patch doesn't work for such different version, I guessed commenting out the interactive password line would be enough
I'm trying to compile it this way and - for instance - replace the binaries in one of the SSHD packages I named in the OP...
Thank you again for your time
Click to expand...
Click to collapse
Hi,
Yes, the patch for v58 does not work for v67. I think one just have to go through the patch and "adjust" it slightly for the newer v67. Hopefully there isn't much changes from v58 to v67. There may be more than just commenting out the password prompt as there are certain functions that don't work in Android as in *NIX. When I have some time, I will attempt to patch v67 meanwhile, I'm running v58 fine on my ZE550ML so no complains there.
Cheers.
Hi,
I've created a guide on compiling the latest dropbear (2015.67) :-
http://forum.xda-developers.com/zenfone2/general/compiling-dropbear-2015-67-zenfone-2-t3142222
Hope it helps.
Cheers.
wolfdude said:
I've created a guide on compiling the latest dropbear (2015.67)
Click to expand...
Click to collapse
Thanks a lot.
Do you think the same process (STATIC build, of course, not patching) could be likely used for other small binaries too ?
Val3r10 said:
Thanks a lot.
Do you think the same process (STATIC build, of course, not patching) could be likely used for other small binaries too ?
Click to expand...
Click to collapse
Of course. I've managed to compile tcpdump, iperf, gdbserver, etc... successfully and working fine on the Zenfone 2.
Cheers.
I found that "Servers Ultimate" SSH/SFTP modules work on the Zenfone2 once properly configured. Its not working 100% but its already more then most solutions out there.