Database Develop

X1 optical joystick problem

Good day everyone
i'm using my X1 since about 2 weeks.
I recently did notice that after waking my phone up the "scrolling down action" is performed...so the optical joystick thinks i'm moving downwards but in fact i'm not even touching it...it not only happens after waking it up, but also when i want to scroll upwards it happens often that it's sliding downwards again when i release the touchy surface...
cleaning of the touchy surface didn't help...aswell as adjusting the sensitivity of the optical joystick...
does anyone else have that problem...or anyone out there having an idea how to fix?

mine dont have that problem at all and if hardreset dont change it i would
write it off as a hardware malfunction

Some solution?
The does same thing happen to me?

I had this problem before too. Somehow, while i was at school, i must have shaken it a lot or something, because i had P.E. that day. When i got home after i had p.e., the joystick scrolling problem stopped. I had the X1 in my pocket the whole day, so i guess when i was running in P.E., something must have shaken and the problem is now fixed.

This has happened to me only once, while browsing. It fixed itself after a soft reset. Very weird.

Solution!!!
Mine had a very similar problem. It was making calls alone once something just touched the joystick's surface. I took it to a repairing center (with a little hope once i read above comments). However they repair it, well, at least the joystick is working on its scroll funtion but when I press it nothing happends. They told me that it was repaired by just cleaningl, with paint thinner and a gum eraser, the part that is marked inside of the red circle in the image below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Mine's got that problem too.. It was so annoying that I disabled the optical joystick thingy... Don't need it anyway

Im glad i dont use that optical thingy. Its annoying when you want to press center button on D-pad but then accidentally scrolls up or down.

Sorry for poping in this post again after er.. i think this is like a year old post. I just had this problem last month.. or maybe months. I been ignoring it for some time now but well it is getting annoying (It always make the speaker go louder for some odd reason by scrolling up or while searching for a contact it scrolls up). I have never used the d-pad and thought of disabling it but not sure how too.
No more warranty as I bought it for some time already (They said so), I send it back to the shop and they wanted to charge me MYR200 to change the ribbon. After thinking a while that d-pad only cost like $7.99USD which is MYR25.10 from cnn.cn website.
Do they mean the slider flex cable which cost MYR147.619 (After converted)?
Does that has any relation with my D-pad getting stuck at the up button?

BIG Problem with Xperia

hello
I have got a problem with my xperia, the top bar shows that my stereo headset is connected but is not...therefore, i cant hear anyone who is trying to call me or i call anyone.. i have been in a vodafone store and they could not find a solution, i also have done hard reset and is still the same... now im about to flash new rom. would that be a solution or any of you got different?
please help me, thanks in advance

try connecting headset again but give it a wiggle about, not too much also try pulling it out and puting it back in quickly several times in a row. be carefull.

i tried that already, not working

after a hard reset i can only assume it's a hardware fault, so i would go get it fixed because if you flash a new rom that will invalidate your waranty.

do that in the FMradio application

thank you guys, i also think that i should return it for vodafone service..
i tried in fmradio and still no working

sorry to hear that. good luck with that
last time that annoying thing happened to me i had to go to the htc HD fm radio app and plug and unplug the offical 3.5 connector to make it work( try plugging->listen to radio->set output to speakers-> then unplug)
a bunch of questions:
-what rom are you using
-did you try different 3.5 connectors
-is the earphone that caused the problem low quality?

the last time this happened to me i used the stylus and just waggled about for ages and ages and eventually the sensor registered that the headphones weren't plugged in.
do a search as plenty of people have had the exact same problem ...
good luck !

yes - just waggle the stylus around in it until it goes - worked for me

thank you..the thing with stylus works, hopefully but its still anoying to do that every time i put my headset
i have got an original vodafone uk rom
yes, i have tried many different headsets
the quality is fine

I have the exact same problem on my 4 month old X1, and now i dont rly know how hard i should wiggle with the stylus...

nottorious_91 said:
I have the exact same problem on my 4 month old X1, and now i dont rly know how hard i should wiggle with the stylus...
Click to expand...
Click to collapse
try waggling and then try inserting the headphones a few times and taking them out too

I've had the same prob for a week now.
After reading up on other HTC phones with the same issue I've found that what went wrong was a little hardware switch inside the jack failed to reset to its off position when the headphones where removed.
To locate the switch:
Turn the phone onto back so that the screen is facing upwards. The switch is at the 4-5 o'clock position if you look directly at the headphone jack, at around 1cm in.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I inserted a small pin which was bent a little at the end to relative position I have described and after I felt it snag just gave it a small wiggle. When doing this I noticed the headphone icon would disappear for a second and return.
This is how I knew I was in the correct position. Then I gave it a good twist.
(I think anti clockwise, but you will know from which direction worked when you wiggled)
The headphone icon disappeared for good and now I'm back to normal phone use!
(Do this at your own risk! But its more precise than sticking the stylus in blind)

kamilanglia17 said:
thank you guys, i also think that i should return it for vodafone service..
i tried in fmradio and still no working
Click to expand...
Click to collapse
DO NOT RETURN IT. This happened to me once, and ONLY once after using the phone for like 6 months. I soft reset and nothing happened.
There is something wrong with the way the device toggled the connection. Just replug and unplug and press play and pause on your video/music player. It should purge sooner or later.
You can also hard reset your device you will find that the problem will most likely purge.

@Charcobeans: Thanks, it worked within 5 seconds Thats just the instructions I searched for. Waggling around did not work, but more precise it was easy. Thanks!

[Q] wonky flash + non working ambient sensor after power button service

Hello,
Recently I sent my nexus one for a button replacement. I got the phone back with some strange symptoms:
- Flash light blink at random event (first boot, after I hang up a call, etc..) but cannot be controlled by software (torch and camera app in CM7, MIUI or the stock firmware). The camera however works fine.
- The ambient sensor is dead. It either reports a very high value (2600 or 5800) or a very low one (10) (these values were taken from the CM7 auto brightness adjustment settings)
- Mic from the headphone when I plug in does not work anymore (the mic works before and tested to be in working condition)
From some online research, it seems like a loose connector can cause the wonky flash light problem (report by fblodroid, he fixed it by plug the connector back)
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=46ef1e3a49030ed9&hl=en
My question is: can the other two problems be related to this connectors as well? Or did I get a defective board?
I plan to fix it once the tools arrives (dealextreme takes forever!). Another option is to bring it back to the service center to get fixed (this will take a week, and who knows what kind of fees on top of that). I'd prefer to fix it if I can.
Anyone has some knowledge about this kind of issue? Any idea what do those connectors do?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

popophobia said:
Hello,
Recently I sent my nexus one for a button replacement. I got the phone back with some strange symptoms:
[...]
Anyone has some knowledge about this kind of issue? Any idea what do those connectors do?
Click to expand...
Click to collapse
Dude, if your N1 is on warranty I wouldn't even bother to think what is causing this problems Send it back. You'd have o wait some time but you will still have your warranty for the future, and if you disassemble it you will probably loose it (not mentioning that your problem could be unfixable!).
They screwed up and they should fix it for free. I hate when electronics come back in worse condition after repair than before...

Well, it's out of warranty. But I think I have 3 months part warranty from the last repair.
They didn't put any seal on the screws this time. Maybe you're right, it's smarter to just send it back to get everything resolved.
I'm just curious whether all the problem described above can be attributed to the board they replaced (or one or two loose connectors).

popophobia said:
Well, it's out of warranty. But I think I have 3 months part warranty from the last repair.
They didn't put any seal on the screws this time. Maybe you're right, it's smarter to just send it back to get everything resolved.
I'm just curious whether all the problem described above can be attributed to the board they replaced (or one or two loose connectors).
Click to expand...
Click to collapse
I didn't know about the warranty, BUT: They spoiled your phone while fixing button so as a consumer you have right to demand that they fix it free of charge! Maybe it's something like silicon defect or "cold solder" (don't now if it's correct name. Google-Translated it) on the main board. They should have tried it before sending it to you.
Wish your N1 will get better soon

N910T won't fix on satellites, even though it can see them.

Hey guys, I'm pulling my hairs out on this problem I am getting with my note 4.
Long story short - I cannot get a GPS fix (to even a single sat) with my N910T.
The longer version:
This thing had a cracked screen - but worked great before that (no GPS problems) and I used it a good year before breaking it. So I bought a N910A (ATT) note 4 to use the screen to fix my trusty note.
I gutted both phones, and put my N910T motherboard in the N910A's frame, with the screen still attached to the frame. I kept the N910A's USB daughterboard (with the charging port) because in the research I did, it seemed basically identical to the one from my broken screen frame, and I knew it would be tricky to get that out and into the new one without busting the new glass or destroying the flex cables.
So after some trouble with the S pen not working initially (the cable didn't press in fully, had to stick paper behind the flex cable and it went in properly) I was able to get the phone up and running again, and all features seemed to work great again.
However - I noticed after a couple days that the GPS was super spotty, so bad it was mostly unusable. I noticed that AGPS was on and it was using wifi and mobile data to help get a fix, so I turned it to GPS only mode. In GPS only mode the phone gets not signal whatsoever, no matter where I am.
I tried the simple fixes many recommend online, one which is to try tightening the screws a bit, and in fact, as this process continued I opened and closed up the phone several times, making sure to carefully but tightly screw all the screws back into place. That didn't help. I also tried making sure the compass calibration was good - and it made no difference. And I even factory reset to make sure there were no issues with installed apps or anything like that.
I got to thinking, perhaps its a issue with the small bendable pins that press from the motherboard into the mid-frame not making good contact, so I tore the phone down a couple more times, slightly bent out - very carefully - all the pins that press into the mid-frame to make them all have a solid contact, and even tried to get any corrosion or debris from the pads on the mid-frame. I even made sure there was contact for those little ones alone the sides of the phone which seem to have something to do with the buttons rather than what I'm dealing with.
Still no luck, so I tried doing a NV rebuild, which I read might solve getting 0 sat fixes, and discovered my phone wouldn't let me into that menu of the service options, so I had to install root and then do it through shortcut master instead. Once I finally was able to get to the menu and run the NV rebuild.... nothing changed.
So I am fresh outta ideas, and I'm thinking that A) that ATT USB daughterboard actually plays a part in GPS somehow and I need to take my TMO one out of the old phone and put it in the new frame and screen.... or B) Something is damaged on my motherboard.... or C) Somebody out there has a better solution
Any ideas, experiences of what worked are all appreciated!

BUMP --------
Still having this issue. Tried opening it up, and realllllly making sure those antenna springs are making contact, and I made sure the contacts on the mid frame are clean.
I tried TopNTP and that made no difference. Here is an image of whats going on when I run GPS Test:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Bump?
Losing hope for my old phone here

Anybody happen to know if the daughter board that has the USB charging port plays any role in gps?

Can't register new face with face unlock

Factory resetting
Upgrading to 12
down grading to 11
factory resetting
using accessibility mode
using "simple" setup mode
outdoors
by windows
by lights
It just wont register a new face no matter what I do. Almost as the module that handles it is completely hosed. Not sure if it matters, but it never does the "blue" squares on the circle when registering, it only ever says "fit face in inner frame".
Anyone have a fix for this?

Did you replace any component on the phone?

#mcl said:
Did you replace any component on the phone?
Click to expand...
Click to collapse
no, all oem

Does front camera work and sensors as well?
What I saw was people which got face unlock broken after changing front sensors, and as it seems, front camera is locked to the motherboard so if you change it you loose Face unlock.
However I also saw people who had a similar problem to you and after uninstall updates from some apps it started working again. I will search those threads and link them here for you

#mcl said:
Does front camera work and sensors as well?
What I saw was people which got face unlock broken after changing front sensors, and as it seems, front camera is locked to the motherboard so if you change it you loose Face unlock.
However I also saw people who had a similar problem to you and after uninstall updates from some apps it started working again. I will search those threads and link them here for you
Click to expand...
Click to collapse
Would be very appreciated.
is there some sensor setting I should mess with?

kallell said:
Would be very appreciated.
is there some sensor setting I should mess with?
Click to expand...
Click to collapse
I am not aware of any settings apart from motion sense settings sorry

Try clearing the system cache.
Hard reboot. Try in safe mode.
I recommended not using any kind of lock.
The user is usually the one that ends up getting locked out. Many times due to a hardware failure... and the lock only makes the situation worse.

kallell said:
... Anyone have a fix for this?
Click to expand...
Click to collapse
@kallell
Sounds like you have a dead sensor or two. You should download and run some sensor testing apps like sensor lab or sensor test . Run those and if you get corroboration across more than one app you have your answer. How is your warranty status? Did you buy the phone directly from Google? If so you may have a pretty good shot at an RMA.

kallell said:
Would be very appreciated.
is there some sensor setting I should mes
Click to expand...
Click to collapse
kallell said:
Would be very appreciated.
is there some sensor setting I should mess with?
Click to expand...
Click to collapse
Hey here are some links:
1.
https://www.reddit.com/r/GooglePixel/comments/eknssj
2. https://forum.xda-developers.com/t/module-fix-broken-face-unlock.4095233/
3. https://forum.xda-developers.com/t/face-unlock-not-recognizing-my-face.4010275/
Hope this helps you. I will be watching this topic, if I found anything new I will let you know

I mean if the phone didn't suffer from any drop and was never water damage, the front sensors are fine almost certainly.
If it is under warranty though I would suggest getting in touch with Google so you don't need to use your time to fix the problem, it's faster and safer.
If not I would suggest you to open the phone. It may be stupid but maybe the conector got disconnected from the motherboard and therefore doesn't work.
This happen with my rear camera. The phone was never damage and never open but somehow the conector manage to disconnect it self from the motherboard.
Here you have a link to Ifixit's guide on how to change the front sensors. I also link a photo to what happen to my rear camera conector.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}