Lock Up on T-mobile pulse hungary 2.1 official ROM

[Guest themadwacky1]

Just a quick problem note, i really love the new 2.1 ROM from t-mobile hungary, however, the only thing that bugs me is that i sometimes, when running an app such as facebook or advanced task killer, i get a lock up.

i'm not sure how to describe it but what happens is that the screen freezes and no further action can be taken - the screen becomes unresponsive to touch, and all buttons have no effect.

however, the phone acts like it is still functioning, as the screen dims and eventually goes to standby mode, however, as all buttons and the screen become unresponsive, the only way of rectifying this is by doing as soft battery pull reset.

has anyone else had any problems like this?

thanks.

[Guest campdave]

Just a quick problem note, i really love the new 2.1 ROM from t-mobile hungary, however, the only thing that bugs me is that i sometimes, when running an app such as facebook or advanced task killer, i get a lock up.

i'm not sure how to describe it but what happens is that the screen freezes and no further action can be taken - the screen becomes unresponsive to touch, and all buttons have no effect.

however, the phone acts like it is still functioning, as the screen dims and eventually goes to standby mode, however, as all buttons and the screen become unresponsive, the only way of rectifying this is by doing as soft battery pull reset.

has anyone else had any problems like this?

thanks.

Installed the 2.1 update this morning, and had a lock up on foursquare shortly after, but all fine since then.

[Guest Zsolabola]

Installed the 2.1 update this morning, and had a lock up on foursquare shortly after, but all fine since then.

The same issue for me

Im runnig a custom R7 MCR, i used gtalk while i had my 3 locups in a row

but since then it works fine

I think this behaviour is more frequent on 2.1 than it was before

[Guest eckengucker1]

You've to install the hungarian UPDATA (the secound one) which came with the 2.1 UPDATA.

[Guest -Wii-]

Do you mean the one thats only 1kb?

[Guest n00rbert]

Yep, pretty sure he means the CUSTOMIZED_HU which is only 1 kb :(

Edited June 1, 2010 by n00rbert

[Guest Stevos]

I'm also beginning to think all questions that start with "I have a problem when I use a task killer" have answered themselves.

http://geekfor.me/faq/you-shouldnt-be-usin...r-with-android/

Android isn't windows, and a task manager/killer is not a solution for badly behaved applications.

[Guest -Wii-]

I'm also beginning to think all questions that start with "I have a problem when I use a task killer" have answered themselves.

http://geekfor.me/faq/you-shouldnt-be-usin...r-with-android/

Android isn't windows, and a task manager/killer is not a solution for badly behaved applications.

The first time i updated i put both files on and then pressed vol up red and on and it updated, i took the big file off and left the smaller one on and did the same again and update failed? did I do it all the first time if so what am i doing wrong?

[Guest n00rbert]

The first time i updated i put both files on and then pressed vol up red and on and it updated, i took the big file off and left the smaller one on and did the same again and update failed? did I do it all the first time if so what am i doing wrong?

Did you put the CUSTOMIZED_HU folder on your sd card or the dload folder in it? you should put the dload folder on the root of your sd card.

If you put the CUSTOMIZED_HU folder on it it makes sense, the first time it used the full update since it was in the dload folder on the root of the sd card, the second time there was no dload folder on the root of the sd card so the update failed.

Edited June 1, 2010 by n00rbert

[Guest Zsolabola]

Did you put the CUSTOMIZED_HU folder on your sd card or the dload folder in it? you should put the dload folder on the root of your sd card.

If you put the CUSTOMIZED_HU folder on it it makes sense, the first time it used the full update since it was in the dload folder on the root of the sd card, the second time there was no dload folder on the root of the sd card so the update failed.

You mean before flashing the modaco ROM ?

Do you have any idea what that tiny file contains ?

Because of this problem (it occurred me 5 times today) I've "downgraded" to factory 2.1 with custimzed update implementation

just to see wether this is a HW or SW failure

Any info welcome regarding this :(

thanks

[Guest mehall]

I updated with the CUSTOMIZE_HU and am still getting these lockups. Had sporadic ones, but I had around 5 in the space of an hour today.

[Guest Zsolabola]

@ Mehal

Which ROM do you use ?

Factory 2.1, or an MCR ?

Edited June 1, 2010 by Zsolabola

[Guest n00rbert]

Oh sorry didn't read good, didn't read you had the MCR. I heard that with the MCR it was better to NOT install the CUSTOMIZED_HU, but i thought that only had to do with wifi problems...

Sorry but i'm not really into the MCR.

[Guest]

Just a quick problem note, i really love the new 2.1 ROM from t-mobile hungary, however, the only thing that bugs me is that i sometimes, when running an app such as facebook or advanced task killer, i get a lock up.

i'm not sure how to describe it but what happens is that the screen freezes and no further action can be taken - the screen becomes unresponsive to touch, and all buttons have no effect.

however, the phone acts like it is still functioning, as the screen dims and eventually goes to standby mode, however, as all buttons and the screen become unresponsive, the only way of rectifying this is by doing as soft battery pull reset.

has anyone else had any problems like this?

thanks.

You sure it's not just slow response which pops up a "force close" some time later? I got this straight after update but a reboot sorted it all out and not seen it for a day or so. When I did simply hitting "wait" on the force close screen sorted it out temporarily.

[Guest mehall]

@zsolabola:

Stock Huawei T-Mobile 2.1

[Guest Zsolabola]

@zsolabola:

Stock Huawei T-Mobile 2.1

Bad news for us I think :(

I'll use my phone tomorrow with stock 2.1 and with customized to check it

[Guest mehall]

It's not happening every day, it was fine all through Monday with medium-light usage, and only froze once on Sunday, with heavy heavy usage

[Guest Azurren]

Only seems to happen when using apps that use a burst of cpu and data for me.

Such as market and facebook refreshes. Luckily it is rare and something we may just have to live with :(

[Guest themadwacky1]

Only seems to happen when using apps that use a burst of cpu and data for me.

Such as market and facebook refreshes. Luckily it is rare and something we may just have to live with :(

Hmmm...yes, that could be the problem.

I have only had it whilst using facebook or advanced task killer (although i have now uninstalled that, to see if it makes any difference).

Also, i have installed the customised_hu thing, however, i have noticed little, if any difference in the before and after.

[Guest Zsolabola]

It's not happening every day, it was fine all through Monday with medium-light usage, and only froze once on Sunday, with heavy heavy usage

Did you used the android keyboard while the phone was locked ?

In the stock relese the android keyboard has a minor bug.

The word prediction cannot be turned off.

Because of this i'm not using it, instead of that today i was using touchpal

No lockups for me

All my previos lockups were during typing

[Guest mehall]

No, I always use Touchpal, really don't like the stock keyboard much.

[Guest Zsolabola]

Then i guess this isn't the solution

I'm running the T-mob stock version with customized for over a day now without any problems

Tomorrow i'll try the MCR again

Thanks

[Guest not so humble german]

I once had a lockup with the browser. That was 8 days ago.