Related
Anyone here experiencing the same problem? At first I thought that was normal, but at some point the touch screen worked while the slider was open and I was really happy with it but now, it no longer works what gives?
am i the only one experiencing this? do you think a ROM upgrade can fix this?
Sometimes (very rarely) the screen doesnt come on and I have to reset, but nothing like you descrived, sorry...
aw! i guess i have an isolated case. thanks twolf!
it's a screen cable problem. just fix it
last week, i had the same proplem. So i sent it to the guarantee service. They replaced the cable, which is connecting the screen with mainboard.
too bad my phone doesn't come with warranty. thanks for the info guys
my phone has the same problem,and I had used many roms, and all of them have the same problem.
my screen isen't working when the keybord is closed,
aneybody have the same problem??
problem
yes i do have the same problem ... my htc niki100 was not working when slide closed ... but when i open it works fine .... sometimes when slide open also it is not working i mean the touch screen ... i removed all parts of my htc niki and i take a look at that but all was fine and i dont know what was the probelm... i think htc failure model is niki... really pissd off guys due to this niki ... if any came to know how to make work that ... just post it and for u i am thankuful..
it is hardware problem. sent my device to service center and they changed the board for free since it is still under warranty. they said it was wear and tear. so it is only matter of time before the new board suffers from wearing out again. unless stop using the sliding keyboard, but tat's the main selling point touch dual is built for =\
how much is the cable $$ connecting the lcd to the boarD?
my niki is out of warranty............can any mobile phone repair shop fix it ?
yawn said:
it is hardware problem. sent my device to service center and they changed the board for free since it is still under warranty. they said it was wear and tear. so it is only matter of time before the new board suffers from wearing out again. unless stop using the sliding keyboard, but tat's the main selling point touch dual is built for =\
Click to expand...
Click to collapse
If you google around you'll see this is quite a common complaint with the Touch Dual. There seems to be a certain flaw with the screen and cable which was never addressed. I had the exact same problem & eventually sent the phone back to HTC to be fixed.
Be warned though - HTC would not fix my phone eventhough it was still under warranty. They said the problem was due to User Mis-Use. My ass it was. I argued it out with them but in the end I just paid the UK£60 to get it fixed - robbing bastards!
You all seem to think it's a hardware issue, and I'm experiencing the same issue, but only under Windows Mobile (I've tried both 6.1 and 6.5 - all sorts of various roms). Android on the other hand, works fine. :/
EDIT:
Well now it's working on Windows too. After I ran Android... SO GIVE THAT A SHOT I GUESS. o.o
Hi
I've got the same problem it's starting to piss me off.. :[email protected]
1) screen doesn't work when slider is opened
2) screen doesn't work at all at times but works again after ....??? xx hours or so.
My warranty has ended, any tips?
Upgraded Windows Mobile to official WM6.1 from HTC.com website.
DrOni(on) said:
You all seem to think it's a hardware issue, and I'm experiencing the same issue, but only under Windows Mobile (I've tried both 6.1 and 6.5 - all sorts of various roms). Android on the other hand, works fine. :/
EDIT:
Well now it's working on Windows too. After I ran Android... SO GIVE THAT A SHOT I GUESS. o.o
Click to expand...
Click to collapse
i came in here to say the same thing.. weird. works fine in android.............
another thing worth noting is that if you keep a finger on the screen while sliding it seems to work everytime
My Niki has the same problem, when slide is open i cannot use the "send" button on the touch screen - so i have to close the slide, to send a SMS.
I bought a HTC Snap now, so my NIKI just lies in the drawer...
Sad, i like the Screen resolution and Rom software on the Niki better than the HTC Snap.
At http://www.ppctechs.com/HTC-Nike_1047/repairs.htm you can buy a HTC Nike ToolKit with special screwdrivers, maybe the cable just needs to be aligned properly, or fixed in a socket...
Has anyone tried to fix it themselves?
guys,
I had the same problem. In fact, my touch screen was totally not working at all. Some threat recon it's loosen cable so i opened my touch dual and tighten the lcd flex cable. It worked after that, but not working when slide is open. I've just changed the flex cable myself and it's working fine now. hope this help.
xiufoong said:
guys,
I had the same problem. In fact, my touch screen was totally not working at all. Some threat recon it's loosen cable so i opened my touch dual and tighten the lcd flex cable. It worked after that, but not working when slide is open. I've just changed the flex cable myself and it's working fine now. hope this help.
Click to expand...
Click to collapse
could you guide me how to fix it? I'm having this problem as well.
Do you have any kind of link as to how to open the niki, screws, cable, where to look etc...?
thanks!
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.
erhm....
my hd2 is somehow stuck in carkit mode, right after completely booting up it turns to carkit mode.
i've allready tried a few roms and it keeps comming back, so my guesses are that it's a hardware problem, anyone familiar with this problem?
I had the exact same problem with my HD2, this issue might have been caused by various reasons. You either have dust/dirt on your sensors or the sensors are damaged.
Try disassembling your device and cleaning them, if that don't work try an android Nand ROM, on some of them you have the option to disable the sensors and you don't have to deal with Navitel. I've been experiencing this problem long time now.. going Android was the only option I had left.
In a lot of cases this was caused by a dodgy USB socket, so before dismantling the phone, give the USB a clean with a dry toothbrush
Lol, never thought I'd see a reply on this thread
But the problem got solved over time, so O guess the sensor was dirty.
Anyway my hd2's antenna is almost dead so I was forced to change my daily device.
But android anyway is a very nice solution for the hd2's life in general
A fully tweaked up hd2 isn't much slower than my current stock One X
I guess time will tell how this phone will end up XD
I dropped my phone and cracked the screen. So since I've did that, the touch screen doesn't work. I went to get the screened replaced and went to test it out and it still doesn't work. What's not allowing my touch screen to work after getting the screen replaced? If I change the screen does is the digitizer attached to the screen so therefore it will get changed too or is it a separate hardware?
Most likely faulty replacement part.
Try downgrade to 4.2.2
DrFredPhD said:
Most likely faulty replacement part.
Click to expand...
Click to collapse
Hi, I've purchased a cheap diplay at ebay. Touch didnt work any more.. after a number of tests i found out this was due to a HW test at boot. When downgrading 4.2.2 everything works fine. Any upgrade 4.3+ failed to enable digitizer after reboot.
PS: When booting eg 4.4.4 with the old digitizer connected and then connect the new digitizer w/o rebboting the the touch was working well.. I'm very interested in geting a confirmation or reason what causes this issue kindly keep me posted
Most replacement screens use an original LCD (recycled from a cracked screen) fitted with a copy touchscreen. Either the incompatibility could be deliberate on LGs part but I think it's probably due to a driver update or something which has broken compatibility with the reverse engineered touchscreen. It could also be a coincidence, some copy parts are prone to just not working for no real reason sometimes.
Hey DrFredPhD
Can you imagine a costum rom with the old touchscreen drivers from 4.2.2 into 4.4.4?
What would this require: To compile a costum kernel? The drivers would usually be in compiled form in the boot.img, right?
I've tried to flash 4.4.4 with the old boot.img from 4.2.2. - but the phone didn't start (as expected..)
Can you imagine someone how could help me in this regard? I think there may be a number of people facing the same problem..
Anyway, thanks for your help - Greetings :good:
Binaries are available for nexus 4, maybe compiling from AOSP with older binaries would work, but you might break functionality too.
It's been done on other devices but probably not for the reason you want.
https://developers.google.com/android/nexus/drivers#makojdq39
So what are you essentially saying? Put the mb in a good working nexus and see if it works or that maybe the tech put a new digitizer with the old rom driver onto an older mb with a new rom driver? And that could possibly cause conflict with drivers or roms? Which in turn will not allow my screen to function?
The part he put on is crap, if you put a decent replacement screen on it'll work fine.
DrFredPhD said:
The part he put on is crap, if you put a decent replacement screen on it'll work fine.
Click to expand...
Click to collapse
Are you sure? Because I don't wanna regret spending money on a new screen and it doesn't work. :laugh:
I've seen phones damaged by a repair bad enough that the touch will never work, but I've seen far more copy touchscreens that are useless.
Hi Guys
Just to say: may bad fake faulty touch "per se" works well under 4.2.2 and updated 4.4.4 also! It just prohibited "start" the phone with this digitizer attached! Both, phone and digitizer are fully functional and "compatible"..