Database Users

Losing phone network randomly

I'm having a wierd problem with my Hermes. I have the Scnaps 4.01 WM6 rom on my phone right now, but the same thing happened with Blacks rom when i was running that.
Sometimes when i turn it on, it says it has signal so i try to make a call i get operation failed, and then you see the signal drop back to searching, it finds the network and then logs back on. Same thing happens even if i dont make a call, turn on the hermes, and look at it, has signal, then 10 seconds or so later it drops to searching (it never really had signal) then logs back on, and then sms's get delivered. I've also had people try to call me during this time and it's like the phone is off.
I've tried a few different radio versions recently but same behavior with all of them. 1.54.30, 1.54.07 and currently on 1.43.
Something else weird is the fact that it seems like (I could be wrong) this only happens after having the rom on for a week or so, ie after flashing a rom, the first week or so i don't get the issue, then it slowly starts to happen - this could just be my imagination.
Has anyone else had this issue? Any ideas/suggestions welcome, thanks

Hi Ferni...
This is something that is becoming quite an issue recently
Firstly, have you made sure the SIM contacts are nice and clean and everything is fitted OK - and have you tried a different rom image? If not - try these first.
Secondly, where abouts in the world are you and what network are you on?
Thirdly - when did you install 1.54.30 and 1.54.07 - did your problems start before or after you flashed a 1.54x radio - and what radio were you running before trying these.
Finally - What other information do you have about your device - is it a herm100,200 or 300, what IPL/SPL is it.
Sorry for the 100 questions, but I'm investigating these issues at the moment as a lot of users have had similar problems especially after using radio 1.54.x as this thread discusses.

Thanks for the reply. Just read the other thread you linked to (and the threads it linked to). Interesting to know i'm not the only one.
I just pulled the sim out and gave it a rub and the contacts and put it back in. I also had a bigger battery in it, so i removed that and put the standard one back in. See if that makes a difference.
I used to run the black rom, now I run the schaps one, trying to avoid flashing it again just a pain to resetup everything you know....
I'm in Australia, on the Optus network. The JasJam is actually only sold by Telstra here, but i got one 2nd hand and use it on the optus network fine (Optus sell the Dopod). The latest radio rom 1.54.30.10 i belive is actually from Telstra - in the offical WM6 rom from them for the JasJam.
As for when i flashed which rom and when the problems started happening - i can't really say sorry, i didn't keep track. I've had the phone around 6 months, flashed it with a cooked WM6 rom (black i think) when i first got it, i probably updated the radio as well.
How do i tell if it's a 100, 200 or 300? Also not sure what SPL it is, HardSPL or something?
Tempted to flash it to the official telstra rom released recently with the latest radio, so if it does die completely i can send it back for warrenty. What do you think?

Thanks for the info - every little helps at the moment!
Firstly, yes - the radio you're running is native to the area and network and so if you're running 1.54.30.10 and it goes duff you should be covered by your warranty so don't worry. Also, it's not certain yet that there is definitely a problem with this radio so don't loose too much sleep. (Most of the problems linked with this radio that I've researched so far seem to be coming from Europe and after rolling back).
As for flashing with the official ROM, that's a decision for you - however in the cases of sudden GSM death, the phone will still boot to Windows and it is still possible to flash the OS and bootloader roms (just not the radio) so if it did go bad with an unofficial ROM on it you should still be able to roll it back - again sleep easy ;-).
As for the problem - the steps you've taken are a good start, see how it goes and keep us informed here.
It may be worth also trying to manually set your band (if applicable on your network). Sometimes problems like this can be caused by issues on the network itself and trying an alternative (maybe a friends) SIM card for a different network or even manually switching the phone to GSM (if available) can "cure" a problem (although it's a pain if you specifically need to use 3G and it's data speeds!).
Finally - to see your full device information you need to enter the "bootloader" (tricolour) screen. Hang on to this information on the bootloader screen as it can be useful if you ever encounter a bad flash.
To do this, hold the OK button on the left of your phone and the power button on the right then press the little reset button with your stylus. You will then see the model at the top with the IPL version below it and then the SPL version below that. To get out of the tricolour screen, press the reset button again. Needless to say this won't erase anything or damage your device but make sure you close your apps and save your data first

I'm not running 1.54.30.10 right now, think i'll flash back to that monday just in case.
Since changing my battery back to the original and cleaning the sim card, still having the same problem. Seems to be happening more and more often as time goes on.
I've actually already manually set my band and tried to run without 3g turned on before i posted this thread when i was doing my own trouble shooting, and it didn't help.
When flashing i normally just push autodetect which is why i don't know my bootloader info off the top of my head.
It's a HERM100 running IPL-1.04 and SPL2.10.Olipro.
I'm starting to think it only has a limited time left in it before it doesn't pick up radio at all. When that happens i'll flash the official firmware back on it, and the orig bootloader (not sure how to do that yet, will have to look it up). And see if i can get warrenty.

ferni said:
I'm not running 1.54.30.10 right now, think i'll flash back to that monday just in case.
Click to expand...
Click to collapse
What radio are you currently running? Thought it was 1.54.30.10 or did you change that the other day when trying a new ROM?
ferni said:
Since changing my battery back to the original and cleaning the sim card, still having the same problem. Seems to be happening more and more often as time goes on.
I've actually already manually set my band and tried to run without 3g turned on before i posted this thread when i was doing my own trouble shooting, and it didn't help.
When flashing i normally just push autodetect which is why i don't know my bootloader info off the top of my head.
It's a HERM100 running IPL-1.04 and SPL2.10.Olipro.
I'm starting to think it only has a limited time left in it before it doesn't pick up radio at all. When that happens i'll flash the official firmware back on it, and the orig bootloader (not sure how to do that yet, will have to look it up). And see if i can get warrenty.
Click to expand...
Click to collapse
*IF* this is the sudden GSM death syndrome then it will progressively get worse unfortunately - but it might not be that (think positive!)
[edit : removed - brainfart you answered my question] Incidentally, just updated this thread here - Look at post #60, it's a long post but there is a couple of possible things for you to try there (multiple flashing on a "chilled" phone) for users who STILL have some GSM connectivity... Might be worth a go and certainly could do no more harm... The post itself is very technical but just follow the instructions about 3/4 way through the post and ask any questions back here in this thread so things don't get too confused!
In terms of flashing your ROM - when you _really_ feel the phone may die _very very soon_ then it's worth considering flashing it with the latest OFFICIAL rom from your provider while you are able to do a full flash but don't leave it until DHL are at your door to collect it just in case you need some help!
Oh yeah... and finally for tonights post - Rolling back from Olipros Hard SPL... back to the normal, official SPL - Mr Vanx has written a fantastic guide to this here complete with illustrations - That should save you some searching
The SPL rollback, of course, should be the very last thing to do before shipping it back under warranty of course tho - just incase you need it in the mean time!
Good luck - and keep us updated - particularly if all works again (or not)forum.xda-developers.com/showthread.php?t=299070&page=32

I'm on 1.43 right now.
So what you think i should do is put my phone in the fridge (minus battery) for 10-15mins, then flash 1.43 a couple of times while it's still cold, and see how that goes?

ferni said:
I'm on 1.43 right now.
So what you think i should do is put my phone in the fridge (minus battery) for 10-15mins, then flash 1.43 a couple of times while it's still cold, and see how that goes?
Click to expand...
Click to collapse
Yes. Crazy as it sounds, if the previous radio caused "logical" bad blocks - a combination of a couple of flashes in quick succession with the PLA at a cooler temperature might recover them! (temperature issue came from the data sheet for the chip itself - Apparently more efficient writing at temperatures a minimum of 10C below ambient).
Good luck - let us know how it goes... I've got my fingers crossed you'll have a Hermes with it's wings back shortly

Last night the phone got worse, i had a missed call, tried to turn the unit on to see who it was and it wouldn't turn on, so i soft reset it, it booted up ok, but wouldn't pick up a signal.. eventually after about 5mins it did, but then it locked up. So i pulled my sim card out put it into an old phone which i'm using for now.
This morning came into work and put it in the fridge for 15mins, and flashed the latest radio firmware on it. Then flashed the latest official telstra rom onto it (getting ready for warrenty). That's just finished, only step left is to put the original boot loader back on. May test it again for a couple of days to see if i can get it to do the same thing on the offical rom/radio before i send it back. Will let you know.
Thanks for your help so far.

Ok Just another update, only a couple of hours since i flashed it and it's already doing the same thing, losing network, so going to call imate and send it for warrenty. We tried

ferni said:
Ok Just another update, only a couple of hours since i flashed it and it's already doing the same thing, losing network, so going to call imate and send it for warrenty. We tried
Click to expand...
Click to collapse
We did indeed - Ah well, at least you're covered by warranty
Mr Vanx has written a fantastic guide to rolling your bootloader back - complete with illustrations. (repeated for others who've just started reading this thread)

Yeah hopefully it gets covered under warrenty. That bootloader guide worked perfect

For anyone who cares, they replaced my radio board under warranty - I now have a new IMEI number. Haven't got the phone back yet to test to see if it's fixed.

Did you ever upgraded the Radio ROM ?
Or was it always 1.43.
My first ROM only upgrade.
http://forum.xda-developers.com/showpost.php?p=1462158&postcount=292

Yeah i had tried a few different radio roms before this. I suspect it didn't like being flashed so many times.

I am having same problem with 8525 here in south texas. currently running latest att official rom. I have flashed k 1.30, tnt special, schaps rom in last week and so as 1.41.xx , 1.48.00.00, 1.51.xxxx, 1.54.xx xx rom and all have same problme.
Don;t know what to do?

I live in WI and travel to rural areas where there is no 3g. I have experienced this same problem when I loose the signal from a 3g area to a non 3g area as it reacquires the signal. I did all the recommended fixes with bandswitch and activesync but to no avail. However, I did this about a week ago, and my problem seem to have disappeared
Go to advance config>data connections>gprs auto attach
disable it
I think the phone goes beserk when it doesn't find the 3g signal?
Try it and please report back if it works

gondalguru said:
I am having same problem with 8525 here in south texas. currently running latest att official rom. I have flashed k 1.30, tnt special, schaps rom in last week and so as 1.41.xx , 1.48.00.00, 1.51.xxxx, 1.54.xx xx rom and all have same problme.
Don;t know what to do?
Click to expand...
Click to collapse
I flashed one of the wm6.1 roms and ended up with 1.54.07 radio and was getting the "modem disconnected" error message everytime I tried to log on to the internet.
I reflashed the original WM6.0 ROM from AT&T and then reflashed my radio to 1.48 (can't go back to 1.16 because of the radio bootloader I think) and then tried to log on to the internet.
That didn't work
But then I made a phone call to my home phone
tried logging on and it worked.
Been working fine since
crossing my fingers and hoping I dodged the bullet, not gonna flash again til ATT comes out with 6.1 then if it acts up even a little I am gonna send it in for warranty repair.
I hope this procedure works for you mate.

pedro2k said:
I live in WI and travel to rural areas where there is no 3g. I have experienced this same problem when I loose the signal from a 3g area to a non 3g area as it reacquires the signal. I did all the recommended fixes with bandswitch and activesync but to no avail. However, I did this about a week ago, and my problem seem to have disappeared
Go to advance config>data connections>gprs auto attach
disable it
I think the phone goes beserk when it doesn't find the 3g signal?
Try it and please report back if it works
Click to expand...
Click to collapse
Not exactly sure where this setting is, the closest thing I could find was to install HTweakC. And now I have auto attach off. I also live in WI rural area, and 3G has been growing. Coming closer my home, and when I go to work it switches to 3G from Edge and I believe this is the biggest cause of this problem. I will let everyone know if this has helped me or not.

Thanks pedro for your suggestion. I will try that and will report back.

Latest Official HTC ROM trashed my device!!!

Hello
Just installed the latest official HTC ROM - RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship - from the HTC website on my device. Upgrade went smooth as so many upgrades (with other phones) before. When it boots 'smart mobility' is shown in it's normal colour for around two seconds during which the font gets some sort of dropshadow effect (much like looking through unclean glasses) and then turns cyan. WM start screen is displayed as I describe as watercolour. Switching off screen and back on gets the normal graphic to live but still with a reoccuring 'smear effect' much like at the start. Device is very sluggish and freezes. Wifi and BT are on by default, no Phone and data reception. When connected to PC it shows ActiveSunc connected icon but 'PC says no' - Little Britain Syndrme. What do you think I should do? I can't revert back to the original ROM as I can't find it anywhere.. can't reinstall the current one as of version message.. in fact can't install any other ROM as I can't get ActiveSync going. Argh! Help! As highly as I think of HTC, this is really screwed up!!
Thanks for sharing your thoughts
Martin

I'm not an expert , but def sounds like a wrong hardspl to me. I've had this happen to me twice because of my inexperience the first time and my carelessness the second. Can you redo the hspl somehow and try another maybe xda cooked rom? Or have you already tried to go back to the rom you flashed from? Thats what saved me before. Go to duttys site. He has a bunch of htc roms for D/L. Maybe you can find your old one there.

cbreze said:
I'm not an expert , but def sounds like a wrong hardspl to me. I've had this happen to me twice because of my inexperience the first time and my carelessness the second. Can you redo the hspl somehow and try another maybe xda cooked rom? Or have you already tried to go back to the rom you flashed from? Thats what saved me before. Go to duttys site. He has a bunch of htc roms for D/L. Maybe you can find your old one there.
Click to expand...
Click to collapse
Thanks for for your thought cbreze. I'm annoyed as everything went by the book and the upgrade went fine until reboot. All I can do is to hard reset the phone at the moment. Can't get an ActiveSync connection going. Any way I can still flash to another ROM without it? Been to dutty's before and there's the same official version that causes me the problem and the Orange UK ROM.. not quite what I had in mind on o2. Can't find the 1.14 ROM which shiped with the device. Any idea where I can get hold of it? Also, I think I have seen a utility somewhere that helps to recover from a bad flash and in the absence of ActiveSync connection. Or was this just a pleasant dream?

Just have seen cRaCKwHoRe post at http://forum.xda-developers.com/showthread.php?t=505377 which exactly describes my issue. Will follow that trough but please let me know if you have any additional thoughts. I'm really p***** off with HTC. They could post cRaCKwHoRe's info this on their site. First time I ever got an official ROM and the last as I'm a burnt child. Usually get them from here and it's always first class stuff. Thank you people.

cRaCKwHoRe's instructions did the trick. Panic over. Thank you to everyone whom had a look at the issue and great thanks and deep bow to life saving cRaCKwHoRe. Donation is on the way as soon as I get paid.

Frequent Hanging of Acer Neotouch S200

Hi Lads, I'm a S200 user in singapore. Had just bought my phone 5 day ago and it's making me like smashing the phone. I had frequent screen hang and I needed to restart it about 7-8 time a day!!!
Does anyone has any solution to solve the frequent hanging of the device?
Appreciated !!!
Cheers

You have added programs yet?
Rom version?

Did not installed any program. Rom is stated NAND?

To find the rom version go start/settings/system information/software
should be something like
Language: EN
Major version: 2
Minor version:003
this site has the OEM rom's, maybe try a later version if yours is not already running a 3.003c version
ftp://ftp.acer-euro.com/smartphone/s200/os_images/

mine stated, Language EN_02, Major 2, Minor 003.
Is this right?

Peanut8787 said:
mine stated, Language EN_02, Major 2, Minor 003.
Is this right?
Click to expand...
Click to collapse
yes thats right. as someone said b4 try updating ur rom.
for me the 3.003c version sux. fm radio doesnt work and phone hangs alot. so i went back to 3.003b version.
maybe u can try....

How to update the rom? I saw alot of posting regarding updating rom but how am i gonna do that?
Cheers

How to update the rom? I saw alot of posting regarding updating rom but how am i gonna do that?
I'm total sux at using smart phone.
Cheers

Anw my FM radio works but i couldn't minimise it and whenever i did it would shut off the radio. The hanging part is when the phone is in lock mode and when i'm trying to unlock it it would just hang there. Really sux.
And i saw some thread that the earpiece is best to use the original as it has 2 strap instead of the normal 3 and the normal earpiece can spoil the phone headset connector. Is this true?

Peanut8787 said:
How to update the rom? I saw alot of posting regarding updating rom but how am i gonna do that?
Cheers
Click to expand...
Click to collapse
download the rom first from the link given above. instructions in the pdf file in the download.
Peanut8787 said:
And i saw some thread that the earpiece is best to use the original as it has 2 strap instead of the normal 3 and the normal earpiece can spoil the phone headset connector. Is this true?
Click to expand...
Click to collapse
dont noe about the earpiece thing. ive always used my own. the connector got abit problem as in hv to plug in deep deep then can be used. but not a big problem.

[Q] "Mobile of the year '09" bull****

I just got my HD2 back from repairs after 1 month now, I had the problem where the phone freezes up when I recieve calls. This got fixed, and I have not noticed any of the symtoms I had earlier. But now...
1. The FM-Radio does not work.
2. When I connect my phone to my computer, my computer sais: "One of the usb devices attached to this computer has malfunctioned, and windows does not recognize it. for assistance in solving this problem, click this message." And just connect - disconnect - connect - disconnect.
3. When I turn on my cellphone, I get a warning: BTTrayCE er ikke et gyldig Pocket Pc-program. (BTTrayCE is not a valid Pocket PC-program in English)
It just kills me that the phone that actually won the "Mobile of the year '09" by Amobil.no, sucks more than the Iphone.
Should I just send my phone back to repairs again, or do you guys have any idea how to fix this without using another month in repairs?
OS: 5.2.21869 (21869.5.0.82)
ROM: 1.66.409.1 (76641) NOR
Manila: 2.5.19211619.0
ROM-date: 01/12/2010
Radio: 2.07.51.22_2

First off, I'm sorry to see that your phone is having these issues. Mine has worked like a charm ever since I installed the first custom ROM.
Now my question; have you HSPL'ed your phone yet?
You could try installing another (custom) ROM and a newer radio version to see if it helps.. It might aswell fix your problems.

BLAST3RR said:
Now my question; have you HSPL'ed your phone yet?
You could try installing another (custom) ROM and a newer radio version to see if it helps.. It might aswell fix your problems.
Click to expand...
Click to collapse
I did use HSPL before I sent my phone to repairs, but it did not fix any problems, therefore I do not believe in HSPL'ing anymore.. I did not notice any difference at all, after installing a custom rom, or radio..

I see.. Have you tried Task29 yet? (Formatting it completely)
And then installing the latest Radio + a custom rom? (Before trying this, be SURE you have HSPL'ed it!)
If you've already tried that, I think the only thing you'd be able to do is to get a huge stone (or your HD2 itself), put a note on it saying 'It still does not work properly', and throwing it through the window of any HTC office in your country .
Or just open a ticket/calling them saying it still doesn't work and that you demand a replacement/new phone, as how it is now it's kinda an expensive brick.

BLAST3RR said:
I see.. Have you tried Task29 yet? (Formatting it completely)
And then installing the latest Radio + a custom rom? (Before trying this, be SURE you have HSPL'ed it!)
Click to expand...
Click to collapse
I just don't dare to do this, I have hacked TomTom, but this seems too dangerous, I'm still a noob in cellphone programming and stuff...
BLAST3RR said:
Or just open a ticket/calling them saying it still doesn't work and that you demand a replacement/new phone, as how it is now it's kinda an expensive brick.
Click to expand...
Click to collapse
Do HTC even bother about their customers? Doesn't seem so, seeing that if the cellphone should have any problems of this sort, they say you will get a new phone. But rather getting a new phone, I got the old one back, in worse condition than before.
Also, I wonder if they can check my problems? Because we have a law in Norway, if the same problem occours after 3 times repaired, you can either get a new phone or money back (same with all other electronics). So could I just lie and say I have the same problem + the new problems? **** the ethics ..

Jnygaard said:
I just don't dare to do this, I have hacked TomTom, but this seems too dangerous, I'm still a noob in cellphone programming and stuff...
Click to expand...
Click to collapse
Task29 isn't that risky.. Just run HSPL again and get that done, then run the packed exe as found in this thread: http://forum.xda-developers.com/showthread.php?t=644781. As long as you press the VolDown button when it restarts, you will be totally fine. However in your case, I'd indeed not expect much improvement, as it really seems to be a hardware problem.
Jnygaard said:
Do HTC even bother about their customers? Doesn't seem so, seeing that if the cellphone should have any problems of this sort, they say you will get a new phone. But rather getting a new phone, I got the old one back, in worse condition than before.
Also, I wonder if they can check my problems? Because we have a law in Norway, if the same problem occours after 3 times repaired, you can either get a new phone or money back (same with all other electronics). So could I just lie and say I have the same problem + the new problems? **** the ethics ..
Click to expand...
Click to collapse
I think it is all the same with those big corporations. One customer, who cares? As long as their phones sell, why would they bother? Same story all over again.
I'd go for the three strikes = new phone way. However, it does suck to have your phone taken away from you for another month or so..

sorry mate..mine works like a charm since day one must be just u it still is the best phone
lmao it has some disadvantages (like tft screen,no tv out/hdmi out/crap loudspeaker) but lmao its still better than most phones out there

Load the latest HTC stock ROM from their website, looks like yours is quite old.

xaccers said:
Load the latest HTC stock ROM from their website, looks like yours is quite old.
Click to expand...
Click to collapse
Guess what, it is the lastest stock, I just checked it.. Norwegian atleast, and I don't bother using other languages (even English). Just posted a ticket on HTC.com/no, and then I will send it to repairs again, and again, and then I'm changing to a Samsung Galaxy S..

I've heard Samsung support is even worse than HTC..
But indeed, the Galaxy S does have features that our phone lacks.. Still, I think the HD2 looks more sexy.

BLAST3RR said:
I've heard Samsung support is even worse than HTC..
But indeed, the Galaxy S does have features that our phone lacks.. Still, I think the HD2 looks more sexy.
Click to expand...
Click to collapse
The HD2 looks way better, I do agree. But my brother bought himself a samsung galaxy s, and he's going to start making games and apps, so he could teach me a little bit, and if I have problems, I could go to him rather than sending it to repairs, (not all problems are easily solved on the intarwebz) and then I'd get rid of Windows Mobile..

Sorry to hear that you have such hard issues with your HD2.
3. When I turn on my cellphone, I get a warning: BTTrayCE er ikke et gyldig Pocket Pc-program. (BTTrayCE is not a valid Pocket PC-program in English)
Click to expand...
Click to collapse
I had the same issue too. TomTom replaces two BT files (Your bluetooth should not work by now) so the BT application can not start up properly. THIS fixes at least this problem (Use Resco Explorer or TotalCommander and unhide system files).
I hope you'll find help for your other issues, too.

darkkoushirou said:
Sorry to hear that you have such hard issues with your HD2.
I had the same issue too. TomTom replaces two BT files (Your bluetooth should not work by now) so the BT application can not start up properly. THIS fixes at least this problem (Use Resco Explorer or TotalCommander and unhide system files).
I hope you'll find help for your other issues, too.
Click to expand...
Click to collapse
I see, tho, will this problem only appear if you have hacked TomTom? Or with the real TomTom aswell? Just want to make sure before I send it back to HTC

Jnygaard said:
I see, tho, will this problem only appear if you have hacked TomTom? Or with the real TomTom aswell? Just want to make sure before I send it back to HTC
Click to expand...
Click to collapse
How did you hack TomTom? Is that so you get free turn-by-turn navigation?

geon106 said:
How did you hack TomTom? Is that so you get free turn-by-turn navigation?
Click to expand...
Click to collapse
Well, instead of buying a licence, you hack it, using a keygen of some sort :S Didn't quite get what I did, but I used CMD to open a keygen and create a file :S Was weird, but hey, I did it... After 2 hours of trying

Easy when you know how, but im sure its not something that should be discussed on the forums. (WTB TomTom for sale from the australian site, as i feel its worth the cash)
anyway, darkkoushirou is correct regarding TomTom + Bluetooth.
I found it easier to install it to the SD card then factory reset. Once thats done i used total commander to simply copy a link back into your start menu.
Now that my custom ROM has XDA_UC i have set it to auto-copy the link back to my start menu after each rom upgrade
I know that when i got the handset i was trying many different apps, some of which caused issues. Once you get an idea of the ones you need, doing a factory reset is recommended. Then only install the 'good' ones.

[Q] Nand Android accelerometer/g-sensor DOES NOT WORK?

Hello!,
After trying a numerous NAND roms for my HD2, on every of them the accelerometer is not working. But flashing back to winmo everything is OK and accelerometer works.
Problems having : No screen rotation, no games work which need accelerometer, no bubble meters and so on.
I saw lots of threads here, but none of them were answered. Also some fixes out there from january, but its is said that new kernels include that fix.. Being really desperate about the accelerometer to start working tryed everything , all those fixes - none of them worked.
I really would appreciate if somebody would say a 100% answer if they had same problem and is it for EVERYONE that you are chilling around without accelerometer with NAND roms?
Or, a nicely explained , or some new fixes around there, to fix that..?
I have European HD2, Bought in Estonia. 2.15 radio, and RAFDroid build atm 4.02
Before teyed all cyagenmod build from MDJ, imilka builds, Coredroid, etc.
Waiting for a adequate anwer!, and Thank you in advance!
Daniil.

No pb for me with each Nand i tested. (prj Clean Desire, typhoon, Hyperdroid)

i had this to on my sd build i used to have but when i went to NAND everything was fixed
maybe you can try to recalibrate it in android?

Auralol said:
Hello!,
After trying a numerous NAND roms for my HD2, on every of them the accelerometer is not working. But flashing back to winmo everything is OK and accelerometer works.
Problems having : No screen rotation, no games work which need accelerometer, no bubble meters and so on.
I saw lots of threads here, but none of them were answered. Also some fixes out there from january, but its is said that new kernels include that fix.. Being really desperate about the accelerometer to start working tryed everything , all those fixes - none of them worked.
I really would appreciate if somebody would say a 100% answer if they had same problem and is it for EVERYONE that you are chilling around without accelerometer with NAND roms?
Or, a nicely explained , or some new fixes around there, to fix that..?
I have European HD2, Bought in Estonia. 2.15 radio, and RAFDroid build atm 4.02
Before teyed all cyagenmod build from MDJ, imilka builds, Coredroid, etc.
Waiting for a adequate anwer!, and Thank you in advance!
Daniil.
Click to expand...
Click to collapse
Usually d G-Sensor/Accelerometer has been pre-calibrated while cooking d android build...I've never had such a problem on SD, NAND or RAM builds....Perform a Task 29 on ur device and try flashing the build contained in my signature....CMY's work has always been great...

Done task29, done recalibration in android, everything... same. There is numerous people having the same prob , as i have seen from questions subforum.

Auralol said:
Done task29, done recalibration in android, everything... same. There is numerous people having the same prob , as i have seen from questions subforum.
Click to expand...
Click to collapse
Hmmm...Since it works on WinMo, try recalibrating it there and then run an android sd build (i just tried "Desire_DL" series and all was ok....on d other hand, have u tried d NAND build in my sig?

I have tryed everything, including your builds in the signature.... Nothing helps
Help!

Try the post that is in my sig, there is alot of info in there that might be of use to you. What definitely controls the G-Sensor is the bma150_usr file. If nothing in my post helps you at all, then I am unable to help you further since I dont have a Eu HD2. But I still believe that there might have been a revision which might explain your troubles as well as some other people.

Tryed that also, no help at all.

Auralol said:
Tryed that also, no help at all.
Click to expand...
Click to collapse
Hmm, dats quite a dilemma....I tk it u can't return n request for another device seeing as u got it 4rom Estonia...or can u?

Android is not supposed to run on HD2 anyways, so why should i have an opportunity to return my device for another one?

Auralol said:
Android is not supposed to run on HD2 anyways, so why should i have an opportunity to return my device for another one?
Click to expand...
Click to collapse
True it wasn't but IT IS...I and several others are proof it works beautifully on the HD2, even better than some native android devices...I offered a suggestion n its ur call 2 tk it or leave it...I on d other hand, love my current android build on my HD2.
Have u tried this workaround?
P.S. Oh yeah, and my accelerometer/g-sensor works perfectly in apps n games.

I mean, yeah it is working, but... not working for my device. And the point was that i can't take it to my local shop for a return, as the g-sensor works for the WinMo, and they will say that its your fault that it isn't working in android. Yeah i know that accelerometer works on androids on the Tmobile HD2-s
And yeah, i have tryed

Different type of g-sensor
I understand that some newer builds of the HD2 have a different type of g-sensor. I have x4 HD2's. 3 are working perfectly with HyperDroid CM7 cheerful cheetah. The forth is used by my company co-director which I recently tried to move over to the HyperDroid CM7 cheerful cheetah from WM6.5. This is when I came across the problem. Very annoying. The fact is that this device went back to HTC to repair/replace a cracked screen (I dropped the device last June). I suspect they gave me a reconditioned or replacement unit with the "updated" sensor.
Please advise me if there are any new developments. I can confirm that the HD2 (with the working g-sensor) has incredible battery life and is only my no.2 device because of the 8mp camera on the DesireHD.
Regards,
Jay

[email protected] said:
I understand that some newer builds of the HD2 have a different type of g-sensor. I have x4 HD2's. 3 are working perfectly with HyperDroid CM7 cheerful cheetah. The forth is used by my company co-director which I recently tried to move over to the HyperDroid CM7 cheerful cheetah from WM6.5. This is when I came across the problem. Very annoying. The fact is that this device went back to HTC to repair/replace a cracked screen (I dropped the device last June). I suspect they gave me a reconditioned or replacement unit with the "updated" sensor.
Please advise me if there are any new developments. I can confirm that the HD2 (with the working g-sensor) has incredible battery life and is only my no.2 device because of the 8mp camera on the DesireHD.
Regards,
Jay
Click to expand...
Click to collapse
Hi Jay, I've got a similar problem.
Actually, I've got (or had) an EU model, and my screen cracked, so it has been out for repair. So both descriptions in this post (yours and Auralol's) fit my problem. I have been looking for a fix for a while now, did you find anything?
I would love it to work, it really is the only thing that doesn't. If this is fixed, my HD2 would be perfect and irreplaceable.
If you find anything that helps, keep me posted?
Kind regards,
Bas

Hey Bas,
I contacted vfuk & simply said that there was a problem with the g-sensor on my HD2... The helpful telephone attendant asked me to remove the battery, memory and sim cards and a replacement device would be with me the next day. The following day the courier took the troubled HD2 and handed me a new Desire HD albeit without the antenna and battery covers. I have a spare battery and ordered the covers from expansys.
I did explain to vfuk what happened - they said I wasn't to worry.
At the time of writing I now have x4 dhd's and a working HD2 with HyperDroid which I am going to give to a pal to lure him away from Nokia...
I now have no way of helping you further. Sorry bout that.
Best,
Jay

[email protected] said:
Hey Bas,
I contacted vfuk & simply said that there was a problem with the g-sensor on my HD2... The helpful telephone attendant asked me to remove the battery, memory and sim cards and a replacement device would be with me the next day. The following day the courier took the troubled HD2 and handed me a new Desire HD albeit without the antenna and battery covers. I have a spare battery and ordered the covers from expansys.
I did explain to vfuk what happened - they said I wasn't to worry.
At the time of writing I now have x4 dhd's and a working HD2 with HyperDroid which I am going to give to a pal to lure him away from Nokia...
I now have no way of helping you further. Sorry bout that.
Best,
Jay
Click to expand...
Click to collapse
Heyy Jay,
Thanks for the reply. So, you kind of worked around the issue Sounds like great customer service. Too bad my provider does not work like that.
Just being curious if you had the same problem as I am facing now, did you try to retrieve / read data from the sensor (i.e. with "sensor debug")? I tried yesterday, didn't get any data at all. Probably means Android doesn't see the sensor, or it is indeed a different sensor and therefore needs other drivers.
I just downloaded some e-books about android and java, just to see how it works with hardware. Maybe it is possible to implement my 'own' drivers in a ROM to make sure the sensor can be detected at least. I guess it is going to be my pet project to find a solution, and when I do, I'll probably try to get it posted on xda. But then again, my programming skills are minimal at this point (just some Basic, html and Step 7), so it might take me a while...
Anyway, thanks for the reply. Too bad your solution does not work for me (I would not mind that either).
Kind regards,
Bas

Bas2ct said:
Heyy Jay,
Thanks for the reply. So, you kind of worked around the issue Sounds like great customer service. Too bad my provider does not work like that.
Just being curious if you had the same problem as I am facing now, did you try to retrieve / read data from the sensor (i.e. with "sensor debug")? I tried yesterday, didn't get any data at all. Probably means Android doesn't see the sensor, or it is indeed a different sensor and therefore needs other drivers.
I just downloaded some e-books about android and java, just to see how it works with hardware. Maybe it is possible to implement my 'own' drivers in a ROM to make sure the sensor can be detected at least. I guess it is going to be my pet project to find a solution, and when I do, I'll probably try to get it posted on xda. But then again, my programming skills are minimal at this point (just some Basic, html and Step 7), so it might take me a while...
Anyway, thanks for the reply. Too bad your solution does not work for me (I would not mind that either).
Kind regards,
Bas
Click to expand...
Click to collapse
Hi,
I'm having the same issue as you and was wondering if you had made any progress or if there is anything I could help you with although my programming knowledge is probably more limited than yours. Anyway this issue seriously needs to be looked at! :'(

Still no fix?
Hello, I know it is old thread, but I see there are more people than only me having this issue. Same thing happens to me. Accelerometer isnt working on Android, but it works great on WinMo. I tried a lot of ROMs, "fixes", but nothing helped at all. I used apps like Sensor debug, and sensor list, seems that they dont see my g sensor at all, like someone said before. As I know, g sensor is connected with bma150_usr file, but I used my Root Explorer to search for that file and there is no such a file at all. Shouldnt it come to my device with other ROM files? Yes, I tried to put it where it should be, but the same s**t again... Is there anyone who solved this thing? Because I dont see any solutions mentioned in the whole xda forum.
Looking forward for answers which REALLY helps.

Hi,
I have this same problem, My g-sensor didin't work on AMeriCan Android.
I was reading a topic http://forum.xda-developers.com/showthread.php?t=902129, and my question for this: How I can delete files
Before installing the file above, go to System/Bin and delete the bma150_usr, then navigate to Data/Misc, and delete the following files:
AK8973Prms.txt
AK8973.Prms.txt.tmp (If there)
bma150_usr.txt (If there)
After navigate to the above file and add it to System/BIN and then your calibrating will function correctly and adjust the values properly.
Click to expand...
Click to collapse