Related
hey guys, I'm about to trade my htc desire for a nexus one and have read up on a few problems, and I wanted to find out first hand from you guys wether they're actually problems, or wether they are a load.
Which leads me to my questions.
Does your nexus one have any of the following problems:
1. trackball gets stuck sometimes
2. the on/off/standby switch has stopped working (or you have had to send it back to be repaired)
3. the touchscreen randomly stops working
4. 3G connectivity issue
5. Wifi problems
6. Proximity sensor sensitivity issue
7. earpiece: insufficient volume
and lastly -
Is there any reason why you would not recommend me selling my desire and buying a nexus?
Thanks,
Brandon
It would be easier to have them numbered
1. Trackball - never heard of it.
2. Power button - never had anything on mine, but there's a good reason to believe there was a faulty batch out there - some had to exchange theirs.
3. Touchscreen - The issue is that it starts "missing" the presses, registering way below. Pressing the power button twice (entering and exiting standby) "cures" it. A real issue, happens very rarely.
4. 3G - opinions are split on it, reported only by vocal minority and only in areas barely covered by 3G, and only long time ago. Personally, never saw anything that could be considered as "issue". Actually, rather good reception and good data rates over bad connections.
5. WiFi - again, depends on what "issue" is. It's not completely flawless, for example, fails connecting to encrypted network w/ Cisco 521G. Haven't had any problems on mine, though.
6. Proximity sensor - never heard of it.
7. Volume - never heard of it.
To the last question - why would you want to do that? You have a device with very similar specs that runs very similar firmware. Froyo is already out for Desire, AFAIK, and that exchange would only bring you the trackball notifications and the future updates (Gingerbread). Is that the reason for you to switch?
P.S. All or almost all of the issues listed above would be similar for both phones, since they're almost identical.
Jack_R1 said:
To the last question - why would you want to do that? You have a device with very similar specs that runs very similar firmware. Froyo is already out for Desire, AFAIK, and that exchange would only bring you the trackball notifications and the future updates (Gingerbread). Is that the reason for you to switch?
P.S. All or almost all of the issues listed above would be similar for both phones, since they're almost identical.
Click to expand...
Click to collapse
Thanks for the reply!
The problem is that the there are only about 4 chefs cooking for the desire (and about 5 others uploading their own version of the 4 roms). And the battery life on the new froyo ROMs are terrible. I used up the whole battery in about 6 hours with 3g not enabled, and brightness at the minimum.
and there seems to be much more support for the nexus. (XDA support that is)
+ there are much more cases available for the nexus, I think it looks better, and I really love the idea of the trackball and how it can change colors
P.S I forgot to ask how are the capacative buttens?
Some have said they don't exactly work (you have to press them a few times before it works)
I remember reading somewhere that you have to press them a bit above the buttons and they work fine. Is this true? or are some devices just randomly screwed?
Thanks,
Brandon
No to all.
Atleast I didn't notice
Any reason not to just keep the Desire? The n1 is great but the Desire is nearly identically and slightly better in some ways.
brandon1108 said:
hey guys, I'm about to trade my htc desire for a nexus one and have read up on a few problems, and I wanted to find out first hand from you guys wether they're actually problems, or wether they are a load.
Which leads me to my questions.
Does your nexus one have any of the following problems:
1. trackball gets stuck sometimes- Never had this problem......
2. the on/off/standby switch has stopped working (or you have had to send it back to be repaired)- Um, not for me.... But I have heard this happening to people.
3. the touchscreen randomly stops working - NEVER ever has this happened
4. 3G connectivity issue - I only use wifi since it's everywhere. More efficiant and faster!
5. Wifi problems - None for me.
6. Proximity sensor sensitivity issue - Nope
7. earpiece: insufficient volume - Nope, I find it too loud sometimes. But, I do have sensative hearing.
and lastly -
Is there any reason why you would not recommend me selling my desire and buying a nexus? No reasons honestly. They are both pretty similar except for support and design as well as a few other diffs. The only thing I like about the desire is it's hardware keys and chin
Thanks,
Brandon
Click to expand...
Click to collapse
brandon1108 said:
Thanks for the reply!
The problem is that the there are only about 4 chefs cooking for the desire (and about 5 others uploading their own version of the 4 roms). And the battery life on the new froyo ROMs are terrible. I used up the whole battery in about 6 hours with 3g not enabled, and brightness at the minimum.
and there seems to be much more support for the nexus. (XDA support that is)
+ there are much more cases available for the nexus, I think it looks better, and I really love the idea of the trackball and how it can change colors
P.S I forgot to ask how are the capacative buttens?
Some have said they don't exactly work (you have to press them a few times before it works)
I remember reading somewhere that you have to press them a bit above the buttons and they work fine. Is this true? or are some devices just randomly screwed?
Thanks,
Brandon
Click to expand...
Click to collapse
Ugh, I do have issues with the capacitive buttons. Like I said above, I envy hardware keys. It's not that they don't work, they just arent calibrated. You need to touch way above where they are for them to register. If you press the button where its placed exactly they don't work.
NOTE: I should let you know about all the cool things the Menu button does (second button with the lines) I just found out about the Menu button on my Nexus Lol!
I would do that trade and not have any issues at all. The nexus is The most active device right now and will be thru this year at least. Those problems you listed are not a big deal, the power button only fails for some people. Use track ball wake and you have nothing to worry about. Everything else is not really a problem.
brandon1108 said:
P.S I forgot to ask how are the capacative buttens?
Some have said they don't exactly work (you have to press them a few times before it works)
I remember reading somewhere that you have to press them a bit above the buttons and they work fine. Is this true? or are some devices just randomly screwed?
Thanks,
Brandon
Click to expand...
Click to collapse
They're all screwed equally All the capacitive buttons register too high, so you have to press higher to hit them. At least they're consistent.
not a single mention of white notification burn-in. seems common.
brandon1108 said:
Does your nexus one have any of the following problems:
1. trackball gets stuck sometimes
3. the touchscreen randomly stops working
7. earpiece: insufficient volume
Thanks,
Brandon
Click to expand...
Click to collapse
yup.
1. get stuck on going "down". kind of annoying but a spazz around with it fixes it.
2 yup, cant get it to unlock sometimes.
3, sort of. wouldnt mind it louder and of better quality. More depth.
mtl171 said:
not a single mention of white notification burn-in. seems common.
Click to expand...
Click to collapse
:O I remember someone talking about it in the desire forum - If I use a black notification bar I should be fine right?
Brandon,
Does your nexus one have any of the following problems:
1. trackball gets stuck sometimes No
2. the on/off/standby switch has stopped working (or you have had to send it back to be repaired) Yes & Yes gettting repaired by HTC as we speak.
3. the touchscreen randomly stops working No - used to occasionally before Froyo but not anymore
4. 3G connectivity issue No
5. Wifi problems No
6. Proximity sensor sensitivity issue No
7. earpiece: insufficient volume No
8. how are the capacative buttons? Fine, If you swipe them downwards in the opposite direction but the same manner as you would, to select the notification bar. If you tap them with the pad of your finger instead of the point it also a non issue. OTOH tapping with the point of your finger you just need to tap slightly below.
PurpleSmurfLlama
I disagree and do not think the majority of power button failures are due to poor maintenance. Is your poor maintenance theory just a hunch perhaps? I keep my phone nice and clean, no obvious crap beneath the button. In another thread someone who had a failing power button dismantled his phone an reported the power button presses a switch that is connected via a ribbon cable to a circuit board. No amount of cleaning these fixed it for him. Furthermore people who have had their "power buttons" repaired have reported that all these these items appear to have been replaced when they get their repaired phone back from HTC. Same phone comes back with new IMEI because the circuit board has been changed as part of the fix. To me this suggests that on the faulty units the issue goes deeper than just the button and a users maintenance of it. I am just hoping that the FIX is permanent.
I've had my Nexus One for a few months now and I can't say I've had any of those problems, well my WiFi sometimes just disconnects, but I think that's just to do with the distance between my room and the router. As for button and trackball problems there's been none, even after a horrifying ordeal where a friend spilt beer on my N1 then instantly after in the panic I dropped it in the sand :/
The swap in my opinion can only be based purely on aesthetics, IMO the N1 is nicer, not being biased, the Desire is beautiful, I just think the N1 is more sleek. Hope this helps even a little.
Sent from my Nexus One using XDA App
brandon1108 said:
:O I remember someone talking about it in the desire forum - If I use a black notification bar I should be fine right?
Click to expand...
Click to collapse
Yes exactly, just use black color and you'll be fine. That white is such a horrible color anyway.
brandon1108 said:
Does your nexus one have any of the following problems:
1. trackball gets stuck sometimes
2. the on/off/standby switch has stopped working (or you have had to send it back to be repaired)
3. the touchscreen randomly stops working
4. 3G connectivity issue
5. Wifi problems
6. Proximity sensor sensitivity issue
7. earpiece: insufficient volume
Click to expand...
Click to collapse
How about a poll?
1. no
2. switch is "soft" on the replacement I just received (was fine on original phone and 1st replacement)
3. no
4. YES! RECEPTION IS A BIG PROBLEM! AS IS 3G CONNECTIVITY (3 bars and websites won't load WTF?)!
5. no
6. no
7. yes
maybe add:
8. PINK screen - YES. Just keep asking HTC for replacements, screw them for their poor quality control.
9. camera color tint (blue for me) - YES. Ok for me ... but I made go another replacement binge if I find anything at fault with this phone.
10. I also experience bad call quality - got fixed by the replacement.
1. Trackball - NO problems here.
2. Power button - NO problems here.
3. Touchscreen Unresponsive - Roughly once or twice a month. I put it to standby and back, and it's fixed. I've noticed that only certain ROMs do this. I never had the problem on FRF50 or FRF83, but I have once in a while on FRF91.
4. 3G Connectivity - NO issues.
5. Wifi - NO issues.
6. Proximity sensor - NO issues.
7. Earpiece volume - NO issue, but I have always had one of Pershoot's kernels installed, which includes an "audio fix."
I would have no hesitation recommending a nexus. Though, if you're a gamer, I'd say get a Galaxy S phone because of the better GPU.
#3 is the only one that consistently pisses me off.. all the other ones are software and can and are fixed with different roms.
I know that this has been a fairly common complaint about the Nexus One but i'm wondering, roughly what percentage of people actually have this issue? To clarify, i mean the problem whereby touching the screen in one place is actually registering elsewhere on the screen.
I've had this problem since buying my n1 and having to constantly turn the screen off and back on again was driving me nuts. Finally i sent the unit back to Vodafone for repair and they in turn sent it to HTC to be fixed. So yesterday i got it back with an enclosed statement along the lines of "we have fixed your fault etc..".
Three minutes into using the damn thing and the fault crops up again. So much for that! To be fair to Vodafone they are sending out a replacement unit now but of course i'm concerned that even that will have the same issue.
What are the odds?
Here is the same.
To developers: the fact that resetting the screen fix the problem makes me to ask if there isn't a way to make the screen re-calibrate itself every X seconds/minutes, without shut off and on the screen every time. Seems to be until now the only solution to this extremely annoying issue.
It really is a bizarre one. I've seen people discussing whether it's a hardware or software issue but nobody seems to have a definitive answer. If it were a hardware problem, surely it would be constant/permanent? If it's a software issue i would have thought that somebody would have bug-fixed it by now? Especially as it seems so prevailant.
I'm stumped!
Other than this one problem though i am completely in love with this phone. The device itself feels solid, durable and pleasant to use. Android is improving all the time and it always impresses when you demonstrate to the un-initiated what the device is capable of. So close to perfect...but not quite!
EDIT... This from the wiki.. "- Q5: Sometimes my screen registers touches in incorrect places, and I need to turn the phone off and on to make it work correctly again
A: This is a hardware problem, nothing can be done about it. Nexus One's digitizer sucks.
Ho-Hum.
I have experienced this problem on android 2.1 ever since upgrading 2.2/2.2.1, I haven't had the problem. I'm very happy with my screen
Sent from my Nexus One using XDA App
msavic6 said:
I have experienced this problem on android 2.1 ever since upgrading 2.2/2.2.1, I haven't had the problem. I'm very happy with my screen
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
That suggests a software problem although i have had it on 2.1, 2.2 and now 2.2.1. I would say that it has happened to me within three minutes of using the phone, 50% of the time within that three minute window. In other words it's cropped up in half the texts/emails i have sent where i have had to do the screen off/on thing to complete the message.
Very annoying.
It has to do mostly with the way people hold their phones, the possibility of registering false touches - including, for example, touching the screen with fingers that aren't completely dry. Some have the issue more than others.
HW issues still can have SW workarounds sometimes. I'm not sure if it's the case. HW and SW need to be analyzed to find one, if exists.
There is no "calibrating" capacitive touchscreen. Resetting its controller might have effects like missing touches and other random screen misbehavior (for example - if the controller is tracking fingers, resetting it would cause it to lose the tracking).
Since getting my phone back from 'repair' the issue is less frequent, suggesting that it's not a usage problem as i'm obviously still using the phone in the same manner as before. Instead it seems that various devices suffer from the problem in varying degrees.
I suppose if i knew what they had actually done to the phone while it was being tended to it might help us discover why the frequency of the problem has been reduced. I know that the digitizer wasn't replaced as the phone came back with the same screen protector on it as it had when i sent it off. That being said, they obviously did something. I just don't know what!
Most probably replaced the phone's MB.
Try upgrading to the latest radio - the issue will probably not be 100% solved, but now I only get it maybe once a month or so...
I may tell them not to bother sending out a replacement. It's happening far less often since it was returned and (going by the poll results), there's a good chance that the replacement could actually be worse than this one is now.
Perhaps the 2.3 update will jar something loose.
ATTENTION PLEASE!!
after flashing miui latest ROM i've never had touchscreen issues anymore in over 20 hours of hard usage (also with the phone in charge!!).
I don't believe is a coincidence, developers please ask miui developers if they have integrated a code to fix this issues.
Thanks!
Sent from my Nexus One using XDA App
pyngwie said:
ATTENTION PLEASE!!
after flashing miui latest ROM i've never had touchscreen issues anymore in over 20 hours of hard usage (also with the phone in charge!!).
I don't believe is a coincidence, developers please ask miui developers if they have integrated a code to fix this issues.
Thanks!
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
could you please download Multitouch Visible Test
http://www.appbrain.com/app/multitouch-visible-test/com.batterypoweredgames.mtvistest
and report back?
xyellx said:
could you please download Multitouch Visible Test
http://www.appbrain.com/app/multitouch-visible-test/com.batterypoweredgames.mtvistest
and report back?
Click to expand...
Click to collapse
I have already restored cyano 6.1.1.
However, about "multitouch issues" I mean inaccuracy, the fact that the touch is recognised in another point of the screen (particularly when you press the bottom part of the panel). I didn't verified the axes-inversion issue, but I'm almost sure that it persists.
The "touch inaccuracy" is nothing else than the usual axis-swapping thing. When accidental dual touches (palm/holding fingers/water/etc) happen, the digitizer goes nuts.
Jack_R1 said:
The "touch inaccuracy" is nothing else than the usual axis-swapping thing. When accidental dual touches (palm/holding fingers/water/etc) happen, the digitizer goes nuts.
Click to expand...
Click to collapse
I don't think so....I pay attentions when the screen goes crazy. I'm absolutely sure that (in charge for example) my touch is ONE.
The only times I was able to trigger the "screen nuts" effect, were when I was typing 2-fingered, and fast - making it register dual touches. Moreover, sometimes a single touch with a single finger is reported as series of touches. Once it happens, it stays until screen off.
Jack_R1 said:
Moreover, sometimes a single touch with a single finger is reported as series of touches. Once it happens, it stays until screen off.
Click to expand...
Click to collapse
I mean this....since I moved to MIUI this is not happened anymore.
Since I uninstalled Htcime the inaccuracy issues seem less so far! Almost only with the phone under charge ...much much better than before! Dunno why....
Sent from my Nexus One using XDA App
I've scoured the internet in attempt to resolve this issue, and I know it's been talked about many a time before, but this just doesn't have an answer yet afaik.
Does anybody have any experience with fixing the inaccuracy of the touch screen after prolonged use? I love the nexus one, it's by far the best phone I've owned; but this little bug makes the phone completely unrealistic in real-world use.
If this isn't a software issue, it has to be something with the digitizer being powered off and back on to remove the accuracy bug. In that case, is there any low-level way to turn the digitizer off and back on as fast as possible every X seconds? That would mean losing touch capability for a few milliseconds, but is much better than locking and unlocking the phone each time it "goes wild."
I had given up all hope that this issue could be resolved in any fashion as dodgy hardware is, well...dodgy. Nothing can be done about it right?
I haven't had a screen wonk since starting in on the CM7 nightlies many moons ago!
IN YOUR FACE WONK!
Is there an FAQ about this digitizer issue?
JoeSchmoe007 said:
Is there an FAQ about this digitizer issue?
Click to expand...
Click to collapse
No, but it's been covered so extensively that nobody really mentions it any more. Either that or others have found what i have, that somehow the CM7 ROM mitigates the problem. Seriously, i haven't had an issue with it for months!
My particular N1 was never good with stock ROMs. Hated them and gave me endless trouble with one thing or another. It's the polar opposite for me with CM ROMs. Never any issues at all. No call or screen wonk, none of the bugs that others often complain about. It's like the phone has an attitude!
After flashing something ridiculous like 40+ CM7 Nightlies and stable releases, i've not had to wipe data once
DirkGently1 said:
No, but it's been covered so extensively that nobody really mentions it any more. Either that or others have found what i have, that somehow the CM7 ROM mitigates the problem. Seriously, i haven't had an issue with it for months!
My particular N1 was never good with stock ROMs. Hated them and gave me endless trouble with one thing or another. It's the polar opposite for me with CM ROMs. Never any issues at all. No call or screen wonk, none of the bugs that others often complain about. It's like the phone has an attitude!
After flashing something ridiculous like 40+ CM7 Nightlies and stable releases, i've not had to wipe data once
Click to expand...
Click to collapse
Can you please describe what the digitizer issue was/is? I just ordered N1 and haven't received it yet. And what about call wonk? I haven't seen anything about this one.
JoeSchmoe007 said:
Can you please describe what the digitizer issue was/is? I just ordered N1 and haven't received it yet. And what about call wonk? I haven't seen anything about this one.
Click to expand...
Click to collapse
Basically the digitizer has a couple of quirks. One is that after prolonged use (I found it to be completely random) the accuracy goes berserk, registering touches nowhere near they actually are. Secondly there is a switching of the axis when you cross two points: video. They are hardware related so there is no fix. The wonk is a problem with CyanogenMod7 specifically, causing black screens when receiving calls.
Personally I rarely if ever come across the digitizer problem and have never came across the wonk. They aren't deal breakers but can cause a few problems if you play a lot of multi-touch games.
Hollow.Droid said:
Basically the digitizer has a couple of quirks. One is that after prolonged use (I found it to be completely random) the accuracy goes berserk, registering touches nowhere near they actually are. Secondly there is a switching of the axis when you cross two points: video. They are hardware related so there is no fix. The wonk is a problem with CyanogenMod7 specifically, causing black screens when receiving calls.
Personally I rarely if ever come across the digitizer problem and have never came across the wonk. They aren't deal breakers but can cause a few problems if you play a lot of multi-touch games.
Click to expand...
Click to collapse
When accuracy goes berserk - does powering phone off/on help?
JoeSchmoe007 said:
Can you please describe what the digitizer issue was/is? I just ordered N1 and haven't received it yet. And what about call wonk? I haven't seen anything about this one.
Click to expand...
Click to collapse
Well, the touchscreen issue is nothing more than a bad digitizer that was released with the phone and never improved during manufacture of the device. All Nexii have the same one, although people suffered the problem in varying degrees. What would happen is every so often your touch on the screen would register in the wrong place so you may be selecting a shortcut on your homescreen to launch an app, but it might register the touch as being an inch higher/lower/somewhere random. the solution has always been to simply press the power button to turn the screen off/on again. This would fix the issue... until it occurred again.
The call wonk is really in two parts. Stock GB ROMs had a habit of introducing a slight delay in one party being able to hear the other during the start of a call. On CM7 ROMs it was a more significant issue of black screens and freezes during the start of a call. These didn't affect affect everyone though, and even Cyanogen himself didn't have it on on his own device.
EDIT: The other issue affecting the N1 was a weak, and often failing, power button. With the need to keep using it to fix the screen wonk the problem was made worse. That's why you might often see mentions of Trackball wake as it reduced the need to use the power button, therefore extending it's life. Trackball wake is only available on custom ROMs so bear that in mind too!
The phone isn't perfect but with the custom ROM devs doing there thing it's pretty decent for me
Hollow.Droid and DirkGently1 - I appreciate your responses.
Can I bring your attention to my other question to which nobody responded yet?
http://forum.xda-developers.com/showthread.php?t=1077733
JoeSchmoe007 said:
When accuracy goes berserk - does powering phone off/on help?
Click to expand...
Click to collapse
When the issue happens you just lock and unlock the screen to fix it. No need for a reboot.
This issue isn't really such a big deal. It happens once a week or so, and it takes a few seconds to black out the screen then unlock, problem gone.
I've bought an Xperia Z3+ two months ago, recently, I've discovered a certain bright spot on its screen, it's particularly available in white and bright backgrounds, it's less noticeable in black backgrounds, and not at all noticeable in non-solid backgrounds.
I know that it's a hardware issue, but the warranty here is a joke, and I don't want to pay for a new screen for such a small issue.
But on the other hand, once I noticed it, it's all I could see in the mobile, and it removes the whole premium feel in it.
I've manually removed the back cover and there's no issue in the battery that would make it press towards the screen and cause such issue.
I was wondering if there's any manual fix for it? I know that it's a light diffusing layer problem, mostly caused by a certain pressure, but is there a way to make it normal again? A certain pressure in an opposite way, or heat, or suction from behind, etc.
Here's a picture that indicates the issue "It's more visible and annoying in real life"
I have the exact same problem at the very same position as you point. My country does not support officially the Z3+ and so the cost is really high. I searched enough on the internet and i think it is where the vibration is but i cannot confirm it. I also see it all the time because i simply know it is right there. At my case, there are other 2 spots but not seen so easy.
I only hope not to get bigger. I wish i knew what caused this so to be carefull (such as sun exposure or something else - although i am REALLY careful as a person with my mobile phones). I cannot help you and i got really dissapointed after my long search on the web so i will have to live with that. It is hardware problem as i really tried everything to find out that.
Hope someone has any solution. It is not only on our phone but to others too. I hope the post won't get lost after some days!
AntwnisGr said:
I have the exact same problem at the very same position as you point.
Click to expand...
Click to collapse
That's so weird, I thought it was caused by an anonymous fall that I wasn't aware of, the other point is barely noticeable but it's at the top left.
Also, my upper speakers started to produce mixed loud and faint sounds when i play something whike the volume is below 25%.
It's winter, and I usually text near heatrrs, which made me think that the speakers problem was caused by the heater and the screen problem was caused by a particular fall.
Since the warranty is useless I've manually disassembled the phone and there's nothing behind that spot of screen except battery, the vibrator is way below the navkeys, there's no screen on the other side of it, which actually seems to prove that our spots are similar by coincidence, because there's no pressure on the other side except for battery, and I highly doubt yours is faulty, because mine isn't.
My z3+ single sim also has the spot at the same place, but it isnt that noticable since i use auto brightness, really weird, i thought because maybe of accidental high press when the phone was in my pocket.Anyway, I'll switch to XZ premium in december, that sh*t is dope
On the top left corner i have too! So it is not a coincidence. Something is there that you couldn't see when you opened it. I only hope it doens't get worse..
I have it too not only there also in the right bottom corner and a line of 1 centimeters like 1 inch bow in the left upper corner one day was not in there and to the other plaff they appear
Sent from my E6533 using XDA-Developers Legacy app
Now that multiple people have it, I started to suspect that there's actually something.
I might open if again when I can't live with it anymore, but for now I'll try to enjoy it as it's new, and hopefully won't get worse.
I have a z3 and z4 that also have these white spots..no way to fix. look up tv lcd problems your not gonna be able to fix....it gonna keep me from buying anymore sonys till they switch to oled.
I have the same problem in the same position and it was happen after a warranty repair.... Sony didn't have noticed it....
so in short this problem has plagued the phone since day one and i suspected a HW issue since nothing fixed it. for those who dont know whats im talking about, you are lucky. the issue is basically that the proximity sensor is missed up so the screen will light up when you are in a call or listening to Whatsapp/Telegram voice messages.
The Solution:
The problem, turned out, was caused by the factory screen protector that came already applied to the phone. i removed it after it was damaged and also removed the case (Spigen Rugged Armor Case), cleaned the phone and VIOLA its working perfectly fine now...
i hope it works for everyone else.
So, what you are saying is:
Since when this phone got launched in May 2019, not a single user facing the proximity sensor issue had the ingenious idea to remove their factory applied screen protector and you are the first one to come up with this "fix"?
I am really sorry to be this discouraging but: This ain't it chief.
Good that it fixed your perception of the issue though
Comrade, the issue is far graver than that. OnePlus 7Pro does not have a proximity sensor per se. It uses software (an ai I think) to "guess" whether to turn on the screen or not which is why listening to voice notes gets crazy...
amirage said:
Comrade, the issue is far graver than that. OnePlus 7Pro does not have a proximity sensor per se. It uses software (an ai I think) to "guess" whether to turn on the screen or not which is why listening to voice notes gets crazy...
Click to expand...
Click to collapse
Even though it does have an infrared sensor under the screen (that has been proven), i agree with you that it seems to be using something like that.. Curiously, the proximity sensor once fired when i flicked off my lights in my room.. This indeed leads me to believe there is more going on than just a simple infrared proximity sensor..
But yeah, i don't think removing the stock screen protector "fixes" the thing.. It may improve things but i doubt it's a fix.. As i said, this phone has been out for a while and people would have noticed if removing the screen protector fixes the proximity sensor for good..So yeah, cheers mate.
I took the screen protector off before I turned the phone on for the first time. I still get the screen lighting up while I'm on a call, often muting it with my cheek.
I must be lucky but at the moment I have no such issue with my new OP7P (MFD: 2019/05). RR Rom. Still have the screen protector on it. What's the MFD of your unit ?
i have problem with my oneplus since i rooted this phone
after root i have installed pixel expereince rom
when i called i found proximity sensor not working
now almost 6 months no fixed i'm stock oos
please help me there is no guard on my phone also no cover
The simplest solution for me has been to use a Bluetooth headset. I rarely use it without it.