Android 2.2 Development

[Guest totiadrenalin]

Correction of the Mount-SDCARD_signed.zip

Now it is work.

For some unknown reason the file wasn't attached in the previews post.

Mount_SDCARD_signed.zip

[Guest hungary]

For some unknown reason the file wasn't attached in the previews post.

Its dont mount the ext2. :huh: Its our real problem with the 2.2.

[Guest M31]

'

Its not 'SIM PIN', its 'NETWORK UNLOCK CODE' (you can buy the code from T-Mobile to unlock the device)

2G and 3G working (i checked it with logcat) and this rom not for daily use!!! ("reverted to FLB 1.5")

Hello!

I flash it and test it, and the GSM or UMTS network is OK, but I have no DATA.

I can live without GPS and Camera, but without DATA no :huh:

[Guest totiadrenalin]

Its dont mount the ext2. :huh: Its our real problem with the 2.2.

Now with new command +

su

mountext2

You can mount your ex2 partition.

But remember.

This think won't mount your ext partition during boot, so if u install a2sd your froyo will never boot up again.

We need to patch the mountd.conf and init.rc to mount the sdcard during boot.

That's why i didn't put the mounting of ext2 partition.

I put dtapps2sd-2.7.5-rc2-signed.zip on this post, but be very careful If you try to play around with a2sd!!!

It'll work anything until next reboot.

Mount_SDCARD_EXT2_signed.zip

dtapps2sd_2.7.5_rc2_signed.zip

Edited August 30, 2010 by totiadrenalin

[Guest totiadrenalin]

Only the automatic network choose work. Manual network change dont work. Error: "error while searching network".

Im living near the borderline, and the phone switch to roaming network, and i cant switch it back for my home network.

LOGCAT:

I/ActivityManager( 1108): Starting activity: Intent { act=android.intent.action.

MAIN cmp=com.android.phone/.NetworkSetting }

D/QCRIL_MSC ( 1044): "RIL"=>"AMSS" [ label = "cm_ph_cmd_get_networks()"];

I/ActivityManager( 1108): Displayed activity com.android.phone/.NetworkSetting:

571 ms (total 571 ms)

D/dalvikvm( 1205): GC_EXPLICIT freed 1478 objects / 77408 bytes in 144ms

D/QCRIL_MSC ( 1044): "RIL"=>"AMSS" [ label = "cm_ph_cmd_get_networks()"];

W/InputManagerService( 1108): Window already focused, ignoring focus gain of: co

m.android.internal.view.IInputMethodClient$Stub$Proxy@43fd8aa8

D/dalvikvm( 1621): GC_FOR_MALLOC freed 9893 objects / 654296 bytes in 74ms

D/QCRIL_MSC ( 1044): "RIL"=>"AMSS" [ label = "cm_ph_cmd_get_networks()"];

W/InputManagerService( 1108): Window already focused, ignoring focus gain of: co

m.android.internal.view.IInputMethodClient$Stub$Proxy@43f8c3a0

D/QCRIL_MSC ( 1044): "RIL"=>"AMSS" [ label = "cm_ph_cmd_get_ph_info()"];

D/MobileDataStateTracker( 1108): default Received state= DISCONNECTED, old= DISC

ONNECTED, reason= (unspecified), apnTypeList= default

It's seems like a the problem is with the RIL

And the DATA to.

Tom!

Can you find what's the problem.

I'm from Macedonia and my network operator is T-mobile Macedonia, but I don't have such a problem.

Maybe there's no config about his network provider.

I can choose needer manual and automatic network.

On froyo of course!

[Guest hungary]

It's seems like a the problem is with the RIL

And the DATA to.

Tom!

Can you find what's the problem.

I'm from Macedonia and my network operator is T-mobile Macedonia, but I don't have such a problem.

Maybe there's no config about his network provider.

I can choose needer manual and automatic network.

On froyo of course!

Thanks for the MountExt2 and ths info. My operator is T-Mobile Hungary!

In hungarian: Magyar fórumtársak! Kérlek teszteljétek, hogy a hálózatválasztás (Settings>Wireless>Mobile Networks>Network operators>Search Networks) nálat működik e FroYo alatt. Nekem két készüléken sem megy. Ha működik, légyszi postoljátok a logcat-et. Köszönöm!

[Guest totiadrenalin]

About the camera!

Check this stuff.

Android Camera API

[Guest totiadrenalin]

Thanks for the MountExt2 and ths info. My operator is T-Mobile Hungary!

In hungarian: Magyar fórumtársak! Kérlek teszteljétek, hogy a hálózatválasztás (Settings>Wireless>Mobile Networks>Network operators>Search Networks) nálat működik e FroYo alatt. Nekem két készüléken sem megy. Ha működik, légyszi postoljátok a logcat-et. Köszönöm!

That's ok.

But would you like to excuse me, and wait an hour or two.

Now I'm pre-occupied, so I will not be able to allocate some time to do this test.

Best regards

Toti

[Guest impalaman]

Thanks for the MountExt2 and ths info. My operator is T-Mobile Hungary!

In hungarian: Magyar fórumtársak! Kérlek teszteljétek, hogy a hálózatválasztás (Settings>Wireless>Mobile Networks>Network operators>Search Networks) nálat működik e FroYo alatt. Nekem két készüléken sem megy. Ha működik, légyszi postoljátok a logcat-et. Köszönöm!

Nálam sem működik a hálózatkeresés, nem vagy egyedül a problémával. :huh:

In english: The network search dont't work for me too, you're not alone with the problem. ;)

Edited August 30, 2010 by impalaman

[Guest gusthy]

Nálam se működik, úgy látszik, ez egy létező hiba.

In english:

It doesn't work for me either, it seems to be an existing issue.

[Guest Patrik W]

Hey!

I have followed this thread for a while and I would like to say that Tom G really have made a great effort on the porting of froyo.

It´s really nice that the audio is working and that making calls is possible.

I found this article that maybe could explain why the wifi is not working. The necessary permissions for the supplicant is explained.

http://hi.baidu.com/aokikyon/blog/item/6ab...49ebf8f885.html

I wish you all that working on this good luck! :-)

/Patrik

[Guest totiadrenalin]

Thanks for the MountExt2 and ths info. My operator is T-Mobile Hungary!

In hungarian: Magyar fórumtársak! Kérlek teszteljétek, hogy a hálózatválasztás (Settings>Wireless>Mobile Networks>Network operators>Search Networks) nálat működik e FroYo alatt. Nekem két készüléken sem megy. Ha működik, légyszi postoljátok a logcat-et. Köszönöm!

I/ActivityManager( 1374): Starting activity: Intent { act=android.intent.action.

MAIN cmp=com.android.phone/.Settings }

D/QCRIL_MSC ( 1312): "RIL"=>"AMSS" [ label = "cm_ph_cmd_get_ph_info()"];

D/QCRIL_MSC ( 1312): "RIL"=>"AMSS" [ label = "cm_ph_cmd_get_ph_info()"];

I/Use2GOnlyCheckBoxPreference( 1474): get preferred network type=7

I/GsmUmtsPreferedNetworkListPreference( 1474): handleGetPreferredNetworkTypeResp

onse

I/GsmUmtsPreferedNetworkListPreference( 1474): the mode which get from NV is GLO

BAL auto, treat it as GSM/WCDMA auto

I/GsmUmtsPreferedNetworkListPreference( 1474): statusNetworkMode : 3, settingsNe

twork : 3

I/ActivityManager( 1374): Displayed activity com.android.phone/.Settings: 866 ms

 (total 866 ms)

I/ActivityManager( 1374): Starting activity: Intent { act=android.intent.action.

MAIN cmp=com.android.phone/.NetworkSetting }

D/QCRIL_MSC ( 1312): "RIL"=>"AMSS" [ label = "cm_ph_cmd_get_networks()"];

I/ActivityManager( 1374): Displayed activity com.android.phone/.NetworkSetting:

583 ms (total 583 ms)

D/skia	( 1474): purging 184K from font cache [23 entries]

D/dalvikvm( 1474): GC freed 3084 objects / 178496 bytes in 122ms

D/skia	( 1464): purging 279K from font cache [34 entries]

D/dalvikvm( 1464): GC freed 30575 objects / 1279288 bytes in 190ms

D/skia	( 1374): purging 168K from font cache [18 entries]

D/dalvikvm( 1374): GC freed 964 objects / 53408 bytes in 295ms

W/phone   ( 1474): Nettype =  NETTYPE_SYS_RAT_GSM_RADIO_ACCESS

D/phone   ( 1474): [wind pnn] operatorNumeric=29401,sim operator = 29401

W/phone   ( 1474): Nettype =  NETTYPE_SYS_RAT_UMTS_RADIO_ACCESS

D/phone   ( 1474): [wind pnn] operatorNumeric=29401,sim operator = 29401

W/phone   ( 1474): Nettype =  NETTYPE_SYS_RAT_GSM_RADIO_ACCESS

D/phone   ( 1474): [wind pnn] operatorNumeric=29402,sim operator = 29401

W/phone   ( 1474): Nettype =  NETTYPE_SYS_RAT_GSM_RADIO_ACCESS

D/phone   ( 1474): [wind pnn] operatorNumeric=29403,sim operator = 29401

W/InputManagerService( 1374): Window already focused, ignoring focus gain of: co

m.android.internal.view.IInputMethodClient$Stub$Proxy@46328b70

D/dalvikvm( 3435): GC freed 10597 objects / 527432 bytes in 117ms

D/dalvikvm( 1478): GC freed 55 objects / 1968 bytes in 111ms

From Froyo logcat (Pulse).

Best Regards

Toti

[Guest totiadrenalin]

Hey!

I have followed this thread for a while and I would like to say that Tom G really have made a great effort on the porting of froyo.

It´s really nice that the audio is working and that making calls is possible.

I found this article that maybe could explain why the wifi is not working. The necessary permissions for the supplicant is explained.

http://hi.baidu.com/aokikyon/blog/item/6ab...49ebf8f885.html

I wish you all that working on this good luck! :-)

/Patrik

Acording to this, all the problems we have been buried in Android Permissions.

GPS, WIFI, Network search, Gyroscope, and Camera.

[Guest totiadrenalin]

Acording to this, all the problems we have been buried in Android Permissions.

GPS, WIFI, Network search, Gyroscope, and Camera.

Tom G!

Check init.rc

I thing there is the biggesт mess.

Make sure the paths are correctly created in init.rc:

mkdir /system/etc/wifi 0770 wifi wifi

chmod 0770 /system/etc/wifi

chmod 0660 /system/etc/wifi/wpa_supplicant.conf

chown wifi wifi /system/etc/wifi/wpa_supplicant.conf

#wpa_supplicant control socket for android wifi.c (android private socket)

mkdir /data/misc/wifi 0770 wifi wifi

mkdir /data/misc/wifi/sockets 0770 wifi wifi

chmod 0770 /data/misc/wifi

chmod 0660 /data/misc/wifi/wpa_supplicant.conf

chown wifi wifi /data/misc/wifi

chown wifi wifi /data/misc/wifi/wpa_supplicant.conf

And

# wpa_supplicant socket (unix socket mode)

mkdir /data/system/wpa_supplicant 0771 wifi wifi

chmod 0771 /data/system/wpa_supplicant

chown wifi wifi /data/system/wpa_supplicant

I'll check this tomorrow, because I need the wifi on my pulse right now and that's why I'm going back to 2.1 now.

I'l restore the froyo tomorrow to see if I could make some progress.

And somebody please to try to patch the mountd.conf and init.rc with this i uploadet.

And rebuild the boot.img again.

So the sdcard will mount propertly during froyo boots up.

modified_mountd___init__1_.zip

Edited August 30, 2010 by totiadrenalin

[Guest hungary]

Tom G!

Check init.rc

I thing there is the biggesт mess.

Make sure the paths are correctly created in init.rc:

mkdir /system/etc/wifi 0770 wifi wifi

chmod 0770 /system/etc/wifi

chmod 0660 /system/etc/wifi/wpa_supplicant.conf

chown wifi wifi /system/etc/wifi/wpa_supplicant.conf

#wpa_supplicant control socket for android wifi.c (android private socket)

mkdir /data/misc/wifi 0770 wifi wifi

mkdir /data/misc/wifi/sockets 0770 wifi wifi

chmod 0770 /data/misc/wifi

chmod 0660 /data/misc/wifi/wpa_supplicant.conf

chown wifi wifi /data/misc/wifi

chown wifi wifi /data/misc/wifi/wpa_supplicant.conf

And

# wpa_supplicant socket (unix socket mode)

mkdir /data/system/wpa_supplicant 0771 wifi wifi

chmod 0771 /data/system/wpa_supplicant

chown wifi wifi /data/system/wpa_supplicant

I'll check this tomorrow, because I need the wifi on my pulse right now and that's why I'm going back to 2.1 now. I'l restore the froyo tomorrow to see if I could make some progress. And somebody please to try to patch the mountd.conf and init.rc with this i uploadet. And rebuild the boot.img again. So the sdcard will mount propertly during froyo boots up.

I checked the init.rc and its OK. I modified it, and its dont work. I think the problem is, system dont create the eth0.

- First init.rc needs to be modified to inform hardware/libhardware_legacy/wifi/wifi.c about the name of the interface, that the driver is already loaded and set the status of wpa_supplicant to running:


setprop wifi.interface "eth0"

setprop wlan.driver.status "ok"



Do NOT add setprop init.svc.wpa_supplicant "running" as I previously mentioned as it will prevent wpa_supplicant from starting from init.


- Secondly hardware/libhardware_legacy/wifi/wifi.c need to be modified so the functions insmod() and rmmod() return 0 (simply add return 0; as the first line in functions since they are not needed when driver is built in kernel) and return before checking for /proc/modules in check_driver_loaded() function.


You might encounter problems with WifiHW module not being able to connect to wpa_supplicant socket even with the correct permisions. Try to turn off / turn on Wifi from the GUI.

[Guest M31]

The manual network change do not work for me too, but I can make a call or send SMS.

However I can not make data a connection. This is a known bug or only I have no luck? :huh:

(T-Mobile H)

[Guest impalaman]

The manual network change do not work for me too, but I can make a call or send SMS.

However I can not make data a connection. This is a known bug or only I have no luck? :huh:

(T-Mobile H)

The data connection problem is a known bug.

[Guest Tom G]

I checked the init.rc and its OK. I modified it, and its dont work. I think the problem is, system dont create the eth0.

- First init.rc needs to be modified to inform hardware/libhardware_legacy/wifi/wifi.c about the name of the interface, that the driver is already loaded and set the status of wpa_supplicant to running:


setprop wifi.interface "eth0"

setprop wlan.driver.status "ok"

Do NOT add setprop init.svc.wpa_supplicant "running" as I previously mentioned as it will prevent wpa_supplicant from starting from init.


- Secondly hardware/libhardware_legacy/wifi/wifi.c need to be modified so the functions insmod() and rmmod() return 0 (simply add return 0; as the first line in functions since they are not needed when driver is built in kernel) and return before checking for /proc/modules in check_driver_loaded() function.


You might encounter problems with WifiHW module not being able to connect to wpa_supplicant socket even with the correct permisions. Try to turn off / turn on Wifi from the GUI.

But it does create eth0.

The module is not already loaded, so we dont want to set status ok. Android successfully loads the module (insmod & rmmod).

wifi.interface is set in build.prop

[Guest Tom G]

I found this article that maybe could explain why the wifi is not working. The necessary permissions for the supplicant is explained.

http://hi.baidu.com/aokikyon/blog/item/6ab...49ebf8f885.html

I wish you all that working on this good luck! :-)

/Patrik

Thank you for the link. I've had a good idea of what was causing the problem for about a week, but haven't had time to look into it further. If I'm right section 8 of that page (about SIOCSIWPRIV) should hopefully hold the answers.

[Guest Tom G]

Now we're getting somewhere.

V/WifiStateTracker( 1117): IP configuration: ipaddr 10.21.194.131 gateway 10.21.194.1 netmask 255.255.255.0 dns1 0.0.0.0 dns2 0.0.0.0 DHCP server 10.21.194.1 lease 86400 seconds

It got an ip through dhcp but not dns settings. Thats a bit strange.

Google loads with http://66.102.11.104, so its definitely work, but domain names won't resolve. I guess a temporary solution could be to put the opendns ips in resolv.conf.

Edited August 31, 2010 by Tom G

[Guest hungary]

Now we're getting somewhere.

V/WifiStateTracker( 1117): IP configuration: ipaddr 10.21.194.131 gateway 10.21.194.1 netmask 255.255.255.0 dns1 0.0.0.0 dns2 0.0.0.0 DHCP server 10.21.194.1 lease 86400 seconds

It got an ip through dhcp but not dns settings. Thats a bit strange. Google loads with http://66.102.11.104, so its definitely work, but domain names won't resolve. I guess a temporary solution could be to put the opendns ips in resolv.conf.

YOu checked the /system/etc/dhcpcd/dhcpcd.conf ? In the 2.2 build its use the 'tiwlan0" If you change it to:

interface eth0

option subnet_mask, routers, domain_name_servers

[Guest Tom G]

YOu checked the /system/etc/dhcpcd/dhcpcd.conf ? In the 2.2 build its use the 'tiwlan0"

If you change it to:

interface eth0

option subnet_mask, routers, domain_name_servers

Thank you. That worked (which is good, because resolv.conf didn't). :huh:

V/WifiStateTracker( 1121): IP configuration: ipaddr 10.21.194.131 gateway 10.21.194.1 netmask 255.255.255.0 dns1 10.21.194.1 dns2 0.0.0.0 DHCP server 10.21.194.1 lease 86400 seconds

It still has some issues with the socket directory not being automatically created and some ownership being wrong, but that should be easy to resolve (I'm doing it manually through the shell at the moment). I don't have time now, but I will get it fixed and new rom uploaded tomorrow.

Some wifi features like signal strength and link speed aren't working. Did they work in official roms? Signal strength is always shown as poor and link speed is shown as 2967552Mbps (not bad for wireless ;)).

[Guest hungary]

Some wifi features like signal strength and link speed aren't working. Did they work in official roms? Signal strength is always shown as poor and link speed is shown as 2967552Mbps (not bad for wireless :huh:).

Yes, both working in official roms.

[Guest flip360]

Nice one guys, next rom will contain working wifi :huh: Wonder whats next after that?

cheers

[Guest DanWilson]

Nice one guys, next rom will contain working wifi ;) Wonder whats next after that?

cheers

Will it?

DO WANT!

But I need to get fastboot working first... Anyone help?

It's stuck on <waiting for device> I'm on Ubuntu 10.04, and it worked before (using fastboot-linux from Paul's AMON-RA zip)

I just don't know what to do... :huh: