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.
Related
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
[This is not the place to say "this is awesome" or "thanks!"]
[DEVS ONLY]
I want to start this thread to keep up the progress on the port.
the bad news is that the SDK is incomplete for now, so (like other devices)
we will have to write our own code for the OS, the nook community
has done a wonderful job writing their own libraries and stuffs, so we will have to do the same.
Instead of pursuing different goals, let's focus on one thing at a time.
since GSM and CDMA versions are already out, it seems we suffer the same bugs, so for now let's unite strength and knowledge to overcome these.
I propose that the first goal to fix is the SurfaceFlinger, so we could at least see the apps, the buttons and the notifications.
it is currently throwing this:
04-06 22:01:35.495: ERROR/Surface(2960): dequeueBuffer failed (Out of memory)
this could lead us that it might coudln't start because of some malloc malfunction or something.
also that pvrsrvinit bugs me a lot.
update:
8/APR/2011
since DiP7 could fix SurfaceFlinger and other things using a different build from the GSM kernel, we have to dig deeper
======================================
CURRENT GOAL
Rebuild Kernel
======================================
Current approaches:
*none
Post any finding, guessing or anything, and please, please don't be afraid to ask anything you have a doubt, as a Dev you should not know everything, so we can help us each other
------------------------------------------
Google Easter egg:
while searching some info about the android.mk file , I put it on the chrome bar to search for that term, but instead I went to
http://android.mk
an easter egg web page from google lol
******TOOLS*********
How to send text and Keystrokes via ADB
http://bradchow.blogspot.com/2011/02/send-intent-and-key-event-by-adb.html
use DroidExplorer to easily access your device from your computer and makes changes from it
http://de.codeplex.com/
The Android Boot Process
http://www.androidenea.com/2009/06/android-boot-process-from-power-on.html
---Kernel Tools----
CPU Datasheet
http://forum.xda-developers.com/showthread.php?t=745877
Samsung GIT
http://android.git.kernel.org/?p=kernel/samsung.git;a=summary
PowerVR SDK
http://www.imgtec.com/powervr/insider/powervr-sdk.asp
Source code of samsung firmwares(keep and eye on this)
http://opensource.samsung.com/
Asus pad honeycomb Kernel Source
http://forum.xda-developers.com/showthread.php?t=1026528
ellokomen said:
======================================
CURRENT GOAL
Find why SurfaceFlinger is not working
======================================
Click to expand...
Click to collapse
Mmmk.. Let me tell you a story.
A long time ago in a galaxy far away... No, that will take too long. In a nutshell, one third of the answer is here, another third is here and the rest is here. I'm not trying to be intentionally vague, I just haven't figured out how these three fit together yet.
Of course, there could also be some bit of code that I missed... some telling line in a debug log that I overlooked or some driver or library that I could have decompiled to sift through its juicy secrets. There could easily be a fix that would take seconds to add and make the whole thing fall in line...
Or we might have to work it from the ground up.
Either way it will happen. It's just a matter of whether it will happen next week, or next month.
(Watch it be a misplaced semi-colon, or a bad symlink... that's how these things go.)
updated approaches and new tools have been added
spacemoose1 said:
Mmmk.. Let me tell you a story.
A long time ago in a galaxy far away... No, that will take too long. In a nutshell, one third of the answer is here, another third is here and the rest is here. I'm not trying to be intentionally vague, I just haven't figured out how these three fit together yet.
Of course, there could also be some bit of code that I missed... some telling line in a debug log that I overlooked or some driver or library that I could have decompiled to sift through its juicy secrets. There could easily be a fix that would take seconds to add and make the whole thing fall in line...
Or we might have to work it from the ground up.
Either way it will happen. It's just a matter of whether it will happen next week, or next month.
(Watch it be a misplaced semi-colon, or a bad symlink... that's how these things go.)
Click to expand...
Click to collapse
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
However I do not think you are wrong that there is a problem somewhere in the kernel. The kernel that has been released for the galaxy tab is a mess of horrid code, I have had to re-write parts of kernel drivers just to get them to work under linux, I would not be surprised if similar patches are needed for honeycomb
lilstevie said:
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
However I do not think you are wrong that there is a problem somewhere in the kernel. The kernel that has been released for the galaxy tab is a mess of horrid code, I have had to re-write parts of kernel drivers just to get them to work under linux, I would not be surprised if similar patches are needed for honeycomb
Click to expand...
Click to collapse
you mean that you made a port of a Linux Distro into the tab?
ellokomen said:
you mean that you made a port of a Linux Distro into the tab?
Click to expand...
Click to collapse
yes click here for the thread on the port of ubuntu
Current kernel source
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun
noobporter said:
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun
Click to expand...
Click to collapse
here it is, bear in mind that this is for CDMA devices
Unfortunatey, we have 4 other honeycomb threads.
Not trying to be rude but spacemoose updates us in the cdma forums AND we have russian rom updates in the gsm forums.
I really dislike the idea of this thread, there is enough clutter amongst the other threads. Do we really need one more place to browse..
The first posts in the roms thread are kept updated by devs.. Is this not enough??
daml said:
Unfortunatey, we have 4 other honeycomb threads.
Not trying to be rude but spacemoose updates us in the cdma forums AND we have russian rom updates in the gsm forums.
I really dislike the idea of this thread, there is enough clutter amongst the other threads. Do we really need one more place to browse..
The first posts in the roms thread are kept updated by devs.. Is this not enough??
Click to expand...
Click to collapse
yeah but we need a place for the other devs to share their milestones, here is a place for technical discussion amongst us, to share the knowledge etc...
the other threads are flooded from non devs messages, so it´s kind of difficult to read 14 pages of information when the 80% is people complaining not making it boot
lilstevie said:
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
Click to expand...
Click to collapse
Yes, and it contains some support for our device (s5pc110), and some more that can be added (pvr) and the architecture necessary to fully support HC without patching the build itself. If we work only towards patching the system build to communicate with the hardware, we won't be able to run AOSP hc versions when the source drops without going through the same painstaking process of hacking the system to function (while creating numerous faults causing FCs in the process). If we build a new kernel, we can get the hardware to communicate in the way future android versions want it to and we can then do what we want with ease.
noobporter said:
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun
Click to expand...
Click to collapse
D'oh! Nobody told me, LOL... I'll get another copy up.
spacemoose1 said:
D'oh! Nobody told me, LOL... I'll get another copy up.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1026528
hey spacemoose! the first portion of honeycomb source... The kernel source of the Asus EEE Pad Transformer... maybe it helps you with a few kernel issues, even if it's for another device... It's honeycomb!
Flokey said:
http://forum.xda-developers.com/showthread.php?t=1026528
hey spacemoose! the first portion of honeycomb source... The kernel source of the Asus EEE Pad Transformer... maybe it helps you with a few kernel issues, even if it's for another device... It's honeycomb!
Click to expand...
Click to collapse
Digging through it now.
spacemoose1 said:
Yes, and it contains some support for our device (s5pc110), and some more that can be added (pvr) and the architecture necessary to fully support HC without patching the build itself. If we work only towards patching the system build to communicate with the hardware, we won't be able to run AOSP hc versions when the source drops without going through the same painstaking process of hacking the system to function (while creating numerous faults causing FCs in the process). If we build a new kernel, we can get the hardware to communicate in the way future android versions want it to and we can then do what we want with ease.
Click to expand...
Click to collapse
Not enough really, PVR kernel module sources have been released from samsung for our device, and is available in update1 zip.
The kernel panics and we have no framebuffer from the nexus s, believe me that is the kernel I want to be running for my project, it is cleaner nicer and things are implemented overall better. unless you know of a solution for kernel debuging over usb
lilstevie said:
Not enough really, PVR kernel module sources have been released from samsung for our device, and is available in update1 zip.
The kernel panics and we have no framebuffer from the nexus s, believe me that is the kernel I want to be running for my project, it is cleaner nicer and things are implemented overall better. unless you know of a solution for kernel debuging over usb
Click to expand...
Click to collapse
Kernel debugging over USB = adb shell cat /proc/kmsg
You can make any kernel work for any device as long as you add the **** it needs. Just takes time. Working on it now.
Goal and tools updated*
spacemoose1 said:
Kernel debugging over USB = adb shell cat /proc/kmsg
You can make any kernel work for any device as long as you add the **** it needs. Just takes time. Working on it now.
Click to expand...
Click to collapse
You don't know what a kernel panic is do you?
lilstevie said:
You don't know what a kernel panic is do you?
Click to expand...
Click to collapse
I thought that linux throws a dump log when it makes a kernel panic specifying the memory address and the cause of crash
Made By :Spacecaker
What u need
windows or linux
ROM (that u wanna port to ace )
Dev Tools (like pack/unpack boot.img) Like this for windows and or linux
What u need to do??
unpack your boot.img
Change file on ramdisk
init.rc need to change >> (unpack the boot img from rom u wanna port
open init.rc and copy the stuff after BOOTPATH
change ramdisk/lib/modules >>> your modules ( not really importatnt )
repack ramdisk boot.img
Download the Guide below to get some pictures +
more tips download http://www.mediafire.com/download.php?u2ff9tthrrc29h1
Click to expand...
Click to collapse
orginel thread : http://forum.xda-developers.com/showthread.php?t=1574332
have you tried to port a kernel before? this guide doesn't mention about some spesific important stuff. it will definetely brick our device.
cool
a cool guide. find as pdf attached
this is only an example. our kernel partition is only 5mb. any size bigger wont work. then how about initbcrm2153 file?the zImage file? i've made two kernel. its difficult. port a kernel is more difficult and definetely not as easy as described in this post.
kurotsugi said:
this is only an example. our kernel partition is only 5mb. any size bigger wont work. then how about initbcrm2153 file?the zImage file? i've made two kernel. its difficult. port a kernel is more difficult and definetely not as easy as described in this post.
Click to expand...
Click to collapse
this guide is made by Spacecaker
he is developer ... so defenetly it will not brick our device .........
kurotsugi said:
this is only an example. our kernel partition is only 5mb. any size bigger wont work. then how about initbcrm2153 file?the zImage file? i've made two kernel. its difficult. port a kernel is more difficult and definetely not as easy as described in this post.
Click to expand...
Click to collapse
porting is too easy
if you have any doubts just check the attached file ! !
he also provided with SS ........
we can easily port it into our deveice
then...prove it. try to port a kernel from mini.
you also forgot this part. whithout this part our device won't work
===============================
then add/replace these in the rom it self ( copy from stock or cm7 )
These are Always needed !!
/lib/libril.so
/lib/libsecril-client.so
/lib/libsec-ril.so
/lib/libdiag.so
/system/hw
/system/modules
/system/etc/firmware , ppp, security, wifi, permission vold.stab
/system/user/keychars, keylayout
========================
one problem also comes from our recovery mode. unfortunately in our device it was stored inside kernel while in other device it was stored in different place.
It can Brick our Device
First Check it is Working and Then Post
thx for it i will try it
i dont think its that easy.. if it would hav been then we would hav had a kernel long back!!
hell_lock said:
i dont think its that easy.. if it would hav been then we would hav had a kernel long back!!
Click to expand...
Click to collapse
if porting means use kernel binary from one device to other device, not only not easy, but near to impossible. unlike pc which architecture is standardized, every cellphone have their own architecture make it impossible create generic kernel like you find in linux distro. you change hardware, it does't work. you mix with module from different version, it does't work. you mix with module from different compiler version, it does't work.
if porting means source code modification, that could be work, but need a lot of work. if someone ask how hard, last time i write my patch, i need about 6 hour just to add 2 lines modification in kernel source. i use linux in last 9 years and in real life i am a programmer, so reading c source code is something that i do almost everyday. still, i need that 6 hour because linux kernel source code is very complex.
and why op give this thread's title kernel. the tutorial is about using rom from other device using your original kernel.
irfanbagus said:
if porting means use kernel binary from one device to other device, not only not easy, but near to impossible. unlike pc which architecture is standardized, every cellphone have their own architecture make it impossible create generic kernel like you find in linux distro. you change hardware, it does't work. you mix with module from different version, it does't work. you mix with module from different compiler version, it does't work.
if porting means source code modification, that could be work, but need a lot of work. if someone ask how hard, last time i write my patch, i need about 6 hour just to add 2 lines modification in kernel source. i use linux in last 9 years and in real life i am a programmer, so reading c source code is something that i do almost everyday. still, i need that 6 hour because linux kernel source code is very complex.
and why op give this thread's title kernel. the tutorial is about using rom from other device using your original kernel.
Click to expand...
Click to collapse
thank you. i just wanna post the same thing before saw your post, and you're right indeed. theres no such thing as "porting kernel". binary kernel is specific, it'll only work with the device it were originally compiled for.
ROFL.....
BTW dont post tutorials , ports, etc that are somewhat copy paste and not tested it yourself..
Hey what about drivers... I wanted to get usb otg drivers on galaxy ace plus... Some dev ported it from galaxy s2 to galaxy s... But i dont have much knoladge of kernel development as i have windows... And i also found few lines about otg in my volt.fstab
# otg sdcard
{
ums_path = /dev/zero
asec = disable
}
usb_mount sdcard2 /mnt/sdcard/usbStorage auto /devices/platform/msm_hsusb_host.0
#end line ## keep this line
So i think it can support usb otg but doesnot have drivers...
Can any one help....or suggest something...
Sent from my GT-S7500 using xda premium
NICE!
Nice thanks!
kurotsugi said:
then...prove it. try to port a kernel from mini.
you also forgot this part. whithout this part our device won't work
===============================
then add/replace these in the rom it self ( copy from stock or cm7 )
These are Always needed !!
/lib/libril.so
/lib/libsecril-client.so
/lib/libsec-ril.so
/lib/libdiag.so
/system/hw
/system/modules
/system/etc/firmware , ppp, security, wifi, permission vold.stab
/system/user/keychars, keylayout
========================
one problem also comes from our recovery mode. unfortunately in our device it was stored inside kernel while in other device it was stored in different place.
Click to expand...
Click to collapse
Right. A Boot image is not completely independent of other partitions
Hi,
I'm looking for a kernel (uImage) with usbhost + multitouch + norefresh for my NST firmware 1.2.1.
Thanks
me too actually. Altough i would not have to be a uImage. Zip files would also be awesome
Have you tried this one?
http://forum.xda-developers.com/showthread.php?t=1906507
I know there is a version with no-refresh and USB Host, not sure about multi-touch,
I'm also looking for one. Have USB host with keyboard working but would like kernel for 1.2.1 with drivers for audio, multitouch, etc
David0226 said:
Have you tried this one?
http://forum.xda-developers.com/showthread.php?t=1906507
I know there is a version with no-refresh and USB Host, not sure about multi-touch,
Click to expand...
Click to collapse
posts on that thread said that only version 166 works on 1.2.1
but only last version (174) of this kernel has usbhost support.
Maybe I misunderstood
jeff_kz has kernel config code here:
https://github.com/doozan/NookManager/blob/master/Buildroot/kernel-config
dnordquest said:
jeff_kz has kernel config code here:
https://github.com/doozan/NookManager/blob/master/Buildroot/kernel-config
Click to expand...
Click to collapse
Thanks for the information about the kernel but I don't have the skill to compile a kernel.
And I don't know which options to turn on in kernel-config to have usbhost, multitouch and no refresh at the same time.
The following two sources for uImage contain the identifier: Linux-2.6.29-omap1.
http://nst-recovery.googlecode.com/files/uImage_usb_audio_test.zip
http://nst-recovery.googlecode.com/files/uImage_mt_usbhost_115.zip
That is the same identifier as the uImage I am using with 1.2.1. Whether either of the above will work with 1.2.1 I do not know & I am hoping someone with experience will say. Also, I am not sure if changes to any other file will be needed to get either running. The first file is said to have been deprecated, though why I know not.
I also do not know what drivers each contains besides those indicated in the name.
dnordquest said:
The following two sources for uImage contain the identifier: Linux-2.6.29-omap1.
http://nst-recovery.googlecode.com/files/uImage_usb_audio_test.zip
http://nst-recovery.googlecode.com/files/uImage_mt_usbhost_115.zip
That is the same identifier as the uImage I am using with 1.2.1. Whether either of the above will work with 1.2.1 I do not know & I am hoping someone with experience will say. Also, I am not sure if changes to any other file will be needed to get either running. The first file is said to have been deprecated, though why I know not.
I also do not know what drivers each contains besides those indicated in the name.
Click to expand...
Click to collapse
I actualy use http://nst-recovery.googlecode.com/files/uImage_mt_usbhost_115.zip on my nook 1.2.1. Usbhost and multitouch works but I can't enable norefresh on this kernel.
I've tried both uImages above & both work on my 1.2.1 but no-refresh unsolved here, too.
fhd kernel ( ZE551 ) & POSSIBLY hd (ZE550) with KVM & Bridge compiled. *need help*
MODERATOR NOTICE:
All thread posted in the Development section must have a link to kernel sources to meet GPLv2 requirements. Because this thread does not have proper sources linked and because development has stopped, the thread has been closed.
This is my first time working with Android kernels, but I compiled the 2.12.40 kernel source adding in support for KVM ( Kernel supported Virtual Machines, ie running Windows almost full speed ) and Bridge ( to allow qemu-kvm to set up network adapters bridged with the current wifi adapter ).
I tar'd the bzImage & modules, but don't know what to do to make something installable/flashable so will need help on that end of things.
Edit:
I uploaded a new flashable kernel img based off 2.19. This one should support: kvm, bridge and NTFS read/ *LIMITED* write, swap and ignore kernel module signatures. XDA only allows 8mb for .img files, so I tar'd it.
Edit2:
I compiled a ZE550 kernel ( called hd ) and if some brave souls want to try it, I also put together a boot.img.
Edit3:
New fhd kernel has been compiled with additional usb modules. Kernel should now load kvm related modules automatically, so you shouldn't need to use the script anymore.
Anyone brave/crazy enough to try it out? I'm guessing you need an unlocked bootloader & root.
Edit 4:
New fhd & hd kernels for 2.20
Edit 5:
New exfat.ko module
ycavan said:
This is my first time working with Android kernels, but I compiled the 2.12.40 kernel source adding in support for KVM ( Kernel supported Virtual Machines, ie running Windows almost full speed ) and Bridge ( to allow qemu-kvm to set up network adapters bridged with the current wifi adapter ).
I tar'd the bzImage & modules, but don't know what to do to make something installable/flashable so will need help on that end of things.
Anyone brave/crazy enough to try it out? I'm guessing you need an unlocked bootloader & root.
Click to expand...
Click to collapse
Why 2.12? 2.18 kernel source is available...
That just happened to be the kernel source linked in Android development. If this test works out, I can probably do the same thing with whichever kernel source is available.
Our phones are pretty amazing to be able to compile their own kernels natively on the device.
Sent from my ASUS_Z00AD using XDA Free mobile app
Finally able to compile the 2.18 kernel.. it's a bit weird since it acted like it was missing some files. Untar'd the 2.18 kernel source over 2.12's kernel source and that allowed it compile.
Anyway, it's in the OP called fhd_kernel_20150629.tar and should have KVM ( kernel supported virtualization ), Bridge ( for Qemu-KVM to create bridging ethernet adapters ) & NTFS Read/ *LIMITED* Write.
Once again, it's in the form of bzImage and the modules since I don't know how to replace the kernel on Android devices. ( normally, I'd just make a test linux line in the boot menu for Linux )
One suggestion would be to flash the zImage using
Code:
fastboot flash zImage nameofzImage
or test it using
Code:
fastboot boot nameofzImage
but I dont know if the phone supports the "boot" command.
I´m not sure about the modules either and I can´t test it, as my phone didn´t arrive yet.
Other solution, try this:
http://forum.xda-developers.com/showthread.php?t=2670512
ycavan said:
Finally able to compile the 2.18 kernel.. it's a bit weird since it acted like it was missing some files. Untar'd the 2.18 kernel source over 2.12's kernel source and that allowed it compile.
Anyway, it's in the OP called fhd_kernel_20150629.tar and should have KVM ( kernel supported virtualization ), Bridge ( for Qemu-KVM to create bridging ethernet adapters ) & NTFS Read/Write.
Once again, it's in the form of bzImage and the modules since I don't know how to replace the kernel on Android devices. ( normally, I'd just make a test linux line in the boot menu for Linux )
Click to expand...
Click to collapse
Can I ask how you included NTFS r/w support into your kernel? Did you just set the CONFIG_NTFS_FS flag?
TheSSJ said:
Can I ask how you included NTFS r/w support into your kernel? Did you just set the CONFIG_NTFS_FS flag?
Click to expand...
Click to collapse
I added CONFIG_NTFS_FS=m ( you could set to that y ) and CONFIG_NTFS_RW=y in /{working directory}/device/asus/moorefield/fhd/mofd_fhd_diffconfig
when you make the kernel, it's going to ***** about the config files not matching; follow the directions and manually update all of the other config files and it will finally compile.
Building for Android is a pita. )
Well, then here come the disappointing news (I discovered that when I wanted to include NTFS USB-OTG support directly by the kernel for my TWRP and it didn't mount it as R/W):
CONFIG_NTFS_RW is just a partial write support. It won't create files or folders, it can only overwrite existing files and only by the size they currently have
config NTFS_RW
bool "NTFS write support"
This enables the partial, but safe, write support in the NTFS driver. The only supported operation is overwriting existing files, without changing the file length. No file or directory creation, deletion or renaming is possible. Note only non-resident files can be written to so you may find that some very small files (<500 bytes or so) cannot be written to.
Click to expand...
Click to collapse
Only possibility available is to include ntfs-3g driver using fuse
Yeah, that is a bit of a downer. Now to figure out why nobody finished the NTFS kernel module.
ycavan said:
Yeah, that is a bit of a downer. Now to figure out why nobody finished the NTFS kernel module.
Click to expand...
Click to collapse
Please keep me posted, I'd like to remove the dependency of ntfs-3g in recovery. I fear there actually is no native support of NTFS (googling was not helpful unfortunately)
1) modify module loading function to ignore module version/magic strings.
2) compile the kernel with toolchain used by ASUS (or close to it)
3) use pre-compiled tntfs.ko from original boot.img
I don't have right now the patch for module loading procedure. Need to check old Galaxy S3/S4 custom kernels source (but it's should be easy to patch by finding error string). In time when exFat module source wasn't available, this trick was very common in samsung custom kernels for exFat support.
Thanks
Wait wait wait. Did I read that correctly? Full speed windows? On the zenfone? I think I just died. Does this mean windows 8/10 or windows xp and below?
I know a bit about android kernel, and i'm thinking about buying this device. Well, i'm going to try to build a kernel for this device as soon as i got this device. One thing you should know is, android is an open-source, so before you uploading your compiled kernel, make sure you have already uploaded the sources
LUCKYSHOT52 said:
Wait wait wait. Did I read that correctly? Full speed windows? On the zenfone? I think I just died. Does this mean windows 8/10 or windows xp and below?
Click to expand...
Click to collapse
It's only in theory.
In reality, there is no Z35xx support in windows, and i doubt anyone will write drivers by himself (windows isn't opensource). Officially Z35xx is Android-only SoC.
FajarMF28 said:
I know a bit about android kernel, and i'm thinking about buying this device. Well, i'm going to try to build a kernel for this device as soon as i got this device. One thing you should know is, android is an open-source, so before you uploading your compiled kernel, make sure you have already uploaded the sources
Click to expand...
Click to collapse
The source is already available, so no worries there, since this is source that Asus released.
For all of the brave folks out there, I was finally able to create a bootable image of the latest 2.19.20 kernel. Anyone brave enough can find it in the OP.
I flashed it and my phone booted up, so that's a bonus.
ycavan said:
For all of the brave folks out there, I was finally able to create a bootable image of the latest 2.19.20 kernel. Anyone brave enough can find it in the OP.
I flashed it and my phone booted up, so that's a bonus.
Click to expand...
Click to collapse
is there extra features such as other governor or i/o scheduler?
cangcan said:
is there extra features such as other governor or i/o scheduler?
Click to expand...
Click to collapse
To be honest? I can't remember since my main focus was getting kvm compiled in.
I've attached my .config for the 20150707 build ( in the boot image ).
I've also attached a screenshot of Windoze 7 being installed.
Commandline for Arch Linux x86_64 to start qemu-kvm to install windoze:
qemu-system-x86_64 -display none -vnc :1,password -monitor stdio -m 1G -smp 4 -enable-kvm -drive file=/mnt/0/machine1.img,format=raw -cpu host -cdrom /mnt/MicroSD/Vcd/en_windows_7.iso -boot menu=on --usbdevice tablet
breakdown of the command line:
-display none = no display, I did this to test the virtual machine. normally, you would probably use -display sdl w/ XServer-XSDL running
-vnc :1,password, This says to set up a vnc server with normal port + 1 ( 5901 ) and you expect a password to be set later
-m 1G, 1 gig of ram
-smp 4, our VM will use 4 cores
-enable-kvm, enable Kernel support Virtual Machines
-drive file=/mnt/0/machine1.img,format=raw, my "disk" file
-cpu host, use the same cpu information
-cdrom /mnt/MicroSD/Vcd/en_windows_7.iso, my Windows 7 install cd turned into an iso
-boot menu=on, enable the boot menu ( hit F12, etc.. )
--usbdevice tablet, Qemu's Vnc server sucks at tracking mouse positions so using tablet mode keeps the mouse pointer .. well on-point
Tks for share
Kernel great work
But how to install window 7 ? ?
Gửi từ ASUS_Z00AD của tôi bằng cách sử dụng Tapatalk