How clsoe are we to a stable and full 2.2? not beta or alpha

[Guest jennie81]

I'm still on the stock Rom and have been looking into the rather complicated procedure of a new rom. However, there do seem to be lots of issues and fixes that still need to be finished. (i dont want my phone to lock up!)

I do like all the positive speed increases people get with 2.2 however!

A few months then do you think? Or will we never get a true 2.2?

J

[Guest jamidodger1]

Please Use The Search Feature On The Forum, ZTE Are releasing The Offical 2.2 Next Week.

[Guest wbaw]

I'm still on the stock Rom and have been looking into the rather complicated procedure of a new rom. However, there do seem to be lots of issues and fixes that still need to be finished. (i dont want my phone to lock up!)

I do like all the positive speed increases people get with 2.2 however!

A few months then do you think? Or will we never get a true 2.2?

J

I don't think the lock ups are caused by 2.2, I think that's an unrelated hardware problem on some phones. It's just minor problems like the led button backlights not working.

We need to wait until ZTE release an official 2.2 version of the blade (this Wednesday in China) to get a stable 2.2 kernel.

[Guest Simon O]

The phone freezing is happening on Eclair and Froyo ROMs so it's nothing to do with the kernel. Anyway as soon as I get hold of the final China ROm then I'll implement the updates into FLB-Froyo. As my ROM stands at the moment it's stable and all known bugs are fixed along with a few bugs I found. WiFi isn't sorted but since the reconnection bug happens on all custom roms, it's not going to be an easy fix if at all possible.

[Guest jamidodger1]

The phone freezing is happening on Eclair and Froyo ROMs so it's nothing to do with the kernel. Anyway as soon as I get hold of the final China ROm then I'll implement the updates into FLB-Froyo. As my ROM stands at the moment it's stable and all known bugs are fixed along with a few bugs I found. WiFi isn't sorted but since the reconnection bug happens on all custom roms, it's not going to be an easy fix if at all possible.

I Thought Zte's China Rom Fixed WiFi And The LED's

[Guest Sebastian404]

I Thought Zte's China Rom Fixed WiFi And The LED's

for a device that's still not officially on-sale, a lot of people seem to 'known' a lot about....

Considering that all the current 2.2 ROMS are using the kernel from the beta of the fabled Chinese device that does not have LED backlit keys... I'm not sure how they will 'fix' them.

[Guest jamidodger1]

Ah :unsure:

[Guest socialworker]

The phone freezing is happening on Eclair and Froyo ROMs so it's nothing to do with the kernel.

That is WRONG.

There are LOTS (100+) of people reporting screen freezes with Froyo only.

There are some people reporting freezes with 2.1, but most of them seem to be hardware related (some mention squeezing the phone helps, some mention the screen failed totally after a while).

The LOT of people having freezes on 2.2 are running 2.1 without freezes.

2.2 freezes --> software problem (hundreds of people)

2.1 freezes --> hardware problem (a handful of people)

Therefore 2 different kind of problems, only one can be fixed by devs, the other by better qc at zte.

I'm not stating that because I want to prove someone wrong, but because I'm hoping for a fix (for the software induced freezes) which wont be possible if false assumptions are the grounds for research.

[Guest Simon O]

That is WRONG.

There are LOTS (100+) of people reporting screen freezes with Froyo only.

There are some people reporting freezes with 2.1, but most of them seem to be hardware related (some mention squeezing the phone helps, some mention the screen failed totally after a while).

The LOT of people having freezes on 2.2 are running 2.1 without freezes.

2.2 freezes --> software problem (hundreds of people)

2.1 freezes --> hardware problem (a handful of people)

Therefore 2 different kind of problems, only one can be fixed by devs, the other by better qc at zte.

I'm not stating that because I want to prove someone wrong, but because I'm hoping for a fix (for the software induced freezes) which wont be possible if false assumptions are the grounds for research.

I'm not making false assumptions. Froyo and Eclair users are reporting exactly the same issue. Can you prove that the screen freezes in Froyo are caused by software? Can you also prove that hundreds of people have a software problem causing the screen freezes? Honestly, you really can't.

You wrote elsewhere that on "2.1 = working perfectly for weeks, NEVER EVER had a freeze" and many people can say the same about 2.2. The last time I ever had a freeze on Froyo was running a the first Chinese leak.

Finally if your phone is freezing so much then take it back and get a replacement. You have a hardware fault.

[Guest ko0l]

Everyones saying the official version will be released next week, but isn't the japanese version official enough? I doubt the chinese version will fix much, we already have leaks. It'll probably just of be a few fixes with a smoother custom lock screen or something.

Edited January 3, 2011 by ko0l

[Guest Simon O]

Everyones saying the official version will be released next week, but isn't the japanese version official enough? I doubt the chinese version will fix much, we already have leaks. It'll probably just of be a few fixes with a smoother custom lock screen or something.

The Japanese ROM is official but the kernel isn't compatible, so if it was caused by the kernel we can't tell if the Japanese ROM fixes it or not. But if it was a software issue then why would it be so random at happening? Surely if it's a software issue then it would happen often.

[Guest Sebastian404]

The Japanese ROM is official but the kernel isn't compatible, so if it was caused by the kernel we can't tell if the Japanese ROM fixes it or not. But if it was a software issue then why would it be so random at happening? Surely if it's a software issue then it would happen often.

I guess the question we are all waiting to find out is.... how do we know the Chinese 'final' kernel is going to be compatible.....

just because the leaked version running off a development device works, is no sign that the production kernel will...

[Guest kallt_kaffe]

I've never had any freezes on 2.1 or 2.2. However I've had the touchscreen go unresposive once on 2.2 which is propably a driver issue in the beta kernel.

I quite certain that the reason the Japanese (released) kernel does not work on our devices is that it is compiled to be loaded to 0x02600000 while our phones load the kernel to 0x02a00000. There also another adress that is 0x02900000 on our phones that is 0x02600000 in the Japanese kernel. However my experiments with the 2.1 kernel shows that changing these two addresses creates over 300 diffs in the binary kernel so to get the Japanese kernel to work on our phones we need the source.

Hopefully the kernel source can solve some of the issues we have but until we get it we can't be certain that it will.

[Guest kallt_kaffe]

---dbl post---

Edited January 3, 2011 by kallt_kaffe

[Guest kallt_kaffe]

I guess the question we are all waiting to find out is.... how do we know the Chinese 'final' kernel is going to be compatible.....

just because the leaked version running off a development device works, is no sign that the production kernel will...

Wasn't the leak that Pauls Froyo is based on a chinese leak also? The one that the strange lookscreen? That kernel didn't work either so I think all the Froyo kernels will be 0x02600000 so my guess is that the Chinese release won't change the kernel problem. We need the source.

[Guest socialworker]

@fibblesan

What just doesn't make sense to me is:

my Blade + 2.1 = working like a charm

my Blade + 2.2 = freezing like a shaved sheep

That's all the evidence I need.

Of course I can't prove anything for anyone else, neither do I have to.

It's just my assumption made from the behaviour of my phone and from reading this forum quite thoroughly.

I assume that's what your opinion is based on too, so I guess we'll have to wait for another 2.2 kernel to see who got it right :unsure:

[Guest Mit321]

@fibblesan

What just doesn't make sense to me is:

my Blade + 2.1 = working like a charm

my Blade + 2.2 = freezing like a shaved sheep

That's all the evidence I need.

Of course I can't prove anything for anyone else, neither do I have to.

It's just my assumption made from the behaviour of my phone and from reading this forum quite thoroughly.

I assume that's what your opinion is based on too, so I guess we'll have to wait for another 2.2 kernel to see who got it right :unsure:

TBH, I have to agree with this guy, have installed some 2.2 ROMs on people's Blades and have had screen freezes and haven't had any on 2.1 ROM's. If you look in some of the more popular 2.2ROM threads you will see quite a few people complaining about screen freezes. So it must be something to do with the 2.2 surely?

[Guest Sebastian404]

Wasn't the leak that Pauls Froyo is based on a chinese leak also? The one that the strange lookscreen? That kernel didn't work either so I think all the Froyo kernels will be 0x02600000 so my guess is that the Chinese release won't change the kernel problem. We need the source.

I'm not sure where Paul got his kernel from, but I can only assume it was from one of the two leaked Chinesse devices..

We know those development devices have a different partition layout from the ZTE-Blade, one that looks much like the Japanese device.

I'm apparently a miserable pessimist, but I have a feeling people are going to be very disappointed with this fabled Chinese 'perfect' ROM.

[Guest Carlrg]

@fibblesan

What just doesn't make sense to me is:

my Blade + 2.1 = working like a charm

my Blade + 2.2 = freezing like a shaved sheep

That's all the evidence I need.

Of course I can't prove anything for anyone else, neither do I have to.

It's just my assumption made from the behaviour of my phone and from reading this forum quite thoroughly.

I assume that's what your opinion is based on too, so I guess we'll have to wait for another 2.2 kernel to see who got it right :unsure:

I have never had a freeze on 2.1 or 2.2 so is it a hardware problem or could it be user error from people not installing roms and fixes properly. Who knows?

Edited January 3, 2011 by Carlrg

[Guest Simon O]

I'm not sure where Paul got his kernel from, but I can only assume it was from one of the two leaked Chinesse devices..

We know those development devices have a different partition layout from the ZTE-Blade, one that looks much like the Japanese device.

I'm apparently a miserable pessimist, but I have a feeling people are going to be very disappointed with this fabled Chinese 'perfect' ROM.

The first Chinese dump kernel has a base address of 0x02a00000 and the second Chinese dump has 0x02600000 same as the Japanese kernel. So all Froyo roms are using the original froyo kernel (which I didn't know).

But what is puzzling me is why the first Chinese kernel has a different base address.

[Guest hecatae]

The first Chinese dump kernel has a base address of 0x02a00000 and the second Chinese dump has 0x02600000 same as the Japanese kernel. So all Froyo roms are using the original froyo kernel (which I didn't know).

But what is puzzling me is why the first Chinese kernel has a different base address.

if the Japanese Kernel could boot, would we need to build a new Clockwork Mod, or could we install the current version.

Going to try that TPT thing soon with both different base address dumps

[Guest wbaw]

I'm not sure where Paul got his kernel from, but I can only assume it was from one of the two leaked Chinesse devices..

We know those development devices have a different partition layout from the ZTE-Blade, one that looks much like the Japanese device.

I'm apparently a miserable pessimist, but I have a feeling people are going to be very disappointed with this fabled Chinese 'perfect' ROM.

Surely they have to release the source to the kernel including their modifications once they start selling phones based on 2.2

[Guest kallt_kaffe]

The first Chinese dump kernel has a base address of 0x02a00000 and the second Chinese dump has 0x02600000 same as the Japanese kernel. So all Froyo roms are using the original froyo kernel (which I didn't know).

But what is puzzling me is why the first Chinese kernel has a different base address.

It's propably something in the memory addressing that has changed between the first dev phone and the second one that was dumped. If we hade a TPT update for the Softbank phones (or the upcoming Chinese ones) we could perhaps "convert" our blade to use 0x02600000 kernels but compling a new kernel from source would propably be a better solution.

[Guest Sebastian404]

Surely they have to release the source to the kernel including their modifications once they start selling phones based on 2.2

hopefully.. tho agian, looking on the negative side... Im not hopefully it will work, considering the mess they made of it before

[Guest Simon O]

It's propably something in the memory addressing that has changed between the first dev phone and the second one that was dumped. If we hade a TPT update for the Softbank phones (or the upcoming Chinese ones) we could perhaps "convert" our blade to use 0x02600000 kernels but compling a new kernel from source would propably be a better solution.

Hm I wonder if the Hungarian TPT can be modified in that way