Trying to OC will the methods used on 902/905 work?
Sent from my DROID BIONIC using xda app-developers app
When someone pulls the kernel config and uses it to recompile the overclock.ko or the opptimizer.ko modules that they used from before then it will work. The modules need to be compiled for this versionvor you will get an exec fotmat error or something like that
If you google pull kernel config there will be awnsers to pullingvworking kernel config from phone.
Then google building cyanogen rom kernel from scratch. There it will tell you what to download and install to build a working kernel. Then use the config from you bionic on ics instead of building your own. Then compile the new overclock.ko module and maybee some can get a working twain.ko for free wifi teather.
Related
Kernel newbie here. I've been looking for instructions on how to add netfilter support to the android kernel (2.6.29 in kernel/msm from android.git.kernel.org), but coming up dry. I've asked around before but all I've heard is "you have to add a lot of lines of code" basically saying I need to do copypasta for the netfilter module to get it enabled in the kernel. I read somewhere else that I should use toolchain arm-eabi-4.3.1 and the option to enable netfilter support should be in the kernel's .config and it's just a matter of saying 'Y' to it.
I tried it, but I still couldn't get wifi-tether to work once I had built the kernel and wlan modules.
I haven't much experience in the linux kernel (actually, other than building it, this is the first time I've tried to modify anything, so I'm tackling it head-on), so I need some guidance.
Any experienced linux-heads willing to help?
I'm trying to get the kernel I've been working on for Captivate working on Vibrant. This poses a bit of a problem, because while I have access to a Vibrant kernel and initramfs, and a known-working config for Vibrant, I lack access to a phone.
I've forked a test branch based on what I have so far. I would appreciate pretty much any of the following:
a volunteer to build this kernel or test a binary
a volunteer to help with Vibrant development
any other Vibrant-specific details that don't apply to Captivate or to SGS in general
I have already built a binary, but it is mostly untested. I want to make it very clear that this is a testing kernel. It should work, it should not break anything... but it might not boot, it might wipe data, I haven't heard of it happening to anybody yet but it's certainly not impossible that it might damage hardware. These are unlikely, except for not working, but are all possible outcomes of trying this kernel. If you want to test this, read the OP in the thread for the Captivate version, have backups of your data ready, preferably duplicated to a hard drive or an SD card that is removed before testing. Have Odin3 and a stock Vibrant kernel on hand, and have ClockworkMod recovery installed.
If it hangs starting up, wait a bit, then pull the battery and start in recovery without trying to start up normally. Then, start clockworkmod, mount /system, and use adb to pull /system/user.log - this should contain a log of what happened when the user init scripts ran, and may provide clues as to what went wrong. You can make sure it doesn't include anything you don't want to reveal, and just PM it to me or join #sgs_dev on freenode and talk to me or some other developers there - perhaps a dev with a Vibrant will have a better idea where to start.
In the long term, I would not mind somebody forking the github repository to work on any Vibrant-specific issues. I can then try to pull changes from a fork and do builds for both phones, if somebody doesn't want to do the Vibrant builds themselves.
Good luck, and thank you.
if no one volunteers by the time I finish installing openSUSE I'll give it a whirl. the binary that is.
Sent from my SGH-T959 using Tapatalk
ill be more than happy to test the binary
I too will be more than happy to give any sort of help possible. Should this be a start from a stock kernel and build deal, ie stock kernel stock rom just rooted with clockwork?
Sent from my Vibrant using tapatalk pro
If you're using a lagfix with the playlogos hack you should undo it first, or set up your user init script to run in the new early user init. Other than that anything that works with a stock kernel should still work.
Sent from my SAMSUNG-SGH-I897 using XDA App
EDIT: "lagfix", thx swype.
Unhelpful said:
If you're using a ladies with the playlogos hack you should undo it first, or set up your user init script to run in the new early user init. Other than that anything that works with a stock kernel should still work.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I'm about to build from your source i just forked to see whats diff then mine. They look though to be about the same except for nilFS
I will probably fork and maintain a vibrant tree with ivan who also has a Vibrant. That way we can get the best of both worlds. And being that we are in the same IRC we pretty much have identical mods to our kernels.
So most likely any changes you make to your captivate Kernel will end up in the vibrant branch as well and I also have the device to test with
See ya in IRC
anomalous3 said:
if no one volunteers by the time I finish installing openSUSE I'll give it a whirl. the binary that is.
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
haha if ur talking about the linux distro i know what u mean
Excellent news! I have some things in my tree I think you could use here, too, but it's much easier to have a developer with a Vibrant who can build them and test immediately.
What advantages does the captivate kernal have over the vibrant kernal, if any?
Sent from my SGH-T959 using Tapatalk
rei165 said:
What advantages does the captivate kernal have over the vibrant kernal, if any?
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
The stock captivate kernel doesn't have any "advantages" and wouldn't really work. Unhelpful, however, has added nilfs support to the captivate kernel as well as some other tweaks, and has now made these changes available to the Vibrant community. As I understand it, NILFS mounts, reads, writes, and unmounts faster on our devices than any of the other filesystems he tested, so there's hope for a permanent lagfix.
I tried this kernel, it does boot but my existing lagfix scripts don't work with it, so I lose all my data. No big deal to fix from recovery, just revert to stock before messing with it if you want to test it. As mentioned, no real advantage either way, but it's nice to have options.
If there is interest, I'll fix my lagfix scripts to run on this kernel. Reverting back to JAC OVv4 works without hassle via clockwork.
Just out of curiosity, is it at all possible to flash a kernel from a different phone? I noticed that the Droid Incredible has 2.6.32.17 while we are still at 2.6.29.6.
What all is involved with porting it over? I'm sure the source code is needed.
No it's not possible (different hardware). However, both Darch and Deca are working to get the HeroC onto the .32 kernel.
Thanks for the reply. I don't know why the hardware issue didn't click in my mind. I guess I was thinking that since they are both CDMA networks that they would work.
The kernel has hardware specific info in it. The 2 devs working on it are basically taking the base kernel and adding and modifying it to work on our phone. Its very time consuming and a lot of trial and error.
Sent from my HERO200 using XDA App
Hello all,
Forgive me if this has been asked/requested before. Is there a version of the cifs.ko module that is compiled for any of the current custom ROMs? I am looking for this file or would like to know how to compile it for a custom ROM. It is used to mount Windows SMB fie shares to our Captivate. I am currently using Cog's 2.2 Beta 9 ROM but it does not have the cifs.ko file.
Programs such as File Expert or Cifsmanager can handle the mounting once the cifs.ko file is present.
Any help would be appreciated,
Thanks in advance for any advice or direction to solving this issue.
I think not only cifs.ko. For double bytes characters support, nls_utf8.ko is also a must. If anyone can compile based on froyo source, it'll be awesome.
agreed on the double byte char
agreed that second file is required but as a start the cifs.ko is required. Fingers crossed someone can assist us,
Wow! Dead subject I guess
I thought this would be provide some great functionality to our Captivates but I guess it's just the two of us who are interested in such features. The adventure was fun while it lasted.
Juxtyce
http://forum.xda-developers.com/showthread.php?t=774321
peep this guys
I'm using Serendipity 5.12 with the Speedmod K13C kernel, and it definitely includes CIFS. There's an option in CWM to enable/disable it. I've been using it quite a bit with CIFSManager and Mount Manager.
juxtyce said:
Hello all,
Forgive me if this has been asked/requested before. Is there a version of the cifs.ko module that is compiled for any of the current custom ROMs? I am looking for this file or would like to know how to compile it for a custom ROM. It is used to mount Windows SMB fie shares to our Captivate. I am currently using Cog's 2.2 Beta 9 ROM but it does not have the cifs.ko file.
Programs such as File Expert or Cifsmanager can handle the mounting once the cifs.ko file is present.
Any help would be appreciated,
Thanks in advance for any advice or direction to solving this issue.
Click to expand...
Click to collapse
Most newer Speedmod and Voodoo based kernels include support for CIFS natively. In fact, with Speedmod it's simply a tweak enabled via recovery. I don't use Voodoo, so I won't say for certain, but I think it's enabled by default in most of the newer builds.
Also, it's worth mentioning, that cifs.ko, and associated helpers tend to only work correctly on a specific build of Android. So taking the cifs.ko from an older 2.1 version of Android will probably NOT work on any of the newer JPX-range or JSX-range of ROMs.
Shammyh said:
Also, it's worth mentioning, that cifs.ko, and associated helpers tend to only work correctly on a specific build of Android. So taking the cifs.ko from an older 2.1 version of Android will probably NOT work on any of the newer JPX-range or JSX-range of ROMs.
Click to expand...
Click to collapse
Exactly. The kernel module (.ko file) needs to be compiled against the source of the rest of the kernel or it will not load. I highly doubt that you will find a CIFS or TUN (for OpenVPN) module that is compiled against a generic source (JPX, KB1, etc) just floating around here. All of the CIFS and TUN support that I've seen are built in to the kernels themselves. If you want these features it's as simple as flashing SuckerPunch, SpeedMod, Firebird 2, or any other kernel for the Captivate that has that support built in. I use Firebird 2 v0.8.
If you don't want to flash a kernel, you have another route. You need to figure out what kernel source you are running (the version, such as 2.6.32.9, will likely not be good enough - you'll need to know if it's JPX or KB1 or something else), find a Captivate kernel that is based on that version, and either download the kernel and extract the zImage file to get the modules or PM the author and they might be kind enough to give you just the modules that you are looking for. This route is way more work and not guaranteed to work, but Linux is all about choices and that is what makes it fu*king awesome.
Good luck!
Hi all,
I have a rooted sm-t810 running stock marshmallow kernel 3.10.9.8374498 and I have been trying for a long time to add support for my xbox 360 wireless dongle and controllers.
I read a lot online about it and it seems that I need to load a specific module (xpad.ko) that is not available by default in my kernel.
However I have no idea where to find one that is compiled and compatible with my kernel and I have absolutely zero experience with compiling the kernel and/or the module from source, I wouldn't know where to begin or what to do about it.
From what I understand I should download the source of my kernel in a linux desktop, compile the module in it, copy the compiled module to my decide and run insmod it, but again, I have zero experience in all this.
Could somebody help me by giving me the compiled xpad.ko for my kernel?
If not, could you tell me step by step what should I do it to do it myself assuming im a total ignorant in kernels,modules, their compilation, the specifics about android, and everything around it ?(before yesterday I didn'teven ever rooted my tablet )
Thank you in advance if anybody is willing to help!
Cheers,
Mastro