I'm looking for a how to on compiling modules for a stock ROM. Is this even possible? My ultimate goal is to either get an external usb wifi adapter working, or compile a different kernel mod for our internal wifi card(one with monitor mode).
*chirp* *chirp* Darn those loud crickets... No seriously... ANYONE?
Take a look at this
http://forum.xda-developers.com/showthread.php?t=1974362
And modify it too what you need.
I don't think its possible to recompile our kernel driver for monitor mode.. you might wanna google "hashcode github maserati" and search through the github.
Sent from my XT894 using xda app-developers app
I've got USB OTG working, I'm trying to get it working with modules that aren't currently compiled. It's not just the wireless driver, but there are several modules that could be compiled, like a dvd drive.
I appreciate the help though
Wrong question?
Maybe I am asking the wrong question? I am trying to get a piece of hardware working with my phone. It works fine in several flavors of linux and has a driver source available(display link). How do I go about getting this to work?
Related
cud anyone share with me how to get sync fixed and wifi fixed on eclair??
Im compiling an elair sapphire rom, ive got it booting, and it runs ok. just no wifi or sync.
please help!
bump!
cmon guys... i need help with this, im a noob to developing....
think i dun ok gettin it to compile and boot!
please help me out... and share ur fixes... it'll only mean more choice of roms!
I dont know a lot but I imagine its two seperate things.
the WiFi I imagine is a driver issue, and the sync is because you are missing the google apps.
I am guessing, but after compiling my own 1.6 rom and overcoming some of the strange things I found in doing that its a somewhat educated guess.
you re right! it is two seperate issues..
i have compiled the rom with the google apps from the milestone included. however i am experiencing the same issues with the sync that other devs did when they started working on eclair.
i am wondering how the other devs fixed the issues as this is the only thing preventing me releasing the rom
can anyone shed any light on these issues for me??? will credit u appropriatley on release.
bump again! sorry
can a dev help me out then??
thought this community was about sharing knowledge??
i think this would be a question that actually does belong in development. try there.
this thread already got moved from the development section!
just need pointin in the right direction, will figure the rest out myself!
bump, bump, bump!
can no one help me with this??!!
im guna try and pull sum stuff from the nexus one dump.. see if that works...
feels like im bangin my head against a brick wall tho..
ive downloaded loadsa roms off this site... and now im tryin to put something back, no one will help me out!
cmon devs, pm me, help me out with a fix for sync and wifi.
thanks!
ok, first of all, you're making a sapphire build but is it for the sapphire or the magic? They both use different kernels. If you're building for the sapphire (32b) then the stock kernel and wlan modules work fine. You might have a bluetooth problem, so, if bluetooth won't start, in your /vendor/htc/sapphire-open look for init.sapphire.rc and at line 59 change where it says "texas" to "texasalt". If you don't have bluetooth problems then don't change it.
Did you change your kernel by any chance? This could happen if you're using somebody else's boot.img or if you knowingly used another kernel and packed it to the default boot.img, or further, if you built your own kernel.
If you used somebody else's kernel, then you need to replace the wlan.ko module, again, in /vendor/htc/sapphire-open with the wlan.ko module from the kernel you took.
If, instead, you built your own kernel, then you need to rebuild the wlan.ko module doing the following (taken mostly in part from Johan de Koning's blog), ~/mydroid reffers to your working android path (mine's ~/Desktop/android/master):
Code:
export PATH=$PATH:~/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.X.X/bin
(replace X.X with the toolchain version numbers you used to build your kernel)
Code:
cd ~/mydroid/system/wlan/ti/sta_dk_4_0_4_32
export KERNEL_DIR=~/mydroid/kernel/
make
and then copy the just-created module to sapphire-open
Code:
cp wlan.ko ~/mydroid/vendor/htc/sapphire-open
And about the sync problem? I'm wondering myself too. My last AOSP master build had gapps on it, but sync was still broken (you had to disable it), and so is still everybody else's based on AOSP, except for JAC/Cyanogen's.
The only other eclair build out there with working sync is Manup's, but his is based on the 2.0.1 sdk system image and he didn't fix sync, it just works on 2.0.1, so whatever was preventing sync from working on the 2.0 aosp build was fixed on 2.0.1, he just tossed the gapps in there and they worked.
I'm interested too in learning how Cyanogen worked out the sync problem on AOSP, he tweeted something like "I think I know how to solve the sync problem" a few days ago, but he didn't elaborate. We have to find someway to lure him to this thread and let us know how to fix it on our repos rather than copy his own.
If you do find out about fixing the sync problem (programatically), let me know please, I'm also interested.
Actually, looking through cyanongen's github, I think I found the answer. I'll make a quick eclair build and test.
http://github.com/cyanogen/android_...mmit/eea38a1ad7a61b4426612222a654da610e02855a
---edit---
nope, not it.
Here's the sync fix:
http://github.com/cyanogen/android_frameworks_base/commit/9fb8bb8a9542dfcaf9f546d9cee545517a03bed1
I think this would be pretty easy to patch into a non-AOSP build using smali/baksmali too since it's so simple.
Not sure what kind of wifi problem you have.. I've had no problems with it.
thanks 10chars
---edit---
nevermind
thanks guys.. i will start my own build as soon as i get home!
Also.. You should be able to build using my sources and get a system.img that actually works 100% and can be fastbooted.
Guys,
Seems like there are lots of threads popping up with new 'packages'. I thought we should create a thread solely for the discussion of kernel hacks/patches so that we can separate the two:
For those of you who dont know, http://gitorious.org/linux-on-qualcomm-s-msm/linux-msm-xdadev is the repo were are working on.
Just to clarify, this topic is ONLY for discussion regarding Kernel patches. Thanks to vdelf's headset patch it seems sensible to focus on:
1. Backlight always on problem FIXED 01/05/10 (vdelf)
2. Battery Issue FIXED 11/05/10 (drlucky)
3. Camera
4. USB
5. GPS
Makes sense. Lets add USB to the list. While charging works, data transfer does not. Also USB might allow us to debug kernel/android on the x1 and that is what dev's always dream of
:suggestion: why not add the latest kernel as download in the 1st post if there is progress. So everyone know where to download the latest updates u ppl do
dexteral said:
:suggestion: why not add the latest kernel as download in the 1st post if there is progress. So everyone know where to download the latest updates u ppl do
Click to expand...
Click to collapse
It will be great to do this, and stick it
@dexteral,
Anyone can checkout the kernel from the above repo I posted. To do what you require we would need to upload the Kernel everytime someone adds a patch...
vdelf said:
Makes sense. Lets add USB to the list. While charging works, data transfer does not. Also USB might allow us to debug kernel/android on the x1 and that is what dev's always dream of
Click to expand...
Click to collapse
Is data transfer even possible in haret? I mean how would system unmount sdcard if it's running from sdcard itself?
not fast data but normal will work
love it
vietdoan20062006
Hi, Lets add fm-radio to the list
Great idea ... otherwise we are creating such a mess with lots of different kernel versions in different threads.
If anyone is interested in compiling the kernel as well as the wifi modules, I have setup a VMWare debian appliance containing all necessary tools and scripts to compile everything. Since this is a few hundes MB, I haven't got a place to upload ... need to check this first. If you are interested, let me know.
@drlucky
Have you had a chance to look at the backlight issue? I am almost out of ideas
Can you post your modifications on the microp-module and what you found out until now?
_Sensible said:
Guys,
Seems like there are lots of threads popping up with new 'packages'. I thought we should create a thread solely for the discussion of kernel hacks/patches so that we can separate the two:
For those of you who dont know, http://gitorious.org/linux-on-qualcomm-s-msm/linux-msm-xdadev is the repo were are working on.
Just to clarify, this topic is ONLY for discussion regarding Kernel patches. Thanks to vdelf's headset patch it seems sensible to focus on:
1. Backlight always on problem
2. Battery Issue
3. Camera
4. USB
5. GPS
Click to expand...
Click to collapse
hey could you post the steps involved for compiling the kernel i am able to comile the kernel but it is not running
Wich toolchain do you use? arm-2008q1 or arm-2009q3?
X1iser said:
Wich toolchain do you use? arm-2008q1 or arm-2009q3?
Click to expand...
Click to collapse
arm-2010q1
could u write all the commands used by you
the way i have written
Personally I'll start to see how to compile the kernel. Can you share the link to download arm-2010q1?
Have you read this post ?
X1iser said:
Personally I'll start to see how to compile the kernel. Can you share the link to download arm-2010q1?
Have you read this post ?
Click to expand...
Click to collapse
http://www.codesourcery.com/downloa...-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
but may be it is not the right one it has got 202 in it insted of 67
ya i read that post only
i was able to compile the kernel but it is giving some errors
_Sensible said:
@drlucky
Have you had a chance to look at the backlight issue? I am almost out of ideas
Click to expand...
Click to collapse
Sorry, haven't had the time. Could you push your changes to the git repo, I will try to have a look at it this week ...
okay i tried to make the kernel bt following the guide above by fatsal...
but i got stuck at
make htckovsky_defconfig ARCH=arm
htckovsky_defconfig doesn't exist (in the new repo anyway, i believe)
any help? which defconfig to use? :S
drlucky said:
Sorry, haven't had the time. Could you push your changes to the git repo, I will try to have a look at it this week ...
Click to expand...
Click to collapse
Just played with the klt-driver a bit. I always get version 0x0000, which on a hero means "bootloader mode". I have tried to migrate the hero code, but with no luck. It seems that the microp-klt needs a "reset", which shoudl be done by using a magical GPIO (on hero: 76), but this doesn't currently work at all. Kernel boots up, but still gets no valuable version number.
Hi, first of all I hope this is the right place for this if not please close/move and tell me the right place to ask.
I am planning to improve the CM-FM app for our N1s, it works but there is a lot of room for improvement (named stations, autosearch, overriding national limits...).
The problem is that I am working on a Windows machine and the FM app needs the modified CM framework classes to compile, it seems there is no option to compile the full CM distribution under Windows.
But it shouldn't be too difficult given the CM framework compiled to use it with android-SDK and eclipse to build just the app.
So I ask here if someone can provide me the compiled classes.
It would be great to have them published with the nightlies, but as I don't think there would be a lot of changes in this part probably I can work with an outdated version for some time.
Why don't you use a virtual machine with Linux for this?
Of course that's a last resource but surely there are people out there that can provide this classes from their last compilations without problems and maybe this can help other developers also.
You'd probably want to be able to compile CM anyway so just installing Ubuntu 64bit in Virtualbox will work fine and is free. Make sure to enable Hardware Virtualization in your BIOS if your CPU supports it.
I do want to compile CM just the radio app, otherwise I would have installed a linux.
Sent from my Nexus One using XDA App
frisco82 said:
I do want to compile CM just the radio app, otherwise I would have installed a linux.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Why so stubborn? It literally takes less than a few hours to install, download sources, and compile your classes. Instead, you'd rather post here, and sit in waiting for who-knows-how-long to get an answer?
Not flaming, just trying to follow your thought process...
I found out the hard way that apparently the WPA2 implementation in Android is faulty. This means it can not connect to WPA2 secured APs which enforce strict specs:
https://forum.openwrt.org/viewtopic.php?id=25870
Would it be possible to fix that in CM ?
Cheers,
Karl
Android is using wpa_supplicant, it doesn't implement the protocols on its own.
So you are saying the bug is actually in wpa_supplicant ?
Should i try to make them aware of the problem ?
First time I hear that, although I have at home WPA2 personal and my Legend connects with it normally.
I have a WPA2 personal network both at home and at my dorm, and my HeroC has been able to connect to them fine no matter what ROM I've used (stock, Sense 2.1 custom ROMS, and CM6/7)
According to the openwrt link i posted above it seems to be a problem with the drivers on openwrt enforcing strict RFC compliance and the wpa_supplicant not sticking to it. So it might just be a problem for a specific setup.
However, the question now is if that should be fixed in android or if openwrt should relax its rules.
I just try to find out which community would be the right one to address...
Hey AliBa !
People at openwrt think its a problem of the TI wireless drivers, and that it could be fixed in CM:
This is not a problem with OpenWRT, hostapd, or wpa_supplicant (the latter two are the same project, and mostly written by one person). This is a bug with Android wifi drivers that do not properly follow spec.
The TI Wilink driver I referred to is particularly at fault, and disabling WMM on the router is a band-aid to the problem - not a fix or a real solution. wpa_supplicant is not even involved in this process since the Wilink driver generates the RSN on its own.
The people who need to address this are TI, not openwrt or CM or someone else (or CM can put in a patch to fix the TI Wilink driver, which is probably a good idea anyway).
Click to expand...
Click to collapse
https://forum.openwrt.org/viewtopic.php?id=25870
There are two RSN settings in tiwlan.ini:
Code:
RSNPreAuthentication
RSNExternalMode
...try setting latter to external.
Hey BlaY0 !
This .ini file is in the build tree, not on the phone, right ? Or can i set that on my phone ?
If its a part of the build files, do you think I should file a bug at CM ?
It's on the phone... /system/etc/wifi/tiwlan.ini. It's configuration file for driver itself.
Might be a noob-problem, but i am unable to write to the file.
I tried terminal emulator, su, vi /etc/wifi/tiwlan.ini, but its read-only.
Any other way i can try this ?
Use recovery to do that or you can use system overlay.
Sent from my HTC Legend
Tried switching the RSN..-config to external as mentioned, but it's not working here.
Hmm, anything else we can do ?
AliBa, are you sure you could not fix this ?
People at openwrt think it could be patched in CM:
https://forum.openwrt.org/viewtopic.php?id=25870
Cheers,
Karl
Yes, I'm sure I can't fix that.
If it's not caused by wpa_supplicant then there's nothing we can do. Sources for neither firmware nor kernel module are open sourced so there's no way to patch them.
Hey !
ali ba said:
Yes, I'm sure I can't fix that.
If it's not caused by wpa_supplicant then there's nothing we can do. Sources for neither firmware nor kernel module are open sourced so there's no way to patch them.
Click to expand...
Click to collapse
Too bad. Didnt know that some (?) kernel modules are closed source in android. What a shame !
Anyway, thanks for trying to help !
karl_k said:
Hey !
Too bad. Didnt know that some (?) kernel modules are closed source in android. What a shame !
Anyway, thanks for trying to help !
Click to expand...
Click to collapse
It's a royal PITA, and we all dislike HTC, Motorola, Samsung etc. for doing it. That said, the CM team do an unbelievable job of dealing with it as well as they do
karl_k said:
Too bad. Didnt know that some (?) kernel modules are closed source in android. What a shame !
Click to expand...
Click to collapse
Every Google device was as close to open source as possible with all kernel sources being released. It's companies like HTC that corrupt that whenever they can. For example they put code into the framework that would normally go into the kernel just to not having to release it.
Moreover, the sources for wl12xx were open sourced by TI using a BSD-like license. The even sadder problem is that HTC modified them and then deliberately removed those modifications (headers) from the kernel sources they released.
So its a dead end, and really nothing can be done about it?
Can't believe that!
So I still love my tf710t but I often need my other Laptop because of missing drivers.
I often built kernel modules for my Computer but I can't get the cross compiler setup working to build the Kernel Modules for my Transformer Pad.
I am using this Rom (BlissPop 4):
https://forum.xda-developers.com/tr...om-unoffical-blisspop-3-5-2015-06-14-t3134963
And I try to build a Kernel Module for the Huion 420 Driver from here:
https://www.dropbox.com/s/mqq3011ym6r5ek3/4x2_5x4_android-driver.zip?dl=0
Can someone help me with a step by step how to. I already googled for hours and followed some tutorials but I still can't get it working.
Download https://github.com/Christopher83/arm-cortex-linux-gnueabi-linaro_4.9?files=1 and like https://forum.xda-developers.com/showthread.php?p=36677987#post36677987