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.
Related
Just noticed it wasn't working. I've flashed back to rooted stock and tried several apps with nothing working. I can't say if it ever worked as I never use it. Has anyone tested this to see what could be the issue? Does it work on a clean phone, unrooted stock original? Are we somehow messing the magnetometer up with flashing?
Bump. Anyone tried their compass even?
Wouldnt rely on it. Ive had the phone sitting on a table with the compass pointing North, closed the app and reopened and it was way off. Closed and opened again and it was pointing a different direction.
So your compass is broke as well. There are phones where this works. It's nice for apps like google skymaps. Question is does it come broke or does rooting/unlocking/flashing somehow mess it up.
I have yet to see a phone where the compass works consistently. Due to the fact that some countries restrict the use of very sensitive magnetometers I doubt we will ever have very reliable ones in cell phones.
Perhaps but this is an advertised feature of a US based phone. We have every right to expect it to function. The question is does it function at all even on new in bow devices. Some youtube videos show it working bit it's not clear if those are i9300s or i535s. It could also just be an unreliable device hitting on some and being broke on others.
So using the sensor test (*#0*#) I was able to see my y axis sensor is very low. It goes above the threshold when the top of the phone is oriented north. The device must be calibrated to start and periodically. It also loses direction if turned up as you would for google skymaps. This makes the app useless. Other devices do not have this problem. I believe I have a defective sensor but also that samsung drivers are shotty. Can anyone else look at their readings and report?
This is probably related to the crap GPS as well. I believe the issue can be fixed in the kernel too bad we don't have many devs that work on the kernels.
Where in the hell is the compass?
Android 4 Life
The compass is a built in piece of hardware that you need an app to see. Search for compass in the play store. Any one should work.
On a sidenote, a Samsung rep checked two of their devices and found it working. One was a vzw on 4.04 and the other was on 4.1. I tried to get him to send me the 4.1 rom to test on but he couldn't.
This may be a sporadic problem inherent in only some devices.
Had vzw ship me a new one but before I returned the old one I flashed it back via odin and low and behold, the compass came back. Even on a stock rom that was slightly modified it wasn't happening. After odin, I was able to root, unlock and flash cwm and keep it running. Once I flashed any rom, the compass was dead but I could flash back to a backup of the stock unmodified rom and it worked. So it's a software issue and I'm going to return the warranty replacement.
Dear all,
A few days ago, my N5's camera stopped working and none of the usual solutions (reboot, clean data and cache of camera app, even complete wipe and change of ROM) did anything to fix the problem. So I went on ebay, and bought a replacement back camera, fitted it and all was well...for a day!!! It looks like after just one day (and nearly no use at all) the new camera has already stopped working. Is anyone aware of what may be causing it, and of a way to fix it? or is it time for a new phone?
Thanks for your help!!
Is it possible the camera connction on the motherboard is a bit flaky?
audit13 said:
Is it possible the camera connction on the motherboard is a bit flaky?
Click to expand...
Click to collapse
Thanks for your reply. I thought that too after the second camera went wrong. I re-opened the phone and checked the connection, and from what I can see it seems quite solid. I am not sure what could possibly be going wrong that causing 2 camera modules to go bad in quick succession though. While the rest of the phone works perfectly.
Maybe it's just coincidence. I guess you could try a third camera to see what happens.
Can't connect to camera
My camera quit working the day I updated to 6.0.1
At first it would work for a few hours after a fresh boot. Now it won't work at all. I replaced the camera module with a working one and it worked for a few hours then died. Now all I get is "can't connect to camera". I'm convinced its related to the marshmallow update.
Safe mode doesn't help. Factory reset doesn't help. Third party apps still let me use the front camera but the rear is dead. I think I've reached the end of the road buying nexus devices and beta testing OS releases.
Maybe it because of your sd card
dixie600mhz said:
My camera quit working the day I updated to 6.0.1
At first it would work for a few hours after a fresh boot. Now it won't work at all. I replaced the camera module with a working one and it worked for a few hours then died. Now all I get is "can't connect to camera". I'm convinced its related to the marshmallow update.
Safe mode doesn't help. Factory reset doesn't help. Third party apps still let me use the front camera but the rear is dead. I think I've reached the end of the road buying nexus devices and beta testing OS releases.
Click to expand...
Click to collapse
Initially I thought this may be a normal issue of age of the phone, but the fact that a few of us are bumping into this so shortly after the marshmallow upgrade makes me think maybe the 2 things are related.
I suppose I could try and install a lollipop rom and buy yet another camera module.
The only component that should face problems in a persons lifetime would be the battery. It is a shame that companies and people treat this stuff as disposable.
OP and others who cannot fix this through software, or a small hardware change, this must be a hardware issue. Something on the mainboard is messing with the camera. Others are running stock marshmallow fine, to rule out any software issues, wipe all and flash new (manually wiping and flashing each partition from fastboot would be best). Report back.
wangdaning said:
The only component that should face problems in a persons lifetime would be the battery. It is a shame that companies and people treat this stuff as disposable.
OP and others who cannot fix this through software, or a small hardware change, this must be a hardware issue. Something on the mainboard is messing with the camera. Others are running stock marshmallow fine, to rule out any software issues, wipe all and flash new (manually wiping and flashing each partition from fastboot would be best). Report back.
Click to expand...
Click to collapse
Thanks for your reply. Done, but to no avail. Infact when you flash from fastboot the camera app is not even installed and the torch does not show up in the notification bar.
It is definitely a hardware issue, which is not resolved by simply replacing the camera module, as that seems to break again in a short amount of time. Not sure if I feel investing in a new mainboard and a new camera module.
Hello everybody!
Recently i bought one Motorola Photon Q and I found one weird problem with my Photon Q.
I cannot regulate the screen's backlight. When it is on 100% it is very bright, but anything below this point (in example 99% or 50%) it goes very dimmed. So, basically I have two levels of backlight. Minimum and maximum. Nothing in the middle.
I tried to regulate it from the recovery mode, but issue stays the same.
Phone already had TWRP and CM 13.
Any ideas what can I do about it?
Regards.
Wow you joined in September 2008 and this is your first post?
Congrats!!
As for the issue, it almost sounds hardware related. Like someone swapped the proximity sensor for the ambient light sensor... If the issue persists in recovery, I'm not sure flashing stock would do you any favors (not that you would want stock, it would just rule out any low-level software issues if you flash thru RSD Lite).
Yes yes, I know. There was nothing I could give from my side. Just usual user.
Changing the sensor? But does it have anything in common, while backlight sensivity is chosen manually?
I'll try to flash it by RSD lite.
Thanks.
MarioK15 said:
Changing the sensor? But does it have anything in common, while backlight sensivity is chosen manually?
I'll try to flash it by RSD lite.
Thanks.
Click to expand...
Click to collapse
Honestly was just firing off the hip based on you description - it sounds hardware related not software, especially since it persists in recovery...
To rule out software entirely, RSD Lite is the best way IMHO. Good luck.
Assuming it is a hardware issue... I'm not sure replacing that sensor is worth the effort. I guess it depends on your desire (and ability) to get this old PQ working properly
It might be the hardware problem. I installed some application to check sensors, and it does not detect proximity sensor.
I was wondering about dismounting this sensor, but probably it would not help at all.
Hi all
Has anyone faced the following problem: my watch updated to the latest Wear OS a week ago. And after this all the sensors died - no any single of them is working.
I've googled and tried everything I can - from multiple factory resets and linking watch to another phones to manually enabling app permissions for sensonrs and dev mode.
Nothing worked. Test in Dev mode shows "Fail" for all tests related to sensors.
Any ideas/advice on how to fix this?
koladko said:
Hi all
Has anyone faced the following problem: my watch updated to the latest Wear OS a week ago. And after this all the sensors died - no any single of them is working.
I've googled and tried everything I can - from multiple factory resets and linking watch to another phones to manually enabling app permissions for sensonrs and dev mode.
Nothing worked. Test in Dev mode shows "Fail" for all tests related to sensors.
Any ideas/advice on how to fix this?
Click to expand...
Click to collapse
My Watch 2 sport (4G) got the same issue after 1 year. Sent it to service and got a replacement for free.
Probably a HW issue not related to the SW update....
rettinn said:
My Watch 2 sport (4G) got the same issue after 1 year. Sent it to service and got a replacement for free.
Probably a HW issue not related to the SW update....
Click to expand...
Click to collapse
THanks... My watch is more than 1 year old, AFAIK warranty is over
Anyway - Thanks for advice!
Got exacly the same situation, i got my hands on a LEO-BX9 BT, when i install the older firmware 7.1.1 at the start the steps appear and the heart rate works good, but then it starts making updates and loosing the sensors data, i dont believe it's HW related as lower versions of Android Wear work without a problem. already tried almost every firmware available on XDA and the only one that worked all sensors (briefly before auto update) was sawfish-OWDD.180215.018 can anyone give me some guidelines about this? i am well informed about flashing, rooting etc. but this is new to me. flashing fastboot rom and even that way not beeing able to use the sensors.
EDIT: i know this is a old thread but this is still a beautiful watch and with capabilities to perform as a daily driver.
i came from a mi band 4 looking for more functions even if it costs charging a watch every night.
Ultimate edit: it is definitly hardware, i opened up my watch, used isopropyl alchool to clean up all contacts and it worked again, all sensors are now working except barometric sensor, it seems it had been submerged more that it can handle by the previous owner so it had water damage on it, it is near the microphone and it is unrecoverable unfortunatly. but hey, now you know. if you are having error in heart sensor, acelerometer and such. opening up and cleaning the board and contacts its a good idea. time to open up the drawer and reviving a smartwatch!
dxtremez said:
Got exacly the same situation, i got my hands on a LEO-BX9 BT, when i install the older firmware 7.1.1 at the start the steps appear and the heart rate works good, but then it starts making updates and loosing the sensors data, i dont believe it's HW related as lower versions of Android Wear work without a problem. already tried almost every firmware available on XDA and the only one that worked all sensors (briefly before auto update) was sawfish-OWDD.180215.018 can anyone give me some guidelines about this? i am well informed about flashing, rooting etc. but this is new to me. flashing fastboot rom and even that way not beeing able to use the sensors.
EDIT: i know this is a old thread but this is still a beautiful watch and with capabilities to perform as a daily driver.
i came from a mi band 4 looking for more functions even if it costs charging a watch every night.
Ultimate edit: it is definitly hardware, i opened up my watch, used isopropyl alchool to clean up all contacts and it worked again, all sensors are now working except barometric sensor, it seems it had been submerged more that it can handle by the previous owner so it had water damage on it, it is near the microphone and it is unrecoverable unfortunatly. but hey, now you know. if you are having error in heart sensor, acelerometer and such. opening up and cleaning the board and contacts its a good idea. time to open up the drawer and reviving a smartwatch!
Click to expand...
Click to collapse
Thank you for your advice . I did exactly what you have mentioned and now my smartwatch is working again .
Hi all, if anyone could help, I'd be really grateful as I'm now getting desperate!
My RN7Pro China did an OTA update this morning, I ended up with "System Destroyed", so did a reset via MIFlash.
Worked fine, except the right half of the touchscreen is now responding to touches inverted vertically...
What's really strange is the navbar buttons work perfectly across the whole screen, so I'm assuming this must be some sort of software glitch.
Left 50% functions as normal.
Navbar functions as normal.
Right 50% (except navbar) is vertically inverted, in-line horizontally.
Makes the phone almost unusable, I'm happy to try anything and everything to get this working again, I'm an IT engineer with 12y experience, so perfectly capable of following in-depth technical instructions if someone is able to suggest a fix?
I have tried flashing CN Stable/Dev and still have the same issue.
Issue also affects TWRP so I suspect it's changed something at a pretty low level that the Stock ROMs son't touch?
Many thanks for reading
john2k10 said:
Hi all, if anyone could help, I'd be really grateful as I'm now getting desperate!
My RN7Pro China did an OTA update this morning, I ended up with "System Destroyed", so did a reset via MIFlash.
Worked fine, except the right half of the touchscreen is now responding to touches inverted vertically...
What's really strange is the navbar buttons work perfectly across the whole screen, so I'm assuming this must be some sort of software glitch.
Left 50% functions as normal.
Navbar functions as normal.
Right 50% (except navbar) is vertically inverted, in-line horizontally.
Makes the phone almost unusable, I'm happy to try anything and everything to get this working again, I'm an IT engineer with 12y experience, so perfectly capable of following in-depth technical instructions if someone is able to suggest a fix?
I have tried flashing CN Stable/Dev and still have the same issue.
Issue also affects TWRP so I suspect it's changed something at a pretty low level that the Stock ROMs son't touch?
Many thanks for reading
Click to expand...
Click to collapse
Have you tried resetting the phone ( as in completely wiping out everything including OS) and then try installing MIUI, if it still persists try a custom ROM
Same issue here, China version in use and went to 10.3.9.0 where issue popped up. Tried to go back 10.3.5.0 but issue still exsist. Absolute annoying issue and makes phone totally unusable.:crying:
resetted of phone and etc, but no help.
Mine's now in a drawer, awaiting any form of fix.
I bought an Umidigi F1 Play while waiting......
Terrible issue and absolutely no support from Xiaomi.
Have personally owned Xiaomi phones since the Redmi 2 and never had any issues with flashing software.
Never again.
Try to flash china rom lowest version of miui 10 which is stable. Works for me.
Does not help, lowest u can flash is 1035 which will not fix the issue.
EDIT: flashed custom ROM, still issue persist
john2k10 said:
Hi all, if anyone could help, I'd be really grateful as I'm now getting desperate!
My RN7Pro China did an OTA update this morning, I ended up with "System Destroyed", so did a reset via MIFlash.
Worked fine, except the right half of the touchscreen is now responding to touches inverted vertically...
What's really strange is the navbar buttons work perfectly across the whole screen, so I'm assuming this must be some sort of software glitch.
Left 50% functions as normal.
Navbar functions as normal.
Right 50% (except navbar) is vertically inverted, in-line horizontally.
Makes the phone almost unusable, I'm happy to try anything and everything to get this working again, I'm an IT engineer with 12y experience, so perfectly capable of following in-depth technical instructions if someone is able to suggest a fix?
I have tried flashing CN Stable/Dev and still have the same issue.
Issue also affects TWRP so I suspect it's changed something at a pretty low level that the Stock ROMs son't touch?
Many thanks for reading
Click to expand...
Click to collapse
Looks like there's a hardware defect in your device, maybe you got a faulty device, try going to a recognised mi store and get it replaced
This is not hw defect, mine was fully functional before firmware update to 1.0.3.9.
mlackke said:
This is not hw defect, mine was fully functional before firmware update to 1.0.3.9.
Click to expand...
Click to collapse
What If the phone was dropped or smth..
Hi,
I have the same problem which occurred after update.
Bump. Has there ever been a software-related fix to this issue? I currently have the same problem as described by the OP on a XIAOMI MI 8 Lite (128GB, 6GB RAM), although it only appeared after unlocking the bootloader and flashing a custom recovery. I've been flashing ROMs for quite a few years now and also double-checked all the software I've been using, I am certain that I made no software-related mistake. Since encountering the issue I have reflashed various original stock firmwares from xiaomi using both the flashtool and twrp, all to no avail. I've even relocked the bootloader, just to be absolutely certain. Since the entire touchscreen still registers input, I find it hard to believe that it is a hardware related issue, especially since I never dropped my phone and it also never experienced any physical trauma (so to speak). Would really appreciate any further input.
john2k10 said:
Hi all, if anyone could help, I'd be really grateful as I'm now getting desperate!
My RN7Pro China did an OTA update this morning, I ended up with "System Destroyed", so did a reset via MIFlash.
Worked fine, except the right half of the touchscreen is now responding to touches inverted vertically...
What's really strange is the navbar buttons work perfectly across the whole screen, so I'm assuming this must be some sort of software glitch.
Left 50% functions as normal.
Navbar functions as normal.
Right 50% (except navbar) is vertically inverted, in-line horizontally.
Makes the phone almost unusable, I'm happy to try anything and everything to get this working again, I'm an IT engineer with 12y experience, so perfectly capable of following in-depth technical instructions if someone is able to suggest a fix?
I have tried flashing CN Stable/Dev and still have the same issue.
Issue also affects TWRP so I suspect it's changed something at a pretty low level that the Stock ROMs son't touch?
Many thanks for reading
Click to expand...
Click to collapse
Hi sir now I am facing same problem like inverted touch 50% of my phone screen can I know how you resolve this problem in past
mlackke said:
Same issue here, China version in use and went to 10.3.9.0 where issue popped up. Tried to go back 10.3.5.0 but issue still exsist. Absolute annoying issue and makes phone totally unusable.:crying:
resetted of phone and etc, but no help.
Click to expand...
Click to collapse
Hi sir now I am facing same problem like inverted touch 50% of my phone screen can I know how you resolve this problem in past
Has anyome fixed that yet? Is it even possible? I have tried everything, dowloaded tons of GB of roms, flashing programs, watched milion vids on YT, and still cant find anything. So i you find somethink, let me know <3
Prakashr09 said:
Hi sir now I am facing same problem like inverted touch 50% of my phone screen can I know how you resolve this problem in past
Click to expand...
Click to collapse
Is there any update ? Strange thing is, it seems not that many devices have this problem ... or I couldn't find other threads about this