I have been combing through my devices LOS kernel source on github looking for the 192.168.xxx prefix applied to usb and wireless networking subnets. Can someone point me in the right direction? I'm bent on changing the prefix to 10.0.xxx range. I'm going to compile the whole ROM to find it next....
Thanks!
Related
I have the wifi only version of the SGT7.7 and it annoys me that the built in wpa_supplicant filters out ad-hoc networks. I am in the process of setting up a development environment for this device but I need the right version of the wpa_supplicant source code. Anyone point me to it?
In any case, this process is somewhat like bashing my head against a brock wall - given the various different toolchains, etc. Anyone want to post a compiled version of ad-hoc wpa_supplicant for this device and put me out of my misery?
Multiple hits out there on the interwebs for other Android devices but none of them work on mine. So far. Size of the binary is way too small in most cases.
This device is running Honeycomb (3.2) right now - fingers crossed for ICS soon. I have rooted it, of course.
# ./wpa_supplicant -version
wpa_supplicant v0.8.x
Copyright (c) 2003-2011, Jouni Malinen <[email protected]> and contributors
Source found
at github.com/CyanogenMod/android_external_wpa_supplicant_8.git
don't know if it's the right source, given it's the ICS stream.
Any joy with this one? I too am after a wpa_supplicant that will enable ad-hoc on SGT7.7.
working on it
Not yet. Still trying to get the right toolchain setup so this thing compiles without error. In my limited free time.
Thanks texkelly. Appreciate the effort.
If there's any testing I can help out with I'd be happy to. I have a rooted SGT 7.7 and have tried the variety of wpa_supplicant files that are already available.
Resurrecting an old thread.
Any updates on this? It would be very helpful to enable ad-hoc so I can share my Smartphone's/Laptop's connection easily.
Thanks in advance.
Extra reading:
http://szym.net/2010/12/adhoc-wifi-in-android/
http://www.olsr.org/?q=olsr_on_android
Tried olsr (rel 0.5) on P6800 but isn't working. Is there a newer version (rel 0.6) here http://www.olsr.org/releases/0.6/ but not a precompiled samsung android version for binaries.
At this moment for adhoc wifi usage only chance is to use CM (9 & 10) but unfortunately both version suffers in wifi drivers (Atheros closed sources drivers) and are still unstable - tethering issues, signal quality, bizarre activation behaviour...
Resurrecting the thread. Anyone?
Hello
Can anyone point me to a guide or summary of alternative kernels please?
You can check our work on the nook color linux kernels in this thread here. http://forum.xda-developers.com/showthread.php?t=1370873&page=285
I also have a guide on using the Git and the Gerrit code review down in cyanogenMod central for the nook color linux tree at this thread link here. http://forum.cyanogenmod.com/topic/50994-follow-along-with-me-trying-to-learn-how-to-code/
If you want to help and have experience on building linux kernels feel free to post a follow up in the first link I have posted. We are using the git and the github to commit code for our linux kernel tree. If you need help on getting up and going on using git, look through the second link I gave, I have all of the links on the github for our project and other helpful tips for you to get started. Right now the top developers are committing code to the jellybean branches. <fat tire> is our top developer and github maintainer for the nook color linux kernel tree, you can find him in the first link I provided and can help you also.
Thanks. I'm able to put a kernel together, but i haven't much experience in original development. I'll keep an eye on that thread though!
Right now we are looking for a few debuggers for the Jelly Bean Kernels. You know how to use debuggers? We need to check for kernel opps that are not being caught by the machines. Last year here there was a developer that rooted 2 kernel opps out and submitted them to Gerrit as a patch. Henk Poley , the developer for the Git extentions used his app and rooted out a few kernel opps on the cyanogenMod stable 7.1 at the time. Check out the my link on debuggers if you are not sure how. Not glamous work but it needs done, and I am getting up and ready to go back to school. Might do that if you want to help.
<Eyeballer> here is looking for someone to strip out all the unnecessary phone .apks for the nook color cyanogenMod builds, like the phone.apk and the telephony.apk along with the voicedialer.apk. I was going to get started on doing that but got sidetracked on getting a proper workflow going on the github. That second thread has links on how to submit work and patches down at cyanogenMod.
~~~~~~~~~~~~~~~
If you are up to a more difficult challenge the wi-fi module needs more work on the Jelly bean builds, they are still getting wake lock problems with it. A few months ago the developers disassembled and reassembled the wi fi module and could not find any code conflicts within the driver or the module. They can fill you in on that up in IRC at #nook color if you want to follow up on that.
Wow. Uh, I don't actually use a debugger, I'm pretty new to building kernels. I used to program C++ in Visual Studio, but so far haven't investigated the debugging process. In my own kernels I use printk, and that's about as sophisticated as it gets.
I wish I could help, but I need the device to available at the moment for my young daughter. Good luck with JB. I'll consider helping if my situation changes.
Hi guy's!
I am BlackFoxy, and i start make sources for ASUS Zenfone 2 Laser
But i need help
If you can, please help me
I in Facebook - https://www.facebook.com/misha.scvorzov
Device sources and more you can see on my GitHub Profile - https://github.com/BlackFoxy757
M here !
Love to help @Shanmugam k @Sujeet Ranipa
What exactly do you need help with?
hardslog said:
What exactly do you need help with?
Click to expand...
Click to collapse
Help with make kernel and correct device and vendor tree
BlackFoxy757 said:
Help with make kernel and correct device and vendor tree
Click to expand...
Click to collapse
Ok I'll give you a little information
1) There is a very highly likely chance that the laser-auto-focus will not work. Of course we don't know until we try but I am not confident because getting things like that which are not in common android source code is very difficult to get working.
2) There are many versions of the ZF2 laser, some come with different kernels therefore will need sources for each kernel (potentially). They also might share the same source (won't know unless I take a good look at it)
3) I am downloading the Kernel source for the ZE551KL and will upload it to github for a starting point. You can easily fork it from there into your github repo. It should be up in a day or less. By the looks of your github repo, you have a different model (one with a 410 snapdragon). Kernel sources are available from the asus.com website under support. You can download it from there for now and I can show you how to upload it to github.
4) If you plan on supporting all the ZF2 laser models, I would suggest for the device repos to make a "common" repo as they will share a lot of the same code, then have separate repos for each model for all the unique characteristics of them.
Edit: kernel uploading to my github. Internet is slow but you can see it soon by going to https://github.com/Hardslog/android_kernel_asus_zf2l
hardslog said:
Ok I'll give you a little information
1) There is a very highly likely chance that the laser-auto-focus will not work. Of course we don't know until we try but I am not confident because getting things like that which are not in common android source code is very difficult to get working.
2) There are many versions of the ZF2 laser, some come with different kernels therefore will need sources for each kernel (potentially). They also might share the same source (won't know unless I take a good look at it)
3) I am downloading the Kernel source for the ZE551KL and will upload it to github for a starting point. You can easily fork it from there into your github repo. It should be up in a day or less. By the looks of your github repo, you have a different model (one with a 410 snapdragon). Kernel sources are available from the asus.com website under support. You can download it from there for now and I can show you how to upload it to github.
4) If you plan on supporting all the ZF2 laser models, I would suggest for the device repos to make a "common" repo as they will share a lot of the same code, then have separate repos for each model for all the unique characteristics of them.
Edit: kernel uploading to my github. Internet is slow but you can see it soon by going to https://github.com/Hardslog/android_kernel_asus_zf2l
Click to expand...
Click to collapse
Yes. I think supported all Z2L
Thank you... we are waiting for you
How is it going?
do you can please creat a custom rom for ze500kl
BlackFoxy757 said:
Yes. I think supported all Z2L
Click to expand...
Click to collapse
There is already a custom ROM for Z00T and Z00L, and I think you should make one for a device that don't have it. Like Z00ED. Also I think you need to have the device so you can test it. No one likes broken ROMs
But.... Why u need make source for zen 2 laser?
Cyanogen have source for this.... And some device already custom.... Only ze500kl don't have.... But i think can use source of msm8916-common !
Hello!
I'm hoping to get custom kernel & rom development up and running quickly for the G5 community, and have created a git repository which provides a kernel source base to start with.
What I've done is taken the v10a release sources and modified them to work with build directories and multiple variants. (should they be unlocked or receive the CodeFire treatment at any time)
Here's where to start: https://github.com/jcadduono/nethunter_kernel_g5/tree/stock-6.0
If you'd like a somewhat updated kernel, the stock-6.0.y branch will be patched from Linux 3.18.y branch at kernel.org, see:
https://github.com/jcadduono/nethunter_kernel_g5/tree/stock-6.0.y
Different from the absolute stock defconfigs, I've made the following changes:
Module signature verification disabled
Unnecessary debugging flags separated into debug_defconfig (use EXTRA_DEFCONFIG=debug_defconfig to enable them)
Flags that were previous set to module (=m) have been set to =y (built-in) in case incompatibilities are unable to load stock modules
Each known variant & target is listed in build.sh comments. The default variant when building with ./build.sh is h850 with debugging disabled.
When using the Makefile, VARIANT_DEFCONFIG=variant_xxx_defconfig adds the additional settings per variant to the target defconfig. (by default stock_defconfig)
build.sh is set up to automatically build a dtb.img after creating the kernel Image.gz based on whichever variant you've built for.
You can use ./menuconfig.sh to modify the stock defconfig, or you can copy the stock_defconfig to another name such as my_defconfig and use TARGET=my ./menuconfig or TARGET=my ./build.sh
It's easier to just set the default target in build.sh/menuconfig.sh - each have their configuration options near the top of the files.
Be sure to edit the config variables in build.sh and menuconfig.sh before using. The VERSION file gets appended to the kernel version shown in `uname` when using build.sh.
The toolchain must be pointed to the correct location before it can build. Be sure to have libncurses5-dev and colordiff packages installed for menuconfig.sh.
For a toolchain, I recommend using the GCC Linaro aarch64 5.3 2016.02 release. You can use basically any aarch64 toolchain though.
Download here: https://releases.linaro.org/compone...o-5.3-2016.02-x86_64_aarch64-linux-gnu.tar.xz
You can start by forking my repository on GitHub and giving it your own name if you like. Extra interesting commits are available in the other branches that you should be able to cherry-pick without issues should you be interested in them.
Looking to test your kernel Image.gz + dtb.img?
Look no further than my LazyFlasher repository!
See here: https://github.com/jcadduono/lazyflasher/tree/kernel-flasher
Simply do:
Code:
git clone -b kernel-flasher https://github.com/jcadduono/lazyflasher.git kernel-flasher
cd kernel-flasher
cp /path/to/Image.gz /path/to/dtb.img ./
make
(simply place your kernel Image.gz (optional) and dtb.img (optional) in the root of the repository and type make!)
And you'll have your own dynamic kernel flashing zip for custom recoveries!
The kernel-flasher repository is capable of great things. You can create scripts in patch.d to do anything you like.
Add files to the ramdisk-patch folder and create a script that copies them into the $ramdisk folder and they will be rebuilt into the ramdisk!
By default, no-verity-opt-encrypt is there as an example.
Using setprop in patch.d scripts allows you to set props in default.prop with ease.
Add functions to patch.d-env to make them globally usable across patch.d scripts.
See other branches for more examples, like how to add f2fs lines to the fstab, or patch for system mode SuperSU.
LazyFlasher is the installer used in the Kali NetHunter project. You can also find more examples in the kali-nethunter GitHub!
Good luck, and happy kernel developing!
Thanks so much for posting this.
Code:
./obligatoryn00bstatement
Sorry for not being too knowledgeable here (yet?) and if this sort of comment doesn't belong.
I am a Computer Science major who really wants to learn some skills to hopefully give back to the community.
Is this an area that I could be of use or should I perhaps spend more time going through material on the XDA-U site?
toefurkey said:
Thanks so much for posting this.
Code:
./obligatoryn00bstatement
Sorry for not being too knowledgeable here (yet?) and if this sort of comment doesn't belong.
I am a Computer Science major who really wants to learn some skills to hopefully give back to the community.
Is this an area that I could be of use or should I perhaps spend more time going through material on the XDA-U site?
Click to expand...
Click to collapse
I'm a little tired and somewhat intoxicated here at 3:45 AM so this is going to be a bit of rambling and so on...
While it's certainly a good idea to study up on what interests you before digging into it, sometimes it really can be easier just to dive in to your hobby.
I'm a high school drop out, never made it through college. Everything I've learned is by taking the great work done by the open source community and reading their code and applying it to other projects. That's the great thing about open source and nonrestrictive licenses. Everything is there for you to figure out, make changes, borrow code, run into problems, and the best part - search for solutions that others have already provided in their struggle to do exactly what you're doing.
Have an idea for a great feature? You can probably find it already implemented in another kernel somewhere.
Find the work someone else has done and modify it to fit your needs, but don't forget to give them credit for their work that you've used!
If you're going to start writing your own code, be certain to keep it tidy and variables/functions with meaningful names and comments so that not only others can understand and learn from it, but that you can return to the same code later on and understand it. Confusing code is how bugs tend to show up and become almost impossible to squash.
What I'm trying to get across here is don't be afraid to not be original. Don't be afraid to use others work to accomplish what you want, so long as they receive some attribution. The quickest way to learn how things work is by understanding what's already there and available to you.
You'll notice that there's projects all over XDA with special features ported from one device to another. Isn't it great having the all the best features people have added to other devices on one really nice device that you have?
PS I've never been on the XDA-U site before, so I can't give an opinion there.
I forgot what I was on about so I'll end this here lol.
?jcadduono you're on fire man thank you for everything you've been doing so far with such little resources.
Sent from my LG-H820 using XDA-Developers mobile app
jcadduono, thanks for the info and wonderful words of wisdom!
I totally agree on what you're saying and my goal is to try diving into this as a hobby. The hardest part for me isn't so much the coding part, but just figuring out a starting point to get grounded and build upon and I feel like what you've provided here is perhaps the starting point I need. Now it's just up to me to push myself in my free time.
Hi, i am new to kernel developing, but i did some roms myself before, so no total linux noob.
I cloned your 6.0.y and want to start from there, but im a little bit lost. Do i need to follow the steps @ github, or is your branch kinda pre setup ?
Toolchain path is also set to the one you gave a link too.
Pinu'u said:
Hi, i am new to kernel developing, but i did some roms myself before, so no total linux noob.
I cloned your 6.0.y and want to start from there, but im a little bit lost. Do i need to follow the steps @ github, or is your branch kinda pre setup ?
Toolchain path is also set to the one you gave a link too.
Click to expand...
Click to collapse
Hopefully once the toolchain path is set you should only need to run ./build.sh to actually build the kernel and dtb.
You may be missing some items for menuconfig.sh, which should just be solved by apt-get install colordiff libncurses5-dev
If building inside a ROM tree, it should be fairly simple for developers to adjust their ROM configs to add more to the kernel make command line, such as VARIANT_DEFCONFIG.
No matter what i do, kernel builds, but no dtb.img will be created. Any ideas where to look / what to test ?
I have stock-6.0.y, and did the h850 one.
Hi, is the stock-6.0.y branch removed?
I didnt find it. and need the right defconfig
greetz
mericon
I am trying to build a custom kernel for my redmi 2 running on Nexus Experience. I found there kernel source at their github page in nx_kernel_xiaomi_msm8916 . It's the only kernel referring to XIAOMI so I think it is the right one.
I am really new to kernel building. I read some tutorials on the web and tried building one for the stock miui rom but it didn't work out.
So before I start re-building the kernel for Nexus Experience I had some questions. I wanted to add the support for external wifi adapters based on RTL8188CUS. I found the option to enable it. My question is that , By just enabling that feature will my phone just start supporting the adapter out of the box or do I have to add some Modules to it.
And the last question, After I compile the kernel I get this zImage file. I put this file in the anyKernel.zip but I found that I also have to add the wlan.ko file and I couldn't find it....
I really need some help here.