Related
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.
Hey Guys/Girls,
Could really use some help. For the life of me I can't compile a kernel module driver ath9k for my USB wireless adapter TL-WN722N. So it can be used by insmod on my rooted Galaxy Note 8.0 GT-N5110 on Kernel 3.0.31 Build BMC9 running android 4.1.2. The source code is available at on Samsung open source library and is listed as the GT-N5110 NA (north america) model. If some one could help me please? I would be forever in your debt... :good:
xPARSONSx said:
Hey Guys/Girls,
Could really use some help. For the life of me I can't compile a kernel module driver ath9k for my USB wireless adapter TL-WN722N. So it can be used by insmod on my rooted Galaxy Note 8.0 GT-N5110 on Kernel 3.0.31 Build BMC9 running android 4.1.2. The source code is available at on Samsung open source library and is listed as the GT-N5110 NA (north america) model. If some one could help me please? I would be forever in your debt... :good:
Click to expand...
Click to collapse
I'm having the exact same issues, i need the rt2x00 modules (however i do have a TL-WN722N so ath9k could work too). It seems Samsung has made this near impossible. I have literally been working around the clock with other developers to figure out what the hell is going on. Civato seems like our only hope at the moment however (not many devs for the note 8). Anyway, if anybody is willing to help I need the modules for the GT-N5110_JB_Opensource.zip (can be found on the samsung open source aswell)
cheers
xPARSONSx said:
Hey Guys/Girls,
Could really use some help. For the life of me I can't compile a kernel module driver ath9k for my USB wireless adapter TL-WN722N. So it can be used by insmod on my rooted Galaxy Note 8.0 GT-N5110 on Kernel 3.0.31 Build BMC9 running android 4.1.2. The source code is available at on Samsung open source library and is listed as the GT-N5110 NA (north america) model. If some one could help me please? I would be forever in your debt... :good:
Click to expand...
Click to collapse
C3PBRO said:
I'm having the exact same issues, i need the rt2x00 modules (however i do have a TL-WN722N so ath9k could work too). It seems Samsung has made this near impossible. I have literally been working around the clock with other developers to figure out what the hell is going on. Civato seems like our only hope at the moment however (not many devs for the note 8). Anyway, if anybody is willing to help I need the modules for the GT-N5110_JB_Opensource.zip (can be found on the samsung open source aswell)
cheers
Click to expand...
Click to collapse
Try this kernel (just new and not yet public) ONLY FOR ANDROID 4.1.2 (4.2.2 version will follow in the Stormcharger thread)
CivZ-StormBorn_Rev2.5-Android4.1.2-GT-N5110.zip
Build in so no modules
Native Exfat support added
Realtek RTL8192CU/RTL8188CU USB Wireless Network Adapter support
Ralink driver support : Ralink rt2500 (USB) / Ralink rt2501/rt73 (USB) / Ralink rt27xx/rt28xx/rt30xx (USB) /
rt2800usb - Include support for rt33xx , rt35xx , rt53xx
Atheros Wireless Cards
Perseus for the E300K, E300S & E300L
Please read the FAQ.
Notes:
* I have not tested and have no way of testing the E300L. I have made the initramfs files available. If something doesn't work and you have any experience with ramdisks, please try to fix. At this point if something doesn't work it could be the zImage or the ramdisk.
Test 3 for E300L:
I haven't given up on the e300l but I won't have any time until after 9/23.
cwr-perseus-e300l-test1.zip (5.2 MB)
odin-perseus-e300l-test1.tar (5.1 MB)
cwr-perseus-e300l-test2.zip (5.2 MB)
odin-perseus-e300l-test2.tar (5.1 MB)
Click to expand...
Click to collapse
Changelog:
- build 091413 Latest
separate defconfig for each device (perseus_e300k_defconfig, etc)
MH2 OSRC source code
added support for E300L (untested)
removed some unnecessary code
made sperate kernels for each device
- build 090513
updated initramfs to fix bootloop on E300S
- build 090313
fully compatible with E300S
build with linaro toolchain
updated initramfs
- build 090213
DMB fixed
- build 082913
perseus alpha9 (as of Aug 29)
perseus_e300k_defconfig updated
Ad-hoc (IBSS) support added to kernel
audio tab removed from stweaks
battery tab added to stweaks
- build 082713
perseus alpha8 (as of Aug 17)
samsung mg2
first build
hardware added ymu831, dmb, modem
stweaks support
Kernels - flash via recovery:
cwr-perseus-e300k-091413.zip (6.6 MB)
cwr-perseus-e300l-091413.zip (6.5 MB)
cwr-perseus-e300s-091413.zip (6.6 MB)
Kernels - flash via Odin:
odin-perseus-e300k-091413.tar (6.4 MB)
odin-perseus-e300l-091413.tar (6.5 MB)
odin-perseus-e300s-091413.tar (6.4 MB)
Kernel Source Code:
perseus-e300x-091413-src.tar.gz (116.2 MB)
Ramdisks:
e300k_initramfs.tar.gz (2.4 MB)
e300l_initramfs.tar.gz (2.3 MB)
e300s_initramfs.tar.gz (2.4 MB)
Be sure to thank AndreiLux for making this possible.
How-To
This is how I set my E300K. You can do it however you want but I know this works. If you have an E300S you need to use the firmware for your phone.
- backup and important data on SD and microSD
- shutdown
- remove sim & microSD
- vol up + home + power to cwr - factory reset - power off
- vol down + home + power to odin - [No Auto Reboot] - flash (E300KKKUAMG2_E300KKTTAMG2_HOME.tar.md5 or firmware for E300S) - remove battery
- vol up + home + power to recovery but will boot to OS
- quick setup OS ("next", "skip" or "no" to everything)
- settings - accounts - backup & reset - factory reset
- quick setup OS ("next", "skip" or "no" to everything)
- settings - more - unknown sources
- connect to PC - copy UPDATE-SuperSU-v1.32.zip to SD
- vol down + home + power to odin - [No Auto Reboot] - flash (i9500-cwm-recovery-6.0.3.2-2.tar) - remove battery
- vol up + home + power to cwr - install zip from sd (UPDATE-SuperSU-v1.32.zip)
- reboot
- shut down
- insert sim
- boot
- enable data or wifi - software update - "modified .. blah, blah"
- open Play - update superSu app & install Busybox or Busybox Pro
- exit Play
- superSU - update binary (Normal) - exit
- Busybox - Root Perm. (Grant) - Backup (No) - Install (Smart Install) - Option "Auto Update Busybox" (No) - exit
- if using microSD - BEGIN
make directory /etc/init.d
make script for exfat
---
#!/system/bin/sh
insmod /lib/modules/exfat_core.ko
insmod /lib/modules/exfat_fs.ko
---
change permission of script to 755
- if using microSD - END
- boot OS
- update all apps via Google Play, Olleh Market, Samsung Apps, etc.
- restart
- vol up + home + power to cwr - install zip from sd (kernel)
FAQ:
1. Why is this in the i9500 thread?
The Galaxy S4 has many variations. SHV-E300K is one of three models sold in South Korea. Since XDA only has a small number of users of this variation, the moderators do not make separate sections for this device.
2. Will you make a kernel for the e300s and e300l?
This depends on if the people testing the devices I don't own can help me make them work. The more useful information you give me, the more likely the kernels will work.
3. XYZ doesn't work. What can I do?
PM me, not AndreiLux. Tell me as much as you can so I can try to recreate the problem.
3. How do I use init.d feature?
make folder /etc/init.d
put your scripts in /etc/init.d/
chmod your scripts
4. How do I mount an SD Card?
4a. (Option 1) load exfat_core & exfat_fs from terminal and then Settings - More (Tab) - Storage - Mount SD Card
4b. (Option 2) load modules via init.d5. Can you add xyz feature?
I will certainly try.
6. STweaks is force closing. What can I do?
The "unexpected error" seems to mostly occur due something messing with busybox in /sbin.
If you are using Busybox Installer (Stericson), Uncheck or decline the option to disable busybox in /sbin.
To get to the Settings page, swipe two pages to the left. There is a check box at the top. This option disables the copy of busybox built into the kernel.
Glad to meet you koe1974 again
Can I add the link of your thread in my thread?
can we also get perseus kernel for E300L ? would love it. please try to develop this kernel for E300S and E300L
I've been waiting for this, anyone know where I can buy a SHV-E300K for a reasonable price?
You know that perseus kernel is for universal 5410 exynos?
SHV-E300K is a i9505 variant which uses snapdragon and you cannot port every feature
btw: this is the wrong section and without kernel source you will get into trouble
Grarak said:
You know that perseus kernel is for universal 5410 exynos?
SHV-E300K is a i9505 variant which uses snapdragon and you cannot port every feature
btw: this is the wrong section and without kernel source you will get into trouble
Click to expand...
Click to collapse
SHV-E300K is an Exynos 5410 phone with LTE support.
Research before posting useless posts.
Grarak said:
You know that perseus kernel is for universal 5410 exynos?
SHV-E300K is a i9505 variant which uses snapdragon and you cannot port every feature
btw: this is the wrong section and without kernel source you will get into trouble
Click to expand...
Click to collapse
The SHV-E300K is not a variant of the I9505. It is a variant of the I9500. And yes, while the source code is for a "UNIVERSAL" 5410 chipset, there are still tons of things that need to be done in order to actually make it work with either phone. I.E. .. ril code, wifi supplicants, cpu governers, audio, and the list does go on. It takes a lot of hard work and patients to get it to work with either phone to be honest. And no this isn't the wrong section due to the fact that it is part of the the I9500 family. We do not have and will not have our own thread for this phone because it is considered a localized phone branding.
lunerceli said:
The SHV-E300K is not a variant of the I9505. It is a variant of the I9500. And yes, while the source code is for a "UNIVERSAL" 5410 chipset, there are still tons of things that need to be done in order to actually make it work with either phone. I.E. .. ril code, wifi supplicants, cpu governers, audio, and the list does go on. It takes a lot of hard work and patients to get it to work with either phone to be honest. And no this isn't the wrong section due to the fact that it is part of the the I9500 family. We do not have and will not have our own thread for this phone because it is considered a localized phone branding.
Click to expand...
Click to collapse
Sorry my bad
Samsung just released too many s4
Sent from my GT-I9500 using xda app-developers app
Grarak said:
Sorry my bad
Samsung just released too many s4
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
Its all good. I wasnt trying to be mean ir anything. Just heloing out with the knowledge flow.
Sent from my SHV-E300K using Tapatalk 2
Koe, getting random crashes with compatibility layer, cloud service agent, and random with com.android.phone. I went back to your old kernel until I get off work and then I will reinstall this kernel and send a log cat...
Also getting baseband service stopped responding. But it recovers once the phone boots completely.
Sent from my SHV-E300K using Tapatalk 2
lunerceli said:
went back to your old kernel until I get off work and then I will reinstall this kernel and send a log cat...
Sent from my SHV-E300K using Tapatalk 2
Click to expand...
Click to collapse
Also let me know if you have frozen/hibernated/uninstalled things from the stock rom.
I am testing against a rom with only a few things frozen and nothing removed.
Sent from my SHV-E300K
koe1974 said:
Also let me know if you have frozen/hibernated/uninstalled things from the stock rom.
I am testing against a rom with only a few things frozen and nothing removed.
Sent from my SHV-E300K
Click to expand...
Click to collapse
Nope, nothing frozen/hibernated/uninstalled from stock rom. I know the baseband service stopped error only happens at boot and then it recovers itself. The others will randomly stop and then quickly recover .. maybe you could turn off show error msg dialogue within the kernel since these services are actually recovering and not hindering anything?? Oh, and I have started work on the K device tree today, made a little bit of progress. It is just going to take all weekend to download the CM10.2 sources. But what I was planning on doing, with your permission of course, is adding your sources into the kernel build of CM and working it that way. With things like this, we would be working together on making this build possible and working out the bugs for each would be a lot faster .. let me know what you think...
lunerceli said:
let me know what you think...
Click to expand...
Click to collapse
It is all open source so what's mine is yours.
Sent from my SHV-E300K
koe1974 said:
It is all open source so what's mine is yours.
Sent from my SHV-E300K
Click to expand...
Click to collapse
Yeah, but it's still the principle of asking permission though. I am old fashioned like that .. LOL.
Thanks
I use E300K~!
Thanks!
But Stweaks is not Working..
and Please UPDATE Matcl..
[Sorry. I don`t speak English..]
DukoOsu said:
But Stweaks is not Working.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2404954
Sent from my SHV-E300K
And dmb is not working too.
No dmb signal.
Same problem korea E300K user.
---------------------------------------------------
Sorry. I don't speak English
Sent from my Korea GS4 E300K
I cannot repair the error of the STweaks at all.
Isn't there kerenl problem ?
---------------------------------------------------
Sorry. I don't speak English
Sent from my Korea GS4 E300K
DukoOsu said:
I cannot repair the error of the STweaks at all.
Isn't there kerenl problem ?
Sent from my Korea GS4 E300K
Click to expand...
Click to collapse
You must tell me more information. What rom are you using? Which Busybox installer? Logcat log, please. Etc..
Sent from my SHV-E300K
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
Hi guys.
I have been working on a project to port NetHunter to Jiayu S3 (advanced for me , MT6752 platform) , working okay so far.
Tho I was still unable to start a new thread in DEVELOPMENT area . This is my first post in XDA. XDA helped me for many informations tho mostly all I care is the dev area so unable to say even a thank-you.
Any way I am here preparing to make a contribution for XDA. More talk with me so I can post the project earlier.
Kernel is modified and patched based on LoliTeam's project on Github.
mac80211 patched with script provided by Offensive-Security , HID manually patched regarding "Kernel-3.10-Nexus9.patch". Not exactly the same yet similar.
Additional Package of NetHunter is built under construction of [email protected]
Tested on AICP 6.0 UNOFFICIAL for JIAYU S3a MT6752 ( Should work on JIAYU S3 normal too I guess. never tried )
Progress:
OTG: Fix the 5V Power Supply for OTG so we can mount more than a USBdisk , like Mouse/Keyboard/JoyStick/WirelessAdapter , all avaliable now.
DuckHunter HID attack: working. Tho simple HID attack item didnt work , no idea why.
BadUSB MITM: RNDIS enabled. Capable to redirect the traffic of the computer you connected through your phone. (DHCPD on phone required, do it manually)
WiFi MITM: built-in wireless adapter does not support Monitor Mode so built-in Nethunter WiFi MITM does not work either. But we can do it manually , with a external USB via an OTG cable
Kali Chroot: Working
USBkeyboard(as HID device): Working
cSploit: Working
Shodan: Working
OpenVPN for Android: Working
VNC: Working
MSF: Working
Not working:
aircrack-ng toolkit: seldom working. But can be replaced by manually command.
War Driving: not working normally , because aircrack-ng. Not planning a fix.
Router Keygen: Only support built-in adapter. Giving it up.
Not tested:
RF Analyzer: No equipment. No plan on it.
Unsolved:
$ifconfig wlan1 mode monitor Wrong command but cause phone stuck (may be kernel panic)
Mana-Toolkit with wlan1 same , phone no responding. SO DO MITM MANUALLY , dont use mana.
Problems:
Battery Power is consumed faster.
Easier to heat up.
I think they are bearable
It has many drawbacks but still working great considering its condition.
Keep project on track:
@ https://github.com/offensive-security/kali-nethunter
@ https://github.com/DKingCN/nethunter-devices
@ https://github.com/DKingCN/android_kernel_jiayu_s3_h560
@ https://github.com/DKingCN/android-keyboard-gadget
Now you are able to build it on your own.
I will release it later when I got enough posts.
Thread closed by OP request.