1.6 ROM development

December 16, 2009

By the way, I looked a bit at the ports and files opened by rild on the Huawei ROM. I haven't managed to associate the open ports with processes yet - I'll have to write a program to do that. Might be good to do as a GUI app.

Open TCP Ports

 :20000

 127.0.0.1:9988

 127.0.0.1:5037

 127.0.0.1:58650

 4.13.100.10:41927

 4.13.100.10:56618

 4.13.100.10:40663

Open UDP ports

 127.0.0.1:58626

 :42838

 127.0.0.1:58610

 127.0.0.1:58611

 127.0.0.1:58615

 127.0.0.1:58620

 127.0.0.1:58621

Running processes:

# ps

root	 1	 0	 308   172   c00b7830 0000c74c S /init

root	 2	 0	 0	 0	 c006f9f4 00000000 S kthreadd

root	 3	 2	 0	 0	 c005fb28 00000000 S ksoftirqd/0

root	 4	 2	 0	 0	 c006c774 00000000 S events/0

root	 5	 2	 0	 0	 c006c774 00000000 S khelper

root	 10	2	 0	 0	 c006c774 00000000 S suspend

root	 114   2	 0	 0	 c006c774 00000000 S kblockd/0

root	 118   2	 0	 0	 c01de928 00000000 S kseriod

root	 137   2	 0	 0	 c006c774 00000000 S kmmcd

root	 143   2	 0	 0	 c006c774 00000000 S btaddconn

root	 144   2	 0	 0	 c006c774 00000000 S btdelconn

root	 161   2	 0	 0	 c006c774 00000000 S modem_notifier

root	 164   2	 0	 0	 c006c774 00000000 S smd_tty

root	 175   2	 0	 0	 c006c774 00000000 S qmi

root	 186   2	 0	 0	 c006c774 00000000 S ctl0

root	 189   2	 0	 0	 c006c774 00000000 S ctl1

root	 192   2	 0	 0	 c006c774 00000000 S ctl2

root	 197   2	 0	 0	 c006c774 00000000 S nmea

root	 199   2	 0	 0	 c003b08c 00000000 D rpcrouter

root	 204   2	 0	 0	 c003dc8c 00000000 S krpcserversd

root	 276   2	 0	 0	 c003c0a0 00000000 S kadspd

root	 292   2	 0	 0	 c008fd14 00000000 S pdflush

root	 294   2	 0	 0	 c008fd14 00000000 S pdflush

root	 296   2	 0	 0	 c0093d3c 00000000 S kswapd0

root	 299   2	 0	 0	 c006c774 00000000 S aio/0

root	 301   2	 0	 0	 c006c774 00000000 S nfsiod

root	 308   2	 0	 0	 c006c774 00000000 S mdp_dma_wq

root	 310   2	 0	 0	 c006c774 00000000 S mdp_vsync_wq

root	 312   2	 0	 0	 c006c774 00000000 S mdp_pipe_ctrl_w

root	 409   2	 0	 0	 c006c774 00000000 S diag_wq

root	 476   2	 0	 0	 c01c9e68 00000000 S mtdblockd

root	 502   2	 0	 0	 c006c774 00000000 S usb_work

root	 509   2	 0	 0	 c006c774 00000000 S diag

root	 510   2	 0	 0	 c006c774 00000000 S gs_tty

root	 514   2	 0	 0	 c01d5cd4 00000000 S USB mass_storag

root	 515   2	 0	 0	 c006c774 00000000 S synaptics_wq

root	 526   2	 0	 0	 c006c774 00000000 S gs_wq

root	 554   2	 0	 0	 c006c774 00000000 S kondemand/0

root	 573   2	 0	 0	 c02932f8 00000000 S krfcommd

root	 574   2	 0	 0	 c006c774 00000000 S rpciod/0

root	 605   2	 0	 0	 c0201028 00000000 S mmcqd

system   980   1	 808   168   c019e998 afe0c47c S /system/bin/servicemanager

root	 981   1	 848   288   c00b7e58 afe0c5a4 S /system/bin/vold

root	 982   1	 688   196   c02304e4 afe0ce0c S /system/bin/debuggerd

root	 983   1	 16892 1280  ffffffff bed31328 S /system/bin/rild

root	 984   1	 6892  512   ffffffff afe0ce0c S /system/bin/oem_rpc_svc

root	 985   1	 94228 11536 c00b7e58 afe0c5a4 S zygote

media	986   1	 22724 1368  ffffffff afe0c47c S /system/bin/mediaserver

bluetooth 987   1	 1168  200   c00b7830 bed913b8 S /system/bin/dbus-daemon

root	 988   1	 816   216   c027e9a8 afe0c1dc S /system/bin/installd

root	 992   1	 1688  188   ffffffff afe0c5a4 S /system/bin/syncpcuiu

root	 996   1	 668   152   c00b7e58 afe0c5a4 S /system/bin/syncat

root	 997   1	 732   160   c00b7e58 afe0c5a4 S /system/bin/syncobex

root	 999   1	 3764  196   ffffffff afe0c5a4 S /system/bin/qmuxd

root	 1001  1	 676   160   c00b7e58 afe0c5a4 S /system/bin/syncctl

root	 1004  1	 3344  168   ffffffff 0000e904 S /sbin/adbd

system   1042  985   207284 23800 ffffffff afe0c47c S system_server

radio	1085  985   146888 13752 ffffffff afe0d414 S com.android.phone

app_5	1130  985   137728 13408 ffffffff afe0d414 S com.android.inputmethod.latin

root	 1171  2	 0	 0	 c003be98 00000000 D audmgr_rpc

app_55   1321  985   127048 11184 ffffffff afe0d414 S com.geekyouup.android.widgets.battery

app_65   1417  985   147484 18988 ffffffff afe0d414 S org.connectbot

app_65   1940  1417  748   228   c005d33c afe0d0ac S /system/bin/sh

app_5	2651  985   193324 22252 ffffffff afe0d414 S android.process.acore

rild open files:

lrwx------ root	 radio			 2009-12-15 20:32 0 -> /dev/null

lrwx------ root	 radio			 2009-12-15 20:32 1 -> /dev/null

lrwx------ root	 radio			 2009-12-15 20:32 2 -> /dev/null

lr-x------ root	 radio			 2009-12-15 20:32 3 -> pipe:[466]

l-wx------ root	 radio			 2009-12-15 20:32 4 -> pipe:[466]

lr-x------ root	 radio			 2009-12-15 20:32 5 -> pipe:[467]

l-wx------ root	 radio			 2009-12-15 20:32 6 -> pipe:[467]

l-wx------ root	 radio			 2009-12-15 20:32 7 -> /dev/log/main

l-wx------ root	 radio			 2009-12-15 20:32 8 -> /dev/log/radio

lrwx------ root	 radio			 2009-12-15 20:32 9 -> /dev/ashmem

lrwx------ root	 radio			 2009-12-15 20:32 10 -> socket:[303]

lrwx------ root	 radio			 2009-12-15 20:32 11 -> socket:[305]

l-wx------ root	 radio			 2009-12-15 20:32 12 -> /dev/log/events

lrwx------ root	 radio			 2009-12-15 20:32 13 -> /dev/oncrpc/30000016:f22ae45c

lrwx------ root	 radio			 2009-12-15 20:32 14 -> /dev/oncrpc/30000000:959ac044

lrwx------ root	 radio			 2009-12-15 20:32 15 -> /dev/oncrpc/30000019:ab60a474

lrwx------ root	 radio			 2009-12-15 20:32 16 -> /dev/oncrpc/3000003c:e89364a0

lrwx------ root	 radio			 2009-12-15 20:32 17 -> /dev/oncrpc/30000003:a7eed910

lrwx------ root	 radio			 2009-12-15 20:32 18 -> /dev/oncrpc/3000000e:d0b61921

lrwx------ root	 radio			 2009-12-15 20:32 19 -> /dev/oncrpc/30000002:00020000

lrwx------ root	 radio			 2009-12-15 20:32 20 -> socket:[468]

lrwx------ root	 radio			 2009-12-15 20:32 21 -> socket:[473]

lrwx------ root	 radio			 2009-12-15 20:32 22 -> /dev/binder

lrwx------ root	 radio			 2009-12-15 20:32 23 -> socket:[758]

lr-x------ root	 radio			 2009-12-15 20:32 24 -> pipe:[1037]

l-wx------ root	 radio			 2009-12-15 20:32 25 -> pipe:[1037]

lr-x------ root	 radio			 2009-12-15 20:32 26 -> /dev/alarm

onc_rpc_oem open files:

lrwx------ root	 root			  2009-12-15 20:29 0 -> /dev/null

lrwx------ root	 root			  2009-12-15 20:29 1 -> /dev/null

lrwx------ root	 root			  2009-12-15 20:29 2 -> /dev/null

lrwx------ root	 root			  2009-12-15 20:29 3 -> /dev/oncrpc/3000006b:00010000

lrwx------ root	 root			  2009-12-15 20:29 4 -> socket:[464]

lrwx------ root	 root			  2009-12-15 20:29 9 -> /dev/ashmem

December 16, 2009

We need to be replacing lib files to get a startup. I have just made a 1.6 rom with bluetooth working. It's sick I know. I'll see what else I can do.

EDIT: and sound.

So are you saying that you also couldn't boot until you replaced some lib files? (So far I've only added, not replaced).

If so, which ones and where did you get the libraries that you overwrote with from?

December 16, 2009

So are you saying that you also couldn't boot until you replaced some lib files? (So far I've only added, not replaced).
If so, which ones and where did you get the libraries that you overwrote with from?

I/SystemServer( 1034): Starting Connectivity Service.

W/dalvikvm( 1034): threadid=25: thread exiting with uncaught exception (group=0x4001da18)

E/AndroidRuntime( 1034): Uncaught handler: thread ConnectivityThread exiting due to uncaught exception

That's where it dies. You need to find the lib file that refers to that service and replace it from a original rom. I got mine from a backup (u8320) rom.

December 16, 2009

I/SystemServer( 1034): Starting Connectivity Service.
W/dalvikvm( 1034): threadid=25: thread exiting with uncaught exception (group=0x4001da18)
E/AndroidRuntime( 1034): Uncaught handler: thread ConnectivityThread exiting due to uncaught exception

That's where it dies. You need to find the lib file that refers to that service and replace it from a original rom. I got mine from a backup (u8320) rom.

Hmm I'm confused as to how to find out which library is at fault. I found this useful page that details the boot process - the text highlighted in red 2/3 down the page is the stuff relevant for my problem. The page explains that "SystemServer::init2" is the thread responsible for starting the Connectivity Service.

Edited December 16, 2009 by jmmL

December 16, 2009

This is sick and wrong. I have lost bluetooth ... but I can find/identify wireless networks. It could be my router ... but it goes as far as to "obtain an address" ... then says unsuccessful.

December 17, 2009

Ok, I know I double post, but I don't care. I'm giving up for the night and probably for the next couple of weeks (commitments etc) so i've gone all out on this last one.

Of the original 1.6 source I have wifi detection (no connection) and sound working. These were achieved by making sure the hardware_legacy.so file in the lib folder was copied from a tmobile stock ROM (I think???) so anyways ... while that's all good. I have something more ...

This link below points to a ported 1.6 stock ROM for the G1. It has bluetooth working and wifi detection (again, no connection). Do what you will with it. I've done all I can I think.

http://www.4shared.com/file/174746990/2ee9d03b/G1port.html

Edited December 17, 2009 by xangma

December 17, 2009

Ok, I know I double post, but I don't care. I'm giving up for the night and probably for the next couple of weeks (commitments etc) so i've gone all out on this last one.

Of the original 1.6 source I have wifi detection (no connection) and sound working. These were achieved by making sure the hardware_legacy.so file in the lib folder was copied from a tmobile stock ROM (I think???) so anyways ... while that's all good. I have something more ...

This link below points to a ported 1.6 stock ROM for the G1. It has bluetooth working and wifi detection (again, no connection). Do what you will with it. I've done all I can I think.

http://www.4shared.com/file/174746990/2ee9d03b/G1port.html

Thanks for posting up the files. However, out of the box, I can't get your images to work. I'll attach the logcat - but it's late and I haven't really had time to go through it. It looks like it's failing with the same error that my builds are failing with.

Here's a link to my latest try: http://rapidshare.com/files/321875140/attempt7.zip

I haven't actually flashed that build myself yet, but all I changed between revisions was the replacement of hardware_legacy.so at your suggestion, so there should not be any additional errors. This build in its current state does not fully boot, at least on my pulse.

log.txt

December 17, 2009

Thanks for posting up the files. However, out of the box, I can't get your images to work. I'll attach the logcat - but it's late and I haven't really had time to go through it. It looks like it's failing with the same error that my builds are failing with.

Here's a link to my latest try: http://rapidshare.com/files/321875140/attempt7.zip
I haven't actually flashed that build myself yet, but all I changed between revisions was the replacement of hardware_legacy.so at your suggestion, so there should not be any additional errors. This build in its current state does not fully boot, at least on my pulse.

Swear I replied to this =/ Stupid internet.

Did you make sure you cleared the userdata and cache partitions. I know this probably does nothing, but just to be sure. It actually did work for me so I'm confused. I am also really tempted to try out your ROM but I've just got my phone back up and running ... I think it's the hardware_legacy.so file you have to replace, don't quote me on it. I swear it worked (better at least) when I replaced it. This is assuming you've got all your other wifi drivers etc in there (/wifi, /etc/wifi) or whatever. Good luck.

Edited December 17, 2009 by xangma

December 17, 2009

Swear I replied to this =/ Stupid internet.

Did you make sure you cleared the userdata and cache partitions. I know this probably does nothing, but just to be sure. It actually did work for me so I'm confused. I am also really tempted to try out your ROM but I've just got my phone back up and running ... I think it's the hardware_legacy.so file you have to replace, don't quote me on it. I swear it worked (better at least) when I replaced it. This is assuming you've got all your other wifi drivers etc in there (/wifi, /etc/wifi) or whatever. Good luck.

Haha oops - forgot to add any wifi stuff in (or bluetooth for that matter).

I've never cleared my userdata or cache between flashes - maybe that's why mine kept failing. Is it simply "fastboot erase userdata"? I'll give it a try later in the morning! If you've got time could you grab a logcat of yours successfully booting up?

I've just found a post on the huawei forums claiming that there's a bug in libandroid_runtime.so in the huawei sources - I'll look in to that as well.

December 17, 2009

Could someone please tell me how to extract the contents of an update.zip, particularly how to extract the contents of a UPDATA.APP file within one?

Thanks

December 17, 2009

Could someone please tell me how to extract the contents of an update.zip, particularly how to extract the contents of a UPDATA.APP file within one?
Thanks

Update.zip can contain many things. Commonly .img files are found in there. Or say, boot.img and a system folder. These are signed zip files and can be applied using fastboot (I never have) or nandroid.

APP files and pulling them apart, assuming you're talking about the December update ... I have tried and have no idea. I know specific programs use this extention ... MAC OS being one of them.

December 17, 2009

Update.zip can contain many things. Commonly .img files are found in there. Or say, boot.img and a system folder. These are signed zip files and can be applied using fastboot (I never have) or nandroid.

APP files and pulling them apart, assuming you're talking about the December update ... I have tried and have no idea. I know specific programs use this extention ... MAC OS being one of them.

I assume Paul must have managed to pull the .APP file apart in order to extract the Dec kernel to add to his custom rom?

I tried running the upgrade with the idea of killing the power after the updater has extracted all the files so I can access the device and copy the extracted files off after, but unfortunatly if you kill the updater, it starts again when you re-power!

December 17, 2009

Hex editor is your friend!

No easy way to extract the December update i'm afraid! ;)

P

December 17, 2009

Hex editor is your friend!

No easy way to extract the December update i'm afraid! ;)

P

I guess the best way is: Clean install -> Update -> nandroid backup.

December 17, 2009

Swear I replied to this =/ Stupid internet.

Did you make sure you cleared the userdata and cache partitions. I know this probably does nothing, but just to be sure. It actually did work for me so I'm confused. I am also really tempted to try out your ROM but I've just got my phone back up and running ... I think it's the hardware_legacy.so file you have to replace, don't quote me on it. I swear it worked (better at least) when I replaced it. This is assuming you've got all your other wifi drivers etc in there (/wifi, /etc/wifi) or whatever. Good luck.

It lives! The tip about clearing userdata and cache works! Haven't had time to try much out yet - the camera doesn't seem to work and it recognises wifi networks, but is unsuccessful in connecting (or at least was on my home one). Might try one of my builds now, just to see if erasing the cache and userdata works. Thanks!

We can't be too far off putting out a 1.6 version now, surely?

Edit:

Other things that don't yet work - sdcard, accelerometer and (possibly) GPS.

Edited December 17, 2009 by jmmL

December 17, 2009

It lives! The tip about clearing userdata and cache works! Haven't had time to try much out yet - the camera doesn't seem to work and it recognises wifi networks, but is unsuccessful in connecting (or at least was on my home one). Might try one of my builds now, just to see if erasing the cache and userdata works. Thanks!

We can't be too far off putting out a 1.6 version now, surely?

Edit:
Other things that don't yet work - sdcard, accelerometer and (possibly) GPS.

No I didn't have time to set up the SDcard. It shouldn't be hard. It's the best build I have though, even if it is a dirty port from the G1. I got as far as I could without building again from the source in the stock 1.6 image so I gave up on that.

I think what we need to do is build the system.img again with all the drivers in the right places so it knows which ones to use. I think I have a day off tomorrow, my last one for a while so I may be in tomorrow sorting it out. It's the radio that's getting me ...

December 17, 2009

Which libs have you pulled from the Pulse ROM? The libs for camera / RIL etc?

P

December 17, 2009

Which libs have you pulled from the Pulse ROM? The libs for camera / RIL etc?

P

Yeah I have. It boots, they just don't work. I think a whole rebuild with source drivers is needed =/

December 17, 2009

Here's a logcat of me turning wifi off then on again. I don't know whether the problem is with the build or with my router - I had trouble with DHCP and my router even with the stock rom, although it did eventually spring into life.

I/ActivityManager( 1108): Displayed activity com.android.settings/.WirelessSettings: 730 ms (total 730 ms)

I/wpa_supplicant( 1815): CTRL-EVENT-TERMINATING - signal 15 received

I/wpa_supplicant( 1815): CTRL-EVENT-TERMINATING - signal 0 received

I/wpa_supplicant( 1815): CTRL-EVENT-STATE-CHANGE id=-1 state=8

E/vold	(  997): Unable to lookup media '/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:0001'

E/vold	(  997): Error processing uevent msg (No such file or directory)

E/WifiHW  ( 1108): mac_param=00:25:68:D1:18:22

I/wpa_supplicant( 5886): CTRL-EVENT-STATE-CHANGE id=-1 state=2

I/wpa_supplicant( 5886): CTRL-EVENT-SCAN-RESULTS  Ready

I/wpa_supplicant( 5886): Trying to associate with 00:0f:b5:bc:b5:92 (SSID='boatwifi' freq=2462 MHz)

I/wpa_supplicant( 5886): CTRL-EVENT-STATE-CHANGE id=-1 state=3

I/wpa_supplicant( 5886): CTRL-EVENT-STATE-CHANGE id=0 state=4

I/wpa_supplicant( 5886): Associated with 00:0f:b5:bc:b5:92

I/wpa_supplicant( 5886): CTRL-EVENT-STATE-CHANGE id=0 state=7

I/wpa_supplicant( 5886): CTRL-EVENT-CONNECTED - Connection to 00:0f:b5:bc:b5:92 completed (auth) [id=0 id_str=]

I/wpa_supplicant( 5886): CTRL-EVENT-SCAN-RESULTS  Ready

I/wpa_supplicant( 5886): Trying to associate with 00:0f:b5:bc:b5:92 (SSID='boatwifi' freq=2462 MHz)

I/wpa_supplicant( 5886): CTRL-EVENT-STATE-CHANGE id=0 state=3

I/wpa_supplicant( 5886): CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

I/wpa_supplicant( 5886): CTRL-EVENT-STATE-CHANGE id=0 state=0

I/wpa_supplicant( 5886): CTRL-EVENT-STATE-CHANGE id=0 state=4

I/wpa_supplicant( 5886): Associated with 00:0f:b5:bc:b5:92

I/wpa_supplicant( 5886): CTRL-EVENT-STATE-CHANGE id=0 state=7

I/wpa_supplicant( 5886): CTRL-EVENT-CONNECTED - Connection to 00:0f:b5:bc:b5:92 completed (reauth) [id=0 id_str=]

I/WifiStateTracker( 1108): DhcpHandler: DHCP request failed: Timed out waiting for DHCP to finish

I/wpa_supplicant( 5886): CTRL-EVENT-STATE-CHANGE id=0 state=8

I/wpa_supplicant( 5886): CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

I/wpa_supplicant( 5886): CTRL-EVENT-STATE-CHANGE id=-1 state=8

I/MediaUploader( 1412): No need to wake up

I/wpa_supplicant( 5886): CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

I/wpa_supplicant( 5886): CTRL-EVENT-STATE-CHANGE id=-1 state=8

I/wpa_supplicant( 5886): CTRL-EVENT-STATE-CHANGE id=-1 state=1

December 17, 2009

Here's a logcat of me turning wifi off then on again. I don't know whether the problem is with the build or with my router - I had trouble with DHCP and my router even with the stock rom, although it did eventually spring into life.

I/ActivityManager( 1108): Displayed activity com.android.settings/.WirelessSettings: 730 ms (total 730 ms)

 I/wpa_supplicant( 1815): CTRL-EVENT-TERMINATING - signal 15 received

 I/wpa_supplicant( 1815): CTRL-EVENT-TERMINATING - signal 0 received

 I/wpa_supplicant( 1815): CTRL-EVENT-STATE-CHANGE id=-1 state=8

 E/vold	(  997): Unable to lookup media '/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:0001'

 E/vold	(  997): Error processing uevent msg (No such file or directory)

 E/WifiHW  ( 1108): mac_param=00:25:68:D1:18:22

 I/wpa_supplicant( 5886): CTRL-EVENT-STATE-CHANGE id=-1 state=2

 I/wpa_supplicant( 5886): CTRL-EVENT-SCAN-RESULTS  Ready

 I/wpa_supplicant( 5886): Trying to associate with 00:0f:b5:bc:b5:92 (SSID='boatwifi' freq=2462 MHz)

 I/wpa_supplicant( 5886): CTRL-EVENT-STATE-CHANGE id=-1 state=3

 I/wpa_supplicant( 5886): CTRL-EVENT-STATE-CHANGE id=0 state=4

 I/wpa_supplicant( 5886): Associated with 00:0f:b5:bc:b5:92

 I/wpa_supplicant( 5886): CTRL-EVENT-STATE-CHANGE id=0 state=7

 I/wpa_supplicant( 5886): CTRL-EVENT-CONNECTED - Connection to 00:0f:b5:bc:b5:92 completed (auth) [id=0 id_str=]

 I/wpa_supplicant( 5886): CTRL-EVENT-SCAN-RESULTS  Ready

 I/wpa_supplicant( 5886): Trying to associate with 00:0f:b5:bc:b5:92 (SSID='boatwifi' freq=2462 MHz)

 I/wpa_supplicant( 5886): CTRL-EVENT-STATE-CHANGE id=0 state=3

 I/wpa_supplicant( 5886): CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

 I/wpa_supplicant( 5886): CTRL-EVENT-STATE-CHANGE id=0 state=0

 I/wpa_supplicant( 5886): CTRL-EVENT-STATE-CHANGE id=0 state=4

 I/wpa_supplicant( 5886): Associated with 00:0f:b5:bc:b5:92

 I/wpa_supplicant( 5886): CTRL-EVENT-STATE-CHANGE id=0 state=7

 I/wpa_supplicant( 5886): CTRL-EVENT-CONNECTED - Connection to 00:0f:b5:bc:b5:92 completed (reauth) [id=0 id_str=]

 I/WifiStateTracker( 1108): DhcpHandler: DHCP request failed: Timed out waiting for DHCP to finish

 I/wpa_supplicant( 5886): CTRL-EVENT-STATE-CHANGE id=0 state=8

 I/wpa_supplicant( 5886): CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

 I/wpa_supplicant( 5886): CTRL-EVENT-STATE-CHANGE id=-1 state=8

 I/MediaUploader( 1412): No need to wake up

 I/wpa_supplicant( 5886): CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

 I/wpa_supplicant( 5886): CTRL-EVENT-STATE-CHANGE id=-1 state=8

 I/wpa_supplicant( 5886): CTRL-EVENT-STATE-CHANGE id=-1 state=1

Yeah I got the same. The DHCP just times out. I thought I fixed it when I found the etc folder, there is a dhcpcp or something with some settings in it which I hadn't copied. So I did and then ... still nothing =/

Edited December 17, 2009 by xangma

December 17, 2009

I will attach my init.rc and list of copied files this evening. xangma: Have you tried running rild manually via adb shell (note you can pass the build.prop parameters on the command line)? Do you get the same errors as me? Also, I looked in the rild source, and it definitely doesn't ignore the build.prop.

I'm at a bit of a loss as to what huawei's build has that mine doesn't which can be causing the RPC errors...

Tim, thanks for all the help so far. If you still have that list of copied files and the init.rc around could you post it up? I think it would be helpful to document before everyone winds down for Christmas!

December 17, 2009

You need to set the permissions on the dhcpd in the update zip update-script, check my ROMs for deets. If you don't do that, you won't get a working connection.

P

December 17, 2009

You need to set the permissions on the dhcpd in the update zip update-script, check my ROMs for deets. If you don't do that, you won't get a working connection.

P

I am having a ball of a time with permissions. I think I might just have a radio soon =/ Thanks so much for letting me know that.

EDIT: I am trying to set the permission of the /dev/oncrpc directory in the init.rc file. It's just not getting it. I have chmod 0777 /dev/oncrpc in there, but it just doesn't get it. Help?

Edited December 17, 2009 by xangma

December 17, 2009

I am having a ball of a time with permissions. I think I might just have a radio soon =/ Thanks so much for letting me know that.

EDIT: I am trying to set the permission of the /dev/oncrpc directory in the init.rc file. It's just not getting it. I have chmod 0777 /dev/oncrpc in there, but it just doesn't get it. Help?

I can change permissions of the files individually. Right, next problem ... I got the oncrpc thing to work by adding this to my init.rc:

    chmod 0777 /dev/oncrpc

     chmod 0777 /dev/oncrpc/30000064:00010000

     chmod 0777 /dev/oncrpc/3000000a:00010000

     chmod 0777 /dev/oncrpc/30000048:00010000

     chmod 0777 /dev/oncrpc/30000089:00010000

     chmod 0777 /dev/oncrpc/3000000e:d0b61921

     chmod 0777 /dev/oncrpc/3000006b:00010000

     chmod 0777 /dev/oncrpc/3000000f:1c5a0000

     chmod 0777 /dev/oncrpc/3000008c:00010000

     chmod 0777 /dev/oncrpc/30000013:00020000

     chmod 0777 /dev/oncrpc/30000014:00010000

     chmod 0777 /dev/oncrpc/30000016:f22ae45c

     chmod 0777 /dev/oncrpc/30000093:00000000

     chmod 0777 /dev/oncrpc/30000019:ab60a474

     chmod 0777 /dev/oncrpc/3000001a:00010000

     chmod 0777 /dev/oncrpc/3000001b:d6b8aee8

     chmod 0777 /dev/oncrpc/3000003c:e89364a0

     chmod 0777 /dev/oncrpc/3000005b:e63bc050

     chmod 0777 /dev/oncrpc/3000001d:ba845703

     chmod 0777 /dev/oncrpc/30000000:959ac044

     chmod 0777 /dev/oncrpc/30000002:00020000

     chmod 0777 /dev/oncrpc/3000005f:d9769667

     chmod 0777 /dev/oncrpc/30000003:a7eed910

     chmod 0777 /dev/oncrpc/30000061:00010000

     chmod 0777 /dev/oncrpc/30000081:00010000

     chmod 0777 /dev/oncrpc/00000000:0[/codebox]

I now however have a new logcat error:

[codebox]E/QC-QMI ( 1204): vendor/qcom-proprietary/data/qmi/src/../platform/linux_qmi_qmux_if_client.c: unable to bind to client socket, rc = -1
E/QC-QMI ( 1204): linux_qmi_qmux_if_tx_msg: send error = -1
E/QC-DSS-LIB( 1204): dsc_qmi_driver_init: qmi_wds_srvc_init_client failed for qmi_cid 0 with error 0
I/DEBUG ( 996): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 996): Build fingerprint: 'generic/generic/generic/:1.6/DRD35/eng.root.20091213.115505:eng/test-keys'
I/DEBUG ( 996): pid: 1204, tid: 1204 >>> /system/bin/rild <<<
I/DEBUG ( 996): signal 11 (SIGSEGV), fault addr deadbaad
I/DEBUG ( 996): r0 00000003 r1 deadbaad r2 00000027 r3 ffff629c
I/DEBUG ( 996): r4 ffff6274 r5 afe30048 r6 afe39dd4 r7 bec306d4
I/DEBUG ( 996): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 996): ip 0000001b sp bec30678 lr afe2000b pc afe1072a cpsr 20000030
I/PackageManager( 1139): /system/app/Browser.apk changed; collecting certs
I/DEBUG ( 996): #00 pc 0001072a /system/lib/libc.so
I/DEBUG ( 996): #01 pc 0000bc5c /system/lib/libdss.so
I/DEBUG ( 996): #02 pc 00009f10 /system/lib/libdss.so
I/DEBUG ( 996): #03 pc 0000a02c /system/lib/libdss.so
I/DEBUG ( 996): #04 pc 000095c0 /system/lib/libdss.so
I/DEBUG ( 996): #05 pc 00076032 /system/lib/libril-qc-1.so
I/DEBUG ( 996): #06 pc 00076ca0 /system/lib/libril-qc-1.so
I/DEBUG ( 996): #07 pc 0000ebc6 /system/lib/libril-qc-1.so
I/DEBUG ( 996): #08 pc 0000f88c /system/lib/libril-qc-1.so
I/DEBUG ( 996): #09 pc 00008cbc /system/bin/rild
I/DEBUG ( 996): #10 pc 0000bd60 /system/lib/libc.so
I/DEBUG ( 996): #11 pc b000163c /system/bin/linker
I/DEBUG ( 996): stack:
I/DEBUG ( 996): bec30638 00017bd8 [heap]
I/DEBUG ( 996): bec3063c afe12f59 /system/lib/libc.so
I/DEBUG ( 996): bec30640 afe39f90
I/DEBUG ( 996): bec30644 afe39fe4
I/DEBUG ( 996): bec30648 00000000
I/DEBUG ( 996): bec3064c afe13f0d /system/lib/libc.so
I/DEBUG ( 996): bec30650 00000dc4
I/DEBUG ( 996): bec30654 f9a7a6e1
I/DEBUG ( 996): bec30658 80d09abc
I/DEBUG ( 996): bec3065c ffff6274
I/DEBUG ( 996): bec30660 afe30048 /system/lib/libc.so
I/DEBUG ( 996): bec30664 afe39dd4
I/DEBUG ( 996): bec30668 bec306d4 [stack]
I/DEBUG ( 996): bec3066c afe10723 /system/lib/libc.so
I/DEBUG ( 996): bec30670 df002777
I/DEBUG ( 996): bec30674 e3a070ad
I/DEBUG ( 996): #00 bec30678 bec306d4 [stack]
I/DEBUG ( 996): bec3067c 80d0939c
I/DEBUG ( 996): bec30680 80d09210
I/DEBUG ( 996): bec30684 f9a7a6e1
I/DEBUG ( 996): bec30688 80c0a0d5 /system/lib/libdss.so
I/DEBUG ( 996): bec3068c fffffbdf
I/DEBUG ( 996): bec30690 ffffffff
I/DEBUG ( 996): bec30694 80c100e0
I/DEBUG ( 996): bec30698 00000000
I/DEBUG ( 996): bec3069c 80c0bc61 /system/lib/libdss.so
I/DEBUG ( 996): #01 bec306a0 80c0de14 /system/lib/libdss.so
I/DEBUG ( 996): bec306a4 80c09f15 /system/lib/libdss.so

EDIT: And I know this will probably help Tim somewhere ... i've been finding his posts all over the net about this. After this 'little' init.rc edit, running rild in the shell gives:

# rild

 Router Read Task Starting 

 251 thread state 0x00000012

 Oncrpc Start complete state 0x00001111 

 ONCRPC Opened device: /dev/oncrpc/30000016:f22ae45c

 ONCRPC Opened device: /dev/oncrpc/30000000:959ac044

 ONCRPC Opened device: /dev/oncrpc/30000019:ab60a474

 ONCRPC Opened device: /dev/oncrpc/3000003c:e89364a0

 ONCRPC Opened device: /dev/oncrpc/30000003:a7eed910

 ONCRPC Opened device: /dev/oncrpc/3000000e:d0b61921

 ONCRPC Opened device: /dev/oncrpc/30000002:00020000

 running in foreground..

 using syslog..

 skipping module load

 using log level 0..

 using interface name rmnet

 using dhcp script /opt/qcom/bin/udhcpc.sh

 using module load script /opt/qcom/bin/qcomdsc-kif.sh

 2397: Entering function dsc_dcm_if_create

 2460: Exiting function dsc_dcm_if_create

 2397: Entering function dsc_dcm_if_create

 2460: Exiting function dsc_dcm_if_create

 2397: Entering function dsc_dcm_if_create

 2460: Exiting function dsc_dcm_if_create

 2397: Entering function dsc_dcm_if_create

 2460: Exiting function dsc_dcm_if_create

 [1] + Stopped (signal)        rild[/codebox]

Edited December 17, 2009 by xangma

December 18, 2009

Hi all,

i followed the kernel/custom roms thread since last week as a reader (got my pulse last week ;) ).

I think we should go a different way to port the kernel. First of all we need a build environment.

@xangma

have you seen the conditions in "init.qcom.sh" from your phone? A generic build won't load the

huawei stuff.

According to a possible patch i would recommend to take a closer look at the kernel/msm from codeaurora.

Seems like huawei just made some changes to their kernel. In general i think it's the msm7201a_surf project (codeaurora) with huawei changes.

I am currently trying to build the environment for cupcake. I'll post if i have some news

Edited December 23, 2009 by _Sebastian_

1.6 ROM development

Recommended Posts

Guest Timmmm

Link to comment

Share on other sites

Popular Days

Popular Days

Guest jmmL

Link to comment

Share on other sites

Guest xangma

Link to comment

Share on other sites

Guest jmmL

Link to comment

Share on other sites

Guest xangma

Link to comment

Share on other sites

Guest xangma

Link to comment

Share on other sites

Guest jmmL

Link to comment

Share on other sites

Guest xangma

Link to comment

Share on other sites

Guest jmmL

Link to comment

Share on other sites

Guest rjm2k

Link to comment

Share on other sites

Guest xangma

Link to comment

Share on other sites

Guest rjm2k

Link to comment

Share on other sites

Guest Paul

Link to comment

Share on other sites

Guest Timmmm

Link to comment

Share on other sites

Guest jmmL

Link to comment

Share on other sites

Guest xangma

Link to comment

Share on other sites

Guest Paul

Link to comment

Share on other sites

Guest xangma

Link to comment

Share on other sites

Guest jmmL

Link to comment

Share on other sites

Guest xangma

Link to comment

Share on other sites

Guest jmmL

Link to comment

Share on other sites

Guest Paul

Link to comment

Share on other sites

Guest xangma

Link to comment

Share on other sites

Guest xangma

Link to comment

Share on other sites

Guest _Sebastian_

Link to comment

Share on other sites

Please sign in to comment