New U8230 ROM on HuaweiDevice.com - analysis

[Guest McSpoon]

...lower neocore benchmark then the T-Mobile style MCR with loads of s*** on it...

Strange. It appears to use the same libhgl.so as the T-Mobile December update. Maybe there are lots of background processes that are slowing it down?

(I did a binary comparison between both libhgl.so files and there are no differences. Is there any way to extract the version numbers from .so files? It would be great if we could compare all of the /system/lib/ files of the different roms and figure out which is the latest version of each file.)

[Guest Daniel Williamson]

Just recovered the old rom, for some reson i couldnt start my wifi connection - kept saying unable to start :/

Dan

[Guest Rem1x]

Strange. It appears to use the same libhgl.so as the T-Mobile December update. Maybe there are lots of background processes that are slowing it down?

Well, my version has quite a bit running, as well as canvas, etc.

[Guest klutsh]

Looking at the upgradeable_versions.txt this update is for both the u8220 & u8230

U8220-6V100R001C55B200

U8220-6V100R001C55B201

U8220-6V100R001C55B202

U8220-6V100R001C55B203

U8220-6V100R001C55B204

U8220-6V100R001C55B205

U8220V100R001C85B115

U8230V100R001C01B205SP01

Does this mean if we could edit the build number to match one of those we could apply the actual update file?

Edited February 3, 2010 by klutsh

[Guest McSpoon]

Does this mean if we could edit the build number to match one of those we could apply the actual update file?

It's unlikely. There is a copy of the build number in the android 'build.prop' but changing that will only fool Android, it's unlikely to fool the real hardware. I'm sure it has another copy separate from the Android area as it can be updated without loading Android. I wouldn't risk trying to fool it anyway.

The updata.app file is capable of reprogramming the whole firmware, including the radio frequency bands and everything. So installing the wrong updata.app file could brick a device. Hence why it checks if the device is listed as being upgradeable, and will refuse if it isn't. However it's reasonably safe to extract the Android parts (eg. boot and system image) because they can be flashed with the Android tools and we have Nandroid backup to roll back to if it doesn't work.

But I wouldn't try to install the non-Android parts of the file. I think there could be regional differences between the versions, such as the radio frequency bands for different countries, etc. And I suspect some countries may have slightly different hardware whilst it's still called a U8220. For example, U8220 owners in Chile discovered their touchscreen doesn't work if they use the ROMs from this forum. Perhaps they have a different touchscreen hardware from the European model?

Edited February 3, 2010 by McSpoon

[Guest chris1991]

Is vibrate working on any1 elses cause its not working on anything for mine even though its selected =/

[Guest McSpoon]

Wooo, Huawei have put another 2 ROMs on their website.

They both have the same U8220V100R001GBRC85B118SP01 version number as the T-Mobile UK December update so possibly still Cupcake. But at least there is a "Normal" and UK T-Mobile versions. Hopefully one is less pink!

And the HOST-U8230V100R001C00B002(normal).zip looks like it could be a CD-ROM.

[Guest CHN-michael]

U8220 V100R001GBRC85B118SP01(UK T-Mobile).zip has the same md5 as the 1.5-Dec for T-MOBILE..

[Guest Ashbeard]

Same issue as the December update, must manually enter 3G APN. This is on the 3 network btw. And vibrate seems broken too.

Edited February 3, 2010 by Ashbeard

[Guest robot1000]

Same issue as the December update, must manually enter 3G APN. This is on the 3 network btw.

Same for all Networks

[Guest klutsh]

U8220 V100R001C85B118SP01(norm al) also has all the t-mobile custom stuff in it and a build date of Nov

Edited February 3, 2010 by klutsh

[Guest Paul]

Hmmm, yeah, no vibrate in this build? At least not in Touchpal?

P

[Guest McSpoon]

Boo! They're just teasing us with the old stuff.

[Guest robot1000]

Hmmm, yeah, no vibrate in this build? At least not in Touchpal?

P

Works for me. Just went into touchpal settings and enabled 'Key Press Vibration'.

I'm experiencing an issue with the dialpad sound becoming extremely quiet. The same issue occurred on the other roms

[Guest flip360]

works for me too, also no vibration but everything else works and its feeling snappier than the 1.7 ROM but that may be my personal opinion ;)

Cheers

[Guest ugurr]

hello Paul, first I'm sorry for my english

I have the phone on when U8230 HUAWEI U8230 V100R001C101B219S P02 (France BYTEL) France had BYTEL, here December Update installed, then the moment I can not make any original uptade, uptade failed is failed. And also the first study, on-screen phone T-Mobile has a text written before Huawei was the first study

U8230V100R001C00B250-update-now a rooted-signed

Please help

[Guest Jan M]

this is the best rom yet! fast and no crashing whatsoever (just doesn't vibrate).

[Guest Bakes]

Can confirm that the vanilla 8220 build of this is in fact that december update, whether you pick the T-Mobile or Normal versions.

[Guest Fremske]

Hi everyone,

Currently four roms appeared in feb. 2010 on the Huawei support site, currently rom nr. 2 is tested and modified by Paul and ready for download. But what is the difference with rom nr. 1 this rom appeared like 3 days go on their site. Does anyone have some more insight in the differences?

U8230:

1) U8230 HOST-U8230V100R001C00B002 (Normal) Normal 2010-02-03

2) U8230 U8230V100R001C00B250 (Normal) Normal 2010-02-01

U8220:

3) U8220 U8220 V100R001GBRC85B118SP01 (UK T-Mobile) UK T-Mobile 2010-02-03

4) U8220 U8220 V100R001C85B118SP01 (normal) normal 2010-02-03

Thank you.

Kindest regards,

Frem

[Guest Jan M]

U8230:

1) U8230 HOST-U8230V100R001C00B002 (Normal) Normal 2010-02-03

2) U8230 U8230V100R001C00B250 (Normal) Normal 2010-02-01

U8220:

3) U8220 U8220 V100R001GBRC85B118SP01 (UK T-Mobile) UK T-Mobile 2010-02-03

4) U8220 U8220 V100R001C85B118SP01 (normal) normal 2010-02-03

1 = cd-rom with windows drivers etc

3,4 = identical to dec. update

[Guest androland]

hello Paul, first I'm sorry for my english

I have the phone on when U8230 HUAWEI U8230 V100R001C101B219S P02 (France BYTEL) France had BYTEL, here December Update installed, then the moment I can not make any original uptade, uptade failed is failed. And also the first study, on-screen phone T-Mobile has a text written before Huawei was the first study

U8230V100R001C00B250-update-now a rooted-signed

Please help

Salut j'ai le même soucis

I have the same problem, what is the solution please?? It's very important.. THANKS

[Guest flip360]

after sticking with this ROM for now, i can say that my battery lasts longer, it is snappier than the 1.7 MCR version, i have no need for setcpu tool anymore, only the vibrations are not working? (maybe they are disabled or something) and i have a problem with the music player starting every time i turn on a game on but only with the headphones in :D other than that everything is working jolly good ;)

cheers

[Guest -Yaya-]

i have a problem with the music player starting every time i turn on a game on but only with the headphones in

This is a known bug... ;)

[Guest Jan M]

This is a known bug... ;)

yep...and not only on the pulse...reported 1 year ago:

http://code.google.com/p/android/issues/detail?id=1896

[Guest ugurr]

hello Paul, first I'm sorry for my english

I have the phone on when U8230 HUAWEI U8230 V100R001C101B219S P02 (France BYTEL) France had BYTEL, here December Update installed, then the moment I can not make any original uptade, uptade failed is failed. And also the first study, on-screen phone T-Mobile has a text written before Huawei was the first study

U8230V100R001C00B250-update-now a rooted-signed

Please help

Salut j'ai le même soucis

I have the same problem, what is the solution please?? It's very important.. THANKS

one to help PLS!

Edited February 9, 2010 by ugurr