I've tried everything I could think of personally. I flashed stock to both slots, wiped a couple of times, and flashed my persist partition backup thinking that would help.
When I try a proximity sensor app it acts like I don't have one. The sensors I believe are null are proximity, tap 2 wake, and auto screen brightness sensor.
I thought I'd ask before calling Google.
I tried connecting to there repair web page but after connecting I always get tinted out.
Try in safe mode if any 3rd party apps have been loaded, otherwise...
Install DevChek and see what sensors are or aren't working.
If you're running stock and a block of sensor readings aren't showing or are skewed, it sounds like a mobo failure.
blackhawk said:
Try in safe mode if any 3rd party apps have been loaded, otherwise...
Install DevChek and see what sensors are or aren't working.
If you're running stock and a block of sensor readings aren't showing or are skewed, it sounds like a mobo failure.
Click to expand...
Click to collapse
Hi thanks for replying.
I've tried safe mode, sorry I forgot to mention.
I've tried a few apps including flar2's dev check.
The ones that you can test sensors, say it either doesn't exist, etc. I replaced persist from backup with fastboot, etc. I'm starting to think maybe it is a hardware fault.
Samuel Holland said:
Hi thanks for replying.
I've tried safe mode, sorry I forgot to mention.
I've tried a few apps including flar2's dev check.
The ones that you can test sensors, say it either doesn't exist, etc. I replaced persist from backup with fastboot, etc. I'm starting to think maybe it is a hardware fault.
Click to expand...
Click to collapse
One reason I run stock is it makes troubleshooting much easier. If the stock firmware's reloaded right it's a hardware fault of some kind.
blackhawk said:
One reason I run stock is it makes troubleshooting much easier. If the firmware's loaded right it's a hardware fault of some kind.
Click to expand...
Click to collapse
Thank you sincerely, I ran stock up until yesterday besides kernel. I have to admit though, evolution is pretty Nice . Thanks, I guess I'm gonna call Google Monday; as much as I was hoping to not be the case, it's looking like hardware. I'll report back what happens.
Samuel Holland said:
Thank you sincerely, I ran stock up until yesterday besides kernel. I have to admit though, evolution is pretty Nice . Thanks, I guess I'm gonna call Google Monday; as much as I was hoping to not be the case, it's looking like hardware. I'll report back what happens.
Click to expand...
Click to collapse
Do u use Evo with its kernel or other kernel?
Samuel Holland said:
Thank you sincerely, I ran stock up until yesterday besides kernel. I have to admit though, evolution is pretty Nice . Thanks, I guess I'm gonna call Google Monday; as much as I was hoping to not be the case, it's looking like hardware. I'll report back what happens.
Click to expand...
Click to collapse
what might be worth a last effort try, is to reflash stock firmware and wipe data/factory reset the phone from stock recovery, if reflashing firmware with a wipe does not work.
to enter stock recovery: boot to recovery on your phone, when on the no command screen press and hold power button, while holding power button press volume up.
That was the only thing that could clear up corruption in the face unlock firmware back on pixel 4xl, which happened sporadically for a few months until google fixed it properly.
Freak07 said:
what might be worth a last effort try, is to reflash stock firmware and wipe data/factory reset the phone from stock recovery, if reflashing firmware with a wipe does not work.
to enter stock recovery: boot to recovery on your phone, when on the no command screen press and hold power button, while holding power button press volume up.
That was the only thing that could clear up corruption in the face unlock firmware back on pixel 4xl, which happened sporadically for a few months until google fixed it properly.
Click to expand...
Click to collapse
Thank you, I'm gonna have to give that a shot, I did flash stock but I didn't wipe in stock recovery. That's a good idea come to think about it. Thanks for replying.
Samuel Holland said:
Thank you, I'm gonna have to give that a shot, I did flash stock but I didn't wipe in stock recovery. That's a good idea come to think about it. Thanks for replying.
Click to expand...
Click to collapse
Freak07 may be right... there may still be a firmware issue. I find it odd you lost both the double tap wake and proximity.
I simply never had to trouble on that level with Androids. I didn't mention a hard reboot but probably should have I rarely use that option.
More commonly I would clear the system cache but I understand that's not an option on Pixels.
blackhawk said:
Freak07 may be right... there may still be a firmware issue. I find it odd you lost both the double tap wake and proximity.
I simply never had to trouble on that level with Androids. I didn't mention a hard reboot but probably should have I rarely use that option.
More commonly I would clear the system cache but I understand that's not an option on Pixels.
Click to expand...
Click to collapse
Yes, I hope so, I'm gonna give it a shot in the next couple days before calling Google. By the way the three sensors not working are barometer, proximity, & light sensor. I'll report back. Thx
Samuel Holland said:
Yes, I hope so, I'm gonna give it a shot in the next couple days before calling Google. By the way the three sensors not working are barometer, proximity, & light sensor. I'll report back. Thx
Click to expand...
Click to collapse
I may be completely wrong here but...I don't think the Pixel 7 Pro even has a barometer? As for the proximity sensor and the light sensor...I think they are one-and-the-same. In that case all you have is one faulty sensor which can be calibrated using the screen brightness slider while auto brightness is turned on! YMMV
jaseman said:
I may be completely wrong here but...I don't think the Pixel 7 Pro even has a barometer?
Click to expand...
Click to collapse
It does have a barometer
{
"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"
}
jaseman said:
As for the proximity sensor and the light sensor...I think they are one-and-the-same.
Click to expand...
Click to collapse
These are definitely discrete sensors.
The main reason I'm so sure, is that I use my P7P (and older phones, way, way back) in zliploc baggies, quite often, as a road-cyclist.
It 100% knows it's in a bag (and is sometimes a pain to use, but the P7P does better than many older phones), AND it still adjusts the brightness, accordingly...
pgrey2 said:
These are definitely discrete sensors.
The main reason I'm so sure, is that I use my P7P (and older phones, way, way back) in zliploc baggies, quite often, as a road-cyclist.
It 100% knows it's in a bag (and is sometimes a pain to use, but the P7P does better than many older phones), AND it still adjusts the brightness, accordingly...
Click to expand...
Click to collapse
If the bag is clear then the brightness adjustment will still work. As for the phone being a pain to use is because there is a layer of loose plastic over the screen! This has nothing to do with proximity sensor. I am sticking to my original view that the proximity sensor and the light sensor are the same! It only makes sense! HOWEVER, I admit I could be wrong!
Well update I stock flashed June update and wiped using stock recovery, but unfortunately they are still not working.
I asked through email if I could send in using warranty, hopefully they will allow me to get it fixed. Used to I could call, but they asked me to email, so I'm on my sixth email going on the second week so hopefully Monday they will allow me to send in. I'm gonna also try the support tab under setting. Thanks everyone for the input and suggestions.
jaseman said:
If the bag is clear then the brightness adjustment will still work. As for the phone being a pain to use is because there is a layer of loose plastic over the screen! This has nothing to do with proximity sensor. I am sticking to my original view that the proximity sensor and the light sensor are the same! It only makes sense! HOWEVER, I admit I could be wrong!
Click to expand...
Click to collapse
The point is, the proximity sensor works with a clear bag, which means it's not using the light sensor.
See this teardown:
Google also lists them as discrete sensors: https://support.google.com/pixelphone/answer/7158570?hl=en&ref_topic=7530176&sjid=15388427490819596714-NA#zippy=,pixel-pro
If you scroll down this last (after looking at the P7P specs for sensors), to the original Pixel/XL, you'll see where they list this sensor as a combined unit, for comparison.
My phone works well inside a ziploc, even WITH a screen protector to-boot. The only thing that's hit-miss, is the fingerprint sensor (works maybe 50% through the extra layers), and the tap-to-wake. This 2nd one is where the proximity sensor comes in, if it were just a light sensor, the bag would have minimal affect, right?
pgrey2 said:
The point is, the proximity sensor works with a clear bag, which means it's not using the light sensor.
Click to expand...
Click to collapse
What is it using then? Crystal ball?
Rstment ^m^ said:
What is it using then? Crystal ball?
Click to expand...
Click to collapse
Nope, IR emitter and receiver.
Another cool way to test, is to take your phone in a completely dark room, in a call (NOT with speakerphone on, this disables the proximity sensor, for obvious reasons), and see if you can still use the screen (hint, you can). If the standard light sensor were being used, it would prevent the phone screen from waking, in this scenario.
There are also a variety of (well rated) sensor test apps out there, which will also demonstrate the difference between the sensors. The light sensor will vary, a LOT, across a wide variety of values, in a lighted room, whereas the proximity sensor will be off, until your hand/face/whatever-body-part is within about 5cm (ish), at which point it triggers, in a very binary way.
The actual light sensor itself (not the LED emitter) may be repurposed for receiving the expected IR, that part is tough to discern, from the specs tests, or schematics. It may be possible to peruse the device-level code, to get more specificity here, but I'm not quite that motivated, at this point...
Related
I don't know if this is just an issue with me or if others are experiencing the same issue.
for some reason my proximity sensor is VERY sensitive... for example if I move my face just 1/2 and inch from the screen my screen turns on and I either press "Mute" or "Speaker" with my cheek OR i hang up on the person I'm calling when I place the phone back against my face.
This happens about 50% of the time... so every other call I make has this issue.
I don't know if I can change the sensitivity or the length of time before the screen turns on.
I'm coming form the Eris/D1/DX/Fascinate and I never had these issues with my older phones.
Any advice or Steps to fix this would be greatly appreciated.
Plz Advise
Happens to me too, but I don't manage to hang up or mute the calls normally. I'd love a solution as well!
Magicadder said:
I don't know if this is just an issue with me or if others are experiencing the same issue.
for some reason my proximity sensor is VERY sensitive... for example if I move my face just 1/2 and inch from the screen my screen turns on and I either press "Mute" or "Speaker" with my cheek OR i hang up on the person I'm calling when I place the phone back against my face.
This happens about 50% of the time... so every other call I make has this issue.
I don't know if I can change the sensitivity or the length of time before the screen turns on.
I'm coming form the Eris/D1/DX/Fascinate and I never had these issues with my older phones.
Any advice or Steps to fix this would be greatly appreciated.
Plz Advise
Click to expand...
Click to collapse
Which kernel / rom are you using? I have heard that some kernels have caused proximity sensor issues but I'm not sure if the issue others have experienced is the same as yours. I'd try a battery pull first, if that doesn't help try a different kernel and see if that fixes it. If the issue still persists, it could be a hardware issue and you might have to get the phone exchanged under the manufacturers warranty.
Sent from my Thunderbolt using Tapatalk
m00nshake said:
Which kernel / rom are you using? I have heard that some kernels have caused proximity sensor issues but I'm not sure if the issue others have experienced is the same as yours. I'd try a battery pull first, if that doesn't help try a different kernel and see if that fixes it. If the issue still persists, it could be a hardware issue and you might have to get the phone exchanged under the manufacturers warranty.
Sent from my Thunderbolt using Tapatalk
Click to expand...
Click to collapse
I'm using Stock firmware with bamf 4.3a Kernal
I've reset this thing too many times... installing different roms and such.. but I can verify that this is happening to another phone. My wife's phone does exactly the same thing. we purchased out tbolts on launch day ( if that helps )
The proximity sensor is located were the Verizon V is at
In between the big V is the sensor. Very hard to see go under a light a tilt the like you would if you want to find scratchs on your phone it really is between the V or I'm you can not find it. Make a phone call and get your index or any finger. And again make sure your under light and make the shadow of your finger go on top of the proximity sensor. Mine is very sensitive also.
-Monky_1
-Monky_1
My proximity sensor seems pretty touchy, as well.
I initially thought it to be a problem with a particular version of Adrynalyne's kernel, but I'm not so sure anymore. Adrynalyne also said that a kernel shouldn't affect the proximity performance -- that HTC puts these setting or whatever in the framework (what that means exactly, I'm not sure).
Anyway, I haven't done any exhaustive testing or anything, but I did notice one thing that seems to help keep my screen off is to have the thing pointed straight down while on the phone. My natural inclination is to have it along my jaw line, with the end pointed at my mouth. But the proximity sensor is to the left-of-center on the phone. Angling it moves the sensor away from your ear a bit. Assuming you've got it up to your right ear, that is.
I'd still welcome any other points folks might have about this.
calbruc said:
My proximity sensor seems pretty touchy, as well.
I initially thought it to be a problem with a particular version of Adrynalyne's kernel, but I'm not so sure anymore. Adrynalyne also said that a kernel shouldn't affect the proximity performance -- that HTC puts these setting or whatever in the framework (what that means exactly, I'm not sure).
Anyway, I haven't done any exhaustive testing or anything, but I did notice one thing that seems to help keep my screen off is to have the thing pointed straight down while on the phone. My natural inclination is to have it along my jaw line, with the end pointed at my mouth. But the proximity sensor is to the left-of-center on the phone. Angling it moves the sensor away from your ear a bit. Assuming you've got it up to your right ear, that is.
I'd still welcome any other points folks might have about this.
Click to expand...
Click to collapse
This is exactly what's happening. It's nice to see that I'm not the only one having this issue... even tho I'm sure it's annoying for everybody. Hopefully we'll be able to get some relief from this.
http://market.android.com/details?id=i4nc4mp.myLock.phone
This app keeps me from smashing my Droids.
this is not a signature I type it in every time maybe sent from my phone or my computer
rizzomegav said:
http://market.android.com/details?id=i4nc4mp.myLock.phone
This app keeps me from smashing my Droids.
this is not a signature I type it in every time maybe sent from my phone or my computer
Click to expand...
Click to collapse
Would this work even tho the Thunderbolt has no physical Trackball or Camera Button?
Not to discredit this app Kudos to the Dev who wrote it, but it seems like a work around and not an actual Fix.
But I'll try it out and reply back with some feedback
Here's what I do and it works for me most of the time. When making or receiving a call, once the call is 'connected' I quickly hit the 'home' button so I'm no longer on the 'phone screen' & then the power button which darkens & locks the screen. Even if the proximity sensor allows the screen to light up, the lockscreen is still there and prevents me from muting or hanging up on the other person. It's not a perfect solution since my jaw has managed to unlock the screen & randomly open apps occasionally but it beats hanging up on someone every 5 seconds.
Sent from my NookColor using Tapatalk
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
gatorguy said:
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
Click to expand...
Click to collapse
BAMF 1.5 is based on the new leak, which includes a fix for the proximity sensor. If the rom you are running isn't based on the recent leak for our phones, then you don't have the fix, and will most likely have problems with it.
Check this thread out at droid forums! It fixed my "problem" with the proximity sensor. Simply blow out the sensor with air. Apparently dust gets in there and jacks it all up. I can confirm big time results with this method.
http://www.droidforums.net/forum/thunderbolt-tech-support/142050-thunderbolt-proximity-sensor-issue.html
Edit: All those kernel switches and setcpu tweaks over pocket lint!!! Damnitman!
Magicadder said:
Would this work even tho the Thunderbolt has no physical Trackball or Camera Button?
Not to discredit this app Kudos to the Dev who wrote it, but it seems like a work around and not an actual Fix.
But I'll try it out and reply back with some feedback
Click to expand...
Click to collapse
Well the fix is only to hold the phone correctly unfortunately. My gf has no problem using either phone (hers or mine) but if I touch them its muted hang up bam.
One of my coworkers has the same problem as me another dosent. Its absolutely user errorish IMO.
It works with my thunder bolt sort of the home key still works. I don't mind it, moreso than buggered calls.
this is not a signature I type it in every time maybe sent from my phone or my computer
gatorguy said:
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
Click to expand...
Click to collapse
A screen protector was an issues for me. The first one I put on did not fit perfectly, so the top of the protector cut directly threw the center of the sensor and collected dust and gave me some issues. The second one i used was applied from the top down to not obstruct the sensor. Solved my problem.
My phone sensor will black out when I am on a call and the phone is against my face, but when I pull the phone away the screen won't come back up for some reason..
I find that it seems to reflect off the arm of my glasses, which is kinda glossy like. When the IR LED reflects back at it, it seems to assume infinite distance. Same thing happened on my Droid.
There was also a case that lacked the cutout for the proximity sensor on the Droid... screen would never turn off because it reflected the IR.
I'm glad to see I'm not the only one with this problem. It's been happening to me for a few weeks now. I've run the majority of available ROMs and kernels (pre- and post- radio update) in multiple combinations so, I believe its safe to say they are not to blame.
I'm not using a screen protector so, that can't be to blame. And I don't have any scratches on my screen either. I'm curious about this dust theory though. It may be the best one I've heard yet. Has anyone else put the air hose to their Thunderbolt yet? I think I'm gonna give it a go asap. But, in the meantime, I'd love to hear whether anyone else has had positive results. If not, I fear I may have to move on to the glasses theory. I really hope it isn't that one though. I don't want to choose between having my Thunderbolt or my sight!
Mine still does it and I'm using the leak , so I don't think there is a fix in it. If so it doesn't work. Locking the screen seems like a pain but that's the best bet for now.
Sent from my ADR6400L using XDA Premium App
dzigns said:
Here's what I do and it works for me most of the time. When making or receiving a call, once the call is 'connected' I quickly hit the 'home' button so I'm no longer on the 'phone screen' & then the power button which darkens & locks the screen. Even if the proximity sensor allows the screen to light up, the lockscreen is still there and prevents me from muting or hanging up on the other person. It's not a perfect solution since my jaw has managed to unlock the screen & randomly open apps occasionally but it beats hanging up on someone every 5 seconds.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
After trying many ways to work around this problem with the proximity sensor I have found that this is actually works the best .... And I can't thank you enough..... I've grown used to this method and so far its flawless.
Thank you again
Sent from my ADR6400L using XDA App
Really interested in this phone but obviously worried as it's there first generation phone. So can those who actually have the phone please use this thread to highlight the main issues they have encountered with the phone, to help others decide please.
Vibration motor sounds feels and sounds like theres a poor animal inside being shocked occasionally to cause the rumble (and sound)
When making calls people on the other end I cannot understand or make out what's being said but incoming calls are just fine
Started a similar thread, but getting sidetracked irl..
This thread is only focusing on the negatives to help people decide whether or not to buy it?
What about the positives? (which really do outnumber the negatives by a lot)
I'm also saying this after receiving a defective-speaker phone first time. Still wouldn't trade this phone for any others even if ya paid me or gave it to me for free.
It's like this...
{
"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"
}
https://insider.razerzone.com/index.php?threads/a-helpers-guide.28247/
eriknors said:
When making calls people on the other end I cannot understand or make out what's being said but incoming calls are just fine
Click to expand...
Click to collapse
For what it's worth i don't have this issue.
I find it's quite a hefty phone - that reeks of quality, but the square angles and smoothness of the build means it has slipped out of my hands a few more times than other phones. Though I am kinda being a bit namby pamby with it till my screen protector and case come through from Amazon, so it's probably just me.
When my phone vibrates, the bottom speaker area is what rattles.. Hold that or squeeze it and it will stop rattling temporarily.
I've been using this phone for two full days now. I love it. Amazing.
There are a few issues I'd like to list and come back too later to see if anyone else is having the same issues, but first let me start with what I love about the phone because I really do love this phone.
What I Love:
Yuuuuge screen. At first I thought I really wanted to go for the OP5T for the 18:9 Ratio. I actually compared side by side and I like this screen much more.
Phone is bulky, yes. But it gives me a feeling of quality. Like its going to last. My last three phones **** on me which were all Samsung. They look pretty, but they aren't built to last anymore. I am certain Samsung builds phones now to be replaced just like apple. My last phone the S7 Edge literally nothing wrong with it. The alarm went off in the morning like always, when I went to swipe the phone froze, got incredibly hot and shut down. After it cooled down I tried resetting it. Booting in safe mode, etc. Nothing it shows a black screen and what bugs me is that the phone works, I can get text message and unlock etc but the screen is black. This bothers me so much because the boot logo and animation shows up so I know its not a hardware issue. Right as the S8 comes out? Coincidence? I don't think so...
Anyways....
The Razer just seems durable to me, No fancy edges etc. (Cheaper to fix a flat panel in the case of cracks as well).
Screen is smooth as butter at 120hz. It really is noticeable, however after the first day I stopped noticing it. It became a passive thing for me. But I do notice when a game is not running at a high fps and it aggravates me now lol. Most of the games I used to play are literally unplayable to me now.
2TB MicroSD - Wow. No way I will ever need all that but still cool.
Audio, Dolby app. So good.
What I hate: Please let me know if any of these have been addressed by Razer.
Phone does get warm in use at, usually when set to 120hz. Like Youtube and gaming. Even regular use like watching youtube videos in HD gets the phone warm. Never hot, but warm.
Bluetooth audio when on youtube can get out of sync. Only way to fix is with restart. Happened twice so far.
I don't know if its just my mind playing tricks on me, but I notice the screen flash to a dimmer brightness at times. It happens in an instant and gradually gets back up. It's hard to explain, but I will be looking at the screen watching a youtube vid or something then look away and when I look back it seems like it's not as bright, but the more I look at it the more I can't see the difference anymore.
So yeah,
EDIT: Also what is ticking me off is that this has the same camera module as the S7 Edge yet better processor and twice the ram yet I can't shoot video in slow-mo 120fps. I know Razer is working on Camera fix, and I sure hope this feature comes along with it.
I thought the phone has a heat pipe or something like that?. Anyway for me seriously am done with phones that generate heat, especially when it's for gaming!
marvi0 said:
I thought the phone has a heat pipe or something like that?. Anyway for me seriously am done with phones that generate heat, especially when it's for gaming!
Click to expand...
Click to collapse
Is this the unicorn you speak of :
I wouldn't rule out this phone based on one or two users experience,at least until they can show how "bad" it is,with some footage/apps that record heating/etc........
Especially if they're charging the phone while playing a grapic-intense game.
marvi0 said:
I thought the phone has a heat pipe or something like that?. Anyway for me seriously am done with phones that generate heat, especially when it's for gaming!
Click to expand...
Click to collapse
No doubt, phones or computers that generate heat are so mid-90's. They're just dumb.
I've had an issue, happened twice now, but it is difficult to reproduce.
Dolby Atmos app open and turned on, wired headphones (Bang & Olufssen in ear buds). I was listening to an audiobook (Audible app, AAX file extension) and after 25-30 minutes of continuous playback (from 1 audiofile), the sound got weird, like it was coming through a drainpipe. This has never happened with music MP3, and only happened twice but each time after a lengthy playback. So far I haven't got it to happen without Atmos running.
Screen touch response seems like it is not very sensitive. Coming from the axon 7 that you could hover over the screen and it would be detected at times, I find myself double tapping home a lot. Really sucks not being able to change nav bar key placement.
RUNNERX said:
Screen touch response seems like it is not very sensitive. Coming from the axon 7 that you could hover over the screen and it would be detected at times, I find myself double tapping home a lot. Really sucks not being able to change nav bar key placement.
Click to expand...
Click to collapse
I came from the Axon 7 and screen responsiveness was horrible on mine. This phone is a significant leap forward from anything ZTE has offered or ever will offer.
tabletalker7 said:
I came from the Axon 7 and screen responsiveness was horrible on mine. This phone is a significant leap forward from anything ZTE has offered or ever will offer.
Click to expand...
Click to collapse
I am having more small issues with the razer than I did on the axon. Like auto rotate not working at times, not being able to move files from the internal storage to the SD card listing to headphones and the dongle gets moved to much and audio cuts off. I am hoping that once there are custom roms somethings will be fixed.
RUNNERX said:
I am having more small issues with the razer than I did on the axon. Like auto rotate not working at times, not being able to move files from the internal storage to the SD card listing to headphones and the dongle gets moved to much and audio cuts off. I am hoping that once there are custom roms somethings will be fixed.
Click to expand...
Click to collapse
Granted while I have not tried the dongle yet I have no problem moving files from internal to external sd and back again (I used a third party file manager). I have to ask the stupid question. Have you tried a factory reset?
tabletalker7 said:
Granted while I have not tried the dongle yet I have no problem moving files from internal to external sd and back again (I used a third party file manager). I have to ask the stupid question. Have you tried a factory reset?
Click to expand...
Click to collapse
It's not every file, some move some don't. No I have not reset yet, have not reached that point of annoyance yet. Don't get me wrong I really like the hardware it's the little software bugs that are what I have trouble with, and that's coming from a guy that usually runs buggy custom roms.
RUNNERX said:
I am having more small issues with the razer than I did on the axon. Like auto rotate not working at times, not being able to move files from the internal storage to the SD card listing to headphones and the dongle gets moved to much and audio cuts off. I am hoping that once there are custom roms somethings will be fixed.
Click to expand...
Click to collapse
Can't say I've not had the auto rotate not work. It was annoying the home screen is set to portrait in Nova settings.
What files are you trying to move though? From the 64GB internal to a SD?
My only issues are random restarts when I try to wake up my phone, and the metal surrounding my power button being slightly bent.
hello, for my experience, i love this phone a lot, but for downside is,
1. Mirror cast, cast doesnt detect other device on my phone, its like not even trying to find.
2. Bluetooth, so hard to connect audio bluetooth to my car radio, even if i can connect it, it play for just a less than a minute, then it stop.
3. Vibration, yep is kind a anoying vibration.
4. Heat, playing a mobile legends for a minute like playing for a hour, but i solved with using razer phone hard cover, at least i didnt feel the heat too much.
So far is good, but compared to my s8 plus, razer still have a lot to do.
Cheers.
Hi there!
First off: I used the search, but am not confident I haven't overlooked something.
If so I'm sorry!
I have a google pixel with lineage-for-microg, whose battery I had replaced some months ago.
Afterwards I wanted to reflash stock android to start afresh and then reflash lineage.
I'm back on lineage 17 (derived from Android10) and have the following problem:
During calls the microphone in speaker mode doesn't work at all, meaning, the person on the other side doesn't here a thing.
The same happens for speaker calls in other apps.
What still works, is audio in videos I take with the camera.
Also the ambient light sensor seems to have stopped working as the automatic luminosity doesn't work and I have to set the light by hand.
And then the proximity sensor during calls doesn't work.
I'd like to fix these and therefore I would like to find out, whether it is more probably a software or a hardware problem.
I found on this forum that it may have to do with the persist.img, that may have been corrupted by twrp.
Unfortunately I don't know where to get a hopefully working persist.img to try that out.
Things that are maybe relevant are these:
1. The battery was changed, so maybe the engineer doing that broke something
2. During reinstallation of lineage17 I had some problem with twrp not working. Afterwards using lineage recovery worked for installing lineage, but I'm not sure, twrp might have broken something.
3. The same issue also is there on stock android 10.
Can anyone point me in some direction?
I realized that the easiest check for software/hardware distinction would be to just flash a new persist.img.
Is anybody out there, that has a pixel sailfish device with working android 10 that would drop me a message? I should be able to just transplant your persist.img to my pixel sailfish.
I would greatly appreciate it!
Edit: Sorry, I misread your post. You're having microphone issues and not speaker issues. Don't have much advice.
In my experience the proximity sensor and ambient light sensor on Pixel XL's never fail. I've repaired dozens and never seen it.
Bongzerker said:
Edit: Sorry, I misread your post. You're having microphone issues and not speaker issues. Don't have much advice.
In my experience the proximity sensor and ambient light sensor on Pixel XL's never fail. I've repaired dozens and never seen it.
Click to expand...
Click to collapse
Nonetheless, thanks for your time!
If I may ask for even more of it:
Not sure, whether Pixel XL and Pixel are similar when it comes to their hardware ( I have a Pixel, not a Pixel XL), but if you have repaired many of them, do you think it is at all possible, that the hardware shop that changed my battery somehow broke these sensors or forgot to reattach a cable to them?
I don't plan to hold them accountable, as I really like them, just would like to have a hint, whether going to the hassle of bringing my phone there and thus not having it for a few days has a reasonable chance of success.
Hello everyone! I just got my POCO X4 Pro 5G phone yesterday. I absolutely love using it to bits.
However, I noticed that while browsing through content on medium (40 - 50%) brightness, the phone does not actually go fully dark. Some parts are lit up while others are not. (On dark videos and imagery, it is noticeable enough to really bother me even on just my first day of use.)
To elaborate on my point, I have downloaded a completely black picture and displayed it on my phone.
I have attached the photos 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"
}
Setup. (This is the phone displaying a completely black image on my gallery)
Lights off (Captured on my Samsung A50 normal mode)
Lights off (Captured on Night Mode)
I have tried to capture it on video, but it is simply not visible enough on video to be worth your time. You'll simply have to trust that I indeed downloaded a completely black image and displayed it on my gallery. (I wouldn't be posting here for no reason if I was lying, wouldn't I?)
Anyway, it is worth noting that on both higher (60-70%) and lowest (0-10%) brightness, the issue disappears completely (e.g. the screen completely shuts off as expected.) but then some of it return on maximum brightness.
Now I can definitely use the screen all the time on these settings, but I also want to ensure the longevity of my AMOLED screen, and it would suck to always be watching content on effectively only two brightness settings.
I have tried using AMOLED Fixer apps on Google Play but to no avail.
Does anyone else have this issue? Do you think it is fixable through software? Should I return the phone to POCO before it's too late?
Thank you for any responses in advance.
I am not able to reproduce this on my device. I've tried all brightness levels, no weird spots on my end. Maybe you should RMA your device. But let's wait and see if anyone else is having this issue.
gmbhneo said:
I am not able to reproduce this on my device. I've tried all brightness levels, no weird spots on my end. Maybe you should RMA your device. But let's wait and see if anyone else is having this issue.
Click to expand...
Click to collapse
Thanks for your input. I did find someone on reddit having a similar problem to mine, on his mi 11 lite. Unfortunately, the solution offered on his replies does not exist on my phone's settings (I can't find P3 anywhere).
https://www.reddit.com/r/Xiaomi/comments/ouqbws
This makes me feel like it could be a software issue, and I'm really liking everything else about the phone so far so I'm still thinking twice about going through the return process. But I still have some time to think about it for now. Please let me know if you find a similar problem with a potential solution!
Interesting... I'll be sure to check my phone once it arrives, cheers
<Mod Edit>: English translation added.
It is recommended that you update the system or set up debugging, good luck
建议你更新系统或者设置调试一下,祝你好运
Some updates, I guess.
I sent the phone to a local authorized Xiaomi Service Center in my area. While the technician did indeed see and acknowledge my phone's problem (e.g. he did see the screen light up on a dark image), he says it is a probably normal operation for my phone. (Which I personally don't agree with, because again, AMOLED screens must be completely dark.)
They simply updated my phone's software and did not replace the screen, and did remind me that if it did go worse, I still have a 1-year warranty for the phone if it breaks. I really needed to use the phone to travel so I didn't bother bugging them more about it.
HOWEVER, while testing things on my own I did notice some possibly noteworthy observations:
- on the almost near to darkest settings, some colors of black become dark-purple/reddish (particularly when I use Spotify).
- when restarting the phone, I noticed my lock screen actually becomes more color accurate (in my opinion) for 1 or 2 seconds, then it suddenly goes back looking kinda washed-out.
From this, I hypothesize that maybe MIUI uses some kind of special AMOLED drivers when booted which causes the screen to produce the unwanted backlight. So I tested by changing my lock screen and wallpaper to a completely black image, then restarting my phone. What I found out was that indeed, the screen issue COMPLETELY DISAPPEARS on the first 1-2 seconds of booting, and then it comes back again after that and stays until I reboot the phone again. Also, I found that on the boot screen itself, the screen issue doesn't exist at all. The POCO and MIUI logo appeared with absolutely no screen backlight.
This leads me to believe that maybe this really is just a software issue, and I am hoping that if there would be a custom rom (because I doubt MIUI would fix this soon) for this phone, it would completely eliminate this issue once and for all.
I got that too man and i am so confused ...even on full black wallpaper or reddit or really dark grey i can see a white tint or spots i cant describe it actually ..
I dunno what is this actually but i got this on three devices ..
I have asked everyone on Telegram group the denied it and say they didn't have such an issue ..even i told them that i have this on three devices ..
I general screen is stunning colors are so great but in dark grey and full black screen or any black screen it sucks ..
Can you feedback please if you had a solution or know what is going on and what is this issue ??
HfTFranz said:
Some updates, I guess.
I sent the phone to a local authorized Xiaomi Service Center in my area. While the technician did indeed see and acknowledge my phone's problem (e.g. he did see the screen light up on a dark image), he says it is a probably normal operation for my phone. (Which I personally don't agree with, because again, AMOLED screens must be completely dark.)
They simply updated my phone's software and did not replace the screen, and did remind me that if it did go worse, I still have a 1-year warranty for the phone if it breaks. I really needed to use the phone to travel so I didn't bother bugging them more about it.
HOWEVER, while testing things on my own I did notice some possibly noteworthy observations:
- on the almost near to darkest settings, some colors of black become dark-purple/reddish (particularly when I use Spotify).
- when restarting the phone, I noticed my lock screen actually becomes more color accurate (in my opinion) for 1 or 2 seconds, then it suddenly goes back looking kinda washed-out.
From this, I hypothesize that maybe MIUI uses some kind of special AMOLED drivers when booted which causes the screen to produce the unwanted backlight. So I tested by changing my lock screen and wallpaper to a completely black image, then restarting my phone. What I found out was that indeed, the screen issue COMPLETELY DISAPPEARS on the first 1-2 seconds of booting, and then it comes back again after that and stays until I reboot the phone again. Also, I found that on the boot screen itself, the screen issue doesn't exist at all. The POCO and MIUI logo appeared with absolutely no screen backlight.
This leads me to believe that maybe this really is just a software issue, and I am hoping that if there would be a custom rom (because I doubt MIUI would fix this soon) for this phone, it would completely eliminate this issue once and for all.
Click to expand...
Click to collapse
I can confirm too that on miui logo on starting device nothing is wrong ...i dunno if it is a defect screen or a defect driver or a backlit issue ...
Have you discovered anything bro ?? Please feedback man ...
Btw i had screen flickers but after updating to 13.0.9 and restarting nothing is wrong now .
tornido066 said:
I dunno what is this actually but i got this on three devices ..
Click to expand...
Click to collapse
Which 3 devices? Are they all POCO X4 Pro 5G as well or are they other Xiaomi products? Also when did you order your X4 Pro and which color is it?
Unfortunately, I also still have not found any solutions for the problem as well. I am planning to return this soon (to Lazada) if there's no update that would fix it (I doubt there would be). For now I am simply trying to find similarities so we could potentially point out the issue.
HfTFranz said:
Which 3 devices? Are they all POCO X4 Pro 5G as well or are they other Xiaomi products? Also when did you order your X4 Pro and which color is it?
Unfortunately, I also still have not found any solutions for the problem as well. I am planning to return this soon (to Lazada) if there's no update that would fix it (I doubt there would be). For now I am simply trying to find similarities so we could potentially point out the issue.
Click to expand...
Click to collapse
Yes all of them are Poco x4 pro and i got them in Lebanon from a retailer he told me that this issue is not under warranty ...
I will unlock bootloader and try custom roms and eu rom to see if this could help by any chance ...
Maybe they are using a very cheap amoled display or it is really a huge software issue ..
Is your phone a global one btw ??
Did you try a custom rom or eu rom ??
I am afraid that this issue will get bigger and the screen is going to break or something ..
Btw why there is no gamut wide p3 option in the settings ??
Btw have you contacted Xiaomi ? I tried to reach the feedback team but they didnt even respond at all ....
HfTFranz said:
Which 3 devices? Are they all POCO X4 Pro 5G as well or are they other Xiaomi products? Also when did you order your X4 Pro and which color is it?
Unfortunately, I also still have not found any solutions for the problem as well. I am planning to return this soon (to Lazada) if there's no update that would fix it (I doubt there would be). For now I am simply trying to find similarities so we could potentially point out the issue.
Click to expand...
Click to collapse
Coming to you with a new information !
Go to settings to system apps updater..it doesnt have any white spots or any issue ! The black there is a pure black ! Please try and feedback bro ...
EDIT : the only possible solution to this in my humble opinion is that they must increase grey level in dark mode and let us enable P3 option in settings,i guess the pictures causing this issue is not 100% black so that's why it is happening.
A.w they should allow us to enable or disable p3 option since the device SUPPOSED TO SUPPORT IT.
tornido066 said:
Yes all of them are Poco x4 pro and i got them in Lebanon from a retailer he told me that this issue is not under warranty ...
I will unlock bootloader and try custom roms and eu rom to see if this could help by any chance ...
Maybe they are using a very cheap amoled display or it is really a huge software issue ..
Is your phone a global one btw ??
Did you try a custom rom or eu rom ??
I am afraid that this issue will get bigger and the screen is going to break or something ..
Btw why there is no gamut wide p3 option in the settings ??
Click to expand...
Click to collapse
Yes, my phone is global one. I have not tried to custom rom it yet.
I am also wondering the same thing, why there is not P3 option in settings.
tornido066 said:
Btw have you contacted Xiaomi ? I tried to reach the feedback team but they didnt even respond at all ....
Click to expand...
Click to collapse
I have, and just like you, they were not very helpful. They only mentioned I should send it to an authorized service repair center, which I did, and same with you, they did not exactly acknowledge this as part of warranty and only did software updates for it.
tornido066 said:
Coming to you with a new information !
Go to settings to system apps updater..it doesnt have any white spots or any issue ! The black there is a pure black ! Please try and feedback bro ...
EDIT : the only possible solution to this in my humble opinion is that they must increase grey level in dark mode and let us enable P3 option in settings,i guess the pictures causing this issue is not 100% black so that's why it is happening.
A.w they should allow us to enable or disable p3 option since the device SUPPOSED TO SUPPORT IT.
Click to expand...
Click to collapse
I tried going to the same menu and unfortunately mine still has white spots in that area. (Maybe your brightness settings changed? Because the issue only really appears on certain brightness levels)
HfTFranz said:
Yes, my phone is global one. I have not tried to custom rom it yet.
I am also wondering the same thing, why there is not P3 option in settings.
I have, and just like you, they were not very helpful. They only mentioned I should send it to an authorized service repair center, which I did, and same with you, they did not exactly acknowledge this as part of warranty and only did software updates for it.
I tried going to the same menu and unfortunately mine still has white spots in that area. (Maybe your brightness settings changed? Because the issue only really appears on certain brightness levels)
Click to expand...
Click to collapse
I guess we should wait or use a custom rom which supports p3 option ,try this bro :
First raise brightness to exactly around 40% then totally switch off the phone ,then try and check that menu i told you to check before ..
Btw my device had like a free from white spots hour when i did that !
But after watching a video for about 15 minutes the issue does come back unfortunately ..
To be honest this issue is not ruining anything for me ,i mean the colors are really good and vibrant and i am enjoying every video i am watching at my phone,i just dont want this to become bigger or damage the screen for real lol.
HfTFranz said:
Yes, my phone is global one. I have not tried to custom rom it yet.
I am also wondering the same thing, why there is not P3 option in settings.
I have, and just like you, they were not very helpful. They only mentioned I should send it to an authorized service repair center, which I did, and same with you, they did not exactly acknowledge this as part of warranty and only did software updates for it.
I tried going to the same menu and unfortunately mine still has white spots in that area. (Maybe your brightness settings changed? Because the issue only really appears on certain brightness levels)
Click to expand...
Click to collapse
Bro do you have this white spots in netflex on main logo ??
Feeding back again ...my three devices are not usable at all using 120hz ...the issue is getting a lot worse on 120 refresh rate and the screen will flicker after 2 or 3 hours ..
This is so stupid i will never ever buy a xiaomi phone again.
tornido066 said:
Bro do you have this white spots in netflex on main logo ??
Click to expand...
Click to collapse
Yes, white spots exist at all times as long as the phone is turned on. I notice it even for my always-on display.
tornido066 said:
Feeding back again ...my three devices are not usable at all using 120hz ...the issue is getting a lot worse on 120 refresh rate and the screen will flicker after 2 or 3 hours ..
This is so stupid i will never ever buy a xiaomi phone again.
Click to expand...
Click to collapse
Yes, the flickering indeed worsens at 120 Hz.
Just like you, I have also decided not to buy Xiaomi products ever again. Quality control is abysmal. My brother owned a Redmi Note 10 Pro and his SIM slot stopped working after just 2-3 months. Because of these scenarios (including yours which you had 3 phones with the same exact screen problem, along with a fishy warranty), I have no doubt that the problem is with Xiaomi's quality control in and of itself. I guess they had to cut corners somewhere. Maybe others got a good deal out of Xiaomi, but with the risk of having a problematic device, is it really worth spending for a company that obviously does not value quality? Anyways, I will definitely be attempting to return this to Lazada. I hope they will accept and refund it.
I also have the same problem. Since i have used Mi A3 for a very long time so, I can tell how amoled screen looks like. But in my Poco X4 Pro 5G i am facing the same issue as you are facing.
HfTFranz said:
Hello everyone! I just got my POCO X4 Pro 5G phone yesterday. I absolutely love using it to bits.
However, I noticed that while browsing through content on medium (40 - 50%) brightness, the phone does not actually go fully dark. Some parts are lit up while others are not. (On dark videos and imagery, it is noticeable enough to really bother me even on just my first day of use.)
To elaborate on my point, I have downloaded a completely black picture and displayed it on my phone.
I have attached the photos below.
View attachment 5562541
Setup. (This is the phone displaying a completely black image on my gallery)
View attachment 5562537
Lights off (Captured on my Samsung A50 normal mode)
View attachment 5562539
Lights off (Captured on Night Mode)
I have tried to capture it on video, but it is simply not visible enough on video to be worth your time. You'll simply have to trust that I indeed downloaded a completely black image and displayed it on my gallery. (I wouldn't be posting here for no reason if I was lying, wouldn't I?)
Anyway, it is worth noting that on both higher (60-70%) and lowest (0-10%) brightness, the issue disappears completely (e.g. the screen completely shuts off as expected.) but then some of it return on maximum brightness.
Now I can definitely use the screen all the time on these settings, but I also want to ensure the longevity of my AMOLED screen, and it would suck to always be watching content on effectively only two brightness settings.
I have tried using AMOLED Fixer apps on Google Play but to no avail.
Does anyone else have this issue? Do you think it is fixable through software? Should I return the phone to POCO before it's too late?
Thank you for any responses in advance.
Click to expand...
Click to collapse
Can you give me your no. I aslo have the same issue
Debraj131 said:
Can you give me your no. I aslo have the same issue
Click to expand...
Click to collapse
I don't want to disclose my number. However, I guess I could give you an update. I filed for a return to Lazada (an online store) and I am still waiting for their refund. I hope they manage to replicate the issue under a very dark environment so I could receive my refund. Anyway, so the phone is not with me right now. I'm sorry, I cannot do much to help you.
Hi everyone!
Just purchased a P6a during Black Friday. In general I am quite happy with the device and would want to keep it.
However, I have massive issues with crashes/freezes/reboots when using the camera.
I know that many people have reported similar issues, but my case is somewhat special in that it only happens on weekends. During the work week, I use the camera normally, and there has not been a single crash.
But when I go hiking/mountaineering/trailrunning on the weekends, I have massive problems.
I would say, every five photos I take, something goes wrong.
Sometimes I get a complete freeze in the camera app and have to do a hard reboot.
Sometimes, the phone simply reboots itself.
Sometimes it switched itself off.
Sometimes, the camera app seems to work correctly, but then a few minutes later the phone reboots all by itself.
Sometimes, these crashes result in broken, unreadable JPG photos on my phone.
This has happened up to ten times on each of my outdoor tours. I have observed this now over three weekends, on four different tours. After such a crash/freeze/reboot, the phone seems to work completely normally again, as long as I do not use the camera app. As soon as I use the camera app again, it does not take long until the problem reappears. But only as long as I am outdoors for extended periods of time. Indoors never any issue.
The natural suspicion is that it must have something to do with the temperatures outside. But temperatures here in late autumn Bavaria have not even been all that cold; the problems already occur at relatively moderate temperatures of a few degrees above freezing.
Software is fully updated, of course.
Because of the 100% clear correlation with outdoor activities of a certain minimum length, which I can only interpret as temperature dependency, I guess this must be a hardware defect, and I should ask Amazon for a replacement. But what do you guys think? What would you do? Is there any diagnostics I can do first?
Thanks a lot!
Locked bootloader still? Are you planning to unlock, or open to it? I would recommend doing so and doing a complete clean flash of the latest stock to both slots. Sometimes OTA's arent as complete as we like to think.
If you dont want to unlock the bootloader then I would at least do a factory reset, if you already havent.
Have you done anything to rule out everything else? Like are you positive that it's because of the temperature?
Maybe it's got something to do with cellular connectivity or GPS?
You could try removing your SIM/entering Airplane mode, and/or turning GPS off, and going outside, see if the issue persists?
Thanks for the responses!
No, I am currently not planning to unlock the bootloader. (Maybe I will, once the phone is 2 years old and the implied warranty has expired, but not now.)
Yes, I could do a factory reset. Is there a good non-unlocked way to backup everything I have already setup and configured?
No, I have no way of being completely sure that it is the temperature. Your idea that it might be linked to GPS is an interesting one. After all, I had the geotagging feature of the camera app enabled. I switched this off now, let's see if the problem occurs again.
Problem is, I can only test it on weekends. Being outdoors for only an hour or so has never been enough to trigger the problem. It had to be a longer stay outdoors of a few hours at least, and that I can only do on weekends.
rhhd said:
Maybe I will, once the phone is 2 years old and the implied warranty has expired, but not now.
Click to expand...
Click to collapse
Pretty sure that you can just flash the stock ROM, re-lock bootloader, and they won't know/bat an eye.
---
Could you leave your phone outside for a few hours? Instead of going on a hike?
From what I've gathered from OP and your reply above is that your phone starts acting up if it's been out in the cold for a while and you open the camera app. You might wanna leave it in the cold for a bit, wait for it to cool down to ambient temperatures, then try to open the camera app? If it still acts up, then we can be more certain that it's got nothing to do with geolocation, but with the cold temperature.
Good idea! I'll try that tonight and put it on my balcony for a few hours.
I suppose it could also be the fact that it get's moved/shaken more when I am moving on my outdoor tours...
rhhd said:
I suppose it could also be the fact that it get's moved/shaken more when I am moving on my outdoor tours...
Click to expand...
Click to collapse
Or maybe changes in altitude? Although, I don't know if you're that hardcore at hiking or not
Anyway, leaving it on your balcony could help narrow down the source of the issue.
I don't think it is changes in altitude, because one of the tours was just a trailrun in only hilly terrain with maybe only 200 meters of altitude difference between highest and lowest point, and even on that tour I had massive issues.
rhhd said:
I don't think it is changes in altitude, because one of the tours was just a trailrun in only hilly terrain with maybe only 200 meters of altitude difference between highest and lowest point, and even on that tour I had massive issues.
Click to expand...
Click to collapse
Do you keep your device in your pocket? If so, it wouldn't be able to get too cold.
When running, it is in a mesh pocket of my running vest, so it would get quite cold. On mountain tours it is usually in an outside pocket of my pants. So yes, close to my body, but still some isolating layers away from my body.
Other question, now that we are talking shaking as a possible cause:
When you shake your phone in front of your ear, with the camera module facing towards your ear, do you hear something? I can definitely hear something shaking, as if a tiny metal part is loose inside the phone.
I keep my bootloader locked. Each month when there is an update I unlock the bootloader and update the phone in case something goes wrong. Once I've successfully updated my phone I relock the bootloader which just requires a reboot. Unlocking and relocking the bootloader does not delete data.
rhhd said:
When you shake your phone in front of your ear, with the camera module facing towards your ear, do you hear something? I can definitely hear something shaking, as if a tiny metal part is loose inside the phone.
Click to expand...
Click to collapse
Yup. Super faintly.
When having a camera app open, it definitely sounds like what you were describing. My best guess would be the OIS trying its best to keep everything stabilized.
xrayA4T said:
Unlocking and relocking the bootloader does not delete data.
Click to expand...
Click to collapse
Does it void warranty though? Like what's Google's warranty policy here? Does unlocking the bootloader once void it already?
Lada333 said:
Yup. Super faintly.
When having a camera app open, it definitely sounds like what you were describing. My best guess would be the OIS trying its best to keep everything stabilized.
Click to expand...
Click to collapse
No, I don't mean the OIS sound. I can also hear that one (very very faintly) when the camera app is open and I move the phone. (Sounds like a tiny tiny motor whirring a little.)
But the little clattering that I mean can be heard always, even when the screen is off. Sounds like a tiny screw is loose or something. It is also clearly audible, not nearly as faint as the OIS whirring.
Lada333 said:
Does it void warranty though? Like what's Google's warranty policy here? Does unlocking the bootloader once void it already?
Click to expand...
Click to collapse
No, it's not like you are flashing a custom ROM (which I'm pretty sure doesn't void the warranty in the US or Europe). It just allows you to flash a full ROM, not just an OTA. Google has provided this functionality. There is not warning when unlocking that this will void the warranty.
rhhd said:
Sounds like a tiny screw is loose or something. It is also clearly audible
Click to expand...
Click to collapse
When I shake my phone "front to back," I hear that. Only when the camera app isn't open though. When I open it, I cannot replicate the sound.
rhhd said:
No, I don't mean the OIS sound. I can also hear that one (very very faintly) when the camera app is open and I move the phone. (Sounds like a tiny tiny motor whirring a little.)
But the little clattering that I mean can be heard always, even when the screen is off. Sounds like a tiny screw is loose or something.
Click to expand...
Click to collapse
Interesting. That seems to be a third sound. Yes, I also have that one, and just as in your case it goes away when the camera app is open.
But the sound I mean is independent of the camera app, and also occurs when shaking the phone side-to-side.
OK, the test results are in:
On Tuesday, I left the phone out in the cold on my balcony for 2,5 hours, and yes, afterwards the problems did occur.
On Wednesday, I used the phone indoors, no issues. A new camera app update was installed, I hoped this might be the fix.
But no: On Thursday, I again put the phone outdoors for 2,5h. The problems are back.
I will ask Amazon for a replacement.
Thanks a lot for your suggestions!
rhhd said:
OK, the test results are in:
On Tuesday, I left the phone out in the cold on my balcony for 2,5 hours, and yes, afterwards the problems did occur.
On Wednesday, I used the phone indoors, no issues. A new camera app update was installed, I hoped this might be the fix.
But no: On Thursday, I again put the phone outdoors for 2,5h. The problems are back.
I will ask Amazon for a replacement.
Thanks a lot for your suggestions!
Click to expand...
Click to collapse
That's so strange!
I'd love to know what actually triggered this odd issue.
I mean, yeah, surely, something to do with cold temperatures, but that in itself doesn't explain a lot, does it?
I hope your replacement device won't have any issues!