Develop Bugs

Data connection problem on my HTC Desire - Desire General

Hi,
Firstly, I have searched the forums and cannot see an answer to this question so apologies if I missed it.
I have an HTC Desire on T-Mobile UK and it is a fantastic phone generally - but I have noticed some issues with the data connection with the phone and wondered if anyone else had the same problems or some ideas/solutions.
My phone does not pick up as strong a signal as I would have expected and the 3G signal seems weaker than I would have thought when I know I have good coverage.
The main two issues are:
- switching from wifi to mobile data is incredibly slow - it is not automatic switch like my old iPhone or HD2 it appears to turn one off and then the other on - is this normal for Android/Desire?
- the other more worrying problem is I was walking where I knew yesterday I had HSDPA coverage and I had no data showing on the phone. After giving up and turning the phone off and then on there it was my data connection. Does anyone else have this problem and if so any advice?
Thank you very much in advance for any help.

I noticed the same yesterday. For some reason the device wouldn't fire up the data connection over T-Mobile UK which was previously working fine from home with wifi off. When out where my Nokia N97 was previously used with a rock solid 3g connection, my Desire wouldn't even try to connect and just displayed a page cannot be loaded error page. I can only presume it had dropped to 2g as there was no 3g or H logo.
I did suspect a local mast outage and will test it again later today but it seems like the 3g reception is flaky on my handset.

Have you guys tried out the APN settings that I posted in another post? Check it out - I don't know if it'll help much, but always worth a try right?

Had a look but those were MMS settings, which I have, I think the phone had picked up from my SIM as it was an unbranded handset. Thanks for posting them anyway
The T-mobile general data APN I have is pretty much the same but without the MMS components ie:
general.t-mobile.uk
username: user
password: pass

nickhem said:
My phone does not pick up as strong a signal as I would have expected and the 3G signal seems weaker than I would have thought when I know I have good coverage.
.......
- the other more worrying problem is I was walking where I knew yesterday I had HSDPA coverage and I had no data showing on the phone. After giving up and turning the phone off and then on there it was my data connection. Does anyone else have this problem and if so any advice?
Click to expand...
Click to collapse
I have to agree with Nickhem, I have previously been using a Compact IV/Touch Diamond on T-Mobile (UK) and all around my house I could always get a strong 3G / HSDPA signal, now on the Desire it seems to flick back and forth between 2G and 3G.
I was using a different ROM (from Shaks on here) with the Compact IV and different Radio to the original, maybe that made a difference?

I was back where I found my phone wouldnt connect to 3g and it seems that it happens anywhere away from my Wifi, if wifi had been previously used. It's not switching to 3G/hsdpa for data and just turns data off by the look of things.
As the OP, I had to turn the phone off and back on to get it to realise no wifi was present and to use 3G. Signal bar was full even once 3G was active, so looks more like a switching issue than a signal problem.
Incidentally, I've got the firmware update as mentioned in another thread but the jump for me was only from 1.15.405.3 to 1.15.405.4. Maybe this is resolved in that update, who knows, will give an update once i find out
I have a Carphone Warehouse handset not one from T-Mobile if that makes a difference.

I bought my Desire SIM free from DeviceWire, and received it Saturday morning. I'm using it with my existing T-Mobile SIM which has come out of a G1. I have the same problem with the phone failing to connect to a mobile data connection when I leave WiFi coverage. Rebooting the phone by powering it off and then on does bring up the 3G or EDGE connection.
I have just submitted a message to HTC support describing the problem. I would encourage everyone with the problem to do the same so that HTC can see that it isn't an isolated problem and that they need to issue a fix quickly.

foner78 said:
I have just submitted a message to HTC support describing the problem. I would encourage everyone with the problem to do the same so that HTC can see that it isn't an isolated problem and that they need to issue a fix quickly.
Click to expand...
Click to collapse
Thanks, done!
Link for others who can't be bothered going to the HTC site
http://www.htc.com/uk/CS_Mail.aspx

I still have this issue and cannot find a way to get the phone to connect without powering it off and on. I have not had a reply from HTC's support.
I'll give it another day or two but then I'll have to consider returning it. This leaves the device virtually worthless to me. What a shame, if this were fixed the Desire really would be THE phone to beat.

Hello! I have the same problem, I will report too this bug to HTC. At this time I am resolving this problem activating-deactivating airplane mode. This way the data connection is up again without needing a system reboot.
Hope this helps. Regards,
Ignacio

Hi. I hv the same. Whenever i leave wifi from at home (morocco) the data connection has been switched off. I also do on/off airplane. Never have this with my Palm Pre. Will drop a complaint as well.

same problem here, desire, orange CH network.

I contacted HTC via the online help and they have suggested ticking the Enable always-on mobile data option in Mobile Network Settings.
I assumed this was like the option on My Nokia N97 to always keep a data connection open even when it isnt required, which would use up battery power. I'll give it a try and see how it goes.

I wish that worked for me, it doesn't seem to make any difference.
Just as an update, I've hard reset the phone today, I haven't installed any apps, left it totally "clean" other than to set up my accounts. It hasn't fixed the problem.
FWIW, a member of HTC support has told me they are treating it as a software issue rather than hardware, are actively investigating the issue and hope to issue a fix "in the near future".

Didnt manage to get a look at the data problem while I was out and about today, however I did enter either a poor T-Mobile coverage area in Bromley, or a T-Mobile mast outage.
The phone had limited/no connectivity offering me Emergency Calls Only and it didn't auto connect to the network again unless I manually chose a network from the list provided, even though I am certain it was initially set to automatic.

not strictly the same issue (not relating to wifi, but not tried that yet)
having nasty issues with 3g/hsdpa on my phone. fresh out of the box it had them and have tried 2 (tmobile) sims in it just in case.
basically my internet seems to stop responding for up to 20 seconds every so often.
Code:
PING www-tmmdi.l.google.com (66.102.9.106) 56(84) bytes of data.
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=1 ttl=50 time=117 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=2 ttl=50 time=116 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=3 ttl=50 time=105 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=4 ttl=50 time=114 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=5 ttl=50 time=102 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=6 ttl=50 time=121 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=7 ttl=50 time=11570 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=8 ttl=50 time=10562 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=9 ttl=50 time=9563 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=10 ttl=50 time=8572 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=11 ttl=50 time=7572 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=12 ttl=50 time=6573 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=13 ttl=50 time=5573 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=14 ttl=50 time=4582 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=15 ttl=50 time=3582 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=16 ttl=50 time=2583 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=17 ttl=50 time=1592 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=18 ttl=50 time=592 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=19 ttl=50 time=122 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=20 ttl=50 time=120 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=21 ttl=50 time=119 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=22 ttl=50 time=127 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=23 ttl=50 time=115 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=24 ttl=50 time=114 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=25 ttl=50 time=112 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=26 ttl=50 time=130 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=27 ttl=50 time=129 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=28 ttl=50 time=128 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=29 ttl=50 time=126 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=30 ttl=50 time=125 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=31 ttl=50 time=124 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=32 ttl=50 time=122 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=33 ttl=50 time=121 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=34 ttl=50 time=119 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=35 ttl=50 time=117 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=36 ttl=50 time=116 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=37 ttl=50 time=115 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=38 ttl=50 time=114 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=39 ttl=50 time=112 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=40 ttl=50 time=131 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=41 ttl=50 time=130 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=42 ttl=50 time=128 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=43 ttl=50 time=127 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=44 ttl=50 time=126 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=45 ttl=50 time=125 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=46 ttl=50 time=123 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=47 ttl=50 time=122 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=48 ttl=50 time=120 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=49 ttl=50 time=119 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=50 ttl=50 time=127 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=51 ttl=50 time=105 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=52 ttl=50 time=113 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=53 ttl=50 time=112 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=54 ttl=50 time=150 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=55 ttl=50 time=129 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=56 ttl=50 time=128 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=57 ttl=50 time=9927 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=58 ttl=50 time=8922 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=59 ttl=50 time=7922 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=60 ttl=50 time=6943 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=61 ttl=50 time=5943 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=62 ttl=50 time=4952 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=63 ttl=50 time=3952 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=64 ttl=50 time=2963 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=65 ttl=50 time=1963 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=66 ttl=50 time=973 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=67 ttl=50 time=122 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=68 ttl=50 time=121 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=69 ttl=50 time=120 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=70 ttl=50 time=118 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=71 ttl=50 time=117 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=72 ttl=50 time=116 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=73 ttl=50 time=114 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=74 ttl=50 time=122 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=75 ttl=50 time=131 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=76 ttl=50 time=129 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=77 ttl=50 time=198 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=78 ttl=50 time=126 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=79 ttl=50 time=124 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=80 ttl=50 time=132 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=81 ttl=50 time=120 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=82 ttl=50 time=119 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=83 ttl=50 time=118 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=84 ttl=50 time=116 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=85 ttl=50 time=115 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=86 ttl=50 time=114 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=87 ttl=50 time=19753 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=88 ttl=50 time=18752 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=89 ttl=50 time=17752 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=90 ttl=50 time=16762 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=91 ttl=50 time=15762 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=92 ttl=50 time=14762 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=93 ttl=50 time=13772 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=94 ttl=50 time=12772 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=95 ttl=50 time=11773 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=96 ttl=50 time=10772 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=97 ttl=50 time=9773 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=98 ttl=50 time=8773 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=99 ttl=50 time=7792 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=100 ttl=50 time=6792 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=101 ttl=50 time=5802 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=102 ttl=50 time=4802 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=103 ttl=50 time=3802 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=104 ttl=50 time=2802 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=105 ttl=50 time=1812 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=106 ttl=50 time=812 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=107 ttl=50 time=123 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=108 ttl=50 time=141 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=109 ttl=50 time=130 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=110 ttl=50 time=129 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=111 ttl=50 time=137 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=112 ttl=50 time=136 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=113 ttl=50 time=125 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=114 ttl=50 time=123 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=115 ttl=50 time=131 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=116 ttl=50 time=130 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=117 ttl=50 time=6840 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=118 ttl=50 time=6132 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=119 ttl=50 time=5133 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=120 ttl=50 time=4133 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=121 ttl=50 time=3133 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=122 ttl=50 time=2133 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=123 ttl=50 time=1133 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=124 ttl=50 time=133 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=125 ttl=50 time=2471 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=126 ttl=50 time=1462 ms
64 bytes from lm-in-f106.1e100.net (66.102.9.106): icmp_seq=127 ttl=50 time=462 ms
doing some speed tests as a seperate test just seems that the whole internet dies, most apps just tend to give up if they are attempting to access when the connection dies.
i do notice it jumping from H to 3g quite a lot (i'm in central london at mo... only get a gprs at home.. again not tested that yet) but when the problems occur it doesnt seem to be relating to a transition between them.
any ideas? getting the same issue?

i have the same problem. going in to airplane mode and then turn airplane mode off again helps sometimes.
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk

Got same issue with no GPRS/3G, also phone will not vibrate on incoming message

Same data connection issue with my Desire (Belgium/Proximus).
Enable/disable Airplanemode sometimes help, but often a reboot is needed :-(
Hope HTC fix this problem very soon...

Resolved
barcode99 said:
Got same issue with no GPRS/3G, also phone will not vibrate on incoming message
Click to expand...
Click to collapse
Believe it or not, i just entered generic APN settings and 3G works like charm... very strange since this should be part of operator settings, at least on WM

Related

Hi I did it and tried the WM5 …. :lol:
but I found one big problem :shock: (( the memory )) :
Program :evil:
Total 24.35 MB
Use 12.80 MB
Free 11.55 MB
Store :evil:
Total 14.57 MB
Use 8.32 MB
Free 6.25 MB
Without any other programs , and if you install any prog. It will keep giving (( No memory available )) and stop .
:idea: (( maybe because it is trail only ))

http://wiki.xda-developers.com/index.php?pagename=Himalaya_2005

I just upgraded my O2 XDA Exec with Ivan's 3.2 AKU ROM but when I check the memory i get these numbers:
Storage:
Total: 35.59 MB
In use: 4.05 MB
Free: 35.54 MB
Program:
Total: 48.20 MB
In use: 19.70 MB
Free: 28.50 MB
Do I need to unlock my ExtROM first? If I unlock it, will upgrading the ROM make use of the unlocked ExtROM?

use the search function and you will find your answer to this question
Regards

xb said:
I just upgraded my O2 XDA Exec with Ivan's 3.2 AKU ROM but when I check the memory i get these numbers:
Storage:
Total: 35.59 MB
In use: 4.05 MB
Free: 35.54 MB
Click to expand...
Click to collapse
I think ur total storage shld b 39.59 MB perhaps.

southernint3l said:
use the search function and you will find your answer to this question
Regards
Click to expand...
Click to collapse
that isn't quite useful. i did search and nothing appeared

i cannot download "Тестпрошивка: http://4pda.ru/forum/dl/post/57433/n560.128mb.rar
Прошивка для 128 RAM: N560_C550_WM6_Pups_777_Team_0_0_4_for128mb: "
from http://4pda.ru/forum/index.php?showtopic=75722.
i do not kown what are error,so i can not download/
who can email me ：[email protected] or upload http://rapidshare.com/
thanks

now is new ROM from http://fsc.newplowe.com web site, with is good for 64 and 128MB RAM version.

Cmd>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x174(372) is BAD block !!!
Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1900
Partition[2], type=0x25, start=0x3200, total=0x25500
Partition[3], type=0x4, start=0x28700, total=0x16900
CE Total Length(with sector info) = 0x5223800
CE CheckSum Length(without sector info) = 0x50E0000
Cmd>task 2a
Check block : 372 - Bad
Help...What the mean???? How do fix this problem....???
Dopod 838pro
Herm 100
IPL-1.04 SPL-2.10 Olipro
Can loding windows, but not stable, how do fix this problem?

What is your phone doing? Is your phone not booting? Almost all hermes devices have bad blocks but still work fine.

section8prime8 said:
Almost all hermes devices have bad blocks but still work fine.
Click to expand...
Click to collapse
Are you sure about that? It is quite weird.

section8prime8 said:
What is your phone doing? Is your phone not booting? Almost all hermes devices have bad blocks but still work fine.
Click to expand...
Click to collapse
Still working, but not stable. What the mean 372 bad block?

burkay said:
Are you sure about that? It is quite weird.
Click to expand...
Click to collapse
Yep, searched the forum and the wiki and it is common to find "bad blocks" on the hermes. It comes from the manufacturer like that. There are a few posts on here that discuss that weirdness. Here's one.

akubiqd said:
Still working, but not stable. What the mean 372 bad block?
Click to expand...
Click to collapse
Ok, not stable as in random resets, or what? What ROM are you using? I'm no expert by any means, but the peeps on here that are will need more info. I will help and do the best I can.

section8prime8 said:
Ok, not stable as in random resets, or what? What ROM are you using? I'm no expert by any means, but the peeps on here that are will need more info. I will help and do the best I can.
Click to expand...
Click to collapse
I using this ROM 23/12/08 20940/build 20931 Manila2D Black FULL...
I loading some program, the touchscreen is dead ,i tried to soft reset it many time but it's still doesn't respond to any touch.

OK, the first thing I do if I have a problem is flash to the AT&T ROM. Try this. Maybe it's something in the ROM when you flashed and a "reset" will help it. Try to flash this and reflash the ROM you liked. I'm limited on having troubles with my phone, but this is where I start. Good luck.

section8prime8 said:
OK, the first thing I do if I have a problem is flash to the AT&T ROM. Try this. Maybe it's something in the ROM when you flashed and a "reset" will help it. Try to flash this and reflash the ROM you liked. I'm limited on having troubles with my phone, but this is where I start. Good luck.
Click to expand...
Click to collapse
Thank you very much....

Hi, I've got "MDA T-Mobile Touch Plus" and it's very slow because I installed some bad programs. I can't uninstall them so I think good way would be hard-soft but maybe there is a new software?
Code:
Rom version 1.35.110.06
ROM date 12/05/07
Radio version 1.58.21.23
Protocol version 25.65.30.04H
CPU QUALCOMM(R) 7200
Speed 400 MHz
RAM size 128 MB
Flash size 256 MB
Data bus 32 bits
Model No. NIKI200
Windows Mobile(R) 6 Professional
CE OS 5.2.1622 (Build 18128.0.4.4)
Processor MSM7200-400MHz
I want it fast and stabile. Can you help me? Where and how to install upgrade? It would be nice if I found polish version of OS.
Thanks in advance!
__
sorry for my english

It's the HTC Nike. Look in that section! http://forum.xda-developers.com/forumdisplay.php?f=404