Android 2.2 Development

[Guest hungary]

and ensure you don't login to google or any other services, or view any websites or do searches/etc that you don't want other people to see. A lot of things are cached in android as you no doubt are well aware.

All previous versions of Android can live quite happily with a completely empty 'data' and 'cache' partition (everything under /cache and /data) (it'll populate them on bootup). I'd be suprised if 2.2 doesn't act in the same way.

Thanks for the warning guys :)

[Guest Epic-Emodude]

What? You have a phone which you never intend to use as... a phone?

Or maybe your one of these people that complains that their contract only allows 1,000 free texts per month?

Being 15 years old and not having many friends (you might be able to see why) i only text people and when I went to phone people im usually at home so I don't really use my phone for calls

[Guest Epic-Emodude]

Please someone send me the data\cust\wifi folder from 2.1 via pm. thanks

Data/cust/wifi contains 1 file called wifi_suppliment.conf that has the following code

# modify for wifi baseline

update_config=1

ctrl_interface=DIR=/data/misc/wpa_supplicant GROUP=system

I couldn't find attachments in pm and im not permitted to upload the file. Hope it helps

Edited August 1, 2010 by Epic-Emodude

[Guest stealthstealer]

Being 15 years old and not having many friends (you might be able to see why) i only text people and when I went to phone people im usually at home so I don't really use my phone for calls

im your friend, emodude :)

[Guest flip360]

me too :)

edit: flashed it and stuck on N1 bootanimation ? should i wipe data before flash?

Edited August 1, 2010 by flip360

[Guest DanWilson]

The entire forum is your friend, homie!

[Guest Epic-Emodude]

im your friend, emodude :)

Thanks =)

[Guest hungary]

Data/cust/wifi contains 1 file called wifi_suppliment.conf that has the following code

# modify for wifi baseline

update_config=1

ctrl_interface=DIR=/data/misc/wpa_supplicant GROUP=system

I couldn't find attachments in pm and im not permitted to upload the file. Hope it helps

Thanks

[Guest rikkiej]

can't wait!!

[Guest hungary]

@Epic: Please send me the /system/cust/life. Thanks!

[Guest Epic-Emodude]

@Epic: Please send me the /system/cust/life. Thanks!

Do you have an email address that i can send thr files to from my gmail account?

Thanx

Aaron

[Guest Tom G]

Well that was a much bigger response than I expected. Thank you to everyone that has taken a look and provided some feedback.

I haven't spent any time on this recently, so any bugs that I mentioned 1-2 weeks ago are still there.

I flashed the 2.2 (0.20) rom:

Its very nice! Great work Tom G!

Working:

Vibrate

2G Network

USB

Apps

Brightness

GPS

Widgets

Browser

SD Card

Broken:

Rotate

Camera

LEDs

3G

Audio

Wi-Fi

Live Wallpaper

54.21 MB free internal storage available!

Edit:

Phone calls working, but the other dont hear anything (because the microphone dont work).

SMS works like charm smile.gif No more sms-issue, like 2.1 T-Mobile Rom.

Its faster after 1 hour running (i think system odexing or caching something) Scrolling much faster, than original 2.1 Rom. (but not faster than LauncherPro)

Ram Usage:

Avail: 12MB+0.00B in 12

Other: 21MB in 3

Edit2:

SD Card Fixed (Unmount and format with phone)

Are you sure GPS works? It wouldn't work for me. I am using the 1.5 firmware so it is interesting to see what works on the 2.1 firmware.

Phone calls working, but the other dont hear anything (because the microphone dont work).

SMS works like charm :) No more sms-issue, like 2.1 T-Mobile Rom.

Its faster after 1 hour running (i think system odexing or caching something) Scrolling much faster, than original 2.1 Rom. (but not faster than LauncherPro)

(Sorry for my bad english, i hope you understand my words)

odexing will come much later and should make it a bit quicker and maybe improve memory usage. There is a lot of prelinking stuff to fix as well which might have a small impact on memory usage. These are very low priority tasks for now.

I think, Tom G is very close to the final working and stable 2.2 FroYo for Pulse :D

The lack of audio is a major issue and I have been stuck on that for a while now. Everything else I have an idea how to fix or can live without, but audio really is a huge problem.

I never tried it, but i think, its work.

@ Tom G: Whats the problem with SD card mounting? I think, the Cam is working, if we have the SD.

The sdcard works, but it always tries to mount the last partition instead of the first. If there is only one partition on the sd it works fine, if the last partition is ext2/3 it will fail. It is a minor problem that I haven't looked into yet, I don't expect fixing it to be difficult.

The camera is not working. Android fails to build without camera support, so I am currently building it with the stub driver. This emulates a camera, but it is not actually driving the hardware. While you will see camera support you will never get a picture out of it with the current setup.

Can you create a rom with the changes you've made (either a flashable or a copy of you nandroid backup if you can remove all your personal information)

Thanx

I doubt he did anything to root it. Its an engineering build so is built rooted.

Is there a possibility that this rom (with fixes from hungary) could be made into a flashable zip so that it can be flashed more easily and people (flibblesan) can make a custom rom from it

I did try to make it as an ota package (update.zip) but it fails because the build system wants a recovery image. I need to look at either including a recovery or finding a way to disable the need for it.

If someone wants to manually extract the image contents and repack them as an update.zip that should work. I tried signing a 2.1 rom last week using JesusFreak's testsign java app and couldn't get it working (java version problem), what do people use for signing roms?

[Guest rikkiej]

The sdcard works, but it always tries to mount the last partition instead of the first. If there is only one partition on the sd it works fine, if the last partition is ext2/3 it will fail. It is a minor problem that I haven't looked into yet, I don't expect fixing it to be difficult.

The camera is not working. Android fails to build without camera support, so I am currently building it with the stub driver. This emulates a camera, but it is not actually driving the hardware. While you will see camera support you will never get a picture out of it with the current setup.

Once you guys get it working, who needs A2SD-ext2 partition when it's built into froyo :)?

[Guest flip360]

booted into froyo just fine, installed gapps from cyanogen, very fast, no fc`s, network working but no data connection, bluetooth working, wifi, 3g and the aforementioned do not. I think we have a fine progress on the froyo front :) waytogo TOM

Edited August 1, 2010 by flip360

[Guest Speckles]

Once you guys get it working, who needs A2SD-ext2 partition when it's built into froyo :)?

The one built into froyo is pants. I'd prefer to just soft-link big APKs to the ext partition on the SD card (rather than the entire app dir)

[Guest gusthy]

booted into froyo just fine, installed gapps from cyanogen, very fast, no fc`s, network working but no data connection, bluetooth working, wifi, 3g and the aforementioned do not. I think we have a fine progress on the froyo front :) waytogo TOM

What is ther matter about the headset? Does it work? (Both incoming and outgoing sound)

[Guest Epic-Emodude]

Any luck with fixing wifi (or any of the other bugs) yet?

[Guest hungary]

@ Tom G:

"Install wireless_tether_2_0_5-pre2.apk

I noticed that when you try to run tethering, it initializes tiwlan with different parameters, so I used those in /etc/wifi/loadit.

So I commented last line and added:

/system/bin/wlan_loader -f /system/etc/wifi/Fw1251r1c.bin -e /proc/calibration -i /data/data/android.tether/conf/tiwlan.ini"

[Guest Tom G]

Any luck with fixing wifi (or any of the other bugs) yet?

Radio data actually works. I mentioned it a week or two back. I think there is a permissions problem stopping Android from recognising it, but you can manually configure it from the command line.

This is only good as a proof that the data connection does work. Android will still not recognise it after manually bringing up the connection. DNS fails. I haven't tried a resolv.conf with some static servers in it yet, that would probably work but it really should set them dynamically by dhcp.

# netcfg

lo	   UP	127.0.0.1	   255.0.0.0	   0x00000049

dummy0   DOWN  0.0.0.0		 0.0.0.0		 0x00000082

rmnet0   UP	0.0.0.0		 0.0.0.0		 0x00001043

rmnet1   DOWN  0.0.0.0		 0.0.0.0		 0x00001002

rmnet2   DOWN  0.0.0.0		 0.0.0.0		 0x00001002

# netcfg rmnet0 dhcp

# netcfg			

lo	   UP	127.0.0.1	   255.0.0.0	   0x00000049

dummy0   DOWN  0.0.0.0		 0.0.0.0		 0x00000082

rmnet0   UP	114.74.101.106  255.255.255.252 0x00001043

rmnet1   DOWN  0.0.0.0		 0.0.0.0		 0x00001002

rmnet2   DOWN  0.0.0.0		 0.0.0.0		 0x00001002

# ping 66.102.11.104

PING 66.102.11.104 (66.102.11.104) 56(84) bytes of data.

64 bytes from 66.102.11.104: icmp_seq=1 ttl=54 time=31535 ms

64 bytes from 66.102.11.104: icmp_seq=2 ttl=54 time=30546 ms

64 bytes from 66.102.11.104: icmp_seq=3 ttl=54 time=29556 ms

64 bytes from 66.102.11.104: icmp_seq=4 ttl=54 time=28575 ms

64 bytes from 66.102.11.104: icmp_seq=5 ttl=54 time=27616 ms

64 bytes from 66.102.11.104: icmp_seq=6 ttl=54 time=26616 ms

64 bytes from 66.102.11.104: icmp_seq=7 ttl=54 time=25616 ms

64 bytes from 66.102.11.104: icmp_seq=8 ttl=54 time=24617 ms

64 bytes from 66.102.11.104: icmp_seq=9 ttl=54 time=23625 ms

64 bytes from 66.102.11.104: icmp_seq=10 ttl=54 time=22626 ms

64 bytes from 66.102.11.104: icmp_seq=11 ttl=54 time=21636 ms

64 bytes from 66.102.11.104: icmp_seq=12 ttl=54 time=20645 ms

64 bytes from 66.102.11.104: icmp_seq=13 ttl=54 time=19646 ms

64 bytes from 66.102.11.104: icmp_seq=14 ttl=54 time=18657 ms

64 bytes from 66.102.11.104: icmp_seq=15 ttl=54 time=17657 ms

64 bytes from 66.102.11.104: icmp_seq=16 ttl=54 time=16666 ms

64 bytes from 66.102.11.104: icmp_seq=17 ttl=54 time=15676 ms

64 bytes from 66.102.11.104: icmp_seq=18 ttl=54 time=14676 ms

64 bytes from 66.102.11.104: icmp_seq=19 ttl=54 time=13686 ms

64 bytes from 66.102.11.104: icmp_seq=20 ttl=54 time=12686 ms

64 bytes from 66.102.11.104: icmp_seq=21 ttl=54 time=11696 ms

64 bytes from 66.102.11.104: icmp_seq=22 ttl=54 time=10696 ms

64 bytes from 66.102.11.104: icmp_seq=23 ttl=54 time=9706 ms

64 bytes from 66.102.11.104: icmp_seq=24 ttl=54 time=8706 ms

64 bytes from 66.102.11.104: icmp_seq=25 ttl=54 time=7716 ms

64 bytes from 66.102.11.104: icmp_seq=26 ttl=54 time=6716 ms

64 bytes from 66.102.11.104: icmp_seq=27 ttl=54 time=5726 ms

64 bytes from 66.102.11.104: icmp_seq=28 ttl=54 time=4726 ms

64 bytes from 66.102.11.104: icmp_seq=29 ttl=54 time=3726 ms

64 bytes from 66.102.11.104: icmp_seq=30 ttl=54 time=2726 ms

64 bytes from 66.102.11.104: icmp_seq=31 ttl=54 time=1736 ms

64 bytes from 66.102.11.104: icmp_seq=32 ttl=54 time=736 ms

64 bytes from 66.102.11.104: icmp_seq=33 ttl=54 time=84.8 ms

64 bytes from 66.102.11.104: icmp_seq=34 ttl=54 time=93.4 ms

64 bytes from 66.102.11.104: icmp_seq=35 ttl=54 time=101 ms

64 bytes from 66.102.11.104: icmp_seq=36 ttl=54 time=100 ms

^C

--- 66.102.11.104 ping statistics ---

36 packets transmitted, 36 received, 0% packet loss, time 35005ms

rtt min/avg/max/mdev = 84.817/14376.724/31535.218/10018.836 ms, pipe 32

# ping google.com	 

ping: unknown host google.com

Some slow pings there.

@ Tom G:

"Install wireless_tether_2_0_5-pre2.apk

I noticed that when you try to run tethering, it initializes tiwlan with different parameters, so I used those in /etc/wifi/loadit.

So I commented last line and added:

/system/bin/wlan_loader -f /system/etc/wifi/Fw1251r1c.bin -e /proc/calibration -i /data/data/android.tether/conf/tiwlan.ini"

Ok, so I guess you've copied that from some other forum? wlan_loader is for loading the firmware for the tiwlan module. We don't use tiwlan, we use ar6000.

The ar6000 module itself loads and I think works correctly, the problem appears to be in wpa_supplicant somewhere and I think is permissions related. If you load the module manually you can manually configure a connection (similar to the radio connection it won't be recognised by Android).

[Guest Epic-Emodude]

Out of interest, what kernel has this been built on .29 or .32?

Also, If you have built it yourself would you be able to add in things like multi-touch and swap support?

Aaron

[Guest flip360]

What is ther matter about the headset? Does it work? (Both incoming and outgoing sound)

i tried and rang somebody but couldnt hear a thing, guess the whole audio part as tom said is not working

@ Epic: its built on the .29 i think

Edited August 2, 2010 by flip360

[Guest Epic-Emodude]

I just sent an angry tweet to t-mobile saying we have a stable froyo rom and they cant even give us 2.1. I would have gone on in a long angry rant but i only had 140 letters =(

[Guest Josh04]

Tom G: It's been a good while since I was looking at it, but when I was going through the Donut code there was definitely a place in some of the Android wifi gubbins where you told it which network adapter/module it was supposed to be using. Without that, the module would load and ifconfig etc would work, but no Android.

[Guest Simon O]

I just sent an angry tweet to t-mobile saying we have a stable froyo rom

that's stretching the definition of stable a bit! :)

[Guest flip360]

that's stretching the definition of stable a bit! :)

LOL