Need a little help making a custom rom please...

[Guest DanWilson]

Sorry I don't know enough about it to answer that, but my best guess would be it has something to do with the settings in the init.rc that could stop network connectivity?

Bobo? Answer us!

[Guest DanWilson]

Most recent boot.img works with Froyo. Overclock is active.

[Guest BigBearMDC]

Bobo? Answer us!

The ramdisk is usually not the problem, but the cmdline. If you use the wrong cmdline network refuses to work. Don't ask me why, I don't know it :lol:

[Guest BigBearMDC]

Most recent boot.img works with Froyo. Overclock is active.

*BoBo FTW*

:lol:

[Guest DanWilson]

*BoBo FTW*

:lol:

I thought you edited my post so it said Bobo FTW. I was gonna lol.

[Guest starkos]

Most recent boot.img works with Froyo. Overclock is active.

You mean the one I posted above? Glad it's working, does SetCpu show the 6 different clock speeds above 528 that I added then?

The ramdisk is usually not the problem, but the cmdline. If you use the wrong cmdline network refuses to work. Don't ask me why, I don't know it :lol:

That was the first thing I thought of but it wasn't that. It's definitely related to a difference in the ramdisks between Froyo & Eclair, which I think means it must be something in the init.rc?

[Guest twrock]

*BoBo FTW*

B)

And for future reference, here's what BoBo told me elsewhere:

The cmdline is the sum of a few commands that are handed to the kernel when the phone boots up. It is saved at the beginning of the boot image, always starting with an offset of 0x40 (if you open the boot image with a HexEditor).

The easiest way to get the cmdline is either via the boot image and a HexEditor or by pulling it off the running device. If you use a HexEditor just open the an existing boot image and have a look at the first few bytes. You can't miss the cmdline, its at the beginning of the file. Copy it and recompile your boot image with it. Another, maybe easier way is to pull it off the running device. Therefore boot into Android or Recovery and connect your device to your PC. If you start your device in recovery mode you'll have to mount the system partition as rw first:

adb shell mount -o rw /dev/block/mtdblock1 /system

Once that's done you can pull the cmdline off your device by typing:

adb shell cat /proc/cmdline

The console will then print the cmdline to the screen so that you can copy it. Then recompile the boot image - done :lol:

"BoBo FTW", indeed.

(Now all I have to find out is if I really can do this; but that's for another day....)

Edited September 25, 2010 by twrock

[Guest DanWilson]

You mean the one I posted above? Glad it's working, does SetCpu show the 6 different clock speeds above 528 that I added then?

I don't know. It is 728 MHz.

Is that right?

[Guest twrock]

"BoBo FTW", indeed.

(Now all I have to find out is if I really can do this; but that's for another day....)

It is indeed "another day", and to quote starkos: "I HAVE NETWORK haha B) !!"

BoBo, you are "the man". Thanks so much.

So, now that I have the original Tre 2.1 rom rooted and running Apps2SD 2.7.5 final. Next stop, swap. (Should be simple, now that I have at least a clue what I'm doing.) :lol:

Edit: Yep, all went as it should. Swap is running too. Thanks for the help.

Edited September 26, 2010 by twrock

[Guest ve100]

you don't need to do all that to get your kernel commandline or to find out your current cpu speed. the standard linux methods work just fine. you don't even need to reboot into recovery, but you might need root-access though.

open up your terminal emulator, or just use adb:

$ su

# cat /proc/cmdline

... {displays kernel boot parameters}

# cat /proc/cpuinfo | grep -i bogomips

... {displays current processor speed}

hope this helps.

[Guest DanWilson]

you don't need to do all that to get your kernel commandline or to find out your current cpu speed. the standard linux methods work just fine. you don't even need to reboot into recovery, but you might need root-access though.

open up your terminal emulator, or just use adb:

$ su

# cat /proc/cmdline

... {displays kernel boot parameters}

# cat /proc/cpuinfo | grep -i bogomips

... {displays current processor speed}

hope this helps.

Thanks! Never knew that.

# cat /proc/cpuinfo | grep -i bogomips

BogoMIPS : 779.35