HD2 crash after/at phone call - HD2 Android Q&A, Help & Troubleshooting and Genera

Hi everbody,
i'm a newbie within the Android on HD issue. I have read many threads but i didn't find a solution about my problem.
First i have tried the 'AmeriCanAndroid AOSP HD2 GB2.3.5 CM7' SD-Version and i have the following problem.
If i get or take a phone call the display goes black and there are no reaction on key presses or so on. I think the android is crashed.
Only accu on/off will help
Did anyone have some i idea about the reason.
Best Regards
Superemo

SuperElmo said:
Hi everbody,
i'm a newbie within the Android on HD issue. I have read many threads but i didn't find a solution about my problem.
First i have tried the 'AmeriCanAndroid AOSP HD2 GB2.3.5 CM7' SD-Version and i have the following problem.
If i get or take a phone call the display goes black and there are no reaction on key presses or so on. I think the android is crashed.
Only accu on/off will help
Did anyone have some i idea about the reason.
Best Regards
Superemo
Click to expand...
Click to collapse
i suggest you post this question in the roms thread...it could be sd card related....
I havent run sd card roms since january when NAND came out....

Related

[Q] NAND Screen stays off after phone call

Hi All
Was using SD versions of Android in my HD2 which worked quite well .....decided to make the jump to NAND recently but I'm having a problem with phone calls.
When I make a call out, everything works fine, but when I hang up on the call, the hard buttons on the bottom of the phone all light up but the screen doesn't turn back on.... Only way to get the screen back on is to plug in the USB cable or power adapter or pull the battery and do a reboot!
Have tried a couple of different builds from different chefs and a couple of Radios just in case.
At the moment I've got the following on it:
Radio is 2.12.50.02_2
Android version is 2.2.1
Build is DL DesireZ v3.4 Final (but this problem also happens with CleanDROID V1.31)
Also tried an MTTY Task 29, reload of MAGLDR then re-flash of the NAND in case traces of my previous ROM were still around but that hasn't helped either.
Any ideas?
I seen many threads about same situation. Actually i itself use daily gpc hd2 gingerbread v1.5 with same problem. Sometime help back button (when call ended not at me). Sometime just more light to proximity (or it light) sensor (when inside and put phone with face to some light). Outside i just must turn phone with face to sun or good light then screen wakes up.
I tested many many nand roms. All have same problem.
Tested win 6.5, win 7 and sd version, they works well. That gives confirmation that my proximity (or it light) sensor works well. And finally that something wrong with nand.
Here was discussion that MAGLDR does that. NO.
I started run over net and find solution. Here seems no help for this right now. Maybe just problem ignored because cookers itself dont have this and cant do anything. If you dont have problem then how you can fix it.
On web i found some discussion about kernel problem or smth about this proximity sensor. I cant find it right now again. There was talking about this problem, but no solution.
I thinked about open new thread and invite kernel chiefs to discussion to solve this problem. But today i find your ask. I opened for any test and help that i can give. I dont be afraid to lose my phone if something must go wrong. Phone is just piece of electronic and you can replace parts. But knowledge and experience you cant buy.
Any ideas how to resolve this little bad thing?
Thanks for the reply.
Yes it's a real problem but mine won't wake up no matter how much light.
The only way I can get it to wake up is to plug it in to power, then the screen wakes up.
Is that the same as yours?
I i remember it right i was suprised once too if this happened. I just put my "again dead" phone to charging and its waked up.
If screen is dead and same time connected to pc (i use for managing inside phone androidcommander) then moving over dirs wake screen back too.
But lets look how long my nerves will be good. Today i thinked to move back win 6.5 and sell this bastard.
No don't sell we need to resolve! I'm hoping someone will look at this thread and help us figure out why this is happening. I can't believe we are the only 2 people who have this issue.
Anyone else have any ideas as to why this is happening?
This issue was also on sd versions. So I see nand has not fixxed it. I am running MDJ HD 4.6 and have this issue. Sometimes the light sensor works properly and other times it goes to black screen and gets stuck.
I read somewhere that it might be the hardware itself. Saw a video on youtube also. Seems the european T8585 and telstra T9193 might have poor light sensors. The T-mobile light sensor supposedly does not have this problem.
So I am guessing anyone with this problem does not have the T-mobile USA version??
It could just be drivers too. It is a pain and sometimes I wish I could just disable the light sensor.
Also NAND roms are no better than sd versions as far as bugs. If the sd version has the bugs then so will the NAND version. The build is just installed at a different location.
Yes good point.... the bug will be replicated as it's just where the OS is stored that's different.
I'm thinking it's the hardware as I have this problem on WinMo6.5 too and I have tried various WinMo roms but had the same problem.
Mine is a UK HD2 supplied by O2. Wish there was a fix for it :-( It's a real problem.
PS I ran PhireMOD's Skinny EVO SD Android for a while and didn't have as much as a problem as I have had with the 2 NAND roms I've tried..... if that's any clue? At least with that rom I was able to make calls and hang up and still get the screen back after I hung up (except for the screen going white and washed out which could only be resolved by a reboot). There was still the problem with the screen being on all the time during a call or the screen being black and not coming back on during a call though.
I have these sort of problems too. It's really annoying when you're in a phonecall and you take the phone away from your ear and it takes a few secs to turn on. Also when I'm unlocking it.
Sent from my HTC HD2 using XDA App
At least yours comes back on lol mine stays off for ages and ages and sometimes doesn't come back on at all!
Noticed that if I shine a torch into the proximity sensor that's the only way I can get the thing to turn back on :-( Also noticed the 2 little holes where the prox sensor sits appear dirty/cloudy... not sure how that happened.
I wonder if the prox sensor is busted or if it's just dirty or something? Going to get a T5 Torx and take my phone apart to find out if it's something I can resolve.
Well i had this with rafpignas kernel...i changed to markinuX today and tested it with over 10 calls and it works flawlessly right now
Hmm, are you sure g9650? Seems my guess about kernel was then true. I use gpc pure gingerbread 1.6 with gpc itself made kernel. I go right now replace kernel and test. Results tomorrow.
Took the phone apart yesterday night and uncovered the proximity sensor. Even out of the case it needs a torch/flashlight to shine on it to bring the screen back on :-( I honestly think the proximity sensor hardware isn't working anymore.
I'll try the kernal you suggested though just in case that's what's causing the problem.
Datas0ft let me know if it works for you?
Latz, actually i taked to test markinus extra clean 1.7.1 (right now on it itype this). Had one call before and no changes.
Also i stuck on taking out kernel at this version. Low knowledge. Dont find any help yet on xda. I work on it. If you have hints dont hestitate say.
Sent from my HTC HD2 using XDA App
:-( I was hoping we found a miracle cure! Ok let me flash mine tonight and try it to see if mine behaves any different. Will post back with results... let me know fi anything changes with your phone datas0ft.
q9650 said:
Well i had this with rafpignas kernel...i changed to markinuX today and tested it with over 10 calls and it works flawlessly right now
Click to expand...
Click to collapse
Can anyone upload MarkinuX Kernel please? Thanks
Ok. Searched forum. Finded way how to get kernel at some nand. Got MarkinuX kernel and now test. Test will be during whole day tomorrow on different conditions.
For kernel extract and install is this thread very good. Helped and teached me.
marcosxd i taked needed files for you and attached.
datas0ft said:
Ok. Searched forum. Finded way how to get kernel at some nand. Got MarkinuX kernel and now test. Test will be during whole day tomorrow on different conditions.
For kernel extract and install is this thread very good. Helped and teached me.
marcosxd i taked needed files for you and attached.
Click to expand...
Click to collapse
Thanks, I just finished downloading the whole Markinus rom to extract kernel haha but you saved me... will test and report, thanks
datas0ft said:
Ok. Searched forum. Finded way how to get kernel at some nand. Got MarkinuX kernel and now test. Test will be during whole day tomorrow on different conditions.
For kernel extract and install is this thread very good. Helped and teached me.
marcosxd i taked needed files for you and attached.
Click to expand...
Click to collapse
Quick question, the zip file you gave me only has two .ko files and zImage while the original rafdroid kernel has like 5 .ko files... what should I do? copy raf's kernel .ko files missing into markinux ones?
Or just pack the zip file using two .ko files? Thanks
I cant ansver. Dont have much knowledge on this. I followed instructions. This taked to me these three files. I installed these.
I finded some problems right now (wifi and gps dont work and my 3g too). This may not happen at kernel side. I have made some changes on rom side. I go replace whole rom and then again kernel. Then i go make final decisions.
I'm having the same problems, you two are not the only ones. This has been really frustrating me lately, and I thought it might have been a problem for only me because I just had the screen replaced. It worked fine in winmo 6.5, now in NAND I'm having some issues. I text a lot more than I actually call, however so it's not that big of a problem for me right now

[Q] new to HD2..touch screen problems!

i have an HD2 with a cracked screen i bought on craigslist. the unlock screen will stop working sometimes, and when i pull the battery and reboot, the home screen sometimes doesn't work. i've heard of these problems before but i'm not sure if this is a software or hardware problem. the previous owner had the phone running on AxLor DF1 XLite WWE. please help!
also i'd like to know how to flash to stock through micro sd, since i don't have a usb cable.
Thanks.
isoDUB said:
i have an HD2 with a cracked screen i bought on craigslist. the unlock screen will stop working sometimes, and when i pull the battery and reboot, the home screen sometimes doesn't work. i've heard of these problems before but i'm not sure if this is a software or hardware problem. the previous owner had the phone running on AxLor DF1 XLite WWE. please help!
also i'd like to know how to flash to stock through micro sd, since i don't have a usb cable.
Thanks.
Click to expand...
Click to collapse
Go to this thread here, this is a thread on flashing from SD card. It has all the info you will need.
Also you can buy a replacement screen and install it. There is a couple of threads here on XDA on how to do this just do a search for them.
T-Macgnolia said:
Go to this thread here, this is a thread on flashing from SD card. It has all the info you will need.
Also you can buy a replacement screen and install it. There is a couple of threads here on XDA on how to do this just do a search for them.
Click to expand...
Click to collapse
thanks, got on the stock T-Mobile rom now, but the touch screen on the lockscreen only sometimes works. would flashing to android fix this? i notice it will unlock sometimes after i press power then give it a few minutes, so i'm not sure if this is hardware or software related, and i'd like to avoid replacing the screen if i can.
EDIT: weird, i read a thread that said i should use the call button to unlock, and after a battery pull and waiting a few minutes, its worked for a bit, so i guess i found a temperary fix....
so now, i was wondering if its possible to boot android from the nand, and boot windows mobile 6.5, wp7, ubuntu, and meego from the sd, or can win mobile 6.5 only be booted from the nand? also, i need spl/hspl to boot all these things right?
isoDUB said:
so now, i was wondering if its possible to boot android from the nand, and boot windows mobile 6.5, wp7, ubuntu, and meego from the sd, or can win mobile 6.5 only be booted from the nand? also, i need spl/hspl to boot all these things right?
Click to expand...
Click to collapse
You can't have them all. You can have WP7 running from NAND and Android running through SD. Not too sure on the rest though.
Sent from my Nexus One using XDA App
isoDUB said:
thanks, got on the stock T-Mobile rom now, but the touch screen on the lockscreen only sometimes works. would flashing to android fix this? i notice it will unlock sometimes after i press power then give it a few minutes, so i'm not sure if this is hardware or software related, and i'd like to avoid replacing the screen if i can.
EDIT: weird, i read a thread that said i should use the call button to unlock, and after a battery pull and waiting a few minutes, its worked for a bit, so i guess i found a temperary fix....
so now, i was wondering if its possible to boot android from the nand, and boot windows mobile 6.5, wp7, ubuntu, and meego from the sd, or can win mobile 6.5 only be booted from the nand? also, i need spl/hspl to boot all these things right?
Click to expand...
Click to collapse
I know it would be a pain in the butt and in the wallet too. But it would probably benifit you to replace your screen. But this is a dessision that you will have to make for yourself.
Glad you found a teperary fix!
Yes you will need HSPL and also MAGLD flashed to your HD2 in that order to flash a NAND Andriod ROM. I beleive you can flash HSPL from your SD card, I think the thread I linked covers this. Buy I din't think you can flash MAGLD from your SD card. So you will have to have a USB cable for this. You can go to the HD2 Andriod NAND ROM section here on XDA and do a search for MAGLD and you will find the thread on it so you can double check and see if you can but I really don't think it is possibble. But you will have to have a USB cable to flash Andriod, WP7, MeeGo, and Ubuntu cause MAGDL does not have SD card flashing ability yet but they are working on it though. They are also working on being abale to run Windows Mobile 6.5 from SD card but as of right now it is not possibl, only from NAND right now. Also if you install a NAND Andriod ROM I think you can run WP7 from SD card but don't hold me to that cause I am not 100% sure of that, but if So that isit no other OS from SD card when running a NAND Andriod ROM.
T-Macgnolia said:
I know it would be a pain in the butt and in the wallet too. But it would probably benifit you to replace your screen. But this is a dessision that you will have to make for yourself.
Glad you found a teperary fix!
Yes you will need HSPL and also MAGLD flashed to your HD2 in that order to flash a NAND Andriod ROM. I beleive you can flash HSPL from your SD card, I think the thread I linked covers this. Buy I din't think you can flash MAGLD from your SD card. So you will have to have a USB cable for this. You can go to the HD2 Andriod NAND ROM section here on XDA and do a search for MAGLD and you will find the thread on it so you can double check and see if you can but I really don't think it is possibble. But you will have to have a USB cable to flash Andriod, WP7, MeeGo, and Ubuntu cause MAGDL does not have SD card flashing ability yet but they are working on it though. They are also working on being abale to run Windows Mobile 6.5 from SD card but as of right now it is not possibl, only from NAND right now. Also if you install a NAND Andriod ROM I think you can run WP7 from SD card but don't hold me to that cause I am not 100% sure of that, but if So that isit no other OS from SD card when running a NAND Andriod ROM.
Click to expand...
Click to collapse
thanks. for now i'll just work on installing android to the nand. i have a question though, will turning off the lockscreen in android possibly fix the touchscreen problem? i've been racking my brain trying to figure this out. i can either hurt my wallet with a screen repair, or i can do a battery pull every everytime i use the phone.. a real pain in the ass... sigh.. at least i got the phone cheap..
isoDUB said:
thanks. for now i'll just work on installing android to the nand. i have a question though, will turning off the lockscreen in android possibly fix the touchscreen problem? i've been racking my brain trying to figure this out. i can either hurt my wallet with a screen repair, or i can do a battery pull every everytime i use the phone.. a real pain in the ass... sigh.. at least i got the phone cheap..
Click to expand...
Click to collapse
You know I can not say for sure if turning off the screen lock would solve your problem. But it sure is worth a shot so I say go for it and see. Also you can use a app like Touch Tools or BsB Tweeks to cut the lock screen off in Windows Mobile. Just do a search here on XDA or do a Google search for them and you will find them I recomend the Touch Tools this is a really great app. It adds a lot of tweeking ability to your HD2. I love it and have been using it for atleast 5 to 6 months now. Anyway if turn off the lock screen with one off these apps and it fixes your issue. Then you will know if you turn off the lock screen in Andriod it should have the same result. Heck if it fixes it you might just keep Windows Mobile ha ha just joking. I would not blame anyone for flashing a NAND Andriod ROM and getting rid of Win Mo. I personaly like Win Mo.
You're best off investing in a USB cable too lol. Your local hardware shop will have them. Its just a basic USB to micro USB cable.
I dont think any amount of tinkering with any OS is going to resolve your touchscreen problem............
The screen is cracked right?? Theres your problem.........
Could be issues with the digitiser as well because of this.
First job, new screen...........
i've been messing with the phone last night, and it seems the problem is related to the end call button. it seems whenever i try to wake up the phone with that button, it will freeze, while using the green button will wake up with no problem most of the time (>20% chance of freeze). it seems the freezing doesn't happen after a certain amount of time, since i left the phone in sleep all night and woke it up in the morning no problem. so in case anyone has the same problem as me and is too cheap to fix it, try only using the end call button when actually calling/putting the phone to sleep.
and where could i get a micro usb cable cheap besides online? i think t-mobile has them but they're like $10+...
it's dead again!
help! (again). the touchscreen is dead after i HAD to use the power button today, and now i can't use the touchscreen at all! i've tried turning the screen on and off like 50 times, tried like 10 battery pulls, but nothing! please help! can i open my phone somehow to get to the end key hardware or something???
earlier today also happened to me this problem, I install several rom a day, I can not go a day without testing new rom, I thought the problem was that, because I found this topic, when I use the button to connect the phone, everything is well, but not always the case that with the off button. Was it any rom that did this damage in some piece of hardware?
Body said:
earlier today also happened to me this problem, I install several rom a day, I can not go a day without testing new rom, I thought the problem was that, because I found this topic, when I use the button to connect the phone, everything is well, but not always the case that with the off button. Was it any rom that did this damage in some piece of hardware?
Click to expand...
Click to collapse
isoDUB said:
help! (again). the touchscreen is dead after i HAD to use the power button today, and now i can't use the touchscreen at all! i've tried turning the screen on and off like 50 times, tried like 10 battery pulls, but nothing! please help! can i open my phone somehow to get to the end key hardware or something???
Click to expand...
Click to collapse
Sorry to tell both of you but your problems are hardware related. Member isoDUB yours is most definitly a hardware issue, but it has been a little bit sense you posted that post so I hope you have got your HD2 fixed or are working on getting it fixed. Member Body yours sounds hardware related to cause if you flash another ROM and you still have the problem with your buttons then it is most definitely a hardware issue.
Best option is to send to HTC and see if you can get a new one for free if you are under warranty.
same problem
hi
im not original english speaking so please excuse my bad english.
a few days ago i got the same problem. the display doesn't work when the phone was waked up with the endcall button.
when i woke up the phone with an other button the display worked.
i sended it to htc an they just told me they will not repair it because it is not in the original contition.
i flashed it with the latest original rom from htc but they didn't tell me what is wrong in detail.
i answerd them an asked what is wrong but until now i didn't get an answer.
Hello, I have a similar problem. When you unlock the screen so we jump on the green but some spots that disappear after a while.
Disaster strikes !!! Same prob here !!!
its indeed something with the buttons ... Touch screen is dead ... but sometimes its workin!!
Three months ago ... I changed the case of the HD2 with a new one. The "old"one was full of scratches ...
I think yhat HTC is not gonna accept that ... the "void-label" on the screw is damaged...
What do you think Guys ??
Grtz
every where the htc hd2 screen problem ........... i think that every one who has the htc hd2 facing the screen problem we shopuld start the new thread where we that who has the htc hd2 without any touch screen problem
Have the same damn problem ..once the screen is locked ..its impossible to slide it to unlock ..previously it was working 50% of the time and now it doesnt work at all :-(( ..
Any suggestions ? ...I read alot on the forums and people seem to say that its digitizer related but the imp thing is to note that almost 98-99% of the people having this problem are frequent Android rom flashers ..so does Android have something to do with this and will flashing original stock rom back be the solution ??

[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

[Q] WP7 bug.. Please help

Hi guys,
I have a issue with my phone but couldn't find a solution anywhere.
I have a 16gb Sandisk card, which I have been using for 2 months now, I have been testing many Roms and had no issue till last couple of days.
Previously I flashed WP7 on it's own, then dual boot with Android (different Radio), then Android only, did all this with no issues, after few weeks of being on Android the phone started going crazy, starting applications on its on, will not respond to touch and mainly pressing keys on the keyboard by it's self, especially when I press the delete button it would go crazy start typing random words.
Thinking it was a issue with Android, flashed a new radio and new wp7 rom, but still have the same issue, keyboard and menu doing random things, the standby screen shaking/vibrating like there's no tomorrow.
Some-one please help, I have flashed 3-4 different Rom's, still same issue.
Is my SD card damaged ? I did a full format and flashed rom again, didn't help.
Anyone ?? Can someone help ??
While this sound much more like a hardware problem than a software problem I've never experienced anything alike. Maybe swing by your retailer's store see if they can get you a replacement?
the wp7 rom can work without the sd (you wont have a lot of data space). you can try running removing the sd and see if the problem repeats.

[Q] Touch screen unresponsive...help

emergency...
after installing the american android latest build, my touch screen has become unresponsive. i can boot up fine and see the lock screes but my inputs are not being read. i dual boot wp7 and my worst nightmare came true because it al the same on wp7, which makes me thing it has to be a coincidental hardware issue.
could this be a software issue, even though it is happening on two different OS?
Is anyone familiar with this and what would be my best next step?
Is there anyway to get my text messages that would be coming in today while my phone is off? i dont even want to boot up since then i will receive these messages and not be able to read them, thus losing them.
help and thanks ,
jason
jason370 said:
emergency...
after installing the american android latest build, my touch screen has become unresponsive. i can boot up fine and see the lock screes but my inputs are not being read. i dual boot wp7 and my worst nightmare came true because it al the same on wp7, which makes me thing it has to be a coincidental hardware issue.
could this be a software issue, even though it is happening on two different OS?
Is anyone familiar with this and what would be my best next step?
Is there anyway to get my text messages that would be coming in today while my phone is off? i dont even want to boot up since then i will receive these messages and not be able to read them, thus losing them.
help and thanks ,
jason
Click to expand...
Click to collapse
Hi Jason,
I have the same issue with my HD2! I did all the tip I can find online but no luck .
I did try to change my Android ROM many of time. Installed W7 and still no good. Install HD2 Stock ROM still behave the same.
Still looking for a solution!!
I think it's tied to the end call button I lose touch every time I hit it in both android and winmo locking and unlocking repeatedly will temp fix as long as I don't use the end button a fix would be great

Categories

Resources