Why no custom roms?

April 22, 2010

I ask this over at XDA and had no reply so im Very Sorry! if this is a stupid question, but I just wanted to know why is it that we have a choice of custom roms for a range of handsets and non for the U8220/pulse, is it because its regarded as the budget bottom end Android phone and no dev's want to touch it? or is it a legal situation?, again sorry if you think this is a dumb question, and also I think its sad that we dont have a 2.1 firmware for the pulse as yet and cant take full advantage of the marketplace.

April 22, 2010

I ask this over at XDA and had no reply so im Very Sorry! if this is a stupid question, but I just wanted to know why is it that we have a choice of custom roms for a range of handsets and non for the U8220/pulse, is it because its regarded as the budget bottom end Android phone and no dev's want to touch it? or is it a legal situation?, again sorry if you think this is a dumb question, and also I think its sad that we dont have a 2.1 firmware for the pulse as yet and cant take full advantage of the marketplace.

There are custom ROMS, just not 2.1 yet. Googling might be the best option, you may find a forum for U8220/pulse.

This may be a handset that the manufactures have chosen to drop and ignore. ;)

April 22, 2010

Well, there is a custom rom, if you look at the top of the forum there's sticky with it in. ;)

The one you're running even ;) as to why there are no more, I'm not sure. Probably because it's not the most popular phone around, certainly not hyped.

Edited April 22, 2010 by giryan

April 22, 2010

There are custom ROMS, just not 2.1 yet. Googling might be the best option, you may find a forum for U8220/pulse.
This may be a handset that the manufactures have chosen to drop and ignore. ;)

there are some modaco custom roms but the last one (1.8, still requires ad-free membership) is from last year so part of what he's saying is right.

it would be great if at least only one dev who knows how to patch android kernels would jump into the forum and do some good things with the phone, like swap support and wifi tethering. i don't ask for other versions of android because it's a very different story, but some improvements with the recent one would be great and appreciated.

Edited April 22, 2010 by helikopter

April 22, 2010

There are custom ROMS, just not 2.1 yet. Googling might be the best option, you may find a forum for U8220/pulse.
This may be a handset that the manufactures have chosen to drop and ignore. ;)

I hope thats not the case because I think the pulse is quite a nice phone, I also have a G1 which iv flashed so many roms to it and at present using a 2.1 firmware rom and it's running quite good, but my pulse runs smoother when scrolling around on home screens and drawer which is obvious I guess since the pulse is still on 1.5.

Anyway thanks for your reply I will do some more GOOGLING!!. ;)

April 22, 2010

there are some modaco custom roms but the last one (1.8, still requires ad-free membership) is from last year so part of what he's saying is right.

it would be great if at least only one dev who knows how to patch android kernels would jump into the forum and do some good things with the phone, like swap support and wifi tethering. i don't ask for other versions of android because it's a very different story, but some improvements with the recent one would be great and appreciated.

Quite right, I guess what im getting at is its easy to find experimental / customs roms for other hand sets even hand sets thats just come out, but for the pulse iv only managed to find whats here at MDC, If only I knew how to port other roms to the pulse ;) but im not a DEV ;)

April 22, 2010

Quite right, I guess what im getting at is its easy to find experimental / customs roms for other hand sets even hand sets thats just come out, but for the pulse iv only managed to find whats here at MDC, If only I knew how to port other roms to the pulse ;) but im not a DEV ;)

I'm working on the Pulse.

Even most of my free - time, beside of other projects I need to make for school.

But I'm not 100% into this matter, so it will take time before I'm able to add netfilter or swap to the kernel.

My main problem at the moment is that networking isn't working in my custom kernels, and I don't know why.

I'm currently working on mutlitouch (well not until I get a reply from Huawei) and an overclocked kernel.

I will have a look at netfilter and swap later on, but please be patient ;)

By the way, its not impossible to become a "dev" (I don't want to name myself as a dev - not yet).

What you have to know is mostly the programming languages C and C++ (actually more C than C++) if you want to modify the kernel, Java and C++ (partly) if you want to write applications/ modify Android.

And it's also advantageous if you have programmed µC's before.

I didn't have any clue about how a kernel works, or even what it does in detail (and I don't entirely know it yet) until I got the Pulse (~ 5 months ago).

I'm learning-by-doing, that's all.

If it works, fine, if not I at least learned something.

Greetings,

BigBear

Edited April 22, 2010 by BigBearMDC

April 22, 2010

BigBearMDC, care to share how you got into the android hacking? Did you just dig into the code or are there any books/articles/etc with detailed android internals?

I'd love to throw my knowledge and very little free time into the problem, but I'm just too lazy to start reading kernel code again :huh: I do have some experience with the linux kernel (and even the windows research kernel :P) and microcontrolers, and I'd love to learn how the android kernel is customized since I'm doing a side project in android. But like I said, I would definitely prefer a book than to have to make sense with a pen and paper of the system.

Edited April 22, 2010 by brickedMyHuaweiU8230

April 23, 2010

I'm working on the Pulse.
Even most of my free - time, beside of other projects I need to make for school.
But I'm not 100% into this matter, so it will take time before I'm able to add netfilter or swap to the kernel.
My main problem at the moment is that networking isn't working in my custom kernels, and I don't know why.
I'm currently working on mutlitouch (well not until I get a reply from Huawei) and an overclocked kernel.
I will have a look at netfilter and swap later on, but please be patient :P

By the way, its not impossible to become a "dev" (I don't want to name myself as a dev - not yet).
What you have to know is mostly the programming languages C and C++ (actually more C than C++) if you want to modify the kernel, Java and C++ (partly) if you want to write applications/ modify Android.
And it's also advantageous if you have programmed µC's before.

I didn't have any clue about how a kernel works, or even what it does in detail (and I don't entirely know it yet) until I got the Pulse (~ 5 months ago).
I'm learning-by-doing, that's all.
If it works, fine, if not I at least learned something.

Greetings,
BigBear

BigBearMDC, care to share how you got into the android hacking? Did you just dig into the code or are there any books/articles/etc with detailed android internals?

I'd love to throw my knowledge and very little free time into the problem, but I'm just too lazy to start reading kernel code again :blink: I do have some experience with the linux kernel (and even the windows research kernel :o) and microcontrolers, and I'd love to learn how the android kernel is customized since I'm doing a side project in android. But like I said, I would definitely prefer a book than to have to make sense with a pen and paper of the system.

I know very little about kernel codeing and modifying roms but very able and willing to learn, at best all I know is how to push / pull /copy / paste and edit a few files, I have a very good understanding though on the hardware side of things, microelectronics and components not sure how that would help though lol :huh: BigBear if you could spear a little more of your time and maybe pm me with some tips on how to get started were to start first so to speak id be most Greatful, I mainly want to know whats needed first in order to port other roms to the pulse, sorry if this is all noooob guys.

April 23, 2010

A little guide, for everyone ho wants to start kernel hacking.

Requirements

A computer running a Linux Distribution (I prefer Ubuntu as I'm used to it)
A list of software packeges - I'll explain you what packages you'll need later
An Android Phone, or at least the Android SDK with the Phone emulator

Enough time and the will to learn

Step 1: setting up the environment

First, you'll have to install Linux. You can try it in a VirtualBox if you want, but it's not only me that faced weird errors within the VirtualBox.
So my recommendation is: Install it on your hard drive. With wubi you can install Ubuntu directly onto your NTFS partition
After you set up your system with Linux, install the following packages:

git-core
gnupg
sun-java5-jdk
flex
bison
gperf
libsdl-dev
libwxgtk2.6-dev
zip
curl
libncurses5-dev
zlib1g-dev

Do this by typing

sudo apt-get install git-core gnupg sun-java5-jdk flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev

into the shell. If apt complains about sun-java5-jdk add the following to your source list (/etc/apt/sources.list):

deb http://us.archive.ubuntu.com/ubuntu/ jaunty multiverse

deb http://us.archive.ubuntu.com/ubuntu/ jaunty-updates multiverse[/code]




Another useful application is Meld Diff.





[size=5][color=#FF0000]Step 2: getting the source[/color][/size]



Lets begin with the easier part - the kernel source.

Download it from here.

(Maybe you'll have to reload the side a few times - Huawei's servers aren't really reliable)

Extract it anywhere you want.

In my examples, I extracted the kernel source to "~/kernel-source".



The next thing is to download the Android source.

That's a bit more complicated.

First, make a directory, in my case "~/android-1.6-source".

Open up a shell and cd into this directory:

[code]cd ~/android-1.6-source

Then write the following two lines:

repo init -u git://android.git.kernel.org/platform/manifest.git -b android-1.6_r2

repo sync[/code]

Now grab a cup of tee (or maybe coffee, if you prefer that :D ), as this might take up to a few hours (depending on your internet connection. It took me ~40 minutes @ 750kB/s).

Make sure you have enough free space!

You'll need up to 7 gigs!

[size=5][color=#FF0000]Step 3: Where to start from now?[/color][/size]

This might not fit for everyone, I'll just explain you how I began to modify the kernel.

I wanted to know if its possible to port the Flash Player from the HTC Hero to the Pulse.

At this moment I never thought of touching something like a kernel source.

I also didn't even know how to compile it...

But then things got more and more difficult.

Just copying the files from the Hero ROM to the Pulse ROM wasn't enough - the flash player crashed all the time.

So I thought, "hmm if I can't port the flash Player alone, why not port the whole Hero ROM?".

And I really thought that this wouldn't be too difficult, but I was terribly wrong B)

So I grabbed the Huawei kernel source (by the way, there are two versions of the kernel source, that one from T-Mobile doesn't work. Always use the QMR kernel source) and the Hero's kernel source and started to copy the drivers.

I think you can imagine how much work it is to start the compiler, wait for errors, patch the errors and start the whole thing from the beginning...

Anyway I began to realize that this was a bit to much for the moment, and then I saw the "Mulltitouch possible in theory?" thread, and had a look at it.

And I thought "hey, that seems to be easier than porting a whole ROM. Let's have a look at this."

And what happened, I tried and tried and tried and ... wait ... holy s*** - it works!

(Well it works in theory. I don't get the coordinates of the second touchpoint, but the driver would deliver them, if there were any :huh: ).

That was my first real felling of success.

But I didn't figure this out on my own, I used the code developed by Luke Hutchinson, who ported MT to the G1.

I never sat down in front of my PC and read the kernel source, ad I'm not planning to do this.

What I want to say is if you have an aim, it's by far simpler to get into this matter.

Just trying to understand the kernel is too much by far, at the beginning.

Do it step by step.

I'm currently at I2C and the Input driver section, I haven't come further until know.

Believe me, that's enough for now :D

So if you ask me where to start?

I can't give you the answer.

Also I haven't seen a book or an article about android hacking/developing.

Most resources in the net aren't really beginner friendly...

You could try, as an example, to just add a few lines into a function you like and print something like

[code]Hello world

everytime this function gets called. To find out how to achieve this is your task, that is what you want to learn :P (in this case its only one line of code B) ) I can only tell you what to do after you modified the kernel -> Step 4 Step 4: Compiling the source First you'll have to compile the kernel. You do this by specifying the platform you want to compile the kernel for - in our case ARM - and the toolchain you want to use - its the arm.eabi-4.4.0 toolchain which we downloaded with the Android 1.6 source. One further thing we need is the kernel config. This file basically tells the kernel which functions should be implemented and compiled. Its just used to configure the kernel. You can download this file by typing:

wget http://sites.google.com/site/tdhutt/pulse_config.txt -O .config

Of course you have to cd into your kernel directory first. Now we can start to compile the kernel. If you compiled the kernel earlier, you should clean the source tree first. Thus all compiled objects get deleted and you end up with the clean source. Do this by typing

make clean

If you want to change your kernel config you can do it by typing

make menuconfig

If you completed the steps above you are ready to compile the kernel:

make ARCH=arm CROSS_COMPILE=~/android-1.6-source/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-

This takes ~30 minutes, depending on your machine. You'll then end up with a zImage. That's the kernel. Once you have the ramdisk you can combine them and flash them to your device. Now lets go on with compiling Android. cd into the android source directory (~/android-1.6-source) Unfortunately I don't exactly know what the different commands are good for, so I just paste them:

. build/envsetup.sh

lunch generic-eng

make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi KERNEL_DIR=$ROMDIR/huawei-1.5-kernel-source/kernel[/code]


This will take ~10 mins up to ~3 hours.



You will end up with a system.img, userdata.img and a ramdisk.





[size=5][color=#FF0000]Step 5: Putting all together and flashing it to the device[/color][/size]



You should now have the following files:[list]

[*]zImage

[*]ramdisk.img

[*]system.img

[*]userdata.img




With the zImage and the ramdisk we'll create the boot.img, using the tool mkbootimg, which gets compiled with the android source (I assume you put the two files in the same directory):

[code]mkbootimg --cmdline "mem=128M console=ttyMSM2,115200n8 no_console_suspend=0" --kernel ./zImage --ramdisk ./ramdisk.img -o boot.img

Now we have a boot.img, a system.img and a userdata.img, and we're ready to flash them onto our device. Therefore we'll need fastboot linux. Download it here (it's part of the amon-ra recovery). Open up a shell, put your device into bootloader mode (by pressing Power + Red End Key + Vol down while the device is powered off) and connect it to the PC. Now cd into your amon-ra recovery folder and type the following:

sudo ./fastboot-linux flash system ./system.img [hit return]

	sending SYSTEM .... (xxxxx)

	writing SYSTEM ....

sudo ./fastboot-linux flash userdata ./userdata.img [hit return]

	sending USERDATA .... (xxxxx)

	writing USERDATA ....

sudo ./fastboot-linux flash boot ./boot.img [hit return]

	sending BOOT .... (xxxxx)

	writing BOOT ....

sudo ./fastboot-linux reboot [hit return][/code]


That's it.

Now you've compiled and flashed your own Android OS.

Congratulations :blink:


I hope that this helps you guys :o


Greetings,

BigBear

April 23, 2010

A little guide, for everyone ho wants to start kernel hacking.
Requirements
A computer running a Linux Distribution (I prefer Ubuntu as I'm used to it)
A list of software packeges - I'll explain you what packages you'll need later
An Android Phone, or at least the Android SDK with the Phone emulator
Enough time and the will to learn

First, you'll have to install Linux. You can try it in a VirtualBox if you want, but it's not only me that faced weird errors within the VirtualBox.
So my recommendation is: Install it on your hard drive. With wubi you can install Ubuntu directly onto your NTFS partition
After you set up your system with Linux, install the following packages:
git-core
gnupg
sun-java5-jdk
flex
bison
gperf
libsdl-dev
libwxgtk2.6-dev
zip
curl
libncurses5-dev
zlib1g-dev
Do this by typing
sudo apt-get install git-core gnupg sun-java5-jdk flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev
into the shell. If apt complains about sun-java5-jdk add the following to your source list (/etc/apt/sources.list):
deb http://us.archive.ubuntu.com/ubuntu/ jaunty multiverse

deb http://us.archive.ubuntu.com/ubuntu/ jaunty-updates multiverse
Another useful application is Meld Diff. Step 2: getting the source Lets begin with the easier part - the kernel source. Download it from here. (Maybe you'll have to reload the side a few times - Huawei's servers aren't really reliable) Extract it anywhere you want. In my examples, I extracted the kernel source to "~/kernel-source". The next thing is to download the Android source. That's a bit more complicated. First, make a directory, in my case "~/android-1.6-source". Open up a shell and cd into this directory:
cd ~/android-1.6-source
Then write the following two lines:
repo init -u git://android.git.kernel.org/platform/manifest.git -b android-1.6_r2

repo sync
Now grab a cup of tee (or maybe coffee, if you prefer that :D ), as this might take up to a few hours (depending on your internet connection. It took me ~40 minutes @ 750kB/s). Make sure you have enough free space! You'll need up to 7 gigs! Step 3: Where to start from now? This might not fit for everyone, I'll just explain you how I began to modify the kernel. I wanted to know if its possible to port the Flash Player from the HTC Hero to the Pulse. At this moment I never thought of touching something like a kernel source. I also didn't even know how to compile it... But then things got more and more difficult. Just copying the files from the Hero ROM to the Pulse ROM wasn't enough - the flash player crashed all the time. So I thought, "hmm if I can't port the flash Player alone, why not port the whole Hero ROM?". And I really thought that this wouldn't be too difficult, but I was terribly wrong B) So I grabbed the Huawei kernel source (by the way, there are two versions of the kernel source, that one from T-Mobile doesn't work. Always use the QMR kernel source) and the Hero's kernel source and started to copy the drivers. I think you can imagine how much work it is to start the compiler, wait for errors, patch the errors and start the whole thing from the beginning... Anyway I began to realize that this was a bit to much for the moment, and then I saw the "Mulltitouch possible in theory?" thread, and had a look at it. And I thought "hey, that seems to be easier than porting a whole ROM. Let's have a look at this." And what happened, I tried and tried and tried and ... wait ... holy s*** - it works! (Well it works in theory. I don't get the coordinates of the second touchpoint, but the driver would deliver them, if there were any :huh: ). That was my first real felling of success. But I didn't figure this out on my own, I used the code developed by Luke Hutchinson, who ported MT to the G1. I never sat down in front of my PC and read the kernel source, ad I'm not planning to do this. What I want to say is if you have an aim, it's by far simpler to get into this matter. Just trying to understand the kernel is too much by far, at the beginning. Do it step by step. I'm currently at I2C and the Input driver section, I haven't come further until know. Believe me, that's enough for now :D So if you ask me where to start? I can't give you the answer. Also I haven't seen a book or an article about android hacking/developing. Most resources in the net aren't really beginner friendly... You could try, as an example, to just add a few lines into a function you like and print something like
Hello world
everytime this function gets called. To find out how to achieve this is your task, that is what you want to learn :P (in this case its only one line of code B) ) I can only tell you what to do after you modified the kernel -> Step 4 Step 4: Compiling the source First you'll have to compile the kernel. You do this by specifying the platform you want to compile the kernel for - in our case ARM - and the toolchain you want to use - its the arm.eabi-4.4.0 toolchain which we downloaded with the Android 1.6 source. One further thing we need is the kernel config. This file basically tells the kernel which functions should be implemented and compiled. Its just used to configure the kernel. You can download this file by typing:
wget http://sites.google.com/site/tdhutt/pulse_config.txt -O .config
Of course you have to cd into your kernel directory first. Now we can start to compile the kernel. If you compiled the kernel earlier, you should clean the source tree first. Thus all compiled objects get deleted and you end up with the clean source. Do this by typing
make clean
If you want to change your kernel config you can do it by typing
make menuconfig
If you completed the steps above you are ready to compile the kernel:
make ARCH=arm CROSS_COMPILE=~/android-1.6-source/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
This takes ~30 minutes, depending on your machine. You'll then end up with a zImage. That's the kernel. Once you have the ramdisk you can combine them and flash them to your device. Now lets go on with compiling Android. cd into the android source directory (~/android-1.6-source) Unfortunately I don't exactly know what the different commands are good for, so I just paste them:
. build/envsetup.sh

lunch generic-eng

make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi KERNEL_DIR=$ROMDIR/huawei-1.5-kernel-source/kernel
This will take ~10 mins up to ~3 hours. You will end up with a system.img, userdata.img and a ramdisk. Step 5: Putting all together and flashing it to the device You should now have the following files:
[*]zImage [*]ramdisk.img [*]system.img [*]userdata.img With the zImage and the ramdisk we'll create the boot.img, using the tool mkbootimg, which gets compiled with the android source (I assume you put the two files in the same directory):
mkbootimg --cmdline "mem=128M console=ttyMSM2,115200n8 no_console_suspend=0" --kernel ./zImage --ramdisk ./ramdisk.img -o boot.img
Now we have a boot.img, a system.img and a userdata.img, and we're ready to flash them onto our device. Therefore we'll need fastboot linux. Download it here (it's part of the amon-ra recovery). Open up a shell, put your device into bootloader mode (by pressing Power + Red End Key + Vol down while the device is powered off) and connect it to the PC. Now cd into your amon-ra recovery folder and type the following:
sudo ./fastboot-linux flash system ./system.img [hit return]

	sending SYSTEM .... (xxxxx)

	writing SYSTEM ....

sudo ./fastboot-linux flash userdata ./userdata.img [hit return]

	sending USERDATA .... (xxxxx)

	writing USERDATA ....

sudo ./fastboot-linux flash boot ./boot.img [hit return]

	sending BOOT .... (xxxxx)

	writing BOOT ....

sudo ./fastboot-linux reboot [hit return]
That's it.
Now you've compiled and flashed your own Android OS.
Congratulations :blink:

I hope that this helps you guys :o

Greetings,
BigBear

Greatest tutorial ever ....
THANKS BigBear,
and i think from what i read that you need a new kernel source...

April 23, 2010

@BigBear

Thanks alot bro!! :huh: I feel like I cant swim and im about to dive in the deep end lol.

April 23, 2010

I will have a look at netfilter and swap later on, but please be patient :huh:

Netfilter is easy to get working (I have a config around here somewhere if you want it), the problem is that the ar6000 driver is incompatible. Netfilter works fine, and will work with bluetooth/pand for wireless tethering but as soon as the ar6000 module is loaded the phone will crash. It will crash if the netfilter support is included in the kernel, even if the nf/iptables modules are not loaded.

Unfortunitely we don't have source for the ar6000 module and the only alternative drivers are some code provided by Atheros to the openmoko project and the code that is actually used in the openmoko project (a large part of the Atheros code has been replaced). I have ported the openmoko driver into the Huawei source and it compiles and loads fine, but so far doesn't work.

One of the reasons I started working on a 2.6.29 kernel was the hope that the openmoko ar6000 driver would be easier to get working as the current openmoko kernel is based on 2.6.29.

I have found a couple of other devices that use linux and the ar6000, but can't find any source for them (a few NEC devices sold only in Japan).

Swap is also on my list of things to look at. I expect it won't be too hard since it already works, we only need to fix the incompatibility with a2sd.

Edited April 23, 2010 by Tom G

April 24, 2010

Netfilter is easy to get working (I have a config around here somewhere if you want it), the problem is that the ar6000 driver is incompatible. Netfilter works fine, and will work with bluetooth/pand for wireless tethering but as soon as the ar6000 module is loaded the phone will crash. It will crash if the netfilter support is included in the kernel, even if the nf/iptables modules are not loaded.
Unfortunitely we don't have source for the ar6000 module and the only alternative drivers are some code provided by Atheros to the openmoko project and the code that is actually used in the openmoko project (a large part of the Atheros code has been replaced). I have ported the openmoko driver into the Huawei source and it compiles and loads fine, but so far doesn't work.

One of the reasons I started working on a 2.6.29 kernel was the hope that the openmoko ar6000 driver would be easier to get working as the current openmoko kernel is based on 2.6.29.

I have found a couple of other devices that use linux and the ar6000, but can't find any source for them (a few NEC devices sold only in Japan).
Swap is also on my list of things to look at. I expect it won't be too hard since it already works, we only need to fix the incompatibility with a2sd.

I see you're working alone.

But if you want, I'll PM you my email address and we can start working on this together :huh:

I didn't even know that enabling netfilter is as simple as editing the kernel config.

But I saw erlier that the ar6000 driver is a module that's not integrated in the kernel, right?

So what do we have to patch?

The driver in the kernel, or the ar6000 module (that is located in /etc/*something*/ar6000)?

Greetings,

BigBear

April 25, 2010

I see you're working alone.
But if you want, I'll PM you my email address and we can start working on this together :huh:

I didn't even know that enabling netfilter is as simple as editing the kernel config.
But I saw erlier that the ar6000 driver is a module that's not integrated in the kernel, right?
So what do we have to patch?
The driver in the kernel, or the ar6000 module (that is located in /etc/*something*/ar6000)?

Greetings,
BigBear

I happy to contribute any progress back to the community, but I generally don't have much time to work on this so I expect any progress I do make will be fairly slow. When I have something worth sharing I will let you know.

I'm fairly new to C programming (have experience in other languages, just not C) and kernel/driver hacking so that certainly isn't helping.

The ar6000 module isn't integrated into the kernel (it is in /system/wifi/ar6000.ko). I assume the problem is in the module somewhere, but as I can't be sure. Debugging support isn't great in Android from what i've seen. logcat is ok for app problems but I can't find anything to get kernel messages (dmesg) at the time of the crash, syslogd in busybox appears to be broken.

At the moment I am trying to find a syslog solution that will work. Hopefully I can write syslog to sd card and get some useful debug messages. Is there an adb function I haven't found to stream syslog?

April 26, 2010

Could the issue not be something as simple as the driver needing to be recompiled against a kernel with netfilter enabled? Linux has pretty poor driver compatibility. (Simple as in the cause, not a simple solution :huh:)

Sign In

Why no custom roms?

Recommended Posts

Guest twics

Guest masterpfa

Guest giryan

Guest helikopter

Guest twics

Guest twics

Guest BigBearMDC

Guest brickedMyHuaweiU8230

Guest twics

Guest BigBearMDC

Guest dadme

Guest twics

Guest Tom G

Guest BigBearMDC

Guest Tom G

Guest Josh04

Please sign in to comment

Browse

Activity

Important Information