Android 2.1 will be released within the next fortnight

[Guest]

Are you kidding?

SURE!

:D

We're currently 4 guys, anyone that wants to join the FroYo porting project is welcome :rolleyes:

I like your attitude! :(

But what about the driver-problems?

[Guest MrLowHoe]

Are you kidding?

SURE!

:(

We're currently 4 guys, anyone that wants to join the FroYo porting project is welcome :rolleyes:

That's what we need! Some positiveness. I really want to learn how to build roms and use the sdk etc. I miss the days when i develeoped for the PSP homebrew scene...school has taken over but during the holidays I plan on spending some of my time getting to grips with Linux again and the inner workings of Android :D

P.S When you try and make an update that needs more memory work with something like the Pulse [not as much memory as some of the big guys that run Android] what are/would we be sacrificing in the ROM, if anything? Things like features, better looking menus bla bla?

[Guest BigBearMDC]

I like your attitude! :(

But what about the driver-problems?

We just need to port them :rolleyes:

Given that the official word from [email protected] back in January was

You may have grounds to return the device as unfit for purpose, as the purpose you bought it was to run the 2.x Firmware on it.

Luckily, Paul offered me a replacement :D

[Guest BigBearMDC]

That's what we need! Some positiveness. I really want to learn how to build roms and use the sdk etc. I miss the days when i develeoped for the PSP homebrew scene...school has taken over but during the holidays I plan on spending some of my time getting to grips with Linux again and the inner workings of Android :rolleyes:

P.S When you try and make an update that needs more memory work with something like the Pulse [not as much memory as some of the big guys that run Android] what are/would we be sacrificing in the ROM, if anything? Things like features, better looking menus bla bla?

I think nothing.

It should in the worst case be possible to export some things onto the SD card.

So I think we won't drop anything out of the ROM :D

[Guest]

We just need to port them :rolleyes:

Great :D

How long might it take before it's released approximately?

[Guest klutsh]

Luckily, Paul offered me a replacement :rolleyes:

It's ok for some :D

I went and traded my Pulse in for a Hero, am now struggling to save for a Desire/N1 as I'm more comfortable coding in flash, and would like to show that games CAN look just as good on Android as they do on iPhone

Good luck to you, I know people are already merging the SDK and N1 2.2 and getting it running on a G1 with a .29 kernel.

[Guest BigBearMDC]

Great :rolleyes:

How long might it take before it's released approximately?

Hmm, one week, two weeks, months, years ... who knows ...

Sorry, but giving an ETA is impossible (but it will not take years :D)

[Guest Simon O]

I don't want you guys to do something stupid, and screw up your Pulse.

As I saw there's now even a fix for vibration, so I guess there's no reason for me to upload it.

I think you're under-weighting the consequences of installing this update...

I screwed up my Pulse, I cant use bluetooth anymore, I can't return to the good [best] old 1.7 Vanilla MCR, I can't apply the dec update etc...

That reminds me... as the Huawei 2.1 beta updated some hardware for you, preventing you from rolling back to stock or MCR, have you tried installing the Swedish 1.5 update that people are using to fix vibration?

[Guest ogiogi]

Hmm, one week, two weeks, months, years ... who knows ...

Sorry, but giving an ETA is impossible (but it will not take years :rolleyes:)

Maybe we should make it a challenge. Whoever does it first will be forever celebrated by the Pulse owners :D. Maybe even get a small ca$$ prize.

[Guest BigBearMDC]

Maybe we should make it a challenge. Whoever does it first will be forever celebrated by the Pulse owners :D. Maybe even get a small ca$$ prize.

Haha, just hit the "Donate" button in my sig, maybe FroYo will then be released faster :rolleyes:

[Guest ogiogi]

Haha, just hit the "Donate" button in my sig, maybe FroYo will then be released faster :rolleyes:

:D :( :( click, click, click, click, click, click, click, click, click, click, click, click, click, click, click, click, click, click, click, click, click, click, click, click, click, click, ;)

[Guest Simon O]

Translation:

"Huawei is telling us that there won't be an upgrade. this is the explanation that we got:

Huawei has after further investigation come to the conclusion that it won't be possible to upgrade 8220 to Android 2.1. The reason is that there isn't enough internal memory and therefore the phone won't work like it should if upgraded.

As you understand we're as sorry about this as you are."

The community have managed in a few weeks to do what Huawei have been 'trying' to do for months. I say 'trying' because it's clear they haven't been trying at all. Typical corporate tactics. Promise an upgrade to 2.1 for an older device, people buy the device when it's on offer, then say "Sorry. No 2.1 update for you. Buy our lovely new phone instead".

Huawei needed to have made the Pulse with the same RAM/ROM size of the Pulse Mini. And released it with 1.6.

I also cannot believe they consider the Pulse Mini/U8110 as a Pulse replacement. It's horrible! Android sucks on 240x320 resolutions. You might as well buy a Nokia :rolleyes:

[Guest mupra]

When the FroYo source will be available?

[Guest]

Hmm, one week, two weeks, months, years ... who knows ...

Sorry, but giving an ETA is impossible (but it will not take years :rolleyes:)

Ok, great, I'm looking forward to it anyway! :D

[Guest BigBearMDC]

When the FroYo source will be available?

I dunno, but I think in at latest 2 weeks.

BTW, upgrading my Pulse with that vibration-fix-firmware doesn't work either =/

[Guest Simon O]

I dunno, but I think in at latest 2 weeks.

BTW, upgrading my Pulse with that vibration-fix-firmware doesn't work either =/

Damn it! That Huawei file really screwed you up :rolleyes:

BTW are you getting another Pulse?

[Guest BigBearMDC]

Damn it! That Huawei file really screwed you up :(

BTW are you getting another Pulse?

Yep Paul's going to send me a replacement :rolleyes:

He's just awesome! :D

[Guest Simon O]

Yep Paul's going to send me a replacement :rolleyes:

He's just awesome! :D

Send him your broken one so he can have a go extracting the files and fixing it :(

[Guest bga]

... I can't return to the good [best] old 1.7 Vanilla MCR, I can't apply the dec update etc...

Just as anyone else who makes the vibration hack.

If I undarstand it well:

Oh, and a word of WARNING to everyone flashing this. You PROBABLY won't be able to use a2sd if you try to go back to 1.5. I can't confim this, but since this (from what I gathered) essentially will turn your device to a U8220-6, it seems you can't go back to the december update, so I'm pretty certain this is the case...

[Guest MarcusHenrique]

Oh, and a word of WARNING to everyone flashing this. You PROBABLY won't be able to use a2sd if you try to go back to 1.5. I can't confim this, but since this (from what I gathered) essentially will turn your device to a U8220-6, it seems you can't go back to the december update, so I'm pretty certain this is the case...

Now you guys know what it feels like to be a U8220-6 owner with no MCR and a2sd support =/

Ha, just kidding. This is just the case of some dev getting the -6 kernel working with a MCR. I've already tried that alot with Bobo's help. But always end up with no network signal.

[Guest BigBearMDC]

Just as anyone else who makes the vibration hack.

If I undarstand it well:

Yap but the difference is that those who install this update will ever be able to return to a MCR.

[Guest de_shepherd]

The community have managed in a few weeks to do what Huawei have been 'trying' to do for months.

I think its more like the community have taken what Huawei had already done, fixed a few issues and decided that they are prepared to live with the occsaional (or possibly regular) crash as the cost of getting 2.1.

For Tmob or even Huawei to do an official release then crashes should be virtually non-existent - consumer law requires products to be "fit for purpose" after all.

Someone I met a few months back had bought the first Android phone available ... however his report was that it had crashed on him and left him without a functioning mobile phone in the middle of a business trip to the US. Result is that he won't consider and android phone again.

[Guest MarcusHenrique]

Yap but the difference is that those who install this update will ever be able to return to a MCR.

No BoBo, I think what guy means is that after flashing a newer update, it's impossible to reflash december one. Since it'll not be listed as upgradeable devices, remember that issue?

[Guest gsk]

No BoBo, I think what guy means is that after flashing a newer update, it's impossible to reflash december one. Since it'll not be listed as upgradeable devices, remember that issue?

Is it not possible to change the list of upgradeable devices? Or can we not edit these update files at all?

[Guest MarcusHenrique]

Is it not possible to change the list of upgradeable devices? Or can we not edit these update files at all?

I've read bigbear saying that it's quite hard to do, since there are checksums in the file. Don't know what exactly is required to get checksums matched again.