Develop Bugs

[Q] Proximity Sensor dead. Suggestions to simulate its working?

Alright. My proximity sensor has been dead for a while now. (And yes, it indeed is dead. I've used Proximity Sensor Recallibrator and different apps for testing it.)
It's not a very big issue to use the phone without a working Proximity Sensor. But it gets annoying while attending calls. With a functional sensor, the phone locks itself when you place the phone next to your ear. However, as expected mine doesn't. I've made it a habit to manually lock the screen by pressing the power button before making a call or after receiving a call. However, there are times when I forget in the rush and it leads to very annoying things, the notification drawer slides down and apparently 'my ear' presses and activates wifi, bluetooth and almost everything on the power widget in the notification drawer.
Its really annoying.
I know there's no real way of actually simulating a proximity sensor. So I just need suggestions from you guys as to how to tackle this problem. Any suggestions with creative ideas or workarounds would be welcome.

When i had an htc hd2 i had the same proble and i was using one out of two apps the problem is i can't fully remember the names, one was ditching the proximity sensor and using the light sensor for proximity and the other one was suposed to make the proximity sensor much snappier using partial info from light sensor. Search the play store for "proximity".
P.S. did you dismantle the phone to see if you have dust behind the speaker gril? I had the same problem with my handset , i could have swore that my sensor was dead but after i cleaned it it worked. Hoped i helped
Sent from my Desire HD using xda app-developers app

bondocel said:
When i had an htc hd2 i had the same proble and i was using one out of two apps the problem is i can't fully remember the names, one was ditching the proximity sensor and using the light sensor for proximity and the other one was suposed to make the proximity sensor much snappier using partial info from light sensor. Search the play store for "proximity".
P.S. did you dismantle the phone to see if you have dust behind the speaker gril? I had the same problem with my handset , i could have swore that my sensor was dead but after i cleaned it it worked. Hoped i helped
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
Light sensor data for proximity checks. Its an innovative idea... although wouldn't that make my phone lock itself when the lights are turned off?
Also, the dust thing might be a problem, I'll give it a try to see if it helps. Thanks.

if4ct0r said:
Light sensor data for proximity checks. Its an innovative idea... although wouldn't that make my phone lock itself when the lights are turned off?
Also, the dust thing might be a problem, I'll give it a try to see if it helps. Thanks.
Click to expand...
Click to collapse
1 No that app activates only in call, it bypasses the the sensor data from proximity to light while in call then reverts back after call ends the only downside is that it is not as snappy but it is better than nothing
2 Dismantle your back casing and you will find the motherload of dust in speaker grill, if you didn't check that out first then i'm 99% sure this is your problem: filth in speaker grill and on proxy and light sensors you will find a carpet of dust
Caution!!!!
-watch a dismantling video before you start
-if you want to use compressed air to clean the speaker funnel don't exceed 2 bar max and blow at a distance of 15-25 cm not closer
For further support i will help you over forum but check google or xda for a tutorial

bondocel said:
1 No that app activates only in call, it bypasses the the sensor data from proximity to light while in call then reverts back after call ends the only downside is that it is not as snappy but it is better than nothing
2 Dismantle your back casing and you will find the motherload of dust in speaker grill, if you didn't check that out first then i'm 99% sure this is your problem: filth in speaker grill and on proxy and light sensors you will find a carpet of dust
Caution!!!!
-watch a dismantling video before you start
-if you want to use compressed air to clean the speaker funnel don't exceed 2 bar max and blow at a distance of 15-25 cm not closer
For further support i will help you over forum but check google or xda for a tutorial
Click to expand...
Click to collapse
Can you recall the name of the apps? A bit more help than "proximity" would do.. there are a ton load of crappy apps out there with proximity in their names
And thanks for the suggestion I was indeed watching a dismantling video just now.

https://play.google.com/store/apps/details?id=TomReay.proxSensor&feature=search_result
This was the app i initialy used but back then it was't only for htc hero it was only fot htc
But i can't seem to find the second one it was something like :
https://play.google.com/store/apps/details?id=com.hardrock.smartscreenoff&feature=search_result
But i am not 100 % sure this is it
Any progres on dismanteling? i do the cleaning about once in 2 months and it works perfect

bondocel said:
https://play.google.com/store/apps/details?id=TomReay.proxSensor&feature=search_result
This was the app i initialy used but back then it was't only for htc hero it was only fot htc
But i can't seem to find the second one it was something like :
https://play.google.com/store/apps/details?id=com.hardrock.smartscreenoff&feature=search_result
But i am not 100 % sure this is it
Any progres on dismanteling? i do the cleaning about once in 2 months and it works perfect
Click to expand...
Click to collapse
These were the apps that I found. The first one does not work. (I tried it out of desperation even though it stated it was only for HTC Hero ). I read the description of the second one you mentioned and it does not state any such feature about using the light sensor. The closest thing that app would do is to turn the screen off by shaking.
Anyway, you've given me the idea about using the light sensor data only when there is a phone call to lock the screen. I'll try to use Tasker to see if I can make a setting for that scenario. Otherwise I'll just go ahead and make the app.
As for the dismantling, I've seen the video and to get to the grill all I have to do is to remove the gps cover, remove the agency sticker, unscrew 5 screws of the main body cover and remove the cover... right? But unfortunately I don't have the screwdrivers right now, I'll get them first tomorrow and then definitely clean the grill.

if4ct0r said:
These were the apps that I found. The first one does not work. (I tried it out of desperation even though it stated it was only for HTC Hero ). I read the description of the second one you mentioned and it does not state any such feature about using the light sensor. The closest thing that app would do is to turn the screen off by shaking.
Anyway, you've given me the idea about using the light sensor data only when there is a phone call to lock the screen. I'll try to use Tasker to see if I can make a setting for that scenario. Otherwise I'll just go ahead and make the app.
As for the dismantling, I've seen the video and to get to the grill all I have to do is to remove the gps cover, remove the agency sticker, unscrew 5 screws of the main body cover and remove the cover... right? But unfortunately I don't have the screwdrivers right now, I'll get them first tomorrow and then definitely clean the grill.
Click to expand...
Click to collapse
If you have the phone for a long time and you never cleaned it , that might be your problem.
Btw didn't you notice that the phone would turn off harder and sometimes sporadickly while in call before it stoped working?

bondocel said:
If you have the phone for a long time and you never cleaned it , that might be your problem.
Btw didn't you notice that the phone would turn off harder and sometimes sporadickly while in call before it stoped working?
Click to expand...
Click to collapse
Actually.. I don't recall when it actually stopped working. So no, I have no recollection of such happenings. But I do believe you that it might be a possible cause because of the way I handle the phone, dust is a very real possibility.

Ok my friend i will stay tuned on the topic. i will go to bed now but i will be here tomorow to help and assist with whatever i can.
Good luck m8!

Tell me if you mannaged to fix anything.

First of all try to clean the sensor

I've got a simple one... Call a friend and place your hand over the sensor. If the screens turns off its working lol

[Q] Wierd touch screen issue! (Nexus 7 2013)

Hello Guys,
I'm experiencing issue with touch screen on my N7 (2013) 32gb, Build number: JSS15R , Unrooted
When I put my N7 on the pillow, or sofa (Not wood or metal surface) , the touch screen NOT responding in some area on screen (on the picture below), otherwise, when I hold my N7 in both hands or just one hand it seems to work just fine!
Do you have this issue or only me ?
Note: I used Multi-Touch test app (by TPYXA software) also for this test, and I did factory reset with no any apps install (only Multi-touch app)
{
"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"
}

sauofee said:
Hello Guys,
I'm experiencing issue with touch screen on my N7 (2013) 32gb, Build number: JSS15R , Unrooted
When I put my N7 on the pillow, or sofa (Not wood or metal surface) , the touch screen NOT responding in some area on screen (on the picture below), otherwise, when I hold my N7 in both hands or just one hand it seems to work just fine!
Do you have this issue or only me ?
Note: I used Multi-Touch test app (by TPYXA software) also for this test, and I did factory reset with no any apps install (only Multi-touch app)
Click to expand...
Click to collapse
I was the first to post this. People think we are crazy. But you are right mine works perfect unless its on a pillow or couch or cloth. On the table it works perfect.
http://forum.xda-developers.com/showthread.php?t=2448015&page=13

lespaulman67 said:
I was the first to post this. People think we are crazy. But you are right mine works perfect unless its on a pillow or couch or cloth. On the table it works perfect.
http://forum.xda-developers.com/showthread.php?t=2448015&page=13
Click to expand...
Click to collapse
Same here. Thought my Nexus 7 was fine for a couple weeks. I have no clue what could cause this but I've tested it a lot and it is definitely fine in my hands or on a hard surface and always really bad on a soft fabric surface. It makes no sense, maybe a hard case on the back would help? Has anyone with this problem tried that, are you using it with or without a case?

lespaulman67 said:
I was the first to post this. People think we are crazy. But you are right mine works perfect unless its on a pillow or couch or cloth. On the table it works perfect.
http://forum.xda-developers.com/showthread.php?t=2448015&page=13
Click to expand...
Click to collapse
What you think, is that hardware or software problem?

will this be caused by statics on certain fabric? (really wild guess)

roytse said:
will this be caused by statics on certain fabric? (really wild guess)
Click to expand...
Click to collapse
I will tell you what I think. I think it has to do with the wireless charging coils in the back of the tablet.
I am using a slimline Moko case. I tried it out of the case and it still did same on couch and pillow. On solid surface works great.Is there anyone out there that has taken the Nexus 7 apart. Unplug the wireless charging see if it fixes the screen issues.

This problem is also known as the grounding issue, although some say that's not an accurate description. Regardless, I had this issue and this thread fixed it. http://forum.xda-developers.com/showthread.php?t=2428133
Take a look and see if one of the files will fix your problem.

Skinnysloth said:
This problem is also known as the grounding issue, although some say that's not an accurate description. Regardless, I had this issue and this thread fixed it. http://forum.xda-developers.com/showthread.php?t=2428133
Take a look and see if one of the files will fix your problem.
Click to expand...
Click to collapse
The ts10 file fixed this issue for me.

fuser-invent said:
Same here. Thought my Nexus 7 was fine for a couple weeks. I have no clue what could cause this but I've tested it a lot and it is definitely fine in my hands or on a hard surface and always really bad on a soft fabric surface. It makes no sense, maybe a hard case on the back would help? Has anyone with this problem tried that, are you using it with or without a case?
Click to expand...
Click to collapse
Wow, just tried it and seems like you right.
Screen going nuts when placed on my bed.
When i touching it with all ten fingers, screen automatically turns off and on, endlessly sometimes.
Seems like thats a hardware problem, i dont think any app able to wake up the screen.
Just made a video. Sorry for quality, my dorm roommate havent back yet, so i were filming alone with power of my ankle.

Google or asus or both should begin talking about this and what is the answer/solution they are going to give us. Mine is going to asus tomorrow, let's see what thy do. I know they have change screen, front and gps to another user, and did not even talk about gps problems at all, so they may know something.

bokoy said:
Google or asus or both should begin talking about this and what is the answer/solution they are going to give us. Mine is going to asus tomorrow, let's see what thy do. I know they have change screen, front and gps to another user, and did not even talk about gps problems at all, so they may know something.
Click to expand...
Click to collapse
Wireless charging coils. Its causing a magnetic field on the back of the tablet. causing something like a grounding issue but really not.
If you take your USB cable and plug it in to your Nexus 7 and run the cord around the screen it will go nuts. It should not do that. Same with head phone plugged in to Nexus 7 and the head phone wire touches the screen it causes issues. There is a shielding problem. or its the wireless charging coils needing taken out.
Electromagnetic Interference
Large power lines, electric motors, kitchen appliances, and other devices may directly interfere with a display picture. Many devices are not properly shielded and their electromagnetic fields can cause disruption. Most modern display devices have sufficient shielding to prevent interference, but damage to the shielding may allow for signals to penetrate. Older displays and economy brands may have minimal shielding, leaving these devices vulnerable. Cables and audio/video equipment are also vulnerable to electromagnetic interference.
Read this guys
http://www.silabs.com/Support Documents/TechnicalDocs/Minimizing-Touchscreen-EMI.pdf

@ lespaulman67
I agree with you :good:.
For me , when I plug my headphone into my N7 the problem with touch screen disappear even if I put it on Fabric ground.
Also, I have Galaxy Note II with QI wireless charging (QI wireless charger with the coil purchased from ebay 6 months ago), until now I don't have any issue with touch screen or charging itself.
Yes, I think the wireless coil caused touch issue.
Thank you all for the information , hope Google and Asus fix this very soon

Here is a logcat for touchscreen fail and sudden screen off/on turning.
Not sure if i did it right though
Note that NFC turning on/off by itself as well.

I have a couple of other tablets that I do amateur Dev work on, so I decided I can do without the nexus for a while and send it in for "repair" to see what happens. I'm curious to find out if they will change out any hardware or just flash a different firmware version and then send it back. I've tried every stock version if firmware with no luck, it seems to work fine for a couple if hour up to a day and the goes back to sucking. I'll report back in this thread when it gets mailed back and let everyone know what turn around time is like and if it actually helps. I have mentioned the ASUS customer service rep on live chat was excellent and its really easy to RMA it back.

I got my tablet back from he service center. It was a pain, they shipped it to the wrong address and then fedex delivered it to a neighbor, had to retrieve it and re-deliver it. Turnaround time at the service center was only one day but shipping in both directions was about a week total.
Even though I requested it, there was no notes on what they did so I contacted customer service. They looked up the notes and told me they had to open the tablet to re-calibrate the touchscreen and also loaded a "newer driver" to fix the issue. They also said it was safe to update the firmware if a new version is released.
So far the tablet is fine but I'll report back after using it for longer to see if the issue really is fixed. If they had to open the tablet, that sounds like people with this particular issue do have to send it in for repair because no firmware update can fix it.

fuser-invent said:
They looked up the notes and told me they had to open the tablet to re-calibrate the touchscreen and also loaded a "newer driver" to fix the issue.
Click to expand...
Click to collapse
Could you do me a favor?
assuming you are rooted, reboot your tablet
then type
su
dmesg | grep "ektf3k" | grep "firmware"
PM or post the output.

sfhub said:
Could you do me a favor?
assuming you are rooted, reboot your tablet
then type
su
dmesg | grep "ektf3k" | grep "firmware"
PM or post the output.
Click to expand...
Click to collapse
What do you need from the output? That command doesn't work together but I can grep them separately. I'm not nearly set-up enough to copy/paste the dmesg, so I'll have to type it out for now. Relevant parts, let me know if you need more:
grep for firmware:
firmware version: 0xa042
firmware id: 0x3029
grep for ektf3k:
x resolution: 0x007e
y resolution: 0x00d2
boot code id: 0x6047
Max X=2239, Max Y=1343
Don't know if you need the rest but I'm guessing not.

Mine got back from asus one week ago, they replaced screen, front and gps. Nothing was fixed, multitouch is still going mad, single touch is a bit improve, as before it works nearly well grounded but over a table or a sofa it works worst.
One friend got it back for a second time, the first time they did the same they have done to mine, now they changed main bd-2g, rear camera, screen, front and gps, 24hrs later he is reporting me that problems are back. Do you know what main bd -2g is? Motherboard?
Where did you type those commands?

bokoy said:
Mine got back from asus one week ago, they replaced screen, front and gps. Nothing was fixed, multitouch is still going mad, single touch is a bit improve, as before it works nearly well grounded but over a table or a sofa it works worst.
One friend got it back for a second time, the first time they did the same they have done to mine, now they changed main bd-2g, rear camera, screen, front and gps, 24hrs later he is reporting me that problems are back. Do you know what main bd -2g is? Motherboard?
Where did you type those commands?
Click to expand...
Click to collapse
Just download any terminal emulator from the play store. I use this one.
As for the touch issues, mines obviously still got the multi-touch thing going on when you get several close fingers together. In my opinion that really has nothing to do with the Nexus 7. I've owned 8 tablets, not including the this Nexus and they all do the same thing if you put a bunch of fingers on the screen and then group them in close together. I'm pretty sure if you were to go to a Best Buy or something and play with all their tablets you would be able to reproduce the same thing on every single one.
The whole "only works when I'm holding it" thing was new to me though. It literally didn't work on any surface or even suspended on a stand. I've been playing around with it more since I got it back and putting it on various things, so far it works on every hard and soft surface, it also works whiles charging via USB and wireless charging. Another thing to note is that it came back with JSS15Q loaded. I haven't updated and don't plan on doing that for a while, even though the customer service people "guaranteed" me that it would be fine.
No clue about the bd-2g though.

fuser-invent said:
firmware version: 0xa042
Click to expand...
Click to collapse
Ok, you didn't get any "newer" touchscreen firmware. This is the standard one that came with JSS15Q/R.
So it is possible you have a screen that now behaves best with the latest touchscreen firmware.

Question about an proximity sensor issue

So i have an H812 model and last year i had the dreaded boot loop issue but got it fixed under warranty and no issue since with that. The issue that is irritating the hell out of me now is that the double tap to turn screen on just stopped working reliably. It barely ever works.
I've tried the sensor calibration from the hidden menu and i have a question about that also. My sensor acts like it calibrates fine but the # next it seems kinda low (# next to proximety cal pass ...). It's around 48. See screenshot for reference taken from xda https://forum.xda-developers.com/attachment.php?attachmentid=3513220&d=1445359160
Has my sensor just crapped out? and if so, is that normal. Any help would be appreciated, i've gotten so addicted to using that feature that people ask me what the hell i'm doing when i try to turn their phones screen on lol.
Edit: No screen protector on btw and the internal board as far as i can see seems fine too. And the double tap to turn screen off works fine.
Thanks

sunster said:
So i have an H812 model and last year i had the dreaded boot loop issue but got it fixed under warranty and no issue since with that. The issue that is irritating the hell out of me now is that the double tap to turn screen on just stopped working reliably. It barely ever works.
I've tried the sensor calibration from the hidden menu and i have a question about that also. My sensor acts like it calibrates fine but the # next it seems kinda low (# next to proximety cal pass ...). It's around 48. See screenshot for reference taken from xda https://forum.xda-developers.com/attachment.php?attachmentid=3513220&d=1445359160
Has my sensor just crapped out? and if so, is that normal. Any help would be appreciated, i've gotten so addicted to using that feature that people ask me what the hell i'm doing when i try to turn their phones screen on lol.
Edit: No screen protector on btw and the internal board as far as i can see seems fine too. And the double tap to turn screen off works fine.
Thanks
Click to expand...
Click to collapse
Is the little black rubber plug in the prox sensor. They may have forgot to put it back in. This little black plug is required for proper prox sensor to function properly.

Thnaks for the response but It worked perfectly for quite some time after the board was replaced by the service center so don't think that's it.

I'm guessing you dropped your phone. That's the problem

deltadiesel said:
I'm guessing you dropped your phone. That's the problem
Click to expand...
Click to collapse
Sorry man, never got an alert to this but better late than never . Can't recall but i might have. Why would you say that? Is there a possibility something moved or broke or just plain got whacked out of place? Of course the issue is still there. I was thinking about opening it up anyways so i'll take a look. Thanks

sunster said:
Sorry man, never got an alert to this but better late than never . Can't recall but i might have. Why would you say that? Is there a possibility something moved or broke or just plain got whacked out of place? Of course the issue is still there. I was thinking about opening it up anyways so i'll take a look. Thanks
Click to expand...
Click to collapse
So i opened it up and checked the rubber piece just to make sure and it's there. Everything else looks ok. I guess the sensor just crapped out and will just continue to live with it.

Hardware issues? Post yours here!

Hi,
I've seen many people making threads out if hardware issues, so I thought about making a roll-up sticky thread (if mods agree with it) about them.
In my case, I'm experiencing 2 really irritating ones that made me contact Razer Support already, currently waiting for an answer.
Whenever my phone hits 100% of battery, the phone stops detecting the charger (probably to avoid killing the battery, which okay, it's nice), but then after just 1 single second, it detects it again. In loop. This is the second time I let my phone charge overnight and I fear my screen will burn because of this, since there's no option to avoid the screen to turn in when charger is plugged in.
Also, in the 4 days I've had it, in a random moment of time whenever I'm just using my phone for WhatsApp, or Chrome, and I transition to another app while the previous app was handling the camera, I can see my screen freezing with a few colourful stripes all over it, on the left hand side most of them. After that happens, 1/4 of the times it happened I managed to get it working again, the rest 3/4 my screen turned off after that and, don't ask how but even though the panel is off, it detects touch input, and the only way to turn it back on is a force reboot pressing all three buttons in the device.
Shall I request an exchange unit? I've had this one for 4 days and idk how normal this is.

NFC hardly ever worked and when it did each terminal said I was trying to use 2 cards at once
Speaker grill at the bottom was lifting off
FP scanner stopped working had to do 5 factory reset and rub the scanner with a wipe constantly to get it to work again
Charger was making very bad buzzing noises when charging (this was completely replaced by razer in have the replacement already)
RMAd to razer (after a fight with Three) was a green one had to get a silver one :/ it's en route to razer ATM so using a Stupid wileyfox phone to get by and it's driving me nuts. I swear if they say the speaker grill was damaged by me and thus the cause I'll freak! Buying the phone was a pain in the ass enough just for it to be a crappy model.
Thinking bout selling it and getting a different phone when it comes back but I'm still torn as everything else was perfect for me.

Roxas598 said:
NFC hardly ever worked and when it did each terminal said I was trying to use 2 cards at once
Speaker grill at the bottom was lifting off
FP scanner stopped working had to do 5 factory reset and rub the scanner with a wipe constantly to get it to work again
Charger was making very bad buzzing noises when charging (this was completely replaced by razer in have the replacement already)
RMAd to razer (after a fight with Three) was a green one had to get a silver one :/ it's en route to razer ATM so using a Stupid wileyfox phone to get by and it's driving me nuts. I swear if they say the speaker grill was damaged by me and thus the cause I'll freak! Buying the phone was a pain in the ass enough just for it to be a crappy model.
Thinking bout selling it and getting a different phone when it comes back but I'm still torn as everything else was perfect for me.
Click to expand...
Click to collapse
If you still see NFC issues with the new unit you get, it would be cool if you could drop me a bug report zip, I would take a look.
Alex

TheCrazyLex said:
If you still see NFC issues with the new unit you get, it would be cool if you could drop me a bug report zip, I would take a look.
Alex
Click to expand...
Click to collapse
If I decide to keep the device I will indeed Alex :good:

I had these horrible lines in my screen and the bottom speaker was messed up. I RMA'd and they fixed the speaker but the lines are still there just not as obvious.

I'm sending my unit back due to vibration motor issues. Besides that it seems good.

@TheCrazyLex, mind having a look at this (that's 1/2 of my issues):
{
"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"
}
Dunno if kernel related due to graphics drivers or actual HW issue. Support team considers it's hardware so I'm currently in terms of RMAing my unit. Want a logcat/dmesg of it? Happens specifically when there's a transition between apps, or when using the camera. Sometimes it happens to hang my phone right after those blue/green stripes appear, on the others hitting the home button restores the device back to it's normal state.

linuxct said:
@TheCrazyLex, mind having a look at this (that's 1/2 of my issues):
Dunno if kernel related due to graphics drivers or actual HW issue. Support team considers it's hardware so I'm currently in terms of RMAing my unit. Want a logcat/dmesg of it? Happens specifically when there's a transition between apps, or when using the camera. Sometimes it happens to hang my phone right after those blue/green stripes appear, on the others hitting the home button restores the device back to it's normal state.
Click to expand...
Click to collapse
I think it's a hardware issue because one of the two dsi lane communication failed.

linuxct said:
@TheCrazyLex, mind having a look at this (that's 1/2 of my issues):
Dunno if kernel related due to graphics drivers or actual HW issue. Support team considers it's hardware so I'm currently in terms of RMAing my unit. Want a logcat/dmesg of it? Happens specifically when there's a transition between apps, or when using the camera. Sometimes it happens to hang my phone right after those blue/green stripes appear, on the others hitting the home button restores the device back to it's normal state.
Click to expand...
Click to collapse
Yep that looks like a hardware issue, no logs should be needed here.
I hope the RMA process will be quick for you!
Alex

Right now I've had 2 issues.
1. The vibration motor is extremely rattly, especially when the phone is on vibrate or double tap power to open the camera.
2. I've got a stuck pixel at the top of the screen and a dead pixel at the bottom, along Whit what appears the screen ever so faintly flickering. I'm currently in contact with Razer to see what they can do about it.
Edit: I've just had a group of dead pixels form at the bottom of the screen a few days ago. I contacted Razer and they are going to do an RMA on it.

I guess mine is more software but the phone app keeps crashing.

I loved my Razer phone, I really did but had a few critical issues which led me to sell.
Vibration motor was week, kinda like a rattle but I think thats with everyone phone. Couldn't feel it in my pocket.
NFC was terrible, took me 10 attempts at a local Tesco to find the right spot, other places it just wouldn't work.
Screen was a tad too dim while using it as a satnav, probably more of my placement of the phone holder but the sun glare would always hit the screen making the viewing really hard.
I'd still recommend the phone though, great device but just for my usuage I couldn't cope.
Sent from my Pixel 2 XL using Tapatalk

I had a speaker issue with the first razer phone where the bottom speaker was distorted and top speaker was fine, then sent it in got a replacement phone and now the top speaker is having issues. Its not distorted but it is less louder and has less quality then the other speaker. Plus i used a noise generator app to test it and i started to smell a little bit of burning coil from the top speaker. I will send it in and get another one and hopefully its not messed up. The main reason to why i have not yet rooted is because i wanna make sure the speakers are fully functional. In my opinion these speakers shpuld not break under 3 weeks. Can you guys run some tests to see if your phones speakers have the same issue? Thanks. I love the phone btw. So good.

Had the phone 6 days and the speaker grills are lifting, gutted isn't the word

When I use the phone in landscape mode (with volume buttons on the bottom) the sound coming from speakers are inverted. Does anyone have the same issue?

Micro SD card only works in FAT32 file system, I formated to original exfat the SanDisk 400GB came with and phone said "unsupported file system,need format" I'm fine with fat32 but just 4GB file limit I don't like even phone itself uses exfat file system as u loaded 8gb file to phone from PC, I'm talking with customer support about this but no luck they just go around and say "did I reset phone" or did I tried micro sd card as internal storage, I tried, no way to put file then as nor pc nor file manager sees micro sd then, and internal storage is about 250mb read and 100mb write, while micro sd is about 80mb read and 60mb write on SanDisk A1 400gb micro sd ps. Card works on Xperia z and Xperia Z2 with exfat file system just fine
---------- Post added at 03:14 AM ---------- Previous post was at 03:13 AM ----------
el4nimal said:
When I use the phone in landscape mode (with volume buttons on the bottom) the sound coming from speakers are inverted. Does anyone have the same issue?
Click to expand...
Click to collapse
YouTube -> stereo sound test and top speaker is right bottom is left

sonyzz said:
YouTube -> stereo sound test and top speaker is right bottom is left
Click to expand...
Click to collapse
Yes, but when I tried to play Dolby Atmos Demo is inverted, which is ironic

el4nimal said:
Yes, but when I tried to play Dolby Atmos Demo is inverted, which is ironic
Click to expand...
Click to collapse
But you don't watch demo everyday lol

sonyzz said:
But you don't watch demo everyday lol
Click to expand...
Click to collapse
You never know :-b

el4nimal said:
You never know :-b
Click to expand...
Click to collapse
No exfat support for micro sd is still bigger issue than stereo reverse since, not deal breaker but can't load 1080p bluray movie which is 16gb in size even I have 400gb micro sd card - limited to 4gb by out dated fat32

[COS13]Proximity sensor not working

i have a oneplus 8 pro that was running on OOS 11 like magic
then update it to COS 12 and the proximity sensor stopped working
yesterday COS 13 came and i thought it would fix the problem but no, the problem still there.
any fix for the proximity sensor one COS 13 please.

Mine is also not working at all since oos12. Im completely stock on oos13 now.
Sensor doesnt react at all.

Hi,
mine too stopped working a few days ago.
Im on OOS13 (eu) but it worked the hole time, suddently it stopped working, without any changes to the system.
I did a proximity sensor test (dialpad : #*899# ) and it does not react at all.
PS : Can anyone tell me where the sensor is located on the phone i cant find it.

riding the same boat

I tried to reset it with "Proximity Sensor Reset" app, but it didnt work so I think its a hardware problem...
Fortunately the hardware piece costs about 5-10 bucks, unfortunately phones today are so glued that I dont wanna hassle to open it just because of the little sensor..
Edit: I found out where the sensor is located somewhere in the right corner,
yesterday I coincidentally noticed that it sometime works when the top right corner comes in contact with my pants or any other fabric.
When I try it with my hands or head it doesn't react at all...

Deavy said:
I tried to reset it with "Proximity Sensor Reset" app, but it didnt work so I think its a hardware problem...
Fortunately the hardware piece costs about 5-10 bucks, unfortunately phones today are so glued that I dont wanna hassle to open it just because of the little sensor..
Edit: I found out where the sensor is located somewhere in the right corner,
yesterday I coincidentally noticed that it sometime works when the top right corner comes in contact with my pants or any other fabric.
When I try it with my hands or head it doesn't react at all...
Click to expand...
Click to collapse
I was going to tell you that, I accidently discovered that proximity sensor is kind of working when in contact with my hoodie that is covering my ears.
but when phone is directly touching the skin it wont work.

Same here. I bought a used one in very good condition and figured out that the phone does not switch off the screen during calls. I can run the diagnostics and see that the sensor works properly when I use some fabric on it but has absolutely no effect when using the hand or the ear.
I wonder how that can be and if it's really an issue with the OS version or a hardware issue.

Also same here. Proximity sensor problems after oos13 update. Has anyone tried custom roms if problem are still occuring on those too?

i found the solution on yt

AidenDRJr said:
i found the solution on yt
Click to expand...
Click to collapse
You are the best thanks a lot
Works 100% fine after new calibration.