i see a few have encounter this problem but yet to find a solution.
Problem: Everytime i make a call or receive a call the screen goes black and only the buttons work but it still useless without any display on screen. I have already tried turning off the auto bright but still doesnt work.
This happen in every android i use but phone doesn't act up when i am using winmo.
I have the same problem, please help !!!!
yascorpion said:
I have the same problem, please help !!!!
Click to expand...
Click to collapse
well the answer is simple because the proximity sensor doesn't work properly
and you have to either change your build or i don't know figure something out
for me the proximity sensor works
and i am using nexus one build
Thank you,I will try your build
yascorpion said:
Thank you,I will try your build
Click to expand...
Click to collapse
Please share with us the result, because I have also tried several builds, and it does not work properly on any. Mostly with Desire HD builds which I'd like to use and it is frustrating. Thanks.
I tried more than 7 builds but it didn't work,I spent like 5 hours to fix it but nothing worked and it's really frustrating. cauz I can't know who call me sometimes and see how many minutes I spent. please share if you have any results.
thank you very much !!!!
yascorpion said:
I tried more than 7 builds but it didn't work,I spent like 5 hours to fix it but nothing worked and it's really frustrating. cauz I can't know who call me sometimes and see how many minutes I spent. please share if you have any results.
thank you very much !!!!
Click to expand...
Click to collapse
the issue is less sensitivity with the proximity sensor. Three reasons which I saw:
1) mechanical reason for less sensitive sensor could be screen protector which is covering left top side of the device. Remove protector from this area where you see two dots.
2) dust between sensor and screen. Blow some air between screen and plastic cover of the device. Perhaps with vacuum-cleaner.
3) this is not your problem apparently, but generally European type HD2 is less sensitive on light according the YouTube video I saw, comparing with TMOUSE device. On the other hand current kernels are the same for both devices. In this matter, put your device during call under the direct light and you will see.
Screeb lite +Android assistant +Brightness Auto off did the trick for me .
Try it ,it might work with your device ....
many of us having the same problem. i was using android nand rom for last two monts, everything was perfect. I did a screen replacement last week, and after that 'g sensor' is not working with android. not pnly g sensor, also proximity sensor and magneto sensor. but the thing is, every sensor is working with winmo 6.5, even with wp7.
i have tried several build, changed hspl...nothing worked. many of us are having the same problem.
all you brilliant people, someone help us man.
This seems to be a general problem After a screen replacement the G-Sensor in Android stops working.
Can anyone can tell us how we can fix this, i.e. what info can we supply to the ROM chefs and kernel gods to help them get to the bottom of this?
It appears that there is a general issue with the G-Sensor after a screen replacement has been done. There are tons of users in the Android Q&A forum with the issue. The sensor works fine in winmo but not in ANY android rom after the screen has been replaced. I'm guessing its a hardware driver issue?
Please could someone tell us what info/data we can give to the ROM chefs and kernel gods so that they can take a look and fix this.
boflynn said:
It appears that there is a general issue with the G-Sensor after a screen replacement has been done. There are tons of users in the Android Q&A forum with the issue. The sensor works fine in winmo but not in ANY android rom after the screen has been replaced. I'm guessing its a hardware driver issue?
Please could someone tell us what info/data we can give to the ROM chefs and kernel gods so that they can take a look and fix this.
Click to expand...
Click to collapse
Dont know if this helps...but I had my Hd2 screen replaced few months back...and dont have this problem... screen is much better than before though with beter colour saturation....check with HTC as this might be an error on their part..
Sent from my HTC HD2 using XDA App
G-Sensor Not Working after Screen Replacement
boflynn said:
It appears that there is a general issue with the G-Sensor after a screen replacement has been done. There are tons of users in the Android Q&A forum with the issue. The sensor works fine in winmo but not in ANY android rom after the screen has been replaced. I'm guessing its a hardware driver issue?
Please could someone tell us what info/data we can give to the ROM chefs and kernel gods so that they can take a look and fix this.
Click to expand...
Click to collapse
I have this same problem with one of my HD2's that had the screen replaced.. Everything works perfectly except the "G-Sensor"...
I posted the problem in this thread http://forum.xda-developers.com/showthread.php?t=902129 a while ago, and been watching ever since... Havent seen any solutions, but more reports of the same problem been added to it daily... I'm also assuming that they changed the G-Sensor hardware along with the screen... Beacause it works perfectly in WinMo, and it dont in none of the Android Builds I've tried (CMYLXGOs all versions, Imilka's all versions, RAFDROID, CyanogenMod, etc)...
Everything works good on my Primary HD2, no problems at all... I'm hoping some Chef/Kernel developer might just take some time to check this out...
Have you guys went into Settings>Display>and ticked the check box for Auto-rotate screen?
T-Macgnolia said:
Have you guys went into Settings>Display>and ticked the check box for Auto-rotate screen?
Click to expand...
Click to collapse
That option is checked by default.. Even if You uncheck and check it, it still dont work... If You go into G-Sensor Calibration, the bubbles dont move at all... All those solution was posted in the thread, in the link above...
I'm really assuming is some hardware/driver problem... It worked fine with android, but after they replace the screen, it stopped working...
cmcmyers said:
That option is checked by default.. Even if You uncheck and check it, it still dont work... If You go into G-Sensor Calibration, the bubbles dont move at all... All those solution was posted in the thread, in the link above...
I'm really assuming is some hardware/driver problem... It worked fine with android, but after they replace the screen, it stopped working...
Click to expand...
Click to collapse
Sorry I did not click on the link and rad the other thread. If you go to calibriate your G-Sensor and it does not move then it sounds like either your internal G-Sensor hardware is faulty or not properly connected. I would make the tech you had work on your HD2 work on it again or take it to another repair shop.
T-Macgnolia said:
Sorry I did not click on the link and rad the other thread. If you go to calibriate your G-Sensor and it does not move then it sounds like either your internal G-Sensor hardware is faulty or not properly connected. I would make the tech you had work on your HD2 work on it again or take it to another repair shop.
Click to expand...
Click to collapse
It's a good point You have there... But I would be assuming that was the problem if the G-Sensor wasnt working in Windows Mobile... Everything works perfectly in WinMo, including the calibration... Thats another reason we have come to believe its a hardware upgrade or something similar...
I have the same problem. I bought an HD2 from someone in the Marketplace, and I can see from the pry marks on the bezel and the broken adhesive that the screen had been replaced at one point. I also believe there must have been some hardware revision that is still compatible with WinMo, as the same driver works unilaterally, but not with Android. Definitely tried most of the recent ROMs and different combinations of kernels, and cLK/MAGLDR, but it never works.
Charnsingh alludes to the G-Sensor code in the kernel in his [DEV] thread here: http://forum.xda-developers.com/showthread.php?t=1049170 (don't post unless you're a dev though), and says that it's pretty minimalistic. So maybe there's a solution out there, but the developers haven't gotten to the bottom of it. I'm watching that thread intently to see if there's anything cooking or if there's something I can help with.
I think there are quite a few users who are suffering from this.
If the devs need anything they have plenty of people to ask for debug info, etc.
I just wish someone had the time to have a look at this
have got the same issue, new screen, sensors stopped working, all the sensors that is, light, proximity, g-sensor, compass. and everything works in winmo (except the compass, don't know why) the interesting thing is, the proximity sensor does work, it just doesn't turn off the screen, but it does turn off the touch screen, and the g-sensor actually seems to work, i can calibrate, and the relevant files are updated (in /data/misc the bma150_usr and the akmd files are created and/or updated) and if i move during calibration, it is aborted. it seems as if there is something broken in software because the chip data is still being read and used somehow, just not piped to the right places...
Every sensor work fine here with except the g sensor
I guess its a kernel issue and not hardware relates
it work perfectly on wm6.5,but not work on any andriod rom.
i have the same issue
so no one is helping us???
i have the same issue too...
Same here works fine in windows but android will not work.
Also have screen replacement
SOLVED
my issue is solved now after motherboard replacement.
a few notes:
- as i eventually discovered, there was in fact a problem with the compass (aka the magnetic field sensor) which didn't work in any os. with this issue i had a good reason to send the phone back to the repair shop and they replaced the motherboard under warranty.
- i don't know what solved the issue, it's either [A] the working compass (which is somehow needed for auto-rotation to work - in android) or the new motherboard (which does not have compatibility issues with the new screen - in android).
so, please check wheather your compass is working or not.
if not, reflash to stock and send it back for a warranty repair.
I replaced the digitizer in my phone myself and the G-sensor works for me in Android.
LOOOOOOOOOOOOOOOOOOTS of threads and posts since 6 months and still nothing. About those sensors problems / screen replacements and still nothing... It's so sad, the HD2 is dying slowly. Lolz, let's keep the faith!!
+1 same problem...
Any solution???
Thx.
Same.
perfect on Windows.
not working, gyroscope, compass, screen rotation on any android.
no problem with proximity and light sensors.
I had tried screen rotations witout main flex (that holdss, vibration, camera, volume, wifi, buzzer)
And the sad point is I had replaced LCD-Digitizer together these are taken from a dead hd2. So my replaced LCD is 100% orijinal. I did not seperate chasis-button flex also.
The compass does Not work correctly on 2 i9505 black...
Any people more?
Sorry for my bad english ...
oriolas said:
The compass does Not work correctly on 2 i9505 black...
Any people more?
Sorry for my bad english ...
Click to expand...
Click to collapse
test the sensor on *#0*#
I've solved it ... I have given two full turns to mobile and it seems that it is calibrated
Thankyou
oriolas said:
I've solved it ... I have given two full turns to mobile and it seems that it is calibrated
Thankyou
Click to expand...
Click to collapse
Hi
recently am facing issues with this s view.
I am not using a s view cover but still the phone shifts to s view suddenly. But only for a second or so and again comes back to normal.
this happens quite often for me when am just holding the phone. Or trying to make a call.this is annoying.
Is my s4 broke.. am worried.
please help me out to solve this
You have to move your phone in a figure 8 position in the air about three times to calibrate your compass for it to work properly.
The flip view cover contains a magnet which screws with the compass, rendering it useless. If you're using the cover remove it and see if it helps.
krico said:
You have to move your phone in a figure 8 position in the air about three times to calibrate your compass for it to work properly.
Click to expand...
Click to collapse
Was that answer for me.... please let me know... how to work this out and how does this work
No dude. It was for the person trying to calibrate their compass.
Calibrations doesn't help ...
I've got CM 5.1 + newest GAAPS and calibration of compass last only for few seconds-2/3 minutes tops and then it's gone and compass again showing wrong directions not even restarting Google Maps - (usually 180* degree opposite to the actual direction). Funny thing, when I downgraded to original Orange Kit Kat 4.4.2 compass worked precise so It assured me, that there is not problem with hardware only software. I cannot use: *#0*# because my I9505 says "Problem with the connection or wrong MMI code" (translating from polish).
All other things including GPS, accelerometer and other sensors works perfectly well.
Anybody know the solution?
Can anybody with Gionee e7 on this forum help me.
i need a simple test to be done on the handset
i am facing problem with the gyro sensor of my current device. (i need that for a app i am developing)
i tested the sensor using a app named Android Sensor box available on play store.(goo.gl/f81PZN)
you can check the video here ( youtube.com/watch?v=YvEkdOrarjo ) for the exact problem i am facing
you can see in the above video that the cube keeps on spinning even while the phone is stable.
It should be stable and only rotate as you move your phone.
Could some one please test this on their Gionee e7 and post the results here.
i want to be sure before purchasing the device that it is not having the same problem.
help will be much appreciated.
Let me know if any one needs any further help regarding carrying out the test
Regards
No problems here, the cube emulates the phone's movement and does not spin at all.
Cant seem to attach anything here. But I'm on stock 4.2.2 (Vietnam).
Let me know if you need more info.
stevefwt said:
No problems here, the cube emulates the phone's movement and does not spin at all.
Cant seem to attach anything here. But I'm on stock 4.2.2 (Vietnam).
Let me know if you need more info.
Click to expand...
Click to collapse
Thanks for the information.
looks like every thing is working fine on the gyro sensor on your side