Database Info

S6 Gyroscope problem

Hello guys. Yesterday I bought a Samsung Galaxy S6, the "normal" S6. I bought it from a guy, tested it 2 times everything fine but today I discovered that the rotation is not working properly. When i dial *#0*# and test the sensors, all pass but the gyro test fails. The phone doesn't have warranty, and I wanna know guys if you also got this problem and if you fixed it. If not, I could replace the gyroscope/accelerometer or what the heck is not working in a GSM service?
A friend told me that if the sensors are damaged then the phone can't be repaired. Please help me if you can. ?
PS: Sorry if I typed wrong.

If your friend doesn't repair phones for a living, then perhaps you should ask someone who does if it's repairable....
Sent from my SM-G920W8 using Tapatalk

Changing rom doesn't solve it? I haven't tried this yet..

It is possible that it could be a software glitch. I had the issue with my ex-S6 Edge, I got it fixed by telling Samsung to reinstall the firmware for me.
I now have an S6, I used Samsung Smart Switch yesterday to reinstall the firmware on my phone. It fixed some issues I had along with less heat and better battery runtime. I suggest you do the same, it's worth a try.
Just be sure to charge your phone to 100% and use *only* the original USB cable from Samsung. You could end up with a bricked phone if you use third party cables, other users have ended up with such fate.

DaryllSwer said:
It is possible that it could be a software glitch. I had the issue with my ex-S6 Edge, I got it fixed by telling Samsung to reinstall the firmware for me.
I now have an S6, I used Samsung Smart Switch yesterday to reinstall the firmware on my phone. It fixed some issues I had along with less heat and better battery runtime. I suggest you do the same, it's worth a try.
Just be sure to charge your phone to 100% and use *only* the original USB cable from Samsung. You could end up with a bricked phone if you use third party cables, other users have ended up with such fate.
Click to expand...
Click to collapse
I have the original cable, but if I use it there are no chances of bricking it right? I did 3 factory resets already, and I cand replace the sensor with problems, it will cost me pretty much. I also have something with the camera. It looks like it takes whiter pictures, I think. I'm going tomorrow in a store to see another S6, to see if the cameras are the same.

velea18 said:
I have the original cable, but if I use it there are no chances of bricking it right? I did 3 factory resets already, and I cand replace the sensor with problems, it will cost me pretty much. I also have something with the camera. It looks like it takes whiter pictures, I think. I'm going tomorrow in a store to see another S6, to see if the cameras are the same.
Click to expand...
Click to collapse
If your phone isn't rooted, if you haven't tripped KNOX. Then you should be good to use Samsung Smart Switch to reinstall the firmware. I used it just about four days ago to reinstall the firmware on my S6. Solved many problems for me. It's worth a shot before replacing the hardware.

Samsung Galaxy S7 Fix Suggestions - Possible Firmware Issue?

Hi All,
I am wondering if you can help me troubleshoot my Samsung Galaxy S7. I am open to any suggestion, even installing non-stock firmware or any other ideas you may have.
I bought the phone (on contract) around 5 months ago, For nearly 3 months now the phone has been freezing 5 - 6 times a day, restarting 2 or 3 times a day. It works for a little while, maybe a week after a factory reset. So my brain is telling me its a software issue as a hardware issue would surely be there from the first minute it reinstalls?
There is nothing obvious as to when it freezes, mostly when loading an app, So I imagine some corrupt kernel call. I would have thought a factory reset would have fixed this though but I guess its just reinstalling the same software and if this is corrupt.
Anyway, my provider in the UK or Samsung are not providing me with any suitable options other than we will "repair" it but will not RMA it and you will be without a phone for 2 months or so. well, this is just not good enough to me as when you pay £600 for a device (which even though I havnt paid as of yet, I am contracted to pay) You dont expect it to break after 2 months. Legally all they have to do is offer a "repair". I just know this is going to be more pain than its worth.
If anyone can help me at all with any possible solution, third party firmware to try and what steps I would need. I would appreciate any help.
Phone: Samsung Galaxy S7 32GB
Model: SM-G930F
Android: 6.0.1
Kernel: 3.18.14-9113173

I don't know buddy, I would wipe the phone clean, install the newest nougat beta and maybe install only a bunch of apps a day and see when you start having problems, maybe one of them is the cause. But that honestly sounds like a hardware issue. I hope this somewhat helps. Good luck

Same problem here. Its a faulty battery and/or power circuity. There is no software fix for that. Thats why it hangs or reboots while opening apps - that needs more amps to be drawn from the battery. Like loading thumbnails in gallery and so on.

TasEsmuEs said:
Same problem here. Its a faulty battery and/or power circuity. There is no software fix for that. Thats why it hangs or reboots while opening apps - that needs more amps to be drawn from the battery. Like loading thumbnails in gallery and so on.
Click to expand...
Click to collapse
Thanks for both replies.
I have tried to reset, still happening, cant install nougat as it freezes as soon as odin recognises it.
I guess I have no choice but to send it to them, I just know I will have problems now for months.

Bluetooth not working

Not sure if this is just my phone but bluetooth has not been working the last update of 7.1.2 and Android O the most recent version. When I toggle bluetooth it does not activate and i have tried clearing out the cache. Not sure if this is a software issue or possible related to hardware. I did have a good drop with my phone although nothing on the exterior appears damaged. Not sure if anyone else is experiencing the same thing.

Just RMAing the phone. It appears that it is only my phone doing it. Actually Google's customer service is really good. I'm glad I bought from them.
I had a Galaxy S4 from Samsung in 2013 and the battery ended up swelling and I called them for a replacement which they would not replace, but would thoughtfully sell me a new battery. Then they lost $5.3 billion from their Note 7 recall due to the battery and I was very happy and laughed.

Was this just the phone audio in your car by chance? I have a similar issue and have an open case with google about it.

marc.ientilucci said:
Was this just the phone audio in your car by chance? I have a similar issue and have an open case with google about it.
Click to expand...
Click to collapse
No it's definitely the phone. I have my Nexus 5x right now on 8.0 and it's working fine. Nothing wrong with the software.
I use Android auto as well and it's working fine. There's something wrong with the hardware component in the phone most likely. I have a 2017 Honda Civic
Did an RMA and sending it out.

mikeprius said:
No it's definitely the phone. I have my Nexus 5x right now on 8.0 and it's working fine. Nothing wrong with the software.
I use Android auto as well and it's working fine. There's something wrong with the hardware component in the phone most likely. I have a 2017 Honda Civic
Did an RMA and sending it out.
Click to expand...
Click to collapse
sorry - let me clarify my question. Was bluetooth media working and just not phone calls over bluetooth? I have a 2017 honda civic as well (LX version so a dumb head unit) and only having bluetooth phone call issues. I can play spotify and other stuff like youtube just fine.

marc.ientilucci said:
sorry - let me clarify my question. Was bluetooth media working and just not phone calls over bluetooth? I have a 2017 honda civic as well (LX version so a dumb head unit) and only having bluetooth phone call issues. I can play spotify and other stuff like youtube just fine.
Click to expand...
Click to collapse
No. Bluetooth would not activate at all so nothing worked. When i toggled the switch it would not turn on and scan for bluetooth. It appears that my situation was much significant as nothing worked. My replacement should be here tommorow. For your stock rooted set up did you just boot into TWRP then flash the latest SU ? Lately I've been running stock, so I don't know what the most recent form to root is for 8.0
Last time I rooted was like April or May of this year, but I just booted the TWRP image, flash TWRP, then flash SU

I've been stock rooted for some time but for the 8.0 update I rooted with SuperSU SRS3 via TWRP. Google had me actually grab a bug report and shoot it over to them along with information about the bluetooth radio manufacture of the car. I am cool with continuing to help them out. anyway, thanks for your feedback and i hope the new one works!

Got my new pixel replacement. It was the phone, I'm on the latest 7.1.2 update and it's working fine. The refurb looks brand new, you can tell it's a refurb by the charging port, but the rest of the phone is virtually new. No scratches on the glass or scuffs on the metal body. Compared to the current pixel I have with multiple long scratches along the front glass screen, even though it's a refurb its still in much better condition than my current Pixel.
I noticed my night light is super orange the screen is compared to my current Pixel. I think this is an issue related to earlier batches of the Pixel. It's just very orange with the night light but given the condition my current pixel is in, I'll still take it over my current one.

What Custom ROM that fixes Microphone Issue?

As we all know Pixels have this dreaded microphone issue. Sometimes it works, sometimes not. If you restart the phone, it temporary fix the problem and after few minutes/hours my mic doesn't respond again. I tried to flash different official rom released from https://developers.google.com/android/images but the issue is still there. I believe it's software issue because the hardware works. I'm now looking to root my phone and flash a custom rom, maybe they fixed the issue in their end.
I installed Sound Meter and Mic Tester to check once in while (you should too) if my mic is working. When I found that the mic don't respond the way it should, that's the time I restart my phone.
* Flashed different versions of: Nougat, Oreo, P (preview) ... but the issue is still there.
Can we list the Custom ROMs that fixes this annoying problem (is there any)?
Sound Meter(if mic is working)
https://photos.app.goo.gl/kcU0APX2pNPYjoG12
Sound Meter(No Response)
https://photos.app.goo.gl/a1lqNeyogTtuHRkE3
Mic Tester (if mic is working)
https://photos.app.goo.gl/K7oZYvSQDS2ndJHc2
Mic Tester (Flat)
https://photos.app.goo.gl/6BPoSryI3ECNJxwu1

chrizcrozz said:
As we all know Pixels have this dreaded microphone issue. Sometimes it works, sometimes are not. I tried to flash different official release from https://developers.google.com/android/images but the issue is still there. I believe it's software issue because the hardware works.
Can we list the Custom ROMs that fixes this annoying problem?
Click to expand...
Click to collapse
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once

jacobas92 said:
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once
Click to expand...
Click to collapse
Did you try to install Sound Meter and Mic Tester? If yes, is it stable (referring to mic Issue)?

chrizcrozz said:
Did you try to install Sound Meter and Mic Tester? If yes, is it stable (referring to mic Issue)?
Click to expand...
Click to collapse
No, I would just lose microphone functionality for a minute at a time, sometimes longer. It happened in phone calls a lot. I just thought my mic was going out but I'm glad I tried a few other roms before buying a new phone. I feel like my issue was far different from your current problems

If this was a software issue, everyone running android 8.1 would have this issue. This sounds like the audio codec manufacturing defect. Unless you have an app that is interfering with something, probably not software

That's weird,. I haven't encountered that issue not on stock but I never stayed on stock for long though as I flashed custom rom a couple of days after receiving my phone. Bought it new in March. I'm running Dirty Unicorns rom though, can be found from the link to Discord on my signature.

I'm definitely interested if you find anything. Installed the April update over the weekend and bam, no mic and random reboots. Factory reset didn't help. I would think it's firmware related since it happened immediately after the update, but idk. Both Sound Meter and Mic Tester show no response.

UPDATE:
I tried to load a custom ROM - Resurrection Remix 6
So far so good. I haven't experience the problem this day.
Usually, I restart my phone 6-8(or more) times a day just to temporary fix the microphone issue.
I will observe in a few days and update this asap.

UPDATE
Resurrection Remix 6.0 works great! I didn't have any problems! It seems fixes that microphone bug.
I have uptime of 36 hours and counting with out restarting my phone. I had few voice calls and few net calls (FB and Skype).
Super big thanks to all who's involved in making that project.
https://photos.app.goo.gl/60ABq4dUFnKNKAcE2

I installed Resurrection Remix 6 and I still have the same microphone issue. Can someone please confirm if by downgrading the problem will be fixed? Thank you.

chrizcrozz said:
UPDATE
Resurrection Remix 6.0 works great! I didn't have any problems! It seems fixes that microphone bug.
I have uptime of 36 hours and counting with out restarting my phone. I had few voice calls and few net calls (FB and Skype).
Super big thanks to all who's involved in making that project.
https://photos.app.goo.gl/60ABq4dUFnKNKAcE2
Click to expand...
Click to collapse
Do I need to downgrade before flashing Resurrection Remix 6.0?
I'm on 8.1.

jacobas92 said:
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once
Click to expand...
Click to collapse
Man, you can comfirm that you got no audio and microphone problems on android P?
If so, I will cry. :,)

zeth717 said:
Man, you can comfirm that you got no audio and microphone problems on android P?
If so, I will cry. :,)
Click to expand...
Click to collapse
problem persisting in Android P too..... i upgraded last night and works well for few hours, then today, starts again........

Thanks for the tip. Ever since I got the June 18 update (D1 android 8.1) I've had random reboots, mic and the odd speaker issue.
I rooted stock with twrp n magick no difference. Even b4 restoring apps. So this week have installed pixel dust. Such a great time BUT mic n speaker problems persist, and the random reboots have become complete crashes. Where I think my phone is bricked, but if you hold power long enough it reboots. That's where I'm at now. Barely got any apps installed, dealing with it. I think I'll give ressurection ROM a ago tomorrow. Thanks for the tip. I know easily when it's happening, because I use ok Google and voice typing ALOT.
I can't believe that only last month I was totally ignorant to this issue and loved my pixel a bit too much. Now it's like dancing with a dragon ?
Does anyone else have any more tips for dealing with this?

mattyyey said:
Thanks for the tip. Ever since I got the June 18 update (D1 android 8.1) I've had random reboots, mic and the odd speaker issue.
I rooted stock with twrp n magick no difference. Even b4 restoring apps. So this week have installed pixel dust. Such a great time BUT mic n speaker problems persist, and the random reboots have become complete crashes. Where I think my phone is bricked, but if you hold power long enough it reboots. That's where I'm at now. Barely got any apps installed, dealing with it. I think I'll give ressurection ROM a ago tomorrow. Thanks for the tip. I know easily when it's happening, because I use ok Google and voice typing ALOT.
I can't believe that only last month I was totally ignorant to this issue and loved my pixel a bit too much. Now it's like dancing with a dragon
Does anyone else have any more tips for dealing with this?
Click to expand...
Click to collapse
I was also pleasantly oblivious a week ago. And I've been running on the March 2018 security patch since...well...March. So I can confirm this issue isn't caused by the June (or April, as another hypothesized) security patch. I haven't updated because I've been using Magisk for root since day 1 (opted not to install twrp), and the one time I system-updated to March, it don't go smoothly with magisk.
My repeating symptoms:
Mic failure some number of hours after boot.
And yesterday (not sure if it's repeating):
Could not receive income phone calls
so I received a Hangouts call instead, and phone did not stop vibrating until the Hangouts call was finished.
Around the time these symptoms started I had:
1 never-before-seen phone brick while I wasn't looking at it. Picked up phone, black screen, no response. Held power button for ~10 seconds to reboot.
1 never-before-seen instance of super laggy scrolling. Freezing for a second before it would scroll. Rebooted to fix.
Claimed fixes:
some say uninstalling apps solved it
some say upgrading to P
some say replacing the motherboard
The frustrating part is not having any way to know what the problem is or what the solution is. And people are experiencing different symptoms, so we can't even be sure we are having the same problem.
This article https://9to5google.com/2018/02/08/google-lawsuit-pixel-defective-microphone/ explains the cause:
If you’ll recall, Google’s 2016 Pixel devices, the Pixel and Pixel XL, faced microphones issues not too long after launch. As Google explained in early 2017, this issue was attributed to “a hairline crack in the solder connection on the audio codec,” with a warranty replacement being the only reliable fix. Later on in the manufacturing process, Google refined this part of the device to reduce the chances of this problem occurring.
Obviously, that was a frustrating issue for Pixel users, as it essentially disabled all three microphones on the device. What made the problem worse, though, was that holding the device in a different way or even a change in temperature could make the problem come back after it had seemingly gone away.
Click to expand...
Click to collapse
Free Motherboard replacements are being offered http://piunikaweb.com/2018/05/03/untangling-google-og-pixel-motherboard-replacement-mess/ by UBreakIFix:
Google is providing free motherboard replacements, but only to those encountering bootloops due to microphone-related issues (lawsuit affect?). Some one who claims to be working for uBreakiFix have recently confirmed this on a Reddit thread discussing the matter.
Click to expand...
Click to collapse

abemore said:
I was also pleasantly oblivious a week ago. And I've been running on the March 2018 security patch since...well...March. So I can confirm this issue isn't caused by the June (or April, as another hypothesized) security patch. I haven't updated because I've been using Magisk for root since day 1 (opted not to install twrp), and the one time I system-updated to March, it don't go smoothly with magisk.
My repeating symptoms:
Mic failure some number of hours after boot.
And yesterday (not sure if it's repeating):
Could not receive income phone calls
so I received a Hangouts call instead, and phone did not stop vibrating until the Hangouts call was finished.
Around the time these symptoms started I had:
1 never-before-seen phone brick while I wasn't looking at it. Picked up phone, black screen, no response. Held power button for ~10 seconds to reboot.
1 never-before-seen instance of super laggy scrolling. Freezing for a second before it would scroll. Rebooted to fix.
Claimed fixes:
some say uninstalling apps solved it
some say upgrading to P
some say replacing the motherboard
The frustrating part is not having any way to know what the problem is or what the solution is. And people are experiencing different symptoms, so we can't even be sure we are having the same problem.
This article https://9to5google.com/2018/02/08/google-lawsuit-pixel-defective-microphone/ explains the cause:
Free Motherboard replacements are being offered http://piunikaweb.com/2018/05/03/untangling-google-og-pixel-motherboard-replacement-mess/ by UBreakIFix:
Click to expand...
Click to collapse
I never had bootloops but the mic and audio issue, with stockROM, pixel dust and CrDroid. Then I heard about the ubreakifix possibility and when to the next store and they changed the MB without hesitation. Since then it works like a charm. Just go there, they are very helpful. That's a hardware issue not a software one.

Long story short - the update triggers the behavior(s), but its actually a manufacturing fault. You can replace part or your full motherboard to fix it. I personally just flashed stock and took it back to EE and they replaced it no cost. I remembering reading its a common problem with a certain early batch of Pixels. I've lost the link but you can use your serial number to check if its an early version thats effected. Apparently its only effects less than 3% of phones but the problem looks bigger when i was searching lmfao.
Anyway software fixes might help, but ultimately its a hardware issue. Get it replaced. Yeah they sent me a new one with a locked bootloader so i have to start from scratch but thats better than living with the error.

mattyyey said:
Long story short - the update triggers the behavior(s), but its actually a manufacturing fault. You can replace part or your full motherboard to fix it. I personally just flashed stock and took it back to EE and they replaced it no cost. I remembering reading its a common problem with a certain early batch of Pixels. I've lost the link but you can use your serial number to check if its an early version thats effected. Apparently its only effects less than 3% of phones but the problem looks bigger when i was searching lmfao.
Anyway software fixes might help, but ultimately its a hardware issue. Get it replaced. Yeah they sent me a new one with a locked bootloader so i have to start from scratch but thats better than living with the error.
Click to expand...
Click to collapse
You're right. I ended up getting a free repair from uBreakifix. The guy said he wasn't allowed to tell me what he did to fix it. I noticed he had downgraded me from Android 9 to 7.1.2. I hoped that wasn't the secret fix. On closer examination, I noticed the serial number had changed, which means they replaced my motherboard...for free...on an out of warranty Pixel that I bought second hand. :good:

Huawei Watch 2 Sport - all sensors are dear after latest Wear OS update

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 .