Android 2.2 Development

[Guest Simon O]

i cant seem to read my contacts from SIM card. I could with FLB but i cannot replace the contacts and contactsprovider apk`s respectively. Any help?

You'll have a hard job. Android was never designed to store contacts on a SIM card. I honestly don't know of any way around this. My experience of SIM contacts on Huawei roms is bad. You can write them but you can't delete them.

[Guest flip360]

its funny because the RBM apk`s could read and backup to sim just fine, damn.

[Guest Rem1x]

Rememeber guys, this is alpha!

Bigger things to worry about :huh:

[Guest flip360]

agreed :huh: and a very good alpha if i might add

[Guest dodge-167]

oh man... I just bought a HTC Hero and it has 2.1, and now Pulse has 2.2... Thats bad luck... Well, ill just steal Pulse from my sister... :huh:

[Guest Rem1x]

oh man... I just bought a HTC Hero and it has 2.1, and now Pulse has 2.2... Thats bad luck... Well, ill just steal Pulse from my sister... :huh:

This might be a stretch but.

Pulse with 2.2 > Hero with 2.1

Really.

[Guest Tom G]

A new issue: Market works, but doesn't find lots of things. It would be nice to check the ROM fingerprint.

Its an engineering build, so uses test keys. Taking a fingerprint off a device with an official Froyo rom should work.

I've been looking into the differences between builds FRF85B and FRF91 and the only differences seem to be some very small security fixes. Tom, did you have problems trying to build FRF91?

No problems with FRF91. The codeaurora source that I was ported the audio from was based on FRF85B, so I used that. I will move to FRF91 as some time.

android2.2_r1=FRF85B

android2.2_r1.1=FRF91

Allso I thing so that making correction in init.rc

export EXTERNAL_STORAGE /mnt/sdcard

to

export EXTERNAL_STORAGE /sdcard


and

# creat mountpoints

	   mkdir /mnt 0775 root system

	   mkdir /mnt/sdcard 0000 system system 


to

#create mountpoints

	   mkdir /sdcard 0000 system system


and delete this line

# Backwards Compat -XXX: Going away in G*

	   symlink /mnt/sdcard /sdcard

Becouse for some unknown reason it only create /mnt, and /mnt/sdcard

but whether it the permissions of /mnt arent righ, or it doesn't do the symlink correct?

Those aren't things I added, they are standard Froyo. The symlink is there for older apps that use sdcard (otherwise they would break).

With the symlink in place it doesn't matter whether the mount point is /sdcard or /mnt/sdcard, it will end up at /mnt/sdcard. None of that is causing the problem, the problem is the way vold is picking partitions (and ignoring vold.fstab).

A short bug report on phone functionality:

Environment:

- Pulse

- 1.5 December Update firmware

- 2.2 0.4 with data and SD card patches

Activity:

I made a relatively long phone call with 3G turned ON. The mobile network was rather poor, so the phone had to do relatively lots of 2G-3G swithces.

Result:

Many reboots similar to that one we had with 2.1 beta.

Question:

Is it possible, that this rild is designed for 2.1 firmware?

It sounds like you have basically the same setup as me.

rild is using the 2.1 driver binary's, so yes it is designed for the 2.1 firmware. I expect we will have the same instability issues that 2.1 on the 1.5 firmware had (which was mostly an issue when switch 2G-3G).

Using the 2.1 firmware will hopefully fix all stability issues.

[Guest screwface]

This might be a stretch but.

Pulse with 2.2 > Hero with 2.1

Really.

Not a chance.

[Guest Rem1x]

Not a chance.

Having used both, 2.2 feels so much smoother.

[Guest AdamBaker]

Is the 2.2 kernel using the binary ar6k driver from /system/wifi in a 2.1 ROM? If so it is possible that kernel internal API changes have broken the status reporting. It should be possible to tell if the problem is a kernel issue by running the iwconfig executable that also lives in /system/wifi.

If that is the problem then we will likely need an open source ar6k driver such as the one at http://git.openmoko.org/?p=kernel.git;a=tr...4056a57eee65e16 which appears to be derived from the same source as the Pulse one although there is evidence Huawei have tweaked some stuff as there is a U8220 firmware file.

[Guest Willz]

What are the current problems with the latest release please guys?

I really want to try 2.2 so I can get my texts through all the time, again. :huh:

[Guest Rem1x]

What are the current problems with the latest release please guys?

I really want to try 2.2 so I can get my texts through all the time, again. :huh:

No use of gyro, no camera.

Too awesome?

edit: Now using Task Tray for true multitasking.

Edited September 1, 2010 by Rem1x

[Guest Willz]

No use of gyro, no camera.

Too awesome?

edit: Now using Task Tray for true multitasking.

What's gyro? :/ and couldn't give a s*** about camera for now. :L

[Guest Rem1x]

What's gyro? :/ and couldn't give a s*** about camera for now. :L

Rotation.

Data does work, but you have to run a script posted in this thread :huh:

[Guest Willz]

Rotation.

Data does work, but you have to run a script posted in this thread :huh:

Oh, so no rotation when texting? ;)

Ah. And how awkward is that? haha.

[Guest Simon O]

What are the current problems with the latest release please guys?

I really want to try 2.2 so I can get my texts through all the time, again. :huh:

No protected apps in the market. Even after I use a fixed build.prop with a different fingerprint. Wiped all phone settings, cleared caches, did the checkin. Nothing seems to work ;)

[Guest Simon O]

its funny because the RBM apk`s could read and backup to sim just fine, damn.

Yes they could. But try deleting a sim contact .. it doesn't work :huh:

[Guest Willz]

I have decided to try this.

But I shall nandroid backup first. So then how do I go about installing 2.2? And if I want to restore, do I just install clockworkmod again and then restore?

[Guest flip360]

Yes they could. But try deleting a sim contact .. it doesn't work ;)

never tried that :huh: but it could backup to sim and also read from it. whats so different about 2.2?

i see that there is no calllog.apk or dialer.apk...

[Guest Simon O]

I have decided to try this.

But I shall nandroid backup first. So then how do I go about installing 2.2? And if I want to restore, do I just install clockworkmod again and then restore?

Nandroid your system then flash the new images using fastboot. It won't do anything to the recovery which will stay on the phone.

[Guest Simon O]

never tried that :huh: but it could backup to sim and also read from it. whats so different about 2.2?

i see that there is no calllog.apk or dialer.apk...

Because this is pure Android. No customisations or custom apps.

[Guest flip360]

thanks flibble, nevertheless I LIKE IT. Keep up the good work guys hope the kernel source gets released!

[Guest Willz]

Nandroid your system then flash the new images using fastboot. It won't do anything to the recovery which will stay on the phone.

Oh. What do you mean by 'flashing the new images using fastboot'? I have only ever flashed through recovery. Or is there a .bat file to run or something?

[Guest AdamBaker]

The accelerometer driver (a gyro is something different) is in the 2.6.27 source (from http://support.t-mobile.co.uk/resources/si...de_11_2009.zip) at drivers/input/accelerometer/gs_st.c. I can't see anything in there that is likely to tie that source to a kernel version.

[Guest Simon O]

Oh. What do you mean by 'flashing the new images using fastboot'? I have only ever flashed through recovery. Or is there a .bat file to run or something?

You need to find fastboot.exe and use that to flast the images:

fastboot.exe flash boot boot.img

fastboot.exe flash system system.img

fastboot.exe flash userdata userdata.img

Should be able to find fastboot in any of the recovery zips on this site.